]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
e12afb5f424c4ee12e445b12d3da6d694924fe21
[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>The life and death of a laptop battery</title>
11 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
13 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
14 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
15 But this do not last. The last few laptops gave me a feeling that
16 within a year, the life time is just a fraction of what it used to be,
17 and it slowly become painful to use the laptop without power connected
18 all the time. Because of this, when I got a new Thinkpad X230 laptop
19 about two years ago, I decided to monitor its battery state to have
20 more hard facts when the battery started to fail.&lt;/p&gt;
21
22 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
23
24 &lt;p&gt;First I tried to find a sensible Debian package to record the
25 battery status, assuming that this must be a problem already handled
26 by someone else. I found
27 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
28 which collects statistics from the battery, but it was completely
29 broken. I sent a few suggestions to the maintainer, but decided to
30 write my own collector as a shell script while I waited for feedback
31 from him. Via
32 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
33 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
34 discovered
35 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
36 available in Debian.&lt;/p&gt;
37
38 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
39 battery stats ever since. Now my
40 /var/log/hjemmenett-battery-status.log file contain around 115,000
41 measurements, from the time the battery was working great until now,
42 when it is unable to charge above 7% of original capacity. My
43 collector shell script is quite simple and look like this:&lt;/p&gt;
44
45 &lt;pre&gt;
46 #!/bin/sh
47 # Inspired by
48 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
49 # See also
50 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
51 logfile=/var/log/hjemmenett-battery-status.log
52
53 files=&quot;manufacturer model_name technology serial_number \
54 energy_full energy_full_design energy_now cycle_count status&quot;
55
56 if [ ! -e &quot;$logfile&quot; ] ; then
57 (
58 printf &quot;timestamp,&quot;
59 for f in $files; do
60 printf &quot;%s,&quot; $f
61 done
62 echo
63 ) &gt; &quot;$logfile&quot;
64 fi
65
66 log_battery() {
67 # Print complete message in one echo call, to avoid race condition
68 # when several log processes run in parallel.
69 msg=$(printf &quot;%s,&quot; $(date +%s); \
70 for f in $files; do \
71 printf &quot;%s,&quot; $(cat $f); \
72 done)
73 echo &quot;$msg&quot;
74 }
75
76 cd /sys/class/power_supply
77
78 for bat in BAT*; do
79 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
80 done
81 &lt;/pre&gt;
82
83 &lt;p&gt;The script is called when the power management system detect a
84 change in the power status (power plug in or out), and when going into
85 and out of hibernation and suspend. In addition, it collect a value
86 every 10 minutes. This make it possible for me know when the battery
87 is discharging, charging and how the maximum charge change over time.
88 The code for the Debian package
89 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
90 available on github&lt;/a&gt;.&lt;/p&gt;
91
92 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
93
94 &lt;pre&gt;
95 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
96 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
97 [...]
98 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
99 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
100 &lt;/pre&gt;
101
102 &lt;p&gt;I wrote a small script to create a graph of the charge development
103 over time. This graph depicted above show the slow death of my laptop
104 battery.&lt;/p&gt;
105
106 &lt;p&gt;But why is this happening? Why are my laptop batteries always
107 dying in a year or two, while the batteries of space probes and
108 satellites keep working year after year. If we are to believe
109 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
110 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
111 chance, and the fix is to not charge the Lithium-ion batteries to 100%
112 all the time, but to stay below 90% of full charge most of the time.
113 I&#39;ve been told that the Tesla electric cars
114 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
115 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
116 100% when preparing for a longer trip (not that I would want a car
117 like Tesla where rights to privacy is abandoned, but that is another
118 story), which I guess is the option we should have for laptops on
119 Linux too.&lt;/p&gt;
120
121 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
122 stop charging at 80%, unless requested to charge to 100% once in
123 preparation for a longer trip? I found
124 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
125 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
126 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
127 load).&lt;/p&gt;
128
129 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
130 at the start. I also wonder why the &quot;full capacity&quot; increases some
131 times, and if it is possible to repeat the process to get the battery
132 back to design capacity. And I wonder if the discharge and charge
133 speed change over time, or if this stay the same. I did not yet try
134 to write a tool to calculate the derivative values of the battery
135 level, but suspect some interesting insights might be learned from
136 those.&lt;/p&gt;
137
138 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
139 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
140 packages instead of the tp-smapi-dkms package I had tried to use
141 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
142 and stop. I&#39;ve done so now, but expect my existing battery is toast
143 and need to be replaced. The proposal is unfortunately Thinkpad
144 specific.&lt;/p&gt;
145 </description>
146 </item>
147
148 <item>
149 <title>New laptop - some more clues and ideas based on feedback</title>
150 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
151 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
152 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
153 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
154 need for a new laptop, and provided very useful feedback. I wish to
155 thank every one of these. Several pointed me to the possibility of
156 fixing my X230, and I am already in the process of getting Lenovo to
157 do so thanks to the on site, next day support contract covering the
158 machine. But the battery is almost useless (I expect to replace it
159 with a non-official battery) and I do not expect the machine to live
160 for many more years, so it is time to plan its replacement. If I did
161 not have a support contract, it was suggested to find replacement parts
162 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
163 might present a language barrier as I do not understand French.&lt;/p&gt;
164
165 &lt;p&gt;One tip I got was to use the
166 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
167 compare laptop models. It seem to have more models available than
168 prisjakt.no. Another tip I got from someone I know have similar
169 keyboard preferences was that the HP EliteBook 840 keyboard is not
170 very good, and this matches my experience with earlier EliteBook
171 keyboards I tested. Because of this, I will not consider it any further.
172
173 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
174 newest Thinkpad X model. The keyboard reintroduces mouse buttons
175 (which is missing from the X240), and is working fairly well with
176 Debian Sid/Unstable according to
177 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
178 got on the keyboard quality are not consistent. Some say the keyboard
179 is good, others say it is ok, while others say it is not very good.
180 Those with experience from X41 and and X60 agree that the X250
181 keyboard is not as good as those trusty old laptops, and suggest I
182 keep and fix my X230 instead of upgrading, or get a used X230 to
183 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
184 activity and battery status, which is very convenient on my X230. I&#39;m
185 also told that the CPU fan is running very often, making it a bit
186 noisy. In any case, the X250 do not work out of the box with Debian
187 Stable/Jessie, one of my requirements.&lt;/p&gt;
188
189 &lt;p&gt;I have also gotten a few vendor proposals, one was
190 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
191 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
192 The latter look very attractive to me.&lt;/p&gt;
193
194 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
195 as I keep looking for a replacement.&lt;/p&gt;
196
197 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
198 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
199 different
200 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
201 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
202 </description>
203 </item>
204
205 <item>
206 <title>Time to find a new laptop, as the old one is broken after only two years</title>
207 <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>
208 <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>
209 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
210 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
211 replacement soon. The left 5 cm of the screen on my Thinkpad X230
212 started flickering yesterday, and I suspect the cause is a broken
213 cable, as changing the angle of the screen some times get rid of the
214 flickering.&lt;/p&gt;
215
216 &lt;p&gt;My requirements have not really changed since I bought it, and is
217 still as
218 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
219 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
220 good help from
221 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
222 where I could select at least a few of the requirements (mouse pin,
223 wifi, weight) and go through the rest manually. Three button mouse
224 and a good keyboard is not available as an option, and all the three
225 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
226 G2) lack three mouse buttons). It is also unclear to me how good the
227 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
228 the keyboard, even if the quality and robustness in the X series have
229 deteriorated since X41.&lt;/p&gt;
230
231 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
232 seem sensible to me? Are there better services around to search the
233 set of available laptops for features? Please send me an email if you
234 have suggestions.&lt;/p&gt;
235
236 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
237 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
238 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
239 </description>
240 </item>
241
242 <item>
243 <title>How to stay with sysvinit in Debian Jessie</title>
244 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
245 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
246 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
247 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
248 sysvinit as its boot system by default. But how can one keep using
249 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
250 courtesy of
251 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
252 Schubert&lt;/a&gt; and
253 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
254 McVittie&lt;/a&gt;.
255
256 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
257 keep sysvinit as your boot system, create a file
258 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
259 you upgrade:&lt;/p&gt;
260
261 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
262 Package: systemd-sysv
263 Pin: release o=Debian
264 Pin-Priority: -1
265 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
266
267 &lt;p&gt;This file content will tell apt and aptitude to not consider
268 installing systemd-sysv as part of any installation and upgrade
269 solution when resolving dependencies, and thus tell it to avoid
270 systemd as a default boot system. The end result should be that the
271 upgraded system keep using sysvinit.&lt;/p&gt;
272
273 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
274 get sysvinit installed by default (debootstrap used by
275 debian-installer have no option for this), but one can tell the
276 installer to switch to sysvinit before the first boot. Either by
277 using a kernel argument to the installer, or by adding a line to the
278 preseed file used. First, the kernel command line argument:
279
280 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
281 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
282 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
283
284 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
285
286 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
287 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
288 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
289
290 &lt;p&gt;One can of course also do this after the first boot by installing
291 the sysvinit-core package.&lt;/p&gt;
292
293 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
294 sysvinit boot sequence in Debian have several hardware specific bugs
295 on Linux caused by the fact that it is unpredictable when hardware
296 devices show up during boot. But on the other hand, the new default
297 boot system still have a few rough edges I hope will be fixed before
298 Jessie is released.&lt;/p&gt;
299
300 &lt;p&gt;Update 2014-11-26: Inspired by
301 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
302 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
303 line.&lt;/p&gt;
304 </description>
305 </item>
306
307 <item>
308 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
309 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
310 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
311 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
312 <description>&lt;p&gt;The right to communicate with your friends and family in private,
313 without anyone snooping, is a right every citicen have in a liberal
314 democracy. But this right is under serious attack these days.&lt;/p&gt;
315
316 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
317 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
318 the whisleblower Snowden) more expensive for Internet email,
319 is to deliver all email using SMTP via Tor. Such SMTP option would be
320 a nice addition to the FreedomBox project if we could send email
321 between FreedomBox machines without leaking metadata about the emails
322 to the people peeking on the wire. I
323 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
324 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
325 lot of useful feedback and suggestions. It also became obvious to me
326 that this was not a novel idea, as the same idea was tested and
327 documented by Johannes Berg as early as 2006, and both
328 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
329 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
330 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
331
332 &lt;p&gt;To implement such system one need to set up a Tor hidden service
333 providing the SMTP protocol on port 25, and use email addresses
334 looking like username@hidden-service-name.onion. With such addresses
335 the connections to port 25 on hidden-service-name.onion using Tor will
336 go to the correct SMTP server. To do this, one need to configure the
337 Tor daemon to provide the hidden service and the mail server to accept
338 emails for this .onion domain. To learn more about Exim configuration
339 in Debian and test the design provided by Johannes Berg in his FAQ, I
340 set out yesterday to create a Debian package for making it trivial to
341 set up such SMTP over Tor service based on Debian. Getting it to work
342 were fairly easy, and
343 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
344 source code for the Debian package&lt;/a&gt; is available from github. I
345 plan to move it into Debian if further testing prove this to be a
346 useful approach.&lt;/p&gt;
347
348 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
349 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
350 get rid of exim4). Install tor, clone the git repository mentioned
351 above, build the deb and install it on the machine. Next, run
352 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
353 the instructions to get the service up and running. Restart tor and
354 exim when it is done, and test mail delivery using swaks like
355 this:&lt;/p&gt;
356
357 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
358 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
359 --to fbx@dutlqrrmjhtfa3vp.onion
360 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
361
362 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
363 address with your own address to test your server. :)&lt;/p&gt;
364
365 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
366 easier and more automatic. Especially the tor setup need more work.
367 Also, the package include a tor-smtp tool written in C, but its task
368 should probably be rewritten in some script language to make the deb
369 architecture independent. It would probably also make the code easier
370 to review. The tor-smtp tool currently need to listen on a socket for
371 exim to talk to it and is started using xinetd. It would be better if
372 no daemon and no socket is needed. I suspect it is possible to get
373 exim to run a command line tool for delivery instead of talking to a
374 socket, and hope to figure out how in a future version of this
375 system.&lt;/p&gt;
376
377 &lt;p&gt;Until I wipe my test machine, I can be reached using the
378 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
379 SMTorP. :)&lt;/p&gt;
380 </description>
381 </item>
382
383 <item>
384 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
385 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
386 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
387 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
388 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
389 alioth.debian.org, you know the web interface is fairly slow to
390 operate. First you visit one web page, enter the moderation password
391 and get a new page shown with a list of all the messages to moderate
392 and various options for each email address. This take a while for
393 every list you moderate, and you need to do it regularly to do a good
394 job as a list moderator. But there is a quick alternative,
395 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
396 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
397 to moderate in a fraction of a second. Here is a test run on two
398 lists I recently took over:&lt;/p&gt;
399
400 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
401 % time listadmin xiph
402 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
403 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
404
405 real 0m1.709s
406 user 0m0.232s
407 sys 0m0.012s
408 %
409 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
410
411 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
412 there are no message in the moderation queue. Every morning I
413 currently moderate 68 mailman lists, and it normally take around two
414 minutes. When I took over the two pkg-xiph lists above a few days
415 ago, there were 400 emails waiting in the moderator queue. It took me
416 less than 15 minutes to process them all using the listadmin
417 program.&lt;/p&gt;
418
419 &lt;p&gt;If you install
420 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
421 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
422 with content like this, the moderation task is a breeze:&lt;/p&gt;
423
424 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
425 username username@example.org
426 spamlevel 23
427 default discard
428 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
429
430 password secret
431 adminurl https://{domain}/mailman/admindb/{list}
432 mailman-list@lists.example.com
433
434 password hidden
435 other-list@otherserver.example.org
436 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
437
438 &lt;p&gt;There are other options to set as well. Check the manual page to
439 learn the details.&lt;/p&gt;
440
441 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
442 the SSL certificate is self signed or not properly signed by a
443 generally accepted signing authority, you can set a environment
444 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
445
446 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
447 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
448 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
449
450 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
451 can provide an argument to the listadmin script like I do in the
452 initial screen dump (the xiph argument). Using an argument, only
453 lists matching the argument string will be processed. This make it
454 quick to accept messages if you notice the moderation request in your
455 email.&lt;/p&gt;
456
457 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
458 mailing lists, as I simply do not have time to spend on that if the
459 process was any slower. The listadmin program have saved me hours of
460 time I could spend elsewhere over the years. It truly is nice free
461 software.&lt;/p&gt;
462
463 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
464 activities, please send Bitcoin donations to my address
465 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
466
467 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
468 configuration example. Also, I&#39;ve been told that the
469 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
470 sure why.&lt;/p&gt;
471 </description>
472 </item>
473
474 <item>
475 <title>Debian Jessie, PXE and automatic firmware installation</title>
476 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
477 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
478 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
479 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
480 problem that the WiFi card require some firmware to work properly.
481 And it has been a pain to fix this using preseeding in Debian.
482 Normally something more is needed. But thanks to
483 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
484 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
485 to do this using simple preseeding.&lt;/p&gt;
486
487 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
488 firmware for the hardware found in the machine (actually, requested by
489 the kernel modules for the hardware). (It can also install user space
490 programs supporting the hardware detected, but that is not the focus
491 of this story.)&lt;/p&gt;
492
493 &lt;p&gt;To get this working in the default installation, two preeseding
494 values are needed. First, the isenkram-cli package must be installed
495 into the target chroot (aka the hard drive) before tasksel is executed
496 in the pkgsel step of the debian-installer system. This is done by
497 preseeding the base-installer/includes debconf value to include the
498 isenkram-cli package. The package name is next passed to debootstrap
499 for installation. With the isenkram-cli package in place, tasksel
500 will automatically use the isenkram tasks to detect hardware specific
501 packages for the machine being installed and install them, because
502 isenkram-cli contain tasksel tasks.&lt;/p&gt;
503
504 &lt;p&gt;Second, one need to enable the non-free APT repository, because
505 most firmware unfortunately is non-free. This is done by preseeding
506 the apt-mirror-setup step. This is unfortunate, but for a lot of
507 hardware it is the only option in Debian.&lt;/p&gt;
508
509 &lt;p&gt;The end result is two lines needed in your preseeding file to get
510 firmware installed automatically by the installer:&lt;/p&gt;
511
512 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
513 base-installer base-installer/includes string isenkram-cli
514 apt-mirror-setup apt-setup/non-free boolean true
515 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
516
517 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
518 both firmware and user space packages when using this method. It also
519 do not work well, so use version 0.15 or later. Installing both
520 firmware and user space packages might give you a bit more than you
521 want, so I decided to split the tasksel task in two, one for firmware
522 and one for user space programs. The firmware task is enabled by
523 default, while the one for user space programs is not. This split is
524 implemented in the package currently in unstable.&lt;/p&gt;
525
526 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
527 this recipe work for you. :)&lt;/p&gt;
528
529 &lt;p&gt;So, I bet you are wondering, how can this work. First and
530 foremost, it work because tasksel is modular, and driven by whatever
531 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
532 isenkram-cli package place two files for tasksel to find. First there
533 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
534
535 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
536 Task: isenkram-packages
537 Section: hardware
538 Description: Hardware specific packages (autodetected by isenkram)
539 Based on the detected hardware various hardware specific packages are
540 proposed.
541 Test-new-install: show show
542 Relevance: 8
543 Packages: for-current-hardware
544
545 Task: isenkram-firmware
546 Section: hardware
547 Description: Hardware specific firmware packages (autodetected by isenkram)
548 Based on the detected hardware various hardware specific firmware
549 packages are proposed.
550 Test-new-install: mark show
551 Relevance: 8
552 Packages: for-current-hardware-firmware
553 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
554
555 &lt;p&gt;The key parts are Test-new-install which indicate how the task
556 should be handled and the Packages line referencing to a script in
557 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
558 list of packages to install. The for-current-hardware-firmware script
559 look like this to list relevant firmware for the machine:
560
561 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
562 #!/bin/sh
563 #
564 PATH=/usr/sbin:$PATH
565 export PATH
566 isenkram-autoinstall-firmware -l
567 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
568
569 &lt;p&gt;With those two pieces in place, the firmware is installed by
570 tasksel during the normal d-i run. :)&lt;/p&gt;
571
572 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
573 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
574 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
575 install.&lt;/p&gt;
576
577 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
578 pilots in testing this feature, as isenkram is used there now to
579 install firmware, replacing the earlier scripts.&lt;/p&gt;
580 </description>
581 </item>
582
583 <item>
584 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
585 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
586 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
587 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
588 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
589 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
590 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
591 on a screen normally showing the bread types and prizes:&lt;/p&gt;
592
593 &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;
594
595 &lt;p&gt;If it had booted as it was supposed to, I would never had known
596 about this hidden Linux installation. It is interesting what
597 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
598 </description>
599 </item>
600
601 <item>
602 <title>New lsdvd release version 0.17 is ready</title>
603 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
604 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
605 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
606 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
607 got a new set of developers a few weeks ago, after the original
608 developer decided to step down and pass the project to fresh blood.
609 This project is now maintained by Petter Reinholdtsen and Steve
610 Dibb.&lt;/p&gt;
611
612 &lt;p&gt;I just wrapped up
613 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
614 new lsdvd release&lt;/a&gt;, available in git or from
615 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
616 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
617 0.17.&lt;/p&gt;
618
619 &lt;ul&gt;
620
621 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
622 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
623 non-existant, to work around additional copy protection&lt;/li&gt;
624 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
625 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
626 &lt;li&gt;Fix include orders&lt;/li&gt;
627 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
628 &lt;li&gt;Fix the chapter count&lt;/li&gt;
629 &lt;li&gt;Make sure the array size and the array limit used when initialising
630 the palette size is the same.&lt;/li&gt;
631 &lt;li&gt;Fix array printing.&lt;/li&gt;
632 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
633 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
634 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
635 with more GCC compiler warnings.&lt;/li&gt;
636
637 &lt;/ul&gt;
638
639 &lt;p&gt;This change bring together patches for lsdvd in use in various
640 Linux and Unix distributions, as well as patches submitted to the
641 project the last nine years. Please check it out. :)&lt;/p&gt;
642 </description>
643 </item>
644
645 <item>
646 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
647 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
649 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
650 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
651 project&lt;/a&gt; provide a Linux solution for schools, including a
652 powerful desktop with education software, a central server providing
653 web pages, user database, user home directories, central login and PXE
654 boot of both clients without disk and the installation to install Debian
655 Edu on machines with disk (and a few other services perhaps to small
656 to mention here). We in the Debian Edu team are currently working on
657 the Jessie based version, trying to get everything in shape before the
658 freeze, to avoid having to maintain our own package repository in the
659 future. The
660 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
661 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
662 work left. Some fatal problems block testing, breaking the installer,
663 but it is possible to work around these to get anyway. Here is a
664 recipe on how to get the installation limping along.&lt;/p&gt;
665
666 &lt;p&gt;First, download the test ISO via
667 &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;,
668 &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;
669 or rsync (use
670 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
671 The ISO build was broken on Tuesday, so we do not get a new ISO every
672 12 hours or so, but thankfully the ISO we already got we are able to
673 install with some tweaking.&lt;/p&gt;
674
675 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
676 (use Alt-Ctrl-F2), run&lt;/p&gt;
677
678 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
679 nano /usr/bin/edu-eatmydata-install
680 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
681
682 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
683 optimization. Return to the installation, select the profile you want
684 and continue. Without this change, exim4-config will fail to install
685 due to a known bug in eatmydata.&lt;/p&gt;
686
687 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
688 this do not work, figure out what your correct value would be. All my
689 test machines need /dev/sda, so I have no advice if it do not fit
690 your need.&lt;/p&gt;
691
692 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
693 root after the initial boot from hard drive, and install the
694 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
695 or mate. If you want several desktop options, install more than one
696 metapackage. Once this is done, reboot and you should have a working
697 graphical login screen. This workaround should no longer be needed
698 once the education-tasks package version 1.801 enter testing in two
699 days.&lt;/p&gt;
700
701 &lt;p&gt;I believe the ISO build will start working on two days when the new
702 tasksel package enter testing and Steve McIntyre get a chance to
703 update the debian-cd git repository. The eatmydata, grub and desktop
704 issues are already fixed in unstable and testing, and should show up
705 on the ISO as soon as the ISO build start working again. Well the
706 eatmydata optimization is really just disabled. The proper fix
707 require an upload by the eatmydata maintainer applying the patch
708 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
709 The rest have proper fixes in unstable.&lt;/p&gt;
710
711 &lt;p&gt;I hope this get you going with the installation testing, as we are
712 quickly running out of time trying to get our Jessie based
713 installation ready before the distribution freeze in a month.&lt;/p&gt;
714 </description>
715 </item>
716
717 <item>
718 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
719 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
720 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
721 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
722 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
723 to handle my fairly large DVD collection. It is a nice command line
724 tool to get details about a DVD, like title, tracks, track length,
725 etc, in XML, Perl or human readable format. But lsdvd have not seen
726 any new development since 2006 and had a few irritating bugs affecting
727 its use with some DVDs. Upstream seemed to be dead, and in January I
728 sent a small probe asking for a version control repository for the
729 project, without any reply. But I use it regularly and would like to
730 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
731 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
732 the project admin, and after getting a reply from him explaining that
733 he was no longer interested in the project, I asked if I could take
734 over. And yesterday, I became project admin.&lt;/p&gt;
735
736 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
737 maintainer interested in joining forces to maintain the upstream
738 project, and I hope we can get a new release out fairly quickly,
739 collecting the patches spread around on the internet into on place.
740 I&#39;ve added the relevant Debian patches to the freshly created git
741 repository, and expect the Gentoo patches to make it too. If you got
742 a DVD collection and care about command line tools, check out
743 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
744 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
745 list&lt;/a&gt;. :)&lt;/p&gt;
746 </description>
747 </item>
748
749 <item>
750 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
751 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
752 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
753 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
754 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
755 a lot quicker. When we install more than 2000 packages in
756 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
757 tasksel in the installer, unpacking the binary packages take forever.
758 A part of the slow I/O issue was discussed in
759 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
760 much file system sync-ing done by dpkg, which is the package
761 responsible for unpacking the binary packages. Other parts (like code
762 executed by postinst scripts) might also sync to disk during
763 installation. All this sync-ing to disk do not really make sense to
764 me. If the machine crash half-way through, I start over, I do not try
765 to salvage the half installed system. So the failure sync-ing is
766 supposed to protect against, hardware or system crash, is not really
767 relevant while the installer is running.&lt;/p&gt;
768
769 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
770 system sync()-ing in a fairly non-intrusive way, without the need to
771 change the code in several packages. The idea is not new, but I have
772 not heard anyone propose the approach using dpkg-divert before. It
773 depend on the small and clever package
774 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
775 uses LD_PRELOAD to replace the system functions for syncing data to
776 disk with functions doing nothing, thus allowing programs to live
777 dangerous while speeding up disk I/O significantly. Instead of
778 modifying the implementation of dpkg, apt and tasksel (which are the
779 packages responsible for selecting, fetching and installing packages),
780 it occurred to me that we could just divert the programs away, replace
781 them with a simple shell wrapper calling
782 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
783 Two days ago I decided to test the idea, and wrapped up a simple
784 implementation for the Debian Edu udeb.&lt;/p&gt;
785
786 &lt;p&gt;The effect was stunning. In my first test it reduced the running
787 time of the pkgsel step (installing tasks) from 64 to less than 44
788 minutes (20 minutes shaved off the installation) on an old Dell
789 Latitude D505 machine. I am not quite sure what the optimised time
790 would have been, as I messed up the testing a bit, causing the debconf
791 priority to get low enough for two questions to pop up during
792 installation. As soon as I saw the questions I moved the installation
793 along, but do not know how long the question were holding up the
794 installation. I did some more measurements using Debian Edu Jessie,
795 and got these results. The time measured is the time stamp in
796 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
797 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
798 yourself. In Debian Edu, the tasksel dialog do not show up, and the
799 timing thus do not depend on how quickly the user handle the tasksel
800 dialog.&lt;/p&gt;
801
802 &lt;p&gt;&lt;table&gt;
803
804 &lt;tr&gt;
805 &lt;th&gt;Machine/setup&lt;/th&gt;
806 &lt;th&gt;Original tasksel&lt;/th&gt;
807 &lt;th&gt;Optimised tasksel&lt;/th&gt;
808 &lt;th&gt;Reduction&lt;/th&gt;
809 &lt;/tr&gt;
810
811 &lt;tr&gt;
812 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
813 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
814 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
815 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
816 &lt;/tr&gt;
817
818 &lt;tr&gt;
819 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
820 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
821 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
822 &lt;td&gt;23 min 40%&lt;/td&gt;
823 &lt;/tr&gt;
824
825 &lt;tr&gt;
826 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
827 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
828 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
829 &lt;td&gt;11 min 50%&lt;/td&gt;
830 &lt;/tr&gt;
831
832 &lt;tr&gt;
833 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
834 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
835 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
836 &lt;td&gt;2 min 33%&lt;/td&gt;
837 &lt;/tr&gt;
838
839 &lt;tr&gt;
840 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
841 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
842 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
843 &lt;td&gt;4 min 21%&lt;/td&gt;
844 &lt;/tr&gt;
845
846 &lt;/table&gt;&lt;/p&gt;
847
848 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
849 time is spent downloading packages. The connection to the Internet
850 was 100Mbit/s during testing, so downloading should not be a
851 significant factor in the measurement. Download typically took a few
852 seconds to a few minutes, depending on the amount of packages being
853 installed.&lt;/p&gt;
854
855 &lt;p&gt;The speedup is implemented by using two hooks in
856 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
857 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
858 finish-install.d hook to remove the divert at the end of the
859 installation. I picked the pre-pkgsel.d hook instead of the
860 post-base-installer.d hook because I test using an ISO without the
861 eatmydata package included, and the post-base-installer.d hook in
862 Debian Edu can only operate on packages included in the ISO. The
863 negative effect of this is that I am unable to activate this
864 optimization for the kernel installation step in d-i. If the code is
865 moved to the post-base-installer.d hook, the speedup would be larger
866 for the entire installation.&lt;/p&gt;
867
868 &lt;p&gt;I&#39;ve implemented this in the
869 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
870 git repository, and plan to provide the optimization as part of the
871 Debian Edu installation. If you want to test this yourself, you can
872 create two files in the installer (or in an udeb). One shell script
873 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
874
875 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
876 #!/bin/sh
877 set -e
878 . /usr/share/debconf/confmodule
879 info() {
880 logger -t my-pkgsel &quot;info: $*&quot;
881 }
882 error() {
883 logger -t my-pkgsel &quot;error: $*&quot;
884 }
885 override_install() {
886 apt-install eatmydata || true
887 if [ -x /target/usr/bin/eatmydata ] ; then
888 for bin in dpkg apt-get aptitude tasksel ; do
889 file=/usr/bin/$bin
890 # Test that the file exist and have not been diverted already.
891 if [ -f /target$file ] ; then
892 info &quot;diverting $file using eatmydata&quot;
893 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
894 &gt; /target$file.edu
895 chmod 755 /target$file.edu
896 in-target dpkg-divert --package debian-edu-config \
897 --rename --quiet --add $file
898 ln -sf ./$bin.edu /target$file
899 else
900 error &quot;unable to divert $file, as it is missing.&quot;
901 fi
902 done
903 else
904 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
905 fi
906 }
907
908 override_install
909 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
910
911 &lt;p&gt;To clean up, another shell script should go into
912 /usr/lib/finish-install.d/ with code like this:
913
914 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
915 #! /bin/sh -e
916 . /usr/share/debconf/confmodule
917 error() {
918 logger -t my-finish-install &quot;error: $@&quot;
919 }
920 remove_install_override() {
921 for bin in dpkg apt-get aptitude tasksel ; do
922 file=/usr/bin/$bin
923 if [ -x /target$file.edu ] ; then
924 rm /target$file
925 in-target dpkg-divert --package debian-edu-config \
926 --rename --quiet --remove $file
927 rm /target$file.edu
928 else
929 error &quot;Missing divert for $file.&quot;
930 fi
931 done
932 sync # Flush file buffers before continuing
933 }
934
935 remove_install_override
936 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
937
938 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
939 edu-eatmydata-install and call it from the pre-pkgsel.d and
940 finish-install.d scripts.&lt;/p&gt;
941
942 &lt;p&gt;By now you might ask if this change should get into the normal
943 Debian installer too? I suspect it should, but am not sure the
944 current debian-installer coordinators find it useful enough. It also
945 depend on the side effects of the change. I&#39;m not aware of any, but I
946 guess we will see if the change is safe after some more testing.
947 Perhaps there is some package in Debian depending on sync() and
948 fsync() having effect? Perhaps it should go into its own udeb, to
949 allow those of us wanting to enable it to do so without affecting
950 everyone.&lt;/p&gt;
951
952 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
953 will break installation of all programs using gnutls because of
954 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
955 eatmydata package in Debian will solve it.&lt;/p&gt;
956
957 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
958 the optimization work again. And I have discovered that the
959 dpkg-divert trick is not really needed and implemented a slightly
960 simpler approach as part of the debian-edu-install package. See
961 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
962
963 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
964 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
965 triggering on i386 made it into testing, and broke this installation
966 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
967 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
968 </description>
969 </item>
970
971 <item>
972 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
973 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
974 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
975 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
976 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
977 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
978 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
979 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
980 learn that there is a large set of publicly available key servers to
981 use when looking for peoples public key. So far I have used
982 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
983 were misbehaving, but those days are ended. The servers I have used
984 up until yesterday have been slow and some times unavailable. I hope
985 those problems are gone now.&lt;/p&gt;
986
987 &lt;p&gt;Behind the round robin DNS entry of the
988 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
989 there is a pool of more than 100 keyservers which are checked every
990 day to ensure they are well connected and up to date. It must be
991 better than what I have used so far. :)&lt;/p&gt;
992
993 &lt;p&gt;Yesterdays speaker told me that the service is the default
994 keyserver provided by the default configuration in GnuPG, but this do
995 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
996
997 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
998 line:&lt;/p&gt;
999
1000 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1001 keyserver pool.sks-keyservers.net
1002 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1003
1004 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1005 entries in DNS. Just for fun, I did just that at work, so now every
1006 user of GnuPG at the University of Oslo should find a OpenGPG
1007 keyserver automatically should their need it:&lt;/p&gt;
1008
1009 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1010 % host -t srv _pgpkey-http._tcp.uio.no
1011 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1012 %
1013 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1014
1015 &lt;p&gt;Now if only
1016 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1017 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1018 very happy. It can look up a given key or search for a user ID, but I
1019 normally do not want that, but to find a trust path from my key to
1020 another key. Given a user ID or key ID, I would like to find (and
1021 download) the keys representing a signature path from my key to the
1022 key in question, to be able to get a trust path between the two keys.
1023 This is as far as I can tell not possible today. Perhaps something
1024 for a future version of the protocol?&lt;/p&gt;
1025 </description>
1026 </item>
1027
1028 <item>
1029 <title>From English wiki to translated PDF and epub via Docbook</title>
1030 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1032 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1033 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1034 project&lt;/a&gt; provide an instruction manual for teachers, system
1035 administrators and other users that contain useful tips for setting up
1036 and maintaining a Debian Edu installation. This text is about how the
1037 text processing of this manual is handled in the project.&lt;/p&gt;
1038
1039 &lt;p&gt;One goal of the project is to provide information in the native
1040 language of its users, and for this we need to handle translations.
1041 But we also want to make sure each language contain the same
1042 information, so for this we need a good way to keep the translations
1043 in sync. And we want it to be easy for our users to improve the
1044 documentation, avoiding the need to learn special formats or tools to
1045 contribute, and the obvious way to do this is to make it possible to
1046 edit the documentation using a web browser. We also want it to be
1047 easy for translators to keep the translation up to date, and give them
1048 help in figuring out what need to be translated. Here is the list of
1049 tools and the process we have found trying to reach all these
1050 goals.&lt;/p&gt;
1051
1052 &lt;p&gt;We maintain the authoritative source of our manual in the
1053 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1054 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1055 front page with references to the different chapters, several pages
1056 for each chapter, and finally one &quot;collection page&quot; gluing all the
1057 chapters together into one large web page (aka
1058 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1059 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1060 processing and translations. Thanks to the fact that the
1061 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1062 wiki.debian.org support exporting pages in
1063 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1064 the list of pages to export using the raw version of the AllInOne
1065 page, loop over each of them to generate a Docbook XML version of the
1066 manual. This process also download images and transform image
1067 references to use the locally downloaded images. The generated
1068 Docbook XML files are slightly broken, so some post-processing is done
1069 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1070 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1071 a handfull of images. The XML file can now be used to generate PDF, HTML
1072 and epub versions of the English manual. This is the basic step of
1073 our process, making PDF (using dblatex), HTML (using xsltproc) and
1074 epub (using dbtoepub) version from Docbook XML, and the resulting files
1075 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1076
1077 &lt;p&gt;But English documentation is not enough for us. We want translated
1078 documentation too, and we want to make it easy for translators to
1079 track the English original. For this we use the
1080 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1081 which allow us to transform the English Docbook XML file into a
1082 translation file (a .pot file), usable with the normal gettext based
1083 translation tools used by those translating free software. The pot
1084 file is used to create and maintain translation files (several .po
1085 files), which the translations update with the native language
1086 translations of all titles, paragraphs and blocks of text in the
1087 original. The next step is combining the original English Docbook XML
1088 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1089 create a translated Docbook XML file (in this case
1090 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1091 translated, if the translation is not complete) Docbook XML file can
1092 then be used like the original to create a PDF, HTML and epub version
1093 of the documentation.&lt;/p&gt;
1094
1095 &lt;p&gt;The translators use different tools to edit the .po files. We
1096 recommend using
1097 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1098 while some use emacs and vi, others can use web based editors like
1099 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1100 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1101 is where the .po file end up, in our git repository. Updated
1102 translations can either be committed directly to git, or submitted as
1103 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1104 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1105
1106 &lt;p&gt;One challenge is images, which both might need to be translated (if
1107 they show translated user applications), and are needed in different
1108 formats when creating PDF and HTML versions (epub is a HTML version in
1109 this regard). For this we transform the original PNG images to the
1110 needed density and format during build, and have a way to provide
1111 translated images by storing translated versions in
1112 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1113 package maintainers know more.&lt;/p&gt;
1114
1115 &lt;p&gt;If you wonder what the result look like, we provide
1116 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1117 of the documentation packages on the web&lt;/a&gt;. See for example the
1118 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1119 PDF version&lt;/a&gt; or the
1120 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1121 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1122 but perhaps it will be done in the future.&lt;/p&gt;
1123
1124 &lt;p&gt;To learn more, check out
1125 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1126 debian-edu-doc package&lt;/a&gt;,
1127 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1128 manual on the wiki&lt;/a&gt; and
1129 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1130 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1131 </description>
1132 </item>
1133
1134 <item>
1135 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1136 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1137 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1138 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1139 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1140 related packages relevant for the computer installed automatically.
1141 So I implemented one, using
1142 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1143 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1144 run tasksel as user root. You should be presented with a new option,
1145 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1146 select it, tasksel will install the packages isenkram claim is fit for
1147 the current hardware, hot pluggable or not.&lt;p&gt;
1148
1149 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1150 description, and the other is the script used to extract the list of
1151 packages to install. The first part is in
1152 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1153 this:&lt;/p&gt;
1154
1155 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1156 Task: isenkram
1157 Section: hardware
1158 Description: Hardware specific packages (autodetected by isenkram)
1159 Based on the detected hardware various hardware specific packages are
1160 proposed.
1161 Test-new-install: mark show
1162 Relevance: 8
1163 Packages: for-current-hardware
1164 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1165
1166 &lt;p&gt;The second part is in
1167 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1168 this:&lt;/p&gt;
1169
1170 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1171 #!/bin/sh
1172 #
1173 (
1174 isenkram-lookup
1175 isenkram-autoinstall-firmware -l
1176 ) | sort -u
1177 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1178
1179 &lt;p&gt;All in all, a very short and simple implementation making it
1180 trivial to install the hardware dependent package we all may want to
1181 have installed on our machines. I&#39;ve not been able to find a way to
1182 get tasksel to tell you exactly which packages it plan to install
1183 before doing the installation. So if you are curious or careful,
1184 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1185
1186 &lt;p&gt;The information about which packages are handling which hardware is
1187 fetched either from the isenkram package itself in
1188 /usr/share/isenkram/, from git.debian.org or from the APT package
1189 database (using the Modaliases header). The APT package database
1190 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1191 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1192 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1193 the python-apt code (bug
1194 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1195 workaround I was able to get rid of the file descriptor leak and
1196 reduce the memory leak from ~30 MiB per hardware detection down to
1197 around 2 MiB per hardware detection. It should make the desktop
1198 daemon a lot more useful. The fix is in version 0.7 uploaded to
1199 unstable today.&lt;/p&gt;
1200
1201 &lt;p&gt;I believe the current way of mapping hardware to packages in
1202 Isenkram is is a good draft, but in the future I expect isenkram to
1203 use the AppStream data source for this. A proposal for getting proper
1204 AppStream support into Debian is floating around as
1205 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1206 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1207 project&lt;/a&gt; will take place this summer to improve the situation. I
1208 look forward to seeing the result, and welcome patches for isenkram to
1209 start using the information when it is ready.&lt;/p&gt;
1210
1211 &lt;p&gt;If you want your package to map to some specific hardware, either
1212 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1213 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1214 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1215 package. See also
1216 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1217 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1218 the information will be migrated to AppStream eventually, but for the
1219 moment I got no better place to store it.&lt;/p&gt;
1220 </description>
1221 </item>
1222
1223 <item>
1224 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1225 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1226 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1227 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1228 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1229 project&lt;/a&gt; is working on providing the software and hardware to make
1230 it easy for non-technical people to host their data and communication
1231 at home, and being able to communicate with their friends and family
1232 encrypted and away from prying eyes. It is still going strong, and
1233 today a major mile stone was reached.&lt;/p&gt;
1234
1235 &lt;p&gt;Today, the last of the packages currently used by the project to
1236 created the system images were accepted into Debian Unstable. It was
1237 the freedombox-setup package, which is used to configure the images
1238 during build and on the first boot. Now all one need to get going is
1239 the build code from the freedom-maker git repository and packages from
1240 Debian. And once the freedombox-setup package enter testing, we can
1241 build everything directly from Debian. :)&lt;/p&gt;
1242
1243 &lt;p&gt;Some key packages used by Freedombox are
1244 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1245 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1246 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1247 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1248 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1249 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1250 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1251 are plans to integrate more packages into the setup. User
1252 documentation is maintained on the Debian wiki. Please
1253 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1254 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1255
1256 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1257 setup, run this on a Debian machine using a user with sudo rights to
1258 become root:&lt;/p&gt;
1259
1260 &lt;p&gt;&lt;pre&gt;
1261 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1262 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1263 u-boot-tools
1264 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1265 freedom-maker
1266 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1267 &lt;/pre&gt;&lt;/p&gt;
1268
1269 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1270 devices. See the README in the freedom-maker git repo for more
1271 details on the build. If you do not want all three images, trim the
1272 make line. Note that the virtualbox-image target is not really
1273 virtualbox specific. It create a x86 image usable in kvm, qemu,
1274 vmware and any other x86 virtual machine environment. You might need
1275 the version of vmdebootstrap in Jessie to get the build working, as it
1276 include fixes for a race condition with kpartx.&lt;/p&gt;
1277
1278 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1279 method, boot a Debian Wheezy ISO and use this boot argument to load
1280 the preseed values:&lt;/p&gt;
1281
1282 &lt;p&gt;&lt;pre&gt;
1283 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;
1284 &lt;/pre&gt;&lt;/p&gt;
1285
1286 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1287 it still work.&lt;/p&gt;
1288
1289 &lt;p&gt;If you wonder how to help, one task you could look at is using
1290 systemd as the boot system. It will become the default for Linux in
1291 Jessie, so we need to make sure it is usable on the Freedombox. I did
1292 a simple test a few weeks ago, and noticed dnsmasq failed to start
1293 during boot when using systemd. I suspect there are other problems
1294 too. :) To detect problems, there is a test suite included, which can
1295 be run from the plinth web interface.&lt;/p&gt;
1296
1297 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1298 us get the new release published. :) Please join us on
1299 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1300 irc.debian.org)&lt;/a&gt; and
1301 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1302 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1303 </description>
1304 </item>
1305
1306 <item>
1307 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1308 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1309 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1310 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1311 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1312 solution for use at home. My requirements are simple, it must be
1313 cheap and locally encrypted (in other words, I keep the encryption
1314 keys, the storage provider do not have access to my private files).
1315 One idea me and my friends had many years ago, before the cloud
1316 storage providers showed up, was to use Google mail as storage,
1317 writing a Linux block device storing blocks as emails in the mail
1318 service provided by Google, and thus get heaps of free space. On top
1319 of this one can add encryption, RAID and volume management to have
1320 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1321 I never found time to implement such system. But the last few weeks I
1322 have looked at a system called
1323 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1324 mounted network backed file system with the features I need.&lt;/p&gt;
1325
1326 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1327 handling several different storage providers, any with Amazon S3,
1328 Google Drive or OpenStack API. There are heaps of such storage
1329 providers. S3QL can also use a local directory as storage, which
1330 combined with sshfs allow for file storage on any ssh server. S3QL
1331 include support for encryption, compression, de-duplication, snapshots
1332 and immutable file systems, allowing me to mount the remote storage as
1333 a local mount point, look at and use the files as if they were local,
1334 while the content is stored in the cloud as well. This allow me to
1335 have a backup that should survive fire. The file system can not be
1336 shared between several machines at the same time, as only one can
1337 mount it at the time, but any machine with the encryption key and
1338 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1339
1340 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1341 package is included already. So to get started, run &lt;tt&gt;apt-get
1342 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1343 Greenqloud, after reading their nice recipe on
1344 &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
1345 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1346 in Iceland more than those in USA when it come to keeping my personal
1347 data safe and private, and thus would rather spend money on a company
1348 in Iceland. Another nice recipe is available from the article
1349 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1350 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1351 Admin magazine. When the provider is picked, figure out how to get
1352 the API key needed to connect to the storage API. With Greencloud,
1353 the key did not show up until I had added payment details to my
1354 account.&lt;/p&gt;
1355
1356 &lt;p&gt;Armed with the API access details, it is time to create the file
1357 system. First, create a new bucket in the cloud. This bucket is the
1358 file system storage area. I picked a bucket name reflecting the
1359 machine that was going to store data there, but any name will do.
1360 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1361 the API login and password, and a locally created password. Store it
1362 all in ~root/.s3ql/authinfo2 like this:
1363
1364 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1365 [s3c]
1366 storage-url: s3c://s.greenqloud.com:443/bucket-name
1367 backend-login: API-login
1368 backend-password: API-password
1369 fs-passphrase: local-password
1370 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1371
1372 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1373 but any sensible way to create a fairly random password should do it.
1374 Armed with these details, it is now time to run mkfs, entering the API
1375 details and password to create it:&lt;/p&gt;
1376
1377 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1378 # mkdir -m 700 /var/lib/s3ql-cache
1379 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1380 --ssl s3c://s.greenqloud.com:443/bucket-name
1381 Enter backend login:
1382 Enter backend password:
1383 Before using S3QL, make sure to read the user&#39;s guide, especially
1384 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1385 Enter encryption password:
1386 Confirm encryption password:
1387 Generating random encryption key...
1388 Creating metadata tables...
1389 Dumping metadata...
1390 ..objects..
1391 ..blocks..
1392 ..inodes..
1393 ..inode_blocks..
1394 ..symlink_targets..
1395 ..names..
1396 ..contents..
1397 ..ext_attributes..
1398 Compressing and uploading metadata...
1399 Wrote 0.00 MB of compressed metadata.
1400 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1401
1402 &lt;p&gt;The next step is mounting the file system to make the storage available.
1403
1404 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1405 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1406 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1407 Using 4 upload threads.
1408 Downloading and decompressing metadata...
1409 Reading metadata...
1410 ..objects..
1411 ..blocks..
1412 ..inodes..
1413 ..inode_blocks..
1414 ..symlink_targets..
1415 ..names..
1416 ..contents..
1417 ..ext_attributes..
1418 Mounting filesystem...
1419 # df -h /s3ql
1420 Filesystem Size Used Avail Use% Mounted on
1421 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1422 #
1423 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1424
1425 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1426 backups in it, and as the metadata used by rsync is downloaded at
1427 mount time, no network traffic (and storage cost) is triggered by
1428 running rsync. To unmount, one should not use the normal umount
1429 command, as this will not flush the cache to the cloud storage, but
1430 instead running the umount.s3ql command like this:
1431
1432 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1433 # umount.s3ql /s3ql
1434 #
1435 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1436
1437 &lt;p&gt;There is a fsck command available to check the file system and
1438 correct any problems detected. This can be used if the local server
1439 crashes while the file system is mounted, to reset the &quot;already
1440 mounted&quot; flag. This is what it look like when processing a working
1441 file system:&lt;/p&gt;
1442
1443 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1444 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1445 Using cached metadata.
1446 File system seems clean, checking anyway.
1447 Checking DB integrity...
1448 Creating temporary extra indices...
1449 Checking lost+found...
1450 Checking cached objects...
1451 Checking names (refcounts)...
1452 Checking contents (names)...
1453 Checking contents (inodes)...
1454 Checking contents (parent inodes)...
1455 Checking objects (reference counts)...
1456 Checking objects (backend)...
1457 ..processed 5000 objects so far..
1458 ..processed 10000 objects so far..
1459 ..processed 15000 objects so far..
1460 Checking objects (sizes)...
1461 Checking blocks (referenced objects)...
1462 Checking blocks (refcounts)...
1463 Checking inode-block mapping (blocks)...
1464 Checking inode-block mapping (inodes)...
1465 Checking inodes (refcounts)...
1466 Checking inodes (sizes)...
1467 Checking extended attributes (names)...
1468 Checking extended attributes (inodes)...
1469 Checking symlinks (inodes)...
1470 Checking directory reachability...
1471 Checking unix conventions...
1472 Checking referential integrity...
1473 Dropping temporary indices...
1474 Backing up old metadata...
1475 Dumping metadata...
1476 ..objects..
1477 ..blocks..
1478 ..inodes..
1479 ..inode_blocks..
1480 ..symlink_targets..
1481 ..names..
1482 ..contents..
1483 ..ext_attributes..
1484 Compressing and uploading metadata...
1485 Wrote 0.89 MB of compressed metadata.
1486 #
1487 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1488
1489 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1490 quick, about the same speed as local file access. Uploading large
1491 amount of data is to me limited by the bandwidth out of and into my
1492 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1493 which is very close to my upload speed, and downloading the same
1494 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1495 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1496 network, not the file system code. I do not know what a good cache
1497 size would be, but suspect that the cache should e larger than your
1498 working set.&lt;/p&gt;
1499
1500 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1501 time. If another machine try, it is told that the file system is
1502 busy:&lt;/p&gt;
1503
1504 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1505 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1506 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1507 Using 8 upload threads.
1508 Backend reports that fs is still mounted elsewhere, aborting.
1509 #
1510 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1511
1512 &lt;p&gt;The file content is uploaded when the cache is full, while the
1513 metadata is uploaded once every 24 hour by default. To ensure the
1514 file system content is flushed to the cloud, one can either umount the
1515 file system, or ask S3QL to flush the cache and metadata using
1516 s3qlctrl:
1517
1518 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1519 # s3qlctrl upload-meta /s3ql
1520 # s3qlctrl flushcache /s3ql
1521 #
1522 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1523
1524 &lt;p&gt;If you are curious about how much space your data uses in the
1525 cloud, and how much compression and deduplication cut down on the
1526 storage usage, you can use s3qlstat on the mounted file system to get
1527 a report:&lt;/p&gt;
1528
1529 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1530 # s3qlstat /s3ql
1531 Directory entries: 9141
1532 Inodes: 9143
1533 Data blocks: 8851
1534 Total data size: 22049.38 MB
1535 After de-duplication: 21955.46 MB (99.57% of total)
1536 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1537 Database size: 2.39 MB (uncompressed)
1538 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1539 #
1540 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1541
1542 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1543 storage. I did not try to locate them all, but am aware of at least
1544 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1545 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1546 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1547 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1548 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1549 accept payment in Bitcoin. Pick one that suit your need. Some of
1550 them provide several GiB of free storage, but the prize models are
1551 quite different and you will have to figure out what suits you
1552 best.&lt;/p&gt;
1553
1554 &lt;p&gt;While researching this blog post, I had a look at research papers
1555 and posters discussing the S3QL file system. There are several, which
1556 told me that the file system is getting a critical check by the
1557 science community and increased my confidence in using it. One nice
1558 poster is titled
1559 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1560 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1561 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1562 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1563 and Pamela Smith. Please have a look.&lt;/p&gt;
1564
1565 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1566 check out the mounted S3QL file system to see if it would be usable as
1567 a home directory (in other word, that it provided POSIX semantics when
1568 it come to locking and umask handling etc). Running
1569 &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
1570 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1571 no error was found. So the file system can be used for home
1572 directories, if one chooses to do so.&lt;/p&gt;
1573
1574 &lt;p&gt;If you do not want a locally file system, and want something that
1575 work without the Linux fuse file system, I would like to mention the
1576 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1577 provide locally encrypted backup using a command line client. It have
1578 a nicer access control system, where one can split out read and write
1579 access, allowing some systems to write to the backup and others to
1580 only read from it.&lt;/p&gt;
1581
1582 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1583 activities, please send Bitcoin donations to my address
1584 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1585 </description>
1586 </item>
1587
1588 <item>
1589 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1590 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1591 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1592 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1593 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1594 project&lt;/a&gt; is working on providing the software and hardware for
1595 making it easy for non-technical people to host their data and
1596 communication at home, and being able to communicate with their
1597 friends and family encrypted and away from prying eyes. It has been
1598 going on for a while, and is slowly progressing towards a new test
1599 release (0.2).&lt;/p&gt;
1600
1601 &lt;p&gt;And what day could be better than the Pi day to announce that the
1602 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1603 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1604 system), and can also be installed using a Debian installer preseed
1605 file. The Debian based Freedombox is now based on Debian Jessie,
1606 where most of the needed packages used are already present. Only one,
1607 the freedombox-setup package, is missing. To try to build your own
1608 boot image to test the current status, fetch the freedom-maker scripts
1609 and build using
1610 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1611 with a user with sudo access to become root:
1612
1613 &lt;pre&gt;
1614 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1615 freedom-maker
1616 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1617 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1618 u-boot-tools
1619 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1620 &lt;/pre&gt;
1621
1622 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1623 devices. See the README for more details on the build. If you do not
1624 want all three images, trim the make line. But note that thanks to &lt;a
1625 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1626 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1627 kpartx call.&lt;/p&gt;
1628
1629 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1630 method, boot a Debian Wheezy ISO and use this boot argument to load
1631 the preseed values:&lt;/p&gt;
1632
1633 &lt;pre&gt;
1634 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;
1635 &lt;/pre&gt;
1636
1637 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1638 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1639 currently hang while setting up APT sources. Killing the
1640 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1641 installation will get the installation going. This affect all
1642 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1643
1644 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1645 us get the new release published. :) Please join us on
1646 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1647 irc.debian.org)&lt;/a&gt; and
1648 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1649 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1650 </description>
1651 </item>
1652
1653 <item>
1654 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1655 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1656 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1657 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1658 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1659 innetgr tools, because I needed them in
1660 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1661 ng-utils, and it has served me well. I placed the project under the
1662 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1663 repository. But many years ago, the CVS repository was dropped (lost,
1664 not migrated to new hardware, not sure), and the project have lacked a
1665 proper home since then.&lt;/p&gt;
1666
1667 &lt;p&gt;Last summer, I had a look at the package and made a new release
1668 fixing a irritating crash bug, but was unable to store the changes in
1669 a proper source control system. I applied for a project on
1670 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1671 to follow up on it. Until today. :)&lt;/p&gt;
1672
1673 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1674 now have a new home, and a git repository with the highlight of the
1675 history of the project. I published all release tarballs and imported
1676 them into the git repository. As the project is really stable and not
1677 expected to gain new features any time soon, I decided to make a new
1678 release and call it 1.0. Visit the new project home on
1679 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1680 if you want to check it out. The new version is also uploaded into
1681 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1682 </description>
1683 </item>
1684
1685 <item>
1686 <title>Testing sysvinit from experimental in Debian Hurd</title>
1687 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1688 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1689 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1690 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1691 their changes into sysvinit, to allow them to use the normal sysvinit
1692 boot system instead of their old one. This follow up on the
1693 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1694 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1695 get Debian on Hurd working more like Debian on Linux. To get started,
1696 I downloaded a prebuilt hard disk image from
1697 &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;,
1698 and started it using virt-manager.&lt;/p&gt;
1699
1700 &lt;p&gt;The first think I had to do after logging in (root without any
1701 password) was to get the network operational. I followed
1702 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1703 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1704 commands as root to get the machine to accept a IP address from the
1705 kvm internal DHCP server:&lt;/p&gt;
1706
1707 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1708 settrans -fgap /dev/netdde /hurd/netdde
1709 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1710 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1711 dhclient /dev/eth0
1712 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1713
1714 &lt;p&gt;After this, the machine had internet connectivity, and I could
1715 upgrade it and install the sysvinit packages from experimental and
1716 enable it as the default boot system in Hurd.&lt;/p&gt;
1717
1718 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1719 running on the machine it for ssh login to work a password need to be
1720 set. Also, note that a bug somewhere in openssh on Hurd block
1721 compression from working. Remember to turn that off on the client
1722 side.&lt;/p&gt;
1723
1724 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1725 stuff:&lt;/p&gt;
1726
1727 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1728 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1729 deb http://http.debian.net/debian/ experimental main
1730 EOF
1731 apt-get update
1732 apt-get dist-upgrade
1733 apt-get install -t experimental initscripts sysv-rc sysvinit \
1734 sysvinit-core sysvinit-utils
1735 update-alternatives --config runsystem
1736 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1737
1738 &lt;p&gt;To reboot after switching boot system, you have to use
1739 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1740 yet a sysvinit process able to receive the signals from the normal
1741 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1742 upgrading every package and rebooting, the network come up with DHCP
1743 after boot as it should, and the settrans/pkill hack mentioned at the
1744 start is no longer needed. But for some strange reason, there are no
1745 longer any login prompt in the virtual console, so I logged in using
1746 ssh instead.
1747
1748 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1749 fail some times. No idea what the cause is, but hope the Hurd porters
1750 figure it out. At least Justus said on IRC (#debian-hurd on
1751 irc.debian.org) that they are aware of the problem. A way to reduce
1752 the impact is to upgrade to the Hurd packages built by Justus by
1753 adding this repository to the machine:&lt;/p&gt;
1754
1755 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1756 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1757 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1758 EOF
1759 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1760
1761 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1762 http://ftp.debian-ports.org/debian, because some of the packages in
1763 unstable do not yet include the required patches that are lingering in
1764 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1765
1766 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1767 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1768 i emacs - GNU Emacs editor (metapackage)
1769 i gdb - GNU Debugger
1770 i hurd-recommended - Miscellaneous translators
1771 i isc-dhcp-client - ISC DHCP client
1772 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1773 i libc-bin - Embedded GNU C Library: Binaries
1774 i libc-dev-bin - Embedded GNU C Library: Development binaries
1775 i libc0.3 - Embedded GNU C Library: Shared libraries
1776 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1777 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1778 i multiarch-support - Transitional package to ensure multiarch compatibilit
1779 i A x11-common - X Window System (X.Org) infrastructure
1780 i xorg - X.Org X Window System
1781 i A xserver-xorg - X.Org X server
1782 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1783 #
1784 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1785
1786 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1787 X.org did not work out of the box and I never took the time to follow
1788 the porters instructions to fix it. This time I was interested in the
1789 command line stuff.&lt;p&gt;
1790 </description>
1791 </item>
1792
1793 <item>
1794 <title>New chrpath release 0.16</title>
1795 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1796 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1797 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1798 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1799 find problems in C, C++ and Java code using static source code
1800 analysis. It can detect a lot of different problems, and is very
1801 useful to find memory and locking bugs in the error handling part of
1802 the source. The company behind it provide
1803 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1804 a community service&lt;/a&gt;, and many hundred free software projects are
1805 already checked. A few days ago I decided to have a closer look at
1806 the Coverity system, and discovered that the
1807 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1808 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1809 projects I am involved with was already registered. But these are
1810 fairly big, and I would also like to have a small and easy project to
1811 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1812 checking of the chrpath project&lt;/a&gt;. It was
1813 added to the checker and discovered seven potential defects. Six of
1814 these were real, mostly resource &quot;leak&quot; when the program detected an
1815 error. Nothing serious, as the resources would be released a fraction
1816 of a second later when the program exited because of the error, but it
1817 is nice to do it right in case the source of the program some time in
1818 the future end up in a library. Having fixed all defects and added
1819 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1820 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1821 publish a new release. These are the release notes:&lt;/p&gt;
1822
1823 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1824
1825 &lt;ul&gt;
1826
1827 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1828 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1829 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1830
1831 &lt;/ul&gt;
1832
1833 &lt;p&gt;You can
1834 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1835 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1836 project if something is wrong with the new release. The test suite
1837 did not discover any old errors, so if you find a new one, please also
1838 include a test suite check.&lt;/p&gt;
1839 </description>
1840 </item>
1841
1842 <item>
1843 <title>New chrpath release 0.15</title>
1844 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1845 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1846 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1847 <description>&lt;p&gt;After many years break from the package and a vain hope that
1848 development would be continued by someone else, I finally pulled my
1849 acts together this morning and wrapped up a new release of chrpath,
1850 the command line tool to modify the rpath and runpath of already
1851 compiled ELF programs. The update was triggered by the persistence of
1852 Isha Vishnoi at IBM, which needed a new config.guess file to get
1853 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1854 is working on. I checked the
1855 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1856 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1857 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1858 packages for interesting patches (failed to find the source from
1859 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1860 These are the release notes:&lt;/p&gt;
1861
1862 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1863
1864 &lt;ul&gt;
1865
1866 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1867 with newer architectures. Thanks to isha vishnoi for the heads
1868 up.&lt;/li&gt;
1869
1870 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1871
1872 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1873 Matthias Klose.&lt;/li&gt;
1874
1875 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1876 Petr Machata found in Fedora.&lt;/li&gt;
1877
1878 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1879 .dynamic is a NULL terminated string. Based on patch found in
1880 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1881
1882 &lt;/ul&gt;
1883
1884 &lt;p&gt;You can
1885 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1886 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1887 project if something is wrong with the new release. The test suite
1888 did not discover any old errors, so if you find a new one, please also
1889 include a testsuite check.&lt;/p&gt;
1890 </description>
1891 </item>
1892
1893 <item>
1894 <title>Debian init.d boot script example for rsyslog</title>
1895 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1896 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1897 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1898 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1899 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1900 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1901 init.d scripts at all. Here is an example init.d script, ie a rewrite
1902 of /etc/init.d/rsyslog:&lt;/p&gt;
1903
1904 &lt;p&gt;&lt;pre&gt;
1905 #!/lib/init/init-d-script
1906 ### BEGIN INIT INFO
1907 # Provides: rsyslog
1908 # Required-Start: $remote_fs $time
1909 # Required-Stop: umountnfs $time
1910 # X-Stop-After: sendsigs
1911 # Default-Start: 2 3 4 5
1912 # Default-Stop: 0 1 6
1913 # Short-Description: enhanced syslogd
1914 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1915 # It is quite compatible to stock sysklogd and can be
1916 # used as a drop-in replacement.
1917 ### END INIT INFO
1918 DESC=&quot;enhanced syslogd&quot;
1919 DAEMON=/usr/sbin/rsyslogd
1920 &lt;/pre&gt;&lt;/p&gt;
1921
1922 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1923 script was 137 lines, and the above is just 15 lines, most of it meta
1924 info/comments.&lt;/p&gt;
1925
1926 &lt;p&gt;How to do this, you ask? Well, one create a new script
1927 /lib/init/init-d-script looking something like this:
1928
1929 &lt;p&gt;&lt;pre&gt;
1930 #!/bin/sh
1931
1932 # Define LSB log_* functions.
1933 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1934 # and status_of_proc is working.
1935 . /lib/lsb/init-functions
1936
1937 #
1938 # Function that starts the daemon/service
1939
1940 #
1941 do_start()
1942 {
1943 # Return
1944 # 0 if daemon has been started
1945 # 1 if daemon was already running
1946 # 2 if daemon could not be started
1947 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1948 || return 1
1949 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1950 $DAEMON_ARGS \
1951 || return 2
1952 # Add code here, if necessary, that waits for the process to be ready
1953 # to handle requests from services started subsequently which depend
1954 # on this one. As a last resort, sleep for some time.
1955 }
1956
1957 #
1958 # Function that stops the daemon/service
1959 #
1960 do_stop()
1961 {
1962 # Return
1963 # 0 if daemon has been stopped
1964 # 1 if daemon was already stopped
1965 # 2 if daemon could not be stopped
1966 # other if a failure occurred
1967 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1968 RETVAL=&quot;$?&quot;
1969 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1970 # Wait for children to finish too if this is a daemon that forks
1971 # and if the daemon is only ever run from this initscript.
1972 # If the above conditions are not satisfied then add some other code
1973 # that waits for the process to drop all resources that could be
1974 # needed by services started subsequently. A last resort is to
1975 # sleep for some time.
1976 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1977 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1978 # Many daemons don&#39;t delete their pidfiles when they exit.
1979 rm -f $PIDFILE
1980 return &quot;$RETVAL&quot;
1981 }
1982
1983 #
1984 # Function that sends a SIGHUP to the daemon/service
1985 #
1986 do_reload() {
1987 #
1988 # If the daemon can reload its configuration without
1989 # restarting (for example, when it is sent a SIGHUP),
1990 # then implement that here.
1991 #
1992 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1993 return 0
1994 }
1995
1996 SCRIPTNAME=$1
1997 scriptbasename=&quot;$(basename $1)&quot;
1998 echo &quot;SN: $scriptbasename&quot;
1999 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2000 script=&quot;$1&quot;
2001 shift
2002 . $script
2003 else
2004 exit 0
2005 fi
2006
2007 NAME=$(basename $DAEMON)
2008 PIDFILE=/var/run/$NAME.pid
2009
2010 # Exit if the package is not installed
2011 #[ -x &quot;$DAEMON&quot; ] || exit 0
2012
2013 # Read configuration variable file if it is present
2014 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2015
2016 # Load the VERBOSE setting and other rcS variables
2017 . /lib/init/vars.sh
2018
2019 case &quot;$1&quot; in
2020 start)
2021 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2022 do_start
2023 case &quot;$?&quot; in
2024 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2025 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2026 esac
2027 ;;
2028 stop)
2029 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2030 do_stop
2031 case &quot;$?&quot; in
2032 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2033 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2034 esac
2035 ;;
2036 status)
2037 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2038 ;;
2039 #reload|force-reload)
2040 #
2041 # If do_reload() is not implemented then leave this commented out
2042 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2043 #
2044 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2045 #do_reload
2046 #log_end_msg $?
2047 #;;
2048 restart|force-reload)
2049 #
2050 # If the &quot;reload&quot; option is implemented then remove the
2051 # &#39;force-reload&#39; alias
2052 #
2053 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2054 do_stop
2055 case &quot;$?&quot; in
2056 0|1)
2057 do_start
2058 case &quot;$?&quot; in
2059 0) log_end_msg 0 ;;
2060 1) log_end_msg 1 ;; # Old process is still running
2061 *) log_end_msg 1 ;; # Failed to start
2062 esac
2063 ;;
2064 *)
2065 # Failed to stop
2066 log_end_msg 1
2067 ;;
2068 esac
2069 ;;
2070 *)
2071 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2072 exit 3
2073 ;;
2074 esac
2075
2076 :
2077 &lt;/pre&gt;&lt;/p&gt;
2078
2079 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2080 lot. I did not really polish the approach, so it might not always
2081 work out of the box, but you get the idea. I did not try very hard to
2082 optimize it nor make it more robust either.&lt;/p&gt;
2083
2084 &lt;p&gt;A better argument for switching init system in Debian than reducing
2085 the size of init scripts (which is a good thing to do anyway), is to
2086 get boot system that is able to handle the kernel events sensibly and
2087 robustly, and do not depend on the boot to run sequentially. The boot
2088 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2089 </description>
2090 </item>
2091
2092 <item>
2093 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2094 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2095 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2096 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2097 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2098 remote display access is the preferred solution with oVirt and RedHat
2099 Enterprise Virtualization, and I was sad to discover the other day
2100 that the browser plugin needed to use these systems seamlessly was
2101 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2102 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2103 2013-04-01, so I decided to wrap up a package based on the great work
2104 from Cajus Pollmeier and put it in a collab-maint maintained git
2105 repository to get a package I could use. I would very much like
2106 others to help me maintain the package (or just take over, I do not
2107 mind), but as no-one had volunteered so far, I just uploaded it to
2108 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2109
2110 &lt;p&gt;The source is now available from
2111 &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;
2112 </description>
2113 </item>
2114
2115 <item>
2116 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2117 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2118 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2119 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2120 <description>&lt;p&gt;The
2121 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2122 program is a a very nice system to create virtual machine images. It
2123 create a image file, add a partition table, mount it and run
2124 debootstrap in the mounted directory to create a Debian system on a
2125 stick. Yesterday, I decided to try to teach it how to make images for
2126 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2127 of a plan to simplify the build system for
2128 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2129 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2130 the virtualbox images, but its current build system made multistrap
2131 based system for Dreamplug images, and it is lacking support for
2132 Raspberry Pi.&lt;/p&gt;
2133
2134 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2135 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2136 code and adjusted it to be able to build armel images on my amd64
2137 Debian laptop. I ended up giving vmdebootstrap five new options,
2138 allowing me to replicate the image creation process I use to make
2139 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2140 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2141 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2142 call debootstrap with --foreign and to copy the handler into the
2143 generated chroot before running the second stage. This allow
2144 vmdebootstrap to create armel images on an amd64 host. Next I added
2145 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2146 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2147 given file system type, allowing me to create an image with a vfat
2148 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2149 variant&lt;/tt&gt; option to allow me to create smaller images without the
2150 Debian base system packages installed. Finally, I added an option
2151 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2152 as a boot loader. It is not needed on the Raspberry Pi and probably
2153 most other non-x86 architectures. The changes were accepted by the
2154 upstream author of vmdebootstrap yesterday and today, and is now
2155 available from
2156 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2157 upstream project page&lt;/a&gt;.&lt;/p&gt;
2158
2159 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2160 create a small script (the customize script) to add the non-free
2161 binary blob needed to boot the Raspberry Pi and the APT source
2162 list:&lt;/p&gt;
2163
2164 &lt;p&gt;&lt;pre&gt;
2165 #!/bin/sh
2166 set -e # Exit on first error
2167 rootdir=&quot;$1&quot;
2168 cd &quot;$rootdir&quot;
2169 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2170 deb http://http.debian.net/debian/ jessie main contrib non-free
2171 EOF
2172 # Install non-free binary blob needed to boot Raspberry Pi. This
2173 # install a kernel somewhere too.
2174 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2175 -O $rootdir/usr/bin/rpi-update
2176 chmod a+x $rootdir/usr/bin/rpi-update
2177 mkdir -p $rootdir/lib/modules
2178 touch $rootdir/boot/start.elf
2179 chroot $rootdir rpi-update
2180 &lt;/pre&gt;&lt;/p&gt;
2181
2182 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2183 to build the image:&lt;/p&gt;
2184
2185 &lt;pre&gt;
2186 sudo ./vmdebootstrap \
2187 --variant minbase \
2188 --arch armel \
2189 --distribution jessie \
2190 --mirror http://http.debian.net/debian \
2191 --image test.img \
2192 --size 600M \
2193 --bootsize 64M \
2194 --boottype vfat \
2195 --log-level debug \
2196 --verbose \
2197 --no-kernel \
2198 --no-extlinux \
2199 --root-password raspberry \
2200 --hostname raspberrypi \
2201 --foreign /usr/bin/qemu-arm-static \
2202 --customize `pwd`/customize \
2203 --package netbase \
2204 --package git-core \
2205 --package binutils \
2206 --package ca-certificates \
2207 --package wget \
2208 --package kmod
2209 &lt;/pre&gt;&lt;/p&gt;
2210
2211 &lt;p&gt;The list of packages being installed are the ones needed by
2212 rpi-update to make the image bootable on the Raspberry Pi, with the
2213 exception of netbase, which is needed by debootstrap to find
2214 /etc/hosts with the minbase variant. I really wish there was a way to
2215 set up an Raspberry Pi using only packages in the Debian archive, but
2216 that is not possible as far as I know, because it boots from the GPU
2217 using a non-free binary blob.&lt;/p&gt;
2218
2219 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2220 probably a few others installed. I have not checked the complete
2221 build dependency list.&lt;/p&gt;
2222
2223 &lt;p&gt;The resulting image will not use the hardware floating point unit
2224 on the Raspberry PI, because the armel architecture in Debian is not
2225 optimized for that use. So the images created will be a bit slower
2226 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2227 </description>
2228 </item>
2229
2230 <item>
2231 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2232 <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>
2233 <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>
2234 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2235 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2236 wider attention. I recommend signing and donating to each one of
2237 these. :)&lt;/p&gt;
2238
2239 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2240 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2241 Women program which is a Google Summer of Code like initiative to get
2242 more women involved in free software. One debian sponsor has offered
2243 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2244 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2245 hope you will to. :)&lt;/p&gt;
2246
2247 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2248 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2249 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2250 take place these days, and their need to fund the work. I&#39;ve already
2251 donated. Are you next?&lt;/p&gt;
2252
2253 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2254 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2255 statement under the heading
2256 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2257 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2258 Norwegian government. So far 499 signatures. I hope you will sign it
2259 too.&lt;/p&gt;
2260 </description>
2261 </item>
2262
2263 <item>
2264 <title>Videos about the Freedombox project - for inspiration and learning</title>
2265 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2266 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2267 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2268 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2269 project&lt;/a&gt; have been going on for a while, and have presented the
2270 vision, ideas and solution several places. Here is a little
2271 collection of videos of talks and presentation of the project.&lt;/p&gt;
2272
2273 &lt;ul&gt;
2274
2275 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2276 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2277
2278 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2279 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2280
2281 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2282 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2283 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2284 (Youtube)&lt;/li&gt;
2285
2286 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2287 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2288
2289 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2290 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2291
2292 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2293 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2294 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2295
2296 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2297 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2298 (Youtube)&lt;/li&gt;
2299
2300 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2301 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2302
2303 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2304 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2305
2306 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2307 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2308 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2309
2310 &lt;/ul&gt;
2311
2312 &lt;p&gt;A larger list is available from
2313 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2314 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2315
2316 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2317 Jessie is coming along quite well, and soon both Owncloud and using
2318 Tor should be available for testers of the Freedombox solution. :) In
2319 a few weeks I hope everything needed to test it is included in Debian.
2320 The withsqlite package is already in Debian, and the plinth package is
2321 pending in NEW. The third and vital part of that puzzle is the
2322 metapackage/setup framework, which is still pending an upload. Join
2323 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2324 (#freedombox on irc.debian.org)&lt;/a&gt; and
2325 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2326 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2327 </description>
2328 </item>
2329
2330 <item>
2331 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2332 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2333 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2334 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2335 <description>&lt;p&gt;I was introduced to the
2336 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2337 in 2010, when Eben Moglen presented his vision about serving the need
2338 of non-technical people to keep their personal information private and
2339 within the legal protection of their own homes. The idea is to give
2340 people back the power over their network and machines, and return
2341 Internet back to its intended peer-to-peer architecture. Instead of
2342 depending on a central service, the Freedombox will give everyone
2343 control over their own basic infrastructure.&lt;/p&gt;
2344
2345 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2346 taken priority. But this summers nasty news about the misuse of trust
2347 and privilege exercised by the &quot;western&quot; intelligence gathering
2348 communities increased my eagerness to contribute to a point where I
2349 actually started working on the project a while back.&lt;/p&gt;
2350
2351 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2352 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2353 create a simple and cheap Debian based appliance that anyone can hook
2354 up in their home and get access to secure and private services and
2355 communication. The initial deployment platform have been the
2356 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2357 which is a piece of hardware I do not own. So to be able to test what
2358 the current Freedombox setup look like, I had to come up with a way to install
2359 it on some hardware I do have access to. I have rewritten the
2360 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2361 image build framework to use .deb packages instead of only copying
2362 setup into the boot images, and thanks to this rewrite I am able to
2363 set up any machine supported by Debian Wheezy as a Freedombox, using
2364 the previously mentioned deb (and a few support debs for packages
2365 missing in Debian).&lt;/p&gt;
2366
2367 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2368 scripts
2369 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2370 and a administrative web interface
2371 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2372 withsqlite), as well as a privacy enhancing proxy based on
2373 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2374 (freedombox-privoxy). There is also a web/javascript based XMPP
2375 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2376 trying (unsuccessfully so far) to talk to the XMPP server
2377 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2378 web interface is pluggable, and the goal is to use it to enable OpenID
2379 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2380 this is really working yet, see
2381 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2382 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2383 on github at the moment. The HTTP proxy is operational out of the
2384 box, and the admin web interface can be used to add/remove plinth
2385 users. I&#39;ve not been able to do anything else with it so far, but
2386 know there are several branches spread around github and other places
2387 with lots of half baked features.&lt;/p&gt;
2388
2389 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2390 following recipes should work to give you a test machine to poke
2391 at.&lt;/p&gt;
2392
2393 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2394
2395 &lt;ol&gt;
2396
2397 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2398 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2399 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2400 to the Debian installer:&lt;p&gt;
2401 &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;
2402
2403 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2404 install on.&lt;/li&gt;
2405
2406 &lt;li&gt;When the installation is finished and the machine have rebooted a
2407 few times, your Freedombox is ready for testing.&lt;/li&gt;
2408
2409 &lt;/ol&gt;
2410
2411 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2412
2413 &lt;ol&gt;
2414
2415 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2416 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2417 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2418 &lt;pre&gt;
2419 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2420 &lt;/pre&gt;&lt;/li&gt;
2421 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2422 &lt;pre&gt;
2423 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2424 apt-key add -
2425 apt-get update
2426 apt-get install freedombox-setup
2427 /usr/lib/freedombox/setup
2428 &lt;/pre&gt;&lt;/li&gt;
2429 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2430
2431 &lt;/ol&gt;
2432
2433 &lt;p&gt;You can test it on other architectures too, but because the
2434 freedombox-privoxy package is binary, it will only work as intended on
2435 the architectures where I have had time to build the binary and put it
2436 in my APT repository. But do not let this stop you. It is only a
2437 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2438
2439 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2440 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2441 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2442 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2443
2444 &lt;p&gt;Please let me know if this works for you, or if you have any
2445 problems. We gather on the IRC channel
2446 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2447 irc.debian.org and the
2448 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2449 mailing list&lt;/a&gt;.&lt;/p&gt;
2450
2451 &lt;p&gt;Once you get your freedombox operational, you can visit
2452 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2453 welcome screen (dead end - do not be surprised if you are unable to
2454 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2455 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2456 default password is &#39;secret&#39;.&lt;/p&gt;
2457 </description>
2458 </item>
2459
2460 <item>
2461 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2462 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2463 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2464 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2465 <description>&lt;p&gt;Earlier, I reported about
2466 &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
2467 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2468 told by IBM that the original disk should be thrown away. And as
2469 there no longer was a problem if I bricked the firmware, I decided
2470 today to try to install Intel firmware to replace the Lenovo firmware
2471 currently on the disk.&lt;/p&gt;
2472
2473 &lt;p&gt;I searched the Intel site for firmware, and found
2474 &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;
2475 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2476 according to the site should contain the latest firmware for SSD
2477 disks. I inserted the broken disk in one of my spare laptops and
2478 booted the ISO from a USB stick. The disk was recognized, but the
2479 program claimed the newest firmware already were installed and refused
2480 to insert any Intel firmware. So no change, and the disk is still
2481 unable to handle write load. :( I guess the only way to get them
2482 working would be if Lenovo releases new firmware. No idea how likely
2483 that is. Anyway, just blogging about this test for completeness. I
2484 got a working Samsung disk, and see no point in spending more time on
2485 the broken disks.&lt;/p&gt;
2486 </description>
2487 </item>
2488
2489 <item>
2490 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2491 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2492 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2493 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2494 <description>&lt;p&gt;Today I switched to
2495 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2496 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2497 my new Thinkpad X230, which was delivered with an
2498 &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
2499 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2500 sustained writes. My hardware supplier have been very forthcoming in
2501 trying to find a solution, and after first trying with another
2502 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2503 disk instead to fix it once and for all. The Samsung disk survived
2504 the installation of Debian with encrypted disks (filling the disk with
2505 random data during installation killed the first two), and I thus
2506 decided to trust it with my data. I have installed it as a Debian Edu
2507 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2508 server at home using Kerberos and LDAP, and will use it as my work
2509 station from now on.&lt;/p&gt;
2510
2511 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2512 Debian Wheezy default installation need to be tuned a bit to increase
2513 performance and increase life time of the disk. The Linux kernel and
2514 user space applications do not yet adjust automatically to such
2515 environment. To make it easier for my self, I created a draft Debian
2516 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2517 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2518 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2519 is set up to adjust the setup of the machine by just installing the
2520 package. If there is any non-SSD disk in the machine, the package
2521 will refuse to install, as I did not try to write any logic to sort
2522 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2523
2524 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2525 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2526 where I set up the machine with one large encrypted partition (in
2527 addition to /boot), put LVM on top of this and set up partitions on
2528 top of this again. See the README file in the package source for the
2529 references I used to pick the settings. At the moment these
2530 parameters are tuned:&lt;/p&gt;
2531
2532 &lt;ul&gt;
2533
2534 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2535 (adding discard to /etc/crypttab)&lt;/li&gt;
2536
2537 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2538 this case a cryptsetup partition) by changing issue_discards from
2539 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2540
2541 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2542 systems.&lt;/li&gt;
2543
2544 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2545 /etc/fstab.&lt;/li&gt;
2546
2547 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2548
2549 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2550 cron.daily).&lt;/li&gt;
2551
2552 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2553 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2554
2555 &lt;/ul&gt;
2556
2557 &lt;p&gt;During installation, I cancelled the part where the installer fill
2558 the disk with random data, as this would kill the SSD performance for
2559 little gain. My goal with the encrypted file system is to ensure
2560 those stealing my laptop end up with a brick and not a working
2561 computer. I have no hope in keeping the really resourceful people
2562 from getting the data on the disk (see
2563 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2564 Thus I concluded that adding the discard option to crypttab is the
2565 right thing to do.&lt;/p&gt;
2566
2567 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2568 it for SSD, but others recommended deadline and a benchmark I found
2569 indicated that deadline might be better for interactive use.&lt;/p&gt;
2570
2571 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2572 and ext4, but read that it would give a performance hit ever time a
2573 file is removed, and thought it best to that that slowdown once a day
2574 instead of during my work.&lt;/p&gt;
2575
2576 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2577 this is already done by Debian Edu.&lt;/p&gt;
2578
2579 &lt;p&gt;I have not yet started on the user space tuning. I expect
2580 iceweasel need some tuning, and perhaps other applications too, but
2581 have not yet had time to investigate those parts.&lt;/p&gt;
2582
2583 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2584 there.&lt;/p&gt;
2585
2586 &lt;p&gt;As for the answer to the question in the title of this blog post,
2587 as far as I know, the only solution I know about is to replace the
2588 disk. It might be possible to flash it with Intel firmware instead of
2589 the Lenovo firmware. But I have not tried and did not want to do so
2590 without approval from Lenovo as I wanted to keep the warranty on the
2591 disk until a solution was found and they wanted the broken disks
2592 back.&lt;/p&gt;
2593 </description>
2594 </item>
2595
2596 <item>
2597 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2598 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2599 <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>
2600 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2601 <description>&lt;p&gt;A few days ago, I wrote about
2602 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2603 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2604 was dying during installation because it is unable to cope with
2605 sustained write. My supplier is in contact with
2606 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2607 replacement disk to try to fix the problem. They decided to send an
2608 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2609
2610 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2611 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2612 same firmware version as the original. This time my hope raised
2613 slightly as the installation progressed, as the original disk used to
2614 die after 4-7% of the disk was written to, while this time it kept
2615 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2616 died again and I was back on square one. I still do not have a new
2617 laptop with a disk I can trust. I can not live with a disk that might
2618 lock up when I download a new
2619 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2620 other large files. I look forward to hearing from my supplier with
2621 the next proposal from Lenovo.&lt;/p&gt;
2622
2623 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2624 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2625 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2626 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2627 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2628 P/N 45N8295, P0C38732.&lt;/p&gt;
2629
2630 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2631 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2632 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2633 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2634 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2635 P/N 45N8295, P0C38732.&lt;/p&gt;
2636
2637 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2638 SA, date and WNPP values. Mentioning all the details here in case
2639 someone is able to use the information to find a way to identify the
2640 failing disk among working ones (if any such working disk actually
2641 exist).&lt;/p&gt;
2642 </description>
2643 </item>
2644
2645 <item>
2646 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2647 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2649 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2650 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2651 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2652 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2653 member assosiation NUUG&lt;/a&gt; and
2654 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2655 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2656 Bitraf&lt;/a&gt;.&lt;/p&gt;
2657
2658 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2659 welcome, and there is no fee to participate. There is on the other
2660 hand limited space, and only room for 30 people. Please put your name
2661 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2662 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2663 </description>
2664 </item>
2665
2666 <item>
2667 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2668 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2669 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2670 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2671 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2672 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2673 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2674 time to spend on it, and it took a while to find a model I believe
2675 will do the job, but two days ago the replacement finally arrived. I
2676 ended up picking a
2677 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2678 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2679 a roaming workstation, and it seemed to work flawlessly. But my
2680 second installation with encrypted disk was not as successful. More
2681 on that below.&lt;/p&gt;
2682
2683 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2684 important requirements (robust and with a good keyboard) are never
2685 listed in the feature list. But I did get good help from the search
2686 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2687 allowed me to limit the list of interesting laptops based on my other
2688 requirements. A bit surprising that SSD disk are not disks according
2689 to that search interface, so I had to drop specifying the number of
2690 disks from my search parameters. I also asked around among friends to
2691 get their impression on keyboards and robustness.&lt;/p&gt;
2692
2693 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2694 X41. I am not quite convinced about the keyboard, as it is
2695 significantly wider than my old keyboard, and I have to stretch my
2696 hand a lot more to reach the edges. But the key response is fairly
2697 good and the individual key shape is fairly easy to handle, so I hope
2698 I will get used to it. My old X40 was starting to fail, and I really
2699 needed a new laptop now. :)&lt;/p&gt;
2700
2701 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2702 visit to the BIOS during boot it disable it.&lt;/p&gt;
2703
2704 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2705 lock up during load. And this happen when installing Debian Wheezy
2706 with encrypted disk, while the disk is being filled with random data.
2707 I also tested to install Ubuntu Raring, and it happen there too if I
2708 reenable the code to fill the disk with random data (it is disabled by
2709 default in Ubuntu). And the bug with is already known. It was
2710 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2711 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2712 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2713 kernel developers as
2714 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2715 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2716 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2717 Lenovo forums, both for
2718 &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
2719 2012-11-10&lt;/a&gt; and for
2720 &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
2721 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2722 reports state that the disk lock up during use if many writes are done
2723 on the disk, so it is much no use to work around the installation
2724 problem and end up with a computer that can lock up at any moment.
2725 There is even a
2726 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2727 available&lt;/a&gt; that will lock up the hard drive after running a few
2728 minutes by writing to a file.&lt;/p&gt;
2729
2730 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2731 contacting PCHELP Norway (request 01D1FDP) which handle support
2732 requests for Lenovo, his first suggestion was to upgrade the disk
2733 firmware. Unfortunately there is no newer firmware available from
2734 Lenovo, as my disk already have the most recent one (version LF1i). I
2735 hope to hear more from him today and hope the problem can be
2736 fixed. :)&lt;/p&gt;
2737 </description>
2738 </item>
2739
2740 <item>
2741 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2742 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2743 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2744 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2745 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2746 trusty old Thinkpad X41. Unfortunately I did not have much time to
2747 spend on it, but today the replacement finally arrived. I ended up
2748 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2749 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2750 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2751 this, it is installing what I hope will be a more final installation,
2752 with a encrypted hard drive to ensure any dope head stealing it end up
2753 with an expencive door stop.&lt;/p&gt;
2754
2755 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2756 important requirements (robust and with a good keyboard) are never
2757 listed in the feature list. But I did get good help from the search
2758 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2759 allowed me to limit the list of interesting laptops based on my other
2760 requirements. A bit surprising that SSD disk are not disks, so I had
2761 to drop number of disks from my search parameters.&lt;/p&gt;
2762
2763 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2764 wider than my old keyboard, and I have to stretch my hand a lot more
2765 to reach the edges. But the key response is fairly good and the
2766 individual key shape is fairly easy to handle, so I hope I will get
2767 used to it. My old X40 was starting to fail, and I really needed a
2768 new laptop now. :)&lt;/p&gt;
2769
2770 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2771 </description>
2772 </item>
2773
2774 <item>
2775 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2776 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2777 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2778 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2779 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2780 perfectly capable of, and I have to do it manually to get things
2781 working. One such task is to find out what firmware packages are
2782 needed to get the hardware on my computer working. Most often this
2783 affect the wifi card, but some times it even affect the RAID
2784 controller or the ethernet card. Today I pushed version 0.4 of the
2785 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2786 including a new script isenkram-autoinstall-firmware handling the
2787 process of asking all the loaded kernel modules what firmware files
2788 they want, find debian packages providing these files and install the
2789 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2790
2791 &lt;p&gt;&lt;pre&gt;
2792 # isenkram-autoinstall-firmware
2793 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2794 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2795 info: locating packages with the requested firmware files
2796 info: Updating APT sources after adding non-free APT source
2797 info: trying to install firmware-ipw2x00
2798 firmware-ipw2x00
2799 firmware-ipw2x00
2800 Preconfiguring packages ...
2801 Selecting previously deselected package firmware-ipw2x00.
2802 (Reading database ... 259727 files and directories currently installed.)
2803 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2804 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2805 #
2806 &lt;/pre&gt;&lt;/p&gt;
2807
2808 &lt;p&gt;When all the requested firmware is present, a simple message is
2809 printed instead:&lt;/p&gt;
2810
2811 &lt;p&gt;&lt;pre&gt;
2812 # isenkram-autoinstall-firmware
2813 info: did not find any firmware files requested by loaded kernel modules. exiting
2814 #
2815 &lt;/pre&gt;&lt;/p&gt;
2816
2817 &lt;p&gt;It could use some polish, but it is already working well and saving
2818 me some time when setting up new machines. :)&lt;/p&gt;
2819
2820 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2821 kernel modules, and look up each one of them using modinfo, to find
2822 the firmware files listed in the module meta-information. Next, it
2823 download the Contents file from a nearby APT mirror, and search for
2824 the firmware files in this file to locate the package with the
2825 requested firmware file. If the package is in the non-free section, a
2826 non-free APT source is added and the package is installed using
2827 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2828 machine.&lt;/p&gt;
2829
2830 &lt;p&gt;I hope someone find time to implement a more polished version of
2831 this script as part of the hw-detect debian-installer module, to
2832 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2833 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2834 firmware during a PXE install when the packages already are available
2835 from the nearby Debian mirror.&lt;/p&gt;
2836 </description>
2837 </item>
2838
2839 <item>
2840 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2841 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2842 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2843 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2844 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2845 the screen just turn black when Linux boot, either during installation
2846 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2847 last few years, but only recently understood the cause. I&#39;ve seen it
2848 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2849 The reason seem to be in the wiring of some laptops. The system to
2850 control the screen background light is inverted, so when Linux try to
2851 turn the brightness fully on, it end up turning it off instead. I do
2852 not know which Linux drivers are affected, but this post is about the
2853 i915 driver used by the
2854 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2855 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2856
2857 &lt;p&gt;The problem can be worked around two ways. Either by adding
2858 i915.invert_brightness=1 as a kernel option, or by adding a file in
2859 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2860 option when it load the i915 kernel module. On Debian and Ubuntu, it
2861 can be done by running these commands as root:&lt;/p&gt;
2862
2863 &lt;pre&gt;
2864 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2865 update-initramfs -u -k all
2866 &lt;/pre&gt;
2867
2868 &lt;p&gt;Since March 2012 there is
2869 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2870 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2871 hardware have this problem, and get the driver to invert the
2872 brightness setting automatically. To use it, one need to add a row in
2873 &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
2874 intel_quirks array&lt;/a&gt; in the driver source
2875 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2876 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2877 number (vendor number 8086 is assumed) and subdevice vendor and device
2878 number.&lt;/p&gt;
2879
2880 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2881 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2882
2883 &lt;p&gt;&lt;pre&gt;
2884 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2885 3rd Gen Core processor Graphics Controller [8086:0156] \
2886 (rev 09) (prog-if 00 [VGA controller])
2887 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2888 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2889 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2890 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2891 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2892 Latency: 0
2893 Interrupt: pin A routed to IRQ 42
2894 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2895 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2896 Region 4: I/O ports at 4000 [size=64]
2897 Expansion ROM at &lt;unassigned&gt; [disabled]
2898 Capabilities: &lt;access denied&gt;
2899 Kernel driver in use: i915
2900 &lt;/pre&gt;&lt;/p&gt;
2901
2902 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2903
2904 &lt;p&gt;&lt;pre&gt;
2905 struct intel_quirk intel_quirks[] = {
2906 ...
2907 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2908 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2909 ...
2910 }
2911 &lt;/pre&gt;&lt;/p&gt;
2912
2913 &lt;p&gt;According to the kernel module instructions (as seen using
2914 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2915 invert_brightness flag should be sent to the
2916 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2917 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2918 developers. But my email about the laptop sent 2013-06-03 have not
2919 yet shown up in
2920 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2921 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2922 emails from non-subscribers. Because of this, I sent my patch also to
2923 the Debian bug tracking system instead as
2924 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2925 sure the patch is not lost.&lt;/p&gt;
2926
2927 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2928 with this problem working properly with Linux. If you use Gnome, your
2929 worries should be over at this point. But if you use KDE, there is
2930 something in KDE ignoring the invert_brightness setting and turning on
2931 the screen during login. I&#39;ve reported it to Debian as
2932 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2933 have no idea yet how to figure out exactly what subsystem is doing
2934 this. Perhaps you can help? Perhaps you know what the Gnome
2935 developers did to handle this, and this can give a clue to the KDE
2936 developers? Or you know where in KDE the screen brightness is changed
2937 during login? If so, please update the BTS report (or get in touch if
2938 you do not know how to update BTS).&lt;/p&gt;
2939
2940 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2941 acpi_backlight=vendor, to disable ACPI backlight support completely,
2942 as the ACPI information on the machine is trash and it is better to
2943 leave it to the intel video driver to control the screen
2944 backlight.&lt;/p&gt;
2945 </description>
2946 </item>
2947
2948 <item>
2949 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2950 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2951 <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>
2952 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2953 <description>&lt;p&gt;Two days ago, I asked
2954 &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
2955 I could install Linux on a Packard Bell EasyNote LV computer
2956 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2957 with the obstacles put in the way of Linux users on a laptop with UEFI
2958 and Windows 8.&lt;/p&gt;
2959
2960 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2961 secure booting or fast boot. I suspect fast boot was the problem,
2962 causing the firmware to boot directly from HD without considering any
2963 key presses and alternative devices, but do not know UEFI settings
2964 enough to tell.&lt;/p&gt;
2965
2966 &lt;p&gt;There is no way to install Linux on the machine in question without
2967 opening the box and disconnecting the hard drive! This is as far as I
2968 can tell, the only way to get access to the firmware setup menu
2969 without accepting the Windows 8 license agreement. I am told (and
2970 found description on how to) that it is possible to configure the
2971 firmware setup once booted into Windows 8. But as I believe the terms
2972 of that agreement are completely unacceptable, accepting the license
2973 was never an alternative. I do not enter agreements I do not intend
2974 to follow.&lt;/p&gt;
2975
2976 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2977 waste many hours on this, but luckily there was a way to get it to
2978 work. But I would not recommend it to anyone planning to run Linux on
2979 it, and I have become sceptical to Windows 8 certified laptops. Is
2980 this the way Linux will be forced out of the market place, by making
2981 it close to impossible for &quot;normal&quot; users to install Linux without
2982 accepting the Microsoft Windows license terms? Or at least not
2983 without risking to loose the warranty?&lt;/p&gt;
2984
2985 &lt;p&gt;I&#39;ve updated the
2986 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2987 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2988 do not have to struggle as much as I did to get Linux into the
2989 machine.&lt;/p&gt;
2990
2991 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2992 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2993 </description>
2994 </item>
2995
2996 <item>
2997 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2998 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2999 <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>
3000 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3001 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3002 new laptops for my parents and a few others. I bought Packard Bell
3003 Easynote LV to run Kubuntu on and use as their home computer. But I
3004 am completely unable to figure out how to install Linux on it. The
3005 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3006 instead of a BIOS to boot.&lt;/p&gt;
3007
3008 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3009 to get it to boot the Linux installer from my USB stick. I have yet
3010 to try the DVD install, and still hope it will work. when I turn on
3011 the computer, there is no information on what buttons to press to get
3012 the normal boot menu. I expect to get some boot menu to select PXE or
3013 USB stick booting. When booting, it first ask for the language to
3014 use, then for some regional settings, and finally if I will accept the
3015 Windows 8 terms of use. As these terms are completely unacceptable to
3016 me, I have no other choice but to turn off the computer and try again
3017 to get it to boot the Linux installer.&lt;/p&gt;
3018
3019 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3020 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3021 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3022 installed on this machine, please get in touch or update that wiki
3023 page. If I can&#39;t find a way to install Linux, I will have to return
3024 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3025
3026 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3027 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3028 on new Laptops?&lt;/p&gt;
3029 </description>
3030 </item>
3031
3032 <item>
3033 <title>How to transform a Debian based system to a Debian Edu installation</title>
3034 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3035 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3036 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3037 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3038 an operating system based on Debian intended for use in schools. It
3039 contain a turn-key solution for the computer network provided to
3040 pupils in the primary schools. It provide both the central server,
3041 network boot servers and desktop environments with heaps of
3042 educational software. The project was founded almost 12 years ago,
3043 2001-07-02. If you want to support the project, which is in need for
3044 cash to fund developer gatherings and other project related activity,
3045 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3046 donate some money&lt;/a&gt;.
3047
3048 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3049 lists and elsewhere, is the question on how to transform a Debian or
3050 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3051 hard, and last week I wrote a script to replicate the steps done by
3052 the Debian Edu installer.&lt;/p&gt;
3053
3054 &lt;p&gt;The script,
3055 &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;
3056 in the debian-edu-config package, will go through these six steps and
3057 transform an existing Debian Wheezy or Ubuntu (untested) installation
3058 into a Debian Edu Workstation:&lt;/p&gt;
3059
3060 &lt;ol&gt;
3061
3062 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3063 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3064 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3065 our configuration.&lt;/li&gt;
3066 &lt;li&gt;Preseed debconf database with profile setup in
3067 /etc/debian-edu/config, and run tasksel to install packages
3068 according to the profile specified in the config above,
3069 overriding some of the Debian automation machinery.&lt;/li&gt;
3070 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3071 that could not be done using preseeding.&lt;/li&gt;
3072 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3073
3074 &lt;/ol&gt;
3075
3076 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3077 replicated like this. Disk partitioning and LVM setup, for example.
3078 So this script just assume there is enough disk space to install all
3079 the needed packages.&lt;/p&gt;
3080
3081 &lt;p&gt;The script was created to help a Debian Edu student working on
3082 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3083 Debian Edu client, and using it he can take the existing
3084 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3085 transform it into a fully functioning Debian Edu Workstation (or
3086 Roaming Workstation, or whatever :).&lt;/p&gt;
3087
3088 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3089 If a LXDE based Roaming workstation is wanted instead, modify the
3090 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3091
3092 &lt;p&gt;&lt;pre&gt;
3093 PROFILE=&quot;Roaming-Workstation&quot;
3094 DESKTOP=&quot;lxde&quot;
3095 &lt;/pre&gt;&lt;/p&gt;
3096
3097 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3098 the cloud, by starting with a virtual Debian installation at some
3099 virtual hosting service and setting up all the services on first
3100 boot.&lt;/p&gt;
3101 </description>
3102 </item>
3103
3104 <item>
3105 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3106 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3107 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3108 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3109 <description>&lt;P&gt;In January,
3110 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3111 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3112 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3113 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3114 marvellous construction system from Denmark. We also created
3115 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3116 a place to take notes and write down our plans and hopes. And several
3117 people showed up to help. I was very happy to see the effect of my
3118 call. Since the small start, we have a debtags tag
3119 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3120 tag for LEGO related packages, and now count 10 packages related to
3121 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3122
3123 &lt;p&gt;&lt;table&gt;
3124 &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;
3125 &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;
3126 &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;
3127 &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;
3128 &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;
3129 &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;
3130 &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;
3131 &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;
3132 &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;
3133 &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;
3134 &lt;/table&gt;&lt;/p&gt;
3135
3136 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3137 currently available in Jessie/testing. leocad is so far only
3138 available in experimental.&lt;/p&gt;
3139
3140 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3141 adding the rest of the great free software tools available on Linux
3142 for LEGO designers.&lt;/p&gt;
3143 </description>
3144 </item>
3145
3146 <item>
3147 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3148 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3149 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3150 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3151 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3152 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3153 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3154 Debian release, and I expect to move my machines at home over to it fairly
3155 soon.&lt;/p&gt;
3156
3157 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3158 in particular make me very happy to see included. The
3159 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3160 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3161 included for the first time. Alongside similar programs like
3162 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3163 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3164 it allow for visual programming where syntax errors can not happen,
3165 and a friendly programming environment for learning to control the
3166 computer. Scratch will also be included in the next release of Debian
3167 Edu.&lt;/a&gt;
3168
3169 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3170 Edu/Skolelinux release too. The
3171 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3172 alpha release&lt;/a&gt; went out last week, and the next should soon
3173 follow.&lt;p&gt;
3174 </description>
3175 </item>
3176
3177 <item>
3178 <title>Isenkram 0.2 finally in the Debian archive</title>
3179 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3181 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3182 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3183 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3184 for many months. I uploaded it to the Debian experimental suite
3185 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3186
3187 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3188 install to work with a pluggable hardware device. The suggestion pop
3189 up when the device is plugged in. For example if a Lego Mindstorm NXT
3190 is inserted, it will suggest to install the program needed to program
3191 the NXT controller. Give it a go, and report bugs and suggestions to
3192 BTS. :)&lt;/p&gt;
3193 </description>
3194 </item>
3195
3196 <item>
3197 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3198 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3199 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3200 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3201 <description>&lt;p&gt;My
3202 &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
3203 bitcoin related blog post&lt;/a&gt; mentioned that the new
3204 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3205 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3206 2013-01-19, and have been available in unstable since then. It was
3207 automatically copied to Ubuntu, and is available in their Raring
3208 version too.&lt;/p&gt;
3209
3210 &lt;p&gt;But there is a strange problem with the build that block this new
3211 version from being available on the i386 and kfreebsd-i386
3212 architectures. For some strange reason, the autobuilders in Debian
3213 for these architectures fail to run the test suite on these
3214 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3215 We are so far unable to reproduce it when building it manually, and
3216 no-one have been able to propose a fix. If you got an idea what is
3217 failing, please let us know via the BTS.&lt;/p&gt;
3218
3219 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3220 I often run low on disk space, is the fact that the client will exit
3221 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3222 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3223 it. :)&lt;/p&gt;
3224
3225 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3226 activities, please send Bitcoin donations to my address
3227 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3228 </description>
3229 </item>
3230
3231 <item>
3232 <title>Welcome to the world, Isenkram!</title>
3233 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3234 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3235 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3236 <description>&lt;p&gt;Yesterday, I
3237 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3238 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3239 pluggable hardware devices, which I
3240 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3241 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3242 up, and caused me to really want to to open up the development to more
3243 people. But before I did this, I want to come up with a sensible name
3244 for this project. Today I finally decided on a new name, and I have
3245 renamed the project from hw-support-handler to this new name. In the
3246 process, I moved the source to git and made it available as a
3247 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3248 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3249 To fetch and build the latest version of the source, use&lt;/p&gt;
3250
3251 &lt;pre&gt;
3252 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3253 cd isenkram &amp;&amp; git-buildpackage -us -uc
3254 &lt;/pre&gt;
3255
3256 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3257 want to hack on the source or improve the package, please go ahead.
3258 But please talk to me first on IRC or via email before you do major
3259 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3260
3261 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3262 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3263 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3264 the German word eisenkram, for those that are familiar with that
3265 word.&lt;/p&gt;
3266
3267 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3268 instructions, to avoid confusing people with an error from the signing
3269 process.&lt;/p&gt;
3270
3271 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3272 clone argument to avoid the need for authentication.&lt;/p&gt;
3273 </description>
3274 </item>
3275
3276 <item>
3277 <title>First prototype ready making hardware easier to use in Debian</title>
3278 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3279 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3280 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3281 <description>&lt;p&gt;Early this month I set out to try to
3282 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3283 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3284 prototype is working, and it is ready for a larger audience. To test
3285 it, fetch the
3286 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3287 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3288 package. You might have to log out and in again activate the
3289 autostart script.&lt;/p&gt;
3290
3291 &lt;p&gt;The design is simple:&lt;/p&gt;
3292
3293 &lt;ul&gt;
3294
3295 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3296 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3297
3298 &lt;li&gt;This program listen for kernel events about new hardware (directly
3299 from the kernel like udev does), not using HAL dbus events as I
3300 initially did.&lt;/li&gt;
3301
3302 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3303 the APT database, a database
3304 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3305 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3306
3307 &lt;li&gt;If a package is mapped to the hardware in question, the package
3308 isn&#39;t installed yet and this is the first time the hardware was
3309 plugged in, show a desktop notification suggesting to install the
3310 package or packages.&lt;/li&gt;
3311
3312 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3313 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3314
3315 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3316 package while showing progress information in a window.&lt;/li&gt;
3317
3318 &lt;/ul&gt;
3319
3320 &lt;p&gt;I still need to come up with a better name for the system. Here
3321 are some screen shots showing the prototype in action. First the
3322 notification, then the password request, and finally the request to
3323 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3324
3325 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3326 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3327 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3328 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3329 &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;
3330
3331 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3332 is already useful. The database of hardware to package mappings also
3333 need more work. It is currently compatible with the Ubuntu way of
3334 storing such information in the package control file, but could be
3335 changed to use other formats instead or in addition to the current
3336 method. I&#39;ve dropped the use of discover for this mapping, as the
3337 modalias approach is more flexible and easier to use on Linux as long
3338 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3339
3340 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3341 here is the command required to check out and build the source: Use
3342 &#39;&lt;tt&gt;svn checkout
3343 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3344 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3345 devscripts package.&lt;/p&gt;
3346
3347 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3348 renamed to Isenkram and the source moved from the Debian Edu
3349 subversion repository to a Debian collab-maint git repository. See
3350 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3351 instructions&lt;/a&gt; for details.&lt;/p&gt;
3352 </description>
3353 </item>
3354
3355 <item>
3356 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3357 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3358 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3359 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3360 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3361 suddenly in bed. With a quiet whimper, it went completely quiet and
3362 black. The power button was no longer able to turn it on. It was a
3363 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3364 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3365 Compaq I had before that. Now I need to find a replacement. To keep
3366 going during Christmas, I moved the one year old SSD disk to my old
3367 X40 where it fitted (only one I had left that could use it), but it is
3368 not a durable solution.
3369
3370 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3371 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3372
3373 &lt;ul&gt;
3374
3375 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3376 than A4).&lt;/li&gt;
3377 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3378 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3379 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3380 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3381 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3382 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3383 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3384 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3385 size).&lt;/li&gt;
3386 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3387 X.org packages.&lt;/li&gt;
3388 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3389 the time).
3390
3391 &lt;/ul&gt;
3392
3393 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3394 list. The reason is simply that the specifications on laptops the
3395 last 10-15 years have been sufficient for my needs, and I have to look
3396 at other features to choose my laptop. But are there still made as
3397 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3398 robust, and Thinkpads seem to be heading in the wrong direction since
3399 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3400 still be useful.&lt;/p&gt;
3401
3402 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3403 external keyboard? I&#39;ll have to check the
3404 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3405 well-supported laptops, or perhaps just buy one preinstalled from one
3406 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3407 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3408 </description>
3409 </item>
3410
3411 <item>
3412 <title>How to find a browser plugin supporting a given MIME type</title>
3413 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3414 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3415 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3416 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3417 install to get support for a given MIME type. Thanks to
3418 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3419 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3420 Unfortunately, not very many packages provide the needed meta
3421 information, Anyway, here is a small script to look up all browser
3422 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3423
3424 &lt;pre&gt;
3425 #!/usr/bin/python
3426 import sys
3427 import apt
3428 def pkgs_handling_mimetype(mimetype):
3429 cache = apt.Cache()
3430 cache.open(None)
3431 thepkgs = []
3432 for pkg in cache:
3433 version = pkg.candidate
3434 if version is None:
3435 version = pkg.installed
3436 if version is None:
3437 continue
3438 record = version.record
3439 if not record.has_key(&#39;Npp-MimeType&#39;):
3440 continue
3441 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3442 for t in mime_types:
3443 t = t.rstrip().strip()
3444 if t == mimetype:
3445 thepkgs.append(pkg.name)
3446 return thepkgs
3447 mimetype = &quot;audio/ogg&quot;
3448 if 1 &lt; len(sys.argv):
3449 mimetype = sys.argv[1]
3450 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3451 for pkg in pkgs_handling_mimetype(mimetype):
3452 print &quot; %s&quot; %pkg
3453 &lt;/pre&gt;
3454
3455 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3456
3457 &lt;pre&gt;
3458 % ./apt-find-browserplug-for-mimetype
3459 Browser plugin packages supporting audio/ogg:
3460 gecko-mediaplayer
3461 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3462 Browser plugin packages supporting application/x-shockwave-flash:
3463 browser-plugin-gnash
3464 %
3465 &lt;/pre&gt;
3466
3467 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3468 itself to query for plugins and propose to install the needed
3469 packages. It would be great if Debian supported such feature too. Is
3470 anyone working on adding it?&lt;/p&gt;
3471
3472 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3473 request for icweasel support for this feature is
3474 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3475 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3476 of manpower and wish for a different design is the reason thus feature
3477 is not yet in iceweasel from Debian.&lt;/p&gt;
3478 </description>
3479 </item>
3480
3481 <item>
3482 <title>What is the most supported MIME type in Debian?</title>
3483 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3484 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3485 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3486 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3487 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3488 proposal to make it possible for a Desktop application to propose to
3489 the user some package to install to gain support for a given MIME
3490 type, font, library etc. that is currently missing. With such
3491 mechanism in place, it would be possible for the desktop to
3492 automatically propose and install leocad if some LDraw file is
3493 downloaded by the browser.&lt;/p&gt;
3494
3495 &lt;p&gt;To get some idea about the current content of the archive, I decided
3496 to write a simple program to extract all .desktop files from the
3497 Debian archive and look up the claimed MIME support there. The result
3498 can be found on the
3499 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3500 site&lt;/a&gt;. Using the collected information, it become possible to
3501 answer the question in the title. Here are the 20 most supported MIME
3502 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3503 The complete list is available from the link above.&lt;/p&gt;
3504
3505 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3506
3507 &lt;pre&gt;
3508 count MIME type
3509 ----- -----------------------
3510 32 text/plain
3511 30 audio/mpeg
3512 29 image/png
3513 28 image/jpeg
3514 27 application/ogg
3515 26 audio/x-mp3
3516 25 image/tiff
3517 25 image/gif
3518 22 image/bmp
3519 22 audio/x-wav
3520 20 audio/x-flac
3521 19 audio/x-mpegurl
3522 18 video/x-ms-asf
3523 18 audio/x-musepack
3524 18 audio/x-mpeg
3525 18 application/x-ogg
3526 17 video/mpeg
3527 17 audio/x-scpls
3528 17 audio/ogg
3529 16 video/x-ms-wmv
3530 &lt;/pre&gt;
3531
3532 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3533
3534 &lt;pre&gt;
3535 count MIME type
3536 ----- -----------------------
3537 33 text/plain
3538 32 image/png
3539 32 image/jpeg
3540 29 audio/mpeg
3541 27 image/gif
3542 26 image/tiff
3543 26 application/ogg
3544 25 audio/x-mp3
3545 22 image/bmp
3546 21 audio/x-wav
3547 19 audio/x-mpegurl
3548 19 audio/x-mpeg
3549 18 video/mpeg
3550 18 audio/x-scpls
3551 18 audio/x-flac
3552 18 application/x-ogg
3553 17 video/x-ms-asf
3554 17 text/html
3555 17 audio/x-musepack
3556 16 image/x-xbitmap
3557 &lt;/pre&gt;
3558
3559 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3560
3561 &lt;pre&gt;
3562 count MIME type
3563 ----- -----------------------
3564 31 text/plain
3565 31 image/png
3566 31 image/jpeg
3567 29 audio/mpeg
3568 28 application/ogg
3569 27 image/gif
3570 26 image/tiff
3571 26 audio/x-mp3
3572 23 audio/x-wav
3573 22 image/bmp
3574 21 audio/x-flac
3575 20 audio/x-mpegurl
3576 19 audio/x-mpeg
3577 18 video/x-ms-asf
3578 18 video/mpeg
3579 18 audio/x-scpls
3580 18 application/x-ogg
3581 17 audio/x-musepack
3582 16 video/x-ms-wmv
3583 16 video/x-msvideo
3584 &lt;/pre&gt;
3585
3586 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3587 information mentioned in DEP-11. I have not yet had time to look at
3588 it, but hope the PackageKit people in Debian are on top of these
3589 issues.&lt;/p&gt;
3590
3591 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3592 discovering a typo in my script.&lt;/p&gt;
3593 </description>
3594 </item>
3595
3596 <item>
3597 <title>Using modalias info to find packages handling my hardware</title>
3598 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3599 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3600 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3601 <description>&lt;p&gt;Yesterday, I wrote about the
3602 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3603 values provided by the Linux kernel&lt;/a&gt; following my hope for
3604 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3605 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3606 modalias values attached to package names can be used to map packages
3607 to hardware. This allow the system to look up and suggest relevant
3608 packages when I plug in some new hardware into my machine, and replace
3609 discover and discover-data as the database used to map hardware to
3610 packages.&lt;/p&gt;
3611
3612 &lt;p&gt;I create a modaliases file with entries like the following,
3613 containing package name, kernel module name (if relevant, otherwise
3614 the package name) and globs matching the relevant hardware
3615 modalias.&lt;/p&gt;
3616
3617 &lt;p&gt;&lt;blockquote&gt;
3618 Package: package-name
3619 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3620 &lt;/blockquote&gt;&lt;/p&gt;
3621
3622 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3623 for a given modalias value using this file.&lt;/p&gt;
3624
3625 &lt;p&gt;An entry like this would suggest the video and picture application
3626 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3627
3628 &lt;p&gt;&lt;blockquote&gt;
3629 Package: cheese
3630 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3631 &lt;/blockquote&gt;&lt;/p&gt;
3632
3633 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3634 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3635
3636 &lt;p&gt;&lt;blockquote&gt;
3637 Package: pcmciautils
3638 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3639 &lt;/blockquote&gt;&lt;/p&gt;
3640
3641 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3642 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3643
3644 &lt;p&gt;&lt;blockquote&gt;
3645 Package: colorhug-client
3646 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3647 &lt;/blockquote&gt;&lt;/p&gt;
3648
3649 &lt;p&gt;I believe the format is compatible with the format of the Packages
3650 file in the Debian archive. Ubuntu already uses their Packages file
3651 to store their mappings from packages to hardware.&lt;/p&gt;
3652
3653 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3654 announce the hardware it support in a way my prototype understand.
3655 This allow those publishing packages in an APT source outside the
3656 Debian archive as well as those backporting packages to make sure the
3657 hardware mapping are included in the package meta information. I&#39;ve
3658 tested such header in the pymissile package, and its modalias mapping
3659 is working as it should with my prototype. It even made it to Ubuntu
3660 Raring.&lt;/p&gt;
3661
3662 &lt;p&gt;To test if it was possible to look up supported hardware using only
3663 the shell tools available in the Debian installer, I wrote a shell
3664 implementation of the lookup code. The idea is to create files for
3665 each modalias and let the shell do the matching. Please check out and
3666 try the
3667 &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;
3668 shell script. It run without any extra dependencies and fetch the
3669 hardware mappings from the Debian archive and the subversion
3670 repository where I currently work on my prototype.&lt;/p&gt;
3671
3672 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3673 install yubikey-personalization:&lt;/p&gt;
3674
3675 &lt;p&gt;&lt;blockquote&gt;
3676 % ./hw-support-lookup
3677 &lt;br&gt;yubikey-personalization
3678 &lt;br&gt;%
3679 &lt;/blockquote&gt;&lt;/p&gt;
3680
3681 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3682 propose to install the pcmciautils package:&lt;/p&gt;
3683
3684 &lt;p&gt;&lt;blockquote&gt;
3685 % ./hw-support-lookup
3686 &lt;br&gt;pcmciautils
3687 &lt;br&gt;%
3688 &lt;/blockquote&gt;&lt;/p&gt;
3689
3690 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3691 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3692 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3693
3694 &lt;p&gt;It could be possible to generate several of the mappings between
3695 packages and hardware. One source would be to look at packages with
3696 kernel modules, ie packages with *.ko files in /lib/modules/, and
3697 extract their modalias information. Another would be to look at
3698 packages with udev rules, ie packages with files in
3699 /lib/udev/rules.d/, and extract their vendor/model information to
3700 generate a modalias matching rule. I have not tested any of these to
3701 see if it work.&lt;/p&gt;
3702
3703 &lt;p&gt;If you want to help implementing a system to let us propose what
3704 packages to install when new hardware is plugged into a Debian
3705 machine, please send me an email or talk to me on
3706 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3707 </description>
3708 </item>
3709
3710 <item>
3711 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3712 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3713 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3714 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3715 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3716 information, to find the packages that support a given piece of
3717 hardware, I refreshed my memory regarding modalias values, and decided
3718 to document the details. Here are my findings so far, also available
3719 in
3720 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3721 Debian Edu subversion repository&lt;/a&gt;:
3722
3723 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3724
3725 &lt;p&gt;This document try to explain what the different types of modalias
3726 values stands for. It is in part based on information from
3727 &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;,
3728 &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;,
3729 &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
3730 &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;.
3731
3732 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3733 this shell script:&lt;/p&gt;
3734
3735 &lt;pre&gt;
3736 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3737 &lt;/pre&gt;
3738
3739 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3740 using modinfo:&lt;/p&gt;
3741
3742 &lt;pre&gt;
3743 % /sbin/modinfo psmouse | grep alias:
3744 alias: serio:ty05pr*id*ex*
3745 alias: serio:ty01pr*id*ex*
3746 %
3747 &lt;/pre&gt;
3748
3749 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3750
3751 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3752 Bridge memory controller:&lt;/p&gt;
3753
3754 &lt;p&gt;&lt;blockquote&gt;
3755 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3756 &lt;/blockquote&gt;&lt;/p&gt;
3757
3758 &lt;p&gt;This represent these values:&lt;/p&gt;
3759
3760 &lt;pre&gt;
3761 v 00008086 (vendor)
3762 d 00002770 (device)
3763 sv 00001028 (subvendor)
3764 sd 000001AD (subdevice)
3765 bc 06 (bus class)
3766 sc 00 (bus subclass)
3767 i 00 (interface)
3768 &lt;/pre&gt;
3769
3770 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3771 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3772 0600. The 0600 class is a host bridge. Other useful bus values are
3773 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3774
3775 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3776 means.&lt;/p&gt;
3777
3778 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3779
3780 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3781 USB hub in a laptop:&lt;/p&gt;
3782
3783 &lt;p&gt;&lt;blockquote&gt;
3784 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3785 &lt;/blockquote&gt;&lt;/p&gt;
3786
3787 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3788
3789 &lt;pre&gt;
3790 v 1D6B (device vendor)
3791 p 0001 (device product)
3792 d 0206 (bcddevice)
3793 dc 09 (device class)
3794 dsc 00 (device subclass)
3795 dp 00 (device protocol)
3796 ic 09 (interface class)
3797 isc 00 (interface subclass)
3798 ip 00 (interface protocol)
3799 &lt;/pre&gt;
3800
3801 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3802 class is in the interface class section. For a simple USB web camera,
3803 these alias entries show up:&lt;/p&gt;
3804
3805 &lt;p&gt;&lt;blockquote&gt;
3806 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3807 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3808 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3809 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3810 &lt;/blockquote&gt;&lt;/p&gt;
3811
3812 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3813 camera), 0101 is audio control device and 0102 is audio streaming (aka
3814 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3815
3816 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3817
3818 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3819 receiver in a Thinkpad X40:&lt;/p&gt;
3820
3821 &lt;p&gt;&lt;blockquote&gt;
3822 acpi:IBM0071:PNP0511:
3823 &lt;/blockquote&gt;&lt;/p&gt;
3824
3825 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3826
3827 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3828
3829 &lt;p&gt;The DMI table contain lots of information about the computer case
3830 and model. This is an entry for a IBM Thinkpad X40, fetched from
3831 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3832
3833 &lt;p&gt;&lt;blockquote&gt;
3834 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3835 &lt;/blockquote&gt;&lt;/p&gt;
3836
3837 &lt;p&gt;The values present are&lt;/p&gt;
3838
3839 &lt;pre&gt;
3840 bvn IBM (BIOS vendor)
3841 bvr 1UETB6WW(1.66) (BIOS version)
3842 bd 06/15/2005 (BIOS date)
3843 svn IBM (system vendor)
3844 pn 2371H4G (product name)
3845 pvr ThinkPadX40 (product version)
3846 rvn IBM (board vendor)
3847 rn 2371H4G (board name)
3848 rvr NotAvailable (board version)
3849 cvn IBM (chassis vendor)
3850 ct 10 (chassis type)
3851 cvr NotAvailable (chassis version)
3852 &lt;/pre&gt;
3853
3854 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3855 found in the dmidecode source:&lt;/p&gt;
3856
3857 &lt;pre&gt;
3858 3 Desktop
3859 4 Low Profile Desktop
3860 5 Pizza Box
3861 6 Mini Tower
3862 7 Tower
3863 8 Portable
3864 9 Laptop
3865 10 Notebook
3866 11 Hand Held
3867 12 Docking Station
3868 13 All In One
3869 14 Sub Notebook
3870 15 Space-saving
3871 16 Lunch Box
3872 17 Main Server Chassis
3873 18 Expansion Chassis
3874 19 Sub Chassis
3875 20 Bus Expansion Chassis
3876 21 Peripheral Chassis
3877 22 RAID Chassis
3878 23 Rack Mount Chassis
3879 24 Sealed-case PC
3880 25 Multi-system
3881 26 CompactPCI
3882 27 AdvancedTCA
3883 28 Blade
3884 29 Blade Enclosing
3885 &lt;/pre&gt;
3886
3887 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3888 table. For example my home server is a tower, but the DMI modalias
3889 claim it is a desktop.&lt;/p&gt;
3890
3891 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3892
3893 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3894 test machine:&lt;/p&gt;
3895
3896 &lt;p&gt;&lt;blockquote&gt;
3897 serio:ty01pr00id00ex00
3898 &lt;/blockquote&gt;&lt;/p&gt;
3899
3900 &lt;p&gt;The values present are&lt;/p&gt;
3901
3902 &lt;pre&gt;
3903 ty 01 (type)
3904 pr 00 (prototype)
3905 id 00 (id)
3906 ex 00 (extra)
3907 &lt;/pre&gt;
3908
3909 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3910 the valid values are.&lt;/p&gt;
3911
3912 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3913
3914 &lt;p&gt;There are heaps of other modalias subtypes according to
3915 file2alias.c. There is the rest of the list from that source: amba,
3916 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3917 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3918 vmbus, x86cpu and zorro. I did not spend time documenting all of
3919 these, as they do not seem relevant for my intended use with mapping
3920 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3921
3922 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3923
3924 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3925 one can use the following shell script:&lt;/p&gt;
3926
3927 &lt;pre&gt;
3928 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3929 echo &quot;$id&quot; ; \
3930 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3931 done
3932 &lt;/pre&gt;
3933
3934 &lt;p&gt;The output can look like this (only the first few entries as the
3935 list is very long on my test machine):&lt;/p&gt;
3936
3937 &lt;pre&gt;
3938 acpi:ACPI0003:
3939 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3940 acpi:device:
3941 FATAL: Module acpi:device: not found.
3942 acpi:IBM0068:
3943 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3944 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3945 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3946 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3947 acpi:IBM0071:PNP0511:
3948 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3949 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3950 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3951 [...]
3952 &lt;/pre&gt;
3953
3954 &lt;p&gt;If you want to help implementing a system to let us propose what
3955 packages to install when new hardware is plugged into a Debian
3956 machine, please send me an email or talk to me on
3957 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3958
3959 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3960 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3961 in /sys/ with space in them.&lt;/p&gt;
3962 </description>
3963 </item>
3964
3965 <item>
3966 <title>Moved the pymissile Debian packaging to collab-maint</title>
3967 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3969 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3970 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3971 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3972 Launcher and updated the Debian package
3973 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3974 sure udev will fix the device permissions when it is plugged in. I
3975 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3976 hopefully make the package be proposed by jockey in Ubuntu when a user
3977 plug in his rocket launcher. In the process I moved the source to a
3978 git repository under collab-maint, to make it easier for any DD to
3979 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3980 is not very active, but the software still work for me even after five
3981 years of relative silence. The new git repository is not listed in
3982 the uploaded package yet, because I want to test the other changes a
3983 bit more before I upload the new version. If you want to check out
3984 the new version with a .desktop file included, visit the
3985 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3986 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3987 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3988 </description>
3989 </item>
3990
3991 <item>
3992 <title>Lets make hardware dongles easier to use in Debian</title>
3993 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3994 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3995 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3996 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3997 general, is that there is a great package management system with the
3998 ability to automatically install software packages by downloading them
3999 from the distribution mirrors, but no way to get it to automatically
4000 install the packages I need to use the hardware I plug into my
4001 machine. Even if the package to use it is easily available from the
4002 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4003 suggest to automatically install the python-nxt, nbc and t2n packages
4004 I need to talk to it. When I plug in a Yubikey, it could propose the
4005 yubikey-personalization package. The information required to do this
4006 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4007
4008 &lt;p&gt;Some years ago, I proposed to
4009 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4010 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4011 simple:
4012
4013 &lt;ul&gt;
4014
4015 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4016 starting when a user log in.&lt;/li&gt;
4017
4018 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4019 hardware is inserted into the computer.&lt;/li&gt;
4020
4021 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4022 database mapping to packages, and take note of any non-installed
4023 packages.&lt;/li&gt;
4024
4025 &lt;li&gt;Show a message to the user proposing to install the discovered
4026 package, and make it easy to install it.&lt;/li&gt;
4027
4028 &lt;/ul&gt;
4029
4030 &lt;p&gt;I am not sure what the best way to implement this is, but my
4031 initial idea was to use dbus events to discover new hardware, the
4032 discover database to find packages and
4033 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4034 packages.&lt;/p&gt;
4035
4036 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4037 draft package is now checked into
4038 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4039 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4040 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4041 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4042 the relevant packages in Debian, and uploaded a new version
4043 2.2013.01.09 to unstable. I also discovered that the current
4044 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4045 package in Debian no longer discovered any USB devices, because
4046 /proc/bus/usb/devices is no longer present. I ported it to use
4047 libusb as a fall back option to get it working. The fixed package
4048 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4049 because of the freeze).&lt;/p&gt;
4050
4051 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4052 desktop notification to show up (only once, the first time it is
4053 inserted):&lt;/p&gt;
4054
4055 &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;
4056
4057 &lt;p&gt;For this prototype to be really useful, some way to automatically
4058 install the proposed packages by pressing the &quot;Please install
4059 program(s)&quot; button should to be implemented.&lt;/p&gt;
4060
4061 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4062 happen, please help me update the discover-data database with mappings
4063 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4064 list the package you would like to have installed when a given
4065 hardware device is inserted into your computer, and report bugs using
4066 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4067 such mapping, please let me know.&lt;/p&gt;
4068
4069 &lt;p&gt;This prototype need more work, and there are several questions that
4070 should be considered before it is ready for production use. Is dbus
4071 the correct way to detect new hardware? At the moment I look for HAL
4072 dbus events on the system bus, because that is the events I could see
4073 on my Debian Squeeze KDE desktop. Are there better events to use?
4074 How should the user be notified? Is the desktop notification
4075 mechanism the best option, or should the background daemon raise a
4076 popup instead? How should packages be installed? When should they
4077 not be installed?&lt;/p&gt;
4078
4079 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4080 please send me an email. :)&lt;/p&gt;
4081 </description>
4082 </item>
4083
4084 <item>
4085 <title>New IRC channel for LEGO designers using Debian</title>
4086 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4087 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4088 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4089 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4090 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4091 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4092 discovered I had to build all the tools myself because none were
4093 already in Debian Squeeze. If Debian support for LEGO is something
4094 you care about, please join me on the IRC channel
4095 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4096 irc.debian.org). There is a lot that could be done to improve the
4097 Debian support for LEGO designers. For example both CAD software
4098 and Mindstorm compilers are missing. :)&lt;/p&gt;
4099
4100 &lt;p&gt;Update 2012-01-03: A
4101 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4102 including links to Lego related packages is now available.&lt;/p&gt;
4103 </description>
4104 </item>
4105
4106 <item>
4107 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4108 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4110 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4111 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4112 year! I hope next year will prove to be a good year.&lt;/p&gt;
4113
4114 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4115 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4116 between each other with minimal overhead, is a very interesting
4117 experiment. And as I wrote a few days ago, the bitcoin situation in
4118 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4119 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4120 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4121 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4122 for one of the ftpmasters to approve the new bitcoin-qt package
4123 name.&lt;/p&gt;
4124
4125 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4126 team in Debian, you can easily test the package in Debian Squeeze
4127 using the following steps to get a set of working packages:&lt;/p&gt;
4128
4129 &lt;blockquote&gt;&lt;pre&gt;
4130 git clone git://git.debian.org/git/collab-maint/bitcoin
4131 cd bitcoin
4132 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4133 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4134 &lt;/pre&gt;&lt;/blockquote&gt;
4135
4136 &lt;p&gt;You might have to install some build dependencies as well. The
4137 list of commands should give you two packages, bitcoind and
4138 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4139 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4140 around 5.6 GiB of data on my machine at the moment. Make sure your
4141 ~/.bitcoin/ directory have lots of spare room if you want to download
4142 all the blocks. The client will warn if the disk is getting full, so
4143 there is not really a problem if you got too little room, but you will
4144 not be able to get all the features out of the client.&lt;/p&gt;
4145
4146 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4147 activities, please send Bitcoin donations to my address
4148 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4149 </description>
4150 </item>
4151
4152 <item>
4153 <title>A word on bitcoin support in Debian</title>
4154 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4155 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4156 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4157 <description>&lt;p&gt;It has been a while since I wrote about
4158 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4159 peer-to-peer based crypto-currency, and the reason is simply that I
4160 have been busy elsewhere. But two days ago, I started looking at the
4161 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4162 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4163 is now maintained by a
4164 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4165 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4166 owe a huge thank you to all these team members. :)
4167 But I was sad to discover that the bitcoin client is missing in
4168 Wheezy. It is only available in Sid (and an outdated client from
4169 backports). The client had several RC bugs registered in BTS blocking
4170 it from entering testing. To try to help the team and improve the
4171 situation, I spent some time providing patches and triaging the bug
4172 reports. I also had a look at the bitcoin package available from Matt
4173 Corallo in a
4174 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4175 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4176 Debian package.&lt;/p&gt;
4177
4178 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4179 IRC, I pushed several patches into the collab-maint git repository to
4180 improve the package. It now contains fixes for the RC issues (not from
4181 me, but fixed by Scott Howard), build rules for a Qt GUI client
4182 package, konqueror support for the bitcoin: URI and bash completion
4183 setup. As I work on Debian Squeeze, I also created
4184 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4185 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4186 it and try to integrate it into the git repository before uploading a
4187 new version to unstable.
4188
4189 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4190 centralized control currently exercised in the monetary system. I
4191 find it completely unacceptable that the USA government is collecting
4192 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4193 that the major credit card companies can block legal money
4194 transactions to Wikileaks. But for bitcoin to succeed, more people
4195 need to use bitcoins, and more people need to accept bitcoins when
4196 they sell products and services. Improving the bitcoin support in
4197 Debian is a small step in the right direction, but not enough.
4198 Unfortunately the user experience when browsing the web and wanting to
4199 pay with bitcoin is still not very good. The bitcoin: URI is a step
4200 in the right direction, but need to work in most or every browser in
4201 use. Also the bitcoin-qt client is too heavy to fire up to do a
4202 quick transaction. I believe there are other clients available, but
4203 have not tested them.&lt;/p&gt;
4204
4205 &lt;p&gt;My
4206 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4207 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4208 I received 20.15 BTC so far on the address I provided in my blog two
4209 years ago, as can be
4210 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4211 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4212 donation. The blockexplorer service demonstrates quite well that
4213 bitcoin is not quite anonymous and untracked. :) I wonder if the
4214 number of users have gone up since then. If you use bitcoin and want
4215 to show your support of my activity, please send Bitcoin donations to
4216 the same address as last time,
4217 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4218 </description>
4219 </item>
4220
4221 <item>
4222 <title>Git repository for song book for Computer Scientists</title>
4223 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4224 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4225 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4226 <description>&lt;p&gt;As I
4227 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4228 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4229 years ago, and today I finally found time to create a public
4230 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4231 repository for the project&lt;/a&gt;.&lt;/p&gt;
4232
4233 &lt;p&gt;If you want to help out, please clone the source and submit patches
4234 to the HTML version. To generate the PDF and PostScript version,
4235 please use prince XML, or let me know about a useful free software
4236 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4237
4238 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4239 PostScript formats at
4240 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4241 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4242 </description>
4243 </item>
4244
4245 <item>
4246 <title>Gratulerer med 19-årsdagen, Debian!</title>
4247 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4248 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4249 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4250 <description>&lt;p&gt;I dag fyller
4251 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4252 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4253 si gratulerer med dagen, Debian!&lt;/p&gt;
4254 </description>
4255 </item>
4256
4257 <item>
4258 <title>Song book for Computer Scientists</title>
4259 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4260 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4261 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4262 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4263 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4264 collecting computer related songs for use at parties. The original
4265 version was written in LaTeX, but a few years ago I got help from
4266 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4267 while keeping the ability to create a nice book in PDF format. I have
4268 not had time to maintain the book for a while now, and guess I should
4269 put it up on some public version control repository where others can
4270 help me extend and update the book. If anyone is volunteering to help
4271 me with this, send me an email. Also let me know if there are songs
4272 missing in my book.&lt;/p&gt;
4273
4274 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4275 me today that I really should let all my readers share the joys of
4276 singing out load about programming, computers and computer networks.
4277 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4278 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4279 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4280 Computer Science Songbook&lt;/a&gt;.
4281 </description>
4282 </item>
4283
4284 <item>
4285 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4286 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4287 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4288 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4289 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4290 around 1000 at the moment. To be able to get help from the vendors
4291 when something go wrong, we want to keep the firmware on the servers
4292 up to date. If the firmware isn&#39;t the latest and greatest, the
4293 vendors typically refuse to start debugging any problems until the
4294 firmware is upgraded. So before every reboot, we want to upgrade the
4295 firmware, and we would really like everyone handling servers at the
4296 university to do this themselves when they plan to reboot a machine.
4297 For that to happen we at the unix server admin group need to provide
4298 the tools to do so.&lt;/p&gt;
4299
4300 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4301 fetch and install the latest firmware for the servers we got. Most of
4302 our hardware are from Dell and HP, so I have focused on these servers
4303 so far. This blog post is about the Dell part.&lt;/P&gt;
4304
4305 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4306 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4307 with firmware information for all 11th generation servers, listing
4308 which firmware should be used on a given model and where on the FTP
4309 site I can find it. Using a simple perl XML parser I can then
4310 download the shell scripts Dell provides to do firmware upgrades from
4311 within Linux and reboot when all the firmware is primed and ready to
4312 be activated on the first reboot.&lt;/p&gt;
4313
4314 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4315 Are there anyone working on similar tools for firmware upgrading all
4316 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4317
4318 &lt;p&gt;&lt;pre&gt;
4319 #!/usr/bin/perl
4320 use strict;
4321 use warnings;
4322 use File::Temp qw(tempdir);
4323 BEGIN {
4324 # Install needed RHEL packages if missing
4325 my %rhelmodules = (
4326 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4327 );
4328 for my $module (keys %rhelmodules) {
4329 eval &quot;use $module;&quot;;
4330 if ($@) {
4331 my $pkg = $rhelmodules{$module};
4332 system(&quot;yum install -y $pkg&quot;);
4333 eval &quot;use $module;&quot;;
4334 }
4335 }
4336 }
4337 my $errorsto = &#39;pere@hungry.com&#39;;
4338
4339 upgrade_dell();
4340
4341 exit 0;
4342
4343 sub run_firmware_script {
4344 my ($opts, $script) = @_;
4345 unless ($script) {
4346 print STDERR &quot;fail: missing script name\n&quot;;
4347 exit 1
4348 }
4349 print STDERR &quot;Running $script\n\n&quot;;
4350
4351 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4352 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4353 } else {
4354 print STDERR &quot;fail: firmware script returned error\n&quot;;
4355 }
4356 }
4357
4358 sub run_firmware_scripts {
4359 my ($opts, @dirs) = @_;
4360 # Run firmware packages
4361 for my $dir (@dirs) {
4362 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4363 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4364 while (my $s = readdir $dh) {
4365 next if $s =~ m/^\.\.?/;
4366 run_firmware_script($opts, &quot;$dir/$s&quot;);
4367 }
4368 closedir $dh;
4369 }
4370 }
4371
4372 sub download {
4373 my $url = shift;
4374 print STDERR &quot;info: Downloading $url\n&quot;;
4375 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4376 }
4377
4378 sub upgrade_dell {
4379 my @dirs;
4380 my $product = `dmidecode -s system-product-name`;
4381 chomp $product;
4382
4383 if ($product =~ m/PowerEdge/) {
4384
4385 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4386 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4387
4388 my $tmpdir = tempdir(
4389 CLEANUP =&gt; 1
4390 );
4391 chdir($tmpdir);
4392 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4393 system(&#39;gunzip Catalog.xml.gz&#39;);
4394 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4395 # -q is quiet, disabling interactivity and reducing console output
4396 my $fwopts = &quot;-q&quot;;
4397 if (@paths) {
4398 for my $url (@paths) {
4399 fetch_dell_fw($url);
4400 }
4401 run_firmware_scripts($fwopts, $tmpdir);
4402 } else {
4403 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4404 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4405 }
4406 chdir(&#39;/&#39;);
4407 } else {
4408 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4409 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4410 }
4411 }
4412
4413 sub fetch_dell_fw {
4414 my $path = shift;
4415 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4416 download($url);
4417 }
4418
4419 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4420 # firmware packages to download from Dell. Only work for Linux
4421 # machines and 11th generation Dell servers.
4422 sub fetch_dell_fw_list {
4423 my $filename = shift;
4424
4425 my $product = `dmidecode -s system-product-name`;
4426 chomp $product;
4427 my ($mybrand, $mymodel) = split(/\s+/, $product);
4428
4429 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4430
4431 my $xml = XMLin($filename);
4432 my @paths;
4433 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4434 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4435 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4436 my $oscode;
4437 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4438 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4439 } else {
4440 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4441 }
4442 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4443 {
4444 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4445 }
4446 }
4447 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4448 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4449
4450 # Drop application packages, only firmware and BIOS
4451 next if &#39;APAC&#39; eq $componenttype;
4452
4453 my $cpath = $component-&gt;{path};
4454 for my $path (@paths) {
4455 if ($cpath =~ m%/$path$%) {
4456 push(@paths, $cpath);
4457 }
4458 }
4459 }
4460 return @paths;
4461 }
4462 &lt;/pre&gt;
4463
4464 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4465 it could work on other platforms with some tweaking. Anyone know a
4466 index like Catalog.xml is available from HP for HP servers? At the
4467 moment I maintain a similar list manually and it is quickly getting
4468 outdated.&lt;/p&gt;
4469 </description>
4470 </item>
4471
4472 <item>
4473 <title>How is booting into runlevel 1 different from single user boots?</title>
4474 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4475 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4476 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4477 <description>&lt;p&gt;Wouter Verhelst have some
4478 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4479 comments and opinions&lt;/a&gt; on my blog post on
4480 &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
4481 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4482 &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
4483 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4484 small piece of his comment now, and though it best to address the
4485 misunderstanding he bring forward:&lt;/p&gt;
4486
4487 &lt;p&gt;&lt;blockquote&gt;
4488 Currently, a system admin has four options: [...] boot to a
4489 single-user system (by adding &#39;single&#39; to the kernel command line;
4490 this runs rcS and rc1 scripts)
4491 &lt;/blockquote&gt;&lt;/p&gt;
4492
4493 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4494 and booting into runlevel 1 is the same. I am not surprised he
4495 believe this, because it would make sense and is a quite sensible
4496 thing to believe. But because the boot in Debian is slightly broken,
4497 runlevel 1 do not work properly and it isn&#39;t the same as single user
4498 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4499 hard to explain.&lt;/p&gt;
4500
4501 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4502 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4503 executed in single user mode is sulogin. Single user mode is a boot
4504 state &quot;between&quot; the runlevels, and when booting into single user mode,
4505 only the scripts in /etc/rcS.d/ are executed before the init process
4506 enters the single user state. When switching to runlevel 1, the state
4507 is in fact not ending in runlevel 1, but it passes through runlevel 1
4508 and end up in the single user mode (see /etc/rc1.d/S03single, which
4509 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4510 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4511 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4512 mode).&lt;/p&gt;
4513
4514 &lt;p&gt;This summary might make it clearer. When booting for the first
4515 time into single user mode, the following commands are executed:
4516 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4517 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4518 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4519 trying to continue after visiting single user mode. Not all services
4520 are started again as they should, causing the machine to end up in an
4521 unpredicatble state. This is why Debian admins recommend rebooting
4522 after visiting single user mode.&lt;/p&gt;
4523
4524 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4525 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4526 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4527 stopped when passing through the scripts in /etc/rc1.d/, and not
4528 started again when switching away from runlevel 1 to the runlevels
4529 2-5. I believe the problem is best fixed by moving all the scripts
4530 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4531 functioning single user mode during boot.&lt;/p&gt;
4532
4533 &lt;p&gt;I have spent several years investigating the Debian boot system,
4534 and discovered this problem a few years ago. I suspect it originates
4535 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4536 </description>
4537 </item>
4538
4539 <item>
4540 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4541 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4542 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4543 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4544 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4545 are started from /etc/rcS.d/. In fact, there is a bite more of them
4546 than make sense, and this causes a few problems. What kind of
4547 problems, you might ask. There are at least two problems. The first
4548 is that it is not possible to recover a machine after switching to
4549 runlevel 1. One need to actually reboot to get the machine back to
4550 the expected state. The other is that single user boot will sometimes
4551 run into problems because some of the subsystems are activated before
4552 the root login is presented, causing problems when trying to recover a
4553 machine from a problem in that subsystem. A minor additional point is
4554 that moving more scripts out of rcS.d/ and into the other rc#.d/
4555 directories will increase the amount of scripts that can run in
4556 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4557
4558 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4559 scripts that _have_ to execute before the root login prompt is
4560 presented during a single user boot should go there. Everything else
4561 should go into the numeric runlevels. This means things like
4562 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4563 the numeric runlevels. Today in Debian, there are around 115 init.d
4564 scripts that are started from rcS.d/, and most of them should be moved
4565 out. Do your package have one of them? Please help us make single
4566 user and runlevel 1 better by moving it.&lt;/p&gt;
4567
4568 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4569 etc. should still be started from rcS.d/, but there is for example no
4570 need to have the network enabled before the single user login prompt
4571 is presented.&lt;/p&gt;
4572
4573 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4574 Debian systems working while scripts migrate and during upgrades, the
4575 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4576 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4577 and the next ones can only be moved when their dependencies have been
4578 moved first. This migration must be done sequentially while we ensure
4579 that the package system upgrade packages in the right order to keep
4580 the system state correct. This will require some coordination when it
4581 comes to network related packages, but most of the packages with
4582 scripts that should migrate do not have anything in rcS.d/ depending
4583 on them. Some packages have already been updated, like the sudo
4584 package, while others are still left to do. I wish I had time to work
4585 on this myself, but real live constrains make it unlikely that I will
4586 find time to push this forward.&lt;/p&gt;
4587 </description>
4588 </item>
4589
4590 <item>
4591 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4592 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4593 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4594 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4595 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4596 mentioned the issues I believe should be improved in Debian for its
4597 desktop to be useful for more people. The use case for this is my
4598 parents, which are currently running Kubuntu which solve the
4599 issues.&lt;/p&gt;
4600
4601 &lt;p&gt;I suspect these four missing features are not very hard to
4602 implement. After all, they are present in Ubuntu, so if we wanted to
4603 do this in Debian we would have a source.&lt;/p&gt;
4604
4605 &lt;ol&gt;
4606
4607 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4608 are new packages available for upgrades, a icon in the KDE status bar
4609 indicate this, and clicking on it will activate the simple upgrade
4610 tool to handle it. I have no problem guiding both of my parents
4611 through the process over the phone. If a kernel reboot is required,
4612 this too is indicated by the status bars and the upgrade tool. Last
4613 time I checked, nothing with the same features was working in KDE in
4614 Debian.&lt;/li&gt;
4615
4616 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4617 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4618 currently have a handler for, it will ask the user if the system
4619 should search for a package that would add support for this MIME type,
4620 and if the user say yes, the APT sources will be searched for packages
4621 advertising the MIME type in their control file (visible in the
4622 Packages file in the APT archive). If one or more packages are found,
4623 it is a simple click of the mouse to add support for the missing mime
4624 type. If the package require the user to accept some non-free
4625 license, this is explained to the user. The entire process make it
4626 more clear to the user why something do not work in the browser, and
4627 make the chances higher for the user to blame the web page authors and
4628 not the browser for any missing features.&lt;/li&gt;
4629
4630 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4631 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4632 it is not supporting, a dialog pop up asking the user if the system
4633 should search for a package that would add support for it. This
4634 happen with things like MP3, Windows Media or H.264. The selection
4635 and installation procedure is very similar to the Firefox browser
4636 plugin handling. This is as far as I know implemented using a
4637 gstreamer hook. The end result is that the user easily get access to
4638 the codecs that are present from the APT archives available, while
4639 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4640
4641 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4642 displaying a text/plain file in my Debian browser, it will propose to
4643 start emacs to show it. If I remember correctly, when doing the same
4644 in Kunbutu it show the file as a text file in the browser. At least I
4645 know Opera will show text files within the browser. I much prefer the
4646 latter behaviour.&lt;/li&gt;
4647
4648 &lt;/ol&gt;
4649
4650 &lt;p&gt;There are other nice features as well, like the simplified suite
4651 upgrader, but given that I am the one mostly doing the dist-upgrade,
4652 it do not matter much.&lt;/p&gt;
4653
4654 &lt;p&gt;I really hope we could get these features in place for the next
4655 Debian release. It would require the coordinated effort of several
4656 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4657 </description>
4658 </item>
4659
4660 <item>
4661 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4662 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4663 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4664 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4665 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4666 site is build on Debian/Squeeze, and this platform was chosen because
4667 I am most familiar with Debian (being a Debian Developer for around 10
4668 years) because it is the latest stable Debian release which should get
4669 security support for a few years.&lt;/p&gt;
4670
4671 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4672 that are missing in Debian at the moment. It would be great if these
4673 modules were added to the Debian archive, allowing anyone to set up
4674 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4675 in their own country using only Debian packages. The list of modules
4676 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4677 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4678 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4679 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4680 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4681 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4682 easier in the future.&lt;/p&gt;
4683
4684 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4685 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4686 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4687 with the responsibility of tracking security problems, which I really
4688 do not have time for.&lt;/p&gt;
4689 </description>
4690 </item>
4691
4692 <item>
4693 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4694 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4695 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4696 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4697 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4698 posts have been in Norwegian the last few weeks, so here is a short
4699 update in English.&lt;/p&gt;
4700
4701 &lt;p&gt;The kids still keep me too busy to get much free software work
4702 done, but I did manage to organise a project to get a Norwegian port
4703 of the British service
4704 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4705 and it has been running for a month now. The entire project has been
4706 organised by me and two others. Around Christmas we gathered sponsors
4707 to fund the development work. In January I drafted a contract with
4708 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4709 and in February the development took place. Most of it involved
4710 converting the source to use GPS coordinates instead of British
4711 easting/northing, and the resulting code should be a lot easier to get
4712 running in any country by now. The Norwegian
4713 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4714 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4715 source and the source for administrative borders in Norway, and
4716 support for this had to be added/fixed.&lt;/p&gt;
4717
4718 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4719 polishing the system before we announced it March 7th. The system is
4720 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4721 problem reports in a few weeks. Soon we hope to announce the Android
4722 and iPhone versions making it even easier to report problems with the
4723 public infrastructure.&lt;/p&gt;
4724
4725 &lt;p&gt;Perhaps something to consider for those of you in countries without
4726 such service?&lt;/p&gt;
4727 </description>
4728 </item>
4729
4730 <item>
4731 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4732 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4733 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4734 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4735 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4736 issues here at my work with the University of Oslo. My idea is that
4737 it should be possible to use the information about security issues
4738 available on the Internet, and check our locally
4739 maintained/distributed software against this information. It should
4740 allow us to verify that no known security issues are forgotten. The
4741 CVE database listing vulnerabilities seem like a great central point,
4742 and by using the package lists from Debian mapped to CVEs provided by
4743 the testing security team, I believed it should be possible to figure
4744 out which security holes were present in our free software
4745 collection.&lt;/p&gt;
4746
4747 &lt;p&gt;After reading up on the topic, it became obvious that the first
4748 building block is to be able to name software packages in a unique and
4749 consistent way across data sources. I considered several ways to do
4750 this, for example coming up with my own naming scheme like using URLs
4751 to project home pages or URLs to the Freshmeat entries, or using some
4752 existing naming scheme. And it seem like I am not the first one to
4753 come across this problem, as MITRE already proposed and implemented a
4754 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4755 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4756 software, hardware and other platform components. The CPE ids are
4757 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4758 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4759 issues for any CPE name. With this in place, all I need to do is to
4760 locate the CPE id for the software packages we use at the university.
4761 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4762 NVD entry if a CVE for the package exist).&lt;/p&gt;
4763
4764 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4765 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4766 check out, one could look up
4767 &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
4768 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4769 The most recent one is
4770 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4771 and at the bottom of the NVD page for this vulnerability the complete
4772 list of affected versions is provided.&lt;/p&gt;
4773
4774 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4775 for offline processing of issues. Using this dump, I&#39;ve written a
4776 small script taking a list of CPEs as input and list all CVEs
4777 affecting the packages represented by these CPEs. One give it CPEs
4778 with version numbers as specified above and get a list of open
4779 security issues out.&lt;/p&gt;
4780
4781 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4782 information need to be high. For that to happen, I believe as many as
4783 possible need to use and contribute to the NVD database. I notice
4784 RHEL is providing
4785 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4786 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4787 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4788
4789 &lt;p&gt;To get an idea about the quality for free software, I spent some
4790 time making it possible to compare the CVE database from Debian with
4791 the CVE database in NVD. The result look fairly good, but there are
4792 some inconsistencies in NVD (same software package having several
4793 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4794 Debian believe are affected by a CVE). Hope to find time to improve
4795 the quality of NVD, but that require being able to get in touch with
4796 someone maintaining it. So far my three emails with questions and
4797 corrections have not seen any reply, but I hope contact can be
4798 established soon.&lt;/p&gt;
4799
4800 &lt;p&gt;An interesting application for CPEs is cross platform package
4801 mapping. It would be useful to know which packages in for example
4802 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4803 this would be trivial if all linux distributions provided CPE entries
4804 for their packages.&lt;/p&gt;
4805 </description>
4806 </item>
4807
4808 <item>
4809 <title>Which module is loaded for a given PCI and USB device?</title>
4810 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4812 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4813 <description>&lt;p&gt;In the
4814 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4815 package in Debian, there is a script to report useful information
4816 about the running hardware for use when people report missing
4817 information. One part of this script that I find very useful when
4818 debugging hardware problems, is the part mapping loaded kernel module
4819 to the PCI device it claims. It allow me to quickly see if the kernel
4820 module I expect is driving the hardware I am struggling with. To see
4821 the output, make sure discover-data is installed and run
4822 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4823 one of my machines like this:&lt;/p&gt;
4824
4825 &lt;pre&gt;
4826 loaded modules:
4827 10de:03eb i2c_nforce2
4828 10de:03f1 ohci_hcd
4829 10de:03f2 ehci_hcd
4830 10de:03f0 snd_hda_intel
4831 10de:03ec pata_amd
4832 10de:03f6 sata_nv
4833 1022:1103 k8temp
4834 109e:036e bttv
4835 109e:0878 snd_bt87x
4836 11ab:4364 sky2
4837 &lt;/pre&gt;
4838
4839 &lt;p&gt;The code in question look like this, slightly modified for
4840 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4841
4842 &lt;pre&gt;
4843 if [ -d /sys/bus/pci/devices/ ] ; then
4844 echo loaded pci modules:
4845 (
4846 cd /sys/bus/pci/devices/
4847 for address in * ; do
4848 if [ -d &quot;$address/driver/module&quot; ] ; then
4849 module=`cd $address/driver/module ; pwd -P | xargs basename`
4850 if grep -q &quot;^$module &quot; /proc/modules ; then
4851 address=$(echo $address |sed s/0000://)
4852 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4853 echo &quot;$id $module&quot;
4854 fi
4855 fi
4856 done
4857 )
4858 echo
4859 fi
4860 &lt;/pre&gt;
4861
4862 &lt;p&gt;Similar code could be used to extract USB device module
4863 mappings:&lt;/p&gt;
4864
4865 &lt;pre&gt;
4866 if [ -d /sys/bus/usb/devices/ ] ; then
4867 echo loaded usb modules:
4868 (
4869 cd /sys/bus/usb/devices/
4870 for address in * ; do
4871 if [ -d &quot;$address/driver/module&quot; ] ; then
4872 module=`cd $address/driver/module ; pwd -P | xargs basename`
4873 if grep -q &quot;^$module &quot; /proc/modules ; then
4874 address=$(echo $address |sed s/0000://)
4875 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4876 if [ &quot;$id&quot; ] ; then
4877 echo &quot;$id $module&quot;
4878 fi
4879 fi
4880 fi
4881 done
4882 )
4883 echo
4884 fi
4885 &lt;/pre&gt;
4886
4887 &lt;p&gt;This might perhaps be something to include in other tools as
4888 well.&lt;/p&gt;
4889 </description>
4890 </item>
4891
4892 <item>
4893 <title>How to test if a laptop is working with Linux</title>
4894 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4895 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4896 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4897 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4898 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4899 batch of computers will work with Linux. Every year for the last few
4900 years the university have organised shared bid of a few thousand
4901 computers, and this year HP won the bid. Two different desktops and
4902 five different laptops are on the list this year. We in the UNIX
4903 group want to know which one of these computers work well with RHEL
4904 and Ubuntu, the two Linux distributions we currently handle at the
4905 university.&lt;/p&gt;
4906
4907 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4908 perhaps inspire others to test hardware as well. To test, I PXE
4909 install the OS version of choice, and log in as my normal user and run
4910 a few applications and plug in selected pieces of hardware. When
4911 something fail, I make a note about this in the test matrix and move
4912 on. If I have some spare time I try to report the bug to the OS
4913 vendor, but as I only have the machines for a short time, I rarely
4914 have the time to do this for all the problems I find.&lt;/p&gt;
4915
4916 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4917 I perform on a new model.&lt;/p&gt;
4918
4919 &lt;ul&gt;
4920
4921 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4922 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4923 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4924
4925 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4926 installation, X.org is working.&lt;/li&gt;
4927
4928 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4929 package mesa-utils on Ubuntu) and writing down the frames per second
4930 reported by the program.&lt;/li&gt;
4931
4932 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4933 logging in, and if I can hear this the test is successful. If there
4934 are several audio exits on the machine, I try them all and check if
4935 the Gnome/KDE audio mixer can control where to send the sound. I
4936 normally test this by playing
4937 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4938 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4939
4940 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4941 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4942
4943 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4944 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4945
4946 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4947 picture from the v4l device show up.&lt;/li&gt;
4948
4949 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4950 any bluetooth devices are discovered. In my office, I normally see a
4951 few.&lt;/li&gt;
4952
4953 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4954 memory modules lying around, and stick them in and see if Gnome/KDE
4955 notice this.&lt;/li&gt;
4956
4957 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4958 special button work, and if the laptop continue to work after
4959 resume.&lt;/li&gt;
4960
4961 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4962 adjusting background light, switching on/off external video output,
4963 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4964 laptop to laptop, so I just write down which are working and which are
4965 not.&lt;/li&gt;
4966
4967 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4968 acceleration sensors etc. I rarely test these, as I do not know how
4969 to quickly test if they are working or not, so I only document their
4970 existence.&lt;/li&gt;
4971
4972 &lt;/ul&gt;
4973
4974 &lt;p&gt;By now I suspect you are really curious what the test results are
4975 for the HP machines I am testing. I&#39;m not done yet, so I will report
4976 the test results later. For now I can report that HP 8100 Elite work
4977 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4978 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4979 can see, I have most machines left to test. One interesting
4980 observation is that Ubuntu Lucid has almost twice the frame rate than
4981 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4982 </description>
4983 </item>
4984
4985 <item>
4986 <title>Some thoughts on BitCoins</title>
4987 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4989 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4990 <description>&lt;p&gt;As I continue to explore
4991 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4992 what properties the system have, and how it will be affected by laws
4993 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4994
4995 &lt;p&gt;One interesting thing to note is that since the transactions are
4996 verified using a peer to peer network, all details about a transaction
4997 is known to everyone. This means that if a BitCoin address has been
4998 published like I did with mine in my initial post about BitCoin, it is
4999 possible for everyone to see how many BitCoins have been transfered to
5000 that address. There is even a web service to look at the details for
5001 all transactions. There I can see that my address
5002 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5003 have received 16.06 Bitcoin, the
5004 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5005 address of Simon Phipps have received 181.97 BitCoin and the address
5006 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5007 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5008 every one of you that donated bitcoins to support my activity. The
5009 fact that anyone can see how much money was transfered to a given
5010 address make it more obvious why the BitCoin community recommend to
5011 generate and hand out a new address for each transaction. I&#39;m told
5012 there is no way to track which addresses belong to a given person or
5013 organisation without the person or organisation revealing it
5014 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5015
5016 &lt;p&gt;In Norway, and in most other countries, there are laws and
5017 regulations limiting how much money one can transfer across the border
5018 without declaring it. There are money laundering, tax and accounting
5019 laws and regulations I would expect to apply to the use of BitCoin.
5020 If the Skolelinux foundation
5021 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5022 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5023 normal bank transfers like EFF is doing, how should this be accounted?
5024 Given that it is impossible to know if money can cross the border or
5025 not, should everything or nothing be declared? What exchange rate
5026 should be used when calculating taxes? Would receivers have to pay
5027 income tax if the foundation were to pay Skolelinux contributors in
5028 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5029
5030 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5031 accepted by a lot of users. It must be possible to get easy access to
5032 the currency (as a wage or using currency exchanges), and it must be
5033 easy to spend it. At the moment BitCoin seem fairly easy to get
5034 access to, but there are very few places to spend it. I am not really
5035 a regular user of any of the vendor types currently accepting BitCoin,
5036 so I wonder when my kind of shop would start accepting BitCoins. I
5037 would like to buy electronics, travels and subway tickets, not herbs
5038 and books. :) The currency is young, and this will improve over time
5039 if it become popular, but I suspect regular banks will start to lobby
5040 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5041 will claim it is helping fund terrorism and money laundering (which
5042 probably would be true, as is any currency in existence), but I
5043 believe the problems should be solved elsewhere and not by blaming
5044 currencies.&lt;/p&gt;
5045
5046 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5047 CPU intensive process that depend on a bit of luck as well (as one is
5048 competing against all the other miners currently spending CPU cycles
5049 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5050 BitCoin when this happen. Yesterday I came across the obvious way to
5051 join forces to increase ones changes of getting at least some coins,
5052 by coordinating the work on mining BitCoins across several machines
5053 and people, and sharing the result if one is lucky and get the 50
5054 BitCoins. Check out
5055 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5056 if this sounds interesting. I have not had time to try to set up a
5057 machine to participate there yet, but have seen that running on ones
5058 own for a few days have not yield any BitCoins througth mining
5059 yet.&lt;/p&gt;
5060
5061 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5062 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5063 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5064 it was interesting to read. The arguments presented seem to be
5065 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5066 </description>
5067 </item>
5068
5069 <item>
5070 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5071 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5072 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5073 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5074 <description>&lt;p&gt;With this weeks lawless
5075 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5076 attacks&lt;/a&gt; on Wikileak and
5077 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5078 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5079 not be trusted to handle money transactions.
5080 A blog post from
5081 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5082 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5083 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5084 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5085 some help from my friend to get it all running, and he even handed me
5086 some bitcoins to get started. I even donated a few bitcoins to Simon
5087 for helping me remember BitCoin.&lt;/p&gt;
5088
5089 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5090 crypto-currency, decentralised and handled using peer-to-peer
5091 networks. It allows anonymous transactions and prohibits central
5092 control over the transactions, making it impossible for governments
5093 and companies alike to block donations and other transactions. The
5094 source is free software, and while the key dependency wxWidgets 2.9
5095 for the graphical user interface is missing in Debian, the command
5096 line client builds just fine. Hopefully Jonas
5097 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5098 Debian&lt;/a&gt; soon.&lt;/p&gt;
5099
5100 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5101 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5102 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5103 currency &quot;stock&quot; markets where the exchange rate is decided. There
5104 are not many users so far, but the concept seems promising. If you
5105 want to get started and lack a friend with any bitcoins to spare,
5106 you can even get
5107 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5108 bitcoin at the time of writing). Use
5109 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5110 on the current exchange rates.&lt;/p&gt;
5111
5112 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5113 machines. If you want to support my activity, please send Bitcoin
5114 donations to the address
5115 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5116 </description>
5117 </item>
5118
5119 <item>
5120 <title>Why isn&#39;t Debian Edu using VLC?</title>
5121 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5123 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5124 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5125 presented, and the winner among the multimedia player were VLC.
5126 Personally, I like VLC, and it is my player of choice when I first try
5127 to play a video file or stream. Only if VLC fail will I drag out
5128 gmplayer to see if it can do better. The reason is mostly the failure
5129 model and trust. When VLC fail, it normally pop up a error message
5130 reporting the problem. When mplayer fail, it normally segfault or
5131 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5132
5133 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5134 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5135 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5136 plugin to play web videos seamlessly, and the VLC browser plugin is
5137 not very good. For example, it lack in-line control buttons, so there
5138 is no way for the user to pause the video. Also, when I
5139 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5140 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5141 failed on several video pages where mplayer based plugins worked. If
5142 the browser plugin for VLC was as good as the gecko-mediaplayer
5143 package (which uses mplayer), we would switch.&lt;/P&gt;
5144
5145 &lt;p&gt;While VLC is a good player, its user interface is slightly
5146 annoying. The most annoying feature is its inconsistent use of
5147 keyboard shortcuts. When the player is in full screen mode, its
5148 shortcuts are different from when it is playing the video in a window.
5149 For example, space only work as pause when in full screen mode. I
5150 wish it had consisten shortcuts and that space also would work when in
5151 window mode. Another nice shortcut in gmplayer is [enter] to restart
5152 the current video. It is very nice when playing short videos from the
5153 web and want to restart it when new people arrive to have a look at
5154 what is going on.&lt;/p&gt;
5155 </description>
5156 </item>
5157
5158 <item>
5159 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5160 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5161 <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>
5162 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5163 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5164 upgrade testing of the
5165 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5166 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5167 This seem like a very good idea, so I adjusted by test scripts and
5168 can now present the updated result from today:&lt;/p&gt;
5169
5170 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5171
5172 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5173
5174 &lt;blockquote&gt;&lt;p&gt;
5175 apache2.2-bin
5176 aptdaemon
5177 baobab
5178 binfmt-support
5179 browser-plugin-gnash
5180 cheese-common
5181 cli-common
5182 cups-pk-helper
5183 dmz-cursor-theme
5184 empathy
5185 empathy-common
5186 freedesktop-sound-theme
5187 freeglut3
5188 gconf-defaults-service
5189 gdm-themes
5190 gedit-plugins
5191 geoclue
5192 geoclue-hostip
5193 geoclue-localnet
5194 geoclue-manual
5195 geoclue-yahoo
5196 gnash
5197 gnash-common
5198 gnome
5199 gnome-backgrounds
5200 gnome-cards-data
5201 gnome-codec-install
5202 gnome-core
5203 gnome-desktop-environment
5204 gnome-disk-utility
5205 gnome-screenshot
5206 gnome-search-tool
5207 gnome-session-canberra
5208 gnome-system-log
5209 gnome-themes-extras
5210 gnome-themes-more
5211 gnome-user-share
5212 gstreamer0.10-fluendo-mp3
5213 gstreamer0.10-tools
5214 gtk2-engines
5215 gtk2-engines-pixbuf
5216 gtk2-engines-smooth
5217 hamster-applet
5218 libapache2-mod-dnssd
5219 libapr1
5220 libaprutil1
5221 libaprutil1-dbd-sqlite3
5222 libaprutil1-ldap
5223 libart2.0-cil
5224 libboost-date-time1.42.0
5225 libboost-python1.42.0
5226 libboost-thread1.42.0
5227 libchamplain-0.4-0
5228 libchamplain-gtk-0.4-0
5229 libcheese-gtk18
5230 libclutter-gtk-0.10-0
5231 libcryptui0
5232 libdiscid0
5233 libelf1
5234 libepc-1.0-2
5235 libepc-common
5236 libepc-ui-1.0-2
5237 libfreerdp-plugins-standard
5238 libfreerdp0
5239 libgconf2.0-cil
5240 libgdata-common
5241 libgdata7
5242 libgdu-gtk0
5243 libgee2
5244 libgeoclue0
5245 libgexiv2-0
5246 libgif4
5247 libglade2.0-cil
5248 libglib2.0-cil
5249 libgmime2.4-cil
5250 libgnome-vfs2.0-cil
5251 libgnome2.24-cil
5252 libgnomepanel2.24-cil
5253 libgpod-common
5254 libgpod4
5255 libgtk2.0-cil
5256 libgtkglext1
5257 libgtksourceview2.0-common
5258 libmono-addins-gui0.2-cil
5259 libmono-addins0.2-cil
5260 libmono-cairo2.0-cil
5261 libmono-corlib2.0-cil
5262 libmono-i18n-west2.0-cil
5263 libmono-posix2.0-cil
5264 libmono-security2.0-cil
5265 libmono-sharpzip2.84-cil
5266 libmono-system2.0-cil
5267 libmtp8
5268 libmusicbrainz3-6
5269 libndesk-dbus-glib1.0-cil
5270 libndesk-dbus1.0-cil
5271 libopal3.6.8
5272 libpolkit-gtk-1-0
5273 libpt2.6.7
5274 libpython2.6
5275 librpm1
5276 librpmio1
5277 libsdl1.2debian
5278 libsrtp0
5279 libssh-4
5280 libtelepathy-farsight0
5281 libtelepathy-glib0
5282 libtidy-0.99-0
5283 media-player-info
5284 mesa-utils
5285 mono-2.0-gac
5286 mono-gac
5287 mono-runtime
5288 nautilus-sendto
5289 nautilus-sendto-empathy
5290 p7zip-full
5291 pkg-config
5292 python-aptdaemon
5293 python-aptdaemon-gtk
5294 python-axiom
5295 python-beautifulsoup
5296 python-bugbuddy
5297 python-clientform
5298 python-coherence
5299 python-configobj
5300 python-crypto
5301 python-cupshelpers
5302 python-elementtree
5303 python-epsilon
5304 python-evolution
5305 python-feedparser
5306 python-gdata
5307 python-gdbm
5308 python-gst0.10
5309 python-gtkglext1
5310 python-gtksourceview2
5311 python-httplib2
5312 python-louie
5313 python-mako
5314 python-markupsafe
5315 python-mechanize
5316 python-nevow
5317 python-notify
5318 python-opengl
5319 python-openssl
5320 python-pam
5321 python-pkg-resources
5322 python-pyasn1
5323 python-pysqlite2
5324 python-rdflib
5325 python-serial
5326 python-tagpy
5327 python-twisted-bin
5328 python-twisted-conch
5329 python-twisted-core
5330 python-twisted-web
5331 python-utidylib
5332 python-webkit
5333 python-xdg
5334 python-zope.interface
5335 remmina
5336 remmina-plugin-data
5337 remmina-plugin-rdp
5338 remmina-plugin-vnc
5339 rhythmbox-plugin-cdrecorder
5340 rhythmbox-plugins
5341 rpm-common
5342 rpm2cpio
5343 seahorse-plugins
5344 shotwell
5345 software-center
5346 system-config-printer-udev
5347 telepathy-gabble
5348 telepathy-mission-control-5
5349 telepathy-salut
5350 tomboy
5351 totem
5352 totem-coherence
5353 totem-mozilla
5354 totem-plugins
5355 transmission-common
5356 xdg-user-dirs
5357 xdg-user-dirs-gtk
5358 xserver-xephyr
5359 &lt;/p&gt;&lt;/blockquote&gt;
5360
5361 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5362
5363 &lt;blockquote&gt;&lt;p&gt;
5364 cheese
5365 ekiga
5366 eog
5367 epiphany-extensions
5368 evolution-exchange
5369 fast-user-switch-applet
5370 file-roller
5371 gcalctool
5372 gconf-editor
5373 gdm
5374 gedit
5375 gedit-common
5376 gnome-games
5377 gnome-games-data
5378 gnome-nettool
5379 gnome-system-tools
5380 gnome-themes
5381 gnuchess
5382 gucharmap
5383 guile-1.8-libs
5384 libavahi-ui0
5385 libdmx1
5386 libgalago3
5387 libgtk-vnc-1.0-0
5388 libgtksourceview2.0-0
5389 liblircclient0
5390 libsdl1.2debian-alsa
5391 libspeexdsp1
5392 libsvga1
5393 rhythmbox
5394 seahorse
5395 sound-juicer
5396 system-config-printer
5397 totem-common
5398 transmission-gtk
5399 vinagre
5400 vino
5401 &lt;/p&gt;&lt;/blockquote&gt;
5402
5403 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5404
5405 &lt;blockquote&gt;&lt;p&gt;
5406 gstreamer0.10-gnomevfs
5407 &lt;/p&gt;&lt;/blockquote&gt;
5408
5409 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5410
5411 &lt;blockquote&gt;&lt;p&gt;
5412 [nothing]
5413 &lt;/p&gt;&lt;/blockquote&gt;
5414
5415 &lt;p&gt;This is for KDE:&lt;/p&gt;
5416
5417 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5418
5419 &lt;blockquote&gt;&lt;p&gt;
5420 ksmserver
5421 &lt;/p&gt;&lt;/blockquote&gt;
5422
5423 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5424
5425 &lt;blockquote&gt;&lt;p&gt;
5426 kwin
5427 network-manager-kde
5428 &lt;/p&gt;&lt;/blockquote&gt;
5429
5430 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5431
5432 &lt;blockquote&gt;&lt;p&gt;
5433 arts
5434 dolphin
5435 freespacenotifier
5436 google-gadgets-gst
5437 google-gadgets-xul
5438 kappfinder
5439 kcalc
5440 kcharselect
5441 kde-core
5442 kde-plasma-desktop
5443 kde-standard
5444 kde-window-manager
5445 kdeartwork
5446 kdeartwork-emoticons
5447 kdeartwork-style
5448 kdeartwork-theme-icon
5449 kdebase
5450 kdebase-apps
5451 kdebase-workspace
5452 kdebase-workspace-bin
5453 kdebase-workspace-data
5454 kdeeject
5455 kdelibs
5456 kdeplasma-addons
5457 kdeutils
5458 kdewallpapers
5459 kdf
5460 kfloppy
5461 kgpg
5462 khelpcenter4
5463 kinfocenter
5464 konq-plugins-l10n
5465 konqueror-nsplugins
5466 kscreensaver
5467 kscreensaver-xsavers
5468 ktimer
5469 kwrite
5470 libgle3
5471 libkde4-ruby1.8
5472 libkonq5
5473 libkonq5-templates
5474 libnetpbm10
5475 libplasma-ruby
5476 libplasma-ruby1.8
5477 libqt4-ruby1.8
5478 marble-data
5479 marble-plugins
5480 netpbm
5481 nuvola-icon-theme
5482 plasma-dataengines-workspace
5483 plasma-desktop
5484 plasma-desktopthemes-artwork
5485 plasma-runners-addons
5486 plasma-scriptengine-googlegadgets
5487 plasma-scriptengine-python
5488 plasma-scriptengine-qedje
5489 plasma-scriptengine-ruby
5490 plasma-scriptengine-webkit
5491 plasma-scriptengines
5492 plasma-wallpapers-addons
5493 plasma-widget-folderview
5494 plasma-widget-networkmanagement
5495 ruby
5496 sweeper
5497 update-notifier-kde
5498 xscreensaver-data-extra
5499 xscreensaver-gl
5500 xscreensaver-gl-extra
5501 xscreensaver-screensaver-bsod
5502 &lt;/p&gt;&lt;/blockquote&gt;
5503
5504 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5505
5506 &lt;blockquote&gt;&lt;p&gt;
5507 ark
5508 google-gadgets-common
5509 google-gadgets-qt
5510 htdig
5511 kate
5512 kdebase-bin
5513 kdebase-data
5514 kdepasswd
5515 kfind
5516 klipper
5517 konq-plugins
5518 konqueror
5519 ksysguard
5520 ksysguardd
5521 libarchive1
5522 libcln6
5523 libeet1
5524 libeina-svn-06
5525 libggadget-1.0-0b
5526 libggadget-qt-1.0-0b
5527 libgps19
5528 libkdecorations4
5529 libkephal4
5530 libkonq4
5531 libkonqsidebarplugin4a
5532 libkscreensaver5
5533 libksgrd4
5534 libksignalplotter4
5535 libkunitconversion4
5536 libkwineffects1a
5537 libmarblewidget4
5538 libntrack-qt4-1
5539 libntrack0
5540 libplasma-geolocation-interface4
5541 libplasmaclock4a
5542 libplasmagenericshell4
5543 libprocesscore4a
5544 libprocessui4a
5545 libqalculate5
5546 libqedje0a
5547 libqtruby4shared2
5548 libqzion0a
5549 libruby1.8
5550 libscim8c2a
5551 libsmokekdecore4-3
5552 libsmokekdeui4-3
5553 libsmokekfile3
5554 libsmokekhtml3
5555 libsmokekio3
5556 libsmokeknewstuff2-3
5557 libsmokeknewstuff3-3
5558 libsmokekparts3
5559 libsmokektexteditor3
5560 libsmokekutils3
5561 libsmokenepomuk3
5562 libsmokephonon3
5563 libsmokeplasma3
5564 libsmokeqtcore4-3
5565 libsmokeqtdbus4-3
5566 libsmokeqtgui4-3
5567 libsmokeqtnetwork4-3
5568 libsmokeqtopengl4-3
5569 libsmokeqtscript4-3
5570 libsmokeqtsql4-3
5571 libsmokeqtsvg4-3
5572 libsmokeqttest4-3
5573 libsmokeqtuitools4-3
5574 libsmokeqtwebkit4-3
5575 libsmokeqtxml4-3
5576 libsmokesolid3
5577 libsmokesoprano3
5578 libtaskmanager4a
5579 libtidy-0.99-0
5580 libweather-ion4a
5581 libxklavier16
5582 libxxf86misc1
5583 okteta
5584 oxygencursors
5585 plasma-dataengines-addons
5586 plasma-scriptengine-superkaramba
5587 plasma-widget-lancelot
5588 plasma-widgets-addons
5589 plasma-widgets-workspace
5590 polkit-kde-1
5591 ruby1.8
5592 systemsettings
5593 update-notifier-common
5594 &lt;/p&gt;&lt;/blockquote&gt;
5595
5596 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5597 aptitude a bit more similar, but there are still quite a lott of
5598 differences. I have no idea what packages should be installed after
5599 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5600 </description>
5601 </item>
5602
5603 <item>
5604 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5605 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5606 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5607 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5608 <description>&lt;p&gt;Most of the computers in use by the
5609 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5610 are virtual machines. And they have been Xen machines running on a
5611 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5612 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5613 bit harder that it could have been, because we set up the Xen virtual
5614 machines to get the virtual partitions from LVM, which as far as I
5615 know is not supported by KVM. So to migrate, we had to convert
5616 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5617
5618 &lt;p&gt;I found
5619 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5620 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5621 migration. It uses qemu-img from the qemu package to make the disk
5622 image, parted to partition it, losetup and kpartx to present the disk
5623 image partions as devices, and dd to copy the data. I NFS mounted the
5624 new servers storage area on the old server to do the migration.&lt;/p&gt;
5625
5626 &lt;pre&gt;
5627 #!/bin/sh
5628
5629 # Based on
5630 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5631
5632 set -e
5633 set -x
5634
5635 if [ -z &quot;$1&quot; ] ; then
5636 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5637 exit 1
5638 else
5639 host=&quot;$1&quot;
5640 fi
5641
5642 if [ ! -e /dev/vg_data/$host-disk ] ; then
5643 echo &quot;error: unable to find LVM volume for $host&quot;
5644 exit 1
5645 fi
5646
5647 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5648 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5649 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5650 totalsize=$(( ( $disksize + $swapsize ) ))
5651
5652 img=$host.img
5653 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5654 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5655
5656 parted $img mklabel msdos
5657 parted $img mkpart primary linux-swap 0 $disksize
5658 parted $img mkpart primary ext2 $disksize $totalsize
5659 parted $img set 1 boot on
5660
5661 modprobe dm-mod
5662 losetup /dev/loop0 $img
5663 kpartx -a /dev/loop0
5664
5665 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5666 fsck.ext3 -f /dev/mapper/loop0p1 || true
5667 mkswap /dev/mapper/loop0p2
5668
5669 kpartx -d /dev/loop0
5670 losetup -d /dev/loop0
5671 &lt;/pre&gt;
5672
5673 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5674 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5675
5676 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5677 the new disk image attached, installed grub-pc and linux-image-686 and
5678 set up grub to boot from the disk image. After this, the KVM machines
5679 seem to work just fine.&lt;/p&gt;
5680 </description>
5681 </item>
5682
5683 <item>
5684 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5685 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5686 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5687 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5688 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5689 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5690 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5691 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5692
5693 &lt;p&gt;I still do not know what a correct migration should look like, so I
5694 report any differences between apt and aptitude and hope someone else
5695 can see if anything should be changed.&lt;/p&gt;
5696
5697 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5698
5699 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5700
5701 &lt;blockquote&gt;&lt;p&gt;
5702 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5703 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5704 dmz-cursor-theme empathy empathy-common finger
5705 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5706 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5707 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5708 gnome-cards-data gnome-codec-install gnome-core
5709 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5710 gnome-search-tool gnome-session-canberra gnome-spell
5711 gnome-system-log gnome-themes-extras gnome-themes-more
5712 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5713 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5714 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5715 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5716 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5717 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5718 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5719 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5720 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5721 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5722 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5723 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5724 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5725 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5726 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5727 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5728 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5729 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5730 libmono-security2.0-cil libmono-sharpzip2.84-cil
5731 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5732 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5733 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5734 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5735 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5736 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5737 libxalan2-java libxerces2-java media-player-info mesa-utils
5738 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5739 nautilus-sendto-empathy openoffice.org-writer2latex
5740 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5741 python-aptdaemon python-aptdaemon-gtk python-axiom
5742 python-beautifulsoup python-bugbuddy python-clientform
5743 python-coherence python-configobj python-crypto python-cupshelpers
5744 python-cupsutils python-eggtrayicon python-elementtree
5745 python-epsilon python-evolution python-feedparser python-gdata
5746 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5747 python-gtksourceview2 python-httplib2 python-louie python-mako
5748 python-markupsafe python-mechanize python-nevow python-notify
5749 python-opengl python-openssl python-pam python-pkg-resources
5750 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5751 python-tagpy python-twisted-bin python-twisted-conch
5752 python-twisted-core python-twisted-web python-utidylib python-webkit
5753 python-xdg python-zope.interface remmina remmina-plugin-data
5754 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5755 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5756 software-center svgalibg1 system-config-printer-udev
5757 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5758 totem totem-coherence totem-mozilla totem-plugins
5759 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5760 zip
5761 &lt;/p&gt;&lt;/blockquote&gt;
5762
5763 Installed using apt-get, removed with aptitude
5764
5765 &lt;blockquote&gt;&lt;p&gt;
5766 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5767 epiphany-extensions epiphany-gecko evolution-exchange
5768 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5769 gedit-common gnome-app-install gnome-games gnome-games-data
5770 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5771 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5772 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5773 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5774 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5775 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5776 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5777 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5778 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5779 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5780 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5781 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5782 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5783 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5784 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5785 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5786 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5787 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5788 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5789 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5790 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5791 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5792 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5793 sound-juicer swfdec-gnome system-config-printer totem-common
5794 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5795 &lt;/p&gt;&lt;/blockquote&gt;
5796
5797 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5798
5799 &lt;blockquote&gt;&lt;p&gt;
5800 gstreamer0.10-gnomevfs
5801 &lt;/p&gt;&lt;/blockquote&gt;
5802
5803 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5804
5805 &lt;blockquote&gt;&lt;p&gt;
5806 [nothing]
5807 &lt;/p&gt;&lt;/blockquote&gt;
5808
5809 &lt;p&gt;This is for KDE:&lt;/p&gt;
5810
5811 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5812
5813 &lt;blockquote&gt;&lt;p&gt;
5814 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5815 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5816 ghostscript-x git gnome-audio gnugo granatier gs-common
5817 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5818 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5819 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5820 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5821 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5822 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5823 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5824 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5825 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5826 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5827 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5828 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5829 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5830 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5831 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5832 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5833 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5834 libkrossui4 libmailtools-perl libmime-tools-perl
5835 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5836 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5837 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5838 lirc luatex marble networkstatus noatun-plugins
5839 openoffice.org-writer2latex palapeli palapeli-data parley
5840 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5841 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5842 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5843 ttf-sazanami-gothic
5844 &lt;/p&gt;&lt;/blockquote&gt;
5845
5846 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5847
5848 &lt;blockquote&gt;&lt;p&gt;
5849 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5850 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5851 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5852 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5853 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5854 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5855 kitchensync kiten kjumpingcube klatin klettres klickety klines
5856 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5857 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5858 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5859 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5860 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5861 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5862 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5863 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5864 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5865 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5866 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5867 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5868 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5869 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5870 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5871 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5872 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5873 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5874 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5875 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5876 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5877 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5878 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5879 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5880 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5881 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5882 &lt;/p&gt;&lt;/blockquote&gt;
5883
5884 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5885
5886 &lt;blockquote&gt;&lt;p&gt;
5887 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5888 kdeartwork kdebase kdebase-apps kdebase-workspace
5889 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5890 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5891 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5892 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5893 xscreensaver-screensaver-bsod
5894 &lt;/p&gt;&lt;/blockquote&gt;
5895
5896 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5897
5898 &lt;blockquote&gt;&lt;p&gt;
5899 kdebase-bin konq-plugins konqueror
5900 &lt;/p&gt;&lt;/blockquote&gt;
5901 </description>
5902 </item>
5903
5904 <item>
5905 <title>Gnash buildbot slave and Debian kfreebsd</title>
5906 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5907 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5908 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5909 <description>&lt;p&gt;Answering
5910 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5911 call from the Gnash project&lt;/a&gt; for
5912 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5913 current source, I have set up a virtual KVM machine on the Debian
5914 Edu/Skolelinux virtualization host to test the git source on
5915 Debian/Squeeze. I hope this can help the developers in getting new
5916 releases out more often.&lt;/p&gt;
5917
5918 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5919 I have considered setting up a &lt;a
5920 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5921 machine as well. I have also considered using the kfreebsd
5922 architecture in Debian as a file server in NUUG to get access to the 5
5923 TB zfs volume we currently use to store DV video. Because of this, I
5924 finally got around to do a test installation of Debian/Squeeze with
5925 kfreebsd. Installation went fairly smooth, thought I noticed some
5926 visual glitches in the cdebconf dialogs (black cursor left on the
5927 screen at random locations). Have not gotten very far with the
5928 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5929 fatal problem. Have to spend some more time on it to see if it is
5930 useful as a file server for NUUG. Will try to find time to set up a
5931 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5932 </description>
5933 </item>
5934
5935 <item>
5936 <title>Debian in 3D</title>
5937 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5938 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5939 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5940 <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;
5941
5942 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5943 3D linked in from
5944 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5945 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5946 </description>
5947 </item>
5948
5949 <item>
5950 <title>Software updates 2010-10-24</title>
5951 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5952 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5953 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5954 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5955
5956 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5957 raise money for the project is going well. The lower limit of 10
5958 signers was reached in 24 hours, and so far 13 people have signed it.
5959 More signers and more funding is most welcome, and I am really curious
5960 how far we can get before the time limit of December 24 is reached.
5961 :)&lt;/p&gt;
5962
5963 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5964 about what appear to be a great code coverage tool capable of
5965 generating code coverage stats without any changes to the source code.
5966 It is called
5967 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5968 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5969 It is missing in Debian, but the git source built just fine in Squeeze
5970 after I installed libelf-dev, libdwarf-dev, pkg-config and
5971 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5972 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5973
5974 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5975 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5976 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5977 alpha test release of the Squeeze based Debian Edu /
5978 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5979 release. Give it a try if you need a complete linux solution for your
5980 school, including central infrastructure server, workstations, thin
5981 client servers and diskless workstations. A nice touch added
5982 yesterday is RDP support on the thin client servers, for windows
5983 clients to get a Linux desktop on request.&lt;/p&gt;
5984 </description>
5985 </item>
5986
5987 <item>
5988 <title>Some notes on Flash in Debian and Debian Edu</title>
5989 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5990 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5991 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5992 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5993 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5994 second most popular used package that is missing in Debian. The sixth
5995 most popular is flashplayer-mozilla. This is a clear indication that
5996 working flash is important for Debian users. Around 10 percent of the
5997 users submitting data to popcon.debian.org have this package
5998 installed.&lt;/p&gt;
5999
6000 &lt;p&gt;In the report written by Lars Risan in August 2008
6001&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
6002 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6003 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6004 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6005 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6006 web sites require Flash to work, and lacking working Flash support in
6007 the web browser and the problems with installing it was perceived as a
6008 good reason to stay with Windows.&lt;/p&gt;
6009
6010 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6011 said to be the retarded cousin that did not really understand
6012 everything you told him but could work fairly well. This was a
6013 comment regarding the problems Linux have with proprietary formats and
6014 non-standard web pages, and is sad because it exposes a fairly common
6015 understanding of whose fault it is if web pages that only work in for
6016 example Internet Explorer 6 fail to work on Firefox, and funny because
6017 it explain very well how annoying it is for users when Linux
6018 distributions do not work with the documents they receive or the web
6019 pages they want to visit.&lt;/p&gt;
6020
6021 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6022 and Debian Edu to have a well working Flash implementation in the
6023 distribution, to get at least popular sites as Youtube and Google
6024 Video to working out of the box. For Squeeze, Debian have the chance
6025 to include the latest version of Gnash that will make this happen, as
6026 the new release 0.8.8 was published a few weeks ago and is resting in
6027 unstable. The new version work with more sites that version 0.8.7.
6028 The Gnash maintainers have asked for a freeze exception, but the
6029 release team have not had time to reply to it yet. I hope they agree
6030 with me that Flash is important for the Debian desktop users, and thus
6031 accept the new package into Squeeze.&lt;/p&gt;
6032 </description>
6033 </item>
6034
6035 <item>
6036 <title>Circular package dependencies harms apt recovery</title>
6037 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6038 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6039 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6040 <description>&lt;p&gt;I discovered this while doing
6041 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6042 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6043 in Debian still got circular dependencies, and it is often claimed
6044 that apt and aptitude should be able to handle this just fine, but
6045 some times these dependency loops causes apt to fail.&lt;/p&gt;
6046
6047 &lt;p&gt;An example is from todays
6048 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6049 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6050 causes perl-modules to fail to upgrade. The cause is simple. If a
6051 package fail to unpack, then only part of packages with the circular
6052 dependency might end up being unpacked when unpacking aborts, and the
6053 ones already unpacked will fail to configure in the recovery phase
6054 because its dependencies are unavailable.&lt;/p&gt;
6055
6056 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6057
6058 &lt;blockquote&gt;&lt;pre&gt;
6059 dpkg: dependency problems prevent configuration of perl-modules:
6060 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6061 Version of perl on system is 5.10.0-19lenny2.
6062 dpkg: error processing perl-modules (--configure):
6063 dependency problems - leaving unconfigured
6064 &lt;/pre&gt;&lt;/blockquote&gt;
6065
6066 &lt;p&gt;The perl/perl-modules circular dependency is already
6067 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6068 hopefully be solved as soon as possible, but it is not the only one,
6069 and each one of these loops in the dependency tree can cause similar
6070 failures. Of course, they only occur when there are bugs in other
6071 packages causing the unpacking to fail, but it is rather nasty when
6072 the failure of one package causes the problem to become worse because
6073 of dependency loops.&lt;/p&gt;
6074
6075 &lt;p&gt;Thanks to
6076 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6077 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6078 dependencies
6079 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6080 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6081
6082 &lt;p&gt;Todays testing also exposed a bug in
6083 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6084 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6085 apt-get and aptitude, the latter possibly caused by some circular
6086 dependency. Reported both to BTS to try to get someone to look at
6087 it.&lt;/p&gt;
6088 </description>
6089 </item>
6090
6091 <item>
6092 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6093 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6094 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6095 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6096 <description>&lt;p&gt;This is a
6097 &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;
6098 on my
6099 &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
6100 work&lt;/a&gt; on
6101 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6102 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6103
6104 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6105 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6106 and dhcp3-server-ldap in Debian use the LDAP server. The two
6107 implementations are quite different in how they use LDAP.&lt;/p&gt;
6108
6109 To get this information, I started slapd with debugging enabled and
6110 dumped the debug output to a file to get the LDAP searches performed
6111 on a Debian Edu main-server. Here is a summary.
6112
6113 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6114
6115 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6116 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6117 the web.
6118
6119 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6120 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6121 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6122 reverse entries are in two different subtrees in LDAP with a structure
6123 based on the DNS names, as in tjener.intern and
6124 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6125
6126 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6127 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6128 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6129 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6130 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6131 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6132 forward entries, it is looking for attributes named dnsttl, arecord,
6133 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6134 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6135 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6136 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6137 spfrecord and modifytimestamp. For reverse entries it is looking for
6138 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6139 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6140 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6141 ldapsearch commands could look like this:&lt;/p&gt;
6142
6143 &lt;blockquote&gt;&lt;pre&gt;
6144 ldapsearch -h ldap \
6145 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6146 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6147 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6148 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6149 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6150 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6151
6152 ldapsearch -h ldap \
6153 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6154 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6155 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6156 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6157 srvrecord naptrrecord modifytimestamp
6158 &lt;/pre&gt;&lt;/blockquote&gt;
6159
6160 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6161 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6162 example LDAP objects used there. In addition to these objects, the
6163 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6164 also exist.&lt;/p&gt;
6165
6166 &lt;blockquote&gt;&lt;pre&gt;
6167 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6168 objectclass: top
6169 objectclass: dnsdomain
6170 objectclass: domainrelatedobject
6171 dc: tjener
6172 arecord: 10.0.2.2
6173 associateddomain: tjener.intern
6174
6175 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6176 objectclass: top
6177 objectclass: dnsdomain2
6178 objectclass: domainrelatedobject
6179 dc: 2
6180 ptrrecord: tjener.intern
6181 associateddomain: 2.2.0.10.in-addr.arpa
6182 &lt;/pre&gt;&lt;/blockquote&gt;
6183
6184 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6185 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6186 same base as in the tree mode for a object with filter
6187 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6188 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6189 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6190 naptrrecord and modifytimestamp. For reverse entires it also do a
6191 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6192 and the requested attributes are associateddomain, dnsttl and
6193 modifytimestamp. In short, in strict mode the objects with ptrrecord
6194 go away, and the arecord attribute in the forward object is used
6195 instead.&lt;/p&gt;
6196
6197 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6198 like this:&lt;/p&gt;
6199
6200 &lt;blockquote&gt;&lt;pre&gt;
6201 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6202 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6203 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6204 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6205 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6206 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6207
6208 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6209 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6210 &lt;/pre&gt;&lt;/blockquote&gt;
6211
6212 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6213 search for SOA records, which behave similar to the forward and
6214 reverse lookups.&lt;/p&gt;
6215
6216 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6217 specify any objectclass names, and instead look for the attributes it
6218 need to generate a DNS reply. This make it able to work with any
6219 objectclass that provide the needed attributes.&lt;/p&gt;
6220
6221 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6222 dnsdomain2 schemas. The latter is used for reverse entries like
6223 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6224
6225 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6226 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6227 attributes) and domainrelatedobject (for associatedDomain). The use
6228 of structural object classes make it impossible to combine these
6229 classes with the object classes used by DHCP.&lt;/p&gt;
6230
6231 &lt;p&gt;There are other schemas that could be used too, for example the
6232 dnszone structural object class used by Gosa and bind-sdb for the DNS
6233 attributes combined with the domainrelatedobject object class, but in
6234 this case some unused attributes would have to be included as well
6235 (zonename and relativedomainname).&lt;/p&gt;
6236
6237 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6238 mode and not use any of the existing objectclasses (dnsdomain,
6239 dnsdomain2 and dnszone) when one want to combine the DNS information
6240 with DHCP information, and instead create a auxiliary object class
6241 defined something like this (using the attributes defined for
6242 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6243
6244 &lt;blockquote&gt;&lt;pre&gt;
6245 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6246 SUP top
6247 AUXILIARY
6248 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6249 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6250 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6251 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6252 A6Record $ DNAMERecord
6253 ))
6254 &lt;/pre&gt;&lt;/blockquote&gt;
6255
6256 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6257 the domainrelatedobject object class, and allow any entity to include
6258 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6259 developers asking for their view on this schema and if they are
6260 interested in providing such schema with PowerDNS, and I hope my
6261 message will be accepted into their mailing list soon.&lt;/p&gt;
6262
6263 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6264
6265 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6266 the object attributes, and then uses the attributes it want. This
6267 make it harder to figure out exactly what attributes are used, but
6268 thanks to the working example in Debian Edu I can at least get an idea
6269 what is needed without having to read the source code.&lt;/p&gt;
6270
6271 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6272 search filter to use to locate the correct dhcpServer entity is
6273 stored. These are the relevant entries from
6274 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6275
6276 &lt;blockquote&gt;&lt;pre&gt;
6277 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6278 ldap-dhcp-server-cn &quot;dhcp&quot;;
6279 &lt;/pre&gt;&lt;/blockquote&gt;
6280
6281 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6282 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6283 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6284 search result is this entry:&lt;/p&gt;
6285
6286 &lt;blockquote&gt;&lt;pre&gt;
6287 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6288 cn: dhcp
6289 objectClass: top
6290 objectClass: dhcpServer
6291 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6292 &lt;/pre&gt;&lt;/blockquote&gt;
6293
6294 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6295 subtree with DHCP configuration. The DHCP configuration subtree base
6296 is located using a base scope search with base &quot;cn=DHCP
6297 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6298 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6299 The search result is this entry:&lt;/p&gt;
6300
6301 &lt;blockquote&gt;&lt;pre&gt;
6302 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6303 cn: DHCP Config
6304 objectClass: top
6305 objectClass: dhcpService
6306 objectClass: dhcpOptions
6307 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6308 dhcpStatements: ddns-update-style none
6309 dhcpStatements: authoritative
6310 dhcpOption: smtp-server code 69 = array of ip-address
6311 dhcpOption: www-server code 72 = array of ip-address
6312 dhcpOption: wpad-url code 252 = text
6313 &lt;/pre&gt;&lt;/blockquote&gt;
6314
6315 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6316 all the DHCP configuration is loaded, it is ready to receive requests.
6317 The subtree in Debian Edu contain objects with object classes
6318 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6319 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6320 and information about netmasks, dynamic range etc. Leaving out the
6321 details here because it is not relevant for the focus of my
6322 investigation, which is to see if it is possible to merge dns and dhcp
6323 related computer objects.&lt;/p&gt;
6324
6325 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6326 of the client (00:00:00:00:00:00 in this example), using a subtree
6327 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6328 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6329 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6330 like:&lt;/p&gt;
6331
6332 &lt;blockquote&gt;&lt;pre&gt;
6333 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6334 cn: hostname
6335 objectClass: top
6336 objectClass: dhcpHost
6337 dhcpHWAddress: ethernet 00:00:00:00:00:00
6338 dhcpStatements: fixed-address hostname
6339 &lt;/pre&gt;&lt;/blockquote&gt;
6340
6341 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6342 The object classes need to have fixed names, and the configuration
6343 need to be stored in a fairly specific LDAP structure. On the
6344 positive side, the invidiual dhcpHost entires can be anywhere without
6345 the DN pointed to by the dhcpServer entries. The latter should make
6346 it possible to group all host entries in a subtree next to the
6347 configuration entries, and this subtree can also be shared with the
6348 DNS server if the schema proposed above is combined with the dhcpHost
6349 structural object class.
6350
6351 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6352
6353 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6354 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6355 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6356 allowing DNS objects to be stored anywhere under the base cn specified
6357 in the configuration.&lt;/p&gt;
6358
6359 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6360 regarding which LDAP schemas to use and which LDAP structure to use.
6361 I guess one could implement ones own schema, as long as the
6362 objectclasses and attributes have the names used, but this do not
6363 really help when the DHCP subtree need to have a fairly fixed
6364 structure.&lt;/p&gt;
6365
6366 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6367 this might work for Debian Edu:&lt;/p&gt;
6368
6369 &lt;blockquote&gt;&lt;pre&gt;
6370 ou=services
6371 cn=machine-info (dhcpService) - dhcpServiceDN points here
6372 cn=dhcp (dhcpServer)
6373 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6374 cn=10.0.2.0 (dhcpSubnet)
6375 cn=group1 (dhcpGroup/dhcpOptions)
6376 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6377 cn=192.168.0.0 (dhcpSubnet)
6378 cn=group1 (dhcpGroup/dhcpOptions)
6379 ou=machines - PowerDNS base points here
6380 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6381 &lt;/pre&gt;&lt;/blockquote&gt;
6382
6383 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6384 entries to be in the dhcpGroup subtrees, the entries can be stored
6385 there instead of a common machines subtree, and the PowerDNS base
6386 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6387
6388 &lt;p&gt;The combined object under the machines subtree would look something
6389 like this:&lt;/p&gt;
6390
6391 &lt;blockquote&gt;&lt;pre&gt;
6392 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6393 dc: hostname
6394 objectClass: top
6395 objectClass: dhcpHost
6396 objectclass: domainrelatedobject
6397 objectclass: dnsDomainAux
6398 associateddomain: hostname.intern
6399 arecord: 10.11.12.13
6400 dhcpHWAddress: ethernet 00:00:00:00:00:00
6401 dhcpStatements: fixed-address hostname.intern
6402 &lt;/pre&gt;&lt;/blockquote&gt;
6403
6404 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6405 machine, as long as the required attributes are available in a
6406 auxiliary object class.&lt;/p&gt;
6407 </description>
6408 </item>
6409
6410 <item>
6411 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6412 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6413 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6414 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6415 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6416 DHCP services in Debian Edu to use the same LDAP objects for a given
6417 computer, to avoid the possibility of having a inconsistent state for
6418 a computer in LDAP (as in DHCP but no DNS entry or the other way
6419 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6420
6421 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6422 information finally found a solution that seem to work.&lt;/p&gt;
6423
6424 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6425 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6426 we switch powerdns to use its strict LDAP method (ldap-method=strict
6427 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6428 merged into one while making it impossible to transfer the reverse map
6429 to a slave DNS server.&lt;/p&gt;
6430
6431 &lt;p&gt;If we also replace the object class used to get the DNS related
6432 attributes to one allowing these attributes to be combined with the
6433 dhcphost object class, we can merge the DNS and DHCP entries into one.
6434 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6435 proper OIDs, but that is a minor issue), and tested the setup. It
6436 seem to work.&lt;/p&gt;
6437
6438 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6439 for both DNS and DHCP, and even the LTSP configuration I suggested in
6440 an earlier email. The combined LDAP object will look something like
6441 this:&lt;/p&gt;
6442
6443 &lt;blockquote&gt;&lt;pre&gt;
6444 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6445 cn: hostname
6446 objectClass: dhcphost
6447 objectclass: domainrelatedobject
6448 objectclass: dnsdomainaux
6449 associateddomain: hostname.intern
6450 arecord: 10.11.12.13
6451 dhcphwaddress: ethernet 00:00:00:00:00:00
6452 dhcpstatements: fixed-address hostname
6453 ldapconfigsound: Y
6454 &lt;/pre&gt;&lt;/blockquote&gt;
6455
6456 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6457 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6458 before asking DNS to resolve the fixed-adddress. LTSP will use
6459 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6460
6461 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6462 dhcphost in a different location, to allow us to put the objects
6463 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6464 that. If I can&#39;t figure out a way to do that, we can still get rid of
6465 the hosts subtree and move all its content into the DHCP Config tree
6466 (which probably should be renamed to be more related to the new
6467 content. I suspect cn=dnsdhcp,ou=services or something like that
6468 might be a good place to put it.&lt;/p&gt;
6469
6470 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6471 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6472 </description>
6473 </item>
6474
6475 <item>
6476 <title>Idea for storing LTSP configuration in LDAP</title>
6477 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6478 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6479 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6480 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6481 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6482 clients, and that this can be used to fetch configuration from LDAP if
6483 Debian Edu choose to store configuration there.&lt;/p&gt;
6484
6485 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6486 to get configuration from LDAP. The idea is to look up the MAC
6487 address of the client in LDAP, and look for attributes on the form
6488 ltspconfigsetting=value, and use this to export SETTING=value to the
6489 LTSP clients.&lt;/p&gt;
6490
6491 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6492 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6493 allowing us to store all information about a computer in one place.&lt;/p&gt;
6494
6495 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6496 this approach. A real LDAP schema for the ltspClientAux objectclass
6497 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6498
6499 &lt;blockquote&gt;&lt;pre&gt;
6500 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6501 #
6502 # Fetch LTSP client settings from LDAP based on MAC address
6503 #
6504 # Uses ethernet address as stored in the dhcpHost objectclass using
6505 # the dhcpHWAddress attribute or ethernet address stored in the
6506 # ieee802Device objectclass with the macAddress attribute.
6507 #
6508 # This module is written to be schema agnostic, and only depend on the
6509 # existence of attribute names.
6510 #
6511 # The LTSP configuration variables are saved directly using a
6512 # ltspConfig prefix and uppercasing the rest of the attribute name.
6513 # To set the SERVER variable, set the ltspConfigServer attribute.
6514 #
6515 # Some LDAP schema should be created with all the relevant
6516 # configuration settings. Something like this should work:
6517 #
6518 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6519 # SUP top
6520 # AUXILIARY
6521 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6522
6523 LDAPSERVER=$(debian-edu-ldapserver)
6524 if [ &quot;$LDAPSERVER&quot; ] ; then
6525 LDAPBASE=$(debian-edu-ldapserver -b)
6526 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6527 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6528 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6529 grep &#39;^ltspConfig&#39; | while read attr value ; do
6530 # Remove prefix and convert to upper case
6531 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6532 # bass value on to clients
6533 eval &quot;$attr=$value; export $attr&quot;
6534 done
6535 done
6536 fi
6537 &lt;/pre&gt;&lt;/blockquote&gt;
6538
6539 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6540 the while block might end up in a subshell causing the variables set
6541 there to not show up in ltsp-config, but if that is the case I am sure
6542 the code can be restructured to make sure the variables are passed on.
6543 I expect that can be solved with some testing. :)&lt;/p&gt;
6544
6545 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6546 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6547
6548 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6549 configuration in LDAP that was created around year 2000 by
6550 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6551 Xperience, Inc., 2000&lt;/a&gt;. I found its
6552 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6553 personal home page over at redhat.com.&lt;/p&gt;
6554 </description>
6555 </item>
6556
6557 <item>
6558 <title>jXplorer, a very nice LDAP GUI</title>
6559 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6560 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6561 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6562 <description>&lt;p&gt;Since
6563 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6564 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6565 LDAP GUI that is even better than luma. The java application
6566 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6567 moving LDAP objects and subtrees using drag-and-drop, and can
6568 authenticate using Kerberos. I have only tested the Kerberos
6569 authentication, but do not have a LDAP setup allowing me to rewrite
6570 LDAP with my test user yet. It is
6571 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6572 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6573 have with it is how it handle errors. If something go wrong, its
6574 non-intuitive behaviour require me to go through some query work list
6575 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6576 </description>
6577 </item>
6578
6579 <item>
6580 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6581 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6582 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6583 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6584 <description>&lt;p&gt;Here is a short update on my &lt;a
6585 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6586 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6587 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6588 not reporting the status for KDE, because the upgrade crashes when
6589 aptitude try because of missing conflicts
6590 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6591 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6592
6593 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6594 complete list of the installed packages. Based on this I see these
6595 differences when I did a test run today. As usual, I do not really
6596 know what the correct set of packages would be, but thought it best to
6597 publish the difference.&lt;/p&gt;
6598
6599 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6600
6601 &lt;blockquote&gt;&lt;p&gt;
6602 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6603 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6604 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6605 libgtksourceview-common libpt-1.10.10-plugins-alsa
6606 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6607 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6608 python-4suite-xml python-eggtrayicon python-gtkhtml2
6609 python-gtkmozembed svgalibg1 xserver-xephyr zip
6610 &lt;/p&gt;&lt;/blockquote&gt;
6611
6612 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6613
6614 &lt;blockquote&gt;&lt;p&gt;
6615 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6616 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6617 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6618 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6619 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6620 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6621 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6622 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6623 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6624 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6625 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6626 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6627 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6628 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6629 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6630 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6631 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6632 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6633 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6634 mysql-common swfdec-gnome totem-gstreamer wodim
6635 &lt;/p&gt;&lt;/blockquote&gt;
6636
6637 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6638
6639 &lt;blockquote&gt;&lt;p&gt;
6640 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6641 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6642 xserver-xorg-input-all xserver-xorg-input-evdev
6643 xserver-xorg-input-kbd xserver-xorg-input-mouse
6644 xserver-xorg-input-synaptics xserver-xorg-video-all
6645 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6646 xserver-xorg-video-chips xserver-xorg-video-cirrus
6647 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6648 xserver-xorg-video-glint xserver-xorg-video-i128
6649 xserver-xorg-video-i740 xserver-xorg-video-mach64
6650 xserver-xorg-video-mga xserver-xorg-video-neomagic
6651 xserver-xorg-video-nouveau xserver-xorg-video-nv
6652 xserver-xorg-video-r128 xserver-xorg-video-radeon
6653 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6654 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6655 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6656 xserver-xorg-video-sis xserver-xorg-video-sisusb
6657 xserver-xorg-video-tdfx xserver-xorg-video-tga
6658 xserver-xorg-video-trident xserver-xorg-video-tseng
6659 xserver-xorg-video-vesa xserver-xorg-video-vmware
6660 xserver-xorg-video-voodoo
6661 &lt;/p&gt;&lt;/blockquote&gt;
6662
6663 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6664
6665 &lt;blockquote&gt;&lt;p&gt;
6666 deskbar-applet xserver-xorg xserver-xorg-core
6667 xserver-xorg-input-wacom xserver-xorg-video-intel
6668 xserver-xorg-video-openchrome
6669 &lt;/p&gt;&lt;/blockquote&gt;
6670
6671 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6672 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6673 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6674 No idea when it hits Squeeze, but when it does I hope it will reduce
6675 the difference somewhat.
6676 </description>
6677 </item>
6678
6679 <item>
6680 <title>LUMA, a very nice LDAP GUI</title>
6681 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6682 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6683 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6684 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6685 directory in Debian Edu, and in the process I started to miss a GUI
6686 tool to browse the LDAP tree. The only one I was able to find in
6687 Debian/Squeeze and Lenny is
6688 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6689 be a great tool to get a overview of the current LDAP directory
6690 populated by default in Skolelinux. Thanks to it, I have been able to
6691 find empty and obsolete subtrees, misplaced objects and duplicate
6692 objects. It will be installed by default in Debian/Squeeze. If you
6693 are working with LDAP, give it a go. :)&lt;/p&gt;
6694
6695 &lt;p&gt;I did notice one problem with it I have not had time to report to
6696 the BTS yet. There is no .desktop file in the package, so the tool do
6697 not show up in the Gnome and KDE menus, but only deep down in in the
6698 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6699 released.&lt;/p&gt;
6700
6701 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6702 like to move objects and remove subtrees directly in the GUI, but have
6703 not found a way to do that with LUMA yet. So in the mean time, I use
6704 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6705
6706 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6707 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6708
6709 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6710 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6711 useful GUI alternative. It seem like a good tool, but is unmaintained
6712 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6713 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6714 </description>
6715 </item>
6716
6717 <item>
6718 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6719 <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>
6720 <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>
6721 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6722 <description>&lt;p&gt;A while back, I
6723 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6724 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6725 for storing DNS and DHCP information in LDAP to combine the two sets
6726 of information into one LDAP object representing a computer.&lt;/p&gt;
6727
6728 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6729 the dhcpHost object class auxiliary, to allow it to be combined with
6730 the dNSDomain object class, and thus forming one object for one
6731 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6732
6733 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6734 without also changing the assigned number for the object class, and I
6735 do not know enough about LDAP schema design to do that properly for
6736 Debian Edu.&lt;/p&gt;
6737
6738 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6739 the
6740 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6741 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6742 available today from IETF.&lt;/p&gt;
6743
6744 &lt;pre&gt;
6745 --- dhcp.schema (revision 65192)
6746 +++ dhcp.schema (working copy)
6747 @@ -376,7 +376,7 @@
6748 objectclass ( 2.16.840.1.113719.1.203.6.6
6749 NAME &#39;dhcpHost&#39;
6750 DESC &#39;This represents information about a particular client&#39;
6751 - SUP top
6752 + SUP top AUXILIARY
6753 MUST cn
6754 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6755 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6756 &lt;/pre&gt;
6757
6758 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6759 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6760 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6761
6762 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6763 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6764 </description>
6765 </item>
6766
6767 <item>
6768 <title>Calling tasksel like the installer, while still getting useful output</title>
6769 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6770 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6771 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6772 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6773 installs packages during the normal debian-installer run. Until now,
6774 I have ended up letting tasksel do the work, with the annoying problem
6775 of not getting any feedback at all when something fails (like a
6776 conffile question from dpkg or a download that fails), using code like
6777 this:
6778
6779 &lt;blockquote&gt;&lt;pre&gt;
6780 export DEBIAN_FRONTEND=noninteractive
6781 tasksel --new-install
6782 &lt;/pre&gt;&lt;/blockquote&gt;
6783
6784 This would invoke tasksel, let its automatic task selection pick the
6785 tasks to install, and continue to install the requested tasks without
6786 any output what so ever.
6787
6788 Recently I revisited this problem while working on the automatic
6789 package upgrade testing, because tasksel would some times hang without
6790 any useful feedback, and I want to see what is going on when it
6791 happen. Then it occured to me, I can parse the output from tasksel
6792 when asked to run in test mode, and use that aptitude command line
6793 printed by tasksel then to simulate the tasksel run. I ended up using
6794 code like this:
6795
6796 &lt;blockquote&gt;&lt;pre&gt;
6797 export DEBIAN_FRONTEND=noninteractive
6798 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6799 $cmd
6800 &lt;/pre&gt;&lt;/blockquote&gt;
6801
6802 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6803 --without-recommends -o APT::Install-Recommends=no -y install
6804 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6805 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6806 laptop task and all packages with priority standard , required and
6807 important, just like tasksel would have done it during
6808 installation.&lt;/p&gt;
6809
6810 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6811 install packages without using debconf-apt-progress, for use cases
6812 like this.&lt;/p&gt;
6813 </description>
6814 </item>
6815
6816 <item>
6817 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6818 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6819 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6820 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6821 <description>&lt;p&gt;My
6822 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6823 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6824 finally made the upgrade logs available from
6825 &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;.
6826 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6827 apt and aptitude, and found their differences interesting. This time
6828 I will only focus on their removal plans.&lt;/p&gt;
6829
6830 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6831 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6832 surprising part is that it want to remove xorg and all
6833 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6834 sure why. When asking aptitude to do the same, it want to remove 129
6835 packages, but most of them are library packages I suspect are no
6836 longer needed. Both of them want to remove bluetooth packages, which
6837 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6838
6839 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6840 which seem like a bad idea and xorg the same way as with Gnome. Asking
6841 aptitude for the same, it wants to remove 192 packages, none which are
6842 too surprising.&lt;/p&gt;
6843
6844 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6845 and avoided, and perhaps others as well. Here are the complete list
6846 of planned removals. The complete logs is available from the URL
6847 above. Note if you want to repeat these tests, that the upgrade test
6848 for kde+apt-get hung in the tasksel setup because of dpkg asking
6849 conffile questions. No idea why. I worked around it by using
6850 &#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
6851 continue.&lt;/p&gt;
6852
6853 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6854 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6855 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6856 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6857 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6858 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6859 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6860 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6861 xserver-xorg-input-kbd xserver-xorg-input-mouse
6862 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6863 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6864 xserver-xorg-video-ati xserver-xorg-video-chips
6865 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6866 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6867 xserver-xorg-video-glint xserver-xorg-video-i128
6868 xserver-xorg-video-i740 xserver-xorg-video-imstt
6869 xserver-xorg-video-intel xserver-xorg-video-mach64
6870 xserver-xorg-video-mga xserver-xorg-video-neomagic
6871 xserver-xorg-video-nsc xserver-xorg-video-nv
6872 xserver-xorg-video-openchrome xserver-xorg-video-r128
6873 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6874 xserver-xorg-video-rendition xserver-xorg-video-s3
6875 xserver-xorg-video-s3virge xserver-xorg-video-savage
6876 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6877 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6878 xserver-xorg-video-tga xserver-xorg-video-trident
6879 xserver-xorg-video-tseng xserver-xorg-video-v4l
6880 xserver-xorg-video-vesa xserver-xorg-video-vga
6881 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6882 xulrunner-1.9-gnome-support&lt;/p&gt;
6883
6884 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6885
6886 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6887 djvulibre-desktop finger gnome-app-install gnome-mount
6888 gnome-network-admin gnome-spell gnome-vfs-obexftp
6889 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6890 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6891 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6892 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6893 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6894 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6895 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6896 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6897 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6898 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6899 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6900 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6901 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6902 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6903 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6904 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6905 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6906 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6907 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6908 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6909 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6910 openoffice.org-writer2latex openssl-blacklist p7zip
6911 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6912 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6913 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6914 swfdec-mozilla totem-gstreamer update-manager wodim
6915 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6916 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6917 zip&lt;/p&gt;
6918
6919 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6920
6921 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6922 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6923 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6924 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6925 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6926 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6927 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6928 xserver-xorg-input-kbd xserver-xorg-input-mouse
6929 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6930 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6931 xserver-xorg-video-ati xserver-xorg-video-chips
6932 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6933 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6934 xserver-xorg-video-glint xserver-xorg-video-i128
6935 xserver-xorg-video-i740 xserver-xorg-video-imstt
6936 xserver-xorg-video-intel xserver-xorg-video-mach64
6937 xserver-xorg-video-mga xserver-xorg-video-neomagic
6938 xserver-xorg-video-nsc xserver-xorg-video-nv
6939 xserver-xorg-video-openchrome xserver-xorg-video-r128
6940 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6941 xserver-xorg-video-rendition xserver-xorg-video-s3
6942 xserver-xorg-video-s3virge xserver-xorg-video-savage
6943 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6944 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6945 xserver-xorg-video-tga xserver-xorg-video-trident
6946 xserver-xorg-video-tseng xserver-xorg-video-v4l
6947 xserver-xorg-video-vesa xserver-xorg-video-vga
6948 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6949
6950 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6951 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6952 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6953 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6954 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6955 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6956 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6957 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6958 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6959 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6960 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6961 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6962 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6963 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6964 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6965 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6966 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6967 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6968 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6969 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6970 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6971 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6972 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6973 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6974 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6975 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6976 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6977 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6978 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6979 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6980 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6981 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6982 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6983 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6984 texlive-common texlive-doc-base texlive-fonts-recommended
6985 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6986 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6987 xulrunner-1.9&lt;/p&gt;
6988
6989 </description>
6990 </item>
6991
6992 <item>
6993 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6994 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6996 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6997 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6998 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6999 have been discovered and reported in the process
7000 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7001 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7002 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7003 kdebase-workspace-data), and to get a more regular testing going on, I
7004 am working on a script to automate the test.&lt;/p&gt;
7005
7006 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7007 Gnome or KDE desktop installation inside the chroot before upgrading
7008 it. To ensure no services are started in the chroot, a policy-rc.d
7009 script is inserted. To make sure tasksel believe it is to install a
7010 desktop on a laptop, the tasksel tests are replaced in the chroot
7011 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7012
7013 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7014 currently always fail because udev refuses to upgrade with the kernel
7015 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7016 is created. The bug report
7017 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7018 this problem do not trigger in a chroot, but I touch the file anyway
7019 to make sure the upgrade go well. Testing on virtual and real
7020 hardware have failed me because of udev so far, and creating this file
7021 do the trick in such settings anyway. This is a
7022 &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
7023 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7024 maintainer because he lack the resources to rewrite udev to keep
7025 working with old kernels or something like that. I really wish the
7026 udev upstream would keep udev backwards compatible, to avoid such
7027 upgrade problem, but given that they fail to do so, I guess
7028 documenting the way out of this mess is the best option we got for
7029 Debian Squeeze.&lt;/p&gt;
7030
7031 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7032 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7033 trick:&lt;/p&gt;
7034
7035 &lt;blockquote&gt;&lt;pre&gt;
7036 #!/bin/sh
7037 set -ex
7038
7039 if [ &quot;$1&quot; ] ; then
7040 desktop=$1
7041 else
7042 desktop=gnome
7043 fi
7044
7045 from=lenny
7046 to=squeeze
7047
7048 exec &amp;lt; /dev/null
7049 unset LANG
7050 mirror=http://ftp.skolelinux.org/debian
7051 tmpdir=chroot-$from-upgrade-$to-$desktop
7052 fuser -mv .
7053 debootstrap $from $tmpdir $mirror
7054 chroot $tmpdir aptitude update
7055 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7056 #!/bin/sh
7057 exit 101
7058 EOF
7059 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7060 exit_cleanup() {
7061 umount $tmpdir/proc
7062 }
7063 mount -t proc proc $tmpdir/proc
7064 # Make sure proc is unmounted also on failure
7065 trap exit_cleanup EXIT INT
7066
7067 chroot $tmpdir aptitude -y install debconf-utils
7068
7069 # Make sure tasksel autoselection trigger. It need the test scripts
7070 # to return the correct answers.
7071 echo tasksel tasksel/desktop multiselect $desktop | \
7072 chroot $tmpdir debconf-set-selections
7073
7074 # Include the desktop and laptop task
7075 for test in desktop laptop ; do
7076 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7077 #!/bin/sh
7078 exit 2
7079 EOF
7080 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7081 done
7082
7083 DEBIAN_FRONTEND=noninteractive
7084 DEBIAN_PRIORITY=critical
7085 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7086 chroot $tmpdir tasksel --new-install
7087
7088 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7089 chroot $tmpdir aptitude update
7090 touch $tmpdir/etc/udev/kernel-upgrade
7091 chroot $tmpdir aptitude -y dist-upgrade
7092 fuser -mv
7093 &lt;/pre&gt;&lt;/blockquote&gt;
7094
7095 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7096 with aptitude, but I have not had time to look at how they behave
7097 differently so far. I hope to get a cron job running to do the test
7098 regularly and post the result on the web. The Gnome upgrade currently
7099 work, while the KDE upgrade fail because of the bug in
7100 kdebase-workspace-data&lt;/p&gt;
7101
7102 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7103 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7104 post, so I will refrain from trying. I can report that for Gnome,
7105 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7106 remove and 1 not upgraded and 1024MB need to be downloaded while for
7107 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7108 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7109
7110 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7111 is able to migrate to dependency based boot sequencing and parallel
7112 booting without a hitch. Was unsure if there were still bugs with
7113 packages failing to clean up their obsolete init.d script during
7114 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7115 packages.&lt;/p&gt;
7116 </description>
7117 </item>
7118
7119 <item>
7120 <title>Upstart or sysvinit - as init.d scripts see it</title>
7121 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7123 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7124 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7125 scripts to migrate (some of) their operations to upstart job while
7126 keeping the init.d for hurd and kfreebsd. The packages with such
7127 needs will need a way to get their init.d scripts to behave
7128 differently when used with sysvinit and with upstart. Because of
7129 this, I had a look at the environment variables set when a init.d
7130 script is running under upstart, and when it is not.&lt;/p&gt;
7131
7132 &lt;p&gt;With upstart, I notice these environment variables are set when a
7133 script is started from rcS.d/ (ignoring some irrelevant ones like
7134 COLUMNS):&lt;/p&gt;
7135
7136 &lt;blockquote&gt;&lt;pre&gt;
7137 DEFAULT_RUNLEVEL=2
7138 previous=N
7139 PREVLEVEL=
7140 RUNLEVEL=
7141 runlevel=S
7142 UPSTART_EVENTS=startup
7143 UPSTART_INSTANCE=
7144 UPSTART_JOB=rc-sysinit
7145 &lt;/pre&gt;&lt;/blockquote&gt;
7146
7147 &lt;p&gt;With sysvinit, these environment variables are set for the same
7148 script.&lt;/p&gt;
7149
7150 &lt;blockquote&gt;&lt;pre&gt;
7151 INIT_VERSION=sysvinit-2.88
7152 previous=N
7153 PREVLEVEL=N
7154 RUNLEVEL=S
7155 runlevel=S
7156 &lt;/pre&gt;&lt;/blockquote&gt;
7157
7158 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7159 sysvinit are not set by upstart. Not sure if it is intentional or not
7160 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7161
7162 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7163 looking for the UPSTART_JOB environment variable seem to be a good
7164 choice.&lt;/p&gt;
7165 </description>
7166 </item>
7167
7168 <item>
7169 <title>A manual for standards wars...</title>
7170 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7171 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7172 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7173 <description>&lt;p&gt;Via the
7174 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7175 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7176 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7177 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7178 following the standards wars of today.&lt;/p&gt;
7179 </description>
7180 </item>
7181
7182 <item>
7183 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7184 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7186 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7187 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7188 to get a list of the machine types in use thanks to the DMI
7189 information extracted from each machine. The script to do so is
7190 included in the sitesummary package, and here is example output from
7191 the Skolelinux build servers:&lt;/p&gt;
7192
7193 &lt;blockquote&gt;&lt;pre&gt;
7194 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7195 vendor count
7196 Dell Computer Corporation 1
7197 PowerEdge 1750 1
7198 IBM 1
7199 eserver xSeries 345 -[8670M1X]- 1
7200 Intel 2
7201 [no-dmi-info] 3
7202 maintainer:~#
7203 &lt;/pre&gt;&lt;/blockquote&gt;
7204
7205 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7206 provided in each machine. Here there are Intel machines without model
7207 information listed with Intel as vendor and no model, and virtual Xen
7208 machines listed as [no-dmi-info]. One can add -l as a command line
7209 option to list the individual machines.&lt;/p&gt;
7210
7211 &lt;p&gt;A larger list is
7212 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7213 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7214 provide the basic sitesummary report publicly. In their report there
7215 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7216 their machines, and as sitesummary is available in both distributions,
7217 it is trivial to get all of them to report to the same central
7218 collector.&lt;/p&gt;
7219 </description>
7220 </item>
7221
7222 <item>
7223 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7224 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7225 <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>
7226 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7227 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7228 start at boot when an NVidia video card is used is handled. The
7229 problem seem to be that the nvidia X.org driver uses a long time to
7230 initialize, and this duration is longer than kdm is configured to
7231 wait.&lt;/p&gt;
7232
7233 &lt;p&gt;I came across two bugs related to this issue,
7234 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7235 against initscripts and passed on to nvidia-glx when it became obvious
7236 that the nvidia drivers were involved, and
7237 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7238 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7239
7240 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7241 problem nvidia video card owners experience and make sure the Debian
7242 distribution work out of the box for these users. The nvidia driver
7243 maintainers expect kdm to be set up to wait longer, while kdm expect
7244 the nvidia driver maintainers to fix the driver to start faster, and
7245 while they wait for each other I guess the users end up switching to a
7246 distribution that work for them. I have no idea what the solution is,
7247 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7248
7249 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7250 </description>
7251 </item>
7252
7253 <item>
7254 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7255 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7256 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7257 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7258 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7259 The feature seem to hold up pretty well, but three fairly serious
7260 issues are known and should be solved:
7261
7262 &lt;p&gt;&lt;ul&gt;
7263
7264 &lt;li&gt;The wicd package seen to
7265 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7266 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7267 parallel booting is enabled. No idea why, but the wicd maintainer
7268 seem to be on the case.&lt;/li&gt;
7269
7270 &lt;li&gt;The nvidia X driver seem to
7271 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7272 triggered more easily when parallel booting is in effect. The
7273 maintainer is on the case.&lt;/li&gt;
7274
7275 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7276 sequencing (the shutdown is broken) when old file-rc users
7277 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7278 sysv-rc. One way to solve it would be for file-rc to create
7279 /etc/init.d/.legacy-bootordering, and another is to try to make
7280 sysv-rc more robust. Will investigate some more and probably upload a
7281 workaround in sysv-rc to help those trying to move from file-rc to
7282 sysv-rc get a working shutdown.&lt;/li&gt;
7283
7284 &lt;/ul&gt;&lt;/p&gt;
7285
7286 &lt;p&gt;All in all not many surprising issues, and all of them seem
7287 solvable before Squeeze is released. In addition to these there are
7288 some packages with bugs in their dependencies and run level settings,
7289 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7290
7291 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7292 the BTS, please usertag the report to get it to show up at
7293 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7294 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7295
7296 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7297 </description>
7298 </item>
7299
7300 <item>
7301 <title>More flexible firmware handling in debian-installer</title>
7302 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7304 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7305 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7306 found time today to return to the project. Having to spend less time
7307 working dependency based boot in debian, as it is almost complete now,
7308 definitely helped freeing some time.&lt;/p&gt;
7309
7310 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7311 include some firmware packages on the Debian Edu CDs, those needed to
7312 get disk and network controllers working. Without having these
7313 firmware packages available during installation, it is impossible to
7314 install Debian Edu on the given machine, and because our target group
7315 are non-technical people, asking them to provide firmware packages on
7316 an external medium is a support pain. Initially, I expected it to be
7317 enough to include the firmware packages on the CD to get
7318 debian-installer to find and use them. This proved to be wrong.
7319 Next, I hoped it was enough to symlink the relevant firmware packages
7320 to some useful location on the CD (tried /cdrom/ and
7321 /cdrom/firmware/). This also proved to not work, and at this point I
7322 found time to look at the debian-installer code to figure out what was
7323 going to work.&lt;/p&gt;
7324
7325 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7326 look revealed that it would only look for firmware packages outside
7327 the installation media, so the CD was never checked for firmware
7328 packages. It would only check USB sticks, floppies and other
7329 &quot;external&quot; media devices. Today I changed it to also look in the
7330 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7331 solve the problem I ran into with Debian edu. I also changed it to
7332 look in /firmware/, to make sure the installer also find firmware
7333 provided in the initrd when booting the installer via PXE, to allow us
7334 to provide the same feature in the PXE setup included in Debian
7335 Edu.&lt;/p&gt;
7336
7337 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7338 activated without asking if the license is accepted, I extended
7339 hw-detect to look for preinst scripts in the firmware packages, and
7340 run these before activating the firmware during installation. The
7341 license question is asked using debconf in the preinst, so this should
7342 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7343
7344 &lt;p&gt;If you want to discuss the details of these features, please
7345 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7346 </description>
7347 </item>
7348
7349 <item>
7350 <title>Parallellized boot is now the default in Debian/unstable</title>
7351 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7352 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7353 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7354 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7355 Debian/unstable for machines using dependency based boot sequencing.
7356 Apparently the testing of concurrent booting has been wider than
7357 expected, if I am to believe the
7358 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7359 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7360 with the feature this weekend, to give us some time to detect any
7361 remaining problems before Squeeze is frozen. If serious problems are
7362 detected, it is simple to change the default back to sequential boot.
7363 The upload of the new sysvinit package also activate a new upstream
7364 version.&lt;/p&gt;
7365
7366 More information about
7367 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7368 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7369 currently possible to disable parallel booting when one run into
7370 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7371
7372 &lt;blockquote&gt;&lt;pre&gt;
7373 CONCURRENCY=none
7374 &lt;/pre&gt;&lt;/blockquote&gt;
7375
7376 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7377 the BTS, please usertag the report to get it to show up at
7378 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7379 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7380 </description>
7381 </item>
7382
7383 <item>
7384 <title>Sitesummary tip: Listing MAC address of all clients</title>
7385 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7386 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7387 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7388 <description>&lt;p&gt;In the recent Debian Edu versions, the
7389 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7390 system&lt;/a&gt; is used to keep track of the machines in the school
7391 network. Each machine will automatically report its status to the
7392 central server after boot and once per night. The network setup is
7393 also reported, and using this information it is possible to get the
7394 MAC address of all network interfaces in the machines. This is useful
7395 to update the DHCP configuration.&lt;/p&gt;
7396
7397 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7398 ist all MAC addresses of all machines reporting to sitesummary. Run
7399 this on the collector host:&lt;/p&gt;
7400
7401 &lt;blockquote&gt;&lt;pre&gt;
7402 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7403 &lt;/pre&gt;&lt;/blockquote&gt;
7404
7405 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7406 line per machine and with space between the MAC addresses.&lt;/p&gt;
7407
7408 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7409 addresses for hosts, it would be possible to extend this to fetch
7410 machine information from sitesummary and update the DHCP and DNS
7411 tables in LDAP using this information. Such tool is unfortunately not
7412 written yet.&lt;/p&gt;
7413 </description>
7414 </item>
7415
7416 <item>
7417 <title>systemd, an interesting alternative to upstart</title>
7418 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7419 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7420 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7421 <description>&lt;p&gt;The last few days a new boot system called
7422 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7423 has been
7424 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7425
7426 to the free software world. I have not yet had time to play around
7427 with it, but it seem to be a very interesting alternative to
7428 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7429 a good alternative for Debian when we are able to switch to an event
7430 based boot system. Tollef is
7431 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7432 systemd into Debian, and I look forward to seeing how well it work. I
7433 like the fact that systemd handles init.d scripts with dependency
7434 information natively, allowing them to run in parallel where upstart
7435 at the moment do not.&lt;/p&gt;
7436
7437 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7438 platform support. It only work on recent Linux kernels, and also need
7439 some new kernel features enabled to function properly. This means
7440 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7441 system. Not sure how that will be handled if systemd proves to be the
7442 way forward.&lt;/p&gt;
7443
7444 &lt;p&gt;In the mean time, based on the
7445 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7446 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7447 decided to enable full parallel booting as the default in Debian as
7448 soon as possible (probably this weekend or early next week), to see if
7449 there are any remaining serious bugs in the init.d dependencies. A
7450 new version of the sysvinit package implementing this change is
7451 already in experimental. If all go well, Squeeze will be released
7452 with parallel booting enabled by default.&lt;/p&gt;
7453 </description>
7454 </item>
7455
7456 <item>
7457 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7458 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7460 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7461 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7462 complete, so complete that it is actually possible to run all the
7463 init.d scripts in parallell based on these dependencies. If you want
7464 to test your Squeeze system, make sure
7465 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7466 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7467 /etc/default/rcS:&lt;/p&gt;
7468
7469 &lt;blockquote&gt;&lt;pre&gt;
7470 CONCURRENCY=makefile
7471 &lt;/pre&gt;&lt;/blockquote&gt;
7472
7473 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7474 scripts in parallel using the dependency information stored in
7475 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7476 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7477 to try to start the kdm and gdm scripts as early as possible, and will
7478 start the facilities required by kdm or gdm as early as possible to
7479 make this happen.&lt;/p&gt;
7480
7481 &lt;p&gt;Give it a try, and see if you like the result. If some services
7482 fail to start properly, it is most likely because they have incomplete
7483 init.d script dependencies in their startup script (or some of their
7484 dependent scripts have incomplete dependencies). Report bugs and get
7485 the package maintainers to fix it. :)&lt;/p&gt;
7486
7487 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7488 manage to get the init.d script dependencies complete and correct. I
7489 expect we will get there in Squeeze+1, if we get manage to test and
7490 fix the remaining issues.&lt;/p&gt;
7491
7492 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7493 the BTS, please usertag the report to get it to show up at
7494 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7495 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7496 </description>
7497 </item>
7498
7499 <item>
7500 <title>Debian has switched to dependency based boot sequencing</title>
7501 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7502 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7503 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7504 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7505 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7506 have been migrated to using dependency based boot sequencing. This
7507 conclude work me and others have been doing for the last three days.
7508 It feels great to see this finally part of the default Debian
7509 installation. Now we just need to weed out the last few problems that
7510 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7511
7512 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7513 fixing the more fundamental problem of handing the event based
7514 non-predictable kernel in the early boot.&lt;/p&gt;
7515 </description>
7516 </item>
7517
7518 <item>
7519 <title>Taking over sysvinit development</title>
7520 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7521 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7522 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7523 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7524 the existing sysvinit upstream developer, I decided a few weeks ago to
7525 take over the package and become the new upstream. The number of
7526 patches to track for the Debian package was becoming a burden, and the
7527 lack of synchronization between the distribution made it hard to keep
7528 the package up to date.&lt;/p&gt;
7529
7530 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7531 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7532 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7533 and Fedora), based on the patches currently in use in these
7534 distributions. We Debian maintainers plan to move to this tarball as
7535 the new upstream as soon as we find time to do the merge. Since the
7536 new tarball was created, we agreed with Werner at SuSe to make a new
7537 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7538 development there. The project is registered and currently waiting
7539 for approval by the Savannah administrators, and as soon as it is
7540 approved, we will import the old versions from svn and continue
7541 working on the future release.&lt;/p&gt;
7542
7543 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7544 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7545 </description>
7546 </item>
7547
7548 <item>
7549 <title>Debian boots quicker and quicker</title>
7550 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7551 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7552 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7553 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7554 people involved in the boot system on Debian and Ubuntu, to see if we
7555 could find more ways to speed up the boot system. This was an Ubuntu
7556 funded
7557 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7558 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7559 of boot systems, and ways to handle the increasing number of boot
7560 issues introduced by the Linux kernel becoming more and more
7561 asynchronous and event base. The Ubuntu approach using udev and
7562 upstart might be a good way forward. Time will show.&lt;/p&gt;
7563
7564 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7565 process in Debian. All of these should be applied to get a quick
7566 boot:&lt;/p&gt;
7567
7568 &lt;ul&gt;
7569
7570 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7571
7572 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7573 clock is in UTC.&lt;/li&gt;
7574
7575 &lt;li&gt;Install and activate the insserv package to enable
7576 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7577 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7578
7579 &lt;/ul&gt;
7580
7581 These points are based on the Google summer of code work done by
7582 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7583 Villegas&lt;/a&gt;.
7584
7585 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7586 unstable yesterday. When we tested it, we were able to cut 6 seconds
7587 from the boot sequence. It depend on very correct dependency
7588 declaration in all init.d scripts, so I expect us to find edge cases
7589 where the dependences in some scripts are slightly wrong when we start
7590 using this.&lt;/p&gt;
7591
7592 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7593 introduced by Raphael Geissert today, one that could affect the
7594 startup speed as well. Instead of starting some scripts concurrently
7595 from rcS.d/ and another set of scripts from rc2.d/, it would be
7596 possible to run a of them in the same process. A quick way to test
7597 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7598 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7599 </description>
7600 </item>
7601
7602 <item>
7603 <title>BSAs påstander om piratkopiering møter motstand</title>
7604 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7605 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7606 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7607 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7608 programvareselskapene som Microsoft og Apple, publisert en rapport der
7609 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7610 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7611 dager siden kom
7612 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7613 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7614 dagene. Et spesielt interessant kommentar fra Sverige,
7615 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7616 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7617
7618 &lt;blockquote&gt;
7619 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7620 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7621 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7622 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7623 &lt;/blockquote&gt;
7624
7625 &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
7626 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7627 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7628 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7629 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7630
7631 &lt;p&gt;Fant lenkene via &lt;a
7632 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7633 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7634 </description>
7635 </item>
7636
7637 <item>
7638 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7639 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7640 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7641 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7642 <description>&lt;p&gt;Kom over
7643 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7644 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7645 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7646 jobber til daglig. En rask opptelling forteller meg at vi har 490
7647 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7648 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7649 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7650 </description>
7651 </item>
7652
7653 <item>
7654 <title>Kryptert harddisk - naturligvis</title>
7655 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7656 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7657 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7658 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7659 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7660 når en tar tap av arbeidstid, fortrolige dokumenter,
7661 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7662 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7663 til at jeg har kryptert harddisken på både kontormaskinen og min
7664 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7665 komme på avveie, den første informasjon relatert til jobben min ved
7666 Universitetet i Oslo, og den andre relatert til blant annet
7667 foreningsarbeide. Kryptering av diskene gjør at det er lite
7668 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7669 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7670 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7671 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7672 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7673 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7674 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7675 det er gjort slik jeg gjør det er minimale, og gevinstene er
7676 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7677 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7678
7679 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7680 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7681 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7682 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7683 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7684 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7685 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7686 betydelige.&lt;/p&gt;
7687 </description>
7688 </item>
7689
7690 <item>
7691 <title>Two projects that have improved the quality of free software a lot</title>
7692 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7693 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7694 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7695 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7696 quality of free software, and I wanted to mention both in case someone
7697 do not yet know them.&lt;/p&gt;
7698
7699 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7700 tool to detect and expose errors in the memory handling of programs.
7701 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7702 and it will report any problems on stdout. It is even better if the
7703 program include debug information. With debug information, it is able
7704 to report the source file name and line number where the problem
7705 occurs. It can report things like &#39;reading past memory block in file
7706 X line N, the memory block was allocated in file Y, line M&#39;, and
7707 &#39;using uninitialised value in control logic&#39;. This tool has made it
7708 trivial to investigate reproducible crash bugs in programs, and have
7709 reduced the number of this kind of bugs in free software a lot.
7710
7711 &lt;p&gt;The second one is
7712 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7713 a source code checker. It is able to process the source of a program
7714 and find problems in the logic without running the program. It
7715 started out as the Stanford Checker and became well known when it was
7716 used to find bugs in the Linux kernel. It is now a commercial tool
7717 and the company behind it is running
7718 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7719 free software community, where a lot of free software projects get
7720 their source checked for free. Several thousand defects have been
7721 found and fixed so far. It can find errors like &#39;lock L taken in file
7722 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7723 Y lines O to P can never be executed&#39;. The projects included in the
7724 community service project have managed to get rid of a lot of
7725 reliability problems thanks to Coverity.&lt;/p&gt;
7726
7727 &lt;p&gt;I believe tools like this, that are able to automatically find
7728 errors in the source, are vital to improve the quality of software and
7729 make sure we can get rid of the crashing and failing software we are
7730 surrounded by today.&lt;/p&gt;
7731 </description>
7732 </item>
7733
7734 <item>
7735 <title>No patch is not better than a useless patch</title>
7736 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7737 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7738 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7739 <description>&lt;p&gt;Julien Blache
7740 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7741 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7742 patch allow one to discuss a concrete and proposed solution, and also
7743 prove that the issue at hand is important enough for someone to spent
7744 time on fixing it. No patch do not provide any of these positive
7745 properties.&lt;/p&gt;
7746 </description>
7747 </item>
7748
7749 <item>
7750 <title>Standardize on protocols and formats, not vendors and applications</title>
7751 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7752 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7753 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7754 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7755 very good one to form a long lived computer infrastructure. It is the
7756 simple one, lost by many in todays computer industry: Standardize on
7757 open network protocols and open exchange/storage formats, not applications.
7758 Applications come and go, while protocols and files tend to stay, and
7759 thus one want to make it easy to change application and vendor, while
7760 avoiding conversion costs and locking users to a specific platform or
7761 application.&lt;/p&gt;
7762
7763 &lt;p&gt;This approach make it possible to replace the client applications
7764 independently of the server applications. One can even allow users to
7765 use several different applications as long as they handle the selected
7766 protocol and format. In the normal case, only one client application
7767 is recommended and users only get help if they choose to use this
7768 application, but those that want to deviate from the easy path are not
7769 blocked from doing so.&lt;/p&gt;
7770
7771 &lt;p&gt;It also allow us to replace the server side without forcing the
7772 users to replace their applications, and thus allow us to select the
7773 best server implementation at any moment, when scale and resouce
7774 requirements change.&lt;/p&gt;
7775
7776 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7777 open formats, but I would never recommend standardizing on a single
7778 application that do not use open network protocol or open formats.&lt;/p&gt;
7779 </description>
7780 </item>
7781
7782 <item>
7783 <title>Returning from Skolelinux developer gathering</title>
7784 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7785 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7786 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7787 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7788 Edu/Skolelinux development gathering. I got a bit done tuning the
7789 desktop, and looked into the dynamic service location protocol
7790 implementation avahi. It look like it could be useful for us. Almost
7791 30 people participated, and I believe it was a great environment to
7792 get to know the Skolelinux system. Walter Bender, involved in the
7793 development of the Sugar educational platform, presented his stuff and
7794 also helped me improve my OLPC installation. He also showed me that
7795 his Turtle Art application can be used in standalone mode, and we
7796 agreed that I would help getting it packaged for Debian. As a
7797 standalone application it would be great for Debian Edu. We also
7798 tried to get the video conferencing working with two OLPCs, but that
7799 proved to be too hard for us. The application seem to need more work
7800 before it is ready for me. I look forward to getting home and relax
7801 now. :)&lt;/p&gt;
7802 </description>
7803 </item>
7804
7805 <item>
7806 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7807 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7808 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7809 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7810 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7811 optimal. There is RFC 2307 documenting one way to store NIS maps in
7812 LDAP, and a modified version of this normally called RFC 2307bis, with
7813 some modifications to be compatible with Active Directory. The RFC
7814 specification handle the content of a lot of system databases, but do
7815 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7816
7817 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7818 we would like to store information about users, SMB clients/hosts,
7819 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7820 and LTSP configuration in LDAP. These objects have a lot in common,
7821 but with the current LDAP schemas it is not possible to have one
7822 object per entity. For example, one need to have at least three LDAP
7823 objects for a given computer, one with the SMB related stuff, one with
7824 DNS information and another with DHCP information. The schemas
7825 provided for DNS and DHCP are impossible to combine into one LDAP
7826 object. In addition, it is impossible to implement quick queries for
7827 netgroup membership, because of the way NIS triples are implemented.
7828 It just do not scale. I believe it is time for a few RFC
7829 specifications to cleam up this mess.&lt;/p&gt;
7830
7831 &lt;p&gt;I would like to have one LDAP object representing each computer in
7832 the network, and this object can then keep the SMB (ie host key), DHCP
7833 (mac address/name) and DNS (name/IP address) settings in one place.
7834 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7835
7836 &lt;p&gt;I would also like to have a quick way to map from a user or
7837 computer and to the net group this user or computer is a member.&lt;/p&gt;
7838
7839 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7840 in this regard, and the unix side need to catch up. Time to start a
7841 new IETF work group?&lt;/p&gt;
7842 </description>
7843 </item>
7844
7845 <item>
7846 <title>Endelig er Debian Lenny gitt ut</title>
7847 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7848 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7849 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7850 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7851 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7852 Et langt steg videre for Debian-prosjektet, og en rekke nye
7853 programpakker blir nå tilgjengelig for de av oss som bruker den
7854 stabile utgaven av Debian. Neste steg er nå å få
7855 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7856 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7857 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7858 slippes løs på skolene. Takk til alle debian-utviklerne som har
7859 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7860 bootsekvens tilgjengelig i stabil utgave, vha pakken
7861 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7862 </description>
7863 </item>
7864
7865 <item>
7866 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7867 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7868 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7869 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7870 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7871 Oslo. Most of Saturday was used for the general assemly for the
7872 member organization, but the rest of the weekend I used to tune the
7873 LTSP installation. LTSP now work out of the box on the 10-network.
7874 Acer Aspire One proved to be a very nice thin client, with both
7875 screen, mouse and keybard in a small box. Was working on getting the
7876 diskless workstation setup configured out of the box, but did not
7877 finish it before the weekend was up.&lt;/p&gt;
7878
7879 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7880 the Brazilian group, so that will have to wait for the next
7881 development gathering. Would love to have the Debian Edu installer
7882 automatically detect and configure a multiseat setup when it find one
7883 of these cards.&lt;/p&gt;
7884 </description>
7885 </item>
7886
7887 <item>
7888 <title>The sorry state of multimedia browser plugins in Debian</title>
7889 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7890 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7891 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7892 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7893 plugins available in Debian Lenny, to see which one we should use by
7894 default in Debian Edu. We need an embedded video playing plugin with
7895 control buttons to pause or stop the video, and capable of streaming
7896 all the multimedia content available on the web. The test results and
7897 notes are available on
7898 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7899 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7900 fill this need. My personal video player favorite, VLC, has a really
7901 bad plugin which fail on a lot of the test pages. A lot of the MIME
7902 types I would expect to work with any free software player (like
7903 video/ogg), just do not work. And simple formats like the
7904 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7905 totem and vlc plugins. I hope the situation will improve soon. No
7906 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7907
7908 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7909 be the only one fitting our needs. :/&lt;/p&gt;
7910 </description>
7911 </item>
7912
7913 </channel>
7914 </rss>