]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
b9e70406dae170adca2670115e551fd28ac41325
[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 capasity. My
43 colletor 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 parallell.
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 mylaptop
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 </description>
138 </item>
139
140 <item>
141 <title>New laptop - some more clues and ideas based on feedback</title>
142 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
143 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
144 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
145 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
146 need for a new laptop, and provided very useful feedback. I wish to
147 thank every one of these. Several pointed me to the possibility of
148 fixing my X230, and I am already in the process of getting Lenovo to
149 do so thanks to the on site, next day support contract covering the
150 machine. But the battery is almost useless (I expect to replace it
151 with a non-official battery) and I do not expect the machine to live
152 for many more years, so it is time to plan its replacement. If I did
153 not have a support contract, it was suggested to find replacement parts
154 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
155 might present a language barrier as I do not understand French.&lt;/p&gt;
156
157 &lt;p&gt;One tip I got was to use the
158 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
159 compare laptop models. It seem to have more models available than
160 prisjakt.no. Another tip I got from someone I know have similar
161 keyboard preferences was that the HP EliteBook 840 keyboard is not
162 very good, and this matches my experience with earlier EliteBook
163 keyboards I tested. Because of this, I will not consider it any further.
164
165 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
166 newest Thinkpad X model. The keyboard reintroduces mouse buttons
167 (which is missing from the X240), and is working fairly well with
168 Debian Sid/Unstable according to
169 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
170 got on the keyboard quality are not consistent. Some say the keyboard
171 is good, others say it is ok, while others say it is not very good.
172 Those with experience from X41 and and X60 agree that the X250
173 keyboard is not as good as those trusty old laptops, and suggest I
174 keep and fix my X230 instead of upgrading, or get a used X230 to
175 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
176 activity and battery status, which is very convenient on my X230. I&#39;m
177 also told that the CPU fan is running very often, making it a bit
178 noisy. In any case, the X250 do not work out of the box with Debian
179 Stable/Jessie, one of my requirements.&lt;/p&gt;
180
181 &lt;p&gt;I have also gotten a few vendor proposals, one was
182 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
183 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
184 The latter look very attractive to me.&lt;/p&gt;
185
186 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
187 as I keep looking for a replacement.&lt;/p&gt;
188
189 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
190 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
191 different
192 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
193 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
194 </description>
195 </item>
196
197 <item>
198 <title>Time to find a new laptop, as the old one is broken after only two years</title>
199 <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>
200 <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>
201 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
202 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
203 replacement soon. The left 5 cm of the screen on my Thinkpad X230
204 started flickering yesterday, and I suspect the cause is a broken
205 cable, as changing the angle of the screen some times get rid of the
206 flickering.&lt;/p&gt;
207
208 &lt;p&gt;My requirements have not really changed since I bought it, and is
209 still as
210 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
211 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
212 good help from
213 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
214 where I could select at least a few of the requirements (mouse pin,
215 wifi, weight) and go through the rest manually. Three button mouse
216 and a good keyboard is not available as an option, and all the three
217 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
218 G2) lack three mouse buttons). It is also unclear to me how good the
219 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
220 the keyboard, even if the quality and robustness in the X series have
221 deteriorated since X41.&lt;/p&gt;
222
223 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
224 seem sensible to me? Are there better services around to search the
225 set of available laptops for features? Please send me an email if you
226 have suggestions.&lt;/p&gt;
227
228 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
229 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
230 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
231 </description>
232 </item>
233
234 <item>
235 <title>How to stay with sysvinit in Debian Jessie</title>
236 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
237 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
238 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
239 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
240 sysvinit as its boot system by default. But how can one keep using
241 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
242 courtesy of
243 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
244 Schubert&lt;/a&gt; and
245 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
246 McVittie&lt;/a&gt;.
247
248 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
249 keep sysvinit as your boot system, create a file
250 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
251 you upgrade:&lt;/p&gt;
252
253 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
254 Package: systemd-sysv
255 Pin: release o=Debian
256 Pin-Priority: -1
257 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
258
259 &lt;p&gt;This file content will tell apt and aptitude to not consider
260 installing systemd-sysv as part of any installation and upgrade
261 solution when resolving dependencies, and thus tell it to avoid
262 systemd as a default boot system. The end result should be that the
263 upgraded system keep using sysvinit.&lt;/p&gt;
264
265 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
266 get sysvinit installed by default (debootstrap used by
267 debian-installer have no option for this), but one can tell the
268 installer to switch to sysvinit before the first boot. Either by
269 using a kernel argument to the installer, or by adding a line to the
270 preseed file used. First, the kernel command line argument:
271
272 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
273 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
274 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
275
276 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
277
278 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
279 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
280 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
281
282 &lt;p&gt;One can of course also do this after the first boot by installing
283 the sysvinit-core package.&lt;/p&gt;
284
285 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
286 sysvinit boot sequence in Debian have several hardware specific bugs
287 on Linux caused by the fact that it is unpredictable when hardware
288 devices show up during boot. But on the other hand, the new default
289 boot system still have a few rough edges I hope will be fixed before
290 Jessie is released.&lt;/p&gt;
291
292 &lt;p&gt;Update 2014-11-26: Inspired by
293 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
294 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
295 line.&lt;/p&gt;
296 </description>
297 </item>
298
299 <item>
300 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
301 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
302 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
303 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
304 <description>&lt;p&gt;The right to communicate with your friends and family in private,
305 without anyone snooping, is a right every citicen have in a liberal
306 democracy. But this right is under serious attack these days.&lt;/p&gt;
307
308 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
309 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
310 the whisleblower Snowden) more expensive for Internet email,
311 is to deliver all email using SMTP via Tor. Such SMTP option would be
312 a nice addition to the FreedomBox project if we could send email
313 between FreedomBox machines without leaking metadata about the emails
314 to the people peeking on the wire. I
315 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
316 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
317 lot of useful feedback and suggestions. It also became obvious to me
318 that this was not a novel idea, as the same idea was tested and
319 documented by Johannes Berg as early as 2006, and both
320 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
321 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
322 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
323
324 &lt;p&gt;To implement such system one need to set up a Tor hidden service
325 providing the SMTP protocol on port 25, and use email addresses
326 looking like username@hidden-service-name.onion. With such addresses
327 the connections to port 25 on hidden-service-name.onion using Tor will
328 go to the correct SMTP server. To do this, one need to configure the
329 Tor daemon to provide the hidden service and the mail server to accept
330 emails for this .onion domain. To learn more about Exim configuration
331 in Debian and test the design provided by Johannes Berg in his FAQ, I
332 set out yesterday to create a Debian package for making it trivial to
333 set up such SMTP over Tor service based on Debian. Getting it to work
334 were fairly easy, and
335 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
336 source code for the Debian package&lt;/a&gt; is available from github. I
337 plan to move it into Debian if further testing prove this to be a
338 useful approach.&lt;/p&gt;
339
340 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
341 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
342 get rid of exim4). Install tor, clone the git repository mentioned
343 above, build the deb and install it on the machine. Next, run
344 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
345 the instructions to get the service up and running. Restart tor and
346 exim when it is done, and test mail delivery using swaks like
347 this:&lt;/p&gt;
348
349 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
350 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
351 --to fbx@dutlqrrmjhtfa3vp.onion
352 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
353
354 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
355 address with your own address to test your server. :)&lt;/p&gt;
356
357 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
358 easier and more automatic. Especially the tor setup need more work.
359 Also, the package include a tor-smtp tool written in C, but its task
360 should probably be rewritten in some script language to make the deb
361 architecture independent. It would probably also make the code easier
362 to review. The tor-smtp tool currently need to listen on a socket for
363 exim to talk to it and is started using xinetd. It would be better if
364 no daemon and no socket is needed. I suspect it is possible to get
365 exim to run a command line tool for delivery instead of talking to a
366 socket, and hope to figure out how in a future version of this
367 system.&lt;/p&gt;
368
369 &lt;p&gt;Until I wipe my test machine, I can be reached using the
370 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
371 SMTorP. :)&lt;/p&gt;
372 </description>
373 </item>
374
375 <item>
376 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
377 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
378 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
379 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
380 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
381 alioth.debian.org, you know the web interface is fairly slow to
382 operate. First you visit one web page, enter the moderation password
383 and get a new page shown with a list of all the messages to moderate
384 and various options for each email address. This take a while for
385 every list you moderate, and you need to do it regularly to do a good
386 job as a list moderator. But there is a quick alternative,
387 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
388 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
389 to moderate in a fraction of a second. Here is a test run on two
390 lists I recently took over:&lt;/p&gt;
391
392 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
393 % time listadmin xiph
394 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
395 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
396
397 real 0m1.709s
398 user 0m0.232s
399 sys 0m0.012s
400 %
401 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
402
403 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
404 there are no message in the moderation queue. Every morning I
405 currently moderate 68 mailman lists, and it normally take around two
406 minutes. When I took over the two pkg-xiph lists above a few days
407 ago, there were 400 emails waiting in the moderator queue. It took me
408 less than 15 minutes to process them all using the listadmin
409 program.&lt;/p&gt;
410
411 &lt;p&gt;If you install
412 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
413 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
414 with content like this, the moderation task is a breeze:&lt;/p&gt;
415
416 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
417 username username@example.org
418 spamlevel 23
419 default discard
420 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
421
422 password secret
423 adminurl https://{domain}/mailman/admindb/{list}
424 mailman-list@lists.example.com
425
426 password hidden
427 other-list@otherserver.example.org
428 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
429
430 &lt;p&gt;There are other options to set as well. Check the manual page to
431 learn the details.&lt;/p&gt;
432
433 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
434 the SSL certificate is self signed or not properly signed by a
435 generally accepted signing authority, you can set a environment
436 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
437
438 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
439 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
440 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
441
442 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
443 can provide an argument to the listadmin script like I do in the
444 initial screen dump (the xiph argument). Using an argument, only
445 lists matching the argument string will be processed. This make it
446 quick to accept messages if you notice the moderation request in your
447 email.&lt;/p&gt;
448
449 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
450 mailing lists, as I simply do not have time to spend on that if the
451 process was any slower. The listadmin program have saved me hours of
452 time I could spend elsewhere over the years. It truly is nice free
453 software.&lt;/p&gt;
454
455 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
456 activities, please send Bitcoin donations to my address
457 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
458
459 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
460 configuration example. Also, I&#39;ve been told that the
461 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
462 sure why.&lt;/p&gt;
463 </description>
464 </item>
465
466 <item>
467 <title>Debian Jessie, PXE and automatic firmware installation</title>
468 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
469 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
470 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
471 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
472 problem that the WiFi card require some firmware to work properly.
473 And it has been a pain to fix this using preseeding in Debian.
474 Normally something more is needed. But thanks to
475 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
476 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
477 to do this using simple preseeding.&lt;/p&gt;
478
479 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
480 firmware for the hardware found in the machine (actually, requested by
481 the kernel modules for the hardware). (It can also install user space
482 programs supporting the hardware detected, but that is not the focus
483 of this story.)&lt;/p&gt;
484
485 &lt;p&gt;To get this working in the default installation, two preeseding
486 values are needed. First, the isenkram-cli package must be installed
487 into the target chroot (aka the hard drive) before tasksel is executed
488 in the pkgsel step of the debian-installer system. This is done by
489 preseeding the base-installer/includes debconf value to include the
490 isenkram-cli package. The package name is next passed to debootstrap
491 for installation. With the isenkram-cli package in place, tasksel
492 will automatically use the isenkram tasks to detect hardware specific
493 packages for the machine being installed and install them, because
494 isenkram-cli contain tasksel tasks.&lt;/p&gt;
495
496 &lt;p&gt;Second, one need to enable the non-free APT repository, because
497 most firmware unfortunately is non-free. This is done by preseeding
498 the apt-mirror-setup step. This is unfortunate, but for a lot of
499 hardware it is the only option in Debian.&lt;/p&gt;
500
501 &lt;p&gt;The end result is two lines needed in your preseeding file to get
502 firmware installed automatically by the installer:&lt;/p&gt;
503
504 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
505 base-installer base-installer/includes string isenkram-cli
506 apt-mirror-setup apt-setup/non-free boolean true
507 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
508
509 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
510 both firmware and user space packages when using this method. It also
511 do not work well, so use version 0.15 or later. Installing both
512 firmware and user space packages might give you a bit more than you
513 want, so I decided to split the tasksel task in two, one for firmware
514 and one for user space programs. The firmware task is enabled by
515 default, while the one for user space programs is not. This split is
516 implemented in the package currently in unstable.&lt;/p&gt;
517
518 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
519 this recipe work for you. :)&lt;/p&gt;
520
521 &lt;p&gt;So, I bet you are wondering, how can this work. First and
522 foremost, it work because tasksel is modular, and driven by whatever
523 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
524 isenkram-cli package place two files for tasksel to find. First there
525 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
526
527 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
528 Task: isenkram-packages
529 Section: hardware
530 Description: Hardware specific packages (autodetected by isenkram)
531 Based on the detected hardware various hardware specific packages are
532 proposed.
533 Test-new-install: show show
534 Relevance: 8
535 Packages: for-current-hardware
536
537 Task: isenkram-firmware
538 Section: hardware
539 Description: Hardware specific firmware packages (autodetected by isenkram)
540 Based on the detected hardware various hardware specific firmware
541 packages are proposed.
542 Test-new-install: mark show
543 Relevance: 8
544 Packages: for-current-hardware-firmware
545 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
546
547 &lt;p&gt;The key parts are Test-new-install which indicate how the task
548 should be handled and the Packages line referencing to a script in
549 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
550 list of packages to install. The for-current-hardware-firmware script
551 look like this to list relevant firmware for the machine:
552
553 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
554 #!/bin/sh
555 #
556 PATH=/usr/sbin:$PATH
557 export PATH
558 isenkram-autoinstall-firmware -l
559 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
560
561 &lt;p&gt;With those two pieces in place, the firmware is installed by
562 tasksel during the normal d-i run. :)&lt;/p&gt;
563
564 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
565 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
566 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
567 install.&lt;/p&gt;
568
569 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
570 pilots in testing this feature, as isenkram is used there now to
571 install firmware, replacing the earlier scripts.&lt;/p&gt;
572 </description>
573 </item>
574
575 <item>
576 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
577 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
578 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
579 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
580 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
581 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
582 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
583 on a screen normally showing the bread types and prizes:&lt;/p&gt;
584
585 &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;
586
587 &lt;p&gt;If it had booted as it was supposed to, I would never had known
588 about this hidden Linux installation. It is interesting what
589 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
590 </description>
591 </item>
592
593 <item>
594 <title>New lsdvd release version 0.17 is ready</title>
595 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
596 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
597 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
598 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
599 got a new set of developers a few weeks ago, after the original
600 developer decided to step down and pass the project to fresh blood.
601 This project is now maintained by Petter Reinholdtsen and Steve
602 Dibb.&lt;/p&gt;
603
604 &lt;p&gt;I just wrapped up
605 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
606 new lsdvd release&lt;/a&gt;, available in git or from
607 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
608 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
609 0.17.&lt;/p&gt;
610
611 &lt;ul&gt;
612
613 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
614 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
615 non-existant, to work around additional copy protection&lt;/li&gt;
616 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
617 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
618 &lt;li&gt;Fix include orders&lt;/li&gt;
619 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
620 &lt;li&gt;Fix the chapter count&lt;/li&gt;
621 &lt;li&gt;Make sure the array size and the array limit used when initialising
622 the palette size is the same.&lt;/li&gt;
623 &lt;li&gt;Fix array printing.&lt;/li&gt;
624 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
625 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
626 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
627 with more GCC compiler warnings.&lt;/li&gt;
628
629 &lt;/ul&gt;
630
631 &lt;p&gt;This change bring together patches for lsdvd in use in various
632 Linux and Unix distributions, as well as patches submitted to the
633 project the last nine years. Please check it out. :)&lt;/p&gt;
634 </description>
635 </item>
636
637 <item>
638 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
639 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
640 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
641 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
642 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
643 project&lt;/a&gt; provide a Linux solution for schools, including a
644 powerful desktop with education software, a central server providing
645 web pages, user database, user home directories, central login and PXE
646 boot of both clients without disk and the installation to install Debian
647 Edu on machines with disk (and a few other services perhaps to small
648 to mention here). We in the Debian Edu team are currently working on
649 the Jessie based version, trying to get everything in shape before the
650 freeze, to avoid having to maintain our own package repository in the
651 future. The
652 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
653 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
654 work left. Some fatal problems block testing, breaking the installer,
655 but it is possible to work around these to get anyway. Here is a
656 recipe on how to get the installation limping along.&lt;/p&gt;
657
658 &lt;p&gt;First, download the test ISO via
659 &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;,
660 &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;
661 or rsync (use
662 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
663 The ISO build was broken on Tuesday, so we do not get a new ISO every
664 12 hours or so, but thankfully the ISO we already got we are able to
665 install with some tweaking.&lt;/p&gt;
666
667 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
668 (use Alt-Ctrl-F2), run&lt;/p&gt;
669
670 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
671 nano /usr/bin/edu-eatmydata-install
672 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
673
674 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
675 optimization. Return to the installation, select the profile you want
676 and continue. Without this change, exim4-config will fail to install
677 due to a known bug in eatmydata.&lt;/p&gt;
678
679 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
680 this do not work, figure out what your correct value would be. All my
681 test machines need /dev/sda, so I have no advice if it do not fit
682 your need.&lt;/p&gt;
683
684 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
685 root after the initial boot from hard drive, and install the
686 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
687 or mate. If you want several desktop options, install more than one
688 metapackage. Once this is done, reboot and you should have a working
689 graphical login screen. This workaround should no longer be needed
690 once the education-tasks package version 1.801 enter testing in two
691 days.&lt;/p&gt;
692
693 &lt;p&gt;I believe the ISO build will start working on two days when the new
694 tasksel package enter testing and Steve McIntyre get a chance to
695 update the debian-cd git repository. The eatmydata, grub and desktop
696 issues are already fixed in unstable and testing, and should show up
697 on the ISO as soon as the ISO build start working again. Well the
698 eatmydata optimization is really just disabled. The proper fix
699 require an upload by the eatmydata maintainer applying the patch
700 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
701 The rest have proper fixes in unstable.&lt;/p&gt;
702
703 &lt;p&gt;I hope this get you going with the installation testing, as we are
704 quickly running out of time trying to get our Jessie based
705 installation ready before the distribution freeze in a month.&lt;/p&gt;
706 </description>
707 </item>
708
709 <item>
710 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
711 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
712 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
713 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
714 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
715 to handle my fairly large DVD collection. It is a nice command line
716 tool to get details about a DVD, like title, tracks, track length,
717 etc, in XML, Perl or human readable format. But lsdvd have not seen
718 any new development since 2006 and had a few irritating bugs affecting
719 its use with some DVDs. Upstream seemed to be dead, and in January I
720 sent a small probe asking for a version control repository for the
721 project, without any reply. But I use it regularly and would like to
722 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
723 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
724 the project admin, and after getting a reply from him explaining that
725 he was no longer interested in the project, I asked if I could take
726 over. And yesterday, I became project admin.&lt;/p&gt;
727
728 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
729 maintainer interested in joining forces to maintain the upstream
730 project, and I hope we can get a new release out fairly quickly,
731 collecting the patches spread around on the internet into on place.
732 I&#39;ve added the relevant Debian patches to the freshly created git
733 repository, and expect the Gentoo patches to make it too. If you got
734 a DVD collection and care about command line tools, check out
735 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
736 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
737 list&lt;/a&gt;. :)&lt;/p&gt;
738 </description>
739 </item>
740
741 <item>
742 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
743 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
744 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
745 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
746 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
747 a lot quicker. When we install more than 2000 packages in
748 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
749 tasksel in the installer, unpacking the binary packages take forever.
750 A part of the slow I/O issue was discussed in
751 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
752 much file system sync-ing done by dpkg, which is the package
753 responsible for unpacking the binary packages. Other parts (like code
754 executed by postinst scripts) might also sync to disk during
755 installation. All this sync-ing to disk do not really make sense to
756 me. If the machine crash half-way through, I start over, I do not try
757 to salvage the half installed system. So the failure sync-ing is
758 supposed to protect against, hardware or system crash, is not really
759 relevant while the installer is running.&lt;/p&gt;
760
761 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
762 system sync()-ing in a fairly non-intrusive way, without the need to
763 change the code in several packages. The idea is not new, but I have
764 not heard anyone propose the approach using dpkg-divert before. It
765 depend on the small and clever package
766 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
767 uses LD_PRELOAD to replace the system functions for syncing data to
768 disk with functions doing nothing, thus allowing programs to live
769 dangerous while speeding up disk I/O significantly. Instead of
770 modifying the implementation of dpkg, apt and tasksel (which are the
771 packages responsible for selecting, fetching and installing packages),
772 it occurred to me that we could just divert the programs away, replace
773 them with a simple shell wrapper calling
774 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
775 Two days ago I decided to test the idea, and wrapped up a simple
776 implementation for the Debian Edu udeb.&lt;/p&gt;
777
778 &lt;p&gt;The effect was stunning. In my first test it reduced the running
779 time of the pkgsel step (installing tasks) from 64 to less than 44
780 minutes (20 minutes shaved off the installation) on an old Dell
781 Latitude D505 machine. I am not quite sure what the optimised time
782 would have been, as I messed up the testing a bit, causing the debconf
783 priority to get low enough for two questions to pop up during
784 installation. As soon as I saw the questions I moved the installation
785 along, but do not know how long the question were holding up the
786 installation. I did some more measurements using Debian Edu Jessie,
787 and got these results. The time measured is the time stamp in
788 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
789 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
790 yourself. In Debian Edu, the tasksel dialog do not show up, and the
791 timing thus do not depend on how quickly the user handle the tasksel
792 dialog.&lt;/p&gt;
793
794 &lt;p&gt;&lt;table&gt;
795
796 &lt;tr&gt;
797 &lt;th&gt;Machine/setup&lt;/th&gt;
798 &lt;th&gt;Original tasksel&lt;/th&gt;
799 &lt;th&gt;Optimised tasksel&lt;/th&gt;
800 &lt;th&gt;Reduction&lt;/th&gt;
801 &lt;/tr&gt;
802
803 &lt;tr&gt;
804 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
805 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
806 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
807 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
808 &lt;/tr&gt;
809
810 &lt;tr&gt;
811 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
812 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
813 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
814 &lt;td&gt;23 min 40%&lt;/td&gt;
815 &lt;/tr&gt;
816
817 &lt;tr&gt;
818 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
819 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
820 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
821 &lt;td&gt;11 min 50%&lt;/td&gt;
822 &lt;/tr&gt;
823
824 &lt;tr&gt;
825 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
826 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
827 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
828 &lt;td&gt;2 min 33%&lt;/td&gt;
829 &lt;/tr&gt;
830
831 &lt;tr&gt;
832 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
833 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
834 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
835 &lt;td&gt;4 min 21%&lt;/td&gt;
836 &lt;/tr&gt;
837
838 &lt;/table&gt;&lt;/p&gt;
839
840 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
841 time is spent downloading packages. The connection to the Internet
842 was 100Mbit/s during testing, so downloading should not be a
843 significant factor in the measurement. Download typically took a few
844 seconds to a few minutes, depending on the amount of packages being
845 installed.&lt;/p&gt;
846
847 &lt;p&gt;The speedup is implemented by using two hooks in
848 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
849 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
850 finish-install.d hook to remove the divert at the end of the
851 installation. I picked the pre-pkgsel.d hook instead of the
852 post-base-installer.d hook because I test using an ISO without the
853 eatmydata package included, and the post-base-installer.d hook in
854 Debian Edu can only operate on packages included in the ISO. The
855 negative effect of this is that I am unable to activate this
856 optimization for the kernel installation step in d-i. If the code is
857 moved to the post-base-installer.d hook, the speedup would be larger
858 for the entire installation.&lt;/p&gt;
859
860 &lt;p&gt;I&#39;ve implemented this in the
861 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
862 git repository, and plan to provide the optimization as part of the
863 Debian Edu installation. If you want to test this yourself, you can
864 create two files in the installer (or in an udeb). One shell script
865 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
866
867 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
868 #!/bin/sh
869 set -e
870 . /usr/share/debconf/confmodule
871 info() {
872 logger -t my-pkgsel &quot;info: $*&quot;
873 }
874 error() {
875 logger -t my-pkgsel &quot;error: $*&quot;
876 }
877 override_install() {
878 apt-install eatmydata || true
879 if [ -x /target/usr/bin/eatmydata ] ; then
880 for bin in dpkg apt-get aptitude tasksel ; do
881 file=/usr/bin/$bin
882 # Test that the file exist and have not been diverted already.
883 if [ -f /target$file ] ; then
884 info &quot;diverting $file using eatmydata&quot;
885 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
886 &gt; /target$file.edu
887 chmod 755 /target$file.edu
888 in-target dpkg-divert --package debian-edu-config \
889 --rename --quiet --add $file
890 ln -sf ./$bin.edu /target$file
891 else
892 error &quot;unable to divert $file, as it is missing.&quot;
893 fi
894 done
895 else
896 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
897 fi
898 }
899
900 override_install
901 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
902
903 &lt;p&gt;To clean up, another shell script should go into
904 /usr/lib/finish-install.d/ with code like this:
905
906 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
907 #! /bin/sh -e
908 . /usr/share/debconf/confmodule
909 error() {
910 logger -t my-finish-install &quot;error: $@&quot;
911 }
912 remove_install_override() {
913 for bin in dpkg apt-get aptitude tasksel ; do
914 file=/usr/bin/$bin
915 if [ -x /target$file.edu ] ; then
916 rm /target$file
917 in-target dpkg-divert --package debian-edu-config \
918 --rename --quiet --remove $file
919 rm /target$file.edu
920 else
921 error &quot;Missing divert for $file.&quot;
922 fi
923 done
924 sync # Flush file buffers before continuing
925 }
926
927 remove_install_override
928 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
929
930 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
931 edu-eatmydata-install and call it from the pre-pkgsel.d and
932 finish-install.d scripts.&lt;/p&gt;
933
934 &lt;p&gt;By now you might ask if this change should get into the normal
935 Debian installer too? I suspect it should, but am not sure the
936 current debian-installer coordinators find it useful enough. It also
937 depend on the side effects of the change. I&#39;m not aware of any, but I
938 guess we will see if the change is safe after some more testing.
939 Perhaps there is some package in Debian depending on sync() and
940 fsync() having effect? Perhaps it should go into its own udeb, to
941 allow those of us wanting to enable it to do so without affecting
942 everyone.&lt;/p&gt;
943
944 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
945 will break installation of all programs using gnutls because of
946 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
947 eatmydata package in Debian will solve it.&lt;/p&gt;
948
949 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
950 the optimization work again. And I have discovered that the
951 dpkg-divert trick is not really needed and implemented a slightly
952 simpler approach as part of the debian-edu-install package. See
953 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
954
955 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
956 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
957 triggering on i386 made it into testing, and broke this installation
958 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
959 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
960 </description>
961 </item>
962
963 <item>
964 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
965 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
966 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
967 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
968 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
969 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
970 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
971 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
972 learn that there is a large set of publicly available key servers to
973 use when looking for peoples public key. So far I have used
974 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
975 were misbehaving, but those days are ended. The servers I have used
976 up until yesterday have been slow and some times unavailable. I hope
977 those problems are gone now.&lt;/p&gt;
978
979 &lt;p&gt;Behind the round robin DNS entry of the
980 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
981 there is a pool of more than 100 keyservers which are checked every
982 day to ensure they are well connected and up to date. It must be
983 better than what I have used so far. :)&lt;/p&gt;
984
985 &lt;p&gt;Yesterdays speaker told me that the service is the default
986 keyserver provided by the default configuration in GnuPG, but this do
987 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
988
989 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
990 line:&lt;/p&gt;
991
992 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
993 keyserver pool.sks-keyservers.net
994 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
995
996 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
997 entries in DNS. Just for fun, I did just that at work, so now every
998 user of GnuPG at the University of Oslo should find a OpenGPG
999 keyserver automatically should their need it:&lt;/p&gt;
1000
1001 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1002 % host -t srv _pgpkey-http._tcp.uio.no
1003 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1004 %
1005 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1006
1007 &lt;p&gt;Now if only
1008 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1009 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1010 very happy. It can look up a given key or search for a user ID, but I
1011 normally do not want that, but to find a trust path from my key to
1012 another key. Given a user ID or key ID, I would like to find (and
1013 download) the keys representing a signature path from my key to the
1014 key in question, to be able to get a trust path between the two keys.
1015 This is as far as I can tell not possible today. Perhaps something
1016 for a future version of the protocol?&lt;/p&gt;
1017 </description>
1018 </item>
1019
1020 <item>
1021 <title>From English wiki to translated PDF and epub via Docbook</title>
1022 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1023 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1024 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1025 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1026 project&lt;/a&gt; provide an instruction manual for teachers, system
1027 administrators and other users that contain useful tips for setting up
1028 and maintaining a Debian Edu installation. This text is about how the
1029 text processing of this manual is handled in the project.&lt;/p&gt;
1030
1031 &lt;p&gt;One goal of the project is to provide information in the native
1032 language of its users, and for this we need to handle translations.
1033 But we also want to make sure each language contain the same
1034 information, so for this we need a good way to keep the translations
1035 in sync. And we want it to be easy for our users to improve the
1036 documentation, avoiding the need to learn special formats or tools to
1037 contribute, and the obvious way to do this is to make it possible to
1038 edit the documentation using a web browser. We also want it to be
1039 easy for translators to keep the translation up to date, and give them
1040 help in figuring out what need to be translated. Here is the list of
1041 tools and the process we have found trying to reach all these
1042 goals.&lt;/p&gt;
1043
1044 &lt;p&gt;We maintain the authoritative source of our manual in the
1045 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1046 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1047 front page with references to the different chapters, several pages
1048 for each chapter, and finally one &quot;collection page&quot; gluing all the
1049 chapters together into one large web page (aka
1050 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1051 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1052 processing and translations. Thanks to the fact that the
1053 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1054 wiki.debian.org support exporting pages in
1055 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1056 the list of pages to export using the raw version of the AllInOne
1057 page, loop over each of them to generate a Docbook XML version of the
1058 manual. This process also download images and transform image
1059 references to use the locally downloaded images. The generated
1060 Docbook XML files are slightly broken, so some post-processing is done
1061 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1062 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1063 a handfull of images. The XML file can now be used to generate PDF, HTML
1064 and epub versions of the English manual. This is the basic step of
1065 our process, making PDF (using dblatex), HTML (using xsltproc) and
1066 epub (using dbtoepub) version from Docbook XML, and the resulting files
1067 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1068
1069 &lt;p&gt;But English documentation is not enough for us. We want translated
1070 documentation too, and we want to make it easy for translators to
1071 track the English original. For this we use the
1072 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1073 which allow us to transform the English Docbook XML file into a
1074 translation file (a .pot file), usable with the normal gettext based
1075 translation tools used by those translating free software. The pot
1076 file is used to create and maintain translation files (several .po
1077 files), which the translations update with the native language
1078 translations of all titles, paragraphs and blocks of text in the
1079 original. The next step is combining the original English Docbook XML
1080 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1081 create a translated Docbook XML file (in this case
1082 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1083 translated, if the translation is not complete) Docbook XML file can
1084 then be used like the original to create a PDF, HTML and epub version
1085 of the documentation.&lt;/p&gt;
1086
1087 &lt;p&gt;The translators use different tools to edit the .po files. We
1088 recommend using
1089 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1090 while some use emacs and vi, others can use web based editors like
1091 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1092 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1093 is where the .po file end up, in our git repository. Updated
1094 translations can either be committed directly to git, or submitted as
1095 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1096 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1097
1098 &lt;p&gt;One challenge is images, which both might need to be translated (if
1099 they show translated user applications), and are needed in different
1100 formats when creating PDF and HTML versions (epub is a HTML version in
1101 this regard). For this we transform the original PNG images to the
1102 needed density and format during build, and have a way to provide
1103 translated images by storing translated versions in
1104 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1105 package maintainers know more.&lt;/p&gt;
1106
1107 &lt;p&gt;If you wonder what the result look like, we provide
1108 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1109 of the documentation packages on the web&lt;/a&gt;. See for example the
1110 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1111 PDF version&lt;/a&gt; or the
1112 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1113 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1114 but perhaps it will be done in the future.&lt;/p&gt;
1115
1116 &lt;p&gt;To learn more, check out
1117 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1118 debian-edu-doc package&lt;/a&gt;,
1119 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1120 manual on the wiki&lt;/a&gt; and
1121 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1122 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1123 </description>
1124 </item>
1125
1126 <item>
1127 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1128 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1129 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1130 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1131 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1132 related packages relevant for the computer installed automatically.
1133 So I implemented one, using
1134 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1135 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1136 run tasksel as user root. You should be presented with a new option,
1137 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1138 select it, tasksel will install the packages isenkram claim is fit for
1139 the current hardware, hot pluggable or not.&lt;p&gt;
1140
1141 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1142 description, and the other is the script used to extract the list of
1143 packages to install. The first part is in
1144 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1145 this:&lt;/p&gt;
1146
1147 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1148 Task: isenkram
1149 Section: hardware
1150 Description: Hardware specific packages (autodetected by isenkram)
1151 Based on the detected hardware various hardware specific packages are
1152 proposed.
1153 Test-new-install: mark show
1154 Relevance: 8
1155 Packages: for-current-hardware
1156 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1157
1158 &lt;p&gt;The second part is in
1159 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1160 this:&lt;/p&gt;
1161
1162 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1163 #!/bin/sh
1164 #
1165 (
1166 isenkram-lookup
1167 isenkram-autoinstall-firmware -l
1168 ) | sort -u
1169 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1170
1171 &lt;p&gt;All in all, a very short and simple implementation making it
1172 trivial to install the hardware dependent package we all may want to
1173 have installed on our machines. I&#39;ve not been able to find a way to
1174 get tasksel to tell you exactly which packages it plan to install
1175 before doing the installation. So if you are curious or careful,
1176 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1177
1178 &lt;p&gt;The information about which packages are handling which hardware is
1179 fetched either from the isenkram package itself in
1180 /usr/share/isenkram/, from git.debian.org or from the APT package
1181 database (using the Modaliases header). The APT package database
1182 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1183 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1184 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1185 the python-apt code (bug
1186 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1187 workaround I was able to get rid of the file descriptor leak and
1188 reduce the memory leak from ~30 MiB per hardware detection down to
1189 around 2 MiB per hardware detection. It should make the desktop
1190 daemon a lot more useful. The fix is in version 0.7 uploaded to
1191 unstable today.&lt;/p&gt;
1192
1193 &lt;p&gt;I believe the current way of mapping hardware to packages in
1194 Isenkram is is a good draft, but in the future I expect isenkram to
1195 use the AppStream data source for this. A proposal for getting proper
1196 AppStream support into Debian is floating around as
1197 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1198 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1199 project&lt;/a&gt; will take place this summer to improve the situation. I
1200 look forward to seeing the result, and welcome patches for isenkram to
1201 start using the information when it is ready.&lt;/p&gt;
1202
1203 &lt;p&gt;If you want your package to map to some specific hardware, either
1204 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1205 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1206 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1207 package. See also
1208 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1209 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1210 the information will be migrated to AppStream eventually, but for the
1211 moment I got no better place to store it.&lt;/p&gt;
1212 </description>
1213 </item>
1214
1215 <item>
1216 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1217 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1218 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1219 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1220 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1221 project&lt;/a&gt; is working on providing the software and hardware to make
1222 it easy for non-technical people to host their data and communication
1223 at home, and being able to communicate with their friends and family
1224 encrypted and away from prying eyes. It is still going strong, and
1225 today a major mile stone was reached.&lt;/p&gt;
1226
1227 &lt;p&gt;Today, the last of the packages currently used by the project to
1228 created the system images were accepted into Debian Unstable. It was
1229 the freedombox-setup package, which is used to configure the images
1230 during build and on the first boot. Now all one need to get going is
1231 the build code from the freedom-maker git repository and packages from
1232 Debian. And once the freedombox-setup package enter testing, we can
1233 build everything directly from Debian. :)&lt;/p&gt;
1234
1235 &lt;p&gt;Some key packages used by Freedombox are
1236 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1237 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1238 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1239 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1240 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1241 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1242 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1243 are plans to integrate more packages into the setup. User
1244 documentation is maintained on the Debian wiki. Please
1245 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1246 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1247
1248 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1249 setup, run this on a Debian machine using a user with sudo rights to
1250 become root:&lt;/p&gt;
1251
1252 &lt;p&gt;&lt;pre&gt;
1253 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1254 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1255 u-boot-tools
1256 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1257 freedom-maker
1258 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1259 &lt;/pre&gt;&lt;/p&gt;
1260
1261 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1262 devices. See the README in the freedom-maker git repo for more
1263 details on the build. If you do not want all three images, trim the
1264 make line. Note that the virtualbox-image target is not really
1265 virtualbox specific. It create a x86 image usable in kvm, qemu,
1266 vmware and any other x86 virtual machine environment. You might need
1267 the version of vmdebootstrap in Jessie to get the build working, as it
1268 include fixes for a race condition with kpartx.&lt;/p&gt;
1269
1270 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1271 method, boot a Debian Wheezy ISO and use this boot argument to load
1272 the preseed values:&lt;/p&gt;
1273
1274 &lt;p&gt;&lt;pre&gt;
1275 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;
1276 &lt;/pre&gt;&lt;/p&gt;
1277
1278 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1279 it still work.&lt;/p&gt;
1280
1281 &lt;p&gt;If you wonder how to help, one task you could look at is using
1282 systemd as the boot system. It will become the default for Linux in
1283 Jessie, so we need to make sure it is usable on the Freedombox. I did
1284 a simple test a few weeks ago, and noticed dnsmasq failed to start
1285 during boot when using systemd. I suspect there are other problems
1286 too. :) To detect problems, there is a test suite included, which can
1287 be run from the plinth web interface.&lt;/p&gt;
1288
1289 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1290 us get the new release published. :) Please join us on
1291 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1292 irc.debian.org)&lt;/a&gt; and
1293 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1294 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1295 </description>
1296 </item>
1297
1298 <item>
1299 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1300 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1301 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1302 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1303 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1304 solution for use at home. My requirements are simple, it must be
1305 cheap and locally encrypted (in other words, I keep the encryption
1306 keys, the storage provider do not have access to my private files).
1307 One idea me and my friends had many years ago, before the cloud
1308 storage providers showed up, was to use Google mail as storage,
1309 writing a Linux block device storing blocks as emails in the mail
1310 service provided by Google, and thus get heaps of free space. On top
1311 of this one can add encryption, RAID and volume management to have
1312 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1313 I never found time to implement such system. But the last few weeks I
1314 have looked at a system called
1315 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1316 mounted network backed file system with the features I need.&lt;/p&gt;
1317
1318 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1319 handling several different storage providers, any with Amazon S3,
1320 Google Drive or OpenStack API. There are heaps of such storage
1321 providers. S3QL can also use a local directory as storage, which
1322 combined with sshfs allow for file storage on any ssh server. S3QL
1323 include support for encryption, compression, de-duplication, snapshots
1324 and immutable file systems, allowing me to mount the remote storage as
1325 a local mount point, look at and use the files as if they were local,
1326 while the content is stored in the cloud as well. This allow me to
1327 have a backup that should survive fire. The file system can not be
1328 shared between several machines at the same time, as only one can
1329 mount it at the time, but any machine with the encryption key and
1330 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1331
1332 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1333 package is included already. So to get started, run &lt;tt&gt;apt-get
1334 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1335 Greenqloud, after reading their nice recipe on
1336 &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
1337 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1338 in Iceland more than those in USA when it come to keeping my personal
1339 data safe and private, and thus would rather spend money on a company
1340 in Iceland. Another nice recipe is available from the article
1341 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1342 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1343 Admin magazine. When the provider is picked, figure out how to get
1344 the API key needed to connect to the storage API. With Greencloud,
1345 the key did not show up until I had added payment details to my
1346 account.&lt;/p&gt;
1347
1348 &lt;p&gt;Armed with the API access details, it is time to create the file
1349 system. First, create a new bucket in the cloud. This bucket is the
1350 file system storage area. I picked a bucket name reflecting the
1351 machine that was going to store data there, but any name will do.
1352 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1353 the API login and password, and a locally created password. Store it
1354 all in ~root/.s3ql/authinfo2 like this:
1355
1356 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1357 [s3c]
1358 storage-url: s3c://s.greenqloud.com:443/bucket-name
1359 backend-login: API-login
1360 backend-password: API-password
1361 fs-passphrase: local-password
1362 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1363
1364 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1365 but any sensible way to create a fairly random password should do it.
1366 Armed with these details, it is now time to run mkfs, entering the API
1367 details and password to create it:&lt;/p&gt;
1368
1369 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1370 # mkdir -m 700 /var/lib/s3ql-cache
1371 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1372 --ssl s3c://s.greenqloud.com:443/bucket-name
1373 Enter backend login:
1374 Enter backend password:
1375 Before using S3QL, make sure to read the user&#39;s guide, especially
1376 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1377 Enter encryption password:
1378 Confirm encryption password:
1379 Generating random encryption key...
1380 Creating metadata tables...
1381 Dumping metadata...
1382 ..objects..
1383 ..blocks..
1384 ..inodes..
1385 ..inode_blocks..
1386 ..symlink_targets..
1387 ..names..
1388 ..contents..
1389 ..ext_attributes..
1390 Compressing and uploading metadata...
1391 Wrote 0.00 MB of compressed metadata.
1392 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1393
1394 &lt;p&gt;The next step is mounting the file system to make the storage available.
1395
1396 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1397 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1398 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1399 Using 4 upload threads.
1400 Downloading and decompressing metadata...
1401 Reading metadata...
1402 ..objects..
1403 ..blocks..
1404 ..inodes..
1405 ..inode_blocks..
1406 ..symlink_targets..
1407 ..names..
1408 ..contents..
1409 ..ext_attributes..
1410 Mounting filesystem...
1411 # df -h /s3ql
1412 Filesystem Size Used Avail Use% Mounted on
1413 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1414 #
1415 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1416
1417 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1418 backups in it, and as the metadata used by rsync is downloaded at
1419 mount time, no network traffic (and storage cost) is triggered by
1420 running rsync. To unmount, one should not use the normal umount
1421 command, as this will not flush the cache to the cloud storage, but
1422 instead running the umount.s3ql command like this:
1423
1424 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1425 # umount.s3ql /s3ql
1426 #
1427 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1428
1429 &lt;p&gt;There is a fsck command available to check the file system and
1430 correct any problems detected. This can be used if the local server
1431 crashes while the file system is mounted, to reset the &quot;already
1432 mounted&quot; flag. This is what it look like when processing a working
1433 file system:&lt;/p&gt;
1434
1435 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1436 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1437 Using cached metadata.
1438 File system seems clean, checking anyway.
1439 Checking DB integrity...
1440 Creating temporary extra indices...
1441 Checking lost+found...
1442 Checking cached objects...
1443 Checking names (refcounts)...
1444 Checking contents (names)...
1445 Checking contents (inodes)...
1446 Checking contents (parent inodes)...
1447 Checking objects (reference counts)...
1448 Checking objects (backend)...
1449 ..processed 5000 objects so far..
1450 ..processed 10000 objects so far..
1451 ..processed 15000 objects so far..
1452 Checking objects (sizes)...
1453 Checking blocks (referenced objects)...
1454 Checking blocks (refcounts)...
1455 Checking inode-block mapping (blocks)...
1456 Checking inode-block mapping (inodes)...
1457 Checking inodes (refcounts)...
1458 Checking inodes (sizes)...
1459 Checking extended attributes (names)...
1460 Checking extended attributes (inodes)...
1461 Checking symlinks (inodes)...
1462 Checking directory reachability...
1463 Checking unix conventions...
1464 Checking referential integrity...
1465 Dropping temporary indices...
1466 Backing up old metadata...
1467 Dumping metadata...
1468 ..objects..
1469 ..blocks..
1470 ..inodes..
1471 ..inode_blocks..
1472 ..symlink_targets..
1473 ..names..
1474 ..contents..
1475 ..ext_attributes..
1476 Compressing and uploading metadata...
1477 Wrote 0.89 MB of compressed metadata.
1478 #
1479 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1480
1481 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1482 quick, about the same speed as local file access. Uploading large
1483 amount of data is to me limited by the bandwidth out of and into my
1484 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1485 which is very close to my upload speed, and downloading the same
1486 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1487 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1488 network, not the file system code. I do not know what a good cache
1489 size would be, but suspect that the cache should e larger than your
1490 working set.&lt;/p&gt;
1491
1492 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1493 time. If another machine try, it is told that the file system is
1494 busy:&lt;/p&gt;
1495
1496 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1497 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1498 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1499 Using 8 upload threads.
1500 Backend reports that fs is still mounted elsewhere, aborting.
1501 #
1502 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1503
1504 &lt;p&gt;The file content is uploaded when the cache is full, while the
1505 metadata is uploaded once every 24 hour by default. To ensure the
1506 file system content is flushed to the cloud, one can either umount the
1507 file system, or ask S3QL to flush the cache and metadata using
1508 s3qlctrl:
1509
1510 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1511 # s3qlctrl upload-meta /s3ql
1512 # s3qlctrl flushcache /s3ql
1513 #
1514 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1515
1516 &lt;p&gt;If you are curious about how much space your data uses in the
1517 cloud, and how much compression and deduplication cut down on the
1518 storage usage, you can use s3qlstat on the mounted file system to get
1519 a report:&lt;/p&gt;
1520
1521 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1522 # s3qlstat /s3ql
1523 Directory entries: 9141
1524 Inodes: 9143
1525 Data blocks: 8851
1526 Total data size: 22049.38 MB
1527 After de-duplication: 21955.46 MB (99.57% of total)
1528 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1529 Database size: 2.39 MB (uncompressed)
1530 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1531 #
1532 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1533
1534 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1535 storage. I did not try to locate them all, but am aware of at least
1536 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1537 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1538 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1539 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1540 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1541 accept payment in Bitcoin. Pick one that suit your need. Some of
1542 them provide several GiB of free storage, but the prize models are
1543 quite different and you will have to figure out what suits you
1544 best.&lt;/p&gt;
1545
1546 &lt;p&gt;While researching this blog post, I had a look at research papers
1547 and posters discussing the S3QL file system. There are several, which
1548 told me that the file system is getting a critical check by the
1549 science community and increased my confidence in using it. One nice
1550 poster is titled
1551 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1552 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1553 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1554 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1555 and Pamela Smith. Please have a look.&lt;/p&gt;
1556
1557 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1558 check out the mounted S3QL file system to see if it would be usable as
1559 a home directory (in other word, that it provided POSIX semantics when
1560 it come to locking and umask handling etc). Running
1561 &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
1562 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1563 no error was found. So the file system can be used for home
1564 directories, if one chooses to do so.&lt;/p&gt;
1565
1566 &lt;p&gt;If you do not want a locally file system, and want something that
1567 work without the Linux fuse file system, I would like to mention the
1568 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1569 provide locally encrypted backup using a command line client. It have
1570 a nicer access control system, where one can split out read and write
1571 access, allowing some systems to write to the backup and others to
1572 only read from it.&lt;/p&gt;
1573
1574 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1575 activities, please send Bitcoin donations to my address
1576 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1577 </description>
1578 </item>
1579
1580 <item>
1581 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1582 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1583 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1584 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1585 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1586 project&lt;/a&gt; is working on providing the software and hardware for
1587 making it easy for non-technical people to host their data and
1588 communication at home, and being able to communicate with their
1589 friends and family encrypted and away from prying eyes. It has been
1590 going on for a while, and is slowly progressing towards a new test
1591 release (0.2).&lt;/p&gt;
1592
1593 &lt;p&gt;And what day could be better than the Pi day to announce that the
1594 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1595 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1596 system), and can also be installed using a Debian installer preseed
1597 file. The Debian based Freedombox is now based on Debian Jessie,
1598 where most of the needed packages used are already present. Only one,
1599 the freedombox-setup package, is missing. To try to build your own
1600 boot image to test the current status, fetch the freedom-maker scripts
1601 and build using
1602 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1603 with a user with sudo access to become root:
1604
1605 &lt;pre&gt;
1606 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1607 freedom-maker
1608 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1609 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1610 u-boot-tools
1611 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1612 &lt;/pre&gt;
1613
1614 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1615 devices. See the README for more details on the build. If you do not
1616 want all three images, trim the make line. But note that thanks to &lt;a
1617 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1618 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1619 kpartx call.&lt;/p&gt;
1620
1621 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1622 method, boot a Debian Wheezy ISO and use this boot argument to load
1623 the preseed values:&lt;/p&gt;
1624
1625 &lt;pre&gt;
1626 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;
1627 &lt;/pre&gt;
1628
1629 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1630 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1631 currently hang while setting up APT sources. Killing the
1632 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1633 installation will get the installation going. This affect all
1634 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1635
1636 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1637 us get the new release published. :) Please join us on
1638 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1639 irc.debian.org)&lt;/a&gt; and
1640 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1641 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1642 </description>
1643 </item>
1644
1645 <item>
1646 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1647 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1649 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1650 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1651 innetgr tools, because I needed them in
1652 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1653 ng-utils, and it has served me well. I placed the project under the
1654 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1655 repository. But many years ago, the CVS repository was dropped (lost,
1656 not migrated to new hardware, not sure), and the project have lacked a
1657 proper home since then.&lt;/p&gt;
1658
1659 &lt;p&gt;Last summer, I had a look at the package and made a new release
1660 fixing a irritating crash bug, but was unable to store the changes in
1661 a proper source control system. I applied for a project on
1662 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1663 to follow up on it. Until today. :)&lt;/p&gt;
1664
1665 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1666 now have a new home, and a git repository with the highlight of the
1667 history of the project. I published all release tarballs and imported
1668 them into the git repository. As the project is really stable and not
1669 expected to gain new features any time soon, I decided to make a new
1670 release and call it 1.0. Visit the new project home on
1671 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1672 if you want to check it out. The new version is also uploaded into
1673 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1674 </description>
1675 </item>
1676
1677 <item>
1678 <title>Testing sysvinit from experimental in Debian Hurd</title>
1679 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1680 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1681 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1682 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1683 their changes into sysvinit, to allow them to use the normal sysvinit
1684 boot system instead of their old one. This follow up on the
1685 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1686 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1687 get Debian on Hurd working more like Debian on Linux. To get started,
1688 I downloaded a prebuilt hard disk image from
1689 &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;,
1690 and started it using virt-manager.&lt;/p&gt;
1691
1692 &lt;p&gt;The first think I had to do after logging in (root without any
1693 password) was to get the network operational. I followed
1694 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1695 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1696 commands as root to get the machine to accept a IP address from the
1697 kvm internal DHCP server:&lt;/p&gt;
1698
1699 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1700 settrans -fgap /dev/netdde /hurd/netdde
1701 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1702 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1703 dhclient /dev/eth0
1704 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1705
1706 &lt;p&gt;After this, the machine had internet connectivity, and I could
1707 upgrade it and install the sysvinit packages from experimental and
1708 enable it as the default boot system in Hurd.&lt;/p&gt;
1709
1710 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1711 running on the machine it for ssh login to work a password need to be
1712 set. Also, note that a bug somewhere in openssh on Hurd block
1713 compression from working. Remember to turn that off on the client
1714 side.&lt;/p&gt;
1715
1716 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1717 stuff:&lt;/p&gt;
1718
1719 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1720 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1721 deb http://http.debian.net/debian/ experimental main
1722 EOF
1723 apt-get update
1724 apt-get dist-upgrade
1725 apt-get install -t experimental initscripts sysv-rc sysvinit \
1726 sysvinit-core sysvinit-utils
1727 update-alternatives --config runsystem
1728 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1729
1730 &lt;p&gt;To reboot after switching boot system, you have to use
1731 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1732 yet a sysvinit process able to receive the signals from the normal
1733 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1734 upgrading every package and rebooting, the network come up with DHCP
1735 after boot as it should, and the settrans/pkill hack mentioned at the
1736 start is no longer needed. But for some strange reason, there are no
1737 longer any login prompt in the virtual console, so I logged in using
1738 ssh instead.
1739
1740 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1741 fail some times. No idea what the cause is, but hope the Hurd porters
1742 figure it out. At least Justus said on IRC (#debian-hurd on
1743 irc.debian.org) that they are aware of the problem. A way to reduce
1744 the impact is to upgrade to the Hurd packages built by Justus by
1745 adding this repository to the machine:&lt;/p&gt;
1746
1747 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1748 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1749 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1750 EOF
1751 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1752
1753 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1754 http://ftp.debian-ports.org/debian, because some of the packages in
1755 unstable do not yet include the required patches that are lingering in
1756 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1757
1758 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1759 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1760 i emacs - GNU Emacs editor (metapackage)
1761 i gdb - GNU Debugger
1762 i hurd-recommended - Miscellaneous translators
1763 i isc-dhcp-client - ISC DHCP client
1764 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1765 i libc-bin - Embedded GNU C Library: Binaries
1766 i libc-dev-bin - Embedded GNU C Library: Development binaries
1767 i libc0.3 - Embedded GNU C Library: Shared libraries
1768 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1769 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1770 i multiarch-support - Transitional package to ensure multiarch compatibilit
1771 i A x11-common - X Window System (X.Org) infrastructure
1772 i xorg - X.Org X Window System
1773 i A xserver-xorg - X.Org X server
1774 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1775 #
1776 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1777
1778 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1779 X.org did not work out of the box and I never took the time to follow
1780 the porters instructions to fix it. This time I was interested in the
1781 command line stuff.&lt;p&gt;
1782 </description>
1783 </item>
1784
1785 <item>
1786 <title>New chrpath release 0.16</title>
1787 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1789 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1790 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1791 find problems in C, C++ and Java code using static source code
1792 analysis. It can detect a lot of different problems, and is very
1793 useful to find memory and locking bugs in the error handling part of
1794 the source. The company behind it provide
1795 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1796 a community service&lt;/a&gt;, and many hundred free software projects are
1797 already checked. A few days ago I decided to have a closer look at
1798 the Coverity system, and discovered that the
1799 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1800 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1801 projects I am involved with was already registered. But these are
1802 fairly big, and I would also like to have a small and easy project to
1803 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1804 checking of the chrpath project&lt;/a&gt;. It was
1805 added to the checker and discovered seven potential defects. Six of
1806 these were real, mostly resource &quot;leak&quot; when the program detected an
1807 error. Nothing serious, as the resources would be released a fraction
1808 of a second later when the program exited because of the error, but it
1809 is nice to do it right in case the source of the program some time in
1810 the future end up in a library. Having fixed all defects and added
1811 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1812 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1813 publish a new release. These are the release notes:&lt;/p&gt;
1814
1815 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1816
1817 &lt;ul&gt;
1818
1819 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1820 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1821 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1822
1823 &lt;/ul&gt;
1824
1825 &lt;p&gt;You can
1826 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1827 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1828 project if something is wrong with the new release. The test suite
1829 did not discover any old errors, so if you find a new one, please also
1830 include a test suite check.&lt;/p&gt;
1831 </description>
1832 </item>
1833
1834 <item>
1835 <title>New chrpath release 0.15</title>
1836 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1837 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1838 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1839 <description>&lt;p&gt;After many years break from the package and a vain hope that
1840 development would be continued by someone else, I finally pulled my
1841 acts together this morning and wrapped up a new release of chrpath,
1842 the command line tool to modify the rpath and runpath of already
1843 compiled ELF programs. The update was triggered by the persistence of
1844 Isha Vishnoi at IBM, which needed a new config.guess file to get
1845 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1846 is working on. I checked the
1847 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1848 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1849 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1850 packages for interesting patches (failed to find the source from
1851 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1852 These are the release notes:&lt;/p&gt;
1853
1854 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1855
1856 &lt;ul&gt;
1857
1858 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1859 with newer architectures. Thanks to isha vishnoi for the heads
1860 up.&lt;/li&gt;
1861
1862 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1863
1864 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1865 Matthias Klose.&lt;/li&gt;
1866
1867 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1868 Petr Machata found in Fedora.&lt;/li&gt;
1869
1870 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1871 .dynamic is a NULL terminated string. Based on patch found in
1872 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1873
1874 &lt;/ul&gt;
1875
1876 &lt;p&gt;You can
1877 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1878 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1879 project if something is wrong with the new release. The test suite
1880 did not discover any old errors, so if you find a new one, please also
1881 include a testsuite check.&lt;/p&gt;
1882 </description>
1883 </item>
1884
1885 <item>
1886 <title>Debian init.d boot script example for rsyslog</title>
1887 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1888 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1889 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1890 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1891 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1892 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1893 init.d scripts at all. Here is an example init.d script, ie a rewrite
1894 of /etc/init.d/rsyslog:&lt;/p&gt;
1895
1896 &lt;p&gt;&lt;pre&gt;
1897 #!/lib/init/init-d-script
1898 ### BEGIN INIT INFO
1899 # Provides: rsyslog
1900 # Required-Start: $remote_fs $time
1901 # Required-Stop: umountnfs $time
1902 # X-Stop-After: sendsigs
1903 # Default-Start: 2 3 4 5
1904 # Default-Stop: 0 1 6
1905 # Short-Description: enhanced syslogd
1906 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1907 # It is quite compatible to stock sysklogd and can be
1908 # used as a drop-in replacement.
1909 ### END INIT INFO
1910 DESC=&quot;enhanced syslogd&quot;
1911 DAEMON=/usr/sbin/rsyslogd
1912 &lt;/pre&gt;&lt;/p&gt;
1913
1914 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1915 script was 137 lines, and the above is just 15 lines, most of it meta
1916 info/comments.&lt;/p&gt;
1917
1918 &lt;p&gt;How to do this, you ask? Well, one create a new script
1919 /lib/init/init-d-script looking something like this:
1920
1921 &lt;p&gt;&lt;pre&gt;
1922 #!/bin/sh
1923
1924 # Define LSB log_* functions.
1925 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1926 # and status_of_proc is working.
1927 . /lib/lsb/init-functions
1928
1929 #
1930 # Function that starts the daemon/service
1931
1932 #
1933 do_start()
1934 {
1935 # Return
1936 # 0 if daemon has been started
1937 # 1 if daemon was already running
1938 # 2 if daemon could not be started
1939 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1940 || return 1
1941 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1942 $DAEMON_ARGS \
1943 || return 2
1944 # Add code here, if necessary, that waits for the process to be ready
1945 # to handle requests from services started subsequently which depend
1946 # on this one. As a last resort, sleep for some time.
1947 }
1948
1949 #
1950 # Function that stops the daemon/service
1951 #
1952 do_stop()
1953 {
1954 # Return
1955 # 0 if daemon has been stopped
1956 # 1 if daemon was already stopped
1957 # 2 if daemon could not be stopped
1958 # other if a failure occurred
1959 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1960 RETVAL=&quot;$?&quot;
1961 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1962 # Wait for children to finish too if this is a daemon that forks
1963 # and if the daemon is only ever run from this initscript.
1964 # If the above conditions are not satisfied then add some other code
1965 # that waits for the process to drop all resources that could be
1966 # needed by services started subsequently. A last resort is to
1967 # sleep for some time.
1968 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1969 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1970 # Many daemons don&#39;t delete their pidfiles when they exit.
1971 rm -f $PIDFILE
1972 return &quot;$RETVAL&quot;
1973 }
1974
1975 #
1976 # Function that sends a SIGHUP to the daemon/service
1977 #
1978 do_reload() {
1979 #
1980 # If the daemon can reload its configuration without
1981 # restarting (for example, when it is sent a SIGHUP),
1982 # then implement that here.
1983 #
1984 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1985 return 0
1986 }
1987
1988 SCRIPTNAME=$1
1989 scriptbasename=&quot;$(basename $1)&quot;
1990 echo &quot;SN: $scriptbasename&quot;
1991 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1992 script=&quot;$1&quot;
1993 shift
1994 . $script
1995 else
1996 exit 0
1997 fi
1998
1999 NAME=$(basename $DAEMON)
2000 PIDFILE=/var/run/$NAME.pid
2001
2002 # Exit if the package is not installed
2003 #[ -x &quot;$DAEMON&quot; ] || exit 0
2004
2005 # Read configuration variable file if it is present
2006 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2007
2008 # Load the VERBOSE setting and other rcS variables
2009 . /lib/init/vars.sh
2010
2011 case &quot;$1&quot; in
2012 start)
2013 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2014 do_start
2015 case &quot;$?&quot; in
2016 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2017 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2018 esac
2019 ;;
2020 stop)
2021 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2022 do_stop
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 status)
2029 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2030 ;;
2031 #reload|force-reload)
2032 #
2033 # If do_reload() is not implemented then leave this commented out
2034 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2035 #
2036 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2037 #do_reload
2038 #log_end_msg $?
2039 #;;
2040 restart|force-reload)
2041 #
2042 # If the &quot;reload&quot; option is implemented then remove the
2043 # &#39;force-reload&#39; alias
2044 #
2045 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2046 do_stop
2047 case &quot;$?&quot; in
2048 0|1)
2049 do_start
2050 case &quot;$?&quot; in
2051 0) log_end_msg 0 ;;
2052 1) log_end_msg 1 ;; # Old process is still running
2053 *) log_end_msg 1 ;; # Failed to start
2054 esac
2055 ;;
2056 *)
2057 # Failed to stop
2058 log_end_msg 1
2059 ;;
2060 esac
2061 ;;
2062 *)
2063 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2064 exit 3
2065 ;;
2066 esac
2067
2068 :
2069 &lt;/pre&gt;&lt;/p&gt;
2070
2071 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2072 lot. I did not really polish the approach, so it might not always
2073 work out of the box, but you get the idea. I did not try very hard to
2074 optimize it nor make it more robust either.&lt;/p&gt;
2075
2076 &lt;p&gt;A better argument for switching init system in Debian than reducing
2077 the size of init scripts (which is a good thing to do anyway), is to
2078 get boot system that is able to handle the kernel events sensibly and
2079 robustly, and do not depend on the boot to run sequentially. The boot
2080 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2081 </description>
2082 </item>
2083
2084 <item>
2085 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2086 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2087 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2088 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2089 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2090 remote display access is the preferred solution with oVirt and RedHat
2091 Enterprise Virtualization, and I was sad to discover the other day
2092 that the browser plugin needed to use these systems seamlessly was
2093 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2094 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2095 2013-04-01, so I decided to wrap up a package based on the great work
2096 from Cajus Pollmeier and put it in a collab-maint maintained git
2097 repository to get a package I could use. I would very much like
2098 others to help me maintain the package (or just take over, I do not
2099 mind), but as no-one had volunteered so far, I just uploaded it to
2100 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2101
2102 &lt;p&gt;The source is now available from
2103 &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;
2104 </description>
2105 </item>
2106
2107 <item>
2108 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2109 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2110 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2111 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2112 <description>&lt;p&gt;The
2113 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2114 program is a a very nice system to create virtual machine images. It
2115 create a image file, add a partition table, mount it and run
2116 debootstrap in the mounted directory to create a Debian system on a
2117 stick. Yesterday, I decided to try to teach it how to make images for
2118 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2119 of a plan to simplify the build system for
2120 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2121 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2122 the virtualbox images, but its current build system made multistrap
2123 based system for Dreamplug images, and it is lacking support for
2124 Raspberry Pi.&lt;/p&gt;
2125
2126 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2127 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2128 code and adjusted it to be able to build armel images on my amd64
2129 Debian laptop. I ended up giving vmdebootstrap five new options,
2130 allowing me to replicate the image creation process I use to make
2131 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2132 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2133 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2134 call debootstrap with --foreign and to copy the handler into the
2135 generated chroot before running the second stage. This allow
2136 vmdebootstrap to create armel images on an amd64 host. Next I added
2137 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2138 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2139 given file system type, allowing me to create an image with a vfat
2140 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2141 variant&lt;/tt&gt; option to allow me to create smaller images without the
2142 Debian base system packages installed. Finally, I added an option
2143 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2144 as a boot loader. It is not needed on the Raspberry Pi and probably
2145 most other non-x86 architectures. The changes were accepted by the
2146 upstream author of vmdebootstrap yesterday and today, and is now
2147 available from
2148 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2149 upstream project page&lt;/a&gt;.&lt;/p&gt;
2150
2151 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2152 create a small script (the customize script) to add the non-free
2153 binary blob needed to boot the Raspberry Pi and the APT source
2154 list:&lt;/p&gt;
2155
2156 &lt;p&gt;&lt;pre&gt;
2157 #!/bin/sh
2158 set -e # Exit on first error
2159 rootdir=&quot;$1&quot;
2160 cd &quot;$rootdir&quot;
2161 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2162 deb http://http.debian.net/debian/ jessie main contrib non-free
2163 EOF
2164 # Install non-free binary blob needed to boot Raspberry Pi. This
2165 # install a kernel somewhere too.
2166 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2167 -O $rootdir/usr/bin/rpi-update
2168 chmod a+x $rootdir/usr/bin/rpi-update
2169 mkdir -p $rootdir/lib/modules
2170 touch $rootdir/boot/start.elf
2171 chroot $rootdir rpi-update
2172 &lt;/pre&gt;&lt;/p&gt;
2173
2174 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2175 to build the image:&lt;/p&gt;
2176
2177 &lt;pre&gt;
2178 sudo ./vmdebootstrap \
2179 --variant minbase \
2180 --arch armel \
2181 --distribution jessie \
2182 --mirror http://http.debian.net/debian \
2183 --image test.img \
2184 --size 600M \
2185 --bootsize 64M \
2186 --boottype vfat \
2187 --log-level debug \
2188 --verbose \
2189 --no-kernel \
2190 --no-extlinux \
2191 --root-password raspberry \
2192 --hostname raspberrypi \
2193 --foreign /usr/bin/qemu-arm-static \
2194 --customize `pwd`/customize \
2195 --package netbase \
2196 --package git-core \
2197 --package binutils \
2198 --package ca-certificates \
2199 --package wget \
2200 --package kmod
2201 &lt;/pre&gt;&lt;/p&gt;
2202
2203 &lt;p&gt;The list of packages being installed are the ones needed by
2204 rpi-update to make the image bootable on the Raspberry Pi, with the
2205 exception of netbase, which is needed by debootstrap to find
2206 /etc/hosts with the minbase variant. I really wish there was a way to
2207 set up an Raspberry Pi using only packages in the Debian archive, but
2208 that is not possible as far as I know, because it boots from the GPU
2209 using a non-free binary blob.&lt;/p&gt;
2210
2211 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2212 probably a few others installed. I have not checked the complete
2213 build dependency list.&lt;/p&gt;
2214
2215 &lt;p&gt;The resulting image will not use the hardware floating point unit
2216 on the Raspberry PI, because the armel architecture in Debian is not
2217 optimized for that use. So the images created will be a bit slower
2218 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2219 </description>
2220 </item>
2221
2222 <item>
2223 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2224 <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>
2225 <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>
2226 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2227 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2228 wider attention. I recommend signing and donating to each one of
2229 these. :)&lt;/p&gt;
2230
2231 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2232 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2233 Women program which is a Google Summer of Code like initiative to get
2234 more women involved in free software. One debian sponsor has offered
2235 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2236 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2237 hope you will to. :)&lt;/p&gt;
2238
2239 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2240 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2241 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2242 take place these days, and their need to fund the work. I&#39;ve already
2243 donated. Are you next?&lt;/p&gt;
2244
2245 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2246 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2247 statement under the heading
2248 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2249 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2250 Norwegian government. So far 499 signatures. I hope you will sign it
2251 too.&lt;/p&gt;
2252 </description>
2253 </item>
2254
2255 <item>
2256 <title>Videos about the Freedombox project - for inspiration and learning</title>
2257 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2258 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2259 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2260 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2261 project&lt;/a&gt; have been going on for a while, and have presented the
2262 vision, ideas and solution several places. Here is a little
2263 collection of videos of talks and presentation of the project.&lt;/p&gt;
2264
2265 &lt;ul&gt;
2266
2267 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2268 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2269
2270 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2271 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2272
2273 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2274 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2275 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2276 (Youtube)&lt;/li&gt;
2277
2278 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2279 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2280
2281 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2282 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2283
2284 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2285 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2286 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2287
2288 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2289 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2290 (Youtube)&lt;/li&gt;
2291
2292 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2293 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2294
2295 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2296 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2297
2298 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2299 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2300 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2301
2302 &lt;/ul&gt;
2303
2304 &lt;p&gt;A larger list is available from
2305 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2306 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2307
2308 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2309 Jessie is coming along quite well, and soon both Owncloud and using
2310 Tor should be available for testers of the Freedombox solution. :) In
2311 a few weeks I hope everything needed to test it is included in Debian.
2312 The withsqlite package is already in Debian, and the plinth package is
2313 pending in NEW. The third and vital part of that puzzle is the
2314 metapackage/setup framework, which is still pending an upload. Join
2315 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2316 (#freedombox on irc.debian.org)&lt;/a&gt; and
2317 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2318 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2319 </description>
2320 </item>
2321
2322 <item>
2323 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2324 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2325 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2326 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2327 <description>&lt;p&gt;I was introduced to the
2328 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2329 in 2010, when Eben Moglen presented his vision about serving the need
2330 of non-technical people to keep their personal information private and
2331 within the legal protection of their own homes. The idea is to give
2332 people back the power over their network and machines, and return
2333 Internet back to its intended peer-to-peer architecture. Instead of
2334 depending on a central service, the Freedombox will give everyone
2335 control over their own basic infrastructure.&lt;/p&gt;
2336
2337 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2338 taken priority. But this summers nasty news about the misuse of trust
2339 and privilege exercised by the &quot;western&quot; intelligence gathering
2340 communities increased my eagerness to contribute to a point where I
2341 actually started working on the project a while back.&lt;/p&gt;
2342
2343 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2344 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2345 create a simple and cheap Debian based appliance that anyone can hook
2346 up in their home and get access to secure and private services and
2347 communication. The initial deployment platform have been the
2348 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2349 which is a piece of hardware I do not own. So to be able to test what
2350 the current Freedombox setup look like, I had to come up with a way to install
2351 it on some hardware I do have access to. I have rewritten the
2352 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2353 image build framework to use .deb packages instead of only copying
2354 setup into the boot images, and thanks to this rewrite I am able to
2355 set up any machine supported by Debian Wheezy as a Freedombox, using
2356 the previously mentioned deb (and a few support debs for packages
2357 missing in Debian).&lt;/p&gt;
2358
2359 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2360 scripts
2361 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2362 and a administrative web interface
2363 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2364 withsqlite), as well as a privacy enhancing proxy based on
2365 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2366 (freedombox-privoxy). There is also a web/javascript based XMPP
2367 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2368 trying (unsuccessfully so far) to talk to the XMPP server
2369 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2370 web interface is pluggable, and the goal is to use it to enable OpenID
2371 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2372 this is really working yet, see
2373 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2374 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2375 on github at the moment. The HTTP proxy is operational out of the
2376 box, and the admin web interface can be used to add/remove plinth
2377 users. I&#39;ve not been able to do anything else with it so far, but
2378 know there are several branches spread around github and other places
2379 with lots of half baked features.&lt;/p&gt;
2380
2381 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2382 following recipes should work to give you a test machine to poke
2383 at.&lt;/p&gt;
2384
2385 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2386
2387 &lt;ol&gt;
2388
2389 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2390 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2391 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2392 to the Debian installer:&lt;p&gt;
2393 &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;
2394
2395 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2396 install on.&lt;/li&gt;
2397
2398 &lt;li&gt;When the installation is finished and the machine have rebooted a
2399 few times, your Freedombox is ready for testing.&lt;/li&gt;
2400
2401 &lt;/ol&gt;
2402
2403 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2404
2405 &lt;ol&gt;
2406
2407 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2408 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2409 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2410 &lt;pre&gt;
2411 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2412 &lt;/pre&gt;&lt;/li&gt;
2413 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2414 &lt;pre&gt;
2415 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2416 apt-key add -
2417 apt-get update
2418 apt-get install freedombox-setup
2419 /usr/lib/freedombox/setup
2420 &lt;/pre&gt;&lt;/li&gt;
2421 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2422
2423 &lt;/ol&gt;
2424
2425 &lt;p&gt;You can test it on other architectures too, but because the
2426 freedombox-privoxy package is binary, it will only work as intended on
2427 the architectures where I have had time to build the binary and put it
2428 in my APT repository. But do not let this stop you. It is only a
2429 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2430
2431 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2432 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2433 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2434 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2435
2436 &lt;p&gt;Please let me know if this works for you, or if you have any
2437 problems. We gather on the IRC channel
2438 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2439 irc.debian.org and the
2440 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2441 mailing list&lt;/a&gt;.&lt;/p&gt;
2442
2443 &lt;p&gt;Once you get your freedombox operational, you can visit
2444 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2445 welcome screen (dead end - do not be surprised if you are unable to
2446 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2447 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2448 default password is &#39;secret&#39;.&lt;/p&gt;
2449 </description>
2450 </item>
2451
2452 <item>
2453 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2454 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2456 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2457 <description>&lt;p&gt;Earlier, I reported about
2458 &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
2459 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2460 told by IBM that the original disk should be thrown away. And as
2461 there no longer was a problem if I bricked the firmware, I decided
2462 today to try to install Intel firmware to replace the Lenovo firmware
2463 currently on the disk.&lt;/p&gt;
2464
2465 &lt;p&gt;I searched the Intel site for firmware, and found
2466 &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;
2467 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2468 according to the site should contain the latest firmware for SSD
2469 disks. I inserted the broken disk in one of my spare laptops and
2470 booted the ISO from a USB stick. The disk was recognized, but the
2471 program claimed the newest firmware already were installed and refused
2472 to insert any Intel firmware. So no change, and the disk is still
2473 unable to handle write load. :( I guess the only way to get them
2474 working would be if Lenovo releases new firmware. No idea how likely
2475 that is. Anyway, just blogging about this test for completeness. I
2476 got a working Samsung disk, and see no point in spending more time on
2477 the broken disks.&lt;/p&gt;
2478 </description>
2479 </item>
2480
2481 <item>
2482 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2483 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2484 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2485 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2486 <description>&lt;p&gt;Today I switched to
2487 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2488 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2489 my new Thinkpad X230, which was delivered with an
2490 &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
2491 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2492 sustained writes. My hardware supplier have been very forthcoming in
2493 trying to find a solution, and after first trying with another
2494 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2495 disk instead to fix it once and for all. The Samsung disk survived
2496 the installation of Debian with encrypted disks (filling the disk with
2497 random data during installation killed the first two), and I thus
2498 decided to trust it with my data. I have installed it as a Debian Edu
2499 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2500 server at home using Kerberos and LDAP, and will use it as my work
2501 station from now on.&lt;/p&gt;
2502
2503 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2504 Debian Wheezy default installation need to be tuned a bit to increase
2505 performance and increase life time of the disk. The Linux kernel and
2506 user space applications do not yet adjust automatically to such
2507 environment. To make it easier for my self, I created a draft Debian
2508 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2509 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2510 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2511 is set up to adjust the setup of the machine by just installing the
2512 package. If there is any non-SSD disk in the machine, the package
2513 will refuse to install, as I did not try to write any logic to sort
2514 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2515
2516 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2517 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2518 where I set up the machine with one large encrypted partition (in
2519 addition to /boot), put LVM on top of this and set up partitions on
2520 top of this again. See the README file in the package source for the
2521 references I used to pick the settings. At the moment these
2522 parameters are tuned:&lt;/p&gt;
2523
2524 &lt;ul&gt;
2525
2526 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2527 (adding discard to /etc/crypttab)&lt;/li&gt;
2528
2529 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2530 this case a cryptsetup partition) by changing issue_discards from
2531 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2532
2533 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2534 systems.&lt;/li&gt;
2535
2536 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2537 /etc/fstab.&lt;/li&gt;
2538
2539 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2540
2541 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2542 cron.daily).&lt;/li&gt;
2543
2544 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2545 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2546
2547 &lt;/ul&gt;
2548
2549 &lt;p&gt;During installation, I cancelled the part where the installer fill
2550 the disk with random data, as this would kill the SSD performance for
2551 little gain. My goal with the encrypted file system is to ensure
2552 those stealing my laptop end up with a brick and not a working
2553 computer. I have no hope in keeping the really resourceful people
2554 from getting the data on the disk (see
2555 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2556 Thus I concluded that adding the discard option to crypttab is the
2557 right thing to do.&lt;/p&gt;
2558
2559 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2560 it for SSD, but others recommended deadline and a benchmark I found
2561 indicated that deadline might be better for interactive use.&lt;/p&gt;
2562
2563 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2564 and ext4, but read that it would give a performance hit ever time a
2565 file is removed, and thought it best to that that slowdown once a day
2566 instead of during my work.&lt;/p&gt;
2567
2568 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2569 this is already done by Debian Edu.&lt;/p&gt;
2570
2571 &lt;p&gt;I have not yet started on the user space tuning. I expect
2572 iceweasel need some tuning, and perhaps other applications too, but
2573 have not yet had time to investigate those parts.&lt;/p&gt;
2574
2575 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2576 there.&lt;/p&gt;
2577
2578 &lt;p&gt;As for the answer to the question in the title of this blog post,
2579 as far as I know, the only solution I know about is to replace the
2580 disk. It might be possible to flash it with Intel firmware instead of
2581 the Lenovo firmware. But I have not tried and did not want to do so
2582 without approval from Lenovo as I wanted to keep the warranty on the
2583 disk until a solution was found and they wanted the broken disks
2584 back.&lt;/p&gt;
2585 </description>
2586 </item>
2587
2588 <item>
2589 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2590 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2591 <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>
2592 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2593 <description>&lt;p&gt;A few days ago, I wrote about
2594 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2595 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2596 was dying during installation because it is unable to cope with
2597 sustained write. My supplier is in contact with
2598 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2599 replacement disk to try to fix the problem. They decided to send an
2600 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2601
2602 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2603 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2604 same firmware version as the original. This time my hope raised
2605 slightly as the installation progressed, as the original disk used to
2606 die after 4-7% of the disk was written to, while this time it kept
2607 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2608 died again and I was back on square one. I still do not have a new
2609 laptop with a disk I can trust. I can not live with a disk that might
2610 lock up when I download a new
2611 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2612 other large files. I look forward to hearing from my supplier with
2613 the next proposal from Lenovo.&lt;/p&gt;
2614
2615 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2616 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2617 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2618 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2619 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2620 P/N 45N8295, P0C38732.&lt;/p&gt;
2621
2622 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2623 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2624 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2625 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2626 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2627 P/N 45N8295, P0C38732.&lt;/p&gt;
2628
2629 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2630 SA, date and WNPP values. Mentioning all the details here in case
2631 someone is able to use the information to find a way to identify the
2632 failing disk among working ones (if any such working disk actually
2633 exist).&lt;/p&gt;
2634 </description>
2635 </item>
2636
2637 <item>
2638 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2639 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2640 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2641 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2642 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2643 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2644 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2645 member assosiation NUUG&lt;/a&gt; and
2646 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2647 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2648 Bitraf&lt;/a&gt;.&lt;/p&gt;
2649
2650 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2651 welcome, and there is no fee to participate. There is on the other
2652 hand limited space, and only room for 30 people. Please put your name
2653 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2654 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2655 </description>
2656 </item>
2657
2658 <item>
2659 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2660 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2661 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2662 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2663 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2664 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2665 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2666 time to spend on it, and it took a while to find a model I believe
2667 will do the job, but two days ago the replacement finally arrived. I
2668 ended up picking a
2669 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2670 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2671 a roaming workstation, and it seemed to work flawlessly. But my
2672 second installation with encrypted disk was not as successful. More
2673 on that below.&lt;/p&gt;
2674
2675 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2676 important requirements (robust and with a good keyboard) are never
2677 listed in the feature list. But I did get good help from the search
2678 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2679 allowed me to limit the list of interesting laptops based on my other
2680 requirements. A bit surprising that SSD disk are not disks according
2681 to that search interface, so I had to drop specifying the number of
2682 disks from my search parameters. I also asked around among friends to
2683 get their impression on keyboards and robustness.&lt;/p&gt;
2684
2685 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2686 X41. I am not quite convinced about the keyboard, as it is
2687 significantly wider than my old keyboard, and I have to stretch my
2688 hand a lot more to reach the edges. But the key response is fairly
2689 good and the individual key shape is fairly easy to handle, so I hope
2690 I will get used to it. My old X40 was starting to fail, and I really
2691 needed a new laptop now. :)&lt;/p&gt;
2692
2693 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2694 visit to the BIOS during boot it disable it.&lt;/p&gt;
2695
2696 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2697 lock up during load. And this happen when installing Debian Wheezy
2698 with encrypted disk, while the disk is being filled with random data.
2699 I also tested to install Ubuntu Raring, and it happen there too if I
2700 reenable the code to fill the disk with random data (it is disabled by
2701 default in Ubuntu). And the bug with is already known. It was
2702 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2703 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2704 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2705 kernel developers as
2706 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2707 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2708 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2709 Lenovo forums, both for
2710 &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
2711 2012-11-10&lt;/a&gt; and for
2712 &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
2713 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2714 reports state that the disk lock up during use if many writes are done
2715 on the disk, so it is much no use to work around the installation
2716 problem and end up with a computer that can lock up at any moment.
2717 There is even a
2718 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2719 available&lt;/a&gt; that will lock up the hard drive after running a few
2720 minutes by writing to a file.&lt;/p&gt;
2721
2722 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2723 contacting PCHELP Norway (request 01D1FDP) which handle support
2724 requests for Lenovo, his first suggestion was to upgrade the disk
2725 firmware. Unfortunately there is no newer firmware available from
2726 Lenovo, as my disk already have the most recent one (version LF1i). I
2727 hope to hear more from him today and hope the problem can be
2728 fixed. :)&lt;/p&gt;
2729 </description>
2730 </item>
2731
2732 <item>
2733 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2734 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2735 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2736 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2737 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2738 trusty old Thinkpad X41. Unfortunately I did not have much time to
2739 spend on it, but today the replacement finally arrived. I ended up
2740 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2741 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2742 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2743 this, it is installing what I hope will be a more final installation,
2744 with a encrypted hard drive to ensure any dope head stealing it end up
2745 with an expencive door stop.&lt;/p&gt;
2746
2747 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2748 important requirements (robust and with a good keyboard) are never
2749 listed in the feature list. But I did get good help from the search
2750 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2751 allowed me to limit the list of interesting laptops based on my other
2752 requirements. A bit surprising that SSD disk are not disks, so I had
2753 to drop number of disks from my search parameters.&lt;/p&gt;
2754
2755 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2756 wider than my old keyboard, and I have to stretch my hand a lot more
2757 to reach the edges. But the key response is fairly good and the
2758 individual key shape is fairly easy to handle, so I hope I will get
2759 used to it. My old X40 was starting to fail, and I really needed a
2760 new laptop now. :)&lt;/p&gt;
2761
2762 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2763 </description>
2764 </item>
2765
2766 <item>
2767 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2768 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2770 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2771 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2772 perfectly capable of, and I have to do it manually to get things
2773 working. One such task is to find out what firmware packages are
2774 needed to get the hardware on my computer working. Most often this
2775 affect the wifi card, but some times it even affect the RAID
2776 controller or the ethernet card. Today I pushed version 0.4 of the
2777 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2778 including a new script isenkram-autoinstall-firmware handling the
2779 process of asking all the loaded kernel modules what firmware files
2780 they want, find debian packages providing these files and install the
2781 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2782
2783 &lt;p&gt;&lt;pre&gt;
2784 # isenkram-autoinstall-firmware
2785 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2786 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2787 info: locating packages with the requested firmware files
2788 info: Updating APT sources after adding non-free APT source
2789 info: trying to install firmware-ipw2x00
2790 firmware-ipw2x00
2791 firmware-ipw2x00
2792 Preconfiguring packages ...
2793 Selecting previously deselected package firmware-ipw2x00.
2794 (Reading database ... 259727 files and directories currently installed.)
2795 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2796 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2797 #
2798 &lt;/pre&gt;&lt;/p&gt;
2799
2800 &lt;p&gt;When all the requested firmware is present, a simple message is
2801 printed instead:&lt;/p&gt;
2802
2803 &lt;p&gt;&lt;pre&gt;
2804 # isenkram-autoinstall-firmware
2805 info: did not find any firmware files requested by loaded kernel modules. exiting
2806 #
2807 &lt;/pre&gt;&lt;/p&gt;
2808
2809 &lt;p&gt;It could use some polish, but it is already working well and saving
2810 me some time when setting up new machines. :)&lt;/p&gt;
2811
2812 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2813 kernel modules, and look up each one of them using modinfo, to find
2814 the firmware files listed in the module meta-information. Next, it
2815 download the Contents file from a nearby APT mirror, and search for
2816 the firmware files in this file to locate the package with the
2817 requested firmware file. If the package is in the non-free section, a
2818 non-free APT source is added and the package is installed using
2819 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2820 machine.&lt;/p&gt;
2821
2822 &lt;p&gt;I hope someone find time to implement a more polished version of
2823 this script as part of the hw-detect debian-installer module, to
2824 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2825 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2826 firmware during a PXE install when the packages already are available
2827 from the nearby Debian mirror.&lt;/p&gt;
2828 </description>
2829 </item>
2830
2831 <item>
2832 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2833 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2834 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2835 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2836 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2837 the screen just turn black when Linux boot, either during installation
2838 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2839 last few years, but only recently understood the cause. I&#39;ve seen it
2840 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2841 The reason seem to be in the wiring of some laptops. The system to
2842 control the screen background light is inverted, so when Linux try to
2843 turn the brightness fully on, it end up turning it off instead. I do
2844 not know which Linux drivers are affected, but this post is about the
2845 i915 driver used by the
2846 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2847 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2848
2849 &lt;p&gt;The problem can be worked around two ways. Either by adding
2850 i915.invert_brightness=1 as a kernel option, or by adding a file in
2851 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2852 option when it load the i915 kernel module. On Debian and Ubuntu, it
2853 can be done by running these commands as root:&lt;/p&gt;
2854
2855 &lt;pre&gt;
2856 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2857 update-initramfs -u -k all
2858 &lt;/pre&gt;
2859
2860 &lt;p&gt;Since March 2012 there is
2861 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2862 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2863 hardware have this problem, and get the driver to invert the
2864 brightness setting automatically. To use it, one need to add a row in
2865 &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
2866 intel_quirks array&lt;/a&gt; in the driver source
2867 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2868 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2869 number (vendor number 8086 is assumed) and subdevice vendor and device
2870 number.&lt;/p&gt;
2871
2872 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2873 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2874
2875 &lt;p&gt;&lt;pre&gt;
2876 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2877 3rd Gen Core processor Graphics Controller [8086:0156] \
2878 (rev 09) (prog-if 00 [VGA controller])
2879 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2880 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2881 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2882 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2883 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2884 Latency: 0
2885 Interrupt: pin A routed to IRQ 42
2886 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2887 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2888 Region 4: I/O ports at 4000 [size=64]
2889 Expansion ROM at &lt;unassigned&gt; [disabled]
2890 Capabilities: &lt;access denied&gt;
2891 Kernel driver in use: i915
2892 &lt;/pre&gt;&lt;/p&gt;
2893
2894 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2895
2896 &lt;p&gt;&lt;pre&gt;
2897 struct intel_quirk intel_quirks[] = {
2898 ...
2899 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2900 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2901 ...
2902 }
2903 &lt;/pre&gt;&lt;/p&gt;
2904
2905 &lt;p&gt;According to the kernel module instructions (as seen using
2906 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2907 invert_brightness flag should be sent to the
2908 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2909 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2910 developers. But my email about the laptop sent 2013-06-03 have not
2911 yet shown up in
2912 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2913 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2914 emails from non-subscribers. Because of this, I sent my patch also to
2915 the Debian bug tracking system instead as
2916 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2917 sure the patch is not lost.&lt;/p&gt;
2918
2919 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2920 with this problem working properly with Linux. If you use Gnome, your
2921 worries should be over at this point. But if you use KDE, there is
2922 something in KDE ignoring the invert_brightness setting and turning on
2923 the screen during login. I&#39;ve reported it to Debian as
2924 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2925 have no idea yet how to figure out exactly what subsystem is doing
2926 this. Perhaps you can help? Perhaps you know what the Gnome
2927 developers did to handle this, and this can give a clue to the KDE
2928 developers? Or you know where in KDE the screen brightness is changed
2929 during login? If so, please update the BTS report (or get in touch if
2930 you do not know how to update BTS).&lt;/p&gt;
2931
2932 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2933 acpi_backlight=vendor, to disable ACPI backlight support completely,
2934 as the ACPI information on the machine is trash and it is better to
2935 leave it to the intel video driver to control the screen
2936 backlight.&lt;/p&gt;
2937 </description>
2938 </item>
2939
2940 <item>
2941 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2942 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2943 <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>
2944 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2945 <description>&lt;p&gt;Two days ago, I asked
2946 &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
2947 I could install Linux on a Packard Bell EasyNote LV computer
2948 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2949 with the obstacles put in the way of Linux users on a laptop with UEFI
2950 and Windows 8.&lt;/p&gt;
2951
2952 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2953 secure booting or fast boot. I suspect fast boot was the problem,
2954 causing the firmware to boot directly from HD without considering any
2955 key presses and alternative devices, but do not know UEFI settings
2956 enough to tell.&lt;/p&gt;
2957
2958 &lt;p&gt;There is no way to install Linux on the machine in question without
2959 opening the box and disconnecting the hard drive! This is as far as I
2960 can tell, the only way to get access to the firmware setup menu
2961 without accepting the Windows 8 license agreement. I am told (and
2962 found description on how to) that it is possible to configure the
2963 firmware setup once booted into Windows 8. But as I believe the terms
2964 of that agreement are completely unacceptable, accepting the license
2965 was never an alternative. I do not enter agreements I do not intend
2966 to follow.&lt;/p&gt;
2967
2968 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2969 waste many hours on this, but luckily there was a way to get it to
2970 work. But I would not recommend it to anyone planning to run Linux on
2971 it, and I have become sceptical to Windows 8 certified laptops. Is
2972 this the way Linux will be forced out of the market place, by making
2973 it close to impossible for &quot;normal&quot; users to install Linux without
2974 accepting the Microsoft Windows license terms? Or at least not
2975 without risking to loose the warranty?&lt;/p&gt;
2976
2977 &lt;p&gt;I&#39;ve updated the
2978 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2979 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2980 do not have to struggle as much as I did to get Linux into the
2981 machine.&lt;/p&gt;
2982
2983 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2984 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2985 </description>
2986 </item>
2987
2988 <item>
2989 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2990 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2991 <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>
2992 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2993 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2994 new laptops for my parents and a few others. I bought Packard Bell
2995 Easynote LV to run Kubuntu on and use as their home computer. But I
2996 am completely unable to figure out how to install Linux on it. The
2997 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2998 instead of a BIOS to boot.&lt;/p&gt;
2999
3000 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3001 to get it to boot the Linux installer from my USB stick. I have yet
3002 to try the DVD install, and still hope it will work. when I turn on
3003 the computer, there is no information on what buttons to press to get
3004 the normal boot menu. I expect to get some boot menu to select PXE or
3005 USB stick booting. When booting, it first ask for the language to
3006 use, then for some regional settings, and finally if I will accept the
3007 Windows 8 terms of use. As these terms are completely unacceptable to
3008 me, I have no other choice but to turn off the computer and try again
3009 to get it to boot the Linux installer.&lt;/p&gt;
3010
3011 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3012 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3013 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3014 installed on this machine, please get in touch or update that wiki
3015 page. If I can&#39;t find a way to install Linux, I will have to return
3016 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3017
3018 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3019 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3020 on new Laptops?&lt;/p&gt;
3021 </description>
3022 </item>
3023
3024 <item>
3025 <title>How to transform a Debian based system to a Debian Edu installation</title>
3026 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3028 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3029 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3030 an operating system based on Debian intended for use in schools. It
3031 contain a turn-key solution for the computer network provided to
3032 pupils in the primary schools. It provide both the central server,
3033 network boot servers and desktop environments with heaps of
3034 educational software. The project was founded almost 12 years ago,
3035 2001-07-02. If you want to support the project, which is in need for
3036 cash to fund developer gatherings and other project related activity,
3037 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3038 donate some money&lt;/a&gt;.
3039
3040 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3041 lists and elsewhere, is the question on how to transform a Debian or
3042 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3043 hard, and last week I wrote a script to replicate the steps done by
3044 the Debian Edu installer.&lt;/p&gt;
3045
3046 &lt;p&gt;The script,
3047 &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;
3048 in the debian-edu-config package, will go through these six steps and
3049 transform an existing Debian Wheezy or Ubuntu (untested) installation
3050 into a Debian Edu Workstation:&lt;/p&gt;
3051
3052 &lt;ol&gt;
3053
3054 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3055 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3056 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3057 our configuration.&lt;/li&gt;
3058 &lt;li&gt;Preseed debconf database with profile setup in
3059 /etc/debian-edu/config, and run tasksel to install packages
3060 according to the profile specified in the config above,
3061 overriding some of the Debian automation machinery.&lt;/li&gt;
3062 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3063 that could not be done using preseeding.&lt;/li&gt;
3064 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3065
3066 &lt;/ol&gt;
3067
3068 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3069 replicated like this. Disk partitioning and LVM setup, for example.
3070 So this script just assume there is enough disk space to install all
3071 the needed packages.&lt;/p&gt;
3072
3073 &lt;p&gt;The script was created to help a Debian Edu student working on
3074 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3075 Debian Edu client, and using it he can take the existing
3076 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3077 transform it into a fully functioning Debian Edu Workstation (or
3078 Roaming Workstation, or whatever :).&lt;/p&gt;
3079
3080 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3081 If a LXDE based Roaming workstation is wanted instead, modify the
3082 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3083
3084 &lt;p&gt;&lt;pre&gt;
3085 PROFILE=&quot;Roaming-Workstation&quot;
3086 DESKTOP=&quot;lxde&quot;
3087 &lt;/pre&gt;&lt;/p&gt;
3088
3089 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3090 the cloud, by starting with a virtual Debian installation at some
3091 virtual hosting service and setting up all the services on first
3092 boot.&lt;/p&gt;
3093 </description>
3094 </item>
3095
3096 <item>
3097 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3098 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3099 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3100 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3101 <description>&lt;P&gt;In January,
3102 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3103 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3104 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3105 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3106 marvellous construction system from Denmark. We also created
3107 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3108 a place to take notes and write down our plans and hopes. And several
3109 people showed up to help. I was very happy to see the effect of my
3110 call. Since the small start, we have a debtags tag
3111 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3112 tag for LEGO related packages, and now count 10 packages related to
3113 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3114
3115 &lt;p&gt;&lt;table&gt;
3116 &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;
3117 &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;
3118 &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;
3119 &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;
3120 &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;
3121 &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;
3122 &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;
3123 &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;
3124 &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;
3125 &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;
3126 &lt;/table&gt;&lt;/p&gt;
3127
3128 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3129 currently available in Jessie/testing. leocad is so far only
3130 available in experimental.&lt;/p&gt;
3131
3132 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3133 adding the rest of the great free software tools available on Linux
3134 for LEGO designers.&lt;/p&gt;
3135 </description>
3136 </item>
3137
3138 <item>
3139 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3140 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3141 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3142 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3143 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3144 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3145 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3146 Debian release, and I expect to move my machines at home over to it fairly
3147 soon.&lt;/p&gt;
3148
3149 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3150 in particular make me very happy to see included. The
3151 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3152 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3153 included for the first time. Alongside similar programs like
3154 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3155 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3156 it allow for visual programming where syntax errors can not happen,
3157 and a friendly programming environment for learning to control the
3158 computer. Scratch will also be included in the next release of Debian
3159 Edu.&lt;/a&gt;
3160
3161 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3162 Edu/Skolelinux release too. The
3163 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3164 alpha release&lt;/a&gt; went out last week, and the next should soon
3165 follow.&lt;p&gt;
3166 </description>
3167 </item>
3168
3169 <item>
3170 <title>Isenkram 0.2 finally in the Debian archive</title>
3171 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3172 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3173 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3174 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3175 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3176 for many months. I uploaded it to the Debian experimental suite
3177 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3178
3179 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3180 install to work with a pluggable hardware device. The suggestion pop
3181 up when the device is plugged in. For example if a Lego Mindstorm NXT
3182 is inserted, it will suggest to install the program needed to program
3183 the NXT controller. Give it a go, and report bugs and suggestions to
3184 BTS. :)&lt;/p&gt;
3185 </description>
3186 </item>
3187
3188 <item>
3189 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3190 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3192 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3193 <description>&lt;p&gt;My
3194 &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
3195 bitcoin related blog post&lt;/a&gt; mentioned that the new
3196 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3197 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3198 2013-01-19, and have been available in unstable since then. It was
3199 automatically copied to Ubuntu, and is available in their Raring
3200 version too.&lt;/p&gt;
3201
3202 &lt;p&gt;But there is a strange problem with the build that block this new
3203 version from being available on the i386 and kfreebsd-i386
3204 architectures. For some strange reason, the autobuilders in Debian
3205 for these architectures fail to run the test suite on these
3206 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3207 We are so far unable to reproduce it when building it manually, and
3208 no-one have been able to propose a fix. If you got an idea what is
3209 failing, please let us know via the BTS.&lt;/p&gt;
3210
3211 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3212 I often run low on disk space, is the fact that the client will exit
3213 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3214 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3215 it. :)&lt;/p&gt;
3216
3217 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3218 activities, please send Bitcoin donations to my address
3219 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3220 </description>
3221 </item>
3222
3223 <item>
3224 <title>Welcome to the world, Isenkram!</title>
3225 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3226 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3227 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3228 <description>&lt;p&gt;Yesterday, I
3229 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3230 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3231 pluggable hardware devices, which I
3232 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3233 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3234 up, and caused me to really want to to open up the development to more
3235 people. But before I did this, I want to come up with a sensible name
3236 for this project. Today I finally decided on a new name, and I have
3237 renamed the project from hw-support-handler to this new name. In the
3238 process, I moved the source to git and made it available as a
3239 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3240 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3241 To fetch and build the latest version of the source, use&lt;/p&gt;
3242
3243 &lt;pre&gt;
3244 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3245 cd isenkram &amp;&amp; git-buildpackage -us -uc
3246 &lt;/pre&gt;
3247
3248 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3249 want to hack on the source or improve the package, please go ahead.
3250 But please talk to me first on IRC or via email before you do major
3251 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3252
3253 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3254 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3255 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3256 the German word eisenkram, for those that are familiar with that
3257 word.&lt;/p&gt;
3258
3259 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3260 instructions, to avoid confusing people with an error from the signing
3261 process.&lt;/p&gt;
3262
3263 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3264 clone argument to avoid the need for authentication.&lt;/p&gt;
3265 </description>
3266 </item>
3267
3268 <item>
3269 <title>First prototype ready making hardware easier to use in Debian</title>
3270 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3271 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3272 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3273 <description>&lt;p&gt;Early this month I set out to try to
3274 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3275 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3276 prototype is working, and it is ready for a larger audience. To test
3277 it, fetch the
3278 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3279 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3280 package. You might have to log out and in again activate the
3281 autostart script.&lt;/p&gt;
3282
3283 &lt;p&gt;The design is simple:&lt;/p&gt;
3284
3285 &lt;ul&gt;
3286
3287 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3288 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3289
3290 &lt;li&gt;This program listen for kernel events about new hardware (directly
3291 from the kernel like udev does), not using HAL dbus events as I
3292 initially did.&lt;/li&gt;
3293
3294 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3295 the APT database, a database
3296 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3297 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3298
3299 &lt;li&gt;If a package is mapped to the hardware in question, the package
3300 isn&#39;t installed yet and this is the first time the hardware was
3301 plugged in, show a desktop notification suggesting to install the
3302 package or packages.&lt;/li&gt;
3303
3304 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3305 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3306
3307 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3308 package while showing progress information in a window.&lt;/li&gt;
3309
3310 &lt;/ul&gt;
3311
3312 &lt;p&gt;I still need to come up with a better name for the system. Here
3313 are some screen shots showing the prototype in action. First the
3314 notification, then the password request, and finally the request to
3315 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3316
3317 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3318 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3319 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3320 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3321 &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;
3322
3323 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3324 is already useful. The database of hardware to package mappings also
3325 need more work. It is currently compatible with the Ubuntu way of
3326 storing such information in the package control file, but could be
3327 changed to use other formats instead or in addition to the current
3328 method. I&#39;ve dropped the use of discover for this mapping, as the
3329 modalias approach is more flexible and easier to use on Linux as long
3330 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3331
3332 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3333 here is the command required to check out and build the source: Use
3334 &#39;&lt;tt&gt;svn checkout
3335 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3336 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3337 devscripts package.&lt;/p&gt;
3338
3339 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3340 renamed to Isenkram and the source moved from the Debian Edu
3341 subversion repository to a Debian collab-maint git repository. See
3342 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3343 instructions&lt;/a&gt; for details.&lt;/p&gt;
3344 </description>
3345 </item>
3346
3347 <item>
3348 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3349 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3350 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3351 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3352 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3353 suddenly in bed. With a quiet whimper, it went completely quiet and
3354 black. The power button was no longer able to turn it on. It was a
3355 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3356 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3357 Compaq I had before that. Now I need to find a replacement. To keep
3358 going during Christmas, I moved the one year old SSD disk to my old
3359 X40 where it fitted (only one I had left that could use it), but it is
3360 not a durable solution.
3361
3362 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3363 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3364
3365 &lt;ul&gt;
3366
3367 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3368 than A4).&lt;/li&gt;
3369 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3370 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3371 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3372 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3373 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3374 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3375 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3376 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3377 size).&lt;/li&gt;
3378 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3379 X.org packages.&lt;/li&gt;
3380 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3381 the time).
3382
3383 &lt;/ul&gt;
3384
3385 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3386 list. The reason is simply that the specifications on laptops the
3387 last 10-15 years have been sufficient for my needs, and I have to look
3388 at other features to choose my laptop. But are there still made as
3389 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3390 robust, and Thinkpads seem to be heading in the wrong direction since
3391 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3392 still be useful.&lt;/p&gt;
3393
3394 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3395 external keyboard? I&#39;ll have to check the
3396 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3397 well-supported laptops, or perhaps just buy one preinstalled from one
3398 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3399 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3400 </description>
3401 </item>
3402
3403 <item>
3404 <title>How to find a browser plugin supporting a given MIME type</title>
3405 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3406 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3407 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3408 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3409 install to get support for a given MIME type. Thanks to
3410 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3411 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3412 Unfortunately, not very many packages provide the needed meta
3413 information, Anyway, here is a small script to look up all browser
3414 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3415
3416 &lt;pre&gt;
3417 #!/usr/bin/python
3418 import sys
3419 import apt
3420 def pkgs_handling_mimetype(mimetype):
3421 cache = apt.Cache()
3422 cache.open(None)
3423 thepkgs = []
3424 for pkg in cache:
3425 version = pkg.candidate
3426 if version is None:
3427 version = pkg.installed
3428 if version is None:
3429 continue
3430 record = version.record
3431 if not record.has_key(&#39;Npp-MimeType&#39;):
3432 continue
3433 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3434 for t in mime_types:
3435 t = t.rstrip().strip()
3436 if t == mimetype:
3437 thepkgs.append(pkg.name)
3438 return thepkgs
3439 mimetype = &quot;audio/ogg&quot;
3440 if 1 &lt; len(sys.argv):
3441 mimetype = sys.argv[1]
3442 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3443 for pkg in pkgs_handling_mimetype(mimetype):
3444 print &quot; %s&quot; %pkg
3445 &lt;/pre&gt;
3446
3447 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3448
3449 &lt;pre&gt;
3450 % ./apt-find-browserplug-for-mimetype
3451 Browser plugin packages supporting audio/ogg:
3452 gecko-mediaplayer
3453 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3454 Browser plugin packages supporting application/x-shockwave-flash:
3455 browser-plugin-gnash
3456 %
3457 &lt;/pre&gt;
3458
3459 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3460 itself to query for plugins and propose to install the needed
3461 packages. It would be great if Debian supported such feature too. Is
3462 anyone working on adding it?&lt;/p&gt;
3463
3464 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3465 request for icweasel support for this feature is
3466 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3467 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3468 of manpower and wish for a different design is the reason thus feature
3469 is not yet in iceweasel from Debian.&lt;/p&gt;
3470 </description>
3471 </item>
3472
3473 <item>
3474 <title>What is the most supported MIME type in Debian?</title>
3475 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3476 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3477 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3478 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3479 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3480 proposal to make it possible for a Desktop application to propose to
3481 the user some package to install to gain support for a given MIME
3482 type, font, library etc. that is currently missing. With such
3483 mechanism in place, it would be possible for the desktop to
3484 automatically propose and install leocad if some LDraw file is
3485 downloaded by the browser.&lt;/p&gt;
3486
3487 &lt;p&gt;To get some idea about the current content of the archive, I decided
3488 to write a simple program to extract all .desktop files from the
3489 Debian archive and look up the claimed MIME support there. The result
3490 can be found on the
3491 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3492 site&lt;/a&gt;. Using the collected information, it become possible to
3493 answer the question in the title. Here are the 20 most supported MIME
3494 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3495 The complete list is available from the link above.&lt;/p&gt;
3496
3497 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3498
3499 &lt;pre&gt;
3500 count MIME type
3501 ----- -----------------------
3502 32 text/plain
3503 30 audio/mpeg
3504 29 image/png
3505 28 image/jpeg
3506 27 application/ogg
3507 26 audio/x-mp3
3508 25 image/tiff
3509 25 image/gif
3510 22 image/bmp
3511 22 audio/x-wav
3512 20 audio/x-flac
3513 19 audio/x-mpegurl
3514 18 video/x-ms-asf
3515 18 audio/x-musepack
3516 18 audio/x-mpeg
3517 18 application/x-ogg
3518 17 video/mpeg
3519 17 audio/x-scpls
3520 17 audio/ogg
3521 16 video/x-ms-wmv
3522 &lt;/pre&gt;
3523
3524 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3525
3526 &lt;pre&gt;
3527 count MIME type
3528 ----- -----------------------
3529 33 text/plain
3530 32 image/png
3531 32 image/jpeg
3532 29 audio/mpeg
3533 27 image/gif
3534 26 image/tiff
3535 26 application/ogg
3536 25 audio/x-mp3
3537 22 image/bmp
3538 21 audio/x-wav
3539 19 audio/x-mpegurl
3540 19 audio/x-mpeg
3541 18 video/mpeg
3542 18 audio/x-scpls
3543 18 audio/x-flac
3544 18 application/x-ogg
3545 17 video/x-ms-asf
3546 17 text/html
3547 17 audio/x-musepack
3548 16 image/x-xbitmap
3549 &lt;/pre&gt;
3550
3551 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3552
3553 &lt;pre&gt;
3554 count MIME type
3555 ----- -----------------------
3556 31 text/plain
3557 31 image/png
3558 31 image/jpeg
3559 29 audio/mpeg
3560 28 application/ogg
3561 27 image/gif
3562 26 image/tiff
3563 26 audio/x-mp3
3564 23 audio/x-wav
3565 22 image/bmp
3566 21 audio/x-flac
3567 20 audio/x-mpegurl
3568 19 audio/x-mpeg
3569 18 video/x-ms-asf
3570 18 video/mpeg
3571 18 audio/x-scpls
3572 18 application/x-ogg
3573 17 audio/x-musepack
3574 16 video/x-ms-wmv
3575 16 video/x-msvideo
3576 &lt;/pre&gt;
3577
3578 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3579 information mentioned in DEP-11. I have not yet had time to look at
3580 it, but hope the PackageKit people in Debian are on top of these
3581 issues.&lt;/p&gt;
3582
3583 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3584 discovering a typo in my script.&lt;/p&gt;
3585 </description>
3586 </item>
3587
3588 <item>
3589 <title>Using modalias info to find packages handling my hardware</title>
3590 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3591 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3592 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3593 <description>&lt;p&gt;Yesterday, I wrote about the
3594 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3595 values provided by the Linux kernel&lt;/a&gt; following my hope for
3596 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3597 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3598 modalias values attached to package names can be used to map packages
3599 to hardware. This allow the system to look up and suggest relevant
3600 packages when I plug in some new hardware into my machine, and replace
3601 discover and discover-data as the database used to map hardware to
3602 packages.&lt;/p&gt;
3603
3604 &lt;p&gt;I create a modaliases file with entries like the following,
3605 containing package name, kernel module name (if relevant, otherwise
3606 the package name) and globs matching the relevant hardware
3607 modalias.&lt;/p&gt;
3608
3609 &lt;p&gt;&lt;blockquote&gt;
3610 Package: package-name
3611 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3612 &lt;/blockquote&gt;&lt;/p&gt;
3613
3614 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3615 for a given modalias value using this file.&lt;/p&gt;
3616
3617 &lt;p&gt;An entry like this would suggest the video and picture application
3618 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3619
3620 &lt;p&gt;&lt;blockquote&gt;
3621 Package: cheese
3622 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3623 &lt;/blockquote&gt;&lt;/p&gt;
3624
3625 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3626 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3627
3628 &lt;p&gt;&lt;blockquote&gt;
3629 Package: pcmciautils
3630 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3631 &lt;/blockquote&gt;&lt;/p&gt;
3632
3633 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3634 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3635
3636 &lt;p&gt;&lt;blockquote&gt;
3637 Package: colorhug-client
3638 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3639 &lt;/blockquote&gt;&lt;/p&gt;
3640
3641 &lt;p&gt;I believe the format is compatible with the format of the Packages
3642 file in the Debian archive. Ubuntu already uses their Packages file
3643 to store their mappings from packages to hardware.&lt;/p&gt;
3644
3645 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3646 announce the hardware it support in a way my prototype understand.
3647 This allow those publishing packages in an APT source outside the
3648 Debian archive as well as those backporting packages to make sure the
3649 hardware mapping are included in the package meta information. I&#39;ve
3650 tested such header in the pymissile package, and its modalias mapping
3651 is working as it should with my prototype. It even made it to Ubuntu
3652 Raring.&lt;/p&gt;
3653
3654 &lt;p&gt;To test if it was possible to look up supported hardware using only
3655 the shell tools available in the Debian installer, I wrote a shell
3656 implementation of the lookup code. The idea is to create files for
3657 each modalias and let the shell do the matching. Please check out and
3658 try the
3659 &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;
3660 shell script. It run without any extra dependencies and fetch the
3661 hardware mappings from the Debian archive and the subversion
3662 repository where I currently work on my prototype.&lt;/p&gt;
3663
3664 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3665 install yubikey-personalization:&lt;/p&gt;
3666
3667 &lt;p&gt;&lt;blockquote&gt;
3668 % ./hw-support-lookup
3669 &lt;br&gt;yubikey-personalization
3670 &lt;br&gt;%
3671 &lt;/blockquote&gt;&lt;/p&gt;
3672
3673 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3674 propose to install the pcmciautils package:&lt;/p&gt;
3675
3676 &lt;p&gt;&lt;blockquote&gt;
3677 % ./hw-support-lookup
3678 &lt;br&gt;pcmciautils
3679 &lt;br&gt;%
3680 &lt;/blockquote&gt;&lt;/p&gt;
3681
3682 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3683 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3684 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3685
3686 &lt;p&gt;It could be possible to generate several of the mappings between
3687 packages and hardware. One source would be to look at packages with
3688 kernel modules, ie packages with *.ko files in /lib/modules/, and
3689 extract their modalias information. Another would be to look at
3690 packages with udev rules, ie packages with files in
3691 /lib/udev/rules.d/, and extract their vendor/model information to
3692 generate a modalias matching rule. I have not tested any of these to
3693 see if it work.&lt;/p&gt;
3694
3695 &lt;p&gt;If you want to help implementing a system to let us propose what
3696 packages to install when new hardware is plugged into a Debian
3697 machine, please send me an email or talk to me on
3698 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3699 </description>
3700 </item>
3701
3702 <item>
3703 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3704 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3705 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3706 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3707 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3708 information, to find the packages that support a given piece of
3709 hardware, I refreshed my memory regarding modalias values, and decided
3710 to document the details. Here are my findings so far, also available
3711 in
3712 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3713 Debian Edu subversion repository&lt;/a&gt;:
3714
3715 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3716
3717 &lt;p&gt;This document try to explain what the different types of modalias
3718 values stands for. It is in part based on information from
3719 &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;,
3720 &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;,
3721 &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
3722 &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;.
3723
3724 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3725 this shell script:&lt;/p&gt;
3726
3727 &lt;pre&gt;
3728 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3729 &lt;/pre&gt;
3730
3731 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3732 using modinfo:&lt;/p&gt;
3733
3734 &lt;pre&gt;
3735 % /sbin/modinfo psmouse | grep alias:
3736 alias: serio:ty05pr*id*ex*
3737 alias: serio:ty01pr*id*ex*
3738 %
3739 &lt;/pre&gt;
3740
3741 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3742
3743 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3744 Bridge memory controller:&lt;/p&gt;
3745
3746 &lt;p&gt;&lt;blockquote&gt;
3747 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3748 &lt;/blockquote&gt;&lt;/p&gt;
3749
3750 &lt;p&gt;This represent these values:&lt;/p&gt;
3751
3752 &lt;pre&gt;
3753 v 00008086 (vendor)
3754 d 00002770 (device)
3755 sv 00001028 (subvendor)
3756 sd 000001AD (subdevice)
3757 bc 06 (bus class)
3758 sc 00 (bus subclass)
3759 i 00 (interface)
3760 &lt;/pre&gt;
3761
3762 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3763 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3764 0600. The 0600 class is a host bridge. Other useful bus values are
3765 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3766
3767 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3768 means.&lt;/p&gt;
3769
3770 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3771
3772 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3773 USB hub in a laptop:&lt;/p&gt;
3774
3775 &lt;p&gt;&lt;blockquote&gt;
3776 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3777 &lt;/blockquote&gt;&lt;/p&gt;
3778
3779 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3780
3781 &lt;pre&gt;
3782 v 1D6B (device vendor)
3783 p 0001 (device product)
3784 d 0206 (bcddevice)
3785 dc 09 (device class)
3786 dsc 00 (device subclass)
3787 dp 00 (device protocol)
3788 ic 09 (interface class)
3789 isc 00 (interface subclass)
3790 ip 00 (interface protocol)
3791 &lt;/pre&gt;
3792
3793 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3794 class is in the interface class section. For a simple USB web camera,
3795 these alias entries show up:&lt;/p&gt;
3796
3797 &lt;p&gt;&lt;blockquote&gt;
3798 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3799 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3800 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3801 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3802 &lt;/blockquote&gt;&lt;/p&gt;
3803
3804 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3805 camera), 0101 is audio control device and 0102 is audio streaming (aka
3806 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3807
3808 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3809
3810 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3811 receiver in a Thinkpad X40:&lt;/p&gt;
3812
3813 &lt;p&gt;&lt;blockquote&gt;
3814 acpi:IBM0071:PNP0511:
3815 &lt;/blockquote&gt;&lt;/p&gt;
3816
3817 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3818
3819 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3820
3821 &lt;p&gt;The DMI table contain lots of information about the computer case
3822 and model. This is an entry for a IBM Thinkpad X40, fetched from
3823 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3824
3825 &lt;p&gt;&lt;blockquote&gt;
3826 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3827 &lt;/blockquote&gt;&lt;/p&gt;
3828
3829 &lt;p&gt;The values present are&lt;/p&gt;
3830
3831 &lt;pre&gt;
3832 bvn IBM (BIOS vendor)
3833 bvr 1UETB6WW(1.66) (BIOS version)
3834 bd 06/15/2005 (BIOS date)
3835 svn IBM (system vendor)
3836 pn 2371H4G (product name)
3837 pvr ThinkPadX40 (product version)
3838 rvn IBM (board vendor)
3839 rn 2371H4G (board name)
3840 rvr NotAvailable (board version)
3841 cvn IBM (chassis vendor)
3842 ct 10 (chassis type)
3843 cvr NotAvailable (chassis version)
3844 &lt;/pre&gt;
3845
3846 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3847 found in the dmidecode source:&lt;/p&gt;
3848
3849 &lt;pre&gt;
3850 3 Desktop
3851 4 Low Profile Desktop
3852 5 Pizza Box
3853 6 Mini Tower
3854 7 Tower
3855 8 Portable
3856 9 Laptop
3857 10 Notebook
3858 11 Hand Held
3859 12 Docking Station
3860 13 All In One
3861 14 Sub Notebook
3862 15 Space-saving
3863 16 Lunch Box
3864 17 Main Server Chassis
3865 18 Expansion Chassis
3866 19 Sub Chassis
3867 20 Bus Expansion Chassis
3868 21 Peripheral Chassis
3869 22 RAID Chassis
3870 23 Rack Mount Chassis
3871 24 Sealed-case PC
3872 25 Multi-system
3873 26 CompactPCI
3874 27 AdvancedTCA
3875 28 Blade
3876 29 Blade Enclosing
3877 &lt;/pre&gt;
3878
3879 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3880 table. For example my home server is a tower, but the DMI modalias
3881 claim it is a desktop.&lt;/p&gt;
3882
3883 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3884
3885 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3886 test machine:&lt;/p&gt;
3887
3888 &lt;p&gt;&lt;blockquote&gt;
3889 serio:ty01pr00id00ex00
3890 &lt;/blockquote&gt;&lt;/p&gt;
3891
3892 &lt;p&gt;The values present are&lt;/p&gt;
3893
3894 &lt;pre&gt;
3895 ty 01 (type)
3896 pr 00 (prototype)
3897 id 00 (id)
3898 ex 00 (extra)
3899 &lt;/pre&gt;
3900
3901 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3902 the valid values are.&lt;/p&gt;
3903
3904 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3905
3906 &lt;p&gt;There are heaps of other modalias subtypes according to
3907 file2alias.c. There is the rest of the list from that source: amba,
3908 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3909 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3910 vmbus, x86cpu and zorro. I did not spend time documenting all of
3911 these, as they do not seem relevant for my intended use with mapping
3912 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3913
3914 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3915
3916 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3917 one can use the following shell script:&lt;/p&gt;
3918
3919 &lt;pre&gt;
3920 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3921 echo &quot;$id&quot; ; \
3922 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3923 done
3924 &lt;/pre&gt;
3925
3926 &lt;p&gt;The output can look like this (only the first few entries as the
3927 list is very long on my test machine):&lt;/p&gt;
3928
3929 &lt;pre&gt;
3930 acpi:ACPI0003:
3931 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3932 acpi:device:
3933 FATAL: Module acpi:device: not found.
3934 acpi:IBM0068:
3935 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3936 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3937 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3938 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3939 acpi:IBM0071:PNP0511:
3940 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3941 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3942 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3943 [...]
3944 &lt;/pre&gt;
3945
3946 &lt;p&gt;If you want to help implementing a system to let us propose what
3947 packages to install when new hardware is plugged into a Debian
3948 machine, please send me an email or talk to me on
3949 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3950
3951 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3952 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3953 in /sys/ with space in them.&lt;/p&gt;
3954 </description>
3955 </item>
3956
3957 <item>
3958 <title>Moved the pymissile Debian packaging to collab-maint</title>
3959 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3960 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3961 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3962 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3963 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3964 Launcher and updated the Debian package
3965 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3966 sure udev will fix the device permissions when it is plugged in. I
3967 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3968 hopefully make the package be proposed by jockey in Ubuntu when a user
3969 plug in his rocket launcher. In the process I moved the source to a
3970 git repository under collab-maint, to make it easier for any DD to
3971 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3972 is not very active, but the software still work for me even after five
3973 years of relative silence. The new git repository is not listed in
3974 the uploaded package yet, because I want to test the other changes a
3975 bit more before I upload the new version. If you want to check out
3976 the new version with a .desktop file included, visit the
3977 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3978 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3979 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3980 </description>
3981 </item>
3982
3983 <item>
3984 <title>Lets make hardware dongles easier to use in Debian</title>
3985 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3986 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3987 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3988 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3989 general, is that there is a great package management system with the
3990 ability to automatically install software packages by downloading them
3991 from the distribution mirrors, but no way to get it to automatically
3992 install the packages I need to use the hardware I plug into my
3993 machine. Even if the package to use it is easily available from the
3994 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3995 suggest to automatically install the python-nxt, nbc and t2n packages
3996 I need to talk to it. When I plug in a Yubikey, it could propose the
3997 yubikey-personalization package. The information required to do this
3998 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3999
4000 &lt;p&gt;Some years ago, I proposed to
4001 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4002 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4003 simple:
4004
4005 &lt;ul&gt;
4006
4007 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4008 starting when a user log in.&lt;/li&gt;
4009
4010 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4011 hardware is inserted into the computer.&lt;/li&gt;
4012
4013 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4014 database mapping to packages, and take note of any non-installed
4015 packages.&lt;/li&gt;
4016
4017 &lt;li&gt;Show a message to the user proposing to install the discovered
4018 package, and make it easy to install it.&lt;/li&gt;
4019
4020 &lt;/ul&gt;
4021
4022 &lt;p&gt;I am not sure what the best way to implement this is, but my
4023 initial idea was to use dbus events to discover new hardware, the
4024 discover database to find packages and
4025 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4026 packages.&lt;/p&gt;
4027
4028 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4029 draft package is now checked into
4030 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4031 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4032 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4033 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4034 the relevant packages in Debian, and uploaded a new version
4035 2.2013.01.09 to unstable. I also discovered that the current
4036 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4037 package in Debian no longer discovered any USB devices, because
4038 /proc/bus/usb/devices is no longer present. I ported it to use
4039 libusb as a fall back option to get it working. The fixed package
4040 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4041 because of the freeze).&lt;/p&gt;
4042
4043 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4044 desktop notification to show up (only once, the first time it is
4045 inserted):&lt;/p&gt;
4046
4047 &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;
4048
4049 &lt;p&gt;For this prototype to be really useful, some way to automatically
4050 install the proposed packages by pressing the &quot;Please install
4051 program(s)&quot; button should to be implemented.&lt;/p&gt;
4052
4053 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4054 happen, please help me update the discover-data database with mappings
4055 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4056 list the package you would like to have installed when a given
4057 hardware device is inserted into your computer, and report bugs using
4058 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4059 such mapping, please let me know.&lt;/p&gt;
4060
4061 &lt;p&gt;This prototype need more work, and there are several questions that
4062 should be considered before it is ready for production use. Is dbus
4063 the correct way to detect new hardware? At the moment I look for HAL
4064 dbus events on the system bus, because that is the events I could see
4065 on my Debian Squeeze KDE desktop. Are there better events to use?
4066 How should the user be notified? Is the desktop notification
4067 mechanism the best option, or should the background daemon raise a
4068 popup instead? How should packages be installed? When should they
4069 not be installed?&lt;/p&gt;
4070
4071 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4072 please send me an email. :)&lt;/p&gt;
4073 </description>
4074 </item>
4075
4076 <item>
4077 <title>New IRC channel for LEGO designers using Debian</title>
4078 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4079 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4080 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4081 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4082 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4083 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4084 discovered I had to build all the tools myself because none were
4085 already in Debian Squeeze. If Debian support for LEGO is something
4086 you care about, please join me on the IRC channel
4087 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4088 irc.debian.org). There is a lot that could be done to improve the
4089 Debian support for LEGO designers. For example both CAD software
4090 and Mindstorm compilers are missing. :)&lt;/p&gt;
4091
4092 &lt;p&gt;Update 2012-01-03: A
4093 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4094 including links to Lego related packages is now available.&lt;/p&gt;
4095 </description>
4096 </item>
4097
4098 <item>
4099 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4100 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4101 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4102 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4103 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4104 year! I hope next year will prove to be a good year.&lt;/p&gt;
4105
4106 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4107 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4108 between each other with minimal overhead, is a very interesting
4109 experiment. And as I wrote a few days ago, the bitcoin situation in
4110 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4111 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4112 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4113 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4114 for one of the ftpmasters to approve the new bitcoin-qt package
4115 name.&lt;/p&gt;
4116
4117 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4118 team in Debian, you can easily test the package in Debian Squeeze
4119 using the following steps to get a set of working packages:&lt;/p&gt;
4120
4121 &lt;blockquote&gt;&lt;pre&gt;
4122 git clone git://git.debian.org/git/collab-maint/bitcoin
4123 cd bitcoin
4124 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4125 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4126 &lt;/pre&gt;&lt;/blockquote&gt;
4127
4128 &lt;p&gt;You might have to install some build dependencies as well. The
4129 list of commands should give you two packages, bitcoind and
4130 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4131 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4132 around 5.6 GiB of data on my machine at the moment. Make sure your
4133 ~/.bitcoin/ directory have lots of spare room if you want to download
4134 all the blocks. The client will warn if the disk is getting full, so
4135 there is not really a problem if you got too little room, but you will
4136 not be able to get all the features out of the client.&lt;/p&gt;
4137
4138 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4139 activities, please send Bitcoin donations to my address
4140 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4141 </description>
4142 </item>
4143
4144 <item>
4145 <title>A word on bitcoin support in Debian</title>
4146 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4147 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4148 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4149 <description>&lt;p&gt;It has been a while since I wrote about
4150 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4151 peer-to-peer based crypto-currency, and the reason is simply that I
4152 have been busy elsewhere. But two days ago, I started looking at the
4153 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4154 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4155 is now maintained by a
4156 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4157 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4158 owe a huge thank you to all these team members. :)
4159 But I was sad to discover that the bitcoin client is missing in
4160 Wheezy. It is only available in Sid (and an outdated client from
4161 backports). The client had several RC bugs registered in BTS blocking
4162 it from entering testing. To try to help the team and improve the
4163 situation, I spent some time providing patches and triaging the bug
4164 reports. I also had a look at the bitcoin package available from Matt
4165 Corallo in a
4166 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4167 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4168 Debian package.&lt;/p&gt;
4169
4170 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4171 IRC, I pushed several patches into the collab-maint git repository to
4172 improve the package. It now contains fixes for the RC issues (not from
4173 me, but fixed by Scott Howard), build rules for a Qt GUI client
4174 package, konqueror support for the bitcoin: URI and bash completion
4175 setup. As I work on Debian Squeeze, I also created
4176 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4177 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4178 it and try to integrate it into the git repository before uploading a
4179 new version to unstable.
4180
4181 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4182 centralized control currently exercised in the monetary system. I
4183 find it completely unacceptable that the USA government is collecting
4184 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4185 that the major credit card companies can block legal money
4186 transactions to Wikileaks. But for bitcoin to succeed, more people
4187 need to use bitcoins, and more people need to accept bitcoins when
4188 they sell products and services. Improving the bitcoin support in
4189 Debian is a small step in the right direction, but not enough.
4190 Unfortunately the user experience when browsing the web and wanting to
4191 pay with bitcoin is still not very good. The bitcoin: URI is a step
4192 in the right direction, but need to work in most or every browser in
4193 use. Also the bitcoin-qt client is too heavy to fire up to do a
4194 quick transaction. I believe there are other clients available, but
4195 have not tested them.&lt;/p&gt;
4196
4197 &lt;p&gt;My
4198 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4199 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4200 I received 20.15 BTC so far on the address I provided in my blog two
4201 years ago, as can be
4202 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4203 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4204 donation. The blockexplorer service demonstrates quite well that
4205 bitcoin is not quite anonymous and untracked. :) I wonder if the
4206 number of users have gone up since then. If you use bitcoin and want
4207 to show your support of my activity, please send Bitcoin donations to
4208 the same address as last time,
4209 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4210 </description>
4211 </item>
4212
4213 <item>
4214 <title>Git repository for song book for Computer Scientists</title>
4215 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4216 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4217 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4218 <description>&lt;p&gt;As I
4219 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4220 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4221 years ago, and today I finally found time to create a public
4222 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4223 repository for the project&lt;/a&gt;.&lt;/p&gt;
4224
4225 &lt;p&gt;If you want to help out, please clone the source and submit patches
4226 to the HTML version. To generate the PDF and PostScript version,
4227 please use prince XML, or let me know about a useful free software
4228 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4229
4230 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4231 PostScript formats at
4232 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4233 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4234 </description>
4235 </item>
4236
4237 <item>
4238 <title>Gratulerer med 19-årsdagen, Debian!</title>
4239 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4241 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4242 <description>&lt;p&gt;I dag fyller
4243 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4244 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4245 si gratulerer med dagen, Debian!&lt;/p&gt;
4246 </description>
4247 </item>
4248
4249 <item>
4250 <title>Song book for Computer Scientists</title>
4251 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4252 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4253 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4254 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4255 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4256 collecting computer related songs for use at parties. The original
4257 version was written in LaTeX, but a few years ago I got help from
4258 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4259 while keeping the ability to create a nice book in PDF format. I have
4260 not had time to maintain the book for a while now, and guess I should
4261 put it up on some public version control repository where others can
4262 help me extend and update the book. If anyone is volunteering to help
4263 me with this, send me an email. Also let me know if there are songs
4264 missing in my book.&lt;/p&gt;
4265
4266 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4267 me today that I really should let all my readers share the joys of
4268 singing out load about programming, computers and computer networks.
4269 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4270 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4271 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4272 Computer Science Songbook&lt;/a&gt;.
4273 </description>
4274 </item>
4275
4276 <item>
4277 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4278 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4279 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4280 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4281 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4282 around 1000 at the moment. To be able to get help from the vendors
4283 when something go wrong, we want to keep the firmware on the servers
4284 up to date. If the firmware isn&#39;t the latest and greatest, the
4285 vendors typically refuse to start debugging any problems until the
4286 firmware is upgraded. So before every reboot, we want to upgrade the
4287 firmware, and we would really like everyone handling servers at the
4288 university to do this themselves when they plan to reboot a machine.
4289 For that to happen we at the unix server admin group need to provide
4290 the tools to do so.&lt;/p&gt;
4291
4292 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4293 fetch and install the latest firmware for the servers we got. Most of
4294 our hardware are from Dell and HP, so I have focused on these servers
4295 so far. This blog post is about the Dell part.&lt;/P&gt;
4296
4297 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4298 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4299 with firmware information for all 11th generation servers, listing
4300 which firmware should be used on a given model and where on the FTP
4301 site I can find it. Using a simple perl XML parser I can then
4302 download the shell scripts Dell provides to do firmware upgrades from
4303 within Linux and reboot when all the firmware is primed and ready to
4304 be activated on the first reboot.&lt;/p&gt;
4305
4306 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4307 Are there anyone working on similar tools for firmware upgrading all
4308 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4309
4310 &lt;p&gt;&lt;pre&gt;
4311 #!/usr/bin/perl
4312 use strict;
4313 use warnings;
4314 use File::Temp qw(tempdir);
4315 BEGIN {
4316 # Install needed RHEL packages if missing
4317 my %rhelmodules = (
4318 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4319 );
4320 for my $module (keys %rhelmodules) {
4321 eval &quot;use $module;&quot;;
4322 if ($@) {
4323 my $pkg = $rhelmodules{$module};
4324 system(&quot;yum install -y $pkg&quot;);
4325 eval &quot;use $module;&quot;;
4326 }
4327 }
4328 }
4329 my $errorsto = &#39;pere@hungry.com&#39;;
4330
4331 upgrade_dell();
4332
4333 exit 0;
4334
4335 sub run_firmware_script {
4336 my ($opts, $script) = @_;
4337 unless ($script) {
4338 print STDERR &quot;fail: missing script name\n&quot;;
4339 exit 1
4340 }
4341 print STDERR &quot;Running $script\n\n&quot;;
4342
4343 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4344 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4345 } else {
4346 print STDERR &quot;fail: firmware script returned error\n&quot;;
4347 }
4348 }
4349
4350 sub run_firmware_scripts {
4351 my ($opts, @dirs) = @_;
4352 # Run firmware packages
4353 for my $dir (@dirs) {
4354 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4355 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4356 while (my $s = readdir $dh) {
4357 next if $s =~ m/^\.\.?/;
4358 run_firmware_script($opts, &quot;$dir/$s&quot;);
4359 }
4360 closedir $dh;
4361 }
4362 }
4363
4364 sub download {
4365 my $url = shift;
4366 print STDERR &quot;info: Downloading $url\n&quot;;
4367 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4368 }
4369
4370 sub upgrade_dell {
4371 my @dirs;
4372 my $product = `dmidecode -s system-product-name`;
4373 chomp $product;
4374
4375 if ($product =~ m/PowerEdge/) {
4376
4377 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4378 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4379
4380 my $tmpdir = tempdir(
4381 CLEANUP =&gt; 1
4382 );
4383 chdir($tmpdir);
4384 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4385 system(&#39;gunzip Catalog.xml.gz&#39;);
4386 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4387 # -q is quiet, disabling interactivity and reducing console output
4388 my $fwopts = &quot;-q&quot;;
4389 if (@paths) {
4390 for my $url (@paths) {
4391 fetch_dell_fw($url);
4392 }
4393 run_firmware_scripts($fwopts, $tmpdir);
4394 } else {
4395 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4396 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4397 }
4398 chdir(&#39;/&#39;);
4399 } else {
4400 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4401 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4402 }
4403 }
4404
4405 sub fetch_dell_fw {
4406 my $path = shift;
4407 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4408 download($url);
4409 }
4410
4411 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4412 # firmware packages to download from Dell. Only work for Linux
4413 # machines and 11th generation Dell servers.
4414 sub fetch_dell_fw_list {
4415 my $filename = shift;
4416
4417 my $product = `dmidecode -s system-product-name`;
4418 chomp $product;
4419 my ($mybrand, $mymodel) = split(/\s+/, $product);
4420
4421 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4422
4423 my $xml = XMLin($filename);
4424 my @paths;
4425 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4426 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4427 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4428 my $oscode;
4429 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4430 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4431 } else {
4432 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4433 }
4434 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4435 {
4436 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4437 }
4438 }
4439 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4440 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4441
4442 # Drop application packages, only firmware and BIOS
4443 next if &#39;APAC&#39; eq $componenttype;
4444
4445 my $cpath = $component-&gt;{path};
4446 for my $path (@paths) {
4447 if ($cpath =~ m%/$path$%) {
4448 push(@paths, $cpath);
4449 }
4450 }
4451 }
4452 return @paths;
4453 }
4454 &lt;/pre&gt;
4455
4456 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4457 it could work on other platforms with some tweaking. Anyone know a
4458 index like Catalog.xml is available from HP for HP servers? At the
4459 moment I maintain a similar list manually and it is quickly getting
4460 outdated.&lt;/p&gt;
4461 </description>
4462 </item>
4463
4464 <item>
4465 <title>How is booting into runlevel 1 different from single user boots?</title>
4466 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4467 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4468 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4469 <description>&lt;p&gt;Wouter Verhelst have some
4470 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4471 comments and opinions&lt;/a&gt; on my blog post on
4472 &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
4473 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4474 &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
4475 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4476 small piece of his comment now, and though it best to address the
4477 misunderstanding he bring forward:&lt;/p&gt;
4478
4479 &lt;p&gt;&lt;blockquote&gt;
4480 Currently, a system admin has four options: [...] boot to a
4481 single-user system (by adding &#39;single&#39; to the kernel command line;
4482 this runs rcS and rc1 scripts)
4483 &lt;/blockquote&gt;&lt;/p&gt;
4484
4485 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4486 and booting into runlevel 1 is the same. I am not surprised he
4487 believe this, because it would make sense and is a quite sensible
4488 thing to believe. But because the boot in Debian is slightly broken,
4489 runlevel 1 do not work properly and it isn&#39;t the same as single user
4490 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4491 hard to explain.&lt;/p&gt;
4492
4493 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4494 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4495 executed in single user mode is sulogin. Single user mode is a boot
4496 state &quot;between&quot; the runlevels, and when booting into single user mode,
4497 only the scripts in /etc/rcS.d/ are executed before the init process
4498 enters the single user state. When switching to runlevel 1, the state
4499 is in fact not ending in runlevel 1, but it passes through runlevel 1
4500 and end up in the single user mode (see /etc/rc1.d/S03single, which
4501 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4502 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4503 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4504 mode).&lt;/p&gt;
4505
4506 &lt;p&gt;This summary might make it clearer. When booting for the first
4507 time into single user mode, the following commands are executed:
4508 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4509 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4510 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4511 trying to continue after visiting single user mode. Not all services
4512 are started again as they should, causing the machine to end up in an
4513 unpredicatble state. This is why Debian admins recommend rebooting
4514 after visiting single user mode.&lt;/p&gt;
4515
4516 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4517 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4518 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4519 stopped when passing through the scripts in /etc/rc1.d/, and not
4520 started again when switching away from runlevel 1 to the runlevels
4521 2-5. I believe the problem is best fixed by moving all the scripts
4522 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4523 functioning single user mode during boot.&lt;/p&gt;
4524
4525 &lt;p&gt;I have spent several years investigating the Debian boot system,
4526 and discovered this problem a few years ago. I suspect it originates
4527 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4528 </description>
4529 </item>
4530
4531 <item>
4532 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4533 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4534 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4535 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4536 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4537 are started from /etc/rcS.d/. In fact, there is a bite more of them
4538 than make sense, and this causes a few problems. What kind of
4539 problems, you might ask. There are at least two problems. The first
4540 is that it is not possible to recover a machine after switching to
4541 runlevel 1. One need to actually reboot to get the machine back to
4542 the expected state. The other is that single user boot will sometimes
4543 run into problems because some of the subsystems are activated before
4544 the root login is presented, causing problems when trying to recover a
4545 machine from a problem in that subsystem. A minor additional point is
4546 that moving more scripts out of rcS.d/ and into the other rc#.d/
4547 directories will increase the amount of scripts that can run in
4548 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4549
4550 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4551 scripts that _have_ to execute before the root login prompt is
4552 presented during a single user boot should go there. Everything else
4553 should go into the numeric runlevels. This means things like
4554 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4555 the numeric runlevels. Today in Debian, there are around 115 init.d
4556 scripts that are started from rcS.d/, and most of them should be moved
4557 out. Do your package have one of them? Please help us make single
4558 user and runlevel 1 better by moving it.&lt;/p&gt;
4559
4560 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4561 etc. should still be started from rcS.d/, but there is for example no
4562 need to have the network enabled before the single user login prompt
4563 is presented.&lt;/p&gt;
4564
4565 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4566 Debian systems working while scripts migrate and during upgrades, the
4567 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4568 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4569 and the next ones can only be moved when their dependencies have been
4570 moved first. This migration must be done sequentially while we ensure
4571 that the package system upgrade packages in the right order to keep
4572 the system state correct. This will require some coordination when it
4573 comes to network related packages, but most of the packages with
4574 scripts that should migrate do not have anything in rcS.d/ depending
4575 on them. Some packages have already been updated, like the sudo
4576 package, while others are still left to do. I wish I had time to work
4577 on this myself, but real live constrains make it unlikely that I will
4578 find time to push this forward.&lt;/p&gt;
4579 </description>
4580 </item>
4581
4582 <item>
4583 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4584 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4585 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4586 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4587 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4588 mentioned the issues I believe should be improved in Debian for its
4589 desktop to be useful for more people. The use case for this is my
4590 parents, which are currently running Kubuntu which solve the
4591 issues.&lt;/p&gt;
4592
4593 &lt;p&gt;I suspect these four missing features are not very hard to
4594 implement. After all, they are present in Ubuntu, so if we wanted to
4595 do this in Debian we would have a source.&lt;/p&gt;
4596
4597 &lt;ol&gt;
4598
4599 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4600 are new packages available for upgrades, a icon in the KDE status bar
4601 indicate this, and clicking on it will activate the simple upgrade
4602 tool to handle it. I have no problem guiding both of my parents
4603 through the process over the phone. If a kernel reboot is required,
4604 this too is indicated by the status bars and the upgrade tool. Last
4605 time I checked, nothing with the same features was working in KDE in
4606 Debian.&lt;/li&gt;
4607
4608 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4609 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4610 currently have a handler for, it will ask the user if the system
4611 should search for a package that would add support for this MIME type,
4612 and if the user say yes, the APT sources will be searched for packages
4613 advertising the MIME type in their control file (visible in the
4614 Packages file in the APT archive). If one or more packages are found,
4615 it is a simple click of the mouse to add support for the missing mime
4616 type. If the package require the user to accept some non-free
4617 license, this is explained to the user. The entire process make it
4618 more clear to the user why something do not work in the browser, and
4619 make the chances higher for the user to blame the web page authors and
4620 not the browser for any missing features.&lt;/li&gt;
4621
4622 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4623 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4624 it is not supporting, a dialog pop up asking the user if the system
4625 should search for a package that would add support for it. This
4626 happen with things like MP3, Windows Media or H.264. The selection
4627 and installation procedure is very similar to the Firefox browser
4628 plugin handling. This is as far as I know implemented using a
4629 gstreamer hook. The end result is that the user easily get access to
4630 the codecs that are present from the APT archives available, while
4631 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4632
4633 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4634 displaying a text/plain file in my Debian browser, it will propose to
4635 start emacs to show it. If I remember correctly, when doing the same
4636 in Kunbutu it show the file as a text file in the browser. At least I
4637 know Opera will show text files within the browser. I much prefer the
4638 latter behaviour.&lt;/li&gt;
4639
4640 &lt;/ol&gt;
4641
4642 &lt;p&gt;There are other nice features as well, like the simplified suite
4643 upgrader, but given that I am the one mostly doing the dist-upgrade,
4644 it do not matter much.&lt;/p&gt;
4645
4646 &lt;p&gt;I really hope we could get these features in place for the next
4647 Debian release. It would require the coordinated effort of several
4648 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4649 </description>
4650 </item>
4651
4652 <item>
4653 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4654 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4655 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4656 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4657 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4658 site is build on Debian/Squeeze, and this platform was chosen because
4659 I am most familiar with Debian (being a Debian Developer for around 10
4660 years) because it is the latest stable Debian release which should get
4661 security support for a few years.&lt;/p&gt;
4662
4663 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4664 that are missing in Debian at the moment. It would be great if these
4665 modules were added to the Debian archive, allowing anyone to set up
4666 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4667 in their own country using only Debian packages. The list of modules
4668 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4669 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4670 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4671 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4672 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4673 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4674 easier in the future.&lt;/p&gt;
4675
4676 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4677 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4678 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4679 with the responsibility of tracking security problems, which I really
4680 do not have time for.&lt;/p&gt;
4681 </description>
4682 </item>
4683
4684 <item>
4685 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4686 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4687 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4688 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4689 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4690 posts have been in Norwegian the last few weeks, so here is a short
4691 update in English.&lt;/p&gt;
4692
4693 &lt;p&gt;The kids still keep me too busy to get much free software work
4694 done, but I did manage to organise a project to get a Norwegian port
4695 of the British service
4696 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4697 and it has been running for a month now. The entire project has been
4698 organised by me and two others. Around Christmas we gathered sponsors
4699 to fund the development work. In January I drafted a contract with
4700 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4701 and in February the development took place. Most of it involved
4702 converting the source to use GPS coordinates instead of British
4703 easting/northing, and the resulting code should be a lot easier to get
4704 running in any country by now. The Norwegian
4705 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4706 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4707 source and the source for administrative borders in Norway, and
4708 support for this had to be added/fixed.&lt;/p&gt;
4709
4710 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4711 polishing the system before we announced it March 7th. The system is
4712 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4713 problem reports in a few weeks. Soon we hope to announce the Android
4714 and iPhone versions making it even easier to report problems with the
4715 public infrastructure.&lt;/p&gt;
4716
4717 &lt;p&gt;Perhaps something to consider for those of you in countries without
4718 such service?&lt;/p&gt;
4719 </description>
4720 </item>
4721
4722 <item>
4723 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4724 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4725 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4726 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4727 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4728 issues here at my work with the University of Oslo. My idea is that
4729 it should be possible to use the information about security issues
4730 available on the Internet, and check our locally
4731 maintained/distributed software against this information. It should
4732 allow us to verify that no known security issues are forgotten. The
4733 CVE database listing vulnerabilities seem like a great central point,
4734 and by using the package lists from Debian mapped to CVEs provided by
4735 the testing security team, I believed it should be possible to figure
4736 out which security holes were present in our free software
4737 collection.&lt;/p&gt;
4738
4739 &lt;p&gt;After reading up on the topic, it became obvious that the first
4740 building block is to be able to name software packages in a unique and
4741 consistent way across data sources. I considered several ways to do
4742 this, for example coming up with my own naming scheme like using URLs
4743 to project home pages or URLs to the Freshmeat entries, or using some
4744 existing naming scheme. And it seem like I am not the first one to
4745 come across this problem, as MITRE already proposed and implemented a
4746 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4747 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4748 software, hardware and other platform components. The CPE ids are
4749 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4750 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4751 issues for any CPE name. With this in place, all I need to do is to
4752 locate the CPE id for the software packages we use at the university.
4753 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4754 NVD entry if a CVE for the package exist).&lt;/p&gt;
4755
4756 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4757 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4758 check out, one could look up
4759 &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
4760 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4761 The most recent one is
4762 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4763 and at the bottom of the NVD page for this vulnerability the complete
4764 list of affected versions is provided.&lt;/p&gt;
4765
4766 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4767 for offline processing of issues. Using this dump, I&#39;ve written a
4768 small script taking a list of CPEs as input and list all CVEs
4769 affecting the packages represented by these CPEs. One give it CPEs
4770 with version numbers as specified above and get a list of open
4771 security issues out.&lt;/p&gt;
4772
4773 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4774 information need to be high. For that to happen, I believe as many as
4775 possible need to use and contribute to the NVD database. I notice
4776 RHEL is providing
4777 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4778 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4779 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4780
4781 &lt;p&gt;To get an idea about the quality for free software, I spent some
4782 time making it possible to compare the CVE database from Debian with
4783 the CVE database in NVD. The result look fairly good, but there are
4784 some inconsistencies in NVD (same software package having several
4785 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4786 Debian believe are affected by a CVE). Hope to find time to improve
4787 the quality of NVD, but that require being able to get in touch with
4788 someone maintaining it. So far my three emails with questions and
4789 corrections have not seen any reply, but I hope contact can be
4790 established soon.&lt;/p&gt;
4791
4792 &lt;p&gt;An interesting application for CPEs is cross platform package
4793 mapping. It would be useful to know which packages in for example
4794 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4795 this would be trivial if all linux distributions provided CPE entries
4796 for their packages.&lt;/p&gt;
4797 </description>
4798 </item>
4799
4800 <item>
4801 <title>Which module is loaded for a given PCI and USB device?</title>
4802 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4803 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4804 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4805 <description>&lt;p&gt;In the
4806 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4807 package in Debian, there is a script to report useful information
4808 about the running hardware for use when people report missing
4809 information. One part of this script that I find very useful when
4810 debugging hardware problems, is the part mapping loaded kernel module
4811 to the PCI device it claims. It allow me to quickly see if the kernel
4812 module I expect is driving the hardware I am struggling with. To see
4813 the output, make sure discover-data is installed and run
4814 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4815 one of my machines like this:&lt;/p&gt;
4816
4817 &lt;pre&gt;
4818 loaded modules:
4819 10de:03eb i2c_nforce2
4820 10de:03f1 ohci_hcd
4821 10de:03f2 ehci_hcd
4822 10de:03f0 snd_hda_intel
4823 10de:03ec pata_amd
4824 10de:03f6 sata_nv
4825 1022:1103 k8temp
4826 109e:036e bttv
4827 109e:0878 snd_bt87x
4828 11ab:4364 sky2
4829 &lt;/pre&gt;
4830
4831 &lt;p&gt;The code in question look like this, slightly modified for
4832 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4833
4834 &lt;pre&gt;
4835 if [ -d /sys/bus/pci/devices/ ] ; then
4836 echo loaded pci modules:
4837 (
4838 cd /sys/bus/pci/devices/
4839 for address in * ; do
4840 if [ -d &quot;$address/driver/module&quot; ] ; then
4841 module=`cd $address/driver/module ; pwd -P | xargs basename`
4842 if grep -q &quot;^$module &quot; /proc/modules ; then
4843 address=$(echo $address |sed s/0000://)
4844 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4845 echo &quot;$id $module&quot;
4846 fi
4847 fi
4848 done
4849 )
4850 echo
4851 fi
4852 &lt;/pre&gt;
4853
4854 &lt;p&gt;Similar code could be used to extract USB device module
4855 mappings:&lt;/p&gt;
4856
4857 &lt;pre&gt;
4858 if [ -d /sys/bus/usb/devices/ ] ; then
4859 echo loaded usb modules:
4860 (
4861 cd /sys/bus/usb/devices/
4862 for address in * ; do
4863 if [ -d &quot;$address/driver/module&quot; ] ; then
4864 module=`cd $address/driver/module ; pwd -P | xargs basename`
4865 if grep -q &quot;^$module &quot; /proc/modules ; then
4866 address=$(echo $address |sed s/0000://)
4867 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4868 if [ &quot;$id&quot; ] ; then
4869 echo &quot;$id $module&quot;
4870 fi
4871 fi
4872 fi
4873 done
4874 )
4875 echo
4876 fi
4877 &lt;/pre&gt;
4878
4879 &lt;p&gt;This might perhaps be something to include in other tools as
4880 well.&lt;/p&gt;
4881 </description>
4882 </item>
4883
4884 <item>
4885 <title>How to test if a laptop is working with Linux</title>
4886 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4887 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4888 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4889 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4890 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4891 batch of computers will work with Linux. Every year for the last few
4892 years the university have organised shared bid of a few thousand
4893 computers, and this year HP won the bid. Two different desktops and
4894 five different laptops are on the list this year. We in the UNIX
4895 group want to know which one of these computers work well with RHEL
4896 and Ubuntu, the two Linux distributions we currently handle at the
4897 university.&lt;/p&gt;
4898
4899 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4900 perhaps inspire others to test hardware as well. To test, I PXE
4901 install the OS version of choice, and log in as my normal user and run
4902 a few applications and plug in selected pieces of hardware. When
4903 something fail, I make a note about this in the test matrix and move
4904 on. If I have some spare time I try to report the bug to the OS
4905 vendor, but as I only have the machines for a short time, I rarely
4906 have the time to do this for all the problems I find.&lt;/p&gt;
4907
4908 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4909 I perform on a new model.&lt;/p&gt;
4910
4911 &lt;ul&gt;
4912
4913 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4914 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4915 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4916
4917 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4918 installation, X.org is working.&lt;/li&gt;
4919
4920 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4921 package mesa-utils on Ubuntu) and writing down the frames per second
4922 reported by the program.&lt;/li&gt;
4923
4924 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4925 logging in, and if I can hear this the test is successful. If there
4926 are several audio exits on the machine, I try them all and check if
4927 the Gnome/KDE audio mixer can control where to send the sound. I
4928 normally test this by playing
4929 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4930 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4931
4932 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4933 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4934
4935 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4936 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4937
4938 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4939 picture from the v4l device show up.&lt;/li&gt;
4940
4941 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4942 any bluetooth devices are discovered. In my office, I normally see a
4943 few.&lt;/li&gt;
4944
4945 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4946 memory modules lying around, and stick them in and see if Gnome/KDE
4947 notice this.&lt;/li&gt;
4948
4949 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4950 special button work, and if the laptop continue to work after
4951 resume.&lt;/li&gt;
4952
4953 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4954 adjusting background light, switching on/off external video output,
4955 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4956 laptop to laptop, so I just write down which are working and which are
4957 not.&lt;/li&gt;
4958
4959 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4960 acceleration sensors etc. I rarely test these, as I do not know how
4961 to quickly test if they are working or not, so I only document their
4962 existence.&lt;/li&gt;
4963
4964 &lt;/ul&gt;
4965
4966 &lt;p&gt;By now I suspect you are really curious what the test results are
4967 for the HP machines I am testing. I&#39;m not done yet, so I will report
4968 the test results later. For now I can report that HP 8100 Elite work
4969 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4970 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4971 can see, I have most machines left to test. One interesting
4972 observation is that Ubuntu Lucid has almost twice the frame rate than
4973 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4974 </description>
4975 </item>
4976
4977 <item>
4978 <title>Some thoughts on BitCoins</title>
4979 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4980 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4981 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4982 <description>&lt;p&gt;As I continue to explore
4983 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4984 what properties the system have, and how it will be affected by laws
4985 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4986
4987 &lt;p&gt;One interesting thing to note is that since the transactions are
4988 verified using a peer to peer network, all details about a transaction
4989 is known to everyone. This means that if a BitCoin address has been
4990 published like I did with mine in my initial post about BitCoin, it is
4991 possible for everyone to see how many BitCoins have been transfered to
4992 that address. There is even a web service to look at the details for
4993 all transactions. There I can see that my address
4994 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4995 have received 16.06 Bitcoin, the
4996 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4997 address of Simon Phipps have received 181.97 BitCoin and the address
4998 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4999 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5000 every one of you that donated bitcoins to support my activity. The
5001 fact that anyone can see how much money was transfered to a given
5002 address make it more obvious why the BitCoin community recommend to
5003 generate and hand out a new address for each transaction. I&#39;m told
5004 there is no way to track which addresses belong to a given person or
5005 organisation without the person or organisation revealing it
5006 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5007
5008 &lt;p&gt;In Norway, and in most other countries, there are laws and
5009 regulations limiting how much money one can transfer across the border
5010 without declaring it. There are money laundering, tax and accounting
5011 laws and regulations I would expect to apply to the use of BitCoin.
5012 If the Skolelinux foundation
5013 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5014 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5015 normal bank transfers like EFF is doing, how should this be accounted?
5016 Given that it is impossible to know if money can cross the border or
5017 not, should everything or nothing be declared? What exchange rate
5018 should be used when calculating taxes? Would receivers have to pay
5019 income tax if the foundation were to pay Skolelinux contributors in
5020 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5021
5022 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5023 accepted by a lot of users. It must be possible to get easy access to
5024 the currency (as a wage or using currency exchanges), and it must be
5025 easy to spend it. At the moment BitCoin seem fairly easy to get
5026 access to, but there are very few places to spend it. I am not really
5027 a regular user of any of the vendor types currently accepting BitCoin,
5028 so I wonder when my kind of shop would start accepting BitCoins. I
5029 would like to buy electronics, travels and subway tickets, not herbs
5030 and books. :) The currency is young, and this will improve over time
5031 if it become popular, but I suspect regular banks will start to lobby
5032 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5033 will claim it is helping fund terrorism and money laundering (which
5034 probably would be true, as is any currency in existence), but I
5035 believe the problems should be solved elsewhere and not by blaming
5036 currencies.&lt;/p&gt;
5037
5038 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5039 CPU intensive process that depend on a bit of luck as well (as one is
5040 competing against all the other miners currently spending CPU cycles
5041 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5042 BitCoin when this happen. Yesterday I came across the obvious way to
5043 join forces to increase ones changes of getting at least some coins,
5044 by coordinating the work on mining BitCoins across several machines
5045 and people, and sharing the result if one is lucky and get the 50
5046 BitCoins. Check out
5047 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5048 if this sounds interesting. I have not had time to try to set up a
5049 machine to participate there yet, but have seen that running on ones
5050 own for a few days have not yield any BitCoins througth mining
5051 yet.&lt;/p&gt;
5052
5053 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5054 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5055 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5056 it was interesting to read. The arguments presented seem to be
5057 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5058 </description>
5059 </item>
5060
5061 <item>
5062 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5063 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5064 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5065 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5066 <description>&lt;p&gt;With this weeks lawless
5067 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5068 attacks&lt;/a&gt; on Wikileak and
5069 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5070 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5071 not be trusted to handle money transactions.
5072 A blog post from
5073 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5074 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5075 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5076 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5077 some help from my friend to get it all running, and he even handed me
5078 some bitcoins to get started. I even donated a few bitcoins to Simon
5079 for helping me remember BitCoin.&lt;/p&gt;
5080
5081 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5082 crypto-currency, decentralised and handled using peer-to-peer
5083 networks. It allows anonymous transactions and prohibits central
5084 control over the transactions, making it impossible for governments
5085 and companies alike to block donations and other transactions. The
5086 source is free software, and while the key dependency wxWidgets 2.9
5087 for the graphical user interface is missing in Debian, the command
5088 line client builds just fine. Hopefully Jonas
5089 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5090 Debian&lt;/a&gt; soon.&lt;/p&gt;
5091
5092 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5093 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5094 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5095 currency &quot;stock&quot; markets where the exchange rate is decided. There
5096 are not many users so far, but the concept seems promising. If you
5097 want to get started and lack a friend with any bitcoins to spare,
5098 you can even get
5099 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5100 bitcoin at the time of writing). Use
5101 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5102 on the current exchange rates.&lt;/p&gt;
5103
5104 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5105 machines. If you want to support my activity, please send Bitcoin
5106 donations to the address
5107 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5108 </description>
5109 </item>
5110
5111 <item>
5112 <title>Why isn&#39;t Debian Edu using VLC?</title>
5113 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5114 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5115 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5116 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5117 presented, and the winner among the multimedia player were VLC.
5118 Personally, I like VLC, and it is my player of choice when I first try
5119 to play a video file or stream. Only if VLC fail will I drag out
5120 gmplayer to see if it can do better. The reason is mostly the failure
5121 model and trust. When VLC fail, it normally pop up a error message
5122 reporting the problem. When mplayer fail, it normally segfault or
5123 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5124
5125 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5126 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5127 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5128 plugin to play web videos seamlessly, and the VLC browser plugin is
5129 not very good. For example, it lack in-line control buttons, so there
5130 is no way for the user to pause the video. Also, when I
5131 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5132 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5133 failed on several video pages where mplayer based plugins worked. If
5134 the browser plugin for VLC was as good as the gecko-mediaplayer
5135 package (which uses mplayer), we would switch.&lt;/P&gt;
5136
5137 &lt;p&gt;While VLC is a good player, its user interface is slightly
5138 annoying. The most annoying feature is its inconsistent use of
5139 keyboard shortcuts. When the player is in full screen mode, its
5140 shortcuts are different from when it is playing the video in a window.
5141 For example, space only work as pause when in full screen mode. I
5142 wish it had consisten shortcuts and that space also would work when in
5143 window mode. Another nice shortcut in gmplayer is [enter] to restart
5144 the current video. It is very nice when playing short videos from the
5145 web and want to restart it when new people arrive to have a look at
5146 what is going on.&lt;/p&gt;
5147 </description>
5148 </item>
5149
5150 <item>
5151 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5152 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5153 <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>
5154 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5155 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5156 upgrade testing of the
5157 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5158 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5159 This seem like a very good idea, so I adjusted by test scripts and
5160 can now present the updated result from today:&lt;/p&gt;
5161
5162 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5163
5164 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5165
5166 &lt;blockquote&gt;&lt;p&gt;
5167 apache2.2-bin
5168 aptdaemon
5169 baobab
5170 binfmt-support
5171 browser-plugin-gnash
5172 cheese-common
5173 cli-common
5174 cups-pk-helper
5175 dmz-cursor-theme
5176 empathy
5177 empathy-common
5178 freedesktop-sound-theme
5179 freeglut3
5180 gconf-defaults-service
5181 gdm-themes
5182 gedit-plugins
5183 geoclue
5184 geoclue-hostip
5185 geoclue-localnet
5186 geoclue-manual
5187 geoclue-yahoo
5188 gnash
5189 gnash-common
5190 gnome
5191 gnome-backgrounds
5192 gnome-cards-data
5193 gnome-codec-install
5194 gnome-core
5195 gnome-desktop-environment
5196 gnome-disk-utility
5197 gnome-screenshot
5198 gnome-search-tool
5199 gnome-session-canberra
5200 gnome-system-log
5201 gnome-themes-extras
5202 gnome-themes-more
5203 gnome-user-share
5204 gstreamer0.10-fluendo-mp3
5205 gstreamer0.10-tools
5206 gtk2-engines
5207 gtk2-engines-pixbuf
5208 gtk2-engines-smooth
5209 hamster-applet
5210 libapache2-mod-dnssd
5211 libapr1
5212 libaprutil1
5213 libaprutil1-dbd-sqlite3
5214 libaprutil1-ldap
5215 libart2.0-cil
5216 libboost-date-time1.42.0
5217 libboost-python1.42.0
5218 libboost-thread1.42.0
5219 libchamplain-0.4-0
5220 libchamplain-gtk-0.4-0
5221 libcheese-gtk18
5222 libclutter-gtk-0.10-0
5223 libcryptui0
5224 libdiscid0
5225 libelf1
5226 libepc-1.0-2
5227 libepc-common
5228 libepc-ui-1.0-2
5229 libfreerdp-plugins-standard
5230 libfreerdp0
5231 libgconf2.0-cil
5232 libgdata-common
5233 libgdata7
5234 libgdu-gtk0
5235 libgee2
5236 libgeoclue0
5237 libgexiv2-0
5238 libgif4
5239 libglade2.0-cil
5240 libglib2.0-cil
5241 libgmime2.4-cil
5242 libgnome-vfs2.0-cil
5243 libgnome2.24-cil
5244 libgnomepanel2.24-cil
5245 libgpod-common
5246 libgpod4
5247 libgtk2.0-cil
5248 libgtkglext1
5249 libgtksourceview2.0-common
5250 libmono-addins-gui0.2-cil
5251 libmono-addins0.2-cil
5252 libmono-cairo2.0-cil
5253 libmono-corlib2.0-cil
5254 libmono-i18n-west2.0-cil
5255 libmono-posix2.0-cil
5256 libmono-security2.0-cil
5257 libmono-sharpzip2.84-cil
5258 libmono-system2.0-cil
5259 libmtp8
5260 libmusicbrainz3-6
5261 libndesk-dbus-glib1.0-cil
5262 libndesk-dbus1.0-cil
5263 libopal3.6.8
5264 libpolkit-gtk-1-0
5265 libpt2.6.7
5266 libpython2.6
5267 librpm1
5268 librpmio1
5269 libsdl1.2debian
5270 libsrtp0
5271 libssh-4
5272 libtelepathy-farsight0
5273 libtelepathy-glib0
5274 libtidy-0.99-0
5275 media-player-info
5276 mesa-utils
5277 mono-2.0-gac
5278 mono-gac
5279 mono-runtime
5280 nautilus-sendto
5281 nautilus-sendto-empathy
5282 p7zip-full
5283 pkg-config
5284 python-aptdaemon
5285 python-aptdaemon-gtk
5286 python-axiom
5287 python-beautifulsoup
5288 python-bugbuddy
5289 python-clientform
5290 python-coherence
5291 python-configobj
5292 python-crypto
5293 python-cupshelpers
5294 python-elementtree
5295 python-epsilon
5296 python-evolution
5297 python-feedparser
5298 python-gdata
5299 python-gdbm
5300 python-gst0.10
5301 python-gtkglext1
5302 python-gtksourceview2
5303 python-httplib2
5304 python-louie
5305 python-mako
5306 python-markupsafe
5307 python-mechanize
5308 python-nevow
5309 python-notify
5310 python-opengl
5311 python-openssl
5312 python-pam
5313 python-pkg-resources
5314 python-pyasn1
5315 python-pysqlite2
5316 python-rdflib
5317 python-serial
5318 python-tagpy
5319 python-twisted-bin
5320 python-twisted-conch
5321 python-twisted-core
5322 python-twisted-web
5323 python-utidylib
5324 python-webkit
5325 python-xdg
5326 python-zope.interface
5327 remmina
5328 remmina-plugin-data
5329 remmina-plugin-rdp
5330 remmina-plugin-vnc
5331 rhythmbox-plugin-cdrecorder
5332 rhythmbox-plugins
5333 rpm-common
5334 rpm2cpio
5335 seahorse-plugins
5336 shotwell
5337 software-center
5338 system-config-printer-udev
5339 telepathy-gabble
5340 telepathy-mission-control-5
5341 telepathy-salut
5342 tomboy
5343 totem
5344 totem-coherence
5345 totem-mozilla
5346 totem-plugins
5347 transmission-common
5348 xdg-user-dirs
5349 xdg-user-dirs-gtk
5350 xserver-xephyr
5351 &lt;/p&gt;&lt;/blockquote&gt;
5352
5353 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5354
5355 &lt;blockquote&gt;&lt;p&gt;
5356 cheese
5357 ekiga
5358 eog
5359 epiphany-extensions
5360 evolution-exchange
5361 fast-user-switch-applet
5362 file-roller
5363 gcalctool
5364 gconf-editor
5365 gdm
5366 gedit
5367 gedit-common
5368 gnome-games
5369 gnome-games-data
5370 gnome-nettool
5371 gnome-system-tools
5372 gnome-themes
5373 gnuchess
5374 gucharmap
5375 guile-1.8-libs
5376 libavahi-ui0
5377 libdmx1
5378 libgalago3
5379 libgtk-vnc-1.0-0
5380 libgtksourceview2.0-0
5381 liblircclient0
5382 libsdl1.2debian-alsa
5383 libspeexdsp1
5384 libsvga1
5385 rhythmbox
5386 seahorse
5387 sound-juicer
5388 system-config-printer
5389 totem-common
5390 transmission-gtk
5391 vinagre
5392 vino
5393 &lt;/p&gt;&lt;/blockquote&gt;
5394
5395 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5396
5397 &lt;blockquote&gt;&lt;p&gt;
5398 gstreamer0.10-gnomevfs
5399 &lt;/p&gt;&lt;/blockquote&gt;
5400
5401 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5402
5403 &lt;blockquote&gt;&lt;p&gt;
5404 [nothing]
5405 &lt;/p&gt;&lt;/blockquote&gt;
5406
5407 &lt;p&gt;This is for KDE:&lt;/p&gt;
5408
5409 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5410
5411 &lt;blockquote&gt;&lt;p&gt;
5412 ksmserver
5413 &lt;/p&gt;&lt;/blockquote&gt;
5414
5415 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5416
5417 &lt;blockquote&gt;&lt;p&gt;
5418 kwin
5419 network-manager-kde
5420 &lt;/p&gt;&lt;/blockquote&gt;
5421
5422 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5423
5424 &lt;blockquote&gt;&lt;p&gt;
5425 arts
5426 dolphin
5427 freespacenotifier
5428 google-gadgets-gst
5429 google-gadgets-xul
5430 kappfinder
5431 kcalc
5432 kcharselect
5433 kde-core
5434 kde-plasma-desktop
5435 kde-standard
5436 kde-window-manager
5437 kdeartwork
5438 kdeartwork-emoticons
5439 kdeartwork-style
5440 kdeartwork-theme-icon
5441 kdebase
5442 kdebase-apps
5443 kdebase-workspace
5444 kdebase-workspace-bin
5445 kdebase-workspace-data
5446 kdeeject
5447 kdelibs
5448 kdeplasma-addons
5449 kdeutils
5450 kdewallpapers
5451 kdf
5452 kfloppy
5453 kgpg
5454 khelpcenter4
5455 kinfocenter
5456 konq-plugins-l10n
5457 konqueror-nsplugins
5458 kscreensaver
5459 kscreensaver-xsavers
5460 ktimer
5461 kwrite
5462 libgle3
5463 libkde4-ruby1.8
5464 libkonq5
5465 libkonq5-templates
5466 libnetpbm10
5467 libplasma-ruby
5468 libplasma-ruby1.8
5469 libqt4-ruby1.8
5470 marble-data
5471 marble-plugins
5472 netpbm
5473 nuvola-icon-theme
5474 plasma-dataengines-workspace
5475 plasma-desktop
5476 plasma-desktopthemes-artwork
5477 plasma-runners-addons
5478 plasma-scriptengine-googlegadgets
5479 plasma-scriptengine-python
5480 plasma-scriptengine-qedje
5481 plasma-scriptengine-ruby
5482 plasma-scriptengine-webkit
5483 plasma-scriptengines
5484 plasma-wallpapers-addons
5485 plasma-widget-folderview
5486 plasma-widget-networkmanagement
5487 ruby
5488 sweeper
5489 update-notifier-kde
5490 xscreensaver-data-extra
5491 xscreensaver-gl
5492 xscreensaver-gl-extra
5493 xscreensaver-screensaver-bsod
5494 &lt;/p&gt;&lt;/blockquote&gt;
5495
5496 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5497
5498 &lt;blockquote&gt;&lt;p&gt;
5499 ark
5500 google-gadgets-common
5501 google-gadgets-qt
5502 htdig
5503 kate
5504 kdebase-bin
5505 kdebase-data
5506 kdepasswd
5507 kfind
5508 klipper
5509 konq-plugins
5510 konqueror
5511 ksysguard
5512 ksysguardd
5513 libarchive1
5514 libcln6
5515 libeet1
5516 libeina-svn-06
5517 libggadget-1.0-0b
5518 libggadget-qt-1.0-0b
5519 libgps19
5520 libkdecorations4
5521 libkephal4
5522 libkonq4
5523 libkonqsidebarplugin4a
5524 libkscreensaver5
5525 libksgrd4
5526 libksignalplotter4
5527 libkunitconversion4
5528 libkwineffects1a
5529 libmarblewidget4
5530 libntrack-qt4-1
5531 libntrack0
5532 libplasma-geolocation-interface4
5533 libplasmaclock4a
5534 libplasmagenericshell4
5535 libprocesscore4a
5536 libprocessui4a
5537 libqalculate5
5538 libqedje0a
5539 libqtruby4shared2
5540 libqzion0a
5541 libruby1.8
5542 libscim8c2a
5543 libsmokekdecore4-3
5544 libsmokekdeui4-3
5545 libsmokekfile3
5546 libsmokekhtml3
5547 libsmokekio3
5548 libsmokeknewstuff2-3
5549 libsmokeknewstuff3-3
5550 libsmokekparts3
5551 libsmokektexteditor3
5552 libsmokekutils3
5553 libsmokenepomuk3
5554 libsmokephonon3
5555 libsmokeplasma3
5556 libsmokeqtcore4-3
5557 libsmokeqtdbus4-3
5558 libsmokeqtgui4-3
5559 libsmokeqtnetwork4-3
5560 libsmokeqtopengl4-3
5561 libsmokeqtscript4-3
5562 libsmokeqtsql4-3
5563 libsmokeqtsvg4-3
5564 libsmokeqttest4-3
5565 libsmokeqtuitools4-3
5566 libsmokeqtwebkit4-3
5567 libsmokeqtxml4-3
5568 libsmokesolid3
5569 libsmokesoprano3
5570 libtaskmanager4a
5571 libtidy-0.99-0
5572 libweather-ion4a
5573 libxklavier16
5574 libxxf86misc1
5575 okteta
5576 oxygencursors
5577 plasma-dataengines-addons
5578 plasma-scriptengine-superkaramba
5579 plasma-widget-lancelot
5580 plasma-widgets-addons
5581 plasma-widgets-workspace
5582 polkit-kde-1
5583 ruby1.8
5584 systemsettings
5585 update-notifier-common
5586 &lt;/p&gt;&lt;/blockquote&gt;
5587
5588 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5589 aptitude a bit more similar, but there are still quite a lott of
5590 differences. I have no idea what packages should be installed after
5591 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5592 </description>
5593 </item>
5594
5595 <item>
5596 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5597 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5598 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5599 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5600 <description>&lt;p&gt;Most of the computers in use by the
5601 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5602 are virtual machines. And they have been Xen machines running on a
5603 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5604 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5605 bit harder that it could have been, because we set up the Xen virtual
5606 machines to get the virtual partitions from LVM, which as far as I
5607 know is not supported by KVM. So to migrate, we had to convert
5608 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5609
5610 &lt;p&gt;I found
5611 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5612 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5613 migration. It uses qemu-img from the qemu package to make the disk
5614 image, parted to partition it, losetup and kpartx to present the disk
5615 image partions as devices, and dd to copy the data. I NFS mounted the
5616 new servers storage area on the old server to do the migration.&lt;/p&gt;
5617
5618 &lt;pre&gt;
5619 #!/bin/sh
5620
5621 # Based on
5622 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5623
5624 set -e
5625 set -x
5626
5627 if [ -z &quot;$1&quot; ] ; then
5628 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5629 exit 1
5630 else
5631 host=&quot;$1&quot;
5632 fi
5633
5634 if [ ! -e /dev/vg_data/$host-disk ] ; then
5635 echo &quot;error: unable to find LVM volume for $host&quot;
5636 exit 1
5637 fi
5638
5639 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5640 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5641 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5642 totalsize=$(( ( $disksize + $swapsize ) ))
5643
5644 img=$host.img
5645 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5646 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5647
5648 parted $img mklabel msdos
5649 parted $img mkpart primary linux-swap 0 $disksize
5650 parted $img mkpart primary ext2 $disksize $totalsize
5651 parted $img set 1 boot on
5652
5653 modprobe dm-mod
5654 losetup /dev/loop0 $img
5655 kpartx -a /dev/loop0
5656
5657 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5658 fsck.ext3 -f /dev/mapper/loop0p1 || true
5659 mkswap /dev/mapper/loop0p2
5660
5661 kpartx -d /dev/loop0
5662 losetup -d /dev/loop0
5663 &lt;/pre&gt;
5664
5665 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5666 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5667
5668 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5669 the new disk image attached, installed grub-pc and linux-image-686 and
5670 set up grub to boot from the disk image. After this, the KVM machines
5671 seem to work just fine.&lt;/p&gt;
5672 </description>
5673 </item>
5674
5675 <item>
5676 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5677 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5678 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5679 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5680 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5681 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5682 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5683 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5684
5685 &lt;p&gt;I still do not know what a correct migration should look like, so I
5686 report any differences between apt and aptitude and hope someone else
5687 can see if anything should be changed.&lt;/p&gt;
5688
5689 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5690
5691 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5692
5693 &lt;blockquote&gt;&lt;p&gt;
5694 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5695 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5696 dmz-cursor-theme empathy empathy-common finger
5697 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5698 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5699 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5700 gnome-cards-data gnome-codec-install gnome-core
5701 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5702 gnome-search-tool gnome-session-canberra gnome-spell
5703 gnome-system-log gnome-themes-extras gnome-themes-more
5704 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5705 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5706 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5707 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5708 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5709 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5710 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5711 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5712 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5713 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5714 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5715 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5716 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5717 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5718 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5719 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5720 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5721 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5722 libmono-security2.0-cil libmono-sharpzip2.84-cil
5723 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5724 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5725 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5726 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5727 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5728 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5729 libxalan2-java libxerces2-java media-player-info mesa-utils
5730 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5731 nautilus-sendto-empathy openoffice.org-writer2latex
5732 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5733 python-aptdaemon python-aptdaemon-gtk python-axiom
5734 python-beautifulsoup python-bugbuddy python-clientform
5735 python-coherence python-configobj python-crypto python-cupshelpers
5736 python-cupsutils python-eggtrayicon python-elementtree
5737 python-epsilon python-evolution python-feedparser python-gdata
5738 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5739 python-gtksourceview2 python-httplib2 python-louie python-mako
5740 python-markupsafe python-mechanize python-nevow python-notify
5741 python-opengl python-openssl python-pam python-pkg-resources
5742 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5743 python-tagpy python-twisted-bin python-twisted-conch
5744 python-twisted-core python-twisted-web python-utidylib python-webkit
5745 python-xdg python-zope.interface remmina remmina-plugin-data
5746 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5747 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5748 software-center svgalibg1 system-config-printer-udev
5749 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5750 totem totem-coherence totem-mozilla totem-plugins
5751 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5752 zip
5753 &lt;/p&gt;&lt;/blockquote&gt;
5754
5755 Installed using apt-get, removed with aptitude
5756
5757 &lt;blockquote&gt;&lt;p&gt;
5758 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5759 epiphany-extensions epiphany-gecko evolution-exchange
5760 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5761 gedit-common gnome-app-install gnome-games gnome-games-data
5762 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5763 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5764 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5765 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5766 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5767 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5768 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5769 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5770 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5771 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5772 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5773 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5774 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5775 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5776 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5777 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5778 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5779 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5780 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5781 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5782 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5783 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5784 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5785 sound-juicer swfdec-gnome system-config-printer totem-common
5786 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5787 &lt;/p&gt;&lt;/blockquote&gt;
5788
5789 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5790
5791 &lt;blockquote&gt;&lt;p&gt;
5792 gstreamer0.10-gnomevfs
5793 &lt;/p&gt;&lt;/blockquote&gt;
5794
5795 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5796
5797 &lt;blockquote&gt;&lt;p&gt;
5798 [nothing]
5799 &lt;/p&gt;&lt;/blockquote&gt;
5800
5801 &lt;p&gt;This is for KDE:&lt;/p&gt;
5802
5803 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5804
5805 &lt;blockquote&gt;&lt;p&gt;
5806 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5807 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5808 ghostscript-x git gnome-audio gnugo granatier gs-common
5809 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5810 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5811 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5812 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5813 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5814 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5815 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5816 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5817 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5818 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5819 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5820 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5821 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5822 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5823 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5824 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5825 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5826 libkrossui4 libmailtools-perl libmime-tools-perl
5827 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5828 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5829 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5830 lirc luatex marble networkstatus noatun-plugins
5831 openoffice.org-writer2latex palapeli palapeli-data parley
5832 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5833 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5834 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5835 ttf-sazanami-gothic
5836 &lt;/p&gt;&lt;/blockquote&gt;
5837
5838 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5839
5840 &lt;blockquote&gt;&lt;p&gt;
5841 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5842 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5843 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5844 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5845 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5846 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5847 kitchensync kiten kjumpingcube klatin klettres klickety klines
5848 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5849 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5850 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5851 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5852 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5853 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5854 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5855 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5856 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5857 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5858 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5859 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5860 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5861 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5862 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5863 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5864 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5865 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5866 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5867 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5868 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5869 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5870 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5871 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5872 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5873 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5874 &lt;/p&gt;&lt;/blockquote&gt;
5875
5876 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5877
5878 &lt;blockquote&gt;&lt;p&gt;
5879 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5880 kdeartwork kdebase kdebase-apps kdebase-workspace
5881 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5882 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5883 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5884 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5885 xscreensaver-screensaver-bsod
5886 &lt;/p&gt;&lt;/blockquote&gt;
5887
5888 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5889
5890 &lt;blockquote&gt;&lt;p&gt;
5891 kdebase-bin konq-plugins konqueror
5892 &lt;/p&gt;&lt;/blockquote&gt;
5893 </description>
5894 </item>
5895
5896 <item>
5897 <title>Gnash buildbot slave and Debian kfreebsd</title>
5898 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5900 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5901 <description>&lt;p&gt;Answering
5902 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5903 call from the Gnash project&lt;/a&gt; for
5904 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5905 current source, I have set up a virtual KVM machine on the Debian
5906 Edu/Skolelinux virtualization host to test the git source on
5907 Debian/Squeeze. I hope this can help the developers in getting new
5908 releases out more often.&lt;/p&gt;
5909
5910 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5911 I have considered setting up a &lt;a
5912 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5913 machine as well. I have also considered using the kfreebsd
5914 architecture in Debian as a file server in NUUG to get access to the 5
5915 TB zfs volume we currently use to store DV video. Because of this, I
5916 finally got around to do a test installation of Debian/Squeeze with
5917 kfreebsd. Installation went fairly smooth, thought I noticed some
5918 visual glitches in the cdebconf dialogs (black cursor left on the
5919 screen at random locations). Have not gotten very far with the
5920 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5921 fatal problem. Have to spend some more time on it to see if it is
5922 useful as a file server for NUUG. Will try to find time to set up a
5923 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5924 </description>
5925 </item>
5926
5927 <item>
5928 <title>Debian in 3D</title>
5929 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5930 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5931 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5932 <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;
5933
5934 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5935 3D linked in from
5936 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5937 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5938 </description>
5939 </item>
5940
5941 <item>
5942 <title>Software updates 2010-10-24</title>
5943 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5944 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5945 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5946 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5947
5948 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5949 raise money for the project is going well. The lower limit of 10
5950 signers was reached in 24 hours, and so far 13 people have signed it.
5951 More signers and more funding is most welcome, and I am really curious
5952 how far we can get before the time limit of December 24 is reached.
5953 :)&lt;/p&gt;
5954
5955 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5956 about what appear to be a great code coverage tool capable of
5957 generating code coverage stats without any changes to the source code.
5958 It is called
5959 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5960 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5961 It is missing in Debian, but the git source built just fine in Squeeze
5962 after I installed libelf-dev, libdwarf-dev, pkg-config and
5963 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5964 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5965
5966 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5967 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5968 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5969 alpha test release of the Squeeze based Debian Edu /
5970 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5971 release. Give it a try if you need a complete linux solution for your
5972 school, including central infrastructure server, workstations, thin
5973 client servers and diskless workstations. A nice touch added
5974 yesterday is RDP support on the thin client servers, for windows
5975 clients to get a Linux desktop on request.&lt;/p&gt;
5976 </description>
5977 </item>
5978
5979 <item>
5980 <title>Some notes on Flash in Debian and Debian Edu</title>
5981 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5982 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5983 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5984 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5985 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5986 second most popular used package that is missing in Debian. The sixth
5987 most popular is flashplayer-mozilla. This is a clear indication that
5988 working flash is important for Debian users. Around 10 percent of the
5989 users submitting data to popcon.debian.org have this package
5990 installed.&lt;/p&gt;
5991
5992 &lt;p&gt;In the report written by Lars Risan in August 2008
5993&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
5994 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5995 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5996 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5997 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5998 web sites require Flash to work, and lacking working Flash support in
5999 the web browser and the problems with installing it was perceived as a
6000 good reason to stay with Windows.&lt;/p&gt;
6001
6002 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6003 said to be the retarded cousin that did not really understand
6004 everything you told him but could work fairly well. This was a
6005 comment regarding the problems Linux have with proprietary formats and
6006 non-standard web pages, and is sad because it exposes a fairly common
6007 understanding of whose fault it is if web pages that only work in for
6008 example Internet Explorer 6 fail to work on Firefox, and funny because
6009 it explain very well how annoying it is for users when Linux
6010 distributions do not work with the documents they receive or the web
6011 pages they want to visit.&lt;/p&gt;
6012
6013 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6014 and Debian Edu to have a well working Flash implementation in the
6015 distribution, to get at least popular sites as Youtube and Google
6016 Video to working out of the box. For Squeeze, Debian have the chance
6017 to include the latest version of Gnash that will make this happen, as
6018 the new release 0.8.8 was published a few weeks ago and is resting in
6019 unstable. The new version work with more sites that version 0.8.7.
6020 The Gnash maintainers have asked for a freeze exception, but the
6021 release team have not had time to reply to it yet. I hope they agree
6022 with me that Flash is important for the Debian desktop users, and thus
6023 accept the new package into Squeeze.&lt;/p&gt;
6024 </description>
6025 </item>
6026
6027 <item>
6028 <title>Circular package dependencies harms apt recovery</title>
6029 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6030 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6031 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6032 <description>&lt;p&gt;I discovered this while doing
6033 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6034 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6035 in Debian still got circular dependencies, and it is often claimed
6036 that apt and aptitude should be able to handle this just fine, but
6037 some times these dependency loops causes apt to fail.&lt;/p&gt;
6038
6039 &lt;p&gt;An example is from todays
6040 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6041 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6042 causes perl-modules to fail to upgrade. The cause is simple. If a
6043 package fail to unpack, then only part of packages with the circular
6044 dependency might end up being unpacked when unpacking aborts, and the
6045 ones already unpacked will fail to configure in the recovery phase
6046 because its dependencies are unavailable.&lt;/p&gt;
6047
6048 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6049
6050 &lt;blockquote&gt;&lt;pre&gt;
6051 dpkg: dependency problems prevent configuration of perl-modules:
6052 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6053 Version of perl on system is 5.10.0-19lenny2.
6054 dpkg: error processing perl-modules (--configure):
6055 dependency problems - leaving unconfigured
6056 &lt;/pre&gt;&lt;/blockquote&gt;
6057
6058 &lt;p&gt;The perl/perl-modules circular dependency is already
6059 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6060 hopefully be solved as soon as possible, but it is not the only one,
6061 and each one of these loops in the dependency tree can cause similar
6062 failures. Of course, they only occur when there are bugs in other
6063 packages causing the unpacking to fail, but it is rather nasty when
6064 the failure of one package causes the problem to become worse because
6065 of dependency loops.&lt;/p&gt;
6066
6067 &lt;p&gt;Thanks to
6068 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6069 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6070 dependencies
6071 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6072 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6073
6074 &lt;p&gt;Todays testing also exposed a bug in
6075 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6076 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6077 apt-get and aptitude, the latter possibly caused by some circular
6078 dependency. Reported both to BTS to try to get someone to look at
6079 it.&lt;/p&gt;
6080 </description>
6081 </item>
6082
6083 <item>
6084 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6085 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6086 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6087 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6088 <description>&lt;p&gt;This is a
6089 &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;
6090 on my
6091 &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
6092 work&lt;/a&gt; on
6093 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6094 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6095
6096 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6097 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6098 and dhcp3-server-ldap in Debian use the LDAP server. The two
6099 implementations are quite different in how they use LDAP.&lt;/p&gt;
6100
6101 To get this information, I started slapd with debugging enabled and
6102 dumped the debug output to a file to get the LDAP searches performed
6103 on a Debian Edu main-server. Here is a summary.
6104
6105 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6106
6107 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6108 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6109 the web.
6110
6111 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6112 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6113 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6114 reverse entries are in two different subtrees in LDAP with a structure
6115 based on the DNS names, as in tjener.intern and
6116 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6117
6118 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6119 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6120 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6121 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6122 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6123 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6124 forward entries, it is looking for attributes named dnsttl, arecord,
6125 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6126 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6127 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6128 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6129 spfrecord and modifytimestamp. For reverse entries it is looking for
6130 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6131 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6132 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6133 ldapsearch commands could look like this:&lt;/p&gt;
6134
6135 &lt;blockquote&gt;&lt;pre&gt;
6136 ldapsearch -h ldap \
6137 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6138 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6139 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6140 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6141 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6142 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6143
6144 ldapsearch -h ldap \
6145 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6146 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6147 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6148 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6149 srvrecord naptrrecord modifytimestamp
6150 &lt;/pre&gt;&lt;/blockquote&gt;
6151
6152 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6153 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6154 example LDAP objects used there. In addition to these objects, the
6155 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6156 also exist.&lt;/p&gt;
6157
6158 &lt;blockquote&gt;&lt;pre&gt;
6159 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6160 objectclass: top
6161 objectclass: dnsdomain
6162 objectclass: domainrelatedobject
6163 dc: tjener
6164 arecord: 10.0.2.2
6165 associateddomain: tjener.intern
6166
6167 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6168 objectclass: top
6169 objectclass: dnsdomain2
6170 objectclass: domainrelatedobject
6171 dc: 2
6172 ptrrecord: tjener.intern
6173 associateddomain: 2.2.0.10.in-addr.arpa
6174 &lt;/pre&gt;&lt;/blockquote&gt;
6175
6176 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6177 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6178 same base as in the tree mode for a object with filter
6179 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6180 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6181 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6182 naptrrecord and modifytimestamp. For reverse entires it also do a
6183 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6184 and the requested attributes are associateddomain, dnsttl and
6185 modifytimestamp. In short, in strict mode the objects with ptrrecord
6186 go away, and the arecord attribute in the forward object is used
6187 instead.&lt;/p&gt;
6188
6189 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6190 like this:&lt;/p&gt;
6191
6192 &lt;blockquote&gt;&lt;pre&gt;
6193 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6194 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6195 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6196 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6197 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6198 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6199
6200 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6201 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6202 &lt;/pre&gt;&lt;/blockquote&gt;
6203
6204 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6205 search for SOA records, which behave similar to the forward and
6206 reverse lookups.&lt;/p&gt;
6207
6208 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6209 specify any objectclass names, and instead look for the attributes it
6210 need to generate a DNS reply. This make it able to work with any
6211 objectclass that provide the needed attributes.&lt;/p&gt;
6212
6213 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6214 dnsdomain2 schemas. The latter is used for reverse entries like
6215 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6216
6217 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6218 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6219 attributes) and domainrelatedobject (for associatedDomain). The use
6220 of structural object classes make it impossible to combine these
6221 classes with the object classes used by DHCP.&lt;/p&gt;
6222
6223 &lt;p&gt;There are other schemas that could be used too, for example the
6224 dnszone structural object class used by Gosa and bind-sdb for the DNS
6225 attributes combined with the domainrelatedobject object class, but in
6226 this case some unused attributes would have to be included as well
6227 (zonename and relativedomainname).&lt;/p&gt;
6228
6229 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6230 mode and not use any of the existing objectclasses (dnsdomain,
6231 dnsdomain2 and dnszone) when one want to combine the DNS information
6232 with DHCP information, and instead create a auxiliary object class
6233 defined something like this (using the attributes defined for
6234 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6235
6236 &lt;blockquote&gt;&lt;pre&gt;
6237 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6238 SUP top
6239 AUXILIARY
6240 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6241 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6242 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6243 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6244 A6Record $ DNAMERecord
6245 ))
6246 &lt;/pre&gt;&lt;/blockquote&gt;
6247
6248 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6249 the domainrelatedobject object class, and allow any entity to include
6250 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6251 developers asking for their view on this schema and if they are
6252 interested in providing such schema with PowerDNS, and I hope my
6253 message will be accepted into their mailing list soon.&lt;/p&gt;
6254
6255 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6256
6257 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6258 the object attributes, and then uses the attributes it want. This
6259 make it harder to figure out exactly what attributes are used, but
6260 thanks to the working example in Debian Edu I can at least get an idea
6261 what is needed without having to read the source code.&lt;/p&gt;
6262
6263 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6264 search filter to use to locate the correct dhcpServer entity is
6265 stored. These are the relevant entries from
6266 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6267
6268 &lt;blockquote&gt;&lt;pre&gt;
6269 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6270 ldap-dhcp-server-cn &quot;dhcp&quot;;
6271 &lt;/pre&gt;&lt;/blockquote&gt;
6272
6273 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6274 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6275 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6276 search result is this entry:&lt;/p&gt;
6277
6278 &lt;blockquote&gt;&lt;pre&gt;
6279 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6280 cn: dhcp
6281 objectClass: top
6282 objectClass: dhcpServer
6283 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6284 &lt;/pre&gt;&lt;/blockquote&gt;
6285
6286 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6287 subtree with DHCP configuration. The DHCP configuration subtree base
6288 is located using a base scope search with base &quot;cn=DHCP
6289 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6290 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6291 The search result is this entry:&lt;/p&gt;
6292
6293 &lt;blockquote&gt;&lt;pre&gt;
6294 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6295 cn: DHCP Config
6296 objectClass: top
6297 objectClass: dhcpService
6298 objectClass: dhcpOptions
6299 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6300 dhcpStatements: ddns-update-style none
6301 dhcpStatements: authoritative
6302 dhcpOption: smtp-server code 69 = array of ip-address
6303 dhcpOption: www-server code 72 = array of ip-address
6304 dhcpOption: wpad-url code 252 = text
6305 &lt;/pre&gt;&lt;/blockquote&gt;
6306
6307 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6308 all the DHCP configuration is loaded, it is ready to receive requests.
6309 The subtree in Debian Edu contain objects with object classes
6310 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6311 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6312 and information about netmasks, dynamic range etc. Leaving out the
6313 details here because it is not relevant for the focus of my
6314 investigation, which is to see if it is possible to merge dns and dhcp
6315 related computer objects.&lt;/p&gt;
6316
6317 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6318 of the client (00:00:00:00:00:00 in this example), using a subtree
6319 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6320 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6321 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6322 like:&lt;/p&gt;
6323
6324 &lt;blockquote&gt;&lt;pre&gt;
6325 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6326 cn: hostname
6327 objectClass: top
6328 objectClass: dhcpHost
6329 dhcpHWAddress: ethernet 00:00:00:00:00:00
6330 dhcpStatements: fixed-address hostname
6331 &lt;/pre&gt;&lt;/blockquote&gt;
6332
6333 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6334 The object classes need to have fixed names, and the configuration
6335 need to be stored in a fairly specific LDAP structure. On the
6336 positive side, the invidiual dhcpHost entires can be anywhere without
6337 the DN pointed to by the dhcpServer entries. The latter should make
6338 it possible to group all host entries in a subtree next to the
6339 configuration entries, and this subtree can also be shared with the
6340 DNS server if the schema proposed above is combined with the dhcpHost
6341 structural object class.
6342
6343 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6344
6345 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6346 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6347 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6348 allowing DNS objects to be stored anywhere under the base cn specified
6349 in the configuration.&lt;/p&gt;
6350
6351 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6352 regarding which LDAP schemas to use and which LDAP structure to use.
6353 I guess one could implement ones own schema, as long as the
6354 objectclasses and attributes have the names used, but this do not
6355 really help when the DHCP subtree need to have a fairly fixed
6356 structure.&lt;/p&gt;
6357
6358 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6359 this might work for Debian Edu:&lt;/p&gt;
6360
6361 &lt;blockquote&gt;&lt;pre&gt;
6362 ou=services
6363 cn=machine-info (dhcpService) - dhcpServiceDN points here
6364 cn=dhcp (dhcpServer)
6365 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6366 cn=10.0.2.0 (dhcpSubnet)
6367 cn=group1 (dhcpGroup/dhcpOptions)
6368 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6369 cn=192.168.0.0 (dhcpSubnet)
6370 cn=group1 (dhcpGroup/dhcpOptions)
6371 ou=machines - PowerDNS base points here
6372 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6373 &lt;/pre&gt;&lt;/blockquote&gt;
6374
6375 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6376 entries to be in the dhcpGroup subtrees, the entries can be stored
6377 there instead of a common machines subtree, and the PowerDNS base
6378 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6379
6380 &lt;p&gt;The combined object under the machines subtree would look something
6381 like this:&lt;/p&gt;
6382
6383 &lt;blockquote&gt;&lt;pre&gt;
6384 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6385 dc: hostname
6386 objectClass: top
6387 objectClass: dhcpHost
6388 objectclass: domainrelatedobject
6389 objectclass: dnsDomainAux
6390 associateddomain: hostname.intern
6391 arecord: 10.11.12.13
6392 dhcpHWAddress: ethernet 00:00:00:00:00:00
6393 dhcpStatements: fixed-address hostname.intern
6394 &lt;/pre&gt;&lt;/blockquote&gt;
6395
6396 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6397 machine, as long as the required attributes are available in a
6398 auxiliary object class.&lt;/p&gt;
6399 </description>
6400 </item>
6401
6402 <item>
6403 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6404 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6405 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6406 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6407 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6408 DHCP services in Debian Edu to use the same LDAP objects for a given
6409 computer, to avoid the possibility of having a inconsistent state for
6410 a computer in LDAP (as in DHCP but no DNS entry or the other way
6411 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6412
6413 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6414 information finally found a solution that seem to work.&lt;/p&gt;
6415
6416 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6417 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6418 we switch powerdns to use its strict LDAP method (ldap-method=strict
6419 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6420 merged into one while making it impossible to transfer the reverse map
6421 to a slave DNS server.&lt;/p&gt;
6422
6423 &lt;p&gt;If we also replace the object class used to get the DNS related
6424 attributes to one allowing these attributes to be combined with the
6425 dhcphost object class, we can merge the DNS and DHCP entries into one.
6426 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6427 proper OIDs, but that is a minor issue), and tested the setup. It
6428 seem to work.&lt;/p&gt;
6429
6430 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6431 for both DNS and DHCP, and even the LTSP configuration I suggested in
6432 an earlier email. The combined LDAP object will look something like
6433 this:&lt;/p&gt;
6434
6435 &lt;blockquote&gt;&lt;pre&gt;
6436 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6437 cn: hostname
6438 objectClass: dhcphost
6439 objectclass: domainrelatedobject
6440 objectclass: dnsdomainaux
6441 associateddomain: hostname.intern
6442 arecord: 10.11.12.13
6443 dhcphwaddress: ethernet 00:00:00:00:00:00
6444 dhcpstatements: fixed-address hostname
6445 ldapconfigsound: Y
6446 &lt;/pre&gt;&lt;/blockquote&gt;
6447
6448 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6449 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6450 before asking DNS to resolve the fixed-adddress. LTSP will use
6451 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6452
6453 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6454 dhcphost in a different location, to allow us to put the objects
6455 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6456 that. If I can&#39;t figure out a way to do that, we can still get rid of
6457 the hosts subtree and move all its content into the DHCP Config tree
6458 (which probably should be renamed to be more related to the new
6459 content. I suspect cn=dnsdhcp,ou=services or something like that
6460 might be a good place to put it.&lt;/p&gt;
6461
6462 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6463 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6464 </description>
6465 </item>
6466
6467 <item>
6468 <title>Idea for storing LTSP configuration in LDAP</title>
6469 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6470 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6471 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6472 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6473 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6474 clients, and that this can be used to fetch configuration from LDAP if
6475 Debian Edu choose to store configuration there.&lt;/p&gt;
6476
6477 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6478 to get configuration from LDAP. The idea is to look up the MAC
6479 address of the client in LDAP, and look for attributes on the form
6480 ltspconfigsetting=value, and use this to export SETTING=value to the
6481 LTSP clients.&lt;/p&gt;
6482
6483 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6484 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6485 allowing us to store all information about a computer in one place.&lt;/p&gt;
6486
6487 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6488 this approach. A real LDAP schema for the ltspClientAux objectclass
6489 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6490
6491 &lt;blockquote&gt;&lt;pre&gt;
6492 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6493 #
6494 # Fetch LTSP client settings from LDAP based on MAC address
6495 #
6496 # Uses ethernet address as stored in the dhcpHost objectclass using
6497 # the dhcpHWAddress attribute or ethernet address stored in the
6498 # ieee802Device objectclass with the macAddress attribute.
6499 #
6500 # This module is written to be schema agnostic, and only depend on the
6501 # existence of attribute names.
6502 #
6503 # The LTSP configuration variables are saved directly using a
6504 # ltspConfig prefix and uppercasing the rest of the attribute name.
6505 # To set the SERVER variable, set the ltspConfigServer attribute.
6506 #
6507 # Some LDAP schema should be created with all the relevant
6508 # configuration settings. Something like this should work:
6509 #
6510 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6511 # SUP top
6512 # AUXILIARY
6513 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6514
6515 LDAPSERVER=$(debian-edu-ldapserver)
6516 if [ &quot;$LDAPSERVER&quot; ] ; then
6517 LDAPBASE=$(debian-edu-ldapserver -b)
6518 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6519 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6520 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6521 grep &#39;^ltspConfig&#39; | while read attr value ; do
6522 # Remove prefix and convert to upper case
6523 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6524 # bass value on to clients
6525 eval &quot;$attr=$value; export $attr&quot;
6526 done
6527 done
6528 fi
6529 &lt;/pre&gt;&lt;/blockquote&gt;
6530
6531 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6532 the while block might end up in a subshell causing the variables set
6533 there to not show up in ltsp-config, but if that is the case I am sure
6534 the code can be restructured to make sure the variables are passed on.
6535 I expect that can be solved with some testing. :)&lt;/p&gt;
6536
6537 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6538 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6539
6540 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6541 configuration in LDAP that was created around year 2000 by
6542 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6543 Xperience, Inc., 2000&lt;/a&gt;. I found its
6544 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6545 personal home page over at redhat.com.&lt;/p&gt;
6546 </description>
6547 </item>
6548
6549 <item>
6550 <title>jXplorer, a very nice LDAP GUI</title>
6551 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6552 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6553 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6554 <description>&lt;p&gt;Since
6555 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6556 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6557 LDAP GUI that is even better than luma. The java application
6558 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6559 moving LDAP objects and subtrees using drag-and-drop, and can
6560 authenticate using Kerberos. I have only tested the Kerberos
6561 authentication, but do not have a LDAP setup allowing me to rewrite
6562 LDAP with my test user yet. It is
6563 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6564 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6565 have with it is how it handle errors. If something go wrong, its
6566 non-intuitive behaviour require me to go through some query work list
6567 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6568 </description>
6569 </item>
6570
6571 <item>
6572 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6573 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6575 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6576 <description>&lt;p&gt;Here is a short update on my &lt;a
6577 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6578 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6579 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6580 not reporting the status for KDE, because the upgrade crashes when
6581 aptitude try because of missing conflicts
6582 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6583 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6584
6585 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6586 complete list of the installed packages. Based on this I see these
6587 differences when I did a test run today. As usual, I do not really
6588 know what the correct set of packages would be, but thought it best to
6589 publish the difference.&lt;/p&gt;
6590
6591 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6592
6593 &lt;blockquote&gt;&lt;p&gt;
6594 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6595 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6596 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6597 libgtksourceview-common libpt-1.10.10-plugins-alsa
6598 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6599 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6600 python-4suite-xml python-eggtrayicon python-gtkhtml2
6601 python-gtkmozembed svgalibg1 xserver-xephyr zip
6602 &lt;/p&gt;&lt;/blockquote&gt;
6603
6604 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6605
6606 &lt;blockquote&gt;&lt;p&gt;
6607 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6608 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6609 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6610 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6611 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6612 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6613 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6614 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6615 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6616 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6617 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6618 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6619 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6620 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6621 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6622 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6623 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6624 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6625 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6626 mysql-common swfdec-gnome totem-gstreamer wodim
6627 &lt;/p&gt;&lt;/blockquote&gt;
6628
6629 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6630
6631 &lt;blockquote&gt;&lt;p&gt;
6632 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6633 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6634 xserver-xorg-input-all xserver-xorg-input-evdev
6635 xserver-xorg-input-kbd xserver-xorg-input-mouse
6636 xserver-xorg-input-synaptics xserver-xorg-video-all
6637 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6638 xserver-xorg-video-chips xserver-xorg-video-cirrus
6639 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6640 xserver-xorg-video-glint xserver-xorg-video-i128
6641 xserver-xorg-video-i740 xserver-xorg-video-mach64
6642 xserver-xorg-video-mga xserver-xorg-video-neomagic
6643 xserver-xorg-video-nouveau xserver-xorg-video-nv
6644 xserver-xorg-video-r128 xserver-xorg-video-radeon
6645 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6646 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6647 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6648 xserver-xorg-video-sis xserver-xorg-video-sisusb
6649 xserver-xorg-video-tdfx xserver-xorg-video-tga
6650 xserver-xorg-video-trident xserver-xorg-video-tseng
6651 xserver-xorg-video-vesa xserver-xorg-video-vmware
6652 xserver-xorg-video-voodoo
6653 &lt;/p&gt;&lt;/blockquote&gt;
6654
6655 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6656
6657 &lt;blockquote&gt;&lt;p&gt;
6658 deskbar-applet xserver-xorg xserver-xorg-core
6659 xserver-xorg-input-wacom xserver-xorg-video-intel
6660 xserver-xorg-video-openchrome
6661 &lt;/p&gt;&lt;/blockquote&gt;
6662
6663 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6664 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6665 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6666 No idea when it hits Squeeze, but when it does I hope it will reduce
6667 the difference somewhat.
6668 </description>
6669 </item>
6670
6671 <item>
6672 <title>LUMA, a very nice LDAP GUI</title>
6673 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6674 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6675 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6676 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6677 directory in Debian Edu, and in the process I started to miss a GUI
6678 tool to browse the LDAP tree. The only one I was able to find in
6679 Debian/Squeeze and Lenny is
6680 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6681 be a great tool to get a overview of the current LDAP directory
6682 populated by default in Skolelinux. Thanks to it, I have been able to
6683 find empty and obsolete subtrees, misplaced objects and duplicate
6684 objects. It will be installed by default in Debian/Squeeze. If you
6685 are working with LDAP, give it a go. :)&lt;/p&gt;
6686
6687 &lt;p&gt;I did notice one problem with it I have not had time to report to
6688 the BTS yet. There is no .desktop file in the package, so the tool do
6689 not show up in the Gnome and KDE menus, but only deep down in in the
6690 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6691 released.&lt;/p&gt;
6692
6693 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6694 like to move objects and remove subtrees directly in the GUI, but have
6695 not found a way to do that with LUMA yet. So in the mean time, I use
6696 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6697
6698 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6699 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6700
6701 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6702 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6703 useful GUI alternative. It seem like a good tool, but is unmaintained
6704 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6705 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6706 </description>
6707 </item>
6708
6709 <item>
6710 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6711 <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>
6712 <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>
6713 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6714 <description>&lt;p&gt;A while back, I
6715 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6716 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6717 for storing DNS and DHCP information in LDAP to combine the two sets
6718 of information into one LDAP object representing a computer.&lt;/p&gt;
6719
6720 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6721 the dhcpHost object class auxiliary, to allow it to be combined with
6722 the dNSDomain object class, and thus forming one object for one
6723 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6724
6725 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6726 without also changing the assigned number for the object class, and I
6727 do not know enough about LDAP schema design to do that properly for
6728 Debian Edu.&lt;/p&gt;
6729
6730 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6731 the
6732 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6733 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6734 available today from IETF.&lt;/p&gt;
6735
6736 &lt;pre&gt;
6737 --- dhcp.schema (revision 65192)
6738 +++ dhcp.schema (working copy)
6739 @@ -376,7 +376,7 @@
6740 objectclass ( 2.16.840.1.113719.1.203.6.6
6741 NAME &#39;dhcpHost&#39;
6742 DESC &#39;This represents information about a particular client&#39;
6743 - SUP top
6744 + SUP top AUXILIARY
6745 MUST cn
6746 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6747 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6748 &lt;/pre&gt;
6749
6750 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6751 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6752 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6753
6754 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6755 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6756 </description>
6757 </item>
6758
6759 <item>
6760 <title>Calling tasksel like the installer, while still getting useful output</title>
6761 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6762 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6763 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6764 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6765 installs packages during the normal debian-installer run. Until now,
6766 I have ended up letting tasksel do the work, with the annoying problem
6767 of not getting any feedback at all when something fails (like a
6768 conffile question from dpkg or a download that fails), using code like
6769 this:
6770
6771 &lt;blockquote&gt;&lt;pre&gt;
6772 export DEBIAN_FRONTEND=noninteractive
6773 tasksel --new-install
6774 &lt;/pre&gt;&lt;/blockquote&gt;
6775
6776 This would invoke tasksel, let its automatic task selection pick the
6777 tasks to install, and continue to install the requested tasks without
6778 any output what so ever.
6779
6780 Recently I revisited this problem while working on the automatic
6781 package upgrade testing, because tasksel would some times hang without
6782 any useful feedback, and I want to see what is going on when it
6783 happen. Then it occured to me, I can parse the output from tasksel
6784 when asked to run in test mode, and use that aptitude command line
6785 printed by tasksel then to simulate the tasksel run. I ended up using
6786 code like this:
6787
6788 &lt;blockquote&gt;&lt;pre&gt;
6789 export DEBIAN_FRONTEND=noninteractive
6790 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6791 $cmd
6792 &lt;/pre&gt;&lt;/blockquote&gt;
6793
6794 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6795 --without-recommends -o APT::Install-Recommends=no -y install
6796 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6797 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6798 laptop task and all packages with priority standard , required and
6799 important, just like tasksel would have done it during
6800 installation.&lt;/p&gt;
6801
6802 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6803 install packages without using debconf-apt-progress, for use cases
6804 like this.&lt;/p&gt;
6805 </description>
6806 </item>
6807
6808 <item>
6809 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6810 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6812 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6813 <description>&lt;p&gt;My
6814 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6815 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6816 finally made the upgrade logs available from
6817 &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;.
6818 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6819 apt and aptitude, and found their differences interesting. This time
6820 I will only focus on their removal plans.&lt;/p&gt;
6821
6822 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6823 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6824 surprising part is that it want to remove xorg and all
6825 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6826 sure why. When asking aptitude to do the same, it want to remove 129
6827 packages, but most of them are library packages I suspect are no
6828 longer needed. Both of them want to remove bluetooth packages, which
6829 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6830
6831 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6832 which seem like a bad idea and xorg the same way as with Gnome. Asking
6833 aptitude for the same, it wants to remove 192 packages, none which are
6834 too surprising.&lt;/p&gt;
6835
6836 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6837 and avoided, and perhaps others as well. Here are the complete list
6838 of planned removals. The complete logs is available from the URL
6839 above. Note if you want to repeat these tests, that the upgrade test
6840 for kde+apt-get hung in the tasksel setup because of dpkg asking
6841 conffile questions. No idea why. I worked around it by using
6842 &#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
6843 continue.&lt;/p&gt;
6844
6845 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6846 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6847 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6848 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6849 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6850 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6851 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6852 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6853 xserver-xorg-input-kbd xserver-xorg-input-mouse
6854 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6855 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6856 xserver-xorg-video-ati xserver-xorg-video-chips
6857 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6858 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6859 xserver-xorg-video-glint xserver-xorg-video-i128
6860 xserver-xorg-video-i740 xserver-xorg-video-imstt
6861 xserver-xorg-video-intel xserver-xorg-video-mach64
6862 xserver-xorg-video-mga xserver-xorg-video-neomagic
6863 xserver-xorg-video-nsc xserver-xorg-video-nv
6864 xserver-xorg-video-openchrome xserver-xorg-video-r128
6865 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6866 xserver-xorg-video-rendition xserver-xorg-video-s3
6867 xserver-xorg-video-s3virge xserver-xorg-video-savage
6868 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6869 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6870 xserver-xorg-video-tga xserver-xorg-video-trident
6871 xserver-xorg-video-tseng xserver-xorg-video-v4l
6872 xserver-xorg-video-vesa xserver-xorg-video-vga
6873 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6874 xulrunner-1.9-gnome-support&lt;/p&gt;
6875
6876 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6877
6878 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6879 djvulibre-desktop finger gnome-app-install gnome-mount
6880 gnome-network-admin gnome-spell gnome-vfs-obexftp
6881 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6882 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6883 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6884 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6885 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6886 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6887 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6888 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6889 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6890 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6891 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6892 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6893 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6894 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6895 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6896 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6897 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6898 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6899 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6900 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6901 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6902 openoffice.org-writer2latex openssl-blacklist p7zip
6903 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6904 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6905 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6906 swfdec-mozilla totem-gstreamer update-manager wodim
6907 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6908 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6909 zip&lt;/p&gt;
6910
6911 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6912
6913 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6914 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6915 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6916 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6917 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6918 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6919 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6920 xserver-xorg-input-kbd xserver-xorg-input-mouse
6921 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6922 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6923 xserver-xorg-video-ati xserver-xorg-video-chips
6924 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6925 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6926 xserver-xorg-video-glint xserver-xorg-video-i128
6927 xserver-xorg-video-i740 xserver-xorg-video-imstt
6928 xserver-xorg-video-intel xserver-xorg-video-mach64
6929 xserver-xorg-video-mga xserver-xorg-video-neomagic
6930 xserver-xorg-video-nsc xserver-xorg-video-nv
6931 xserver-xorg-video-openchrome xserver-xorg-video-r128
6932 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6933 xserver-xorg-video-rendition xserver-xorg-video-s3
6934 xserver-xorg-video-s3virge xserver-xorg-video-savage
6935 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6936 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6937 xserver-xorg-video-tga xserver-xorg-video-trident
6938 xserver-xorg-video-tseng xserver-xorg-video-v4l
6939 xserver-xorg-video-vesa xserver-xorg-video-vga
6940 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6941
6942 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6943 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6944 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6945 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6946 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6947 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6948 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6949 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6950 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6951 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6952 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6953 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6954 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6955 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6956 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6957 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6958 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6959 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6960 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6961 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6962 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6963 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6964 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6965 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6966 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6967 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6968 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6969 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6970 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6971 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6972 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6973 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6974 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6975 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6976 texlive-common texlive-doc-base texlive-fonts-recommended
6977 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6978 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6979 xulrunner-1.9&lt;/p&gt;
6980
6981 </description>
6982 </item>
6983
6984 <item>
6985 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6986 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6987 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6988 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6989 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6990 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6991 have been discovered and reported in the process
6992 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6993 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6994 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6995 kdebase-workspace-data), and to get a more regular testing going on, I
6996 am working on a script to automate the test.&lt;/p&gt;
6997
6998 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6999 Gnome or KDE desktop installation inside the chroot before upgrading
7000 it. To ensure no services are started in the chroot, a policy-rc.d
7001 script is inserted. To make sure tasksel believe it is to install a
7002 desktop on a laptop, the tasksel tests are replaced in the chroot
7003 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7004
7005 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7006 currently always fail because udev refuses to upgrade with the kernel
7007 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7008 is created. The bug report
7009 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7010 this problem do not trigger in a chroot, but I touch the file anyway
7011 to make sure the upgrade go well. Testing on virtual and real
7012 hardware have failed me because of udev so far, and creating this file
7013 do the trick in such settings anyway. This is a
7014 &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
7015 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7016 maintainer because he lack the resources to rewrite udev to keep
7017 working with old kernels or something like that. I really wish the
7018 udev upstream would keep udev backwards compatible, to avoid such
7019 upgrade problem, but given that they fail to do so, I guess
7020 documenting the way out of this mess is the best option we got for
7021 Debian Squeeze.&lt;/p&gt;
7022
7023 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7024 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7025 trick:&lt;/p&gt;
7026
7027 &lt;blockquote&gt;&lt;pre&gt;
7028 #!/bin/sh
7029 set -ex
7030
7031 if [ &quot;$1&quot; ] ; then
7032 desktop=$1
7033 else
7034 desktop=gnome
7035 fi
7036
7037 from=lenny
7038 to=squeeze
7039
7040 exec &amp;lt; /dev/null
7041 unset LANG
7042 mirror=http://ftp.skolelinux.org/debian
7043 tmpdir=chroot-$from-upgrade-$to-$desktop
7044 fuser -mv .
7045 debootstrap $from $tmpdir $mirror
7046 chroot $tmpdir aptitude update
7047 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7048 #!/bin/sh
7049 exit 101
7050 EOF
7051 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7052 exit_cleanup() {
7053 umount $tmpdir/proc
7054 }
7055 mount -t proc proc $tmpdir/proc
7056 # Make sure proc is unmounted also on failure
7057 trap exit_cleanup EXIT INT
7058
7059 chroot $tmpdir aptitude -y install debconf-utils
7060
7061 # Make sure tasksel autoselection trigger. It need the test scripts
7062 # to return the correct answers.
7063 echo tasksel tasksel/desktop multiselect $desktop | \
7064 chroot $tmpdir debconf-set-selections
7065
7066 # Include the desktop and laptop task
7067 for test in desktop laptop ; do
7068 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7069 #!/bin/sh
7070 exit 2
7071 EOF
7072 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7073 done
7074
7075 DEBIAN_FRONTEND=noninteractive
7076 DEBIAN_PRIORITY=critical
7077 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7078 chroot $tmpdir tasksel --new-install
7079
7080 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7081 chroot $tmpdir aptitude update
7082 touch $tmpdir/etc/udev/kernel-upgrade
7083 chroot $tmpdir aptitude -y dist-upgrade
7084 fuser -mv
7085 &lt;/pre&gt;&lt;/blockquote&gt;
7086
7087 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7088 with aptitude, but I have not had time to look at how they behave
7089 differently so far. I hope to get a cron job running to do the test
7090 regularly and post the result on the web. The Gnome upgrade currently
7091 work, while the KDE upgrade fail because of the bug in
7092 kdebase-workspace-data&lt;/p&gt;
7093
7094 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7095 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7096 post, so I will refrain from trying. I can report that for Gnome,
7097 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7098 remove and 1 not upgraded and 1024MB need to be downloaded while for
7099 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7100 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7101
7102 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7103 is able to migrate to dependency based boot sequencing and parallel
7104 booting without a hitch. Was unsure if there were still bugs with
7105 packages failing to clean up their obsolete init.d script during
7106 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7107 packages.&lt;/p&gt;
7108 </description>
7109 </item>
7110
7111 <item>
7112 <title>Upstart or sysvinit - as init.d scripts see it</title>
7113 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7114 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7115 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7116 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7117 scripts to migrate (some of) their operations to upstart job while
7118 keeping the init.d for hurd and kfreebsd. The packages with such
7119 needs will need a way to get their init.d scripts to behave
7120 differently when used with sysvinit and with upstart. Because of
7121 this, I had a look at the environment variables set when a init.d
7122 script is running under upstart, and when it is not.&lt;/p&gt;
7123
7124 &lt;p&gt;With upstart, I notice these environment variables are set when a
7125 script is started from rcS.d/ (ignoring some irrelevant ones like
7126 COLUMNS):&lt;/p&gt;
7127
7128 &lt;blockquote&gt;&lt;pre&gt;
7129 DEFAULT_RUNLEVEL=2
7130 previous=N
7131 PREVLEVEL=
7132 RUNLEVEL=
7133 runlevel=S
7134 UPSTART_EVENTS=startup
7135 UPSTART_INSTANCE=
7136 UPSTART_JOB=rc-sysinit
7137 &lt;/pre&gt;&lt;/blockquote&gt;
7138
7139 &lt;p&gt;With sysvinit, these environment variables are set for the same
7140 script.&lt;/p&gt;
7141
7142 &lt;blockquote&gt;&lt;pre&gt;
7143 INIT_VERSION=sysvinit-2.88
7144 previous=N
7145 PREVLEVEL=N
7146 RUNLEVEL=S
7147 runlevel=S
7148 &lt;/pre&gt;&lt;/blockquote&gt;
7149
7150 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7151 sysvinit are not set by upstart. Not sure if it is intentional or not
7152 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7153
7154 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7155 looking for the UPSTART_JOB environment variable seem to be a good
7156 choice.&lt;/p&gt;
7157 </description>
7158 </item>
7159
7160 <item>
7161 <title>A manual for standards wars...</title>
7162 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7163 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7164 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7165 <description>&lt;p&gt;Via the
7166 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7167 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7168 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7169 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7170 following the standards wars of today.&lt;/p&gt;
7171 </description>
7172 </item>
7173
7174 <item>
7175 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7176 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7177 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7178 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7179 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7180 to get a list of the machine types in use thanks to the DMI
7181 information extracted from each machine. The script to do so is
7182 included in the sitesummary package, and here is example output from
7183 the Skolelinux build servers:&lt;/p&gt;
7184
7185 &lt;blockquote&gt;&lt;pre&gt;
7186 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7187 vendor count
7188 Dell Computer Corporation 1
7189 PowerEdge 1750 1
7190 IBM 1
7191 eserver xSeries 345 -[8670M1X]- 1
7192 Intel 2
7193 [no-dmi-info] 3
7194 maintainer:~#
7195 &lt;/pre&gt;&lt;/blockquote&gt;
7196
7197 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7198 provided in each machine. Here there are Intel machines without model
7199 information listed with Intel as vendor and no model, and virtual Xen
7200 machines listed as [no-dmi-info]. One can add -l as a command line
7201 option to list the individual machines.&lt;/p&gt;
7202
7203 &lt;p&gt;A larger list is
7204 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7205 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7206 provide the basic sitesummary report publicly. In their report there
7207 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7208 their machines, and as sitesummary is available in both distributions,
7209 it is trivial to get all of them to report to the same central
7210 collector.&lt;/p&gt;
7211 </description>
7212 </item>
7213
7214 <item>
7215 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7216 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7217 <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>
7218 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7219 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7220 start at boot when an NVidia video card is used is handled. The
7221 problem seem to be that the nvidia X.org driver uses a long time to
7222 initialize, and this duration is longer than kdm is configured to
7223 wait.&lt;/p&gt;
7224
7225 &lt;p&gt;I came across two bugs related to this issue,
7226 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7227 against initscripts and passed on to nvidia-glx when it became obvious
7228 that the nvidia drivers were involved, and
7229 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7230 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7231
7232 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7233 problem nvidia video card owners experience and make sure the Debian
7234 distribution work out of the box for these users. The nvidia driver
7235 maintainers expect kdm to be set up to wait longer, while kdm expect
7236 the nvidia driver maintainers to fix the driver to start faster, and
7237 while they wait for each other I guess the users end up switching to a
7238 distribution that work for them. I have no idea what the solution is,
7239 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7240
7241 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7242 </description>
7243 </item>
7244
7245 <item>
7246 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7247 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7248 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7249 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7250 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7251 The feature seem to hold up pretty well, but three fairly serious
7252 issues are known and should be solved:
7253
7254 &lt;p&gt;&lt;ul&gt;
7255
7256 &lt;li&gt;The wicd package seen to
7257 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7258 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7259 parallel booting is enabled. No idea why, but the wicd maintainer
7260 seem to be on the case.&lt;/li&gt;
7261
7262 &lt;li&gt;The nvidia X driver seem to
7263 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7264 triggered more easily when parallel booting is in effect. The
7265 maintainer is on the case.&lt;/li&gt;
7266
7267 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7268 sequencing (the shutdown is broken) when old file-rc users
7269 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7270 sysv-rc. One way to solve it would be for file-rc to create
7271 /etc/init.d/.legacy-bootordering, and another is to try to make
7272 sysv-rc more robust. Will investigate some more and probably upload a
7273 workaround in sysv-rc to help those trying to move from file-rc to
7274 sysv-rc get a working shutdown.&lt;/li&gt;
7275
7276 &lt;/ul&gt;&lt;/p&gt;
7277
7278 &lt;p&gt;All in all not many surprising issues, and all of them seem
7279 solvable before Squeeze is released. In addition to these there are
7280 some packages with bugs in their dependencies and run level settings,
7281 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7282
7283 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7284 the BTS, please usertag the report to get it to show up at
7285 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7286 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7287
7288 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7289 </description>
7290 </item>
7291
7292 <item>
7293 <title>More flexible firmware handling in debian-installer</title>
7294 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7295 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7296 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7297 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7298 found time today to return to the project. Having to spend less time
7299 working dependency based boot in debian, as it is almost complete now,
7300 definitely helped freeing some time.&lt;/p&gt;
7301
7302 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7303 include some firmware packages on the Debian Edu CDs, those needed to
7304 get disk and network controllers working. Without having these
7305 firmware packages available during installation, it is impossible to
7306 install Debian Edu on the given machine, and because our target group
7307 are non-technical people, asking them to provide firmware packages on
7308 an external medium is a support pain. Initially, I expected it to be
7309 enough to include the firmware packages on the CD to get
7310 debian-installer to find and use them. This proved to be wrong.
7311 Next, I hoped it was enough to symlink the relevant firmware packages
7312 to some useful location on the CD (tried /cdrom/ and
7313 /cdrom/firmware/). This also proved to not work, and at this point I
7314 found time to look at the debian-installer code to figure out what was
7315 going to work.&lt;/p&gt;
7316
7317 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7318 look revealed that it would only look for firmware packages outside
7319 the installation media, so the CD was never checked for firmware
7320 packages. It would only check USB sticks, floppies and other
7321 &quot;external&quot; media devices. Today I changed it to also look in the
7322 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7323 solve the problem I ran into with Debian edu. I also changed it to
7324 look in /firmware/, to make sure the installer also find firmware
7325 provided in the initrd when booting the installer via PXE, to allow us
7326 to provide the same feature in the PXE setup included in Debian
7327 Edu.&lt;/p&gt;
7328
7329 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7330 activated without asking if the license is accepted, I extended
7331 hw-detect to look for preinst scripts in the firmware packages, and
7332 run these before activating the firmware during installation. The
7333 license question is asked using debconf in the preinst, so this should
7334 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7335
7336 &lt;p&gt;If you want to discuss the details of these features, please
7337 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7338 </description>
7339 </item>
7340
7341 <item>
7342 <title>Parallellized boot is now the default in Debian/unstable</title>
7343 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7344 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7345 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7346 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7347 Debian/unstable for machines using dependency based boot sequencing.
7348 Apparently the testing of concurrent booting has been wider than
7349 expected, if I am to believe the
7350 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7351 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7352 with the feature this weekend, to give us some time to detect any
7353 remaining problems before Squeeze is frozen. If serious problems are
7354 detected, it is simple to change the default back to sequential boot.
7355 The upload of the new sysvinit package also activate a new upstream
7356 version.&lt;/p&gt;
7357
7358 More information about
7359 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7360 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7361 currently possible to disable parallel booting when one run into
7362 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7363
7364 &lt;blockquote&gt;&lt;pre&gt;
7365 CONCURRENCY=none
7366 &lt;/pre&gt;&lt;/blockquote&gt;
7367
7368 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7369 the BTS, please usertag the report to get it to show up at
7370 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7371 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7372 </description>
7373 </item>
7374
7375 <item>
7376 <title>Sitesummary tip: Listing MAC address of all clients</title>
7377 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7378 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7379 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7380 <description>&lt;p&gt;In the recent Debian Edu versions, the
7381 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7382 system&lt;/a&gt; is used to keep track of the machines in the school
7383 network. Each machine will automatically report its status to the
7384 central server after boot and once per night. The network setup is
7385 also reported, and using this information it is possible to get the
7386 MAC address of all network interfaces in the machines. This is useful
7387 to update the DHCP configuration.&lt;/p&gt;
7388
7389 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7390 ist all MAC addresses of all machines reporting to sitesummary. Run
7391 this on the collector host:&lt;/p&gt;
7392
7393 &lt;blockquote&gt;&lt;pre&gt;
7394 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7395 &lt;/pre&gt;&lt;/blockquote&gt;
7396
7397 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7398 line per machine and with space between the MAC addresses.&lt;/p&gt;
7399
7400 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7401 addresses for hosts, it would be possible to extend this to fetch
7402 machine information from sitesummary and update the DHCP and DNS
7403 tables in LDAP using this information. Such tool is unfortunately not
7404 written yet.&lt;/p&gt;
7405 </description>
7406 </item>
7407
7408 <item>
7409 <title>systemd, an interesting alternative to upstart</title>
7410 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7411 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7412 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7413 <description>&lt;p&gt;The last few days a new boot system called
7414 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7415 has been
7416 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7417
7418 to the free software world. I have not yet had time to play around
7419 with it, but it seem to be a very interesting alternative to
7420 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7421 a good alternative for Debian when we are able to switch to an event
7422 based boot system. Tollef is
7423 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7424 systemd into Debian, and I look forward to seeing how well it work. I
7425 like the fact that systemd handles init.d scripts with dependency
7426 information natively, allowing them to run in parallel where upstart
7427 at the moment do not.&lt;/p&gt;
7428
7429 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7430 platform support. It only work on recent Linux kernels, and also need
7431 some new kernel features enabled to function properly. This means
7432 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7433 system. Not sure how that will be handled if systemd proves to be the
7434 way forward.&lt;/p&gt;
7435
7436 &lt;p&gt;In the mean time, based on the
7437 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7438 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7439 decided to enable full parallel booting as the default in Debian as
7440 soon as possible (probably this weekend or early next week), to see if
7441 there are any remaining serious bugs in the init.d dependencies. A
7442 new version of the sysvinit package implementing this change is
7443 already in experimental. If all go well, Squeeze will be released
7444 with parallel booting enabled by default.&lt;/p&gt;
7445 </description>
7446 </item>
7447
7448 <item>
7449 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7450 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7451 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7452 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7453 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7454 complete, so complete that it is actually possible to run all the
7455 init.d scripts in parallell based on these dependencies. If you want
7456 to test your Squeeze system, make sure
7457 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7458 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7459 /etc/default/rcS:&lt;/p&gt;
7460
7461 &lt;blockquote&gt;&lt;pre&gt;
7462 CONCURRENCY=makefile
7463 &lt;/pre&gt;&lt;/blockquote&gt;
7464
7465 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7466 scripts in parallel using the dependency information stored in
7467 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7468 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7469 to try to start the kdm and gdm scripts as early as possible, and will
7470 start the facilities required by kdm or gdm as early as possible to
7471 make this happen.&lt;/p&gt;
7472
7473 &lt;p&gt;Give it a try, and see if you like the result. If some services
7474 fail to start properly, it is most likely because they have incomplete
7475 init.d script dependencies in their startup script (or some of their
7476 dependent scripts have incomplete dependencies). Report bugs and get
7477 the package maintainers to fix it. :)&lt;/p&gt;
7478
7479 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7480 manage to get the init.d script dependencies complete and correct. I
7481 expect we will get there in Squeeze+1, if we get manage to test and
7482 fix the remaining issues.&lt;/p&gt;
7483
7484 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7485 the BTS, please usertag the report to get it to show up at
7486 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7487 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7488 </description>
7489 </item>
7490
7491 <item>
7492 <title>Debian has switched to dependency based boot sequencing</title>
7493 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7494 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7495 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7496 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7497 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7498 have been migrated to using dependency based boot sequencing. This
7499 conclude work me and others have been doing for the last three days.
7500 It feels great to see this finally part of the default Debian
7501 installation. Now we just need to weed out the last few problems that
7502 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7503
7504 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7505 fixing the more fundamental problem of handing the event based
7506 non-predictable kernel in the early boot.&lt;/p&gt;
7507 </description>
7508 </item>
7509
7510 <item>
7511 <title>Taking over sysvinit development</title>
7512 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7513 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7514 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7515 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7516 the existing sysvinit upstream developer, I decided a few weeks ago to
7517 take over the package and become the new upstream. The number of
7518 patches to track for the Debian package was becoming a burden, and the
7519 lack of synchronization between the distribution made it hard to keep
7520 the package up to date.&lt;/p&gt;
7521
7522 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7523 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7524 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7525 and Fedora), based on the patches currently in use in these
7526 distributions. We Debian maintainers plan to move to this tarball as
7527 the new upstream as soon as we find time to do the merge. Since the
7528 new tarball was created, we agreed with Werner at SuSe to make a new
7529 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7530 development there. The project is registered and currently waiting
7531 for approval by the Savannah administrators, and as soon as it is
7532 approved, we will import the old versions from svn and continue
7533 working on the future release.&lt;/p&gt;
7534
7535 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7536 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7537 </description>
7538 </item>
7539
7540 <item>
7541 <title>Debian boots quicker and quicker</title>
7542 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7543 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7544 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7545 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7546 people involved in the boot system on Debian and Ubuntu, to see if we
7547 could find more ways to speed up the boot system. This was an Ubuntu
7548 funded
7549 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7550 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7551 of boot systems, and ways to handle the increasing number of boot
7552 issues introduced by the Linux kernel becoming more and more
7553 asynchronous and event base. The Ubuntu approach using udev and
7554 upstart might be a good way forward. Time will show.&lt;/p&gt;
7555
7556 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7557 process in Debian. All of these should be applied to get a quick
7558 boot:&lt;/p&gt;
7559
7560 &lt;ul&gt;
7561
7562 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7563
7564 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7565 clock is in UTC.&lt;/li&gt;
7566
7567 &lt;li&gt;Install and activate the insserv package to enable
7568 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7569 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7570
7571 &lt;/ul&gt;
7572
7573 These points are based on the Google summer of code work done by
7574 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7575 Villegas&lt;/a&gt;.
7576
7577 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7578 unstable yesterday. When we tested it, we were able to cut 6 seconds
7579 from the boot sequence. It depend on very correct dependency
7580 declaration in all init.d scripts, so I expect us to find edge cases
7581 where the dependences in some scripts are slightly wrong when we start
7582 using this.&lt;/p&gt;
7583
7584 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7585 introduced by Raphael Geissert today, one that could affect the
7586 startup speed as well. Instead of starting some scripts concurrently
7587 from rcS.d/ and another set of scripts from rc2.d/, it would be
7588 possible to run a of them in the same process. A quick way to test
7589 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7590 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7591 </description>
7592 </item>
7593
7594 <item>
7595 <title>BSAs påstander om piratkopiering møter motstand</title>
7596 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7597 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7598 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7599 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7600 programvareselskapene som Microsoft og Apple, publisert en rapport der
7601 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7602 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7603 dager siden kom
7604 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7605 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7606 dagene. Et spesielt interessant kommentar fra Sverige,
7607 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7608 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7609
7610 &lt;blockquote&gt;
7611 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7612 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7613 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7614 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7615 &lt;/blockquote&gt;
7616
7617 &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
7618 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7619 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7620 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7621 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7622
7623 &lt;p&gt;Fant lenkene via &lt;a
7624 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7625 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7626 </description>
7627 </item>
7628
7629 <item>
7630 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7631 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7632 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7633 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7634 <description>&lt;p&gt;Kom over
7635 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7636 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7637 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7638 jobber til daglig. En rask opptelling forteller meg at vi har 490
7639 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7640 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7641 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7642 </description>
7643 </item>
7644
7645 <item>
7646 <title>Kryptert harddisk - naturligvis</title>
7647 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7649 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7650 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7651 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7652 når en tar tap av arbeidstid, fortrolige dokumenter,
7653 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7654 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7655 til at jeg har kryptert harddisken på både kontormaskinen og min
7656 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7657 komme på avveie, den første informasjon relatert til jobben min ved
7658 Universitetet i Oslo, og den andre relatert til blant annet
7659 foreningsarbeide. Kryptering av diskene gjør at det er lite
7660 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7661 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7662 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7663 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7664 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7665 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7666 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7667 det er gjort slik jeg gjør det er minimale, og gevinstene er
7668 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7669 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7670
7671 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7672 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7673 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7674 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7675 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7676 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7677 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7678 betydelige.&lt;/p&gt;
7679 </description>
7680 </item>
7681
7682 <item>
7683 <title>Two projects that have improved the quality of free software a lot</title>
7684 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7685 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7686 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7687 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7688 quality of free software, and I wanted to mention both in case someone
7689 do not yet know them.&lt;/p&gt;
7690
7691 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7692 tool to detect and expose errors in the memory handling of programs.
7693 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7694 and it will report any problems on stdout. It is even better if the
7695 program include debug information. With debug information, it is able
7696 to report the source file name and line number where the problem
7697 occurs. It can report things like &#39;reading past memory block in file
7698 X line N, the memory block was allocated in file Y, line M&#39;, and
7699 &#39;using uninitialised value in control logic&#39;. This tool has made it
7700 trivial to investigate reproducible crash bugs in programs, and have
7701 reduced the number of this kind of bugs in free software a lot.
7702
7703 &lt;p&gt;The second one is
7704 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7705 a source code checker. It is able to process the source of a program
7706 and find problems in the logic without running the program. It
7707 started out as the Stanford Checker and became well known when it was
7708 used to find bugs in the Linux kernel. It is now a commercial tool
7709 and the company behind it is running
7710 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7711 free software community, where a lot of free software projects get
7712 their source checked for free. Several thousand defects have been
7713 found and fixed so far. It can find errors like &#39;lock L taken in file
7714 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7715 Y lines O to P can never be executed&#39;. The projects included in the
7716 community service project have managed to get rid of a lot of
7717 reliability problems thanks to Coverity.&lt;/p&gt;
7718
7719 &lt;p&gt;I believe tools like this, that are able to automatically find
7720 errors in the source, are vital to improve the quality of software and
7721 make sure we can get rid of the crashing and failing software we are
7722 surrounded by today.&lt;/p&gt;
7723 </description>
7724 </item>
7725
7726 <item>
7727 <title>No patch is not better than a useless patch</title>
7728 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7730 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7731 <description>&lt;p&gt;Julien Blache
7732 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7733 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7734 patch allow one to discuss a concrete and proposed solution, and also
7735 prove that the issue at hand is important enough for someone to spent
7736 time on fixing it. No patch do not provide any of these positive
7737 properties.&lt;/p&gt;
7738 </description>
7739 </item>
7740
7741 <item>
7742 <title>Standardize on protocols and formats, not vendors and applications</title>
7743 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7744 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7745 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7746 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7747 very good one to form a long lived computer infrastructure. It is the
7748 simple one, lost by many in todays computer industry: Standardize on
7749 open network protocols and open exchange/storage formats, not applications.
7750 Applications come and go, while protocols and files tend to stay, and
7751 thus one want to make it easy to change application and vendor, while
7752 avoiding conversion costs and locking users to a specific platform or
7753 application.&lt;/p&gt;
7754
7755 &lt;p&gt;This approach make it possible to replace the client applications
7756 independently of the server applications. One can even allow users to
7757 use several different applications as long as they handle the selected
7758 protocol and format. In the normal case, only one client application
7759 is recommended and users only get help if they choose to use this
7760 application, but those that want to deviate from the easy path are not
7761 blocked from doing so.&lt;/p&gt;
7762
7763 &lt;p&gt;It also allow us to replace the server side without forcing the
7764 users to replace their applications, and thus allow us to select the
7765 best server implementation at any moment, when scale and resouce
7766 requirements change.&lt;/p&gt;
7767
7768 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7769 open formats, but I would never recommend standardizing on a single
7770 application that do not use open network protocol or open formats.&lt;/p&gt;
7771 </description>
7772 </item>
7773
7774 <item>
7775 <title>Returning from Skolelinux developer gathering</title>
7776 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7777 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7778 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7779 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7780 Edu/Skolelinux development gathering. I got a bit done tuning the
7781 desktop, and looked into the dynamic service location protocol
7782 implementation avahi. It look like it could be useful for us. Almost
7783 30 people participated, and I believe it was a great environment to
7784 get to know the Skolelinux system. Walter Bender, involved in the
7785 development of the Sugar educational platform, presented his stuff and
7786 also helped me improve my OLPC installation. He also showed me that
7787 his Turtle Art application can be used in standalone mode, and we
7788 agreed that I would help getting it packaged for Debian. As a
7789 standalone application it would be great for Debian Edu. We also
7790 tried to get the video conferencing working with two OLPCs, but that
7791 proved to be too hard for us. The application seem to need more work
7792 before it is ready for me. I look forward to getting home and relax
7793 now. :)&lt;/p&gt;
7794 </description>
7795 </item>
7796
7797 <item>
7798 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7799 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7800 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7801 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7802 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7803 optimal. There is RFC 2307 documenting one way to store NIS maps in
7804 LDAP, and a modified version of this normally called RFC 2307bis, with
7805 some modifications to be compatible with Active Directory. The RFC
7806 specification handle the content of a lot of system databases, but do
7807 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7808
7809 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7810 we would like to store information about users, SMB clients/hosts,
7811 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7812 and LTSP configuration in LDAP. These objects have a lot in common,
7813 but with the current LDAP schemas it is not possible to have one
7814 object per entity. For example, one need to have at least three LDAP
7815 objects for a given computer, one with the SMB related stuff, one with
7816 DNS information and another with DHCP information. The schemas
7817 provided for DNS and DHCP are impossible to combine into one LDAP
7818 object. In addition, it is impossible to implement quick queries for
7819 netgroup membership, because of the way NIS triples are implemented.
7820 It just do not scale. I believe it is time for a few RFC
7821 specifications to cleam up this mess.&lt;/p&gt;
7822
7823 &lt;p&gt;I would like to have one LDAP object representing each computer in
7824 the network, and this object can then keep the SMB (ie host key), DHCP
7825 (mac address/name) and DNS (name/IP address) settings in one place.
7826 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7827
7828 &lt;p&gt;I would also like to have a quick way to map from a user or
7829 computer and to the net group this user or computer is a member.&lt;/p&gt;
7830
7831 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7832 in this regard, and the unix side need to catch up. Time to start a
7833 new IETF work group?&lt;/p&gt;
7834 </description>
7835 </item>
7836
7837 <item>
7838 <title>Endelig er Debian Lenny gitt ut</title>
7839 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7840 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7841 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7842 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7843 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7844 Et langt steg videre for Debian-prosjektet, og en rekke nye
7845 programpakker blir nå tilgjengelig for de av oss som bruker den
7846 stabile utgaven av Debian. Neste steg er nå å få
7847 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7848 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7849 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7850 slippes løs på skolene. Takk til alle debian-utviklerne som har
7851 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7852 bootsekvens tilgjengelig i stabil utgave, vha pakken
7853 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7854 </description>
7855 </item>
7856
7857 <item>
7858 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7859 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7860 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7861 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7862 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7863 Oslo. Most of Saturday was used for the general assemly for the
7864 member organization, but the rest of the weekend I used to tune the
7865 LTSP installation. LTSP now work out of the box on the 10-network.
7866 Acer Aspire One proved to be a very nice thin client, with both
7867 screen, mouse and keybard in a small box. Was working on getting the
7868 diskless workstation setup configured out of the box, but did not
7869 finish it before the weekend was up.&lt;/p&gt;
7870
7871 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7872 the Brazilian group, so that will have to wait for the next
7873 development gathering. Would love to have the Debian Edu installer
7874 automatically detect and configure a multiseat setup when it find one
7875 of these cards.&lt;/p&gt;
7876 </description>
7877 </item>
7878
7879 <item>
7880 <title>The sorry state of multimedia browser plugins in Debian</title>
7881 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7882 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7883 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7884 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7885 plugins available in Debian Lenny, to see which one we should use by
7886 default in Debian Edu. We need an embedded video playing plugin with
7887 control buttons to pause or stop the video, and capable of streaming
7888 all the multimedia content available on the web. The test results and
7889 notes are available on
7890 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7891 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7892 fill this need. My personal video player favorite, VLC, has a really
7893 bad plugin which fail on a lot of the test pages. A lot of the MIME
7894 types I would expect to work with any free software player (like
7895 video/ogg), just do not work. And simple formats like the
7896 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7897 totem and vlc plugins. I hope the situation will improve soon. No
7898 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7899
7900 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7901 be the only one fitting our needs. :/&lt;/p&gt;
7902 </description>
7903 </item>
7904
7905 </channel>
7906 </rss>