]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
9802e1757bf5384583aaabd2fed4551043391533
[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 GNU General Public License is not magic pixie dust</title>
11 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
13 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
14 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
15 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
16 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
17 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
18 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
19
20 &lt;blockquote&gt;
21
22 &lt;p&gt;&lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;&lt;img src=&quot;https://sfconservancy.org/img/supporter-badge.png&quot; width=&quot;194&quot; height=&quot;90&quot; alt=&quot;Become a Software Freedom Conservancy Supporter!&quot; align=&quot;right&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
23
24 &lt;blockquote&gt;
25 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
26
27 The first step is to choose a
28 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
29 code.&lt;br/&gt;
30
31 The next step is, when someone fails to follow that copyleft license,
32 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
33
34 and its a simple fact of our modern society that such type of
35 work&lt;br/&gt;
36
37 is incredibly expensive to do and incredibly difficult to do.
38 &lt;/blockquote&gt;
39
40 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
41 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
42 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
43 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
44
45 &lt;p&gt;As the Debian Website
46 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
47 &lt;a href=&quot;https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&amp;amp;r2=1.25&quot;&gt;to&lt;/a&gt;
48 imply, public domain and permissively licensed software can lead to
49 the production of more proprietary software as people discover useful
50 software, extend it and or incorporate it into their hardware or
51 software products. Copyleft licenses such as the GNU GPL were created
52 to close off this avenue to the production of proprietary software but
53 such licenses are not enough. With the ongoing adoption of Free
54 Software by individuals and groups, inevitably the community&#39;s
55 expectations of license compliance are violated, usually out of
56 ignorance of the way Free Software works, but not always. As Karen
57 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
58 Freedom&quot;&gt;FaiF&lt;/a&gt;
59 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
60 copyleft is nothing if no-one is willing and able to stand up in court
61 to protect it. The reality of today&#39;s world is that legal
62 representation is expensive, difficult and time consuming. With
63 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
64 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
65 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
66 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
67 of the Linux project, Debian and other groups against GPL violations.
68 In March the SFC supported a
69 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
70 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
71 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
72 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
73 kernel. Since then two of their sponsors pulled corporate funding and
74 conferences
75 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
76 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
77 less on corporate funding and more on the broad community of
78 individuals who support Free Software and copyleft. So the SFC has
79 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
80 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
81 a community of folks who stand up for copyleft and the GPL by
82 supporting their work on promoting and supporting copyleft and Free
83 Software.&lt;/p&gt;
84
85 &lt;p&gt;If you support Free Software,
86 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
87 what the SFC do, agree with their
88 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
89 principles&lt;/a&gt;, are happy about their
90 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
91 work on a project that is an SFC
92 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
93 just want to stand up for copyleft, please join
94 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
95 Allan Webber&lt;/a&gt;,
96 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
97 Smith&lt;/a&gt;,
98 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
99 Bacon&lt;/a&gt;, myself and
100 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
101 becoming a
102 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
103 next week your donation will be
104 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
105 by an anonymous donor. Please also consider asking your employer to
106 match your donation or become a sponsor of SFC. Don&#39;t forget to
107 spread the word about your support for SFC via email, your blog and or
108 social media accounts.&lt;/p&gt;
109
110 &lt;/blockquote&gt;
111
112 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
113 of Software Freedom Conservancy myself. Perhaps you should be a
114 supporter too?&lt;/p&gt;
115 </description>
116 </item>
117
118 <item>
119 <title>PGP key transition statement for key EE4E02F9</title>
120 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
121 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
122 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
123 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
124 set it up properly. I wanted to generate it offline and have it
125 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
126 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
127 time to sit down with an offline machine almost took forever. But
128 finally I&#39;ve been able to complete the process, and have now moved
129 from my old GPG key to a new GPG key. See
130 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
131 full transition statement, signed with both my old and new key&lt;/a&gt; for
132 the details. This is my new key:&lt;/p&gt;
133
134 &lt;pre&gt;
135 pub 3936R/&lt;a href=&quot;http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html&quot;&gt;111D6B29EE4E02F9&lt;/a&gt; 2015-11-03 [expires: 2019-11-14]
136 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
137 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
138 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
139 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
140 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
141 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
142 &lt;/pre&gt;
143
144 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
145 my old key.&lt;/p&gt;
146
147 &lt;p&gt;If you signed my old key
148 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
149 I&#39;d very much appreciate a signature on my new key, details and
150 instructions in the transition statement. I m happy to reciprocate if
151 you have a similarly signed transition statement to present.&lt;/p&gt;
152 </description>
153 </item>
154
155 <item>
156 <title>The life and death of a laptop battery</title>
157 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
159 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
160 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
161 But this do not last. The last few laptops gave me a feeling that
162 within a year, the life time is just a fraction of what it used to be,
163 and it slowly become painful to use the laptop without power connected
164 all the time. Because of this, when I got a new Thinkpad X230 laptop
165 about two years ago, I decided to monitor its battery state to have
166 more hard facts when the battery started to fail.&lt;/p&gt;
167
168 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
169
170 &lt;p&gt;First I tried to find a sensible Debian package to record the
171 battery status, assuming that this must be a problem already handled
172 by someone else. I found
173 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
174 which collects statistics from the battery, but it was completely
175 broken. I sent a few suggestions to the maintainer, but decided to
176 write my own collector as a shell script while I waited for feedback
177 from him. Via
178 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
179 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
180 discovered
181 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
182 available in Debian.&lt;/p&gt;
183
184 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
185 battery stats ever since. Now my
186 /var/log/hjemmenett-battery-status.log file contain around 115,000
187 measurements, from the time the battery was working great until now,
188 when it is unable to charge above 7% of original capacity. My
189 collector shell script is quite simple and look like this:&lt;/p&gt;
190
191 &lt;pre&gt;
192 #!/bin/sh
193 # Inspired by
194 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
195 # See also
196 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
197 logfile=/var/log/hjemmenett-battery-status.log
198
199 files=&quot;manufacturer model_name technology serial_number \
200 energy_full energy_full_design energy_now cycle_count status&quot;
201
202 if [ ! -e &quot;$logfile&quot; ] ; then
203 (
204 printf &quot;timestamp,&quot;
205 for f in $files; do
206 printf &quot;%s,&quot; $f
207 done
208 echo
209 ) &gt; &quot;$logfile&quot;
210 fi
211
212 log_battery() {
213 # Print complete message in one echo call, to avoid race condition
214 # when several log processes run in parallel.
215 msg=$(printf &quot;%s,&quot; $(date +%s); \
216 for f in $files; do \
217 printf &quot;%s,&quot; $(cat $f); \
218 done)
219 echo &quot;$msg&quot;
220 }
221
222 cd /sys/class/power_supply
223
224 for bat in BAT*; do
225 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
226 done
227 &lt;/pre&gt;
228
229 &lt;p&gt;The script is called when the power management system detect a
230 change in the power status (power plug in or out), and when going into
231 and out of hibernation and suspend. In addition, it collect a value
232 every 10 minutes. This make it possible for me know when the battery
233 is discharging, charging and how the maximum charge change over time.
234 The code for the Debian package
235 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
236 available on github&lt;/a&gt;.&lt;/p&gt;
237
238 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
239
240 &lt;pre&gt;
241 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
242 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
243 [...]
244 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
245 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
246 &lt;/pre&gt;
247
248 &lt;p&gt;I wrote a small script to create a graph of the charge development
249 over time. This graph depicted above show the slow death of my laptop
250 battery.&lt;/p&gt;
251
252 &lt;p&gt;But why is this happening? Why are my laptop batteries always
253 dying in a year or two, while the batteries of space probes and
254 satellites keep working year after year. If we are to believe
255 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
256 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
257 chance, and the fix is to not charge the Lithium-ion batteries to 100%
258 all the time, but to stay below 90% of full charge most of the time.
259 I&#39;ve been told that the Tesla electric cars
260 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
261 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
262 100% when preparing for a longer trip (not that I would want a car
263 like Tesla where rights to privacy is abandoned, but that is another
264 story), which I guess is the option we should have for laptops on
265 Linux too.&lt;/p&gt;
266
267 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
268 stop charging at 80%, unless requested to charge to 100% once in
269 preparation for a longer trip? I found
270 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
271 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
272 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
273 load).&lt;/p&gt;
274
275 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
276 at the start. I also wonder why the &quot;full capacity&quot; increases some
277 times, and if it is possible to repeat the process to get the battery
278 back to design capacity. And I wonder if the discharge and charge
279 speed change over time, or if this stay the same. I did not yet try
280 to write a tool to calculate the derivative values of the battery
281 level, but suspect some interesting insights might be learned from
282 those.&lt;/p&gt;
283
284 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
285 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
286 packages instead of the tp-smapi-dkms package I had tried to use
287 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
288 and stop. I&#39;ve done so now, but expect my existing battery is toast
289 and need to be replaced. The proposal is unfortunately Thinkpad
290 specific.&lt;/p&gt;
291 </description>
292 </item>
293
294 <item>
295 <title>New laptop - some more clues and ideas based on feedback</title>
296 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
297 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
298 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
299 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
300 need for a new laptop, and provided very useful feedback. I wish to
301 thank every one of these. Several pointed me to the possibility of
302 fixing my X230, and I am already in the process of getting Lenovo to
303 do so thanks to the on site, next day support contract covering the
304 machine. But the battery is almost useless (I expect to replace it
305 with a non-official battery) and I do not expect the machine to live
306 for many more years, so it is time to plan its replacement. If I did
307 not have a support contract, it was suggested to find replacement parts
308 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
309 might present a language barrier as I do not understand French.&lt;/p&gt;
310
311 &lt;p&gt;One tip I got was to use the
312 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
313 compare laptop models. It seem to have more models available than
314 prisjakt.no. Another tip I got from someone I know have similar
315 keyboard preferences was that the HP EliteBook 840 keyboard is not
316 very good, and this matches my experience with earlier EliteBook
317 keyboards I tested. Because of this, I will not consider it any further.
318
319 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
320 newest Thinkpad X model. The keyboard reintroduces mouse buttons
321 (which is missing from the X240), and is working fairly well with
322 Debian Sid/Unstable according to
323 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
324 got on the keyboard quality are not consistent. Some say the keyboard
325 is good, others say it is ok, while others say it is not very good.
326 Those with experience from X41 and and X60 agree that the X250
327 keyboard is not as good as those trusty old laptops, and suggest I
328 keep and fix my X230 instead of upgrading, or get a used X230 to
329 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
330 activity and battery status, which is very convenient on my X230. I&#39;m
331 also told that the CPU fan is running very often, making it a bit
332 noisy. In any case, the X250 do not work out of the box with Debian
333 Stable/Jessie, one of my requirements.&lt;/p&gt;
334
335 &lt;p&gt;I have also gotten a few vendor proposals, one was
336 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
337 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
338 The latter look very attractive to me.&lt;/p&gt;
339
340 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
341 as I keep looking for a replacement.&lt;/p&gt;
342
343 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
344 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
345 different
346 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
347 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
348 </description>
349 </item>
350
351 <item>
352 <title>Time to find a new laptop, as the old one is broken after only two years</title>
353 <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>
354 <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>
355 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
356 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
357 replacement soon. The left 5 cm of the screen on my Thinkpad X230
358 started flickering yesterday, and I suspect the cause is a broken
359 cable, as changing the angle of the screen some times get rid of the
360 flickering.&lt;/p&gt;
361
362 &lt;p&gt;My requirements have not really changed since I bought it, and is
363 still as
364 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
365 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
366 good help from
367 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
368 where I could select at least a few of the requirements (mouse pin,
369 wifi, weight) and go through the rest manually. Three button mouse
370 and a good keyboard is not available as an option, and all the three
371 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
372 G2) lack three mouse buttons). It is also unclear to me how good the
373 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
374 the keyboard, even if the quality and robustness in the X series have
375 deteriorated since X41.&lt;/p&gt;
376
377 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
378 seem sensible to me? Are there better services around to search the
379 set of available laptops for features? Please send me an email if you
380 have suggestions.&lt;/p&gt;
381
382 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
383 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
384 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
385 </description>
386 </item>
387
388 <item>
389 <title>How to stay with sysvinit in Debian Jessie</title>
390 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
391 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
392 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
393 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
394 sysvinit as its boot system by default. But how can one keep using
395 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
396 courtesy of
397 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
398 Schubert&lt;/a&gt; and
399 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
400 McVittie&lt;/a&gt;.
401
402 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
403 keep sysvinit as your boot system, create a file
404 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
405 you upgrade:&lt;/p&gt;
406
407 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
408 Package: systemd-sysv
409 Pin: release o=Debian
410 Pin-Priority: -1
411 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
412
413 &lt;p&gt;This file content will tell apt and aptitude to not consider
414 installing systemd-sysv as part of any installation and upgrade
415 solution when resolving dependencies, and thus tell it to avoid
416 systemd as a default boot system. The end result should be that the
417 upgraded system keep using sysvinit.&lt;/p&gt;
418
419 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
420 get sysvinit installed by default (debootstrap used by
421 debian-installer have no option for this), but one can tell the
422 installer to switch to sysvinit before the first boot. Either by
423 using a kernel argument to the installer, or by adding a line to the
424 preseed file used. First, the kernel command line argument:
425
426 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
427 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
428 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
429
430 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
431
432 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
433 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
434 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
435
436 &lt;p&gt;One can of course also do this after the first boot by installing
437 the sysvinit-core package.&lt;/p&gt;
438
439 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
440 sysvinit boot sequence in Debian have several hardware specific bugs
441 on Linux caused by the fact that it is unpredictable when hardware
442 devices show up during boot. But on the other hand, the new default
443 boot system still have a few rough edges I hope will be fixed before
444 Jessie is released.&lt;/p&gt;
445
446 &lt;p&gt;Update 2014-11-26: Inspired by
447 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
448 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
449 line.&lt;/p&gt;
450 </description>
451 </item>
452
453 <item>
454 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
455 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
456 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
457 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
458 <description>&lt;p&gt;The right to communicate with your friends and family in private,
459 without anyone snooping, is a right every citicen have in a liberal
460 democracy. But this right is under serious attack these days.&lt;/p&gt;
461
462 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
463 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
464 the whisleblower Snowden) more expensive for Internet email,
465 is to deliver all email using SMTP via Tor. Such SMTP option would be
466 a nice addition to the FreedomBox project if we could send email
467 between FreedomBox machines without leaking metadata about the emails
468 to the people peeking on the wire. I
469 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
470 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
471 lot of useful feedback and suggestions. It also became obvious to me
472 that this was not a novel idea, as the same idea was tested and
473 documented by Johannes Berg as early as 2006, and both
474 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
475 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
476 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
477
478 &lt;p&gt;To implement such system one need to set up a Tor hidden service
479 providing the SMTP protocol on port 25, and use email addresses
480 looking like username@hidden-service-name.onion. With such addresses
481 the connections to port 25 on hidden-service-name.onion using Tor will
482 go to the correct SMTP server. To do this, one need to configure the
483 Tor daemon to provide the hidden service and the mail server to accept
484 emails for this .onion domain. To learn more about Exim configuration
485 in Debian and test the design provided by Johannes Berg in his FAQ, I
486 set out yesterday to create a Debian package for making it trivial to
487 set up such SMTP over Tor service based on Debian. Getting it to work
488 were fairly easy, and
489 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
490 source code for the Debian package&lt;/a&gt; is available from github. I
491 plan to move it into Debian if further testing prove this to be a
492 useful approach.&lt;/p&gt;
493
494 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
495 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
496 get rid of exim4). Install tor, clone the git repository mentioned
497 above, build the deb and install it on the machine. Next, run
498 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
499 the instructions to get the service up and running. Restart tor and
500 exim when it is done, and test mail delivery using swaks like
501 this:&lt;/p&gt;
502
503 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
504 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
505 --to fbx@dutlqrrmjhtfa3vp.onion
506 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
507
508 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
509 address with your own address to test your server. :)&lt;/p&gt;
510
511 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
512 easier and more automatic. Especially the tor setup need more work.
513 Also, the package include a tor-smtp tool written in C, but its task
514 should probably be rewritten in some script language to make the deb
515 architecture independent. It would probably also make the code easier
516 to review. The tor-smtp tool currently need to listen on a socket for
517 exim to talk to it and is started using xinetd. It would be better if
518 no daemon and no socket is needed. I suspect it is possible to get
519 exim to run a command line tool for delivery instead of talking to a
520 socket, and hope to figure out how in a future version of this
521 system.&lt;/p&gt;
522
523 &lt;p&gt;Until I wipe my test machine, I can be reached using the
524 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
525 SMTorP. :)&lt;/p&gt;
526 </description>
527 </item>
528
529 <item>
530 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
531 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
533 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
534 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
535 alioth.debian.org, you know the web interface is fairly slow to
536 operate. First you visit one web page, enter the moderation password
537 and get a new page shown with a list of all the messages to moderate
538 and various options for each email address. This take a while for
539 every list you moderate, and you need to do it regularly to do a good
540 job as a list moderator. But there is a quick alternative,
541 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
542 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
543 to moderate in a fraction of a second. Here is a test run on two
544 lists I recently took over:&lt;/p&gt;
545
546 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
547 % time listadmin xiph
548 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
549 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
550
551 real 0m1.709s
552 user 0m0.232s
553 sys 0m0.012s
554 %
555 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
556
557 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
558 there are no message in the moderation queue. Every morning I
559 currently moderate 68 mailman lists, and it normally take around two
560 minutes. When I took over the two pkg-xiph lists above a few days
561 ago, there were 400 emails waiting in the moderator queue. It took me
562 less than 15 minutes to process them all using the listadmin
563 program.&lt;/p&gt;
564
565 &lt;p&gt;If you install
566 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
567 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
568 with content like this, the moderation task is a breeze:&lt;/p&gt;
569
570 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
571 username username@example.org
572 spamlevel 23
573 default discard
574 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
575
576 password secret
577 adminurl https://{domain}/mailman/admindb/{list}
578 mailman-list@lists.example.com
579
580 password hidden
581 other-list@otherserver.example.org
582 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
583
584 &lt;p&gt;There are other options to set as well. Check the manual page to
585 learn the details.&lt;/p&gt;
586
587 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
588 the SSL certificate is self signed or not properly signed by a
589 generally accepted signing authority, you can set a environment
590 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
591
592 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
593 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
594 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
595
596 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
597 can provide an argument to the listadmin script like I do in the
598 initial screen dump (the xiph argument). Using an argument, only
599 lists matching the argument string will be processed. This make it
600 quick to accept messages if you notice the moderation request in your
601 email.&lt;/p&gt;
602
603 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
604 mailing lists, as I simply do not have time to spend on that if the
605 process was any slower. The listadmin program have saved me hours of
606 time I could spend elsewhere over the years. It truly is nice free
607 software.&lt;/p&gt;
608
609 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
610 activities, please send Bitcoin donations to my address
611 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
612
613 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
614 configuration example. Also, I&#39;ve been told that the
615 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
616 sure why.&lt;/p&gt;
617 </description>
618 </item>
619
620 <item>
621 <title>Debian Jessie, PXE and automatic firmware installation</title>
622 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
624 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
625 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
626 problem that the WiFi card require some firmware to work properly.
627 And it has been a pain to fix this using preseeding in Debian.
628 Normally something more is needed. But thanks to
629 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
630 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
631 to do this using simple preseeding.&lt;/p&gt;
632
633 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
634 firmware for the hardware found in the machine (actually, requested by
635 the kernel modules for the hardware). (It can also install user space
636 programs supporting the hardware detected, but that is not the focus
637 of this story.)&lt;/p&gt;
638
639 &lt;p&gt;To get this working in the default installation, two preeseding
640 values are needed. First, the isenkram-cli package must be installed
641 into the target chroot (aka the hard drive) before tasksel is executed
642 in the pkgsel step of the debian-installer system. This is done by
643 preseeding the base-installer/includes debconf value to include the
644 isenkram-cli package. The package name is next passed to debootstrap
645 for installation. With the isenkram-cli package in place, tasksel
646 will automatically use the isenkram tasks to detect hardware specific
647 packages for the machine being installed and install them, because
648 isenkram-cli contain tasksel tasks.&lt;/p&gt;
649
650 &lt;p&gt;Second, one need to enable the non-free APT repository, because
651 most firmware unfortunately is non-free. This is done by preseeding
652 the apt-mirror-setup step. This is unfortunate, but for a lot of
653 hardware it is the only option in Debian.&lt;/p&gt;
654
655 &lt;p&gt;The end result is two lines needed in your preseeding file to get
656 firmware installed automatically by the installer:&lt;/p&gt;
657
658 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
659 base-installer base-installer/includes string isenkram-cli
660 apt-mirror-setup apt-setup/non-free boolean true
661 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
662
663 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
664 both firmware and user space packages when using this method. It also
665 do not work well, so use version 0.15 or later. Installing both
666 firmware and user space packages might give you a bit more than you
667 want, so I decided to split the tasksel task in two, one for firmware
668 and one for user space programs. The firmware task is enabled by
669 default, while the one for user space programs is not. This split is
670 implemented in the package currently in unstable.&lt;/p&gt;
671
672 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
673 this recipe work for you. :)&lt;/p&gt;
674
675 &lt;p&gt;So, I bet you are wondering, how can this work. First and
676 foremost, it work because tasksel is modular, and driven by whatever
677 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
678 isenkram-cli package place two files for tasksel to find. First there
679 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
680
681 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
682 Task: isenkram-packages
683 Section: hardware
684 Description: Hardware specific packages (autodetected by isenkram)
685 Based on the detected hardware various hardware specific packages are
686 proposed.
687 Test-new-install: show show
688 Relevance: 8
689 Packages: for-current-hardware
690
691 Task: isenkram-firmware
692 Section: hardware
693 Description: Hardware specific firmware packages (autodetected by isenkram)
694 Based on the detected hardware various hardware specific firmware
695 packages are proposed.
696 Test-new-install: mark show
697 Relevance: 8
698 Packages: for-current-hardware-firmware
699 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
700
701 &lt;p&gt;The key parts are Test-new-install which indicate how the task
702 should be handled and the Packages line referencing to a script in
703 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
704 list of packages to install. The for-current-hardware-firmware script
705 look like this to list relevant firmware for the machine:
706
707 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
708 #!/bin/sh
709 #
710 PATH=/usr/sbin:$PATH
711 export PATH
712 isenkram-autoinstall-firmware -l
713 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
714
715 &lt;p&gt;With those two pieces in place, the firmware is installed by
716 tasksel during the normal d-i run. :)&lt;/p&gt;
717
718 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
719 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
720 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
721 install.&lt;/p&gt;
722
723 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
724 pilots in testing this feature, as isenkram is used there now to
725 install firmware, replacing the earlier scripts.&lt;/p&gt;
726 </description>
727 </item>
728
729 <item>
730 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
731 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
732 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
733 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
734 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
735 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
736 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
737 on a screen normally showing the bread types and prizes:&lt;/p&gt;
738
739 &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;
740
741 &lt;p&gt;If it had booted as it was supposed to, I would never had known
742 about this hidden Linux installation. It is interesting what
743 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
744 </description>
745 </item>
746
747 <item>
748 <title>New lsdvd release version 0.17 is ready</title>
749 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
750 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
751 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
752 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
753 got a new set of developers a few weeks ago, after the original
754 developer decided to step down and pass the project to fresh blood.
755 This project is now maintained by Petter Reinholdtsen and Steve
756 Dibb.&lt;/p&gt;
757
758 &lt;p&gt;I just wrapped up
759 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
760 new lsdvd release&lt;/a&gt;, available in git or from
761 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
762 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
763 0.17.&lt;/p&gt;
764
765 &lt;ul&gt;
766
767 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
768 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
769 non-existant, to work around additional copy protection&lt;/li&gt;
770 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
771 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
772 &lt;li&gt;Fix include orders&lt;/li&gt;
773 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
774 &lt;li&gt;Fix the chapter count&lt;/li&gt;
775 &lt;li&gt;Make sure the array size and the array limit used when initialising
776 the palette size is the same.&lt;/li&gt;
777 &lt;li&gt;Fix array printing.&lt;/li&gt;
778 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
779 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
780 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
781 with more GCC compiler warnings.&lt;/li&gt;
782
783 &lt;/ul&gt;
784
785 &lt;p&gt;This change bring together patches for lsdvd in use in various
786 Linux and Unix distributions, as well as patches submitted to the
787 project the last nine years. Please check it out. :)&lt;/p&gt;
788 </description>
789 </item>
790
791 <item>
792 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
793 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
794 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
795 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
796 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
797 project&lt;/a&gt; provide a Linux solution for schools, including a
798 powerful desktop with education software, a central server providing
799 web pages, user database, user home directories, central login and PXE
800 boot of both clients without disk and the installation to install Debian
801 Edu on machines with disk (and a few other services perhaps to small
802 to mention here). We in the Debian Edu team are currently working on
803 the Jessie based version, trying to get everything in shape before the
804 freeze, to avoid having to maintain our own package repository in the
805 future. The
806 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
807 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
808 work left. Some fatal problems block testing, breaking the installer,
809 but it is possible to work around these to get anyway. Here is a
810 recipe on how to get the installation limping along.&lt;/p&gt;
811
812 &lt;p&gt;First, download the test ISO via
813 &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;,
814 &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;
815 or rsync (use
816 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
817 The ISO build was broken on Tuesday, so we do not get a new ISO every
818 12 hours or so, but thankfully the ISO we already got we are able to
819 install with some tweaking.&lt;/p&gt;
820
821 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
822 (use Alt-Ctrl-F2), run&lt;/p&gt;
823
824 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
825 nano /usr/bin/edu-eatmydata-install
826 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
827
828 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
829 optimization. Return to the installation, select the profile you want
830 and continue. Without this change, exim4-config will fail to install
831 due to a known bug in eatmydata.&lt;/p&gt;
832
833 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
834 this do not work, figure out what your correct value would be. All my
835 test machines need /dev/sda, so I have no advice if it do not fit
836 your need.&lt;/p&gt;
837
838 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
839 root after the initial boot from hard drive, and install the
840 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
841 or mate. If you want several desktop options, install more than one
842 metapackage. Once this is done, reboot and you should have a working
843 graphical login screen. This workaround should no longer be needed
844 once the education-tasks package version 1.801 enter testing in two
845 days.&lt;/p&gt;
846
847 &lt;p&gt;I believe the ISO build will start working on two days when the new
848 tasksel package enter testing and Steve McIntyre get a chance to
849 update the debian-cd git repository. The eatmydata, grub and desktop
850 issues are already fixed in unstable and testing, and should show up
851 on the ISO as soon as the ISO build start working again. Well the
852 eatmydata optimization is really just disabled. The proper fix
853 require an upload by the eatmydata maintainer applying the patch
854 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
855 The rest have proper fixes in unstable.&lt;/p&gt;
856
857 &lt;p&gt;I hope this get you going with the installation testing, as we are
858 quickly running out of time trying to get our Jessie based
859 installation ready before the distribution freeze in a month.&lt;/p&gt;
860 </description>
861 </item>
862
863 <item>
864 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
865 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
866 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
867 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
868 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
869 to handle my fairly large DVD collection. It is a nice command line
870 tool to get details about a DVD, like title, tracks, track length,
871 etc, in XML, Perl or human readable format. But lsdvd have not seen
872 any new development since 2006 and had a few irritating bugs affecting
873 its use with some DVDs. Upstream seemed to be dead, and in January I
874 sent a small probe asking for a version control repository for the
875 project, without any reply. But I use it regularly and would like to
876 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
877 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
878 the project admin, and after getting a reply from him explaining that
879 he was no longer interested in the project, I asked if I could take
880 over. And yesterday, I became project admin.&lt;/p&gt;
881
882 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
883 maintainer interested in joining forces to maintain the upstream
884 project, and I hope we can get a new release out fairly quickly,
885 collecting the patches spread around on the internet into on place.
886 I&#39;ve added the relevant Debian patches to the freshly created git
887 repository, and expect the Gentoo patches to make it too. If you got
888 a DVD collection and care about command line tools, check out
889 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
890 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
891 list&lt;/a&gt;. :)&lt;/p&gt;
892 </description>
893 </item>
894
895 <item>
896 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
897 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
898 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
899 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
900 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
901 a lot quicker. When we install more than 2000 packages in
902 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
903 tasksel in the installer, unpacking the binary packages take forever.
904 A part of the slow I/O issue was discussed in
905 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
906 much file system sync-ing done by dpkg, which is the package
907 responsible for unpacking the binary packages. Other parts (like code
908 executed by postinst scripts) might also sync to disk during
909 installation. All this sync-ing to disk do not really make sense to
910 me. If the machine crash half-way through, I start over, I do not try
911 to salvage the half installed system. So the failure sync-ing is
912 supposed to protect against, hardware or system crash, is not really
913 relevant while the installer is running.&lt;/p&gt;
914
915 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
916 system sync()-ing in a fairly non-intrusive way, without the need to
917 change the code in several packages. The idea is not new, but I have
918 not heard anyone propose the approach using dpkg-divert before. It
919 depend on the small and clever package
920 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
921 uses LD_PRELOAD to replace the system functions for syncing data to
922 disk with functions doing nothing, thus allowing programs to live
923 dangerous while speeding up disk I/O significantly. Instead of
924 modifying the implementation of dpkg, apt and tasksel (which are the
925 packages responsible for selecting, fetching and installing packages),
926 it occurred to me that we could just divert the programs away, replace
927 them with a simple shell wrapper calling
928 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
929 Two days ago I decided to test the idea, and wrapped up a simple
930 implementation for the Debian Edu udeb.&lt;/p&gt;
931
932 &lt;p&gt;The effect was stunning. In my first test it reduced the running
933 time of the pkgsel step (installing tasks) from 64 to less than 44
934 minutes (20 minutes shaved off the installation) on an old Dell
935 Latitude D505 machine. I am not quite sure what the optimised time
936 would have been, as I messed up the testing a bit, causing the debconf
937 priority to get low enough for two questions to pop up during
938 installation. As soon as I saw the questions I moved the installation
939 along, but do not know how long the question were holding up the
940 installation. I did some more measurements using Debian Edu Jessie,
941 and got these results. The time measured is the time stamp in
942 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
943 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
944 yourself. In Debian Edu, the tasksel dialog do not show up, and the
945 timing thus do not depend on how quickly the user handle the tasksel
946 dialog.&lt;/p&gt;
947
948 &lt;p&gt;&lt;table&gt;
949
950 &lt;tr&gt;
951 &lt;th&gt;Machine/setup&lt;/th&gt;
952 &lt;th&gt;Original tasksel&lt;/th&gt;
953 &lt;th&gt;Optimised tasksel&lt;/th&gt;
954 &lt;th&gt;Reduction&lt;/th&gt;
955 &lt;/tr&gt;
956
957 &lt;tr&gt;
958 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
959 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
960 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
961 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
962 &lt;/tr&gt;
963
964 &lt;tr&gt;
965 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
966 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
967 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
968 &lt;td&gt;23 min 40%&lt;/td&gt;
969 &lt;/tr&gt;
970
971 &lt;tr&gt;
972 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
973 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
974 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
975 &lt;td&gt;11 min 50%&lt;/td&gt;
976 &lt;/tr&gt;
977
978 &lt;tr&gt;
979 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
980 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
981 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
982 &lt;td&gt;2 min 33%&lt;/td&gt;
983 &lt;/tr&gt;
984
985 &lt;tr&gt;
986 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
987 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
988 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
989 &lt;td&gt;4 min 21%&lt;/td&gt;
990 &lt;/tr&gt;
991
992 &lt;/table&gt;&lt;/p&gt;
993
994 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
995 time is spent downloading packages. The connection to the Internet
996 was 100Mbit/s during testing, so downloading should not be a
997 significant factor in the measurement. Download typically took a few
998 seconds to a few minutes, depending on the amount of packages being
999 installed.&lt;/p&gt;
1000
1001 &lt;p&gt;The speedup is implemented by using two hooks in
1002 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1003 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1004 finish-install.d hook to remove the divert at the end of the
1005 installation. I picked the pre-pkgsel.d hook instead of the
1006 post-base-installer.d hook because I test using an ISO without the
1007 eatmydata package included, and the post-base-installer.d hook in
1008 Debian Edu can only operate on packages included in the ISO. The
1009 negative effect of this is that I am unable to activate this
1010 optimization for the kernel installation step in d-i. If the code is
1011 moved to the post-base-installer.d hook, the speedup would be larger
1012 for the entire installation.&lt;/p&gt;
1013
1014 &lt;p&gt;I&#39;ve implemented this in the
1015 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1016 git repository, and plan to provide the optimization as part of the
1017 Debian Edu installation. If you want to test this yourself, you can
1018 create two files in the installer (or in an udeb). One shell script
1019 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1020
1021 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1022 #!/bin/sh
1023 set -e
1024 . /usr/share/debconf/confmodule
1025 info() {
1026 logger -t my-pkgsel &quot;info: $*&quot;
1027 }
1028 error() {
1029 logger -t my-pkgsel &quot;error: $*&quot;
1030 }
1031 override_install() {
1032 apt-install eatmydata || true
1033 if [ -x /target/usr/bin/eatmydata ] ; then
1034 for bin in dpkg apt-get aptitude tasksel ; do
1035 file=/usr/bin/$bin
1036 # Test that the file exist and have not been diverted already.
1037 if [ -f /target$file ] ; then
1038 info &quot;diverting $file using eatmydata&quot;
1039 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1040 &gt; /target$file.edu
1041 chmod 755 /target$file.edu
1042 in-target dpkg-divert --package debian-edu-config \
1043 --rename --quiet --add $file
1044 ln -sf ./$bin.edu /target$file
1045 else
1046 error &quot;unable to divert $file, as it is missing.&quot;
1047 fi
1048 done
1049 else
1050 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1051 fi
1052 }
1053
1054 override_install
1055 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1056
1057 &lt;p&gt;To clean up, another shell script should go into
1058 /usr/lib/finish-install.d/ with code like this:
1059
1060 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1061 #! /bin/sh -e
1062 . /usr/share/debconf/confmodule
1063 error() {
1064 logger -t my-finish-install &quot;error: $@&quot;
1065 }
1066 remove_install_override() {
1067 for bin in dpkg apt-get aptitude tasksel ; do
1068 file=/usr/bin/$bin
1069 if [ -x /target$file.edu ] ; then
1070 rm /target$file
1071 in-target dpkg-divert --package debian-edu-config \
1072 --rename --quiet --remove $file
1073 rm /target$file.edu
1074 else
1075 error &quot;Missing divert for $file.&quot;
1076 fi
1077 done
1078 sync # Flush file buffers before continuing
1079 }
1080
1081 remove_install_override
1082 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1083
1084 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1085 edu-eatmydata-install and call it from the pre-pkgsel.d and
1086 finish-install.d scripts.&lt;/p&gt;
1087
1088 &lt;p&gt;By now you might ask if this change should get into the normal
1089 Debian installer too? I suspect it should, but am not sure the
1090 current debian-installer coordinators find it useful enough. It also
1091 depend on the side effects of the change. I&#39;m not aware of any, but I
1092 guess we will see if the change is safe after some more testing.
1093 Perhaps there is some package in Debian depending on sync() and
1094 fsync() having effect? Perhaps it should go into its own udeb, to
1095 allow those of us wanting to enable it to do so without affecting
1096 everyone.&lt;/p&gt;
1097
1098 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1099 will break installation of all programs using gnutls because of
1100 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1101 eatmydata package in Debian will solve it.&lt;/p&gt;
1102
1103 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1104 the optimization work again. And I have discovered that the
1105 dpkg-divert trick is not really needed and implemented a slightly
1106 simpler approach as part of the debian-edu-install package. See
1107 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1108
1109 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1110 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1111 triggering on i386 made it into testing, and broke this installation
1112 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1113 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1114 </description>
1115 </item>
1116
1117 <item>
1118 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1119 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1120 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1121 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1122 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1123 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1124 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1125 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1126 learn that there is a large set of publicly available key servers to
1127 use when looking for peoples public key. So far I have used
1128 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1129 were misbehaving, but those days are ended. The servers I have used
1130 up until yesterday have been slow and some times unavailable. I hope
1131 those problems are gone now.&lt;/p&gt;
1132
1133 &lt;p&gt;Behind the round robin DNS entry of the
1134 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1135 there is a pool of more than 100 keyservers which are checked every
1136 day to ensure they are well connected and up to date. It must be
1137 better than what I have used so far. :)&lt;/p&gt;
1138
1139 &lt;p&gt;Yesterdays speaker told me that the service is the default
1140 keyserver provided by the default configuration in GnuPG, but this do
1141 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1142
1143 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1144 line:&lt;/p&gt;
1145
1146 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1147 keyserver pool.sks-keyservers.net
1148 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1149
1150 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1151 entries in DNS. Just for fun, I did just that at work, so now every
1152 user of GnuPG at the University of Oslo should find a OpenGPG
1153 keyserver automatically should their need it:&lt;/p&gt;
1154
1155 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1156 % host -t srv _pgpkey-http._tcp.uio.no
1157 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1158 %
1159 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1160
1161 &lt;p&gt;Now if only
1162 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1163 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1164 very happy. It can look up a given key or search for a user ID, but I
1165 normally do not want that, but to find a trust path from my key to
1166 another key. Given a user ID or key ID, I would like to find (and
1167 download) the keys representing a signature path from my key to the
1168 key in question, to be able to get a trust path between the two keys.
1169 This is as far as I can tell not possible today. Perhaps something
1170 for a future version of the protocol?&lt;/p&gt;
1171 </description>
1172 </item>
1173
1174 <item>
1175 <title>From English wiki to translated PDF and epub via Docbook</title>
1176 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1177 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1178 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1179 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1180 project&lt;/a&gt; provide an instruction manual for teachers, system
1181 administrators and other users that contain useful tips for setting up
1182 and maintaining a Debian Edu installation. This text is about how the
1183 text processing of this manual is handled in the project.&lt;/p&gt;
1184
1185 &lt;p&gt;One goal of the project is to provide information in the native
1186 language of its users, and for this we need to handle translations.
1187 But we also want to make sure each language contain the same
1188 information, so for this we need a good way to keep the translations
1189 in sync. And we want it to be easy for our users to improve the
1190 documentation, avoiding the need to learn special formats or tools to
1191 contribute, and the obvious way to do this is to make it possible to
1192 edit the documentation using a web browser. We also want it to be
1193 easy for translators to keep the translation up to date, and give them
1194 help in figuring out what need to be translated. Here is the list of
1195 tools and the process we have found trying to reach all these
1196 goals.&lt;/p&gt;
1197
1198 &lt;p&gt;We maintain the authoritative source of our manual in the
1199 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1200 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1201 front page with references to the different chapters, several pages
1202 for each chapter, and finally one &quot;collection page&quot; gluing all the
1203 chapters together into one large web page (aka
1204 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1205 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1206 processing and translations. Thanks to the fact that the
1207 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1208 wiki.debian.org support exporting pages in
1209 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1210 the list of pages to export using the raw version of the AllInOne
1211 page, loop over each of them to generate a Docbook XML version of the
1212 manual. This process also download images and transform image
1213 references to use the locally downloaded images. The generated
1214 Docbook XML files are slightly broken, so some post-processing is done
1215 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1216 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1217 a handfull of images. The XML file can now be used to generate PDF, HTML
1218 and epub versions of the English manual. This is the basic step of
1219 our process, making PDF (using dblatex), HTML (using xsltproc) and
1220 epub (using dbtoepub) version from Docbook XML, and the resulting files
1221 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1222
1223 &lt;p&gt;But English documentation is not enough for us. We want translated
1224 documentation too, and we want to make it easy for translators to
1225 track the English original. For this we use the
1226 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1227 which allow us to transform the English Docbook XML file into a
1228 translation file (a .pot file), usable with the normal gettext based
1229 translation tools used by those translating free software. The pot
1230 file is used to create and maintain translation files (several .po
1231 files), which the translations update with the native language
1232 translations of all titles, paragraphs and blocks of text in the
1233 original. The next step is combining the original English Docbook XML
1234 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1235 create a translated Docbook XML file (in this case
1236 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1237 translated, if the translation is not complete) Docbook XML file can
1238 then be used like the original to create a PDF, HTML and epub version
1239 of the documentation.&lt;/p&gt;
1240
1241 &lt;p&gt;The translators use different tools to edit the .po files. We
1242 recommend using
1243 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1244 while some use emacs and vi, others can use web based editors like
1245 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1246 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1247 is where the .po file end up, in our git repository. Updated
1248 translations can either be committed directly to git, or submitted as
1249 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1250 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1251
1252 &lt;p&gt;One challenge is images, which both might need to be translated (if
1253 they show translated user applications), and are needed in different
1254 formats when creating PDF and HTML versions (epub is a HTML version in
1255 this regard). For this we transform the original PNG images to the
1256 needed density and format during build, and have a way to provide
1257 translated images by storing translated versions in
1258 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1259 package maintainers know more.&lt;/p&gt;
1260
1261 &lt;p&gt;If you wonder what the result look like, we provide
1262 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1263 of the documentation packages on the web&lt;/a&gt;. See for example the
1264 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1265 PDF version&lt;/a&gt; or the
1266 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1267 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1268 but perhaps it will be done in the future.&lt;/p&gt;
1269
1270 &lt;p&gt;To learn more, check out
1271 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1272 debian-edu-doc package&lt;/a&gt;,
1273 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1274 manual on the wiki&lt;/a&gt; and
1275 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1276 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1277 </description>
1278 </item>
1279
1280 <item>
1281 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1282 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1283 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1284 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1285 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1286 related packages relevant for the computer installed automatically.
1287 So I implemented one, using
1288 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1289 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1290 run tasksel as user root. You should be presented with a new option,
1291 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1292 select it, tasksel will install the packages isenkram claim is fit for
1293 the current hardware, hot pluggable or not.&lt;p&gt;
1294
1295 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1296 description, and the other is the script used to extract the list of
1297 packages to install. The first part is in
1298 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1299 this:&lt;/p&gt;
1300
1301 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1302 Task: isenkram
1303 Section: hardware
1304 Description: Hardware specific packages (autodetected by isenkram)
1305 Based on the detected hardware various hardware specific packages are
1306 proposed.
1307 Test-new-install: mark show
1308 Relevance: 8
1309 Packages: for-current-hardware
1310 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1311
1312 &lt;p&gt;The second part is in
1313 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1314 this:&lt;/p&gt;
1315
1316 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1317 #!/bin/sh
1318 #
1319 (
1320 isenkram-lookup
1321 isenkram-autoinstall-firmware -l
1322 ) | sort -u
1323 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1324
1325 &lt;p&gt;All in all, a very short and simple implementation making it
1326 trivial to install the hardware dependent package we all may want to
1327 have installed on our machines. I&#39;ve not been able to find a way to
1328 get tasksel to tell you exactly which packages it plan to install
1329 before doing the installation. So if you are curious or careful,
1330 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1331
1332 &lt;p&gt;The information about which packages are handling which hardware is
1333 fetched either from the isenkram package itself in
1334 /usr/share/isenkram/, from git.debian.org or from the APT package
1335 database (using the Modaliases header). The APT package database
1336 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1337 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1338 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1339 the python-apt code (bug
1340 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1341 workaround I was able to get rid of the file descriptor leak and
1342 reduce the memory leak from ~30 MiB per hardware detection down to
1343 around 2 MiB per hardware detection. It should make the desktop
1344 daemon a lot more useful. The fix is in version 0.7 uploaded to
1345 unstable today.&lt;/p&gt;
1346
1347 &lt;p&gt;I believe the current way of mapping hardware to packages in
1348 Isenkram is is a good draft, but in the future I expect isenkram to
1349 use the AppStream data source for this. A proposal for getting proper
1350 AppStream support into Debian is floating around as
1351 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1352 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1353 project&lt;/a&gt; will take place this summer to improve the situation. I
1354 look forward to seeing the result, and welcome patches for isenkram to
1355 start using the information when it is ready.&lt;/p&gt;
1356
1357 &lt;p&gt;If you want your package to map to some specific hardware, either
1358 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1359 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1360 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1361 package. See also
1362 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1363 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1364 the information will be migrated to AppStream eventually, but for the
1365 moment I got no better place to store it.&lt;/p&gt;
1366 </description>
1367 </item>
1368
1369 <item>
1370 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1371 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1373 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1374 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1375 project&lt;/a&gt; is working on providing the software and hardware to make
1376 it easy for non-technical people to host their data and communication
1377 at home, and being able to communicate with their friends and family
1378 encrypted and away from prying eyes. It is still going strong, and
1379 today a major mile stone was reached.&lt;/p&gt;
1380
1381 &lt;p&gt;Today, the last of the packages currently used by the project to
1382 created the system images were accepted into Debian Unstable. It was
1383 the freedombox-setup package, which is used to configure the images
1384 during build and on the first boot. Now all one need to get going is
1385 the build code from the freedom-maker git repository and packages from
1386 Debian. And once the freedombox-setup package enter testing, we can
1387 build everything directly from Debian. :)&lt;/p&gt;
1388
1389 &lt;p&gt;Some key packages used by Freedombox are
1390 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1391 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1392 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1393 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1394 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1395 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1396 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1397 are plans to integrate more packages into the setup. User
1398 documentation is maintained on the Debian wiki. Please
1399 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1400 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1401
1402 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1403 setup, run this on a Debian machine using a user with sudo rights to
1404 become root:&lt;/p&gt;
1405
1406 &lt;p&gt;&lt;pre&gt;
1407 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1408 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1409 u-boot-tools
1410 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1411 freedom-maker
1412 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1413 &lt;/pre&gt;&lt;/p&gt;
1414
1415 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1416 devices. See the README in the freedom-maker git repo for more
1417 details on the build. If you do not want all three images, trim the
1418 make line. Note that the virtualbox-image target is not really
1419 virtualbox specific. It create a x86 image usable in kvm, qemu,
1420 vmware and any other x86 virtual machine environment. You might need
1421 the version of vmdebootstrap in Jessie to get the build working, as it
1422 include fixes for a race condition with kpartx.&lt;/p&gt;
1423
1424 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1425 method, boot a Debian Wheezy ISO and use this boot argument to load
1426 the preseed values:&lt;/p&gt;
1427
1428 &lt;p&gt;&lt;pre&gt;
1429 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;
1430 &lt;/pre&gt;&lt;/p&gt;
1431
1432 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1433 it still work.&lt;/p&gt;
1434
1435 &lt;p&gt;If you wonder how to help, one task you could look at is using
1436 systemd as the boot system. It will become the default for Linux in
1437 Jessie, so we need to make sure it is usable on the Freedombox. I did
1438 a simple test a few weeks ago, and noticed dnsmasq failed to start
1439 during boot when using systemd. I suspect there are other problems
1440 too. :) To detect problems, there is a test suite included, which can
1441 be run from the plinth web interface.&lt;/p&gt;
1442
1443 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1444 us get the new release published. :) Please join us on
1445 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1446 irc.debian.org)&lt;/a&gt; and
1447 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1448 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1449 </description>
1450 </item>
1451
1452 <item>
1453 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1454 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1456 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1457 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1458 solution for use at home. My requirements are simple, it must be
1459 cheap and locally encrypted (in other words, I keep the encryption
1460 keys, the storage provider do not have access to my private files).
1461 One idea me and my friends had many years ago, before the cloud
1462 storage providers showed up, was to use Google mail as storage,
1463 writing a Linux block device storing blocks as emails in the mail
1464 service provided by Google, and thus get heaps of free space. On top
1465 of this one can add encryption, RAID and volume management to have
1466 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1467 I never found time to implement such system. But the last few weeks I
1468 have looked at a system called
1469 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1470 mounted network backed file system with the features I need.&lt;/p&gt;
1471
1472 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1473 handling several different storage providers, any with Amazon S3,
1474 Google Drive or OpenStack API. There are heaps of such storage
1475 providers. S3QL can also use a local directory as storage, which
1476 combined with sshfs allow for file storage on any ssh server. S3QL
1477 include support for encryption, compression, de-duplication, snapshots
1478 and immutable file systems, allowing me to mount the remote storage as
1479 a local mount point, look at and use the files as if they were local,
1480 while the content is stored in the cloud as well. This allow me to
1481 have a backup that should survive fire. The file system can not be
1482 shared between several machines at the same time, as only one can
1483 mount it at the time, but any machine with the encryption key and
1484 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1485
1486 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1487 package is included already. So to get started, run &lt;tt&gt;apt-get
1488 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1489 Greenqloud, after reading their nice recipe on
1490 &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
1491 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1492 in Iceland more than those in USA when it come to keeping my personal
1493 data safe and private, and thus would rather spend money on a company
1494 in Iceland. Another nice recipe is available from the article
1495 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1496 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1497 Admin magazine. When the provider is picked, figure out how to get
1498 the API key needed to connect to the storage API. With Greencloud,
1499 the key did not show up until I had added payment details to my
1500 account.&lt;/p&gt;
1501
1502 &lt;p&gt;Armed with the API access details, it is time to create the file
1503 system. First, create a new bucket in the cloud. This bucket is the
1504 file system storage area. I picked a bucket name reflecting the
1505 machine that was going to store data there, but any name will do.
1506 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1507 the API login and password, and a locally created password. Store it
1508 all in ~root/.s3ql/authinfo2 like this:
1509
1510 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1511 [s3c]
1512 storage-url: s3c://s.greenqloud.com:443/bucket-name
1513 backend-login: API-login
1514 backend-password: API-password
1515 fs-passphrase: local-password
1516 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1517
1518 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1519 but any sensible way to create a fairly random password should do it.
1520 Armed with these details, it is now time to run mkfs, entering the API
1521 details and password to create it:&lt;/p&gt;
1522
1523 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1524 # mkdir -m 700 /var/lib/s3ql-cache
1525 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1526 --ssl s3c://s.greenqloud.com:443/bucket-name
1527 Enter backend login:
1528 Enter backend password:
1529 Before using S3QL, make sure to read the user&#39;s guide, especially
1530 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1531 Enter encryption password:
1532 Confirm encryption password:
1533 Generating random encryption key...
1534 Creating metadata tables...
1535 Dumping metadata...
1536 ..objects..
1537 ..blocks..
1538 ..inodes..
1539 ..inode_blocks..
1540 ..symlink_targets..
1541 ..names..
1542 ..contents..
1543 ..ext_attributes..
1544 Compressing and uploading metadata...
1545 Wrote 0.00 MB of compressed metadata.
1546 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1547
1548 &lt;p&gt;The next step is mounting the file system to make the storage available.
1549
1550 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1551 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1552 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1553 Using 4 upload threads.
1554 Downloading and decompressing metadata...
1555 Reading metadata...
1556 ..objects..
1557 ..blocks..
1558 ..inodes..
1559 ..inode_blocks..
1560 ..symlink_targets..
1561 ..names..
1562 ..contents..
1563 ..ext_attributes..
1564 Mounting filesystem...
1565 # df -h /s3ql
1566 Filesystem Size Used Avail Use% Mounted on
1567 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1568 #
1569 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1570
1571 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1572 backups in it, and as the metadata used by rsync is downloaded at
1573 mount time, no network traffic (and storage cost) is triggered by
1574 running rsync. To unmount, one should not use the normal umount
1575 command, as this will not flush the cache to the cloud storage, but
1576 instead running the umount.s3ql command like this:
1577
1578 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1579 # umount.s3ql /s3ql
1580 #
1581 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1582
1583 &lt;p&gt;There is a fsck command available to check the file system and
1584 correct any problems detected. This can be used if the local server
1585 crashes while the file system is mounted, to reset the &quot;already
1586 mounted&quot; flag. This is what it look like when processing a working
1587 file system:&lt;/p&gt;
1588
1589 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1590 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1591 Using cached metadata.
1592 File system seems clean, checking anyway.
1593 Checking DB integrity...
1594 Creating temporary extra indices...
1595 Checking lost+found...
1596 Checking cached objects...
1597 Checking names (refcounts)...
1598 Checking contents (names)...
1599 Checking contents (inodes)...
1600 Checking contents (parent inodes)...
1601 Checking objects (reference counts)...
1602 Checking objects (backend)...
1603 ..processed 5000 objects so far..
1604 ..processed 10000 objects so far..
1605 ..processed 15000 objects so far..
1606 Checking objects (sizes)...
1607 Checking blocks (referenced objects)...
1608 Checking blocks (refcounts)...
1609 Checking inode-block mapping (blocks)...
1610 Checking inode-block mapping (inodes)...
1611 Checking inodes (refcounts)...
1612 Checking inodes (sizes)...
1613 Checking extended attributes (names)...
1614 Checking extended attributes (inodes)...
1615 Checking symlinks (inodes)...
1616 Checking directory reachability...
1617 Checking unix conventions...
1618 Checking referential integrity...
1619 Dropping temporary indices...
1620 Backing up old metadata...
1621 Dumping metadata...
1622 ..objects..
1623 ..blocks..
1624 ..inodes..
1625 ..inode_blocks..
1626 ..symlink_targets..
1627 ..names..
1628 ..contents..
1629 ..ext_attributes..
1630 Compressing and uploading metadata...
1631 Wrote 0.89 MB of compressed metadata.
1632 #
1633 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1634
1635 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1636 quick, about the same speed as local file access. Uploading large
1637 amount of data is to me limited by the bandwidth out of and into my
1638 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1639 which is very close to my upload speed, and downloading the same
1640 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1641 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1642 network, not the file system code. I do not know what a good cache
1643 size would be, but suspect that the cache should e larger than your
1644 working set.&lt;/p&gt;
1645
1646 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1647 time. If another machine try, it is told that the file system is
1648 busy:&lt;/p&gt;
1649
1650 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1651 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1652 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1653 Using 8 upload threads.
1654 Backend reports that fs is still mounted elsewhere, aborting.
1655 #
1656 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1657
1658 &lt;p&gt;The file content is uploaded when the cache is full, while the
1659 metadata is uploaded once every 24 hour by default. To ensure the
1660 file system content is flushed to the cloud, one can either umount the
1661 file system, or ask S3QL to flush the cache and metadata using
1662 s3qlctrl:
1663
1664 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1665 # s3qlctrl upload-meta /s3ql
1666 # s3qlctrl flushcache /s3ql
1667 #
1668 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1669
1670 &lt;p&gt;If you are curious about how much space your data uses in the
1671 cloud, and how much compression and deduplication cut down on the
1672 storage usage, you can use s3qlstat on the mounted file system to get
1673 a report:&lt;/p&gt;
1674
1675 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1676 # s3qlstat /s3ql
1677 Directory entries: 9141
1678 Inodes: 9143
1679 Data blocks: 8851
1680 Total data size: 22049.38 MB
1681 After de-duplication: 21955.46 MB (99.57% of total)
1682 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1683 Database size: 2.39 MB (uncompressed)
1684 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1685 #
1686 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1687
1688 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1689 storage. I did not try to locate them all, but am aware of at least
1690 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1691 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1692 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1693 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1694 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1695 accept payment in Bitcoin. Pick one that suit your need. Some of
1696 them provide several GiB of free storage, but the prize models are
1697 quite different and you will have to figure out what suits you
1698 best.&lt;/p&gt;
1699
1700 &lt;p&gt;While researching this blog post, I had a look at research papers
1701 and posters discussing the S3QL file system. There are several, which
1702 told me that the file system is getting a critical check by the
1703 science community and increased my confidence in using it. One nice
1704 poster is titled
1705 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1706 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1707 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1708 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1709 and Pamela Smith. Please have a look.&lt;/p&gt;
1710
1711 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1712 check out the mounted S3QL file system to see if it would be usable as
1713 a home directory (in other word, that it provided POSIX semantics when
1714 it come to locking and umask handling etc). Running
1715 &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
1716 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1717 no error was found. So the file system can be used for home
1718 directories, if one chooses to do so.&lt;/p&gt;
1719
1720 &lt;p&gt;If you do not want a locally file system, and want something that
1721 work without the Linux fuse file system, I would like to mention the
1722 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1723 provide locally encrypted backup using a command line client. It have
1724 a nicer access control system, where one can split out read and write
1725 access, allowing some systems to write to the backup and others to
1726 only read from it.&lt;/p&gt;
1727
1728 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1729 activities, please send Bitcoin donations to my address
1730 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1731 </description>
1732 </item>
1733
1734 <item>
1735 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1736 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1737 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1738 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1739 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1740 project&lt;/a&gt; is working on providing the software and hardware for
1741 making it easy for non-technical people to host their data and
1742 communication at home, and being able to communicate with their
1743 friends and family encrypted and away from prying eyes. It has been
1744 going on for a while, and is slowly progressing towards a new test
1745 release (0.2).&lt;/p&gt;
1746
1747 &lt;p&gt;And what day could be better than the Pi day to announce that the
1748 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1749 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1750 system), and can also be installed using a Debian installer preseed
1751 file. The Debian based Freedombox is now based on Debian Jessie,
1752 where most of the needed packages used are already present. Only one,
1753 the freedombox-setup package, is missing. To try to build your own
1754 boot image to test the current status, fetch the freedom-maker scripts
1755 and build using
1756 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1757 with a user with sudo access to become root:
1758
1759 &lt;pre&gt;
1760 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1761 freedom-maker
1762 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1763 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1764 u-boot-tools
1765 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1766 &lt;/pre&gt;
1767
1768 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1769 devices. See the README for more details on the build. If you do not
1770 want all three images, trim the make line. But note that thanks to &lt;a
1771 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1772 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1773 kpartx call.&lt;/p&gt;
1774
1775 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1776 method, boot a Debian Wheezy ISO and use this boot argument to load
1777 the preseed values:&lt;/p&gt;
1778
1779 &lt;pre&gt;
1780 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;
1781 &lt;/pre&gt;
1782
1783 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1784 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1785 currently hang while setting up APT sources. Killing the
1786 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1787 installation will get the installation going. This affect all
1788 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1789
1790 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1791 us get the new release published. :) Please join us on
1792 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1793 irc.debian.org)&lt;/a&gt; and
1794 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1795 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1796 </description>
1797 </item>
1798
1799 <item>
1800 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1801 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1802 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1803 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1804 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1805 innetgr tools, because I needed them in
1806 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1807 ng-utils, and it has served me well. I placed the project under the
1808 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1809 repository. But many years ago, the CVS repository was dropped (lost,
1810 not migrated to new hardware, not sure), and the project have lacked a
1811 proper home since then.&lt;/p&gt;
1812
1813 &lt;p&gt;Last summer, I had a look at the package and made a new release
1814 fixing a irritating crash bug, but was unable to store the changes in
1815 a proper source control system. I applied for a project on
1816 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1817 to follow up on it. Until today. :)&lt;/p&gt;
1818
1819 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1820 now have a new home, and a git repository with the highlight of the
1821 history of the project. I published all release tarballs and imported
1822 them into the git repository. As the project is really stable and not
1823 expected to gain new features any time soon, I decided to make a new
1824 release and call it 1.0. Visit the new project home on
1825 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1826 if you want to check it out. The new version is also uploaded into
1827 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1828 </description>
1829 </item>
1830
1831 <item>
1832 <title>Testing sysvinit from experimental in Debian Hurd</title>
1833 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1834 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1835 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1836 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1837 their changes into sysvinit, to allow them to use the normal sysvinit
1838 boot system instead of their old one. This follow up on the
1839 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1840 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1841 get Debian on Hurd working more like Debian on Linux. To get started,
1842 I downloaded a prebuilt hard disk image from
1843 &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;,
1844 and started it using virt-manager.&lt;/p&gt;
1845
1846 &lt;p&gt;The first think I had to do after logging in (root without any
1847 password) was to get the network operational. I followed
1848 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1849 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1850 commands as root to get the machine to accept a IP address from the
1851 kvm internal DHCP server:&lt;/p&gt;
1852
1853 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1854 settrans -fgap /dev/netdde /hurd/netdde
1855 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1856 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1857 dhclient /dev/eth0
1858 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1859
1860 &lt;p&gt;After this, the machine had internet connectivity, and I could
1861 upgrade it and install the sysvinit packages from experimental and
1862 enable it as the default boot system in Hurd.&lt;/p&gt;
1863
1864 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1865 running on the machine it for ssh login to work a password need to be
1866 set. Also, note that a bug somewhere in openssh on Hurd block
1867 compression from working. Remember to turn that off on the client
1868 side.&lt;/p&gt;
1869
1870 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1871 stuff:&lt;/p&gt;
1872
1873 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1874 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1875 deb http://http.debian.net/debian/ experimental main
1876 EOF
1877 apt-get update
1878 apt-get dist-upgrade
1879 apt-get install -t experimental initscripts sysv-rc sysvinit \
1880 sysvinit-core sysvinit-utils
1881 update-alternatives --config runsystem
1882 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1883
1884 &lt;p&gt;To reboot after switching boot system, you have to use
1885 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1886 yet a sysvinit process able to receive the signals from the normal
1887 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1888 upgrading every package and rebooting, the network come up with DHCP
1889 after boot as it should, and the settrans/pkill hack mentioned at the
1890 start is no longer needed. But for some strange reason, there are no
1891 longer any login prompt in the virtual console, so I logged in using
1892 ssh instead.
1893
1894 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1895 fail some times. No idea what the cause is, but hope the Hurd porters
1896 figure it out. At least Justus said on IRC (#debian-hurd on
1897 irc.debian.org) that they are aware of the problem. A way to reduce
1898 the impact is to upgrade to the Hurd packages built by Justus by
1899 adding this repository to the machine:&lt;/p&gt;
1900
1901 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1902 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1903 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1904 EOF
1905 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1906
1907 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1908 http://ftp.debian-ports.org/debian, because some of the packages in
1909 unstable do not yet include the required patches that are lingering in
1910 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1911
1912 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1913 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1914 i emacs - GNU Emacs editor (metapackage)
1915 i gdb - GNU Debugger
1916 i hurd-recommended - Miscellaneous translators
1917 i isc-dhcp-client - ISC DHCP client
1918 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1919 i libc-bin - Embedded GNU C Library: Binaries
1920 i libc-dev-bin - Embedded GNU C Library: Development binaries
1921 i libc0.3 - Embedded GNU C Library: Shared libraries
1922 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1923 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1924 i multiarch-support - Transitional package to ensure multiarch compatibilit
1925 i A x11-common - X Window System (X.Org) infrastructure
1926 i xorg - X.Org X Window System
1927 i A xserver-xorg - X.Org X server
1928 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1929 #
1930 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1931
1932 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1933 X.org did not work out of the box and I never took the time to follow
1934 the porters instructions to fix it. This time I was interested in the
1935 command line stuff.&lt;p&gt;
1936 </description>
1937 </item>
1938
1939 <item>
1940 <title>New chrpath release 0.16</title>
1941 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1942 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1943 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1944 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1945 find problems in C, C++ and Java code using static source code
1946 analysis. It can detect a lot of different problems, and is very
1947 useful to find memory and locking bugs in the error handling part of
1948 the source. The company behind it provide
1949 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1950 a community service&lt;/a&gt;, and many hundred free software projects are
1951 already checked. A few days ago I decided to have a closer look at
1952 the Coverity system, and discovered that the
1953 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1954 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1955 projects I am involved with was already registered. But these are
1956 fairly big, and I would also like to have a small and easy project to
1957 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1958 checking of the chrpath project&lt;/a&gt;. It was
1959 added to the checker and discovered seven potential defects. Six of
1960 these were real, mostly resource &quot;leak&quot; when the program detected an
1961 error. Nothing serious, as the resources would be released a fraction
1962 of a second later when the program exited because of the error, but it
1963 is nice to do it right in case the source of the program some time in
1964 the future end up in a library. Having fixed all defects and added
1965 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1966 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1967 publish a new release. These are the release notes:&lt;/p&gt;
1968
1969 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1970
1971 &lt;ul&gt;
1972
1973 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1974 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1975 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1976
1977 &lt;/ul&gt;
1978
1979 &lt;p&gt;You can
1980 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1981 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1982 project if something is wrong with the new release. The test suite
1983 did not discover any old errors, so if you find a new one, please also
1984 include a test suite check.&lt;/p&gt;
1985 </description>
1986 </item>
1987
1988 <item>
1989 <title>New chrpath release 0.15</title>
1990 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1991 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1992 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1993 <description>&lt;p&gt;After many years break from the package and a vain hope that
1994 development would be continued by someone else, I finally pulled my
1995 acts together this morning and wrapped up a new release of chrpath,
1996 the command line tool to modify the rpath and runpath of already
1997 compiled ELF programs. The update was triggered by the persistence of
1998 Isha Vishnoi at IBM, which needed a new config.guess file to get
1999 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2000 is working on. I checked the
2001 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2002 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2003 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2004 packages for interesting patches (failed to find the source from
2005 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2006 These are the release notes:&lt;/p&gt;
2007
2008 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2009
2010 &lt;ul&gt;
2011
2012 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2013 with newer architectures. Thanks to isha vishnoi for the heads
2014 up.&lt;/li&gt;
2015
2016 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2017
2018 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2019 Matthias Klose.&lt;/li&gt;
2020
2021 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2022 Petr Machata found in Fedora.&lt;/li&gt;
2023
2024 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2025 .dynamic is a NULL terminated string. Based on patch found in
2026 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2027
2028 &lt;/ul&gt;
2029
2030 &lt;p&gt;You can
2031 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2032 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2033 project if something is wrong with the new release. The test suite
2034 did not discover any old errors, so if you find a new one, please also
2035 include a testsuite check.&lt;/p&gt;
2036 </description>
2037 </item>
2038
2039 <item>
2040 <title>Debian init.d boot script example for rsyslog</title>
2041 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2042 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2043 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2044 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2045 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2046 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2047 init.d scripts at all. Here is an example init.d script, ie a rewrite
2048 of /etc/init.d/rsyslog:&lt;/p&gt;
2049
2050 &lt;p&gt;&lt;pre&gt;
2051 #!/lib/init/init-d-script
2052 ### BEGIN INIT INFO
2053 # Provides: rsyslog
2054 # Required-Start: $remote_fs $time
2055 # Required-Stop: umountnfs $time
2056 # X-Stop-After: sendsigs
2057 # Default-Start: 2 3 4 5
2058 # Default-Stop: 0 1 6
2059 # Short-Description: enhanced syslogd
2060 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2061 # It is quite compatible to stock sysklogd and can be
2062 # used as a drop-in replacement.
2063 ### END INIT INFO
2064 DESC=&quot;enhanced syslogd&quot;
2065 DAEMON=/usr/sbin/rsyslogd
2066 &lt;/pre&gt;&lt;/p&gt;
2067
2068 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2069 script was 137 lines, and the above is just 15 lines, most of it meta
2070 info/comments.&lt;/p&gt;
2071
2072 &lt;p&gt;How to do this, you ask? Well, one create a new script
2073 /lib/init/init-d-script looking something like this:
2074
2075 &lt;p&gt;&lt;pre&gt;
2076 #!/bin/sh
2077
2078 # Define LSB log_* functions.
2079 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2080 # and status_of_proc is working.
2081 . /lib/lsb/init-functions
2082
2083 #
2084 # Function that starts the daemon/service
2085
2086 #
2087 do_start()
2088 {
2089 # Return
2090 # 0 if daemon has been started
2091 # 1 if daemon was already running
2092 # 2 if daemon could not be started
2093 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2094 || return 1
2095 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2096 $DAEMON_ARGS \
2097 || return 2
2098 # Add code here, if necessary, that waits for the process to be ready
2099 # to handle requests from services started subsequently which depend
2100 # on this one. As a last resort, sleep for some time.
2101 }
2102
2103 #
2104 # Function that stops the daemon/service
2105 #
2106 do_stop()
2107 {
2108 # Return
2109 # 0 if daemon has been stopped
2110 # 1 if daemon was already stopped
2111 # 2 if daemon could not be stopped
2112 # other if a failure occurred
2113 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2114 RETVAL=&quot;$?&quot;
2115 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2116 # Wait for children to finish too if this is a daemon that forks
2117 # and if the daemon is only ever run from this initscript.
2118 # If the above conditions are not satisfied then add some other code
2119 # that waits for the process to drop all resources that could be
2120 # needed by services started subsequently. A last resort is to
2121 # sleep for some time.
2122 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2123 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2124 # Many daemons don&#39;t delete their pidfiles when they exit.
2125 rm -f $PIDFILE
2126 return &quot;$RETVAL&quot;
2127 }
2128
2129 #
2130 # Function that sends a SIGHUP to the daemon/service
2131 #
2132 do_reload() {
2133 #
2134 # If the daemon can reload its configuration without
2135 # restarting (for example, when it is sent a SIGHUP),
2136 # then implement that here.
2137 #
2138 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2139 return 0
2140 }
2141
2142 SCRIPTNAME=$1
2143 scriptbasename=&quot;$(basename $1)&quot;
2144 echo &quot;SN: $scriptbasename&quot;
2145 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2146 script=&quot;$1&quot;
2147 shift
2148 . $script
2149 else
2150 exit 0
2151 fi
2152
2153 NAME=$(basename $DAEMON)
2154 PIDFILE=/var/run/$NAME.pid
2155
2156 # Exit if the package is not installed
2157 #[ -x &quot;$DAEMON&quot; ] || exit 0
2158
2159 # Read configuration variable file if it is present
2160 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2161
2162 # Load the VERBOSE setting and other rcS variables
2163 . /lib/init/vars.sh
2164
2165 case &quot;$1&quot; in
2166 start)
2167 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2168 do_start
2169 case &quot;$?&quot; in
2170 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2171 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2172 esac
2173 ;;
2174 stop)
2175 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2176 do_stop
2177 case &quot;$?&quot; in
2178 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2179 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2180 esac
2181 ;;
2182 status)
2183 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2184 ;;
2185 #reload|force-reload)
2186 #
2187 # If do_reload() is not implemented then leave this commented out
2188 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2189 #
2190 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2191 #do_reload
2192 #log_end_msg $?
2193 #;;
2194 restart|force-reload)
2195 #
2196 # If the &quot;reload&quot; option is implemented then remove the
2197 # &#39;force-reload&#39; alias
2198 #
2199 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2200 do_stop
2201 case &quot;$?&quot; in
2202 0|1)
2203 do_start
2204 case &quot;$?&quot; in
2205 0) log_end_msg 0 ;;
2206 1) log_end_msg 1 ;; # Old process is still running
2207 *) log_end_msg 1 ;; # Failed to start
2208 esac
2209 ;;
2210 *)
2211 # Failed to stop
2212 log_end_msg 1
2213 ;;
2214 esac
2215 ;;
2216 *)
2217 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2218 exit 3
2219 ;;
2220 esac
2221
2222 :
2223 &lt;/pre&gt;&lt;/p&gt;
2224
2225 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2226 lot. I did not really polish the approach, so it might not always
2227 work out of the box, but you get the idea. I did not try very hard to
2228 optimize it nor make it more robust either.&lt;/p&gt;
2229
2230 &lt;p&gt;A better argument for switching init system in Debian than reducing
2231 the size of init scripts (which is a good thing to do anyway), is to
2232 get boot system that is able to handle the kernel events sensibly and
2233 robustly, and do not depend on the boot to run sequentially. The boot
2234 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2235 </description>
2236 </item>
2237
2238 <item>
2239 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2240 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2241 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2242 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2243 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2244 remote display access is the preferred solution with oVirt and RedHat
2245 Enterprise Virtualization, and I was sad to discover the other day
2246 that the browser plugin needed to use these systems seamlessly was
2247 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2248 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2249 2013-04-01, so I decided to wrap up a package based on the great work
2250 from Cajus Pollmeier and put it in a collab-maint maintained git
2251 repository to get a package I could use. I would very much like
2252 others to help me maintain the package (or just take over, I do not
2253 mind), but as no-one had volunteered so far, I just uploaded it to
2254 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2255
2256 &lt;p&gt;The source is now available from
2257 &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;
2258 </description>
2259 </item>
2260
2261 <item>
2262 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2263 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2264 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2265 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2266 <description>&lt;p&gt;The
2267 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2268 program is a a very nice system to create virtual machine images. It
2269 create a image file, add a partition table, mount it and run
2270 debootstrap in the mounted directory to create a Debian system on a
2271 stick. Yesterday, I decided to try to teach it how to make images for
2272 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2273 of a plan to simplify the build system for
2274 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2275 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2276 the virtualbox images, but its current build system made multistrap
2277 based system for Dreamplug images, and it is lacking support for
2278 Raspberry Pi.&lt;/p&gt;
2279
2280 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2281 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2282 code and adjusted it to be able to build armel images on my amd64
2283 Debian laptop. I ended up giving vmdebootstrap five new options,
2284 allowing me to replicate the image creation process I use to make
2285 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2286 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2287 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2288 call debootstrap with --foreign and to copy the handler into the
2289 generated chroot before running the second stage. This allow
2290 vmdebootstrap to create armel images on an amd64 host. Next I added
2291 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2292 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2293 given file system type, allowing me to create an image with a vfat
2294 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2295 variant&lt;/tt&gt; option to allow me to create smaller images without the
2296 Debian base system packages installed. Finally, I added an option
2297 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2298 as a boot loader. It is not needed on the Raspberry Pi and probably
2299 most other non-x86 architectures. The changes were accepted by the
2300 upstream author of vmdebootstrap yesterday and today, and is now
2301 available from
2302 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2303 upstream project page&lt;/a&gt;.&lt;/p&gt;
2304
2305 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2306 create a small script (the customize script) to add the non-free
2307 binary blob needed to boot the Raspberry Pi and the APT source
2308 list:&lt;/p&gt;
2309
2310 &lt;p&gt;&lt;pre&gt;
2311 #!/bin/sh
2312 set -e # Exit on first error
2313 rootdir=&quot;$1&quot;
2314 cd &quot;$rootdir&quot;
2315 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2316 deb http://http.debian.net/debian/ jessie main contrib non-free
2317 EOF
2318 # Install non-free binary blob needed to boot Raspberry Pi. This
2319 # install a kernel somewhere too.
2320 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2321 -O $rootdir/usr/bin/rpi-update
2322 chmod a+x $rootdir/usr/bin/rpi-update
2323 mkdir -p $rootdir/lib/modules
2324 touch $rootdir/boot/start.elf
2325 chroot $rootdir rpi-update
2326 &lt;/pre&gt;&lt;/p&gt;
2327
2328 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2329 to build the image:&lt;/p&gt;
2330
2331 &lt;pre&gt;
2332 sudo ./vmdebootstrap \
2333 --variant minbase \
2334 --arch armel \
2335 --distribution jessie \
2336 --mirror http://http.debian.net/debian \
2337 --image test.img \
2338 --size 600M \
2339 --bootsize 64M \
2340 --boottype vfat \
2341 --log-level debug \
2342 --verbose \
2343 --no-kernel \
2344 --no-extlinux \
2345 --root-password raspberry \
2346 --hostname raspberrypi \
2347 --foreign /usr/bin/qemu-arm-static \
2348 --customize `pwd`/customize \
2349 --package netbase \
2350 --package git-core \
2351 --package binutils \
2352 --package ca-certificates \
2353 --package wget \
2354 --package kmod
2355 &lt;/pre&gt;&lt;/p&gt;
2356
2357 &lt;p&gt;The list of packages being installed are the ones needed by
2358 rpi-update to make the image bootable on the Raspberry Pi, with the
2359 exception of netbase, which is needed by debootstrap to find
2360 /etc/hosts with the minbase variant. I really wish there was a way to
2361 set up an Raspberry Pi using only packages in the Debian archive, but
2362 that is not possible as far as I know, because it boots from the GPU
2363 using a non-free binary blob.&lt;/p&gt;
2364
2365 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2366 probably a few others installed. I have not checked the complete
2367 build dependency list.&lt;/p&gt;
2368
2369 &lt;p&gt;The resulting image will not use the hardware floating point unit
2370 on the Raspberry PI, because the armel architecture in Debian is not
2371 optimized for that use. So the images created will be a bit slower
2372 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2373 </description>
2374 </item>
2375
2376 <item>
2377 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2378 <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>
2379 <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>
2380 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2381 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2382 wider attention. I recommend signing and donating to each one of
2383 these. :)&lt;/p&gt;
2384
2385 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2386 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2387 Women program which is a Google Summer of Code like initiative to get
2388 more women involved in free software. One debian sponsor has offered
2389 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2390 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2391 hope you will to. :)&lt;/p&gt;
2392
2393 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2394 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2395 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2396 take place these days, and their need to fund the work. I&#39;ve already
2397 donated. Are you next?&lt;/p&gt;
2398
2399 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2400 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2401 statement under the heading
2402 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2403 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2404 Norwegian government. So far 499 signatures. I hope you will sign it
2405 too.&lt;/p&gt;
2406 </description>
2407 </item>
2408
2409 <item>
2410 <title>Videos about the Freedombox project - for inspiration and learning</title>
2411 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2412 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2413 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2414 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2415 project&lt;/a&gt; have been going on for a while, and have presented the
2416 vision, ideas and solution several places. Here is a little
2417 collection of videos of talks and presentation of the project.&lt;/p&gt;
2418
2419 &lt;ul&gt;
2420
2421 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2422 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2423
2424 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2425 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2426
2427 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2428 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2429 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2430 (Youtube)&lt;/li&gt;
2431
2432 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2433 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2434
2435 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2436 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2437
2438 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2439 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2440 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2441
2442 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2443 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2444 (Youtube)&lt;/li&gt;
2445
2446 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2447 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2448
2449 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2450 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2451
2452 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2453 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2454 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2455
2456 &lt;/ul&gt;
2457
2458 &lt;p&gt;A larger list is available from
2459 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2460 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2461
2462 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2463 Jessie is coming along quite well, and soon both Owncloud and using
2464 Tor should be available for testers of the Freedombox solution. :) In
2465 a few weeks I hope everything needed to test it is included in Debian.
2466 The withsqlite package is already in Debian, and the plinth package is
2467 pending in NEW. The third and vital part of that puzzle is the
2468 metapackage/setup framework, which is still pending an upload. Join
2469 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2470 (#freedombox on irc.debian.org)&lt;/a&gt; and
2471 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2472 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2473 </description>
2474 </item>
2475
2476 <item>
2477 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2478 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2479 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2480 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2481 <description>&lt;p&gt;I was introduced to the
2482 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2483 in 2010, when Eben Moglen presented his vision about serving the need
2484 of non-technical people to keep their personal information private and
2485 within the legal protection of their own homes. The idea is to give
2486 people back the power over their network and machines, and return
2487 Internet back to its intended peer-to-peer architecture. Instead of
2488 depending on a central service, the Freedombox will give everyone
2489 control over their own basic infrastructure.&lt;/p&gt;
2490
2491 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2492 taken priority. But this summers nasty news about the misuse of trust
2493 and privilege exercised by the &quot;western&quot; intelligence gathering
2494 communities increased my eagerness to contribute to a point where I
2495 actually started working on the project a while back.&lt;/p&gt;
2496
2497 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2498 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2499 create a simple and cheap Debian based appliance that anyone can hook
2500 up in their home and get access to secure and private services and
2501 communication. The initial deployment platform have been the
2502 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2503 which is a piece of hardware I do not own. So to be able to test what
2504 the current Freedombox setup look like, I had to come up with a way to install
2505 it on some hardware I do have access to. I have rewritten the
2506 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2507 image build framework to use .deb packages instead of only copying
2508 setup into the boot images, and thanks to this rewrite I am able to
2509 set up any machine supported by Debian Wheezy as a Freedombox, using
2510 the previously mentioned deb (and a few support debs for packages
2511 missing in Debian).&lt;/p&gt;
2512
2513 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2514 scripts
2515 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2516 and a administrative web interface
2517 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2518 withsqlite), as well as a privacy enhancing proxy based on
2519 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2520 (freedombox-privoxy). There is also a web/javascript based XMPP
2521 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2522 trying (unsuccessfully so far) to talk to the XMPP server
2523 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2524 web interface is pluggable, and the goal is to use it to enable OpenID
2525 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2526 this is really working yet, see
2527 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2528 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2529 on github at the moment. The HTTP proxy is operational out of the
2530 box, and the admin web interface can be used to add/remove plinth
2531 users. I&#39;ve not been able to do anything else with it so far, but
2532 know there are several branches spread around github and other places
2533 with lots of half baked features.&lt;/p&gt;
2534
2535 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2536 following recipes should work to give you a test machine to poke
2537 at.&lt;/p&gt;
2538
2539 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2540
2541 &lt;ol&gt;
2542
2543 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2544 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2545 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2546 to the Debian installer:&lt;p&gt;
2547 &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;
2548
2549 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2550 install on.&lt;/li&gt;
2551
2552 &lt;li&gt;When the installation is finished and the machine have rebooted a
2553 few times, your Freedombox is ready for testing.&lt;/li&gt;
2554
2555 &lt;/ol&gt;
2556
2557 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2558
2559 &lt;ol&gt;
2560
2561 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2562 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2563 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2564 &lt;pre&gt;
2565 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2566 &lt;/pre&gt;&lt;/li&gt;
2567 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2568 &lt;pre&gt;
2569 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2570 apt-key add -
2571 apt-get update
2572 apt-get install freedombox-setup
2573 /usr/lib/freedombox/setup
2574 &lt;/pre&gt;&lt;/li&gt;
2575 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2576
2577 &lt;/ol&gt;
2578
2579 &lt;p&gt;You can test it on other architectures too, but because the
2580 freedombox-privoxy package is binary, it will only work as intended on
2581 the architectures where I have had time to build the binary and put it
2582 in my APT repository. But do not let this stop you. It is only a
2583 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2584
2585 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2586 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2587 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2588 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2589
2590 &lt;p&gt;Please let me know if this works for you, or if you have any
2591 problems. We gather on the IRC channel
2592 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2593 irc.debian.org and the
2594 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2595 mailing list&lt;/a&gt;.&lt;/p&gt;
2596
2597 &lt;p&gt;Once you get your freedombox operational, you can visit
2598 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2599 welcome screen (dead end - do not be surprised if you are unable to
2600 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2601 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2602 default password is &#39;secret&#39;.&lt;/p&gt;
2603 </description>
2604 </item>
2605
2606 <item>
2607 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2608 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2609 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2610 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2611 <description>&lt;p&gt;Earlier, I reported about
2612 &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
2613 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2614 told by IBM that the original disk should be thrown away. And as
2615 there no longer was a problem if I bricked the firmware, I decided
2616 today to try to install Intel firmware to replace the Lenovo firmware
2617 currently on the disk.&lt;/p&gt;
2618
2619 &lt;p&gt;I searched the Intel site for firmware, and found
2620 &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;
2621 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2622 according to the site should contain the latest firmware for SSD
2623 disks. I inserted the broken disk in one of my spare laptops and
2624 booted the ISO from a USB stick. The disk was recognized, but the
2625 program claimed the newest firmware already were installed and refused
2626 to insert any Intel firmware. So no change, and the disk is still
2627 unable to handle write load. :( I guess the only way to get them
2628 working would be if Lenovo releases new firmware. No idea how likely
2629 that is. Anyway, just blogging about this test for completeness. I
2630 got a working Samsung disk, and see no point in spending more time on
2631 the broken disks.&lt;/p&gt;
2632 </description>
2633 </item>
2634
2635 <item>
2636 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2637 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2638 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2639 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2640 <description>&lt;p&gt;Today I switched to
2641 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2642 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2643 my new Thinkpad X230, which was delivered with an
2644 &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
2645 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2646 sustained writes. My hardware supplier have been very forthcoming in
2647 trying to find a solution, and after first trying with another
2648 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2649 disk instead to fix it once and for all. The Samsung disk survived
2650 the installation of Debian with encrypted disks (filling the disk with
2651 random data during installation killed the first two), and I thus
2652 decided to trust it with my data. I have installed it as a Debian Edu
2653 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2654 server at home using Kerberos and LDAP, and will use it as my work
2655 station from now on.&lt;/p&gt;
2656
2657 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2658 Debian Wheezy default installation need to be tuned a bit to increase
2659 performance and increase life time of the disk. The Linux kernel and
2660 user space applications do not yet adjust automatically to such
2661 environment. To make it easier for my self, I created a draft Debian
2662 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2663 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2664 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2665 is set up to adjust the setup of the machine by just installing the
2666 package. If there is any non-SSD disk in the machine, the package
2667 will refuse to install, as I did not try to write any logic to sort
2668 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2669
2670 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2671 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2672 where I set up the machine with one large encrypted partition (in
2673 addition to /boot), put LVM on top of this and set up partitions on
2674 top of this again. See the README file in the package source for the
2675 references I used to pick the settings. At the moment these
2676 parameters are tuned:&lt;/p&gt;
2677
2678 &lt;ul&gt;
2679
2680 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2681 (adding discard to /etc/crypttab)&lt;/li&gt;
2682
2683 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2684 this case a cryptsetup partition) by changing issue_discards from
2685 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2686
2687 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2688 systems.&lt;/li&gt;
2689
2690 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2691 /etc/fstab.&lt;/li&gt;
2692
2693 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2694
2695 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2696 cron.daily).&lt;/li&gt;
2697
2698 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2699 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2700
2701 &lt;/ul&gt;
2702
2703 &lt;p&gt;During installation, I cancelled the part where the installer fill
2704 the disk with random data, as this would kill the SSD performance for
2705 little gain. My goal with the encrypted file system is to ensure
2706 those stealing my laptop end up with a brick and not a working
2707 computer. I have no hope in keeping the really resourceful people
2708 from getting the data on the disk (see
2709 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2710 Thus I concluded that adding the discard option to crypttab is the
2711 right thing to do.&lt;/p&gt;
2712
2713 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2714 it for SSD, but others recommended deadline and a benchmark I found
2715 indicated that deadline might be better for interactive use.&lt;/p&gt;
2716
2717 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2718 and ext4, but read that it would give a performance hit ever time a
2719 file is removed, and thought it best to that that slowdown once a day
2720 instead of during my work.&lt;/p&gt;
2721
2722 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2723 this is already done by Debian Edu.&lt;/p&gt;
2724
2725 &lt;p&gt;I have not yet started on the user space tuning. I expect
2726 iceweasel need some tuning, and perhaps other applications too, but
2727 have not yet had time to investigate those parts.&lt;/p&gt;
2728
2729 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2730 there.&lt;/p&gt;
2731
2732 &lt;p&gt;As for the answer to the question in the title of this blog post,
2733 as far as I know, the only solution I know about is to replace the
2734 disk. It might be possible to flash it with Intel firmware instead of
2735 the Lenovo firmware. But I have not tried and did not want to do so
2736 without approval from Lenovo as I wanted to keep the warranty on the
2737 disk until a solution was found and they wanted the broken disks
2738 back.&lt;/p&gt;
2739 </description>
2740 </item>
2741
2742 <item>
2743 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2744 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2745 <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>
2746 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2747 <description>&lt;p&gt;A few days ago, I wrote about
2748 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2749 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2750 was dying during installation because it is unable to cope with
2751 sustained write. My supplier is in contact with
2752 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2753 replacement disk to try to fix the problem. They decided to send an
2754 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2755
2756 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2757 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2758 same firmware version as the original. This time my hope raised
2759 slightly as the installation progressed, as the original disk used to
2760 die after 4-7% of the disk was written to, while this time it kept
2761 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2762 died again and I was back on square one. I still do not have a new
2763 laptop with a disk I can trust. I can not live with a disk that might
2764 lock up when I download a new
2765 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2766 other large files. I look forward to hearing from my supplier with
2767 the next proposal from Lenovo.&lt;/p&gt;
2768
2769 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2770 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2771 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2772 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2773 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2774 P/N 45N8295, P0C38732.&lt;/p&gt;
2775
2776 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2777 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2778 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2779 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2780 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2781 P/N 45N8295, P0C38732.&lt;/p&gt;
2782
2783 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2784 SA, date and WNPP values. Mentioning all the details here in case
2785 someone is able to use the information to find a way to identify the
2786 failing disk among working ones (if any such working disk actually
2787 exist).&lt;/p&gt;
2788 </description>
2789 </item>
2790
2791 <item>
2792 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2793 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2794 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2795 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2796 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2797 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2798 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2799 member assosiation NUUG&lt;/a&gt; and
2800 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2801 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2802 Bitraf&lt;/a&gt;.&lt;/p&gt;
2803
2804 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2805 welcome, and there is no fee to participate. There is on the other
2806 hand limited space, and only room for 30 people. Please put your name
2807 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2808 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2809 </description>
2810 </item>
2811
2812 <item>
2813 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2814 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2815 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2816 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2817 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2818 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2819 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2820 time to spend on it, and it took a while to find a model I believe
2821 will do the job, but two days ago the replacement finally arrived. I
2822 ended up picking a
2823 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2824 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2825 a roaming workstation, and it seemed to work flawlessly. But my
2826 second installation with encrypted disk was not as successful. More
2827 on that below.&lt;/p&gt;
2828
2829 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2830 important requirements (robust and with a good keyboard) are never
2831 listed in the feature list. But I did get good help from the search
2832 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2833 allowed me to limit the list of interesting laptops based on my other
2834 requirements. A bit surprising that SSD disk are not disks according
2835 to that search interface, so I had to drop specifying the number of
2836 disks from my search parameters. I also asked around among friends to
2837 get their impression on keyboards and robustness.&lt;/p&gt;
2838
2839 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2840 X41. I am not quite convinced about the keyboard, as it is
2841 significantly wider than my old keyboard, and I have to stretch my
2842 hand a lot more to reach the edges. But the key response is fairly
2843 good and the individual key shape is fairly easy to handle, so I hope
2844 I will get used to it. My old X40 was starting to fail, and I really
2845 needed a new laptop now. :)&lt;/p&gt;
2846
2847 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2848 visit to the BIOS during boot it disable it.&lt;/p&gt;
2849
2850 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2851 lock up during load. And this happen when installing Debian Wheezy
2852 with encrypted disk, while the disk is being filled with random data.
2853 I also tested to install Ubuntu Raring, and it happen there too if I
2854 reenable the code to fill the disk with random data (it is disabled by
2855 default in Ubuntu). And the bug with is already known. It was
2856 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2857 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2858 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2859 kernel developers as
2860 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2861 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2862 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2863 Lenovo forums, both for
2864 &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
2865 2012-11-10&lt;/a&gt; and for
2866 &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
2867 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2868 reports state that the disk lock up during use if many writes are done
2869 on the disk, so it is much no use to work around the installation
2870 problem and end up with a computer that can lock up at any moment.
2871 There is even a
2872 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2873 available&lt;/a&gt; that will lock up the hard drive after running a few
2874 minutes by writing to a file.&lt;/p&gt;
2875
2876 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2877 contacting PCHELP Norway (request 01D1FDP) which handle support
2878 requests for Lenovo, his first suggestion was to upgrade the disk
2879 firmware. Unfortunately there is no newer firmware available from
2880 Lenovo, as my disk already have the most recent one (version LF1i). I
2881 hope to hear more from him today and hope the problem can be
2882 fixed. :)&lt;/p&gt;
2883 </description>
2884 </item>
2885
2886 <item>
2887 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2888 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2890 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2891 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2892 trusty old Thinkpad X41. Unfortunately I did not have much time to
2893 spend on it, but today the replacement finally arrived. I ended up
2894 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2895 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2896 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2897 this, it is installing what I hope will be a more final installation,
2898 with a encrypted hard drive to ensure any dope head stealing it end up
2899 with an expencive door stop.&lt;/p&gt;
2900
2901 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2902 important requirements (robust and with a good keyboard) are never
2903 listed in the feature list. But I did get good help from the search
2904 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2905 allowed me to limit the list of interesting laptops based on my other
2906 requirements. A bit surprising that SSD disk are not disks, so I had
2907 to drop number of disks from my search parameters.&lt;/p&gt;
2908
2909 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2910 wider than my old keyboard, and I have to stretch my hand a lot more
2911 to reach the edges. But the key response is fairly good and the
2912 individual key shape is fairly easy to handle, so I hope I will get
2913 used to it. My old X40 was starting to fail, and I really needed a
2914 new laptop now. :)&lt;/p&gt;
2915
2916 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2917 </description>
2918 </item>
2919
2920 <item>
2921 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2922 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2923 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2924 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2925 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2926 perfectly capable of, and I have to do it manually to get things
2927 working. One such task is to find out what firmware packages are
2928 needed to get the hardware on my computer working. Most often this
2929 affect the wifi card, but some times it even affect the RAID
2930 controller or the ethernet card. Today I pushed version 0.4 of the
2931 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2932 including a new script isenkram-autoinstall-firmware handling the
2933 process of asking all the loaded kernel modules what firmware files
2934 they want, find debian packages providing these files and install the
2935 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2936
2937 &lt;p&gt;&lt;pre&gt;
2938 # isenkram-autoinstall-firmware
2939 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2940 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2941 info: locating packages with the requested firmware files
2942 info: Updating APT sources after adding non-free APT source
2943 info: trying to install firmware-ipw2x00
2944 firmware-ipw2x00
2945 firmware-ipw2x00
2946 Preconfiguring packages ...
2947 Selecting previously deselected package firmware-ipw2x00.
2948 (Reading database ... 259727 files and directories currently installed.)
2949 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2950 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2951 #
2952 &lt;/pre&gt;&lt;/p&gt;
2953
2954 &lt;p&gt;When all the requested firmware is present, a simple message is
2955 printed instead:&lt;/p&gt;
2956
2957 &lt;p&gt;&lt;pre&gt;
2958 # isenkram-autoinstall-firmware
2959 info: did not find any firmware files requested by loaded kernel modules. exiting
2960 #
2961 &lt;/pre&gt;&lt;/p&gt;
2962
2963 &lt;p&gt;It could use some polish, but it is already working well and saving
2964 me some time when setting up new machines. :)&lt;/p&gt;
2965
2966 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2967 kernel modules, and look up each one of them using modinfo, to find
2968 the firmware files listed in the module meta-information. Next, it
2969 download the Contents file from a nearby APT mirror, and search for
2970 the firmware files in this file to locate the package with the
2971 requested firmware file. If the package is in the non-free section, a
2972 non-free APT source is added and the package is installed using
2973 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2974 machine.&lt;/p&gt;
2975
2976 &lt;p&gt;I hope someone find time to implement a more polished version of
2977 this script as part of the hw-detect debian-installer module, to
2978 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2979 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2980 firmware during a PXE install when the packages already are available
2981 from the nearby Debian mirror.&lt;/p&gt;
2982 </description>
2983 </item>
2984
2985 <item>
2986 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2987 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2989 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2990 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2991 the screen just turn black when Linux boot, either during installation
2992 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2993 last few years, but only recently understood the cause. I&#39;ve seen it
2994 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2995 The reason seem to be in the wiring of some laptops. The system to
2996 control the screen background light is inverted, so when Linux try to
2997 turn the brightness fully on, it end up turning it off instead. I do
2998 not know which Linux drivers are affected, but this post is about the
2999 i915 driver used by the
3000 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3001 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3002
3003 &lt;p&gt;The problem can be worked around two ways. Either by adding
3004 i915.invert_brightness=1 as a kernel option, or by adding a file in
3005 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3006 option when it load the i915 kernel module. On Debian and Ubuntu, it
3007 can be done by running these commands as root:&lt;/p&gt;
3008
3009 &lt;pre&gt;
3010 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3011 update-initramfs -u -k all
3012 &lt;/pre&gt;
3013
3014 &lt;p&gt;Since March 2012 there is
3015 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3016 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3017 hardware have this problem, and get the driver to invert the
3018 brightness setting automatically. To use it, one need to add a row in
3019 &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
3020 intel_quirks array&lt;/a&gt; in the driver source
3021 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3022 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3023 number (vendor number 8086 is assumed) and subdevice vendor and device
3024 number.&lt;/p&gt;
3025
3026 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3027 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3028
3029 &lt;p&gt;&lt;pre&gt;
3030 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3031 3rd Gen Core processor Graphics Controller [8086:0156] \
3032 (rev 09) (prog-if 00 [VGA controller])
3033 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3034 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3035 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3036 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3037 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3038 Latency: 0
3039 Interrupt: pin A routed to IRQ 42
3040 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3041 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3042 Region 4: I/O ports at 4000 [size=64]
3043 Expansion ROM at &lt;unassigned&gt; [disabled]
3044 Capabilities: &lt;access denied&gt;
3045 Kernel driver in use: i915
3046 &lt;/pre&gt;&lt;/p&gt;
3047
3048 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3049
3050 &lt;p&gt;&lt;pre&gt;
3051 struct intel_quirk intel_quirks[] = {
3052 ...
3053 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3054 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3055 ...
3056 }
3057 &lt;/pre&gt;&lt;/p&gt;
3058
3059 &lt;p&gt;According to the kernel module instructions (as seen using
3060 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3061 invert_brightness flag should be sent to the
3062 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3063 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3064 developers. But my email about the laptop sent 2013-06-03 have not
3065 yet shown up in
3066 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3067 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3068 emails from non-subscribers. Because of this, I sent my patch also to
3069 the Debian bug tracking system instead as
3070 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3071 sure the patch is not lost.&lt;/p&gt;
3072
3073 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3074 with this problem working properly with Linux. If you use Gnome, your
3075 worries should be over at this point. But if you use KDE, there is
3076 something in KDE ignoring the invert_brightness setting and turning on
3077 the screen during login. I&#39;ve reported it to Debian as
3078 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3079 have no idea yet how to figure out exactly what subsystem is doing
3080 this. Perhaps you can help? Perhaps you know what the Gnome
3081 developers did to handle this, and this can give a clue to the KDE
3082 developers? Or you know where in KDE the screen brightness is changed
3083 during login? If so, please update the BTS report (or get in touch if
3084 you do not know how to update BTS).&lt;/p&gt;
3085
3086 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3087 acpi_backlight=vendor, to disable ACPI backlight support completely,
3088 as the ACPI information on the machine is trash and it is better to
3089 leave it to the intel video driver to control the screen
3090 backlight.&lt;/p&gt;
3091 </description>
3092 </item>
3093
3094 <item>
3095 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3096 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3097 <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>
3098 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3099 <description>&lt;p&gt;Two days ago, I asked
3100 &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
3101 I could install Linux on a Packard Bell EasyNote LV computer
3102 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3103 with the obstacles put in the way of Linux users on a laptop with UEFI
3104 and Windows 8.&lt;/p&gt;
3105
3106 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3107 secure booting or fast boot. I suspect fast boot was the problem,
3108 causing the firmware to boot directly from HD without considering any
3109 key presses and alternative devices, but do not know UEFI settings
3110 enough to tell.&lt;/p&gt;
3111
3112 &lt;p&gt;There is no way to install Linux on the machine in question without
3113 opening the box and disconnecting the hard drive! This is as far as I
3114 can tell, the only way to get access to the firmware setup menu
3115 without accepting the Windows 8 license agreement. I am told (and
3116 found description on how to) that it is possible to configure the
3117 firmware setup once booted into Windows 8. But as I believe the terms
3118 of that agreement are completely unacceptable, accepting the license
3119 was never an alternative. I do not enter agreements I do not intend
3120 to follow.&lt;/p&gt;
3121
3122 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3123 waste many hours on this, but luckily there was a way to get it to
3124 work. But I would not recommend it to anyone planning to run Linux on
3125 it, and I have become sceptical to Windows 8 certified laptops. Is
3126 this the way Linux will be forced out of the market place, by making
3127 it close to impossible for &quot;normal&quot; users to install Linux without
3128 accepting the Microsoft Windows license terms? Or at least not
3129 without risking to loose the warranty?&lt;/p&gt;
3130
3131 &lt;p&gt;I&#39;ve updated the
3132 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3133 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3134 do not have to struggle as much as I did to get Linux into the
3135 machine.&lt;/p&gt;
3136
3137 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3138 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3139 </description>
3140 </item>
3141
3142 <item>
3143 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3144 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3145 <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>
3146 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3147 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3148 new laptops for my parents and a few others. I bought Packard Bell
3149 Easynote LV to run Kubuntu on and use as their home computer. But I
3150 am completely unable to figure out how to install Linux on it. The
3151 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3152 instead of a BIOS to boot.&lt;/p&gt;
3153
3154 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3155 to get it to boot the Linux installer from my USB stick. I have yet
3156 to try the DVD install, and still hope it will work. when I turn on
3157 the computer, there is no information on what buttons to press to get
3158 the normal boot menu. I expect to get some boot menu to select PXE or
3159 USB stick booting. When booting, it first ask for the language to
3160 use, then for some regional settings, and finally if I will accept the
3161 Windows 8 terms of use. As these terms are completely unacceptable to
3162 me, I have no other choice but to turn off the computer and try again
3163 to get it to boot the Linux installer.&lt;/p&gt;
3164
3165 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3166 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3167 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3168 installed on this machine, please get in touch or update that wiki
3169 page. If I can&#39;t find a way to install Linux, I will have to return
3170 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3171
3172 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3173 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3174 on new Laptops?&lt;/p&gt;
3175 </description>
3176 </item>
3177
3178 <item>
3179 <title>How to transform a Debian based system to a Debian Edu installation</title>
3180 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3181 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3182 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3183 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3184 an operating system based on Debian intended for use in schools. It
3185 contain a turn-key solution for the computer network provided to
3186 pupils in the primary schools. It provide both the central server,
3187 network boot servers and desktop environments with heaps of
3188 educational software. The project was founded almost 12 years ago,
3189 2001-07-02. If you want to support the project, which is in need for
3190 cash to fund developer gatherings and other project related activity,
3191 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3192 donate some money&lt;/a&gt;.
3193
3194 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3195 lists and elsewhere, is the question on how to transform a Debian or
3196 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3197 hard, and last week I wrote a script to replicate the steps done by
3198 the Debian Edu installer.&lt;/p&gt;
3199
3200 &lt;p&gt;The script,
3201 &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;
3202 in the debian-edu-config package, will go through these six steps and
3203 transform an existing Debian Wheezy or Ubuntu (untested) installation
3204 into a Debian Edu Workstation:&lt;/p&gt;
3205
3206 &lt;ol&gt;
3207
3208 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3209 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3210 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3211 our configuration.&lt;/li&gt;
3212 &lt;li&gt;Preseed debconf database with profile setup in
3213 /etc/debian-edu/config, and run tasksel to install packages
3214 according to the profile specified in the config above,
3215 overriding some of the Debian automation machinery.&lt;/li&gt;
3216 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3217 that could not be done using preseeding.&lt;/li&gt;
3218 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3219
3220 &lt;/ol&gt;
3221
3222 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3223 replicated like this. Disk partitioning and LVM setup, for example.
3224 So this script just assume there is enough disk space to install all
3225 the needed packages.&lt;/p&gt;
3226
3227 &lt;p&gt;The script was created to help a Debian Edu student working on
3228 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3229 Debian Edu client, and using it he can take the existing
3230 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3231 transform it into a fully functioning Debian Edu Workstation (or
3232 Roaming Workstation, or whatever :).&lt;/p&gt;
3233
3234 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3235 If a LXDE based Roaming workstation is wanted instead, modify the
3236 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3237
3238 &lt;p&gt;&lt;pre&gt;
3239 PROFILE=&quot;Roaming-Workstation&quot;
3240 DESKTOP=&quot;lxde&quot;
3241 &lt;/pre&gt;&lt;/p&gt;
3242
3243 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3244 the cloud, by starting with a virtual Debian installation at some
3245 virtual hosting service and setting up all the services on first
3246 boot.&lt;/p&gt;
3247 </description>
3248 </item>
3249
3250 <item>
3251 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3252 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3253 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3254 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3255 <description>&lt;P&gt;In January,
3256 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3257 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3258 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3259 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3260 marvellous construction system from Denmark. We also created
3261 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3262 a place to take notes and write down our plans and hopes. And several
3263 people showed up to help. I was very happy to see the effect of my
3264 call. Since the small start, we have a debtags tag
3265 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3266 tag for LEGO related packages, and now count 10 packages related to
3267 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3268
3269 &lt;p&gt;&lt;table&gt;
3270 &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;
3271 &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;
3272 &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;
3273 &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;
3274 &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;
3275 &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;
3276 &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;
3277 &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;
3278 &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;
3279 &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;
3280 &lt;/table&gt;&lt;/p&gt;
3281
3282 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3283 currently available in Jessie/testing. leocad is so far only
3284 available in experimental.&lt;/p&gt;
3285
3286 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3287 adding the rest of the great free software tools available on Linux
3288 for LEGO designers.&lt;/p&gt;
3289 </description>
3290 </item>
3291
3292 <item>
3293 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3294 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3295 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3296 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3297 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3298 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3299 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3300 Debian release, and I expect to move my machines at home over to it fairly
3301 soon.&lt;/p&gt;
3302
3303 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3304 in particular make me very happy to see included. The
3305 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3306 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3307 included for the first time. Alongside similar programs like
3308 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3309 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3310 it allow for visual programming where syntax errors can not happen,
3311 and a friendly programming environment for learning to control the
3312 computer. Scratch will also be included in the next release of Debian
3313 Edu.&lt;/a&gt;
3314
3315 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3316 Edu/Skolelinux release too. The
3317 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3318 alpha release&lt;/a&gt; went out last week, and the next should soon
3319 follow.&lt;p&gt;
3320 </description>
3321 </item>
3322
3323 <item>
3324 <title>Isenkram 0.2 finally in the Debian archive</title>
3325 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3327 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3328 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3329 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3330 for many months. I uploaded it to the Debian experimental suite
3331 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3332
3333 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3334 install to work with a pluggable hardware device. The suggestion pop
3335 up when the device is plugged in. For example if a Lego Mindstorm NXT
3336 is inserted, it will suggest to install the program needed to program
3337 the NXT controller. Give it a go, and report bugs and suggestions to
3338 BTS. :)&lt;/p&gt;
3339 </description>
3340 </item>
3341
3342 <item>
3343 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3344 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3346 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3347 <description>&lt;p&gt;My
3348 &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
3349 bitcoin related blog post&lt;/a&gt; mentioned that the new
3350 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3351 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3352 2013-01-19, and have been available in unstable since then. It was
3353 automatically copied to Ubuntu, and is available in their Raring
3354 version too.&lt;/p&gt;
3355
3356 &lt;p&gt;But there is a strange problem with the build that block this new
3357 version from being available on the i386 and kfreebsd-i386
3358 architectures. For some strange reason, the autobuilders in Debian
3359 for these architectures fail to run the test suite on these
3360 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3361 We are so far unable to reproduce it when building it manually, and
3362 no-one have been able to propose a fix. If you got an idea what is
3363 failing, please let us know via the BTS.&lt;/p&gt;
3364
3365 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3366 I often run low on disk space, is the fact that the client will exit
3367 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3368 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3369 it. :)&lt;/p&gt;
3370
3371 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3372 activities, please send Bitcoin donations to my address
3373 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3374 </description>
3375 </item>
3376
3377 <item>
3378 <title>Welcome to the world, Isenkram!</title>
3379 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3380 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3381 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3382 <description>&lt;p&gt;Yesterday, I
3383 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3384 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3385 pluggable hardware devices, which I
3386 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3387 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3388 up, and caused me to really want to to open up the development to more
3389 people. But before I did this, I want to come up with a sensible name
3390 for this project. Today I finally decided on a new name, and I have
3391 renamed the project from hw-support-handler to this new name. In the
3392 process, I moved the source to git and made it available as a
3393 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3394 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3395 To fetch and build the latest version of the source, use&lt;/p&gt;
3396
3397 &lt;pre&gt;
3398 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3399 cd isenkram &amp;&amp; git-buildpackage -us -uc
3400 &lt;/pre&gt;
3401
3402 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3403 want to hack on the source or improve the package, please go ahead.
3404 But please talk to me first on IRC or via email before you do major
3405 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3406
3407 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3408 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3409 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3410 the German word eisenkram, for those that are familiar with that
3411 word.&lt;/p&gt;
3412
3413 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3414 instructions, to avoid confusing people with an error from the signing
3415 process.&lt;/p&gt;
3416
3417 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3418 clone argument to avoid the need for authentication.&lt;/p&gt;
3419 </description>
3420 </item>
3421
3422 <item>
3423 <title>First prototype ready making hardware easier to use in Debian</title>
3424 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3425 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3426 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3427 <description>&lt;p&gt;Early this month I set out to try to
3428 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3429 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3430 prototype is working, and it is ready for a larger audience. To test
3431 it, fetch the
3432 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3433 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3434 package. You might have to log out and in again activate the
3435 autostart script.&lt;/p&gt;
3436
3437 &lt;p&gt;The design is simple:&lt;/p&gt;
3438
3439 &lt;ul&gt;
3440
3441 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3442 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3443
3444 &lt;li&gt;This program listen for kernel events about new hardware (directly
3445 from the kernel like udev does), not using HAL dbus events as I
3446 initially did.&lt;/li&gt;
3447
3448 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3449 the APT database, a database
3450 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3451 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3452
3453 &lt;li&gt;If a package is mapped to the hardware in question, the package
3454 isn&#39;t installed yet and this is the first time the hardware was
3455 plugged in, show a desktop notification suggesting to install the
3456 package or packages.&lt;/li&gt;
3457
3458 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3459 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3460
3461 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3462 package while showing progress information in a window.&lt;/li&gt;
3463
3464 &lt;/ul&gt;
3465
3466 &lt;p&gt;I still need to come up with a better name for the system. Here
3467 are some screen shots showing the prototype in action. First the
3468 notification, then the password request, and finally the request to
3469 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3470
3471 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3472 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3473 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3474 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3475 &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;
3476
3477 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3478 is already useful. The database of hardware to package mappings also
3479 need more work. It is currently compatible with the Ubuntu way of
3480 storing such information in the package control file, but could be
3481 changed to use other formats instead or in addition to the current
3482 method. I&#39;ve dropped the use of discover for this mapping, as the
3483 modalias approach is more flexible and easier to use on Linux as long
3484 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3485
3486 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3487 here is the command required to check out and build the source: Use
3488 &#39;&lt;tt&gt;svn checkout
3489 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3490 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3491 devscripts package.&lt;/p&gt;
3492
3493 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3494 renamed to Isenkram and the source moved from the Debian Edu
3495 subversion repository to a Debian collab-maint git repository. See
3496 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3497 instructions&lt;/a&gt; for details.&lt;/p&gt;
3498 </description>
3499 </item>
3500
3501 <item>
3502 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3503 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3504 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3505 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3506 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3507 suddenly in bed. With a quiet whimper, it went completely quiet and
3508 black. The power button was no longer able to turn it on. It was a
3509 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3510 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3511 Compaq I had before that. Now I need to find a replacement. To keep
3512 going during Christmas, I moved the one year old SSD disk to my old
3513 X40 where it fitted (only one I had left that could use it), but it is
3514 not a durable solution.
3515
3516 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3517 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3518
3519 &lt;ul&gt;
3520
3521 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3522 than A4).&lt;/li&gt;
3523 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3524 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3525 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3526 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3527 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3528 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3529 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3530 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3531 size).&lt;/li&gt;
3532 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3533 X.org packages.&lt;/li&gt;
3534 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3535 the time).
3536
3537 &lt;/ul&gt;
3538
3539 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3540 list. The reason is simply that the specifications on laptops the
3541 last 10-15 years have been sufficient for my needs, and I have to look
3542 at other features to choose my laptop. But are there still made as
3543 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3544 robust, and Thinkpads seem to be heading in the wrong direction since
3545 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3546 still be useful.&lt;/p&gt;
3547
3548 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3549 external keyboard? I&#39;ll have to check the
3550 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3551 well-supported laptops, or perhaps just buy one preinstalled from one
3552 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3553 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3554 </description>
3555 </item>
3556
3557 <item>
3558 <title>How to find a browser plugin supporting a given MIME type</title>
3559 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3560 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3561 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3562 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3563 install to get support for a given MIME type. Thanks to
3564 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3565 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3566 Unfortunately, not very many packages provide the needed meta
3567 information, Anyway, here is a small script to look up all browser
3568 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3569
3570 &lt;pre&gt;
3571 #!/usr/bin/python
3572 import sys
3573 import apt
3574 def pkgs_handling_mimetype(mimetype):
3575 cache = apt.Cache()
3576 cache.open(None)
3577 thepkgs = []
3578 for pkg in cache:
3579 version = pkg.candidate
3580 if version is None:
3581 version = pkg.installed
3582 if version is None:
3583 continue
3584 record = version.record
3585 if not record.has_key(&#39;Npp-MimeType&#39;):
3586 continue
3587 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3588 for t in mime_types:
3589 t = t.rstrip().strip()
3590 if t == mimetype:
3591 thepkgs.append(pkg.name)
3592 return thepkgs
3593 mimetype = &quot;audio/ogg&quot;
3594 if 1 &lt; len(sys.argv):
3595 mimetype = sys.argv[1]
3596 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3597 for pkg in pkgs_handling_mimetype(mimetype):
3598 print &quot; %s&quot; %pkg
3599 &lt;/pre&gt;
3600
3601 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3602
3603 &lt;pre&gt;
3604 % ./apt-find-browserplug-for-mimetype
3605 Browser plugin packages supporting audio/ogg:
3606 gecko-mediaplayer
3607 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3608 Browser plugin packages supporting application/x-shockwave-flash:
3609 browser-plugin-gnash
3610 %
3611 &lt;/pre&gt;
3612
3613 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3614 itself to query for plugins and propose to install the needed
3615 packages. It would be great if Debian supported such feature too. Is
3616 anyone working on adding it?&lt;/p&gt;
3617
3618 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3619 request for icweasel support for this feature is
3620 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3621 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3622 of manpower and wish for a different design is the reason thus feature
3623 is not yet in iceweasel from Debian.&lt;/p&gt;
3624 </description>
3625 </item>
3626
3627 <item>
3628 <title>What is the most supported MIME type in Debian?</title>
3629 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3631 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3632 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3633 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3634 proposal to make it possible for a Desktop application to propose to
3635 the user some package to install to gain support for a given MIME
3636 type, font, library etc. that is currently missing. With such
3637 mechanism in place, it would be possible for the desktop to
3638 automatically propose and install leocad if some LDraw file is
3639 downloaded by the browser.&lt;/p&gt;
3640
3641 &lt;p&gt;To get some idea about the current content of the archive, I decided
3642 to write a simple program to extract all .desktop files from the
3643 Debian archive and look up the claimed MIME support there. The result
3644 can be found on the
3645 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3646 site&lt;/a&gt;. Using the collected information, it become possible to
3647 answer the question in the title. Here are the 20 most supported MIME
3648 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3649 The complete list is available from the link above.&lt;/p&gt;
3650
3651 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3652
3653 &lt;pre&gt;
3654 count MIME type
3655 ----- -----------------------
3656 32 text/plain
3657 30 audio/mpeg
3658 29 image/png
3659 28 image/jpeg
3660 27 application/ogg
3661 26 audio/x-mp3
3662 25 image/tiff
3663 25 image/gif
3664 22 image/bmp
3665 22 audio/x-wav
3666 20 audio/x-flac
3667 19 audio/x-mpegurl
3668 18 video/x-ms-asf
3669 18 audio/x-musepack
3670 18 audio/x-mpeg
3671 18 application/x-ogg
3672 17 video/mpeg
3673 17 audio/x-scpls
3674 17 audio/ogg
3675 16 video/x-ms-wmv
3676 &lt;/pre&gt;
3677
3678 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3679
3680 &lt;pre&gt;
3681 count MIME type
3682 ----- -----------------------
3683 33 text/plain
3684 32 image/png
3685 32 image/jpeg
3686 29 audio/mpeg
3687 27 image/gif
3688 26 image/tiff
3689 26 application/ogg
3690 25 audio/x-mp3
3691 22 image/bmp
3692 21 audio/x-wav
3693 19 audio/x-mpegurl
3694 19 audio/x-mpeg
3695 18 video/mpeg
3696 18 audio/x-scpls
3697 18 audio/x-flac
3698 18 application/x-ogg
3699 17 video/x-ms-asf
3700 17 text/html
3701 17 audio/x-musepack
3702 16 image/x-xbitmap
3703 &lt;/pre&gt;
3704
3705 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3706
3707 &lt;pre&gt;
3708 count MIME type
3709 ----- -----------------------
3710 31 text/plain
3711 31 image/png
3712 31 image/jpeg
3713 29 audio/mpeg
3714 28 application/ogg
3715 27 image/gif
3716 26 image/tiff
3717 26 audio/x-mp3
3718 23 audio/x-wav
3719 22 image/bmp
3720 21 audio/x-flac
3721 20 audio/x-mpegurl
3722 19 audio/x-mpeg
3723 18 video/x-ms-asf
3724 18 video/mpeg
3725 18 audio/x-scpls
3726 18 application/x-ogg
3727 17 audio/x-musepack
3728 16 video/x-ms-wmv
3729 16 video/x-msvideo
3730 &lt;/pre&gt;
3731
3732 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3733 information mentioned in DEP-11. I have not yet had time to look at
3734 it, but hope the PackageKit people in Debian are on top of these
3735 issues.&lt;/p&gt;
3736
3737 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3738 discovering a typo in my script.&lt;/p&gt;
3739 </description>
3740 </item>
3741
3742 <item>
3743 <title>Using modalias info to find packages handling my hardware</title>
3744 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3745 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3746 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3747 <description>&lt;p&gt;Yesterday, I wrote about the
3748 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3749 values provided by the Linux kernel&lt;/a&gt; following my hope for
3750 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3751 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3752 modalias values attached to package names can be used to map packages
3753 to hardware. This allow the system to look up and suggest relevant
3754 packages when I plug in some new hardware into my machine, and replace
3755 discover and discover-data as the database used to map hardware to
3756 packages.&lt;/p&gt;
3757
3758 &lt;p&gt;I create a modaliases file with entries like the following,
3759 containing package name, kernel module name (if relevant, otherwise
3760 the package name) and globs matching the relevant hardware
3761 modalias.&lt;/p&gt;
3762
3763 &lt;p&gt;&lt;blockquote&gt;
3764 Package: package-name
3765 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3766 &lt;/blockquote&gt;&lt;/p&gt;
3767
3768 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3769 for a given modalias value using this file.&lt;/p&gt;
3770
3771 &lt;p&gt;An entry like this would suggest the video and picture application
3772 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3773
3774 &lt;p&gt;&lt;blockquote&gt;
3775 Package: cheese
3776 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3777 &lt;/blockquote&gt;&lt;/p&gt;
3778
3779 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3780 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3781
3782 &lt;p&gt;&lt;blockquote&gt;
3783 Package: pcmciautils
3784 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3785 &lt;/blockquote&gt;&lt;/p&gt;
3786
3787 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3788 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3789
3790 &lt;p&gt;&lt;blockquote&gt;
3791 Package: colorhug-client
3792 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3793 &lt;/blockquote&gt;&lt;/p&gt;
3794
3795 &lt;p&gt;I believe the format is compatible with the format of the Packages
3796 file in the Debian archive. Ubuntu already uses their Packages file
3797 to store their mappings from packages to hardware.&lt;/p&gt;
3798
3799 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3800 announce the hardware it support in a way my prototype understand.
3801 This allow those publishing packages in an APT source outside the
3802 Debian archive as well as those backporting packages to make sure the
3803 hardware mapping are included in the package meta information. I&#39;ve
3804 tested such header in the pymissile package, and its modalias mapping
3805 is working as it should with my prototype. It even made it to Ubuntu
3806 Raring.&lt;/p&gt;
3807
3808 &lt;p&gt;To test if it was possible to look up supported hardware using only
3809 the shell tools available in the Debian installer, I wrote a shell
3810 implementation of the lookup code. The idea is to create files for
3811 each modalias and let the shell do the matching. Please check out and
3812 try the
3813 &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;
3814 shell script. It run without any extra dependencies and fetch the
3815 hardware mappings from the Debian archive and the subversion
3816 repository where I currently work on my prototype.&lt;/p&gt;
3817
3818 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3819 install yubikey-personalization:&lt;/p&gt;
3820
3821 &lt;p&gt;&lt;blockquote&gt;
3822 % ./hw-support-lookup
3823 &lt;br&gt;yubikey-personalization
3824 &lt;br&gt;%
3825 &lt;/blockquote&gt;&lt;/p&gt;
3826
3827 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3828 propose to install the pcmciautils package:&lt;/p&gt;
3829
3830 &lt;p&gt;&lt;blockquote&gt;
3831 % ./hw-support-lookup
3832 &lt;br&gt;pcmciautils
3833 &lt;br&gt;%
3834 &lt;/blockquote&gt;&lt;/p&gt;
3835
3836 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3837 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3838 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3839
3840 &lt;p&gt;It could be possible to generate several of the mappings between
3841 packages and hardware. One source would be to look at packages with
3842 kernel modules, ie packages with *.ko files in /lib/modules/, and
3843 extract their modalias information. Another would be to look at
3844 packages with udev rules, ie packages with files in
3845 /lib/udev/rules.d/, and extract their vendor/model information to
3846 generate a modalias matching rule. I have not tested any of these to
3847 see if it work.&lt;/p&gt;
3848
3849 &lt;p&gt;If you want to help implementing a system to let us propose what
3850 packages to install when new hardware is plugged into a Debian
3851 machine, please send me an email or talk to me on
3852 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3853 </description>
3854 </item>
3855
3856 <item>
3857 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3858 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3859 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3860 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3861 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3862 information, to find the packages that support a given piece of
3863 hardware, I refreshed my memory regarding modalias values, and decided
3864 to document the details. Here are my findings so far, also available
3865 in
3866 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3867 Debian Edu subversion repository&lt;/a&gt;:
3868
3869 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3870
3871 &lt;p&gt;This document try to explain what the different types of modalias
3872 values stands for. It is in part based on information from
3873 &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;,
3874 &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;,
3875 &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
3876 &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;.
3877
3878 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3879 this shell script:&lt;/p&gt;
3880
3881 &lt;pre&gt;
3882 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3883 &lt;/pre&gt;
3884
3885 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3886 using modinfo:&lt;/p&gt;
3887
3888 &lt;pre&gt;
3889 % /sbin/modinfo psmouse | grep alias:
3890 alias: serio:ty05pr*id*ex*
3891 alias: serio:ty01pr*id*ex*
3892 %
3893 &lt;/pre&gt;
3894
3895 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3896
3897 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3898 Bridge memory controller:&lt;/p&gt;
3899
3900 &lt;p&gt;&lt;blockquote&gt;
3901 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3902 &lt;/blockquote&gt;&lt;/p&gt;
3903
3904 &lt;p&gt;This represent these values:&lt;/p&gt;
3905
3906 &lt;pre&gt;
3907 v 00008086 (vendor)
3908 d 00002770 (device)
3909 sv 00001028 (subvendor)
3910 sd 000001AD (subdevice)
3911 bc 06 (bus class)
3912 sc 00 (bus subclass)
3913 i 00 (interface)
3914 &lt;/pre&gt;
3915
3916 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3917 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3918 0600. The 0600 class is a host bridge. Other useful bus values are
3919 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3920
3921 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3922 means.&lt;/p&gt;
3923
3924 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3925
3926 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3927 USB hub in a laptop:&lt;/p&gt;
3928
3929 &lt;p&gt;&lt;blockquote&gt;
3930 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3931 &lt;/blockquote&gt;&lt;/p&gt;
3932
3933 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3934
3935 &lt;pre&gt;
3936 v 1D6B (device vendor)
3937 p 0001 (device product)
3938 d 0206 (bcddevice)
3939 dc 09 (device class)
3940 dsc 00 (device subclass)
3941 dp 00 (device protocol)
3942 ic 09 (interface class)
3943 isc 00 (interface subclass)
3944 ip 00 (interface protocol)
3945 &lt;/pre&gt;
3946
3947 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3948 class is in the interface class section. For a simple USB web camera,
3949 these alias entries show up:&lt;/p&gt;
3950
3951 &lt;p&gt;&lt;blockquote&gt;
3952 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3953 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3954 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3955 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3956 &lt;/blockquote&gt;&lt;/p&gt;
3957
3958 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3959 camera), 0101 is audio control device and 0102 is audio streaming (aka
3960 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3961
3962 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3963
3964 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3965 receiver in a Thinkpad X40:&lt;/p&gt;
3966
3967 &lt;p&gt;&lt;blockquote&gt;
3968 acpi:IBM0071:PNP0511:
3969 &lt;/blockquote&gt;&lt;/p&gt;
3970
3971 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3972
3973 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3974
3975 &lt;p&gt;The DMI table contain lots of information about the computer case
3976 and model. This is an entry for a IBM Thinkpad X40, fetched from
3977 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3978
3979 &lt;p&gt;&lt;blockquote&gt;
3980 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3981 &lt;/blockquote&gt;&lt;/p&gt;
3982
3983 &lt;p&gt;The values present are&lt;/p&gt;
3984
3985 &lt;pre&gt;
3986 bvn IBM (BIOS vendor)
3987 bvr 1UETB6WW(1.66) (BIOS version)
3988 bd 06/15/2005 (BIOS date)
3989 svn IBM (system vendor)
3990 pn 2371H4G (product name)
3991 pvr ThinkPadX40 (product version)
3992 rvn IBM (board vendor)
3993 rn 2371H4G (board name)
3994 rvr NotAvailable (board version)
3995 cvn IBM (chassis vendor)
3996 ct 10 (chassis type)
3997 cvr NotAvailable (chassis version)
3998 &lt;/pre&gt;
3999
4000 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4001 found in the dmidecode source:&lt;/p&gt;
4002
4003 &lt;pre&gt;
4004 3 Desktop
4005 4 Low Profile Desktop
4006 5 Pizza Box
4007 6 Mini Tower
4008 7 Tower
4009 8 Portable
4010 9 Laptop
4011 10 Notebook
4012 11 Hand Held
4013 12 Docking Station
4014 13 All In One
4015 14 Sub Notebook
4016 15 Space-saving
4017 16 Lunch Box
4018 17 Main Server Chassis
4019 18 Expansion Chassis
4020 19 Sub Chassis
4021 20 Bus Expansion Chassis
4022 21 Peripheral Chassis
4023 22 RAID Chassis
4024 23 Rack Mount Chassis
4025 24 Sealed-case PC
4026 25 Multi-system
4027 26 CompactPCI
4028 27 AdvancedTCA
4029 28 Blade
4030 29 Blade Enclosing
4031 &lt;/pre&gt;
4032
4033 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4034 table. For example my home server is a tower, but the DMI modalias
4035 claim it is a desktop.&lt;/p&gt;
4036
4037 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4038
4039 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4040 test machine:&lt;/p&gt;
4041
4042 &lt;p&gt;&lt;blockquote&gt;
4043 serio:ty01pr00id00ex00
4044 &lt;/blockquote&gt;&lt;/p&gt;
4045
4046 &lt;p&gt;The values present are&lt;/p&gt;
4047
4048 &lt;pre&gt;
4049 ty 01 (type)
4050 pr 00 (prototype)
4051 id 00 (id)
4052 ex 00 (extra)
4053 &lt;/pre&gt;
4054
4055 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4056 the valid values are.&lt;/p&gt;
4057
4058 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4059
4060 &lt;p&gt;There are heaps of other modalias subtypes according to
4061 file2alias.c. There is the rest of the list from that source: amba,
4062 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4063 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4064 vmbus, x86cpu and zorro. I did not spend time documenting all of
4065 these, as they do not seem relevant for my intended use with mapping
4066 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4067
4068 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4069
4070 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4071 one can use the following shell script:&lt;/p&gt;
4072
4073 &lt;pre&gt;
4074 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4075 echo &quot;$id&quot; ; \
4076 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4077 done
4078 &lt;/pre&gt;
4079
4080 &lt;p&gt;The output can look like this (only the first few entries as the
4081 list is very long on my test machine):&lt;/p&gt;
4082
4083 &lt;pre&gt;
4084 acpi:ACPI0003:
4085 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4086 acpi:device:
4087 FATAL: Module acpi:device: not found.
4088 acpi:IBM0068:
4089 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4090 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4091 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4092 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4093 acpi:IBM0071:PNP0511:
4094 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4095 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4096 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4097 [...]
4098 &lt;/pre&gt;
4099
4100 &lt;p&gt;If you want to help implementing a system to let us propose what
4101 packages to install when new hardware is plugged into a Debian
4102 machine, please send me an email or talk to me on
4103 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4104
4105 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4106 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4107 in /sys/ with space in them.&lt;/p&gt;
4108 </description>
4109 </item>
4110
4111 <item>
4112 <title>Moved the pymissile Debian packaging to collab-maint</title>
4113 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4114 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4115 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4116 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4117 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4118 Launcher and updated the Debian package
4119 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4120 sure udev will fix the device permissions when it is plugged in. I
4121 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4122 hopefully make the package be proposed by jockey in Ubuntu when a user
4123 plug in his rocket launcher. In the process I moved the source to a
4124 git repository under collab-maint, to make it easier for any DD to
4125 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4126 is not very active, but the software still work for me even after five
4127 years of relative silence. The new git repository is not listed in
4128 the uploaded package yet, because I want to test the other changes a
4129 bit more before I upload the new version. If you want to check out
4130 the new version with a .desktop file included, visit the
4131 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4132 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4133 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4134 </description>
4135 </item>
4136
4137 <item>
4138 <title>Lets make hardware dongles easier to use in Debian</title>
4139 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4140 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4141 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4142 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4143 general, is that there is a great package management system with the
4144 ability to automatically install software packages by downloading them
4145 from the distribution mirrors, but no way to get it to automatically
4146 install the packages I need to use the hardware I plug into my
4147 machine. Even if the package to use it is easily available from the
4148 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4149 suggest to automatically install the python-nxt, nbc and t2n packages
4150 I need to talk to it. When I plug in a Yubikey, it could propose the
4151 yubikey-personalization package. The information required to do this
4152 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4153
4154 &lt;p&gt;Some years ago, I proposed to
4155 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4156 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4157 simple:
4158
4159 &lt;ul&gt;
4160
4161 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4162 starting when a user log in.&lt;/li&gt;
4163
4164 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4165 hardware is inserted into the computer.&lt;/li&gt;
4166
4167 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4168 database mapping to packages, and take note of any non-installed
4169 packages.&lt;/li&gt;
4170
4171 &lt;li&gt;Show a message to the user proposing to install the discovered
4172 package, and make it easy to install it.&lt;/li&gt;
4173
4174 &lt;/ul&gt;
4175
4176 &lt;p&gt;I am not sure what the best way to implement this is, but my
4177 initial idea was to use dbus events to discover new hardware, the
4178 discover database to find packages and
4179 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4180 packages.&lt;/p&gt;
4181
4182 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4183 draft package is now checked into
4184 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4185 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4186 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4187 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4188 the relevant packages in Debian, and uploaded a new version
4189 2.2013.01.09 to unstable. I also discovered that the current
4190 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4191 package in Debian no longer discovered any USB devices, because
4192 /proc/bus/usb/devices is no longer present. I ported it to use
4193 libusb as a fall back option to get it working. The fixed package
4194 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4195 because of the freeze).&lt;/p&gt;
4196
4197 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4198 desktop notification to show up (only once, the first time it is
4199 inserted):&lt;/p&gt;
4200
4201 &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;
4202
4203 &lt;p&gt;For this prototype to be really useful, some way to automatically
4204 install the proposed packages by pressing the &quot;Please install
4205 program(s)&quot; button should to be implemented.&lt;/p&gt;
4206
4207 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4208 happen, please help me update the discover-data database with mappings
4209 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4210 list the package you would like to have installed when a given
4211 hardware device is inserted into your computer, and report bugs using
4212 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4213 such mapping, please let me know.&lt;/p&gt;
4214
4215 &lt;p&gt;This prototype need more work, and there are several questions that
4216 should be considered before it is ready for production use. Is dbus
4217 the correct way to detect new hardware? At the moment I look for HAL
4218 dbus events on the system bus, because that is the events I could see
4219 on my Debian Squeeze KDE desktop. Are there better events to use?
4220 How should the user be notified? Is the desktop notification
4221 mechanism the best option, or should the background daemon raise a
4222 popup instead? How should packages be installed? When should they
4223 not be installed?&lt;/p&gt;
4224
4225 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4226 please send me an email. :)&lt;/p&gt;
4227 </description>
4228 </item>
4229
4230 <item>
4231 <title>New IRC channel for LEGO designers using Debian</title>
4232 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4233 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4234 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4235 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4236 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4237 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4238 discovered I had to build all the tools myself because none were
4239 already in Debian Squeeze. If Debian support for LEGO is something
4240 you care about, please join me on the IRC channel
4241 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4242 irc.debian.org). There is a lot that could be done to improve the
4243 Debian support for LEGO designers. For example both CAD software
4244 and Mindstorm compilers are missing. :)&lt;/p&gt;
4245
4246 &lt;p&gt;Update 2012-01-03: A
4247 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4248 including links to Lego related packages is now available.&lt;/p&gt;
4249 </description>
4250 </item>
4251
4252 <item>
4253 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4254 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4255 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4256 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4257 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4258 year! I hope next year will prove to be a good year.&lt;/p&gt;
4259
4260 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4261 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4262 between each other with minimal overhead, is a very interesting
4263 experiment. And as I wrote a few days ago, the bitcoin situation in
4264 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4265 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4266 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4267 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4268 for one of the ftpmasters to approve the new bitcoin-qt package
4269 name.&lt;/p&gt;
4270
4271 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4272 team in Debian, you can easily test the package in Debian Squeeze
4273 using the following steps to get a set of working packages:&lt;/p&gt;
4274
4275 &lt;blockquote&gt;&lt;pre&gt;
4276 git clone git://git.debian.org/git/collab-maint/bitcoin
4277 cd bitcoin
4278 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4279 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4280 &lt;/pre&gt;&lt;/blockquote&gt;
4281
4282 &lt;p&gt;You might have to install some build dependencies as well. The
4283 list of commands should give you two packages, bitcoind and
4284 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4285 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4286 around 5.6 GiB of data on my machine at the moment. Make sure your
4287 ~/.bitcoin/ directory have lots of spare room if you want to download
4288 all the blocks. The client will warn if the disk is getting full, so
4289 there is not really a problem if you got too little room, but you will
4290 not be able to get all the features out of the client.&lt;/p&gt;
4291
4292 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4293 activities, please send Bitcoin donations to my address
4294 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4295 </description>
4296 </item>
4297
4298 <item>
4299 <title>A word on bitcoin support in Debian</title>
4300 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4301 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4302 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4303 <description>&lt;p&gt;It has been a while since I wrote about
4304 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4305 peer-to-peer based crypto-currency, and the reason is simply that I
4306 have been busy elsewhere. But two days ago, I started looking at the
4307 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4308 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4309 is now maintained by a
4310 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4311 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4312 owe a huge thank you to all these team members. :)
4313 But I was sad to discover that the bitcoin client is missing in
4314 Wheezy. It is only available in Sid (and an outdated client from
4315 backports). The client had several RC bugs registered in BTS blocking
4316 it from entering testing. To try to help the team and improve the
4317 situation, I spent some time providing patches and triaging the bug
4318 reports. I also had a look at the bitcoin package available from Matt
4319 Corallo in a
4320 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4321 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4322 Debian package.&lt;/p&gt;
4323
4324 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4325 IRC, I pushed several patches into the collab-maint git repository to
4326 improve the package. It now contains fixes for the RC issues (not from
4327 me, but fixed by Scott Howard), build rules for a Qt GUI client
4328 package, konqueror support for the bitcoin: URI and bash completion
4329 setup. As I work on Debian Squeeze, I also created
4330 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4331 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4332 it and try to integrate it into the git repository before uploading a
4333 new version to unstable.
4334
4335 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4336 centralized control currently exercised in the monetary system. I
4337 find it completely unacceptable that the USA government is collecting
4338 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4339 that the major credit card companies can block legal money
4340 transactions to Wikileaks. But for bitcoin to succeed, more people
4341 need to use bitcoins, and more people need to accept bitcoins when
4342 they sell products and services. Improving the bitcoin support in
4343 Debian is a small step in the right direction, but not enough.
4344 Unfortunately the user experience when browsing the web and wanting to
4345 pay with bitcoin is still not very good. The bitcoin: URI is a step
4346 in the right direction, but need to work in most or every browser in
4347 use. Also the bitcoin-qt client is too heavy to fire up to do a
4348 quick transaction. I believe there are other clients available, but
4349 have not tested them.&lt;/p&gt;
4350
4351 &lt;p&gt;My
4352 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4353 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4354 I received 20.15 BTC so far on the address I provided in my blog two
4355 years ago, as can be
4356 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4357 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4358 donation. The blockexplorer service demonstrates quite well that
4359 bitcoin is not quite anonymous and untracked. :) I wonder if the
4360 number of users have gone up since then. If you use bitcoin and want
4361 to show your support of my activity, please send Bitcoin donations to
4362 the same address as last time,
4363 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4364 </description>
4365 </item>
4366
4367 <item>
4368 <title>Git repository for song book for Computer Scientists</title>
4369 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4370 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4371 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4372 <description>&lt;p&gt;As I
4373 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4374 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4375 years ago, and today I finally found time to create a public
4376 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4377 repository for the project&lt;/a&gt;.&lt;/p&gt;
4378
4379 &lt;p&gt;If you want to help out, please clone the source and submit patches
4380 to the HTML version. To generate the PDF and PostScript version,
4381 please use prince XML, or let me know about a useful free software
4382 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4383
4384 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4385 PostScript formats at
4386 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4387 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4388 </description>
4389 </item>
4390
4391 <item>
4392 <title>Gratulerer med 19-årsdagen, Debian!</title>
4393 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4394 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4395 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4396 <description>&lt;p&gt;I dag fyller
4397 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4398 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4399 si gratulerer med dagen, Debian!&lt;/p&gt;
4400 </description>
4401 </item>
4402
4403 <item>
4404 <title>Song book for Computer Scientists</title>
4405 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4406 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4407 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4408 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4409 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4410 collecting computer related songs for use at parties. The original
4411 version was written in LaTeX, but a few years ago I got help from
4412 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4413 while keeping the ability to create a nice book in PDF format. I have
4414 not had time to maintain the book for a while now, and guess I should
4415 put it up on some public version control repository where others can
4416 help me extend and update the book. If anyone is volunteering to help
4417 me with this, send me an email. Also let me know if there are songs
4418 missing in my book.&lt;/p&gt;
4419
4420 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4421 me today that I really should let all my readers share the joys of
4422 singing out load about programming, computers and computer networks.
4423 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4424 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4425 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4426 Computer Science Songbook&lt;/a&gt;.
4427 </description>
4428 </item>
4429
4430 <item>
4431 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4432 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4433 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4434 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4435 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4436 around 1000 at the moment. To be able to get help from the vendors
4437 when something go wrong, we want to keep the firmware on the servers
4438 up to date. If the firmware isn&#39;t the latest and greatest, the
4439 vendors typically refuse to start debugging any problems until the
4440 firmware is upgraded. So before every reboot, we want to upgrade the
4441 firmware, and we would really like everyone handling servers at the
4442 university to do this themselves when they plan to reboot a machine.
4443 For that to happen we at the unix server admin group need to provide
4444 the tools to do so.&lt;/p&gt;
4445
4446 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4447 fetch and install the latest firmware for the servers we got. Most of
4448 our hardware are from Dell and HP, so I have focused on these servers
4449 so far. This blog post is about the Dell part.&lt;/P&gt;
4450
4451 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4452 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4453 with firmware information for all 11th generation servers, listing
4454 which firmware should be used on a given model and where on the FTP
4455 site I can find it. Using a simple perl XML parser I can then
4456 download the shell scripts Dell provides to do firmware upgrades from
4457 within Linux and reboot when all the firmware is primed and ready to
4458 be activated on the first reboot.&lt;/p&gt;
4459
4460 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4461 Are there anyone working on similar tools for firmware upgrading all
4462 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4463
4464 &lt;p&gt;&lt;pre&gt;
4465 #!/usr/bin/perl
4466 use strict;
4467 use warnings;
4468 use File::Temp qw(tempdir);
4469 BEGIN {
4470 # Install needed RHEL packages if missing
4471 my %rhelmodules = (
4472 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4473 );
4474 for my $module (keys %rhelmodules) {
4475 eval &quot;use $module;&quot;;
4476 if ($@) {
4477 my $pkg = $rhelmodules{$module};
4478 system(&quot;yum install -y $pkg&quot;);
4479 eval &quot;use $module;&quot;;
4480 }
4481 }
4482 }
4483 my $errorsto = &#39;pere@hungry.com&#39;;
4484
4485 upgrade_dell();
4486
4487 exit 0;
4488
4489 sub run_firmware_script {
4490 my ($opts, $script) = @_;
4491 unless ($script) {
4492 print STDERR &quot;fail: missing script name\n&quot;;
4493 exit 1
4494 }
4495 print STDERR &quot;Running $script\n\n&quot;;
4496
4497 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4498 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4499 } else {
4500 print STDERR &quot;fail: firmware script returned error\n&quot;;
4501 }
4502 }
4503
4504 sub run_firmware_scripts {
4505 my ($opts, @dirs) = @_;
4506 # Run firmware packages
4507 for my $dir (@dirs) {
4508 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4509 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4510 while (my $s = readdir $dh) {
4511 next if $s =~ m/^\.\.?/;
4512 run_firmware_script($opts, &quot;$dir/$s&quot;);
4513 }
4514 closedir $dh;
4515 }
4516 }
4517
4518 sub download {
4519 my $url = shift;
4520 print STDERR &quot;info: Downloading $url\n&quot;;
4521 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4522 }
4523
4524 sub upgrade_dell {
4525 my @dirs;
4526 my $product = `dmidecode -s system-product-name`;
4527 chomp $product;
4528
4529 if ($product =~ m/PowerEdge/) {
4530
4531 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4532 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4533
4534 my $tmpdir = tempdir(
4535 CLEANUP =&gt; 1
4536 );
4537 chdir($tmpdir);
4538 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4539 system(&#39;gunzip Catalog.xml.gz&#39;);
4540 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4541 # -q is quiet, disabling interactivity and reducing console output
4542 my $fwopts = &quot;-q&quot;;
4543 if (@paths) {
4544 for my $url (@paths) {
4545 fetch_dell_fw($url);
4546 }
4547 run_firmware_scripts($fwopts, $tmpdir);
4548 } else {
4549 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4550 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4551 }
4552 chdir(&#39;/&#39;);
4553 } else {
4554 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4555 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4556 }
4557 }
4558
4559 sub fetch_dell_fw {
4560 my $path = shift;
4561 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4562 download($url);
4563 }
4564
4565 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4566 # firmware packages to download from Dell. Only work for Linux
4567 # machines and 11th generation Dell servers.
4568 sub fetch_dell_fw_list {
4569 my $filename = shift;
4570
4571 my $product = `dmidecode -s system-product-name`;
4572 chomp $product;
4573 my ($mybrand, $mymodel) = split(/\s+/, $product);
4574
4575 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4576
4577 my $xml = XMLin($filename);
4578 my @paths;
4579 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4580 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4581 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4582 my $oscode;
4583 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4584 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4585 } else {
4586 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4587 }
4588 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4589 {
4590 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4591 }
4592 }
4593 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4594 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4595
4596 # Drop application packages, only firmware and BIOS
4597 next if &#39;APAC&#39; eq $componenttype;
4598
4599 my $cpath = $component-&gt;{path};
4600 for my $path (@paths) {
4601 if ($cpath =~ m%/$path$%) {
4602 push(@paths, $cpath);
4603 }
4604 }
4605 }
4606 return @paths;
4607 }
4608 &lt;/pre&gt;
4609
4610 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4611 it could work on other platforms with some tweaking. Anyone know a
4612 index like Catalog.xml is available from HP for HP servers? At the
4613 moment I maintain a similar list manually and it is quickly getting
4614 outdated.&lt;/p&gt;
4615 </description>
4616 </item>
4617
4618 <item>
4619 <title>How is booting into runlevel 1 different from single user boots?</title>
4620 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4621 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4622 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4623 <description>&lt;p&gt;Wouter Verhelst have some
4624 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4625 comments and opinions&lt;/a&gt; on my blog post on
4626 &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
4627 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4628 &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
4629 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4630 small piece of his comment now, and though it best to address the
4631 misunderstanding he bring forward:&lt;/p&gt;
4632
4633 &lt;p&gt;&lt;blockquote&gt;
4634 Currently, a system admin has four options: [...] boot to a
4635 single-user system (by adding &#39;single&#39; to the kernel command line;
4636 this runs rcS and rc1 scripts)
4637 &lt;/blockquote&gt;&lt;/p&gt;
4638
4639 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4640 and booting into runlevel 1 is the same. I am not surprised he
4641 believe this, because it would make sense and is a quite sensible
4642 thing to believe. But because the boot in Debian is slightly broken,
4643 runlevel 1 do not work properly and it isn&#39;t the same as single user
4644 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4645 hard to explain.&lt;/p&gt;
4646
4647 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4648 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4649 executed in single user mode is sulogin. Single user mode is a boot
4650 state &quot;between&quot; the runlevels, and when booting into single user mode,
4651 only the scripts in /etc/rcS.d/ are executed before the init process
4652 enters the single user state. When switching to runlevel 1, the state
4653 is in fact not ending in runlevel 1, but it passes through runlevel 1
4654 and end up in the single user mode (see /etc/rc1.d/S03single, which
4655 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4656 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4657 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4658 mode).&lt;/p&gt;
4659
4660 &lt;p&gt;This summary might make it clearer. When booting for the first
4661 time into single user mode, the following commands are executed:
4662 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4663 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4664 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4665 trying to continue after visiting single user mode. Not all services
4666 are started again as they should, causing the machine to end up in an
4667 unpredicatble state. This is why Debian admins recommend rebooting
4668 after visiting single user mode.&lt;/p&gt;
4669
4670 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4671 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4672 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4673 stopped when passing through the scripts in /etc/rc1.d/, and not
4674 started again when switching away from runlevel 1 to the runlevels
4675 2-5. I believe the problem is best fixed by moving all the scripts
4676 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4677 functioning single user mode during boot.&lt;/p&gt;
4678
4679 &lt;p&gt;I have spent several years investigating the Debian boot system,
4680 and discovered this problem a few years ago. I suspect it originates
4681 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4682 </description>
4683 </item>
4684
4685 <item>
4686 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4687 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4688 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4689 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4690 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4691 are started from /etc/rcS.d/. In fact, there is a bite more of them
4692 than make sense, and this causes a few problems. What kind of
4693 problems, you might ask. There are at least two problems. The first
4694 is that it is not possible to recover a machine after switching to
4695 runlevel 1. One need to actually reboot to get the machine back to
4696 the expected state. The other is that single user boot will sometimes
4697 run into problems because some of the subsystems are activated before
4698 the root login is presented, causing problems when trying to recover a
4699 machine from a problem in that subsystem. A minor additional point is
4700 that moving more scripts out of rcS.d/ and into the other rc#.d/
4701 directories will increase the amount of scripts that can run in
4702 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4703
4704 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4705 scripts that _have_ to execute before the root login prompt is
4706 presented during a single user boot should go there. Everything else
4707 should go into the numeric runlevels. This means things like
4708 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4709 the numeric runlevels. Today in Debian, there are around 115 init.d
4710 scripts that are started from rcS.d/, and most of them should be moved
4711 out. Do your package have one of them? Please help us make single
4712 user and runlevel 1 better by moving it.&lt;/p&gt;
4713
4714 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4715 etc. should still be started from rcS.d/, but there is for example no
4716 need to have the network enabled before the single user login prompt
4717 is presented.&lt;/p&gt;
4718
4719 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4720 Debian systems working while scripts migrate and during upgrades, the
4721 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4722 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4723 and the next ones can only be moved when their dependencies have been
4724 moved first. This migration must be done sequentially while we ensure
4725 that the package system upgrade packages in the right order to keep
4726 the system state correct. This will require some coordination when it
4727 comes to network related packages, but most of the packages with
4728 scripts that should migrate do not have anything in rcS.d/ depending
4729 on them. Some packages have already been updated, like the sudo
4730 package, while others are still left to do. I wish I had time to work
4731 on this myself, but real live constrains make it unlikely that I will
4732 find time to push this forward.&lt;/p&gt;
4733 </description>
4734 </item>
4735
4736 <item>
4737 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4738 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4739 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4740 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4741 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4742 mentioned the issues I believe should be improved in Debian for its
4743 desktop to be useful for more people. The use case for this is my
4744 parents, which are currently running Kubuntu which solve the
4745 issues.&lt;/p&gt;
4746
4747 &lt;p&gt;I suspect these four missing features are not very hard to
4748 implement. After all, they are present in Ubuntu, so if we wanted to
4749 do this in Debian we would have a source.&lt;/p&gt;
4750
4751 &lt;ol&gt;
4752
4753 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4754 are new packages available for upgrades, a icon in the KDE status bar
4755 indicate this, and clicking on it will activate the simple upgrade
4756 tool to handle it. I have no problem guiding both of my parents
4757 through the process over the phone. If a kernel reboot is required,
4758 this too is indicated by the status bars and the upgrade tool. Last
4759 time I checked, nothing with the same features was working in KDE in
4760 Debian.&lt;/li&gt;
4761
4762 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4763 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4764 currently have a handler for, it will ask the user if the system
4765 should search for a package that would add support for this MIME type,
4766 and if the user say yes, the APT sources will be searched for packages
4767 advertising the MIME type in their control file (visible in the
4768 Packages file in the APT archive). If one or more packages are found,
4769 it is a simple click of the mouse to add support for the missing mime
4770 type. If the package require the user to accept some non-free
4771 license, this is explained to the user. The entire process make it
4772 more clear to the user why something do not work in the browser, and
4773 make the chances higher for the user to blame the web page authors and
4774 not the browser for any missing features.&lt;/li&gt;
4775
4776 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4777 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4778 it is not supporting, a dialog pop up asking the user if the system
4779 should search for a package that would add support for it. This
4780 happen with things like MP3, Windows Media or H.264. The selection
4781 and installation procedure is very similar to the Firefox browser
4782 plugin handling. This is as far as I know implemented using a
4783 gstreamer hook. The end result is that the user easily get access to
4784 the codecs that are present from the APT archives available, while
4785 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4786
4787 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4788 displaying a text/plain file in my Debian browser, it will propose to
4789 start emacs to show it. If I remember correctly, when doing the same
4790 in Kunbutu it show the file as a text file in the browser. At least I
4791 know Opera will show text files within the browser. I much prefer the
4792 latter behaviour.&lt;/li&gt;
4793
4794 &lt;/ol&gt;
4795
4796 &lt;p&gt;There are other nice features as well, like the simplified suite
4797 upgrader, but given that I am the one mostly doing the dist-upgrade,
4798 it do not matter much.&lt;/p&gt;
4799
4800 &lt;p&gt;I really hope we could get these features in place for the next
4801 Debian release. It would require the coordinated effort of several
4802 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4803 </description>
4804 </item>
4805
4806 <item>
4807 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4808 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4809 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4810 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4811 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4812 site is build on Debian/Squeeze, and this platform was chosen because
4813 I am most familiar with Debian (being a Debian Developer for around 10
4814 years) because it is the latest stable Debian release which should get
4815 security support for a few years.&lt;/p&gt;
4816
4817 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4818 that are missing in Debian at the moment. It would be great if these
4819 modules were added to the Debian archive, allowing anyone to set up
4820 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4821 in their own country using only Debian packages. The list of modules
4822 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4823 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4824 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4825 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4826 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4827 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4828 easier in the future.&lt;/p&gt;
4829
4830 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4831 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4832 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4833 with the responsibility of tracking security problems, which I really
4834 do not have time for.&lt;/p&gt;
4835 </description>
4836 </item>
4837
4838 <item>
4839 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4840 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4841 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4842 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4843 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4844 posts have been in Norwegian the last few weeks, so here is a short
4845 update in English.&lt;/p&gt;
4846
4847 &lt;p&gt;The kids still keep me too busy to get much free software work
4848 done, but I did manage to organise a project to get a Norwegian port
4849 of the British service
4850 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4851 and it has been running for a month now. The entire project has been
4852 organised by me and two others. Around Christmas we gathered sponsors
4853 to fund the development work. In January I drafted a contract with
4854 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4855 and in February the development took place. Most of it involved
4856 converting the source to use GPS coordinates instead of British
4857 easting/northing, and the resulting code should be a lot easier to get
4858 running in any country by now. The Norwegian
4859 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4860 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4861 source and the source for administrative borders in Norway, and
4862 support for this had to be added/fixed.&lt;/p&gt;
4863
4864 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4865 polishing the system before we announced it March 7th. The system is
4866 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4867 problem reports in a few weeks. Soon we hope to announce the Android
4868 and iPhone versions making it even easier to report problems with the
4869 public infrastructure.&lt;/p&gt;
4870
4871 &lt;p&gt;Perhaps something to consider for those of you in countries without
4872 such service?&lt;/p&gt;
4873 </description>
4874 </item>
4875
4876 <item>
4877 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4878 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4879 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4880 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4881 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4882 issues here at my work with the University of Oslo. My idea is that
4883 it should be possible to use the information about security issues
4884 available on the Internet, and check our locally
4885 maintained/distributed software against this information. It should
4886 allow us to verify that no known security issues are forgotten. The
4887 CVE database listing vulnerabilities seem like a great central point,
4888 and by using the package lists from Debian mapped to CVEs provided by
4889 the testing security team, I believed it should be possible to figure
4890 out which security holes were present in our free software
4891 collection.&lt;/p&gt;
4892
4893 &lt;p&gt;After reading up on the topic, it became obvious that the first
4894 building block is to be able to name software packages in a unique and
4895 consistent way across data sources. I considered several ways to do
4896 this, for example coming up with my own naming scheme like using URLs
4897 to project home pages or URLs to the Freshmeat entries, or using some
4898 existing naming scheme. And it seem like I am not the first one to
4899 come across this problem, as MITRE already proposed and implemented a
4900 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4901 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4902 software, hardware and other platform components. The CPE ids are
4903 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4904 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4905 issues for any CPE name. With this in place, all I need to do is to
4906 locate the CPE id for the software packages we use at the university.
4907 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4908 NVD entry if a CVE for the package exist).&lt;/p&gt;
4909
4910 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4911 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4912 check out, one could look up
4913 &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
4914 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4915 The most recent one is
4916 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4917 and at the bottom of the NVD page for this vulnerability the complete
4918 list of affected versions is provided.&lt;/p&gt;
4919
4920 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4921 for offline processing of issues. Using this dump, I&#39;ve written a
4922 small script taking a list of CPEs as input and list all CVEs
4923 affecting the packages represented by these CPEs. One give it CPEs
4924 with version numbers as specified above and get a list of open
4925 security issues out.&lt;/p&gt;
4926
4927 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4928 information need to be high. For that to happen, I believe as many as
4929 possible need to use and contribute to the NVD database. I notice
4930 RHEL is providing
4931 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4932 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4933 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4934
4935 &lt;p&gt;To get an idea about the quality for free software, I spent some
4936 time making it possible to compare the CVE database from Debian with
4937 the CVE database in NVD. The result look fairly good, but there are
4938 some inconsistencies in NVD (same software package having several
4939 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4940 Debian believe are affected by a CVE). Hope to find time to improve
4941 the quality of NVD, but that require being able to get in touch with
4942 someone maintaining it. So far my three emails with questions and
4943 corrections have not seen any reply, but I hope contact can be
4944 established soon.&lt;/p&gt;
4945
4946 &lt;p&gt;An interesting application for CPEs is cross platform package
4947 mapping. It would be useful to know which packages in for example
4948 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4949 this would be trivial if all linux distributions provided CPE entries
4950 for their packages.&lt;/p&gt;
4951 </description>
4952 </item>
4953
4954 <item>
4955 <title>Which module is loaded for a given PCI and USB device?</title>
4956 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4957 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4958 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4959 <description>&lt;p&gt;In the
4960 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4961 package in Debian, there is a script to report useful information
4962 about the running hardware for use when people report missing
4963 information. One part of this script that I find very useful when
4964 debugging hardware problems, is the part mapping loaded kernel module
4965 to the PCI device it claims. It allow me to quickly see if the kernel
4966 module I expect is driving the hardware I am struggling with. To see
4967 the output, make sure discover-data is installed and run
4968 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4969 one of my machines like this:&lt;/p&gt;
4970
4971 &lt;pre&gt;
4972 loaded modules:
4973 10de:03eb i2c_nforce2
4974 10de:03f1 ohci_hcd
4975 10de:03f2 ehci_hcd
4976 10de:03f0 snd_hda_intel
4977 10de:03ec pata_amd
4978 10de:03f6 sata_nv
4979 1022:1103 k8temp
4980 109e:036e bttv
4981 109e:0878 snd_bt87x
4982 11ab:4364 sky2
4983 &lt;/pre&gt;
4984
4985 &lt;p&gt;The code in question look like this, slightly modified for
4986 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4987
4988 &lt;pre&gt;
4989 if [ -d /sys/bus/pci/devices/ ] ; then
4990 echo loaded pci modules:
4991 (
4992 cd /sys/bus/pci/devices/
4993 for address in * ; do
4994 if [ -d &quot;$address/driver/module&quot; ] ; then
4995 module=`cd $address/driver/module ; pwd -P | xargs basename`
4996 if grep -q &quot;^$module &quot; /proc/modules ; then
4997 address=$(echo $address |sed s/0000://)
4998 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4999 echo &quot;$id $module&quot;
5000 fi
5001 fi
5002 done
5003 )
5004 echo
5005 fi
5006 &lt;/pre&gt;
5007
5008 &lt;p&gt;Similar code could be used to extract USB device module
5009 mappings:&lt;/p&gt;
5010
5011 &lt;pre&gt;
5012 if [ -d /sys/bus/usb/devices/ ] ; then
5013 echo loaded usb modules:
5014 (
5015 cd /sys/bus/usb/devices/
5016 for address in * ; do
5017 if [ -d &quot;$address/driver/module&quot; ] ; then
5018 module=`cd $address/driver/module ; pwd -P | xargs basename`
5019 if grep -q &quot;^$module &quot; /proc/modules ; then
5020 address=$(echo $address |sed s/0000://)
5021 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5022 if [ &quot;$id&quot; ] ; then
5023 echo &quot;$id $module&quot;
5024 fi
5025 fi
5026 fi
5027 done
5028 )
5029 echo
5030 fi
5031 &lt;/pre&gt;
5032
5033 &lt;p&gt;This might perhaps be something to include in other tools as
5034 well.&lt;/p&gt;
5035 </description>
5036 </item>
5037
5038 <item>
5039 <title>How to test if a laptop is working with Linux</title>
5040 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5041 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5042 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5043 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5044 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5045 batch of computers will work with Linux. Every year for the last few
5046 years the university have organised shared bid of a few thousand
5047 computers, and this year HP won the bid. Two different desktops and
5048 five different laptops are on the list this year. We in the UNIX
5049 group want to know which one of these computers work well with RHEL
5050 and Ubuntu, the two Linux distributions we currently handle at the
5051 university.&lt;/p&gt;
5052
5053 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5054 perhaps inspire others to test hardware as well. To test, I PXE
5055 install the OS version of choice, and log in as my normal user and run
5056 a few applications and plug in selected pieces of hardware. When
5057 something fail, I make a note about this in the test matrix and move
5058 on. If I have some spare time I try to report the bug to the OS
5059 vendor, but as I only have the machines for a short time, I rarely
5060 have the time to do this for all the problems I find.&lt;/p&gt;
5061
5062 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5063 I perform on a new model.&lt;/p&gt;
5064
5065 &lt;ul&gt;
5066
5067 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5068 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5069 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5070
5071 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5072 installation, X.org is working.&lt;/li&gt;
5073
5074 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5075 package mesa-utils on Ubuntu) and writing down the frames per second
5076 reported by the program.&lt;/li&gt;
5077
5078 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5079 logging in, and if I can hear this the test is successful. If there
5080 are several audio exits on the machine, I try them all and check if
5081 the Gnome/KDE audio mixer can control where to send the sound. I
5082 normally test this by playing
5083 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5084 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5085
5086 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5087 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5088
5089 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5090 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5091
5092 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5093 picture from the v4l device show up.&lt;/li&gt;
5094
5095 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5096 any bluetooth devices are discovered. In my office, I normally see a
5097 few.&lt;/li&gt;
5098
5099 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5100 memory modules lying around, and stick them in and see if Gnome/KDE
5101 notice this.&lt;/li&gt;
5102
5103 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5104 special button work, and if the laptop continue to work after
5105 resume.&lt;/li&gt;
5106
5107 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5108 adjusting background light, switching on/off external video output,
5109 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5110 laptop to laptop, so I just write down which are working and which are
5111 not.&lt;/li&gt;
5112
5113 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5114 acceleration sensors etc. I rarely test these, as I do not know how
5115 to quickly test if they are working or not, so I only document their
5116 existence.&lt;/li&gt;
5117
5118 &lt;/ul&gt;
5119
5120 &lt;p&gt;By now I suspect you are really curious what the test results are
5121 for the HP machines I am testing. I&#39;m not done yet, so I will report
5122 the test results later. For now I can report that HP 8100 Elite work
5123 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5124 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5125 can see, I have most machines left to test. One interesting
5126 observation is that Ubuntu Lucid has almost twice the frame rate than
5127 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5128 </description>
5129 </item>
5130
5131 <item>
5132 <title>Some thoughts on BitCoins</title>
5133 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5134 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5135 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5136 <description>&lt;p&gt;As I continue to explore
5137 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5138 what properties the system have, and how it will be affected by laws
5139 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5140
5141 &lt;p&gt;One interesting thing to note is that since the transactions are
5142 verified using a peer to peer network, all details about a transaction
5143 is known to everyone. This means that if a BitCoin address has been
5144 published like I did with mine in my initial post about BitCoin, it is
5145 possible for everyone to see how many BitCoins have been transfered to
5146 that address. There is even a web service to look at the details for
5147 all transactions. There I can see that my address
5148 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5149 have received 16.06 Bitcoin, the
5150 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5151 address of Simon Phipps have received 181.97 BitCoin and the address
5152 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5153 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5154 every one of you that donated bitcoins to support my activity. The
5155 fact that anyone can see how much money was transfered to a given
5156 address make it more obvious why the BitCoin community recommend to
5157 generate and hand out a new address for each transaction. I&#39;m told
5158 there is no way to track which addresses belong to a given person or
5159 organisation without the person or organisation revealing it
5160 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5161
5162 &lt;p&gt;In Norway, and in most other countries, there are laws and
5163 regulations limiting how much money one can transfer across the border
5164 without declaring it. There are money laundering, tax and accounting
5165 laws and regulations I would expect to apply to the use of BitCoin.
5166 If the Skolelinux foundation
5167 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5168 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5169 normal bank transfers like EFF is doing, how should this be accounted?
5170 Given that it is impossible to know if money can cross the border or
5171 not, should everything or nothing be declared? What exchange rate
5172 should be used when calculating taxes? Would receivers have to pay
5173 income tax if the foundation were to pay Skolelinux contributors in
5174 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5175
5176 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5177 accepted by a lot of users. It must be possible to get easy access to
5178 the currency (as a wage or using currency exchanges), and it must be
5179 easy to spend it. At the moment BitCoin seem fairly easy to get
5180 access to, but there are very few places to spend it. I am not really
5181 a regular user of any of the vendor types currently accepting BitCoin,
5182 so I wonder when my kind of shop would start accepting BitCoins. I
5183 would like to buy electronics, travels and subway tickets, not herbs
5184 and books. :) The currency is young, and this will improve over time
5185 if it become popular, but I suspect regular banks will start to lobby
5186 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5187 will claim it is helping fund terrorism and money laundering (which
5188 probably would be true, as is any currency in existence), but I
5189 believe the problems should be solved elsewhere and not by blaming
5190 currencies.&lt;/p&gt;
5191
5192 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5193 CPU intensive process that depend on a bit of luck as well (as one is
5194 competing against all the other miners currently spending CPU cycles
5195 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5196 BitCoin when this happen. Yesterday I came across the obvious way to
5197 join forces to increase ones changes of getting at least some coins,
5198 by coordinating the work on mining BitCoins across several machines
5199 and people, and sharing the result if one is lucky and get the 50
5200 BitCoins. Check out
5201 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5202 if this sounds interesting. I have not had time to try to set up a
5203 machine to participate there yet, but have seen that running on ones
5204 own for a few days have not yield any BitCoins througth mining
5205 yet.&lt;/p&gt;
5206
5207 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5208 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5209 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5210 it was interesting to read. The arguments presented seem to be
5211 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5212 </description>
5213 </item>
5214
5215 <item>
5216 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5217 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5218 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5219 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5220 <description>&lt;p&gt;With this weeks lawless
5221 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5222 attacks&lt;/a&gt; on Wikileak and
5223 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5224 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5225 not be trusted to handle money transactions.
5226 A blog post from
5227 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5228 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5229 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5230 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5231 some help from my friend to get it all running, and he even handed me
5232 some bitcoins to get started. I even donated a few bitcoins to Simon
5233 for helping me remember BitCoin.&lt;/p&gt;
5234
5235 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5236 crypto-currency, decentralised and handled using peer-to-peer
5237 networks. It allows anonymous transactions and prohibits central
5238 control over the transactions, making it impossible for governments
5239 and companies alike to block donations and other transactions. The
5240 source is free software, and while the key dependency wxWidgets 2.9
5241 for the graphical user interface is missing in Debian, the command
5242 line client builds just fine. Hopefully Jonas
5243 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5244 Debian&lt;/a&gt; soon.&lt;/p&gt;
5245
5246 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5247 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5248 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5249 currency &quot;stock&quot; markets where the exchange rate is decided. There
5250 are not many users so far, but the concept seems promising. If you
5251 want to get started and lack a friend with any bitcoins to spare,
5252 you can even get
5253 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5254 bitcoin at the time of writing). Use
5255 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5256 on the current exchange rates.&lt;/p&gt;
5257
5258 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5259 machines. If you want to support my activity, please send Bitcoin
5260 donations to the address
5261 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5262 </description>
5263 </item>
5264
5265 <item>
5266 <title>Why isn&#39;t Debian Edu using VLC?</title>
5267 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5268 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5269 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5270 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5271 presented, and the winner among the multimedia player were VLC.
5272 Personally, I like VLC, and it is my player of choice when I first try
5273 to play a video file or stream. Only if VLC fail will I drag out
5274 gmplayer to see if it can do better. The reason is mostly the failure
5275 model and trust. When VLC fail, it normally pop up a error message
5276 reporting the problem. When mplayer fail, it normally segfault or
5277 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5278
5279 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5280 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5281 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5282 plugin to play web videos seamlessly, and the VLC browser plugin is
5283 not very good. For example, it lack in-line control buttons, so there
5284 is no way for the user to pause the video. Also, when I
5285 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5286 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5287 failed on several video pages where mplayer based plugins worked. If
5288 the browser plugin for VLC was as good as the gecko-mediaplayer
5289 package (which uses mplayer), we would switch.&lt;/P&gt;
5290
5291 &lt;p&gt;While VLC is a good player, its user interface is slightly
5292 annoying. The most annoying feature is its inconsistent use of
5293 keyboard shortcuts. When the player is in full screen mode, its
5294 shortcuts are different from when it is playing the video in a window.
5295 For example, space only work as pause when in full screen mode. I
5296 wish it had consisten shortcuts and that space also would work when in
5297 window mode. Another nice shortcut in gmplayer is [enter] to restart
5298 the current video. It is very nice when playing short videos from the
5299 web and want to restart it when new people arrive to have a look at
5300 what is going on.&lt;/p&gt;
5301 </description>
5302 </item>
5303
5304 <item>
5305 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5306 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5307 <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>
5308 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5309 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5310 upgrade testing of the
5311 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5312 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5313 This seem like a very good idea, so I adjusted by test scripts and
5314 can now present the updated result from today:&lt;/p&gt;
5315
5316 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5317
5318 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5319
5320 &lt;blockquote&gt;&lt;p&gt;
5321 apache2.2-bin
5322 aptdaemon
5323 baobab
5324 binfmt-support
5325 browser-plugin-gnash
5326 cheese-common
5327 cli-common
5328 cups-pk-helper
5329 dmz-cursor-theme
5330 empathy
5331 empathy-common
5332 freedesktop-sound-theme
5333 freeglut3
5334 gconf-defaults-service
5335 gdm-themes
5336 gedit-plugins
5337 geoclue
5338 geoclue-hostip
5339 geoclue-localnet
5340 geoclue-manual
5341 geoclue-yahoo
5342 gnash
5343 gnash-common
5344 gnome
5345 gnome-backgrounds
5346 gnome-cards-data
5347 gnome-codec-install
5348 gnome-core
5349 gnome-desktop-environment
5350 gnome-disk-utility
5351 gnome-screenshot
5352 gnome-search-tool
5353 gnome-session-canberra
5354 gnome-system-log
5355 gnome-themes-extras
5356 gnome-themes-more
5357 gnome-user-share
5358 gstreamer0.10-fluendo-mp3
5359 gstreamer0.10-tools
5360 gtk2-engines
5361 gtk2-engines-pixbuf
5362 gtk2-engines-smooth
5363 hamster-applet
5364 libapache2-mod-dnssd
5365 libapr1
5366 libaprutil1
5367 libaprutil1-dbd-sqlite3
5368 libaprutil1-ldap
5369 libart2.0-cil
5370 libboost-date-time1.42.0
5371 libboost-python1.42.0
5372 libboost-thread1.42.0
5373 libchamplain-0.4-0
5374 libchamplain-gtk-0.4-0
5375 libcheese-gtk18
5376 libclutter-gtk-0.10-0
5377 libcryptui0
5378 libdiscid0
5379 libelf1
5380 libepc-1.0-2
5381 libepc-common
5382 libepc-ui-1.0-2
5383 libfreerdp-plugins-standard
5384 libfreerdp0
5385 libgconf2.0-cil
5386 libgdata-common
5387 libgdata7
5388 libgdu-gtk0
5389 libgee2
5390 libgeoclue0
5391 libgexiv2-0
5392 libgif4
5393 libglade2.0-cil
5394 libglib2.0-cil
5395 libgmime2.4-cil
5396 libgnome-vfs2.0-cil
5397 libgnome2.24-cil
5398 libgnomepanel2.24-cil
5399 libgpod-common
5400 libgpod4
5401 libgtk2.0-cil
5402 libgtkglext1
5403 libgtksourceview2.0-common
5404 libmono-addins-gui0.2-cil
5405 libmono-addins0.2-cil
5406 libmono-cairo2.0-cil
5407 libmono-corlib2.0-cil
5408 libmono-i18n-west2.0-cil
5409 libmono-posix2.0-cil
5410 libmono-security2.0-cil
5411 libmono-sharpzip2.84-cil
5412 libmono-system2.0-cil
5413 libmtp8
5414 libmusicbrainz3-6
5415 libndesk-dbus-glib1.0-cil
5416 libndesk-dbus1.0-cil
5417 libopal3.6.8
5418 libpolkit-gtk-1-0
5419 libpt2.6.7
5420 libpython2.6
5421 librpm1
5422 librpmio1
5423 libsdl1.2debian
5424 libsrtp0
5425 libssh-4
5426 libtelepathy-farsight0
5427 libtelepathy-glib0
5428 libtidy-0.99-0
5429 media-player-info
5430 mesa-utils
5431 mono-2.0-gac
5432 mono-gac
5433 mono-runtime
5434 nautilus-sendto
5435 nautilus-sendto-empathy
5436 p7zip-full
5437 pkg-config
5438 python-aptdaemon
5439 python-aptdaemon-gtk
5440 python-axiom
5441 python-beautifulsoup
5442 python-bugbuddy
5443 python-clientform
5444 python-coherence
5445 python-configobj
5446 python-crypto
5447 python-cupshelpers
5448 python-elementtree
5449 python-epsilon
5450 python-evolution
5451 python-feedparser
5452 python-gdata
5453 python-gdbm
5454 python-gst0.10
5455 python-gtkglext1
5456 python-gtksourceview2
5457 python-httplib2
5458 python-louie
5459 python-mako
5460 python-markupsafe
5461 python-mechanize
5462 python-nevow
5463 python-notify
5464 python-opengl
5465 python-openssl
5466 python-pam
5467 python-pkg-resources
5468 python-pyasn1
5469 python-pysqlite2
5470 python-rdflib
5471 python-serial
5472 python-tagpy
5473 python-twisted-bin
5474 python-twisted-conch
5475 python-twisted-core
5476 python-twisted-web
5477 python-utidylib
5478 python-webkit
5479 python-xdg
5480 python-zope.interface
5481 remmina
5482 remmina-plugin-data
5483 remmina-plugin-rdp
5484 remmina-plugin-vnc
5485 rhythmbox-plugin-cdrecorder
5486 rhythmbox-plugins
5487 rpm-common
5488 rpm2cpio
5489 seahorse-plugins
5490 shotwell
5491 software-center
5492 system-config-printer-udev
5493 telepathy-gabble
5494 telepathy-mission-control-5
5495 telepathy-salut
5496 tomboy
5497 totem
5498 totem-coherence
5499 totem-mozilla
5500 totem-plugins
5501 transmission-common
5502 xdg-user-dirs
5503 xdg-user-dirs-gtk
5504 xserver-xephyr
5505 &lt;/p&gt;&lt;/blockquote&gt;
5506
5507 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5508
5509 &lt;blockquote&gt;&lt;p&gt;
5510 cheese
5511 ekiga
5512 eog
5513 epiphany-extensions
5514 evolution-exchange
5515 fast-user-switch-applet
5516 file-roller
5517 gcalctool
5518 gconf-editor
5519 gdm
5520 gedit
5521 gedit-common
5522 gnome-games
5523 gnome-games-data
5524 gnome-nettool
5525 gnome-system-tools
5526 gnome-themes
5527 gnuchess
5528 gucharmap
5529 guile-1.8-libs
5530 libavahi-ui0
5531 libdmx1
5532 libgalago3
5533 libgtk-vnc-1.0-0
5534 libgtksourceview2.0-0
5535 liblircclient0
5536 libsdl1.2debian-alsa
5537 libspeexdsp1
5538 libsvga1
5539 rhythmbox
5540 seahorse
5541 sound-juicer
5542 system-config-printer
5543 totem-common
5544 transmission-gtk
5545 vinagre
5546 vino
5547 &lt;/p&gt;&lt;/blockquote&gt;
5548
5549 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5550
5551 &lt;blockquote&gt;&lt;p&gt;
5552 gstreamer0.10-gnomevfs
5553 &lt;/p&gt;&lt;/blockquote&gt;
5554
5555 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5556
5557 &lt;blockquote&gt;&lt;p&gt;
5558 [nothing]
5559 &lt;/p&gt;&lt;/blockquote&gt;
5560
5561 &lt;p&gt;This is for KDE:&lt;/p&gt;
5562
5563 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5564
5565 &lt;blockquote&gt;&lt;p&gt;
5566 ksmserver
5567 &lt;/p&gt;&lt;/blockquote&gt;
5568
5569 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5570
5571 &lt;blockquote&gt;&lt;p&gt;
5572 kwin
5573 network-manager-kde
5574 &lt;/p&gt;&lt;/blockquote&gt;
5575
5576 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5577
5578 &lt;blockquote&gt;&lt;p&gt;
5579 arts
5580 dolphin
5581 freespacenotifier
5582 google-gadgets-gst
5583 google-gadgets-xul
5584 kappfinder
5585 kcalc
5586 kcharselect
5587 kde-core
5588 kde-plasma-desktop
5589 kde-standard
5590 kde-window-manager
5591 kdeartwork
5592 kdeartwork-emoticons
5593 kdeartwork-style
5594 kdeartwork-theme-icon
5595 kdebase
5596 kdebase-apps
5597 kdebase-workspace
5598 kdebase-workspace-bin
5599 kdebase-workspace-data
5600 kdeeject
5601 kdelibs
5602 kdeplasma-addons
5603 kdeutils
5604 kdewallpapers
5605 kdf
5606 kfloppy
5607 kgpg
5608 khelpcenter4
5609 kinfocenter
5610 konq-plugins-l10n
5611 konqueror-nsplugins
5612 kscreensaver
5613 kscreensaver-xsavers
5614 ktimer
5615 kwrite
5616 libgle3
5617 libkde4-ruby1.8
5618 libkonq5
5619 libkonq5-templates
5620 libnetpbm10
5621 libplasma-ruby
5622 libplasma-ruby1.8
5623 libqt4-ruby1.8
5624 marble-data
5625 marble-plugins
5626 netpbm
5627 nuvola-icon-theme
5628 plasma-dataengines-workspace
5629 plasma-desktop
5630 plasma-desktopthemes-artwork
5631 plasma-runners-addons
5632 plasma-scriptengine-googlegadgets
5633 plasma-scriptengine-python
5634 plasma-scriptengine-qedje
5635 plasma-scriptengine-ruby
5636 plasma-scriptengine-webkit
5637 plasma-scriptengines
5638 plasma-wallpapers-addons
5639 plasma-widget-folderview
5640 plasma-widget-networkmanagement
5641 ruby
5642 sweeper
5643 update-notifier-kde
5644 xscreensaver-data-extra
5645 xscreensaver-gl
5646 xscreensaver-gl-extra
5647 xscreensaver-screensaver-bsod
5648 &lt;/p&gt;&lt;/blockquote&gt;
5649
5650 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5651
5652 &lt;blockquote&gt;&lt;p&gt;
5653 ark
5654 google-gadgets-common
5655 google-gadgets-qt
5656 htdig
5657 kate
5658 kdebase-bin
5659 kdebase-data
5660 kdepasswd
5661 kfind
5662 klipper
5663 konq-plugins
5664 konqueror
5665 ksysguard
5666 ksysguardd
5667 libarchive1
5668 libcln6
5669 libeet1
5670 libeina-svn-06
5671 libggadget-1.0-0b
5672 libggadget-qt-1.0-0b
5673 libgps19
5674 libkdecorations4
5675 libkephal4
5676 libkonq4
5677 libkonqsidebarplugin4a
5678 libkscreensaver5
5679 libksgrd4
5680 libksignalplotter4
5681 libkunitconversion4
5682 libkwineffects1a
5683 libmarblewidget4
5684 libntrack-qt4-1
5685 libntrack0
5686 libplasma-geolocation-interface4
5687 libplasmaclock4a
5688 libplasmagenericshell4
5689 libprocesscore4a
5690 libprocessui4a
5691 libqalculate5
5692 libqedje0a
5693 libqtruby4shared2
5694 libqzion0a
5695 libruby1.8
5696 libscim8c2a
5697 libsmokekdecore4-3
5698 libsmokekdeui4-3
5699 libsmokekfile3
5700 libsmokekhtml3
5701 libsmokekio3
5702 libsmokeknewstuff2-3
5703 libsmokeknewstuff3-3
5704 libsmokekparts3
5705 libsmokektexteditor3
5706 libsmokekutils3
5707 libsmokenepomuk3
5708 libsmokephonon3
5709 libsmokeplasma3
5710 libsmokeqtcore4-3
5711 libsmokeqtdbus4-3
5712 libsmokeqtgui4-3
5713 libsmokeqtnetwork4-3
5714 libsmokeqtopengl4-3
5715 libsmokeqtscript4-3
5716 libsmokeqtsql4-3
5717 libsmokeqtsvg4-3
5718 libsmokeqttest4-3
5719 libsmokeqtuitools4-3
5720 libsmokeqtwebkit4-3
5721 libsmokeqtxml4-3
5722 libsmokesolid3
5723 libsmokesoprano3
5724 libtaskmanager4a
5725 libtidy-0.99-0
5726 libweather-ion4a
5727 libxklavier16
5728 libxxf86misc1
5729 okteta
5730 oxygencursors
5731 plasma-dataengines-addons
5732 plasma-scriptengine-superkaramba
5733 plasma-widget-lancelot
5734 plasma-widgets-addons
5735 plasma-widgets-workspace
5736 polkit-kde-1
5737 ruby1.8
5738 systemsettings
5739 update-notifier-common
5740 &lt;/p&gt;&lt;/blockquote&gt;
5741
5742 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5743 aptitude a bit more similar, but there are still quite a lott of
5744 differences. I have no idea what packages should be installed after
5745 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5746 </description>
5747 </item>
5748
5749 <item>
5750 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5751 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5752 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5753 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5754 <description>&lt;p&gt;Most of the computers in use by the
5755 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5756 are virtual machines. And they have been Xen machines running on a
5757 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5758 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5759 bit harder that it could have been, because we set up the Xen virtual
5760 machines to get the virtual partitions from LVM, which as far as I
5761 know is not supported by KVM. So to migrate, we had to convert
5762 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5763
5764 &lt;p&gt;I found
5765 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5766 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5767 migration. It uses qemu-img from the qemu package to make the disk
5768 image, parted to partition it, losetup and kpartx to present the disk
5769 image partions as devices, and dd to copy the data. I NFS mounted the
5770 new servers storage area on the old server to do the migration.&lt;/p&gt;
5771
5772 &lt;pre&gt;
5773 #!/bin/sh
5774
5775 # Based on
5776 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5777
5778 set -e
5779 set -x
5780
5781 if [ -z &quot;$1&quot; ] ; then
5782 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5783 exit 1
5784 else
5785 host=&quot;$1&quot;
5786 fi
5787
5788 if [ ! -e /dev/vg_data/$host-disk ] ; then
5789 echo &quot;error: unable to find LVM volume for $host&quot;
5790 exit 1
5791 fi
5792
5793 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5794 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5795 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5796 totalsize=$(( ( $disksize + $swapsize ) ))
5797
5798 img=$host.img
5799 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5800 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5801
5802 parted $img mklabel msdos
5803 parted $img mkpart primary linux-swap 0 $disksize
5804 parted $img mkpart primary ext2 $disksize $totalsize
5805 parted $img set 1 boot on
5806
5807 modprobe dm-mod
5808 losetup /dev/loop0 $img
5809 kpartx -a /dev/loop0
5810
5811 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5812 fsck.ext3 -f /dev/mapper/loop0p1 || true
5813 mkswap /dev/mapper/loop0p2
5814
5815 kpartx -d /dev/loop0
5816 losetup -d /dev/loop0
5817 &lt;/pre&gt;
5818
5819 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5820 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5821
5822 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5823 the new disk image attached, installed grub-pc and linux-image-686 and
5824 set up grub to boot from the disk image. After this, the KVM machines
5825 seem to work just fine.&lt;/p&gt;
5826 </description>
5827 </item>
5828
5829 <item>
5830 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5831 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5833 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5834 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5835 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5836 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5837 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5838
5839 &lt;p&gt;I still do not know what a correct migration should look like, so I
5840 report any differences between apt and aptitude and hope someone else
5841 can see if anything should be changed.&lt;/p&gt;
5842
5843 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5844
5845 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5846
5847 &lt;blockquote&gt;&lt;p&gt;
5848 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5849 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5850 dmz-cursor-theme empathy empathy-common finger
5851 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5852 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5853 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5854 gnome-cards-data gnome-codec-install gnome-core
5855 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5856 gnome-search-tool gnome-session-canberra gnome-spell
5857 gnome-system-log gnome-themes-extras gnome-themes-more
5858 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5859 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5860 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5861 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5862 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5863 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5864 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5865 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5866 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5867 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5868 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5869 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5870 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5871 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5872 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5873 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5874 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5875 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5876 libmono-security2.0-cil libmono-sharpzip2.84-cil
5877 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5878 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5879 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5880 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5881 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5882 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5883 libxalan2-java libxerces2-java media-player-info mesa-utils
5884 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5885 nautilus-sendto-empathy openoffice.org-writer2latex
5886 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5887 python-aptdaemon python-aptdaemon-gtk python-axiom
5888 python-beautifulsoup python-bugbuddy python-clientform
5889 python-coherence python-configobj python-crypto python-cupshelpers
5890 python-cupsutils python-eggtrayicon python-elementtree
5891 python-epsilon python-evolution python-feedparser python-gdata
5892 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5893 python-gtksourceview2 python-httplib2 python-louie python-mako
5894 python-markupsafe python-mechanize python-nevow python-notify
5895 python-opengl python-openssl python-pam python-pkg-resources
5896 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5897 python-tagpy python-twisted-bin python-twisted-conch
5898 python-twisted-core python-twisted-web python-utidylib python-webkit
5899 python-xdg python-zope.interface remmina remmina-plugin-data
5900 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5901 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5902 software-center svgalibg1 system-config-printer-udev
5903 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5904 totem totem-coherence totem-mozilla totem-plugins
5905 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5906 zip
5907 &lt;/p&gt;&lt;/blockquote&gt;
5908
5909 Installed using apt-get, removed with aptitude
5910
5911 &lt;blockquote&gt;&lt;p&gt;
5912 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5913 epiphany-extensions epiphany-gecko evolution-exchange
5914 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5915 gedit-common gnome-app-install gnome-games gnome-games-data
5916 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5917 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5918 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5919 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5920 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5921 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5922 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5923 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5924 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5925 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5926 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5927 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5928 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5929 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5930 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5931 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5932 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5933 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5934 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5935 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5936 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5937 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5938 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5939 sound-juicer swfdec-gnome system-config-printer totem-common
5940 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5941 &lt;/p&gt;&lt;/blockquote&gt;
5942
5943 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5944
5945 &lt;blockquote&gt;&lt;p&gt;
5946 gstreamer0.10-gnomevfs
5947 &lt;/p&gt;&lt;/blockquote&gt;
5948
5949 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5950
5951 &lt;blockquote&gt;&lt;p&gt;
5952 [nothing]
5953 &lt;/p&gt;&lt;/blockquote&gt;
5954
5955 &lt;p&gt;This is for KDE:&lt;/p&gt;
5956
5957 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5958
5959 &lt;blockquote&gt;&lt;p&gt;
5960 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5961 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5962 ghostscript-x git gnome-audio gnugo granatier gs-common
5963 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5964 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5965 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5966 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5967 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5968 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5969 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5970 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5971 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5972 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5973 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5974 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5975 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5976 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5977 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5978 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5979 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5980 libkrossui4 libmailtools-perl libmime-tools-perl
5981 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5982 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5983 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5984 lirc luatex marble networkstatus noatun-plugins
5985 openoffice.org-writer2latex palapeli palapeli-data parley
5986 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5987 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5988 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5989 ttf-sazanami-gothic
5990 &lt;/p&gt;&lt;/blockquote&gt;
5991
5992 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5993
5994 &lt;blockquote&gt;&lt;p&gt;
5995 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5996 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5997 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5998 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5999 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6000 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6001 kitchensync kiten kjumpingcube klatin klettres klickety klines
6002 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6003 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6004 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6005 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6006 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6007 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6008 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6009 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6010 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6011 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6012 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6013 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6014 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6015 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6016 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6017 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6018 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6019 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6020 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6021 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6022 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6023 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6024 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6025 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6026 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6027 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6028 &lt;/p&gt;&lt;/blockquote&gt;
6029
6030 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6031
6032 &lt;blockquote&gt;&lt;p&gt;
6033 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6034 kdeartwork kdebase kdebase-apps kdebase-workspace
6035 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6036 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6037 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6038 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6039 xscreensaver-screensaver-bsod
6040 &lt;/p&gt;&lt;/blockquote&gt;
6041
6042 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6043
6044 &lt;blockquote&gt;&lt;p&gt;
6045 kdebase-bin konq-plugins konqueror
6046 &lt;/p&gt;&lt;/blockquote&gt;
6047 </description>
6048 </item>
6049
6050 <item>
6051 <title>Gnash buildbot slave and Debian kfreebsd</title>
6052 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6053 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6054 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6055 <description>&lt;p&gt;Answering
6056 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6057 call from the Gnash project&lt;/a&gt; for
6058 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6059 current source, I have set up a virtual KVM machine on the Debian
6060 Edu/Skolelinux virtualization host to test the git source on
6061 Debian/Squeeze. I hope this can help the developers in getting new
6062 releases out more often.&lt;/p&gt;
6063
6064 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6065 I have considered setting up a &lt;a
6066 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6067 machine as well. I have also considered using the kfreebsd
6068 architecture in Debian as a file server in NUUG to get access to the 5
6069 TB zfs volume we currently use to store DV video. Because of this, I
6070 finally got around to do a test installation of Debian/Squeeze with
6071 kfreebsd. Installation went fairly smooth, thought I noticed some
6072 visual glitches in the cdebconf dialogs (black cursor left on the
6073 screen at random locations). Have not gotten very far with the
6074 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6075 fatal problem. Have to spend some more time on it to see if it is
6076 useful as a file server for NUUG. Will try to find time to set up a
6077 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6078 </description>
6079 </item>
6080
6081 <item>
6082 <title>Debian in 3D</title>
6083 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6084 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6085 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6086 <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;
6087
6088 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6089 3D linked in from
6090 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6091 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6092 </description>
6093 </item>
6094
6095 <item>
6096 <title>Software updates 2010-10-24</title>
6097 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6098 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6099 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6100 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6101
6102 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6103 raise money for the project is going well. The lower limit of 10
6104 signers was reached in 24 hours, and so far 13 people have signed it.
6105 More signers and more funding is most welcome, and I am really curious
6106 how far we can get before the time limit of December 24 is reached.
6107 :)&lt;/p&gt;
6108
6109 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6110 about what appear to be a great code coverage tool capable of
6111 generating code coverage stats without any changes to the source code.
6112 It is called
6113 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6114 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6115 It is missing in Debian, but the git source built just fine in Squeeze
6116 after I installed libelf-dev, libdwarf-dev, pkg-config and
6117 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6118 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6119
6120 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6121 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6122 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6123 alpha test release of the Squeeze based Debian Edu /
6124 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6125 release. Give it a try if you need a complete linux solution for your
6126 school, including central infrastructure server, workstations, thin
6127 client servers and diskless workstations. A nice touch added
6128 yesterday is RDP support on the thin client servers, for windows
6129 clients to get a Linux desktop on request.&lt;/p&gt;
6130 </description>
6131 </item>
6132
6133 <item>
6134 <title>Some notes on Flash in Debian and Debian Edu</title>
6135 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6136 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6137 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6138 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6139 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6140 second most popular used package that is missing in Debian. The sixth
6141 most popular is flashplayer-mozilla. This is a clear indication that
6142 working flash is important for Debian users. Around 10 percent of the
6143 users submitting data to popcon.debian.org have this package
6144 installed.&lt;/p&gt;
6145
6146 &lt;p&gt;In the report written by Lars Risan in August 2008
6147&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
6148 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6149 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6150 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6151 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6152 web sites require Flash to work, and lacking working Flash support in
6153 the web browser and the problems with installing it was perceived as a
6154 good reason to stay with Windows.&lt;/p&gt;
6155
6156 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6157 said to be the retarded cousin that did not really understand
6158 everything you told him but could work fairly well. This was a
6159 comment regarding the problems Linux have with proprietary formats and
6160 non-standard web pages, and is sad because it exposes a fairly common
6161 understanding of whose fault it is if web pages that only work in for
6162 example Internet Explorer 6 fail to work on Firefox, and funny because
6163 it explain very well how annoying it is for users when Linux
6164 distributions do not work with the documents they receive or the web
6165 pages they want to visit.&lt;/p&gt;
6166
6167 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6168 and Debian Edu to have a well working Flash implementation in the
6169 distribution, to get at least popular sites as Youtube and Google
6170 Video to working out of the box. For Squeeze, Debian have the chance
6171 to include the latest version of Gnash that will make this happen, as
6172 the new release 0.8.8 was published a few weeks ago and is resting in
6173 unstable. The new version work with more sites that version 0.8.7.
6174 The Gnash maintainers have asked for a freeze exception, but the
6175 release team have not had time to reply to it yet. I hope they agree
6176 with me that Flash is important for the Debian desktop users, and thus
6177 accept the new package into Squeeze.&lt;/p&gt;
6178 </description>
6179 </item>
6180
6181 <item>
6182 <title>Circular package dependencies harms apt recovery</title>
6183 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6185 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6186 <description>&lt;p&gt;I discovered this while doing
6187 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6188 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6189 in Debian still got circular dependencies, and it is often claimed
6190 that apt and aptitude should be able to handle this just fine, but
6191 some times these dependency loops causes apt to fail.&lt;/p&gt;
6192
6193 &lt;p&gt;An example is from todays
6194 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6195 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6196 causes perl-modules to fail to upgrade. The cause is simple. If a
6197 package fail to unpack, then only part of packages with the circular
6198 dependency might end up being unpacked when unpacking aborts, and the
6199 ones already unpacked will fail to configure in the recovery phase
6200 because its dependencies are unavailable.&lt;/p&gt;
6201
6202 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6203
6204 &lt;blockquote&gt;&lt;pre&gt;
6205 dpkg: dependency problems prevent configuration of perl-modules:
6206 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6207 Version of perl on system is 5.10.0-19lenny2.
6208 dpkg: error processing perl-modules (--configure):
6209 dependency problems - leaving unconfigured
6210 &lt;/pre&gt;&lt;/blockquote&gt;
6211
6212 &lt;p&gt;The perl/perl-modules circular dependency is already
6213 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6214 hopefully be solved as soon as possible, but it is not the only one,
6215 and each one of these loops in the dependency tree can cause similar
6216 failures. Of course, they only occur when there are bugs in other
6217 packages causing the unpacking to fail, but it is rather nasty when
6218 the failure of one package causes the problem to become worse because
6219 of dependency loops.&lt;/p&gt;
6220
6221 &lt;p&gt;Thanks to
6222 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6223 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6224 dependencies
6225 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6226 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6227
6228 &lt;p&gt;Todays testing also exposed a bug in
6229 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6230 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6231 apt-get and aptitude, the latter possibly caused by some circular
6232 dependency. Reported both to BTS to try to get someone to look at
6233 it.&lt;/p&gt;
6234 </description>
6235 </item>
6236
6237 <item>
6238 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6239 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6241 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6242 <description>&lt;p&gt;This is a
6243 &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;
6244 on my
6245 &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
6246 work&lt;/a&gt; on
6247 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6248 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6249
6250 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6251 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6252 and dhcp3-server-ldap in Debian use the LDAP server. The two
6253 implementations are quite different in how they use LDAP.&lt;/p&gt;
6254
6255 To get this information, I started slapd with debugging enabled and
6256 dumped the debug output to a file to get the LDAP searches performed
6257 on a Debian Edu main-server. Here is a summary.
6258
6259 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6260
6261 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6262 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6263 the web.
6264
6265 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6266 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6267 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6268 reverse entries are in two different subtrees in LDAP with a structure
6269 based on the DNS names, as in tjener.intern and
6270 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6271
6272 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6273 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6274 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6275 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6276 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6277 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6278 forward entries, it is looking for attributes named dnsttl, arecord,
6279 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6280 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6281 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6282 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6283 spfrecord and modifytimestamp. For reverse entries it is looking for
6284 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6285 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6286 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6287 ldapsearch commands could look like this:&lt;/p&gt;
6288
6289 &lt;blockquote&gt;&lt;pre&gt;
6290 ldapsearch -h ldap \
6291 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6292 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6293 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6294 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6295 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6296 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6297
6298 ldapsearch -h ldap \
6299 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6300 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6301 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6302 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6303 srvrecord naptrrecord modifytimestamp
6304 &lt;/pre&gt;&lt;/blockquote&gt;
6305
6306 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6307 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6308 example LDAP objects used there. In addition to these objects, the
6309 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6310 also exist.&lt;/p&gt;
6311
6312 &lt;blockquote&gt;&lt;pre&gt;
6313 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6314 objectclass: top
6315 objectclass: dnsdomain
6316 objectclass: domainrelatedobject
6317 dc: tjener
6318 arecord: 10.0.2.2
6319 associateddomain: tjener.intern
6320
6321 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6322 objectclass: top
6323 objectclass: dnsdomain2
6324 objectclass: domainrelatedobject
6325 dc: 2
6326 ptrrecord: tjener.intern
6327 associateddomain: 2.2.0.10.in-addr.arpa
6328 &lt;/pre&gt;&lt;/blockquote&gt;
6329
6330 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6331 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6332 same base as in the tree mode for a object with filter
6333 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6334 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6335 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6336 naptrrecord and modifytimestamp. For reverse entires it also do a
6337 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6338 and the requested attributes are associateddomain, dnsttl and
6339 modifytimestamp. In short, in strict mode the objects with ptrrecord
6340 go away, and the arecord attribute in the forward object is used
6341 instead.&lt;/p&gt;
6342
6343 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6344 like this:&lt;/p&gt;
6345
6346 &lt;blockquote&gt;&lt;pre&gt;
6347 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6348 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6349 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6350 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6351 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6352 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6353
6354 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6355 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6356 &lt;/pre&gt;&lt;/blockquote&gt;
6357
6358 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6359 search for SOA records, which behave similar to the forward and
6360 reverse lookups.&lt;/p&gt;
6361
6362 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6363 specify any objectclass names, and instead look for the attributes it
6364 need to generate a DNS reply. This make it able to work with any
6365 objectclass that provide the needed attributes.&lt;/p&gt;
6366
6367 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6368 dnsdomain2 schemas. The latter is used for reverse entries like
6369 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6370
6371 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6372 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6373 attributes) and domainrelatedobject (for associatedDomain). The use
6374 of structural object classes make it impossible to combine these
6375 classes with the object classes used by DHCP.&lt;/p&gt;
6376
6377 &lt;p&gt;There are other schemas that could be used too, for example the
6378 dnszone structural object class used by Gosa and bind-sdb for the DNS
6379 attributes combined with the domainrelatedobject object class, but in
6380 this case some unused attributes would have to be included as well
6381 (zonename and relativedomainname).&lt;/p&gt;
6382
6383 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6384 mode and not use any of the existing objectclasses (dnsdomain,
6385 dnsdomain2 and dnszone) when one want to combine the DNS information
6386 with DHCP information, and instead create a auxiliary object class
6387 defined something like this (using the attributes defined for
6388 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6389
6390 &lt;blockquote&gt;&lt;pre&gt;
6391 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6392 SUP top
6393 AUXILIARY
6394 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6395 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6396 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6397 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6398 A6Record $ DNAMERecord
6399 ))
6400 &lt;/pre&gt;&lt;/blockquote&gt;
6401
6402 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6403 the domainrelatedobject object class, and allow any entity to include
6404 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6405 developers asking for their view on this schema and if they are
6406 interested in providing such schema with PowerDNS, and I hope my
6407 message will be accepted into their mailing list soon.&lt;/p&gt;
6408
6409 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6410
6411 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6412 the object attributes, and then uses the attributes it want. This
6413 make it harder to figure out exactly what attributes are used, but
6414 thanks to the working example in Debian Edu I can at least get an idea
6415 what is needed without having to read the source code.&lt;/p&gt;
6416
6417 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6418 search filter to use to locate the correct dhcpServer entity is
6419 stored. These are the relevant entries from
6420 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6421
6422 &lt;blockquote&gt;&lt;pre&gt;
6423 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6424 ldap-dhcp-server-cn &quot;dhcp&quot;;
6425 &lt;/pre&gt;&lt;/blockquote&gt;
6426
6427 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6428 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6429 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6430 search result is this entry:&lt;/p&gt;
6431
6432 &lt;blockquote&gt;&lt;pre&gt;
6433 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6434 cn: dhcp
6435 objectClass: top
6436 objectClass: dhcpServer
6437 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6438 &lt;/pre&gt;&lt;/blockquote&gt;
6439
6440 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6441 subtree with DHCP configuration. The DHCP configuration subtree base
6442 is located using a base scope search with base &quot;cn=DHCP
6443 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6444 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6445 The search result is this entry:&lt;/p&gt;
6446
6447 &lt;blockquote&gt;&lt;pre&gt;
6448 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6449 cn: DHCP Config
6450 objectClass: top
6451 objectClass: dhcpService
6452 objectClass: dhcpOptions
6453 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6454 dhcpStatements: ddns-update-style none
6455 dhcpStatements: authoritative
6456 dhcpOption: smtp-server code 69 = array of ip-address
6457 dhcpOption: www-server code 72 = array of ip-address
6458 dhcpOption: wpad-url code 252 = text
6459 &lt;/pre&gt;&lt;/blockquote&gt;
6460
6461 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6462 all the DHCP configuration is loaded, it is ready to receive requests.
6463 The subtree in Debian Edu contain objects with object classes
6464 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6465 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6466 and information about netmasks, dynamic range etc. Leaving out the
6467 details here because it is not relevant for the focus of my
6468 investigation, which is to see if it is possible to merge dns and dhcp
6469 related computer objects.&lt;/p&gt;
6470
6471 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6472 of the client (00:00:00:00:00:00 in this example), using a subtree
6473 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6474 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6475 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6476 like:&lt;/p&gt;
6477
6478 &lt;blockquote&gt;&lt;pre&gt;
6479 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6480 cn: hostname
6481 objectClass: top
6482 objectClass: dhcpHost
6483 dhcpHWAddress: ethernet 00:00:00:00:00:00
6484 dhcpStatements: fixed-address hostname
6485 &lt;/pre&gt;&lt;/blockquote&gt;
6486
6487 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6488 The object classes need to have fixed names, and the configuration
6489 need to be stored in a fairly specific LDAP structure. On the
6490 positive side, the invidiual dhcpHost entires can be anywhere without
6491 the DN pointed to by the dhcpServer entries. The latter should make
6492 it possible to group all host entries in a subtree next to the
6493 configuration entries, and this subtree can also be shared with the
6494 DNS server if the schema proposed above is combined with the dhcpHost
6495 structural object class.
6496
6497 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6498
6499 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6500 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6501 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6502 allowing DNS objects to be stored anywhere under the base cn specified
6503 in the configuration.&lt;/p&gt;
6504
6505 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6506 regarding which LDAP schemas to use and which LDAP structure to use.
6507 I guess one could implement ones own schema, as long as the
6508 objectclasses and attributes have the names used, but this do not
6509 really help when the DHCP subtree need to have a fairly fixed
6510 structure.&lt;/p&gt;
6511
6512 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6513 this might work for Debian Edu:&lt;/p&gt;
6514
6515 &lt;blockquote&gt;&lt;pre&gt;
6516 ou=services
6517 cn=machine-info (dhcpService) - dhcpServiceDN points here
6518 cn=dhcp (dhcpServer)
6519 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6520 cn=10.0.2.0 (dhcpSubnet)
6521 cn=group1 (dhcpGroup/dhcpOptions)
6522 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6523 cn=192.168.0.0 (dhcpSubnet)
6524 cn=group1 (dhcpGroup/dhcpOptions)
6525 ou=machines - PowerDNS base points here
6526 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6527 &lt;/pre&gt;&lt;/blockquote&gt;
6528
6529 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6530 entries to be in the dhcpGroup subtrees, the entries can be stored
6531 there instead of a common machines subtree, and the PowerDNS base
6532 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6533
6534 &lt;p&gt;The combined object under the machines subtree would look something
6535 like this:&lt;/p&gt;
6536
6537 &lt;blockquote&gt;&lt;pre&gt;
6538 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6539 dc: hostname
6540 objectClass: top
6541 objectClass: dhcpHost
6542 objectclass: domainrelatedobject
6543 objectclass: dnsDomainAux
6544 associateddomain: hostname.intern
6545 arecord: 10.11.12.13
6546 dhcpHWAddress: ethernet 00:00:00:00:00:00
6547 dhcpStatements: fixed-address hostname.intern
6548 &lt;/pre&gt;&lt;/blockquote&gt;
6549
6550 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6551 machine, as long as the required attributes are available in a
6552 auxiliary object class.&lt;/p&gt;
6553 </description>
6554 </item>
6555
6556 <item>
6557 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6558 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6559 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6560 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6561 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6562 DHCP services in Debian Edu to use the same LDAP objects for a given
6563 computer, to avoid the possibility of having a inconsistent state for
6564 a computer in LDAP (as in DHCP but no DNS entry or the other way
6565 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6566
6567 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6568 information finally found a solution that seem to work.&lt;/p&gt;
6569
6570 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6571 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6572 we switch powerdns to use its strict LDAP method (ldap-method=strict
6573 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6574 merged into one while making it impossible to transfer the reverse map
6575 to a slave DNS server.&lt;/p&gt;
6576
6577 &lt;p&gt;If we also replace the object class used to get the DNS related
6578 attributes to one allowing these attributes to be combined with the
6579 dhcphost object class, we can merge the DNS and DHCP entries into one.
6580 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6581 proper OIDs, but that is a minor issue), and tested the setup. It
6582 seem to work.&lt;/p&gt;
6583
6584 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6585 for both DNS and DHCP, and even the LTSP configuration I suggested in
6586 an earlier email. The combined LDAP object will look something like
6587 this:&lt;/p&gt;
6588
6589 &lt;blockquote&gt;&lt;pre&gt;
6590 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6591 cn: hostname
6592 objectClass: dhcphost
6593 objectclass: domainrelatedobject
6594 objectclass: dnsdomainaux
6595 associateddomain: hostname.intern
6596 arecord: 10.11.12.13
6597 dhcphwaddress: ethernet 00:00:00:00:00:00
6598 dhcpstatements: fixed-address hostname
6599 ldapconfigsound: Y
6600 &lt;/pre&gt;&lt;/blockquote&gt;
6601
6602 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6603 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6604 before asking DNS to resolve the fixed-adddress. LTSP will use
6605 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6606
6607 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6608 dhcphost in a different location, to allow us to put the objects
6609 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6610 that. If I can&#39;t figure out a way to do that, we can still get rid of
6611 the hosts subtree and move all its content into the DHCP Config tree
6612 (which probably should be renamed to be more related to the new
6613 content. I suspect cn=dnsdhcp,ou=services or something like that
6614 might be a good place to put it.&lt;/p&gt;
6615
6616 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6617 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6618 </description>
6619 </item>
6620
6621 <item>
6622 <title>Idea for storing LTSP configuration in LDAP</title>
6623 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6624 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6625 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6626 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6627 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6628 clients, and that this can be used to fetch configuration from LDAP if
6629 Debian Edu choose to store configuration there.&lt;/p&gt;
6630
6631 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6632 to get configuration from LDAP. The idea is to look up the MAC
6633 address of the client in LDAP, and look for attributes on the form
6634 ltspconfigsetting=value, and use this to export SETTING=value to the
6635 LTSP clients.&lt;/p&gt;
6636
6637 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6638 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6639 allowing us to store all information about a computer in one place.&lt;/p&gt;
6640
6641 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6642 this approach. A real LDAP schema for the ltspClientAux objectclass
6643 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6644
6645 &lt;blockquote&gt;&lt;pre&gt;
6646 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6647 #
6648 # Fetch LTSP client settings from LDAP based on MAC address
6649 #
6650 # Uses ethernet address as stored in the dhcpHost objectclass using
6651 # the dhcpHWAddress attribute or ethernet address stored in the
6652 # ieee802Device objectclass with the macAddress attribute.
6653 #
6654 # This module is written to be schema agnostic, and only depend on the
6655 # existence of attribute names.
6656 #
6657 # The LTSP configuration variables are saved directly using a
6658 # ltspConfig prefix and uppercasing the rest of the attribute name.
6659 # To set the SERVER variable, set the ltspConfigServer attribute.
6660 #
6661 # Some LDAP schema should be created with all the relevant
6662 # configuration settings. Something like this should work:
6663 #
6664 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6665 # SUP top
6666 # AUXILIARY
6667 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6668
6669 LDAPSERVER=$(debian-edu-ldapserver)
6670 if [ &quot;$LDAPSERVER&quot; ] ; then
6671 LDAPBASE=$(debian-edu-ldapserver -b)
6672 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6673 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6674 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6675 grep &#39;^ltspConfig&#39; | while read attr value ; do
6676 # Remove prefix and convert to upper case
6677 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6678 # bass value on to clients
6679 eval &quot;$attr=$value; export $attr&quot;
6680 done
6681 done
6682 fi
6683 &lt;/pre&gt;&lt;/blockquote&gt;
6684
6685 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6686 the while block might end up in a subshell causing the variables set
6687 there to not show up in ltsp-config, but if that is the case I am sure
6688 the code can be restructured to make sure the variables are passed on.
6689 I expect that can be solved with some testing. :)&lt;/p&gt;
6690
6691 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6692 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6693
6694 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6695 configuration in LDAP that was created around year 2000 by
6696 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6697 Xperience, Inc., 2000&lt;/a&gt;. I found its
6698 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6699 personal home page over at redhat.com.&lt;/p&gt;
6700 </description>
6701 </item>
6702
6703 <item>
6704 <title>jXplorer, a very nice LDAP GUI</title>
6705 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6707 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6708 <description>&lt;p&gt;Since
6709 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6710 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6711 LDAP GUI that is even better than luma. The java application
6712 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6713 moving LDAP objects and subtrees using drag-and-drop, and can
6714 authenticate using Kerberos. I have only tested the Kerberos
6715 authentication, but do not have a LDAP setup allowing me to rewrite
6716 LDAP with my test user yet. It is
6717 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6718 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6719 have with it is how it handle errors. If something go wrong, its
6720 non-intuitive behaviour require me to go through some query work list
6721 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6722 </description>
6723 </item>
6724
6725 <item>
6726 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6727 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6728 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6729 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6730 <description>&lt;p&gt;Here is a short update on my &lt;a
6731 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6732 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6733 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6734 not reporting the status for KDE, because the upgrade crashes when
6735 aptitude try because of missing conflicts
6736 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6737 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6738
6739 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6740 complete list of the installed packages. Based on this I see these
6741 differences when I did a test run today. As usual, I do not really
6742 know what the correct set of packages would be, but thought it best to
6743 publish the difference.&lt;/p&gt;
6744
6745 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6746
6747 &lt;blockquote&gt;&lt;p&gt;
6748 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6749 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6750 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6751 libgtksourceview-common libpt-1.10.10-plugins-alsa
6752 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6753 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6754 python-4suite-xml python-eggtrayicon python-gtkhtml2
6755 python-gtkmozembed svgalibg1 xserver-xephyr zip
6756 &lt;/p&gt;&lt;/blockquote&gt;
6757
6758 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6759
6760 &lt;blockquote&gt;&lt;p&gt;
6761 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6762 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6763 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6764 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6765 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6766 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6767 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6768 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6769 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6770 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6771 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6772 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6773 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6774 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6775 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6776 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6777 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6778 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6779 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6780 mysql-common swfdec-gnome totem-gstreamer wodim
6781 &lt;/p&gt;&lt;/blockquote&gt;
6782
6783 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6784
6785 &lt;blockquote&gt;&lt;p&gt;
6786 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6787 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6788 xserver-xorg-input-all xserver-xorg-input-evdev
6789 xserver-xorg-input-kbd xserver-xorg-input-mouse
6790 xserver-xorg-input-synaptics xserver-xorg-video-all
6791 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6792 xserver-xorg-video-chips xserver-xorg-video-cirrus
6793 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6794 xserver-xorg-video-glint xserver-xorg-video-i128
6795 xserver-xorg-video-i740 xserver-xorg-video-mach64
6796 xserver-xorg-video-mga xserver-xorg-video-neomagic
6797 xserver-xorg-video-nouveau xserver-xorg-video-nv
6798 xserver-xorg-video-r128 xserver-xorg-video-radeon
6799 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6800 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6801 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6802 xserver-xorg-video-sis xserver-xorg-video-sisusb
6803 xserver-xorg-video-tdfx xserver-xorg-video-tga
6804 xserver-xorg-video-trident xserver-xorg-video-tseng
6805 xserver-xorg-video-vesa xserver-xorg-video-vmware
6806 xserver-xorg-video-voodoo
6807 &lt;/p&gt;&lt;/blockquote&gt;
6808
6809 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6810
6811 &lt;blockquote&gt;&lt;p&gt;
6812 deskbar-applet xserver-xorg xserver-xorg-core
6813 xserver-xorg-input-wacom xserver-xorg-video-intel
6814 xserver-xorg-video-openchrome
6815 &lt;/p&gt;&lt;/blockquote&gt;
6816
6817 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6818 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6819 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6820 No idea when it hits Squeeze, but when it does I hope it will reduce
6821 the difference somewhat.
6822 </description>
6823 </item>
6824
6825 <item>
6826 <title>LUMA, a very nice LDAP GUI</title>
6827 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6828 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6829 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6830 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6831 directory in Debian Edu, and in the process I started to miss a GUI
6832 tool to browse the LDAP tree. The only one I was able to find in
6833 Debian/Squeeze and Lenny is
6834 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6835 be a great tool to get a overview of the current LDAP directory
6836 populated by default in Skolelinux. Thanks to it, I have been able to
6837 find empty and obsolete subtrees, misplaced objects and duplicate
6838 objects. It will be installed by default in Debian/Squeeze. If you
6839 are working with LDAP, give it a go. :)&lt;/p&gt;
6840
6841 &lt;p&gt;I did notice one problem with it I have not had time to report to
6842 the BTS yet. There is no .desktop file in the package, so the tool do
6843 not show up in the Gnome and KDE menus, but only deep down in in the
6844 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6845 released.&lt;/p&gt;
6846
6847 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6848 like to move objects and remove subtrees directly in the GUI, but have
6849 not found a way to do that with LUMA yet. So in the mean time, I use
6850 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6851
6852 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6853 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6854
6855 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6856 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6857 useful GUI alternative. It seem like a good tool, but is unmaintained
6858 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6859 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6860 </description>
6861 </item>
6862
6863 <item>
6864 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6865 <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>
6866 <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>
6867 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6868 <description>&lt;p&gt;A while back, I
6869 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6870 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6871 for storing DNS and DHCP information in LDAP to combine the two sets
6872 of information into one LDAP object representing a computer.&lt;/p&gt;
6873
6874 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6875 the dhcpHost object class auxiliary, to allow it to be combined with
6876 the dNSDomain object class, and thus forming one object for one
6877 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6878
6879 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6880 without also changing the assigned number for the object class, and I
6881 do not know enough about LDAP schema design to do that properly for
6882 Debian Edu.&lt;/p&gt;
6883
6884 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6885 the
6886 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6887 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6888 available today from IETF.&lt;/p&gt;
6889
6890 &lt;pre&gt;
6891 --- dhcp.schema (revision 65192)
6892 +++ dhcp.schema (working copy)
6893 @@ -376,7 +376,7 @@
6894 objectclass ( 2.16.840.1.113719.1.203.6.6
6895 NAME &#39;dhcpHost&#39;
6896 DESC &#39;This represents information about a particular client&#39;
6897 - SUP top
6898 + SUP top AUXILIARY
6899 MUST cn
6900 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6901 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6902 &lt;/pre&gt;
6903
6904 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6905 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6906 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6907
6908 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6909 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6910 </description>
6911 </item>
6912
6913 <item>
6914 <title>Calling tasksel like the installer, while still getting useful output</title>
6915 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6916 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6917 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6918 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6919 installs packages during the normal debian-installer run. Until now,
6920 I have ended up letting tasksel do the work, with the annoying problem
6921 of not getting any feedback at all when something fails (like a
6922 conffile question from dpkg or a download that fails), using code like
6923 this:
6924
6925 &lt;blockquote&gt;&lt;pre&gt;
6926 export DEBIAN_FRONTEND=noninteractive
6927 tasksel --new-install
6928 &lt;/pre&gt;&lt;/blockquote&gt;
6929
6930 This would invoke tasksel, let its automatic task selection pick the
6931 tasks to install, and continue to install the requested tasks without
6932 any output what so ever.
6933
6934 Recently I revisited this problem while working on the automatic
6935 package upgrade testing, because tasksel would some times hang without
6936 any useful feedback, and I want to see what is going on when it
6937 happen. Then it occured to me, I can parse the output from tasksel
6938 when asked to run in test mode, and use that aptitude command line
6939 printed by tasksel then to simulate the tasksel run. I ended up using
6940 code like this:
6941
6942 &lt;blockquote&gt;&lt;pre&gt;
6943 export DEBIAN_FRONTEND=noninteractive
6944 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6945 $cmd
6946 &lt;/pre&gt;&lt;/blockquote&gt;
6947
6948 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6949 --without-recommends -o APT::Install-Recommends=no -y install
6950 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6951 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6952 laptop task and all packages with priority standard , required and
6953 important, just like tasksel would have done it during
6954 installation.&lt;/p&gt;
6955
6956 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6957 install packages without using debconf-apt-progress, for use cases
6958 like this.&lt;/p&gt;
6959 </description>
6960 </item>
6961
6962 <item>
6963 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6964 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6965 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6966 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6967 <description>&lt;p&gt;My
6968 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6969 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6970 finally made the upgrade logs available from
6971 &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;.
6972 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6973 apt and aptitude, and found their differences interesting. This time
6974 I will only focus on their removal plans.&lt;/p&gt;
6975
6976 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6977 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6978 surprising part is that it want to remove xorg and all
6979 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6980 sure why. When asking aptitude to do the same, it want to remove 129
6981 packages, but most of them are library packages I suspect are no
6982 longer needed. Both of them want to remove bluetooth packages, which
6983 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6984
6985 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6986 which seem like a bad idea and xorg the same way as with Gnome. Asking
6987 aptitude for the same, it wants to remove 192 packages, none which are
6988 too surprising.&lt;/p&gt;
6989
6990 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6991 and avoided, and perhaps others as well. Here are the complete list
6992 of planned removals. The complete logs is available from the URL
6993 above. Note if you want to repeat these tests, that the upgrade test
6994 for kde+apt-get hung in the tasksel setup because of dpkg asking
6995 conffile questions. No idea why. I worked around it by using
6996 &#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
6997 continue.&lt;/p&gt;
6998
6999 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7000 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7001 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7002 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7003 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7004 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7005 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7006 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7007 xserver-xorg-input-kbd xserver-xorg-input-mouse
7008 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7009 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7010 xserver-xorg-video-ati xserver-xorg-video-chips
7011 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7012 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7013 xserver-xorg-video-glint xserver-xorg-video-i128
7014 xserver-xorg-video-i740 xserver-xorg-video-imstt
7015 xserver-xorg-video-intel xserver-xorg-video-mach64
7016 xserver-xorg-video-mga xserver-xorg-video-neomagic
7017 xserver-xorg-video-nsc xserver-xorg-video-nv
7018 xserver-xorg-video-openchrome xserver-xorg-video-r128
7019 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7020 xserver-xorg-video-rendition xserver-xorg-video-s3
7021 xserver-xorg-video-s3virge xserver-xorg-video-savage
7022 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7023 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7024 xserver-xorg-video-tga xserver-xorg-video-trident
7025 xserver-xorg-video-tseng xserver-xorg-video-v4l
7026 xserver-xorg-video-vesa xserver-xorg-video-vga
7027 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7028 xulrunner-1.9-gnome-support&lt;/p&gt;
7029
7030 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7031
7032 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7033 djvulibre-desktop finger gnome-app-install gnome-mount
7034 gnome-network-admin gnome-spell gnome-vfs-obexftp
7035 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7036 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7037 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7038 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7039 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7040 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7041 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7042 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7043 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7044 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7045 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7046 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7047 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7048 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7049 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7050 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7051 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7052 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7053 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7054 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7055 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7056 openoffice.org-writer2latex openssl-blacklist p7zip
7057 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7058 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7059 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7060 swfdec-mozilla totem-gstreamer update-manager wodim
7061 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7062 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7063 zip&lt;/p&gt;
7064
7065 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7066
7067 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7068 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7069 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7070 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7071 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7072 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7073 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7074 xserver-xorg-input-kbd xserver-xorg-input-mouse
7075 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7076 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7077 xserver-xorg-video-ati xserver-xorg-video-chips
7078 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7079 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7080 xserver-xorg-video-glint xserver-xorg-video-i128
7081 xserver-xorg-video-i740 xserver-xorg-video-imstt
7082 xserver-xorg-video-intel xserver-xorg-video-mach64
7083 xserver-xorg-video-mga xserver-xorg-video-neomagic
7084 xserver-xorg-video-nsc xserver-xorg-video-nv
7085 xserver-xorg-video-openchrome xserver-xorg-video-r128
7086 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7087 xserver-xorg-video-rendition xserver-xorg-video-s3
7088 xserver-xorg-video-s3virge xserver-xorg-video-savage
7089 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7090 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7091 xserver-xorg-video-tga xserver-xorg-video-trident
7092 xserver-xorg-video-tseng xserver-xorg-video-v4l
7093 xserver-xorg-video-vesa xserver-xorg-video-vga
7094 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7095
7096 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7097 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7098 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7099 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7100 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7101 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7102 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7103 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7104 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7105 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7106 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7107 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7108 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7109 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7110 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7111 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7112 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7113 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7114 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7115 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7116 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7117 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7118 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7119 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7120 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7121 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7122 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7123 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7124 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7125 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7126 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7127 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7128 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7129 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7130 texlive-common texlive-doc-base texlive-fonts-recommended
7131 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7132 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7133 xulrunner-1.9&lt;/p&gt;
7134
7135 </description>
7136 </item>
7137
7138 <item>
7139 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7140 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7141 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7142 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7143 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7144 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7145 have been discovered and reported in the process
7146 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7147 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7148 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7149 kdebase-workspace-data), and to get a more regular testing going on, I
7150 am working on a script to automate the test.&lt;/p&gt;
7151
7152 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7153 Gnome or KDE desktop installation inside the chroot before upgrading
7154 it. To ensure no services are started in the chroot, a policy-rc.d
7155 script is inserted. To make sure tasksel believe it is to install a
7156 desktop on a laptop, the tasksel tests are replaced in the chroot
7157 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7158
7159 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7160 currently always fail because udev refuses to upgrade with the kernel
7161 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7162 is created. The bug report
7163 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7164 this problem do not trigger in a chroot, but I touch the file anyway
7165 to make sure the upgrade go well. Testing on virtual and real
7166 hardware have failed me because of udev so far, and creating this file
7167 do the trick in such settings anyway. This is a
7168 &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
7169 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7170 maintainer because he lack the resources to rewrite udev to keep
7171 working with old kernels or something like that. I really wish the
7172 udev upstream would keep udev backwards compatible, to avoid such
7173 upgrade problem, but given that they fail to do so, I guess
7174 documenting the way out of this mess is the best option we got for
7175 Debian Squeeze.&lt;/p&gt;
7176
7177 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7178 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7179 trick:&lt;/p&gt;
7180
7181 &lt;blockquote&gt;&lt;pre&gt;
7182 #!/bin/sh
7183 set -ex
7184
7185 if [ &quot;$1&quot; ] ; then
7186 desktop=$1
7187 else
7188 desktop=gnome
7189 fi
7190
7191 from=lenny
7192 to=squeeze
7193
7194 exec &amp;lt; /dev/null
7195 unset LANG
7196 mirror=http://ftp.skolelinux.org/debian
7197 tmpdir=chroot-$from-upgrade-$to-$desktop
7198 fuser -mv .
7199 debootstrap $from $tmpdir $mirror
7200 chroot $tmpdir aptitude update
7201 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7202 #!/bin/sh
7203 exit 101
7204 EOF
7205 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7206 exit_cleanup() {
7207 umount $tmpdir/proc
7208 }
7209 mount -t proc proc $tmpdir/proc
7210 # Make sure proc is unmounted also on failure
7211 trap exit_cleanup EXIT INT
7212
7213 chroot $tmpdir aptitude -y install debconf-utils
7214
7215 # Make sure tasksel autoselection trigger. It need the test scripts
7216 # to return the correct answers.
7217 echo tasksel tasksel/desktop multiselect $desktop | \
7218 chroot $tmpdir debconf-set-selections
7219
7220 # Include the desktop and laptop task
7221 for test in desktop laptop ; do
7222 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7223 #!/bin/sh
7224 exit 2
7225 EOF
7226 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7227 done
7228
7229 DEBIAN_FRONTEND=noninteractive
7230 DEBIAN_PRIORITY=critical
7231 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7232 chroot $tmpdir tasksel --new-install
7233
7234 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7235 chroot $tmpdir aptitude update
7236 touch $tmpdir/etc/udev/kernel-upgrade
7237 chroot $tmpdir aptitude -y dist-upgrade
7238 fuser -mv
7239 &lt;/pre&gt;&lt;/blockquote&gt;
7240
7241 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7242 with aptitude, but I have not had time to look at how they behave
7243 differently so far. I hope to get a cron job running to do the test
7244 regularly and post the result on the web. The Gnome upgrade currently
7245 work, while the KDE upgrade fail because of the bug in
7246 kdebase-workspace-data&lt;/p&gt;
7247
7248 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7249 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7250 post, so I will refrain from trying. I can report that for Gnome,
7251 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7252 remove and 1 not upgraded and 1024MB need to be downloaded while for
7253 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7254 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7255
7256 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7257 is able to migrate to dependency based boot sequencing and parallel
7258 booting without a hitch. Was unsure if there were still bugs with
7259 packages failing to clean up their obsolete init.d script during
7260 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7261 packages.&lt;/p&gt;
7262 </description>
7263 </item>
7264
7265 <item>
7266 <title>Upstart or sysvinit - as init.d scripts see it</title>
7267 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7268 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7269 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7270 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7271 scripts to migrate (some of) their operations to upstart job while
7272 keeping the init.d for hurd and kfreebsd. The packages with such
7273 needs will need a way to get their init.d scripts to behave
7274 differently when used with sysvinit and with upstart. Because of
7275 this, I had a look at the environment variables set when a init.d
7276 script is running under upstart, and when it is not.&lt;/p&gt;
7277
7278 &lt;p&gt;With upstart, I notice these environment variables are set when a
7279 script is started from rcS.d/ (ignoring some irrelevant ones like
7280 COLUMNS):&lt;/p&gt;
7281
7282 &lt;blockquote&gt;&lt;pre&gt;
7283 DEFAULT_RUNLEVEL=2
7284 previous=N
7285 PREVLEVEL=
7286 RUNLEVEL=
7287 runlevel=S
7288 UPSTART_EVENTS=startup
7289 UPSTART_INSTANCE=
7290 UPSTART_JOB=rc-sysinit
7291 &lt;/pre&gt;&lt;/blockquote&gt;
7292
7293 &lt;p&gt;With sysvinit, these environment variables are set for the same
7294 script.&lt;/p&gt;
7295
7296 &lt;blockquote&gt;&lt;pre&gt;
7297 INIT_VERSION=sysvinit-2.88
7298 previous=N
7299 PREVLEVEL=N
7300 RUNLEVEL=S
7301 runlevel=S
7302 &lt;/pre&gt;&lt;/blockquote&gt;
7303
7304 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7305 sysvinit are not set by upstart. Not sure if it is intentional or not
7306 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7307
7308 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7309 looking for the UPSTART_JOB environment variable seem to be a good
7310 choice.&lt;/p&gt;
7311 </description>
7312 </item>
7313
7314 <item>
7315 <title>A manual for standards wars...</title>
7316 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7317 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7318 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7319 <description>&lt;p&gt;Via the
7320 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7321 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7322 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7323 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7324 following the standards wars of today.&lt;/p&gt;
7325 </description>
7326 </item>
7327
7328 <item>
7329 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7330 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7331 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7332 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7333 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7334 to get a list of the machine types in use thanks to the DMI
7335 information extracted from each machine. The script to do so is
7336 included in the sitesummary package, and here is example output from
7337 the Skolelinux build servers:&lt;/p&gt;
7338
7339 &lt;blockquote&gt;&lt;pre&gt;
7340 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7341 vendor count
7342 Dell Computer Corporation 1
7343 PowerEdge 1750 1
7344 IBM 1
7345 eserver xSeries 345 -[8670M1X]- 1
7346 Intel 2
7347 [no-dmi-info] 3
7348 maintainer:~#
7349 &lt;/pre&gt;&lt;/blockquote&gt;
7350
7351 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7352 provided in each machine. Here there are Intel machines without model
7353 information listed with Intel as vendor and no model, and virtual Xen
7354 machines listed as [no-dmi-info]. One can add -l as a command line
7355 option to list the individual machines.&lt;/p&gt;
7356
7357 &lt;p&gt;A larger list is
7358 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7359 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7360 provide the basic sitesummary report publicly. In their report there
7361 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7362 their machines, and as sitesummary is available in both distributions,
7363 it is trivial to get all of them to report to the same central
7364 collector.&lt;/p&gt;
7365 </description>
7366 </item>
7367
7368 <item>
7369 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7370 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7371 <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>
7372 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7373 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7374 start at boot when an NVidia video card is used is handled. The
7375 problem seem to be that the nvidia X.org driver uses a long time to
7376 initialize, and this duration is longer than kdm is configured to
7377 wait.&lt;/p&gt;
7378
7379 &lt;p&gt;I came across two bugs related to this issue,
7380 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7381 against initscripts and passed on to nvidia-glx when it became obvious
7382 that the nvidia drivers were involved, and
7383 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7384 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7385
7386 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7387 problem nvidia video card owners experience and make sure the Debian
7388 distribution work out of the box for these users. The nvidia driver
7389 maintainers expect kdm to be set up to wait longer, while kdm expect
7390 the nvidia driver maintainers to fix the driver to start faster, and
7391 while they wait for each other I guess the users end up switching to a
7392 distribution that work for them. I have no idea what the solution is,
7393 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7394
7395 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7396 </description>
7397 </item>
7398
7399 <item>
7400 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7401 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7403 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7404 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7405 The feature seem to hold up pretty well, but three fairly serious
7406 issues are known and should be solved:
7407
7408 &lt;p&gt;&lt;ul&gt;
7409
7410 &lt;li&gt;The wicd package seen to
7411 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7412 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7413 parallel booting is enabled. No idea why, but the wicd maintainer
7414 seem to be on the case.&lt;/li&gt;
7415
7416 &lt;li&gt;The nvidia X driver seem to
7417 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7418 triggered more easily when parallel booting is in effect. The
7419 maintainer is on the case.&lt;/li&gt;
7420
7421 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7422 sequencing (the shutdown is broken) when old file-rc users
7423 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7424 sysv-rc. One way to solve it would be for file-rc to create
7425 /etc/init.d/.legacy-bootordering, and another is to try to make
7426 sysv-rc more robust. Will investigate some more and probably upload a
7427 workaround in sysv-rc to help those trying to move from file-rc to
7428 sysv-rc get a working shutdown.&lt;/li&gt;
7429
7430 &lt;/ul&gt;&lt;/p&gt;
7431
7432 &lt;p&gt;All in all not many surprising issues, and all of them seem
7433 solvable before Squeeze is released. In addition to these there are
7434 some packages with bugs in their dependencies and run level settings,
7435 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7436
7437 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7438 the BTS, please usertag the report to get it to show up at
7439 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7440 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7441
7442 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7443 </description>
7444 </item>
7445
7446 <item>
7447 <title>More flexible firmware handling in debian-installer</title>
7448 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7449 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7450 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7451 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7452 found time today to return to the project. Having to spend less time
7453 working dependency based boot in debian, as it is almost complete now,
7454 definitely helped freeing some time.&lt;/p&gt;
7455
7456 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7457 include some firmware packages on the Debian Edu CDs, those needed to
7458 get disk and network controllers working. Without having these
7459 firmware packages available during installation, it is impossible to
7460 install Debian Edu on the given machine, and because our target group
7461 are non-technical people, asking them to provide firmware packages on
7462 an external medium is a support pain. Initially, I expected it to be
7463 enough to include the firmware packages on the CD to get
7464 debian-installer to find and use them. This proved to be wrong.
7465 Next, I hoped it was enough to symlink the relevant firmware packages
7466 to some useful location on the CD (tried /cdrom/ and
7467 /cdrom/firmware/). This also proved to not work, and at this point I
7468 found time to look at the debian-installer code to figure out what was
7469 going to work.&lt;/p&gt;
7470
7471 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7472 look revealed that it would only look for firmware packages outside
7473 the installation media, so the CD was never checked for firmware
7474 packages. It would only check USB sticks, floppies and other
7475 &quot;external&quot; media devices. Today I changed it to also look in the
7476 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7477 solve the problem I ran into with Debian edu. I also changed it to
7478 look in /firmware/, to make sure the installer also find firmware
7479 provided in the initrd when booting the installer via PXE, to allow us
7480 to provide the same feature in the PXE setup included in Debian
7481 Edu.&lt;/p&gt;
7482
7483 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7484 activated without asking if the license is accepted, I extended
7485 hw-detect to look for preinst scripts in the firmware packages, and
7486 run these before activating the firmware during installation. The
7487 license question is asked using debconf in the preinst, so this should
7488 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7489
7490 &lt;p&gt;If you want to discuss the details of these features, please
7491 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7492 </description>
7493 </item>
7494
7495 <item>
7496 <title>Parallellized boot is now the default in Debian/unstable</title>
7497 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7498 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7499 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7500 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7501 Debian/unstable for machines using dependency based boot sequencing.
7502 Apparently the testing of concurrent booting has been wider than
7503 expected, if I am to believe the
7504 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7505 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7506 with the feature this weekend, to give us some time to detect any
7507 remaining problems before Squeeze is frozen. If serious problems are
7508 detected, it is simple to change the default back to sequential boot.
7509 The upload of the new sysvinit package also activate a new upstream
7510 version.&lt;/p&gt;
7511
7512 More information about
7513 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7514 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7515 currently possible to disable parallel booting when one run into
7516 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7517
7518 &lt;blockquote&gt;&lt;pre&gt;
7519 CONCURRENCY=none
7520 &lt;/pre&gt;&lt;/blockquote&gt;
7521
7522 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7523 the BTS, please usertag the report to get it to show up at
7524 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7525 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7526 </description>
7527 </item>
7528
7529 <item>
7530 <title>Sitesummary tip: Listing MAC address of all clients</title>
7531 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7533 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7534 <description>&lt;p&gt;In the recent Debian Edu versions, the
7535 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7536 system&lt;/a&gt; is used to keep track of the machines in the school
7537 network. Each machine will automatically report its status to the
7538 central server after boot and once per night. The network setup is
7539 also reported, and using this information it is possible to get the
7540 MAC address of all network interfaces in the machines. This is useful
7541 to update the DHCP configuration.&lt;/p&gt;
7542
7543 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7544 ist all MAC addresses of all machines reporting to sitesummary. Run
7545 this on the collector host:&lt;/p&gt;
7546
7547 &lt;blockquote&gt;&lt;pre&gt;
7548 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7549 &lt;/pre&gt;&lt;/blockquote&gt;
7550
7551 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7552 line per machine and with space between the MAC addresses.&lt;/p&gt;
7553
7554 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7555 addresses for hosts, it would be possible to extend this to fetch
7556 machine information from sitesummary and update the DHCP and DNS
7557 tables in LDAP using this information. Such tool is unfortunately not
7558 written yet.&lt;/p&gt;
7559 </description>
7560 </item>
7561
7562 <item>
7563 <title>systemd, an interesting alternative to upstart</title>
7564 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7565 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7566 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7567 <description>&lt;p&gt;The last few days a new boot system called
7568 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7569 has been
7570 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7571
7572 to the free software world. I have not yet had time to play around
7573 with it, but it seem to be a very interesting alternative to
7574 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7575 a good alternative for Debian when we are able to switch to an event
7576 based boot system. Tollef is
7577 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7578 systemd into Debian, and I look forward to seeing how well it work. I
7579 like the fact that systemd handles init.d scripts with dependency
7580 information natively, allowing them to run in parallel where upstart
7581 at the moment do not.&lt;/p&gt;
7582
7583 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7584 platform support. It only work on recent Linux kernels, and also need
7585 some new kernel features enabled to function properly. This means
7586 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7587 system. Not sure how that will be handled if systemd proves to be the
7588 way forward.&lt;/p&gt;
7589
7590 &lt;p&gt;In the mean time, based on the
7591 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7592 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7593 decided to enable full parallel booting as the default in Debian as
7594 soon as possible (probably this weekend or early next week), to see if
7595 there are any remaining serious bugs in the init.d dependencies. A
7596 new version of the sysvinit package implementing this change is
7597 already in experimental. If all go well, Squeeze will be released
7598 with parallel booting enabled by default.&lt;/p&gt;
7599 </description>
7600 </item>
7601
7602 <item>
7603 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7604 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7605 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7606 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7607 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7608 complete, so complete that it is actually possible to run all the
7609 init.d scripts in parallell based on these dependencies. If you want
7610 to test your Squeeze system, make sure
7611 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7612 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7613 /etc/default/rcS:&lt;/p&gt;
7614
7615 &lt;blockquote&gt;&lt;pre&gt;
7616 CONCURRENCY=makefile
7617 &lt;/pre&gt;&lt;/blockquote&gt;
7618
7619 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7620 scripts in parallel using the dependency information stored in
7621 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7622 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7623 to try to start the kdm and gdm scripts as early as possible, and will
7624 start the facilities required by kdm or gdm as early as possible to
7625 make this happen.&lt;/p&gt;
7626
7627 &lt;p&gt;Give it a try, and see if you like the result. If some services
7628 fail to start properly, it is most likely because they have incomplete
7629 init.d script dependencies in their startup script (or some of their
7630 dependent scripts have incomplete dependencies). Report bugs and get
7631 the package maintainers to fix it. :)&lt;/p&gt;
7632
7633 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7634 manage to get the init.d script dependencies complete and correct. I
7635 expect we will get there in Squeeze+1, if we get manage to test and
7636 fix the remaining issues.&lt;/p&gt;
7637
7638 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7639 the BTS, please usertag the report to get it to show up at
7640 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7641 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7642 </description>
7643 </item>
7644
7645 <item>
7646 <title>Debian has switched to dependency based boot sequencing</title>
7647 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7649 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7650 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7651 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7652 have been migrated to using dependency based boot sequencing. This
7653 conclude work me and others have been doing for the last three days.
7654 It feels great to see this finally part of the default Debian
7655 installation. Now we just need to weed out the last few problems that
7656 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7657
7658 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7659 fixing the more fundamental problem of handing the event based
7660 non-predictable kernel in the early boot.&lt;/p&gt;
7661 </description>
7662 </item>
7663
7664 <item>
7665 <title>Taking over sysvinit development</title>
7666 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7667 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7668 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7669 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7670 the existing sysvinit upstream developer, I decided a few weeks ago to
7671 take over the package and become the new upstream. The number of
7672 patches to track for the Debian package was becoming a burden, and the
7673 lack of synchronization between the distribution made it hard to keep
7674 the package up to date.&lt;/p&gt;
7675
7676 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7677 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7678 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7679 and Fedora), based on the patches currently in use in these
7680 distributions. We Debian maintainers plan to move to this tarball as
7681 the new upstream as soon as we find time to do the merge. Since the
7682 new tarball was created, we agreed with Werner at SuSe to make a new
7683 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7684 development there. The project is registered and currently waiting
7685 for approval by the Savannah administrators, and as soon as it is
7686 approved, we will import the old versions from svn and continue
7687 working on the future release.&lt;/p&gt;
7688
7689 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7690 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7691 </description>
7692 </item>
7693
7694 <item>
7695 <title>Debian boots quicker and quicker</title>
7696 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7697 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7698 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7699 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7700 people involved in the boot system on Debian and Ubuntu, to see if we
7701 could find more ways to speed up the boot system. This was an Ubuntu
7702 funded
7703 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7704 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7705 of boot systems, and ways to handle the increasing number of boot
7706 issues introduced by the Linux kernel becoming more and more
7707 asynchronous and event base. The Ubuntu approach using udev and
7708 upstart might be a good way forward. Time will show.&lt;/p&gt;
7709
7710 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7711 process in Debian. All of these should be applied to get a quick
7712 boot:&lt;/p&gt;
7713
7714 &lt;ul&gt;
7715
7716 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7717
7718 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7719 clock is in UTC.&lt;/li&gt;
7720
7721 &lt;li&gt;Install and activate the insserv package to enable
7722 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7723 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7724
7725 &lt;/ul&gt;
7726
7727 These points are based on the Google summer of code work done by
7728 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7729 Villegas&lt;/a&gt;.
7730
7731 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7732 unstable yesterday. When we tested it, we were able to cut 6 seconds
7733 from the boot sequence. It depend on very correct dependency
7734 declaration in all init.d scripts, so I expect us to find edge cases
7735 where the dependences in some scripts are slightly wrong when we start
7736 using this.&lt;/p&gt;
7737
7738 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7739 introduced by Raphael Geissert today, one that could affect the
7740 startup speed as well. Instead of starting some scripts concurrently
7741 from rcS.d/ and another set of scripts from rc2.d/, it would be
7742 possible to run a of them in the same process. A quick way to test
7743 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7744 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7745 </description>
7746 </item>
7747
7748 <item>
7749 <title>BSAs påstander om piratkopiering møter motstand</title>
7750 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7751 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7752 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7753 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7754 programvareselskapene som Microsoft og Apple, publisert en rapport der
7755 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7756 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7757 dager siden kom
7758 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7759 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7760 dagene. Et spesielt interessant kommentar fra Sverige,
7761 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7762 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7763
7764 &lt;blockquote&gt;
7765 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7766 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7767 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7768 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7769 &lt;/blockquote&gt;
7770
7771 &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
7772 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7773 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7774 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7775 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7776
7777 &lt;p&gt;Fant lenkene via &lt;a
7778 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7779 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7780 </description>
7781 </item>
7782
7783 <item>
7784 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7785 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7786 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7787 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7788 <description>&lt;p&gt;Kom over
7789 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7790 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7791 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7792 jobber til daglig. En rask opptelling forteller meg at vi har 490
7793 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7794 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7795 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7796 </description>
7797 </item>
7798
7799 <item>
7800 <title>Kryptert harddisk - naturligvis</title>
7801 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7802 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7803 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7804 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7805 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7806 når en tar tap av arbeidstid, fortrolige dokumenter,
7807 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7808 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7809 til at jeg har kryptert harddisken på både kontormaskinen og min
7810 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7811 komme på avveie, den første informasjon relatert til jobben min ved
7812 Universitetet i Oslo, og den andre relatert til blant annet
7813 foreningsarbeide. Kryptering av diskene gjør at det er lite
7814 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7815 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7816 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7817 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7818 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7819 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7820 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7821 det er gjort slik jeg gjør det er minimale, og gevinstene er
7822 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7823 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7824
7825 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7826 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7827 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7828 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7829 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7830 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7831 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7832 betydelige.&lt;/p&gt;
7833 </description>
7834 </item>
7835
7836 <item>
7837 <title>Two projects that have improved the quality of free software a lot</title>
7838 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7839 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7840 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7841 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7842 quality of free software, and I wanted to mention both in case someone
7843 do not yet know them.&lt;/p&gt;
7844
7845 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7846 tool to detect and expose errors in the memory handling of programs.
7847 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7848 and it will report any problems on stdout. It is even better if the
7849 program include debug information. With debug information, it is able
7850 to report the source file name and line number where the problem
7851 occurs. It can report things like &#39;reading past memory block in file
7852 X line N, the memory block was allocated in file Y, line M&#39;, and
7853 &#39;using uninitialised value in control logic&#39;. This tool has made it
7854 trivial to investigate reproducible crash bugs in programs, and have
7855 reduced the number of this kind of bugs in free software a lot.
7856
7857 &lt;p&gt;The second one is
7858 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7859 a source code checker. It is able to process the source of a program
7860 and find problems in the logic without running the program. It
7861 started out as the Stanford Checker and became well known when it was
7862 used to find bugs in the Linux kernel. It is now a commercial tool
7863 and the company behind it is running
7864 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7865 free software community, where a lot of free software projects get
7866 their source checked for free. Several thousand defects have been
7867 found and fixed so far. It can find errors like &#39;lock L taken in file
7868 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7869 Y lines O to P can never be executed&#39;. The projects included in the
7870 community service project have managed to get rid of a lot of
7871 reliability problems thanks to Coverity.&lt;/p&gt;
7872
7873 &lt;p&gt;I believe tools like this, that are able to automatically find
7874 errors in the source, are vital to improve the quality of software and
7875 make sure we can get rid of the crashing and failing software we are
7876 surrounded by today.&lt;/p&gt;
7877 </description>
7878 </item>
7879
7880 <item>
7881 <title>No patch is not better than a useless patch</title>
7882 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7883 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7884 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7885 <description>&lt;p&gt;Julien Blache
7886 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7887 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7888 patch allow one to discuss a concrete and proposed solution, and also
7889 prove that the issue at hand is important enough for someone to spent
7890 time on fixing it. No patch do not provide any of these positive
7891 properties.&lt;/p&gt;
7892 </description>
7893 </item>
7894
7895 <item>
7896 <title>Standardize on protocols and formats, not vendors and applications</title>
7897 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7898 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7899 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7900 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7901 very good one to form a long lived computer infrastructure. It is the
7902 simple one, lost by many in todays computer industry: Standardize on
7903 open network protocols and open exchange/storage formats, not applications.
7904 Applications come and go, while protocols and files tend to stay, and
7905 thus one want to make it easy to change application and vendor, while
7906 avoiding conversion costs and locking users to a specific platform or
7907 application.&lt;/p&gt;
7908
7909 &lt;p&gt;This approach make it possible to replace the client applications
7910 independently of the server applications. One can even allow users to
7911 use several different applications as long as they handle the selected
7912 protocol and format. In the normal case, only one client application
7913 is recommended and users only get help if they choose to use this
7914 application, but those that want to deviate from the easy path are not
7915 blocked from doing so.&lt;/p&gt;
7916
7917 &lt;p&gt;It also allow us to replace the server side without forcing the
7918 users to replace their applications, and thus allow us to select the
7919 best server implementation at any moment, when scale and resouce
7920 requirements change.&lt;/p&gt;
7921
7922 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7923 open formats, but I would never recommend standardizing on a single
7924 application that do not use open network protocol or open formats.&lt;/p&gt;
7925 </description>
7926 </item>
7927
7928 <item>
7929 <title>Returning from Skolelinux developer gathering</title>
7930 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7932 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7933 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7934 Edu/Skolelinux development gathering. I got a bit done tuning the
7935 desktop, and looked into the dynamic service location protocol
7936 implementation avahi. It look like it could be useful for us. Almost
7937 30 people participated, and I believe it was a great environment to
7938 get to know the Skolelinux system. Walter Bender, involved in the
7939 development of the Sugar educational platform, presented his stuff and
7940 also helped me improve my OLPC installation. He also showed me that
7941 his Turtle Art application can be used in standalone mode, and we
7942 agreed that I would help getting it packaged for Debian. As a
7943 standalone application it would be great for Debian Edu. We also
7944 tried to get the video conferencing working with two OLPCs, but that
7945 proved to be too hard for us. The application seem to need more work
7946 before it is ready for me. I look forward to getting home and relax
7947 now. :)&lt;/p&gt;
7948 </description>
7949 </item>
7950
7951 <item>
7952 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7953 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7954 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7955 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7956 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7957 optimal. There is RFC 2307 documenting one way to store NIS maps in
7958 LDAP, and a modified version of this normally called RFC 2307bis, with
7959 some modifications to be compatible with Active Directory. The RFC
7960 specification handle the content of a lot of system databases, but do
7961 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7962
7963 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7964 we would like to store information about users, SMB clients/hosts,
7965 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7966 and LTSP configuration in LDAP. These objects have a lot in common,
7967 but with the current LDAP schemas it is not possible to have one
7968 object per entity. For example, one need to have at least three LDAP
7969 objects for a given computer, one with the SMB related stuff, one with
7970 DNS information and another with DHCP information. The schemas
7971 provided for DNS and DHCP are impossible to combine into one LDAP
7972 object. In addition, it is impossible to implement quick queries for
7973 netgroup membership, because of the way NIS triples are implemented.
7974 It just do not scale. I believe it is time for a few RFC
7975 specifications to cleam up this mess.&lt;/p&gt;
7976
7977 &lt;p&gt;I would like to have one LDAP object representing each computer in
7978 the network, and this object can then keep the SMB (ie host key), DHCP
7979 (mac address/name) and DNS (name/IP address) settings in one place.
7980 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7981
7982 &lt;p&gt;I would also like to have a quick way to map from a user or
7983 computer and to the net group this user or computer is a member.&lt;/p&gt;
7984
7985 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7986 in this regard, and the unix side need to catch up. Time to start a
7987 new IETF work group?&lt;/p&gt;
7988 </description>
7989 </item>
7990
7991 <item>
7992 <title>Endelig er Debian Lenny gitt ut</title>
7993 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7994 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7995 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7996 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7997 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7998 Et langt steg videre for Debian-prosjektet, og en rekke nye
7999 programpakker blir nå tilgjengelig for de av oss som bruker den
8000 stabile utgaven av Debian. Neste steg er nå å få
8001 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8002 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8003 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8004 slippes løs på skolene. Takk til alle debian-utviklerne som har
8005 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8006 bootsekvens tilgjengelig i stabil utgave, vha pakken
8007 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8008 </description>
8009 </item>
8010
8011 <item>
8012 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8013 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8014 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8015 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8016 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8017 Oslo. Most of Saturday was used for the general assemly for the
8018 member organization, but the rest of the weekend I used to tune the
8019 LTSP installation. LTSP now work out of the box on the 10-network.
8020 Acer Aspire One proved to be a very nice thin client, with both
8021 screen, mouse and keybard in a small box. Was working on getting the
8022 diskless workstation setup configured out of the box, but did not
8023 finish it before the weekend was up.&lt;/p&gt;
8024
8025 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8026 the Brazilian group, so that will have to wait for the next
8027 development gathering. Would love to have the Debian Edu installer
8028 automatically detect and configure a multiseat setup when it find one
8029 of these cards.&lt;/p&gt;
8030 </description>
8031 </item>
8032
8033 <item>
8034 <title>The sorry state of multimedia browser plugins in Debian</title>
8035 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8036 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8037 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8038 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8039 plugins available in Debian Lenny, to see which one we should use by
8040 default in Debian Edu. We need an embedded video playing plugin with
8041 control buttons to pause or stop the video, and capable of streaming
8042 all the multimedia content available on the web. The test results and
8043 notes are available on
8044 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8045 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8046 fill this need. My personal video player favorite, VLC, has a really
8047 bad plugin which fail on a lot of the test pages. A lot of the MIME
8048 types I would expect to work with any free software player (like
8049 video/ogg), just do not work. And simple formats like the
8050 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8051 totem and vlc plugins. I hope the situation will improve soon. No
8052 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8053
8054 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8055 be the only one fitting our needs. :/&lt;/p&gt;
8056 </description>
8057 </item>
8058
8059 </channel>
8060 </rss>