]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
f1ae33fa5d66d5c8ea22c8398a262134287dae5e
[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/EE4E02F9 2015-11-03 [expires: 2019-11-14]
27 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
28 uid Petter Reinholdtsen &lt;pere@hungry.com&gt;
29 uid Petter Reinholdtsen &lt;pere@debian.org&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, I&#39;d very much appreciate a signature on
39 my new key, details and instructions in the transition statement. I m
40 happy to reciprocate if you have a similarly signed transition
41 statement to present.&lt;/p&gt;
42 </description>
43 </item>
44
45 <item>
46 <title>The life and death of a laptop battery</title>
47 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
48 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
49 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
50 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
51 But this do not last. The last few laptops gave me a feeling that
52 within a year, the life time is just a fraction of what it used to be,
53 and it slowly become painful to use the laptop without power connected
54 all the time. Because of this, when I got a new Thinkpad X230 laptop
55 about two years ago, I decided to monitor its battery state to have
56 more hard facts when the battery started to fail.&lt;/p&gt;
57
58 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
59
60 &lt;p&gt;First I tried to find a sensible Debian package to record the
61 battery status, assuming that this must be a problem already handled
62 by someone else. I found
63 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
64 which collects statistics from the battery, but it was completely
65 broken. I sent a few suggestions to the maintainer, but decided to
66 write my own collector as a shell script while I waited for feedback
67 from him. Via
68 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
69 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
70 discovered
71 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
72 available in Debian.&lt;/p&gt;
73
74 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
75 battery stats ever since. Now my
76 /var/log/hjemmenett-battery-status.log file contain around 115,000
77 measurements, from the time the battery was working great until now,
78 when it is unable to charge above 7% of original capacity. My
79 collector shell script is quite simple and look like this:&lt;/p&gt;
80
81 &lt;pre&gt;
82 #!/bin/sh
83 # Inspired by
84 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
85 # See also
86 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
87 logfile=/var/log/hjemmenett-battery-status.log
88
89 files=&quot;manufacturer model_name technology serial_number \
90 energy_full energy_full_design energy_now cycle_count status&quot;
91
92 if [ ! -e &quot;$logfile&quot; ] ; then
93 (
94 printf &quot;timestamp,&quot;
95 for f in $files; do
96 printf &quot;%s,&quot; $f
97 done
98 echo
99 ) &gt; &quot;$logfile&quot;
100 fi
101
102 log_battery() {
103 # Print complete message in one echo call, to avoid race condition
104 # when several log processes run in parallel.
105 msg=$(printf &quot;%s,&quot; $(date +%s); \
106 for f in $files; do \
107 printf &quot;%s,&quot; $(cat $f); \
108 done)
109 echo &quot;$msg&quot;
110 }
111
112 cd /sys/class/power_supply
113
114 for bat in BAT*; do
115 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
116 done
117 &lt;/pre&gt;
118
119 &lt;p&gt;The script is called when the power management system detect a
120 change in the power status (power plug in or out), and when going into
121 and out of hibernation and suspend. In addition, it collect a value
122 every 10 minutes. This make it possible for me know when the battery
123 is discharging, charging and how the maximum charge change over time.
124 The code for the Debian package
125 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
126 available on github&lt;/a&gt;.&lt;/p&gt;
127
128 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
129
130 &lt;pre&gt;
131 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
132 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
133 [...]
134 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
135 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
136 &lt;/pre&gt;
137
138 &lt;p&gt;I wrote a small script to create a graph of the charge development
139 over time. This graph depicted above show the slow death of my laptop
140 battery.&lt;/p&gt;
141
142 &lt;p&gt;But why is this happening? Why are my laptop batteries always
143 dying in a year or two, while the batteries of space probes and
144 satellites keep working year after year. If we are to believe
145 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
146 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
147 chance, and the fix is to not charge the Lithium-ion batteries to 100%
148 all the time, but to stay below 90% of full charge most of the time.
149 I&#39;ve been told that the Tesla electric cars
150 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
151 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
152 100% when preparing for a longer trip (not that I would want a car
153 like Tesla where rights to privacy is abandoned, but that is another
154 story), which I guess is the option we should have for laptops on
155 Linux too.&lt;/p&gt;
156
157 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
158 stop charging at 80%, unless requested to charge to 100% once in
159 preparation for a longer trip? I found
160 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
161 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
162 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
163 load).&lt;/p&gt;
164
165 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
166 at the start. I also wonder why the &quot;full capacity&quot; increases some
167 times, and if it is possible to repeat the process to get the battery
168 back to design capacity. And I wonder if the discharge and charge
169 speed change over time, or if this stay the same. I did not yet try
170 to write a tool to calculate the derivative values of the battery
171 level, but suspect some interesting insights might be learned from
172 those.&lt;/p&gt;
173
174 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
175 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
176 packages instead of the tp-smapi-dkms package I had tried to use
177 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
178 and stop. I&#39;ve done so now, but expect my existing battery is toast
179 and need to be replaced. The proposal is unfortunately Thinkpad
180 specific.&lt;/p&gt;
181 </description>
182 </item>
183
184 <item>
185 <title>New laptop - some more clues and ideas based on feedback</title>
186 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
187 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
188 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
189 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
190 need for a new laptop, and provided very useful feedback. I wish to
191 thank every one of these. Several pointed me to the possibility of
192 fixing my X230, and I am already in the process of getting Lenovo to
193 do so thanks to the on site, next day support contract covering the
194 machine. But the battery is almost useless (I expect to replace it
195 with a non-official battery) and I do not expect the machine to live
196 for many more years, so it is time to plan its replacement. If I did
197 not have a support contract, it was suggested to find replacement parts
198 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
199 might present a language barrier as I do not understand French.&lt;/p&gt;
200
201 &lt;p&gt;One tip I got was to use the
202 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
203 compare laptop models. It seem to have more models available than
204 prisjakt.no. Another tip I got from someone I know have similar
205 keyboard preferences was that the HP EliteBook 840 keyboard is not
206 very good, and this matches my experience with earlier EliteBook
207 keyboards I tested. Because of this, I will not consider it any further.
208
209 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
210 newest Thinkpad X model. The keyboard reintroduces mouse buttons
211 (which is missing from the X240), and is working fairly well with
212 Debian Sid/Unstable according to
213 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
214 got on the keyboard quality are not consistent. Some say the keyboard
215 is good, others say it is ok, while others say it is not very good.
216 Those with experience from X41 and and X60 agree that the X250
217 keyboard is not as good as those trusty old laptops, and suggest I
218 keep and fix my X230 instead of upgrading, or get a used X230 to
219 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
220 activity and battery status, which is very convenient on my X230. I&#39;m
221 also told that the CPU fan is running very often, making it a bit
222 noisy. In any case, the X250 do not work out of the box with Debian
223 Stable/Jessie, one of my requirements.&lt;/p&gt;
224
225 &lt;p&gt;I have also gotten a few vendor proposals, one was
226 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
227 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
228 The latter look very attractive to me.&lt;/p&gt;
229
230 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
231 as I keep looking for a replacement.&lt;/p&gt;
232
233 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
234 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
235 different
236 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
237 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
238 </description>
239 </item>
240
241 <item>
242 <title>Time to find a new laptop, as the old one is broken after only two years</title>
243 <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>
244 <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>
245 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
246 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
247 replacement soon. The left 5 cm of the screen on my Thinkpad X230
248 started flickering yesterday, and I suspect the cause is a broken
249 cable, as changing the angle of the screen some times get rid of the
250 flickering.&lt;/p&gt;
251
252 &lt;p&gt;My requirements have not really changed since I bought it, and is
253 still as
254 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
255 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
256 good help from
257 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
258 where I could select at least a few of the requirements (mouse pin,
259 wifi, weight) and go through the rest manually. Three button mouse
260 and a good keyboard is not available as an option, and all the three
261 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
262 G2) lack three mouse buttons). It is also unclear to me how good the
263 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
264 the keyboard, even if the quality and robustness in the X series have
265 deteriorated since X41.&lt;/p&gt;
266
267 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
268 seem sensible to me? Are there better services around to search the
269 set of available laptops for features? Please send me an email if you
270 have suggestions.&lt;/p&gt;
271
272 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
273 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
274 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
275 </description>
276 </item>
277
278 <item>
279 <title>How to stay with sysvinit in Debian Jessie</title>
280 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
281 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
282 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
283 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
284 sysvinit as its boot system by default. But how can one keep using
285 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
286 courtesy of
287 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
288 Schubert&lt;/a&gt; and
289 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
290 McVittie&lt;/a&gt;.
291
292 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
293 keep sysvinit as your boot system, create a file
294 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
295 you upgrade:&lt;/p&gt;
296
297 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
298 Package: systemd-sysv
299 Pin: release o=Debian
300 Pin-Priority: -1
301 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
302
303 &lt;p&gt;This file content will tell apt and aptitude to not consider
304 installing systemd-sysv as part of any installation and upgrade
305 solution when resolving dependencies, and thus tell it to avoid
306 systemd as a default boot system. The end result should be that the
307 upgraded system keep using sysvinit.&lt;/p&gt;
308
309 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
310 get sysvinit installed by default (debootstrap used by
311 debian-installer have no option for this), but one can tell the
312 installer to switch to sysvinit before the first boot. Either by
313 using a kernel argument to the installer, or by adding a line to the
314 preseed file used. First, the kernel command line argument:
315
316 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
317 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
318 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
319
320 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
321
322 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
323 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
324 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
325
326 &lt;p&gt;One can of course also do this after the first boot by installing
327 the sysvinit-core package.&lt;/p&gt;
328
329 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
330 sysvinit boot sequence in Debian have several hardware specific bugs
331 on Linux caused by the fact that it is unpredictable when hardware
332 devices show up during boot. But on the other hand, the new default
333 boot system still have a few rough edges I hope will be fixed before
334 Jessie is released.&lt;/p&gt;
335
336 &lt;p&gt;Update 2014-11-26: Inspired by
337 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
338 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
339 line.&lt;/p&gt;
340 </description>
341 </item>
342
343 <item>
344 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
345 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
346 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
347 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
348 <description>&lt;p&gt;The right to communicate with your friends and family in private,
349 without anyone snooping, is a right every citicen have in a liberal
350 democracy. But this right is under serious attack these days.&lt;/p&gt;
351
352 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
353 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
354 the whisleblower Snowden) more expensive for Internet email,
355 is to deliver all email using SMTP via Tor. Such SMTP option would be
356 a nice addition to the FreedomBox project if we could send email
357 between FreedomBox machines without leaking metadata about the emails
358 to the people peeking on the wire. I
359 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
360 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
361 lot of useful feedback and suggestions. It also became obvious to me
362 that this was not a novel idea, as the same idea was tested and
363 documented by Johannes Berg as early as 2006, and both
364 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
365 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
366 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
367
368 &lt;p&gt;To implement such system one need to set up a Tor hidden service
369 providing the SMTP protocol on port 25, and use email addresses
370 looking like username@hidden-service-name.onion. With such addresses
371 the connections to port 25 on hidden-service-name.onion using Tor will
372 go to the correct SMTP server. To do this, one need to configure the
373 Tor daemon to provide the hidden service and the mail server to accept
374 emails for this .onion domain. To learn more about Exim configuration
375 in Debian and test the design provided by Johannes Berg in his FAQ, I
376 set out yesterday to create a Debian package for making it trivial to
377 set up such SMTP over Tor service based on Debian. Getting it to work
378 were fairly easy, and
379 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
380 source code for the Debian package&lt;/a&gt; is available from github. I
381 plan to move it into Debian if further testing prove this to be a
382 useful approach.&lt;/p&gt;
383
384 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
385 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
386 get rid of exim4). Install tor, clone the git repository mentioned
387 above, build the deb and install it on the machine. Next, run
388 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
389 the instructions to get the service up and running. Restart tor and
390 exim when it is done, and test mail delivery using swaks like
391 this:&lt;/p&gt;
392
393 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
394 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
395 --to fbx@dutlqrrmjhtfa3vp.onion
396 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
397
398 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
399 address with your own address to test your server. :)&lt;/p&gt;
400
401 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
402 easier and more automatic. Especially the tor setup need more work.
403 Also, the package include a tor-smtp tool written in C, but its task
404 should probably be rewritten in some script language to make the deb
405 architecture independent. It would probably also make the code easier
406 to review. The tor-smtp tool currently need to listen on a socket for
407 exim to talk to it and is started using xinetd. It would be better if
408 no daemon and no socket is needed. I suspect it is possible to get
409 exim to run a command line tool for delivery instead of talking to a
410 socket, and hope to figure out how in a future version of this
411 system.&lt;/p&gt;
412
413 &lt;p&gt;Until I wipe my test machine, I can be reached using the
414 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
415 SMTorP. :)&lt;/p&gt;
416 </description>
417 </item>
418
419 <item>
420 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
421 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
423 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
424 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
425 alioth.debian.org, you know the web interface is fairly slow to
426 operate. First you visit one web page, enter the moderation password
427 and get a new page shown with a list of all the messages to moderate
428 and various options for each email address. This take a while for
429 every list you moderate, and you need to do it regularly to do a good
430 job as a list moderator. But there is a quick alternative,
431 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
432 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
433 to moderate in a fraction of a second. Here is a test run on two
434 lists I recently took over:&lt;/p&gt;
435
436 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
437 % time listadmin xiph
438 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
439 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
440
441 real 0m1.709s
442 user 0m0.232s
443 sys 0m0.012s
444 %
445 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
446
447 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
448 there are no message in the moderation queue. Every morning I
449 currently moderate 68 mailman lists, and it normally take around two
450 minutes. When I took over the two pkg-xiph lists above a few days
451 ago, there were 400 emails waiting in the moderator queue. It took me
452 less than 15 minutes to process them all using the listadmin
453 program.&lt;/p&gt;
454
455 &lt;p&gt;If you install
456 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
457 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
458 with content like this, the moderation task is a breeze:&lt;/p&gt;
459
460 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
461 username username@example.org
462 spamlevel 23
463 default discard
464 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
465
466 password secret
467 adminurl https://{domain}/mailman/admindb/{list}
468 mailman-list@lists.example.com
469
470 password hidden
471 other-list@otherserver.example.org
472 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
473
474 &lt;p&gt;There are other options to set as well. Check the manual page to
475 learn the details.&lt;/p&gt;
476
477 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
478 the SSL certificate is self signed or not properly signed by a
479 generally accepted signing authority, you can set a environment
480 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
481
482 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
483 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
484 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
485
486 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
487 can provide an argument to the listadmin script like I do in the
488 initial screen dump (the xiph argument). Using an argument, only
489 lists matching the argument string will be processed. This make it
490 quick to accept messages if you notice the moderation request in your
491 email.&lt;/p&gt;
492
493 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
494 mailing lists, as I simply do not have time to spend on that if the
495 process was any slower. The listadmin program have saved me hours of
496 time I could spend elsewhere over the years. It truly is nice free
497 software.&lt;/p&gt;
498
499 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
500 activities, please send Bitcoin donations to my address
501 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
502
503 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
504 configuration example. Also, I&#39;ve been told that the
505 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
506 sure why.&lt;/p&gt;
507 </description>
508 </item>
509
510 <item>
511 <title>Debian Jessie, PXE and automatic firmware installation</title>
512 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
513 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
514 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
515 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
516 problem that the WiFi card require some firmware to work properly.
517 And it has been a pain to fix this using preseeding in Debian.
518 Normally something more is needed. But thanks to
519 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
520 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
521 to do this using simple preseeding.&lt;/p&gt;
522
523 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
524 firmware for the hardware found in the machine (actually, requested by
525 the kernel modules for the hardware). (It can also install user space
526 programs supporting the hardware detected, but that is not the focus
527 of this story.)&lt;/p&gt;
528
529 &lt;p&gt;To get this working in the default installation, two preeseding
530 values are needed. First, the isenkram-cli package must be installed
531 into the target chroot (aka the hard drive) before tasksel is executed
532 in the pkgsel step of the debian-installer system. This is done by
533 preseeding the base-installer/includes debconf value to include the
534 isenkram-cli package. The package name is next passed to debootstrap
535 for installation. With the isenkram-cli package in place, tasksel
536 will automatically use the isenkram tasks to detect hardware specific
537 packages for the machine being installed and install them, because
538 isenkram-cli contain tasksel tasks.&lt;/p&gt;
539
540 &lt;p&gt;Second, one need to enable the non-free APT repository, because
541 most firmware unfortunately is non-free. This is done by preseeding
542 the apt-mirror-setup step. This is unfortunate, but for a lot of
543 hardware it is the only option in Debian.&lt;/p&gt;
544
545 &lt;p&gt;The end result is two lines needed in your preseeding file to get
546 firmware installed automatically by the installer:&lt;/p&gt;
547
548 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
549 base-installer base-installer/includes string isenkram-cli
550 apt-mirror-setup apt-setup/non-free boolean true
551 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
552
553 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
554 both firmware and user space packages when using this method. It also
555 do not work well, so use version 0.15 or later. Installing both
556 firmware and user space packages might give you a bit more than you
557 want, so I decided to split the tasksel task in two, one for firmware
558 and one for user space programs. The firmware task is enabled by
559 default, while the one for user space programs is not. This split is
560 implemented in the package currently in unstable.&lt;/p&gt;
561
562 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
563 this recipe work for you. :)&lt;/p&gt;
564
565 &lt;p&gt;So, I bet you are wondering, how can this work. First and
566 foremost, it work because tasksel is modular, and driven by whatever
567 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
568 isenkram-cli package place two files for tasksel to find. First there
569 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
570
571 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
572 Task: isenkram-packages
573 Section: hardware
574 Description: Hardware specific packages (autodetected by isenkram)
575 Based on the detected hardware various hardware specific packages are
576 proposed.
577 Test-new-install: show show
578 Relevance: 8
579 Packages: for-current-hardware
580
581 Task: isenkram-firmware
582 Section: hardware
583 Description: Hardware specific firmware packages (autodetected by isenkram)
584 Based on the detected hardware various hardware specific firmware
585 packages are proposed.
586 Test-new-install: mark show
587 Relevance: 8
588 Packages: for-current-hardware-firmware
589 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
590
591 &lt;p&gt;The key parts are Test-new-install which indicate how the task
592 should be handled and the Packages line referencing to a script in
593 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
594 list of packages to install. The for-current-hardware-firmware script
595 look like this to list relevant firmware for the machine:
596
597 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
598 #!/bin/sh
599 #
600 PATH=/usr/sbin:$PATH
601 export PATH
602 isenkram-autoinstall-firmware -l
603 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
604
605 &lt;p&gt;With those two pieces in place, the firmware is installed by
606 tasksel during the normal d-i run. :)&lt;/p&gt;
607
608 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
609 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
610 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
611 install.&lt;/p&gt;
612
613 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
614 pilots in testing this feature, as isenkram is used there now to
615 install firmware, replacing the earlier scripts.&lt;/p&gt;
616 </description>
617 </item>
618
619 <item>
620 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
621 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
622 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
623 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
624 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
625 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
626 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
627 on a screen normally showing the bread types and prizes:&lt;/p&gt;
628
629 &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;
630
631 &lt;p&gt;If it had booted as it was supposed to, I would never had known
632 about this hidden Linux installation. It is interesting what
633 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
634 </description>
635 </item>
636
637 <item>
638 <title>New lsdvd release version 0.17 is ready</title>
639 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
640 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
641 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
642 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
643 got a new set of developers a few weeks ago, after the original
644 developer decided to step down and pass the project to fresh blood.
645 This project is now maintained by Petter Reinholdtsen and Steve
646 Dibb.&lt;/p&gt;
647
648 &lt;p&gt;I just wrapped up
649 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
650 new lsdvd release&lt;/a&gt;, available in git or from
651 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
652 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
653 0.17.&lt;/p&gt;
654
655 &lt;ul&gt;
656
657 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
658 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
659 non-existant, to work around additional copy protection&lt;/li&gt;
660 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
661 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
662 &lt;li&gt;Fix include orders&lt;/li&gt;
663 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
664 &lt;li&gt;Fix the chapter count&lt;/li&gt;
665 &lt;li&gt;Make sure the array size and the array limit used when initialising
666 the palette size is the same.&lt;/li&gt;
667 &lt;li&gt;Fix array printing.&lt;/li&gt;
668 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
669 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
670 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
671 with more GCC compiler warnings.&lt;/li&gt;
672
673 &lt;/ul&gt;
674
675 &lt;p&gt;This change bring together patches for lsdvd in use in various
676 Linux and Unix distributions, as well as patches submitted to the
677 project the last nine years. Please check it out. :)&lt;/p&gt;
678 </description>
679 </item>
680
681 <item>
682 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
683 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
685 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
686 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
687 project&lt;/a&gt; provide a Linux solution for schools, including a
688 powerful desktop with education software, a central server providing
689 web pages, user database, user home directories, central login and PXE
690 boot of both clients without disk and the installation to install Debian
691 Edu on machines with disk (and a few other services perhaps to small
692 to mention here). We in the Debian Edu team are currently working on
693 the Jessie based version, trying to get everything in shape before the
694 freeze, to avoid having to maintain our own package repository in the
695 future. The
696 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
697 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
698 work left. Some fatal problems block testing, breaking the installer,
699 but it is possible to work around these to get anyway. Here is a
700 recipe on how to get the installation limping along.&lt;/p&gt;
701
702 &lt;p&gt;First, download the test ISO via
703 &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;,
704 &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;
705 or rsync (use
706 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
707 The ISO build was broken on Tuesday, so we do not get a new ISO every
708 12 hours or so, but thankfully the ISO we already got we are able to
709 install with some tweaking.&lt;/p&gt;
710
711 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
712 (use Alt-Ctrl-F2), run&lt;/p&gt;
713
714 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
715 nano /usr/bin/edu-eatmydata-install
716 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
717
718 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
719 optimization. Return to the installation, select the profile you want
720 and continue. Without this change, exim4-config will fail to install
721 due to a known bug in eatmydata.&lt;/p&gt;
722
723 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
724 this do not work, figure out what your correct value would be. All my
725 test machines need /dev/sda, so I have no advice if it do not fit
726 your need.&lt;/p&gt;
727
728 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
729 root after the initial boot from hard drive, and install the
730 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
731 or mate. If you want several desktop options, install more than one
732 metapackage. Once this is done, reboot and you should have a working
733 graphical login screen. This workaround should no longer be needed
734 once the education-tasks package version 1.801 enter testing in two
735 days.&lt;/p&gt;
736
737 &lt;p&gt;I believe the ISO build will start working on two days when the new
738 tasksel package enter testing and Steve McIntyre get a chance to
739 update the debian-cd git repository. The eatmydata, grub and desktop
740 issues are already fixed in unstable and testing, and should show up
741 on the ISO as soon as the ISO build start working again. Well the
742 eatmydata optimization is really just disabled. The proper fix
743 require an upload by the eatmydata maintainer applying the patch
744 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
745 The rest have proper fixes in unstable.&lt;/p&gt;
746
747 &lt;p&gt;I hope this get you going with the installation testing, as we are
748 quickly running out of time trying to get our Jessie based
749 installation ready before the distribution freeze in a month.&lt;/p&gt;
750 </description>
751 </item>
752
753 <item>
754 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
755 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
756 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
757 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
758 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
759 to handle my fairly large DVD collection. It is a nice command line
760 tool to get details about a DVD, like title, tracks, track length,
761 etc, in XML, Perl or human readable format. But lsdvd have not seen
762 any new development since 2006 and had a few irritating bugs affecting
763 its use with some DVDs. Upstream seemed to be dead, and in January I
764 sent a small probe asking for a version control repository for the
765 project, without any reply. But I use it regularly and would like to
766 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
767 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
768 the project admin, and after getting a reply from him explaining that
769 he was no longer interested in the project, I asked if I could take
770 over. And yesterday, I became project admin.&lt;/p&gt;
771
772 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
773 maintainer interested in joining forces to maintain the upstream
774 project, and I hope we can get a new release out fairly quickly,
775 collecting the patches spread around on the internet into on place.
776 I&#39;ve added the relevant Debian patches to the freshly created git
777 repository, and expect the Gentoo patches to make it too. If you got
778 a DVD collection and care about command line tools, check out
779 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
780 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
781 list&lt;/a&gt;. :)&lt;/p&gt;
782 </description>
783 </item>
784
785 <item>
786 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
787 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
789 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
790 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
791 a lot quicker. When we install more than 2000 packages in
792 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
793 tasksel in the installer, unpacking the binary packages take forever.
794 A part of the slow I/O issue was discussed in
795 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
796 much file system sync-ing done by dpkg, which is the package
797 responsible for unpacking the binary packages. Other parts (like code
798 executed by postinst scripts) might also sync to disk during
799 installation. All this sync-ing to disk do not really make sense to
800 me. If the machine crash half-way through, I start over, I do not try
801 to salvage the half installed system. So the failure sync-ing is
802 supposed to protect against, hardware or system crash, is not really
803 relevant while the installer is running.&lt;/p&gt;
804
805 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
806 system sync()-ing in a fairly non-intrusive way, without the need to
807 change the code in several packages. The idea is not new, but I have
808 not heard anyone propose the approach using dpkg-divert before. It
809 depend on the small and clever package
810 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
811 uses LD_PRELOAD to replace the system functions for syncing data to
812 disk with functions doing nothing, thus allowing programs to live
813 dangerous while speeding up disk I/O significantly. Instead of
814 modifying the implementation of dpkg, apt and tasksel (which are the
815 packages responsible for selecting, fetching and installing packages),
816 it occurred to me that we could just divert the programs away, replace
817 them with a simple shell wrapper calling
818 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
819 Two days ago I decided to test the idea, and wrapped up a simple
820 implementation for the Debian Edu udeb.&lt;/p&gt;
821
822 &lt;p&gt;The effect was stunning. In my first test it reduced the running
823 time of the pkgsel step (installing tasks) from 64 to less than 44
824 minutes (20 minutes shaved off the installation) on an old Dell
825 Latitude D505 machine. I am not quite sure what the optimised time
826 would have been, as I messed up the testing a bit, causing the debconf
827 priority to get low enough for two questions to pop up during
828 installation. As soon as I saw the questions I moved the installation
829 along, but do not know how long the question were holding up the
830 installation. I did some more measurements using Debian Edu Jessie,
831 and got these results. The time measured is the time stamp in
832 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
833 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
834 yourself. In Debian Edu, the tasksel dialog do not show up, and the
835 timing thus do not depend on how quickly the user handle the tasksel
836 dialog.&lt;/p&gt;
837
838 &lt;p&gt;&lt;table&gt;
839
840 &lt;tr&gt;
841 &lt;th&gt;Machine/setup&lt;/th&gt;
842 &lt;th&gt;Original tasksel&lt;/th&gt;
843 &lt;th&gt;Optimised tasksel&lt;/th&gt;
844 &lt;th&gt;Reduction&lt;/th&gt;
845 &lt;/tr&gt;
846
847 &lt;tr&gt;
848 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
849 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
850 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
851 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
852 &lt;/tr&gt;
853
854 &lt;tr&gt;
855 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
856 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
857 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
858 &lt;td&gt;23 min 40%&lt;/td&gt;
859 &lt;/tr&gt;
860
861 &lt;tr&gt;
862 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
863 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
864 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
865 &lt;td&gt;11 min 50%&lt;/td&gt;
866 &lt;/tr&gt;
867
868 &lt;tr&gt;
869 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
870 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
871 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
872 &lt;td&gt;2 min 33%&lt;/td&gt;
873 &lt;/tr&gt;
874
875 &lt;tr&gt;
876 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
877 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
878 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
879 &lt;td&gt;4 min 21%&lt;/td&gt;
880 &lt;/tr&gt;
881
882 &lt;/table&gt;&lt;/p&gt;
883
884 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
885 time is spent downloading packages. The connection to the Internet
886 was 100Mbit/s during testing, so downloading should not be a
887 significant factor in the measurement. Download typically took a few
888 seconds to a few minutes, depending on the amount of packages being
889 installed.&lt;/p&gt;
890
891 &lt;p&gt;The speedup is implemented by using two hooks in
892 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
893 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
894 finish-install.d hook to remove the divert at the end of the
895 installation. I picked the pre-pkgsel.d hook instead of the
896 post-base-installer.d hook because I test using an ISO without the
897 eatmydata package included, and the post-base-installer.d hook in
898 Debian Edu can only operate on packages included in the ISO. The
899 negative effect of this is that I am unable to activate this
900 optimization for the kernel installation step in d-i. If the code is
901 moved to the post-base-installer.d hook, the speedup would be larger
902 for the entire installation.&lt;/p&gt;
903
904 &lt;p&gt;I&#39;ve implemented this in the
905 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
906 git repository, and plan to provide the optimization as part of the
907 Debian Edu installation. If you want to test this yourself, you can
908 create two files in the installer (or in an udeb). One shell script
909 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
910
911 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
912 #!/bin/sh
913 set -e
914 . /usr/share/debconf/confmodule
915 info() {
916 logger -t my-pkgsel &quot;info: $*&quot;
917 }
918 error() {
919 logger -t my-pkgsel &quot;error: $*&quot;
920 }
921 override_install() {
922 apt-install eatmydata || true
923 if [ -x /target/usr/bin/eatmydata ] ; then
924 for bin in dpkg apt-get aptitude tasksel ; do
925 file=/usr/bin/$bin
926 # Test that the file exist and have not been diverted already.
927 if [ -f /target$file ] ; then
928 info &quot;diverting $file using eatmydata&quot;
929 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
930 &gt; /target$file.edu
931 chmod 755 /target$file.edu
932 in-target dpkg-divert --package debian-edu-config \
933 --rename --quiet --add $file
934 ln -sf ./$bin.edu /target$file
935 else
936 error &quot;unable to divert $file, as it is missing.&quot;
937 fi
938 done
939 else
940 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
941 fi
942 }
943
944 override_install
945 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
946
947 &lt;p&gt;To clean up, another shell script should go into
948 /usr/lib/finish-install.d/ with code like this:
949
950 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
951 #! /bin/sh -e
952 . /usr/share/debconf/confmodule
953 error() {
954 logger -t my-finish-install &quot;error: $@&quot;
955 }
956 remove_install_override() {
957 for bin in dpkg apt-get aptitude tasksel ; do
958 file=/usr/bin/$bin
959 if [ -x /target$file.edu ] ; then
960 rm /target$file
961 in-target dpkg-divert --package debian-edu-config \
962 --rename --quiet --remove $file
963 rm /target$file.edu
964 else
965 error &quot;Missing divert for $file.&quot;
966 fi
967 done
968 sync # Flush file buffers before continuing
969 }
970
971 remove_install_override
972 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
973
974 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
975 edu-eatmydata-install and call it from the pre-pkgsel.d and
976 finish-install.d scripts.&lt;/p&gt;
977
978 &lt;p&gt;By now you might ask if this change should get into the normal
979 Debian installer too? I suspect it should, but am not sure the
980 current debian-installer coordinators find it useful enough. It also
981 depend on the side effects of the change. I&#39;m not aware of any, but I
982 guess we will see if the change is safe after some more testing.
983 Perhaps there is some package in Debian depending on sync() and
984 fsync() having effect? Perhaps it should go into its own udeb, to
985 allow those of us wanting to enable it to do so without affecting
986 everyone.&lt;/p&gt;
987
988 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
989 will break installation of all programs using gnutls because of
990 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
991 eatmydata package in Debian will solve it.&lt;/p&gt;
992
993 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
994 the optimization work again. And I have discovered that the
995 dpkg-divert trick is not really needed and implemented a slightly
996 simpler approach as part of the debian-edu-install package. See
997 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
998
999 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1000 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1001 triggering on i386 made it into testing, and broke this installation
1002 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1003 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1004 </description>
1005 </item>
1006
1007 <item>
1008 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1009 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1010 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1011 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1012 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1013 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1014 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1015 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1016 learn that there is a large set of publicly available key servers to
1017 use when looking for peoples public key. So far I have used
1018 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1019 were misbehaving, but those days are ended. The servers I have used
1020 up until yesterday have been slow and some times unavailable. I hope
1021 those problems are gone now.&lt;/p&gt;
1022
1023 &lt;p&gt;Behind the round robin DNS entry of the
1024 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1025 there is a pool of more than 100 keyservers which are checked every
1026 day to ensure they are well connected and up to date. It must be
1027 better than what I have used so far. :)&lt;/p&gt;
1028
1029 &lt;p&gt;Yesterdays speaker told me that the service is the default
1030 keyserver provided by the default configuration in GnuPG, but this do
1031 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1032
1033 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1034 line:&lt;/p&gt;
1035
1036 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1037 keyserver pool.sks-keyservers.net
1038 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1039
1040 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1041 entries in DNS. Just for fun, I did just that at work, so now every
1042 user of GnuPG at the University of Oslo should find a OpenGPG
1043 keyserver automatically should their need it:&lt;/p&gt;
1044
1045 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1046 % host -t srv _pgpkey-http._tcp.uio.no
1047 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1048 %
1049 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1050
1051 &lt;p&gt;Now if only
1052 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1053 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1054 very happy. It can look up a given key or search for a user ID, but I
1055 normally do not want that, but to find a trust path from my key to
1056 another key. Given a user ID or key ID, I would like to find (and
1057 download) the keys representing a signature path from my key to the
1058 key in question, to be able to get a trust path between the two keys.
1059 This is as far as I can tell not possible today. Perhaps something
1060 for a future version of the protocol?&lt;/p&gt;
1061 </description>
1062 </item>
1063
1064 <item>
1065 <title>From English wiki to translated PDF and epub via Docbook</title>
1066 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1067 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1068 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1069 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1070 project&lt;/a&gt; provide an instruction manual for teachers, system
1071 administrators and other users that contain useful tips for setting up
1072 and maintaining a Debian Edu installation. This text is about how the
1073 text processing of this manual is handled in the project.&lt;/p&gt;
1074
1075 &lt;p&gt;One goal of the project is to provide information in the native
1076 language of its users, and for this we need to handle translations.
1077 But we also want to make sure each language contain the same
1078 information, so for this we need a good way to keep the translations
1079 in sync. And we want it to be easy for our users to improve the
1080 documentation, avoiding the need to learn special formats or tools to
1081 contribute, and the obvious way to do this is to make it possible to
1082 edit the documentation using a web browser. We also want it to be
1083 easy for translators to keep the translation up to date, and give them
1084 help in figuring out what need to be translated. Here is the list of
1085 tools and the process we have found trying to reach all these
1086 goals.&lt;/p&gt;
1087
1088 &lt;p&gt;We maintain the authoritative source of our manual in the
1089 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1090 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1091 front page with references to the different chapters, several pages
1092 for each chapter, and finally one &quot;collection page&quot; gluing all the
1093 chapters together into one large web page (aka
1094 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1095 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1096 processing and translations. Thanks to the fact that the
1097 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1098 wiki.debian.org support exporting pages in
1099 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1100 the list of pages to export using the raw version of the AllInOne
1101 page, loop over each of them to generate a Docbook XML version of the
1102 manual. This process also download images and transform image
1103 references to use the locally downloaded images. The generated
1104 Docbook XML files are slightly broken, so some post-processing is done
1105 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1106 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1107 a handfull of images. The XML file can now be used to generate PDF, HTML
1108 and epub versions of the English manual. This is the basic step of
1109 our process, making PDF (using dblatex), HTML (using xsltproc) and
1110 epub (using dbtoepub) version from Docbook XML, and the resulting files
1111 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1112
1113 &lt;p&gt;But English documentation is not enough for us. We want translated
1114 documentation too, and we want to make it easy for translators to
1115 track the English original. For this we use the
1116 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1117 which allow us to transform the English Docbook XML file into a
1118 translation file (a .pot file), usable with the normal gettext based
1119 translation tools used by those translating free software. The pot
1120 file is used to create and maintain translation files (several .po
1121 files), which the translations update with the native language
1122 translations of all titles, paragraphs and blocks of text in the
1123 original. The next step is combining the original English Docbook XML
1124 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1125 create a translated Docbook XML file (in this case
1126 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1127 translated, if the translation is not complete) Docbook XML file can
1128 then be used like the original to create a PDF, HTML and epub version
1129 of the documentation.&lt;/p&gt;
1130
1131 &lt;p&gt;The translators use different tools to edit the .po files. We
1132 recommend using
1133 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1134 while some use emacs and vi, others can use web based editors like
1135 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1136 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1137 is where the .po file end up, in our git repository. Updated
1138 translations can either be committed directly to git, or submitted as
1139 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1140 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1141
1142 &lt;p&gt;One challenge is images, which both might need to be translated (if
1143 they show translated user applications), and are needed in different
1144 formats when creating PDF and HTML versions (epub is a HTML version in
1145 this regard). For this we transform the original PNG images to the
1146 needed density and format during build, and have a way to provide
1147 translated images by storing translated versions in
1148 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1149 package maintainers know more.&lt;/p&gt;
1150
1151 &lt;p&gt;If you wonder what the result look like, we provide
1152 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1153 of the documentation packages on the web&lt;/a&gt;. See for example the
1154 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1155 PDF version&lt;/a&gt; or the
1156 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1157 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1158 but perhaps it will be done in the future.&lt;/p&gt;
1159
1160 &lt;p&gt;To learn more, check out
1161 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1162 debian-edu-doc package&lt;/a&gt;,
1163 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1164 manual on the wiki&lt;/a&gt; and
1165 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1166 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1167 </description>
1168 </item>
1169
1170 <item>
1171 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1172 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1173 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1174 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1175 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1176 related packages relevant for the computer installed automatically.
1177 So I implemented one, using
1178 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1179 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1180 run tasksel as user root. You should be presented with a new option,
1181 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1182 select it, tasksel will install the packages isenkram claim is fit for
1183 the current hardware, hot pluggable or not.&lt;p&gt;
1184
1185 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1186 description, and the other is the script used to extract the list of
1187 packages to install. The first part is in
1188 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1189 this:&lt;/p&gt;
1190
1191 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1192 Task: isenkram
1193 Section: hardware
1194 Description: Hardware specific packages (autodetected by isenkram)
1195 Based on the detected hardware various hardware specific packages are
1196 proposed.
1197 Test-new-install: mark show
1198 Relevance: 8
1199 Packages: for-current-hardware
1200 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1201
1202 &lt;p&gt;The second part is in
1203 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1204 this:&lt;/p&gt;
1205
1206 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1207 #!/bin/sh
1208 #
1209 (
1210 isenkram-lookup
1211 isenkram-autoinstall-firmware -l
1212 ) | sort -u
1213 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1214
1215 &lt;p&gt;All in all, a very short and simple implementation making it
1216 trivial to install the hardware dependent package we all may want to
1217 have installed on our machines. I&#39;ve not been able to find a way to
1218 get tasksel to tell you exactly which packages it plan to install
1219 before doing the installation. So if you are curious or careful,
1220 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1221
1222 &lt;p&gt;The information about which packages are handling which hardware is
1223 fetched either from the isenkram package itself in
1224 /usr/share/isenkram/, from git.debian.org or from the APT package
1225 database (using the Modaliases header). The APT package database
1226 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1227 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1228 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1229 the python-apt code (bug
1230 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1231 workaround I was able to get rid of the file descriptor leak and
1232 reduce the memory leak from ~30 MiB per hardware detection down to
1233 around 2 MiB per hardware detection. It should make the desktop
1234 daemon a lot more useful. The fix is in version 0.7 uploaded to
1235 unstable today.&lt;/p&gt;
1236
1237 &lt;p&gt;I believe the current way of mapping hardware to packages in
1238 Isenkram is is a good draft, but in the future I expect isenkram to
1239 use the AppStream data source for this. A proposal for getting proper
1240 AppStream support into Debian is floating around as
1241 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1242 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1243 project&lt;/a&gt; will take place this summer to improve the situation. I
1244 look forward to seeing the result, and welcome patches for isenkram to
1245 start using the information when it is ready.&lt;/p&gt;
1246
1247 &lt;p&gt;If you want your package to map to some specific hardware, either
1248 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1249 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1250 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1251 package. See also
1252 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1253 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1254 the information will be migrated to AppStream eventually, but for the
1255 moment I got no better place to store it.&lt;/p&gt;
1256 </description>
1257 </item>
1258
1259 <item>
1260 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1261 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1262 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1263 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1264 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1265 project&lt;/a&gt; is working on providing the software and hardware to make
1266 it easy for non-technical people to host their data and communication
1267 at home, and being able to communicate with their friends and family
1268 encrypted and away from prying eyes. It is still going strong, and
1269 today a major mile stone was reached.&lt;/p&gt;
1270
1271 &lt;p&gt;Today, the last of the packages currently used by the project to
1272 created the system images were accepted into Debian Unstable. It was
1273 the freedombox-setup package, which is used to configure the images
1274 during build and on the first boot. Now all one need to get going is
1275 the build code from the freedom-maker git repository and packages from
1276 Debian. And once the freedombox-setup package enter testing, we can
1277 build everything directly from Debian. :)&lt;/p&gt;
1278
1279 &lt;p&gt;Some key packages used by Freedombox are
1280 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1281 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1282 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1283 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1284 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1285 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1286 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1287 are plans to integrate more packages into the setup. User
1288 documentation is maintained on the Debian wiki. Please
1289 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1290 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1291
1292 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1293 setup, run this on a Debian machine using a user with sudo rights to
1294 become root:&lt;/p&gt;
1295
1296 &lt;p&gt;&lt;pre&gt;
1297 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1298 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1299 u-boot-tools
1300 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1301 freedom-maker
1302 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1303 &lt;/pre&gt;&lt;/p&gt;
1304
1305 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1306 devices. See the README in the freedom-maker git repo for more
1307 details on the build. If you do not want all three images, trim the
1308 make line. Note that the virtualbox-image target is not really
1309 virtualbox specific. It create a x86 image usable in kvm, qemu,
1310 vmware and any other x86 virtual machine environment. You might need
1311 the version of vmdebootstrap in Jessie to get the build working, as it
1312 include fixes for a race condition with kpartx.&lt;/p&gt;
1313
1314 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1315 method, boot a Debian Wheezy ISO and use this boot argument to load
1316 the preseed values:&lt;/p&gt;
1317
1318 &lt;p&gt;&lt;pre&gt;
1319 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;
1320 &lt;/pre&gt;&lt;/p&gt;
1321
1322 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1323 it still work.&lt;/p&gt;
1324
1325 &lt;p&gt;If you wonder how to help, one task you could look at is using
1326 systemd as the boot system. It will become the default for Linux in
1327 Jessie, so we need to make sure it is usable on the Freedombox. I did
1328 a simple test a few weeks ago, and noticed dnsmasq failed to start
1329 during boot when using systemd. I suspect there are other problems
1330 too. :) To detect problems, there is a test suite included, which can
1331 be run from the plinth web interface.&lt;/p&gt;
1332
1333 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1334 us get the new release published. :) Please join us on
1335 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1336 irc.debian.org)&lt;/a&gt; and
1337 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1338 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1339 </description>
1340 </item>
1341
1342 <item>
1343 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1344 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1346 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1347 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1348 solution for use at home. My requirements are simple, it must be
1349 cheap and locally encrypted (in other words, I keep the encryption
1350 keys, the storage provider do not have access to my private files).
1351 One idea me and my friends had many years ago, before the cloud
1352 storage providers showed up, was to use Google mail as storage,
1353 writing a Linux block device storing blocks as emails in the mail
1354 service provided by Google, and thus get heaps of free space. On top
1355 of this one can add encryption, RAID and volume management to have
1356 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1357 I never found time to implement such system. But the last few weeks I
1358 have looked at a system called
1359 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1360 mounted network backed file system with the features I need.&lt;/p&gt;
1361
1362 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1363 handling several different storage providers, any with Amazon S3,
1364 Google Drive or OpenStack API. There are heaps of such storage
1365 providers. S3QL can also use a local directory as storage, which
1366 combined with sshfs allow for file storage on any ssh server. S3QL
1367 include support for encryption, compression, de-duplication, snapshots
1368 and immutable file systems, allowing me to mount the remote storage as
1369 a local mount point, look at and use the files as if they were local,
1370 while the content is stored in the cloud as well. This allow me to
1371 have a backup that should survive fire. The file system can not be
1372 shared between several machines at the same time, as only one can
1373 mount it at the time, but any machine with the encryption key and
1374 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1375
1376 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1377 package is included already. So to get started, run &lt;tt&gt;apt-get
1378 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1379 Greenqloud, after reading their nice recipe on
1380 &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
1381 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1382 in Iceland more than those in USA when it come to keeping my personal
1383 data safe and private, and thus would rather spend money on a company
1384 in Iceland. Another nice recipe is available from the article
1385 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1386 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1387 Admin magazine. When the provider is picked, figure out how to get
1388 the API key needed to connect to the storage API. With Greencloud,
1389 the key did not show up until I had added payment details to my
1390 account.&lt;/p&gt;
1391
1392 &lt;p&gt;Armed with the API access details, it is time to create the file
1393 system. First, create a new bucket in the cloud. This bucket is the
1394 file system storage area. I picked a bucket name reflecting the
1395 machine that was going to store data there, but any name will do.
1396 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1397 the API login and password, and a locally created password. Store it
1398 all in ~root/.s3ql/authinfo2 like this:
1399
1400 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1401 [s3c]
1402 storage-url: s3c://s.greenqloud.com:443/bucket-name
1403 backend-login: API-login
1404 backend-password: API-password
1405 fs-passphrase: local-password
1406 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1407
1408 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1409 but any sensible way to create a fairly random password should do it.
1410 Armed with these details, it is now time to run mkfs, entering the API
1411 details and password to create it:&lt;/p&gt;
1412
1413 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1414 # mkdir -m 700 /var/lib/s3ql-cache
1415 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1416 --ssl s3c://s.greenqloud.com:443/bucket-name
1417 Enter backend login:
1418 Enter backend password:
1419 Before using S3QL, make sure to read the user&#39;s guide, especially
1420 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1421 Enter encryption password:
1422 Confirm encryption password:
1423 Generating random encryption key...
1424 Creating metadata tables...
1425 Dumping metadata...
1426 ..objects..
1427 ..blocks..
1428 ..inodes..
1429 ..inode_blocks..
1430 ..symlink_targets..
1431 ..names..
1432 ..contents..
1433 ..ext_attributes..
1434 Compressing and uploading metadata...
1435 Wrote 0.00 MB of compressed metadata.
1436 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1437
1438 &lt;p&gt;The next step is mounting the file system to make the storage available.
1439
1440 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1441 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1442 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1443 Using 4 upload threads.
1444 Downloading and decompressing metadata...
1445 Reading metadata...
1446 ..objects..
1447 ..blocks..
1448 ..inodes..
1449 ..inode_blocks..
1450 ..symlink_targets..
1451 ..names..
1452 ..contents..
1453 ..ext_attributes..
1454 Mounting filesystem...
1455 # df -h /s3ql
1456 Filesystem Size Used Avail Use% Mounted on
1457 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1458 #
1459 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1460
1461 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1462 backups in it, and as the metadata used by rsync is downloaded at
1463 mount time, no network traffic (and storage cost) is triggered by
1464 running rsync. To unmount, one should not use the normal umount
1465 command, as this will not flush the cache to the cloud storage, but
1466 instead running the umount.s3ql command like this:
1467
1468 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1469 # umount.s3ql /s3ql
1470 #
1471 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1472
1473 &lt;p&gt;There is a fsck command available to check the file system and
1474 correct any problems detected. This can be used if the local server
1475 crashes while the file system is mounted, to reset the &quot;already
1476 mounted&quot; flag. This is what it look like when processing a working
1477 file system:&lt;/p&gt;
1478
1479 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1480 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1481 Using cached metadata.
1482 File system seems clean, checking anyway.
1483 Checking DB integrity...
1484 Creating temporary extra indices...
1485 Checking lost+found...
1486 Checking cached objects...
1487 Checking names (refcounts)...
1488 Checking contents (names)...
1489 Checking contents (inodes)...
1490 Checking contents (parent inodes)...
1491 Checking objects (reference counts)...
1492 Checking objects (backend)...
1493 ..processed 5000 objects so far..
1494 ..processed 10000 objects so far..
1495 ..processed 15000 objects so far..
1496 Checking objects (sizes)...
1497 Checking blocks (referenced objects)...
1498 Checking blocks (refcounts)...
1499 Checking inode-block mapping (blocks)...
1500 Checking inode-block mapping (inodes)...
1501 Checking inodes (refcounts)...
1502 Checking inodes (sizes)...
1503 Checking extended attributes (names)...
1504 Checking extended attributes (inodes)...
1505 Checking symlinks (inodes)...
1506 Checking directory reachability...
1507 Checking unix conventions...
1508 Checking referential integrity...
1509 Dropping temporary indices...
1510 Backing up old metadata...
1511 Dumping metadata...
1512 ..objects..
1513 ..blocks..
1514 ..inodes..
1515 ..inode_blocks..
1516 ..symlink_targets..
1517 ..names..
1518 ..contents..
1519 ..ext_attributes..
1520 Compressing and uploading metadata...
1521 Wrote 0.89 MB of compressed metadata.
1522 #
1523 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1524
1525 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1526 quick, about the same speed as local file access. Uploading large
1527 amount of data is to me limited by the bandwidth out of and into my
1528 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1529 which is very close to my upload speed, and downloading the same
1530 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1531 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1532 network, not the file system code. I do not know what a good cache
1533 size would be, but suspect that the cache should e larger than your
1534 working set.&lt;/p&gt;
1535
1536 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1537 time. If another machine try, it is told that the file system is
1538 busy:&lt;/p&gt;
1539
1540 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1541 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1542 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1543 Using 8 upload threads.
1544 Backend reports that fs is still mounted elsewhere, aborting.
1545 #
1546 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1547
1548 &lt;p&gt;The file content is uploaded when the cache is full, while the
1549 metadata is uploaded once every 24 hour by default. To ensure the
1550 file system content is flushed to the cloud, one can either umount the
1551 file system, or ask S3QL to flush the cache and metadata using
1552 s3qlctrl:
1553
1554 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1555 # s3qlctrl upload-meta /s3ql
1556 # s3qlctrl flushcache /s3ql
1557 #
1558 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1559
1560 &lt;p&gt;If you are curious about how much space your data uses in the
1561 cloud, and how much compression and deduplication cut down on the
1562 storage usage, you can use s3qlstat on the mounted file system to get
1563 a report:&lt;/p&gt;
1564
1565 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1566 # s3qlstat /s3ql
1567 Directory entries: 9141
1568 Inodes: 9143
1569 Data blocks: 8851
1570 Total data size: 22049.38 MB
1571 After de-duplication: 21955.46 MB (99.57% of total)
1572 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1573 Database size: 2.39 MB (uncompressed)
1574 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1575 #
1576 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1577
1578 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1579 storage. I did not try to locate them all, but am aware of at least
1580 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1581 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1582 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1583 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1584 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1585 accept payment in Bitcoin. Pick one that suit your need. Some of
1586 them provide several GiB of free storage, but the prize models are
1587 quite different and you will have to figure out what suits you
1588 best.&lt;/p&gt;
1589
1590 &lt;p&gt;While researching this blog post, I had a look at research papers
1591 and posters discussing the S3QL file system. There are several, which
1592 told me that the file system is getting a critical check by the
1593 science community and increased my confidence in using it. One nice
1594 poster is titled
1595 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1596 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1597 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1598 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1599 and Pamela Smith. Please have a look.&lt;/p&gt;
1600
1601 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1602 check out the mounted S3QL file system to see if it would be usable as
1603 a home directory (in other word, that it provided POSIX semantics when
1604 it come to locking and umask handling etc). Running
1605 &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
1606 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1607 no error was found. So the file system can be used for home
1608 directories, if one chooses to do so.&lt;/p&gt;
1609
1610 &lt;p&gt;If you do not want a locally file system, and want something that
1611 work without the Linux fuse file system, I would like to mention the
1612 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1613 provide locally encrypted backup using a command line client. It have
1614 a nicer access control system, where one can split out read and write
1615 access, allowing some systems to write to the backup and others to
1616 only read from it.&lt;/p&gt;
1617
1618 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1619 activities, please send Bitcoin donations to my address
1620 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1621 </description>
1622 </item>
1623
1624 <item>
1625 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1626 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1627 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1628 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1629 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1630 project&lt;/a&gt; is working on providing the software and hardware for
1631 making it easy for non-technical people to host their data and
1632 communication at home, and being able to communicate with their
1633 friends and family encrypted and away from prying eyes. It has been
1634 going on for a while, and is slowly progressing towards a new test
1635 release (0.2).&lt;/p&gt;
1636
1637 &lt;p&gt;And what day could be better than the Pi day to announce that the
1638 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1639 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1640 system), and can also be installed using a Debian installer preseed
1641 file. The Debian based Freedombox is now based on Debian Jessie,
1642 where most of the needed packages used are already present. Only one,
1643 the freedombox-setup package, is missing. To try to build your own
1644 boot image to test the current status, fetch the freedom-maker scripts
1645 and build using
1646 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1647 with a user with sudo access to become root:
1648
1649 &lt;pre&gt;
1650 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1651 freedom-maker
1652 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1653 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1654 u-boot-tools
1655 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1656 &lt;/pre&gt;
1657
1658 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1659 devices. See the README for more details on the build. If you do not
1660 want all three images, trim the make line. But note that thanks to &lt;a
1661 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1662 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1663 kpartx call.&lt;/p&gt;
1664
1665 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1666 method, boot a Debian Wheezy ISO and use this boot argument to load
1667 the preseed values:&lt;/p&gt;
1668
1669 &lt;pre&gt;
1670 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;
1671 &lt;/pre&gt;
1672
1673 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1674 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1675 currently hang while setting up APT sources. Killing the
1676 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1677 installation will get the installation going. This affect all
1678 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1679
1680 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1681 us get the new release published. :) Please join us on
1682 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1683 irc.debian.org)&lt;/a&gt; and
1684 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1685 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1686 </description>
1687 </item>
1688
1689 <item>
1690 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1691 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1692 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1693 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1694 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1695 innetgr tools, because I needed them in
1696 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1697 ng-utils, and it has served me well. I placed the project under the
1698 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1699 repository. But many years ago, the CVS repository was dropped (lost,
1700 not migrated to new hardware, not sure), and the project have lacked a
1701 proper home since then.&lt;/p&gt;
1702
1703 &lt;p&gt;Last summer, I had a look at the package and made a new release
1704 fixing a irritating crash bug, but was unable to store the changes in
1705 a proper source control system. I applied for a project on
1706 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1707 to follow up on it. Until today. :)&lt;/p&gt;
1708
1709 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1710 now have a new home, and a git repository with the highlight of the
1711 history of the project. I published all release tarballs and imported
1712 them into the git repository. As the project is really stable and not
1713 expected to gain new features any time soon, I decided to make a new
1714 release and call it 1.0. Visit the new project home on
1715 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1716 if you want to check it out. The new version is also uploaded into
1717 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1718 </description>
1719 </item>
1720
1721 <item>
1722 <title>Testing sysvinit from experimental in Debian Hurd</title>
1723 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1724 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1725 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1726 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1727 their changes into sysvinit, to allow them to use the normal sysvinit
1728 boot system instead of their old one. This follow up on the
1729 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1730 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1731 get Debian on Hurd working more like Debian on Linux. To get started,
1732 I downloaded a prebuilt hard disk image from
1733 &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;,
1734 and started it using virt-manager.&lt;/p&gt;
1735
1736 &lt;p&gt;The first think I had to do after logging in (root without any
1737 password) was to get the network operational. I followed
1738 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1739 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1740 commands as root to get the machine to accept a IP address from the
1741 kvm internal DHCP server:&lt;/p&gt;
1742
1743 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1744 settrans -fgap /dev/netdde /hurd/netdde
1745 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1746 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1747 dhclient /dev/eth0
1748 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1749
1750 &lt;p&gt;After this, the machine had internet connectivity, and I could
1751 upgrade it and install the sysvinit packages from experimental and
1752 enable it as the default boot system in Hurd.&lt;/p&gt;
1753
1754 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1755 running on the machine it for ssh login to work a password need to be
1756 set. Also, note that a bug somewhere in openssh on Hurd block
1757 compression from working. Remember to turn that off on the client
1758 side.&lt;/p&gt;
1759
1760 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1761 stuff:&lt;/p&gt;
1762
1763 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1764 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1765 deb http://http.debian.net/debian/ experimental main
1766 EOF
1767 apt-get update
1768 apt-get dist-upgrade
1769 apt-get install -t experimental initscripts sysv-rc sysvinit \
1770 sysvinit-core sysvinit-utils
1771 update-alternatives --config runsystem
1772 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1773
1774 &lt;p&gt;To reboot after switching boot system, you have to use
1775 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1776 yet a sysvinit process able to receive the signals from the normal
1777 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1778 upgrading every package and rebooting, the network come up with DHCP
1779 after boot as it should, and the settrans/pkill hack mentioned at the
1780 start is no longer needed. But for some strange reason, there are no
1781 longer any login prompt in the virtual console, so I logged in using
1782 ssh instead.
1783
1784 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1785 fail some times. No idea what the cause is, but hope the Hurd porters
1786 figure it out. At least Justus said on IRC (#debian-hurd on
1787 irc.debian.org) that they are aware of the problem. A way to reduce
1788 the impact is to upgrade to the Hurd packages built by Justus by
1789 adding this repository to the machine:&lt;/p&gt;
1790
1791 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1792 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1793 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1794 EOF
1795 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1796
1797 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1798 http://ftp.debian-ports.org/debian, because some of the packages in
1799 unstable do not yet include the required patches that are lingering in
1800 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1801
1802 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1803 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1804 i emacs - GNU Emacs editor (metapackage)
1805 i gdb - GNU Debugger
1806 i hurd-recommended - Miscellaneous translators
1807 i isc-dhcp-client - ISC DHCP client
1808 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1809 i libc-bin - Embedded GNU C Library: Binaries
1810 i libc-dev-bin - Embedded GNU C Library: Development binaries
1811 i libc0.3 - Embedded GNU C Library: Shared libraries
1812 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1813 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1814 i multiarch-support - Transitional package to ensure multiarch compatibilit
1815 i A x11-common - X Window System (X.Org) infrastructure
1816 i xorg - X.Org X Window System
1817 i A xserver-xorg - X.Org X server
1818 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1819 #
1820 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1821
1822 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1823 X.org did not work out of the box and I never took the time to follow
1824 the porters instructions to fix it. This time I was interested in the
1825 command line stuff.&lt;p&gt;
1826 </description>
1827 </item>
1828
1829 <item>
1830 <title>New chrpath release 0.16</title>
1831 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1833 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1834 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1835 find problems in C, C++ and Java code using static source code
1836 analysis. It can detect a lot of different problems, and is very
1837 useful to find memory and locking bugs in the error handling part of
1838 the source. The company behind it provide
1839 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1840 a community service&lt;/a&gt;, and many hundred free software projects are
1841 already checked. A few days ago I decided to have a closer look at
1842 the Coverity system, and discovered that the
1843 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1844 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1845 projects I am involved with was already registered. But these are
1846 fairly big, and I would also like to have a small and easy project to
1847 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1848 checking of the chrpath project&lt;/a&gt;. It was
1849 added to the checker and discovered seven potential defects. Six of
1850 these were real, mostly resource &quot;leak&quot; when the program detected an
1851 error. Nothing serious, as the resources would be released a fraction
1852 of a second later when the program exited because of the error, but it
1853 is nice to do it right in case the source of the program some time in
1854 the future end up in a library. Having fixed all defects and added
1855 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1856 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1857 publish a new release. These are the release notes:&lt;/p&gt;
1858
1859 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1860
1861 &lt;ul&gt;
1862
1863 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1864 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1865 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1866
1867 &lt;/ul&gt;
1868
1869 &lt;p&gt;You can
1870 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1871 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1872 project if something is wrong with the new release. The test suite
1873 did not discover any old errors, so if you find a new one, please also
1874 include a test suite check.&lt;/p&gt;
1875 </description>
1876 </item>
1877
1878 <item>
1879 <title>New chrpath release 0.15</title>
1880 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1882 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1883 <description>&lt;p&gt;After many years break from the package and a vain hope that
1884 development would be continued by someone else, I finally pulled my
1885 acts together this morning and wrapped up a new release of chrpath,
1886 the command line tool to modify the rpath and runpath of already
1887 compiled ELF programs. The update was triggered by the persistence of
1888 Isha Vishnoi at IBM, which needed a new config.guess file to get
1889 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1890 is working on. I checked the
1891 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1892 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1893 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1894 packages for interesting patches (failed to find the source from
1895 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1896 These are the release notes:&lt;/p&gt;
1897
1898 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1899
1900 &lt;ul&gt;
1901
1902 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1903 with newer architectures. Thanks to isha vishnoi for the heads
1904 up.&lt;/li&gt;
1905
1906 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1907
1908 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1909 Matthias Klose.&lt;/li&gt;
1910
1911 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1912 Petr Machata found in Fedora.&lt;/li&gt;
1913
1914 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1915 .dynamic is a NULL terminated string. Based on patch found in
1916 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1917
1918 &lt;/ul&gt;
1919
1920 &lt;p&gt;You can
1921 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1922 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1923 project if something is wrong with the new release. The test suite
1924 did not discover any old errors, so if you find a new one, please also
1925 include a testsuite check.&lt;/p&gt;
1926 </description>
1927 </item>
1928
1929 <item>
1930 <title>Debian init.d boot script example for rsyslog</title>
1931 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1932 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1933 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1934 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1935 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1936 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1937 init.d scripts at all. Here is an example init.d script, ie a rewrite
1938 of /etc/init.d/rsyslog:&lt;/p&gt;
1939
1940 &lt;p&gt;&lt;pre&gt;
1941 #!/lib/init/init-d-script
1942 ### BEGIN INIT INFO
1943 # Provides: rsyslog
1944 # Required-Start: $remote_fs $time
1945 # Required-Stop: umountnfs $time
1946 # X-Stop-After: sendsigs
1947 # Default-Start: 2 3 4 5
1948 # Default-Stop: 0 1 6
1949 # Short-Description: enhanced syslogd
1950 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1951 # It is quite compatible to stock sysklogd and can be
1952 # used as a drop-in replacement.
1953 ### END INIT INFO
1954 DESC=&quot;enhanced syslogd&quot;
1955 DAEMON=/usr/sbin/rsyslogd
1956 &lt;/pre&gt;&lt;/p&gt;
1957
1958 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1959 script was 137 lines, and the above is just 15 lines, most of it meta
1960 info/comments.&lt;/p&gt;
1961
1962 &lt;p&gt;How to do this, you ask? Well, one create a new script
1963 /lib/init/init-d-script looking something like this:
1964
1965 &lt;p&gt;&lt;pre&gt;
1966 #!/bin/sh
1967
1968 # Define LSB log_* functions.
1969 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1970 # and status_of_proc is working.
1971 . /lib/lsb/init-functions
1972
1973 #
1974 # Function that starts the daemon/service
1975
1976 #
1977 do_start()
1978 {
1979 # Return
1980 # 0 if daemon has been started
1981 # 1 if daemon was already running
1982 # 2 if daemon could not be started
1983 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1984 || return 1
1985 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1986 $DAEMON_ARGS \
1987 || return 2
1988 # Add code here, if necessary, that waits for the process to be ready
1989 # to handle requests from services started subsequently which depend
1990 # on this one. As a last resort, sleep for some time.
1991 }
1992
1993 #
1994 # Function that stops the daemon/service
1995 #
1996 do_stop()
1997 {
1998 # Return
1999 # 0 if daemon has been stopped
2000 # 1 if daemon was already stopped
2001 # 2 if daemon could not be stopped
2002 # other if a failure occurred
2003 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2004 RETVAL=&quot;$?&quot;
2005 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2006 # Wait for children to finish too if this is a daemon that forks
2007 # and if the daemon is only ever run from this initscript.
2008 # If the above conditions are not satisfied then add some other code
2009 # that waits for the process to drop all resources that could be
2010 # needed by services started subsequently. A last resort is to
2011 # sleep for some time.
2012 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2013 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2014 # Many daemons don&#39;t delete their pidfiles when they exit.
2015 rm -f $PIDFILE
2016 return &quot;$RETVAL&quot;
2017 }
2018
2019 #
2020 # Function that sends a SIGHUP to the daemon/service
2021 #
2022 do_reload() {
2023 #
2024 # If the daemon can reload its configuration without
2025 # restarting (for example, when it is sent a SIGHUP),
2026 # then implement that here.
2027 #
2028 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2029 return 0
2030 }
2031
2032 SCRIPTNAME=$1
2033 scriptbasename=&quot;$(basename $1)&quot;
2034 echo &quot;SN: $scriptbasename&quot;
2035 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2036 script=&quot;$1&quot;
2037 shift
2038 . $script
2039 else
2040 exit 0
2041 fi
2042
2043 NAME=$(basename $DAEMON)
2044 PIDFILE=/var/run/$NAME.pid
2045
2046 # Exit if the package is not installed
2047 #[ -x &quot;$DAEMON&quot; ] || exit 0
2048
2049 # Read configuration variable file if it is present
2050 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2051
2052 # Load the VERBOSE setting and other rcS variables
2053 . /lib/init/vars.sh
2054
2055 case &quot;$1&quot; in
2056 start)
2057 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2058 do_start
2059 case &quot;$?&quot; in
2060 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2061 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2062 esac
2063 ;;
2064 stop)
2065 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2066 do_stop
2067 case &quot;$?&quot; in
2068 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2069 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2070 esac
2071 ;;
2072 status)
2073 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2074 ;;
2075 #reload|force-reload)
2076 #
2077 # If do_reload() is not implemented then leave this commented out
2078 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2079 #
2080 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2081 #do_reload
2082 #log_end_msg $?
2083 #;;
2084 restart|force-reload)
2085 #
2086 # If the &quot;reload&quot; option is implemented then remove the
2087 # &#39;force-reload&#39; alias
2088 #
2089 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2090 do_stop
2091 case &quot;$?&quot; in
2092 0|1)
2093 do_start
2094 case &quot;$?&quot; in
2095 0) log_end_msg 0 ;;
2096 1) log_end_msg 1 ;; # Old process is still running
2097 *) log_end_msg 1 ;; # Failed to start
2098 esac
2099 ;;
2100 *)
2101 # Failed to stop
2102 log_end_msg 1
2103 ;;
2104 esac
2105 ;;
2106 *)
2107 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2108 exit 3
2109 ;;
2110 esac
2111
2112 :
2113 &lt;/pre&gt;&lt;/p&gt;
2114
2115 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2116 lot. I did not really polish the approach, so it might not always
2117 work out of the box, but you get the idea. I did not try very hard to
2118 optimize it nor make it more robust either.&lt;/p&gt;
2119
2120 &lt;p&gt;A better argument for switching init system in Debian than reducing
2121 the size of init scripts (which is a good thing to do anyway), is to
2122 get boot system that is able to handle the kernel events sensibly and
2123 robustly, and do not depend on the boot to run sequentially. The boot
2124 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2125 </description>
2126 </item>
2127
2128 <item>
2129 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2130 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2131 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2132 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2133 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2134 remote display access is the preferred solution with oVirt and RedHat
2135 Enterprise Virtualization, and I was sad to discover the other day
2136 that the browser plugin needed to use these systems seamlessly was
2137 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2138 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2139 2013-04-01, so I decided to wrap up a package based on the great work
2140 from Cajus Pollmeier and put it in a collab-maint maintained git
2141 repository to get a package I could use. I would very much like
2142 others to help me maintain the package (or just take over, I do not
2143 mind), but as no-one had volunteered so far, I just uploaded it to
2144 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2145
2146 &lt;p&gt;The source is now available from
2147 &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;
2148 </description>
2149 </item>
2150
2151 <item>
2152 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2153 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2154 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2155 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2156 <description>&lt;p&gt;The
2157 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2158 program is a a very nice system to create virtual machine images. It
2159 create a image file, add a partition table, mount it and run
2160 debootstrap in the mounted directory to create a Debian system on a
2161 stick. Yesterday, I decided to try to teach it how to make images for
2162 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2163 of a plan to simplify the build system for
2164 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2165 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2166 the virtualbox images, but its current build system made multistrap
2167 based system for Dreamplug images, and it is lacking support for
2168 Raspberry Pi.&lt;/p&gt;
2169
2170 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2171 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2172 code and adjusted it to be able to build armel images on my amd64
2173 Debian laptop. I ended up giving vmdebootstrap five new options,
2174 allowing me to replicate the image creation process I use to make
2175 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2176 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2177 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2178 call debootstrap with --foreign and to copy the handler into the
2179 generated chroot before running the second stage. This allow
2180 vmdebootstrap to create armel images on an amd64 host. Next I added
2181 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2182 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2183 given file system type, allowing me to create an image with a vfat
2184 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2185 variant&lt;/tt&gt; option to allow me to create smaller images without the
2186 Debian base system packages installed. Finally, I added an option
2187 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2188 as a boot loader. It is not needed on the Raspberry Pi and probably
2189 most other non-x86 architectures. The changes were accepted by the
2190 upstream author of vmdebootstrap yesterday and today, and is now
2191 available from
2192 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2193 upstream project page&lt;/a&gt;.&lt;/p&gt;
2194
2195 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2196 create a small script (the customize script) to add the non-free
2197 binary blob needed to boot the Raspberry Pi and the APT source
2198 list:&lt;/p&gt;
2199
2200 &lt;p&gt;&lt;pre&gt;
2201 #!/bin/sh
2202 set -e # Exit on first error
2203 rootdir=&quot;$1&quot;
2204 cd &quot;$rootdir&quot;
2205 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2206 deb http://http.debian.net/debian/ jessie main contrib non-free
2207 EOF
2208 # Install non-free binary blob needed to boot Raspberry Pi. This
2209 # install a kernel somewhere too.
2210 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2211 -O $rootdir/usr/bin/rpi-update
2212 chmod a+x $rootdir/usr/bin/rpi-update
2213 mkdir -p $rootdir/lib/modules
2214 touch $rootdir/boot/start.elf
2215 chroot $rootdir rpi-update
2216 &lt;/pre&gt;&lt;/p&gt;
2217
2218 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2219 to build the image:&lt;/p&gt;
2220
2221 &lt;pre&gt;
2222 sudo ./vmdebootstrap \
2223 --variant minbase \
2224 --arch armel \
2225 --distribution jessie \
2226 --mirror http://http.debian.net/debian \
2227 --image test.img \
2228 --size 600M \
2229 --bootsize 64M \
2230 --boottype vfat \
2231 --log-level debug \
2232 --verbose \
2233 --no-kernel \
2234 --no-extlinux \
2235 --root-password raspberry \
2236 --hostname raspberrypi \
2237 --foreign /usr/bin/qemu-arm-static \
2238 --customize `pwd`/customize \
2239 --package netbase \
2240 --package git-core \
2241 --package binutils \
2242 --package ca-certificates \
2243 --package wget \
2244 --package kmod
2245 &lt;/pre&gt;&lt;/p&gt;
2246
2247 &lt;p&gt;The list of packages being installed are the ones needed by
2248 rpi-update to make the image bootable on the Raspberry Pi, with the
2249 exception of netbase, which is needed by debootstrap to find
2250 /etc/hosts with the minbase variant. I really wish there was a way to
2251 set up an Raspberry Pi using only packages in the Debian archive, but
2252 that is not possible as far as I know, because it boots from the GPU
2253 using a non-free binary blob.&lt;/p&gt;
2254
2255 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2256 probably a few others installed. I have not checked the complete
2257 build dependency list.&lt;/p&gt;
2258
2259 &lt;p&gt;The resulting image will not use the hardware floating point unit
2260 on the Raspberry PI, because the armel architecture in Debian is not
2261 optimized for that use. So the images created will be a bit slower
2262 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2263 </description>
2264 </item>
2265
2266 <item>
2267 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2268 <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>
2269 <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>
2270 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2271 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2272 wider attention. I recommend signing and donating to each one of
2273 these. :)&lt;/p&gt;
2274
2275 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2276 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2277 Women program which is a Google Summer of Code like initiative to get
2278 more women involved in free software. One debian sponsor has offered
2279 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2280 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2281 hope you will to. :)&lt;/p&gt;
2282
2283 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2284 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2285 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2286 take place these days, and their need to fund the work. I&#39;ve already
2287 donated. Are you next?&lt;/p&gt;
2288
2289 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2290 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2291 statement under the heading
2292 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2293 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2294 Norwegian government. So far 499 signatures. I hope you will sign it
2295 too.&lt;/p&gt;
2296 </description>
2297 </item>
2298
2299 <item>
2300 <title>Videos about the Freedombox project - for inspiration and learning</title>
2301 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2302 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2303 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2304 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2305 project&lt;/a&gt; have been going on for a while, and have presented the
2306 vision, ideas and solution several places. Here is a little
2307 collection of videos of talks and presentation of the project.&lt;/p&gt;
2308
2309 &lt;ul&gt;
2310
2311 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2312 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2313
2314 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2315 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2316
2317 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2318 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2319 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2320 (Youtube)&lt;/li&gt;
2321
2322 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2323 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2324
2325 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2326 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2327
2328 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2329 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2330 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2331
2332 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2333 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2334 (Youtube)&lt;/li&gt;
2335
2336 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2337 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2338
2339 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2340 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2341
2342 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2343 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2344 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2345
2346 &lt;/ul&gt;
2347
2348 &lt;p&gt;A larger list is available from
2349 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2350 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2351
2352 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2353 Jessie is coming along quite well, and soon both Owncloud and using
2354 Tor should be available for testers of the Freedombox solution. :) In
2355 a few weeks I hope everything needed to test it is included in Debian.
2356 The withsqlite package is already in Debian, and the plinth package is
2357 pending in NEW. The third and vital part of that puzzle is the
2358 metapackage/setup framework, which is still pending an upload. Join
2359 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2360 (#freedombox on irc.debian.org)&lt;/a&gt; and
2361 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2362 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2363 </description>
2364 </item>
2365
2366 <item>
2367 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2368 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2369 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2370 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2371 <description>&lt;p&gt;I was introduced to the
2372 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2373 in 2010, when Eben Moglen presented his vision about serving the need
2374 of non-technical people to keep their personal information private and
2375 within the legal protection of their own homes. The idea is to give
2376 people back the power over their network and machines, and return
2377 Internet back to its intended peer-to-peer architecture. Instead of
2378 depending on a central service, the Freedombox will give everyone
2379 control over their own basic infrastructure.&lt;/p&gt;
2380
2381 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2382 taken priority. But this summers nasty news about the misuse of trust
2383 and privilege exercised by the &quot;western&quot; intelligence gathering
2384 communities increased my eagerness to contribute to a point where I
2385 actually started working on the project a while back.&lt;/p&gt;
2386
2387 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2388 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2389 create a simple and cheap Debian based appliance that anyone can hook
2390 up in their home and get access to secure and private services and
2391 communication. The initial deployment platform have been the
2392 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2393 which is a piece of hardware I do not own. So to be able to test what
2394 the current Freedombox setup look like, I had to come up with a way to install
2395 it on some hardware I do have access to. I have rewritten the
2396 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2397 image build framework to use .deb packages instead of only copying
2398 setup into the boot images, and thanks to this rewrite I am able to
2399 set up any machine supported by Debian Wheezy as a Freedombox, using
2400 the previously mentioned deb (and a few support debs for packages
2401 missing in Debian).&lt;/p&gt;
2402
2403 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2404 scripts
2405 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2406 and a administrative web interface
2407 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2408 withsqlite), as well as a privacy enhancing proxy based on
2409 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2410 (freedombox-privoxy). There is also a web/javascript based XMPP
2411 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2412 trying (unsuccessfully so far) to talk to the XMPP server
2413 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2414 web interface is pluggable, and the goal is to use it to enable OpenID
2415 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2416 this is really working yet, see
2417 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2418 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2419 on github at the moment. The HTTP proxy is operational out of the
2420 box, and the admin web interface can be used to add/remove plinth
2421 users. I&#39;ve not been able to do anything else with it so far, but
2422 know there are several branches spread around github and other places
2423 with lots of half baked features.&lt;/p&gt;
2424
2425 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2426 following recipes should work to give you a test machine to poke
2427 at.&lt;/p&gt;
2428
2429 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2430
2431 &lt;ol&gt;
2432
2433 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2434 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2435 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2436 to the Debian installer:&lt;p&gt;
2437 &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;
2438
2439 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2440 install on.&lt;/li&gt;
2441
2442 &lt;li&gt;When the installation is finished and the machine have rebooted a
2443 few times, your Freedombox is ready for testing.&lt;/li&gt;
2444
2445 &lt;/ol&gt;
2446
2447 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2448
2449 &lt;ol&gt;
2450
2451 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2452 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2453 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2454 &lt;pre&gt;
2455 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2456 &lt;/pre&gt;&lt;/li&gt;
2457 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2458 &lt;pre&gt;
2459 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2460 apt-key add -
2461 apt-get update
2462 apt-get install freedombox-setup
2463 /usr/lib/freedombox/setup
2464 &lt;/pre&gt;&lt;/li&gt;
2465 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2466
2467 &lt;/ol&gt;
2468
2469 &lt;p&gt;You can test it on other architectures too, but because the
2470 freedombox-privoxy package is binary, it will only work as intended on
2471 the architectures where I have had time to build the binary and put it
2472 in my APT repository. But do not let this stop you. It is only a
2473 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2474
2475 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2476 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2477 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2478 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2479
2480 &lt;p&gt;Please let me know if this works for you, or if you have any
2481 problems. We gather on the IRC channel
2482 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2483 irc.debian.org and the
2484 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2485 mailing list&lt;/a&gt;.&lt;/p&gt;
2486
2487 &lt;p&gt;Once you get your freedombox operational, you can visit
2488 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2489 welcome screen (dead end - do not be surprised if you are unable to
2490 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2491 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2492 default password is &#39;secret&#39;.&lt;/p&gt;
2493 </description>
2494 </item>
2495
2496 <item>
2497 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2498 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2499 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2500 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2501 <description>&lt;p&gt;Earlier, I reported about
2502 &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
2503 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2504 told by IBM that the original disk should be thrown away. And as
2505 there no longer was a problem if I bricked the firmware, I decided
2506 today to try to install Intel firmware to replace the Lenovo firmware
2507 currently on the disk.&lt;/p&gt;
2508
2509 &lt;p&gt;I searched the Intel site for firmware, and found
2510 &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;
2511 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2512 according to the site should contain the latest firmware for SSD
2513 disks. I inserted the broken disk in one of my spare laptops and
2514 booted the ISO from a USB stick. The disk was recognized, but the
2515 program claimed the newest firmware already were installed and refused
2516 to insert any Intel firmware. So no change, and the disk is still
2517 unable to handle write load. :( I guess the only way to get them
2518 working would be if Lenovo releases new firmware. No idea how likely
2519 that is. Anyway, just blogging about this test for completeness. I
2520 got a working Samsung disk, and see no point in spending more time on
2521 the broken disks.&lt;/p&gt;
2522 </description>
2523 </item>
2524
2525 <item>
2526 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2527 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2528 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2529 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2530 <description>&lt;p&gt;Today I switched to
2531 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2532 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2533 my new Thinkpad X230, which was delivered with an
2534 &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
2535 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2536 sustained writes. My hardware supplier have been very forthcoming in
2537 trying to find a solution, and after first trying with another
2538 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2539 disk instead to fix it once and for all. The Samsung disk survived
2540 the installation of Debian with encrypted disks (filling the disk with
2541 random data during installation killed the first two), and I thus
2542 decided to trust it with my data. I have installed it as a Debian Edu
2543 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2544 server at home using Kerberos and LDAP, and will use it as my work
2545 station from now on.&lt;/p&gt;
2546
2547 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2548 Debian Wheezy default installation need to be tuned a bit to increase
2549 performance and increase life time of the disk. The Linux kernel and
2550 user space applications do not yet adjust automatically to such
2551 environment. To make it easier for my self, I created a draft Debian
2552 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2553 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2554 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2555 is set up to adjust the setup of the machine by just installing the
2556 package. If there is any non-SSD disk in the machine, the package
2557 will refuse to install, as I did not try to write any logic to sort
2558 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2559
2560 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2561 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2562 where I set up the machine with one large encrypted partition (in
2563 addition to /boot), put LVM on top of this and set up partitions on
2564 top of this again. See the README file in the package source for the
2565 references I used to pick the settings. At the moment these
2566 parameters are tuned:&lt;/p&gt;
2567
2568 &lt;ul&gt;
2569
2570 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2571 (adding discard to /etc/crypttab)&lt;/li&gt;
2572
2573 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2574 this case a cryptsetup partition) by changing issue_discards from
2575 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2576
2577 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2578 systems.&lt;/li&gt;
2579
2580 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2581 /etc/fstab.&lt;/li&gt;
2582
2583 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2584
2585 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2586 cron.daily).&lt;/li&gt;
2587
2588 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2589 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2590
2591 &lt;/ul&gt;
2592
2593 &lt;p&gt;During installation, I cancelled the part where the installer fill
2594 the disk with random data, as this would kill the SSD performance for
2595 little gain. My goal with the encrypted file system is to ensure
2596 those stealing my laptop end up with a brick and not a working
2597 computer. I have no hope in keeping the really resourceful people
2598 from getting the data on the disk (see
2599 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2600 Thus I concluded that adding the discard option to crypttab is the
2601 right thing to do.&lt;/p&gt;
2602
2603 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2604 it for SSD, but others recommended deadline and a benchmark I found
2605 indicated that deadline might be better for interactive use.&lt;/p&gt;
2606
2607 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2608 and ext4, but read that it would give a performance hit ever time a
2609 file is removed, and thought it best to that that slowdown once a day
2610 instead of during my work.&lt;/p&gt;
2611
2612 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2613 this is already done by Debian Edu.&lt;/p&gt;
2614
2615 &lt;p&gt;I have not yet started on the user space tuning. I expect
2616 iceweasel need some tuning, and perhaps other applications too, but
2617 have not yet had time to investigate those parts.&lt;/p&gt;
2618
2619 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2620 there.&lt;/p&gt;
2621
2622 &lt;p&gt;As for the answer to the question in the title of this blog post,
2623 as far as I know, the only solution I know about is to replace the
2624 disk. It might be possible to flash it with Intel firmware instead of
2625 the Lenovo firmware. But I have not tried and did not want to do so
2626 without approval from Lenovo as I wanted to keep the warranty on the
2627 disk until a solution was found and they wanted the broken disks
2628 back.&lt;/p&gt;
2629 </description>
2630 </item>
2631
2632 <item>
2633 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2634 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2635 <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>
2636 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2637 <description>&lt;p&gt;A few days ago, I wrote about
2638 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2639 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2640 was dying during installation because it is unable to cope with
2641 sustained write. My supplier is in contact with
2642 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2643 replacement disk to try to fix the problem. They decided to send an
2644 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2645
2646 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2647 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2648 same firmware version as the original. This time my hope raised
2649 slightly as the installation progressed, as the original disk used to
2650 die after 4-7% of the disk was written to, while this time it kept
2651 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2652 died again and I was back on square one. I still do not have a new
2653 laptop with a disk I can trust. I can not live with a disk that might
2654 lock up when I download a new
2655 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2656 other large files. I look forward to hearing from my supplier with
2657 the next proposal from Lenovo.&lt;/p&gt;
2658
2659 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2660 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2661 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2662 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2663 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2664 P/N 45N8295, P0C38732.&lt;/p&gt;
2665
2666 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2667 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2668 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2669 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2670 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2671 P/N 45N8295, P0C38732.&lt;/p&gt;
2672
2673 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2674 SA, date and WNPP values. Mentioning all the details here in case
2675 someone is able to use the information to find a way to identify the
2676 failing disk among working ones (if any such working disk actually
2677 exist).&lt;/p&gt;
2678 </description>
2679 </item>
2680
2681 <item>
2682 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2683 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2685 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2686 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2687 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2688 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2689 member assosiation NUUG&lt;/a&gt; and
2690 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2691 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2692 Bitraf&lt;/a&gt;.&lt;/p&gt;
2693
2694 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2695 welcome, and there is no fee to participate. There is on the other
2696 hand limited space, and only room for 30 people. Please put your name
2697 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2698 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2699 </description>
2700 </item>
2701
2702 <item>
2703 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2704 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2705 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2706 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2707 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2708 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2709 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2710 time to spend on it, and it took a while to find a model I believe
2711 will do the job, but two days ago the replacement finally arrived. I
2712 ended up picking a
2713 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2714 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2715 a roaming workstation, and it seemed to work flawlessly. But my
2716 second installation with encrypted disk was not as successful. More
2717 on that below.&lt;/p&gt;
2718
2719 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2720 important requirements (robust and with a good keyboard) are never
2721 listed in the feature list. But I did get good help from the search
2722 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2723 allowed me to limit the list of interesting laptops based on my other
2724 requirements. A bit surprising that SSD disk are not disks according
2725 to that search interface, so I had to drop specifying the number of
2726 disks from my search parameters. I also asked around among friends to
2727 get their impression on keyboards and robustness.&lt;/p&gt;
2728
2729 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2730 X41. I am not quite convinced about the keyboard, as it is
2731 significantly wider than my old keyboard, and I have to stretch my
2732 hand a lot more to reach the edges. But the key response is fairly
2733 good and the individual key shape is fairly easy to handle, so I hope
2734 I will get used to it. My old X40 was starting to fail, and I really
2735 needed a new laptop now. :)&lt;/p&gt;
2736
2737 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2738 visit to the BIOS during boot it disable it.&lt;/p&gt;
2739
2740 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2741 lock up during load. And this happen when installing Debian Wheezy
2742 with encrypted disk, while the disk is being filled with random data.
2743 I also tested to install Ubuntu Raring, and it happen there too if I
2744 reenable the code to fill the disk with random data (it is disabled by
2745 default in Ubuntu). And the bug with is already known. It was
2746 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2747 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2748 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2749 kernel developers as
2750 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2751 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2752 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2753 Lenovo forums, both for
2754 &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
2755 2012-11-10&lt;/a&gt; and for
2756 &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
2757 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2758 reports state that the disk lock up during use if many writes are done
2759 on the disk, so it is much no use to work around the installation
2760 problem and end up with a computer that can lock up at any moment.
2761 There is even a
2762 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2763 available&lt;/a&gt; that will lock up the hard drive after running a few
2764 minutes by writing to a file.&lt;/p&gt;
2765
2766 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2767 contacting PCHELP Norway (request 01D1FDP) which handle support
2768 requests for Lenovo, his first suggestion was to upgrade the disk
2769 firmware. Unfortunately there is no newer firmware available from
2770 Lenovo, as my disk already have the most recent one (version LF1i). I
2771 hope to hear more from him today and hope the problem can be
2772 fixed. :)&lt;/p&gt;
2773 </description>
2774 </item>
2775
2776 <item>
2777 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2778 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2779 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2780 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2781 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2782 trusty old Thinkpad X41. Unfortunately I did not have much time to
2783 spend on it, but today the replacement finally arrived. I ended up
2784 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2785 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2786 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2787 this, it is installing what I hope will be a more final installation,
2788 with a encrypted hard drive to ensure any dope head stealing it end up
2789 with an expencive door stop.&lt;/p&gt;
2790
2791 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2792 important requirements (robust and with a good keyboard) are never
2793 listed in the feature list. But I did get good help from the search
2794 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2795 allowed me to limit the list of interesting laptops based on my other
2796 requirements. A bit surprising that SSD disk are not disks, so I had
2797 to drop number of disks from my search parameters.&lt;/p&gt;
2798
2799 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2800 wider than my old keyboard, and I have to stretch my hand a lot more
2801 to reach the edges. But the key response is fairly good and the
2802 individual key shape is fairly easy to handle, so I hope I will get
2803 used to it. My old X40 was starting to fail, and I really needed a
2804 new laptop now. :)&lt;/p&gt;
2805
2806 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2807 </description>
2808 </item>
2809
2810 <item>
2811 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2812 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2813 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2814 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2815 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2816 perfectly capable of, and I have to do it manually to get things
2817 working. One such task is to find out what firmware packages are
2818 needed to get the hardware on my computer working. Most often this
2819 affect the wifi card, but some times it even affect the RAID
2820 controller or the ethernet card. Today I pushed version 0.4 of the
2821 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2822 including a new script isenkram-autoinstall-firmware handling the
2823 process of asking all the loaded kernel modules what firmware files
2824 they want, find debian packages providing these files and install the
2825 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2826
2827 &lt;p&gt;&lt;pre&gt;
2828 # isenkram-autoinstall-firmware
2829 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2830 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2831 info: locating packages with the requested firmware files
2832 info: Updating APT sources after adding non-free APT source
2833 info: trying to install firmware-ipw2x00
2834 firmware-ipw2x00
2835 firmware-ipw2x00
2836 Preconfiguring packages ...
2837 Selecting previously deselected package firmware-ipw2x00.
2838 (Reading database ... 259727 files and directories currently installed.)
2839 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2840 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2841 #
2842 &lt;/pre&gt;&lt;/p&gt;
2843
2844 &lt;p&gt;When all the requested firmware is present, a simple message is
2845 printed instead:&lt;/p&gt;
2846
2847 &lt;p&gt;&lt;pre&gt;
2848 # isenkram-autoinstall-firmware
2849 info: did not find any firmware files requested by loaded kernel modules. exiting
2850 #
2851 &lt;/pre&gt;&lt;/p&gt;
2852
2853 &lt;p&gt;It could use some polish, but it is already working well and saving
2854 me some time when setting up new machines. :)&lt;/p&gt;
2855
2856 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2857 kernel modules, and look up each one of them using modinfo, to find
2858 the firmware files listed in the module meta-information. Next, it
2859 download the Contents file from a nearby APT mirror, and search for
2860 the firmware files in this file to locate the package with the
2861 requested firmware file. If the package is in the non-free section, a
2862 non-free APT source is added and the package is installed using
2863 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2864 machine.&lt;/p&gt;
2865
2866 &lt;p&gt;I hope someone find time to implement a more polished version of
2867 this script as part of the hw-detect debian-installer module, to
2868 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2869 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2870 firmware during a PXE install when the packages already are available
2871 from the nearby Debian mirror.&lt;/p&gt;
2872 </description>
2873 </item>
2874
2875 <item>
2876 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2877 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2878 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2879 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2880 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2881 the screen just turn black when Linux boot, either during installation
2882 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2883 last few years, but only recently understood the cause. I&#39;ve seen it
2884 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2885 The reason seem to be in the wiring of some laptops. The system to
2886 control the screen background light is inverted, so when Linux try to
2887 turn the brightness fully on, it end up turning it off instead. I do
2888 not know which Linux drivers are affected, but this post is about the
2889 i915 driver used by the
2890 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2891 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2892
2893 &lt;p&gt;The problem can be worked around two ways. Either by adding
2894 i915.invert_brightness=1 as a kernel option, or by adding a file in
2895 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2896 option when it load the i915 kernel module. On Debian and Ubuntu, it
2897 can be done by running these commands as root:&lt;/p&gt;
2898
2899 &lt;pre&gt;
2900 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2901 update-initramfs -u -k all
2902 &lt;/pre&gt;
2903
2904 &lt;p&gt;Since March 2012 there is
2905 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2906 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2907 hardware have this problem, and get the driver to invert the
2908 brightness setting automatically. To use it, one need to add a row in
2909 &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
2910 intel_quirks array&lt;/a&gt; in the driver source
2911 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2912 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2913 number (vendor number 8086 is assumed) and subdevice vendor and device
2914 number.&lt;/p&gt;
2915
2916 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2917 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2918
2919 &lt;p&gt;&lt;pre&gt;
2920 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2921 3rd Gen Core processor Graphics Controller [8086:0156] \
2922 (rev 09) (prog-if 00 [VGA controller])
2923 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2924 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2925 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2926 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2927 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2928 Latency: 0
2929 Interrupt: pin A routed to IRQ 42
2930 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2931 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2932 Region 4: I/O ports at 4000 [size=64]
2933 Expansion ROM at &lt;unassigned&gt; [disabled]
2934 Capabilities: &lt;access denied&gt;
2935 Kernel driver in use: i915
2936 &lt;/pre&gt;&lt;/p&gt;
2937
2938 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2939
2940 &lt;p&gt;&lt;pre&gt;
2941 struct intel_quirk intel_quirks[] = {
2942 ...
2943 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2944 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2945 ...
2946 }
2947 &lt;/pre&gt;&lt;/p&gt;
2948
2949 &lt;p&gt;According to the kernel module instructions (as seen using
2950 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2951 invert_brightness flag should be sent to the
2952 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2953 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2954 developers. But my email about the laptop sent 2013-06-03 have not
2955 yet shown up in
2956 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2957 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2958 emails from non-subscribers. Because of this, I sent my patch also to
2959 the Debian bug tracking system instead as
2960 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2961 sure the patch is not lost.&lt;/p&gt;
2962
2963 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2964 with this problem working properly with Linux. If you use Gnome, your
2965 worries should be over at this point. But if you use KDE, there is
2966 something in KDE ignoring the invert_brightness setting and turning on
2967 the screen during login. I&#39;ve reported it to Debian as
2968 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2969 have no idea yet how to figure out exactly what subsystem is doing
2970 this. Perhaps you can help? Perhaps you know what the Gnome
2971 developers did to handle this, and this can give a clue to the KDE
2972 developers? Or you know where in KDE the screen brightness is changed
2973 during login? If so, please update the BTS report (or get in touch if
2974 you do not know how to update BTS).&lt;/p&gt;
2975
2976 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2977 acpi_backlight=vendor, to disable ACPI backlight support completely,
2978 as the ACPI information on the machine is trash and it is better to
2979 leave it to the intel video driver to control the screen
2980 backlight.&lt;/p&gt;
2981 </description>
2982 </item>
2983
2984 <item>
2985 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2986 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2987 <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>
2988 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2989 <description>&lt;p&gt;Two days ago, I asked
2990 &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
2991 I could install Linux on a Packard Bell EasyNote LV computer
2992 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2993 with the obstacles put in the way of Linux users on a laptop with UEFI
2994 and Windows 8.&lt;/p&gt;
2995
2996 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2997 secure booting or fast boot. I suspect fast boot was the problem,
2998 causing the firmware to boot directly from HD without considering any
2999 key presses and alternative devices, but do not know UEFI settings
3000 enough to tell.&lt;/p&gt;
3001
3002 &lt;p&gt;There is no way to install Linux on the machine in question without
3003 opening the box and disconnecting the hard drive! This is as far as I
3004 can tell, the only way to get access to the firmware setup menu
3005 without accepting the Windows 8 license agreement. I am told (and
3006 found description on how to) that it is possible to configure the
3007 firmware setup once booted into Windows 8. But as I believe the terms
3008 of that agreement are completely unacceptable, accepting the license
3009 was never an alternative. I do not enter agreements I do not intend
3010 to follow.&lt;/p&gt;
3011
3012 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3013 waste many hours on this, but luckily there was a way to get it to
3014 work. But I would not recommend it to anyone planning to run Linux on
3015 it, and I have become sceptical to Windows 8 certified laptops. Is
3016 this the way Linux will be forced out of the market place, by making
3017 it close to impossible for &quot;normal&quot; users to install Linux without
3018 accepting the Microsoft Windows license terms? Or at least not
3019 without risking to loose the warranty?&lt;/p&gt;
3020
3021 &lt;p&gt;I&#39;ve updated the
3022 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3023 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3024 do not have to struggle as much as I did to get Linux into the
3025 machine.&lt;/p&gt;
3026
3027 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3028 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3029 </description>
3030 </item>
3031
3032 <item>
3033 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3034 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3035 <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>
3036 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3037 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3038 new laptops for my parents and a few others. I bought Packard Bell
3039 Easynote LV to run Kubuntu on and use as their home computer. But I
3040 am completely unable to figure out how to install Linux on it. The
3041 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3042 instead of a BIOS to boot.&lt;/p&gt;
3043
3044 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3045 to get it to boot the Linux installer from my USB stick. I have yet
3046 to try the DVD install, and still hope it will work. when I turn on
3047 the computer, there is no information on what buttons to press to get
3048 the normal boot menu. I expect to get some boot menu to select PXE or
3049 USB stick booting. When booting, it first ask for the language to
3050 use, then for some regional settings, and finally if I will accept the
3051 Windows 8 terms of use. As these terms are completely unacceptable to
3052 me, I have no other choice but to turn off the computer and try again
3053 to get it to boot the Linux installer.&lt;/p&gt;
3054
3055 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3056 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3057 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3058 installed on this machine, please get in touch or update that wiki
3059 page. If I can&#39;t find a way to install Linux, I will have to return
3060 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3061
3062 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3063 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3064 on new Laptops?&lt;/p&gt;
3065 </description>
3066 </item>
3067
3068 <item>
3069 <title>How to transform a Debian based system to a Debian Edu installation</title>
3070 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3071 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3072 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3073 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3074 an operating system based on Debian intended for use in schools. It
3075 contain a turn-key solution for the computer network provided to
3076 pupils in the primary schools. It provide both the central server,
3077 network boot servers and desktop environments with heaps of
3078 educational software. The project was founded almost 12 years ago,
3079 2001-07-02. If you want to support the project, which is in need for
3080 cash to fund developer gatherings and other project related activity,
3081 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3082 donate some money&lt;/a&gt;.
3083
3084 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3085 lists and elsewhere, is the question on how to transform a Debian or
3086 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3087 hard, and last week I wrote a script to replicate the steps done by
3088 the Debian Edu installer.&lt;/p&gt;
3089
3090 &lt;p&gt;The script,
3091 &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;
3092 in the debian-edu-config package, will go through these six steps and
3093 transform an existing Debian Wheezy or Ubuntu (untested) installation
3094 into a Debian Edu Workstation:&lt;/p&gt;
3095
3096 &lt;ol&gt;
3097
3098 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3099 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3100 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3101 our configuration.&lt;/li&gt;
3102 &lt;li&gt;Preseed debconf database with profile setup in
3103 /etc/debian-edu/config, and run tasksel to install packages
3104 according to the profile specified in the config above,
3105 overriding some of the Debian automation machinery.&lt;/li&gt;
3106 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3107 that could not be done using preseeding.&lt;/li&gt;
3108 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3109
3110 &lt;/ol&gt;
3111
3112 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3113 replicated like this. Disk partitioning and LVM setup, for example.
3114 So this script just assume there is enough disk space to install all
3115 the needed packages.&lt;/p&gt;
3116
3117 &lt;p&gt;The script was created to help a Debian Edu student working on
3118 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3119 Debian Edu client, and using it he can take the existing
3120 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3121 transform it into a fully functioning Debian Edu Workstation (or
3122 Roaming Workstation, or whatever :).&lt;/p&gt;
3123
3124 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3125 If a LXDE based Roaming workstation is wanted instead, modify the
3126 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3127
3128 &lt;p&gt;&lt;pre&gt;
3129 PROFILE=&quot;Roaming-Workstation&quot;
3130 DESKTOP=&quot;lxde&quot;
3131 &lt;/pre&gt;&lt;/p&gt;
3132
3133 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3134 the cloud, by starting with a virtual Debian installation at some
3135 virtual hosting service and setting up all the services on first
3136 boot.&lt;/p&gt;
3137 </description>
3138 </item>
3139
3140 <item>
3141 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3142 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3143 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3144 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3145 <description>&lt;P&gt;In January,
3146 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3147 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3148 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3149 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3150 marvellous construction system from Denmark. We also created
3151 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3152 a place to take notes and write down our plans and hopes. And several
3153 people showed up to help. I was very happy to see the effect of my
3154 call. Since the small start, we have a debtags tag
3155 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3156 tag for LEGO related packages, and now count 10 packages related to
3157 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3158
3159 &lt;p&gt;&lt;table&gt;
3160 &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;
3161 &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;
3162 &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;
3163 &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;
3164 &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;
3165 &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;
3166 &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;
3167 &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;
3168 &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;
3169 &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;
3170 &lt;/table&gt;&lt;/p&gt;
3171
3172 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3173 currently available in Jessie/testing. leocad is so far only
3174 available in experimental.&lt;/p&gt;
3175
3176 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3177 adding the rest of the great free software tools available on Linux
3178 for LEGO designers.&lt;/p&gt;
3179 </description>
3180 </item>
3181
3182 <item>
3183 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3184 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3186 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3187 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3188 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3189 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3190 Debian release, and I expect to move my machines at home over to it fairly
3191 soon.&lt;/p&gt;
3192
3193 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3194 in particular make me very happy to see included. The
3195 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3196 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3197 included for the first time. Alongside similar programs like
3198 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3199 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3200 it allow for visual programming where syntax errors can not happen,
3201 and a friendly programming environment for learning to control the
3202 computer. Scratch will also be included in the next release of Debian
3203 Edu.&lt;/a&gt;
3204
3205 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3206 Edu/Skolelinux release too. The
3207 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3208 alpha release&lt;/a&gt; went out last week, and the next should soon
3209 follow.&lt;p&gt;
3210 </description>
3211 </item>
3212
3213 <item>
3214 <title>Isenkram 0.2 finally in the Debian archive</title>
3215 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3216 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3217 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3218 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3219 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3220 for many months. I uploaded it to the Debian experimental suite
3221 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3222
3223 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3224 install to work with a pluggable hardware device. The suggestion pop
3225 up when the device is plugged in. For example if a Lego Mindstorm NXT
3226 is inserted, it will suggest to install the program needed to program
3227 the NXT controller. Give it a go, and report bugs and suggestions to
3228 BTS. :)&lt;/p&gt;
3229 </description>
3230 </item>
3231
3232 <item>
3233 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3234 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3235 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3236 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3237 <description>&lt;p&gt;My
3238 &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
3239 bitcoin related blog post&lt;/a&gt; mentioned that the new
3240 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3241 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3242 2013-01-19, and have been available in unstable since then. It was
3243 automatically copied to Ubuntu, and is available in their Raring
3244 version too.&lt;/p&gt;
3245
3246 &lt;p&gt;But there is a strange problem with the build that block this new
3247 version from being available on the i386 and kfreebsd-i386
3248 architectures. For some strange reason, the autobuilders in Debian
3249 for these architectures fail to run the test suite on these
3250 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3251 We are so far unable to reproduce it when building it manually, and
3252 no-one have been able to propose a fix. If you got an idea what is
3253 failing, please let us know via the BTS.&lt;/p&gt;
3254
3255 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3256 I often run low on disk space, is the fact that the client will exit
3257 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3258 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3259 it. :)&lt;/p&gt;
3260
3261 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3262 activities, please send Bitcoin donations to my address
3263 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3264 </description>
3265 </item>
3266
3267 <item>
3268 <title>Welcome to the world, Isenkram!</title>
3269 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3271 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3272 <description>&lt;p&gt;Yesterday, I
3273 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3274 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3275 pluggable hardware devices, which I
3276 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3277 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3278 up, and caused me to really want to to open up the development to more
3279 people. But before I did this, I want to come up with a sensible name
3280 for this project. Today I finally decided on a new name, and I have
3281 renamed the project from hw-support-handler to this new name. In the
3282 process, I moved the source to git and made it available as a
3283 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3284 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3285 To fetch and build the latest version of the source, use&lt;/p&gt;
3286
3287 &lt;pre&gt;
3288 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3289 cd isenkram &amp;&amp; git-buildpackage -us -uc
3290 &lt;/pre&gt;
3291
3292 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3293 want to hack on the source or improve the package, please go ahead.
3294 But please talk to me first on IRC or via email before you do major
3295 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3296
3297 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3298 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3299 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3300 the German word eisenkram, for those that are familiar with that
3301 word.&lt;/p&gt;
3302
3303 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3304 instructions, to avoid confusing people with an error from the signing
3305 process.&lt;/p&gt;
3306
3307 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3308 clone argument to avoid the need for authentication.&lt;/p&gt;
3309 </description>
3310 </item>
3311
3312 <item>
3313 <title>First prototype ready making hardware easier to use in Debian</title>
3314 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3315 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3316 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3317 <description>&lt;p&gt;Early this month I set out to try to
3318 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3319 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3320 prototype is working, and it is ready for a larger audience. To test
3321 it, fetch the
3322 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3323 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3324 package. You might have to log out and in again activate the
3325 autostart script.&lt;/p&gt;
3326
3327 &lt;p&gt;The design is simple:&lt;/p&gt;
3328
3329 &lt;ul&gt;
3330
3331 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3332 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3333
3334 &lt;li&gt;This program listen for kernel events about new hardware (directly
3335 from the kernel like udev does), not using HAL dbus events as I
3336 initially did.&lt;/li&gt;
3337
3338 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3339 the APT database, a database
3340 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3341 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3342
3343 &lt;li&gt;If a package is mapped to the hardware in question, the package
3344 isn&#39;t installed yet and this is the first time the hardware was
3345 plugged in, show a desktop notification suggesting to install the
3346 package or packages.&lt;/li&gt;
3347
3348 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3349 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3350
3351 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3352 package while showing progress information in a window.&lt;/li&gt;
3353
3354 &lt;/ul&gt;
3355
3356 &lt;p&gt;I still need to come up with a better name for the system. Here
3357 are some screen shots showing the prototype in action. First the
3358 notification, then the password request, and finally the request to
3359 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3360
3361 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3362 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3363 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3364 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3365 &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;
3366
3367 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3368 is already useful. The database of hardware to package mappings also
3369 need more work. It is currently compatible with the Ubuntu way of
3370 storing such information in the package control file, but could be
3371 changed to use other formats instead or in addition to the current
3372 method. I&#39;ve dropped the use of discover for this mapping, as the
3373 modalias approach is more flexible and easier to use on Linux as long
3374 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3375
3376 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3377 here is the command required to check out and build the source: Use
3378 &#39;&lt;tt&gt;svn checkout
3379 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3380 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3381 devscripts package.&lt;/p&gt;
3382
3383 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3384 renamed to Isenkram and the source moved from the Debian Edu
3385 subversion repository to a Debian collab-maint git repository. See
3386 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3387 instructions&lt;/a&gt; for details.&lt;/p&gt;
3388 </description>
3389 </item>
3390
3391 <item>
3392 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3393 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3394 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3395 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3396 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3397 suddenly in bed. With a quiet whimper, it went completely quiet and
3398 black. The power button was no longer able to turn it on. It was a
3399 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3400 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3401 Compaq I had before that. Now I need to find a replacement. To keep
3402 going during Christmas, I moved the one year old SSD disk to my old
3403 X40 where it fitted (only one I had left that could use it), but it is
3404 not a durable solution.
3405
3406 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3407 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3408
3409 &lt;ul&gt;
3410
3411 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3412 than A4).&lt;/li&gt;
3413 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3414 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3415 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3416 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3417 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3418 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3419 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3420 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3421 size).&lt;/li&gt;
3422 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3423 X.org packages.&lt;/li&gt;
3424 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3425 the time).
3426
3427 &lt;/ul&gt;
3428
3429 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3430 list. The reason is simply that the specifications on laptops the
3431 last 10-15 years have been sufficient for my needs, and I have to look
3432 at other features to choose my laptop. But are there still made as
3433 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3434 robust, and Thinkpads seem to be heading in the wrong direction since
3435 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3436 still be useful.&lt;/p&gt;
3437
3438 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3439 external keyboard? I&#39;ll have to check the
3440 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3441 well-supported laptops, or perhaps just buy one preinstalled from one
3442 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3443 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3444 </description>
3445 </item>
3446
3447 <item>
3448 <title>How to find a browser plugin supporting a given MIME type</title>
3449 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3451 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3452 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3453 install to get support for a given MIME type. Thanks to
3454 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3455 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3456 Unfortunately, not very many packages provide the needed meta
3457 information, Anyway, here is a small script to look up all browser
3458 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3459
3460 &lt;pre&gt;
3461 #!/usr/bin/python
3462 import sys
3463 import apt
3464 def pkgs_handling_mimetype(mimetype):
3465 cache = apt.Cache()
3466 cache.open(None)
3467 thepkgs = []
3468 for pkg in cache:
3469 version = pkg.candidate
3470 if version is None:
3471 version = pkg.installed
3472 if version is None:
3473 continue
3474 record = version.record
3475 if not record.has_key(&#39;Npp-MimeType&#39;):
3476 continue
3477 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3478 for t in mime_types:
3479 t = t.rstrip().strip()
3480 if t == mimetype:
3481 thepkgs.append(pkg.name)
3482 return thepkgs
3483 mimetype = &quot;audio/ogg&quot;
3484 if 1 &lt; len(sys.argv):
3485 mimetype = sys.argv[1]
3486 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3487 for pkg in pkgs_handling_mimetype(mimetype):
3488 print &quot; %s&quot; %pkg
3489 &lt;/pre&gt;
3490
3491 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3492
3493 &lt;pre&gt;
3494 % ./apt-find-browserplug-for-mimetype
3495 Browser plugin packages supporting audio/ogg:
3496 gecko-mediaplayer
3497 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3498 Browser plugin packages supporting application/x-shockwave-flash:
3499 browser-plugin-gnash
3500 %
3501 &lt;/pre&gt;
3502
3503 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3504 itself to query for plugins and propose to install the needed
3505 packages. It would be great if Debian supported such feature too. Is
3506 anyone working on adding it?&lt;/p&gt;
3507
3508 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3509 request for icweasel support for this feature is
3510 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3511 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3512 of manpower and wish for a different design is the reason thus feature
3513 is not yet in iceweasel from Debian.&lt;/p&gt;
3514 </description>
3515 </item>
3516
3517 <item>
3518 <title>What is the most supported MIME type in Debian?</title>
3519 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3520 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3521 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3522 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3523 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3524 proposal to make it possible for a Desktop application to propose to
3525 the user some package to install to gain support for a given MIME
3526 type, font, library etc. that is currently missing. With such
3527 mechanism in place, it would be possible for the desktop to
3528 automatically propose and install leocad if some LDraw file is
3529 downloaded by the browser.&lt;/p&gt;
3530
3531 &lt;p&gt;To get some idea about the current content of the archive, I decided
3532 to write a simple program to extract all .desktop files from the
3533 Debian archive and look up the claimed MIME support there. The result
3534 can be found on the
3535 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3536 site&lt;/a&gt;. Using the collected information, it become possible to
3537 answer the question in the title. Here are the 20 most supported MIME
3538 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3539 The complete list is available from the link above.&lt;/p&gt;
3540
3541 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3542
3543 &lt;pre&gt;
3544 count MIME type
3545 ----- -----------------------
3546 32 text/plain
3547 30 audio/mpeg
3548 29 image/png
3549 28 image/jpeg
3550 27 application/ogg
3551 26 audio/x-mp3
3552 25 image/tiff
3553 25 image/gif
3554 22 image/bmp
3555 22 audio/x-wav
3556 20 audio/x-flac
3557 19 audio/x-mpegurl
3558 18 video/x-ms-asf
3559 18 audio/x-musepack
3560 18 audio/x-mpeg
3561 18 application/x-ogg
3562 17 video/mpeg
3563 17 audio/x-scpls
3564 17 audio/ogg
3565 16 video/x-ms-wmv
3566 &lt;/pre&gt;
3567
3568 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3569
3570 &lt;pre&gt;
3571 count MIME type
3572 ----- -----------------------
3573 33 text/plain
3574 32 image/png
3575 32 image/jpeg
3576 29 audio/mpeg
3577 27 image/gif
3578 26 image/tiff
3579 26 application/ogg
3580 25 audio/x-mp3
3581 22 image/bmp
3582 21 audio/x-wav
3583 19 audio/x-mpegurl
3584 19 audio/x-mpeg
3585 18 video/mpeg
3586 18 audio/x-scpls
3587 18 audio/x-flac
3588 18 application/x-ogg
3589 17 video/x-ms-asf
3590 17 text/html
3591 17 audio/x-musepack
3592 16 image/x-xbitmap
3593 &lt;/pre&gt;
3594
3595 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3596
3597 &lt;pre&gt;
3598 count MIME type
3599 ----- -----------------------
3600 31 text/plain
3601 31 image/png
3602 31 image/jpeg
3603 29 audio/mpeg
3604 28 application/ogg
3605 27 image/gif
3606 26 image/tiff
3607 26 audio/x-mp3
3608 23 audio/x-wav
3609 22 image/bmp
3610 21 audio/x-flac
3611 20 audio/x-mpegurl
3612 19 audio/x-mpeg
3613 18 video/x-ms-asf
3614 18 video/mpeg
3615 18 audio/x-scpls
3616 18 application/x-ogg
3617 17 audio/x-musepack
3618 16 video/x-ms-wmv
3619 16 video/x-msvideo
3620 &lt;/pre&gt;
3621
3622 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3623 information mentioned in DEP-11. I have not yet had time to look at
3624 it, but hope the PackageKit people in Debian are on top of these
3625 issues.&lt;/p&gt;
3626
3627 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3628 discovering a typo in my script.&lt;/p&gt;
3629 </description>
3630 </item>
3631
3632 <item>
3633 <title>Using modalias info to find packages handling my hardware</title>
3634 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3635 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3636 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3637 <description>&lt;p&gt;Yesterday, I wrote about the
3638 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3639 values provided by the Linux kernel&lt;/a&gt; following my hope for
3640 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3641 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3642 modalias values attached to package names can be used to map packages
3643 to hardware. This allow the system to look up and suggest relevant
3644 packages when I plug in some new hardware into my machine, and replace
3645 discover and discover-data as the database used to map hardware to
3646 packages.&lt;/p&gt;
3647
3648 &lt;p&gt;I create a modaliases file with entries like the following,
3649 containing package name, kernel module name (if relevant, otherwise
3650 the package name) and globs matching the relevant hardware
3651 modalias.&lt;/p&gt;
3652
3653 &lt;p&gt;&lt;blockquote&gt;
3654 Package: package-name
3655 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3656 &lt;/blockquote&gt;&lt;/p&gt;
3657
3658 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3659 for a given modalias value using this file.&lt;/p&gt;
3660
3661 &lt;p&gt;An entry like this would suggest the video and picture application
3662 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3663
3664 &lt;p&gt;&lt;blockquote&gt;
3665 Package: cheese
3666 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3667 &lt;/blockquote&gt;&lt;/p&gt;
3668
3669 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3670 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3671
3672 &lt;p&gt;&lt;blockquote&gt;
3673 Package: pcmciautils
3674 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3675 &lt;/blockquote&gt;&lt;/p&gt;
3676
3677 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3678 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3679
3680 &lt;p&gt;&lt;blockquote&gt;
3681 Package: colorhug-client
3682 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3683 &lt;/blockquote&gt;&lt;/p&gt;
3684
3685 &lt;p&gt;I believe the format is compatible with the format of the Packages
3686 file in the Debian archive. Ubuntu already uses their Packages file
3687 to store their mappings from packages to hardware.&lt;/p&gt;
3688
3689 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3690 announce the hardware it support in a way my prototype understand.
3691 This allow those publishing packages in an APT source outside the
3692 Debian archive as well as those backporting packages to make sure the
3693 hardware mapping are included in the package meta information. I&#39;ve
3694 tested such header in the pymissile package, and its modalias mapping
3695 is working as it should with my prototype. It even made it to Ubuntu
3696 Raring.&lt;/p&gt;
3697
3698 &lt;p&gt;To test if it was possible to look up supported hardware using only
3699 the shell tools available in the Debian installer, I wrote a shell
3700 implementation of the lookup code. The idea is to create files for
3701 each modalias and let the shell do the matching. Please check out and
3702 try the
3703 &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;
3704 shell script. It run without any extra dependencies and fetch the
3705 hardware mappings from the Debian archive and the subversion
3706 repository where I currently work on my prototype.&lt;/p&gt;
3707
3708 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3709 install yubikey-personalization:&lt;/p&gt;
3710
3711 &lt;p&gt;&lt;blockquote&gt;
3712 % ./hw-support-lookup
3713 &lt;br&gt;yubikey-personalization
3714 &lt;br&gt;%
3715 &lt;/blockquote&gt;&lt;/p&gt;
3716
3717 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3718 propose to install the pcmciautils package:&lt;/p&gt;
3719
3720 &lt;p&gt;&lt;blockquote&gt;
3721 % ./hw-support-lookup
3722 &lt;br&gt;pcmciautils
3723 &lt;br&gt;%
3724 &lt;/blockquote&gt;&lt;/p&gt;
3725
3726 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3727 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3728 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3729
3730 &lt;p&gt;It could be possible to generate several of the mappings between
3731 packages and hardware. One source would be to look at packages with
3732 kernel modules, ie packages with *.ko files in /lib/modules/, and
3733 extract their modalias information. Another would be to look at
3734 packages with udev rules, ie packages with files in
3735 /lib/udev/rules.d/, and extract their vendor/model information to
3736 generate a modalias matching rule. I have not tested any of these to
3737 see if it work.&lt;/p&gt;
3738
3739 &lt;p&gt;If you want to help implementing a system to let us propose what
3740 packages to install when new hardware is plugged into a Debian
3741 machine, please send me an email or talk to me on
3742 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3743 </description>
3744 </item>
3745
3746 <item>
3747 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3748 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3749 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3750 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3751 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3752 information, to find the packages that support a given piece of
3753 hardware, I refreshed my memory regarding modalias values, and decided
3754 to document the details. Here are my findings so far, also available
3755 in
3756 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3757 Debian Edu subversion repository&lt;/a&gt;:
3758
3759 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3760
3761 &lt;p&gt;This document try to explain what the different types of modalias
3762 values stands for. It is in part based on information from
3763 &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;,
3764 &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;,
3765 &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
3766 &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;.
3767
3768 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3769 this shell script:&lt;/p&gt;
3770
3771 &lt;pre&gt;
3772 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3773 &lt;/pre&gt;
3774
3775 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3776 using modinfo:&lt;/p&gt;
3777
3778 &lt;pre&gt;
3779 % /sbin/modinfo psmouse | grep alias:
3780 alias: serio:ty05pr*id*ex*
3781 alias: serio:ty01pr*id*ex*
3782 %
3783 &lt;/pre&gt;
3784
3785 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3786
3787 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3788 Bridge memory controller:&lt;/p&gt;
3789
3790 &lt;p&gt;&lt;blockquote&gt;
3791 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3792 &lt;/blockquote&gt;&lt;/p&gt;
3793
3794 &lt;p&gt;This represent these values:&lt;/p&gt;
3795
3796 &lt;pre&gt;
3797 v 00008086 (vendor)
3798 d 00002770 (device)
3799 sv 00001028 (subvendor)
3800 sd 000001AD (subdevice)
3801 bc 06 (bus class)
3802 sc 00 (bus subclass)
3803 i 00 (interface)
3804 &lt;/pre&gt;
3805
3806 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3807 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3808 0600. The 0600 class is a host bridge. Other useful bus values are
3809 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3810
3811 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3812 means.&lt;/p&gt;
3813
3814 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3815
3816 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3817 USB hub in a laptop:&lt;/p&gt;
3818
3819 &lt;p&gt;&lt;blockquote&gt;
3820 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3821 &lt;/blockquote&gt;&lt;/p&gt;
3822
3823 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3824
3825 &lt;pre&gt;
3826 v 1D6B (device vendor)
3827 p 0001 (device product)
3828 d 0206 (bcddevice)
3829 dc 09 (device class)
3830 dsc 00 (device subclass)
3831 dp 00 (device protocol)
3832 ic 09 (interface class)
3833 isc 00 (interface subclass)
3834 ip 00 (interface protocol)
3835 &lt;/pre&gt;
3836
3837 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3838 class is in the interface class section. For a simple USB web camera,
3839 these alias entries show up:&lt;/p&gt;
3840
3841 &lt;p&gt;&lt;blockquote&gt;
3842 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3843 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3844 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3845 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3846 &lt;/blockquote&gt;&lt;/p&gt;
3847
3848 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3849 camera), 0101 is audio control device and 0102 is audio streaming (aka
3850 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3851
3852 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3853
3854 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3855 receiver in a Thinkpad X40:&lt;/p&gt;
3856
3857 &lt;p&gt;&lt;blockquote&gt;
3858 acpi:IBM0071:PNP0511:
3859 &lt;/blockquote&gt;&lt;/p&gt;
3860
3861 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3862
3863 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3864
3865 &lt;p&gt;The DMI table contain lots of information about the computer case
3866 and model. This is an entry for a IBM Thinkpad X40, fetched from
3867 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3868
3869 &lt;p&gt;&lt;blockquote&gt;
3870 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3871 &lt;/blockquote&gt;&lt;/p&gt;
3872
3873 &lt;p&gt;The values present are&lt;/p&gt;
3874
3875 &lt;pre&gt;
3876 bvn IBM (BIOS vendor)
3877 bvr 1UETB6WW(1.66) (BIOS version)
3878 bd 06/15/2005 (BIOS date)
3879 svn IBM (system vendor)
3880 pn 2371H4G (product name)
3881 pvr ThinkPadX40 (product version)
3882 rvn IBM (board vendor)
3883 rn 2371H4G (board name)
3884 rvr NotAvailable (board version)
3885 cvn IBM (chassis vendor)
3886 ct 10 (chassis type)
3887 cvr NotAvailable (chassis version)
3888 &lt;/pre&gt;
3889
3890 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3891 found in the dmidecode source:&lt;/p&gt;
3892
3893 &lt;pre&gt;
3894 3 Desktop
3895 4 Low Profile Desktop
3896 5 Pizza Box
3897 6 Mini Tower
3898 7 Tower
3899 8 Portable
3900 9 Laptop
3901 10 Notebook
3902 11 Hand Held
3903 12 Docking Station
3904 13 All In One
3905 14 Sub Notebook
3906 15 Space-saving
3907 16 Lunch Box
3908 17 Main Server Chassis
3909 18 Expansion Chassis
3910 19 Sub Chassis
3911 20 Bus Expansion Chassis
3912 21 Peripheral Chassis
3913 22 RAID Chassis
3914 23 Rack Mount Chassis
3915 24 Sealed-case PC
3916 25 Multi-system
3917 26 CompactPCI
3918 27 AdvancedTCA
3919 28 Blade
3920 29 Blade Enclosing
3921 &lt;/pre&gt;
3922
3923 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3924 table. For example my home server is a tower, but the DMI modalias
3925 claim it is a desktop.&lt;/p&gt;
3926
3927 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3928
3929 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3930 test machine:&lt;/p&gt;
3931
3932 &lt;p&gt;&lt;blockquote&gt;
3933 serio:ty01pr00id00ex00
3934 &lt;/blockquote&gt;&lt;/p&gt;
3935
3936 &lt;p&gt;The values present are&lt;/p&gt;
3937
3938 &lt;pre&gt;
3939 ty 01 (type)
3940 pr 00 (prototype)
3941 id 00 (id)
3942 ex 00 (extra)
3943 &lt;/pre&gt;
3944
3945 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3946 the valid values are.&lt;/p&gt;
3947
3948 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3949
3950 &lt;p&gt;There are heaps of other modalias subtypes according to
3951 file2alias.c. There is the rest of the list from that source: amba,
3952 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3953 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3954 vmbus, x86cpu and zorro. I did not spend time documenting all of
3955 these, as they do not seem relevant for my intended use with mapping
3956 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3957
3958 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3959
3960 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3961 one can use the following shell script:&lt;/p&gt;
3962
3963 &lt;pre&gt;
3964 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3965 echo &quot;$id&quot; ; \
3966 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3967 done
3968 &lt;/pre&gt;
3969
3970 &lt;p&gt;The output can look like this (only the first few entries as the
3971 list is very long on my test machine):&lt;/p&gt;
3972
3973 &lt;pre&gt;
3974 acpi:ACPI0003:
3975 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3976 acpi:device:
3977 FATAL: Module acpi:device: not found.
3978 acpi:IBM0068:
3979 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3980 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3981 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3982 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3983 acpi:IBM0071:PNP0511:
3984 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3985 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3986 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3987 [...]
3988 &lt;/pre&gt;
3989
3990 &lt;p&gt;If you want to help implementing a system to let us propose what
3991 packages to install when new hardware is plugged into a Debian
3992 machine, please send me an email or talk to me on
3993 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3994
3995 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3996 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3997 in /sys/ with space in them.&lt;/p&gt;
3998 </description>
3999 </item>
4000
4001 <item>
4002 <title>Moved the pymissile Debian packaging to collab-maint</title>
4003 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4004 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4005 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4006 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4007 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4008 Launcher and updated the Debian package
4009 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4010 sure udev will fix the device permissions when it is plugged in. I
4011 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4012 hopefully make the package be proposed by jockey in Ubuntu when a user
4013 plug in his rocket launcher. In the process I moved the source to a
4014 git repository under collab-maint, to make it easier for any DD to
4015 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4016 is not very active, but the software still work for me even after five
4017 years of relative silence. The new git repository is not listed in
4018 the uploaded package yet, because I want to test the other changes a
4019 bit more before I upload the new version. If you want to check out
4020 the new version with a .desktop file included, visit the
4021 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4022 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4023 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4024 </description>
4025 </item>
4026
4027 <item>
4028 <title>Lets make hardware dongles easier to use in Debian</title>
4029 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4030 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4031 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4032 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4033 general, is that there is a great package management system with the
4034 ability to automatically install software packages by downloading them
4035 from the distribution mirrors, but no way to get it to automatically
4036 install the packages I need to use the hardware I plug into my
4037 machine. Even if the package to use it is easily available from the
4038 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4039 suggest to automatically install the python-nxt, nbc and t2n packages
4040 I need to talk to it. When I plug in a Yubikey, it could propose the
4041 yubikey-personalization package. The information required to do this
4042 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4043
4044 &lt;p&gt;Some years ago, I proposed to
4045 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4046 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4047 simple:
4048
4049 &lt;ul&gt;
4050
4051 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4052 starting when a user log in.&lt;/li&gt;
4053
4054 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4055 hardware is inserted into the computer.&lt;/li&gt;
4056
4057 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4058 database mapping to packages, and take note of any non-installed
4059 packages.&lt;/li&gt;
4060
4061 &lt;li&gt;Show a message to the user proposing to install the discovered
4062 package, and make it easy to install it.&lt;/li&gt;
4063
4064 &lt;/ul&gt;
4065
4066 &lt;p&gt;I am not sure what the best way to implement this is, but my
4067 initial idea was to use dbus events to discover new hardware, the
4068 discover database to find packages and
4069 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4070 packages.&lt;/p&gt;
4071
4072 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4073 draft package is now checked into
4074 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4075 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4076 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4077 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4078 the relevant packages in Debian, and uploaded a new version
4079 2.2013.01.09 to unstable. I also discovered that the current
4080 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4081 package in Debian no longer discovered any USB devices, because
4082 /proc/bus/usb/devices is no longer present. I ported it to use
4083 libusb as a fall back option to get it working. The fixed package
4084 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4085 because of the freeze).&lt;/p&gt;
4086
4087 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4088 desktop notification to show up (only once, the first time it is
4089 inserted):&lt;/p&gt;
4090
4091 &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;
4092
4093 &lt;p&gt;For this prototype to be really useful, some way to automatically
4094 install the proposed packages by pressing the &quot;Please install
4095 program(s)&quot; button should to be implemented.&lt;/p&gt;
4096
4097 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4098 happen, please help me update the discover-data database with mappings
4099 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4100 list the package you would like to have installed when a given
4101 hardware device is inserted into your computer, and report bugs using
4102 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4103 such mapping, please let me know.&lt;/p&gt;
4104
4105 &lt;p&gt;This prototype need more work, and there are several questions that
4106 should be considered before it is ready for production use. Is dbus
4107 the correct way to detect new hardware? At the moment I look for HAL
4108 dbus events on the system bus, because that is the events I could see
4109 on my Debian Squeeze KDE desktop. Are there better events to use?
4110 How should the user be notified? Is the desktop notification
4111 mechanism the best option, or should the background daemon raise a
4112 popup instead? How should packages be installed? When should they
4113 not be installed?&lt;/p&gt;
4114
4115 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4116 please send me an email. :)&lt;/p&gt;
4117 </description>
4118 </item>
4119
4120 <item>
4121 <title>New IRC channel for LEGO designers using Debian</title>
4122 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4123 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4124 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4125 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4126 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4127 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4128 discovered I had to build all the tools myself because none were
4129 already in Debian Squeeze. If Debian support for LEGO is something
4130 you care about, please join me on the IRC channel
4131 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4132 irc.debian.org). There is a lot that could be done to improve the
4133 Debian support for LEGO designers. For example both CAD software
4134 and Mindstorm compilers are missing. :)&lt;/p&gt;
4135
4136 &lt;p&gt;Update 2012-01-03: A
4137 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4138 including links to Lego related packages is now available.&lt;/p&gt;
4139 </description>
4140 </item>
4141
4142 <item>
4143 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4144 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4145 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4146 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4147 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4148 year! I hope next year will prove to be a good year.&lt;/p&gt;
4149
4150 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4151 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4152 between each other with minimal overhead, is a very interesting
4153 experiment. And as I wrote a few days ago, the bitcoin situation in
4154 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4155 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4156 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4157 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4158 for one of the ftpmasters to approve the new bitcoin-qt package
4159 name.&lt;/p&gt;
4160
4161 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4162 team in Debian, you can easily test the package in Debian Squeeze
4163 using the following steps to get a set of working packages:&lt;/p&gt;
4164
4165 &lt;blockquote&gt;&lt;pre&gt;
4166 git clone git://git.debian.org/git/collab-maint/bitcoin
4167 cd bitcoin
4168 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4169 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4170 &lt;/pre&gt;&lt;/blockquote&gt;
4171
4172 &lt;p&gt;You might have to install some build dependencies as well. The
4173 list of commands should give you two packages, bitcoind and
4174 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4175 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4176 around 5.6 GiB of data on my machine at the moment. Make sure your
4177 ~/.bitcoin/ directory have lots of spare room if you want to download
4178 all the blocks. The client will warn if the disk is getting full, so
4179 there is not really a problem if you got too little room, but you will
4180 not be able to get all the features out of the client.&lt;/p&gt;
4181
4182 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4183 activities, please send Bitcoin donations to my address
4184 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4185 </description>
4186 </item>
4187
4188 <item>
4189 <title>A word on bitcoin support in Debian</title>
4190 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4192 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4193 <description>&lt;p&gt;It has been a while since I wrote about
4194 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4195 peer-to-peer based crypto-currency, and the reason is simply that I
4196 have been busy elsewhere. But two days ago, I started looking at the
4197 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4198 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4199 is now maintained by a
4200 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4201 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4202 owe a huge thank you to all these team members. :)
4203 But I was sad to discover that the bitcoin client is missing in
4204 Wheezy. It is only available in Sid (and an outdated client from
4205 backports). The client had several RC bugs registered in BTS blocking
4206 it from entering testing. To try to help the team and improve the
4207 situation, I spent some time providing patches and triaging the bug
4208 reports. I also had a look at the bitcoin package available from Matt
4209 Corallo in a
4210 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4211 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4212 Debian package.&lt;/p&gt;
4213
4214 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4215 IRC, I pushed several patches into the collab-maint git repository to
4216 improve the package. It now contains fixes for the RC issues (not from
4217 me, but fixed by Scott Howard), build rules for a Qt GUI client
4218 package, konqueror support for the bitcoin: URI and bash completion
4219 setup. As I work on Debian Squeeze, I also created
4220 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4221 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4222 it and try to integrate it into the git repository before uploading a
4223 new version to unstable.
4224
4225 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4226 centralized control currently exercised in the monetary system. I
4227 find it completely unacceptable that the USA government is collecting
4228 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4229 that the major credit card companies can block legal money
4230 transactions to Wikileaks. But for bitcoin to succeed, more people
4231 need to use bitcoins, and more people need to accept bitcoins when
4232 they sell products and services. Improving the bitcoin support in
4233 Debian is a small step in the right direction, but not enough.
4234 Unfortunately the user experience when browsing the web and wanting to
4235 pay with bitcoin is still not very good. The bitcoin: URI is a step
4236 in the right direction, but need to work in most or every browser in
4237 use. Also the bitcoin-qt client is too heavy to fire up to do a
4238 quick transaction. I believe there are other clients available, but
4239 have not tested them.&lt;/p&gt;
4240
4241 &lt;p&gt;My
4242 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4243 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4244 I received 20.15 BTC so far on the address I provided in my blog two
4245 years ago, as can be
4246 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4247 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4248 donation. The blockexplorer service demonstrates quite well that
4249 bitcoin is not quite anonymous and untracked. :) I wonder if the
4250 number of users have gone up since then. If you use bitcoin and want
4251 to show your support of my activity, please send Bitcoin donations to
4252 the same address as last time,
4253 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4254 </description>
4255 </item>
4256
4257 <item>
4258 <title>Git repository for song book for Computer Scientists</title>
4259 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4260 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4261 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4262 <description>&lt;p&gt;As I
4263 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4264 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4265 years ago, and today I finally found time to create a public
4266 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4267 repository for the project&lt;/a&gt;.&lt;/p&gt;
4268
4269 &lt;p&gt;If you want to help out, please clone the source and submit patches
4270 to the HTML version. To generate the PDF and PostScript version,
4271 please use prince XML, or let me know about a useful free software
4272 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4273
4274 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4275 PostScript formats at
4276 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4277 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4278 </description>
4279 </item>
4280
4281 <item>
4282 <title>Gratulerer med 19-årsdagen, Debian!</title>
4283 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4284 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4285 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4286 <description>&lt;p&gt;I dag fyller
4287 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4288 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4289 si gratulerer med dagen, Debian!&lt;/p&gt;
4290 </description>
4291 </item>
4292
4293 <item>
4294 <title>Song book for Computer Scientists</title>
4295 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4297 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4298 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4299 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4300 collecting computer related songs for use at parties. The original
4301 version was written in LaTeX, but a few years ago I got help from
4302 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4303 while keeping the ability to create a nice book in PDF format. I have
4304 not had time to maintain the book for a while now, and guess I should
4305 put it up on some public version control repository where others can
4306 help me extend and update the book. If anyone is volunteering to help
4307 me with this, send me an email. Also let me know if there are songs
4308 missing in my book.&lt;/p&gt;
4309
4310 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4311 me today that I really should let all my readers share the joys of
4312 singing out load about programming, computers and computer networks.
4313 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4314 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4315 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4316 Computer Science Songbook&lt;/a&gt;.
4317 </description>
4318 </item>
4319
4320 <item>
4321 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4322 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4323 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4324 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4325 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4326 around 1000 at the moment. To be able to get help from the vendors
4327 when something go wrong, we want to keep the firmware on the servers
4328 up to date. If the firmware isn&#39;t the latest and greatest, the
4329 vendors typically refuse to start debugging any problems until the
4330 firmware is upgraded. So before every reboot, we want to upgrade the
4331 firmware, and we would really like everyone handling servers at the
4332 university to do this themselves when they plan to reboot a machine.
4333 For that to happen we at the unix server admin group need to provide
4334 the tools to do so.&lt;/p&gt;
4335
4336 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4337 fetch and install the latest firmware for the servers we got. Most of
4338 our hardware are from Dell and HP, so I have focused on these servers
4339 so far. This blog post is about the Dell part.&lt;/P&gt;
4340
4341 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4342 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4343 with firmware information for all 11th generation servers, listing
4344 which firmware should be used on a given model and where on the FTP
4345 site I can find it. Using a simple perl XML parser I can then
4346 download the shell scripts Dell provides to do firmware upgrades from
4347 within Linux and reboot when all the firmware is primed and ready to
4348 be activated on the first reboot.&lt;/p&gt;
4349
4350 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4351 Are there anyone working on similar tools for firmware upgrading all
4352 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4353
4354 &lt;p&gt;&lt;pre&gt;
4355 #!/usr/bin/perl
4356 use strict;
4357 use warnings;
4358 use File::Temp qw(tempdir);
4359 BEGIN {
4360 # Install needed RHEL packages if missing
4361 my %rhelmodules = (
4362 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4363 );
4364 for my $module (keys %rhelmodules) {
4365 eval &quot;use $module;&quot;;
4366 if ($@) {
4367 my $pkg = $rhelmodules{$module};
4368 system(&quot;yum install -y $pkg&quot;);
4369 eval &quot;use $module;&quot;;
4370 }
4371 }
4372 }
4373 my $errorsto = &#39;pere@hungry.com&#39;;
4374
4375 upgrade_dell();
4376
4377 exit 0;
4378
4379 sub run_firmware_script {
4380 my ($opts, $script) = @_;
4381 unless ($script) {
4382 print STDERR &quot;fail: missing script name\n&quot;;
4383 exit 1
4384 }
4385 print STDERR &quot;Running $script\n\n&quot;;
4386
4387 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4388 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4389 } else {
4390 print STDERR &quot;fail: firmware script returned error\n&quot;;
4391 }
4392 }
4393
4394 sub run_firmware_scripts {
4395 my ($opts, @dirs) = @_;
4396 # Run firmware packages
4397 for my $dir (@dirs) {
4398 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4399 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4400 while (my $s = readdir $dh) {
4401 next if $s =~ m/^\.\.?/;
4402 run_firmware_script($opts, &quot;$dir/$s&quot;);
4403 }
4404 closedir $dh;
4405 }
4406 }
4407
4408 sub download {
4409 my $url = shift;
4410 print STDERR &quot;info: Downloading $url\n&quot;;
4411 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4412 }
4413
4414 sub upgrade_dell {
4415 my @dirs;
4416 my $product = `dmidecode -s system-product-name`;
4417 chomp $product;
4418
4419 if ($product =~ m/PowerEdge/) {
4420
4421 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4422 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4423
4424 my $tmpdir = tempdir(
4425 CLEANUP =&gt; 1
4426 );
4427 chdir($tmpdir);
4428 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4429 system(&#39;gunzip Catalog.xml.gz&#39;);
4430 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4431 # -q is quiet, disabling interactivity and reducing console output
4432 my $fwopts = &quot;-q&quot;;
4433 if (@paths) {
4434 for my $url (@paths) {
4435 fetch_dell_fw($url);
4436 }
4437 run_firmware_scripts($fwopts, $tmpdir);
4438 } else {
4439 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4440 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4441 }
4442 chdir(&#39;/&#39;);
4443 } else {
4444 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4445 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4446 }
4447 }
4448
4449 sub fetch_dell_fw {
4450 my $path = shift;
4451 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4452 download($url);
4453 }
4454
4455 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4456 # firmware packages to download from Dell. Only work for Linux
4457 # machines and 11th generation Dell servers.
4458 sub fetch_dell_fw_list {
4459 my $filename = shift;
4460
4461 my $product = `dmidecode -s system-product-name`;
4462 chomp $product;
4463 my ($mybrand, $mymodel) = split(/\s+/, $product);
4464
4465 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4466
4467 my $xml = XMLin($filename);
4468 my @paths;
4469 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4470 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4471 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4472 my $oscode;
4473 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4474 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4475 } else {
4476 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4477 }
4478 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4479 {
4480 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4481 }
4482 }
4483 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4484 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4485
4486 # Drop application packages, only firmware and BIOS
4487 next if &#39;APAC&#39; eq $componenttype;
4488
4489 my $cpath = $component-&gt;{path};
4490 for my $path (@paths) {
4491 if ($cpath =~ m%/$path$%) {
4492 push(@paths, $cpath);
4493 }
4494 }
4495 }
4496 return @paths;
4497 }
4498 &lt;/pre&gt;
4499
4500 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4501 it could work on other platforms with some tweaking. Anyone know a
4502 index like Catalog.xml is available from HP for HP servers? At the
4503 moment I maintain a similar list manually and it is quickly getting
4504 outdated.&lt;/p&gt;
4505 </description>
4506 </item>
4507
4508 <item>
4509 <title>How is booting into runlevel 1 different from single user boots?</title>
4510 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4512 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4513 <description>&lt;p&gt;Wouter Verhelst have some
4514 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4515 comments and opinions&lt;/a&gt; on my blog post on
4516 &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
4517 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4518 &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
4519 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4520 small piece of his comment now, and though it best to address the
4521 misunderstanding he bring forward:&lt;/p&gt;
4522
4523 &lt;p&gt;&lt;blockquote&gt;
4524 Currently, a system admin has four options: [...] boot to a
4525 single-user system (by adding &#39;single&#39; to the kernel command line;
4526 this runs rcS and rc1 scripts)
4527 &lt;/blockquote&gt;&lt;/p&gt;
4528
4529 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4530 and booting into runlevel 1 is the same. I am not surprised he
4531 believe this, because it would make sense and is a quite sensible
4532 thing to believe. But because the boot in Debian is slightly broken,
4533 runlevel 1 do not work properly and it isn&#39;t the same as single user
4534 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4535 hard to explain.&lt;/p&gt;
4536
4537 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4538 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4539 executed in single user mode is sulogin. Single user mode is a boot
4540 state &quot;between&quot; the runlevels, and when booting into single user mode,
4541 only the scripts in /etc/rcS.d/ are executed before the init process
4542 enters the single user state. When switching to runlevel 1, the state
4543 is in fact not ending in runlevel 1, but it passes through runlevel 1
4544 and end up in the single user mode (see /etc/rc1.d/S03single, which
4545 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4546 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4547 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4548 mode).&lt;/p&gt;
4549
4550 &lt;p&gt;This summary might make it clearer. When booting for the first
4551 time into single user mode, the following commands are executed:
4552 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4553 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4554 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4555 trying to continue after visiting single user mode. Not all services
4556 are started again as they should, causing the machine to end up in an
4557 unpredicatble state. This is why Debian admins recommend rebooting
4558 after visiting single user mode.&lt;/p&gt;
4559
4560 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4561 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4562 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4563 stopped when passing through the scripts in /etc/rc1.d/, and not
4564 started again when switching away from runlevel 1 to the runlevels
4565 2-5. I believe the problem is best fixed by moving all the scripts
4566 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4567 functioning single user mode during boot.&lt;/p&gt;
4568
4569 &lt;p&gt;I have spent several years investigating the Debian boot system,
4570 and discovered this problem a few years ago. I suspect it originates
4571 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4572 </description>
4573 </item>
4574
4575 <item>
4576 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4577 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4578 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4579 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4580 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4581 are started from /etc/rcS.d/. In fact, there is a bite more of them
4582 than make sense, and this causes a few problems. What kind of
4583 problems, you might ask. There are at least two problems. The first
4584 is that it is not possible to recover a machine after switching to
4585 runlevel 1. One need to actually reboot to get the machine back to
4586 the expected state. The other is that single user boot will sometimes
4587 run into problems because some of the subsystems are activated before
4588 the root login is presented, causing problems when trying to recover a
4589 machine from a problem in that subsystem. A minor additional point is
4590 that moving more scripts out of rcS.d/ and into the other rc#.d/
4591 directories will increase the amount of scripts that can run in
4592 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4593
4594 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4595 scripts that _have_ to execute before the root login prompt is
4596 presented during a single user boot should go there. Everything else
4597 should go into the numeric runlevels. This means things like
4598 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4599 the numeric runlevels. Today in Debian, there are around 115 init.d
4600 scripts that are started from rcS.d/, and most of them should be moved
4601 out. Do your package have one of them? Please help us make single
4602 user and runlevel 1 better by moving it.&lt;/p&gt;
4603
4604 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4605 etc. should still be started from rcS.d/, but there is for example no
4606 need to have the network enabled before the single user login prompt
4607 is presented.&lt;/p&gt;
4608
4609 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4610 Debian systems working while scripts migrate and during upgrades, the
4611 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4612 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4613 and the next ones can only be moved when their dependencies have been
4614 moved first. This migration must be done sequentially while we ensure
4615 that the package system upgrade packages in the right order to keep
4616 the system state correct. This will require some coordination when it
4617 comes to network related packages, but most of the packages with
4618 scripts that should migrate do not have anything in rcS.d/ depending
4619 on them. Some packages have already been updated, like the sudo
4620 package, while others are still left to do. I wish I had time to work
4621 on this myself, but real live constrains make it unlikely that I will
4622 find time to push this forward.&lt;/p&gt;
4623 </description>
4624 </item>
4625
4626 <item>
4627 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4628 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4629 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4630 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4631 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4632 mentioned the issues I believe should be improved in Debian for its
4633 desktop to be useful for more people. The use case for this is my
4634 parents, which are currently running Kubuntu which solve the
4635 issues.&lt;/p&gt;
4636
4637 &lt;p&gt;I suspect these four missing features are not very hard to
4638 implement. After all, they are present in Ubuntu, so if we wanted to
4639 do this in Debian we would have a source.&lt;/p&gt;
4640
4641 &lt;ol&gt;
4642
4643 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4644 are new packages available for upgrades, a icon in the KDE status bar
4645 indicate this, and clicking on it will activate the simple upgrade
4646 tool to handle it. I have no problem guiding both of my parents
4647 through the process over the phone. If a kernel reboot is required,
4648 this too is indicated by the status bars and the upgrade tool. Last
4649 time I checked, nothing with the same features was working in KDE in
4650 Debian.&lt;/li&gt;
4651
4652 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4653 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4654 currently have a handler for, it will ask the user if the system
4655 should search for a package that would add support for this MIME type,
4656 and if the user say yes, the APT sources will be searched for packages
4657 advertising the MIME type in their control file (visible in the
4658 Packages file in the APT archive). If one or more packages are found,
4659 it is a simple click of the mouse to add support for the missing mime
4660 type. If the package require the user to accept some non-free
4661 license, this is explained to the user. The entire process make it
4662 more clear to the user why something do not work in the browser, and
4663 make the chances higher for the user to blame the web page authors and
4664 not the browser for any missing features.&lt;/li&gt;
4665
4666 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4667 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4668 it is not supporting, a dialog pop up asking the user if the system
4669 should search for a package that would add support for it. This
4670 happen with things like MP3, Windows Media or H.264. The selection
4671 and installation procedure is very similar to the Firefox browser
4672 plugin handling. This is as far as I know implemented using a
4673 gstreamer hook. The end result is that the user easily get access to
4674 the codecs that are present from the APT archives available, while
4675 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4676
4677 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4678 displaying a text/plain file in my Debian browser, it will propose to
4679 start emacs to show it. If I remember correctly, when doing the same
4680 in Kunbutu it show the file as a text file in the browser. At least I
4681 know Opera will show text files within the browser. I much prefer the
4682 latter behaviour.&lt;/li&gt;
4683
4684 &lt;/ol&gt;
4685
4686 &lt;p&gt;There are other nice features as well, like the simplified suite
4687 upgrader, but given that I am the one mostly doing the dist-upgrade,
4688 it do not matter much.&lt;/p&gt;
4689
4690 &lt;p&gt;I really hope we could get these features in place for the next
4691 Debian release. It would require the coordinated effort of several
4692 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4693 </description>
4694 </item>
4695
4696 <item>
4697 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4698 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4699 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4700 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4701 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4702 site is build on Debian/Squeeze, and this platform was chosen because
4703 I am most familiar with Debian (being a Debian Developer for around 10
4704 years) because it is the latest stable Debian release which should get
4705 security support for a few years.&lt;/p&gt;
4706
4707 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4708 that are missing in Debian at the moment. It would be great if these
4709 modules were added to the Debian archive, allowing anyone to set up
4710 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4711 in their own country using only Debian packages. The list of modules
4712 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4713 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4714 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4715 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4716 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4717 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4718 easier in the future.&lt;/p&gt;
4719
4720 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4721 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4722 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4723 with the responsibility of tracking security problems, which I really
4724 do not have time for.&lt;/p&gt;
4725 </description>
4726 </item>
4727
4728 <item>
4729 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4730 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4731 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4732 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4733 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4734 posts have been in Norwegian the last few weeks, so here is a short
4735 update in English.&lt;/p&gt;
4736
4737 &lt;p&gt;The kids still keep me too busy to get much free software work
4738 done, but I did manage to organise a project to get a Norwegian port
4739 of the British service
4740 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4741 and it has been running for a month now. The entire project has been
4742 organised by me and two others. Around Christmas we gathered sponsors
4743 to fund the development work. In January I drafted a contract with
4744 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4745 and in February the development took place. Most of it involved
4746 converting the source to use GPS coordinates instead of British
4747 easting/northing, and the resulting code should be a lot easier to get
4748 running in any country by now. The Norwegian
4749 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4750 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4751 source and the source for administrative borders in Norway, and
4752 support for this had to be added/fixed.&lt;/p&gt;
4753
4754 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4755 polishing the system before we announced it March 7th. The system is
4756 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4757 problem reports in a few weeks. Soon we hope to announce the Android
4758 and iPhone versions making it even easier to report problems with the
4759 public infrastructure.&lt;/p&gt;
4760
4761 &lt;p&gt;Perhaps something to consider for those of you in countries without
4762 such service?&lt;/p&gt;
4763 </description>
4764 </item>
4765
4766 <item>
4767 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4768 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4770 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4771 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4772 issues here at my work with the University of Oslo. My idea is that
4773 it should be possible to use the information about security issues
4774 available on the Internet, and check our locally
4775 maintained/distributed software against this information. It should
4776 allow us to verify that no known security issues are forgotten. The
4777 CVE database listing vulnerabilities seem like a great central point,
4778 and by using the package lists from Debian mapped to CVEs provided by
4779 the testing security team, I believed it should be possible to figure
4780 out which security holes were present in our free software
4781 collection.&lt;/p&gt;
4782
4783 &lt;p&gt;After reading up on the topic, it became obvious that the first
4784 building block is to be able to name software packages in a unique and
4785 consistent way across data sources. I considered several ways to do
4786 this, for example coming up with my own naming scheme like using URLs
4787 to project home pages or URLs to the Freshmeat entries, or using some
4788 existing naming scheme. And it seem like I am not the first one to
4789 come across this problem, as MITRE already proposed and implemented a
4790 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4791 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4792 software, hardware and other platform components. The CPE ids are
4793 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4794 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4795 issues for any CPE name. With this in place, all I need to do is to
4796 locate the CPE id for the software packages we use at the university.
4797 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4798 NVD entry if a CVE for the package exist).&lt;/p&gt;
4799
4800 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4801 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4802 check out, one could look up
4803 &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
4804 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4805 The most recent one is
4806 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4807 and at the bottom of the NVD page for this vulnerability the complete
4808 list of affected versions is provided.&lt;/p&gt;
4809
4810 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4811 for offline processing of issues. Using this dump, I&#39;ve written a
4812 small script taking a list of CPEs as input and list all CVEs
4813 affecting the packages represented by these CPEs. One give it CPEs
4814 with version numbers as specified above and get a list of open
4815 security issues out.&lt;/p&gt;
4816
4817 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4818 information need to be high. For that to happen, I believe as many as
4819 possible need to use and contribute to the NVD database. I notice
4820 RHEL is providing
4821 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4822 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4823 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4824
4825 &lt;p&gt;To get an idea about the quality for free software, I spent some
4826 time making it possible to compare the CVE database from Debian with
4827 the CVE database in NVD. The result look fairly good, but there are
4828 some inconsistencies in NVD (same software package having several
4829 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4830 Debian believe are affected by a CVE). Hope to find time to improve
4831 the quality of NVD, but that require being able to get in touch with
4832 someone maintaining it. So far my three emails with questions and
4833 corrections have not seen any reply, but I hope contact can be
4834 established soon.&lt;/p&gt;
4835
4836 &lt;p&gt;An interesting application for CPEs is cross platform package
4837 mapping. It would be useful to know which packages in for example
4838 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4839 this would be trivial if all linux distributions provided CPE entries
4840 for their packages.&lt;/p&gt;
4841 </description>
4842 </item>
4843
4844 <item>
4845 <title>Which module is loaded for a given PCI and USB device?</title>
4846 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4847 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4848 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4849 <description>&lt;p&gt;In the
4850 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4851 package in Debian, there is a script to report useful information
4852 about the running hardware for use when people report missing
4853 information. One part of this script that I find very useful when
4854 debugging hardware problems, is the part mapping loaded kernel module
4855 to the PCI device it claims. It allow me to quickly see if the kernel
4856 module I expect is driving the hardware I am struggling with. To see
4857 the output, make sure discover-data is installed and run
4858 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4859 one of my machines like this:&lt;/p&gt;
4860
4861 &lt;pre&gt;
4862 loaded modules:
4863 10de:03eb i2c_nforce2
4864 10de:03f1 ohci_hcd
4865 10de:03f2 ehci_hcd
4866 10de:03f0 snd_hda_intel
4867 10de:03ec pata_amd
4868 10de:03f6 sata_nv
4869 1022:1103 k8temp
4870 109e:036e bttv
4871 109e:0878 snd_bt87x
4872 11ab:4364 sky2
4873 &lt;/pre&gt;
4874
4875 &lt;p&gt;The code in question look like this, slightly modified for
4876 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4877
4878 &lt;pre&gt;
4879 if [ -d /sys/bus/pci/devices/ ] ; then
4880 echo loaded pci modules:
4881 (
4882 cd /sys/bus/pci/devices/
4883 for address in * ; do
4884 if [ -d &quot;$address/driver/module&quot; ] ; then
4885 module=`cd $address/driver/module ; pwd -P | xargs basename`
4886 if grep -q &quot;^$module &quot; /proc/modules ; then
4887 address=$(echo $address |sed s/0000://)
4888 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4889 echo &quot;$id $module&quot;
4890 fi
4891 fi
4892 done
4893 )
4894 echo
4895 fi
4896 &lt;/pre&gt;
4897
4898 &lt;p&gt;Similar code could be used to extract USB device module
4899 mappings:&lt;/p&gt;
4900
4901 &lt;pre&gt;
4902 if [ -d /sys/bus/usb/devices/ ] ; then
4903 echo loaded usb modules:
4904 (
4905 cd /sys/bus/usb/devices/
4906 for address in * ; do
4907 if [ -d &quot;$address/driver/module&quot; ] ; then
4908 module=`cd $address/driver/module ; pwd -P | xargs basename`
4909 if grep -q &quot;^$module &quot; /proc/modules ; then
4910 address=$(echo $address |sed s/0000://)
4911 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4912 if [ &quot;$id&quot; ] ; then
4913 echo &quot;$id $module&quot;
4914 fi
4915 fi
4916 fi
4917 done
4918 )
4919 echo
4920 fi
4921 &lt;/pre&gt;
4922
4923 &lt;p&gt;This might perhaps be something to include in other tools as
4924 well.&lt;/p&gt;
4925 </description>
4926 </item>
4927
4928 <item>
4929 <title>How to test if a laptop is working with Linux</title>
4930 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4932 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4933 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4934 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4935 batch of computers will work with Linux. Every year for the last few
4936 years the university have organised shared bid of a few thousand
4937 computers, and this year HP won the bid. Two different desktops and
4938 five different laptops are on the list this year. We in the UNIX
4939 group want to know which one of these computers work well with RHEL
4940 and Ubuntu, the two Linux distributions we currently handle at the
4941 university.&lt;/p&gt;
4942
4943 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4944 perhaps inspire others to test hardware as well. To test, I PXE
4945 install the OS version of choice, and log in as my normal user and run
4946 a few applications and plug in selected pieces of hardware. When
4947 something fail, I make a note about this in the test matrix and move
4948 on. If I have some spare time I try to report the bug to the OS
4949 vendor, but as I only have the machines for a short time, I rarely
4950 have the time to do this for all the problems I find.&lt;/p&gt;
4951
4952 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4953 I perform on a new model.&lt;/p&gt;
4954
4955 &lt;ul&gt;
4956
4957 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4958 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4959 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4960
4961 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4962 installation, X.org is working.&lt;/li&gt;
4963
4964 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4965 package mesa-utils on Ubuntu) and writing down the frames per second
4966 reported by the program.&lt;/li&gt;
4967
4968 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4969 logging in, and if I can hear this the test is successful. If there
4970 are several audio exits on the machine, I try them all and check if
4971 the Gnome/KDE audio mixer can control where to send the sound. I
4972 normally test this by playing
4973 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4974 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4975
4976 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4977 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4978
4979 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4980 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4981
4982 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4983 picture from the v4l device show up.&lt;/li&gt;
4984
4985 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4986 any bluetooth devices are discovered. In my office, I normally see a
4987 few.&lt;/li&gt;
4988
4989 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4990 memory modules lying around, and stick them in and see if Gnome/KDE
4991 notice this.&lt;/li&gt;
4992
4993 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4994 special button work, and if the laptop continue to work after
4995 resume.&lt;/li&gt;
4996
4997 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4998 adjusting background light, switching on/off external video output,
4999 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5000 laptop to laptop, so I just write down which are working and which are
5001 not.&lt;/li&gt;
5002
5003 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5004 acceleration sensors etc. I rarely test these, as I do not know how
5005 to quickly test if they are working or not, so I only document their
5006 existence.&lt;/li&gt;
5007
5008 &lt;/ul&gt;
5009
5010 &lt;p&gt;By now I suspect you are really curious what the test results are
5011 for the HP machines I am testing. I&#39;m not done yet, so I will report
5012 the test results later. For now I can report that HP 8100 Elite work
5013 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5014 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5015 can see, I have most machines left to test. One interesting
5016 observation is that Ubuntu Lucid has almost twice the frame rate than
5017 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5018 </description>
5019 </item>
5020
5021 <item>
5022 <title>Some thoughts on BitCoins</title>
5023 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5024 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5025 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5026 <description>&lt;p&gt;As I continue to explore
5027 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5028 what properties the system have, and how it will be affected by laws
5029 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5030
5031 &lt;p&gt;One interesting thing to note is that since the transactions are
5032 verified using a peer to peer network, all details about a transaction
5033 is known to everyone. This means that if a BitCoin address has been
5034 published like I did with mine in my initial post about BitCoin, it is
5035 possible for everyone to see how many BitCoins have been transfered to
5036 that address. There is even a web service to look at the details for
5037 all transactions. There I can see that my address
5038 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5039 have received 16.06 Bitcoin, the
5040 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5041 address of Simon Phipps have received 181.97 BitCoin and the address
5042 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5043 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5044 every one of you that donated bitcoins to support my activity. The
5045 fact that anyone can see how much money was transfered to a given
5046 address make it more obvious why the BitCoin community recommend to
5047 generate and hand out a new address for each transaction. I&#39;m told
5048 there is no way to track which addresses belong to a given person or
5049 organisation without the person or organisation revealing it
5050 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5051
5052 &lt;p&gt;In Norway, and in most other countries, there are laws and
5053 regulations limiting how much money one can transfer across the border
5054 without declaring it. There are money laundering, tax and accounting
5055 laws and regulations I would expect to apply to the use of BitCoin.
5056 If the Skolelinux foundation
5057 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5058 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5059 normal bank transfers like EFF is doing, how should this be accounted?
5060 Given that it is impossible to know if money can cross the border or
5061 not, should everything or nothing be declared? What exchange rate
5062 should be used when calculating taxes? Would receivers have to pay
5063 income tax if the foundation were to pay Skolelinux contributors in
5064 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5065
5066 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5067 accepted by a lot of users. It must be possible to get easy access to
5068 the currency (as a wage or using currency exchanges), and it must be
5069 easy to spend it. At the moment BitCoin seem fairly easy to get
5070 access to, but there are very few places to spend it. I am not really
5071 a regular user of any of the vendor types currently accepting BitCoin,
5072 so I wonder when my kind of shop would start accepting BitCoins. I
5073 would like to buy electronics, travels and subway tickets, not herbs
5074 and books. :) The currency is young, and this will improve over time
5075 if it become popular, but I suspect regular banks will start to lobby
5076 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5077 will claim it is helping fund terrorism and money laundering (which
5078 probably would be true, as is any currency in existence), but I
5079 believe the problems should be solved elsewhere and not by blaming
5080 currencies.&lt;/p&gt;
5081
5082 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5083 CPU intensive process that depend on a bit of luck as well (as one is
5084 competing against all the other miners currently spending CPU cycles
5085 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5086 BitCoin when this happen. Yesterday I came across the obvious way to
5087 join forces to increase ones changes of getting at least some coins,
5088 by coordinating the work on mining BitCoins across several machines
5089 and people, and sharing the result if one is lucky and get the 50
5090 BitCoins. Check out
5091 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5092 if this sounds interesting. I have not had time to try to set up a
5093 machine to participate there yet, but have seen that running on ones
5094 own for a few days have not yield any BitCoins througth mining
5095 yet.&lt;/p&gt;
5096
5097 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5098 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5099 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5100 it was interesting to read. The arguments presented seem to be
5101 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5102 </description>
5103 </item>
5104
5105 <item>
5106 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5107 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5109 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5110 <description>&lt;p&gt;With this weeks lawless
5111 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5112 attacks&lt;/a&gt; on Wikileak and
5113 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5114 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5115 not be trusted to handle money transactions.
5116 A blog post from
5117 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5118 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5119 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5120 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5121 some help from my friend to get it all running, and he even handed me
5122 some bitcoins to get started. I even donated a few bitcoins to Simon
5123 for helping me remember BitCoin.&lt;/p&gt;
5124
5125 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5126 crypto-currency, decentralised and handled using peer-to-peer
5127 networks. It allows anonymous transactions and prohibits central
5128 control over the transactions, making it impossible for governments
5129 and companies alike to block donations and other transactions. The
5130 source is free software, and while the key dependency wxWidgets 2.9
5131 for the graphical user interface is missing in Debian, the command
5132 line client builds just fine. Hopefully Jonas
5133 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5134 Debian&lt;/a&gt; soon.&lt;/p&gt;
5135
5136 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5137 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5138 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5139 currency &quot;stock&quot; markets where the exchange rate is decided. There
5140 are not many users so far, but the concept seems promising. If you
5141 want to get started and lack a friend with any bitcoins to spare,
5142 you can even get
5143 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5144 bitcoin at the time of writing). Use
5145 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5146 on the current exchange rates.&lt;/p&gt;
5147
5148 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5149 machines. If you want to support my activity, please send Bitcoin
5150 donations to the address
5151 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5152 </description>
5153 </item>
5154
5155 <item>
5156 <title>Why isn&#39;t Debian Edu using VLC?</title>
5157 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5159 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5160 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5161 presented, and the winner among the multimedia player were VLC.
5162 Personally, I like VLC, and it is my player of choice when I first try
5163 to play a video file or stream. Only if VLC fail will I drag out
5164 gmplayer to see if it can do better. The reason is mostly the failure
5165 model and trust. When VLC fail, it normally pop up a error message
5166 reporting the problem. When mplayer fail, it normally segfault or
5167 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5168
5169 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5170 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5171 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5172 plugin to play web videos seamlessly, and the VLC browser plugin is
5173 not very good. For example, it lack in-line control buttons, so there
5174 is no way for the user to pause the video. Also, when I
5175 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5176 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5177 failed on several video pages where mplayer based plugins worked. If
5178 the browser plugin for VLC was as good as the gecko-mediaplayer
5179 package (which uses mplayer), we would switch.&lt;/P&gt;
5180
5181 &lt;p&gt;While VLC is a good player, its user interface is slightly
5182 annoying. The most annoying feature is its inconsistent use of
5183 keyboard shortcuts. When the player is in full screen mode, its
5184 shortcuts are different from when it is playing the video in a window.
5185 For example, space only work as pause when in full screen mode. I
5186 wish it had consisten shortcuts and that space also would work when in
5187 window mode. Another nice shortcut in gmplayer is [enter] to restart
5188 the current video. It is very nice when playing short videos from the
5189 web and want to restart it when new people arrive to have a look at
5190 what is going on.&lt;/p&gt;
5191 </description>
5192 </item>
5193
5194 <item>
5195 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5196 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5197 <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>
5198 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5199 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5200 upgrade testing of the
5201 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5202 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5203 This seem like a very good idea, so I adjusted by test scripts and
5204 can now present the updated result from today:&lt;/p&gt;
5205
5206 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5207
5208 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5209
5210 &lt;blockquote&gt;&lt;p&gt;
5211 apache2.2-bin
5212 aptdaemon
5213 baobab
5214 binfmt-support
5215 browser-plugin-gnash
5216 cheese-common
5217 cli-common
5218 cups-pk-helper
5219 dmz-cursor-theme
5220 empathy
5221 empathy-common
5222 freedesktop-sound-theme
5223 freeglut3
5224 gconf-defaults-service
5225 gdm-themes
5226 gedit-plugins
5227 geoclue
5228 geoclue-hostip
5229 geoclue-localnet
5230 geoclue-manual
5231 geoclue-yahoo
5232 gnash
5233 gnash-common
5234 gnome
5235 gnome-backgrounds
5236 gnome-cards-data
5237 gnome-codec-install
5238 gnome-core
5239 gnome-desktop-environment
5240 gnome-disk-utility
5241 gnome-screenshot
5242 gnome-search-tool
5243 gnome-session-canberra
5244 gnome-system-log
5245 gnome-themes-extras
5246 gnome-themes-more
5247 gnome-user-share
5248 gstreamer0.10-fluendo-mp3
5249 gstreamer0.10-tools
5250 gtk2-engines
5251 gtk2-engines-pixbuf
5252 gtk2-engines-smooth
5253 hamster-applet
5254 libapache2-mod-dnssd
5255 libapr1
5256 libaprutil1
5257 libaprutil1-dbd-sqlite3
5258 libaprutil1-ldap
5259 libart2.0-cil
5260 libboost-date-time1.42.0
5261 libboost-python1.42.0
5262 libboost-thread1.42.0
5263 libchamplain-0.4-0
5264 libchamplain-gtk-0.4-0
5265 libcheese-gtk18
5266 libclutter-gtk-0.10-0
5267 libcryptui0
5268 libdiscid0
5269 libelf1
5270 libepc-1.0-2
5271 libepc-common
5272 libepc-ui-1.0-2
5273 libfreerdp-plugins-standard
5274 libfreerdp0
5275 libgconf2.0-cil
5276 libgdata-common
5277 libgdata7
5278 libgdu-gtk0
5279 libgee2
5280 libgeoclue0
5281 libgexiv2-0
5282 libgif4
5283 libglade2.0-cil
5284 libglib2.0-cil
5285 libgmime2.4-cil
5286 libgnome-vfs2.0-cil
5287 libgnome2.24-cil
5288 libgnomepanel2.24-cil
5289 libgpod-common
5290 libgpod4
5291 libgtk2.0-cil
5292 libgtkglext1
5293 libgtksourceview2.0-common
5294 libmono-addins-gui0.2-cil
5295 libmono-addins0.2-cil
5296 libmono-cairo2.0-cil
5297 libmono-corlib2.0-cil
5298 libmono-i18n-west2.0-cil
5299 libmono-posix2.0-cil
5300 libmono-security2.0-cil
5301 libmono-sharpzip2.84-cil
5302 libmono-system2.0-cil
5303 libmtp8
5304 libmusicbrainz3-6
5305 libndesk-dbus-glib1.0-cil
5306 libndesk-dbus1.0-cil
5307 libopal3.6.8
5308 libpolkit-gtk-1-0
5309 libpt2.6.7
5310 libpython2.6
5311 librpm1
5312 librpmio1
5313 libsdl1.2debian
5314 libsrtp0
5315 libssh-4
5316 libtelepathy-farsight0
5317 libtelepathy-glib0
5318 libtidy-0.99-0
5319 media-player-info
5320 mesa-utils
5321 mono-2.0-gac
5322 mono-gac
5323 mono-runtime
5324 nautilus-sendto
5325 nautilus-sendto-empathy
5326 p7zip-full
5327 pkg-config
5328 python-aptdaemon
5329 python-aptdaemon-gtk
5330 python-axiom
5331 python-beautifulsoup
5332 python-bugbuddy
5333 python-clientform
5334 python-coherence
5335 python-configobj
5336 python-crypto
5337 python-cupshelpers
5338 python-elementtree
5339 python-epsilon
5340 python-evolution
5341 python-feedparser
5342 python-gdata
5343 python-gdbm
5344 python-gst0.10
5345 python-gtkglext1
5346 python-gtksourceview2
5347 python-httplib2
5348 python-louie
5349 python-mako
5350 python-markupsafe
5351 python-mechanize
5352 python-nevow
5353 python-notify
5354 python-opengl
5355 python-openssl
5356 python-pam
5357 python-pkg-resources
5358 python-pyasn1
5359 python-pysqlite2
5360 python-rdflib
5361 python-serial
5362 python-tagpy
5363 python-twisted-bin
5364 python-twisted-conch
5365 python-twisted-core
5366 python-twisted-web
5367 python-utidylib
5368 python-webkit
5369 python-xdg
5370 python-zope.interface
5371 remmina
5372 remmina-plugin-data
5373 remmina-plugin-rdp
5374 remmina-plugin-vnc
5375 rhythmbox-plugin-cdrecorder
5376 rhythmbox-plugins
5377 rpm-common
5378 rpm2cpio
5379 seahorse-plugins
5380 shotwell
5381 software-center
5382 system-config-printer-udev
5383 telepathy-gabble
5384 telepathy-mission-control-5
5385 telepathy-salut
5386 tomboy
5387 totem
5388 totem-coherence
5389 totem-mozilla
5390 totem-plugins
5391 transmission-common
5392 xdg-user-dirs
5393 xdg-user-dirs-gtk
5394 xserver-xephyr
5395 &lt;/p&gt;&lt;/blockquote&gt;
5396
5397 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5398
5399 &lt;blockquote&gt;&lt;p&gt;
5400 cheese
5401 ekiga
5402 eog
5403 epiphany-extensions
5404 evolution-exchange
5405 fast-user-switch-applet
5406 file-roller
5407 gcalctool
5408 gconf-editor
5409 gdm
5410 gedit
5411 gedit-common
5412 gnome-games
5413 gnome-games-data
5414 gnome-nettool
5415 gnome-system-tools
5416 gnome-themes
5417 gnuchess
5418 gucharmap
5419 guile-1.8-libs
5420 libavahi-ui0
5421 libdmx1
5422 libgalago3
5423 libgtk-vnc-1.0-0
5424 libgtksourceview2.0-0
5425 liblircclient0
5426 libsdl1.2debian-alsa
5427 libspeexdsp1
5428 libsvga1
5429 rhythmbox
5430 seahorse
5431 sound-juicer
5432 system-config-printer
5433 totem-common
5434 transmission-gtk
5435 vinagre
5436 vino
5437 &lt;/p&gt;&lt;/blockquote&gt;
5438
5439 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5440
5441 &lt;blockquote&gt;&lt;p&gt;
5442 gstreamer0.10-gnomevfs
5443 &lt;/p&gt;&lt;/blockquote&gt;
5444
5445 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5446
5447 &lt;blockquote&gt;&lt;p&gt;
5448 [nothing]
5449 &lt;/p&gt;&lt;/blockquote&gt;
5450
5451 &lt;p&gt;This is for KDE:&lt;/p&gt;
5452
5453 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5454
5455 &lt;blockquote&gt;&lt;p&gt;
5456 ksmserver
5457 &lt;/p&gt;&lt;/blockquote&gt;
5458
5459 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5460
5461 &lt;blockquote&gt;&lt;p&gt;
5462 kwin
5463 network-manager-kde
5464 &lt;/p&gt;&lt;/blockquote&gt;
5465
5466 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5467
5468 &lt;blockquote&gt;&lt;p&gt;
5469 arts
5470 dolphin
5471 freespacenotifier
5472 google-gadgets-gst
5473 google-gadgets-xul
5474 kappfinder
5475 kcalc
5476 kcharselect
5477 kde-core
5478 kde-plasma-desktop
5479 kde-standard
5480 kde-window-manager
5481 kdeartwork
5482 kdeartwork-emoticons
5483 kdeartwork-style
5484 kdeartwork-theme-icon
5485 kdebase
5486 kdebase-apps
5487 kdebase-workspace
5488 kdebase-workspace-bin
5489 kdebase-workspace-data
5490 kdeeject
5491 kdelibs
5492 kdeplasma-addons
5493 kdeutils
5494 kdewallpapers
5495 kdf
5496 kfloppy
5497 kgpg
5498 khelpcenter4
5499 kinfocenter
5500 konq-plugins-l10n
5501 konqueror-nsplugins
5502 kscreensaver
5503 kscreensaver-xsavers
5504 ktimer
5505 kwrite
5506 libgle3
5507 libkde4-ruby1.8
5508 libkonq5
5509 libkonq5-templates
5510 libnetpbm10
5511 libplasma-ruby
5512 libplasma-ruby1.8
5513 libqt4-ruby1.8
5514 marble-data
5515 marble-plugins
5516 netpbm
5517 nuvola-icon-theme
5518 plasma-dataengines-workspace
5519 plasma-desktop
5520 plasma-desktopthemes-artwork
5521 plasma-runners-addons
5522 plasma-scriptengine-googlegadgets
5523 plasma-scriptengine-python
5524 plasma-scriptengine-qedje
5525 plasma-scriptengine-ruby
5526 plasma-scriptengine-webkit
5527 plasma-scriptengines
5528 plasma-wallpapers-addons
5529 plasma-widget-folderview
5530 plasma-widget-networkmanagement
5531 ruby
5532 sweeper
5533 update-notifier-kde
5534 xscreensaver-data-extra
5535 xscreensaver-gl
5536 xscreensaver-gl-extra
5537 xscreensaver-screensaver-bsod
5538 &lt;/p&gt;&lt;/blockquote&gt;
5539
5540 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5541
5542 &lt;blockquote&gt;&lt;p&gt;
5543 ark
5544 google-gadgets-common
5545 google-gadgets-qt
5546 htdig
5547 kate
5548 kdebase-bin
5549 kdebase-data
5550 kdepasswd
5551 kfind
5552 klipper
5553 konq-plugins
5554 konqueror
5555 ksysguard
5556 ksysguardd
5557 libarchive1
5558 libcln6
5559 libeet1
5560 libeina-svn-06
5561 libggadget-1.0-0b
5562 libggadget-qt-1.0-0b
5563 libgps19
5564 libkdecorations4
5565 libkephal4
5566 libkonq4
5567 libkonqsidebarplugin4a
5568 libkscreensaver5
5569 libksgrd4
5570 libksignalplotter4
5571 libkunitconversion4
5572 libkwineffects1a
5573 libmarblewidget4
5574 libntrack-qt4-1
5575 libntrack0
5576 libplasma-geolocation-interface4
5577 libplasmaclock4a
5578 libplasmagenericshell4
5579 libprocesscore4a
5580 libprocessui4a
5581 libqalculate5
5582 libqedje0a
5583 libqtruby4shared2
5584 libqzion0a
5585 libruby1.8
5586 libscim8c2a
5587 libsmokekdecore4-3
5588 libsmokekdeui4-3
5589 libsmokekfile3
5590 libsmokekhtml3
5591 libsmokekio3
5592 libsmokeknewstuff2-3
5593 libsmokeknewstuff3-3
5594 libsmokekparts3
5595 libsmokektexteditor3
5596 libsmokekutils3
5597 libsmokenepomuk3
5598 libsmokephonon3
5599 libsmokeplasma3
5600 libsmokeqtcore4-3
5601 libsmokeqtdbus4-3
5602 libsmokeqtgui4-3
5603 libsmokeqtnetwork4-3
5604 libsmokeqtopengl4-3
5605 libsmokeqtscript4-3
5606 libsmokeqtsql4-3
5607 libsmokeqtsvg4-3
5608 libsmokeqttest4-3
5609 libsmokeqtuitools4-3
5610 libsmokeqtwebkit4-3
5611 libsmokeqtxml4-3
5612 libsmokesolid3
5613 libsmokesoprano3
5614 libtaskmanager4a
5615 libtidy-0.99-0
5616 libweather-ion4a
5617 libxklavier16
5618 libxxf86misc1
5619 okteta
5620 oxygencursors
5621 plasma-dataengines-addons
5622 plasma-scriptengine-superkaramba
5623 plasma-widget-lancelot
5624 plasma-widgets-addons
5625 plasma-widgets-workspace
5626 polkit-kde-1
5627 ruby1.8
5628 systemsettings
5629 update-notifier-common
5630 &lt;/p&gt;&lt;/blockquote&gt;
5631
5632 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5633 aptitude a bit more similar, but there are still quite a lott of
5634 differences. I have no idea what packages should be installed after
5635 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5636 </description>
5637 </item>
5638
5639 <item>
5640 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5641 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5642 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5643 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5644 <description>&lt;p&gt;Most of the computers in use by the
5645 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5646 are virtual machines. And they have been Xen machines running on a
5647 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5648 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5649 bit harder that it could have been, because we set up the Xen virtual
5650 machines to get the virtual partitions from LVM, which as far as I
5651 know is not supported by KVM. So to migrate, we had to convert
5652 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5653
5654 &lt;p&gt;I found
5655 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5656 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5657 migration. It uses qemu-img from the qemu package to make the disk
5658 image, parted to partition it, losetup and kpartx to present the disk
5659 image partions as devices, and dd to copy the data. I NFS mounted the
5660 new servers storage area on the old server to do the migration.&lt;/p&gt;
5661
5662 &lt;pre&gt;
5663 #!/bin/sh
5664
5665 # Based on
5666 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5667
5668 set -e
5669 set -x
5670
5671 if [ -z &quot;$1&quot; ] ; then
5672 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5673 exit 1
5674 else
5675 host=&quot;$1&quot;
5676 fi
5677
5678 if [ ! -e /dev/vg_data/$host-disk ] ; then
5679 echo &quot;error: unable to find LVM volume for $host&quot;
5680 exit 1
5681 fi
5682
5683 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5684 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5685 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5686 totalsize=$(( ( $disksize + $swapsize ) ))
5687
5688 img=$host.img
5689 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5690 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5691
5692 parted $img mklabel msdos
5693 parted $img mkpart primary linux-swap 0 $disksize
5694 parted $img mkpart primary ext2 $disksize $totalsize
5695 parted $img set 1 boot on
5696
5697 modprobe dm-mod
5698 losetup /dev/loop0 $img
5699 kpartx -a /dev/loop0
5700
5701 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5702 fsck.ext3 -f /dev/mapper/loop0p1 || true
5703 mkswap /dev/mapper/loop0p2
5704
5705 kpartx -d /dev/loop0
5706 losetup -d /dev/loop0
5707 &lt;/pre&gt;
5708
5709 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5710 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5711
5712 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5713 the new disk image attached, installed grub-pc and linux-image-686 and
5714 set up grub to boot from the disk image. After this, the KVM machines
5715 seem to work just fine.&lt;/p&gt;
5716 </description>
5717 </item>
5718
5719 <item>
5720 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5721 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5722 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5723 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5724 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5725 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5726 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5727 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5728
5729 &lt;p&gt;I still do not know what a correct migration should look like, so I
5730 report any differences between apt and aptitude and hope someone else
5731 can see if anything should be changed.&lt;/p&gt;
5732
5733 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5734
5735 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5736
5737 &lt;blockquote&gt;&lt;p&gt;
5738 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5739 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5740 dmz-cursor-theme empathy empathy-common finger
5741 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5742 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5743 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5744 gnome-cards-data gnome-codec-install gnome-core
5745 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5746 gnome-search-tool gnome-session-canberra gnome-spell
5747 gnome-system-log gnome-themes-extras gnome-themes-more
5748 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5749 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5750 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5751 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5752 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5753 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5754 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5755 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5756 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5757 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5758 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5759 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5760 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5761 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5762 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5763 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5764 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5765 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5766 libmono-security2.0-cil libmono-sharpzip2.84-cil
5767 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5768 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5769 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5770 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5771 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5772 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5773 libxalan2-java libxerces2-java media-player-info mesa-utils
5774 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5775 nautilus-sendto-empathy openoffice.org-writer2latex
5776 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5777 python-aptdaemon python-aptdaemon-gtk python-axiom
5778 python-beautifulsoup python-bugbuddy python-clientform
5779 python-coherence python-configobj python-crypto python-cupshelpers
5780 python-cupsutils python-eggtrayicon python-elementtree
5781 python-epsilon python-evolution python-feedparser python-gdata
5782 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5783 python-gtksourceview2 python-httplib2 python-louie python-mako
5784 python-markupsafe python-mechanize python-nevow python-notify
5785 python-opengl python-openssl python-pam python-pkg-resources
5786 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5787 python-tagpy python-twisted-bin python-twisted-conch
5788 python-twisted-core python-twisted-web python-utidylib python-webkit
5789 python-xdg python-zope.interface remmina remmina-plugin-data
5790 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5791 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5792 software-center svgalibg1 system-config-printer-udev
5793 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5794 totem totem-coherence totem-mozilla totem-plugins
5795 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5796 zip
5797 &lt;/p&gt;&lt;/blockquote&gt;
5798
5799 Installed using apt-get, removed with aptitude
5800
5801 &lt;blockquote&gt;&lt;p&gt;
5802 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5803 epiphany-extensions epiphany-gecko evolution-exchange
5804 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5805 gedit-common gnome-app-install gnome-games gnome-games-data
5806 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5807 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5808 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5809 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5810 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5811 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5812 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5813 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5814 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5815 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5816 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5817 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5818 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5819 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5820 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5821 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5822 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5823 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5824 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5825 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5826 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5827 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5828 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5829 sound-juicer swfdec-gnome system-config-printer totem-common
5830 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5831 &lt;/p&gt;&lt;/blockquote&gt;
5832
5833 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5834
5835 &lt;blockquote&gt;&lt;p&gt;
5836 gstreamer0.10-gnomevfs
5837 &lt;/p&gt;&lt;/blockquote&gt;
5838
5839 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5840
5841 &lt;blockquote&gt;&lt;p&gt;
5842 [nothing]
5843 &lt;/p&gt;&lt;/blockquote&gt;
5844
5845 &lt;p&gt;This is for KDE:&lt;/p&gt;
5846
5847 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5848
5849 &lt;blockquote&gt;&lt;p&gt;
5850 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5851 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5852 ghostscript-x git gnome-audio gnugo granatier gs-common
5853 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5854 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5855 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5856 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5857 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5858 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5859 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5860 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5861 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5862 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5863 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5864 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5865 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5866 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5867 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5868 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5869 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5870 libkrossui4 libmailtools-perl libmime-tools-perl
5871 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5872 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5873 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5874 lirc luatex marble networkstatus noatun-plugins
5875 openoffice.org-writer2latex palapeli palapeli-data parley
5876 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5877 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5878 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5879 ttf-sazanami-gothic
5880 &lt;/p&gt;&lt;/blockquote&gt;
5881
5882 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5883
5884 &lt;blockquote&gt;&lt;p&gt;
5885 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5886 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5887 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5888 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5889 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5890 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5891 kitchensync kiten kjumpingcube klatin klettres klickety klines
5892 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5893 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5894 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5895 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5896 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5897 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5898 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5899 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5900 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5901 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5902 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5903 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5904 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5905 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5906 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5907 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5908 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5909 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5910 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5911 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5912 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5913 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5914 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5915 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5916 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5917 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5918 &lt;/p&gt;&lt;/blockquote&gt;
5919
5920 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5921
5922 &lt;blockquote&gt;&lt;p&gt;
5923 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5924 kdeartwork kdebase kdebase-apps kdebase-workspace
5925 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5926 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5927 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5928 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5929 xscreensaver-screensaver-bsod
5930 &lt;/p&gt;&lt;/blockquote&gt;
5931
5932 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5933
5934 &lt;blockquote&gt;&lt;p&gt;
5935 kdebase-bin konq-plugins konqueror
5936 &lt;/p&gt;&lt;/blockquote&gt;
5937 </description>
5938 </item>
5939
5940 <item>
5941 <title>Gnash buildbot slave and Debian kfreebsd</title>
5942 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5943 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5944 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5945 <description>&lt;p&gt;Answering
5946 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5947 call from the Gnash project&lt;/a&gt; for
5948 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5949 current source, I have set up a virtual KVM machine on the Debian
5950 Edu/Skolelinux virtualization host to test the git source on
5951 Debian/Squeeze. I hope this can help the developers in getting new
5952 releases out more often.&lt;/p&gt;
5953
5954 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5955 I have considered setting up a &lt;a
5956 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5957 machine as well. I have also considered using the kfreebsd
5958 architecture in Debian as a file server in NUUG to get access to the 5
5959 TB zfs volume we currently use to store DV video. Because of this, I
5960 finally got around to do a test installation of Debian/Squeeze with
5961 kfreebsd. Installation went fairly smooth, thought I noticed some
5962 visual glitches in the cdebconf dialogs (black cursor left on the
5963 screen at random locations). Have not gotten very far with the
5964 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5965 fatal problem. Have to spend some more time on it to see if it is
5966 useful as a file server for NUUG. Will try to find time to set up a
5967 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5968 </description>
5969 </item>
5970
5971 <item>
5972 <title>Debian in 3D</title>
5973 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5974 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5975 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5976 <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;
5977
5978 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5979 3D linked in from
5980 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5981 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5982 </description>
5983 </item>
5984
5985 <item>
5986 <title>Software updates 2010-10-24</title>
5987 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5989 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5990 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5991
5992 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5993 raise money for the project is going well. The lower limit of 10
5994 signers was reached in 24 hours, and so far 13 people have signed it.
5995 More signers and more funding is most welcome, and I am really curious
5996 how far we can get before the time limit of December 24 is reached.
5997 :)&lt;/p&gt;
5998
5999 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6000 about what appear to be a great code coverage tool capable of
6001 generating code coverage stats without any changes to the source code.
6002 It is called
6003 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6004 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6005 It is missing in Debian, but the git source built just fine in Squeeze
6006 after I installed libelf-dev, libdwarf-dev, pkg-config and
6007 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6008 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6009
6010 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6011 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6012 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6013 alpha test release of the Squeeze based Debian Edu /
6014 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6015 release. Give it a try if you need a complete linux solution for your
6016 school, including central infrastructure server, workstations, thin
6017 client servers and diskless workstations. A nice touch added
6018 yesterday is RDP support on the thin client servers, for windows
6019 clients to get a Linux desktop on request.&lt;/p&gt;
6020 </description>
6021 </item>
6022
6023 <item>
6024 <title>Some notes on Flash in Debian and Debian Edu</title>
6025 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6027 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6028 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6029 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6030 second most popular used package that is missing in Debian. The sixth
6031 most popular is flashplayer-mozilla. This is a clear indication that
6032 working flash is important for Debian users. Around 10 percent of the
6033 users submitting data to popcon.debian.org have this package
6034 installed.&lt;/p&gt;
6035
6036 &lt;p&gt;In the report written by Lars Risan in August 2008
6037&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
6038 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6039 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6040 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6041 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6042 web sites require Flash to work, and lacking working Flash support in
6043 the web browser and the problems with installing it was perceived as a
6044 good reason to stay with Windows.&lt;/p&gt;
6045
6046 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6047 said to be the retarded cousin that did not really understand
6048 everything you told him but could work fairly well. This was a
6049 comment regarding the problems Linux have with proprietary formats and
6050 non-standard web pages, and is sad because it exposes a fairly common
6051 understanding of whose fault it is if web pages that only work in for
6052 example Internet Explorer 6 fail to work on Firefox, and funny because
6053 it explain very well how annoying it is for users when Linux
6054 distributions do not work with the documents they receive or the web
6055 pages they want to visit.&lt;/p&gt;
6056
6057 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6058 and Debian Edu to have a well working Flash implementation in the
6059 distribution, to get at least popular sites as Youtube and Google
6060 Video to working out of the box. For Squeeze, Debian have the chance
6061 to include the latest version of Gnash that will make this happen, as
6062 the new release 0.8.8 was published a few weeks ago and is resting in
6063 unstable. The new version work with more sites that version 0.8.7.
6064 The Gnash maintainers have asked for a freeze exception, but the
6065 release team have not had time to reply to it yet. I hope they agree
6066 with me that Flash is important for the Debian desktop users, and thus
6067 accept the new package into Squeeze.&lt;/p&gt;
6068 </description>
6069 </item>
6070
6071 <item>
6072 <title>Circular package dependencies harms apt recovery</title>
6073 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6074 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6075 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6076 <description>&lt;p&gt;I discovered this while doing
6077 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6078 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6079 in Debian still got circular dependencies, and it is often claimed
6080 that apt and aptitude should be able to handle this just fine, but
6081 some times these dependency loops causes apt to fail.&lt;/p&gt;
6082
6083 &lt;p&gt;An example is from todays
6084 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6085 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6086 causes perl-modules to fail to upgrade. The cause is simple. If a
6087 package fail to unpack, then only part of packages with the circular
6088 dependency might end up being unpacked when unpacking aborts, and the
6089 ones already unpacked will fail to configure in the recovery phase
6090 because its dependencies are unavailable.&lt;/p&gt;
6091
6092 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6093
6094 &lt;blockquote&gt;&lt;pre&gt;
6095 dpkg: dependency problems prevent configuration of perl-modules:
6096 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6097 Version of perl on system is 5.10.0-19lenny2.
6098 dpkg: error processing perl-modules (--configure):
6099 dependency problems - leaving unconfigured
6100 &lt;/pre&gt;&lt;/blockquote&gt;
6101
6102 &lt;p&gt;The perl/perl-modules circular dependency is already
6103 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6104 hopefully be solved as soon as possible, but it is not the only one,
6105 and each one of these loops in the dependency tree can cause similar
6106 failures. Of course, they only occur when there are bugs in other
6107 packages causing the unpacking to fail, but it is rather nasty when
6108 the failure of one package causes the problem to become worse because
6109 of dependency loops.&lt;/p&gt;
6110
6111 &lt;p&gt;Thanks to
6112 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6113 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6114 dependencies
6115 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6116 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6117
6118 &lt;p&gt;Todays testing also exposed a bug in
6119 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6120 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6121 apt-get and aptitude, the latter possibly caused by some circular
6122 dependency. Reported both to BTS to try to get someone to look at
6123 it.&lt;/p&gt;
6124 </description>
6125 </item>
6126
6127 <item>
6128 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6129 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6130 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6131 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6132 <description>&lt;p&gt;This is a
6133 &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;
6134 on my
6135 &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
6136 work&lt;/a&gt; on
6137 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6138 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6139
6140 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6141 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6142 and dhcp3-server-ldap in Debian use the LDAP server. The two
6143 implementations are quite different in how they use LDAP.&lt;/p&gt;
6144
6145 To get this information, I started slapd with debugging enabled and
6146 dumped the debug output to a file to get the LDAP searches performed
6147 on a Debian Edu main-server. Here is a summary.
6148
6149 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6150
6151 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6152 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6153 the web.
6154
6155 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6156 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6157 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6158 reverse entries are in two different subtrees in LDAP with a structure
6159 based on the DNS names, as in tjener.intern and
6160 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6161
6162 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6163 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6164 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6165 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6166 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6167 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6168 forward entries, it is looking for attributes named dnsttl, arecord,
6169 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6170 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6171 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6172 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6173 spfrecord and modifytimestamp. For reverse entries it is looking for
6174 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6175 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6176 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6177 ldapsearch commands could look like this:&lt;/p&gt;
6178
6179 &lt;blockquote&gt;&lt;pre&gt;
6180 ldapsearch -h ldap \
6181 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6182 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6183 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6184 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6185 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6186 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6187
6188 ldapsearch -h ldap \
6189 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6190 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6191 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6192 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6193 srvrecord naptrrecord modifytimestamp
6194 &lt;/pre&gt;&lt;/blockquote&gt;
6195
6196 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6197 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6198 example LDAP objects used there. In addition to these objects, the
6199 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6200 also exist.&lt;/p&gt;
6201
6202 &lt;blockquote&gt;&lt;pre&gt;
6203 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6204 objectclass: top
6205 objectclass: dnsdomain
6206 objectclass: domainrelatedobject
6207 dc: tjener
6208 arecord: 10.0.2.2
6209 associateddomain: tjener.intern
6210
6211 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6212 objectclass: top
6213 objectclass: dnsdomain2
6214 objectclass: domainrelatedobject
6215 dc: 2
6216 ptrrecord: tjener.intern
6217 associateddomain: 2.2.0.10.in-addr.arpa
6218 &lt;/pre&gt;&lt;/blockquote&gt;
6219
6220 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6221 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6222 same base as in the tree mode for a object with filter
6223 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6224 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6225 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6226 naptrrecord and modifytimestamp. For reverse entires it also do a
6227 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6228 and the requested attributes are associateddomain, dnsttl and
6229 modifytimestamp. In short, in strict mode the objects with ptrrecord
6230 go away, and the arecord attribute in the forward object is used
6231 instead.&lt;/p&gt;
6232
6233 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6234 like this:&lt;/p&gt;
6235
6236 &lt;blockquote&gt;&lt;pre&gt;
6237 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6238 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6239 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6240 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6241 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6242 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6243
6244 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6245 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6246 &lt;/pre&gt;&lt;/blockquote&gt;
6247
6248 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6249 search for SOA records, which behave similar to the forward and
6250 reverse lookups.&lt;/p&gt;
6251
6252 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6253 specify any objectclass names, and instead look for the attributes it
6254 need to generate a DNS reply. This make it able to work with any
6255 objectclass that provide the needed attributes.&lt;/p&gt;
6256
6257 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6258 dnsdomain2 schemas. The latter is used for reverse entries like
6259 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6260
6261 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6262 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6263 attributes) and domainrelatedobject (for associatedDomain). The use
6264 of structural object classes make it impossible to combine these
6265 classes with the object classes used by DHCP.&lt;/p&gt;
6266
6267 &lt;p&gt;There are other schemas that could be used too, for example the
6268 dnszone structural object class used by Gosa and bind-sdb for the DNS
6269 attributes combined with the domainrelatedobject object class, but in
6270 this case some unused attributes would have to be included as well
6271 (zonename and relativedomainname).&lt;/p&gt;
6272
6273 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6274 mode and not use any of the existing objectclasses (dnsdomain,
6275 dnsdomain2 and dnszone) when one want to combine the DNS information
6276 with DHCP information, and instead create a auxiliary object class
6277 defined something like this (using the attributes defined for
6278 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6279
6280 &lt;blockquote&gt;&lt;pre&gt;
6281 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6282 SUP top
6283 AUXILIARY
6284 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6285 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6286 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6287 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6288 A6Record $ DNAMERecord
6289 ))
6290 &lt;/pre&gt;&lt;/blockquote&gt;
6291
6292 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6293 the domainrelatedobject object class, and allow any entity to include
6294 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6295 developers asking for their view on this schema and if they are
6296 interested in providing such schema with PowerDNS, and I hope my
6297 message will be accepted into their mailing list soon.&lt;/p&gt;
6298
6299 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6300
6301 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6302 the object attributes, and then uses the attributes it want. This
6303 make it harder to figure out exactly what attributes are used, but
6304 thanks to the working example in Debian Edu I can at least get an idea
6305 what is needed without having to read the source code.&lt;/p&gt;
6306
6307 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6308 search filter to use to locate the correct dhcpServer entity is
6309 stored. These are the relevant entries from
6310 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6311
6312 &lt;blockquote&gt;&lt;pre&gt;
6313 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6314 ldap-dhcp-server-cn &quot;dhcp&quot;;
6315 &lt;/pre&gt;&lt;/blockquote&gt;
6316
6317 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6318 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6319 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6320 search result is this entry:&lt;/p&gt;
6321
6322 &lt;blockquote&gt;&lt;pre&gt;
6323 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6324 cn: dhcp
6325 objectClass: top
6326 objectClass: dhcpServer
6327 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6328 &lt;/pre&gt;&lt;/blockquote&gt;
6329
6330 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6331 subtree with DHCP configuration. The DHCP configuration subtree base
6332 is located using a base scope search with base &quot;cn=DHCP
6333 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6334 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6335 The search result is this entry:&lt;/p&gt;
6336
6337 &lt;blockquote&gt;&lt;pre&gt;
6338 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6339 cn: DHCP Config
6340 objectClass: top
6341 objectClass: dhcpService
6342 objectClass: dhcpOptions
6343 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6344 dhcpStatements: ddns-update-style none
6345 dhcpStatements: authoritative
6346 dhcpOption: smtp-server code 69 = array of ip-address
6347 dhcpOption: www-server code 72 = array of ip-address
6348 dhcpOption: wpad-url code 252 = text
6349 &lt;/pre&gt;&lt;/blockquote&gt;
6350
6351 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6352 all the DHCP configuration is loaded, it is ready to receive requests.
6353 The subtree in Debian Edu contain objects with object classes
6354 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6355 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6356 and information about netmasks, dynamic range etc. Leaving out the
6357 details here because it is not relevant for the focus of my
6358 investigation, which is to see if it is possible to merge dns and dhcp
6359 related computer objects.&lt;/p&gt;
6360
6361 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6362 of the client (00:00:00:00:00:00 in this example), using a subtree
6363 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6364 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6365 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6366 like:&lt;/p&gt;
6367
6368 &lt;blockquote&gt;&lt;pre&gt;
6369 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6370 cn: hostname
6371 objectClass: top
6372 objectClass: dhcpHost
6373 dhcpHWAddress: ethernet 00:00:00:00:00:00
6374 dhcpStatements: fixed-address hostname
6375 &lt;/pre&gt;&lt;/blockquote&gt;
6376
6377 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6378 The object classes need to have fixed names, and the configuration
6379 need to be stored in a fairly specific LDAP structure. On the
6380 positive side, the invidiual dhcpHost entires can be anywhere without
6381 the DN pointed to by the dhcpServer entries. The latter should make
6382 it possible to group all host entries in a subtree next to the
6383 configuration entries, and this subtree can also be shared with the
6384 DNS server if the schema proposed above is combined with the dhcpHost
6385 structural object class.
6386
6387 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6388
6389 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6390 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6391 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6392 allowing DNS objects to be stored anywhere under the base cn specified
6393 in the configuration.&lt;/p&gt;
6394
6395 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6396 regarding which LDAP schemas to use and which LDAP structure to use.
6397 I guess one could implement ones own schema, as long as the
6398 objectclasses and attributes have the names used, but this do not
6399 really help when the DHCP subtree need to have a fairly fixed
6400 structure.&lt;/p&gt;
6401
6402 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6403 this might work for Debian Edu:&lt;/p&gt;
6404
6405 &lt;blockquote&gt;&lt;pre&gt;
6406 ou=services
6407 cn=machine-info (dhcpService) - dhcpServiceDN points here
6408 cn=dhcp (dhcpServer)
6409 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6410 cn=10.0.2.0 (dhcpSubnet)
6411 cn=group1 (dhcpGroup/dhcpOptions)
6412 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6413 cn=192.168.0.0 (dhcpSubnet)
6414 cn=group1 (dhcpGroup/dhcpOptions)
6415 ou=machines - PowerDNS base points here
6416 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6417 &lt;/pre&gt;&lt;/blockquote&gt;
6418
6419 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6420 entries to be in the dhcpGroup subtrees, the entries can be stored
6421 there instead of a common machines subtree, and the PowerDNS base
6422 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6423
6424 &lt;p&gt;The combined object under the machines subtree would look something
6425 like this:&lt;/p&gt;
6426
6427 &lt;blockquote&gt;&lt;pre&gt;
6428 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6429 dc: hostname
6430 objectClass: top
6431 objectClass: dhcpHost
6432 objectclass: domainrelatedobject
6433 objectclass: dnsDomainAux
6434 associateddomain: hostname.intern
6435 arecord: 10.11.12.13
6436 dhcpHWAddress: ethernet 00:00:00:00:00:00
6437 dhcpStatements: fixed-address hostname.intern
6438 &lt;/pre&gt;&lt;/blockquote&gt;
6439
6440 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6441 machine, as long as the required attributes are available in a
6442 auxiliary object class.&lt;/p&gt;
6443 </description>
6444 </item>
6445
6446 <item>
6447 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6448 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6449 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6450 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6451 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6452 DHCP services in Debian Edu to use the same LDAP objects for a given
6453 computer, to avoid the possibility of having a inconsistent state for
6454 a computer in LDAP (as in DHCP but no DNS entry or the other way
6455 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6456
6457 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6458 information finally found a solution that seem to work.&lt;/p&gt;
6459
6460 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6461 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6462 we switch powerdns to use its strict LDAP method (ldap-method=strict
6463 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6464 merged into one while making it impossible to transfer the reverse map
6465 to a slave DNS server.&lt;/p&gt;
6466
6467 &lt;p&gt;If we also replace the object class used to get the DNS related
6468 attributes to one allowing these attributes to be combined with the
6469 dhcphost object class, we can merge the DNS and DHCP entries into one.
6470 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6471 proper OIDs, but that is a minor issue), and tested the setup. It
6472 seem to work.&lt;/p&gt;
6473
6474 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6475 for both DNS and DHCP, and even the LTSP configuration I suggested in
6476 an earlier email. The combined LDAP object will look something like
6477 this:&lt;/p&gt;
6478
6479 &lt;blockquote&gt;&lt;pre&gt;
6480 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6481 cn: hostname
6482 objectClass: dhcphost
6483 objectclass: domainrelatedobject
6484 objectclass: dnsdomainaux
6485 associateddomain: hostname.intern
6486 arecord: 10.11.12.13
6487 dhcphwaddress: ethernet 00:00:00:00:00:00
6488 dhcpstatements: fixed-address hostname
6489 ldapconfigsound: Y
6490 &lt;/pre&gt;&lt;/blockquote&gt;
6491
6492 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6493 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6494 before asking DNS to resolve the fixed-adddress. LTSP will use
6495 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6496
6497 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6498 dhcphost in a different location, to allow us to put the objects
6499 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6500 that. If I can&#39;t figure out a way to do that, we can still get rid of
6501 the hosts subtree and move all its content into the DHCP Config tree
6502 (which probably should be renamed to be more related to the new
6503 content. I suspect cn=dnsdhcp,ou=services or something like that
6504 might be a good place to put it.&lt;/p&gt;
6505
6506 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6507 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6508 </description>
6509 </item>
6510
6511 <item>
6512 <title>Idea for storing LTSP configuration in LDAP</title>
6513 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6515 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6516 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6517 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6518 clients, and that this can be used to fetch configuration from LDAP if
6519 Debian Edu choose to store configuration there.&lt;/p&gt;
6520
6521 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6522 to get configuration from LDAP. The idea is to look up the MAC
6523 address of the client in LDAP, and look for attributes on the form
6524 ltspconfigsetting=value, and use this to export SETTING=value to the
6525 LTSP clients.&lt;/p&gt;
6526
6527 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6528 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6529 allowing us to store all information about a computer in one place.&lt;/p&gt;
6530
6531 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6532 this approach. A real LDAP schema for the ltspClientAux objectclass
6533 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6534
6535 &lt;blockquote&gt;&lt;pre&gt;
6536 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6537 #
6538 # Fetch LTSP client settings from LDAP based on MAC address
6539 #
6540 # Uses ethernet address as stored in the dhcpHost objectclass using
6541 # the dhcpHWAddress attribute or ethernet address stored in the
6542 # ieee802Device objectclass with the macAddress attribute.
6543 #
6544 # This module is written to be schema agnostic, and only depend on the
6545 # existence of attribute names.
6546 #
6547 # The LTSP configuration variables are saved directly using a
6548 # ltspConfig prefix and uppercasing the rest of the attribute name.
6549 # To set the SERVER variable, set the ltspConfigServer attribute.
6550 #
6551 # Some LDAP schema should be created with all the relevant
6552 # configuration settings. Something like this should work:
6553 #
6554 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6555 # SUP top
6556 # AUXILIARY
6557 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6558
6559 LDAPSERVER=$(debian-edu-ldapserver)
6560 if [ &quot;$LDAPSERVER&quot; ] ; then
6561 LDAPBASE=$(debian-edu-ldapserver -b)
6562 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6563 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6564 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6565 grep &#39;^ltspConfig&#39; | while read attr value ; do
6566 # Remove prefix and convert to upper case
6567 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6568 # bass value on to clients
6569 eval &quot;$attr=$value; export $attr&quot;
6570 done
6571 done
6572 fi
6573 &lt;/pre&gt;&lt;/blockquote&gt;
6574
6575 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6576 the while block might end up in a subshell causing the variables set
6577 there to not show up in ltsp-config, but if that is the case I am sure
6578 the code can be restructured to make sure the variables are passed on.
6579 I expect that can be solved with some testing. :)&lt;/p&gt;
6580
6581 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6582 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6583
6584 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6585 configuration in LDAP that was created around year 2000 by
6586 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6587 Xperience, Inc., 2000&lt;/a&gt;. I found its
6588 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6589 personal home page over at redhat.com.&lt;/p&gt;
6590 </description>
6591 </item>
6592
6593 <item>
6594 <title>jXplorer, a very nice LDAP GUI</title>
6595 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6596 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6597 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6598 <description>&lt;p&gt;Since
6599 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6600 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6601 LDAP GUI that is even better than luma. The java application
6602 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6603 moving LDAP objects and subtrees using drag-and-drop, and can
6604 authenticate using Kerberos. I have only tested the Kerberos
6605 authentication, but do not have a LDAP setup allowing me to rewrite
6606 LDAP with my test user yet. It is
6607 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6608 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6609 have with it is how it handle errors. If something go wrong, its
6610 non-intuitive behaviour require me to go through some query work list
6611 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6612 </description>
6613 </item>
6614
6615 <item>
6616 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6617 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6619 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6620 <description>&lt;p&gt;Here is a short update on my &lt;a
6621 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6622 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6623 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6624 not reporting the status for KDE, because the upgrade crashes when
6625 aptitude try because of missing conflicts
6626 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6627 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6628
6629 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6630 complete list of the installed packages. Based on this I see these
6631 differences when I did a test run today. As usual, I do not really
6632 know what the correct set of packages would be, but thought it best to
6633 publish the difference.&lt;/p&gt;
6634
6635 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6636
6637 &lt;blockquote&gt;&lt;p&gt;
6638 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6639 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6640 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6641 libgtksourceview-common libpt-1.10.10-plugins-alsa
6642 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6643 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6644 python-4suite-xml python-eggtrayicon python-gtkhtml2
6645 python-gtkmozembed svgalibg1 xserver-xephyr zip
6646 &lt;/p&gt;&lt;/blockquote&gt;
6647
6648 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6649
6650 &lt;blockquote&gt;&lt;p&gt;
6651 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6652 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6653 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6654 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6655 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6656 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6657 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6658 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6659 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6660 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6661 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6662 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6663 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6664 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6665 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6666 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6667 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6668 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6669 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6670 mysql-common swfdec-gnome totem-gstreamer wodim
6671 &lt;/p&gt;&lt;/blockquote&gt;
6672
6673 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6674
6675 &lt;blockquote&gt;&lt;p&gt;
6676 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6677 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6678 xserver-xorg-input-all xserver-xorg-input-evdev
6679 xserver-xorg-input-kbd xserver-xorg-input-mouse
6680 xserver-xorg-input-synaptics xserver-xorg-video-all
6681 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6682 xserver-xorg-video-chips xserver-xorg-video-cirrus
6683 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6684 xserver-xorg-video-glint xserver-xorg-video-i128
6685 xserver-xorg-video-i740 xserver-xorg-video-mach64
6686 xserver-xorg-video-mga xserver-xorg-video-neomagic
6687 xserver-xorg-video-nouveau xserver-xorg-video-nv
6688 xserver-xorg-video-r128 xserver-xorg-video-radeon
6689 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6690 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6691 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6692 xserver-xorg-video-sis xserver-xorg-video-sisusb
6693 xserver-xorg-video-tdfx xserver-xorg-video-tga
6694 xserver-xorg-video-trident xserver-xorg-video-tseng
6695 xserver-xorg-video-vesa xserver-xorg-video-vmware
6696 xserver-xorg-video-voodoo
6697 &lt;/p&gt;&lt;/blockquote&gt;
6698
6699 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6700
6701 &lt;blockquote&gt;&lt;p&gt;
6702 deskbar-applet xserver-xorg xserver-xorg-core
6703 xserver-xorg-input-wacom xserver-xorg-video-intel
6704 xserver-xorg-video-openchrome
6705 &lt;/p&gt;&lt;/blockquote&gt;
6706
6707 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6708 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6709 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6710 No idea when it hits Squeeze, but when it does I hope it will reduce
6711 the difference somewhat.
6712 </description>
6713 </item>
6714
6715 <item>
6716 <title>LUMA, a very nice LDAP GUI</title>
6717 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6718 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6719 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6720 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6721 directory in Debian Edu, and in the process I started to miss a GUI
6722 tool to browse the LDAP tree. The only one I was able to find in
6723 Debian/Squeeze and Lenny is
6724 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6725 be a great tool to get a overview of the current LDAP directory
6726 populated by default in Skolelinux. Thanks to it, I have been able to
6727 find empty and obsolete subtrees, misplaced objects and duplicate
6728 objects. It will be installed by default in Debian/Squeeze. If you
6729 are working with LDAP, give it a go. :)&lt;/p&gt;
6730
6731 &lt;p&gt;I did notice one problem with it I have not had time to report to
6732 the BTS yet. There is no .desktop file in the package, so the tool do
6733 not show up in the Gnome and KDE menus, but only deep down in in the
6734 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6735 released.&lt;/p&gt;
6736
6737 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6738 like to move objects and remove subtrees directly in the GUI, but have
6739 not found a way to do that with LUMA yet. So in the mean time, I use
6740 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6741
6742 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6743 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6744
6745 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6746 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6747 useful GUI alternative. It seem like a good tool, but is unmaintained
6748 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6749 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6750 </description>
6751 </item>
6752
6753 <item>
6754 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6755 <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>
6756 <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>
6757 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6758 <description>&lt;p&gt;A while back, I
6759 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6760 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6761 for storing DNS and DHCP information in LDAP to combine the two sets
6762 of information into one LDAP object representing a computer.&lt;/p&gt;
6763
6764 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6765 the dhcpHost object class auxiliary, to allow it to be combined with
6766 the dNSDomain object class, and thus forming one object for one
6767 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6768
6769 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6770 without also changing the assigned number for the object class, and I
6771 do not know enough about LDAP schema design to do that properly for
6772 Debian Edu.&lt;/p&gt;
6773
6774 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6775 the
6776 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6777 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6778 available today from IETF.&lt;/p&gt;
6779
6780 &lt;pre&gt;
6781 --- dhcp.schema (revision 65192)
6782 +++ dhcp.schema (working copy)
6783 @@ -376,7 +376,7 @@
6784 objectclass ( 2.16.840.1.113719.1.203.6.6
6785 NAME &#39;dhcpHost&#39;
6786 DESC &#39;This represents information about a particular client&#39;
6787 - SUP top
6788 + SUP top AUXILIARY
6789 MUST cn
6790 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6791 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6792 &lt;/pre&gt;
6793
6794 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6795 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6796 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6797
6798 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6799 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6800 </description>
6801 </item>
6802
6803 <item>
6804 <title>Calling tasksel like the installer, while still getting useful output</title>
6805 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6806 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6807 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6808 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6809 installs packages during the normal debian-installer run. Until now,
6810 I have ended up letting tasksel do the work, with the annoying problem
6811 of not getting any feedback at all when something fails (like a
6812 conffile question from dpkg or a download that fails), using code like
6813 this:
6814
6815 &lt;blockquote&gt;&lt;pre&gt;
6816 export DEBIAN_FRONTEND=noninteractive
6817 tasksel --new-install
6818 &lt;/pre&gt;&lt;/blockquote&gt;
6819
6820 This would invoke tasksel, let its automatic task selection pick the
6821 tasks to install, and continue to install the requested tasks without
6822 any output what so ever.
6823
6824 Recently I revisited this problem while working on the automatic
6825 package upgrade testing, because tasksel would some times hang without
6826 any useful feedback, and I want to see what is going on when it
6827 happen. Then it occured to me, I can parse the output from tasksel
6828 when asked to run in test mode, and use that aptitude command line
6829 printed by tasksel then to simulate the tasksel run. I ended up using
6830 code like this:
6831
6832 &lt;blockquote&gt;&lt;pre&gt;
6833 export DEBIAN_FRONTEND=noninteractive
6834 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6835 $cmd
6836 &lt;/pre&gt;&lt;/blockquote&gt;
6837
6838 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6839 --without-recommends -o APT::Install-Recommends=no -y install
6840 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6841 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6842 laptop task and all packages with priority standard , required and
6843 important, just like tasksel would have done it during
6844 installation.&lt;/p&gt;
6845
6846 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6847 install packages without using debconf-apt-progress, for use cases
6848 like this.&lt;/p&gt;
6849 </description>
6850 </item>
6851
6852 <item>
6853 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6854 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6855 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6856 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6857 <description>&lt;p&gt;My
6858 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6859 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6860 finally made the upgrade logs available from
6861 &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;.
6862 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6863 apt and aptitude, and found their differences interesting. This time
6864 I will only focus on their removal plans.&lt;/p&gt;
6865
6866 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6867 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6868 surprising part is that it want to remove xorg and all
6869 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6870 sure why. When asking aptitude to do the same, it want to remove 129
6871 packages, but most of them are library packages I suspect are no
6872 longer needed. Both of them want to remove bluetooth packages, which
6873 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6874
6875 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6876 which seem like a bad idea and xorg the same way as with Gnome. Asking
6877 aptitude for the same, it wants to remove 192 packages, none which are
6878 too surprising.&lt;/p&gt;
6879
6880 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6881 and avoided, and perhaps others as well. Here are the complete list
6882 of planned removals. The complete logs is available from the URL
6883 above. Note if you want to repeat these tests, that the upgrade test
6884 for kde+apt-get hung in the tasksel setup because of dpkg asking
6885 conffile questions. No idea why. I worked around it by using
6886 &#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
6887 continue.&lt;/p&gt;
6888
6889 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6890 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6891 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6892 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6893 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6894 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6895 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6896 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6897 xserver-xorg-input-kbd xserver-xorg-input-mouse
6898 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6899 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6900 xserver-xorg-video-ati xserver-xorg-video-chips
6901 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6902 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6903 xserver-xorg-video-glint xserver-xorg-video-i128
6904 xserver-xorg-video-i740 xserver-xorg-video-imstt
6905 xserver-xorg-video-intel xserver-xorg-video-mach64
6906 xserver-xorg-video-mga xserver-xorg-video-neomagic
6907 xserver-xorg-video-nsc xserver-xorg-video-nv
6908 xserver-xorg-video-openchrome xserver-xorg-video-r128
6909 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6910 xserver-xorg-video-rendition xserver-xorg-video-s3
6911 xserver-xorg-video-s3virge xserver-xorg-video-savage
6912 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6913 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6914 xserver-xorg-video-tga xserver-xorg-video-trident
6915 xserver-xorg-video-tseng xserver-xorg-video-v4l
6916 xserver-xorg-video-vesa xserver-xorg-video-vga
6917 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6918 xulrunner-1.9-gnome-support&lt;/p&gt;
6919
6920 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6921
6922 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6923 djvulibre-desktop finger gnome-app-install gnome-mount
6924 gnome-network-admin gnome-spell gnome-vfs-obexftp
6925 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6926 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6927 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6928 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6929 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6930 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6931 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6932 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6933 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6934 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6935 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6936 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6937 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6938 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6939 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6940 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6941 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6942 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6943 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6944 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6945 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6946 openoffice.org-writer2latex openssl-blacklist p7zip
6947 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6948 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6949 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6950 swfdec-mozilla totem-gstreamer update-manager wodim
6951 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6952 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6953 zip&lt;/p&gt;
6954
6955 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6956
6957 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6958 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6959 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6960 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6961 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6962 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6963 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6964 xserver-xorg-input-kbd xserver-xorg-input-mouse
6965 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6966 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6967 xserver-xorg-video-ati xserver-xorg-video-chips
6968 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6969 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6970 xserver-xorg-video-glint xserver-xorg-video-i128
6971 xserver-xorg-video-i740 xserver-xorg-video-imstt
6972 xserver-xorg-video-intel xserver-xorg-video-mach64
6973 xserver-xorg-video-mga xserver-xorg-video-neomagic
6974 xserver-xorg-video-nsc xserver-xorg-video-nv
6975 xserver-xorg-video-openchrome xserver-xorg-video-r128
6976 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6977 xserver-xorg-video-rendition xserver-xorg-video-s3
6978 xserver-xorg-video-s3virge xserver-xorg-video-savage
6979 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6980 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6981 xserver-xorg-video-tga xserver-xorg-video-trident
6982 xserver-xorg-video-tseng xserver-xorg-video-v4l
6983 xserver-xorg-video-vesa xserver-xorg-video-vga
6984 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6985
6986 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6987 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6988 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6989 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6990 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6991 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6992 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6993 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6994 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6995 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6996 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6997 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6998 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6999 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7000 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7001 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7002 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7003 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7004 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7005 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7006 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7007 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7008 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7009 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7010 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7011 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7012 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7013 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7014 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7015 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7016 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7017 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7018 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7019 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7020 texlive-common texlive-doc-base texlive-fonts-recommended
7021 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7022 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7023 xulrunner-1.9&lt;/p&gt;
7024
7025 </description>
7026 </item>
7027
7028 <item>
7029 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7030 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7032 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7033 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7034 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7035 have been discovered and reported in the process
7036 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7037 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7038 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7039 kdebase-workspace-data), and to get a more regular testing going on, I
7040 am working on a script to automate the test.&lt;/p&gt;
7041
7042 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7043 Gnome or KDE desktop installation inside the chroot before upgrading
7044 it. To ensure no services are started in the chroot, a policy-rc.d
7045 script is inserted. To make sure tasksel believe it is to install a
7046 desktop on a laptop, the tasksel tests are replaced in the chroot
7047 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7048
7049 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7050 currently always fail because udev refuses to upgrade with the kernel
7051 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7052 is created. The bug report
7053 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7054 this problem do not trigger in a chroot, but I touch the file anyway
7055 to make sure the upgrade go well. Testing on virtual and real
7056 hardware have failed me because of udev so far, and creating this file
7057 do the trick in such settings anyway. This is a
7058 &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
7059 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7060 maintainer because he lack the resources to rewrite udev to keep
7061 working with old kernels or something like that. I really wish the
7062 udev upstream would keep udev backwards compatible, to avoid such
7063 upgrade problem, but given that they fail to do so, I guess
7064 documenting the way out of this mess is the best option we got for
7065 Debian Squeeze.&lt;/p&gt;
7066
7067 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7068 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7069 trick:&lt;/p&gt;
7070
7071 &lt;blockquote&gt;&lt;pre&gt;
7072 #!/bin/sh
7073 set -ex
7074
7075 if [ &quot;$1&quot; ] ; then
7076 desktop=$1
7077 else
7078 desktop=gnome
7079 fi
7080
7081 from=lenny
7082 to=squeeze
7083
7084 exec &amp;lt; /dev/null
7085 unset LANG
7086 mirror=http://ftp.skolelinux.org/debian
7087 tmpdir=chroot-$from-upgrade-$to-$desktop
7088 fuser -mv .
7089 debootstrap $from $tmpdir $mirror
7090 chroot $tmpdir aptitude update
7091 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7092 #!/bin/sh
7093 exit 101
7094 EOF
7095 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7096 exit_cleanup() {
7097 umount $tmpdir/proc
7098 }
7099 mount -t proc proc $tmpdir/proc
7100 # Make sure proc is unmounted also on failure
7101 trap exit_cleanup EXIT INT
7102
7103 chroot $tmpdir aptitude -y install debconf-utils
7104
7105 # Make sure tasksel autoselection trigger. It need the test scripts
7106 # to return the correct answers.
7107 echo tasksel tasksel/desktop multiselect $desktop | \
7108 chroot $tmpdir debconf-set-selections
7109
7110 # Include the desktop and laptop task
7111 for test in desktop laptop ; do
7112 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7113 #!/bin/sh
7114 exit 2
7115 EOF
7116 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7117 done
7118
7119 DEBIAN_FRONTEND=noninteractive
7120 DEBIAN_PRIORITY=critical
7121 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7122 chroot $tmpdir tasksel --new-install
7123
7124 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7125 chroot $tmpdir aptitude update
7126 touch $tmpdir/etc/udev/kernel-upgrade
7127 chroot $tmpdir aptitude -y dist-upgrade
7128 fuser -mv
7129 &lt;/pre&gt;&lt;/blockquote&gt;
7130
7131 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7132 with aptitude, but I have not had time to look at how they behave
7133 differently so far. I hope to get a cron job running to do the test
7134 regularly and post the result on the web. The Gnome upgrade currently
7135 work, while the KDE upgrade fail because of the bug in
7136 kdebase-workspace-data&lt;/p&gt;
7137
7138 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7139 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7140 post, so I will refrain from trying. I can report that for Gnome,
7141 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7142 remove and 1 not upgraded and 1024MB need to be downloaded while for
7143 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7144 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7145
7146 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7147 is able to migrate to dependency based boot sequencing and parallel
7148 booting without a hitch. Was unsure if there were still bugs with
7149 packages failing to clean up their obsolete init.d script during
7150 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7151 packages.&lt;/p&gt;
7152 </description>
7153 </item>
7154
7155 <item>
7156 <title>Upstart or sysvinit - as init.d scripts see it</title>
7157 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7159 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7160 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7161 scripts to migrate (some of) their operations to upstart job while
7162 keeping the init.d for hurd and kfreebsd. The packages with such
7163 needs will need a way to get their init.d scripts to behave
7164 differently when used with sysvinit and with upstart. Because of
7165 this, I had a look at the environment variables set when a init.d
7166 script is running under upstart, and when it is not.&lt;/p&gt;
7167
7168 &lt;p&gt;With upstart, I notice these environment variables are set when a
7169 script is started from rcS.d/ (ignoring some irrelevant ones like
7170 COLUMNS):&lt;/p&gt;
7171
7172 &lt;blockquote&gt;&lt;pre&gt;
7173 DEFAULT_RUNLEVEL=2
7174 previous=N
7175 PREVLEVEL=
7176 RUNLEVEL=
7177 runlevel=S
7178 UPSTART_EVENTS=startup
7179 UPSTART_INSTANCE=
7180 UPSTART_JOB=rc-sysinit
7181 &lt;/pre&gt;&lt;/blockquote&gt;
7182
7183 &lt;p&gt;With sysvinit, these environment variables are set for the same
7184 script.&lt;/p&gt;
7185
7186 &lt;blockquote&gt;&lt;pre&gt;
7187 INIT_VERSION=sysvinit-2.88
7188 previous=N
7189 PREVLEVEL=N
7190 RUNLEVEL=S
7191 runlevel=S
7192 &lt;/pre&gt;&lt;/blockquote&gt;
7193
7194 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7195 sysvinit are not set by upstart. Not sure if it is intentional or not
7196 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7197
7198 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7199 looking for the UPSTART_JOB environment variable seem to be a good
7200 choice.&lt;/p&gt;
7201 </description>
7202 </item>
7203
7204 <item>
7205 <title>A manual for standards wars...</title>
7206 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7207 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7208 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7209 <description>&lt;p&gt;Via the
7210 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7211 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7212 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7213 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7214 following the standards wars of today.&lt;/p&gt;
7215 </description>
7216 </item>
7217
7218 <item>
7219 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7220 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7222 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7223 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7224 to get a list of the machine types in use thanks to the DMI
7225 information extracted from each machine. The script to do so is
7226 included in the sitesummary package, and here is example output from
7227 the Skolelinux build servers:&lt;/p&gt;
7228
7229 &lt;blockquote&gt;&lt;pre&gt;
7230 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7231 vendor count
7232 Dell Computer Corporation 1
7233 PowerEdge 1750 1
7234 IBM 1
7235 eserver xSeries 345 -[8670M1X]- 1
7236 Intel 2
7237 [no-dmi-info] 3
7238 maintainer:~#
7239 &lt;/pre&gt;&lt;/blockquote&gt;
7240
7241 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7242 provided in each machine. Here there are Intel machines without model
7243 information listed with Intel as vendor and no model, and virtual Xen
7244 machines listed as [no-dmi-info]. One can add -l as a command line
7245 option to list the individual machines.&lt;/p&gt;
7246
7247 &lt;p&gt;A larger list is
7248 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7249 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7250 provide the basic sitesummary report publicly. In their report there
7251 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7252 their machines, and as sitesummary is available in both distributions,
7253 it is trivial to get all of them to report to the same central
7254 collector.&lt;/p&gt;
7255 </description>
7256 </item>
7257
7258 <item>
7259 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7260 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7261 <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>
7262 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7263 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7264 start at boot when an NVidia video card is used is handled. The
7265 problem seem to be that the nvidia X.org driver uses a long time to
7266 initialize, and this duration is longer than kdm is configured to
7267 wait.&lt;/p&gt;
7268
7269 &lt;p&gt;I came across two bugs related to this issue,
7270 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7271 against initscripts and passed on to nvidia-glx when it became obvious
7272 that the nvidia drivers were involved, and
7273 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7274 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7275
7276 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7277 problem nvidia video card owners experience and make sure the Debian
7278 distribution work out of the box for these users. The nvidia driver
7279 maintainers expect kdm to be set up to wait longer, while kdm expect
7280 the nvidia driver maintainers to fix the driver to start faster, and
7281 while they wait for each other I guess the users end up switching to a
7282 distribution that work for them. I have no idea what the solution is,
7283 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7284
7285 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7286 </description>
7287 </item>
7288
7289 <item>
7290 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7291 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7292 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7293 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7294 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7295 The feature seem to hold up pretty well, but three fairly serious
7296 issues are known and should be solved:
7297
7298 &lt;p&gt;&lt;ul&gt;
7299
7300 &lt;li&gt;The wicd package seen to
7301 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7302 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7303 parallel booting is enabled. No idea why, but the wicd maintainer
7304 seem to be on the case.&lt;/li&gt;
7305
7306 &lt;li&gt;The nvidia X driver seem to
7307 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7308 triggered more easily when parallel booting is in effect. The
7309 maintainer is on the case.&lt;/li&gt;
7310
7311 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7312 sequencing (the shutdown is broken) when old file-rc users
7313 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7314 sysv-rc. One way to solve it would be for file-rc to create
7315 /etc/init.d/.legacy-bootordering, and another is to try to make
7316 sysv-rc more robust. Will investigate some more and probably upload a
7317 workaround in sysv-rc to help those trying to move from file-rc to
7318 sysv-rc get a working shutdown.&lt;/li&gt;
7319
7320 &lt;/ul&gt;&lt;/p&gt;
7321
7322 &lt;p&gt;All in all not many surprising issues, and all of them seem
7323 solvable before Squeeze is released. In addition to these there are
7324 some packages with bugs in their dependencies and run level settings,
7325 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7326
7327 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7328 the BTS, please usertag the report to get it to show up at
7329 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7330 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7331
7332 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7333 </description>
7334 </item>
7335
7336 <item>
7337 <title>More flexible firmware handling in debian-installer</title>
7338 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7339 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7340 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7341 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7342 found time today to return to the project. Having to spend less time
7343 working dependency based boot in debian, as it is almost complete now,
7344 definitely helped freeing some time.&lt;/p&gt;
7345
7346 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7347 include some firmware packages on the Debian Edu CDs, those needed to
7348 get disk and network controllers working. Without having these
7349 firmware packages available during installation, it is impossible to
7350 install Debian Edu on the given machine, and because our target group
7351 are non-technical people, asking them to provide firmware packages on
7352 an external medium is a support pain. Initially, I expected it to be
7353 enough to include the firmware packages on the CD to get
7354 debian-installer to find and use them. This proved to be wrong.
7355 Next, I hoped it was enough to symlink the relevant firmware packages
7356 to some useful location on the CD (tried /cdrom/ and
7357 /cdrom/firmware/). This also proved to not work, and at this point I
7358 found time to look at the debian-installer code to figure out what was
7359 going to work.&lt;/p&gt;
7360
7361 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7362 look revealed that it would only look for firmware packages outside
7363 the installation media, so the CD was never checked for firmware
7364 packages. It would only check USB sticks, floppies and other
7365 &quot;external&quot; media devices. Today I changed it to also look in the
7366 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7367 solve the problem I ran into with Debian edu. I also changed it to
7368 look in /firmware/, to make sure the installer also find firmware
7369 provided in the initrd when booting the installer via PXE, to allow us
7370 to provide the same feature in the PXE setup included in Debian
7371 Edu.&lt;/p&gt;
7372
7373 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7374 activated without asking if the license is accepted, I extended
7375 hw-detect to look for preinst scripts in the firmware packages, and
7376 run these before activating the firmware during installation. The
7377 license question is asked using debconf in the preinst, so this should
7378 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7379
7380 &lt;p&gt;If you want to discuss the details of these features, please
7381 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7382 </description>
7383 </item>
7384
7385 <item>
7386 <title>Parallellized boot is now the default in Debian/unstable</title>
7387 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7389 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7390 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7391 Debian/unstable for machines using dependency based boot sequencing.
7392 Apparently the testing of concurrent booting has been wider than
7393 expected, if I am to believe the
7394 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7395 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7396 with the feature this weekend, to give us some time to detect any
7397 remaining problems before Squeeze is frozen. If serious problems are
7398 detected, it is simple to change the default back to sequential boot.
7399 The upload of the new sysvinit package also activate a new upstream
7400 version.&lt;/p&gt;
7401
7402 More information about
7403 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7404 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7405 currently possible to disable parallel booting when one run into
7406 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7407
7408 &lt;blockquote&gt;&lt;pre&gt;
7409 CONCURRENCY=none
7410 &lt;/pre&gt;&lt;/blockquote&gt;
7411
7412 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7413 the BTS, please usertag the report to get it to show up at
7414 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7415 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7416 </description>
7417 </item>
7418
7419 <item>
7420 <title>Sitesummary tip: Listing MAC address of all clients</title>
7421 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7423 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7424 <description>&lt;p&gt;In the recent Debian Edu versions, the
7425 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7426 system&lt;/a&gt; is used to keep track of the machines in the school
7427 network. Each machine will automatically report its status to the
7428 central server after boot and once per night. The network setup is
7429 also reported, and using this information it is possible to get the
7430 MAC address of all network interfaces in the machines. This is useful
7431 to update the DHCP configuration.&lt;/p&gt;
7432
7433 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7434 ist all MAC addresses of all machines reporting to sitesummary. Run
7435 this on the collector host:&lt;/p&gt;
7436
7437 &lt;blockquote&gt;&lt;pre&gt;
7438 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7439 &lt;/pre&gt;&lt;/blockquote&gt;
7440
7441 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7442 line per machine and with space between the MAC addresses.&lt;/p&gt;
7443
7444 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7445 addresses for hosts, it would be possible to extend this to fetch
7446 machine information from sitesummary and update the DHCP and DNS
7447 tables in LDAP using this information. Such tool is unfortunately not
7448 written yet.&lt;/p&gt;
7449 </description>
7450 </item>
7451
7452 <item>
7453 <title>systemd, an interesting alternative to upstart</title>
7454 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7456 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7457 <description>&lt;p&gt;The last few days a new boot system called
7458 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7459 has been
7460 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7461
7462 to the free software world. I have not yet had time to play around
7463 with it, but it seem to be a very interesting alternative to
7464 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7465 a good alternative for Debian when we are able to switch to an event
7466 based boot system. Tollef is
7467 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7468 systemd into Debian, and I look forward to seeing how well it work. I
7469 like the fact that systemd handles init.d scripts with dependency
7470 information natively, allowing them to run in parallel where upstart
7471 at the moment do not.&lt;/p&gt;
7472
7473 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7474 platform support. It only work on recent Linux kernels, and also need
7475 some new kernel features enabled to function properly. This means
7476 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7477 system. Not sure how that will be handled if systemd proves to be the
7478 way forward.&lt;/p&gt;
7479
7480 &lt;p&gt;In the mean time, based on the
7481 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7482 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7483 decided to enable full parallel booting as the default in Debian as
7484 soon as possible (probably this weekend or early next week), to see if
7485 there are any remaining serious bugs in the init.d dependencies. A
7486 new version of the sysvinit package implementing this change is
7487 already in experimental. If all go well, Squeeze will be released
7488 with parallel booting enabled by default.&lt;/p&gt;
7489 </description>
7490 </item>
7491
7492 <item>
7493 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7494 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7495 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7496 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7497 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7498 complete, so complete that it is actually possible to run all the
7499 init.d scripts in parallell based on these dependencies. If you want
7500 to test your Squeeze system, make sure
7501 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7502 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7503 /etc/default/rcS:&lt;/p&gt;
7504
7505 &lt;blockquote&gt;&lt;pre&gt;
7506 CONCURRENCY=makefile
7507 &lt;/pre&gt;&lt;/blockquote&gt;
7508
7509 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7510 scripts in parallel using the dependency information stored in
7511 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7512 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7513 to try to start the kdm and gdm scripts as early as possible, and will
7514 start the facilities required by kdm or gdm as early as possible to
7515 make this happen.&lt;/p&gt;
7516
7517 &lt;p&gt;Give it a try, and see if you like the result. If some services
7518 fail to start properly, it is most likely because they have incomplete
7519 init.d script dependencies in their startup script (or some of their
7520 dependent scripts have incomplete dependencies). Report bugs and get
7521 the package maintainers to fix it. :)&lt;/p&gt;
7522
7523 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7524 manage to get the init.d script dependencies complete and correct. I
7525 expect we will get there in Squeeze+1, if we get manage to test and
7526 fix the remaining issues.&lt;/p&gt;
7527
7528 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7529 the BTS, please usertag the report to get it to show up at
7530 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7531 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7532 </description>
7533 </item>
7534
7535 <item>
7536 <title>Debian has switched to dependency based boot sequencing</title>
7537 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7538 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7539 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7540 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7541 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7542 have been migrated to using dependency based boot sequencing. This
7543 conclude work me and others have been doing for the last three days.
7544 It feels great to see this finally part of the default Debian
7545 installation. Now we just need to weed out the last few problems that
7546 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7547
7548 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7549 fixing the more fundamental problem of handing the event based
7550 non-predictable kernel in the early boot.&lt;/p&gt;
7551 </description>
7552 </item>
7553
7554 <item>
7555 <title>Taking over sysvinit development</title>
7556 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7558 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7559 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7560 the existing sysvinit upstream developer, I decided a few weeks ago to
7561 take over the package and become the new upstream. The number of
7562 patches to track for the Debian package was becoming a burden, and the
7563 lack of synchronization between the distribution made it hard to keep
7564 the package up to date.&lt;/p&gt;
7565
7566 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7567 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7568 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7569 and Fedora), based on the patches currently in use in these
7570 distributions. We Debian maintainers plan to move to this tarball as
7571 the new upstream as soon as we find time to do the merge. Since the
7572 new tarball was created, we agreed with Werner at SuSe to make a new
7573 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7574 development there. The project is registered and currently waiting
7575 for approval by the Savannah administrators, and as soon as it is
7576 approved, we will import the old versions from svn and continue
7577 working on the future release.&lt;/p&gt;
7578
7579 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7580 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7581 </description>
7582 </item>
7583
7584 <item>
7585 <title>Debian boots quicker and quicker</title>
7586 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7587 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7588 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7589 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7590 people involved in the boot system on Debian and Ubuntu, to see if we
7591 could find more ways to speed up the boot system. This was an Ubuntu
7592 funded
7593 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7594 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7595 of boot systems, and ways to handle the increasing number of boot
7596 issues introduced by the Linux kernel becoming more and more
7597 asynchronous and event base. The Ubuntu approach using udev and
7598 upstart might be a good way forward. Time will show.&lt;/p&gt;
7599
7600 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7601 process in Debian. All of these should be applied to get a quick
7602 boot:&lt;/p&gt;
7603
7604 &lt;ul&gt;
7605
7606 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7607
7608 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7609 clock is in UTC.&lt;/li&gt;
7610
7611 &lt;li&gt;Install and activate the insserv package to enable
7612 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7613 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7614
7615 &lt;/ul&gt;
7616
7617 These points are based on the Google summer of code work done by
7618 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7619 Villegas&lt;/a&gt;.
7620
7621 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7622 unstable yesterday. When we tested it, we were able to cut 6 seconds
7623 from the boot sequence. It depend on very correct dependency
7624 declaration in all init.d scripts, so I expect us to find edge cases
7625 where the dependences in some scripts are slightly wrong when we start
7626 using this.&lt;/p&gt;
7627
7628 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7629 introduced by Raphael Geissert today, one that could affect the
7630 startup speed as well. Instead of starting some scripts concurrently
7631 from rcS.d/ and another set of scripts from rc2.d/, it would be
7632 possible to run a of them in the same process. A quick way to test
7633 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7634 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7635 </description>
7636 </item>
7637
7638 <item>
7639 <title>BSAs påstander om piratkopiering møter motstand</title>
7640 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7641 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7642 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7643 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7644 programvareselskapene som Microsoft og Apple, publisert en rapport der
7645 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7646 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7647 dager siden kom
7648 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7649 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7650 dagene. Et spesielt interessant kommentar fra Sverige,
7651 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7652 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7653
7654 &lt;blockquote&gt;
7655 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7656 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7657 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7658 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7659 &lt;/blockquote&gt;
7660
7661 &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
7662 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7663 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7664 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7665 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7666
7667 &lt;p&gt;Fant lenkene via &lt;a
7668 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7669 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7670 </description>
7671 </item>
7672
7673 <item>
7674 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7675 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7676 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7677 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7678 <description>&lt;p&gt;Kom over
7679 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7680 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7681 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7682 jobber til daglig. En rask opptelling forteller meg at vi har 490
7683 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7684 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7685 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7686 </description>
7687 </item>
7688
7689 <item>
7690 <title>Kryptert harddisk - naturligvis</title>
7691 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7692 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7693 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7694 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7695 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7696 når en tar tap av arbeidstid, fortrolige dokumenter,
7697 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7698 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7699 til at jeg har kryptert harddisken på både kontormaskinen og min
7700 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7701 komme på avveie, den første informasjon relatert til jobben min ved
7702 Universitetet i Oslo, og den andre relatert til blant annet
7703 foreningsarbeide. Kryptering av diskene gjør at det er lite
7704 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7705 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7706 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7707 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7708 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7709 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7710 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7711 det er gjort slik jeg gjør det er minimale, og gevinstene er
7712 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7713 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7714
7715 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7716 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7717 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7718 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7719 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7720 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7721 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7722 betydelige.&lt;/p&gt;
7723 </description>
7724 </item>
7725
7726 <item>
7727 <title>Two projects that have improved the quality of free software a lot</title>
7728 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7730 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7731 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7732 quality of free software, and I wanted to mention both in case someone
7733 do not yet know them.&lt;/p&gt;
7734
7735 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7736 tool to detect and expose errors in the memory handling of programs.
7737 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7738 and it will report any problems on stdout. It is even better if the
7739 program include debug information. With debug information, it is able
7740 to report the source file name and line number where the problem
7741 occurs. It can report things like &#39;reading past memory block in file
7742 X line N, the memory block was allocated in file Y, line M&#39;, and
7743 &#39;using uninitialised value in control logic&#39;. This tool has made it
7744 trivial to investigate reproducible crash bugs in programs, and have
7745 reduced the number of this kind of bugs in free software a lot.
7746
7747 &lt;p&gt;The second one is
7748 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7749 a source code checker. It is able to process the source of a program
7750 and find problems in the logic without running the program. It
7751 started out as the Stanford Checker and became well known when it was
7752 used to find bugs in the Linux kernel. It is now a commercial tool
7753 and the company behind it is running
7754 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7755 free software community, where a lot of free software projects get
7756 their source checked for free. Several thousand defects have been
7757 found and fixed so far. It can find errors like &#39;lock L taken in file
7758 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7759 Y lines O to P can never be executed&#39;. The projects included in the
7760 community service project have managed to get rid of a lot of
7761 reliability problems thanks to Coverity.&lt;/p&gt;
7762
7763 &lt;p&gt;I believe tools like this, that are able to automatically find
7764 errors in the source, are vital to improve the quality of software and
7765 make sure we can get rid of the crashing and failing software we are
7766 surrounded by today.&lt;/p&gt;
7767 </description>
7768 </item>
7769
7770 <item>
7771 <title>No patch is not better than a useless patch</title>
7772 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7773 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7774 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7775 <description>&lt;p&gt;Julien Blache
7776 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7777 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7778 patch allow one to discuss a concrete and proposed solution, and also
7779 prove that the issue at hand is important enough for someone to spent
7780 time on fixing it. No patch do not provide any of these positive
7781 properties.&lt;/p&gt;
7782 </description>
7783 </item>
7784
7785 <item>
7786 <title>Standardize on protocols and formats, not vendors and applications</title>
7787 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7789 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7790 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7791 very good one to form a long lived computer infrastructure. It is the
7792 simple one, lost by many in todays computer industry: Standardize on
7793 open network protocols and open exchange/storage formats, not applications.
7794 Applications come and go, while protocols and files tend to stay, and
7795 thus one want to make it easy to change application and vendor, while
7796 avoiding conversion costs and locking users to a specific platform or
7797 application.&lt;/p&gt;
7798
7799 &lt;p&gt;This approach make it possible to replace the client applications
7800 independently of the server applications. One can even allow users to
7801 use several different applications as long as they handle the selected
7802 protocol and format. In the normal case, only one client application
7803 is recommended and users only get help if they choose to use this
7804 application, but those that want to deviate from the easy path are not
7805 blocked from doing so.&lt;/p&gt;
7806
7807 &lt;p&gt;It also allow us to replace the server side without forcing the
7808 users to replace their applications, and thus allow us to select the
7809 best server implementation at any moment, when scale and resouce
7810 requirements change.&lt;/p&gt;
7811
7812 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7813 open formats, but I would never recommend standardizing on a single
7814 application that do not use open network protocol or open formats.&lt;/p&gt;
7815 </description>
7816 </item>
7817
7818 <item>
7819 <title>Returning from Skolelinux developer gathering</title>
7820 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7821 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7822 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7823 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7824 Edu/Skolelinux development gathering. I got a bit done tuning the
7825 desktop, and looked into the dynamic service location protocol
7826 implementation avahi. It look like it could be useful for us. Almost
7827 30 people participated, and I believe it was a great environment to
7828 get to know the Skolelinux system. Walter Bender, involved in the
7829 development of the Sugar educational platform, presented his stuff and
7830 also helped me improve my OLPC installation. He also showed me that
7831 his Turtle Art application can be used in standalone mode, and we
7832 agreed that I would help getting it packaged for Debian. As a
7833 standalone application it would be great for Debian Edu. We also
7834 tried to get the video conferencing working with two OLPCs, but that
7835 proved to be too hard for us. The application seem to need more work
7836 before it is ready for me. I look forward to getting home and relax
7837 now. :)&lt;/p&gt;
7838 </description>
7839 </item>
7840
7841 <item>
7842 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7843 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7844 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7845 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7846 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7847 optimal. There is RFC 2307 documenting one way to store NIS maps in
7848 LDAP, and a modified version of this normally called RFC 2307bis, with
7849 some modifications to be compatible with Active Directory. The RFC
7850 specification handle the content of a lot of system databases, but do
7851 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7852
7853 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7854 we would like to store information about users, SMB clients/hosts,
7855 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7856 and LTSP configuration in LDAP. These objects have a lot in common,
7857 but with the current LDAP schemas it is not possible to have one
7858 object per entity. For example, one need to have at least three LDAP
7859 objects for a given computer, one with the SMB related stuff, one with
7860 DNS information and another with DHCP information. The schemas
7861 provided for DNS and DHCP are impossible to combine into one LDAP
7862 object. In addition, it is impossible to implement quick queries for
7863 netgroup membership, because of the way NIS triples are implemented.
7864 It just do not scale. I believe it is time for a few RFC
7865 specifications to cleam up this mess.&lt;/p&gt;
7866
7867 &lt;p&gt;I would like to have one LDAP object representing each computer in
7868 the network, and this object can then keep the SMB (ie host key), DHCP
7869 (mac address/name) and DNS (name/IP address) settings in one place.
7870 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7871
7872 &lt;p&gt;I would also like to have a quick way to map from a user or
7873 computer and to the net group this user or computer is a member.&lt;/p&gt;
7874
7875 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7876 in this regard, and the unix side need to catch up. Time to start a
7877 new IETF work group?&lt;/p&gt;
7878 </description>
7879 </item>
7880
7881 <item>
7882 <title>Endelig er Debian Lenny gitt ut</title>
7883 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7884 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7885 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7886 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7887 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7888 Et langt steg videre for Debian-prosjektet, og en rekke nye
7889 programpakker blir nå tilgjengelig for de av oss som bruker den
7890 stabile utgaven av Debian. Neste steg er nå å få
7891 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7892 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7893 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7894 slippes løs på skolene. Takk til alle debian-utviklerne som har
7895 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7896 bootsekvens tilgjengelig i stabil utgave, vha pakken
7897 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7898 </description>
7899 </item>
7900
7901 <item>
7902 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7903 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7904 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7905 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7906 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7907 Oslo. Most of Saturday was used for the general assemly for the
7908 member organization, but the rest of the weekend I used to tune the
7909 LTSP installation. LTSP now work out of the box on the 10-network.
7910 Acer Aspire One proved to be a very nice thin client, with both
7911 screen, mouse and keybard in a small box. Was working on getting the
7912 diskless workstation setup configured out of the box, but did not
7913 finish it before the weekend was up.&lt;/p&gt;
7914
7915 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7916 the Brazilian group, so that will have to wait for the next
7917 development gathering. Would love to have the Debian Edu installer
7918 automatically detect and configure a multiseat setup when it find one
7919 of these cards.&lt;/p&gt;
7920 </description>
7921 </item>
7922
7923 <item>
7924 <title>The sorry state of multimedia browser plugins in Debian</title>
7925 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7926 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7927 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7928 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7929 plugins available in Debian Lenny, to see which one we should use by
7930 default in Debian Edu. We need an embedded video playing plugin with
7931 control buttons to pause or stop the video, and capable of streaming
7932 all the multimedia content available on the web. The test results and
7933 notes are available on
7934 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7935 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7936 fill this need. My personal video player favorite, VLC, has a really
7937 bad plugin which fail on a lot of the test pages. A lot of the MIME
7938 types I would expect to work with any free software player (like
7939 video/ogg), just do not work. And simple formats like the
7940 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7941 totem and vlc plugins. I hope the situation will improve soon. No
7942 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7943
7944 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7945 be the only one fitting our needs. :/&lt;/p&gt;
7946 </description>
7947 </item>
7948
7949 </channel>
7950 </rss>