]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
6e850809edd7dee59fc652e6b693aec1e6005dbe
[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>PGP key transition statement for key EE4E02F9</title>
11 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
13 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
14 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
15 set it up properly. I wanted to generate it offline and have it
16 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
17 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
18 time to sit down with an offline machine almost took forever. But
19 finally I&#39;ve been able to complete the process, and have now moved
20 from my old GPG key to a new GPG key. See
21 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
22 full transition statement, signed with both my old and new key&lt;/a&gt; for
23 the details. This is my new key:&lt;/p&gt;
24
25 &lt;pre&gt;
26 pub 3936R/&lt;a href=&quot;http://pgp.cs.uu.nl/stats/EE4E02F9.html&quot;&gt;EE4E02F9&lt;/a&gt; 2015-11-03 [expires: 2019-11-14]
27 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
28 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
29 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
30 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
31 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
32 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
33 &lt;/pre&gt;
34
35 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
36 my old key.&lt;/p&gt;
37
38 &lt;p&gt;If you signed my old key
39 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
40 I&#39;d very much appreciate a signature on my new key, details and
41 instructions in the transition statement. I m happy to reciprocate if
42 you have a similarly signed transition statement to present.&lt;/p&gt;
43 </description>
44 </item>
45
46 <item>
47 <title>The life and death of a laptop battery</title>
48 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
49 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
50 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
51 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
52 But this do not last. The last few laptops gave me a feeling that
53 within a year, the life time is just a fraction of what it used to be,
54 and it slowly become painful to use the laptop without power connected
55 all the time. Because of this, when I got a new Thinkpad X230 laptop
56 about two years ago, I decided to monitor its battery state to have
57 more hard facts when the battery started to fail.&lt;/p&gt;
58
59 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
60
61 &lt;p&gt;First I tried to find a sensible Debian package to record the
62 battery status, assuming that this must be a problem already handled
63 by someone else. I found
64 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
65 which collects statistics from the battery, but it was completely
66 broken. I sent a few suggestions to the maintainer, but decided to
67 write my own collector as a shell script while I waited for feedback
68 from him. Via
69 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
70 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
71 discovered
72 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
73 available in Debian.&lt;/p&gt;
74
75 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
76 battery stats ever since. Now my
77 /var/log/hjemmenett-battery-status.log file contain around 115,000
78 measurements, from the time the battery was working great until now,
79 when it is unable to charge above 7% of original capacity. My
80 collector shell script is quite simple and look like this:&lt;/p&gt;
81
82 &lt;pre&gt;
83 #!/bin/sh
84 # Inspired by
85 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
86 # See also
87 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
88 logfile=/var/log/hjemmenett-battery-status.log
89
90 files=&quot;manufacturer model_name technology serial_number \
91 energy_full energy_full_design energy_now cycle_count status&quot;
92
93 if [ ! -e &quot;$logfile&quot; ] ; then
94 (
95 printf &quot;timestamp,&quot;
96 for f in $files; do
97 printf &quot;%s,&quot; $f
98 done
99 echo
100 ) &gt; &quot;$logfile&quot;
101 fi
102
103 log_battery() {
104 # Print complete message in one echo call, to avoid race condition
105 # when several log processes run in parallel.
106 msg=$(printf &quot;%s,&quot; $(date +%s); \
107 for f in $files; do \
108 printf &quot;%s,&quot; $(cat $f); \
109 done)
110 echo &quot;$msg&quot;
111 }
112
113 cd /sys/class/power_supply
114
115 for bat in BAT*; do
116 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
117 done
118 &lt;/pre&gt;
119
120 &lt;p&gt;The script is called when the power management system detect a
121 change in the power status (power plug in or out), and when going into
122 and out of hibernation and suspend. In addition, it collect a value
123 every 10 minutes. This make it possible for me know when the battery
124 is discharging, charging and how the maximum charge change over time.
125 The code for the Debian package
126 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
127 available on github&lt;/a&gt;.&lt;/p&gt;
128
129 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
130
131 &lt;pre&gt;
132 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
133 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
134 [...]
135 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
136 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
137 &lt;/pre&gt;
138
139 &lt;p&gt;I wrote a small script to create a graph of the charge development
140 over time. This graph depicted above show the slow death of my laptop
141 battery.&lt;/p&gt;
142
143 &lt;p&gt;But why is this happening? Why are my laptop batteries always
144 dying in a year or two, while the batteries of space probes and
145 satellites keep working year after year. If we are to believe
146 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
147 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
148 chance, and the fix is to not charge the Lithium-ion batteries to 100%
149 all the time, but to stay below 90% of full charge most of the time.
150 I&#39;ve been told that the Tesla electric cars
151 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
152 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
153 100% when preparing for a longer trip (not that I would want a car
154 like Tesla where rights to privacy is abandoned, but that is another
155 story), which I guess is the option we should have for laptops on
156 Linux too.&lt;/p&gt;
157
158 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
159 stop charging at 80%, unless requested to charge to 100% once in
160 preparation for a longer trip? I found
161 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
162 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
163 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
164 load).&lt;/p&gt;
165
166 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
167 at the start. I also wonder why the &quot;full capacity&quot; increases some
168 times, and if it is possible to repeat the process to get the battery
169 back to design capacity. And I wonder if the discharge and charge
170 speed change over time, or if this stay the same. I did not yet try
171 to write a tool to calculate the derivative values of the battery
172 level, but suspect some interesting insights might be learned from
173 those.&lt;/p&gt;
174
175 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
176 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
177 packages instead of the tp-smapi-dkms package I had tried to use
178 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
179 and stop. I&#39;ve done so now, but expect my existing battery is toast
180 and need to be replaced. The proposal is unfortunately Thinkpad
181 specific.&lt;/p&gt;
182 </description>
183 </item>
184
185 <item>
186 <title>New laptop - some more clues and ideas based on feedback</title>
187 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
188 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
189 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
190 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
191 need for a new laptop, and provided very useful feedback. I wish to
192 thank every one of these. Several pointed me to the possibility of
193 fixing my X230, and I am already in the process of getting Lenovo to
194 do so thanks to the on site, next day support contract covering the
195 machine. But the battery is almost useless (I expect to replace it
196 with a non-official battery) and I do not expect the machine to live
197 for many more years, so it is time to plan its replacement. If I did
198 not have a support contract, it was suggested to find replacement parts
199 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
200 might present a language barrier as I do not understand French.&lt;/p&gt;
201
202 &lt;p&gt;One tip I got was to use the
203 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
204 compare laptop models. It seem to have more models available than
205 prisjakt.no. Another tip I got from someone I know have similar
206 keyboard preferences was that the HP EliteBook 840 keyboard is not
207 very good, and this matches my experience with earlier EliteBook
208 keyboards I tested. Because of this, I will not consider it any further.
209
210 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
211 newest Thinkpad X model. The keyboard reintroduces mouse buttons
212 (which is missing from the X240), and is working fairly well with
213 Debian Sid/Unstable according to
214 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
215 got on the keyboard quality are not consistent. Some say the keyboard
216 is good, others say it is ok, while others say it is not very good.
217 Those with experience from X41 and and X60 agree that the X250
218 keyboard is not as good as those trusty old laptops, and suggest I
219 keep and fix my X230 instead of upgrading, or get a used X230 to
220 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
221 activity and battery status, which is very convenient on my X230. I&#39;m
222 also told that the CPU fan is running very often, making it a bit
223 noisy. In any case, the X250 do not work out of the box with Debian
224 Stable/Jessie, one of my requirements.&lt;/p&gt;
225
226 &lt;p&gt;I have also gotten a few vendor proposals, one was
227 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
228 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
229 The latter look very attractive to me.&lt;/p&gt;
230
231 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
232 as I keep looking for a replacement.&lt;/p&gt;
233
234 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
235 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
236 different
237 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
238 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
239 </description>
240 </item>
241
242 <item>
243 <title>Time to find a new laptop, as the old one is broken after only two years</title>
244 <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>
245 <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>
246 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
247 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
248 replacement soon. The left 5 cm of the screen on my Thinkpad X230
249 started flickering yesterday, and I suspect the cause is a broken
250 cable, as changing the angle of the screen some times get rid of the
251 flickering.&lt;/p&gt;
252
253 &lt;p&gt;My requirements have not really changed since I bought it, and is
254 still as
255 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
256 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
257 good help from
258 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
259 where I could select at least a few of the requirements (mouse pin,
260 wifi, weight) and go through the rest manually. Three button mouse
261 and a good keyboard is not available as an option, and all the three
262 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
263 G2) lack three mouse buttons). It is also unclear to me how good the
264 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
265 the keyboard, even if the quality and robustness in the X series have
266 deteriorated since X41.&lt;/p&gt;
267
268 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
269 seem sensible to me? Are there better services around to search the
270 set of available laptops for features? Please send me an email if you
271 have suggestions.&lt;/p&gt;
272
273 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
274 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
275 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
276 </description>
277 </item>
278
279 <item>
280 <title>How to stay with sysvinit in Debian Jessie</title>
281 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
282 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
283 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
284 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
285 sysvinit as its boot system by default. But how can one keep using
286 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
287 courtesy of
288 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
289 Schubert&lt;/a&gt; and
290 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
291 McVittie&lt;/a&gt;.
292
293 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
294 keep sysvinit as your boot system, create a file
295 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
296 you upgrade:&lt;/p&gt;
297
298 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
299 Package: systemd-sysv
300 Pin: release o=Debian
301 Pin-Priority: -1
302 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
303
304 &lt;p&gt;This file content will tell apt and aptitude to not consider
305 installing systemd-sysv as part of any installation and upgrade
306 solution when resolving dependencies, and thus tell it to avoid
307 systemd as a default boot system. The end result should be that the
308 upgraded system keep using sysvinit.&lt;/p&gt;
309
310 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
311 get sysvinit installed by default (debootstrap used by
312 debian-installer have no option for this), but one can tell the
313 installer to switch to sysvinit before the first boot. Either by
314 using a kernel argument to the installer, or by adding a line to the
315 preseed file used. First, the kernel command line argument:
316
317 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
318 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
319 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
320
321 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
322
323 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
324 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
325 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
326
327 &lt;p&gt;One can of course also do this after the first boot by installing
328 the sysvinit-core package.&lt;/p&gt;
329
330 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
331 sysvinit boot sequence in Debian have several hardware specific bugs
332 on Linux caused by the fact that it is unpredictable when hardware
333 devices show up during boot. But on the other hand, the new default
334 boot system still have a few rough edges I hope will be fixed before
335 Jessie is released.&lt;/p&gt;
336
337 &lt;p&gt;Update 2014-11-26: Inspired by
338 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
339 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
340 line.&lt;/p&gt;
341 </description>
342 </item>
343
344 <item>
345 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
346 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
347 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
348 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
349 <description>&lt;p&gt;The right to communicate with your friends and family in private,
350 without anyone snooping, is a right every citicen have in a liberal
351 democracy. But this right is under serious attack these days.&lt;/p&gt;
352
353 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
354 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
355 the whisleblower Snowden) more expensive for Internet email,
356 is to deliver all email using SMTP via Tor. Such SMTP option would be
357 a nice addition to the FreedomBox project if we could send email
358 between FreedomBox machines without leaking metadata about the emails
359 to the people peeking on the wire. I
360 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
361 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
362 lot of useful feedback and suggestions. It also became obvious to me
363 that this was not a novel idea, as the same idea was tested and
364 documented by Johannes Berg as early as 2006, and both
365 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
366 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
367 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
368
369 &lt;p&gt;To implement such system one need to set up a Tor hidden service
370 providing the SMTP protocol on port 25, and use email addresses
371 looking like username@hidden-service-name.onion. With such addresses
372 the connections to port 25 on hidden-service-name.onion using Tor will
373 go to the correct SMTP server. To do this, one need to configure the
374 Tor daemon to provide the hidden service and the mail server to accept
375 emails for this .onion domain. To learn more about Exim configuration
376 in Debian and test the design provided by Johannes Berg in his FAQ, I
377 set out yesterday to create a Debian package for making it trivial to
378 set up such SMTP over Tor service based on Debian. Getting it to work
379 were fairly easy, and
380 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
381 source code for the Debian package&lt;/a&gt; is available from github. I
382 plan to move it into Debian if further testing prove this to be a
383 useful approach.&lt;/p&gt;
384
385 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
386 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
387 get rid of exim4). Install tor, clone the git repository mentioned
388 above, build the deb and install it on the machine. Next, run
389 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
390 the instructions to get the service up and running. Restart tor and
391 exim when it is done, and test mail delivery using swaks like
392 this:&lt;/p&gt;
393
394 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
395 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
396 --to fbx@dutlqrrmjhtfa3vp.onion
397 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
398
399 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
400 address with your own address to test your server. :)&lt;/p&gt;
401
402 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
403 easier and more automatic. Especially the tor setup need more work.
404 Also, the package include a tor-smtp tool written in C, but its task
405 should probably be rewritten in some script language to make the deb
406 architecture independent. It would probably also make the code easier
407 to review. The tor-smtp tool currently need to listen on a socket for
408 exim to talk to it and is started using xinetd. It would be better if
409 no daemon and no socket is needed. I suspect it is possible to get
410 exim to run a command line tool for delivery instead of talking to a
411 socket, and hope to figure out how in a future version of this
412 system.&lt;/p&gt;
413
414 &lt;p&gt;Until I wipe my test machine, I can be reached using the
415 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
416 SMTorP. :)&lt;/p&gt;
417 </description>
418 </item>
419
420 <item>
421 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
422 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
423 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
424 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
425 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
426 alioth.debian.org, you know the web interface is fairly slow to
427 operate. First you visit one web page, enter the moderation password
428 and get a new page shown with a list of all the messages to moderate
429 and various options for each email address. This take a while for
430 every list you moderate, and you need to do it regularly to do a good
431 job as a list moderator. But there is a quick alternative,
432 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
433 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
434 to moderate in a fraction of a second. Here is a test run on two
435 lists I recently took over:&lt;/p&gt;
436
437 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
438 % time listadmin xiph
439 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
440 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
441
442 real 0m1.709s
443 user 0m0.232s
444 sys 0m0.012s
445 %
446 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
447
448 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
449 there are no message in the moderation queue. Every morning I
450 currently moderate 68 mailman lists, and it normally take around two
451 minutes. When I took over the two pkg-xiph lists above a few days
452 ago, there were 400 emails waiting in the moderator queue. It took me
453 less than 15 minutes to process them all using the listadmin
454 program.&lt;/p&gt;
455
456 &lt;p&gt;If you install
457 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
458 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
459 with content like this, the moderation task is a breeze:&lt;/p&gt;
460
461 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
462 username username@example.org
463 spamlevel 23
464 default discard
465 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
466
467 password secret
468 adminurl https://{domain}/mailman/admindb/{list}
469 mailman-list@lists.example.com
470
471 password hidden
472 other-list@otherserver.example.org
473 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
474
475 &lt;p&gt;There are other options to set as well. Check the manual page to
476 learn the details.&lt;/p&gt;
477
478 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
479 the SSL certificate is self signed or not properly signed by a
480 generally accepted signing authority, you can set a environment
481 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
482
483 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
484 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
485 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
486
487 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
488 can provide an argument to the listadmin script like I do in the
489 initial screen dump (the xiph argument). Using an argument, only
490 lists matching the argument string will be processed. This make it
491 quick to accept messages if you notice the moderation request in your
492 email.&lt;/p&gt;
493
494 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
495 mailing lists, as I simply do not have time to spend on that if the
496 process was any slower. The listadmin program have saved me hours of
497 time I could spend elsewhere over the years. It truly is nice free
498 software.&lt;/p&gt;
499
500 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
501 activities, please send Bitcoin donations to my address
502 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
503
504 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
505 configuration example. Also, I&#39;ve been told that the
506 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
507 sure why.&lt;/p&gt;
508 </description>
509 </item>
510
511 <item>
512 <title>Debian Jessie, PXE and automatic firmware installation</title>
513 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
515 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
516 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
517 problem that the WiFi card require some firmware to work properly.
518 And it has been a pain to fix this using preseeding in Debian.
519 Normally something more is needed. But thanks to
520 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
521 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
522 to do this using simple preseeding.&lt;/p&gt;
523
524 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
525 firmware for the hardware found in the machine (actually, requested by
526 the kernel modules for the hardware). (It can also install user space
527 programs supporting the hardware detected, but that is not the focus
528 of this story.)&lt;/p&gt;
529
530 &lt;p&gt;To get this working in the default installation, two preeseding
531 values are needed. First, the isenkram-cli package must be installed
532 into the target chroot (aka the hard drive) before tasksel is executed
533 in the pkgsel step of the debian-installer system. This is done by
534 preseeding the base-installer/includes debconf value to include the
535 isenkram-cli package. The package name is next passed to debootstrap
536 for installation. With the isenkram-cli package in place, tasksel
537 will automatically use the isenkram tasks to detect hardware specific
538 packages for the machine being installed and install them, because
539 isenkram-cli contain tasksel tasks.&lt;/p&gt;
540
541 &lt;p&gt;Second, one need to enable the non-free APT repository, because
542 most firmware unfortunately is non-free. This is done by preseeding
543 the apt-mirror-setup step. This is unfortunate, but for a lot of
544 hardware it is the only option in Debian.&lt;/p&gt;
545
546 &lt;p&gt;The end result is two lines needed in your preseeding file to get
547 firmware installed automatically by the installer:&lt;/p&gt;
548
549 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
550 base-installer base-installer/includes string isenkram-cli
551 apt-mirror-setup apt-setup/non-free boolean true
552 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
553
554 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
555 both firmware and user space packages when using this method. It also
556 do not work well, so use version 0.15 or later. Installing both
557 firmware and user space packages might give you a bit more than you
558 want, so I decided to split the tasksel task in two, one for firmware
559 and one for user space programs. The firmware task is enabled by
560 default, while the one for user space programs is not. This split is
561 implemented in the package currently in unstable.&lt;/p&gt;
562
563 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
564 this recipe work for you. :)&lt;/p&gt;
565
566 &lt;p&gt;So, I bet you are wondering, how can this work. First and
567 foremost, it work because tasksel is modular, and driven by whatever
568 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
569 isenkram-cli package place two files for tasksel to find. First there
570 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
571
572 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
573 Task: isenkram-packages
574 Section: hardware
575 Description: Hardware specific packages (autodetected by isenkram)
576 Based on the detected hardware various hardware specific packages are
577 proposed.
578 Test-new-install: show show
579 Relevance: 8
580 Packages: for-current-hardware
581
582 Task: isenkram-firmware
583 Section: hardware
584 Description: Hardware specific firmware packages (autodetected by isenkram)
585 Based on the detected hardware various hardware specific firmware
586 packages are proposed.
587 Test-new-install: mark show
588 Relevance: 8
589 Packages: for-current-hardware-firmware
590 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
591
592 &lt;p&gt;The key parts are Test-new-install which indicate how the task
593 should be handled and the Packages line referencing to a script in
594 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
595 list of packages to install. The for-current-hardware-firmware script
596 look like this to list relevant firmware for the machine:
597
598 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
599 #!/bin/sh
600 #
601 PATH=/usr/sbin:$PATH
602 export PATH
603 isenkram-autoinstall-firmware -l
604 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
605
606 &lt;p&gt;With those two pieces in place, the firmware is installed by
607 tasksel during the normal d-i run. :)&lt;/p&gt;
608
609 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
610 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
611 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
612 install.&lt;/p&gt;
613
614 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
615 pilots in testing this feature, as isenkram is used there now to
616 install firmware, replacing the earlier scripts.&lt;/p&gt;
617 </description>
618 </item>
619
620 <item>
621 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
622 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
624 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
625 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
626 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
627 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
628 on a screen normally showing the bread types and prizes:&lt;/p&gt;
629
630 &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;
631
632 &lt;p&gt;If it had booted as it was supposed to, I would never had known
633 about this hidden Linux installation. It is interesting what
634 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
635 </description>
636 </item>
637
638 <item>
639 <title>New lsdvd release version 0.17 is ready</title>
640 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
641 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
642 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
643 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
644 got a new set of developers a few weeks ago, after the original
645 developer decided to step down and pass the project to fresh blood.
646 This project is now maintained by Petter Reinholdtsen and Steve
647 Dibb.&lt;/p&gt;
648
649 &lt;p&gt;I just wrapped up
650 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
651 new lsdvd release&lt;/a&gt;, available in git or from
652 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
653 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
654 0.17.&lt;/p&gt;
655
656 &lt;ul&gt;
657
658 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
659 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
660 non-existant, to work around additional copy protection&lt;/li&gt;
661 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
662 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
663 &lt;li&gt;Fix include orders&lt;/li&gt;
664 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
665 &lt;li&gt;Fix the chapter count&lt;/li&gt;
666 &lt;li&gt;Make sure the array size and the array limit used when initialising
667 the palette size is the same.&lt;/li&gt;
668 &lt;li&gt;Fix array printing.&lt;/li&gt;
669 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
670 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
671 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
672 with more GCC compiler warnings.&lt;/li&gt;
673
674 &lt;/ul&gt;
675
676 &lt;p&gt;This change bring together patches for lsdvd in use in various
677 Linux and Unix distributions, as well as patches submitted to the
678 project the last nine years. Please check it out. :)&lt;/p&gt;
679 </description>
680 </item>
681
682 <item>
683 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
684 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
685 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
686 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
687 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
688 project&lt;/a&gt; provide a Linux solution for schools, including a
689 powerful desktop with education software, a central server providing
690 web pages, user database, user home directories, central login and PXE
691 boot of both clients without disk and the installation to install Debian
692 Edu on machines with disk (and a few other services perhaps to small
693 to mention here). We in the Debian Edu team are currently working on
694 the Jessie based version, trying to get everything in shape before the
695 freeze, to avoid having to maintain our own package repository in the
696 future. The
697 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
698 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
699 work left. Some fatal problems block testing, breaking the installer,
700 but it is possible to work around these to get anyway. Here is a
701 recipe on how to get the installation limping along.&lt;/p&gt;
702
703 &lt;p&gt;First, download the test ISO via
704 &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;,
705 &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;
706 or rsync (use
707 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
708 The ISO build was broken on Tuesday, so we do not get a new ISO every
709 12 hours or so, but thankfully the ISO we already got we are able to
710 install with some tweaking.&lt;/p&gt;
711
712 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
713 (use Alt-Ctrl-F2), run&lt;/p&gt;
714
715 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
716 nano /usr/bin/edu-eatmydata-install
717 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
718
719 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
720 optimization. Return to the installation, select the profile you want
721 and continue. Without this change, exim4-config will fail to install
722 due to a known bug in eatmydata.&lt;/p&gt;
723
724 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
725 this do not work, figure out what your correct value would be. All my
726 test machines need /dev/sda, so I have no advice if it do not fit
727 your need.&lt;/p&gt;
728
729 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
730 root after the initial boot from hard drive, and install the
731 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
732 or mate. If you want several desktop options, install more than one
733 metapackage. Once this is done, reboot and you should have a working
734 graphical login screen. This workaround should no longer be needed
735 once the education-tasks package version 1.801 enter testing in two
736 days.&lt;/p&gt;
737
738 &lt;p&gt;I believe the ISO build will start working on two days when the new
739 tasksel package enter testing and Steve McIntyre get a chance to
740 update the debian-cd git repository. The eatmydata, grub and desktop
741 issues are already fixed in unstable and testing, and should show up
742 on the ISO as soon as the ISO build start working again. Well the
743 eatmydata optimization is really just disabled. The proper fix
744 require an upload by the eatmydata maintainer applying the patch
745 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
746 The rest have proper fixes in unstable.&lt;/p&gt;
747
748 &lt;p&gt;I hope this get you going with the installation testing, as we are
749 quickly running out of time trying to get our Jessie based
750 installation ready before the distribution freeze in a month.&lt;/p&gt;
751 </description>
752 </item>
753
754 <item>
755 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
756 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
757 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
758 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
759 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
760 to handle my fairly large DVD collection. It is a nice command line
761 tool to get details about a DVD, like title, tracks, track length,
762 etc, in XML, Perl or human readable format. But lsdvd have not seen
763 any new development since 2006 and had a few irritating bugs affecting
764 its use with some DVDs. Upstream seemed to be dead, and in January I
765 sent a small probe asking for a version control repository for the
766 project, without any reply. But I use it regularly and would like to
767 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
768 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
769 the project admin, and after getting a reply from him explaining that
770 he was no longer interested in the project, I asked if I could take
771 over. And yesterday, I became project admin.&lt;/p&gt;
772
773 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
774 maintainer interested in joining forces to maintain the upstream
775 project, and I hope we can get a new release out fairly quickly,
776 collecting the patches spread around on the internet into on place.
777 I&#39;ve added the relevant Debian patches to the freshly created git
778 repository, and expect the Gentoo patches to make it too. If you got
779 a DVD collection and care about command line tools, check out
780 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
781 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
782 list&lt;/a&gt;. :)&lt;/p&gt;
783 </description>
784 </item>
785
786 <item>
787 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
788 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
789 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
790 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
791 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
792 a lot quicker. When we install more than 2000 packages in
793 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
794 tasksel in the installer, unpacking the binary packages take forever.
795 A part of the slow I/O issue was discussed in
796 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
797 much file system sync-ing done by dpkg, which is the package
798 responsible for unpacking the binary packages. Other parts (like code
799 executed by postinst scripts) might also sync to disk during
800 installation. All this sync-ing to disk do not really make sense to
801 me. If the machine crash half-way through, I start over, I do not try
802 to salvage the half installed system. So the failure sync-ing is
803 supposed to protect against, hardware or system crash, is not really
804 relevant while the installer is running.&lt;/p&gt;
805
806 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
807 system sync()-ing in a fairly non-intrusive way, without the need to
808 change the code in several packages. The idea is not new, but I have
809 not heard anyone propose the approach using dpkg-divert before. It
810 depend on the small and clever package
811 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
812 uses LD_PRELOAD to replace the system functions for syncing data to
813 disk with functions doing nothing, thus allowing programs to live
814 dangerous while speeding up disk I/O significantly. Instead of
815 modifying the implementation of dpkg, apt and tasksel (which are the
816 packages responsible for selecting, fetching and installing packages),
817 it occurred to me that we could just divert the programs away, replace
818 them with a simple shell wrapper calling
819 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
820 Two days ago I decided to test the idea, and wrapped up a simple
821 implementation for the Debian Edu udeb.&lt;/p&gt;
822
823 &lt;p&gt;The effect was stunning. In my first test it reduced the running
824 time of the pkgsel step (installing tasks) from 64 to less than 44
825 minutes (20 minutes shaved off the installation) on an old Dell
826 Latitude D505 machine. I am not quite sure what the optimised time
827 would have been, as I messed up the testing a bit, causing the debconf
828 priority to get low enough for two questions to pop up during
829 installation. As soon as I saw the questions I moved the installation
830 along, but do not know how long the question were holding up the
831 installation. I did some more measurements using Debian Edu Jessie,
832 and got these results. The time measured is the time stamp in
833 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
834 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
835 yourself. In Debian Edu, the tasksel dialog do not show up, and the
836 timing thus do not depend on how quickly the user handle the tasksel
837 dialog.&lt;/p&gt;
838
839 &lt;p&gt;&lt;table&gt;
840
841 &lt;tr&gt;
842 &lt;th&gt;Machine/setup&lt;/th&gt;
843 &lt;th&gt;Original tasksel&lt;/th&gt;
844 &lt;th&gt;Optimised tasksel&lt;/th&gt;
845 &lt;th&gt;Reduction&lt;/th&gt;
846 &lt;/tr&gt;
847
848 &lt;tr&gt;
849 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
850 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
851 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
852 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
853 &lt;/tr&gt;
854
855 &lt;tr&gt;
856 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
857 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
858 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
859 &lt;td&gt;23 min 40%&lt;/td&gt;
860 &lt;/tr&gt;
861
862 &lt;tr&gt;
863 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
864 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
865 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
866 &lt;td&gt;11 min 50%&lt;/td&gt;
867 &lt;/tr&gt;
868
869 &lt;tr&gt;
870 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
871 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
872 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
873 &lt;td&gt;2 min 33%&lt;/td&gt;
874 &lt;/tr&gt;
875
876 &lt;tr&gt;
877 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
878 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
879 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
880 &lt;td&gt;4 min 21%&lt;/td&gt;
881 &lt;/tr&gt;
882
883 &lt;/table&gt;&lt;/p&gt;
884
885 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
886 time is spent downloading packages. The connection to the Internet
887 was 100Mbit/s during testing, so downloading should not be a
888 significant factor in the measurement. Download typically took a few
889 seconds to a few minutes, depending on the amount of packages being
890 installed.&lt;/p&gt;
891
892 &lt;p&gt;The speedup is implemented by using two hooks in
893 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
894 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
895 finish-install.d hook to remove the divert at the end of the
896 installation. I picked the pre-pkgsel.d hook instead of the
897 post-base-installer.d hook because I test using an ISO without the
898 eatmydata package included, and the post-base-installer.d hook in
899 Debian Edu can only operate on packages included in the ISO. The
900 negative effect of this is that I am unable to activate this
901 optimization for the kernel installation step in d-i. If the code is
902 moved to the post-base-installer.d hook, the speedup would be larger
903 for the entire installation.&lt;/p&gt;
904
905 &lt;p&gt;I&#39;ve implemented this in the
906 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
907 git repository, and plan to provide the optimization as part of the
908 Debian Edu installation. If you want to test this yourself, you can
909 create two files in the installer (or in an udeb). One shell script
910 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
911
912 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
913 #!/bin/sh
914 set -e
915 . /usr/share/debconf/confmodule
916 info() {
917 logger -t my-pkgsel &quot;info: $*&quot;
918 }
919 error() {
920 logger -t my-pkgsel &quot;error: $*&quot;
921 }
922 override_install() {
923 apt-install eatmydata || true
924 if [ -x /target/usr/bin/eatmydata ] ; then
925 for bin in dpkg apt-get aptitude tasksel ; do
926 file=/usr/bin/$bin
927 # Test that the file exist and have not been diverted already.
928 if [ -f /target$file ] ; then
929 info &quot;diverting $file using eatmydata&quot;
930 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
931 &gt; /target$file.edu
932 chmod 755 /target$file.edu
933 in-target dpkg-divert --package debian-edu-config \
934 --rename --quiet --add $file
935 ln -sf ./$bin.edu /target$file
936 else
937 error &quot;unable to divert $file, as it is missing.&quot;
938 fi
939 done
940 else
941 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
942 fi
943 }
944
945 override_install
946 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
947
948 &lt;p&gt;To clean up, another shell script should go into
949 /usr/lib/finish-install.d/ with code like this:
950
951 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
952 #! /bin/sh -e
953 . /usr/share/debconf/confmodule
954 error() {
955 logger -t my-finish-install &quot;error: $@&quot;
956 }
957 remove_install_override() {
958 for bin in dpkg apt-get aptitude tasksel ; do
959 file=/usr/bin/$bin
960 if [ -x /target$file.edu ] ; then
961 rm /target$file
962 in-target dpkg-divert --package debian-edu-config \
963 --rename --quiet --remove $file
964 rm /target$file.edu
965 else
966 error &quot;Missing divert for $file.&quot;
967 fi
968 done
969 sync # Flush file buffers before continuing
970 }
971
972 remove_install_override
973 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
974
975 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
976 edu-eatmydata-install and call it from the pre-pkgsel.d and
977 finish-install.d scripts.&lt;/p&gt;
978
979 &lt;p&gt;By now you might ask if this change should get into the normal
980 Debian installer too? I suspect it should, but am not sure the
981 current debian-installer coordinators find it useful enough. It also
982 depend on the side effects of the change. I&#39;m not aware of any, but I
983 guess we will see if the change is safe after some more testing.
984 Perhaps there is some package in Debian depending on sync() and
985 fsync() having effect? Perhaps it should go into its own udeb, to
986 allow those of us wanting to enable it to do so without affecting
987 everyone.&lt;/p&gt;
988
989 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
990 will break installation of all programs using gnutls because of
991 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
992 eatmydata package in Debian will solve it.&lt;/p&gt;
993
994 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
995 the optimization work again. And I have discovered that the
996 dpkg-divert trick is not really needed and implemented a slightly
997 simpler approach as part of the debian-edu-install package. See
998 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
999
1000 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1001 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1002 triggering on i386 made it into testing, and broke this installation
1003 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1004 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1005 </description>
1006 </item>
1007
1008 <item>
1009 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1010 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1011 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1012 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1013 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1014 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1015 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1016 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1017 learn that there is a large set of publicly available key servers to
1018 use when looking for peoples public key. So far I have used
1019 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1020 were misbehaving, but those days are ended. The servers I have used
1021 up until yesterday have been slow and some times unavailable. I hope
1022 those problems are gone now.&lt;/p&gt;
1023
1024 &lt;p&gt;Behind the round robin DNS entry of the
1025 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1026 there is a pool of more than 100 keyservers which are checked every
1027 day to ensure they are well connected and up to date. It must be
1028 better than what I have used so far. :)&lt;/p&gt;
1029
1030 &lt;p&gt;Yesterdays speaker told me that the service is the default
1031 keyserver provided by the default configuration in GnuPG, but this do
1032 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1033
1034 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1035 line:&lt;/p&gt;
1036
1037 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1038 keyserver pool.sks-keyservers.net
1039 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1040
1041 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1042 entries in DNS. Just for fun, I did just that at work, so now every
1043 user of GnuPG at the University of Oslo should find a OpenGPG
1044 keyserver automatically should their need it:&lt;/p&gt;
1045
1046 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1047 % host -t srv _pgpkey-http._tcp.uio.no
1048 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1049 %
1050 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1051
1052 &lt;p&gt;Now if only
1053 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1054 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1055 very happy. It can look up a given key or search for a user ID, but I
1056 normally do not want that, but to find a trust path from my key to
1057 another key. Given a user ID or key ID, I would like to find (and
1058 download) the keys representing a signature path from my key to the
1059 key in question, to be able to get a trust path between the two keys.
1060 This is as far as I can tell not possible today. Perhaps something
1061 for a future version of the protocol?&lt;/p&gt;
1062 </description>
1063 </item>
1064
1065 <item>
1066 <title>From English wiki to translated PDF and epub via Docbook</title>
1067 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1068 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1069 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1070 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1071 project&lt;/a&gt; provide an instruction manual for teachers, system
1072 administrators and other users that contain useful tips for setting up
1073 and maintaining a Debian Edu installation. This text is about how the
1074 text processing of this manual is handled in the project.&lt;/p&gt;
1075
1076 &lt;p&gt;One goal of the project is to provide information in the native
1077 language of its users, and for this we need to handle translations.
1078 But we also want to make sure each language contain the same
1079 information, so for this we need a good way to keep the translations
1080 in sync. And we want it to be easy for our users to improve the
1081 documentation, avoiding the need to learn special formats or tools to
1082 contribute, and the obvious way to do this is to make it possible to
1083 edit the documentation using a web browser. We also want it to be
1084 easy for translators to keep the translation up to date, and give them
1085 help in figuring out what need to be translated. Here is the list of
1086 tools and the process we have found trying to reach all these
1087 goals.&lt;/p&gt;
1088
1089 &lt;p&gt;We maintain the authoritative source of our manual in the
1090 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1091 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1092 front page with references to the different chapters, several pages
1093 for each chapter, and finally one &quot;collection page&quot; gluing all the
1094 chapters together into one large web page (aka
1095 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1096 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1097 processing and translations. Thanks to the fact that the
1098 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1099 wiki.debian.org support exporting pages in
1100 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1101 the list of pages to export using the raw version of the AllInOne
1102 page, loop over each of them to generate a Docbook XML version of the
1103 manual. This process also download images and transform image
1104 references to use the locally downloaded images. The generated
1105 Docbook XML files are slightly broken, so some post-processing is done
1106 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1107 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1108 a handfull of images. The XML file can now be used to generate PDF, HTML
1109 and epub versions of the English manual. This is the basic step of
1110 our process, making PDF (using dblatex), HTML (using xsltproc) and
1111 epub (using dbtoepub) version from Docbook XML, and the resulting files
1112 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1113
1114 &lt;p&gt;But English documentation is not enough for us. We want translated
1115 documentation too, and we want to make it easy for translators to
1116 track the English original. For this we use the
1117 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1118 which allow us to transform the English Docbook XML file into a
1119 translation file (a .pot file), usable with the normal gettext based
1120 translation tools used by those translating free software. The pot
1121 file is used to create and maintain translation files (several .po
1122 files), which the translations update with the native language
1123 translations of all titles, paragraphs and blocks of text in the
1124 original. The next step is combining the original English Docbook XML
1125 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1126 create a translated Docbook XML file (in this case
1127 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1128 translated, if the translation is not complete) Docbook XML file can
1129 then be used like the original to create a PDF, HTML and epub version
1130 of the documentation.&lt;/p&gt;
1131
1132 &lt;p&gt;The translators use different tools to edit the .po files. We
1133 recommend using
1134 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1135 while some use emacs and vi, others can use web based editors like
1136 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1137 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1138 is where the .po file end up, in our git repository. Updated
1139 translations can either be committed directly to git, or submitted as
1140 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1141 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1142
1143 &lt;p&gt;One challenge is images, which both might need to be translated (if
1144 they show translated user applications), and are needed in different
1145 formats when creating PDF and HTML versions (epub is a HTML version in
1146 this regard). For this we transform the original PNG images to the
1147 needed density and format during build, and have a way to provide
1148 translated images by storing translated versions in
1149 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1150 package maintainers know more.&lt;/p&gt;
1151
1152 &lt;p&gt;If you wonder what the result look like, we provide
1153 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1154 of the documentation packages on the web&lt;/a&gt;. See for example the
1155 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1156 PDF version&lt;/a&gt; or the
1157 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1158 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1159 but perhaps it will be done in the future.&lt;/p&gt;
1160
1161 &lt;p&gt;To learn more, check out
1162 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1163 debian-edu-doc package&lt;/a&gt;,
1164 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1165 manual on the wiki&lt;/a&gt; and
1166 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1167 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1168 </description>
1169 </item>
1170
1171 <item>
1172 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1173 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1174 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1175 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1176 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1177 related packages relevant for the computer installed automatically.
1178 So I implemented one, using
1179 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1180 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1181 run tasksel as user root. You should be presented with a new option,
1182 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1183 select it, tasksel will install the packages isenkram claim is fit for
1184 the current hardware, hot pluggable or not.&lt;p&gt;
1185
1186 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1187 description, and the other is the script used to extract the list of
1188 packages to install. The first part is in
1189 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1190 this:&lt;/p&gt;
1191
1192 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1193 Task: isenkram
1194 Section: hardware
1195 Description: Hardware specific packages (autodetected by isenkram)
1196 Based on the detected hardware various hardware specific packages are
1197 proposed.
1198 Test-new-install: mark show
1199 Relevance: 8
1200 Packages: for-current-hardware
1201 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1202
1203 &lt;p&gt;The second part is in
1204 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1205 this:&lt;/p&gt;
1206
1207 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1208 #!/bin/sh
1209 #
1210 (
1211 isenkram-lookup
1212 isenkram-autoinstall-firmware -l
1213 ) | sort -u
1214 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1215
1216 &lt;p&gt;All in all, a very short and simple implementation making it
1217 trivial to install the hardware dependent package we all may want to
1218 have installed on our machines. I&#39;ve not been able to find a way to
1219 get tasksel to tell you exactly which packages it plan to install
1220 before doing the installation. So if you are curious or careful,
1221 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1222
1223 &lt;p&gt;The information about which packages are handling which hardware is
1224 fetched either from the isenkram package itself in
1225 /usr/share/isenkram/, from git.debian.org or from the APT package
1226 database (using the Modaliases header). The APT package database
1227 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1228 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1229 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1230 the python-apt code (bug
1231 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1232 workaround I was able to get rid of the file descriptor leak and
1233 reduce the memory leak from ~30 MiB per hardware detection down to
1234 around 2 MiB per hardware detection. It should make the desktop
1235 daemon a lot more useful. The fix is in version 0.7 uploaded to
1236 unstable today.&lt;/p&gt;
1237
1238 &lt;p&gt;I believe the current way of mapping hardware to packages in
1239 Isenkram is is a good draft, but in the future I expect isenkram to
1240 use the AppStream data source for this. A proposal for getting proper
1241 AppStream support into Debian is floating around as
1242 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1243 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1244 project&lt;/a&gt; will take place this summer to improve the situation. I
1245 look forward to seeing the result, and welcome patches for isenkram to
1246 start using the information when it is ready.&lt;/p&gt;
1247
1248 &lt;p&gt;If you want your package to map to some specific hardware, either
1249 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1250 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1251 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1252 package. See also
1253 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1254 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1255 the information will be migrated to AppStream eventually, but for the
1256 moment I got no better place to store it.&lt;/p&gt;
1257 </description>
1258 </item>
1259
1260 <item>
1261 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1262 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1263 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1264 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1265 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1266 project&lt;/a&gt; is working on providing the software and hardware to make
1267 it easy for non-technical people to host their data and communication
1268 at home, and being able to communicate with their friends and family
1269 encrypted and away from prying eyes. It is still going strong, and
1270 today a major mile stone was reached.&lt;/p&gt;
1271
1272 &lt;p&gt;Today, the last of the packages currently used by the project to
1273 created the system images were accepted into Debian Unstable. It was
1274 the freedombox-setup package, which is used to configure the images
1275 during build and on the first boot. Now all one need to get going is
1276 the build code from the freedom-maker git repository and packages from
1277 Debian. And once the freedombox-setup package enter testing, we can
1278 build everything directly from Debian. :)&lt;/p&gt;
1279
1280 &lt;p&gt;Some key packages used by Freedombox are
1281 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1282 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1283 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1284 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1285 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1286 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1287 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1288 are plans to integrate more packages into the setup. User
1289 documentation is maintained on the Debian wiki. Please
1290 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1291 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1292
1293 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1294 setup, run this on a Debian machine using a user with sudo rights to
1295 become root:&lt;/p&gt;
1296
1297 &lt;p&gt;&lt;pre&gt;
1298 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1299 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1300 u-boot-tools
1301 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1302 freedom-maker
1303 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1304 &lt;/pre&gt;&lt;/p&gt;
1305
1306 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1307 devices. See the README in the freedom-maker git repo for more
1308 details on the build. If you do not want all three images, trim the
1309 make line. Note that the virtualbox-image target is not really
1310 virtualbox specific. It create a x86 image usable in kvm, qemu,
1311 vmware and any other x86 virtual machine environment. You might need
1312 the version of vmdebootstrap in Jessie to get the build working, as it
1313 include fixes for a race condition with kpartx.&lt;/p&gt;
1314
1315 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1316 method, boot a Debian Wheezy ISO and use this boot argument to load
1317 the preseed values:&lt;/p&gt;
1318
1319 &lt;p&gt;&lt;pre&gt;
1320 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;
1321 &lt;/pre&gt;&lt;/p&gt;
1322
1323 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1324 it still work.&lt;/p&gt;
1325
1326 &lt;p&gt;If you wonder how to help, one task you could look at is using
1327 systemd as the boot system. It will become the default for Linux in
1328 Jessie, so we need to make sure it is usable on the Freedombox. I did
1329 a simple test a few weeks ago, and noticed dnsmasq failed to start
1330 during boot when using systemd. I suspect there are other problems
1331 too. :) To detect problems, there is a test suite included, which can
1332 be run from the plinth web interface.&lt;/p&gt;
1333
1334 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1335 us get the new release published. :) Please join us on
1336 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1337 irc.debian.org)&lt;/a&gt; and
1338 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1339 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1340 </description>
1341 </item>
1342
1343 <item>
1344 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1345 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1346 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1347 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1348 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1349 solution for use at home. My requirements are simple, it must be
1350 cheap and locally encrypted (in other words, I keep the encryption
1351 keys, the storage provider do not have access to my private files).
1352 One idea me and my friends had many years ago, before the cloud
1353 storage providers showed up, was to use Google mail as storage,
1354 writing a Linux block device storing blocks as emails in the mail
1355 service provided by Google, and thus get heaps of free space. On top
1356 of this one can add encryption, RAID and volume management to have
1357 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1358 I never found time to implement such system. But the last few weeks I
1359 have looked at a system called
1360 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1361 mounted network backed file system with the features I need.&lt;/p&gt;
1362
1363 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1364 handling several different storage providers, any with Amazon S3,
1365 Google Drive or OpenStack API. There are heaps of such storage
1366 providers. S3QL can also use a local directory as storage, which
1367 combined with sshfs allow for file storage on any ssh server. S3QL
1368 include support for encryption, compression, de-duplication, snapshots
1369 and immutable file systems, allowing me to mount the remote storage as
1370 a local mount point, look at and use the files as if they were local,
1371 while the content is stored in the cloud as well. This allow me to
1372 have a backup that should survive fire. The file system can not be
1373 shared between several machines at the same time, as only one can
1374 mount it at the time, but any machine with the encryption key and
1375 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1376
1377 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1378 package is included already. So to get started, run &lt;tt&gt;apt-get
1379 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1380 Greenqloud, after reading their nice recipe on
1381 &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
1382 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1383 in Iceland more than those in USA when it come to keeping my personal
1384 data safe and private, and thus would rather spend money on a company
1385 in Iceland. Another nice recipe is available from the article
1386 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1387 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1388 Admin magazine. When the provider is picked, figure out how to get
1389 the API key needed to connect to the storage API. With Greencloud,
1390 the key did not show up until I had added payment details to my
1391 account.&lt;/p&gt;
1392
1393 &lt;p&gt;Armed with the API access details, it is time to create the file
1394 system. First, create a new bucket in the cloud. This bucket is the
1395 file system storage area. I picked a bucket name reflecting the
1396 machine that was going to store data there, but any name will do.
1397 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1398 the API login and password, and a locally created password. Store it
1399 all in ~root/.s3ql/authinfo2 like this:
1400
1401 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1402 [s3c]
1403 storage-url: s3c://s.greenqloud.com:443/bucket-name
1404 backend-login: API-login
1405 backend-password: API-password
1406 fs-passphrase: local-password
1407 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1408
1409 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1410 but any sensible way to create a fairly random password should do it.
1411 Armed with these details, it is now time to run mkfs, entering the API
1412 details and password to create it:&lt;/p&gt;
1413
1414 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1415 # mkdir -m 700 /var/lib/s3ql-cache
1416 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1417 --ssl s3c://s.greenqloud.com:443/bucket-name
1418 Enter backend login:
1419 Enter backend password:
1420 Before using S3QL, make sure to read the user&#39;s guide, especially
1421 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1422 Enter encryption password:
1423 Confirm encryption password:
1424 Generating random encryption key...
1425 Creating metadata tables...
1426 Dumping metadata...
1427 ..objects..
1428 ..blocks..
1429 ..inodes..
1430 ..inode_blocks..
1431 ..symlink_targets..
1432 ..names..
1433 ..contents..
1434 ..ext_attributes..
1435 Compressing and uploading metadata...
1436 Wrote 0.00 MB of compressed metadata.
1437 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1438
1439 &lt;p&gt;The next step is mounting the file system to make the storage available.
1440
1441 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1442 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1443 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1444 Using 4 upload threads.
1445 Downloading and decompressing metadata...
1446 Reading metadata...
1447 ..objects..
1448 ..blocks..
1449 ..inodes..
1450 ..inode_blocks..
1451 ..symlink_targets..
1452 ..names..
1453 ..contents..
1454 ..ext_attributes..
1455 Mounting filesystem...
1456 # df -h /s3ql
1457 Filesystem Size Used Avail Use% Mounted on
1458 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1459 #
1460 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1461
1462 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1463 backups in it, and as the metadata used by rsync is downloaded at
1464 mount time, no network traffic (and storage cost) is triggered by
1465 running rsync. To unmount, one should not use the normal umount
1466 command, as this will not flush the cache to the cloud storage, but
1467 instead running the umount.s3ql command like this:
1468
1469 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1470 # umount.s3ql /s3ql
1471 #
1472 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1473
1474 &lt;p&gt;There is a fsck command available to check the file system and
1475 correct any problems detected. This can be used if the local server
1476 crashes while the file system is mounted, to reset the &quot;already
1477 mounted&quot; flag. This is what it look like when processing a working
1478 file system:&lt;/p&gt;
1479
1480 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1481 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1482 Using cached metadata.
1483 File system seems clean, checking anyway.
1484 Checking DB integrity...
1485 Creating temporary extra indices...
1486 Checking lost+found...
1487 Checking cached objects...
1488 Checking names (refcounts)...
1489 Checking contents (names)...
1490 Checking contents (inodes)...
1491 Checking contents (parent inodes)...
1492 Checking objects (reference counts)...
1493 Checking objects (backend)...
1494 ..processed 5000 objects so far..
1495 ..processed 10000 objects so far..
1496 ..processed 15000 objects so far..
1497 Checking objects (sizes)...
1498 Checking blocks (referenced objects)...
1499 Checking blocks (refcounts)...
1500 Checking inode-block mapping (blocks)...
1501 Checking inode-block mapping (inodes)...
1502 Checking inodes (refcounts)...
1503 Checking inodes (sizes)...
1504 Checking extended attributes (names)...
1505 Checking extended attributes (inodes)...
1506 Checking symlinks (inodes)...
1507 Checking directory reachability...
1508 Checking unix conventions...
1509 Checking referential integrity...
1510 Dropping temporary indices...
1511 Backing up old metadata...
1512 Dumping metadata...
1513 ..objects..
1514 ..blocks..
1515 ..inodes..
1516 ..inode_blocks..
1517 ..symlink_targets..
1518 ..names..
1519 ..contents..
1520 ..ext_attributes..
1521 Compressing and uploading metadata...
1522 Wrote 0.89 MB of compressed metadata.
1523 #
1524 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1525
1526 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1527 quick, about the same speed as local file access. Uploading large
1528 amount of data is to me limited by the bandwidth out of and into my
1529 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1530 which is very close to my upload speed, and downloading the same
1531 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1532 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1533 network, not the file system code. I do not know what a good cache
1534 size would be, but suspect that the cache should e larger than your
1535 working set.&lt;/p&gt;
1536
1537 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1538 time. If another machine try, it is told that the file system is
1539 busy:&lt;/p&gt;
1540
1541 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1542 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1543 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1544 Using 8 upload threads.
1545 Backend reports that fs is still mounted elsewhere, aborting.
1546 #
1547 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1548
1549 &lt;p&gt;The file content is uploaded when the cache is full, while the
1550 metadata is uploaded once every 24 hour by default. To ensure the
1551 file system content is flushed to the cloud, one can either umount the
1552 file system, or ask S3QL to flush the cache and metadata using
1553 s3qlctrl:
1554
1555 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1556 # s3qlctrl upload-meta /s3ql
1557 # s3qlctrl flushcache /s3ql
1558 #
1559 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1560
1561 &lt;p&gt;If you are curious about how much space your data uses in the
1562 cloud, and how much compression and deduplication cut down on the
1563 storage usage, you can use s3qlstat on the mounted file system to get
1564 a report:&lt;/p&gt;
1565
1566 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1567 # s3qlstat /s3ql
1568 Directory entries: 9141
1569 Inodes: 9143
1570 Data blocks: 8851
1571 Total data size: 22049.38 MB
1572 After de-duplication: 21955.46 MB (99.57% of total)
1573 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1574 Database size: 2.39 MB (uncompressed)
1575 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1576 #
1577 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1578
1579 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1580 storage. I did not try to locate them all, but am aware of at least
1581 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1582 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1583 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1584 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1585 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1586 accept payment in Bitcoin. Pick one that suit your need. Some of
1587 them provide several GiB of free storage, but the prize models are
1588 quite different and you will have to figure out what suits you
1589 best.&lt;/p&gt;
1590
1591 &lt;p&gt;While researching this blog post, I had a look at research papers
1592 and posters discussing the S3QL file system. There are several, which
1593 told me that the file system is getting a critical check by the
1594 science community and increased my confidence in using it. One nice
1595 poster is titled
1596 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1597 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1598 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1599 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1600 and Pamela Smith. Please have a look.&lt;/p&gt;
1601
1602 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1603 check out the mounted S3QL file system to see if it would be usable as
1604 a home directory (in other word, that it provided POSIX semantics when
1605 it come to locking and umask handling etc). Running
1606 &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
1607 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1608 no error was found. So the file system can be used for home
1609 directories, if one chooses to do so.&lt;/p&gt;
1610
1611 &lt;p&gt;If you do not want a locally file system, and want something that
1612 work without the Linux fuse file system, I would like to mention the
1613 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1614 provide locally encrypted backup using a command line client. It have
1615 a nicer access control system, where one can split out read and write
1616 access, allowing some systems to write to the backup and others to
1617 only read from it.&lt;/p&gt;
1618
1619 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1620 activities, please send Bitcoin donations to my address
1621 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1622 </description>
1623 </item>
1624
1625 <item>
1626 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1627 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1628 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1629 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1630 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1631 project&lt;/a&gt; is working on providing the software and hardware for
1632 making it easy for non-technical people to host their data and
1633 communication at home, and being able to communicate with their
1634 friends and family encrypted and away from prying eyes. It has been
1635 going on for a while, and is slowly progressing towards a new test
1636 release (0.2).&lt;/p&gt;
1637
1638 &lt;p&gt;And what day could be better than the Pi day to announce that the
1639 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1640 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1641 system), and can also be installed using a Debian installer preseed
1642 file. The Debian based Freedombox is now based on Debian Jessie,
1643 where most of the needed packages used are already present. Only one,
1644 the freedombox-setup package, is missing. To try to build your own
1645 boot image to test the current status, fetch the freedom-maker scripts
1646 and build using
1647 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1648 with a user with sudo access to become root:
1649
1650 &lt;pre&gt;
1651 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1652 freedom-maker
1653 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1654 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1655 u-boot-tools
1656 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1657 &lt;/pre&gt;
1658
1659 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1660 devices. See the README for more details on the build. If you do not
1661 want all three images, trim the make line. But note that thanks to &lt;a
1662 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1663 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1664 kpartx call.&lt;/p&gt;
1665
1666 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1667 method, boot a Debian Wheezy ISO and use this boot argument to load
1668 the preseed values:&lt;/p&gt;
1669
1670 &lt;pre&gt;
1671 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;
1672 &lt;/pre&gt;
1673
1674 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1675 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1676 currently hang while setting up APT sources. Killing the
1677 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1678 installation will get the installation going. This affect all
1679 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1680
1681 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1682 us get the new release published. :) Please join us on
1683 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1684 irc.debian.org)&lt;/a&gt; and
1685 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1686 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1687 </description>
1688 </item>
1689
1690 <item>
1691 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1692 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1693 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1694 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1695 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1696 innetgr tools, because I needed them in
1697 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1698 ng-utils, and it has served me well. I placed the project under the
1699 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1700 repository. But many years ago, the CVS repository was dropped (lost,
1701 not migrated to new hardware, not sure), and the project have lacked a
1702 proper home since then.&lt;/p&gt;
1703
1704 &lt;p&gt;Last summer, I had a look at the package and made a new release
1705 fixing a irritating crash bug, but was unable to store the changes in
1706 a proper source control system. I applied for a project on
1707 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1708 to follow up on it. Until today. :)&lt;/p&gt;
1709
1710 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1711 now have a new home, and a git repository with the highlight of the
1712 history of the project. I published all release tarballs and imported
1713 them into the git repository. As the project is really stable and not
1714 expected to gain new features any time soon, I decided to make a new
1715 release and call it 1.0. Visit the new project home on
1716 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1717 if you want to check it out. The new version is also uploaded into
1718 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1719 </description>
1720 </item>
1721
1722 <item>
1723 <title>Testing sysvinit from experimental in Debian Hurd</title>
1724 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1725 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1726 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1727 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1728 their changes into sysvinit, to allow them to use the normal sysvinit
1729 boot system instead of their old one. This follow up on the
1730 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1731 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1732 get Debian on Hurd working more like Debian on Linux. To get started,
1733 I downloaded a prebuilt hard disk image from
1734 &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;,
1735 and started it using virt-manager.&lt;/p&gt;
1736
1737 &lt;p&gt;The first think I had to do after logging in (root without any
1738 password) was to get the network operational. I followed
1739 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1740 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1741 commands as root to get the machine to accept a IP address from the
1742 kvm internal DHCP server:&lt;/p&gt;
1743
1744 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1745 settrans -fgap /dev/netdde /hurd/netdde
1746 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1747 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1748 dhclient /dev/eth0
1749 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1750
1751 &lt;p&gt;After this, the machine had internet connectivity, and I could
1752 upgrade it and install the sysvinit packages from experimental and
1753 enable it as the default boot system in Hurd.&lt;/p&gt;
1754
1755 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1756 running on the machine it for ssh login to work a password need to be
1757 set. Also, note that a bug somewhere in openssh on Hurd block
1758 compression from working. Remember to turn that off on the client
1759 side.&lt;/p&gt;
1760
1761 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1762 stuff:&lt;/p&gt;
1763
1764 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1765 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1766 deb http://http.debian.net/debian/ experimental main
1767 EOF
1768 apt-get update
1769 apt-get dist-upgrade
1770 apt-get install -t experimental initscripts sysv-rc sysvinit \
1771 sysvinit-core sysvinit-utils
1772 update-alternatives --config runsystem
1773 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1774
1775 &lt;p&gt;To reboot after switching boot system, you have to use
1776 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1777 yet a sysvinit process able to receive the signals from the normal
1778 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1779 upgrading every package and rebooting, the network come up with DHCP
1780 after boot as it should, and the settrans/pkill hack mentioned at the
1781 start is no longer needed. But for some strange reason, there are no
1782 longer any login prompt in the virtual console, so I logged in using
1783 ssh instead.
1784
1785 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1786 fail some times. No idea what the cause is, but hope the Hurd porters
1787 figure it out. At least Justus said on IRC (#debian-hurd on
1788 irc.debian.org) that they are aware of the problem. A way to reduce
1789 the impact is to upgrade to the Hurd packages built by Justus by
1790 adding this repository to the machine:&lt;/p&gt;
1791
1792 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1793 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1794 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1795 EOF
1796 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1797
1798 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1799 http://ftp.debian-ports.org/debian, because some of the packages in
1800 unstable do not yet include the required patches that are lingering in
1801 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1802
1803 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1804 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1805 i emacs - GNU Emacs editor (metapackage)
1806 i gdb - GNU Debugger
1807 i hurd-recommended - Miscellaneous translators
1808 i isc-dhcp-client - ISC DHCP client
1809 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1810 i libc-bin - Embedded GNU C Library: Binaries
1811 i libc-dev-bin - Embedded GNU C Library: Development binaries
1812 i libc0.3 - Embedded GNU C Library: Shared libraries
1813 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1814 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1815 i multiarch-support - Transitional package to ensure multiarch compatibilit
1816 i A x11-common - X Window System (X.Org) infrastructure
1817 i xorg - X.Org X Window System
1818 i A xserver-xorg - X.Org X server
1819 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1820 #
1821 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1822
1823 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1824 X.org did not work out of the box and I never took the time to follow
1825 the porters instructions to fix it. This time I was interested in the
1826 command line stuff.&lt;p&gt;
1827 </description>
1828 </item>
1829
1830 <item>
1831 <title>New chrpath release 0.16</title>
1832 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1833 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1834 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1835 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1836 find problems in C, C++ and Java code using static source code
1837 analysis. It can detect a lot of different problems, and is very
1838 useful to find memory and locking bugs in the error handling part of
1839 the source. The company behind it provide
1840 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1841 a community service&lt;/a&gt;, and many hundred free software projects are
1842 already checked. A few days ago I decided to have a closer look at
1843 the Coverity system, and discovered that the
1844 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1845 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1846 projects I am involved with was already registered. But these are
1847 fairly big, and I would also like to have a small and easy project to
1848 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1849 checking of the chrpath project&lt;/a&gt;. It was
1850 added to the checker and discovered seven potential defects. Six of
1851 these were real, mostly resource &quot;leak&quot; when the program detected an
1852 error. Nothing serious, as the resources would be released a fraction
1853 of a second later when the program exited because of the error, but it
1854 is nice to do it right in case the source of the program some time in
1855 the future end up in a library. Having fixed all defects and added
1856 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1857 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1858 publish a new release. These are the release notes:&lt;/p&gt;
1859
1860 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1861
1862 &lt;ul&gt;
1863
1864 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1865 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1866 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1867
1868 &lt;/ul&gt;
1869
1870 &lt;p&gt;You can
1871 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1872 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1873 project if something is wrong with the new release. The test suite
1874 did not discover any old errors, so if you find a new one, please also
1875 include a test suite check.&lt;/p&gt;
1876 </description>
1877 </item>
1878
1879 <item>
1880 <title>New chrpath release 0.15</title>
1881 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1882 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1883 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1884 <description>&lt;p&gt;After many years break from the package and a vain hope that
1885 development would be continued by someone else, I finally pulled my
1886 acts together this morning and wrapped up a new release of chrpath,
1887 the command line tool to modify the rpath and runpath of already
1888 compiled ELF programs. The update was triggered by the persistence of
1889 Isha Vishnoi at IBM, which needed a new config.guess file to get
1890 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1891 is working on. I checked the
1892 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1893 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1894 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1895 packages for interesting patches (failed to find the source from
1896 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1897 These are the release notes:&lt;/p&gt;
1898
1899 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1900
1901 &lt;ul&gt;
1902
1903 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1904 with newer architectures. Thanks to isha vishnoi for the heads
1905 up.&lt;/li&gt;
1906
1907 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1908
1909 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1910 Matthias Klose.&lt;/li&gt;
1911
1912 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1913 Petr Machata found in Fedora.&lt;/li&gt;
1914
1915 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1916 .dynamic is a NULL terminated string. Based on patch found in
1917 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1918
1919 &lt;/ul&gt;
1920
1921 &lt;p&gt;You can
1922 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1923 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1924 project if something is wrong with the new release. The test suite
1925 did not discover any old errors, so if you find a new one, please also
1926 include a testsuite check.&lt;/p&gt;
1927 </description>
1928 </item>
1929
1930 <item>
1931 <title>Debian init.d boot script example for rsyslog</title>
1932 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1933 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1934 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1935 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1936 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1937 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1938 init.d scripts at all. Here is an example init.d script, ie a rewrite
1939 of /etc/init.d/rsyslog:&lt;/p&gt;
1940
1941 &lt;p&gt;&lt;pre&gt;
1942 #!/lib/init/init-d-script
1943 ### BEGIN INIT INFO
1944 # Provides: rsyslog
1945 # Required-Start: $remote_fs $time
1946 # Required-Stop: umountnfs $time
1947 # X-Stop-After: sendsigs
1948 # Default-Start: 2 3 4 5
1949 # Default-Stop: 0 1 6
1950 # Short-Description: enhanced syslogd
1951 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1952 # It is quite compatible to stock sysklogd and can be
1953 # used as a drop-in replacement.
1954 ### END INIT INFO
1955 DESC=&quot;enhanced syslogd&quot;
1956 DAEMON=/usr/sbin/rsyslogd
1957 &lt;/pre&gt;&lt;/p&gt;
1958
1959 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1960 script was 137 lines, and the above is just 15 lines, most of it meta
1961 info/comments.&lt;/p&gt;
1962
1963 &lt;p&gt;How to do this, you ask? Well, one create a new script
1964 /lib/init/init-d-script looking something like this:
1965
1966 &lt;p&gt;&lt;pre&gt;
1967 #!/bin/sh
1968
1969 # Define LSB log_* functions.
1970 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1971 # and status_of_proc is working.
1972 . /lib/lsb/init-functions
1973
1974 #
1975 # Function that starts the daemon/service
1976
1977 #
1978 do_start()
1979 {
1980 # Return
1981 # 0 if daemon has been started
1982 # 1 if daemon was already running
1983 # 2 if daemon could not be started
1984 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1985 || return 1
1986 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1987 $DAEMON_ARGS \
1988 || return 2
1989 # Add code here, if necessary, that waits for the process to be ready
1990 # to handle requests from services started subsequently which depend
1991 # on this one. As a last resort, sleep for some time.
1992 }
1993
1994 #
1995 # Function that stops the daemon/service
1996 #
1997 do_stop()
1998 {
1999 # Return
2000 # 0 if daemon has been stopped
2001 # 1 if daemon was already stopped
2002 # 2 if daemon could not be stopped
2003 # other if a failure occurred
2004 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2005 RETVAL=&quot;$?&quot;
2006 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2007 # Wait for children to finish too if this is a daemon that forks
2008 # and if the daemon is only ever run from this initscript.
2009 # If the above conditions are not satisfied then add some other code
2010 # that waits for the process to drop all resources that could be
2011 # needed by services started subsequently. A last resort is to
2012 # sleep for some time.
2013 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2014 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2015 # Many daemons don&#39;t delete their pidfiles when they exit.
2016 rm -f $PIDFILE
2017 return &quot;$RETVAL&quot;
2018 }
2019
2020 #
2021 # Function that sends a SIGHUP to the daemon/service
2022 #
2023 do_reload() {
2024 #
2025 # If the daemon can reload its configuration without
2026 # restarting (for example, when it is sent a SIGHUP),
2027 # then implement that here.
2028 #
2029 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2030 return 0
2031 }
2032
2033 SCRIPTNAME=$1
2034 scriptbasename=&quot;$(basename $1)&quot;
2035 echo &quot;SN: $scriptbasename&quot;
2036 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2037 script=&quot;$1&quot;
2038 shift
2039 . $script
2040 else
2041 exit 0
2042 fi
2043
2044 NAME=$(basename $DAEMON)
2045 PIDFILE=/var/run/$NAME.pid
2046
2047 # Exit if the package is not installed
2048 #[ -x &quot;$DAEMON&quot; ] || exit 0
2049
2050 # Read configuration variable file if it is present
2051 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2052
2053 # Load the VERBOSE setting and other rcS variables
2054 . /lib/init/vars.sh
2055
2056 case &quot;$1&quot; in
2057 start)
2058 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2059 do_start
2060 case &quot;$?&quot; in
2061 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2062 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2063 esac
2064 ;;
2065 stop)
2066 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2067 do_stop
2068 case &quot;$?&quot; in
2069 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2070 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2071 esac
2072 ;;
2073 status)
2074 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2075 ;;
2076 #reload|force-reload)
2077 #
2078 # If do_reload() is not implemented then leave this commented out
2079 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2080 #
2081 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2082 #do_reload
2083 #log_end_msg $?
2084 #;;
2085 restart|force-reload)
2086 #
2087 # If the &quot;reload&quot; option is implemented then remove the
2088 # &#39;force-reload&#39; alias
2089 #
2090 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2091 do_stop
2092 case &quot;$?&quot; in
2093 0|1)
2094 do_start
2095 case &quot;$?&quot; in
2096 0) log_end_msg 0 ;;
2097 1) log_end_msg 1 ;; # Old process is still running
2098 *) log_end_msg 1 ;; # Failed to start
2099 esac
2100 ;;
2101 *)
2102 # Failed to stop
2103 log_end_msg 1
2104 ;;
2105 esac
2106 ;;
2107 *)
2108 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2109 exit 3
2110 ;;
2111 esac
2112
2113 :
2114 &lt;/pre&gt;&lt;/p&gt;
2115
2116 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2117 lot. I did not really polish the approach, so it might not always
2118 work out of the box, but you get the idea. I did not try very hard to
2119 optimize it nor make it more robust either.&lt;/p&gt;
2120
2121 &lt;p&gt;A better argument for switching init system in Debian than reducing
2122 the size of init scripts (which is a good thing to do anyway), is to
2123 get boot system that is able to handle the kernel events sensibly and
2124 robustly, and do not depend on the boot to run sequentially. The boot
2125 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2126 </description>
2127 </item>
2128
2129 <item>
2130 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2131 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2132 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2133 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2134 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2135 remote display access is the preferred solution with oVirt and RedHat
2136 Enterprise Virtualization, and I was sad to discover the other day
2137 that the browser plugin needed to use these systems seamlessly was
2138 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2139 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2140 2013-04-01, so I decided to wrap up a package based on the great work
2141 from Cajus Pollmeier and put it in a collab-maint maintained git
2142 repository to get a package I could use. I would very much like
2143 others to help me maintain the package (or just take over, I do not
2144 mind), but as no-one had volunteered so far, I just uploaded it to
2145 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2146
2147 &lt;p&gt;The source is now available from
2148 &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;
2149 </description>
2150 </item>
2151
2152 <item>
2153 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2154 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2155 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2156 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2157 <description>&lt;p&gt;The
2158 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2159 program is a a very nice system to create virtual machine images. It
2160 create a image file, add a partition table, mount it and run
2161 debootstrap in the mounted directory to create a Debian system on a
2162 stick. Yesterday, I decided to try to teach it how to make images for
2163 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2164 of a plan to simplify the build system for
2165 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2166 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2167 the virtualbox images, but its current build system made multistrap
2168 based system for Dreamplug images, and it is lacking support for
2169 Raspberry Pi.&lt;/p&gt;
2170
2171 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2172 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2173 code and adjusted it to be able to build armel images on my amd64
2174 Debian laptop. I ended up giving vmdebootstrap five new options,
2175 allowing me to replicate the image creation process I use to make
2176 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2177 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2178 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2179 call debootstrap with --foreign and to copy the handler into the
2180 generated chroot before running the second stage. This allow
2181 vmdebootstrap to create armel images on an amd64 host. Next I added
2182 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2183 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2184 given file system type, allowing me to create an image with a vfat
2185 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2186 variant&lt;/tt&gt; option to allow me to create smaller images without the
2187 Debian base system packages installed. Finally, I added an option
2188 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2189 as a boot loader. It is not needed on the Raspberry Pi and probably
2190 most other non-x86 architectures. The changes were accepted by the
2191 upstream author of vmdebootstrap yesterday and today, and is now
2192 available from
2193 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2194 upstream project page&lt;/a&gt;.&lt;/p&gt;
2195
2196 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2197 create a small script (the customize script) to add the non-free
2198 binary blob needed to boot the Raspberry Pi and the APT source
2199 list:&lt;/p&gt;
2200
2201 &lt;p&gt;&lt;pre&gt;
2202 #!/bin/sh
2203 set -e # Exit on first error
2204 rootdir=&quot;$1&quot;
2205 cd &quot;$rootdir&quot;
2206 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2207 deb http://http.debian.net/debian/ jessie main contrib non-free
2208 EOF
2209 # Install non-free binary blob needed to boot Raspberry Pi. This
2210 # install a kernel somewhere too.
2211 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2212 -O $rootdir/usr/bin/rpi-update
2213 chmod a+x $rootdir/usr/bin/rpi-update
2214 mkdir -p $rootdir/lib/modules
2215 touch $rootdir/boot/start.elf
2216 chroot $rootdir rpi-update
2217 &lt;/pre&gt;&lt;/p&gt;
2218
2219 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2220 to build the image:&lt;/p&gt;
2221
2222 &lt;pre&gt;
2223 sudo ./vmdebootstrap \
2224 --variant minbase \
2225 --arch armel \
2226 --distribution jessie \
2227 --mirror http://http.debian.net/debian \
2228 --image test.img \
2229 --size 600M \
2230 --bootsize 64M \
2231 --boottype vfat \
2232 --log-level debug \
2233 --verbose \
2234 --no-kernel \
2235 --no-extlinux \
2236 --root-password raspberry \
2237 --hostname raspberrypi \
2238 --foreign /usr/bin/qemu-arm-static \
2239 --customize `pwd`/customize \
2240 --package netbase \
2241 --package git-core \
2242 --package binutils \
2243 --package ca-certificates \
2244 --package wget \
2245 --package kmod
2246 &lt;/pre&gt;&lt;/p&gt;
2247
2248 &lt;p&gt;The list of packages being installed are the ones needed by
2249 rpi-update to make the image bootable on the Raspberry Pi, with the
2250 exception of netbase, which is needed by debootstrap to find
2251 /etc/hosts with the minbase variant. I really wish there was a way to
2252 set up an Raspberry Pi using only packages in the Debian archive, but
2253 that is not possible as far as I know, because it boots from the GPU
2254 using a non-free binary blob.&lt;/p&gt;
2255
2256 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2257 probably a few others installed. I have not checked the complete
2258 build dependency list.&lt;/p&gt;
2259
2260 &lt;p&gt;The resulting image will not use the hardware floating point unit
2261 on the Raspberry PI, because the armel architecture in Debian is not
2262 optimized for that use. So the images created will be a bit slower
2263 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2264 </description>
2265 </item>
2266
2267 <item>
2268 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2269 <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>
2270 <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>
2271 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2272 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2273 wider attention. I recommend signing and donating to each one of
2274 these. :)&lt;/p&gt;
2275
2276 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2277 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2278 Women program which is a Google Summer of Code like initiative to get
2279 more women involved in free software. One debian sponsor has offered
2280 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2281 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2282 hope you will to. :)&lt;/p&gt;
2283
2284 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2285 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2286 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2287 take place these days, and their need to fund the work. I&#39;ve already
2288 donated. Are you next?&lt;/p&gt;
2289
2290 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2291 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2292 statement under the heading
2293 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2294 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2295 Norwegian government. So far 499 signatures. I hope you will sign it
2296 too.&lt;/p&gt;
2297 </description>
2298 </item>
2299
2300 <item>
2301 <title>Videos about the Freedombox project - for inspiration and learning</title>
2302 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2304 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2305 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2306 project&lt;/a&gt; have been going on for a while, and have presented the
2307 vision, ideas and solution several places. Here is a little
2308 collection of videos of talks and presentation of the project.&lt;/p&gt;
2309
2310 &lt;ul&gt;
2311
2312 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2313 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2314
2315 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2316 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2317
2318 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2319 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2320 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2321 (Youtube)&lt;/li&gt;
2322
2323 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2324 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2325
2326 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2327 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2328
2329 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2330 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2331 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2332
2333 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2334 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2335 (Youtube)&lt;/li&gt;
2336
2337 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2338 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2339
2340 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2341 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2342
2343 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2344 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2345 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2346
2347 &lt;/ul&gt;
2348
2349 &lt;p&gt;A larger list is available from
2350 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2351 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2352
2353 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2354 Jessie is coming along quite well, and soon both Owncloud and using
2355 Tor should be available for testers of the Freedombox solution. :) In
2356 a few weeks I hope everything needed to test it is included in Debian.
2357 The withsqlite package is already in Debian, and the plinth package is
2358 pending in NEW. The third and vital part of that puzzle is the
2359 metapackage/setup framework, which is still pending an upload. Join
2360 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2361 (#freedombox on irc.debian.org)&lt;/a&gt; and
2362 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2363 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2364 </description>
2365 </item>
2366
2367 <item>
2368 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2369 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2370 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2371 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2372 <description>&lt;p&gt;I was introduced to the
2373 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2374 in 2010, when Eben Moglen presented his vision about serving the need
2375 of non-technical people to keep their personal information private and
2376 within the legal protection of their own homes. The idea is to give
2377 people back the power over their network and machines, and return
2378 Internet back to its intended peer-to-peer architecture. Instead of
2379 depending on a central service, the Freedombox will give everyone
2380 control over their own basic infrastructure.&lt;/p&gt;
2381
2382 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2383 taken priority. But this summers nasty news about the misuse of trust
2384 and privilege exercised by the &quot;western&quot; intelligence gathering
2385 communities increased my eagerness to contribute to a point where I
2386 actually started working on the project a while back.&lt;/p&gt;
2387
2388 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2389 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2390 create a simple and cheap Debian based appliance that anyone can hook
2391 up in their home and get access to secure and private services and
2392 communication. The initial deployment platform have been the
2393 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2394 which is a piece of hardware I do not own. So to be able to test what
2395 the current Freedombox setup look like, I had to come up with a way to install
2396 it on some hardware I do have access to. I have rewritten the
2397 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2398 image build framework to use .deb packages instead of only copying
2399 setup into the boot images, and thanks to this rewrite I am able to
2400 set up any machine supported by Debian Wheezy as a Freedombox, using
2401 the previously mentioned deb (and a few support debs for packages
2402 missing in Debian).&lt;/p&gt;
2403
2404 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2405 scripts
2406 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2407 and a administrative web interface
2408 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2409 withsqlite), as well as a privacy enhancing proxy based on
2410 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2411 (freedombox-privoxy). There is also a web/javascript based XMPP
2412 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2413 trying (unsuccessfully so far) to talk to the XMPP server
2414 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2415 web interface is pluggable, and the goal is to use it to enable OpenID
2416 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2417 this is really working yet, see
2418 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2419 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2420 on github at the moment. The HTTP proxy is operational out of the
2421 box, and the admin web interface can be used to add/remove plinth
2422 users. I&#39;ve not been able to do anything else with it so far, but
2423 know there are several branches spread around github and other places
2424 with lots of half baked features.&lt;/p&gt;
2425
2426 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2427 following recipes should work to give you a test machine to poke
2428 at.&lt;/p&gt;
2429
2430 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2431
2432 &lt;ol&gt;
2433
2434 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2435 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2436 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2437 to the Debian installer:&lt;p&gt;
2438 &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;
2439
2440 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2441 install on.&lt;/li&gt;
2442
2443 &lt;li&gt;When the installation is finished and the machine have rebooted a
2444 few times, your Freedombox is ready for testing.&lt;/li&gt;
2445
2446 &lt;/ol&gt;
2447
2448 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2449
2450 &lt;ol&gt;
2451
2452 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2453 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2454 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2455 &lt;pre&gt;
2456 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2457 &lt;/pre&gt;&lt;/li&gt;
2458 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2459 &lt;pre&gt;
2460 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2461 apt-key add -
2462 apt-get update
2463 apt-get install freedombox-setup
2464 /usr/lib/freedombox/setup
2465 &lt;/pre&gt;&lt;/li&gt;
2466 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2467
2468 &lt;/ol&gt;
2469
2470 &lt;p&gt;You can test it on other architectures too, but because the
2471 freedombox-privoxy package is binary, it will only work as intended on
2472 the architectures where I have had time to build the binary and put it
2473 in my APT repository. But do not let this stop you. It is only a
2474 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2475
2476 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2477 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2478 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2479 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2480
2481 &lt;p&gt;Please let me know if this works for you, or if you have any
2482 problems. We gather on the IRC channel
2483 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2484 irc.debian.org and the
2485 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2486 mailing list&lt;/a&gt;.&lt;/p&gt;
2487
2488 &lt;p&gt;Once you get your freedombox operational, you can visit
2489 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2490 welcome screen (dead end - do not be surprised if you are unable to
2491 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2492 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2493 default password is &#39;secret&#39;.&lt;/p&gt;
2494 </description>
2495 </item>
2496
2497 <item>
2498 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2499 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2500 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2501 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2502 <description>&lt;p&gt;Earlier, I reported about
2503 &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
2504 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2505 told by IBM that the original disk should be thrown away. And as
2506 there no longer was a problem if I bricked the firmware, I decided
2507 today to try to install Intel firmware to replace the Lenovo firmware
2508 currently on the disk.&lt;/p&gt;
2509
2510 &lt;p&gt;I searched the Intel site for firmware, and found
2511 &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;
2512 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2513 according to the site should contain the latest firmware for SSD
2514 disks. I inserted the broken disk in one of my spare laptops and
2515 booted the ISO from a USB stick. The disk was recognized, but the
2516 program claimed the newest firmware already were installed and refused
2517 to insert any Intel firmware. So no change, and the disk is still
2518 unable to handle write load. :( I guess the only way to get them
2519 working would be if Lenovo releases new firmware. No idea how likely
2520 that is. Anyway, just blogging about this test for completeness. I
2521 got a working Samsung disk, and see no point in spending more time on
2522 the broken disks.&lt;/p&gt;
2523 </description>
2524 </item>
2525
2526 <item>
2527 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2528 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2530 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2531 <description>&lt;p&gt;Today I switched to
2532 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2533 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2534 my new Thinkpad X230, which was delivered with an
2535 &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
2536 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2537 sustained writes. My hardware supplier have been very forthcoming in
2538 trying to find a solution, and after first trying with another
2539 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2540 disk instead to fix it once and for all. The Samsung disk survived
2541 the installation of Debian with encrypted disks (filling the disk with
2542 random data during installation killed the first two), and I thus
2543 decided to trust it with my data. I have installed it as a Debian Edu
2544 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2545 server at home using Kerberos and LDAP, and will use it as my work
2546 station from now on.&lt;/p&gt;
2547
2548 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2549 Debian Wheezy default installation need to be tuned a bit to increase
2550 performance and increase life time of the disk. The Linux kernel and
2551 user space applications do not yet adjust automatically to such
2552 environment. To make it easier for my self, I created a draft Debian
2553 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2554 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2555 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2556 is set up to adjust the setup of the machine by just installing the
2557 package. If there is any non-SSD disk in the machine, the package
2558 will refuse to install, as I did not try to write any logic to sort
2559 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2560
2561 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2562 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2563 where I set up the machine with one large encrypted partition (in
2564 addition to /boot), put LVM on top of this and set up partitions on
2565 top of this again. See the README file in the package source for the
2566 references I used to pick the settings. At the moment these
2567 parameters are tuned:&lt;/p&gt;
2568
2569 &lt;ul&gt;
2570
2571 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2572 (adding discard to /etc/crypttab)&lt;/li&gt;
2573
2574 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2575 this case a cryptsetup partition) by changing issue_discards from
2576 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2577
2578 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2579 systems.&lt;/li&gt;
2580
2581 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2582 /etc/fstab.&lt;/li&gt;
2583
2584 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2585
2586 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2587 cron.daily).&lt;/li&gt;
2588
2589 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2590 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2591
2592 &lt;/ul&gt;
2593
2594 &lt;p&gt;During installation, I cancelled the part where the installer fill
2595 the disk with random data, as this would kill the SSD performance for
2596 little gain. My goal with the encrypted file system is to ensure
2597 those stealing my laptop end up with a brick and not a working
2598 computer. I have no hope in keeping the really resourceful people
2599 from getting the data on the disk (see
2600 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2601 Thus I concluded that adding the discard option to crypttab is the
2602 right thing to do.&lt;/p&gt;
2603
2604 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2605 it for SSD, but others recommended deadline and a benchmark I found
2606 indicated that deadline might be better for interactive use.&lt;/p&gt;
2607
2608 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2609 and ext4, but read that it would give a performance hit ever time a
2610 file is removed, and thought it best to that that slowdown once a day
2611 instead of during my work.&lt;/p&gt;
2612
2613 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2614 this is already done by Debian Edu.&lt;/p&gt;
2615
2616 &lt;p&gt;I have not yet started on the user space tuning. I expect
2617 iceweasel need some tuning, and perhaps other applications too, but
2618 have not yet had time to investigate those parts.&lt;/p&gt;
2619
2620 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2621 there.&lt;/p&gt;
2622
2623 &lt;p&gt;As for the answer to the question in the title of this blog post,
2624 as far as I know, the only solution I know about is to replace the
2625 disk. It might be possible to flash it with Intel firmware instead of
2626 the Lenovo firmware. But I have not tried and did not want to do so
2627 without approval from Lenovo as I wanted to keep the warranty on the
2628 disk until a solution was found and they wanted the broken disks
2629 back.&lt;/p&gt;
2630 </description>
2631 </item>
2632
2633 <item>
2634 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2635 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2636 <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>
2637 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2638 <description>&lt;p&gt;A few days ago, I wrote about
2639 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2640 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2641 was dying during installation because it is unable to cope with
2642 sustained write. My supplier is in contact with
2643 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2644 replacement disk to try to fix the problem. They decided to send an
2645 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2646
2647 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2648 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2649 same firmware version as the original. This time my hope raised
2650 slightly as the installation progressed, as the original disk used to
2651 die after 4-7% of the disk was written to, while this time it kept
2652 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2653 died again and I was back on square one. I still do not have a new
2654 laptop with a disk I can trust. I can not live with a disk that might
2655 lock up when I download a new
2656 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2657 other large files. I look forward to hearing from my supplier with
2658 the next proposal from Lenovo.&lt;/p&gt;
2659
2660 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2661 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2662 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2663 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2664 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2665 P/N 45N8295, P0C38732.&lt;/p&gt;
2666
2667 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2668 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2669 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2670 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2671 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2672 P/N 45N8295, P0C38732.&lt;/p&gt;
2673
2674 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2675 SA, date and WNPP values. Mentioning all the details here in case
2676 someone is able to use the information to find a way to identify the
2677 failing disk among working ones (if any such working disk actually
2678 exist).&lt;/p&gt;
2679 </description>
2680 </item>
2681
2682 <item>
2683 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2684 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2685 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2686 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2687 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2688 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2689 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2690 member assosiation NUUG&lt;/a&gt; and
2691 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2692 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2693 Bitraf&lt;/a&gt;.&lt;/p&gt;
2694
2695 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2696 welcome, and there is no fee to participate. There is on the other
2697 hand limited space, and only room for 30 people. Please put your name
2698 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2699 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2700 </description>
2701 </item>
2702
2703 <item>
2704 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2705 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2707 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2708 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2709 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2710 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2711 time to spend on it, and it took a while to find a model I believe
2712 will do the job, but two days ago the replacement finally arrived. I
2713 ended up picking a
2714 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2715 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2716 a roaming workstation, and it seemed to work flawlessly. But my
2717 second installation with encrypted disk was not as successful. More
2718 on that below.&lt;/p&gt;
2719
2720 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2721 important requirements (robust and with a good keyboard) are never
2722 listed in the feature list. But I did get good help from the search
2723 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2724 allowed me to limit the list of interesting laptops based on my other
2725 requirements. A bit surprising that SSD disk are not disks according
2726 to that search interface, so I had to drop specifying the number of
2727 disks from my search parameters. I also asked around among friends to
2728 get their impression on keyboards and robustness.&lt;/p&gt;
2729
2730 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2731 X41. I am not quite convinced about the keyboard, as it is
2732 significantly wider than my old keyboard, and I have to stretch my
2733 hand a lot more to reach the edges. But the key response is fairly
2734 good and the individual key shape is fairly easy to handle, so I hope
2735 I will get used to it. My old X40 was starting to fail, and I really
2736 needed a new laptop now. :)&lt;/p&gt;
2737
2738 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2739 visit to the BIOS during boot it disable it.&lt;/p&gt;
2740
2741 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2742 lock up during load. And this happen when installing Debian Wheezy
2743 with encrypted disk, while the disk is being filled with random data.
2744 I also tested to install Ubuntu Raring, and it happen there too if I
2745 reenable the code to fill the disk with random data (it is disabled by
2746 default in Ubuntu). And the bug with is already known. It was
2747 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2748 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2749 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2750 kernel developers as
2751 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2752 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2753 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2754 Lenovo forums, both for
2755 &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
2756 2012-11-10&lt;/a&gt; and for
2757 &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
2758 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2759 reports state that the disk lock up during use if many writes are done
2760 on the disk, so it is much no use to work around the installation
2761 problem and end up with a computer that can lock up at any moment.
2762 There is even a
2763 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2764 available&lt;/a&gt; that will lock up the hard drive after running a few
2765 minutes by writing to a file.&lt;/p&gt;
2766
2767 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2768 contacting PCHELP Norway (request 01D1FDP) which handle support
2769 requests for Lenovo, his first suggestion was to upgrade the disk
2770 firmware. Unfortunately there is no newer firmware available from
2771 Lenovo, as my disk already have the most recent one (version LF1i). I
2772 hope to hear more from him today and hope the problem can be
2773 fixed. :)&lt;/p&gt;
2774 </description>
2775 </item>
2776
2777 <item>
2778 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2779 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2780 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2781 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2782 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2783 trusty old Thinkpad X41. Unfortunately I did not have much time to
2784 spend on it, but today the replacement finally arrived. I ended up
2785 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2786 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2787 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2788 this, it is installing what I hope will be a more final installation,
2789 with a encrypted hard drive to ensure any dope head stealing it end up
2790 with an expencive door stop.&lt;/p&gt;
2791
2792 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2793 important requirements (robust and with a good keyboard) are never
2794 listed in the feature list. But I did get good help from the search
2795 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2796 allowed me to limit the list of interesting laptops based on my other
2797 requirements. A bit surprising that SSD disk are not disks, so I had
2798 to drop number of disks from my search parameters.&lt;/p&gt;
2799
2800 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2801 wider than my old keyboard, and I have to stretch my hand a lot more
2802 to reach the edges. But the key response is fairly good and the
2803 individual key shape is fairly easy to handle, so I hope I will get
2804 used to it. My old X40 was starting to fail, and I really needed a
2805 new laptop now. :)&lt;/p&gt;
2806
2807 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2808 </description>
2809 </item>
2810
2811 <item>
2812 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2813 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2814 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2815 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2816 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2817 perfectly capable of, and I have to do it manually to get things
2818 working. One such task is to find out what firmware packages are
2819 needed to get the hardware on my computer working. Most often this
2820 affect the wifi card, but some times it even affect the RAID
2821 controller or the ethernet card. Today I pushed version 0.4 of the
2822 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2823 including a new script isenkram-autoinstall-firmware handling the
2824 process of asking all the loaded kernel modules what firmware files
2825 they want, find debian packages providing these files and install the
2826 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2827
2828 &lt;p&gt;&lt;pre&gt;
2829 # isenkram-autoinstall-firmware
2830 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2831 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2832 info: locating packages with the requested firmware files
2833 info: Updating APT sources after adding non-free APT source
2834 info: trying to install firmware-ipw2x00
2835 firmware-ipw2x00
2836 firmware-ipw2x00
2837 Preconfiguring packages ...
2838 Selecting previously deselected package firmware-ipw2x00.
2839 (Reading database ... 259727 files and directories currently installed.)
2840 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2841 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2842 #
2843 &lt;/pre&gt;&lt;/p&gt;
2844
2845 &lt;p&gt;When all the requested firmware is present, a simple message is
2846 printed instead:&lt;/p&gt;
2847
2848 &lt;p&gt;&lt;pre&gt;
2849 # isenkram-autoinstall-firmware
2850 info: did not find any firmware files requested by loaded kernel modules. exiting
2851 #
2852 &lt;/pre&gt;&lt;/p&gt;
2853
2854 &lt;p&gt;It could use some polish, but it is already working well and saving
2855 me some time when setting up new machines. :)&lt;/p&gt;
2856
2857 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2858 kernel modules, and look up each one of them using modinfo, to find
2859 the firmware files listed in the module meta-information. Next, it
2860 download the Contents file from a nearby APT mirror, and search for
2861 the firmware files in this file to locate the package with the
2862 requested firmware file. If the package is in the non-free section, a
2863 non-free APT source is added and the package is installed using
2864 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2865 machine.&lt;/p&gt;
2866
2867 &lt;p&gt;I hope someone find time to implement a more polished version of
2868 this script as part of the hw-detect debian-installer module, to
2869 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2870 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2871 firmware during a PXE install when the packages already are available
2872 from the nearby Debian mirror.&lt;/p&gt;
2873 </description>
2874 </item>
2875
2876 <item>
2877 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2878 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2879 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2880 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2881 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2882 the screen just turn black when Linux boot, either during installation
2883 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2884 last few years, but only recently understood the cause. I&#39;ve seen it
2885 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2886 The reason seem to be in the wiring of some laptops. The system to
2887 control the screen background light is inverted, so when Linux try to
2888 turn the brightness fully on, it end up turning it off instead. I do
2889 not know which Linux drivers are affected, but this post is about the
2890 i915 driver used by the
2891 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2892 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2893
2894 &lt;p&gt;The problem can be worked around two ways. Either by adding
2895 i915.invert_brightness=1 as a kernel option, or by adding a file in
2896 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2897 option when it load the i915 kernel module. On Debian and Ubuntu, it
2898 can be done by running these commands as root:&lt;/p&gt;
2899
2900 &lt;pre&gt;
2901 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2902 update-initramfs -u -k all
2903 &lt;/pre&gt;
2904
2905 &lt;p&gt;Since March 2012 there is
2906 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2907 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2908 hardware have this problem, and get the driver to invert the
2909 brightness setting automatically. To use it, one need to add a row in
2910 &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
2911 intel_quirks array&lt;/a&gt; in the driver source
2912 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2913 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2914 number (vendor number 8086 is assumed) and subdevice vendor and device
2915 number.&lt;/p&gt;
2916
2917 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2918 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2919
2920 &lt;p&gt;&lt;pre&gt;
2921 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2922 3rd Gen Core processor Graphics Controller [8086:0156] \
2923 (rev 09) (prog-if 00 [VGA controller])
2924 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2925 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2926 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2927 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2928 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2929 Latency: 0
2930 Interrupt: pin A routed to IRQ 42
2931 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2932 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2933 Region 4: I/O ports at 4000 [size=64]
2934 Expansion ROM at &lt;unassigned&gt; [disabled]
2935 Capabilities: &lt;access denied&gt;
2936 Kernel driver in use: i915
2937 &lt;/pre&gt;&lt;/p&gt;
2938
2939 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2940
2941 &lt;p&gt;&lt;pre&gt;
2942 struct intel_quirk intel_quirks[] = {
2943 ...
2944 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2945 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2946 ...
2947 }
2948 &lt;/pre&gt;&lt;/p&gt;
2949
2950 &lt;p&gt;According to the kernel module instructions (as seen using
2951 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2952 invert_brightness flag should be sent to the
2953 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2954 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2955 developers. But my email about the laptop sent 2013-06-03 have not
2956 yet shown up in
2957 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2958 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2959 emails from non-subscribers. Because of this, I sent my patch also to
2960 the Debian bug tracking system instead as
2961 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2962 sure the patch is not lost.&lt;/p&gt;
2963
2964 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2965 with this problem working properly with Linux. If you use Gnome, your
2966 worries should be over at this point. But if you use KDE, there is
2967 something in KDE ignoring the invert_brightness setting and turning on
2968 the screen during login. I&#39;ve reported it to Debian as
2969 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2970 have no idea yet how to figure out exactly what subsystem is doing
2971 this. Perhaps you can help? Perhaps you know what the Gnome
2972 developers did to handle this, and this can give a clue to the KDE
2973 developers? Or you know where in KDE the screen brightness is changed
2974 during login? If so, please update the BTS report (or get in touch if
2975 you do not know how to update BTS).&lt;/p&gt;
2976
2977 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2978 acpi_backlight=vendor, to disable ACPI backlight support completely,
2979 as the ACPI information on the machine is trash and it is better to
2980 leave it to the intel video driver to control the screen
2981 backlight.&lt;/p&gt;
2982 </description>
2983 </item>
2984
2985 <item>
2986 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2987 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2988 <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>
2989 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2990 <description>&lt;p&gt;Two days ago, I asked
2991 &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
2992 I could install Linux on a Packard Bell EasyNote LV computer
2993 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2994 with the obstacles put in the way of Linux users on a laptop with UEFI
2995 and Windows 8.&lt;/p&gt;
2996
2997 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2998 secure booting or fast boot. I suspect fast boot was the problem,
2999 causing the firmware to boot directly from HD without considering any
3000 key presses and alternative devices, but do not know UEFI settings
3001 enough to tell.&lt;/p&gt;
3002
3003 &lt;p&gt;There is no way to install Linux on the machine in question without
3004 opening the box and disconnecting the hard drive! This is as far as I
3005 can tell, the only way to get access to the firmware setup menu
3006 without accepting the Windows 8 license agreement. I am told (and
3007 found description on how to) that it is possible to configure the
3008 firmware setup once booted into Windows 8. But as I believe the terms
3009 of that agreement are completely unacceptable, accepting the license
3010 was never an alternative. I do not enter agreements I do not intend
3011 to follow.&lt;/p&gt;
3012
3013 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3014 waste many hours on this, but luckily there was a way to get it to
3015 work. But I would not recommend it to anyone planning to run Linux on
3016 it, and I have become sceptical to Windows 8 certified laptops. Is
3017 this the way Linux will be forced out of the market place, by making
3018 it close to impossible for &quot;normal&quot; users to install Linux without
3019 accepting the Microsoft Windows license terms? Or at least not
3020 without risking to loose the warranty?&lt;/p&gt;
3021
3022 &lt;p&gt;I&#39;ve updated the
3023 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3024 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3025 do not have to struggle as much as I did to get Linux into the
3026 machine.&lt;/p&gt;
3027
3028 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3029 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3030 </description>
3031 </item>
3032
3033 <item>
3034 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3035 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3036 <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>
3037 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3038 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3039 new laptops for my parents and a few others. I bought Packard Bell
3040 Easynote LV to run Kubuntu on and use as their home computer. But I
3041 am completely unable to figure out how to install Linux on it. The
3042 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3043 instead of a BIOS to boot.&lt;/p&gt;
3044
3045 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3046 to get it to boot the Linux installer from my USB stick. I have yet
3047 to try the DVD install, and still hope it will work. when I turn on
3048 the computer, there is no information on what buttons to press to get
3049 the normal boot menu. I expect to get some boot menu to select PXE or
3050 USB stick booting. When booting, it first ask for the language to
3051 use, then for some regional settings, and finally if I will accept the
3052 Windows 8 terms of use. As these terms are completely unacceptable to
3053 me, I have no other choice but to turn off the computer and try again
3054 to get it to boot the Linux installer.&lt;/p&gt;
3055
3056 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3057 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3058 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3059 installed on this machine, please get in touch or update that wiki
3060 page. If I can&#39;t find a way to install Linux, I will have to return
3061 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3062
3063 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3064 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3065 on new Laptops?&lt;/p&gt;
3066 </description>
3067 </item>
3068
3069 <item>
3070 <title>How to transform a Debian based system to a Debian Edu installation</title>
3071 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3072 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3073 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3074 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3075 an operating system based on Debian intended for use in schools. It
3076 contain a turn-key solution for the computer network provided to
3077 pupils in the primary schools. It provide both the central server,
3078 network boot servers and desktop environments with heaps of
3079 educational software. The project was founded almost 12 years ago,
3080 2001-07-02. If you want to support the project, which is in need for
3081 cash to fund developer gatherings and other project related activity,
3082 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3083 donate some money&lt;/a&gt;.
3084
3085 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3086 lists and elsewhere, is the question on how to transform a Debian or
3087 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3088 hard, and last week I wrote a script to replicate the steps done by
3089 the Debian Edu installer.&lt;/p&gt;
3090
3091 &lt;p&gt;The script,
3092 &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;
3093 in the debian-edu-config package, will go through these six steps and
3094 transform an existing Debian Wheezy or Ubuntu (untested) installation
3095 into a Debian Edu Workstation:&lt;/p&gt;
3096
3097 &lt;ol&gt;
3098
3099 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3100 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3101 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3102 our configuration.&lt;/li&gt;
3103 &lt;li&gt;Preseed debconf database with profile setup in
3104 /etc/debian-edu/config, and run tasksel to install packages
3105 according to the profile specified in the config above,
3106 overriding some of the Debian automation machinery.&lt;/li&gt;
3107 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3108 that could not be done using preseeding.&lt;/li&gt;
3109 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3110
3111 &lt;/ol&gt;
3112
3113 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3114 replicated like this. Disk partitioning and LVM setup, for example.
3115 So this script just assume there is enough disk space to install all
3116 the needed packages.&lt;/p&gt;
3117
3118 &lt;p&gt;The script was created to help a Debian Edu student working on
3119 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3120 Debian Edu client, and using it he can take the existing
3121 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3122 transform it into a fully functioning Debian Edu Workstation (or
3123 Roaming Workstation, or whatever :).&lt;/p&gt;
3124
3125 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3126 If a LXDE based Roaming workstation is wanted instead, modify the
3127 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3128
3129 &lt;p&gt;&lt;pre&gt;
3130 PROFILE=&quot;Roaming-Workstation&quot;
3131 DESKTOP=&quot;lxde&quot;
3132 &lt;/pre&gt;&lt;/p&gt;
3133
3134 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3135 the cloud, by starting with a virtual Debian installation at some
3136 virtual hosting service and setting up all the services on first
3137 boot.&lt;/p&gt;
3138 </description>
3139 </item>
3140
3141 <item>
3142 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3143 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3144 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3145 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3146 <description>&lt;P&gt;In January,
3147 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3148 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3149 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3150 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3151 marvellous construction system from Denmark. We also created
3152 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3153 a place to take notes and write down our plans and hopes. And several
3154 people showed up to help. I was very happy to see the effect of my
3155 call. Since the small start, we have a debtags tag
3156 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3157 tag for LEGO related packages, and now count 10 packages related to
3158 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3159
3160 &lt;p&gt;&lt;table&gt;
3161 &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;
3162 &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;
3163 &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;
3164 &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;
3165 &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;
3166 &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;
3167 &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;
3168 &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;
3169 &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;
3170 &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;
3171 &lt;/table&gt;&lt;/p&gt;
3172
3173 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3174 currently available in Jessie/testing. leocad is so far only
3175 available in experimental.&lt;/p&gt;
3176
3177 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3178 adding the rest of the great free software tools available on Linux
3179 for LEGO designers.&lt;/p&gt;
3180 </description>
3181 </item>
3182
3183 <item>
3184 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3185 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3186 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3187 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3188 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3189 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3190 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3191 Debian release, and I expect to move my machines at home over to it fairly
3192 soon.&lt;/p&gt;
3193
3194 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3195 in particular make me very happy to see included. The
3196 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3197 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3198 included for the first time. Alongside similar programs like
3199 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3200 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3201 it allow for visual programming where syntax errors can not happen,
3202 and a friendly programming environment for learning to control the
3203 computer. Scratch will also be included in the next release of Debian
3204 Edu.&lt;/a&gt;
3205
3206 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3207 Edu/Skolelinux release too. The
3208 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3209 alpha release&lt;/a&gt; went out last week, and the next should soon
3210 follow.&lt;p&gt;
3211 </description>
3212 </item>
3213
3214 <item>
3215 <title>Isenkram 0.2 finally in the Debian archive</title>
3216 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3217 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3218 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3219 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3220 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3221 for many months. I uploaded it to the Debian experimental suite
3222 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3223
3224 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3225 install to work with a pluggable hardware device. The suggestion pop
3226 up when the device is plugged in. For example if a Lego Mindstorm NXT
3227 is inserted, it will suggest to install the program needed to program
3228 the NXT controller. Give it a go, and report bugs and suggestions to
3229 BTS. :)&lt;/p&gt;
3230 </description>
3231 </item>
3232
3233 <item>
3234 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3235 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3236 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3237 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3238 <description>&lt;p&gt;My
3239 &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
3240 bitcoin related blog post&lt;/a&gt; mentioned that the new
3241 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3242 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3243 2013-01-19, and have been available in unstable since then. It was
3244 automatically copied to Ubuntu, and is available in their Raring
3245 version too.&lt;/p&gt;
3246
3247 &lt;p&gt;But there is a strange problem with the build that block this new
3248 version from being available on the i386 and kfreebsd-i386
3249 architectures. For some strange reason, the autobuilders in Debian
3250 for these architectures fail to run the test suite on these
3251 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3252 We are so far unable to reproduce it when building it manually, and
3253 no-one have been able to propose a fix. If you got an idea what is
3254 failing, please let us know via the BTS.&lt;/p&gt;
3255
3256 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3257 I often run low on disk space, is the fact that the client will exit
3258 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3259 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3260 it. :)&lt;/p&gt;
3261
3262 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3263 activities, please send Bitcoin donations to my address
3264 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3265 </description>
3266 </item>
3267
3268 <item>
3269 <title>Welcome to the world, Isenkram!</title>
3270 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3271 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3272 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3273 <description>&lt;p&gt;Yesterday, I
3274 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3275 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3276 pluggable hardware devices, which I
3277 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3278 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3279 up, and caused me to really want to to open up the development to more
3280 people. But before I did this, I want to come up with a sensible name
3281 for this project. Today I finally decided on a new name, and I have
3282 renamed the project from hw-support-handler to this new name. In the
3283 process, I moved the source to git and made it available as a
3284 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3285 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3286 To fetch and build the latest version of the source, use&lt;/p&gt;
3287
3288 &lt;pre&gt;
3289 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3290 cd isenkram &amp;&amp; git-buildpackage -us -uc
3291 &lt;/pre&gt;
3292
3293 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3294 want to hack on the source or improve the package, please go ahead.
3295 But please talk to me first on IRC or via email before you do major
3296 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3297
3298 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3299 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3300 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3301 the German word eisenkram, for those that are familiar with that
3302 word.&lt;/p&gt;
3303
3304 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3305 instructions, to avoid confusing people with an error from the signing
3306 process.&lt;/p&gt;
3307
3308 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3309 clone argument to avoid the need for authentication.&lt;/p&gt;
3310 </description>
3311 </item>
3312
3313 <item>
3314 <title>First prototype ready making hardware easier to use in Debian</title>
3315 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3316 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3317 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3318 <description>&lt;p&gt;Early this month I set out to try to
3319 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3320 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3321 prototype is working, and it is ready for a larger audience. To test
3322 it, fetch the
3323 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3324 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3325 package. You might have to log out and in again activate the
3326 autostart script.&lt;/p&gt;
3327
3328 &lt;p&gt;The design is simple:&lt;/p&gt;
3329
3330 &lt;ul&gt;
3331
3332 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3333 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3334
3335 &lt;li&gt;This program listen for kernel events about new hardware (directly
3336 from the kernel like udev does), not using HAL dbus events as I
3337 initially did.&lt;/li&gt;
3338
3339 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3340 the APT database, a database
3341 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3342 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3343
3344 &lt;li&gt;If a package is mapped to the hardware in question, the package
3345 isn&#39;t installed yet and this is the first time the hardware was
3346 plugged in, show a desktop notification suggesting to install the
3347 package or packages.&lt;/li&gt;
3348
3349 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3350 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3351
3352 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3353 package while showing progress information in a window.&lt;/li&gt;
3354
3355 &lt;/ul&gt;
3356
3357 &lt;p&gt;I still need to come up with a better name for the system. Here
3358 are some screen shots showing the prototype in action. First the
3359 notification, then the password request, and finally the request to
3360 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3361
3362 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3363 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3364 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3365 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3366 &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;
3367
3368 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3369 is already useful. The database of hardware to package mappings also
3370 need more work. It is currently compatible with the Ubuntu way of
3371 storing such information in the package control file, but could be
3372 changed to use other formats instead or in addition to the current
3373 method. I&#39;ve dropped the use of discover for this mapping, as the
3374 modalias approach is more flexible and easier to use on Linux as long
3375 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3376
3377 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3378 here is the command required to check out and build the source: Use
3379 &#39;&lt;tt&gt;svn checkout
3380 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3381 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3382 devscripts package.&lt;/p&gt;
3383
3384 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3385 renamed to Isenkram and the source moved from the Debian Edu
3386 subversion repository to a Debian collab-maint git repository. See
3387 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3388 instructions&lt;/a&gt; for details.&lt;/p&gt;
3389 </description>
3390 </item>
3391
3392 <item>
3393 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3394 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3395 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3396 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3397 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3398 suddenly in bed. With a quiet whimper, it went completely quiet and
3399 black. The power button was no longer able to turn it on. It was a
3400 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3401 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3402 Compaq I had before that. Now I need to find a replacement. To keep
3403 going during Christmas, I moved the one year old SSD disk to my old
3404 X40 where it fitted (only one I had left that could use it), but it is
3405 not a durable solution.
3406
3407 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3408 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3409
3410 &lt;ul&gt;
3411
3412 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3413 than A4).&lt;/li&gt;
3414 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3415 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3416 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3417 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3418 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3419 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3420 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3421 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3422 size).&lt;/li&gt;
3423 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3424 X.org packages.&lt;/li&gt;
3425 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3426 the time).
3427
3428 &lt;/ul&gt;
3429
3430 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3431 list. The reason is simply that the specifications on laptops the
3432 last 10-15 years have been sufficient for my needs, and I have to look
3433 at other features to choose my laptop. But are there still made as
3434 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3435 robust, and Thinkpads seem to be heading in the wrong direction since
3436 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3437 still be useful.&lt;/p&gt;
3438
3439 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3440 external keyboard? I&#39;ll have to check the
3441 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3442 well-supported laptops, or perhaps just buy one preinstalled from one
3443 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3444 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3445 </description>
3446 </item>
3447
3448 <item>
3449 <title>How to find a browser plugin supporting a given MIME type</title>
3450 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3451 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3452 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3453 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3454 install to get support for a given MIME type. Thanks to
3455 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3456 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3457 Unfortunately, not very many packages provide the needed meta
3458 information, Anyway, here is a small script to look up all browser
3459 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3460
3461 &lt;pre&gt;
3462 #!/usr/bin/python
3463 import sys
3464 import apt
3465 def pkgs_handling_mimetype(mimetype):
3466 cache = apt.Cache()
3467 cache.open(None)
3468 thepkgs = []
3469 for pkg in cache:
3470 version = pkg.candidate
3471 if version is None:
3472 version = pkg.installed
3473 if version is None:
3474 continue
3475 record = version.record
3476 if not record.has_key(&#39;Npp-MimeType&#39;):
3477 continue
3478 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3479 for t in mime_types:
3480 t = t.rstrip().strip()
3481 if t == mimetype:
3482 thepkgs.append(pkg.name)
3483 return thepkgs
3484 mimetype = &quot;audio/ogg&quot;
3485 if 1 &lt; len(sys.argv):
3486 mimetype = sys.argv[1]
3487 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3488 for pkg in pkgs_handling_mimetype(mimetype):
3489 print &quot; %s&quot; %pkg
3490 &lt;/pre&gt;
3491
3492 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3493
3494 &lt;pre&gt;
3495 % ./apt-find-browserplug-for-mimetype
3496 Browser plugin packages supporting audio/ogg:
3497 gecko-mediaplayer
3498 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3499 Browser plugin packages supporting application/x-shockwave-flash:
3500 browser-plugin-gnash
3501 %
3502 &lt;/pre&gt;
3503
3504 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3505 itself to query for plugins and propose to install the needed
3506 packages. It would be great if Debian supported such feature too. Is
3507 anyone working on adding it?&lt;/p&gt;
3508
3509 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3510 request for icweasel support for this feature is
3511 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3512 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3513 of manpower and wish for a different design is the reason thus feature
3514 is not yet in iceweasel from Debian.&lt;/p&gt;
3515 </description>
3516 </item>
3517
3518 <item>
3519 <title>What is the most supported MIME type in Debian?</title>
3520 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3521 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3522 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3523 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3524 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3525 proposal to make it possible for a Desktop application to propose to
3526 the user some package to install to gain support for a given MIME
3527 type, font, library etc. that is currently missing. With such
3528 mechanism in place, it would be possible for the desktop to
3529 automatically propose and install leocad if some LDraw file is
3530 downloaded by the browser.&lt;/p&gt;
3531
3532 &lt;p&gt;To get some idea about the current content of the archive, I decided
3533 to write a simple program to extract all .desktop files from the
3534 Debian archive and look up the claimed MIME support there. The result
3535 can be found on the
3536 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3537 site&lt;/a&gt;. Using the collected information, it become possible to
3538 answer the question in the title. Here are the 20 most supported MIME
3539 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3540 The complete list is available from the link above.&lt;/p&gt;
3541
3542 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3543
3544 &lt;pre&gt;
3545 count MIME type
3546 ----- -----------------------
3547 32 text/plain
3548 30 audio/mpeg
3549 29 image/png
3550 28 image/jpeg
3551 27 application/ogg
3552 26 audio/x-mp3
3553 25 image/tiff
3554 25 image/gif
3555 22 image/bmp
3556 22 audio/x-wav
3557 20 audio/x-flac
3558 19 audio/x-mpegurl
3559 18 video/x-ms-asf
3560 18 audio/x-musepack
3561 18 audio/x-mpeg
3562 18 application/x-ogg
3563 17 video/mpeg
3564 17 audio/x-scpls
3565 17 audio/ogg
3566 16 video/x-ms-wmv
3567 &lt;/pre&gt;
3568
3569 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3570
3571 &lt;pre&gt;
3572 count MIME type
3573 ----- -----------------------
3574 33 text/plain
3575 32 image/png
3576 32 image/jpeg
3577 29 audio/mpeg
3578 27 image/gif
3579 26 image/tiff
3580 26 application/ogg
3581 25 audio/x-mp3
3582 22 image/bmp
3583 21 audio/x-wav
3584 19 audio/x-mpegurl
3585 19 audio/x-mpeg
3586 18 video/mpeg
3587 18 audio/x-scpls
3588 18 audio/x-flac
3589 18 application/x-ogg
3590 17 video/x-ms-asf
3591 17 text/html
3592 17 audio/x-musepack
3593 16 image/x-xbitmap
3594 &lt;/pre&gt;
3595
3596 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3597
3598 &lt;pre&gt;
3599 count MIME type
3600 ----- -----------------------
3601 31 text/plain
3602 31 image/png
3603 31 image/jpeg
3604 29 audio/mpeg
3605 28 application/ogg
3606 27 image/gif
3607 26 image/tiff
3608 26 audio/x-mp3
3609 23 audio/x-wav
3610 22 image/bmp
3611 21 audio/x-flac
3612 20 audio/x-mpegurl
3613 19 audio/x-mpeg
3614 18 video/x-ms-asf
3615 18 video/mpeg
3616 18 audio/x-scpls
3617 18 application/x-ogg
3618 17 audio/x-musepack
3619 16 video/x-ms-wmv
3620 16 video/x-msvideo
3621 &lt;/pre&gt;
3622
3623 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3624 information mentioned in DEP-11. I have not yet had time to look at
3625 it, but hope the PackageKit people in Debian are on top of these
3626 issues.&lt;/p&gt;
3627
3628 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3629 discovering a typo in my script.&lt;/p&gt;
3630 </description>
3631 </item>
3632
3633 <item>
3634 <title>Using modalias info to find packages handling my hardware</title>
3635 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3636 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3637 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3638 <description>&lt;p&gt;Yesterday, I wrote about the
3639 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3640 values provided by the Linux kernel&lt;/a&gt; following my hope for
3641 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3642 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3643 modalias values attached to package names can be used to map packages
3644 to hardware. This allow the system to look up and suggest relevant
3645 packages when I plug in some new hardware into my machine, and replace
3646 discover and discover-data as the database used to map hardware to
3647 packages.&lt;/p&gt;
3648
3649 &lt;p&gt;I create a modaliases file with entries like the following,
3650 containing package name, kernel module name (if relevant, otherwise
3651 the package name) and globs matching the relevant hardware
3652 modalias.&lt;/p&gt;
3653
3654 &lt;p&gt;&lt;blockquote&gt;
3655 Package: package-name
3656 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3657 &lt;/blockquote&gt;&lt;/p&gt;
3658
3659 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3660 for a given modalias value using this file.&lt;/p&gt;
3661
3662 &lt;p&gt;An entry like this would suggest the video and picture application
3663 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3664
3665 &lt;p&gt;&lt;blockquote&gt;
3666 Package: cheese
3667 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3668 &lt;/blockquote&gt;&lt;/p&gt;
3669
3670 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3671 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3672
3673 &lt;p&gt;&lt;blockquote&gt;
3674 Package: pcmciautils
3675 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3676 &lt;/blockquote&gt;&lt;/p&gt;
3677
3678 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3679 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3680
3681 &lt;p&gt;&lt;blockquote&gt;
3682 Package: colorhug-client
3683 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3684 &lt;/blockquote&gt;&lt;/p&gt;
3685
3686 &lt;p&gt;I believe the format is compatible with the format of the Packages
3687 file in the Debian archive. Ubuntu already uses their Packages file
3688 to store their mappings from packages to hardware.&lt;/p&gt;
3689
3690 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3691 announce the hardware it support in a way my prototype understand.
3692 This allow those publishing packages in an APT source outside the
3693 Debian archive as well as those backporting packages to make sure the
3694 hardware mapping are included in the package meta information. I&#39;ve
3695 tested such header in the pymissile package, and its modalias mapping
3696 is working as it should with my prototype. It even made it to Ubuntu
3697 Raring.&lt;/p&gt;
3698
3699 &lt;p&gt;To test if it was possible to look up supported hardware using only
3700 the shell tools available in the Debian installer, I wrote a shell
3701 implementation of the lookup code. The idea is to create files for
3702 each modalias and let the shell do the matching. Please check out and
3703 try the
3704 &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;
3705 shell script. It run without any extra dependencies and fetch the
3706 hardware mappings from the Debian archive and the subversion
3707 repository where I currently work on my prototype.&lt;/p&gt;
3708
3709 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3710 install yubikey-personalization:&lt;/p&gt;
3711
3712 &lt;p&gt;&lt;blockquote&gt;
3713 % ./hw-support-lookup
3714 &lt;br&gt;yubikey-personalization
3715 &lt;br&gt;%
3716 &lt;/blockquote&gt;&lt;/p&gt;
3717
3718 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3719 propose to install the pcmciautils package:&lt;/p&gt;
3720
3721 &lt;p&gt;&lt;blockquote&gt;
3722 % ./hw-support-lookup
3723 &lt;br&gt;pcmciautils
3724 &lt;br&gt;%
3725 &lt;/blockquote&gt;&lt;/p&gt;
3726
3727 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3728 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3729 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3730
3731 &lt;p&gt;It could be possible to generate several of the mappings between
3732 packages and hardware. One source would be to look at packages with
3733 kernel modules, ie packages with *.ko files in /lib/modules/, and
3734 extract their modalias information. Another would be to look at
3735 packages with udev rules, ie packages with files in
3736 /lib/udev/rules.d/, and extract their vendor/model information to
3737 generate a modalias matching rule. I have not tested any of these to
3738 see if it work.&lt;/p&gt;
3739
3740 &lt;p&gt;If you want to help implementing a system to let us propose what
3741 packages to install when new hardware is plugged into a Debian
3742 machine, please send me an email or talk to me on
3743 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3744 </description>
3745 </item>
3746
3747 <item>
3748 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3749 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3750 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3751 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3752 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3753 information, to find the packages that support a given piece of
3754 hardware, I refreshed my memory regarding modalias values, and decided
3755 to document the details. Here are my findings so far, also available
3756 in
3757 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3758 Debian Edu subversion repository&lt;/a&gt;:
3759
3760 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3761
3762 &lt;p&gt;This document try to explain what the different types of modalias
3763 values stands for. It is in part based on information from
3764 &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;,
3765 &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;,
3766 &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
3767 &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;.
3768
3769 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3770 this shell script:&lt;/p&gt;
3771
3772 &lt;pre&gt;
3773 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3774 &lt;/pre&gt;
3775
3776 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3777 using modinfo:&lt;/p&gt;
3778
3779 &lt;pre&gt;
3780 % /sbin/modinfo psmouse | grep alias:
3781 alias: serio:ty05pr*id*ex*
3782 alias: serio:ty01pr*id*ex*
3783 %
3784 &lt;/pre&gt;
3785
3786 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3787
3788 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3789 Bridge memory controller:&lt;/p&gt;
3790
3791 &lt;p&gt;&lt;blockquote&gt;
3792 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3793 &lt;/blockquote&gt;&lt;/p&gt;
3794
3795 &lt;p&gt;This represent these values:&lt;/p&gt;
3796
3797 &lt;pre&gt;
3798 v 00008086 (vendor)
3799 d 00002770 (device)
3800 sv 00001028 (subvendor)
3801 sd 000001AD (subdevice)
3802 bc 06 (bus class)
3803 sc 00 (bus subclass)
3804 i 00 (interface)
3805 &lt;/pre&gt;
3806
3807 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3808 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3809 0600. The 0600 class is a host bridge. Other useful bus values are
3810 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3811
3812 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3813 means.&lt;/p&gt;
3814
3815 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3816
3817 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3818 USB hub in a laptop:&lt;/p&gt;
3819
3820 &lt;p&gt;&lt;blockquote&gt;
3821 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3822 &lt;/blockquote&gt;&lt;/p&gt;
3823
3824 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3825
3826 &lt;pre&gt;
3827 v 1D6B (device vendor)
3828 p 0001 (device product)
3829 d 0206 (bcddevice)
3830 dc 09 (device class)
3831 dsc 00 (device subclass)
3832 dp 00 (device protocol)
3833 ic 09 (interface class)
3834 isc 00 (interface subclass)
3835 ip 00 (interface protocol)
3836 &lt;/pre&gt;
3837
3838 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3839 class is in the interface class section. For a simple USB web camera,
3840 these alias entries show up:&lt;/p&gt;
3841
3842 &lt;p&gt;&lt;blockquote&gt;
3843 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3844 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3845 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3846 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3847 &lt;/blockquote&gt;&lt;/p&gt;
3848
3849 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3850 camera), 0101 is audio control device and 0102 is audio streaming (aka
3851 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3852
3853 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3854
3855 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3856 receiver in a Thinkpad X40:&lt;/p&gt;
3857
3858 &lt;p&gt;&lt;blockquote&gt;
3859 acpi:IBM0071:PNP0511:
3860 &lt;/blockquote&gt;&lt;/p&gt;
3861
3862 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3863
3864 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3865
3866 &lt;p&gt;The DMI table contain lots of information about the computer case
3867 and model. This is an entry for a IBM Thinkpad X40, fetched from
3868 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3869
3870 &lt;p&gt;&lt;blockquote&gt;
3871 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3872 &lt;/blockquote&gt;&lt;/p&gt;
3873
3874 &lt;p&gt;The values present are&lt;/p&gt;
3875
3876 &lt;pre&gt;
3877 bvn IBM (BIOS vendor)
3878 bvr 1UETB6WW(1.66) (BIOS version)
3879 bd 06/15/2005 (BIOS date)
3880 svn IBM (system vendor)
3881 pn 2371H4G (product name)
3882 pvr ThinkPadX40 (product version)
3883 rvn IBM (board vendor)
3884 rn 2371H4G (board name)
3885 rvr NotAvailable (board version)
3886 cvn IBM (chassis vendor)
3887 ct 10 (chassis type)
3888 cvr NotAvailable (chassis version)
3889 &lt;/pre&gt;
3890
3891 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3892 found in the dmidecode source:&lt;/p&gt;
3893
3894 &lt;pre&gt;
3895 3 Desktop
3896 4 Low Profile Desktop
3897 5 Pizza Box
3898 6 Mini Tower
3899 7 Tower
3900 8 Portable
3901 9 Laptop
3902 10 Notebook
3903 11 Hand Held
3904 12 Docking Station
3905 13 All In One
3906 14 Sub Notebook
3907 15 Space-saving
3908 16 Lunch Box
3909 17 Main Server Chassis
3910 18 Expansion Chassis
3911 19 Sub Chassis
3912 20 Bus Expansion Chassis
3913 21 Peripheral Chassis
3914 22 RAID Chassis
3915 23 Rack Mount Chassis
3916 24 Sealed-case PC
3917 25 Multi-system
3918 26 CompactPCI
3919 27 AdvancedTCA
3920 28 Blade
3921 29 Blade Enclosing
3922 &lt;/pre&gt;
3923
3924 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3925 table. For example my home server is a tower, but the DMI modalias
3926 claim it is a desktop.&lt;/p&gt;
3927
3928 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3929
3930 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3931 test machine:&lt;/p&gt;
3932
3933 &lt;p&gt;&lt;blockquote&gt;
3934 serio:ty01pr00id00ex00
3935 &lt;/blockquote&gt;&lt;/p&gt;
3936
3937 &lt;p&gt;The values present are&lt;/p&gt;
3938
3939 &lt;pre&gt;
3940 ty 01 (type)
3941 pr 00 (prototype)
3942 id 00 (id)
3943 ex 00 (extra)
3944 &lt;/pre&gt;
3945
3946 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3947 the valid values are.&lt;/p&gt;
3948
3949 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3950
3951 &lt;p&gt;There are heaps of other modalias subtypes according to
3952 file2alias.c. There is the rest of the list from that source: amba,
3953 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3954 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3955 vmbus, x86cpu and zorro. I did not spend time documenting all of
3956 these, as they do not seem relevant for my intended use with mapping
3957 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3958
3959 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3960
3961 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3962 one can use the following shell script:&lt;/p&gt;
3963
3964 &lt;pre&gt;
3965 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3966 echo &quot;$id&quot; ; \
3967 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3968 done
3969 &lt;/pre&gt;
3970
3971 &lt;p&gt;The output can look like this (only the first few entries as the
3972 list is very long on my test machine):&lt;/p&gt;
3973
3974 &lt;pre&gt;
3975 acpi:ACPI0003:
3976 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3977 acpi:device:
3978 FATAL: Module acpi:device: not found.
3979 acpi:IBM0068:
3980 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3981 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3982 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3983 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3984 acpi:IBM0071:PNP0511:
3985 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3986 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3987 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3988 [...]
3989 &lt;/pre&gt;
3990
3991 &lt;p&gt;If you want to help implementing a system to let us propose what
3992 packages to install when new hardware is plugged into a Debian
3993 machine, please send me an email or talk to me on
3994 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3995
3996 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3997 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3998 in /sys/ with space in them.&lt;/p&gt;
3999 </description>
4000 </item>
4001
4002 <item>
4003 <title>Moved the pymissile Debian packaging to collab-maint</title>
4004 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4005 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4006 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4007 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4008 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4009 Launcher and updated the Debian package
4010 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4011 sure udev will fix the device permissions when it is plugged in. I
4012 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4013 hopefully make the package be proposed by jockey in Ubuntu when a user
4014 plug in his rocket launcher. In the process I moved the source to a
4015 git repository under collab-maint, to make it easier for any DD to
4016 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4017 is not very active, but the software still work for me even after five
4018 years of relative silence. The new git repository is not listed in
4019 the uploaded package yet, because I want to test the other changes a
4020 bit more before I upload the new version. If you want to check out
4021 the new version with a .desktop file included, visit the
4022 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4023 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4024 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4025 </description>
4026 </item>
4027
4028 <item>
4029 <title>Lets make hardware dongles easier to use in Debian</title>
4030 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4032 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4033 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4034 general, is that there is a great package management system with the
4035 ability to automatically install software packages by downloading them
4036 from the distribution mirrors, but no way to get it to automatically
4037 install the packages I need to use the hardware I plug into my
4038 machine. Even if the package to use it is easily available from the
4039 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4040 suggest to automatically install the python-nxt, nbc and t2n packages
4041 I need to talk to it. When I plug in a Yubikey, it could propose the
4042 yubikey-personalization package. The information required to do this
4043 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4044
4045 &lt;p&gt;Some years ago, I proposed to
4046 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4047 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4048 simple:
4049
4050 &lt;ul&gt;
4051
4052 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4053 starting when a user log in.&lt;/li&gt;
4054
4055 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4056 hardware is inserted into the computer.&lt;/li&gt;
4057
4058 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4059 database mapping to packages, and take note of any non-installed
4060 packages.&lt;/li&gt;
4061
4062 &lt;li&gt;Show a message to the user proposing to install the discovered
4063 package, and make it easy to install it.&lt;/li&gt;
4064
4065 &lt;/ul&gt;
4066
4067 &lt;p&gt;I am not sure what the best way to implement this is, but my
4068 initial idea was to use dbus events to discover new hardware, the
4069 discover database to find packages and
4070 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4071 packages.&lt;/p&gt;
4072
4073 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4074 draft package is now checked into
4075 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4076 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4077 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4078 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4079 the relevant packages in Debian, and uploaded a new version
4080 2.2013.01.09 to unstable. I also discovered that the current
4081 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4082 package in Debian no longer discovered any USB devices, because
4083 /proc/bus/usb/devices is no longer present. I ported it to use
4084 libusb as a fall back option to get it working. The fixed package
4085 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4086 because of the freeze).&lt;/p&gt;
4087
4088 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4089 desktop notification to show up (only once, the first time it is
4090 inserted):&lt;/p&gt;
4091
4092 &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;
4093
4094 &lt;p&gt;For this prototype to be really useful, some way to automatically
4095 install the proposed packages by pressing the &quot;Please install
4096 program(s)&quot; button should to be implemented.&lt;/p&gt;
4097
4098 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4099 happen, please help me update the discover-data database with mappings
4100 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4101 list the package you would like to have installed when a given
4102 hardware device is inserted into your computer, and report bugs using
4103 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4104 such mapping, please let me know.&lt;/p&gt;
4105
4106 &lt;p&gt;This prototype need more work, and there are several questions that
4107 should be considered before it is ready for production use. Is dbus
4108 the correct way to detect new hardware? At the moment I look for HAL
4109 dbus events on the system bus, because that is the events I could see
4110 on my Debian Squeeze KDE desktop. Are there better events to use?
4111 How should the user be notified? Is the desktop notification
4112 mechanism the best option, or should the background daemon raise a
4113 popup instead? How should packages be installed? When should they
4114 not be installed?&lt;/p&gt;
4115
4116 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4117 please send me an email. :)&lt;/p&gt;
4118 </description>
4119 </item>
4120
4121 <item>
4122 <title>New IRC channel for LEGO designers using Debian</title>
4123 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4124 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4125 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4126 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4127 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4128 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4129 discovered I had to build all the tools myself because none were
4130 already in Debian Squeeze. If Debian support for LEGO is something
4131 you care about, please join me on the IRC channel
4132 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4133 irc.debian.org). There is a lot that could be done to improve the
4134 Debian support for LEGO designers. For example both CAD software
4135 and Mindstorm compilers are missing. :)&lt;/p&gt;
4136
4137 &lt;p&gt;Update 2012-01-03: A
4138 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4139 including links to Lego related packages is now available.&lt;/p&gt;
4140 </description>
4141 </item>
4142
4143 <item>
4144 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4145 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4146 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4147 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4148 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4149 year! I hope next year will prove to be a good year.&lt;/p&gt;
4150
4151 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4152 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4153 between each other with minimal overhead, is a very interesting
4154 experiment. And as I wrote a few days ago, the bitcoin situation in
4155 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4156 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4157 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4158 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4159 for one of the ftpmasters to approve the new bitcoin-qt package
4160 name.&lt;/p&gt;
4161
4162 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4163 team in Debian, you can easily test the package in Debian Squeeze
4164 using the following steps to get a set of working packages:&lt;/p&gt;
4165
4166 &lt;blockquote&gt;&lt;pre&gt;
4167 git clone git://git.debian.org/git/collab-maint/bitcoin
4168 cd bitcoin
4169 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4170 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4171 &lt;/pre&gt;&lt;/blockquote&gt;
4172
4173 &lt;p&gt;You might have to install some build dependencies as well. The
4174 list of commands should give you two packages, bitcoind and
4175 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4176 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4177 around 5.6 GiB of data on my machine at the moment. Make sure your
4178 ~/.bitcoin/ directory have lots of spare room if you want to download
4179 all the blocks. The client will warn if the disk is getting full, so
4180 there is not really a problem if you got too little room, but you will
4181 not be able to get all the features out of the client.&lt;/p&gt;
4182
4183 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4184 activities, please send Bitcoin donations to my address
4185 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4186 </description>
4187 </item>
4188
4189 <item>
4190 <title>A word on bitcoin support in Debian</title>
4191 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4192 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4193 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4194 <description>&lt;p&gt;It has been a while since I wrote about
4195 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4196 peer-to-peer based crypto-currency, and the reason is simply that I
4197 have been busy elsewhere. But two days ago, I started looking at the
4198 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4199 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4200 is now maintained by a
4201 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4202 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4203 owe a huge thank you to all these team members. :)
4204 But I was sad to discover that the bitcoin client is missing in
4205 Wheezy. It is only available in Sid (and an outdated client from
4206 backports). The client had several RC bugs registered in BTS blocking
4207 it from entering testing. To try to help the team and improve the
4208 situation, I spent some time providing patches and triaging the bug
4209 reports. I also had a look at the bitcoin package available from Matt
4210 Corallo in a
4211 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4212 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4213 Debian package.&lt;/p&gt;
4214
4215 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4216 IRC, I pushed several patches into the collab-maint git repository to
4217 improve the package. It now contains fixes for the RC issues (not from
4218 me, but fixed by Scott Howard), build rules for a Qt GUI client
4219 package, konqueror support for the bitcoin: URI and bash completion
4220 setup. As I work on Debian Squeeze, I also created
4221 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4222 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4223 it and try to integrate it into the git repository before uploading a
4224 new version to unstable.
4225
4226 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4227 centralized control currently exercised in the monetary system. I
4228 find it completely unacceptable that the USA government is collecting
4229 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4230 that the major credit card companies can block legal money
4231 transactions to Wikileaks. But for bitcoin to succeed, more people
4232 need to use bitcoins, and more people need to accept bitcoins when
4233 they sell products and services. Improving the bitcoin support in
4234 Debian is a small step in the right direction, but not enough.
4235 Unfortunately the user experience when browsing the web and wanting to
4236 pay with bitcoin is still not very good. The bitcoin: URI is a step
4237 in the right direction, but need to work in most or every browser in
4238 use. Also the bitcoin-qt client is too heavy to fire up to do a
4239 quick transaction. I believe there are other clients available, but
4240 have not tested them.&lt;/p&gt;
4241
4242 &lt;p&gt;My
4243 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4244 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4245 I received 20.15 BTC so far on the address I provided in my blog two
4246 years ago, as can be
4247 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4248 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4249 donation. The blockexplorer service demonstrates quite well that
4250 bitcoin is not quite anonymous and untracked. :) I wonder if the
4251 number of users have gone up since then. If you use bitcoin and want
4252 to show your support of my activity, please send Bitcoin donations to
4253 the same address as last time,
4254 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4255 </description>
4256 </item>
4257
4258 <item>
4259 <title>Git repository for song book for Computer Scientists</title>
4260 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4261 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4262 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4263 <description>&lt;p&gt;As I
4264 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4265 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4266 years ago, and today I finally found time to create a public
4267 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4268 repository for the project&lt;/a&gt;.&lt;/p&gt;
4269
4270 &lt;p&gt;If you want to help out, please clone the source and submit patches
4271 to the HTML version. To generate the PDF and PostScript version,
4272 please use prince XML, or let me know about a useful free software
4273 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4274
4275 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4276 PostScript formats at
4277 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4278 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4279 </description>
4280 </item>
4281
4282 <item>
4283 <title>Gratulerer med 19-årsdagen, Debian!</title>
4284 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4285 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4286 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4287 <description>&lt;p&gt;I dag fyller
4288 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4289 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4290 si gratulerer med dagen, Debian!&lt;/p&gt;
4291 </description>
4292 </item>
4293
4294 <item>
4295 <title>Song book for Computer Scientists</title>
4296 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4297 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4298 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4299 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4300 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4301 collecting computer related songs for use at parties. The original
4302 version was written in LaTeX, but a few years ago I got help from
4303 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4304 while keeping the ability to create a nice book in PDF format. I have
4305 not had time to maintain the book for a while now, and guess I should
4306 put it up on some public version control repository where others can
4307 help me extend and update the book. If anyone is volunteering to help
4308 me with this, send me an email. Also let me know if there are songs
4309 missing in my book.&lt;/p&gt;
4310
4311 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4312 me today that I really should let all my readers share the joys of
4313 singing out load about programming, computers and computer networks.
4314 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4315 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4316 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4317 Computer Science Songbook&lt;/a&gt;.
4318 </description>
4319 </item>
4320
4321 <item>
4322 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4323 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4324 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4325 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4326 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4327 around 1000 at the moment. To be able to get help from the vendors
4328 when something go wrong, we want to keep the firmware on the servers
4329 up to date. If the firmware isn&#39;t the latest and greatest, the
4330 vendors typically refuse to start debugging any problems until the
4331 firmware is upgraded. So before every reboot, we want to upgrade the
4332 firmware, and we would really like everyone handling servers at the
4333 university to do this themselves when they plan to reboot a machine.
4334 For that to happen we at the unix server admin group need to provide
4335 the tools to do so.&lt;/p&gt;
4336
4337 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4338 fetch and install the latest firmware for the servers we got. Most of
4339 our hardware are from Dell and HP, so I have focused on these servers
4340 so far. This blog post is about the Dell part.&lt;/P&gt;
4341
4342 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4343 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4344 with firmware information for all 11th generation servers, listing
4345 which firmware should be used on a given model and where on the FTP
4346 site I can find it. Using a simple perl XML parser I can then
4347 download the shell scripts Dell provides to do firmware upgrades from
4348 within Linux and reboot when all the firmware is primed and ready to
4349 be activated on the first reboot.&lt;/p&gt;
4350
4351 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4352 Are there anyone working on similar tools for firmware upgrading all
4353 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4354
4355 &lt;p&gt;&lt;pre&gt;
4356 #!/usr/bin/perl
4357 use strict;
4358 use warnings;
4359 use File::Temp qw(tempdir);
4360 BEGIN {
4361 # Install needed RHEL packages if missing
4362 my %rhelmodules = (
4363 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4364 );
4365 for my $module (keys %rhelmodules) {
4366 eval &quot;use $module;&quot;;
4367 if ($@) {
4368 my $pkg = $rhelmodules{$module};
4369 system(&quot;yum install -y $pkg&quot;);
4370 eval &quot;use $module;&quot;;
4371 }
4372 }
4373 }
4374 my $errorsto = &#39;pere@hungry.com&#39;;
4375
4376 upgrade_dell();
4377
4378 exit 0;
4379
4380 sub run_firmware_script {
4381 my ($opts, $script) = @_;
4382 unless ($script) {
4383 print STDERR &quot;fail: missing script name\n&quot;;
4384 exit 1
4385 }
4386 print STDERR &quot;Running $script\n\n&quot;;
4387
4388 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4389 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4390 } else {
4391 print STDERR &quot;fail: firmware script returned error\n&quot;;
4392 }
4393 }
4394
4395 sub run_firmware_scripts {
4396 my ($opts, @dirs) = @_;
4397 # Run firmware packages
4398 for my $dir (@dirs) {
4399 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4400 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4401 while (my $s = readdir $dh) {
4402 next if $s =~ m/^\.\.?/;
4403 run_firmware_script($opts, &quot;$dir/$s&quot;);
4404 }
4405 closedir $dh;
4406 }
4407 }
4408
4409 sub download {
4410 my $url = shift;
4411 print STDERR &quot;info: Downloading $url\n&quot;;
4412 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4413 }
4414
4415 sub upgrade_dell {
4416 my @dirs;
4417 my $product = `dmidecode -s system-product-name`;
4418 chomp $product;
4419
4420 if ($product =~ m/PowerEdge/) {
4421
4422 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4423 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4424
4425 my $tmpdir = tempdir(
4426 CLEANUP =&gt; 1
4427 );
4428 chdir($tmpdir);
4429 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4430 system(&#39;gunzip Catalog.xml.gz&#39;);
4431 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4432 # -q is quiet, disabling interactivity and reducing console output
4433 my $fwopts = &quot;-q&quot;;
4434 if (@paths) {
4435 for my $url (@paths) {
4436 fetch_dell_fw($url);
4437 }
4438 run_firmware_scripts($fwopts, $tmpdir);
4439 } else {
4440 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4441 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4442 }
4443 chdir(&#39;/&#39;);
4444 } else {
4445 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4446 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4447 }
4448 }
4449
4450 sub fetch_dell_fw {
4451 my $path = shift;
4452 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4453 download($url);
4454 }
4455
4456 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4457 # firmware packages to download from Dell. Only work for Linux
4458 # machines and 11th generation Dell servers.
4459 sub fetch_dell_fw_list {
4460 my $filename = shift;
4461
4462 my $product = `dmidecode -s system-product-name`;
4463 chomp $product;
4464 my ($mybrand, $mymodel) = split(/\s+/, $product);
4465
4466 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4467
4468 my $xml = XMLin($filename);
4469 my @paths;
4470 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4471 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4472 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4473 my $oscode;
4474 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4475 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4476 } else {
4477 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4478 }
4479 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4480 {
4481 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4482 }
4483 }
4484 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4485 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4486
4487 # Drop application packages, only firmware and BIOS
4488 next if &#39;APAC&#39; eq $componenttype;
4489
4490 my $cpath = $component-&gt;{path};
4491 for my $path (@paths) {
4492 if ($cpath =~ m%/$path$%) {
4493 push(@paths, $cpath);
4494 }
4495 }
4496 }
4497 return @paths;
4498 }
4499 &lt;/pre&gt;
4500
4501 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4502 it could work on other platforms with some tweaking. Anyone know a
4503 index like Catalog.xml is available from HP for HP servers? At the
4504 moment I maintain a similar list manually and it is quickly getting
4505 outdated.&lt;/p&gt;
4506 </description>
4507 </item>
4508
4509 <item>
4510 <title>How is booting into runlevel 1 different from single user boots?</title>
4511 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4512 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4513 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4514 <description>&lt;p&gt;Wouter Verhelst have some
4515 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4516 comments and opinions&lt;/a&gt; on my blog post on
4517 &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
4518 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4519 &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
4520 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4521 small piece of his comment now, and though it best to address the
4522 misunderstanding he bring forward:&lt;/p&gt;
4523
4524 &lt;p&gt;&lt;blockquote&gt;
4525 Currently, a system admin has four options: [...] boot to a
4526 single-user system (by adding &#39;single&#39; to the kernel command line;
4527 this runs rcS and rc1 scripts)
4528 &lt;/blockquote&gt;&lt;/p&gt;
4529
4530 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4531 and booting into runlevel 1 is the same. I am not surprised he
4532 believe this, because it would make sense and is a quite sensible
4533 thing to believe. But because the boot in Debian is slightly broken,
4534 runlevel 1 do not work properly and it isn&#39;t the same as single user
4535 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4536 hard to explain.&lt;/p&gt;
4537
4538 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4539 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4540 executed in single user mode is sulogin. Single user mode is a boot
4541 state &quot;between&quot; the runlevels, and when booting into single user mode,
4542 only the scripts in /etc/rcS.d/ are executed before the init process
4543 enters the single user state. When switching to runlevel 1, the state
4544 is in fact not ending in runlevel 1, but it passes through runlevel 1
4545 and end up in the single user mode (see /etc/rc1.d/S03single, which
4546 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4547 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4548 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4549 mode).&lt;/p&gt;
4550
4551 &lt;p&gt;This summary might make it clearer. When booting for the first
4552 time into single user mode, the following commands are executed:
4553 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4554 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4555 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4556 trying to continue after visiting single user mode. Not all services
4557 are started again as they should, causing the machine to end up in an
4558 unpredicatble state. This is why Debian admins recommend rebooting
4559 after visiting single user mode.&lt;/p&gt;
4560
4561 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4562 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4563 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4564 stopped when passing through the scripts in /etc/rc1.d/, and not
4565 started again when switching away from runlevel 1 to the runlevels
4566 2-5. I believe the problem is best fixed by moving all the scripts
4567 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4568 functioning single user mode during boot.&lt;/p&gt;
4569
4570 &lt;p&gt;I have spent several years investigating the Debian boot system,
4571 and discovered this problem a few years ago. I suspect it originates
4572 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4573 </description>
4574 </item>
4575
4576 <item>
4577 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4578 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4579 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4580 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4581 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4582 are started from /etc/rcS.d/. In fact, there is a bite more of them
4583 than make sense, and this causes a few problems. What kind of
4584 problems, you might ask. There are at least two problems. The first
4585 is that it is not possible to recover a machine after switching to
4586 runlevel 1. One need to actually reboot to get the machine back to
4587 the expected state. The other is that single user boot will sometimes
4588 run into problems because some of the subsystems are activated before
4589 the root login is presented, causing problems when trying to recover a
4590 machine from a problem in that subsystem. A minor additional point is
4591 that moving more scripts out of rcS.d/ and into the other rc#.d/
4592 directories will increase the amount of scripts that can run in
4593 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4594
4595 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4596 scripts that _have_ to execute before the root login prompt is
4597 presented during a single user boot should go there. Everything else
4598 should go into the numeric runlevels. This means things like
4599 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4600 the numeric runlevels. Today in Debian, there are around 115 init.d
4601 scripts that are started from rcS.d/, and most of them should be moved
4602 out. Do your package have one of them? Please help us make single
4603 user and runlevel 1 better by moving it.&lt;/p&gt;
4604
4605 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4606 etc. should still be started from rcS.d/, but there is for example no
4607 need to have the network enabled before the single user login prompt
4608 is presented.&lt;/p&gt;
4609
4610 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4611 Debian systems working while scripts migrate and during upgrades, the
4612 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4613 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4614 and the next ones can only be moved when their dependencies have been
4615 moved first. This migration must be done sequentially while we ensure
4616 that the package system upgrade packages in the right order to keep
4617 the system state correct. This will require some coordination when it
4618 comes to network related packages, but most of the packages with
4619 scripts that should migrate do not have anything in rcS.d/ depending
4620 on them. Some packages have already been updated, like the sudo
4621 package, while others are still left to do. I wish I had time to work
4622 on this myself, but real live constrains make it unlikely that I will
4623 find time to push this forward.&lt;/p&gt;
4624 </description>
4625 </item>
4626
4627 <item>
4628 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4629 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4631 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4632 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4633 mentioned the issues I believe should be improved in Debian for its
4634 desktop to be useful for more people. The use case for this is my
4635 parents, which are currently running Kubuntu which solve the
4636 issues.&lt;/p&gt;
4637
4638 &lt;p&gt;I suspect these four missing features are not very hard to
4639 implement. After all, they are present in Ubuntu, so if we wanted to
4640 do this in Debian we would have a source.&lt;/p&gt;
4641
4642 &lt;ol&gt;
4643
4644 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4645 are new packages available for upgrades, a icon in the KDE status bar
4646 indicate this, and clicking on it will activate the simple upgrade
4647 tool to handle it. I have no problem guiding both of my parents
4648 through the process over the phone. If a kernel reboot is required,
4649 this too is indicated by the status bars and the upgrade tool. Last
4650 time I checked, nothing with the same features was working in KDE in
4651 Debian.&lt;/li&gt;
4652
4653 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4654 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4655 currently have a handler for, it will ask the user if the system
4656 should search for a package that would add support for this MIME type,
4657 and if the user say yes, the APT sources will be searched for packages
4658 advertising the MIME type in their control file (visible in the
4659 Packages file in the APT archive). If one or more packages are found,
4660 it is a simple click of the mouse to add support for the missing mime
4661 type. If the package require the user to accept some non-free
4662 license, this is explained to the user. The entire process make it
4663 more clear to the user why something do not work in the browser, and
4664 make the chances higher for the user to blame the web page authors and
4665 not the browser for any missing features.&lt;/li&gt;
4666
4667 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4668 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4669 it is not supporting, a dialog pop up asking the user if the system
4670 should search for a package that would add support for it. This
4671 happen with things like MP3, Windows Media or H.264. The selection
4672 and installation procedure is very similar to the Firefox browser
4673 plugin handling. This is as far as I know implemented using a
4674 gstreamer hook. The end result is that the user easily get access to
4675 the codecs that are present from the APT archives available, while
4676 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4677
4678 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4679 displaying a text/plain file in my Debian browser, it will propose to
4680 start emacs to show it. If I remember correctly, when doing the same
4681 in Kunbutu it show the file as a text file in the browser. At least I
4682 know Opera will show text files within the browser. I much prefer the
4683 latter behaviour.&lt;/li&gt;
4684
4685 &lt;/ol&gt;
4686
4687 &lt;p&gt;There are other nice features as well, like the simplified suite
4688 upgrader, but given that I am the one mostly doing the dist-upgrade,
4689 it do not matter much.&lt;/p&gt;
4690
4691 &lt;p&gt;I really hope we could get these features in place for the next
4692 Debian release. It would require the coordinated effort of several
4693 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4694 </description>
4695 </item>
4696
4697 <item>
4698 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4699 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4700 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4701 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4702 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4703 site is build on Debian/Squeeze, and this platform was chosen because
4704 I am most familiar with Debian (being a Debian Developer for around 10
4705 years) because it is the latest stable Debian release which should get
4706 security support for a few years.&lt;/p&gt;
4707
4708 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4709 that are missing in Debian at the moment. It would be great if these
4710 modules were added to the Debian archive, allowing anyone to set up
4711 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4712 in their own country using only Debian packages. The list of modules
4713 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4714 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4715 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4716 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4717 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4718 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4719 easier in the future.&lt;/p&gt;
4720
4721 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4722 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4723 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4724 with the responsibility of tracking security problems, which I really
4725 do not have time for.&lt;/p&gt;
4726 </description>
4727 </item>
4728
4729 <item>
4730 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4731 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4732 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4733 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4734 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4735 posts have been in Norwegian the last few weeks, so here is a short
4736 update in English.&lt;/p&gt;
4737
4738 &lt;p&gt;The kids still keep me too busy to get much free software work
4739 done, but I did manage to organise a project to get a Norwegian port
4740 of the British service
4741 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4742 and it has been running for a month now. The entire project has been
4743 organised by me and two others. Around Christmas we gathered sponsors
4744 to fund the development work. In January I drafted a contract with
4745 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4746 and in February the development took place. Most of it involved
4747 converting the source to use GPS coordinates instead of British
4748 easting/northing, and the resulting code should be a lot easier to get
4749 running in any country by now. The Norwegian
4750 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4751 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4752 source and the source for administrative borders in Norway, and
4753 support for this had to be added/fixed.&lt;/p&gt;
4754
4755 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4756 polishing the system before we announced it March 7th. The system is
4757 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4758 problem reports in a few weeks. Soon we hope to announce the Android
4759 and iPhone versions making it even easier to report problems with the
4760 public infrastructure.&lt;/p&gt;
4761
4762 &lt;p&gt;Perhaps something to consider for those of you in countries without
4763 such service?&lt;/p&gt;
4764 </description>
4765 </item>
4766
4767 <item>
4768 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4769 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4770 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4771 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4772 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4773 issues here at my work with the University of Oslo. My idea is that
4774 it should be possible to use the information about security issues
4775 available on the Internet, and check our locally
4776 maintained/distributed software against this information. It should
4777 allow us to verify that no known security issues are forgotten. The
4778 CVE database listing vulnerabilities seem like a great central point,
4779 and by using the package lists from Debian mapped to CVEs provided by
4780 the testing security team, I believed it should be possible to figure
4781 out which security holes were present in our free software
4782 collection.&lt;/p&gt;
4783
4784 &lt;p&gt;After reading up on the topic, it became obvious that the first
4785 building block is to be able to name software packages in a unique and
4786 consistent way across data sources. I considered several ways to do
4787 this, for example coming up with my own naming scheme like using URLs
4788 to project home pages or URLs to the Freshmeat entries, or using some
4789 existing naming scheme. And it seem like I am not the first one to
4790 come across this problem, as MITRE already proposed and implemented a
4791 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4792 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4793 software, hardware and other platform components. The CPE ids are
4794 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4795 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4796 issues for any CPE name. With this in place, all I need to do is to
4797 locate the CPE id for the software packages we use at the university.
4798 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4799 NVD entry if a CVE for the package exist).&lt;/p&gt;
4800
4801 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4802 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4803 check out, one could look up
4804 &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
4805 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4806 The most recent one is
4807 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4808 and at the bottom of the NVD page for this vulnerability the complete
4809 list of affected versions is provided.&lt;/p&gt;
4810
4811 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4812 for offline processing of issues. Using this dump, I&#39;ve written a
4813 small script taking a list of CPEs as input and list all CVEs
4814 affecting the packages represented by these CPEs. One give it CPEs
4815 with version numbers as specified above and get a list of open
4816 security issues out.&lt;/p&gt;
4817
4818 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4819 information need to be high. For that to happen, I believe as many as
4820 possible need to use and contribute to the NVD database. I notice
4821 RHEL is providing
4822 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4823 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4824 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4825
4826 &lt;p&gt;To get an idea about the quality for free software, I spent some
4827 time making it possible to compare the CVE database from Debian with
4828 the CVE database in NVD. The result look fairly good, but there are
4829 some inconsistencies in NVD (same software package having several
4830 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4831 Debian believe are affected by a CVE). Hope to find time to improve
4832 the quality of NVD, but that require being able to get in touch with
4833 someone maintaining it. So far my three emails with questions and
4834 corrections have not seen any reply, but I hope contact can be
4835 established soon.&lt;/p&gt;
4836
4837 &lt;p&gt;An interesting application for CPEs is cross platform package
4838 mapping. It would be useful to know which packages in for example
4839 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4840 this would be trivial if all linux distributions provided CPE entries
4841 for their packages.&lt;/p&gt;
4842 </description>
4843 </item>
4844
4845 <item>
4846 <title>Which module is loaded for a given PCI and USB device?</title>
4847 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4848 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4849 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4850 <description>&lt;p&gt;In the
4851 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4852 package in Debian, there is a script to report useful information
4853 about the running hardware for use when people report missing
4854 information. One part of this script that I find very useful when
4855 debugging hardware problems, is the part mapping loaded kernel module
4856 to the PCI device it claims. It allow me to quickly see if the kernel
4857 module I expect is driving the hardware I am struggling with. To see
4858 the output, make sure discover-data is installed and run
4859 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4860 one of my machines like this:&lt;/p&gt;
4861
4862 &lt;pre&gt;
4863 loaded modules:
4864 10de:03eb i2c_nforce2
4865 10de:03f1 ohci_hcd
4866 10de:03f2 ehci_hcd
4867 10de:03f0 snd_hda_intel
4868 10de:03ec pata_amd
4869 10de:03f6 sata_nv
4870 1022:1103 k8temp
4871 109e:036e bttv
4872 109e:0878 snd_bt87x
4873 11ab:4364 sky2
4874 &lt;/pre&gt;
4875
4876 &lt;p&gt;The code in question look like this, slightly modified for
4877 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4878
4879 &lt;pre&gt;
4880 if [ -d /sys/bus/pci/devices/ ] ; then
4881 echo loaded pci modules:
4882 (
4883 cd /sys/bus/pci/devices/
4884 for address in * ; do
4885 if [ -d &quot;$address/driver/module&quot; ] ; then
4886 module=`cd $address/driver/module ; pwd -P | xargs basename`
4887 if grep -q &quot;^$module &quot; /proc/modules ; then
4888 address=$(echo $address |sed s/0000://)
4889 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4890 echo &quot;$id $module&quot;
4891 fi
4892 fi
4893 done
4894 )
4895 echo
4896 fi
4897 &lt;/pre&gt;
4898
4899 &lt;p&gt;Similar code could be used to extract USB device module
4900 mappings:&lt;/p&gt;
4901
4902 &lt;pre&gt;
4903 if [ -d /sys/bus/usb/devices/ ] ; then
4904 echo loaded usb modules:
4905 (
4906 cd /sys/bus/usb/devices/
4907 for address in * ; do
4908 if [ -d &quot;$address/driver/module&quot; ] ; then
4909 module=`cd $address/driver/module ; pwd -P | xargs basename`
4910 if grep -q &quot;^$module &quot; /proc/modules ; then
4911 address=$(echo $address |sed s/0000://)
4912 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4913 if [ &quot;$id&quot; ] ; then
4914 echo &quot;$id $module&quot;
4915 fi
4916 fi
4917 fi
4918 done
4919 )
4920 echo
4921 fi
4922 &lt;/pre&gt;
4923
4924 &lt;p&gt;This might perhaps be something to include in other tools as
4925 well.&lt;/p&gt;
4926 </description>
4927 </item>
4928
4929 <item>
4930 <title>How to test if a laptop is working with Linux</title>
4931 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4932 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4933 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4934 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4935 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4936 batch of computers will work with Linux. Every year for the last few
4937 years the university have organised shared bid of a few thousand
4938 computers, and this year HP won the bid. Two different desktops and
4939 five different laptops are on the list this year. We in the UNIX
4940 group want to know which one of these computers work well with RHEL
4941 and Ubuntu, the two Linux distributions we currently handle at the
4942 university.&lt;/p&gt;
4943
4944 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4945 perhaps inspire others to test hardware as well. To test, I PXE
4946 install the OS version of choice, and log in as my normal user and run
4947 a few applications and plug in selected pieces of hardware. When
4948 something fail, I make a note about this in the test matrix and move
4949 on. If I have some spare time I try to report the bug to the OS
4950 vendor, but as I only have the machines for a short time, I rarely
4951 have the time to do this for all the problems I find.&lt;/p&gt;
4952
4953 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4954 I perform on a new model.&lt;/p&gt;
4955
4956 &lt;ul&gt;
4957
4958 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4959 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4960 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4961
4962 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4963 installation, X.org is working.&lt;/li&gt;
4964
4965 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4966 package mesa-utils on Ubuntu) and writing down the frames per second
4967 reported by the program.&lt;/li&gt;
4968
4969 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4970 logging in, and if I can hear this the test is successful. If there
4971 are several audio exits on the machine, I try them all and check if
4972 the Gnome/KDE audio mixer can control where to send the sound. I
4973 normally test this by playing
4974 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4975 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4976
4977 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4978 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4979
4980 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4981 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4982
4983 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4984 picture from the v4l device show up.&lt;/li&gt;
4985
4986 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4987 any bluetooth devices are discovered. In my office, I normally see a
4988 few.&lt;/li&gt;
4989
4990 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4991 memory modules lying around, and stick them in and see if Gnome/KDE
4992 notice this.&lt;/li&gt;
4993
4994 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4995 special button work, and if the laptop continue to work after
4996 resume.&lt;/li&gt;
4997
4998 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4999 adjusting background light, switching on/off external video output,
5000 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5001 laptop to laptop, so I just write down which are working and which are
5002 not.&lt;/li&gt;
5003
5004 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5005 acceleration sensors etc. I rarely test these, as I do not know how
5006 to quickly test if they are working or not, so I only document their
5007 existence.&lt;/li&gt;
5008
5009 &lt;/ul&gt;
5010
5011 &lt;p&gt;By now I suspect you are really curious what the test results are
5012 for the HP machines I am testing. I&#39;m not done yet, so I will report
5013 the test results later. For now I can report that HP 8100 Elite work
5014 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5015 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5016 can see, I have most machines left to test. One interesting
5017 observation is that Ubuntu Lucid has almost twice the frame rate than
5018 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5019 </description>
5020 </item>
5021
5022 <item>
5023 <title>Some thoughts on BitCoins</title>
5024 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5025 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5026 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5027 <description>&lt;p&gt;As I continue to explore
5028 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5029 what properties the system have, and how it will be affected by laws
5030 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5031
5032 &lt;p&gt;One interesting thing to note is that since the transactions are
5033 verified using a peer to peer network, all details about a transaction
5034 is known to everyone. This means that if a BitCoin address has been
5035 published like I did with mine in my initial post about BitCoin, it is
5036 possible for everyone to see how many BitCoins have been transfered to
5037 that address. There is even a web service to look at the details for
5038 all transactions. There I can see that my address
5039 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5040 have received 16.06 Bitcoin, the
5041 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5042 address of Simon Phipps have received 181.97 BitCoin and the address
5043 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5044 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5045 every one of you that donated bitcoins to support my activity. The
5046 fact that anyone can see how much money was transfered to a given
5047 address make it more obvious why the BitCoin community recommend to
5048 generate and hand out a new address for each transaction. I&#39;m told
5049 there is no way to track which addresses belong to a given person or
5050 organisation without the person or organisation revealing it
5051 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5052
5053 &lt;p&gt;In Norway, and in most other countries, there are laws and
5054 regulations limiting how much money one can transfer across the border
5055 without declaring it. There are money laundering, tax and accounting
5056 laws and regulations I would expect to apply to the use of BitCoin.
5057 If the Skolelinux foundation
5058 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5059 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5060 normal bank transfers like EFF is doing, how should this be accounted?
5061 Given that it is impossible to know if money can cross the border or
5062 not, should everything or nothing be declared? What exchange rate
5063 should be used when calculating taxes? Would receivers have to pay
5064 income tax if the foundation were to pay Skolelinux contributors in
5065 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5066
5067 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5068 accepted by a lot of users. It must be possible to get easy access to
5069 the currency (as a wage or using currency exchanges), and it must be
5070 easy to spend it. At the moment BitCoin seem fairly easy to get
5071 access to, but there are very few places to spend it. I am not really
5072 a regular user of any of the vendor types currently accepting BitCoin,
5073 so I wonder when my kind of shop would start accepting BitCoins. I
5074 would like to buy electronics, travels and subway tickets, not herbs
5075 and books. :) The currency is young, and this will improve over time
5076 if it become popular, but I suspect regular banks will start to lobby
5077 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5078 will claim it is helping fund terrorism and money laundering (which
5079 probably would be true, as is any currency in existence), but I
5080 believe the problems should be solved elsewhere and not by blaming
5081 currencies.&lt;/p&gt;
5082
5083 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5084 CPU intensive process that depend on a bit of luck as well (as one is
5085 competing against all the other miners currently spending CPU cycles
5086 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5087 BitCoin when this happen. Yesterday I came across the obvious way to
5088 join forces to increase ones changes of getting at least some coins,
5089 by coordinating the work on mining BitCoins across several machines
5090 and people, and sharing the result if one is lucky and get the 50
5091 BitCoins. Check out
5092 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5093 if this sounds interesting. I have not had time to try to set up a
5094 machine to participate there yet, but have seen that running on ones
5095 own for a few days have not yield any BitCoins througth mining
5096 yet.&lt;/p&gt;
5097
5098 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5099 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5100 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5101 it was interesting to read. The arguments presented seem to be
5102 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5103 </description>
5104 </item>
5105
5106 <item>
5107 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5108 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5110 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5111 <description>&lt;p&gt;With this weeks lawless
5112 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5113 attacks&lt;/a&gt; on Wikileak and
5114 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5115 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5116 not be trusted to handle money transactions.
5117 A blog post from
5118 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5119 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5120 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5121 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5122 some help from my friend to get it all running, and he even handed me
5123 some bitcoins to get started. I even donated a few bitcoins to Simon
5124 for helping me remember BitCoin.&lt;/p&gt;
5125
5126 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5127 crypto-currency, decentralised and handled using peer-to-peer
5128 networks. It allows anonymous transactions and prohibits central
5129 control over the transactions, making it impossible for governments
5130 and companies alike to block donations and other transactions. The
5131 source is free software, and while the key dependency wxWidgets 2.9
5132 for the graphical user interface is missing in Debian, the command
5133 line client builds just fine. Hopefully Jonas
5134 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5135 Debian&lt;/a&gt; soon.&lt;/p&gt;
5136
5137 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5138 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5139 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5140 currency &quot;stock&quot; markets where the exchange rate is decided. There
5141 are not many users so far, but the concept seems promising. If you
5142 want to get started and lack a friend with any bitcoins to spare,
5143 you can even get
5144 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5145 bitcoin at the time of writing). Use
5146 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5147 on the current exchange rates.&lt;/p&gt;
5148
5149 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5150 machines. If you want to support my activity, please send Bitcoin
5151 donations to the address
5152 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5153 </description>
5154 </item>
5155
5156 <item>
5157 <title>Why isn&#39;t Debian Edu using VLC?</title>
5158 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5159 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5160 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5161 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5162 presented, and the winner among the multimedia player were VLC.
5163 Personally, I like VLC, and it is my player of choice when I first try
5164 to play a video file or stream. Only if VLC fail will I drag out
5165 gmplayer to see if it can do better. The reason is mostly the failure
5166 model and trust. When VLC fail, it normally pop up a error message
5167 reporting the problem. When mplayer fail, it normally segfault or
5168 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5169
5170 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5171 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5172 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5173 plugin to play web videos seamlessly, and the VLC browser plugin is
5174 not very good. For example, it lack in-line control buttons, so there
5175 is no way for the user to pause the video. Also, when I
5176 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5177 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5178 failed on several video pages where mplayer based plugins worked. If
5179 the browser plugin for VLC was as good as the gecko-mediaplayer
5180 package (which uses mplayer), we would switch.&lt;/P&gt;
5181
5182 &lt;p&gt;While VLC is a good player, its user interface is slightly
5183 annoying. The most annoying feature is its inconsistent use of
5184 keyboard shortcuts. When the player is in full screen mode, its
5185 shortcuts are different from when it is playing the video in a window.
5186 For example, space only work as pause when in full screen mode. I
5187 wish it had consisten shortcuts and that space also would work when in
5188 window mode. Another nice shortcut in gmplayer is [enter] to restart
5189 the current video. It is very nice when playing short videos from the
5190 web and want to restart it when new people arrive to have a look at
5191 what is going on.&lt;/p&gt;
5192 </description>
5193 </item>
5194
5195 <item>
5196 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5197 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5198 <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>
5199 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5200 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5201 upgrade testing of the
5202 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5203 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5204 This seem like a very good idea, so I adjusted by test scripts and
5205 can now present the updated result from today:&lt;/p&gt;
5206
5207 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5208
5209 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5210
5211 &lt;blockquote&gt;&lt;p&gt;
5212 apache2.2-bin
5213 aptdaemon
5214 baobab
5215 binfmt-support
5216 browser-plugin-gnash
5217 cheese-common
5218 cli-common
5219 cups-pk-helper
5220 dmz-cursor-theme
5221 empathy
5222 empathy-common
5223 freedesktop-sound-theme
5224 freeglut3
5225 gconf-defaults-service
5226 gdm-themes
5227 gedit-plugins
5228 geoclue
5229 geoclue-hostip
5230 geoclue-localnet
5231 geoclue-manual
5232 geoclue-yahoo
5233 gnash
5234 gnash-common
5235 gnome
5236 gnome-backgrounds
5237 gnome-cards-data
5238 gnome-codec-install
5239 gnome-core
5240 gnome-desktop-environment
5241 gnome-disk-utility
5242 gnome-screenshot
5243 gnome-search-tool
5244 gnome-session-canberra
5245 gnome-system-log
5246 gnome-themes-extras
5247 gnome-themes-more
5248 gnome-user-share
5249 gstreamer0.10-fluendo-mp3
5250 gstreamer0.10-tools
5251 gtk2-engines
5252 gtk2-engines-pixbuf
5253 gtk2-engines-smooth
5254 hamster-applet
5255 libapache2-mod-dnssd
5256 libapr1
5257 libaprutil1
5258 libaprutil1-dbd-sqlite3
5259 libaprutil1-ldap
5260 libart2.0-cil
5261 libboost-date-time1.42.0
5262 libboost-python1.42.0
5263 libboost-thread1.42.0
5264 libchamplain-0.4-0
5265 libchamplain-gtk-0.4-0
5266 libcheese-gtk18
5267 libclutter-gtk-0.10-0
5268 libcryptui0
5269 libdiscid0
5270 libelf1
5271 libepc-1.0-2
5272 libepc-common
5273 libepc-ui-1.0-2
5274 libfreerdp-plugins-standard
5275 libfreerdp0
5276 libgconf2.0-cil
5277 libgdata-common
5278 libgdata7
5279 libgdu-gtk0
5280 libgee2
5281 libgeoclue0
5282 libgexiv2-0
5283 libgif4
5284 libglade2.0-cil
5285 libglib2.0-cil
5286 libgmime2.4-cil
5287 libgnome-vfs2.0-cil
5288 libgnome2.24-cil
5289 libgnomepanel2.24-cil
5290 libgpod-common
5291 libgpod4
5292 libgtk2.0-cil
5293 libgtkglext1
5294 libgtksourceview2.0-common
5295 libmono-addins-gui0.2-cil
5296 libmono-addins0.2-cil
5297 libmono-cairo2.0-cil
5298 libmono-corlib2.0-cil
5299 libmono-i18n-west2.0-cil
5300 libmono-posix2.0-cil
5301 libmono-security2.0-cil
5302 libmono-sharpzip2.84-cil
5303 libmono-system2.0-cil
5304 libmtp8
5305 libmusicbrainz3-6
5306 libndesk-dbus-glib1.0-cil
5307 libndesk-dbus1.0-cil
5308 libopal3.6.8
5309 libpolkit-gtk-1-0
5310 libpt2.6.7
5311 libpython2.6
5312 librpm1
5313 librpmio1
5314 libsdl1.2debian
5315 libsrtp0
5316 libssh-4
5317 libtelepathy-farsight0
5318 libtelepathy-glib0
5319 libtidy-0.99-0
5320 media-player-info
5321 mesa-utils
5322 mono-2.0-gac
5323 mono-gac
5324 mono-runtime
5325 nautilus-sendto
5326 nautilus-sendto-empathy
5327 p7zip-full
5328 pkg-config
5329 python-aptdaemon
5330 python-aptdaemon-gtk
5331 python-axiom
5332 python-beautifulsoup
5333 python-bugbuddy
5334 python-clientform
5335 python-coherence
5336 python-configobj
5337 python-crypto
5338 python-cupshelpers
5339 python-elementtree
5340 python-epsilon
5341 python-evolution
5342 python-feedparser
5343 python-gdata
5344 python-gdbm
5345 python-gst0.10
5346 python-gtkglext1
5347 python-gtksourceview2
5348 python-httplib2
5349 python-louie
5350 python-mako
5351 python-markupsafe
5352 python-mechanize
5353 python-nevow
5354 python-notify
5355 python-opengl
5356 python-openssl
5357 python-pam
5358 python-pkg-resources
5359 python-pyasn1
5360 python-pysqlite2
5361 python-rdflib
5362 python-serial
5363 python-tagpy
5364 python-twisted-bin
5365 python-twisted-conch
5366 python-twisted-core
5367 python-twisted-web
5368 python-utidylib
5369 python-webkit
5370 python-xdg
5371 python-zope.interface
5372 remmina
5373 remmina-plugin-data
5374 remmina-plugin-rdp
5375 remmina-plugin-vnc
5376 rhythmbox-plugin-cdrecorder
5377 rhythmbox-plugins
5378 rpm-common
5379 rpm2cpio
5380 seahorse-plugins
5381 shotwell
5382 software-center
5383 system-config-printer-udev
5384 telepathy-gabble
5385 telepathy-mission-control-5
5386 telepathy-salut
5387 tomboy
5388 totem
5389 totem-coherence
5390 totem-mozilla
5391 totem-plugins
5392 transmission-common
5393 xdg-user-dirs
5394 xdg-user-dirs-gtk
5395 xserver-xephyr
5396 &lt;/p&gt;&lt;/blockquote&gt;
5397
5398 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5399
5400 &lt;blockquote&gt;&lt;p&gt;
5401 cheese
5402 ekiga
5403 eog
5404 epiphany-extensions
5405 evolution-exchange
5406 fast-user-switch-applet
5407 file-roller
5408 gcalctool
5409 gconf-editor
5410 gdm
5411 gedit
5412 gedit-common
5413 gnome-games
5414 gnome-games-data
5415 gnome-nettool
5416 gnome-system-tools
5417 gnome-themes
5418 gnuchess
5419 gucharmap
5420 guile-1.8-libs
5421 libavahi-ui0
5422 libdmx1
5423 libgalago3
5424 libgtk-vnc-1.0-0
5425 libgtksourceview2.0-0
5426 liblircclient0
5427 libsdl1.2debian-alsa
5428 libspeexdsp1
5429 libsvga1
5430 rhythmbox
5431 seahorse
5432 sound-juicer
5433 system-config-printer
5434 totem-common
5435 transmission-gtk
5436 vinagre
5437 vino
5438 &lt;/p&gt;&lt;/blockquote&gt;
5439
5440 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5441
5442 &lt;blockquote&gt;&lt;p&gt;
5443 gstreamer0.10-gnomevfs
5444 &lt;/p&gt;&lt;/blockquote&gt;
5445
5446 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5447
5448 &lt;blockquote&gt;&lt;p&gt;
5449 [nothing]
5450 &lt;/p&gt;&lt;/blockquote&gt;
5451
5452 &lt;p&gt;This is for KDE:&lt;/p&gt;
5453
5454 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5455
5456 &lt;blockquote&gt;&lt;p&gt;
5457 ksmserver
5458 &lt;/p&gt;&lt;/blockquote&gt;
5459
5460 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5461
5462 &lt;blockquote&gt;&lt;p&gt;
5463 kwin
5464 network-manager-kde
5465 &lt;/p&gt;&lt;/blockquote&gt;
5466
5467 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5468
5469 &lt;blockquote&gt;&lt;p&gt;
5470 arts
5471 dolphin
5472 freespacenotifier
5473 google-gadgets-gst
5474 google-gadgets-xul
5475 kappfinder
5476 kcalc
5477 kcharselect
5478 kde-core
5479 kde-plasma-desktop
5480 kde-standard
5481 kde-window-manager
5482 kdeartwork
5483 kdeartwork-emoticons
5484 kdeartwork-style
5485 kdeartwork-theme-icon
5486 kdebase
5487 kdebase-apps
5488 kdebase-workspace
5489 kdebase-workspace-bin
5490 kdebase-workspace-data
5491 kdeeject
5492 kdelibs
5493 kdeplasma-addons
5494 kdeutils
5495 kdewallpapers
5496 kdf
5497 kfloppy
5498 kgpg
5499 khelpcenter4
5500 kinfocenter
5501 konq-plugins-l10n
5502 konqueror-nsplugins
5503 kscreensaver
5504 kscreensaver-xsavers
5505 ktimer
5506 kwrite
5507 libgle3
5508 libkde4-ruby1.8
5509 libkonq5
5510 libkonq5-templates
5511 libnetpbm10
5512 libplasma-ruby
5513 libplasma-ruby1.8
5514 libqt4-ruby1.8
5515 marble-data
5516 marble-plugins
5517 netpbm
5518 nuvola-icon-theme
5519 plasma-dataengines-workspace
5520 plasma-desktop
5521 plasma-desktopthemes-artwork
5522 plasma-runners-addons
5523 plasma-scriptengine-googlegadgets
5524 plasma-scriptengine-python
5525 plasma-scriptengine-qedje
5526 plasma-scriptengine-ruby
5527 plasma-scriptengine-webkit
5528 plasma-scriptengines
5529 plasma-wallpapers-addons
5530 plasma-widget-folderview
5531 plasma-widget-networkmanagement
5532 ruby
5533 sweeper
5534 update-notifier-kde
5535 xscreensaver-data-extra
5536 xscreensaver-gl
5537 xscreensaver-gl-extra
5538 xscreensaver-screensaver-bsod
5539 &lt;/p&gt;&lt;/blockquote&gt;
5540
5541 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5542
5543 &lt;blockquote&gt;&lt;p&gt;
5544 ark
5545 google-gadgets-common
5546 google-gadgets-qt
5547 htdig
5548 kate
5549 kdebase-bin
5550 kdebase-data
5551 kdepasswd
5552 kfind
5553 klipper
5554 konq-plugins
5555 konqueror
5556 ksysguard
5557 ksysguardd
5558 libarchive1
5559 libcln6
5560 libeet1
5561 libeina-svn-06
5562 libggadget-1.0-0b
5563 libggadget-qt-1.0-0b
5564 libgps19
5565 libkdecorations4
5566 libkephal4
5567 libkonq4
5568 libkonqsidebarplugin4a
5569 libkscreensaver5
5570 libksgrd4
5571 libksignalplotter4
5572 libkunitconversion4
5573 libkwineffects1a
5574 libmarblewidget4
5575 libntrack-qt4-1
5576 libntrack0
5577 libplasma-geolocation-interface4
5578 libplasmaclock4a
5579 libplasmagenericshell4
5580 libprocesscore4a
5581 libprocessui4a
5582 libqalculate5
5583 libqedje0a
5584 libqtruby4shared2
5585 libqzion0a
5586 libruby1.8
5587 libscim8c2a
5588 libsmokekdecore4-3
5589 libsmokekdeui4-3
5590 libsmokekfile3
5591 libsmokekhtml3
5592 libsmokekio3
5593 libsmokeknewstuff2-3
5594 libsmokeknewstuff3-3
5595 libsmokekparts3
5596 libsmokektexteditor3
5597 libsmokekutils3
5598 libsmokenepomuk3
5599 libsmokephonon3
5600 libsmokeplasma3
5601 libsmokeqtcore4-3
5602 libsmokeqtdbus4-3
5603 libsmokeqtgui4-3
5604 libsmokeqtnetwork4-3
5605 libsmokeqtopengl4-3
5606 libsmokeqtscript4-3
5607 libsmokeqtsql4-3
5608 libsmokeqtsvg4-3
5609 libsmokeqttest4-3
5610 libsmokeqtuitools4-3
5611 libsmokeqtwebkit4-3
5612 libsmokeqtxml4-3
5613 libsmokesolid3
5614 libsmokesoprano3
5615 libtaskmanager4a
5616 libtidy-0.99-0
5617 libweather-ion4a
5618 libxklavier16
5619 libxxf86misc1
5620 okteta
5621 oxygencursors
5622 plasma-dataengines-addons
5623 plasma-scriptengine-superkaramba
5624 plasma-widget-lancelot
5625 plasma-widgets-addons
5626 plasma-widgets-workspace
5627 polkit-kde-1
5628 ruby1.8
5629 systemsettings
5630 update-notifier-common
5631 &lt;/p&gt;&lt;/blockquote&gt;
5632
5633 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5634 aptitude a bit more similar, but there are still quite a lott of
5635 differences. I have no idea what packages should be installed after
5636 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5637 </description>
5638 </item>
5639
5640 <item>
5641 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5642 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5643 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5644 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5645 <description>&lt;p&gt;Most of the computers in use by the
5646 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5647 are virtual machines. And they have been Xen machines running on a
5648 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5649 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5650 bit harder that it could have been, because we set up the Xen virtual
5651 machines to get the virtual partitions from LVM, which as far as I
5652 know is not supported by KVM. So to migrate, we had to convert
5653 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5654
5655 &lt;p&gt;I found
5656 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5657 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5658 migration. It uses qemu-img from the qemu package to make the disk
5659 image, parted to partition it, losetup and kpartx to present the disk
5660 image partions as devices, and dd to copy the data. I NFS mounted the
5661 new servers storage area on the old server to do the migration.&lt;/p&gt;
5662
5663 &lt;pre&gt;
5664 #!/bin/sh
5665
5666 # Based on
5667 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5668
5669 set -e
5670 set -x
5671
5672 if [ -z &quot;$1&quot; ] ; then
5673 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5674 exit 1
5675 else
5676 host=&quot;$1&quot;
5677 fi
5678
5679 if [ ! -e /dev/vg_data/$host-disk ] ; then
5680 echo &quot;error: unable to find LVM volume for $host&quot;
5681 exit 1
5682 fi
5683
5684 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5685 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5686 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5687 totalsize=$(( ( $disksize + $swapsize ) ))
5688
5689 img=$host.img
5690 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5691 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5692
5693 parted $img mklabel msdos
5694 parted $img mkpart primary linux-swap 0 $disksize
5695 parted $img mkpart primary ext2 $disksize $totalsize
5696 parted $img set 1 boot on
5697
5698 modprobe dm-mod
5699 losetup /dev/loop0 $img
5700 kpartx -a /dev/loop0
5701
5702 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5703 fsck.ext3 -f /dev/mapper/loop0p1 || true
5704 mkswap /dev/mapper/loop0p2
5705
5706 kpartx -d /dev/loop0
5707 losetup -d /dev/loop0
5708 &lt;/pre&gt;
5709
5710 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5711 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5712
5713 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5714 the new disk image attached, installed grub-pc and linux-image-686 and
5715 set up grub to boot from the disk image. After this, the KVM machines
5716 seem to work just fine.&lt;/p&gt;
5717 </description>
5718 </item>
5719
5720 <item>
5721 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5722 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5723 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5724 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5725 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5726 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5727 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5728 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5729
5730 &lt;p&gt;I still do not know what a correct migration should look like, so I
5731 report any differences between apt and aptitude and hope someone else
5732 can see if anything should be changed.&lt;/p&gt;
5733
5734 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5735
5736 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5737
5738 &lt;blockquote&gt;&lt;p&gt;
5739 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5740 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5741 dmz-cursor-theme empathy empathy-common finger
5742 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5743 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5744 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5745 gnome-cards-data gnome-codec-install gnome-core
5746 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5747 gnome-search-tool gnome-session-canberra gnome-spell
5748 gnome-system-log gnome-themes-extras gnome-themes-more
5749 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5750 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5751 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5752 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5753 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5754 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5755 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5756 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5757 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5758 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5759 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5760 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5761 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5762 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5763 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5764 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5765 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5766 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5767 libmono-security2.0-cil libmono-sharpzip2.84-cil
5768 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5769 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5770 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5771 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5772 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5773 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5774 libxalan2-java libxerces2-java media-player-info mesa-utils
5775 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5776 nautilus-sendto-empathy openoffice.org-writer2latex
5777 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5778 python-aptdaemon python-aptdaemon-gtk python-axiom
5779 python-beautifulsoup python-bugbuddy python-clientform
5780 python-coherence python-configobj python-crypto python-cupshelpers
5781 python-cupsutils python-eggtrayicon python-elementtree
5782 python-epsilon python-evolution python-feedparser python-gdata
5783 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5784 python-gtksourceview2 python-httplib2 python-louie python-mako
5785 python-markupsafe python-mechanize python-nevow python-notify
5786 python-opengl python-openssl python-pam python-pkg-resources
5787 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5788 python-tagpy python-twisted-bin python-twisted-conch
5789 python-twisted-core python-twisted-web python-utidylib python-webkit
5790 python-xdg python-zope.interface remmina remmina-plugin-data
5791 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5792 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5793 software-center svgalibg1 system-config-printer-udev
5794 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5795 totem totem-coherence totem-mozilla totem-plugins
5796 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5797 zip
5798 &lt;/p&gt;&lt;/blockquote&gt;
5799
5800 Installed using apt-get, removed with aptitude
5801
5802 &lt;blockquote&gt;&lt;p&gt;
5803 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5804 epiphany-extensions epiphany-gecko evolution-exchange
5805 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5806 gedit-common gnome-app-install gnome-games gnome-games-data
5807 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5808 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5809 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5810 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5811 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5812 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5813 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5814 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5815 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5816 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5817 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5818 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5819 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5820 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5821 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5822 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5823 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5824 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5825 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5826 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5827 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5828 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5829 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5830 sound-juicer swfdec-gnome system-config-printer totem-common
5831 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5832 &lt;/p&gt;&lt;/blockquote&gt;
5833
5834 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5835
5836 &lt;blockquote&gt;&lt;p&gt;
5837 gstreamer0.10-gnomevfs
5838 &lt;/p&gt;&lt;/blockquote&gt;
5839
5840 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5841
5842 &lt;blockquote&gt;&lt;p&gt;
5843 [nothing]
5844 &lt;/p&gt;&lt;/blockquote&gt;
5845
5846 &lt;p&gt;This is for KDE:&lt;/p&gt;
5847
5848 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5849
5850 &lt;blockquote&gt;&lt;p&gt;
5851 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5852 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5853 ghostscript-x git gnome-audio gnugo granatier gs-common
5854 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5855 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5856 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5857 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5858 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5859 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5860 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5861 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5862 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5863 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5864 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5865 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5866 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5867 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5868 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5869 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5870 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5871 libkrossui4 libmailtools-perl libmime-tools-perl
5872 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5873 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5874 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5875 lirc luatex marble networkstatus noatun-plugins
5876 openoffice.org-writer2latex palapeli palapeli-data parley
5877 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5878 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5879 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5880 ttf-sazanami-gothic
5881 &lt;/p&gt;&lt;/blockquote&gt;
5882
5883 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5884
5885 &lt;blockquote&gt;&lt;p&gt;
5886 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5887 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5888 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5889 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5890 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5891 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5892 kitchensync kiten kjumpingcube klatin klettres klickety klines
5893 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5894 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5895 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5896 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5897 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5898 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5899 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5900 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5901 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5902 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5903 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5904 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5905 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5906 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5907 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5908 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5909 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5910 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5911 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5912 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5913 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5914 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5915 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5916 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5917 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5918 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5919 &lt;/p&gt;&lt;/blockquote&gt;
5920
5921 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5922
5923 &lt;blockquote&gt;&lt;p&gt;
5924 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5925 kdeartwork kdebase kdebase-apps kdebase-workspace
5926 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5927 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5928 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5929 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5930 xscreensaver-screensaver-bsod
5931 &lt;/p&gt;&lt;/blockquote&gt;
5932
5933 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5934
5935 &lt;blockquote&gt;&lt;p&gt;
5936 kdebase-bin konq-plugins konqueror
5937 &lt;/p&gt;&lt;/blockquote&gt;
5938 </description>
5939 </item>
5940
5941 <item>
5942 <title>Gnash buildbot slave and Debian kfreebsd</title>
5943 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5944 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5945 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5946 <description>&lt;p&gt;Answering
5947 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5948 call from the Gnash project&lt;/a&gt; for
5949 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5950 current source, I have set up a virtual KVM machine on the Debian
5951 Edu/Skolelinux virtualization host to test the git source on
5952 Debian/Squeeze. I hope this can help the developers in getting new
5953 releases out more often.&lt;/p&gt;
5954
5955 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5956 I have considered setting up a &lt;a
5957 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5958 machine as well. I have also considered using the kfreebsd
5959 architecture in Debian as a file server in NUUG to get access to the 5
5960 TB zfs volume we currently use to store DV video. Because of this, I
5961 finally got around to do a test installation of Debian/Squeeze with
5962 kfreebsd. Installation went fairly smooth, thought I noticed some
5963 visual glitches in the cdebconf dialogs (black cursor left on the
5964 screen at random locations). Have not gotten very far with the
5965 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5966 fatal problem. Have to spend some more time on it to see if it is
5967 useful as a file server for NUUG. Will try to find time to set up a
5968 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5969 </description>
5970 </item>
5971
5972 <item>
5973 <title>Debian in 3D</title>
5974 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5975 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5976 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5977 <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;
5978
5979 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5980 3D linked in from
5981 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5982 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5983 </description>
5984 </item>
5985
5986 <item>
5987 <title>Software updates 2010-10-24</title>
5988 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5989 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5990 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5991 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5992
5993 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5994 raise money for the project is going well. The lower limit of 10
5995 signers was reached in 24 hours, and so far 13 people have signed it.
5996 More signers and more funding is most welcome, and I am really curious
5997 how far we can get before the time limit of December 24 is reached.
5998 :)&lt;/p&gt;
5999
6000 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6001 about what appear to be a great code coverage tool capable of
6002 generating code coverage stats without any changes to the source code.
6003 It is called
6004 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6005 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6006 It is missing in Debian, but the git source built just fine in Squeeze
6007 after I installed libelf-dev, libdwarf-dev, pkg-config and
6008 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6009 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6010
6011 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6012 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6013 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6014 alpha test release of the Squeeze based Debian Edu /
6015 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6016 release. Give it a try if you need a complete linux solution for your
6017 school, including central infrastructure server, workstations, thin
6018 client servers and diskless workstations. A nice touch added
6019 yesterday is RDP support on the thin client servers, for windows
6020 clients to get a Linux desktop on request.&lt;/p&gt;
6021 </description>
6022 </item>
6023
6024 <item>
6025 <title>Some notes on Flash in Debian and Debian Edu</title>
6026 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6028 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6029 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6030 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6031 second most popular used package that is missing in Debian. The sixth
6032 most popular is flashplayer-mozilla. This is a clear indication that
6033 working flash is important for Debian users. Around 10 percent of the
6034 users submitting data to popcon.debian.org have this package
6035 installed.&lt;/p&gt;
6036
6037 &lt;p&gt;In the report written by Lars Risan in August 2008
6038&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
6039 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6040 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6041 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6042 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6043 web sites require Flash to work, and lacking working Flash support in
6044 the web browser and the problems with installing it was perceived as a
6045 good reason to stay with Windows.&lt;/p&gt;
6046
6047 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6048 said to be the retarded cousin that did not really understand
6049 everything you told him but could work fairly well. This was a
6050 comment regarding the problems Linux have with proprietary formats and
6051 non-standard web pages, and is sad because it exposes a fairly common
6052 understanding of whose fault it is if web pages that only work in for
6053 example Internet Explorer 6 fail to work on Firefox, and funny because
6054 it explain very well how annoying it is for users when Linux
6055 distributions do not work with the documents they receive or the web
6056 pages they want to visit.&lt;/p&gt;
6057
6058 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6059 and Debian Edu to have a well working Flash implementation in the
6060 distribution, to get at least popular sites as Youtube and Google
6061 Video to working out of the box. For Squeeze, Debian have the chance
6062 to include the latest version of Gnash that will make this happen, as
6063 the new release 0.8.8 was published a few weeks ago and is resting in
6064 unstable. The new version work with more sites that version 0.8.7.
6065 The Gnash maintainers have asked for a freeze exception, but the
6066 release team have not had time to reply to it yet. I hope they agree
6067 with me that Flash is important for the Debian desktop users, and thus
6068 accept the new package into Squeeze.&lt;/p&gt;
6069 </description>
6070 </item>
6071
6072 <item>
6073 <title>Circular package dependencies harms apt recovery</title>
6074 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6075 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6076 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6077 <description>&lt;p&gt;I discovered this while doing
6078 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6079 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6080 in Debian still got circular dependencies, and it is often claimed
6081 that apt and aptitude should be able to handle this just fine, but
6082 some times these dependency loops causes apt to fail.&lt;/p&gt;
6083
6084 &lt;p&gt;An example is from todays
6085 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6086 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6087 causes perl-modules to fail to upgrade. The cause is simple. If a
6088 package fail to unpack, then only part of packages with the circular
6089 dependency might end up being unpacked when unpacking aborts, and the
6090 ones already unpacked will fail to configure in the recovery phase
6091 because its dependencies are unavailable.&lt;/p&gt;
6092
6093 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6094
6095 &lt;blockquote&gt;&lt;pre&gt;
6096 dpkg: dependency problems prevent configuration of perl-modules:
6097 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6098 Version of perl on system is 5.10.0-19lenny2.
6099 dpkg: error processing perl-modules (--configure):
6100 dependency problems - leaving unconfigured
6101 &lt;/pre&gt;&lt;/blockquote&gt;
6102
6103 &lt;p&gt;The perl/perl-modules circular dependency is already
6104 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6105 hopefully be solved as soon as possible, but it is not the only one,
6106 and each one of these loops in the dependency tree can cause similar
6107 failures. Of course, they only occur when there are bugs in other
6108 packages causing the unpacking to fail, but it is rather nasty when
6109 the failure of one package causes the problem to become worse because
6110 of dependency loops.&lt;/p&gt;
6111
6112 &lt;p&gt;Thanks to
6113 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6114 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6115 dependencies
6116 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6117 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6118
6119 &lt;p&gt;Todays testing also exposed a bug in
6120 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6121 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6122 apt-get and aptitude, the latter possibly caused by some circular
6123 dependency. Reported both to BTS to try to get someone to look at
6124 it.&lt;/p&gt;
6125 </description>
6126 </item>
6127
6128 <item>
6129 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6130 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6131 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6132 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6133 <description>&lt;p&gt;This is a
6134 &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;
6135 on my
6136 &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
6137 work&lt;/a&gt; on
6138 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6139 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6140
6141 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6142 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6143 and dhcp3-server-ldap in Debian use the LDAP server. The two
6144 implementations are quite different in how they use LDAP.&lt;/p&gt;
6145
6146 To get this information, I started slapd with debugging enabled and
6147 dumped the debug output to a file to get the LDAP searches performed
6148 on a Debian Edu main-server. Here is a summary.
6149
6150 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6151
6152 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6153 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6154 the web.
6155
6156 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6157 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6158 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6159 reverse entries are in two different subtrees in LDAP with a structure
6160 based on the DNS names, as in tjener.intern and
6161 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6162
6163 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6164 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6165 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6166 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6167 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6168 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6169 forward entries, it is looking for attributes named dnsttl, arecord,
6170 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6171 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6172 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6173 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6174 spfrecord and modifytimestamp. For reverse entries it is looking for
6175 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6176 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6177 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6178 ldapsearch commands could look like this:&lt;/p&gt;
6179
6180 &lt;blockquote&gt;&lt;pre&gt;
6181 ldapsearch -h ldap \
6182 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6183 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6184 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6185 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6186 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6187 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6188
6189 ldapsearch -h ldap \
6190 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6191 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6192 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6193 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6194 srvrecord naptrrecord modifytimestamp
6195 &lt;/pre&gt;&lt;/blockquote&gt;
6196
6197 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6198 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6199 example LDAP objects used there. In addition to these objects, the
6200 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6201 also exist.&lt;/p&gt;
6202
6203 &lt;blockquote&gt;&lt;pre&gt;
6204 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6205 objectclass: top
6206 objectclass: dnsdomain
6207 objectclass: domainrelatedobject
6208 dc: tjener
6209 arecord: 10.0.2.2
6210 associateddomain: tjener.intern
6211
6212 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6213 objectclass: top
6214 objectclass: dnsdomain2
6215 objectclass: domainrelatedobject
6216 dc: 2
6217 ptrrecord: tjener.intern
6218 associateddomain: 2.2.0.10.in-addr.arpa
6219 &lt;/pre&gt;&lt;/blockquote&gt;
6220
6221 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6222 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6223 same base as in the tree mode for a object with filter
6224 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6225 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6226 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6227 naptrrecord and modifytimestamp. For reverse entires it also do a
6228 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6229 and the requested attributes are associateddomain, dnsttl and
6230 modifytimestamp. In short, in strict mode the objects with ptrrecord
6231 go away, and the arecord attribute in the forward object is used
6232 instead.&lt;/p&gt;
6233
6234 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6235 like this:&lt;/p&gt;
6236
6237 &lt;blockquote&gt;&lt;pre&gt;
6238 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6239 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6240 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6241 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6242 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6243 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6244
6245 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6246 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6247 &lt;/pre&gt;&lt;/blockquote&gt;
6248
6249 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6250 search for SOA records, which behave similar to the forward and
6251 reverse lookups.&lt;/p&gt;
6252
6253 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6254 specify any objectclass names, and instead look for the attributes it
6255 need to generate a DNS reply. This make it able to work with any
6256 objectclass that provide the needed attributes.&lt;/p&gt;
6257
6258 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6259 dnsdomain2 schemas. The latter is used for reverse entries like
6260 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6261
6262 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6263 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6264 attributes) and domainrelatedobject (for associatedDomain). The use
6265 of structural object classes make it impossible to combine these
6266 classes with the object classes used by DHCP.&lt;/p&gt;
6267
6268 &lt;p&gt;There are other schemas that could be used too, for example the
6269 dnszone structural object class used by Gosa and bind-sdb for the DNS
6270 attributes combined with the domainrelatedobject object class, but in
6271 this case some unused attributes would have to be included as well
6272 (zonename and relativedomainname).&lt;/p&gt;
6273
6274 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6275 mode and not use any of the existing objectclasses (dnsdomain,
6276 dnsdomain2 and dnszone) when one want to combine the DNS information
6277 with DHCP information, and instead create a auxiliary object class
6278 defined something like this (using the attributes defined for
6279 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6280
6281 &lt;blockquote&gt;&lt;pre&gt;
6282 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6283 SUP top
6284 AUXILIARY
6285 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6286 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6287 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6288 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6289 A6Record $ DNAMERecord
6290 ))
6291 &lt;/pre&gt;&lt;/blockquote&gt;
6292
6293 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6294 the domainrelatedobject object class, and allow any entity to include
6295 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6296 developers asking for their view on this schema and if they are
6297 interested in providing such schema with PowerDNS, and I hope my
6298 message will be accepted into their mailing list soon.&lt;/p&gt;
6299
6300 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6301
6302 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6303 the object attributes, and then uses the attributes it want. This
6304 make it harder to figure out exactly what attributes are used, but
6305 thanks to the working example in Debian Edu I can at least get an idea
6306 what is needed without having to read the source code.&lt;/p&gt;
6307
6308 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6309 search filter to use to locate the correct dhcpServer entity is
6310 stored. These are the relevant entries from
6311 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6312
6313 &lt;blockquote&gt;&lt;pre&gt;
6314 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6315 ldap-dhcp-server-cn &quot;dhcp&quot;;
6316 &lt;/pre&gt;&lt;/blockquote&gt;
6317
6318 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6319 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6320 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6321 search result is this entry:&lt;/p&gt;
6322
6323 &lt;blockquote&gt;&lt;pre&gt;
6324 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6325 cn: dhcp
6326 objectClass: top
6327 objectClass: dhcpServer
6328 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6329 &lt;/pre&gt;&lt;/blockquote&gt;
6330
6331 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6332 subtree with DHCP configuration. The DHCP configuration subtree base
6333 is located using a base scope search with base &quot;cn=DHCP
6334 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6335 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6336 The search result is this entry:&lt;/p&gt;
6337
6338 &lt;blockquote&gt;&lt;pre&gt;
6339 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6340 cn: DHCP Config
6341 objectClass: top
6342 objectClass: dhcpService
6343 objectClass: dhcpOptions
6344 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6345 dhcpStatements: ddns-update-style none
6346 dhcpStatements: authoritative
6347 dhcpOption: smtp-server code 69 = array of ip-address
6348 dhcpOption: www-server code 72 = array of ip-address
6349 dhcpOption: wpad-url code 252 = text
6350 &lt;/pre&gt;&lt;/blockquote&gt;
6351
6352 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6353 all the DHCP configuration is loaded, it is ready to receive requests.
6354 The subtree in Debian Edu contain objects with object classes
6355 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6356 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6357 and information about netmasks, dynamic range etc. Leaving out the
6358 details here because it is not relevant for the focus of my
6359 investigation, which is to see if it is possible to merge dns and dhcp
6360 related computer objects.&lt;/p&gt;
6361
6362 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6363 of the client (00:00:00:00:00:00 in this example), using a subtree
6364 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6365 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6366 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6367 like:&lt;/p&gt;
6368
6369 &lt;blockquote&gt;&lt;pre&gt;
6370 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6371 cn: hostname
6372 objectClass: top
6373 objectClass: dhcpHost
6374 dhcpHWAddress: ethernet 00:00:00:00:00:00
6375 dhcpStatements: fixed-address hostname
6376 &lt;/pre&gt;&lt;/blockquote&gt;
6377
6378 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6379 The object classes need to have fixed names, and the configuration
6380 need to be stored in a fairly specific LDAP structure. On the
6381 positive side, the invidiual dhcpHost entires can be anywhere without
6382 the DN pointed to by the dhcpServer entries. The latter should make
6383 it possible to group all host entries in a subtree next to the
6384 configuration entries, and this subtree can also be shared with the
6385 DNS server if the schema proposed above is combined with the dhcpHost
6386 structural object class.
6387
6388 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6389
6390 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6391 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6392 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6393 allowing DNS objects to be stored anywhere under the base cn specified
6394 in the configuration.&lt;/p&gt;
6395
6396 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6397 regarding which LDAP schemas to use and which LDAP structure to use.
6398 I guess one could implement ones own schema, as long as the
6399 objectclasses and attributes have the names used, but this do not
6400 really help when the DHCP subtree need to have a fairly fixed
6401 structure.&lt;/p&gt;
6402
6403 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6404 this might work for Debian Edu:&lt;/p&gt;
6405
6406 &lt;blockquote&gt;&lt;pre&gt;
6407 ou=services
6408 cn=machine-info (dhcpService) - dhcpServiceDN points here
6409 cn=dhcp (dhcpServer)
6410 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6411 cn=10.0.2.0 (dhcpSubnet)
6412 cn=group1 (dhcpGroup/dhcpOptions)
6413 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6414 cn=192.168.0.0 (dhcpSubnet)
6415 cn=group1 (dhcpGroup/dhcpOptions)
6416 ou=machines - PowerDNS base points here
6417 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6418 &lt;/pre&gt;&lt;/blockquote&gt;
6419
6420 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6421 entries to be in the dhcpGroup subtrees, the entries can be stored
6422 there instead of a common machines subtree, and the PowerDNS base
6423 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6424
6425 &lt;p&gt;The combined object under the machines subtree would look something
6426 like this:&lt;/p&gt;
6427
6428 &lt;blockquote&gt;&lt;pre&gt;
6429 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6430 dc: hostname
6431 objectClass: top
6432 objectClass: dhcpHost
6433 objectclass: domainrelatedobject
6434 objectclass: dnsDomainAux
6435 associateddomain: hostname.intern
6436 arecord: 10.11.12.13
6437 dhcpHWAddress: ethernet 00:00:00:00:00:00
6438 dhcpStatements: fixed-address hostname.intern
6439 &lt;/pre&gt;&lt;/blockquote&gt;
6440
6441 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6442 machine, as long as the required attributes are available in a
6443 auxiliary object class.&lt;/p&gt;
6444 </description>
6445 </item>
6446
6447 <item>
6448 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6449 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6451 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6452 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6453 DHCP services in Debian Edu to use the same LDAP objects for a given
6454 computer, to avoid the possibility of having a inconsistent state for
6455 a computer in LDAP (as in DHCP but no DNS entry or the other way
6456 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6457
6458 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6459 information finally found a solution that seem to work.&lt;/p&gt;
6460
6461 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6462 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6463 we switch powerdns to use its strict LDAP method (ldap-method=strict
6464 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6465 merged into one while making it impossible to transfer the reverse map
6466 to a slave DNS server.&lt;/p&gt;
6467
6468 &lt;p&gt;If we also replace the object class used to get the DNS related
6469 attributes to one allowing these attributes to be combined with the
6470 dhcphost object class, we can merge the DNS and DHCP entries into one.
6471 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6472 proper OIDs, but that is a minor issue), and tested the setup. It
6473 seem to work.&lt;/p&gt;
6474
6475 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6476 for both DNS and DHCP, and even the LTSP configuration I suggested in
6477 an earlier email. The combined LDAP object will look something like
6478 this:&lt;/p&gt;
6479
6480 &lt;blockquote&gt;&lt;pre&gt;
6481 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6482 cn: hostname
6483 objectClass: dhcphost
6484 objectclass: domainrelatedobject
6485 objectclass: dnsdomainaux
6486 associateddomain: hostname.intern
6487 arecord: 10.11.12.13
6488 dhcphwaddress: ethernet 00:00:00:00:00:00
6489 dhcpstatements: fixed-address hostname
6490 ldapconfigsound: Y
6491 &lt;/pre&gt;&lt;/blockquote&gt;
6492
6493 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6494 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6495 before asking DNS to resolve the fixed-adddress. LTSP will use
6496 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6497
6498 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6499 dhcphost in a different location, to allow us to put the objects
6500 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6501 that. If I can&#39;t figure out a way to do that, we can still get rid of
6502 the hosts subtree and move all its content into the DHCP Config tree
6503 (which probably should be renamed to be more related to the new
6504 content. I suspect cn=dnsdhcp,ou=services or something like that
6505 might be a good place to put it.&lt;/p&gt;
6506
6507 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6508 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6509 </description>
6510 </item>
6511
6512 <item>
6513 <title>Idea for storing LTSP configuration in LDAP</title>
6514 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6516 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6517 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6518 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6519 clients, and that this can be used to fetch configuration from LDAP if
6520 Debian Edu choose to store configuration there.&lt;/p&gt;
6521
6522 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6523 to get configuration from LDAP. The idea is to look up the MAC
6524 address of the client in LDAP, and look for attributes on the form
6525 ltspconfigsetting=value, and use this to export SETTING=value to the
6526 LTSP clients.&lt;/p&gt;
6527
6528 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6529 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6530 allowing us to store all information about a computer in one place.&lt;/p&gt;
6531
6532 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6533 this approach. A real LDAP schema for the ltspClientAux objectclass
6534 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6535
6536 &lt;blockquote&gt;&lt;pre&gt;
6537 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6538 #
6539 # Fetch LTSP client settings from LDAP based on MAC address
6540 #
6541 # Uses ethernet address as stored in the dhcpHost objectclass using
6542 # the dhcpHWAddress attribute or ethernet address stored in the
6543 # ieee802Device objectclass with the macAddress attribute.
6544 #
6545 # This module is written to be schema agnostic, and only depend on the
6546 # existence of attribute names.
6547 #
6548 # The LTSP configuration variables are saved directly using a
6549 # ltspConfig prefix and uppercasing the rest of the attribute name.
6550 # To set the SERVER variable, set the ltspConfigServer attribute.
6551 #
6552 # Some LDAP schema should be created with all the relevant
6553 # configuration settings. Something like this should work:
6554 #
6555 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6556 # SUP top
6557 # AUXILIARY
6558 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6559
6560 LDAPSERVER=$(debian-edu-ldapserver)
6561 if [ &quot;$LDAPSERVER&quot; ] ; then
6562 LDAPBASE=$(debian-edu-ldapserver -b)
6563 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6564 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6565 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6566 grep &#39;^ltspConfig&#39; | while read attr value ; do
6567 # Remove prefix and convert to upper case
6568 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6569 # bass value on to clients
6570 eval &quot;$attr=$value; export $attr&quot;
6571 done
6572 done
6573 fi
6574 &lt;/pre&gt;&lt;/blockquote&gt;
6575
6576 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6577 the while block might end up in a subshell causing the variables set
6578 there to not show up in ltsp-config, but if that is the case I am sure
6579 the code can be restructured to make sure the variables are passed on.
6580 I expect that can be solved with some testing. :)&lt;/p&gt;
6581
6582 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6583 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6584
6585 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6586 configuration in LDAP that was created around year 2000 by
6587 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6588 Xperience, Inc., 2000&lt;/a&gt;. I found its
6589 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6590 personal home page over at redhat.com.&lt;/p&gt;
6591 </description>
6592 </item>
6593
6594 <item>
6595 <title>jXplorer, a very nice LDAP GUI</title>
6596 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6597 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6598 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6599 <description>&lt;p&gt;Since
6600 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6601 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6602 LDAP GUI that is even better than luma. The java application
6603 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6604 moving LDAP objects and subtrees using drag-and-drop, and can
6605 authenticate using Kerberos. I have only tested the Kerberos
6606 authentication, but do not have a LDAP setup allowing me to rewrite
6607 LDAP with my test user yet. It is
6608 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6609 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6610 have with it is how it handle errors. If something go wrong, its
6611 non-intuitive behaviour require me to go through some query work list
6612 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6613 </description>
6614 </item>
6615
6616 <item>
6617 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6618 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6619 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6620 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6621 <description>&lt;p&gt;Here is a short update on my &lt;a
6622 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6623 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6624 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6625 not reporting the status for KDE, because the upgrade crashes when
6626 aptitude try because of missing conflicts
6627 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6628 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6629
6630 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6631 complete list of the installed packages. Based on this I see these
6632 differences when I did a test run today. As usual, I do not really
6633 know what the correct set of packages would be, but thought it best to
6634 publish the difference.&lt;/p&gt;
6635
6636 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6637
6638 &lt;blockquote&gt;&lt;p&gt;
6639 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6640 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6641 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6642 libgtksourceview-common libpt-1.10.10-plugins-alsa
6643 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6644 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6645 python-4suite-xml python-eggtrayicon python-gtkhtml2
6646 python-gtkmozembed svgalibg1 xserver-xephyr zip
6647 &lt;/p&gt;&lt;/blockquote&gt;
6648
6649 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6650
6651 &lt;blockquote&gt;&lt;p&gt;
6652 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6653 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6654 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6655 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6656 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6657 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6658 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6659 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6660 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6661 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6662 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6663 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6664 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6665 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6666 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6667 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6668 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6669 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6670 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6671 mysql-common swfdec-gnome totem-gstreamer wodim
6672 &lt;/p&gt;&lt;/blockquote&gt;
6673
6674 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6675
6676 &lt;blockquote&gt;&lt;p&gt;
6677 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6678 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6679 xserver-xorg-input-all xserver-xorg-input-evdev
6680 xserver-xorg-input-kbd xserver-xorg-input-mouse
6681 xserver-xorg-input-synaptics xserver-xorg-video-all
6682 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6683 xserver-xorg-video-chips xserver-xorg-video-cirrus
6684 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6685 xserver-xorg-video-glint xserver-xorg-video-i128
6686 xserver-xorg-video-i740 xserver-xorg-video-mach64
6687 xserver-xorg-video-mga xserver-xorg-video-neomagic
6688 xserver-xorg-video-nouveau xserver-xorg-video-nv
6689 xserver-xorg-video-r128 xserver-xorg-video-radeon
6690 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6691 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6692 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6693 xserver-xorg-video-sis xserver-xorg-video-sisusb
6694 xserver-xorg-video-tdfx xserver-xorg-video-tga
6695 xserver-xorg-video-trident xserver-xorg-video-tseng
6696 xserver-xorg-video-vesa xserver-xorg-video-vmware
6697 xserver-xorg-video-voodoo
6698 &lt;/p&gt;&lt;/blockquote&gt;
6699
6700 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6701
6702 &lt;blockquote&gt;&lt;p&gt;
6703 deskbar-applet xserver-xorg xserver-xorg-core
6704 xserver-xorg-input-wacom xserver-xorg-video-intel
6705 xserver-xorg-video-openchrome
6706 &lt;/p&gt;&lt;/blockquote&gt;
6707
6708 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6709 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6710 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6711 No idea when it hits Squeeze, but when it does I hope it will reduce
6712 the difference somewhat.
6713 </description>
6714 </item>
6715
6716 <item>
6717 <title>LUMA, a very nice LDAP GUI</title>
6718 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6719 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6720 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6721 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6722 directory in Debian Edu, and in the process I started to miss a GUI
6723 tool to browse the LDAP tree. The only one I was able to find in
6724 Debian/Squeeze and Lenny is
6725 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6726 be a great tool to get a overview of the current LDAP directory
6727 populated by default in Skolelinux. Thanks to it, I have been able to
6728 find empty and obsolete subtrees, misplaced objects and duplicate
6729 objects. It will be installed by default in Debian/Squeeze. If you
6730 are working with LDAP, give it a go. :)&lt;/p&gt;
6731
6732 &lt;p&gt;I did notice one problem with it I have not had time to report to
6733 the BTS yet. There is no .desktop file in the package, so the tool do
6734 not show up in the Gnome and KDE menus, but only deep down in in the
6735 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6736 released.&lt;/p&gt;
6737
6738 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6739 like to move objects and remove subtrees directly in the GUI, but have
6740 not found a way to do that with LUMA yet. So in the mean time, I use
6741 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6742
6743 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6744 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6745
6746 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6747 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6748 useful GUI alternative. It seem like a good tool, but is unmaintained
6749 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6750 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6751 </description>
6752 </item>
6753
6754 <item>
6755 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6756 <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>
6757 <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>
6758 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6759 <description>&lt;p&gt;A while back, I
6760 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6761 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6762 for storing DNS and DHCP information in LDAP to combine the two sets
6763 of information into one LDAP object representing a computer.&lt;/p&gt;
6764
6765 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6766 the dhcpHost object class auxiliary, to allow it to be combined with
6767 the dNSDomain object class, and thus forming one object for one
6768 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6769
6770 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6771 without also changing the assigned number for the object class, and I
6772 do not know enough about LDAP schema design to do that properly for
6773 Debian Edu.&lt;/p&gt;
6774
6775 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6776 the
6777 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6778 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6779 available today from IETF.&lt;/p&gt;
6780
6781 &lt;pre&gt;
6782 --- dhcp.schema (revision 65192)
6783 +++ dhcp.schema (working copy)
6784 @@ -376,7 +376,7 @@
6785 objectclass ( 2.16.840.1.113719.1.203.6.6
6786 NAME &#39;dhcpHost&#39;
6787 DESC &#39;This represents information about a particular client&#39;
6788 - SUP top
6789 + SUP top AUXILIARY
6790 MUST cn
6791 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6792 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6793 &lt;/pre&gt;
6794
6795 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6796 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6797 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6798
6799 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6800 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6801 </description>
6802 </item>
6803
6804 <item>
6805 <title>Calling tasksel like the installer, while still getting useful output</title>
6806 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6807 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6808 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6809 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6810 installs packages during the normal debian-installer run. Until now,
6811 I have ended up letting tasksel do the work, with the annoying problem
6812 of not getting any feedback at all when something fails (like a
6813 conffile question from dpkg or a download that fails), using code like
6814 this:
6815
6816 &lt;blockquote&gt;&lt;pre&gt;
6817 export DEBIAN_FRONTEND=noninteractive
6818 tasksel --new-install
6819 &lt;/pre&gt;&lt;/blockquote&gt;
6820
6821 This would invoke tasksel, let its automatic task selection pick the
6822 tasks to install, and continue to install the requested tasks without
6823 any output what so ever.
6824
6825 Recently I revisited this problem while working on the automatic
6826 package upgrade testing, because tasksel would some times hang without
6827 any useful feedback, and I want to see what is going on when it
6828 happen. Then it occured to me, I can parse the output from tasksel
6829 when asked to run in test mode, and use that aptitude command line
6830 printed by tasksel then to simulate the tasksel run. I ended up using
6831 code like this:
6832
6833 &lt;blockquote&gt;&lt;pre&gt;
6834 export DEBIAN_FRONTEND=noninteractive
6835 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6836 $cmd
6837 &lt;/pre&gt;&lt;/blockquote&gt;
6838
6839 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6840 --without-recommends -o APT::Install-Recommends=no -y install
6841 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6842 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6843 laptop task and all packages with priority standard , required and
6844 important, just like tasksel would have done it during
6845 installation.&lt;/p&gt;
6846
6847 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6848 install packages without using debconf-apt-progress, for use cases
6849 like this.&lt;/p&gt;
6850 </description>
6851 </item>
6852
6853 <item>
6854 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6855 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6856 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6857 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6858 <description>&lt;p&gt;My
6859 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6860 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6861 finally made the upgrade logs available from
6862 &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;.
6863 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6864 apt and aptitude, and found their differences interesting. This time
6865 I will only focus on their removal plans.&lt;/p&gt;
6866
6867 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6868 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6869 surprising part is that it want to remove xorg and all
6870 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6871 sure why. When asking aptitude to do the same, it want to remove 129
6872 packages, but most of them are library packages I suspect are no
6873 longer needed. Both of them want to remove bluetooth packages, which
6874 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6875
6876 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6877 which seem like a bad idea and xorg the same way as with Gnome. Asking
6878 aptitude for the same, it wants to remove 192 packages, none which are
6879 too surprising.&lt;/p&gt;
6880
6881 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6882 and avoided, and perhaps others as well. Here are the complete list
6883 of planned removals. The complete logs is available from the URL
6884 above. Note if you want to repeat these tests, that the upgrade test
6885 for kde+apt-get hung in the tasksel setup because of dpkg asking
6886 conffile questions. No idea why. I worked around it by using
6887 &#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
6888 continue.&lt;/p&gt;
6889
6890 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6891 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6892 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6893 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6894 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6895 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6896 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6897 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6898 xserver-xorg-input-kbd xserver-xorg-input-mouse
6899 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6900 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6901 xserver-xorg-video-ati xserver-xorg-video-chips
6902 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6903 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6904 xserver-xorg-video-glint xserver-xorg-video-i128
6905 xserver-xorg-video-i740 xserver-xorg-video-imstt
6906 xserver-xorg-video-intel xserver-xorg-video-mach64
6907 xserver-xorg-video-mga xserver-xorg-video-neomagic
6908 xserver-xorg-video-nsc xserver-xorg-video-nv
6909 xserver-xorg-video-openchrome xserver-xorg-video-r128
6910 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6911 xserver-xorg-video-rendition xserver-xorg-video-s3
6912 xserver-xorg-video-s3virge xserver-xorg-video-savage
6913 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6914 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6915 xserver-xorg-video-tga xserver-xorg-video-trident
6916 xserver-xorg-video-tseng xserver-xorg-video-v4l
6917 xserver-xorg-video-vesa xserver-xorg-video-vga
6918 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6919 xulrunner-1.9-gnome-support&lt;/p&gt;
6920
6921 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6922
6923 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6924 djvulibre-desktop finger gnome-app-install gnome-mount
6925 gnome-network-admin gnome-spell gnome-vfs-obexftp
6926 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6927 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6928 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6929 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6930 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6931 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6932 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6933 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6934 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6935 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6936 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6937 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6938 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6939 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6940 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6941 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6942 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6943 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6944 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6945 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6946 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6947 openoffice.org-writer2latex openssl-blacklist p7zip
6948 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6949 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6950 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6951 swfdec-mozilla totem-gstreamer update-manager wodim
6952 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6953 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6954 zip&lt;/p&gt;
6955
6956 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6957
6958 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6959 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6960 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6961 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6962 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6963 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6964 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6965 xserver-xorg-input-kbd xserver-xorg-input-mouse
6966 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6967 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6968 xserver-xorg-video-ati xserver-xorg-video-chips
6969 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6970 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6971 xserver-xorg-video-glint xserver-xorg-video-i128
6972 xserver-xorg-video-i740 xserver-xorg-video-imstt
6973 xserver-xorg-video-intel xserver-xorg-video-mach64
6974 xserver-xorg-video-mga xserver-xorg-video-neomagic
6975 xserver-xorg-video-nsc xserver-xorg-video-nv
6976 xserver-xorg-video-openchrome xserver-xorg-video-r128
6977 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6978 xserver-xorg-video-rendition xserver-xorg-video-s3
6979 xserver-xorg-video-s3virge xserver-xorg-video-savage
6980 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6981 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6982 xserver-xorg-video-tga xserver-xorg-video-trident
6983 xserver-xorg-video-tseng xserver-xorg-video-v4l
6984 xserver-xorg-video-vesa xserver-xorg-video-vga
6985 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6986
6987 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6988 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6989 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6990 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6991 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6992 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6993 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6994 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6995 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6996 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6997 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6998 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6999 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7000 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7001 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7002 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7003 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7004 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7005 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7006 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7007 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7008 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7009 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7010 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7011 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7012 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7013 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7014 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7015 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7016 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7017 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7018 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7019 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7020 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7021 texlive-common texlive-doc-base texlive-fonts-recommended
7022 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7023 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7024 xulrunner-1.9&lt;/p&gt;
7025
7026 </description>
7027 </item>
7028
7029 <item>
7030 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7031 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7032 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7033 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7034 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7035 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7036 have been discovered and reported in the process
7037 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7038 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7039 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7040 kdebase-workspace-data), and to get a more regular testing going on, I
7041 am working on a script to automate the test.&lt;/p&gt;
7042
7043 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7044 Gnome or KDE desktop installation inside the chroot before upgrading
7045 it. To ensure no services are started in the chroot, a policy-rc.d
7046 script is inserted. To make sure tasksel believe it is to install a
7047 desktop on a laptop, the tasksel tests are replaced in the chroot
7048 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7049
7050 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7051 currently always fail because udev refuses to upgrade with the kernel
7052 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7053 is created. The bug report
7054 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7055 this problem do not trigger in a chroot, but I touch the file anyway
7056 to make sure the upgrade go well. Testing on virtual and real
7057 hardware have failed me because of udev so far, and creating this file
7058 do the trick in such settings anyway. This is a
7059 &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
7060 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7061 maintainer because he lack the resources to rewrite udev to keep
7062 working with old kernels or something like that. I really wish the
7063 udev upstream would keep udev backwards compatible, to avoid such
7064 upgrade problem, but given that they fail to do so, I guess
7065 documenting the way out of this mess is the best option we got for
7066 Debian Squeeze.&lt;/p&gt;
7067
7068 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7069 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7070 trick:&lt;/p&gt;
7071
7072 &lt;blockquote&gt;&lt;pre&gt;
7073 #!/bin/sh
7074 set -ex
7075
7076 if [ &quot;$1&quot; ] ; then
7077 desktop=$1
7078 else
7079 desktop=gnome
7080 fi
7081
7082 from=lenny
7083 to=squeeze
7084
7085 exec &amp;lt; /dev/null
7086 unset LANG
7087 mirror=http://ftp.skolelinux.org/debian
7088 tmpdir=chroot-$from-upgrade-$to-$desktop
7089 fuser -mv .
7090 debootstrap $from $tmpdir $mirror
7091 chroot $tmpdir aptitude update
7092 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7093 #!/bin/sh
7094 exit 101
7095 EOF
7096 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7097 exit_cleanup() {
7098 umount $tmpdir/proc
7099 }
7100 mount -t proc proc $tmpdir/proc
7101 # Make sure proc is unmounted also on failure
7102 trap exit_cleanup EXIT INT
7103
7104 chroot $tmpdir aptitude -y install debconf-utils
7105
7106 # Make sure tasksel autoselection trigger. It need the test scripts
7107 # to return the correct answers.
7108 echo tasksel tasksel/desktop multiselect $desktop | \
7109 chroot $tmpdir debconf-set-selections
7110
7111 # Include the desktop and laptop task
7112 for test in desktop laptop ; do
7113 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7114 #!/bin/sh
7115 exit 2
7116 EOF
7117 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7118 done
7119
7120 DEBIAN_FRONTEND=noninteractive
7121 DEBIAN_PRIORITY=critical
7122 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7123 chroot $tmpdir tasksel --new-install
7124
7125 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7126 chroot $tmpdir aptitude update
7127 touch $tmpdir/etc/udev/kernel-upgrade
7128 chroot $tmpdir aptitude -y dist-upgrade
7129 fuser -mv
7130 &lt;/pre&gt;&lt;/blockquote&gt;
7131
7132 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7133 with aptitude, but I have not had time to look at how they behave
7134 differently so far. I hope to get a cron job running to do the test
7135 regularly and post the result on the web. The Gnome upgrade currently
7136 work, while the KDE upgrade fail because of the bug in
7137 kdebase-workspace-data&lt;/p&gt;
7138
7139 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7140 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7141 post, so I will refrain from trying. I can report that for Gnome,
7142 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7143 remove and 1 not upgraded and 1024MB need to be downloaded while for
7144 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7145 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7146
7147 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7148 is able to migrate to dependency based boot sequencing and parallel
7149 booting without a hitch. Was unsure if there were still bugs with
7150 packages failing to clean up their obsolete init.d script during
7151 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7152 packages.&lt;/p&gt;
7153 </description>
7154 </item>
7155
7156 <item>
7157 <title>Upstart or sysvinit - as init.d scripts see it</title>
7158 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7159 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7160 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7161 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7162 scripts to migrate (some of) their operations to upstart job while
7163 keeping the init.d for hurd and kfreebsd. The packages with such
7164 needs will need a way to get their init.d scripts to behave
7165 differently when used with sysvinit and with upstart. Because of
7166 this, I had a look at the environment variables set when a init.d
7167 script is running under upstart, and when it is not.&lt;/p&gt;
7168
7169 &lt;p&gt;With upstart, I notice these environment variables are set when a
7170 script is started from rcS.d/ (ignoring some irrelevant ones like
7171 COLUMNS):&lt;/p&gt;
7172
7173 &lt;blockquote&gt;&lt;pre&gt;
7174 DEFAULT_RUNLEVEL=2
7175 previous=N
7176 PREVLEVEL=
7177 RUNLEVEL=
7178 runlevel=S
7179 UPSTART_EVENTS=startup
7180 UPSTART_INSTANCE=
7181 UPSTART_JOB=rc-sysinit
7182 &lt;/pre&gt;&lt;/blockquote&gt;
7183
7184 &lt;p&gt;With sysvinit, these environment variables are set for the same
7185 script.&lt;/p&gt;
7186
7187 &lt;blockquote&gt;&lt;pre&gt;
7188 INIT_VERSION=sysvinit-2.88
7189 previous=N
7190 PREVLEVEL=N
7191 RUNLEVEL=S
7192 runlevel=S
7193 &lt;/pre&gt;&lt;/blockquote&gt;
7194
7195 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7196 sysvinit are not set by upstart. Not sure if it is intentional or not
7197 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7198
7199 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7200 looking for the UPSTART_JOB environment variable seem to be a good
7201 choice.&lt;/p&gt;
7202 </description>
7203 </item>
7204
7205 <item>
7206 <title>A manual for standards wars...</title>
7207 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7209 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7210 <description>&lt;p&gt;Via the
7211 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7212 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7213 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7214 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7215 following the standards wars of today.&lt;/p&gt;
7216 </description>
7217 </item>
7218
7219 <item>
7220 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7221 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7222 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7223 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7224 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7225 to get a list of the machine types in use thanks to the DMI
7226 information extracted from each machine. The script to do so is
7227 included in the sitesummary package, and here is example output from
7228 the Skolelinux build servers:&lt;/p&gt;
7229
7230 &lt;blockquote&gt;&lt;pre&gt;
7231 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7232 vendor count
7233 Dell Computer Corporation 1
7234 PowerEdge 1750 1
7235 IBM 1
7236 eserver xSeries 345 -[8670M1X]- 1
7237 Intel 2
7238 [no-dmi-info] 3
7239 maintainer:~#
7240 &lt;/pre&gt;&lt;/blockquote&gt;
7241
7242 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7243 provided in each machine. Here there are Intel machines without model
7244 information listed with Intel as vendor and no model, and virtual Xen
7245 machines listed as [no-dmi-info]. One can add -l as a command line
7246 option to list the individual machines.&lt;/p&gt;
7247
7248 &lt;p&gt;A larger list is
7249 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7250 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7251 provide the basic sitesummary report publicly. In their report there
7252 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7253 their machines, and as sitesummary is available in both distributions,
7254 it is trivial to get all of them to report to the same central
7255 collector.&lt;/p&gt;
7256 </description>
7257 </item>
7258
7259 <item>
7260 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7261 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7262 <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>
7263 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7264 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7265 start at boot when an NVidia video card is used is handled. The
7266 problem seem to be that the nvidia X.org driver uses a long time to
7267 initialize, and this duration is longer than kdm is configured to
7268 wait.&lt;/p&gt;
7269
7270 &lt;p&gt;I came across two bugs related to this issue,
7271 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7272 against initscripts and passed on to nvidia-glx when it became obvious
7273 that the nvidia drivers were involved, and
7274 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7275 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7276
7277 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7278 problem nvidia video card owners experience and make sure the Debian
7279 distribution work out of the box for these users. The nvidia driver
7280 maintainers expect kdm to be set up to wait longer, while kdm expect
7281 the nvidia driver maintainers to fix the driver to start faster, and
7282 while they wait for each other I guess the users end up switching to a
7283 distribution that work for them. I have no idea what the solution is,
7284 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7285
7286 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7287 </description>
7288 </item>
7289
7290 <item>
7291 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7292 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7293 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7294 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7295 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7296 The feature seem to hold up pretty well, but three fairly serious
7297 issues are known and should be solved:
7298
7299 &lt;p&gt;&lt;ul&gt;
7300
7301 &lt;li&gt;The wicd package seen to
7302 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7303 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7304 parallel booting is enabled. No idea why, but the wicd maintainer
7305 seem to be on the case.&lt;/li&gt;
7306
7307 &lt;li&gt;The nvidia X driver seem to
7308 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7309 triggered more easily when parallel booting is in effect. The
7310 maintainer is on the case.&lt;/li&gt;
7311
7312 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7313 sequencing (the shutdown is broken) when old file-rc users
7314 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7315 sysv-rc. One way to solve it would be for file-rc to create
7316 /etc/init.d/.legacy-bootordering, and another is to try to make
7317 sysv-rc more robust. Will investigate some more and probably upload a
7318 workaround in sysv-rc to help those trying to move from file-rc to
7319 sysv-rc get a working shutdown.&lt;/li&gt;
7320
7321 &lt;/ul&gt;&lt;/p&gt;
7322
7323 &lt;p&gt;All in all not many surprising issues, and all of them seem
7324 solvable before Squeeze is released. In addition to these there are
7325 some packages with bugs in their dependencies and run level settings,
7326 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7327
7328 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7329 the BTS, please usertag the report to get it to show up at
7330 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7331 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7332
7333 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7334 </description>
7335 </item>
7336
7337 <item>
7338 <title>More flexible firmware handling in debian-installer</title>
7339 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7340 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7341 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7342 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7343 found time today to return to the project. Having to spend less time
7344 working dependency based boot in debian, as it is almost complete now,
7345 definitely helped freeing some time.&lt;/p&gt;
7346
7347 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7348 include some firmware packages on the Debian Edu CDs, those needed to
7349 get disk and network controllers working. Without having these
7350 firmware packages available during installation, it is impossible to
7351 install Debian Edu on the given machine, and because our target group
7352 are non-technical people, asking them to provide firmware packages on
7353 an external medium is a support pain. Initially, I expected it to be
7354 enough to include the firmware packages on the CD to get
7355 debian-installer to find and use them. This proved to be wrong.
7356 Next, I hoped it was enough to symlink the relevant firmware packages
7357 to some useful location on the CD (tried /cdrom/ and
7358 /cdrom/firmware/). This also proved to not work, and at this point I
7359 found time to look at the debian-installer code to figure out what was
7360 going to work.&lt;/p&gt;
7361
7362 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7363 look revealed that it would only look for firmware packages outside
7364 the installation media, so the CD was never checked for firmware
7365 packages. It would only check USB sticks, floppies and other
7366 &quot;external&quot; media devices. Today I changed it to also look in the
7367 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7368 solve the problem I ran into with Debian edu. I also changed it to
7369 look in /firmware/, to make sure the installer also find firmware
7370 provided in the initrd when booting the installer via PXE, to allow us
7371 to provide the same feature in the PXE setup included in Debian
7372 Edu.&lt;/p&gt;
7373
7374 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7375 activated without asking if the license is accepted, I extended
7376 hw-detect to look for preinst scripts in the firmware packages, and
7377 run these before activating the firmware during installation. The
7378 license question is asked using debconf in the preinst, so this should
7379 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7380
7381 &lt;p&gt;If you want to discuss the details of these features, please
7382 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7383 </description>
7384 </item>
7385
7386 <item>
7387 <title>Parallellized boot is now the default in Debian/unstable</title>
7388 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7389 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7390 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7391 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7392 Debian/unstable for machines using dependency based boot sequencing.
7393 Apparently the testing of concurrent booting has been wider than
7394 expected, if I am to believe the
7395 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7396 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7397 with the feature this weekend, to give us some time to detect any
7398 remaining problems before Squeeze is frozen. If serious problems are
7399 detected, it is simple to change the default back to sequential boot.
7400 The upload of the new sysvinit package also activate a new upstream
7401 version.&lt;/p&gt;
7402
7403 More information about
7404 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7405 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7406 currently possible to disable parallel booting when one run into
7407 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7408
7409 &lt;blockquote&gt;&lt;pre&gt;
7410 CONCURRENCY=none
7411 &lt;/pre&gt;&lt;/blockquote&gt;
7412
7413 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7414 the BTS, please usertag the report to get it to show up at
7415 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7416 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7417 </description>
7418 </item>
7419
7420 <item>
7421 <title>Sitesummary tip: Listing MAC address of all clients</title>
7422 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7423 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7424 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7425 <description>&lt;p&gt;In the recent Debian Edu versions, the
7426 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7427 system&lt;/a&gt; is used to keep track of the machines in the school
7428 network. Each machine will automatically report its status to the
7429 central server after boot and once per night. The network setup is
7430 also reported, and using this information it is possible to get the
7431 MAC address of all network interfaces in the machines. This is useful
7432 to update the DHCP configuration.&lt;/p&gt;
7433
7434 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7435 ist all MAC addresses of all machines reporting to sitesummary. Run
7436 this on the collector host:&lt;/p&gt;
7437
7438 &lt;blockquote&gt;&lt;pre&gt;
7439 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7440 &lt;/pre&gt;&lt;/blockquote&gt;
7441
7442 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7443 line per machine and with space between the MAC addresses.&lt;/p&gt;
7444
7445 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7446 addresses for hosts, it would be possible to extend this to fetch
7447 machine information from sitesummary and update the DHCP and DNS
7448 tables in LDAP using this information. Such tool is unfortunately not
7449 written yet.&lt;/p&gt;
7450 </description>
7451 </item>
7452
7453 <item>
7454 <title>systemd, an interesting alternative to upstart</title>
7455 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7456 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7457 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7458 <description>&lt;p&gt;The last few days a new boot system called
7459 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7460 has been
7461 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7462
7463 to the free software world. I have not yet had time to play around
7464 with it, but it seem to be a very interesting alternative to
7465 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7466 a good alternative for Debian when we are able to switch to an event
7467 based boot system. Tollef is
7468 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7469 systemd into Debian, and I look forward to seeing how well it work. I
7470 like the fact that systemd handles init.d scripts with dependency
7471 information natively, allowing them to run in parallel where upstart
7472 at the moment do not.&lt;/p&gt;
7473
7474 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7475 platform support. It only work on recent Linux kernels, and also need
7476 some new kernel features enabled to function properly. This means
7477 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7478 system. Not sure how that will be handled if systemd proves to be the
7479 way forward.&lt;/p&gt;
7480
7481 &lt;p&gt;In the mean time, based on the
7482 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7483 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7484 decided to enable full parallel booting as the default in Debian as
7485 soon as possible (probably this weekend or early next week), to see if
7486 there are any remaining serious bugs in the init.d dependencies. A
7487 new version of the sysvinit package implementing this change is
7488 already in experimental. If all go well, Squeeze will be released
7489 with parallel booting enabled by default.&lt;/p&gt;
7490 </description>
7491 </item>
7492
7493 <item>
7494 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7495 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7496 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7497 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7498 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7499 complete, so complete that it is actually possible to run all the
7500 init.d scripts in parallell based on these dependencies. If you want
7501 to test your Squeeze system, make sure
7502 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7503 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7504 /etc/default/rcS:&lt;/p&gt;
7505
7506 &lt;blockquote&gt;&lt;pre&gt;
7507 CONCURRENCY=makefile
7508 &lt;/pre&gt;&lt;/blockquote&gt;
7509
7510 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7511 scripts in parallel using the dependency information stored in
7512 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7513 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7514 to try to start the kdm and gdm scripts as early as possible, and will
7515 start the facilities required by kdm or gdm as early as possible to
7516 make this happen.&lt;/p&gt;
7517
7518 &lt;p&gt;Give it a try, and see if you like the result. If some services
7519 fail to start properly, it is most likely because they have incomplete
7520 init.d script dependencies in their startup script (or some of their
7521 dependent scripts have incomplete dependencies). Report bugs and get
7522 the package maintainers to fix it. :)&lt;/p&gt;
7523
7524 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7525 manage to get the init.d script dependencies complete and correct. I
7526 expect we will get there in Squeeze+1, if we get manage to test and
7527 fix the remaining issues.&lt;/p&gt;
7528
7529 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7530 the BTS, please usertag the report to get it to show up at
7531 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7532 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7533 </description>
7534 </item>
7535
7536 <item>
7537 <title>Debian has switched to dependency based boot sequencing</title>
7538 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7539 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7540 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7541 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7542 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7543 have been migrated to using dependency based boot sequencing. This
7544 conclude work me and others have been doing for the last three days.
7545 It feels great to see this finally part of the default Debian
7546 installation. Now we just need to weed out the last few problems that
7547 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7548
7549 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7550 fixing the more fundamental problem of handing the event based
7551 non-predictable kernel in the early boot.&lt;/p&gt;
7552 </description>
7553 </item>
7554
7555 <item>
7556 <title>Taking over sysvinit development</title>
7557 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7558 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7559 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7560 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7561 the existing sysvinit upstream developer, I decided a few weeks ago to
7562 take over the package and become the new upstream. The number of
7563 patches to track for the Debian package was becoming a burden, and the
7564 lack of synchronization between the distribution made it hard to keep
7565 the package up to date.&lt;/p&gt;
7566
7567 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7568 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7569 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7570 and Fedora), based on the patches currently in use in these
7571 distributions. We Debian maintainers plan to move to this tarball as
7572 the new upstream as soon as we find time to do the merge. Since the
7573 new tarball was created, we agreed with Werner at SuSe to make a new
7574 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7575 development there. The project is registered and currently waiting
7576 for approval by the Savannah administrators, and as soon as it is
7577 approved, we will import the old versions from svn and continue
7578 working on the future release.&lt;/p&gt;
7579
7580 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7581 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7582 </description>
7583 </item>
7584
7585 <item>
7586 <title>Debian boots quicker and quicker</title>
7587 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7588 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7589 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7590 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7591 people involved in the boot system on Debian and Ubuntu, to see if we
7592 could find more ways to speed up the boot system. This was an Ubuntu
7593 funded
7594 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7595 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7596 of boot systems, and ways to handle the increasing number of boot
7597 issues introduced by the Linux kernel becoming more and more
7598 asynchronous and event base. The Ubuntu approach using udev and
7599 upstart might be a good way forward. Time will show.&lt;/p&gt;
7600
7601 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7602 process in Debian. All of these should be applied to get a quick
7603 boot:&lt;/p&gt;
7604
7605 &lt;ul&gt;
7606
7607 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7608
7609 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7610 clock is in UTC.&lt;/li&gt;
7611
7612 &lt;li&gt;Install and activate the insserv package to enable
7613 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7614 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7615
7616 &lt;/ul&gt;
7617
7618 These points are based on the Google summer of code work done by
7619 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7620 Villegas&lt;/a&gt;.
7621
7622 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7623 unstable yesterday. When we tested it, we were able to cut 6 seconds
7624 from the boot sequence. It depend on very correct dependency
7625 declaration in all init.d scripts, so I expect us to find edge cases
7626 where the dependences in some scripts are slightly wrong when we start
7627 using this.&lt;/p&gt;
7628
7629 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7630 introduced by Raphael Geissert today, one that could affect the
7631 startup speed as well. Instead of starting some scripts concurrently
7632 from rcS.d/ and another set of scripts from rc2.d/, it would be
7633 possible to run a of them in the same process. A quick way to test
7634 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7635 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7636 </description>
7637 </item>
7638
7639 <item>
7640 <title>BSAs påstander om piratkopiering møter motstand</title>
7641 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7642 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7643 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7644 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7645 programvareselskapene som Microsoft og Apple, publisert en rapport der
7646 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7647 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7648 dager siden kom
7649 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7650 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7651 dagene. Et spesielt interessant kommentar fra Sverige,
7652 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7653 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7654
7655 &lt;blockquote&gt;
7656 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7657 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7658 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7659 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7660 &lt;/blockquote&gt;
7661
7662 &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
7663 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7664 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7665 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7666 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7667
7668 &lt;p&gt;Fant lenkene via &lt;a
7669 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7670 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7671 </description>
7672 </item>
7673
7674 <item>
7675 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7676 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7677 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7678 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7679 <description>&lt;p&gt;Kom over
7680 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7681 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7682 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7683 jobber til daglig. En rask opptelling forteller meg at vi har 490
7684 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7685 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7686 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7687 </description>
7688 </item>
7689
7690 <item>
7691 <title>Kryptert harddisk - naturligvis</title>
7692 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7693 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7694 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7695 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7696 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7697 når en tar tap av arbeidstid, fortrolige dokumenter,
7698 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7699 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7700 til at jeg har kryptert harddisken på både kontormaskinen og min
7701 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7702 komme på avveie, den første informasjon relatert til jobben min ved
7703 Universitetet i Oslo, og den andre relatert til blant annet
7704 foreningsarbeide. Kryptering av diskene gjør at det er lite
7705 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7706 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7707 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7708 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7709 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7710 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7711 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7712 det er gjort slik jeg gjør det er minimale, og gevinstene er
7713 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7714 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7715
7716 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7717 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7718 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7719 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7720 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7721 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7722 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7723 betydelige.&lt;/p&gt;
7724 </description>
7725 </item>
7726
7727 <item>
7728 <title>Two projects that have improved the quality of free software a lot</title>
7729 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7730 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7731 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7732 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7733 quality of free software, and I wanted to mention both in case someone
7734 do not yet know them.&lt;/p&gt;
7735
7736 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7737 tool to detect and expose errors in the memory handling of programs.
7738 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7739 and it will report any problems on stdout. It is even better if the
7740 program include debug information. With debug information, it is able
7741 to report the source file name and line number where the problem
7742 occurs. It can report things like &#39;reading past memory block in file
7743 X line N, the memory block was allocated in file Y, line M&#39;, and
7744 &#39;using uninitialised value in control logic&#39;. This tool has made it
7745 trivial to investigate reproducible crash bugs in programs, and have
7746 reduced the number of this kind of bugs in free software a lot.
7747
7748 &lt;p&gt;The second one is
7749 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7750 a source code checker. It is able to process the source of a program
7751 and find problems in the logic without running the program. It
7752 started out as the Stanford Checker and became well known when it was
7753 used to find bugs in the Linux kernel. It is now a commercial tool
7754 and the company behind it is running
7755 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7756 free software community, where a lot of free software projects get
7757 their source checked for free. Several thousand defects have been
7758 found and fixed so far. It can find errors like &#39;lock L taken in file
7759 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7760 Y lines O to P can never be executed&#39;. The projects included in the
7761 community service project have managed to get rid of a lot of
7762 reliability problems thanks to Coverity.&lt;/p&gt;
7763
7764 &lt;p&gt;I believe tools like this, that are able to automatically find
7765 errors in the source, are vital to improve the quality of software and
7766 make sure we can get rid of the crashing and failing software we are
7767 surrounded by today.&lt;/p&gt;
7768 </description>
7769 </item>
7770
7771 <item>
7772 <title>No patch is not better than a useless patch</title>
7773 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7774 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7775 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7776 <description>&lt;p&gt;Julien Blache
7777 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7778 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7779 patch allow one to discuss a concrete and proposed solution, and also
7780 prove that the issue at hand is important enough for someone to spent
7781 time on fixing it. No patch do not provide any of these positive
7782 properties.&lt;/p&gt;
7783 </description>
7784 </item>
7785
7786 <item>
7787 <title>Standardize on protocols and formats, not vendors and applications</title>
7788 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7789 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7790 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7791 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7792 very good one to form a long lived computer infrastructure. It is the
7793 simple one, lost by many in todays computer industry: Standardize on
7794 open network protocols and open exchange/storage formats, not applications.
7795 Applications come and go, while protocols and files tend to stay, and
7796 thus one want to make it easy to change application and vendor, while
7797 avoiding conversion costs and locking users to a specific platform or
7798 application.&lt;/p&gt;
7799
7800 &lt;p&gt;This approach make it possible to replace the client applications
7801 independently of the server applications. One can even allow users to
7802 use several different applications as long as they handle the selected
7803 protocol and format. In the normal case, only one client application
7804 is recommended and users only get help if they choose to use this
7805 application, but those that want to deviate from the easy path are not
7806 blocked from doing so.&lt;/p&gt;
7807
7808 &lt;p&gt;It also allow us to replace the server side without forcing the
7809 users to replace their applications, and thus allow us to select the
7810 best server implementation at any moment, when scale and resouce
7811 requirements change.&lt;/p&gt;
7812
7813 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7814 open formats, but I would never recommend standardizing on a single
7815 application that do not use open network protocol or open formats.&lt;/p&gt;
7816 </description>
7817 </item>
7818
7819 <item>
7820 <title>Returning from Skolelinux developer gathering</title>
7821 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7822 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7823 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7824 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7825 Edu/Skolelinux development gathering. I got a bit done tuning the
7826 desktop, and looked into the dynamic service location protocol
7827 implementation avahi. It look like it could be useful for us. Almost
7828 30 people participated, and I believe it was a great environment to
7829 get to know the Skolelinux system. Walter Bender, involved in the
7830 development of the Sugar educational platform, presented his stuff and
7831 also helped me improve my OLPC installation. He also showed me that
7832 his Turtle Art application can be used in standalone mode, and we
7833 agreed that I would help getting it packaged for Debian. As a
7834 standalone application it would be great for Debian Edu. We also
7835 tried to get the video conferencing working with two OLPCs, but that
7836 proved to be too hard for us. The application seem to need more work
7837 before it is ready for me. I look forward to getting home and relax
7838 now. :)&lt;/p&gt;
7839 </description>
7840 </item>
7841
7842 <item>
7843 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7844 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7845 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7846 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7847 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7848 optimal. There is RFC 2307 documenting one way to store NIS maps in
7849 LDAP, and a modified version of this normally called RFC 2307bis, with
7850 some modifications to be compatible with Active Directory. The RFC
7851 specification handle the content of a lot of system databases, but do
7852 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7853
7854 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7855 we would like to store information about users, SMB clients/hosts,
7856 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7857 and LTSP configuration in LDAP. These objects have a lot in common,
7858 but with the current LDAP schemas it is not possible to have one
7859 object per entity. For example, one need to have at least three LDAP
7860 objects for a given computer, one with the SMB related stuff, one with
7861 DNS information and another with DHCP information. The schemas
7862 provided for DNS and DHCP are impossible to combine into one LDAP
7863 object. In addition, it is impossible to implement quick queries for
7864 netgroup membership, because of the way NIS triples are implemented.
7865 It just do not scale. I believe it is time for a few RFC
7866 specifications to cleam up this mess.&lt;/p&gt;
7867
7868 &lt;p&gt;I would like to have one LDAP object representing each computer in
7869 the network, and this object can then keep the SMB (ie host key), DHCP
7870 (mac address/name) and DNS (name/IP address) settings in one place.
7871 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7872
7873 &lt;p&gt;I would also like to have a quick way to map from a user or
7874 computer and to the net group this user or computer is a member.&lt;/p&gt;
7875
7876 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7877 in this regard, and the unix side need to catch up. Time to start a
7878 new IETF work group?&lt;/p&gt;
7879 </description>
7880 </item>
7881
7882 <item>
7883 <title>Endelig er Debian Lenny gitt ut</title>
7884 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7885 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7886 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7887 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7888 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7889 Et langt steg videre for Debian-prosjektet, og en rekke nye
7890 programpakker blir nå tilgjengelig for de av oss som bruker den
7891 stabile utgaven av Debian. Neste steg er nå å få
7892 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7893 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7894 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7895 slippes løs på skolene. Takk til alle debian-utviklerne som har
7896 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7897 bootsekvens tilgjengelig i stabil utgave, vha pakken
7898 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7899 </description>
7900 </item>
7901
7902 <item>
7903 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7904 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7905 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7906 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7907 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7908 Oslo. Most of Saturday was used for the general assemly for the
7909 member organization, but the rest of the weekend I used to tune the
7910 LTSP installation. LTSP now work out of the box on the 10-network.
7911 Acer Aspire One proved to be a very nice thin client, with both
7912 screen, mouse and keybard in a small box. Was working on getting the
7913 diskless workstation setup configured out of the box, but did not
7914 finish it before the weekend was up.&lt;/p&gt;
7915
7916 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7917 the Brazilian group, so that will have to wait for the next
7918 development gathering. Would love to have the Debian Edu installer
7919 automatically detect and configure a multiseat setup when it find one
7920 of these cards.&lt;/p&gt;
7921 </description>
7922 </item>
7923
7924 <item>
7925 <title>The sorry state of multimedia browser plugins in Debian</title>
7926 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7927 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7928 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7929 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7930 plugins available in Debian Lenny, to see which one we should use by
7931 default in Debian Edu. We need an embedded video playing plugin with
7932 control buttons to pause or stop the video, and capable of streaming
7933 all the multimedia content available on the web. The test results and
7934 notes are available on
7935 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7936 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7937 fill this need. My personal video player favorite, VLC, has a really
7938 bad plugin which fail on a lot of the test pages. A lot of the MIME
7939 types I would expect to work with any free software player (like
7940 video/ogg), just do not work. And simple formats like the
7941 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7942 totem and vlc plugins. I hope the situation will improve soon. No
7943 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7944
7945 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7946 be the only one fitting our needs. :/&lt;/p&gt;
7947 </description>
7948 </item>
7949
7950 </channel>
7951 </rss>