]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
fb8d81c774e69d1626e24a53f3c7887a92e06127
[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>New laptop - some more clues and ideas based on feedback</title>
11 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
13 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
14 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
15 need for a new laptop, and provided very useful feedback. I wish to
16 thank every one of these. Several pointed me to the possibility of
17 fixing my X230, and I am already in the process of getting Lenovo to
18 do so thanks to the on site, next day support contract covering the
19 machine. But the battery is almost useless (I expect to replace it
20 with a non-official battery) and I do not expect the machine to live
21 for many more years, so it is time to plan its replacement. If I did
22 not have a support contract, it was suggested to find replacement parts
23 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
24 might present a language barrier as I do not understand French.&lt;/p&gt;
25
26 &lt;p&gt;One tip I got was to use the
27 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
28 compare laptop models. It seem to have more models available than
29 prisjakt.no. Another tip I got from someone I know have similar
30 keyboard preferences was that the HP EliteBook 840 keyboard is not
31 very good, and this matches my experience with earlier EliteBook
32 keyboards I tested. Because of this, I will not consider it any further.
33
34 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
35 newest Thinkpad X model. The keyboard reintroduces mouse buttons
36 (which is missing from the X240), and is working fairly well with
37 Debian Sid/Unstable according to
38 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
39 got on the keyboard quality are not consistent. Some say the keyboard
40 is good, others say it is ok, while others say it is not very good.
41 Those with experience from X41 and and X60 agree that the X250
42 keyboard is not as good as those trusty old laptops, and suggest I
43 keep and fix my X230 instead of upgrading, or get a used X230 to
44 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
45 activity and battery status, which is very convenient on my X230. I&#39;m
46 also told that the CPU fan is running very often, making it a bit
47 noisy. In any case, the X250 do not work out of the box with Debian
48 Stable/Jessie, one of my requirements.&lt;/p&gt;
49
50 &lt;p&gt;I have also gotten a few vendor proposals, one was
51 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
52 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
53 The latter look very attractive to me.&lt;/p&gt;
54
55 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
56 as I keep looking for a replacement.&lt;/p&gt;
57
58 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
59 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
60 different
61 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
62 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
63 </description>
64 </item>
65
66 <item>
67 <title>Time to find a new laptop, as the old one is broken after only two years</title>
68 <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>
69 <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>
70 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
71 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
72 replacement soon. The left 5 cm of the screen on my Thinkpad X230
73 started flickering yesterday, and I suspect the cause is a broken
74 cable, as changing the angle of the screen some times get rid of the
75 flickering.&lt;/p&gt;
76
77 &lt;p&gt;My requirements have not really changed since I bought it, and is
78 still as
79 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
80 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
81 good help from
82 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
83 where I could select at least a few of the requirements (mouse pin,
84 wifi, weight) and go through the rest manually. Three button mouse
85 and a good keyboard is not available as an option, and all the three
86 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
87 G2) lack three mouse buttons). It is also unclear to me how good the
88 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
89 the keyboard, even if the quality and robustness in the X series have
90 deteriorated since X41.&lt;/p&gt;
91
92 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
93 seem sensible to me? Are there better services around to search the
94 set of available laptops for features? Please send me an email if you
95 have suggestions.&lt;/p&gt;
96
97 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
98 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
99 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
100 </description>
101 </item>
102
103 <item>
104 <title>How to stay with sysvinit in Debian Jessie</title>
105 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
106 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
107 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
108 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
109 sysvinit as its boot system by default. But how can one keep using
110 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
111 courtesy of
112 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
113 Schubert&lt;/a&gt; and
114 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
115 McVittie&lt;/a&gt;.
116
117 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
118 keep sysvinit as your boot system, create a file
119 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
120 you upgrade:&lt;/p&gt;
121
122 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
123 Package: systemd-sysv
124 Pin: release o=Debian
125 Pin-Priority: -1
126 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
127
128 &lt;p&gt;This file content will tell apt and aptitude to not consider
129 installing systemd-sysv as part of any installation and upgrade
130 solution when resolving dependencies, and thus tell it to avoid
131 systemd as a default boot system. The end result should be that the
132 upgraded system keep using sysvinit.&lt;/p&gt;
133
134 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
135 get sysvinit installed by default (debootstrap used by
136 debian-installer have no option for this), but one can tell the
137 installer to switch to sysvinit before the first boot. Either by
138 using a kernel argument to the installer, or by adding a line to the
139 preseed file used. First, the kernel command line argument:
140
141 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
142 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
143 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
144
145 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
146
147 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
148 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
149 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
150
151 &lt;p&gt;One can of course also do this after the first boot by installing
152 the sysvinit-core package.&lt;/p&gt;
153
154 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
155 sysvinit boot sequence in Debian have several hardware specific bugs
156 on Linux caused by the fact that it is unpredictable when hardware
157 devices show up during boot. But on the other hand, the new default
158 boot system still have a few rough edges I hope will be fixed before
159 Jessie is released.&lt;/p&gt;
160
161 &lt;p&gt;Update 2014-11-26: Inspired by
162 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
163 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
164 line.&lt;/p&gt;
165 </description>
166 </item>
167
168 <item>
169 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
170 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
171 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
172 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
173 <description>&lt;p&gt;The right to communicate with your friends and family in private,
174 without anyone snooping, is a right every citicen have in a liberal
175 democracy. But this right is under serious attack these days.&lt;/p&gt;
176
177 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
178 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
179 the whisleblower Snowden) more expensive for Internet email,
180 is to deliver all email using SMTP via Tor. Such SMTP option would be
181 a nice addition to the FreedomBox project if we could send email
182 between FreedomBox machines without leaking metadata about the emails
183 to the people peeking on the wire. I
184 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
185 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
186 lot of useful feedback and suggestions. It also became obvious to me
187 that this was not a novel idea, as the same idea was tested and
188 documented by Johannes Berg as early as 2006, and both
189 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
190 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
191 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
192
193 &lt;p&gt;To implement such system one need to set up a Tor hidden service
194 providing the SMTP protocol on port 25, and use email addresses
195 looking like username@hidden-service-name.onion. With such addresses
196 the connections to port 25 on hidden-service-name.onion using Tor will
197 go to the correct SMTP server. To do this, one need to configure the
198 Tor daemon to provide the hidden service and the mail server to accept
199 emails for this .onion domain. To learn more about Exim configuration
200 in Debian and test the design provided by Johannes Berg in his FAQ, I
201 set out yesterday to create a Debian package for making it trivial to
202 set up such SMTP over Tor service based on Debian. Getting it to work
203 were fairly easy, and
204 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
205 source code for the Debian package&lt;/a&gt; is available from github. I
206 plan to move it into Debian if further testing prove this to be a
207 useful approach.&lt;/p&gt;
208
209 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
210 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
211 get rid of exim4). Install tor, clone the git repository mentioned
212 above, build the deb and install it on the machine. Next, run
213 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
214 the instructions to get the service up and running. Restart tor and
215 exim when it is done, and test mail delivery using swaks like
216 this:&lt;/p&gt;
217
218 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
219 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
220 --to fbx@dutlqrrmjhtfa3vp.onion
221 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
222
223 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
224 address with your own address to test your server. :)&lt;/p&gt;
225
226 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
227 easier and more automatic. Especially the tor setup need more work.
228 Also, the package include a tor-smtp tool written in C, but its task
229 should probably be rewritten in some script language to make the deb
230 architecture independent. It would probably also make the code easier
231 to review. The tor-smtp tool currently need to listen on a socket for
232 exim to talk to it and is started using xinetd. It would be better if
233 no daemon and no socket is needed. I suspect it is possible to get
234 exim to run a command line tool for delivery instead of talking to a
235 socket, and hope to figure out how in a future version of this
236 system.&lt;/p&gt;
237
238 &lt;p&gt;Until I wipe my test machine, I can be reached using the
239 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
240 SMTorP. :)&lt;/p&gt;
241 </description>
242 </item>
243
244 <item>
245 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
246 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
247 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
248 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
249 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
250 alioth.debian.org, you know the web interface is fairly slow to
251 operate. First you visit one web page, enter the moderation password
252 and get a new page shown with a list of all the messages to moderate
253 and various options for each email address. This take a while for
254 every list you moderate, and you need to do it regularly to do a good
255 job as a list moderator. But there is a quick alternative,
256 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
257 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
258 to moderate in a fraction of a second. Here is a test run on two
259 lists I recently took over:&lt;/p&gt;
260
261 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
262 % time listadmin xiph
263 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
264 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
265
266 real 0m1.709s
267 user 0m0.232s
268 sys 0m0.012s
269 %
270 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
271
272 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
273 there are no message in the moderation queue. Every morning I
274 currently moderate 68 mailman lists, and it normally take around two
275 minutes. When I took over the two pkg-xiph lists above a few days
276 ago, there were 400 emails waiting in the moderator queue. It took me
277 less than 15 minutes to process them all using the listadmin
278 program.&lt;/p&gt;
279
280 &lt;p&gt;If you install
281 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
282 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
283 with content like this, the moderation task is a breeze:&lt;/p&gt;
284
285 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
286 username username@example.org
287 spamlevel 23
288 default discard
289 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
290
291 password secret
292 adminurl https://{domain}/mailman/admindb/{list}
293 mailman-list@lists.example.com
294
295 password hidden
296 other-list@otherserver.example.org
297 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
298
299 &lt;p&gt;There are other options to set as well. Check the manual page to
300 learn the details.&lt;/p&gt;
301
302 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
303 the SSL certificate is self signed or not properly signed by a
304 generally accepted signing authority, you can set a environment
305 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
306
307 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
308 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
309 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
310
311 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
312 can provide an argument to the listadmin script like I do in the
313 initial screen dump (the xiph argument). Using an argument, only
314 lists matching the argument string will be processed. This make it
315 quick to accept messages if you notice the moderation request in your
316 email.&lt;/p&gt;
317
318 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
319 mailing lists, as I simply do not have time to spend on that if the
320 process was any slower. The listadmin program have saved me hours of
321 time I could spend elsewhere over the years. It truly is nice free
322 software.&lt;/p&gt;
323
324 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
325 activities, please send Bitcoin donations to my address
326 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
327
328 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
329 configuration example. Also, I&#39;ve been told that the
330 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
331 sure why.&lt;/p&gt;
332 </description>
333 </item>
334
335 <item>
336 <title>Debian Jessie, PXE and automatic firmware installation</title>
337 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
339 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
340 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
341 problem that the WiFi card require some firmware to work properly.
342 And it has been a pain to fix this using preseeding in Debian.
343 Normally something more is needed. But thanks to
344 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
345 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
346 to do this using simple preseeding.&lt;/p&gt;
347
348 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
349 firmware for the hardware found in the machine (actually, requested by
350 the kernel modules for the hardware). (It can also install user space
351 programs supporting the hardware detected, but that is not the focus
352 of this story.)&lt;/p&gt;
353
354 &lt;p&gt;To get this working in the default installation, two preeseding
355 values are needed. First, the isenkram-cli package must be installed
356 into the target chroot (aka the hard drive) before tasksel is executed
357 in the pkgsel step of the debian-installer system. This is done by
358 preseeding the base-installer/includes debconf value to include the
359 isenkram-cli package. The package name is next passed to debootstrap
360 for installation. With the isenkram-cli package in place, tasksel
361 will automatically use the isenkram tasks to detect hardware specific
362 packages for the machine being installed and install them, because
363 isenkram-cli contain tasksel tasks.&lt;/p&gt;
364
365 &lt;p&gt;Second, one need to enable the non-free APT repository, because
366 most firmware unfortunately is non-free. This is done by preseeding
367 the apt-mirror-setup step. This is unfortunate, but for a lot of
368 hardware it is the only option in Debian.&lt;/p&gt;
369
370 &lt;p&gt;The end result is two lines needed in your preseeding file to get
371 firmware installed automatically by the installer:&lt;/p&gt;
372
373 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
374 base-installer base-installer/includes string isenkram-cli
375 apt-mirror-setup apt-setup/non-free boolean true
376 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
377
378 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
379 both firmware and user space packages when using this method. It also
380 do not work well, so use version 0.15 or later. Installing both
381 firmware and user space packages might give you a bit more than you
382 want, so I decided to split the tasksel task in two, one for firmware
383 and one for user space programs. The firmware task is enabled by
384 default, while the one for user space programs is not. This split is
385 implemented in the package currently in unstable.&lt;/p&gt;
386
387 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
388 this recipe work for you. :)&lt;/p&gt;
389
390 &lt;p&gt;So, I bet you are wondering, how can this work. First and
391 foremost, it work because tasksel is modular, and driven by whatever
392 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
393 isenkram-cli package place two files for tasksel to find. First there
394 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
395
396 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
397 Task: isenkram-packages
398 Section: hardware
399 Description: Hardware specific packages (autodetected by isenkram)
400 Based on the detected hardware various hardware specific packages are
401 proposed.
402 Test-new-install: show show
403 Relevance: 8
404 Packages: for-current-hardware
405
406 Task: isenkram-firmware
407 Section: hardware
408 Description: Hardware specific firmware packages (autodetected by isenkram)
409 Based on the detected hardware various hardware specific firmware
410 packages are proposed.
411 Test-new-install: mark show
412 Relevance: 8
413 Packages: for-current-hardware-firmware
414 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
415
416 &lt;p&gt;The key parts are Test-new-install which indicate how the task
417 should be handled and the Packages line referencing to a script in
418 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
419 list of packages to install. The for-current-hardware-firmware script
420 look like this to list relevant firmware for the machine:
421
422 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
423 #!/bin/sh
424 #
425 PATH=/usr/sbin:$PATH
426 export PATH
427 isenkram-autoinstall-firmware -l
428 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
429
430 &lt;p&gt;With those two pieces in place, the firmware is installed by
431 tasksel during the normal d-i run. :)&lt;/p&gt;
432
433 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
434 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
435 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
436 install.&lt;/p&gt;
437
438 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
439 pilots in testing this feature, as isenkram is used there now to
440 install firmware, replacing the earlier scripts.&lt;/p&gt;
441 </description>
442 </item>
443
444 <item>
445 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
446 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
447 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
448 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
449 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
450 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
451 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
452 on a screen normally showing the bread types and prizes:&lt;/p&gt;
453
454 &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;
455
456 &lt;p&gt;If it had booted as it was supposed to, I would never had known
457 about this hidden Linux installation. It is interesting what
458 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
459 </description>
460 </item>
461
462 <item>
463 <title>New lsdvd release version 0.17 is ready</title>
464 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
465 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
466 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
467 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
468 got a new set of developers a few weeks ago, after the original
469 developer decided to step down and pass the project to fresh blood.
470 This project is now maintained by Petter Reinholdtsen and Steve
471 Dibb.&lt;/p&gt;
472
473 &lt;p&gt;I just wrapped up
474 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
475 new lsdvd release&lt;/a&gt;, available in git or from
476 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
477 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
478 0.17.&lt;/p&gt;
479
480 &lt;ul&gt;
481
482 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
483 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
484 non-existant, to work around additional copy protection&lt;/li&gt;
485 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
486 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
487 &lt;li&gt;Fix include orders&lt;/li&gt;
488 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
489 &lt;li&gt;Fix the chapter count&lt;/li&gt;
490 &lt;li&gt;Make sure the array size and the array limit used when initialising
491 the palette size is the same.&lt;/li&gt;
492 &lt;li&gt;Fix array printing.&lt;/li&gt;
493 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
494 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
495 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
496 with more GCC compiler warnings.&lt;/li&gt;
497
498 &lt;/ul&gt;
499
500 &lt;p&gt;This change bring together patches for lsdvd in use in various
501 Linux and Unix distributions, as well as patches submitted to the
502 project the last nine years. Please check it out. :)&lt;/p&gt;
503 </description>
504 </item>
505
506 <item>
507 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
508 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
509 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
510 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
511 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
512 project&lt;/a&gt; provide a Linux solution for schools, including a
513 powerful desktop with education software, a central server providing
514 web pages, user database, user home directories, central login and PXE
515 boot of both clients without disk and the installation to install Debian
516 Edu on machines with disk (and a few other services perhaps to small
517 to mention here). We in the Debian Edu team are currently working on
518 the Jessie based version, trying to get everything in shape before the
519 freeze, to avoid having to maintain our own package repository in the
520 future. The
521 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
522 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
523 work left. Some fatal problems block testing, breaking the installer,
524 but it is possible to work around these to get anyway. Here is a
525 recipe on how to get the installation limping along.&lt;/p&gt;
526
527 &lt;p&gt;First, download the test ISO via
528 &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;,
529 &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;
530 or rsync (use
531 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
532 The ISO build was broken on Tuesday, so we do not get a new ISO every
533 12 hours or so, but thankfully the ISO we already got we are able to
534 install with some tweaking.&lt;/p&gt;
535
536 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
537 (use Alt-Ctrl-F2), run&lt;/p&gt;
538
539 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
540 nano /usr/bin/edu-eatmydata-install
541 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
542
543 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
544 optimization. Return to the installation, select the profile you want
545 and continue. Without this change, exim4-config will fail to install
546 due to a known bug in eatmydata.&lt;/p&gt;
547
548 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
549 this do not work, figure out what your correct value would be. All my
550 test machines need /dev/sda, so I have no advice if it do not fit
551 your need.&lt;/p&gt;
552
553 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
554 root after the initial boot from hard drive, and install the
555 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
556 or mate. If you want several desktop options, install more than one
557 metapackage. Once this is done, reboot and you should have a working
558 graphical login screen. This workaround should no longer be needed
559 once the education-tasks package version 1.801 enter testing in two
560 days.&lt;/p&gt;
561
562 &lt;p&gt;I believe the ISO build will start working on two days when the new
563 tasksel package enter testing and Steve McIntyre get a chance to
564 update the debian-cd git repository. The eatmydata, grub and desktop
565 issues are already fixed in unstable and testing, and should show up
566 on the ISO as soon as the ISO build start working again. Well the
567 eatmydata optimization is really just disabled. The proper fix
568 require an upload by the eatmydata maintainer applying the patch
569 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
570 The rest have proper fixes in unstable.&lt;/p&gt;
571
572 &lt;p&gt;I hope this get you going with the installation testing, as we are
573 quickly running out of time trying to get our Jessie based
574 installation ready before the distribution freeze in a month.&lt;/p&gt;
575 </description>
576 </item>
577
578 <item>
579 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
580 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
581 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
582 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
583 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
584 to handle my fairly large DVD collection. It is a nice command line
585 tool to get details about a DVD, like title, tracks, track length,
586 etc, in XML, Perl or human readable format. But lsdvd have not seen
587 any new development since 2006 and had a few irritating bugs affecting
588 its use with some DVDs. Upstream seemed to be dead, and in January I
589 sent a small probe asking for a version control repository for the
590 project, without any reply. But I use it regularly and would like to
591 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
592 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
593 the project admin, and after getting a reply from him explaining that
594 he was no longer interested in the project, I asked if I could take
595 over. And yesterday, I became project admin.&lt;/p&gt;
596
597 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
598 maintainer interested in joining forces to maintain the upstream
599 project, and I hope we can get a new release out fairly quickly,
600 collecting the patches spread around on the internet into on place.
601 I&#39;ve added the relevant Debian patches to the freshly created git
602 repository, and expect the Gentoo patches to make it too. If you got
603 a DVD collection and care about command line tools, check out
604 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
605 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
606 list&lt;/a&gt;. :)&lt;/p&gt;
607 </description>
608 </item>
609
610 <item>
611 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
612 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
614 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
615 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
616 a lot quicker. When we install more than 2000 packages in
617 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
618 tasksel in the installer, unpacking the binary packages take forever.
619 A part of the slow I/O issue was discussed in
620 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
621 much file system sync-ing done by dpkg, which is the package
622 responsible for unpacking the binary packages. Other parts (like code
623 executed by postinst scripts) might also sync to disk during
624 installation. All this sync-ing to disk do not really make sense to
625 me. If the machine crash half-way through, I start over, I do not try
626 to salvage the half installed system. So the failure sync-ing is
627 supposed to protect against, hardware or system crash, is not really
628 relevant while the installer is running.&lt;/p&gt;
629
630 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
631 system sync()-ing in a fairly non-intrusive way, without the need to
632 change the code in several packages. The idea is not new, but I have
633 not heard anyone propose the approach using dpkg-divert before. It
634 depend on the small and clever package
635 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
636 uses LD_PRELOAD to replace the system functions for syncing data to
637 disk with functions doing nothing, thus allowing programs to live
638 dangerous while speeding up disk I/O significantly. Instead of
639 modifying the implementation of dpkg, apt and tasksel (which are the
640 packages responsible for selecting, fetching and installing packages),
641 it occurred to me that we could just divert the programs away, replace
642 them with a simple shell wrapper calling
643 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
644 Two days ago I decided to test the idea, and wrapped up a simple
645 implementation for the Debian Edu udeb.&lt;/p&gt;
646
647 &lt;p&gt;The effect was stunning. In my first test it reduced the running
648 time of the pkgsel step (installing tasks) from 64 to less than 44
649 minutes (20 minutes shaved off the installation) on an old Dell
650 Latitude D505 machine. I am not quite sure what the optimised time
651 would have been, as I messed up the testing a bit, causing the debconf
652 priority to get low enough for two questions to pop up during
653 installation. As soon as I saw the questions I moved the installation
654 along, but do not know how long the question were holding up the
655 installation. I did some more measurements using Debian Edu Jessie,
656 and got these results. The time measured is the time stamp in
657 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
658 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
659 yourself. In Debian Edu, the tasksel dialog do not show up, and the
660 timing thus do not depend on how quickly the user handle the tasksel
661 dialog.&lt;/p&gt;
662
663 &lt;p&gt;&lt;table&gt;
664
665 &lt;tr&gt;
666 &lt;th&gt;Machine/setup&lt;/th&gt;
667 &lt;th&gt;Original tasksel&lt;/th&gt;
668 &lt;th&gt;Optimised tasksel&lt;/th&gt;
669 &lt;th&gt;Reduction&lt;/th&gt;
670 &lt;/tr&gt;
671
672 &lt;tr&gt;
673 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
674 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
675 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
676 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
677 &lt;/tr&gt;
678
679 &lt;tr&gt;
680 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
681 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
682 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
683 &lt;td&gt;23 min 40%&lt;/td&gt;
684 &lt;/tr&gt;
685
686 &lt;tr&gt;
687 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
688 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
689 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
690 &lt;td&gt;11 min 50%&lt;/td&gt;
691 &lt;/tr&gt;
692
693 &lt;tr&gt;
694 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
695 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
696 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
697 &lt;td&gt;2 min 33%&lt;/td&gt;
698 &lt;/tr&gt;
699
700 &lt;tr&gt;
701 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
702 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
703 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
704 &lt;td&gt;4 min 21%&lt;/td&gt;
705 &lt;/tr&gt;
706
707 &lt;/table&gt;&lt;/p&gt;
708
709 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
710 time is spent downloading packages. The connection to the Internet
711 was 100Mbit/s during testing, so downloading should not be a
712 significant factor in the measurement. Download typically took a few
713 seconds to a few minutes, depending on the amount of packages being
714 installed.&lt;/p&gt;
715
716 &lt;p&gt;The speedup is implemented by using two hooks in
717 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
718 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
719 finish-install.d hook to remove the divert at the end of the
720 installation. I picked the pre-pkgsel.d hook instead of the
721 post-base-installer.d hook because I test using an ISO without the
722 eatmydata package included, and the post-base-installer.d hook in
723 Debian Edu can only operate on packages included in the ISO. The
724 negative effect of this is that I am unable to activate this
725 optimization for the kernel installation step in d-i. If the code is
726 moved to the post-base-installer.d hook, the speedup would be larger
727 for the entire installation.&lt;/p&gt;
728
729 &lt;p&gt;I&#39;ve implemented this in the
730 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
731 git repository, and plan to provide the optimization as part of the
732 Debian Edu installation. If you want to test this yourself, you can
733 create two files in the installer (or in an udeb). One shell script
734 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
735
736 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
737 #!/bin/sh
738 set -e
739 . /usr/share/debconf/confmodule
740 info() {
741 logger -t my-pkgsel &quot;info: $*&quot;
742 }
743 error() {
744 logger -t my-pkgsel &quot;error: $*&quot;
745 }
746 override_install() {
747 apt-install eatmydata || true
748 if [ -x /target/usr/bin/eatmydata ] ; then
749 for bin in dpkg apt-get aptitude tasksel ; do
750 file=/usr/bin/$bin
751 # Test that the file exist and have not been diverted already.
752 if [ -f /target$file ] ; then
753 info &quot;diverting $file using eatmydata&quot;
754 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
755 &gt; /target$file.edu
756 chmod 755 /target$file.edu
757 in-target dpkg-divert --package debian-edu-config \
758 --rename --quiet --add $file
759 ln -sf ./$bin.edu /target$file
760 else
761 error &quot;unable to divert $file, as it is missing.&quot;
762 fi
763 done
764 else
765 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
766 fi
767 }
768
769 override_install
770 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
771
772 &lt;p&gt;To clean up, another shell script should go into
773 /usr/lib/finish-install.d/ with code like this:
774
775 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
776 #! /bin/sh -e
777 . /usr/share/debconf/confmodule
778 error() {
779 logger -t my-finish-install &quot;error: $@&quot;
780 }
781 remove_install_override() {
782 for bin in dpkg apt-get aptitude tasksel ; do
783 file=/usr/bin/$bin
784 if [ -x /target$file.edu ] ; then
785 rm /target$file
786 in-target dpkg-divert --package debian-edu-config \
787 --rename --quiet --remove $file
788 rm /target$file.edu
789 else
790 error &quot;Missing divert for $file.&quot;
791 fi
792 done
793 sync # Flush file buffers before continuing
794 }
795
796 remove_install_override
797 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
798
799 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
800 edu-eatmydata-install and call it from the pre-pkgsel.d and
801 finish-install.d scripts.&lt;/p&gt;
802
803 &lt;p&gt;By now you might ask if this change should get into the normal
804 Debian installer too? I suspect it should, but am not sure the
805 current debian-installer coordinators find it useful enough. It also
806 depend on the side effects of the change. I&#39;m not aware of any, but I
807 guess we will see if the change is safe after some more testing.
808 Perhaps there is some package in Debian depending on sync() and
809 fsync() having effect? Perhaps it should go into its own udeb, to
810 allow those of us wanting to enable it to do so without affecting
811 everyone.&lt;/p&gt;
812
813 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
814 will break installation of all programs using gnutls because of
815 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
816 eatmydata package in Debian will solve it.&lt;/p&gt;
817
818 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
819 the optimization work again. And I have discovered that the
820 dpkg-divert trick is not really needed and implemented a slightly
821 simpler approach as part of the debian-edu-install package. See
822 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
823
824 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
825 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
826 triggering on i386 made it into testing, and broke this installation
827 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
828 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
829 </description>
830 </item>
831
832 <item>
833 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
834 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
835 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
836 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
837 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
838 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
839 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
840 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
841 learn that there is a large set of publicly available key servers to
842 use when looking for peoples public key. So far I have used
843 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
844 were misbehaving, but those days are ended. The servers I have used
845 up until yesterday have been slow and some times unavailable. I hope
846 those problems are gone now.&lt;/p&gt;
847
848 &lt;p&gt;Behind the round robin DNS entry of the
849 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
850 there is a pool of more than 100 keyservers which are checked every
851 day to ensure they are well connected and up to date. It must be
852 better than what I have used so far. :)&lt;/p&gt;
853
854 &lt;p&gt;Yesterdays speaker told me that the service is the default
855 keyserver provided by the default configuration in GnuPG, but this do
856 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
857
858 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
859 line:&lt;/p&gt;
860
861 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
862 keyserver pool.sks-keyservers.net
863 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
864
865 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
866 entries in DNS. Just for fun, I did just that at work, so now every
867 user of GnuPG at the University of Oslo should find a OpenGPG
868 keyserver automatically should their need it:&lt;/p&gt;
869
870 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
871 % host -t srv _pgpkey-http._tcp.uio.no
872 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
873 %
874 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
875
876 &lt;p&gt;Now if only
877 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
878 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
879 very happy. It can look up a given key or search for a user ID, but I
880 normally do not want that, but to find a trust path from my key to
881 another key. Given a user ID or key ID, I would like to find (and
882 download) the keys representing a signature path from my key to the
883 key in question, to be able to get a trust path between the two keys.
884 This is as far as I can tell not possible today. Perhaps something
885 for a future version of the protocol?&lt;/p&gt;
886 </description>
887 </item>
888
889 <item>
890 <title>From English wiki to translated PDF and epub via Docbook</title>
891 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
892 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
893 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
894 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
895 project&lt;/a&gt; provide an instruction manual for teachers, system
896 administrators and other users that contain useful tips for setting up
897 and maintaining a Debian Edu installation. This text is about how the
898 text processing of this manual is handled in the project.&lt;/p&gt;
899
900 &lt;p&gt;One goal of the project is to provide information in the native
901 language of its users, and for this we need to handle translations.
902 But we also want to make sure each language contain the same
903 information, so for this we need a good way to keep the translations
904 in sync. And we want it to be easy for our users to improve the
905 documentation, avoiding the need to learn special formats or tools to
906 contribute, and the obvious way to do this is to make it possible to
907 edit the documentation using a web browser. We also want it to be
908 easy for translators to keep the translation up to date, and give them
909 help in figuring out what need to be translated. Here is the list of
910 tools and the process we have found trying to reach all these
911 goals.&lt;/p&gt;
912
913 &lt;p&gt;We maintain the authoritative source of our manual in the
914 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
915 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
916 front page with references to the different chapters, several pages
917 for each chapter, and finally one &quot;collection page&quot; gluing all the
918 chapters together into one large web page (aka
919 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
920 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
921 processing and translations. Thanks to the fact that the
922 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
923 wiki.debian.org support exporting pages in
924 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
925 the list of pages to export using the raw version of the AllInOne
926 page, loop over each of them to generate a Docbook XML version of the
927 manual. This process also download images and transform image
928 references to use the locally downloaded images. The generated
929 Docbook XML files are slightly broken, so some post-processing is done
930 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
931 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
932 a handfull of images. The XML file can now be used to generate PDF, HTML
933 and epub versions of the English manual. This is the basic step of
934 our process, making PDF (using dblatex), HTML (using xsltproc) and
935 epub (using dbtoepub) version from Docbook XML, and the resulting files
936 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
937
938 &lt;p&gt;But English documentation is not enough for us. We want translated
939 documentation too, and we want to make it easy for translators to
940 track the English original. For this we use the
941 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
942 which allow us to transform the English Docbook XML file into a
943 translation file (a .pot file), usable with the normal gettext based
944 translation tools used by those translating free software. The pot
945 file is used to create and maintain translation files (several .po
946 files), which the translations update with the native language
947 translations of all titles, paragraphs and blocks of text in the
948 original. The next step is combining the original English Docbook XML
949 and the translation file (say debian-edu-wheezy-manual.nb.po), to
950 create a translated Docbook XML file (in this case
951 debian-edu-wheezy-manual.nb.xml). This translated (or partly
952 translated, if the translation is not complete) Docbook XML file can
953 then be used like the original to create a PDF, HTML and epub version
954 of the documentation.&lt;/p&gt;
955
956 &lt;p&gt;The translators use different tools to edit the .po files. We
957 recommend using
958 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
959 while some use emacs and vi, others can use web based editors like
960 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
961 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
962 is where the .po file end up, in our git repository. Updated
963 translations can either be committed directly to git, or submitted as
964 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
965 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
966
967 &lt;p&gt;One challenge is images, which both might need to be translated (if
968 they show translated user applications), and are needed in different
969 formats when creating PDF and HTML versions (epub is a HTML version in
970 this regard). For this we transform the original PNG images to the
971 needed density and format during build, and have a way to provide
972 translated images by storing translated versions in
973 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
974 package maintainers know more.&lt;/p&gt;
975
976 &lt;p&gt;If you wonder what the result look like, we provide
977 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
978 of the documentation packages on the web&lt;/a&gt;. See for example the
979 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
980 PDF version&lt;/a&gt; or the
981 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
982 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
983 but perhaps it will be done in the future.&lt;/p&gt;
984
985 &lt;p&gt;To learn more, check out
986 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
987 debian-edu-doc package&lt;/a&gt;,
988 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
989 manual on the wiki&lt;/a&gt; and
990 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
991 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
992 </description>
993 </item>
994
995 <item>
996 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
997 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
998 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
999 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1000 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1001 related packages relevant for the computer installed automatically.
1002 So I implemented one, using
1003 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1004 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1005 run tasksel as user root. You should be presented with a new option,
1006 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1007 select it, tasksel will install the packages isenkram claim is fit for
1008 the current hardware, hot pluggable or not.&lt;p&gt;
1009
1010 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1011 description, and the other is the script used to extract the list of
1012 packages to install. The first part is in
1013 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1014 this:&lt;/p&gt;
1015
1016 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1017 Task: isenkram
1018 Section: hardware
1019 Description: Hardware specific packages (autodetected by isenkram)
1020 Based on the detected hardware various hardware specific packages are
1021 proposed.
1022 Test-new-install: mark show
1023 Relevance: 8
1024 Packages: for-current-hardware
1025 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1026
1027 &lt;p&gt;The second part is in
1028 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1029 this:&lt;/p&gt;
1030
1031 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1032 #!/bin/sh
1033 #
1034 (
1035 isenkram-lookup
1036 isenkram-autoinstall-firmware -l
1037 ) | sort -u
1038 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1039
1040 &lt;p&gt;All in all, a very short and simple implementation making it
1041 trivial to install the hardware dependent package we all may want to
1042 have installed on our machines. I&#39;ve not been able to find a way to
1043 get tasksel to tell you exactly which packages it plan to install
1044 before doing the installation. So if you are curious or careful,
1045 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1046
1047 &lt;p&gt;The information about which packages are handling which hardware is
1048 fetched either from the isenkram package itself in
1049 /usr/share/isenkram/, from git.debian.org or from the APT package
1050 database (using the Modaliases header). The APT package database
1051 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1052 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1053 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1054 the python-apt code (bug
1055 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1056 workaround I was able to get rid of the file descriptor leak and
1057 reduce the memory leak from ~30 MiB per hardware detection down to
1058 around 2 MiB per hardware detection. It should make the desktop
1059 daemon a lot more useful. The fix is in version 0.7 uploaded to
1060 unstable today.&lt;/p&gt;
1061
1062 &lt;p&gt;I believe the current way of mapping hardware to packages in
1063 Isenkram is is a good draft, but in the future I expect isenkram to
1064 use the AppStream data source for this. A proposal for getting proper
1065 AppStream support into Debian is floating around as
1066 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1067 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1068 project&lt;/a&gt; will take place this summer to improve the situation. I
1069 look forward to seeing the result, and welcome patches for isenkram to
1070 start using the information when it is ready.&lt;/p&gt;
1071
1072 &lt;p&gt;If you want your package to map to some specific hardware, either
1073 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1074 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1075 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1076 package. See also
1077 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1078 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1079 the information will be migrated to AppStream eventually, but for the
1080 moment I got no better place to store it.&lt;/p&gt;
1081 </description>
1082 </item>
1083
1084 <item>
1085 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1086 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1087 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1088 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1089 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1090 project&lt;/a&gt; is working on providing the software and hardware to make
1091 it easy for non-technical people to host their data and communication
1092 at home, and being able to communicate with their friends and family
1093 encrypted and away from prying eyes. It is still going strong, and
1094 today a major mile stone was reached.&lt;/p&gt;
1095
1096 &lt;p&gt;Today, the last of the packages currently used by the project to
1097 created the system images were accepted into Debian Unstable. It was
1098 the freedombox-setup package, which is used to configure the images
1099 during build and on the first boot. Now all one need to get going is
1100 the build code from the freedom-maker git repository and packages from
1101 Debian. And once the freedombox-setup package enter testing, we can
1102 build everything directly from Debian. :)&lt;/p&gt;
1103
1104 &lt;p&gt;Some key packages used by Freedombox are
1105 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1106 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1107 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1108 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1109 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1110 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1111 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1112 are plans to integrate more packages into the setup. User
1113 documentation is maintained on the Debian wiki. Please
1114 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1115 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1116
1117 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1118 setup, run this on a Debian machine using a user with sudo rights to
1119 become root:&lt;/p&gt;
1120
1121 &lt;p&gt;&lt;pre&gt;
1122 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1123 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1124 u-boot-tools
1125 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1126 freedom-maker
1127 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1128 &lt;/pre&gt;&lt;/p&gt;
1129
1130 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1131 devices. See the README in the freedom-maker git repo for more
1132 details on the build. If you do not want all three images, trim the
1133 make line. Note that the virtualbox-image target is not really
1134 virtualbox specific. It create a x86 image usable in kvm, qemu,
1135 vmware and any other x86 virtual machine environment. You might need
1136 the version of vmdebootstrap in Jessie to get the build working, as it
1137 include fixes for a race condition with kpartx.&lt;/p&gt;
1138
1139 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1140 method, boot a Debian Wheezy ISO and use this boot argument to load
1141 the preseed values:&lt;/p&gt;
1142
1143 &lt;p&gt;&lt;pre&gt;
1144 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;
1145 &lt;/pre&gt;&lt;/p&gt;
1146
1147 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1148 it still work.&lt;/p&gt;
1149
1150 &lt;p&gt;If you wonder how to help, one task you could look at is using
1151 systemd as the boot system. It will become the default for Linux in
1152 Jessie, so we need to make sure it is usable on the Freedombox. I did
1153 a simple test a few weeks ago, and noticed dnsmasq failed to start
1154 during boot when using systemd. I suspect there are other problems
1155 too. :) To detect problems, there is a test suite included, which can
1156 be run from the plinth web interface.&lt;/p&gt;
1157
1158 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1159 us get the new release published. :) Please join us on
1160 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1161 irc.debian.org)&lt;/a&gt; and
1162 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1163 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1164 </description>
1165 </item>
1166
1167 <item>
1168 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1169 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1170 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1171 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1172 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1173 solution for use at home. My requirements are simple, it must be
1174 cheap and locally encrypted (in other words, I keep the encryption
1175 keys, the storage provider do not have access to my private files).
1176 One idea me and my friends had many years ago, before the cloud
1177 storage providers showed up, was to use Google mail as storage,
1178 writing a Linux block device storing blocks as emails in the mail
1179 service provided by Google, and thus get heaps of free space. On top
1180 of this one can add encryption, RAID and volume management to have
1181 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1182 I never found time to implement such system. But the last few weeks I
1183 have looked at a system called
1184 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1185 mounted network backed file system with the features I need.&lt;/p&gt;
1186
1187 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1188 handling several different storage providers, any with Amazon S3,
1189 Google Drive or OpenStack API. There are heaps of such storage
1190 providers. S3QL can also use a local directory as storage, which
1191 combined with sshfs allow for file storage on any ssh server. S3QL
1192 include support for encryption, compression, de-duplication, snapshots
1193 and immutable file systems, allowing me to mount the remote storage as
1194 a local mount point, look at and use the files as if they were local,
1195 while the content is stored in the cloud as well. This allow me to
1196 have a backup that should survive fire. The file system can not be
1197 shared between several machines at the same time, as only one can
1198 mount it at the time, but any machine with the encryption key and
1199 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1200
1201 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1202 package is included already. So to get started, run &lt;tt&gt;apt-get
1203 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1204 Greenqloud, after reading their nice recipe on
1205 &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
1206 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1207 in Iceland more than those in USA when it come to keeping my personal
1208 data safe and private, and thus would rather spend money on a company
1209 in Iceland. Another nice recipe is available from the article
1210 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1211 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1212 Admin magazine. When the provider is picked, figure out how to get
1213 the API key needed to connect to the storage API. With Greencloud,
1214 the key did not show up until I had added payment details to my
1215 account.&lt;/p&gt;
1216
1217 &lt;p&gt;Armed with the API access details, it is time to create the file
1218 system. First, create a new bucket in the cloud. This bucket is the
1219 file system storage area. I picked a bucket name reflecting the
1220 machine that was going to store data there, but any name will do.
1221 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1222 the API login and password, and a locally created password. Store it
1223 all in ~root/.s3ql/authinfo2 like this:
1224
1225 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1226 [s3c]
1227 storage-url: s3c://s.greenqloud.com:443/bucket-name
1228 backend-login: API-login
1229 backend-password: API-password
1230 fs-passphrase: local-password
1231 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1232
1233 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1234 but any sensible way to create a fairly random password should do it.
1235 Armed with these details, it is now time to run mkfs, entering the API
1236 details and password to create it:&lt;/p&gt;
1237
1238 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1239 # mkdir -m 700 /var/lib/s3ql-cache
1240 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1241 --ssl s3c://s.greenqloud.com:443/bucket-name
1242 Enter backend login:
1243 Enter backend password:
1244 Before using S3QL, make sure to read the user&#39;s guide, especially
1245 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1246 Enter encryption password:
1247 Confirm encryption password:
1248 Generating random encryption key...
1249 Creating metadata tables...
1250 Dumping metadata...
1251 ..objects..
1252 ..blocks..
1253 ..inodes..
1254 ..inode_blocks..
1255 ..symlink_targets..
1256 ..names..
1257 ..contents..
1258 ..ext_attributes..
1259 Compressing and uploading metadata...
1260 Wrote 0.00 MB of compressed metadata.
1261 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1262
1263 &lt;p&gt;The next step is mounting the file system to make the storage available.
1264
1265 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1266 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1267 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1268 Using 4 upload threads.
1269 Downloading and decompressing metadata...
1270 Reading metadata...
1271 ..objects..
1272 ..blocks..
1273 ..inodes..
1274 ..inode_blocks..
1275 ..symlink_targets..
1276 ..names..
1277 ..contents..
1278 ..ext_attributes..
1279 Mounting filesystem...
1280 # df -h /s3ql
1281 Filesystem Size Used Avail Use% Mounted on
1282 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1283 #
1284 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1285
1286 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1287 backups in it, and as the metadata used by rsync is downloaded at
1288 mount time, no network traffic (and storage cost) is triggered by
1289 running rsync. To unmount, one should not use the normal umount
1290 command, as this will not flush the cache to the cloud storage, but
1291 instead running the umount.s3ql command like this:
1292
1293 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1294 # umount.s3ql /s3ql
1295 #
1296 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1297
1298 &lt;p&gt;There is a fsck command available to check the file system and
1299 correct any problems detected. This can be used if the local server
1300 crashes while the file system is mounted, to reset the &quot;already
1301 mounted&quot; flag. This is what it look like when processing a working
1302 file system:&lt;/p&gt;
1303
1304 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1305 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1306 Using cached metadata.
1307 File system seems clean, checking anyway.
1308 Checking DB integrity...
1309 Creating temporary extra indices...
1310 Checking lost+found...
1311 Checking cached objects...
1312 Checking names (refcounts)...
1313 Checking contents (names)...
1314 Checking contents (inodes)...
1315 Checking contents (parent inodes)...
1316 Checking objects (reference counts)...
1317 Checking objects (backend)...
1318 ..processed 5000 objects so far..
1319 ..processed 10000 objects so far..
1320 ..processed 15000 objects so far..
1321 Checking objects (sizes)...
1322 Checking blocks (referenced objects)...
1323 Checking blocks (refcounts)...
1324 Checking inode-block mapping (blocks)...
1325 Checking inode-block mapping (inodes)...
1326 Checking inodes (refcounts)...
1327 Checking inodes (sizes)...
1328 Checking extended attributes (names)...
1329 Checking extended attributes (inodes)...
1330 Checking symlinks (inodes)...
1331 Checking directory reachability...
1332 Checking unix conventions...
1333 Checking referential integrity...
1334 Dropping temporary indices...
1335 Backing up old metadata...
1336 Dumping metadata...
1337 ..objects..
1338 ..blocks..
1339 ..inodes..
1340 ..inode_blocks..
1341 ..symlink_targets..
1342 ..names..
1343 ..contents..
1344 ..ext_attributes..
1345 Compressing and uploading metadata...
1346 Wrote 0.89 MB of compressed metadata.
1347 #
1348 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1349
1350 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1351 quick, about the same speed as local file access. Uploading large
1352 amount of data is to me limited by the bandwidth out of and into my
1353 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1354 which is very close to my upload speed, and downloading the same
1355 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1356 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1357 network, not the file system code. I do not know what a good cache
1358 size would be, but suspect that the cache should e larger than your
1359 working set.&lt;/p&gt;
1360
1361 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1362 time. If another machine try, it is told that the file system is
1363 busy:&lt;/p&gt;
1364
1365 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1366 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1367 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1368 Using 8 upload threads.
1369 Backend reports that fs is still mounted elsewhere, aborting.
1370 #
1371 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1372
1373 &lt;p&gt;The file content is uploaded when the cache is full, while the
1374 metadata is uploaded once every 24 hour by default. To ensure the
1375 file system content is flushed to the cloud, one can either umount the
1376 file system, or ask S3QL to flush the cache and metadata using
1377 s3qlctrl:
1378
1379 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1380 # s3qlctrl upload-meta /s3ql
1381 # s3qlctrl flushcache /s3ql
1382 #
1383 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1384
1385 &lt;p&gt;If you are curious about how much space your data uses in the
1386 cloud, and how much compression and deduplication cut down on the
1387 storage usage, you can use s3qlstat on the mounted file system to get
1388 a report:&lt;/p&gt;
1389
1390 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1391 # s3qlstat /s3ql
1392 Directory entries: 9141
1393 Inodes: 9143
1394 Data blocks: 8851
1395 Total data size: 22049.38 MB
1396 After de-duplication: 21955.46 MB (99.57% of total)
1397 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1398 Database size: 2.39 MB (uncompressed)
1399 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1400 #
1401 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1402
1403 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1404 storage. I did not try to locate them all, but am aware of at least
1405 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1406 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1407 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1408 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1409 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1410 accept payment in Bitcoin. Pick one that suit your need. Some of
1411 them provide several GiB of free storage, but the prize models are
1412 quite different and you will have to figure out what suits you
1413 best.&lt;/p&gt;
1414
1415 &lt;p&gt;While researching this blog post, I had a look at research papers
1416 and posters discussing the S3QL file system. There are several, which
1417 told me that the file system is getting a critical check by the
1418 science community and increased my confidence in using it. One nice
1419 poster is titled
1420 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1421 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1422 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1423 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1424 and Pamela Smith. Please have a look.&lt;/p&gt;
1425
1426 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1427 check out the mounted S3QL file system to see if it would be usable as
1428 a home directory (in other word, that it provided POSIX semantics when
1429 it come to locking and umask handling etc). Running
1430 &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
1431 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1432 no error was found. So the file system can be used for home
1433 directories, if one chooses to do so.&lt;/p&gt;
1434
1435 &lt;p&gt;If you do not want a locally file system, and want something that
1436 work without the Linux fuse file system, I would like to mention the
1437 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1438 provide locally encrypted backup using a command line client. It have
1439 a nicer access control system, where one can split out read and write
1440 access, allowing some systems to write to the backup and others to
1441 only read from it.&lt;/p&gt;
1442
1443 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1444 activities, please send Bitcoin donations to my address
1445 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1446 </description>
1447 </item>
1448
1449 <item>
1450 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1451 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1452 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1453 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1454 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1455 project&lt;/a&gt; is working on providing the software and hardware for
1456 making it easy for non-technical people to host their data and
1457 communication at home, and being able to communicate with their
1458 friends and family encrypted and away from prying eyes. It has been
1459 going on for a while, and is slowly progressing towards a new test
1460 release (0.2).&lt;/p&gt;
1461
1462 &lt;p&gt;And what day could be better than the Pi day to announce that the
1463 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1464 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1465 system), and can also be installed using a Debian installer preseed
1466 file. The Debian based Freedombox is now based on Debian Jessie,
1467 where most of the needed packages used are already present. Only one,
1468 the freedombox-setup package, is missing. To try to build your own
1469 boot image to test the current status, fetch the freedom-maker scripts
1470 and build using
1471 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1472 with a user with sudo access to become root:
1473
1474 &lt;pre&gt;
1475 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1476 freedom-maker
1477 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1478 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1479 u-boot-tools
1480 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1481 &lt;/pre&gt;
1482
1483 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1484 devices. See the README for more details on the build. If you do not
1485 want all three images, trim the make line. But note that thanks to &lt;a
1486 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1487 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1488 kpartx call.&lt;/p&gt;
1489
1490 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1491 method, boot a Debian Wheezy ISO and use this boot argument to load
1492 the preseed values:&lt;/p&gt;
1493
1494 &lt;pre&gt;
1495 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;
1496 &lt;/pre&gt;
1497
1498 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1499 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1500 currently hang while setting up APT sources. Killing the
1501 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1502 installation will get the installation going. This affect all
1503 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1504
1505 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1506 us get the new release published. :) Please join us on
1507 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1508 irc.debian.org)&lt;/a&gt; and
1509 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1510 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1511 </description>
1512 </item>
1513
1514 <item>
1515 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1516 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1517 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1518 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1519 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1520 innetgr tools, because I needed them in
1521 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1522 ng-utils, and it has served me well. I placed the project under the
1523 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1524 repository. But many years ago, the CVS repository was dropped (lost,
1525 not migrated to new hardware, not sure), and the project have lacked a
1526 proper home since then.&lt;/p&gt;
1527
1528 &lt;p&gt;Last summer, I had a look at the package and made a new release
1529 fixing a irritating crash bug, but was unable to store the changes in
1530 a proper source control system. I applied for a project on
1531 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1532 to follow up on it. Until today. :)&lt;/p&gt;
1533
1534 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1535 now have a new home, and a git repository with the highlight of the
1536 history of the project. I published all release tarballs and imported
1537 them into the git repository. As the project is really stable and not
1538 expected to gain new features any time soon, I decided to make a new
1539 release and call it 1.0. Visit the new project home on
1540 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1541 if you want to check it out. The new version is also uploaded into
1542 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1543 </description>
1544 </item>
1545
1546 <item>
1547 <title>Testing sysvinit from experimental in Debian Hurd</title>
1548 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1549 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1550 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1551 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1552 their changes into sysvinit, to allow them to use the normal sysvinit
1553 boot system instead of their old one. This follow up on the
1554 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1555 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1556 get Debian on Hurd working more like Debian on Linux. To get started,
1557 I downloaded a prebuilt hard disk image from
1558 &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;,
1559 and started it using virt-manager.&lt;/p&gt;
1560
1561 &lt;p&gt;The first think I had to do after logging in (root without any
1562 password) was to get the network operational. I followed
1563 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1564 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1565 commands as root to get the machine to accept a IP address from the
1566 kvm internal DHCP server:&lt;/p&gt;
1567
1568 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1569 settrans -fgap /dev/netdde /hurd/netdde
1570 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1571 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1572 dhclient /dev/eth0
1573 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1574
1575 &lt;p&gt;After this, the machine had internet connectivity, and I could
1576 upgrade it and install the sysvinit packages from experimental and
1577 enable it as the default boot system in Hurd.&lt;/p&gt;
1578
1579 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1580 running on the machine it for ssh login to work a password need to be
1581 set. Also, note that a bug somewhere in openssh on Hurd block
1582 compression from working. Remember to turn that off on the client
1583 side.&lt;/p&gt;
1584
1585 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1586 stuff:&lt;/p&gt;
1587
1588 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1589 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1590 deb http://http.debian.net/debian/ experimental main
1591 EOF
1592 apt-get update
1593 apt-get dist-upgrade
1594 apt-get install -t experimental initscripts sysv-rc sysvinit \
1595 sysvinit-core sysvinit-utils
1596 update-alternatives --config runsystem
1597 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1598
1599 &lt;p&gt;To reboot after switching boot system, you have to use
1600 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1601 yet a sysvinit process able to receive the signals from the normal
1602 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1603 upgrading every package and rebooting, the network come up with DHCP
1604 after boot as it should, and the settrans/pkill hack mentioned at the
1605 start is no longer needed. But for some strange reason, there are no
1606 longer any login prompt in the virtual console, so I logged in using
1607 ssh instead.
1608
1609 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1610 fail some times. No idea what the cause is, but hope the Hurd porters
1611 figure it out. At least Justus said on IRC (#debian-hurd on
1612 irc.debian.org) that they are aware of the problem. A way to reduce
1613 the impact is to upgrade to the Hurd packages built by Justus by
1614 adding this repository to the machine:&lt;/p&gt;
1615
1616 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1617 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1618 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1619 EOF
1620 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1621
1622 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1623 http://ftp.debian-ports.org/debian, because some of the packages in
1624 unstable do not yet include the required patches that are lingering in
1625 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1626
1627 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1628 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1629 i emacs - GNU Emacs editor (metapackage)
1630 i gdb - GNU Debugger
1631 i hurd-recommended - Miscellaneous translators
1632 i isc-dhcp-client - ISC DHCP client
1633 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1634 i libc-bin - Embedded GNU C Library: Binaries
1635 i libc-dev-bin - Embedded GNU C Library: Development binaries
1636 i libc0.3 - Embedded GNU C Library: Shared libraries
1637 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1638 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1639 i multiarch-support - Transitional package to ensure multiarch compatibilit
1640 i A x11-common - X Window System (X.Org) infrastructure
1641 i xorg - X.Org X Window System
1642 i A xserver-xorg - X.Org X server
1643 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1644 #
1645 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1646
1647 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1648 X.org did not work out of the box and I never took the time to follow
1649 the porters instructions to fix it. This time I was interested in the
1650 command line stuff.&lt;p&gt;
1651 </description>
1652 </item>
1653
1654 <item>
1655 <title>New chrpath release 0.16</title>
1656 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1657 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1658 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1659 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1660 find problems in C, C++ and Java code using static source code
1661 analysis. It can detect a lot of different problems, and is very
1662 useful to find memory and locking bugs in the error handling part of
1663 the source. The company behind it provide
1664 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1665 a community service&lt;/a&gt;, and many hundred free software projects are
1666 already checked. A few days ago I decided to have a closer look at
1667 the Coverity system, and discovered that the
1668 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1669 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1670 projects I am involved with was already registered. But these are
1671 fairly big, and I would also like to have a small and easy project to
1672 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1673 checking of the chrpath project&lt;/a&gt;. It was
1674 added to the checker and discovered seven potential defects. Six of
1675 these were real, mostly resource &quot;leak&quot; when the program detected an
1676 error. Nothing serious, as the resources would be released a fraction
1677 of a second later when the program exited because of the error, but it
1678 is nice to do it right in case the source of the program some time in
1679 the future end up in a library. Having fixed all defects and added
1680 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1681 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1682 publish a new release. These are the release notes:&lt;/p&gt;
1683
1684 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1685
1686 &lt;ul&gt;
1687
1688 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1689 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1690 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1691
1692 &lt;/ul&gt;
1693
1694 &lt;p&gt;You can
1695 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1696 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1697 project if something is wrong with the new release. The test suite
1698 did not discover any old errors, so if you find a new one, please also
1699 include a test suite check.&lt;/p&gt;
1700 </description>
1701 </item>
1702
1703 <item>
1704 <title>New chrpath release 0.15</title>
1705 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1707 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1708 <description>&lt;p&gt;After many years break from the package and a vain hope that
1709 development would be continued by someone else, I finally pulled my
1710 acts together this morning and wrapped up a new release of chrpath,
1711 the command line tool to modify the rpath and runpath of already
1712 compiled ELF programs. The update was triggered by the persistence of
1713 Isha Vishnoi at IBM, which needed a new config.guess file to get
1714 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1715 is working on. I checked the
1716 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1717 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1718 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1719 packages for interesting patches (failed to find the source from
1720 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1721 These are the release notes:&lt;/p&gt;
1722
1723 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1724
1725 &lt;ul&gt;
1726
1727 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1728 with newer architectures. Thanks to isha vishnoi for the heads
1729 up.&lt;/li&gt;
1730
1731 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1732
1733 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1734 Matthias Klose.&lt;/li&gt;
1735
1736 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1737 Petr Machata found in Fedora.&lt;/li&gt;
1738
1739 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1740 .dynamic is a NULL terminated string. Based on patch found in
1741 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1742
1743 &lt;/ul&gt;
1744
1745 &lt;p&gt;You can
1746 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1747 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1748 project if something is wrong with the new release. The test suite
1749 did not discover any old errors, so if you find a new one, please also
1750 include a testsuite check.&lt;/p&gt;
1751 </description>
1752 </item>
1753
1754 <item>
1755 <title>Debian init.d boot script example for rsyslog</title>
1756 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1757 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1758 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1759 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1760 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1761 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1762 init.d scripts at all. Here is an example init.d script, ie a rewrite
1763 of /etc/init.d/rsyslog:&lt;/p&gt;
1764
1765 &lt;p&gt;&lt;pre&gt;
1766 #!/lib/init/init-d-script
1767 ### BEGIN INIT INFO
1768 # Provides: rsyslog
1769 # Required-Start: $remote_fs $time
1770 # Required-Stop: umountnfs $time
1771 # X-Stop-After: sendsigs
1772 # Default-Start: 2 3 4 5
1773 # Default-Stop: 0 1 6
1774 # Short-Description: enhanced syslogd
1775 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1776 # It is quite compatible to stock sysklogd and can be
1777 # used as a drop-in replacement.
1778 ### END INIT INFO
1779 DESC=&quot;enhanced syslogd&quot;
1780 DAEMON=/usr/sbin/rsyslogd
1781 &lt;/pre&gt;&lt;/p&gt;
1782
1783 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1784 script was 137 lines, and the above is just 15 lines, most of it meta
1785 info/comments.&lt;/p&gt;
1786
1787 &lt;p&gt;How to do this, you ask? Well, one create a new script
1788 /lib/init/init-d-script looking something like this:
1789
1790 &lt;p&gt;&lt;pre&gt;
1791 #!/bin/sh
1792
1793 # Define LSB log_* functions.
1794 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1795 # and status_of_proc is working.
1796 . /lib/lsb/init-functions
1797
1798 #
1799 # Function that starts the daemon/service
1800
1801 #
1802 do_start()
1803 {
1804 # Return
1805 # 0 if daemon has been started
1806 # 1 if daemon was already running
1807 # 2 if daemon could not be started
1808 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1809 || return 1
1810 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1811 $DAEMON_ARGS \
1812 || return 2
1813 # Add code here, if necessary, that waits for the process to be ready
1814 # to handle requests from services started subsequently which depend
1815 # on this one. As a last resort, sleep for some time.
1816 }
1817
1818 #
1819 # Function that stops the daemon/service
1820 #
1821 do_stop()
1822 {
1823 # Return
1824 # 0 if daemon has been stopped
1825 # 1 if daemon was already stopped
1826 # 2 if daemon could not be stopped
1827 # other if a failure occurred
1828 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1829 RETVAL=&quot;$?&quot;
1830 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1831 # Wait for children to finish too if this is a daemon that forks
1832 # and if the daemon is only ever run from this initscript.
1833 # If the above conditions are not satisfied then add some other code
1834 # that waits for the process to drop all resources that could be
1835 # needed by services started subsequently. A last resort is to
1836 # sleep for some time.
1837 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1838 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1839 # Many daemons don&#39;t delete their pidfiles when they exit.
1840 rm -f $PIDFILE
1841 return &quot;$RETVAL&quot;
1842 }
1843
1844 #
1845 # Function that sends a SIGHUP to the daemon/service
1846 #
1847 do_reload() {
1848 #
1849 # If the daemon can reload its configuration without
1850 # restarting (for example, when it is sent a SIGHUP),
1851 # then implement that here.
1852 #
1853 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1854 return 0
1855 }
1856
1857 SCRIPTNAME=$1
1858 scriptbasename=&quot;$(basename $1)&quot;
1859 echo &quot;SN: $scriptbasename&quot;
1860 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1861 script=&quot;$1&quot;
1862 shift
1863 . $script
1864 else
1865 exit 0
1866 fi
1867
1868 NAME=$(basename $DAEMON)
1869 PIDFILE=/var/run/$NAME.pid
1870
1871 # Exit if the package is not installed
1872 #[ -x &quot;$DAEMON&quot; ] || exit 0
1873
1874 # Read configuration variable file if it is present
1875 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
1876
1877 # Load the VERBOSE setting and other rcS variables
1878 . /lib/init/vars.sh
1879
1880 case &quot;$1&quot; in
1881 start)
1882 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
1883 do_start
1884 case &quot;$?&quot; in
1885 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1886 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1887 esac
1888 ;;
1889 stop)
1890 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
1891 do_stop
1892 case &quot;$?&quot; in
1893 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1894 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1895 esac
1896 ;;
1897 status)
1898 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
1899 ;;
1900 #reload|force-reload)
1901 #
1902 # If do_reload() is not implemented then leave this commented out
1903 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
1904 #
1905 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
1906 #do_reload
1907 #log_end_msg $?
1908 #;;
1909 restart|force-reload)
1910 #
1911 # If the &quot;reload&quot; option is implemented then remove the
1912 # &#39;force-reload&#39; alias
1913 #
1914 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
1915 do_stop
1916 case &quot;$?&quot; in
1917 0|1)
1918 do_start
1919 case &quot;$?&quot; in
1920 0) log_end_msg 0 ;;
1921 1) log_end_msg 1 ;; # Old process is still running
1922 *) log_end_msg 1 ;; # Failed to start
1923 esac
1924 ;;
1925 *)
1926 # Failed to stop
1927 log_end_msg 1
1928 ;;
1929 esac
1930 ;;
1931 *)
1932 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
1933 exit 3
1934 ;;
1935 esac
1936
1937 :
1938 &lt;/pre&gt;&lt;/p&gt;
1939
1940 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
1941 lot. I did not really polish the approach, so it might not always
1942 work out of the box, but you get the idea. I did not try very hard to
1943 optimize it nor make it more robust either.&lt;/p&gt;
1944
1945 &lt;p&gt;A better argument for switching init system in Debian than reducing
1946 the size of init scripts (which is a good thing to do anyway), is to
1947 get boot system that is able to handle the kernel events sensibly and
1948 robustly, and do not depend on the boot to run sequentially. The boot
1949 and the kernel have not behaved sequentially in years.&lt;/p&gt;
1950 </description>
1951 </item>
1952
1953 <item>
1954 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
1955 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
1956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
1957 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
1958 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
1959 remote display access is the preferred solution with oVirt and RedHat
1960 Enterprise Virtualization, and I was sad to discover the other day
1961 that the browser plugin needed to use these systems seamlessly was
1962 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
1963 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
1964 2013-04-01, so I decided to wrap up a package based on the great work
1965 from Cajus Pollmeier and put it in a collab-maint maintained git
1966 repository to get a package I could use. I would very much like
1967 others to help me maintain the package (or just take over, I do not
1968 mind), but as no-one had volunteered so far, I just uploaded it to
1969 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
1970
1971 &lt;p&gt;The source is now available from
1972 &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;
1973 </description>
1974 </item>
1975
1976 <item>
1977 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
1978 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
1979 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
1980 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
1981 <description>&lt;p&gt;The
1982 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
1983 program is a a very nice system to create virtual machine images. It
1984 create a image file, add a partition table, mount it and run
1985 debootstrap in the mounted directory to create a Debian system on a
1986 stick. Yesterday, I decided to try to teach it how to make images for
1987 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1988 of a plan to simplify the build system for
1989 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1990 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1991 the virtualbox images, but its current build system made multistrap
1992 based system for Dreamplug images, and it is lacking support for
1993 Raspberry Pi.&lt;/p&gt;
1994
1995 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1996 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1997 code and adjusted it to be able to build armel images on my amd64
1998 Debian laptop. I ended up giving vmdebootstrap five new options,
1999 allowing me to replicate the image creation process I use to make
2000 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2001 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2002 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2003 call debootstrap with --foreign and to copy the handler into the
2004 generated chroot before running the second stage. This allow
2005 vmdebootstrap to create armel images on an amd64 host. Next I added
2006 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2007 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2008 given file system type, allowing me to create an image with a vfat
2009 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2010 variant&lt;/tt&gt; option to allow me to create smaller images without the
2011 Debian base system packages installed. Finally, I added an option
2012 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2013 as a boot loader. It is not needed on the Raspberry Pi and probably
2014 most other non-x86 architectures. The changes were accepted by the
2015 upstream author of vmdebootstrap yesterday and today, and is now
2016 available from
2017 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2018 upstream project page&lt;/a&gt;.&lt;/p&gt;
2019
2020 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2021 create a small script (the customize script) to add the non-free
2022 binary blob needed to boot the Raspberry Pi and the APT source
2023 list:&lt;/p&gt;
2024
2025 &lt;p&gt;&lt;pre&gt;
2026 #!/bin/sh
2027 set -e # Exit on first error
2028 rootdir=&quot;$1&quot;
2029 cd &quot;$rootdir&quot;
2030 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2031 deb http://http.debian.net/debian/ jessie main contrib non-free
2032 EOF
2033 # Install non-free binary blob needed to boot Raspberry Pi. This
2034 # install a kernel somewhere too.
2035 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2036 -O $rootdir/usr/bin/rpi-update
2037 chmod a+x $rootdir/usr/bin/rpi-update
2038 mkdir -p $rootdir/lib/modules
2039 touch $rootdir/boot/start.elf
2040 chroot $rootdir rpi-update
2041 &lt;/pre&gt;&lt;/p&gt;
2042
2043 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2044 to build the image:&lt;/p&gt;
2045
2046 &lt;pre&gt;
2047 sudo ./vmdebootstrap \
2048 --variant minbase \
2049 --arch armel \
2050 --distribution jessie \
2051 --mirror http://http.debian.net/debian \
2052 --image test.img \
2053 --size 600M \
2054 --bootsize 64M \
2055 --boottype vfat \
2056 --log-level debug \
2057 --verbose \
2058 --no-kernel \
2059 --no-extlinux \
2060 --root-password raspberry \
2061 --hostname raspberrypi \
2062 --foreign /usr/bin/qemu-arm-static \
2063 --customize `pwd`/customize \
2064 --package netbase \
2065 --package git-core \
2066 --package binutils \
2067 --package ca-certificates \
2068 --package wget \
2069 --package kmod
2070 &lt;/pre&gt;&lt;/p&gt;
2071
2072 &lt;p&gt;The list of packages being installed are the ones needed by
2073 rpi-update to make the image bootable on the Raspberry Pi, with the
2074 exception of netbase, which is needed by debootstrap to find
2075 /etc/hosts with the minbase variant. I really wish there was a way to
2076 set up an Raspberry Pi using only packages in the Debian archive, but
2077 that is not possible as far as I know, because it boots from the GPU
2078 using a non-free binary blob.&lt;/p&gt;
2079
2080 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2081 probably a few others installed. I have not checked the complete
2082 build dependency list.&lt;/p&gt;
2083
2084 &lt;p&gt;The resulting image will not use the hardware floating point unit
2085 on the Raspberry PI, because the armel architecture in Debian is not
2086 optimized for that use. So the images created will be a bit slower
2087 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2088 </description>
2089 </item>
2090
2091 <item>
2092 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2093 <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>
2094 <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>
2095 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2096 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2097 wider attention. I recommend signing and donating to each one of
2098 these. :)&lt;/p&gt;
2099
2100 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2101 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2102 Women program which is a Google Summer of Code like initiative to get
2103 more women involved in free software. One debian sponsor has offered
2104 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2105 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2106 hope you will to. :)&lt;/p&gt;
2107
2108 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2109 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2110 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2111 take place these days, and their need to fund the work. I&#39;ve already
2112 donated. Are you next?&lt;/p&gt;
2113
2114 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2115 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2116 statement under the heading
2117 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2118 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2119 Norwegian government. So far 499 signatures. I hope you will sign it
2120 too.&lt;/p&gt;
2121 </description>
2122 </item>
2123
2124 <item>
2125 <title>Videos about the Freedombox project - for inspiration and learning</title>
2126 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2127 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2128 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2129 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2130 project&lt;/a&gt; have been going on for a while, and have presented the
2131 vision, ideas and solution several places. Here is a little
2132 collection of videos of talks and presentation of the project.&lt;/p&gt;
2133
2134 &lt;ul&gt;
2135
2136 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2137 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2138
2139 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2140 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2141
2142 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2143 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2144 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2145 (Youtube)&lt;/li&gt;
2146
2147 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2148 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2149
2150 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2151 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2152
2153 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2154 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2155 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2156
2157 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2158 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2159 (Youtube)&lt;/li&gt;
2160
2161 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2162 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2163
2164 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2165 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2166
2167 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2168 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2169 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2170
2171 &lt;/ul&gt;
2172
2173 &lt;p&gt;A larger list is available from
2174 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2175 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2176
2177 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2178 Jessie is coming along quite well, and soon both Owncloud and using
2179 Tor should be available for testers of the Freedombox solution. :) In
2180 a few weeks I hope everything needed to test it is included in Debian.
2181 The withsqlite package is already in Debian, and the plinth package is
2182 pending in NEW. The third and vital part of that puzzle is the
2183 metapackage/setup framework, which is still pending an upload. Join
2184 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2185 (#freedombox on irc.debian.org)&lt;/a&gt; and
2186 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2187 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2188 </description>
2189 </item>
2190
2191 <item>
2192 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2193 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2194 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2195 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2196 <description>&lt;p&gt;I was introduced to the
2197 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2198 in 2010, when Eben Moglen presented his vision about serving the need
2199 of non-technical people to keep their personal information private and
2200 within the legal protection of their own homes. The idea is to give
2201 people back the power over their network and machines, and return
2202 Internet back to its intended peer-to-peer architecture. Instead of
2203 depending on a central service, the Freedombox will give everyone
2204 control over their own basic infrastructure.&lt;/p&gt;
2205
2206 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2207 taken priority. But this summers nasty news about the misuse of trust
2208 and privilege exercised by the &quot;western&quot; intelligence gathering
2209 communities increased my eagerness to contribute to a point where I
2210 actually started working on the project a while back.&lt;/p&gt;
2211
2212 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2213 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2214 create a simple and cheap Debian based appliance that anyone can hook
2215 up in their home and get access to secure and private services and
2216 communication. The initial deployment platform have been the
2217 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2218 which is a piece of hardware I do not own. So to be able to test what
2219 the current Freedombox setup look like, I had to come up with a way to install
2220 it on some hardware I do have access to. I have rewritten the
2221 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2222 image build framework to use .deb packages instead of only copying
2223 setup into the boot images, and thanks to this rewrite I am able to
2224 set up any machine supported by Debian Wheezy as a Freedombox, using
2225 the previously mentioned deb (and a few support debs for packages
2226 missing in Debian).&lt;/p&gt;
2227
2228 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2229 scripts
2230 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2231 and a administrative web interface
2232 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2233 withsqlite), as well as a privacy enhancing proxy based on
2234 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2235 (freedombox-privoxy). There is also a web/javascript based XMPP
2236 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2237 trying (unsuccessfully so far) to talk to the XMPP server
2238 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2239 web interface is pluggable, and the goal is to use it to enable OpenID
2240 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2241 this is really working yet, see
2242 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2243 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2244 on github at the moment. The HTTP proxy is operational out of the
2245 box, and the admin web interface can be used to add/remove plinth
2246 users. I&#39;ve not been able to do anything else with it so far, but
2247 know there are several branches spread around github and other places
2248 with lots of half baked features.&lt;/p&gt;
2249
2250 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2251 following recipes should work to give you a test machine to poke
2252 at.&lt;/p&gt;
2253
2254 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2255
2256 &lt;ol&gt;
2257
2258 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2259 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2260 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2261 to the Debian installer:&lt;p&gt;
2262 &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;
2263
2264 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2265 install on.&lt;/li&gt;
2266
2267 &lt;li&gt;When the installation is finished and the machine have rebooted a
2268 few times, your Freedombox is ready for testing.&lt;/li&gt;
2269
2270 &lt;/ol&gt;
2271
2272 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2273
2274 &lt;ol&gt;
2275
2276 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2277 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2278 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2279 &lt;pre&gt;
2280 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2281 &lt;/pre&gt;&lt;/li&gt;
2282 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2283 &lt;pre&gt;
2284 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2285 apt-key add -
2286 apt-get update
2287 apt-get install freedombox-setup
2288 /usr/lib/freedombox/setup
2289 &lt;/pre&gt;&lt;/li&gt;
2290 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2291
2292 &lt;/ol&gt;
2293
2294 &lt;p&gt;You can test it on other architectures too, but because the
2295 freedombox-privoxy package is binary, it will only work as intended on
2296 the architectures where I have had time to build the binary and put it
2297 in my APT repository. But do not let this stop you. It is only a
2298 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2299
2300 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2301 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2302 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2303 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2304
2305 &lt;p&gt;Please let me know if this works for you, or if you have any
2306 problems. We gather on the IRC channel
2307 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2308 irc.debian.org and the
2309 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2310 mailing list&lt;/a&gt;.&lt;/p&gt;
2311
2312 &lt;p&gt;Once you get your freedombox operational, you can visit
2313 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2314 welcome screen (dead end - do not be surprised if you are unable to
2315 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2316 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2317 default password is &#39;secret&#39;.&lt;/p&gt;
2318 </description>
2319 </item>
2320
2321 <item>
2322 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2323 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2324 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2325 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2326 <description>&lt;p&gt;Earlier, I reported about
2327 &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
2328 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2329 told by IBM that the original disk should be thrown away. And as
2330 there no longer was a problem if I bricked the firmware, I decided
2331 today to try to install Intel firmware to replace the Lenovo firmware
2332 currently on the disk.&lt;/p&gt;
2333
2334 &lt;p&gt;I searched the Intel site for firmware, and found
2335 &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;
2336 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2337 according to the site should contain the latest firmware for SSD
2338 disks. I inserted the broken disk in one of my spare laptops and
2339 booted the ISO from a USB stick. The disk was recognized, but the
2340 program claimed the newest firmware already were installed and refused
2341 to insert any Intel firmware. So no change, and the disk is still
2342 unable to handle write load. :( I guess the only way to get them
2343 working would be if Lenovo releases new firmware. No idea how likely
2344 that is. Anyway, just blogging about this test for completeness. I
2345 got a working Samsung disk, and see no point in spending more time on
2346 the broken disks.&lt;/p&gt;
2347 </description>
2348 </item>
2349
2350 <item>
2351 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2352 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2354 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2355 <description>&lt;p&gt;Today I switched to
2356 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2357 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2358 my new Thinkpad X230, which was delivered with an
2359 &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
2360 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2361 sustained writes. My hardware supplier have been very forthcoming in
2362 trying to find a solution, and after first trying with another
2363 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2364 disk instead to fix it once and for all. The Samsung disk survived
2365 the installation of Debian with encrypted disks (filling the disk with
2366 random data during installation killed the first two), and I thus
2367 decided to trust it with my data. I have installed it as a Debian Edu
2368 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2369 server at home using Kerberos and LDAP, and will use it as my work
2370 station from now on.&lt;/p&gt;
2371
2372 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2373 Debian Wheezy default installation need to be tuned a bit to increase
2374 performance and increase life time of the disk. The Linux kernel and
2375 user space applications do not yet adjust automatically to such
2376 environment. To make it easier for my self, I created a draft Debian
2377 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2378 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2379 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2380 is set up to adjust the setup of the machine by just installing the
2381 package. If there is any non-SSD disk in the machine, the package
2382 will refuse to install, as I did not try to write any logic to sort
2383 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2384
2385 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2386 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2387 where I set up the machine with one large encrypted partition (in
2388 addition to /boot), put LVM on top of this and set up partitions on
2389 top of this again. See the README file in the package source for the
2390 references I used to pick the settings. At the moment these
2391 parameters are tuned:&lt;/p&gt;
2392
2393 &lt;ul&gt;
2394
2395 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2396 (adding discard to /etc/crypttab)&lt;/li&gt;
2397
2398 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2399 this case a cryptsetup partition) by changing issue_discards from
2400 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2401
2402 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2403 systems.&lt;/li&gt;
2404
2405 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2406 /etc/fstab.&lt;/li&gt;
2407
2408 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2409
2410 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2411 cron.daily).&lt;/li&gt;
2412
2413 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2414 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2415
2416 &lt;/ul&gt;
2417
2418 &lt;p&gt;During installation, I cancelled the part where the installer fill
2419 the disk with random data, as this would kill the SSD performance for
2420 little gain. My goal with the encrypted file system is to ensure
2421 those stealing my laptop end up with a brick and not a working
2422 computer. I have no hope in keeping the really resourceful people
2423 from getting the data on the disk (see
2424 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2425 Thus I concluded that adding the discard option to crypttab is the
2426 right thing to do.&lt;/p&gt;
2427
2428 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2429 it for SSD, but others recommended deadline and a benchmark I found
2430 indicated that deadline might be better for interactive use.&lt;/p&gt;
2431
2432 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2433 and ext4, but read that it would give a performance hit ever time a
2434 file is removed, and thought it best to that that slowdown once a day
2435 instead of during my work.&lt;/p&gt;
2436
2437 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2438 this is already done by Debian Edu.&lt;/p&gt;
2439
2440 &lt;p&gt;I have not yet started on the user space tuning. I expect
2441 iceweasel need some tuning, and perhaps other applications too, but
2442 have not yet had time to investigate those parts.&lt;/p&gt;
2443
2444 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2445 there.&lt;/p&gt;
2446
2447 &lt;p&gt;As for the answer to the question in the title of this blog post,
2448 as far as I know, the only solution I know about is to replace the
2449 disk. It might be possible to flash it with Intel firmware instead of
2450 the Lenovo firmware. But I have not tried and did not want to do so
2451 without approval from Lenovo as I wanted to keep the warranty on the
2452 disk until a solution was found and they wanted the broken disks
2453 back.&lt;/p&gt;
2454 </description>
2455 </item>
2456
2457 <item>
2458 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2459 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2460 <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>
2461 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2462 <description>&lt;p&gt;A few days ago, I wrote about
2463 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2464 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2465 was dying during installation because it is unable to cope with
2466 sustained write. My supplier is in contact with
2467 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2468 replacement disk to try to fix the problem. They decided to send an
2469 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2470
2471 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2472 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2473 same firmware version as the original. This time my hope raised
2474 slightly as the installation progressed, as the original disk used to
2475 die after 4-7% of the disk was written to, while this time it kept
2476 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2477 died again and I was back on square one. I still do not have a new
2478 laptop with a disk I can trust. I can not live with a disk that might
2479 lock up when I download a new
2480 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2481 other large files. I look forward to hearing from my supplier with
2482 the next proposal from Lenovo.&lt;/p&gt;
2483
2484 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2485 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2486 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2487 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2488 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2489 P/N 45N8295, P0C38732.&lt;/p&gt;
2490
2491 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2492 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2493 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2494 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2495 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2496 P/N 45N8295, P0C38732.&lt;/p&gt;
2497
2498 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2499 SA, date and WNPP values. Mentioning all the details here in case
2500 someone is able to use the information to find a way to identify the
2501 failing disk among working ones (if any such working disk actually
2502 exist).&lt;/p&gt;
2503 </description>
2504 </item>
2505
2506 <item>
2507 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2508 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2509 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2510 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2511 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2512 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2513 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2514 member assosiation NUUG&lt;/a&gt; and
2515 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2516 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2517 Bitraf&lt;/a&gt;.&lt;/p&gt;
2518
2519 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2520 welcome, and there is no fee to participate. There is on the other
2521 hand limited space, and only room for 30 people. Please put your name
2522 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2523 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2524 </description>
2525 </item>
2526
2527 <item>
2528 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2529 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2530 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2531 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2532 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2533 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2534 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2535 time to spend on it, and it took a while to find a model I believe
2536 will do the job, but two days ago the replacement finally arrived. I
2537 ended up picking a
2538 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2539 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2540 a roaming workstation, and it seemed to work flawlessly. But my
2541 second installation with encrypted disk was not as successful. More
2542 on that below.&lt;/p&gt;
2543
2544 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2545 important requirements (robust and with a good keyboard) are never
2546 listed in the feature list. But I did get good help from the search
2547 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2548 allowed me to limit the list of interesting laptops based on my other
2549 requirements. A bit surprising that SSD disk are not disks according
2550 to that search interface, so I had to drop specifying the number of
2551 disks from my search parameters. I also asked around among friends to
2552 get their impression on keyboards and robustness.&lt;/p&gt;
2553
2554 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2555 X41. I am not quite convinced about the keyboard, as it is
2556 significantly wider than my old keyboard, and I have to stretch my
2557 hand a lot more to reach the edges. But the key response is fairly
2558 good and the individual key shape is fairly easy to handle, so I hope
2559 I will get used to it. My old X40 was starting to fail, and I really
2560 needed a new laptop now. :)&lt;/p&gt;
2561
2562 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2563 visit to the BIOS during boot it disable it.&lt;/p&gt;
2564
2565 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2566 lock up during load. And this happen when installing Debian Wheezy
2567 with encrypted disk, while the disk is being filled with random data.
2568 I also tested to install Ubuntu Raring, and it happen there too if I
2569 reenable the code to fill the disk with random data (it is disabled by
2570 default in Ubuntu). And the bug with is already known. It was
2571 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2572 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2573 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2574 kernel developers as
2575 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2576 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2577 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2578 Lenovo forums, both for
2579 &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
2580 2012-11-10&lt;/a&gt; and for
2581 &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
2582 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2583 reports state that the disk lock up during use if many writes are done
2584 on the disk, so it is much no use to work around the installation
2585 problem and end up with a computer that can lock up at any moment.
2586 There is even a
2587 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2588 available&lt;/a&gt; that will lock up the hard drive after running a few
2589 minutes by writing to a file.&lt;/p&gt;
2590
2591 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2592 contacting PCHELP Norway (request 01D1FDP) which handle support
2593 requests for Lenovo, his first suggestion was to upgrade the disk
2594 firmware. Unfortunately there is no newer firmware available from
2595 Lenovo, as my disk already have the most recent one (version LF1i). I
2596 hope to hear more from him today and hope the problem can be
2597 fixed. :)&lt;/p&gt;
2598 </description>
2599 </item>
2600
2601 <item>
2602 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2603 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2604 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2605 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2606 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2607 trusty old Thinkpad X41. Unfortunately I did not have much time to
2608 spend on it, but today the replacement finally arrived. I ended up
2609 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2610 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2611 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2612 this, it is installing what I hope will be a more final installation,
2613 with a encrypted hard drive to ensure any dope head stealing it end up
2614 with an expencive door stop.&lt;/p&gt;
2615
2616 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2617 important requirements (robust and with a good keyboard) are never
2618 listed in the feature list. But I did get good help from the search
2619 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2620 allowed me to limit the list of interesting laptops based on my other
2621 requirements. A bit surprising that SSD disk are not disks, so I had
2622 to drop number of disks from my search parameters.&lt;/p&gt;
2623
2624 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2625 wider than my old keyboard, and I have to stretch my hand a lot more
2626 to reach the edges. But the key response is fairly good and the
2627 individual key shape is fairly easy to handle, so I hope I will get
2628 used to it. My old X40 was starting to fail, and I really needed a
2629 new laptop now. :)&lt;/p&gt;
2630
2631 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2632 </description>
2633 </item>
2634
2635 <item>
2636 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2637 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2638 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2639 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2640 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2641 perfectly capable of, and I have to do it manually to get things
2642 working. One such task is to find out what firmware packages are
2643 needed to get the hardware on my computer working. Most often this
2644 affect the wifi card, but some times it even affect the RAID
2645 controller or the ethernet card. Today I pushed version 0.4 of the
2646 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2647 including a new script isenkram-autoinstall-firmware handling the
2648 process of asking all the loaded kernel modules what firmware files
2649 they want, find debian packages providing these files and install the
2650 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2651
2652 &lt;p&gt;&lt;pre&gt;
2653 # isenkram-autoinstall-firmware
2654 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2655 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2656 info: locating packages with the requested firmware files
2657 info: Updating APT sources after adding non-free APT source
2658 info: trying to install firmware-ipw2x00
2659 firmware-ipw2x00
2660 firmware-ipw2x00
2661 Preconfiguring packages ...
2662 Selecting previously deselected package firmware-ipw2x00.
2663 (Reading database ... 259727 files and directories currently installed.)
2664 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2665 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2666 #
2667 &lt;/pre&gt;&lt;/p&gt;
2668
2669 &lt;p&gt;When all the requested firmware is present, a simple message is
2670 printed instead:&lt;/p&gt;
2671
2672 &lt;p&gt;&lt;pre&gt;
2673 # isenkram-autoinstall-firmware
2674 info: did not find any firmware files requested by loaded kernel modules. exiting
2675 #
2676 &lt;/pre&gt;&lt;/p&gt;
2677
2678 &lt;p&gt;It could use some polish, but it is already working well and saving
2679 me some time when setting up new machines. :)&lt;/p&gt;
2680
2681 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2682 kernel modules, and look up each one of them using modinfo, to find
2683 the firmware files listed in the module meta-information. Next, it
2684 download the Contents file from a nearby APT mirror, and search for
2685 the firmware files in this file to locate the package with the
2686 requested firmware file. If the package is in the non-free section, a
2687 non-free APT source is added and the package is installed using
2688 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2689 machine.&lt;/p&gt;
2690
2691 &lt;p&gt;I hope someone find time to implement a more polished version of
2692 this script as part of the hw-detect debian-installer module, to
2693 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2694 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2695 firmware during a PXE install when the packages already are available
2696 from the nearby Debian mirror.&lt;/p&gt;
2697 </description>
2698 </item>
2699
2700 <item>
2701 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2702 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2703 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2704 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2705 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2706 the screen just turn black when Linux boot, either during installation
2707 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2708 last few years, but only recently understood the cause. I&#39;ve seen it
2709 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2710 The reason seem to be in the wiring of some laptops. The system to
2711 control the screen background light is inverted, so when Linux try to
2712 turn the brightness fully on, it end up turning it off instead. I do
2713 not know which Linux drivers are affected, but this post is about the
2714 i915 driver used by the
2715 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2716 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2717
2718 &lt;p&gt;The problem can be worked around two ways. Either by adding
2719 i915.invert_brightness=1 as a kernel option, or by adding a file in
2720 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2721 option when it load the i915 kernel module. On Debian and Ubuntu, it
2722 can be done by running these commands as root:&lt;/p&gt;
2723
2724 &lt;pre&gt;
2725 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2726 update-initramfs -u -k all
2727 &lt;/pre&gt;
2728
2729 &lt;p&gt;Since March 2012 there is
2730 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2731 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2732 hardware have this problem, and get the driver to invert the
2733 brightness setting automatically. To use it, one need to add a row in
2734 &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
2735 intel_quirks array&lt;/a&gt; in the driver source
2736 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2737 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2738 number (vendor number 8086 is assumed) and subdevice vendor and device
2739 number.&lt;/p&gt;
2740
2741 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2742 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2743
2744 &lt;p&gt;&lt;pre&gt;
2745 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2746 3rd Gen Core processor Graphics Controller [8086:0156] \
2747 (rev 09) (prog-if 00 [VGA controller])
2748 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2749 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2750 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2751 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2752 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2753 Latency: 0
2754 Interrupt: pin A routed to IRQ 42
2755 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2756 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2757 Region 4: I/O ports at 4000 [size=64]
2758 Expansion ROM at &lt;unassigned&gt; [disabled]
2759 Capabilities: &lt;access denied&gt;
2760 Kernel driver in use: i915
2761 &lt;/pre&gt;&lt;/p&gt;
2762
2763 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2764
2765 &lt;p&gt;&lt;pre&gt;
2766 struct intel_quirk intel_quirks[] = {
2767 ...
2768 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2769 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2770 ...
2771 }
2772 &lt;/pre&gt;&lt;/p&gt;
2773
2774 &lt;p&gt;According to the kernel module instructions (as seen using
2775 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2776 invert_brightness flag should be sent to the
2777 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2778 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2779 developers. But my email about the laptop sent 2013-06-03 have not
2780 yet shown up in
2781 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2782 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2783 emails from non-subscribers. Because of this, I sent my patch also to
2784 the Debian bug tracking system instead as
2785 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2786 sure the patch is not lost.&lt;/p&gt;
2787
2788 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2789 with this problem working properly with Linux. If you use Gnome, your
2790 worries should be over at this point. But if you use KDE, there is
2791 something in KDE ignoring the invert_brightness setting and turning on
2792 the screen during login. I&#39;ve reported it to Debian as
2793 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2794 have no idea yet how to figure out exactly what subsystem is doing
2795 this. Perhaps you can help? Perhaps you know what the Gnome
2796 developers did to handle this, and this can give a clue to the KDE
2797 developers? Or you know where in KDE the screen brightness is changed
2798 during login? If so, please update the BTS report (or get in touch if
2799 you do not know how to update BTS).&lt;/p&gt;
2800
2801 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2802 acpi_backlight=vendor, to disable ACPI backlight support completely,
2803 as the ACPI information on the machine is trash and it is better to
2804 leave it to the intel video driver to control the screen
2805 backlight.&lt;/p&gt;
2806 </description>
2807 </item>
2808
2809 <item>
2810 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2811 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2812 <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>
2813 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2814 <description>&lt;p&gt;Two days ago, I asked
2815 &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
2816 I could install Linux on a Packard Bell EasyNote LV computer
2817 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2818 with the obstacles put in the way of Linux users on a laptop with UEFI
2819 and Windows 8.&lt;/p&gt;
2820
2821 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2822 secure booting or fast boot. I suspect fast boot was the problem,
2823 causing the firmware to boot directly from HD without considering any
2824 key presses and alternative devices, but do not know UEFI settings
2825 enough to tell.&lt;/p&gt;
2826
2827 &lt;p&gt;There is no way to install Linux on the machine in question without
2828 opening the box and disconnecting the hard drive! This is as far as I
2829 can tell, the only way to get access to the firmware setup menu
2830 without accepting the Windows 8 license agreement. I am told (and
2831 found description on how to) that it is possible to configure the
2832 firmware setup once booted into Windows 8. But as I believe the terms
2833 of that agreement are completely unacceptable, accepting the license
2834 was never an alternative. I do not enter agreements I do not intend
2835 to follow.&lt;/p&gt;
2836
2837 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2838 waste many hours on this, but luckily there was a way to get it to
2839 work. But I would not recommend it to anyone planning to run Linux on
2840 it, and I have become sceptical to Windows 8 certified laptops. Is
2841 this the way Linux will be forced out of the market place, by making
2842 it close to impossible for &quot;normal&quot; users to install Linux without
2843 accepting the Microsoft Windows license terms? Or at least not
2844 without risking to loose the warranty?&lt;/p&gt;
2845
2846 &lt;p&gt;I&#39;ve updated the
2847 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2848 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2849 do not have to struggle as much as I did to get Linux into the
2850 machine.&lt;/p&gt;
2851
2852 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2853 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2854 </description>
2855 </item>
2856
2857 <item>
2858 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2859 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2860 <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>
2861 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2862 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2863 new laptops for my parents and a few others. I bought Packard Bell
2864 Easynote LV to run Kubuntu on and use as their home computer. But I
2865 am completely unable to figure out how to install Linux on it. The
2866 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2867 instead of a BIOS to boot.&lt;/p&gt;
2868
2869 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
2870 to get it to boot the Linux installer from my USB stick. I have yet
2871 to try the DVD install, and still hope it will work. when I turn on
2872 the computer, there is no information on what buttons to press to get
2873 the normal boot menu. I expect to get some boot menu to select PXE or
2874 USB stick booting. When booting, it first ask for the language to
2875 use, then for some regional settings, and finally if I will accept the
2876 Windows 8 terms of use. As these terms are completely unacceptable to
2877 me, I have no other choice but to turn off the computer and try again
2878 to get it to boot the Linux installer.&lt;/p&gt;
2879
2880 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
2881 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2882 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
2883 installed on this machine, please get in touch or update that wiki
2884 page. If I can&#39;t find a way to install Linux, I will have to return
2885 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
2886
2887 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
2888 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
2889 on new Laptops?&lt;/p&gt;
2890 </description>
2891 </item>
2892
2893 <item>
2894 <title>How to transform a Debian based system to a Debian Edu installation</title>
2895 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
2896 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
2897 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
2898 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
2899 an operating system based on Debian intended for use in schools. It
2900 contain a turn-key solution for the computer network provided to
2901 pupils in the primary schools. It provide both the central server,
2902 network boot servers and desktop environments with heaps of
2903 educational software. The project was founded almost 12 years ago,
2904 2001-07-02. If you want to support the project, which is in need for
2905 cash to fund developer gatherings and other project related activity,
2906 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
2907 donate some money&lt;/a&gt;.
2908
2909 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
2910 lists and elsewhere, is the question on how to transform a Debian or
2911 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
2912 hard, and last week I wrote a script to replicate the steps done by
2913 the Debian Edu installer.&lt;/p&gt;
2914
2915 &lt;p&gt;The script,
2916 &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;
2917 in the debian-edu-config package, will go through these six steps and
2918 transform an existing Debian Wheezy or Ubuntu (untested) installation
2919 into a Debian Edu Workstation:&lt;/p&gt;
2920
2921 &lt;ol&gt;
2922
2923 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
2924 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
2925 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
2926 our configuration.&lt;/li&gt;
2927 &lt;li&gt;Preseed debconf database with profile setup in
2928 /etc/debian-edu/config, and run tasksel to install packages
2929 according to the profile specified in the config above,
2930 overriding some of the Debian automation machinery.&lt;/li&gt;
2931 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
2932 that could not be done using preseeding.&lt;/li&gt;
2933 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
2934
2935 &lt;/ol&gt;
2936
2937 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
2938 replicated like this. Disk partitioning and LVM setup, for example.
2939 So this script just assume there is enough disk space to install all
2940 the needed packages.&lt;/p&gt;
2941
2942 &lt;p&gt;The script was created to help a Debian Edu student working on
2943 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
2944 Debian Edu client, and using it he can take the existing
2945 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
2946 transform it into a fully functioning Debian Edu Workstation (or
2947 Roaming Workstation, or whatever :).&lt;/p&gt;
2948
2949 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
2950 If a LXDE based Roaming workstation is wanted instead, modify the
2951 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
2952
2953 &lt;p&gt;&lt;pre&gt;
2954 PROFILE=&quot;Roaming-Workstation&quot;
2955 DESKTOP=&quot;lxde&quot;
2956 &lt;/pre&gt;&lt;/p&gt;
2957
2958 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
2959 the cloud, by starting with a virtual Debian installation at some
2960 virtual hosting service and setting up all the services on first
2961 boot.&lt;/p&gt;
2962 </description>
2963 </item>
2964
2965 <item>
2966 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
2967 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
2968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
2969 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
2970 <description>&lt;P&gt;In January,
2971 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
2972 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
2973 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
2974 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
2975 marvellous construction system from Denmark. We also created
2976 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
2977 a place to take notes and write down our plans and hopes. And several
2978 people showed up to help. I was very happy to see the effect of my
2979 call. Since the small start, we have a debtags tag
2980 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
2981 tag for LEGO related packages, and now count 10 packages related to
2982 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
2983
2984 &lt;p&gt;&lt;table&gt;
2985 &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;
2986 &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;
2987 &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;
2988 &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;
2989 &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;
2990 &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;
2991 &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;
2992 &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;
2993 &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;
2994 &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;
2995 &lt;/table&gt;&lt;/p&gt;
2996
2997 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2998 currently available in Jessie/testing. leocad is so far only
2999 available in experimental.&lt;/p&gt;
3000
3001 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3002 adding the rest of the great free software tools available on Linux
3003 for LEGO designers.&lt;/p&gt;
3004 </description>
3005 </item>
3006
3007 <item>
3008 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3009 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3010 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3011 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3012 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3013 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3014 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3015 Debian release, and I expect to move my machines at home over to it fairly
3016 soon.&lt;/p&gt;
3017
3018 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3019 in particular make me very happy to see included. The
3020 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3021 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3022 included for the first time. Alongside similar programs like
3023 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3024 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3025 it allow for visual programming where syntax errors can not happen,
3026 and a friendly programming environment for learning to control the
3027 computer. Scratch will also be included in the next release of Debian
3028 Edu.&lt;/a&gt;
3029
3030 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3031 Edu/Skolelinux release too. The
3032 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3033 alpha release&lt;/a&gt; went out last week, and the next should soon
3034 follow.&lt;p&gt;
3035 </description>
3036 </item>
3037
3038 <item>
3039 <title>Isenkram 0.2 finally in the Debian archive</title>
3040 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3041 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3042 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3043 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3044 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3045 for many months. I uploaded it to the Debian experimental suite
3046 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3047
3048 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3049 install to work with a pluggable hardware device. The suggestion pop
3050 up when the device is plugged in. For example if a Lego Mindstorm NXT
3051 is inserted, it will suggest to install the program needed to program
3052 the NXT controller. Give it a go, and report bugs and suggestions to
3053 BTS. :)&lt;/p&gt;
3054 </description>
3055 </item>
3056
3057 <item>
3058 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3059 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3060 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3061 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3062 <description>&lt;p&gt;My
3063 &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
3064 bitcoin related blog post&lt;/a&gt; mentioned that the new
3065 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3066 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3067 2013-01-19, and have been available in unstable since then. It was
3068 automatically copied to Ubuntu, and is available in their Raring
3069 version too.&lt;/p&gt;
3070
3071 &lt;p&gt;But there is a strange problem with the build that block this new
3072 version from being available on the i386 and kfreebsd-i386
3073 architectures. For some strange reason, the autobuilders in Debian
3074 for these architectures fail to run the test suite on these
3075 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3076 We are so far unable to reproduce it when building it manually, and
3077 no-one have been able to propose a fix. If you got an idea what is
3078 failing, please let us know via the BTS.&lt;/p&gt;
3079
3080 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3081 I often run low on disk space, is the fact that the client will exit
3082 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3083 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3084 it. :)&lt;/p&gt;
3085
3086 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3087 activities, please send Bitcoin donations to my address
3088 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3089 </description>
3090 </item>
3091
3092 <item>
3093 <title>Welcome to the world, Isenkram!</title>
3094 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3095 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3096 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3097 <description>&lt;p&gt;Yesterday, I
3098 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3099 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3100 pluggable hardware devices, which I
3101 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3102 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3103 up, and caused me to really want to to open up the development to more
3104 people. But before I did this, I want to come up with a sensible name
3105 for this project. Today I finally decided on a new name, and I have
3106 renamed the project from hw-support-handler to this new name. In the
3107 process, I moved the source to git and made it available as a
3108 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3109 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3110 To fetch and build the latest version of the source, use&lt;/p&gt;
3111
3112 &lt;pre&gt;
3113 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3114 cd isenkram &amp;&amp; git-buildpackage -us -uc
3115 &lt;/pre&gt;
3116
3117 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3118 want to hack on the source or improve the package, please go ahead.
3119 But please talk to me first on IRC or via email before you do major
3120 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3121
3122 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3123 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3124 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3125 the German word eisenkram, for those that are familiar with that
3126 word.&lt;/p&gt;
3127
3128 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3129 instructions, to avoid confusing people with an error from the signing
3130 process.&lt;/p&gt;
3131
3132 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3133 clone argument to avoid the need for authentication.&lt;/p&gt;
3134 </description>
3135 </item>
3136
3137 <item>
3138 <title>First prototype ready making hardware easier to use in Debian</title>
3139 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3140 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3141 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3142 <description>&lt;p&gt;Early this month I set out to try to
3143 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3144 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3145 prototype is working, and it is ready for a larger audience. To test
3146 it, fetch the
3147 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3148 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3149 package. You might have to log out and in again activate the
3150 autostart script.&lt;/p&gt;
3151
3152 &lt;p&gt;The design is simple:&lt;/p&gt;
3153
3154 &lt;ul&gt;
3155
3156 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3157 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3158
3159 &lt;li&gt;This program listen for kernel events about new hardware (directly
3160 from the kernel like udev does), not using HAL dbus events as I
3161 initially did.&lt;/li&gt;
3162
3163 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3164 the APT database, a database
3165 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3166 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3167
3168 &lt;li&gt;If a package is mapped to the hardware in question, the package
3169 isn&#39;t installed yet and this is the first time the hardware was
3170 plugged in, show a desktop notification suggesting to install the
3171 package or packages.&lt;/li&gt;
3172
3173 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3174 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3175
3176 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3177 package while showing progress information in a window.&lt;/li&gt;
3178
3179 &lt;/ul&gt;
3180
3181 &lt;p&gt;I still need to come up with a better name for the system. Here
3182 are some screen shots showing the prototype in action. First the
3183 notification, then the password request, and finally the request to
3184 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3185
3186 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3187 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3188 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3189 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3190 &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;
3191
3192 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3193 is already useful. The database of hardware to package mappings also
3194 need more work. It is currently compatible with the Ubuntu way of
3195 storing such information in the package control file, but could be
3196 changed to use other formats instead or in addition to the current
3197 method. I&#39;ve dropped the use of discover for this mapping, as the
3198 modalias approach is more flexible and easier to use on Linux as long
3199 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3200
3201 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3202 here is the command required to check out and build the source: Use
3203 &#39;&lt;tt&gt;svn checkout
3204 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3205 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3206 devscripts package.&lt;/p&gt;
3207
3208 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3209 renamed to Isenkram and the source moved from the Debian Edu
3210 subversion repository to a Debian collab-maint git repository. See
3211 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3212 instructions&lt;/a&gt; for details.&lt;/p&gt;
3213 </description>
3214 </item>
3215
3216 <item>
3217 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3218 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3219 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3220 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3221 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3222 suddenly in bed. With a quiet whimper, it went completely quiet and
3223 black. The power button was no longer able to turn it on. It was a
3224 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3225 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3226 Compaq I had before that. Now I need to find a replacement. To keep
3227 going during Christmas, I moved the one year old SSD disk to my old
3228 X40 where it fitted (only one I had left that could use it), but it is
3229 not a durable solution.
3230
3231 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3232 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3233
3234 &lt;ul&gt;
3235
3236 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3237 than A4).&lt;/li&gt;
3238 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3239 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3240 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3241 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3242 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3243 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3244 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3245 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3246 size).&lt;/li&gt;
3247 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3248 X.org packages.&lt;/li&gt;
3249 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3250 the time).
3251
3252 &lt;/ul&gt;
3253
3254 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3255 list. The reason is simply that the specifications on laptops the
3256 last 10-15 years have been sufficient for my needs, and I have to look
3257 at other features to choose my laptop. But are there still made as
3258 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3259 robust, and Thinkpads seem to be heading in the wrong direction since
3260 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3261 still be useful.&lt;/p&gt;
3262
3263 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3264 external keyboard? I&#39;ll have to check the
3265 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3266 well-supported laptops, or perhaps just buy one preinstalled from one
3267 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3268 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3269 </description>
3270 </item>
3271
3272 <item>
3273 <title>How to find a browser plugin supporting a given MIME type</title>
3274 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3275 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3276 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3277 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3278 install to get support for a given MIME type. Thanks to
3279 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3280 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3281 Unfortunately, not very many packages provide the needed meta
3282 information, Anyway, here is a small script to look up all browser
3283 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3284
3285 &lt;pre&gt;
3286 #!/usr/bin/python
3287 import sys
3288 import apt
3289 def pkgs_handling_mimetype(mimetype):
3290 cache = apt.Cache()
3291 cache.open(None)
3292 thepkgs = []
3293 for pkg in cache:
3294 version = pkg.candidate
3295 if version is None:
3296 version = pkg.installed
3297 if version is None:
3298 continue
3299 record = version.record
3300 if not record.has_key(&#39;Npp-MimeType&#39;):
3301 continue
3302 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3303 for t in mime_types:
3304 t = t.rstrip().strip()
3305 if t == mimetype:
3306 thepkgs.append(pkg.name)
3307 return thepkgs
3308 mimetype = &quot;audio/ogg&quot;
3309 if 1 &lt; len(sys.argv):
3310 mimetype = sys.argv[1]
3311 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3312 for pkg in pkgs_handling_mimetype(mimetype):
3313 print &quot; %s&quot; %pkg
3314 &lt;/pre&gt;
3315
3316 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3317
3318 &lt;pre&gt;
3319 % ./apt-find-browserplug-for-mimetype
3320 Browser plugin packages supporting audio/ogg:
3321 gecko-mediaplayer
3322 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3323 Browser plugin packages supporting application/x-shockwave-flash:
3324 browser-plugin-gnash
3325 %
3326 &lt;/pre&gt;
3327
3328 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3329 itself to query for plugins and propose to install the needed
3330 packages. It would be great if Debian supported such feature too. Is
3331 anyone working on adding it?&lt;/p&gt;
3332
3333 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3334 request for icweasel support for this feature is
3335 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3336 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3337 of manpower and wish for a different design is the reason thus feature
3338 is not yet in iceweasel from Debian.&lt;/p&gt;
3339 </description>
3340 </item>
3341
3342 <item>
3343 <title>What is the most supported MIME type in Debian?</title>
3344 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3346 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3347 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3348 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3349 proposal to make it possible for a Desktop application to propose to
3350 the user some package to install to gain support for a given MIME
3351 type, font, library etc. that is currently missing. With such
3352 mechanism in place, it would be possible for the desktop to
3353 automatically propose and install leocad if some LDraw file is
3354 downloaded by the browser.&lt;/p&gt;
3355
3356 &lt;p&gt;To get some idea about the current content of the archive, I decided
3357 to write a simple program to extract all .desktop files from the
3358 Debian archive and look up the claimed MIME support there. The result
3359 can be found on the
3360 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3361 site&lt;/a&gt;. Using the collected information, it become possible to
3362 answer the question in the title. Here are the 20 most supported MIME
3363 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3364 The complete list is available from the link above.&lt;/p&gt;
3365
3366 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3367
3368 &lt;pre&gt;
3369 count MIME type
3370 ----- -----------------------
3371 32 text/plain
3372 30 audio/mpeg
3373 29 image/png
3374 28 image/jpeg
3375 27 application/ogg
3376 26 audio/x-mp3
3377 25 image/tiff
3378 25 image/gif
3379 22 image/bmp
3380 22 audio/x-wav
3381 20 audio/x-flac
3382 19 audio/x-mpegurl
3383 18 video/x-ms-asf
3384 18 audio/x-musepack
3385 18 audio/x-mpeg
3386 18 application/x-ogg
3387 17 video/mpeg
3388 17 audio/x-scpls
3389 17 audio/ogg
3390 16 video/x-ms-wmv
3391 &lt;/pre&gt;
3392
3393 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3394
3395 &lt;pre&gt;
3396 count MIME type
3397 ----- -----------------------
3398 33 text/plain
3399 32 image/png
3400 32 image/jpeg
3401 29 audio/mpeg
3402 27 image/gif
3403 26 image/tiff
3404 26 application/ogg
3405 25 audio/x-mp3
3406 22 image/bmp
3407 21 audio/x-wav
3408 19 audio/x-mpegurl
3409 19 audio/x-mpeg
3410 18 video/mpeg
3411 18 audio/x-scpls
3412 18 audio/x-flac
3413 18 application/x-ogg
3414 17 video/x-ms-asf
3415 17 text/html
3416 17 audio/x-musepack
3417 16 image/x-xbitmap
3418 &lt;/pre&gt;
3419
3420 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3421
3422 &lt;pre&gt;
3423 count MIME type
3424 ----- -----------------------
3425 31 text/plain
3426 31 image/png
3427 31 image/jpeg
3428 29 audio/mpeg
3429 28 application/ogg
3430 27 image/gif
3431 26 image/tiff
3432 26 audio/x-mp3
3433 23 audio/x-wav
3434 22 image/bmp
3435 21 audio/x-flac
3436 20 audio/x-mpegurl
3437 19 audio/x-mpeg
3438 18 video/x-ms-asf
3439 18 video/mpeg
3440 18 audio/x-scpls
3441 18 application/x-ogg
3442 17 audio/x-musepack
3443 16 video/x-ms-wmv
3444 16 video/x-msvideo
3445 &lt;/pre&gt;
3446
3447 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3448 information mentioned in DEP-11. I have not yet had time to look at
3449 it, but hope the PackageKit people in Debian are on top of these
3450 issues.&lt;/p&gt;
3451
3452 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3453 discovering a typo in my script.&lt;/p&gt;
3454 </description>
3455 </item>
3456
3457 <item>
3458 <title>Using modalias info to find packages handling my hardware</title>
3459 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3460 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3461 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3462 <description>&lt;p&gt;Yesterday, I wrote about the
3463 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3464 values provided by the Linux kernel&lt;/a&gt; following my hope for
3465 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3466 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3467 modalias values attached to package names can be used to map packages
3468 to hardware. This allow the system to look up and suggest relevant
3469 packages when I plug in some new hardware into my machine, and replace
3470 discover and discover-data as the database used to map hardware to
3471 packages.&lt;/p&gt;
3472
3473 &lt;p&gt;I create a modaliases file with entries like the following,
3474 containing package name, kernel module name (if relevant, otherwise
3475 the package name) and globs matching the relevant hardware
3476 modalias.&lt;/p&gt;
3477
3478 &lt;p&gt;&lt;blockquote&gt;
3479 Package: package-name
3480 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3481 &lt;/blockquote&gt;&lt;/p&gt;
3482
3483 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3484 for a given modalias value using this file.&lt;/p&gt;
3485
3486 &lt;p&gt;An entry like this would suggest the video and picture application
3487 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3488
3489 &lt;p&gt;&lt;blockquote&gt;
3490 Package: cheese
3491 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3492 &lt;/blockquote&gt;&lt;/p&gt;
3493
3494 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3495 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3496
3497 &lt;p&gt;&lt;blockquote&gt;
3498 Package: pcmciautils
3499 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3500 &lt;/blockquote&gt;&lt;/p&gt;
3501
3502 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3503 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3504
3505 &lt;p&gt;&lt;blockquote&gt;
3506 Package: colorhug-client
3507 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3508 &lt;/blockquote&gt;&lt;/p&gt;
3509
3510 &lt;p&gt;I believe the format is compatible with the format of the Packages
3511 file in the Debian archive. Ubuntu already uses their Packages file
3512 to store their mappings from packages to hardware.&lt;/p&gt;
3513
3514 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3515 announce the hardware it support in a way my prototype understand.
3516 This allow those publishing packages in an APT source outside the
3517 Debian archive as well as those backporting packages to make sure the
3518 hardware mapping are included in the package meta information. I&#39;ve
3519 tested such header in the pymissile package, and its modalias mapping
3520 is working as it should with my prototype. It even made it to Ubuntu
3521 Raring.&lt;/p&gt;
3522
3523 &lt;p&gt;To test if it was possible to look up supported hardware using only
3524 the shell tools available in the Debian installer, I wrote a shell
3525 implementation of the lookup code. The idea is to create files for
3526 each modalias and let the shell do the matching. Please check out and
3527 try the
3528 &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;
3529 shell script. It run without any extra dependencies and fetch the
3530 hardware mappings from the Debian archive and the subversion
3531 repository where I currently work on my prototype.&lt;/p&gt;
3532
3533 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3534 install yubikey-personalization:&lt;/p&gt;
3535
3536 &lt;p&gt;&lt;blockquote&gt;
3537 % ./hw-support-lookup
3538 &lt;br&gt;yubikey-personalization
3539 &lt;br&gt;%
3540 &lt;/blockquote&gt;&lt;/p&gt;
3541
3542 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3543 propose to install the pcmciautils package:&lt;/p&gt;
3544
3545 &lt;p&gt;&lt;blockquote&gt;
3546 % ./hw-support-lookup
3547 &lt;br&gt;pcmciautils
3548 &lt;br&gt;%
3549 &lt;/blockquote&gt;&lt;/p&gt;
3550
3551 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3552 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3553 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3554
3555 &lt;p&gt;It could be possible to generate several of the mappings between
3556 packages and hardware. One source would be to look at packages with
3557 kernel modules, ie packages with *.ko files in /lib/modules/, and
3558 extract their modalias information. Another would be to look at
3559 packages with udev rules, ie packages with files in
3560 /lib/udev/rules.d/, and extract their vendor/model information to
3561 generate a modalias matching rule. I have not tested any of these to
3562 see if it work.&lt;/p&gt;
3563
3564 &lt;p&gt;If you want to help implementing a system to let us propose what
3565 packages to install when new hardware is plugged into a Debian
3566 machine, please send me an email or talk to me on
3567 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3568 </description>
3569 </item>
3570
3571 <item>
3572 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3573 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3575 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3576 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3577 information, to find the packages that support a given piece of
3578 hardware, I refreshed my memory regarding modalias values, and decided
3579 to document the details. Here are my findings so far, also available
3580 in
3581 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3582 Debian Edu subversion repository&lt;/a&gt;:
3583
3584 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3585
3586 &lt;p&gt;This document try to explain what the different types of modalias
3587 values stands for. It is in part based on information from
3588 &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;,
3589 &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;,
3590 &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
3591 &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;.
3592
3593 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3594 this shell script:&lt;/p&gt;
3595
3596 &lt;pre&gt;
3597 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3598 &lt;/pre&gt;
3599
3600 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3601 using modinfo:&lt;/p&gt;
3602
3603 &lt;pre&gt;
3604 % /sbin/modinfo psmouse | grep alias:
3605 alias: serio:ty05pr*id*ex*
3606 alias: serio:ty01pr*id*ex*
3607 %
3608 &lt;/pre&gt;
3609
3610 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3611
3612 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3613 Bridge memory controller:&lt;/p&gt;
3614
3615 &lt;p&gt;&lt;blockquote&gt;
3616 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3617 &lt;/blockquote&gt;&lt;/p&gt;
3618
3619 &lt;p&gt;This represent these values:&lt;/p&gt;
3620
3621 &lt;pre&gt;
3622 v 00008086 (vendor)
3623 d 00002770 (device)
3624 sv 00001028 (subvendor)
3625 sd 000001AD (subdevice)
3626 bc 06 (bus class)
3627 sc 00 (bus subclass)
3628 i 00 (interface)
3629 &lt;/pre&gt;
3630
3631 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3632 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3633 0600. The 0600 class is a host bridge. Other useful bus values are
3634 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3635
3636 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3637 means.&lt;/p&gt;
3638
3639 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3640
3641 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3642 USB hub in a laptop:&lt;/p&gt;
3643
3644 &lt;p&gt;&lt;blockquote&gt;
3645 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3646 &lt;/blockquote&gt;&lt;/p&gt;
3647
3648 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3649
3650 &lt;pre&gt;
3651 v 1D6B (device vendor)
3652 p 0001 (device product)
3653 d 0206 (bcddevice)
3654 dc 09 (device class)
3655 dsc 00 (device subclass)
3656 dp 00 (device protocol)
3657 ic 09 (interface class)
3658 isc 00 (interface subclass)
3659 ip 00 (interface protocol)
3660 &lt;/pre&gt;
3661
3662 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3663 class is in the interface class section. For a simple USB web camera,
3664 these alias entries show up:&lt;/p&gt;
3665
3666 &lt;p&gt;&lt;blockquote&gt;
3667 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3668 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3669 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3670 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3671 &lt;/blockquote&gt;&lt;/p&gt;
3672
3673 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3674 camera), 0101 is audio control device and 0102 is audio streaming (aka
3675 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3676
3677 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3678
3679 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3680 receiver in a Thinkpad X40:&lt;/p&gt;
3681
3682 &lt;p&gt;&lt;blockquote&gt;
3683 acpi:IBM0071:PNP0511:
3684 &lt;/blockquote&gt;&lt;/p&gt;
3685
3686 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3687
3688 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3689
3690 &lt;p&gt;The DMI table contain lots of information about the computer case
3691 and model. This is an entry for a IBM Thinkpad X40, fetched from
3692 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3693
3694 &lt;p&gt;&lt;blockquote&gt;
3695 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3696 &lt;/blockquote&gt;&lt;/p&gt;
3697
3698 &lt;p&gt;The values present are&lt;/p&gt;
3699
3700 &lt;pre&gt;
3701 bvn IBM (BIOS vendor)
3702 bvr 1UETB6WW(1.66) (BIOS version)
3703 bd 06/15/2005 (BIOS date)
3704 svn IBM (system vendor)
3705 pn 2371H4G (product name)
3706 pvr ThinkPadX40 (product version)
3707 rvn IBM (board vendor)
3708 rn 2371H4G (board name)
3709 rvr NotAvailable (board version)
3710 cvn IBM (chassis vendor)
3711 ct 10 (chassis type)
3712 cvr NotAvailable (chassis version)
3713 &lt;/pre&gt;
3714
3715 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3716 found in the dmidecode source:&lt;/p&gt;
3717
3718 &lt;pre&gt;
3719 3 Desktop
3720 4 Low Profile Desktop
3721 5 Pizza Box
3722 6 Mini Tower
3723 7 Tower
3724 8 Portable
3725 9 Laptop
3726 10 Notebook
3727 11 Hand Held
3728 12 Docking Station
3729 13 All In One
3730 14 Sub Notebook
3731 15 Space-saving
3732 16 Lunch Box
3733 17 Main Server Chassis
3734 18 Expansion Chassis
3735 19 Sub Chassis
3736 20 Bus Expansion Chassis
3737 21 Peripheral Chassis
3738 22 RAID Chassis
3739 23 Rack Mount Chassis
3740 24 Sealed-case PC
3741 25 Multi-system
3742 26 CompactPCI
3743 27 AdvancedTCA
3744 28 Blade
3745 29 Blade Enclosing
3746 &lt;/pre&gt;
3747
3748 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3749 table. For example my home server is a tower, but the DMI modalias
3750 claim it is a desktop.&lt;/p&gt;
3751
3752 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3753
3754 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3755 test machine:&lt;/p&gt;
3756
3757 &lt;p&gt;&lt;blockquote&gt;
3758 serio:ty01pr00id00ex00
3759 &lt;/blockquote&gt;&lt;/p&gt;
3760
3761 &lt;p&gt;The values present are&lt;/p&gt;
3762
3763 &lt;pre&gt;
3764 ty 01 (type)
3765 pr 00 (prototype)
3766 id 00 (id)
3767 ex 00 (extra)
3768 &lt;/pre&gt;
3769
3770 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3771 the valid values are.&lt;/p&gt;
3772
3773 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3774
3775 &lt;p&gt;There are heaps of other modalias subtypes according to
3776 file2alias.c. There is the rest of the list from that source: amba,
3777 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3778 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3779 vmbus, x86cpu and zorro. I did not spend time documenting all of
3780 these, as they do not seem relevant for my intended use with mapping
3781 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3782
3783 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3784
3785 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3786 one can use the following shell script:&lt;/p&gt;
3787
3788 &lt;pre&gt;
3789 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3790 echo &quot;$id&quot; ; \
3791 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3792 done
3793 &lt;/pre&gt;
3794
3795 &lt;p&gt;The output can look like this (only the first few entries as the
3796 list is very long on my test machine):&lt;/p&gt;
3797
3798 &lt;pre&gt;
3799 acpi:ACPI0003:
3800 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3801 acpi:device:
3802 FATAL: Module acpi:device: not found.
3803 acpi:IBM0068:
3804 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3805 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3806 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3807 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3808 acpi:IBM0071:PNP0511:
3809 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3810 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3811 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3812 [...]
3813 &lt;/pre&gt;
3814
3815 &lt;p&gt;If you want to help implementing a system to let us propose what
3816 packages to install when new hardware is plugged into a Debian
3817 machine, please send me an email or talk to me on
3818 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3819
3820 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3821 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3822 in /sys/ with space in them.&lt;/p&gt;
3823 </description>
3824 </item>
3825
3826 <item>
3827 <title>Moved the pymissile Debian packaging to collab-maint</title>
3828 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3829 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3830 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3831 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3832 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3833 Launcher and updated the Debian package
3834 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3835 sure udev will fix the device permissions when it is plugged in. I
3836 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3837 hopefully make the package be proposed by jockey in Ubuntu when a user
3838 plug in his rocket launcher. In the process I moved the source to a
3839 git repository under collab-maint, to make it easier for any DD to
3840 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3841 is not very active, but the software still work for me even after five
3842 years of relative silence. The new git repository is not listed in
3843 the uploaded package yet, because I want to test the other changes a
3844 bit more before I upload the new version. If you want to check out
3845 the new version with a .desktop file included, visit the
3846 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3847 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3848 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3849 </description>
3850 </item>
3851
3852 <item>
3853 <title>Lets make hardware dongles easier to use in Debian</title>
3854 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3855 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3856 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3857 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3858 general, is that there is a great package management system with the
3859 ability to automatically install software packages by downloading them
3860 from the distribution mirrors, but no way to get it to automatically
3861 install the packages I need to use the hardware I plug into my
3862 machine. Even if the package to use it is easily available from the
3863 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3864 suggest to automatically install the python-nxt, nbc and t2n packages
3865 I need to talk to it. When I plug in a Yubikey, it could propose the
3866 yubikey-personalization package. The information required to do this
3867 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3868
3869 &lt;p&gt;Some years ago, I proposed to
3870 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
3871 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
3872 simple:
3873
3874 &lt;ul&gt;
3875
3876 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
3877 starting when a user log in.&lt;/li&gt;
3878
3879 &lt;li&gt;Set this program up to listen for kernel events emitted when new
3880 hardware is inserted into the computer.&lt;/li&gt;
3881
3882 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
3883 database mapping to packages, and take note of any non-installed
3884 packages.&lt;/li&gt;
3885
3886 &lt;li&gt;Show a message to the user proposing to install the discovered
3887 package, and make it easy to install it.&lt;/li&gt;
3888
3889 &lt;/ul&gt;
3890
3891 &lt;p&gt;I am not sure what the best way to implement this is, but my
3892 initial idea was to use dbus events to discover new hardware, the
3893 discover database to find packages and
3894 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
3895 packages.&lt;/p&gt;
3896
3897 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
3898 draft package is now checked into
3899 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3900 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
3901 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
3902 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3903 the relevant packages in Debian, and uploaded a new version
3904 2.2013.01.09 to unstable. I also discovered that the current
3905 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
3906 package in Debian no longer discovered any USB devices, because
3907 /proc/bus/usb/devices is no longer present. I ported it to use
3908 libusb as a fall back option to get it working. The fixed package
3909 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
3910 because of the freeze).&lt;/p&gt;
3911
3912 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
3913 desktop notification to show up (only once, the first time it is
3914 inserted):&lt;/p&gt;
3915
3916 &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;
3917
3918 &lt;p&gt;For this prototype to be really useful, some way to automatically
3919 install the proposed packages by pressing the &quot;Please install
3920 program(s)&quot; button should to be implemented.&lt;/p&gt;
3921
3922 &lt;p&gt;If this idea seem useful to you, and you want to help make it
3923 happen, please help me update the discover-data database with mappings
3924 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
3925 list the package you would like to have installed when a given
3926 hardware device is inserted into your computer, and report bugs using
3927 reportbug if it isn&#39;t. Or, if you know of a better way to provide
3928 such mapping, please let me know.&lt;/p&gt;
3929
3930 &lt;p&gt;This prototype need more work, and there are several questions that
3931 should be considered before it is ready for production use. Is dbus
3932 the correct way to detect new hardware? At the moment I look for HAL
3933 dbus events on the system bus, because that is the events I could see
3934 on my Debian Squeeze KDE desktop. Are there better events to use?
3935 How should the user be notified? Is the desktop notification
3936 mechanism the best option, or should the background daemon raise a
3937 popup instead? How should packages be installed? When should they
3938 not be installed?&lt;/p&gt;
3939
3940 &lt;p&gt;If you want to help getting such feature implemented in Debian,
3941 please send me an email. :)&lt;/p&gt;
3942 </description>
3943 </item>
3944
3945 <item>
3946 <title>New IRC channel for LEGO designers using Debian</title>
3947 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
3948 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
3949 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
3950 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
3951 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
3952 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
3953 discovered I had to build all the tools myself because none were
3954 already in Debian Squeeze. If Debian support for LEGO is something
3955 you care about, please join me on the IRC channel
3956 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
3957 irc.debian.org). There is a lot that could be done to improve the
3958 Debian support for LEGO designers. For example both CAD software
3959 and Mindstorm compilers are missing. :)&lt;/p&gt;
3960
3961 &lt;p&gt;Update 2012-01-03: A
3962 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
3963 including links to Lego related packages is now available.&lt;/p&gt;
3964 </description>
3965 </item>
3966
3967 <item>
3968 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
3969 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
3970 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
3971 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
3972 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
3973 year! I hope next year will prove to be a good year.&lt;/p&gt;
3974
3975 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
3976 decentralised &quot;currency&quot; that allow people to transfer bitcoins
3977 between each other with minimal overhead, is a very interesting
3978 experiment. And as I wrote a few days ago, the bitcoin situation in
3979 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
3980 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
3981 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
3982 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
3983 for one of the ftpmasters to approve the new bitcoin-qt package
3984 name.&lt;/p&gt;
3985
3986 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3987 team in Debian, you can easily test the package in Debian Squeeze
3988 using the following steps to get a set of working packages:&lt;/p&gt;
3989
3990 &lt;blockquote&gt;&lt;pre&gt;
3991 git clone git://git.debian.org/git/collab-maint/bitcoin
3992 cd bitcoin
3993 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3994 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3995 &lt;/pre&gt;&lt;/blockquote&gt;
3996
3997 &lt;p&gt;You might have to install some build dependencies as well. The
3998 list of commands should give you two packages, bitcoind and
3999 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4000 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4001 around 5.6 GiB of data on my machine at the moment. Make sure your
4002 ~/.bitcoin/ directory have lots of spare room if you want to download
4003 all the blocks. The client will warn if the disk is getting full, so
4004 there is not really a problem if you got too little room, but you will
4005 not be able to get all the features out of the client.&lt;/p&gt;
4006
4007 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4008 activities, please send Bitcoin donations to my address
4009 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4010 </description>
4011 </item>
4012
4013 <item>
4014 <title>A word on bitcoin support in Debian</title>
4015 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4016 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4017 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4018 <description>&lt;p&gt;It has been a while since I wrote about
4019 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4020 peer-to-peer based crypto-currency, and the reason is simply that I
4021 have been busy elsewhere. But two days ago, I started looking at the
4022 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4023 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4024 is now maintained by a
4025 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4026 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4027 owe a huge thank you to all these team members. :)
4028 But I was sad to discover that the bitcoin client is missing in
4029 Wheezy. It is only available in Sid (and an outdated client from
4030 backports). The client had several RC bugs registered in BTS blocking
4031 it from entering testing. To try to help the team and improve the
4032 situation, I spent some time providing patches and triaging the bug
4033 reports. I also had a look at the bitcoin package available from Matt
4034 Corallo in a
4035 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4036 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4037 Debian package.&lt;/p&gt;
4038
4039 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4040 IRC, I pushed several patches into the collab-maint git repository to
4041 improve the package. It now contains fixes for the RC issues (not from
4042 me, but fixed by Scott Howard), build rules for a Qt GUI client
4043 package, konqueror support for the bitcoin: URI and bash completion
4044 setup. As I work on Debian Squeeze, I also created
4045 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4046 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4047 it and try to integrate it into the git repository before uploading a
4048 new version to unstable.
4049
4050 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4051 centralized control currently exercised in the monetary system. I
4052 find it completely unacceptable that the USA government is collecting
4053 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4054 that the major credit card companies can block legal money
4055 transactions to Wikileaks. But for bitcoin to succeed, more people
4056 need to use bitcoins, and more people need to accept bitcoins when
4057 they sell products and services. Improving the bitcoin support in
4058 Debian is a small step in the right direction, but not enough.
4059 Unfortunately the user experience when browsing the web and wanting to
4060 pay with bitcoin is still not very good. The bitcoin: URI is a step
4061 in the right direction, but need to work in most or every browser in
4062 use. Also the bitcoin-qt client is too heavy to fire up to do a
4063 quick transaction. I believe there are other clients available, but
4064 have not tested them.&lt;/p&gt;
4065
4066 &lt;p&gt;My
4067 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4068 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4069 I received 20.15 BTC so far on the address I provided in my blog two
4070 years ago, as can be
4071 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4072 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4073 donation. The blockexplorer service demonstrates quite well that
4074 bitcoin is not quite anonymous and untracked. :) I wonder if the
4075 number of users have gone up since then. If you use bitcoin and want
4076 to show your support of my activity, please send Bitcoin donations to
4077 the same address as last time,
4078 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4079 </description>
4080 </item>
4081
4082 <item>
4083 <title>Git repository for song book for Computer Scientists</title>
4084 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4085 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4086 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4087 <description>&lt;p&gt;As I
4088 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4089 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4090 years ago, and today I finally found time to create a public
4091 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4092 repository for the project&lt;/a&gt;.&lt;/p&gt;
4093
4094 &lt;p&gt;If you want to help out, please clone the source and submit patches
4095 to the HTML version. To generate the PDF and PostScript version,
4096 please use prince XML, or let me know about a useful free software
4097 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4098
4099 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4100 PostScript formats at
4101 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4102 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4103 </description>
4104 </item>
4105
4106 <item>
4107 <title>Gratulerer med 19-årsdagen, Debian!</title>
4108 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4110 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4111 <description>&lt;p&gt;I dag fyller
4112 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4113 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4114 si gratulerer med dagen, Debian!&lt;/p&gt;
4115 </description>
4116 </item>
4117
4118 <item>
4119 <title>Song book for Computer Scientists</title>
4120 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4121 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4122 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4123 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4124 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4125 collecting computer related songs for use at parties. The original
4126 version was written in LaTeX, but a few years ago I got help from
4127 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4128 while keeping the ability to create a nice book in PDF format. I have
4129 not had time to maintain the book for a while now, and guess I should
4130 put it up on some public version control repository where others can
4131 help me extend and update the book. If anyone is volunteering to help
4132 me with this, send me an email. Also let me know if there are songs
4133 missing in my book.&lt;/p&gt;
4134
4135 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4136 me today that I really should let all my readers share the joys of
4137 singing out load about programming, computers and computer networks.
4138 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4139 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4140 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4141 Computer Science Songbook&lt;/a&gt;.
4142 </description>
4143 </item>
4144
4145 <item>
4146 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4147 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4148 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4149 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4150 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4151 around 1000 at the moment. To be able to get help from the vendors
4152 when something go wrong, we want to keep the firmware on the servers
4153 up to date. If the firmware isn&#39;t the latest and greatest, the
4154 vendors typically refuse to start debugging any problems until the
4155 firmware is upgraded. So before every reboot, we want to upgrade the
4156 firmware, and we would really like everyone handling servers at the
4157 university to do this themselves when they plan to reboot a machine.
4158 For that to happen we at the unix server admin group need to provide
4159 the tools to do so.&lt;/p&gt;
4160
4161 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4162 fetch and install the latest firmware for the servers we got. Most of
4163 our hardware are from Dell and HP, so I have focused on these servers
4164 so far. This blog post is about the Dell part.&lt;/P&gt;
4165
4166 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4167 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4168 with firmware information for all 11th generation servers, listing
4169 which firmware should be used on a given model and where on the FTP
4170 site I can find it. Using a simple perl XML parser I can then
4171 download the shell scripts Dell provides to do firmware upgrades from
4172 within Linux and reboot when all the firmware is primed and ready to
4173 be activated on the first reboot.&lt;/p&gt;
4174
4175 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4176 Are there anyone working on similar tools for firmware upgrading all
4177 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4178
4179 &lt;p&gt;&lt;pre&gt;
4180 #!/usr/bin/perl
4181 use strict;
4182 use warnings;
4183 use File::Temp qw(tempdir);
4184 BEGIN {
4185 # Install needed RHEL packages if missing
4186 my %rhelmodules = (
4187 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4188 );
4189 for my $module (keys %rhelmodules) {
4190 eval &quot;use $module;&quot;;
4191 if ($@) {
4192 my $pkg = $rhelmodules{$module};
4193 system(&quot;yum install -y $pkg&quot;);
4194 eval &quot;use $module;&quot;;
4195 }
4196 }
4197 }
4198 my $errorsto = &#39;pere@hungry.com&#39;;
4199
4200 upgrade_dell();
4201
4202 exit 0;
4203
4204 sub run_firmware_script {
4205 my ($opts, $script) = @_;
4206 unless ($script) {
4207 print STDERR &quot;fail: missing script name\n&quot;;
4208 exit 1
4209 }
4210 print STDERR &quot;Running $script\n\n&quot;;
4211
4212 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4213 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4214 } else {
4215 print STDERR &quot;fail: firmware script returned error\n&quot;;
4216 }
4217 }
4218
4219 sub run_firmware_scripts {
4220 my ($opts, @dirs) = @_;
4221 # Run firmware packages
4222 for my $dir (@dirs) {
4223 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4224 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4225 while (my $s = readdir $dh) {
4226 next if $s =~ m/^\.\.?/;
4227 run_firmware_script($opts, &quot;$dir/$s&quot;);
4228 }
4229 closedir $dh;
4230 }
4231 }
4232
4233 sub download {
4234 my $url = shift;
4235 print STDERR &quot;info: Downloading $url\n&quot;;
4236 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4237 }
4238
4239 sub upgrade_dell {
4240 my @dirs;
4241 my $product = `dmidecode -s system-product-name`;
4242 chomp $product;
4243
4244 if ($product =~ m/PowerEdge/) {
4245
4246 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4247 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4248
4249 my $tmpdir = tempdir(
4250 CLEANUP =&gt; 1
4251 );
4252 chdir($tmpdir);
4253 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4254 system(&#39;gunzip Catalog.xml.gz&#39;);
4255 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4256 # -q is quiet, disabling interactivity and reducing console output
4257 my $fwopts = &quot;-q&quot;;
4258 if (@paths) {
4259 for my $url (@paths) {
4260 fetch_dell_fw($url);
4261 }
4262 run_firmware_scripts($fwopts, $tmpdir);
4263 } else {
4264 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4265 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4266 }
4267 chdir(&#39;/&#39;);
4268 } else {
4269 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4270 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4271 }
4272 }
4273
4274 sub fetch_dell_fw {
4275 my $path = shift;
4276 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4277 download($url);
4278 }
4279
4280 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4281 # firmware packages to download from Dell. Only work for Linux
4282 # machines and 11th generation Dell servers.
4283 sub fetch_dell_fw_list {
4284 my $filename = shift;
4285
4286 my $product = `dmidecode -s system-product-name`;
4287 chomp $product;
4288 my ($mybrand, $mymodel) = split(/\s+/, $product);
4289
4290 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4291
4292 my $xml = XMLin($filename);
4293 my @paths;
4294 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4295 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4296 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4297 my $oscode;
4298 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4299 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4300 } else {
4301 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4302 }
4303 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4304 {
4305 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4306 }
4307 }
4308 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4309 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4310
4311 # Drop application packages, only firmware and BIOS
4312 next if &#39;APAC&#39; eq $componenttype;
4313
4314 my $cpath = $component-&gt;{path};
4315 for my $path (@paths) {
4316 if ($cpath =~ m%/$path$%) {
4317 push(@paths, $cpath);
4318 }
4319 }
4320 }
4321 return @paths;
4322 }
4323 &lt;/pre&gt;
4324
4325 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4326 it could work on other platforms with some tweaking. Anyone know a
4327 index like Catalog.xml is available from HP for HP servers? At the
4328 moment I maintain a similar list manually and it is quickly getting
4329 outdated.&lt;/p&gt;
4330 </description>
4331 </item>
4332
4333 <item>
4334 <title>How is booting into runlevel 1 different from single user boots?</title>
4335 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4336 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4337 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4338 <description>&lt;p&gt;Wouter Verhelst have some
4339 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4340 comments and opinions&lt;/a&gt; on my blog post on
4341 &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
4342 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4343 &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
4344 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4345 small piece of his comment now, and though it best to address the
4346 misunderstanding he bring forward:&lt;/p&gt;
4347
4348 &lt;p&gt;&lt;blockquote&gt;
4349 Currently, a system admin has four options: [...] boot to a
4350 single-user system (by adding &#39;single&#39; to the kernel command line;
4351 this runs rcS and rc1 scripts)
4352 &lt;/blockquote&gt;&lt;/p&gt;
4353
4354 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4355 and booting into runlevel 1 is the same. I am not surprised he
4356 believe this, because it would make sense and is a quite sensible
4357 thing to believe. But because the boot in Debian is slightly broken,
4358 runlevel 1 do not work properly and it isn&#39;t the same as single user
4359 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4360 hard to explain.&lt;/p&gt;
4361
4362 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4363 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4364 executed in single user mode is sulogin. Single user mode is a boot
4365 state &quot;between&quot; the runlevels, and when booting into single user mode,
4366 only the scripts in /etc/rcS.d/ are executed before the init process
4367 enters the single user state. When switching to runlevel 1, the state
4368 is in fact not ending in runlevel 1, but it passes through runlevel 1
4369 and end up in the single user mode (see /etc/rc1.d/S03single, which
4370 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4371 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4372 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4373 mode).&lt;/p&gt;
4374
4375 &lt;p&gt;This summary might make it clearer. When booting for the first
4376 time into single user mode, the following commands are executed:
4377 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4378 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4379 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4380 trying to continue after visiting single user mode. Not all services
4381 are started again as they should, causing the machine to end up in an
4382 unpredicatble state. This is why Debian admins recommend rebooting
4383 after visiting single user mode.&lt;/p&gt;
4384
4385 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4386 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4387 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4388 stopped when passing through the scripts in /etc/rc1.d/, and not
4389 started again when switching away from runlevel 1 to the runlevels
4390 2-5. I believe the problem is best fixed by moving all the scripts
4391 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4392 functioning single user mode during boot.&lt;/p&gt;
4393
4394 &lt;p&gt;I have spent several years investigating the Debian boot system,
4395 and discovered this problem a few years ago. I suspect it originates
4396 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4397 </description>
4398 </item>
4399
4400 <item>
4401 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4402 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4403 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4404 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4405 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4406 are started from /etc/rcS.d/. In fact, there is a bite more of them
4407 than make sense, and this causes a few problems. What kind of
4408 problems, you might ask. There are at least two problems. The first
4409 is that it is not possible to recover a machine after switching to
4410 runlevel 1. One need to actually reboot to get the machine back to
4411 the expected state. The other is that single user boot will sometimes
4412 run into problems because some of the subsystems are activated before
4413 the root login is presented, causing problems when trying to recover a
4414 machine from a problem in that subsystem. A minor additional point is
4415 that moving more scripts out of rcS.d/ and into the other rc#.d/
4416 directories will increase the amount of scripts that can run in
4417 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4418
4419 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4420 scripts that _have_ to execute before the root login prompt is
4421 presented during a single user boot should go there. Everything else
4422 should go into the numeric runlevels. This means things like
4423 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4424 the numeric runlevels. Today in Debian, there are around 115 init.d
4425 scripts that are started from rcS.d/, and most of them should be moved
4426 out. Do your package have one of them? Please help us make single
4427 user and runlevel 1 better by moving it.&lt;/p&gt;
4428
4429 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4430 etc. should still be started from rcS.d/, but there is for example no
4431 need to have the network enabled before the single user login prompt
4432 is presented.&lt;/p&gt;
4433
4434 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4435 Debian systems working while scripts migrate and during upgrades, the
4436 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4437 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4438 and the next ones can only be moved when their dependencies have been
4439 moved first. This migration must be done sequentially while we ensure
4440 that the package system upgrade packages in the right order to keep
4441 the system state correct. This will require some coordination when it
4442 comes to network related packages, but most of the packages with
4443 scripts that should migrate do not have anything in rcS.d/ depending
4444 on them. Some packages have already been updated, like the sudo
4445 package, while others are still left to do. I wish I had time to work
4446 on this myself, but real live constrains make it unlikely that I will
4447 find time to push this forward.&lt;/p&gt;
4448 </description>
4449 </item>
4450
4451 <item>
4452 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4453 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4454 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4455 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4456 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4457 mentioned the issues I believe should be improved in Debian for its
4458 desktop to be useful for more people. The use case for this is my
4459 parents, which are currently running Kubuntu which solve the
4460 issues.&lt;/p&gt;
4461
4462 &lt;p&gt;I suspect these four missing features are not very hard to
4463 implement. After all, they are present in Ubuntu, so if we wanted to
4464 do this in Debian we would have a source.&lt;/p&gt;
4465
4466 &lt;ol&gt;
4467
4468 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4469 are new packages available for upgrades, a icon in the KDE status bar
4470 indicate this, and clicking on it will activate the simple upgrade
4471 tool to handle it. I have no problem guiding both of my parents
4472 through the process over the phone. If a kernel reboot is required,
4473 this too is indicated by the status bars and the upgrade tool. Last
4474 time I checked, nothing with the same features was working in KDE in
4475 Debian.&lt;/li&gt;
4476
4477 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4478 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4479 currently have a handler for, it will ask the user if the system
4480 should search for a package that would add support for this MIME type,
4481 and if the user say yes, the APT sources will be searched for packages
4482 advertising the MIME type in their control file (visible in the
4483 Packages file in the APT archive). If one or more packages are found,
4484 it is a simple click of the mouse to add support for the missing mime
4485 type. If the package require the user to accept some non-free
4486 license, this is explained to the user. The entire process make it
4487 more clear to the user why something do not work in the browser, and
4488 make the chances higher for the user to blame the web page authors and
4489 not the browser for any missing features.&lt;/li&gt;
4490
4491 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4492 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4493 it is not supporting, a dialog pop up asking the user if the system
4494 should search for a package that would add support for it. This
4495 happen with things like MP3, Windows Media or H.264. The selection
4496 and installation procedure is very similar to the Firefox browser
4497 plugin handling. This is as far as I know implemented using a
4498 gstreamer hook. The end result is that the user easily get access to
4499 the codecs that are present from the APT archives available, while
4500 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4501
4502 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4503 displaying a text/plain file in my Debian browser, it will propose to
4504 start emacs to show it. If I remember correctly, when doing the same
4505 in Kunbutu it show the file as a text file in the browser. At least I
4506 know Opera will show text files within the browser. I much prefer the
4507 latter behaviour.&lt;/li&gt;
4508
4509 &lt;/ol&gt;
4510
4511 &lt;p&gt;There are other nice features as well, like the simplified suite
4512 upgrader, but given that I am the one mostly doing the dist-upgrade,
4513 it do not matter much.&lt;/p&gt;
4514
4515 &lt;p&gt;I really hope we could get these features in place for the next
4516 Debian release. It would require the coordinated effort of several
4517 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4518 </description>
4519 </item>
4520
4521 <item>
4522 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4523 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4524 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4525 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4526 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4527 site is build on Debian/Squeeze, and this platform was chosen because
4528 I am most familiar with Debian (being a Debian Developer for around 10
4529 years) because it is the latest stable Debian release which should get
4530 security support for a few years.&lt;/p&gt;
4531
4532 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4533 that are missing in Debian at the moment. It would be great if these
4534 modules were added to the Debian archive, allowing anyone to set up
4535 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4536 in their own country using only Debian packages. The list of modules
4537 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4538 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4539 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4540 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4541 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4542 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4543 easier in the future.&lt;/p&gt;
4544
4545 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4546 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4547 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4548 with the responsibility of tracking security problems, which I really
4549 do not have time for.&lt;/p&gt;
4550 </description>
4551 </item>
4552
4553 <item>
4554 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4555 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4556 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4557 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4558 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4559 posts have been in Norwegian the last few weeks, so here is a short
4560 update in English.&lt;/p&gt;
4561
4562 &lt;p&gt;The kids still keep me too busy to get much free software work
4563 done, but I did manage to organise a project to get a Norwegian port
4564 of the British service
4565 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4566 and it has been running for a month now. The entire project has been
4567 organised by me and two others. Around Christmas we gathered sponsors
4568 to fund the development work. In January I drafted a contract with
4569 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4570 and in February the development took place. Most of it involved
4571 converting the source to use GPS coordinates instead of British
4572 easting/northing, and the resulting code should be a lot easier to get
4573 running in any country by now. The Norwegian
4574 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4575 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4576 source and the source for administrative borders in Norway, and
4577 support for this had to be added/fixed.&lt;/p&gt;
4578
4579 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4580 polishing the system before we announced it March 7th. The system is
4581 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4582 problem reports in a few weeks. Soon we hope to announce the Android
4583 and iPhone versions making it even easier to report problems with the
4584 public infrastructure.&lt;/p&gt;
4585
4586 &lt;p&gt;Perhaps something to consider for those of you in countries without
4587 such service?&lt;/p&gt;
4588 </description>
4589 </item>
4590
4591 <item>
4592 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4593 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4594 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4595 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4596 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4597 issues here at my work with the University of Oslo. My idea is that
4598 it should be possible to use the information about security issues
4599 available on the Internet, and check our locally
4600 maintained/distributed software against this information. It should
4601 allow us to verify that no known security issues are forgotten. The
4602 CVE database listing vulnerabilities seem like a great central point,
4603 and by using the package lists from Debian mapped to CVEs provided by
4604 the testing security team, I believed it should be possible to figure
4605 out which security holes were present in our free software
4606 collection.&lt;/p&gt;
4607
4608 &lt;p&gt;After reading up on the topic, it became obvious that the first
4609 building block is to be able to name software packages in a unique and
4610 consistent way across data sources. I considered several ways to do
4611 this, for example coming up with my own naming scheme like using URLs
4612 to project home pages or URLs to the Freshmeat entries, or using some
4613 existing naming scheme. And it seem like I am not the first one to
4614 come across this problem, as MITRE already proposed and implemented a
4615 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4616 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4617 software, hardware and other platform components. The CPE ids are
4618 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4619 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4620 issues for any CPE name. With this in place, all I need to do is to
4621 locate the CPE id for the software packages we use at the university.
4622 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4623 NVD entry if a CVE for the package exist).&lt;/p&gt;
4624
4625 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4626 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4627 check out, one could look up
4628 &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
4629 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4630 The most recent one is
4631 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4632 and at the bottom of the NVD page for this vulnerability the complete
4633 list of affected versions is provided.&lt;/p&gt;
4634
4635 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4636 for offline processing of issues. Using this dump, I&#39;ve written a
4637 small script taking a list of CPEs as input and list all CVEs
4638 affecting the packages represented by these CPEs. One give it CPEs
4639 with version numbers as specified above and get a list of open
4640 security issues out.&lt;/p&gt;
4641
4642 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4643 information need to be high. For that to happen, I believe as many as
4644 possible need to use and contribute to the NVD database. I notice
4645 RHEL is providing
4646 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4647 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4648 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4649
4650 &lt;p&gt;To get an idea about the quality for free software, I spent some
4651 time making it possible to compare the CVE database from Debian with
4652 the CVE database in NVD. The result look fairly good, but there are
4653 some inconsistencies in NVD (same software package having several
4654 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4655 Debian believe are affected by a CVE). Hope to find time to improve
4656 the quality of NVD, but that require being able to get in touch with
4657 someone maintaining it. So far my three emails with questions and
4658 corrections have not seen any reply, but I hope contact can be
4659 established soon.&lt;/p&gt;
4660
4661 &lt;p&gt;An interesting application for CPEs is cross platform package
4662 mapping. It would be useful to know which packages in for example
4663 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4664 this would be trivial if all linux distributions provided CPE entries
4665 for their packages.&lt;/p&gt;
4666 </description>
4667 </item>
4668
4669 <item>
4670 <title>Which module is loaded for a given PCI and USB device?</title>
4671 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4672 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4673 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4674 <description>&lt;p&gt;In the
4675 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4676 package in Debian, there is a script to report useful information
4677 about the running hardware for use when people report missing
4678 information. One part of this script that I find very useful when
4679 debugging hardware problems, is the part mapping loaded kernel module
4680 to the PCI device it claims. It allow me to quickly see if the kernel
4681 module I expect is driving the hardware I am struggling with. To see
4682 the output, make sure discover-data is installed and run
4683 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4684 one of my machines like this:&lt;/p&gt;
4685
4686 &lt;pre&gt;
4687 loaded modules:
4688 10de:03eb i2c_nforce2
4689 10de:03f1 ohci_hcd
4690 10de:03f2 ehci_hcd
4691 10de:03f0 snd_hda_intel
4692 10de:03ec pata_amd
4693 10de:03f6 sata_nv
4694 1022:1103 k8temp
4695 109e:036e bttv
4696 109e:0878 snd_bt87x
4697 11ab:4364 sky2
4698 &lt;/pre&gt;
4699
4700 &lt;p&gt;The code in question look like this, slightly modified for
4701 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4702
4703 &lt;pre&gt;
4704 if [ -d /sys/bus/pci/devices/ ] ; then
4705 echo loaded pci modules:
4706 (
4707 cd /sys/bus/pci/devices/
4708 for address in * ; do
4709 if [ -d &quot;$address/driver/module&quot; ] ; then
4710 module=`cd $address/driver/module ; pwd -P | xargs basename`
4711 if grep -q &quot;^$module &quot; /proc/modules ; then
4712 address=$(echo $address |sed s/0000://)
4713 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4714 echo &quot;$id $module&quot;
4715 fi
4716 fi
4717 done
4718 )
4719 echo
4720 fi
4721 &lt;/pre&gt;
4722
4723 &lt;p&gt;Similar code could be used to extract USB device module
4724 mappings:&lt;/p&gt;
4725
4726 &lt;pre&gt;
4727 if [ -d /sys/bus/usb/devices/ ] ; then
4728 echo loaded usb modules:
4729 (
4730 cd /sys/bus/usb/devices/
4731 for address in * ; do
4732 if [ -d &quot;$address/driver/module&quot; ] ; then
4733 module=`cd $address/driver/module ; pwd -P | xargs basename`
4734 if grep -q &quot;^$module &quot; /proc/modules ; then
4735 address=$(echo $address |sed s/0000://)
4736 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4737 if [ &quot;$id&quot; ] ; then
4738 echo &quot;$id $module&quot;
4739 fi
4740 fi
4741 fi
4742 done
4743 )
4744 echo
4745 fi
4746 &lt;/pre&gt;
4747
4748 &lt;p&gt;This might perhaps be something to include in other tools as
4749 well.&lt;/p&gt;
4750 </description>
4751 </item>
4752
4753 <item>
4754 <title>How to test if a laptop is working with Linux</title>
4755 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4756 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4757 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4758 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4759 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4760 batch of computers will work with Linux. Every year for the last few
4761 years the university have organised shared bid of a few thousand
4762 computers, and this year HP won the bid. Two different desktops and
4763 five different laptops are on the list this year. We in the UNIX
4764 group want to know which one of these computers work well with RHEL
4765 and Ubuntu, the two Linux distributions we currently handle at the
4766 university.&lt;/p&gt;
4767
4768 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4769 perhaps inspire others to test hardware as well. To test, I PXE
4770 install the OS version of choice, and log in as my normal user and run
4771 a few applications and plug in selected pieces of hardware. When
4772 something fail, I make a note about this in the test matrix and move
4773 on. If I have some spare time I try to report the bug to the OS
4774 vendor, but as I only have the machines for a short time, I rarely
4775 have the time to do this for all the problems I find.&lt;/p&gt;
4776
4777 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4778 I perform on a new model.&lt;/p&gt;
4779
4780 &lt;ul&gt;
4781
4782 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4783 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4784 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4785
4786 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4787 installation, X.org is working.&lt;/li&gt;
4788
4789 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4790 package mesa-utils on Ubuntu) and writing down the frames per second
4791 reported by the program.&lt;/li&gt;
4792
4793 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4794 logging in, and if I can hear this the test is successful. If there
4795 are several audio exits on the machine, I try them all and check if
4796 the Gnome/KDE audio mixer can control where to send the sound. I
4797 normally test this by playing
4798 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4799 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4800
4801 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4802 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4803
4804 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4805 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4806
4807 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4808 picture from the v4l device show up.&lt;/li&gt;
4809
4810 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4811 any bluetooth devices are discovered. In my office, I normally see a
4812 few.&lt;/li&gt;
4813
4814 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4815 memory modules lying around, and stick them in and see if Gnome/KDE
4816 notice this.&lt;/li&gt;
4817
4818 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4819 special button work, and if the laptop continue to work after
4820 resume.&lt;/li&gt;
4821
4822 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4823 adjusting background light, switching on/off external video output,
4824 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4825 laptop to laptop, so I just write down which are working and which are
4826 not.&lt;/li&gt;
4827
4828 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4829 acceleration sensors etc. I rarely test these, as I do not know how
4830 to quickly test if they are working or not, so I only document their
4831 existence.&lt;/li&gt;
4832
4833 &lt;/ul&gt;
4834
4835 &lt;p&gt;By now I suspect you are really curious what the test results are
4836 for the HP machines I am testing. I&#39;m not done yet, so I will report
4837 the test results later. For now I can report that HP 8100 Elite work
4838 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4839 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4840 can see, I have most machines left to test. One interesting
4841 observation is that Ubuntu Lucid has almost twice the frame rate than
4842 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4843 </description>
4844 </item>
4845
4846 <item>
4847 <title>Some thoughts on BitCoins</title>
4848 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4849 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4850 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4851 <description>&lt;p&gt;As I continue to explore
4852 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4853 what properties the system have, and how it will be affected by laws
4854 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4855
4856 &lt;p&gt;One interesting thing to note is that since the transactions are
4857 verified using a peer to peer network, all details about a transaction
4858 is known to everyone. This means that if a BitCoin address has been
4859 published like I did with mine in my initial post about BitCoin, it is
4860 possible for everyone to see how many BitCoins have been transfered to
4861 that address. There is even a web service to look at the details for
4862 all transactions. There I can see that my address
4863 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4864 have received 16.06 Bitcoin, the
4865 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4866 address of Simon Phipps have received 181.97 BitCoin and the address
4867 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4868 of EFF have received 2447.38 BitCoins so far. Thank you to each and
4869 every one of you that donated bitcoins to support my activity. The
4870 fact that anyone can see how much money was transfered to a given
4871 address make it more obvious why the BitCoin community recommend to
4872 generate and hand out a new address for each transaction. I&#39;m told
4873 there is no way to track which addresses belong to a given person or
4874 organisation without the person or organisation revealing it
4875 themselves, as Simon, EFF and I have done.&lt;/p&gt;
4876
4877 &lt;p&gt;In Norway, and in most other countries, there are laws and
4878 regulations limiting how much money one can transfer across the border
4879 without declaring it. There are money laundering, tax and accounting
4880 laws and regulations I would expect to apply to the use of BitCoin.
4881 If the Skolelinux foundation
4882 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
4883 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
4884 normal bank transfers like EFF is doing, how should this be accounted?
4885 Given that it is impossible to know if money can cross the border or
4886 not, should everything or nothing be declared? What exchange rate
4887 should be used when calculating taxes? Would receivers have to pay
4888 income tax if the foundation were to pay Skolelinux contributors in
4889 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
4890
4891 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
4892 accepted by a lot of users. It must be possible to get easy access to
4893 the currency (as a wage or using currency exchanges), and it must be
4894 easy to spend it. At the moment BitCoin seem fairly easy to get
4895 access to, but there are very few places to spend it. I am not really
4896 a regular user of any of the vendor types currently accepting BitCoin,
4897 so I wonder when my kind of shop would start accepting BitCoins. I
4898 would like to buy electronics, travels and subway tickets, not herbs
4899 and books. :) The currency is young, and this will improve over time
4900 if it become popular, but I suspect regular banks will start to lobby
4901 to get BitCoin declared illegal if it become popular. I&#39;m sure they
4902 will claim it is helping fund terrorism and money laundering (which
4903 probably would be true, as is any currency in existence), but I
4904 believe the problems should be solved elsewhere and not by blaming
4905 currencies.&lt;/p&gt;
4906
4907 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
4908 CPU intensive process that depend on a bit of luck as well (as one is
4909 competing against all the other miners currently spending CPU cycles
4910 to see which one get the next lump of cash). The &quot;winner&quot; get 50
4911 BitCoin when this happen. Yesterday I came across the obvious way to
4912 join forces to increase ones changes of getting at least some coins,
4913 by coordinating the work on mining BitCoins across several machines
4914 and people, and sharing the result if one is lucky and get the 50
4915 BitCoins. Check out
4916 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
4917 if this sounds interesting. I have not had time to try to set up a
4918 machine to participate there yet, but have seen that running on ones
4919 own for a few days have not yield any BitCoins througth mining
4920 yet.&lt;/p&gt;
4921
4922 &lt;p&gt;Update 2010-12-15: Found an &lt;a
4923 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
4924 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
4925 it was interesting to read. The arguments presented seem to be
4926 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
4927 </description>
4928 </item>
4929
4930 <item>
4931 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
4932 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
4933 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
4934 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
4935 <description>&lt;p&gt;With this weeks lawless
4936 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
4937 attacks&lt;/a&gt; on Wikileak and
4938 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
4939 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
4940 not be trusted to handle money transactions.
4941 A blog post from
4942 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
4943 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
4944 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
4945 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
4946 some help from my friend to get it all running, and he even handed me
4947 some bitcoins to get started. I even donated a few bitcoins to Simon
4948 for helping me remember BitCoin.&lt;/p&gt;
4949
4950 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
4951 crypto-currency, decentralised and handled using peer-to-peer
4952 networks. It allows anonymous transactions and prohibits central
4953 control over the transactions, making it impossible for governments
4954 and companies alike to block donations and other transactions. The
4955 source is free software, and while the key dependency wxWidgets 2.9
4956 for the graphical user interface is missing in Debian, the command
4957 line client builds just fine. Hopefully Jonas
4958 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
4959 Debian&lt;/a&gt; soon.&lt;/p&gt;
4960
4961 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
4962 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
4963 bitcoins&lt;/a&gt; when selling services and goods, and there are even
4964 currency &quot;stock&quot; markets where the exchange rate is decided. There
4965 are not many users so far, but the concept seems promising. If you
4966 want to get started and lack a friend with any bitcoins to spare,
4967 you can even get
4968 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
4969 bitcoin at the time of writing). Use
4970 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
4971 on the current exchange rates.&lt;/p&gt;
4972
4973 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
4974 machines. If you want to support my activity, please send Bitcoin
4975 donations to the address
4976 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
4977 </description>
4978 </item>
4979
4980 <item>
4981 <title>Why isn&#39;t Debian Edu using VLC?</title>
4982 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
4983 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
4984 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
4985 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4986 presented, and the winner among the multimedia player were VLC.
4987 Personally, I like VLC, and it is my player of choice when I first try
4988 to play a video file or stream. Only if VLC fail will I drag out
4989 gmplayer to see if it can do better. The reason is mostly the failure
4990 model and trust. When VLC fail, it normally pop up a error message
4991 reporting the problem. When mplayer fail, it normally segfault or
4992 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4993
4994 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4995 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4996 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4997 plugin to play web videos seamlessly, and the VLC browser plugin is
4998 not very good. For example, it lack in-line control buttons, so there
4999 is no way for the user to pause the video. Also, when I
5000 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5001 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5002 failed on several video pages where mplayer based plugins worked. If
5003 the browser plugin for VLC was as good as the gecko-mediaplayer
5004 package (which uses mplayer), we would switch.&lt;/P&gt;
5005
5006 &lt;p&gt;While VLC is a good player, its user interface is slightly
5007 annoying. The most annoying feature is its inconsistent use of
5008 keyboard shortcuts. When the player is in full screen mode, its
5009 shortcuts are different from when it is playing the video in a window.
5010 For example, space only work as pause when in full screen mode. I
5011 wish it had consisten shortcuts and that space also would work when in
5012 window mode. Another nice shortcut in gmplayer is [enter] to restart
5013 the current video. It is very nice when playing short videos from the
5014 web and want to restart it when new people arrive to have a look at
5015 what is going on.&lt;/p&gt;
5016 </description>
5017 </item>
5018
5019 <item>
5020 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5021 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5022 <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>
5023 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5024 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5025 upgrade testing of the
5026 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5027 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5028 This seem like a very good idea, so I adjusted by test scripts and
5029 can now present the updated result from today:&lt;/p&gt;
5030
5031 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5032
5033 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5034
5035 &lt;blockquote&gt;&lt;p&gt;
5036 apache2.2-bin
5037 aptdaemon
5038 baobab
5039 binfmt-support
5040 browser-plugin-gnash
5041 cheese-common
5042 cli-common
5043 cups-pk-helper
5044 dmz-cursor-theme
5045 empathy
5046 empathy-common
5047 freedesktop-sound-theme
5048 freeglut3
5049 gconf-defaults-service
5050 gdm-themes
5051 gedit-plugins
5052 geoclue
5053 geoclue-hostip
5054 geoclue-localnet
5055 geoclue-manual
5056 geoclue-yahoo
5057 gnash
5058 gnash-common
5059 gnome
5060 gnome-backgrounds
5061 gnome-cards-data
5062 gnome-codec-install
5063 gnome-core
5064 gnome-desktop-environment
5065 gnome-disk-utility
5066 gnome-screenshot
5067 gnome-search-tool
5068 gnome-session-canberra
5069 gnome-system-log
5070 gnome-themes-extras
5071 gnome-themes-more
5072 gnome-user-share
5073 gstreamer0.10-fluendo-mp3
5074 gstreamer0.10-tools
5075 gtk2-engines
5076 gtk2-engines-pixbuf
5077 gtk2-engines-smooth
5078 hamster-applet
5079 libapache2-mod-dnssd
5080 libapr1
5081 libaprutil1
5082 libaprutil1-dbd-sqlite3
5083 libaprutil1-ldap
5084 libart2.0-cil
5085 libboost-date-time1.42.0
5086 libboost-python1.42.0
5087 libboost-thread1.42.0
5088 libchamplain-0.4-0
5089 libchamplain-gtk-0.4-0
5090 libcheese-gtk18
5091 libclutter-gtk-0.10-0
5092 libcryptui0
5093 libdiscid0
5094 libelf1
5095 libepc-1.0-2
5096 libepc-common
5097 libepc-ui-1.0-2
5098 libfreerdp-plugins-standard
5099 libfreerdp0
5100 libgconf2.0-cil
5101 libgdata-common
5102 libgdata7
5103 libgdu-gtk0
5104 libgee2
5105 libgeoclue0
5106 libgexiv2-0
5107 libgif4
5108 libglade2.0-cil
5109 libglib2.0-cil
5110 libgmime2.4-cil
5111 libgnome-vfs2.0-cil
5112 libgnome2.24-cil
5113 libgnomepanel2.24-cil
5114 libgpod-common
5115 libgpod4
5116 libgtk2.0-cil
5117 libgtkglext1
5118 libgtksourceview2.0-common
5119 libmono-addins-gui0.2-cil
5120 libmono-addins0.2-cil
5121 libmono-cairo2.0-cil
5122 libmono-corlib2.0-cil
5123 libmono-i18n-west2.0-cil
5124 libmono-posix2.0-cil
5125 libmono-security2.0-cil
5126 libmono-sharpzip2.84-cil
5127 libmono-system2.0-cil
5128 libmtp8
5129 libmusicbrainz3-6
5130 libndesk-dbus-glib1.0-cil
5131 libndesk-dbus1.0-cil
5132 libopal3.6.8
5133 libpolkit-gtk-1-0
5134 libpt2.6.7
5135 libpython2.6
5136 librpm1
5137 librpmio1
5138 libsdl1.2debian
5139 libsrtp0
5140 libssh-4
5141 libtelepathy-farsight0
5142 libtelepathy-glib0
5143 libtidy-0.99-0
5144 media-player-info
5145 mesa-utils
5146 mono-2.0-gac
5147 mono-gac
5148 mono-runtime
5149 nautilus-sendto
5150 nautilus-sendto-empathy
5151 p7zip-full
5152 pkg-config
5153 python-aptdaemon
5154 python-aptdaemon-gtk
5155 python-axiom
5156 python-beautifulsoup
5157 python-bugbuddy
5158 python-clientform
5159 python-coherence
5160 python-configobj
5161 python-crypto
5162 python-cupshelpers
5163 python-elementtree
5164 python-epsilon
5165 python-evolution
5166 python-feedparser
5167 python-gdata
5168 python-gdbm
5169 python-gst0.10
5170 python-gtkglext1
5171 python-gtksourceview2
5172 python-httplib2
5173 python-louie
5174 python-mako
5175 python-markupsafe
5176 python-mechanize
5177 python-nevow
5178 python-notify
5179 python-opengl
5180 python-openssl
5181 python-pam
5182 python-pkg-resources
5183 python-pyasn1
5184 python-pysqlite2
5185 python-rdflib
5186 python-serial
5187 python-tagpy
5188 python-twisted-bin
5189 python-twisted-conch
5190 python-twisted-core
5191 python-twisted-web
5192 python-utidylib
5193 python-webkit
5194 python-xdg
5195 python-zope.interface
5196 remmina
5197 remmina-plugin-data
5198 remmina-plugin-rdp
5199 remmina-plugin-vnc
5200 rhythmbox-plugin-cdrecorder
5201 rhythmbox-plugins
5202 rpm-common
5203 rpm2cpio
5204 seahorse-plugins
5205 shotwell
5206 software-center
5207 system-config-printer-udev
5208 telepathy-gabble
5209 telepathy-mission-control-5
5210 telepathy-salut
5211 tomboy
5212 totem
5213 totem-coherence
5214 totem-mozilla
5215 totem-plugins
5216 transmission-common
5217 xdg-user-dirs
5218 xdg-user-dirs-gtk
5219 xserver-xephyr
5220 &lt;/p&gt;&lt;/blockquote&gt;
5221
5222 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5223
5224 &lt;blockquote&gt;&lt;p&gt;
5225 cheese
5226 ekiga
5227 eog
5228 epiphany-extensions
5229 evolution-exchange
5230 fast-user-switch-applet
5231 file-roller
5232 gcalctool
5233 gconf-editor
5234 gdm
5235 gedit
5236 gedit-common
5237 gnome-games
5238 gnome-games-data
5239 gnome-nettool
5240 gnome-system-tools
5241 gnome-themes
5242 gnuchess
5243 gucharmap
5244 guile-1.8-libs
5245 libavahi-ui0
5246 libdmx1
5247 libgalago3
5248 libgtk-vnc-1.0-0
5249 libgtksourceview2.0-0
5250 liblircclient0
5251 libsdl1.2debian-alsa
5252 libspeexdsp1
5253 libsvga1
5254 rhythmbox
5255 seahorse
5256 sound-juicer
5257 system-config-printer
5258 totem-common
5259 transmission-gtk
5260 vinagre
5261 vino
5262 &lt;/p&gt;&lt;/blockquote&gt;
5263
5264 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5265
5266 &lt;blockquote&gt;&lt;p&gt;
5267 gstreamer0.10-gnomevfs
5268 &lt;/p&gt;&lt;/blockquote&gt;
5269
5270 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5271
5272 &lt;blockquote&gt;&lt;p&gt;
5273 [nothing]
5274 &lt;/p&gt;&lt;/blockquote&gt;
5275
5276 &lt;p&gt;This is for KDE:&lt;/p&gt;
5277
5278 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5279
5280 &lt;blockquote&gt;&lt;p&gt;
5281 ksmserver
5282 &lt;/p&gt;&lt;/blockquote&gt;
5283
5284 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5285
5286 &lt;blockquote&gt;&lt;p&gt;
5287 kwin
5288 network-manager-kde
5289 &lt;/p&gt;&lt;/blockquote&gt;
5290
5291 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5292
5293 &lt;blockquote&gt;&lt;p&gt;
5294 arts
5295 dolphin
5296 freespacenotifier
5297 google-gadgets-gst
5298 google-gadgets-xul
5299 kappfinder
5300 kcalc
5301 kcharselect
5302 kde-core
5303 kde-plasma-desktop
5304 kde-standard
5305 kde-window-manager
5306 kdeartwork
5307 kdeartwork-emoticons
5308 kdeartwork-style
5309 kdeartwork-theme-icon
5310 kdebase
5311 kdebase-apps
5312 kdebase-workspace
5313 kdebase-workspace-bin
5314 kdebase-workspace-data
5315 kdeeject
5316 kdelibs
5317 kdeplasma-addons
5318 kdeutils
5319 kdewallpapers
5320 kdf
5321 kfloppy
5322 kgpg
5323 khelpcenter4
5324 kinfocenter
5325 konq-plugins-l10n
5326 konqueror-nsplugins
5327 kscreensaver
5328 kscreensaver-xsavers
5329 ktimer
5330 kwrite
5331 libgle3
5332 libkde4-ruby1.8
5333 libkonq5
5334 libkonq5-templates
5335 libnetpbm10
5336 libplasma-ruby
5337 libplasma-ruby1.8
5338 libqt4-ruby1.8
5339 marble-data
5340 marble-plugins
5341 netpbm
5342 nuvola-icon-theme
5343 plasma-dataengines-workspace
5344 plasma-desktop
5345 plasma-desktopthemes-artwork
5346 plasma-runners-addons
5347 plasma-scriptengine-googlegadgets
5348 plasma-scriptengine-python
5349 plasma-scriptengine-qedje
5350 plasma-scriptengine-ruby
5351 plasma-scriptengine-webkit
5352 plasma-scriptengines
5353 plasma-wallpapers-addons
5354 plasma-widget-folderview
5355 plasma-widget-networkmanagement
5356 ruby
5357 sweeper
5358 update-notifier-kde
5359 xscreensaver-data-extra
5360 xscreensaver-gl
5361 xscreensaver-gl-extra
5362 xscreensaver-screensaver-bsod
5363 &lt;/p&gt;&lt;/blockquote&gt;
5364
5365 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5366
5367 &lt;blockquote&gt;&lt;p&gt;
5368 ark
5369 google-gadgets-common
5370 google-gadgets-qt
5371 htdig
5372 kate
5373 kdebase-bin
5374 kdebase-data
5375 kdepasswd
5376 kfind
5377 klipper
5378 konq-plugins
5379 konqueror
5380 ksysguard
5381 ksysguardd
5382 libarchive1
5383 libcln6
5384 libeet1
5385 libeina-svn-06
5386 libggadget-1.0-0b
5387 libggadget-qt-1.0-0b
5388 libgps19
5389 libkdecorations4
5390 libkephal4
5391 libkonq4
5392 libkonqsidebarplugin4a
5393 libkscreensaver5
5394 libksgrd4
5395 libksignalplotter4
5396 libkunitconversion4
5397 libkwineffects1a
5398 libmarblewidget4
5399 libntrack-qt4-1
5400 libntrack0
5401 libplasma-geolocation-interface4
5402 libplasmaclock4a
5403 libplasmagenericshell4
5404 libprocesscore4a
5405 libprocessui4a
5406 libqalculate5
5407 libqedje0a
5408 libqtruby4shared2
5409 libqzion0a
5410 libruby1.8
5411 libscim8c2a
5412 libsmokekdecore4-3
5413 libsmokekdeui4-3
5414 libsmokekfile3
5415 libsmokekhtml3
5416 libsmokekio3
5417 libsmokeknewstuff2-3
5418 libsmokeknewstuff3-3
5419 libsmokekparts3
5420 libsmokektexteditor3
5421 libsmokekutils3
5422 libsmokenepomuk3
5423 libsmokephonon3
5424 libsmokeplasma3
5425 libsmokeqtcore4-3
5426 libsmokeqtdbus4-3
5427 libsmokeqtgui4-3
5428 libsmokeqtnetwork4-3
5429 libsmokeqtopengl4-3
5430 libsmokeqtscript4-3
5431 libsmokeqtsql4-3
5432 libsmokeqtsvg4-3
5433 libsmokeqttest4-3
5434 libsmokeqtuitools4-3
5435 libsmokeqtwebkit4-3
5436 libsmokeqtxml4-3
5437 libsmokesolid3
5438 libsmokesoprano3
5439 libtaskmanager4a
5440 libtidy-0.99-0
5441 libweather-ion4a
5442 libxklavier16
5443 libxxf86misc1
5444 okteta
5445 oxygencursors
5446 plasma-dataengines-addons
5447 plasma-scriptengine-superkaramba
5448 plasma-widget-lancelot
5449 plasma-widgets-addons
5450 plasma-widgets-workspace
5451 polkit-kde-1
5452 ruby1.8
5453 systemsettings
5454 update-notifier-common
5455 &lt;/p&gt;&lt;/blockquote&gt;
5456
5457 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5458 aptitude a bit more similar, but there are still quite a lott of
5459 differences. I have no idea what packages should be installed after
5460 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5461 </description>
5462 </item>
5463
5464 <item>
5465 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5466 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5467 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5468 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5469 <description>&lt;p&gt;Most of the computers in use by the
5470 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5471 are virtual machines. And they have been Xen machines running on a
5472 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5473 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5474 bit harder that it could have been, because we set up the Xen virtual
5475 machines to get the virtual partitions from LVM, which as far as I
5476 know is not supported by KVM. So to migrate, we had to convert
5477 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5478
5479 &lt;p&gt;I found
5480 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5481 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5482 migration. It uses qemu-img from the qemu package to make the disk
5483 image, parted to partition it, losetup and kpartx to present the disk
5484 image partions as devices, and dd to copy the data. I NFS mounted the
5485 new servers storage area on the old server to do the migration.&lt;/p&gt;
5486
5487 &lt;pre&gt;
5488 #!/bin/sh
5489
5490 # Based on
5491 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5492
5493 set -e
5494 set -x
5495
5496 if [ -z &quot;$1&quot; ] ; then
5497 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5498 exit 1
5499 else
5500 host=&quot;$1&quot;
5501 fi
5502
5503 if [ ! -e /dev/vg_data/$host-disk ] ; then
5504 echo &quot;error: unable to find LVM volume for $host&quot;
5505 exit 1
5506 fi
5507
5508 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5509 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5510 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5511 totalsize=$(( ( $disksize + $swapsize ) ))
5512
5513 img=$host.img
5514 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5515 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5516
5517 parted $img mklabel msdos
5518 parted $img mkpart primary linux-swap 0 $disksize
5519 parted $img mkpart primary ext2 $disksize $totalsize
5520 parted $img set 1 boot on
5521
5522 modprobe dm-mod
5523 losetup /dev/loop0 $img
5524 kpartx -a /dev/loop0
5525
5526 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5527 fsck.ext3 -f /dev/mapper/loop0p1 || true
5528 mkswap /dev/mapper/loop0p2
5529
5530 kpartx -d /dev/loop0
5531 losetup -d /dev/loop0
5532 &lt;/pre&gt;
5533
5534 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5535 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5536
5537 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5538 the new disk image attached, installed grub-pc and linux-image-686 and
5539 set up grub to boot from the disk image. After this, the KVM machines
5540 seem to work just fine.&lt;/p&gt;
5541 </description>
5542 </item>
5543
5544 <item>
5545 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5546 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5547 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5548 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5549 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5550 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5551 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5552 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5553
5554 &lt;p&gt;I still do not know what a correct migration should look like, so I
5555 report any differences between apt and aptitude and hope someone else
5556 can see if anything should be changed.&lt;/p&gt;
5557
5558 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5559
5560 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5561
5562 &lt;blockquote&gt;&lt;p&gt;
5563 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5564 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5565 dmz-cursor-theme empathy empathy-common finger
5566 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5567 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5568 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5569 gnome-cards-data gnome-codec-install gnome-core
5570 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5571 gnome-search-tool gnome-session-canberra gnome-spell
5572 gnome-system-log gnome-themes-extras gnome-themes-more
5573 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5574 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5575 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5576 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5577 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5578 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5579 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5580 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5581 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5582 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5583 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5584 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5585 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5586 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5587 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5588 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5589 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5590 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5591 libmono-security2.0-cil libmono-sharpzip2.84-cil
5592 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5593 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5594 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5595 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5596 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5597 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5598 libxalan2-java libxerces2-java media-player-info mesa-utils
5599 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5600 nautilus-sendto-empathy openoffice.org-writer2latex
5601 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5602 python-aptdaemon python-aptdaemon-gtk python-axiom
5603 python-beautifulsoup python-bugbuddy python-clientform
5604 python-coherence python-configobj python-crypto python-cupshelpers
5605 python-cupsutils python-eggtrayicon python-elementtree
5606 python-epsilon python-evolution python-feedparser python-gdata
5607 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5608 python-gtksourceview2 python-httplib2 python-louie python-mako
5609 python-markupsafe python-mechanize python-nevow python-notify
5610 python-opengl python-openssl python-pam python-pkg-resources
5611 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5612 python-tagpy python-twisted-bin python-twisted-conch
5613 python-twisted-core python-twisted-web python-utidylib python-webkit
5614 python-xdg python-zope.interface remmina remmina-plugin-data
5615 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5616 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5617 software-center svgalibg1 system-config-printer-udev
5618 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5619 totem totem-coherence totem-mozilla totem-plugins
5620 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5621 zip
5622 &lt;/p&gt;&lt;/blockquote&gt;
5623
5624 Installed using apt-get, removed with aptitude
5625
5626 &lt;blockquote&gt;&lt;p&gt;
5627 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5628 epiphany-extensions epiphany-gecko evolution-exchange
5629 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5630 gedit-common gnome-app-install gnome-games gnome-games-data
5631 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5632 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5633 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5634 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5635 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5636 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5637 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5638 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5639 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5640 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5641 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5642 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5643 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5644 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5645 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5646 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5647 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5648 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5649 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5650 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5651 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5652 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5653 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5654 sound-juicer swfdec-gnome system-config-printer totem-common
5655 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5656 &lt;/p&gt;&lt;/blockquote&gt;
5657
5658 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5659
5660 &lt;blockquote&gt;&lt;p&gt;
5661 gstreamer0.10-gnomevfs
5662 &lt;/p&gt;&lt;/blockquote&gt;
5663
5664 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5665
5666 &lt;blockquote&gt;&lt;p&gt;
5667 [nothing]
5668 &lt;/p&gt;&lt;/blockquote&gt;
5669
5670 &lt;p&gt;This is for KDE:&lt;/p&gt;
5671
5672 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5673
5674 &lt;blockquote&gt;&lt;p&gt;
5675 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5676 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5677 ghostscript-x git gnome-audio gnugo granatier gs-common
5678 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5679 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5680 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5681 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5682 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5683 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5684 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5685 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5686 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5687 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5688 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5689 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5690 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5691 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5692 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5693 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5694 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5695 libkrossui4 libmailtools-perl libmime-tools-perl
5696 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5697 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5698 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5699 lirc luatex marble networkstatus noatun-plugins
5700 openoffice.org-writer2latex palapeli palapeli-data parley
5701 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5702 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5703 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5704 ttf-sazanami-gothic
5705 &lt;/p&gt;&lt;/blockquote&gt;
5706
5707 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5708
5709 &lt;blockquote&gt;&lt;p&gt;
5710 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5711 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5712 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5713 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5714 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5715 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5716 kitchensync kiten kjumpingcube klatin klettres klickety klines
5717 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5718 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5719 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5720 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5721 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5722 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5723 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5724 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5725 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5726 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5727 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5728 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5729 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5730 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5731 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5732 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5733 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5734 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5735 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5736 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5737 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5738 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5739 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5740 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5741 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5742 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5743 &lt;/p&gt;&lt;/blockquote&gt;
5744
5745 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5746
5747 &lt;blockquote&gt;&lt;p&gt;
5748 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5749 kdeartwork kdebase kdebase-apps kdebase-workspace
5750 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5751 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5752 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5753 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5754 xscreensaver-screensaver-bsod
5755 &lt;/p&gt;&lt;/blockquote&gt;
5756
5757 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5758
5759 &lt;blockquote&gt;&lt;p&gt;
5760 kdebase-bin konq-plugins konqueror
5761 &lt;/p&gt;&lt;/blockquote&gt;
5762 </description>
5763 </item>
5764
5765 <item>
5766 <title>Gnash buildbot slave and Debian kfreebsd</title>
5767 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5768 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5769 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5770 <description>&lt;p&gt;Answering
5771 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5772 call from the Gnash project&lt;/a&gt; for
5773 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5774 current source, I have set up a virtual KVM machine on the Debian
5775 Edu/Skolelinux virtualization host to test the git source on
5776 Debian/Squeeze. I hope this can help the developers in getting new
5777 releases out more often.&lt;/p&gt;
5778
5779 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5780 I have considered setting up a &lt;a
5781 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5782 machine as well. I have also considered using the kfreebsd
5783 architecture in Debian as a file server in NUUG to get access to the 5
5784 TB zfs volume we currently use to store DV video. Because of this, I
5785 finally got around to do a test installation of Debian/Squeeze with
5786 kfreebsd. Installation went fairly smooth, thought I noticed some
5787 visual glitches in the cdebconf dialogs (black cursor left on the
5788 screen at random locations). Have not gotten very far with the
5789 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5790 fatal problem. Have to spend some more time on it to see if it is
5791 useful as a file server for NUUG. Will try to find time to set up a
5792 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5793 </description>
5794 </item>
5795
5796 <item>
5797 <title>Debian in 3D</title>
5798 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5799 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5800 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5801 <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;
5802
5803 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5804 3D linked in from
5805 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5806 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5807 </description>
5808 </item>
5809
5810 <item>
5811 <title>Software updates 2010-10-24</title>
5812 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5813 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5814 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5815 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5816
5817 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5818 raise money for the project is going well. The lower limit of 10
5819 signers was reached in 24 hours, and so far 13 people have signed it.
5820 More signers and more funding is most welcome, and I am really curious
5821 how far we can get before the time limit of December 24 is reached.
5822 :)&lt;/p&gt;
5823
5824 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5825 about what appear to be a great code coverage tool capable of
5826 generating code coverage stats without any changes to the source code.
5827 It is called
5828 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5829 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5830 It is missing in Debian, but the git source built just fine in Squeeze
5831 after I installed libelf-dev, libdwarf-dev, pkg-config and
5832 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5833 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5834
5835 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5836 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5837 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5838 alpha test release of the Squeeze based Debian Edu /
5839 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5840 release. Give it a try if you need a complete linux solution for your
5841 school, including central infrastructure server, workstations, thin
5842 client servers and diskless workstations. A nice touch added
5843 yesterday is RDP support on the thin client servers, for windows
5844 clients to get a Linux desktop on request.&lt;/p&gt;
5845 </description>
5846 </item>
5847
5848 <item>
5849 <title>Some notes on Flash in Debian and Debian Edu</title>
5850 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5851 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5852 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5853 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5854 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5855 second most popular used package that is missing in Debian. The sixth
5856 most popular is flashplayer-mozilla. This is a clear indication that
5857 working flash is important for Debian users. Around 10 percent of the
5858 users submitting data to popcon.debian.org have this package
5859 installed.&lt;/p&gt;
5860
5861 &lt;p&gt;In the report written by Lars Risan in August 2008
5862&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
5863 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5864 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5865 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5866 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5867 web sites require Flash to work, and lacking working Flash support in
5868 the web browser and the problems with installing it was perceived as a
5869 good reason to stay with Windows.&lt;/p&gt;
5870
5871 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
5872 said to be the retarded cousin that did not really understand
5873 everything you told him but could work fairly well. This was a
5874 comment regarding the problems Linux have with proprietary formats and
5875 non-standard web pages, and is sad because it exposes a fairly common
5876 understanding of whose fault it is if web pages that only work in for
5877 example Internet Explorer 6 fail to work on Firefox, and funny because
5878 it explain very well how annoying it is for users when Linux
5879 distributions do not work with the documents they receive or the web
5880 pages they want to visit.&lt;/p&gt;
5881
5882 &lt;p&gt;This is part of the reason why I believe it is important for Debian
5883 and Debian Edu to have a well working Flash implementation in the
5884 distribution, to get at least popular sites as Youtube and Google
5885 Video to working out of the box. For Squeeze, Debian have the chance
5886 to include the latest version of Gnash that will make this happen, as
5887 the new release 0.8.8 was published a few weeks ago and is resting in
5888 unstable. The new version work with more sites that version 0.8.7.
5889 The Gnash maintainers have asked for a freeze exception, but the
5890 release team have not had time to reply to it yet. I hope they agree
5891 with me that Flash is important for the Debian desktop users, and thus
5892 accept the new package into Squeeze.&lt;/p&gt;
5893 </description>
5894 </item>
5895
5896 <item>
5897 <title>Circular package dependencies harms apt recovery</title>
5898 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
5899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
5900 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
5901 <description>&lt;p&gt;I discovered this while doing
5902 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
5903 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
5904 in Debian still got circular dependencies, and it is often claimed
5905 that apt and aptitude should be able to handle this just fine, but
5906 some times these dependency loops causes apt to fail.&lt;/p&gt;
5907
5908 &lt;p&gt;An example is from todays
5909 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
5910 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
5911 causes perl-modules to fail to upgrade. The cause is simple. If a
5912 package fail to unpack, then only part of packages with the circular
5913 dependency might end up being unpacked when unpacking aborts, and the
5914 ones already unpacked will fail to configure in the recovery phase
5915 because its dependencies are unavailable.&lt;/p&gt;
5916
5917 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
5918
5919 &lt;blockquote&gt;&lt;pre&gt;
5920 dpkg: dependency problems prevent configuration of perl-modules:
5921 perl-modules depends on perl (&gt;= 5.10.1-1); however:
5922 Version of perl on system is 5.10.0-19lenny2.
5923 dpkg: error processing perl-modules (--configure):
5924 dependency problems - leaving unconfigured
5925 &lt;/pre&gt;&lt;/blockquote&gt;
5926
5927 &lt;p&gt;The perl/perl-modules circular dependency is already
5928 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
5929 hopefully be solved as soon as possible, but it is not the only one,
5930 and each one of these loops in the dependency tree can cause similar
5931 failures. Of course, they only occur when there are bugs in other
5932 packages causing the unpacking to fail, but it is rather nasty when
5933 the failure of one package causes the problem to become worse because
5934 of dependency loops.&lt;/p&gt;
5935
5936 &lt;p&gt;Thanks to
5937 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
5938 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
5939 dependencies
5940 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
5941 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
5942
5943 &lt;p&gt;Todays testing also exposed a bug in
5944 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
5945 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
5946 apt-get and aptitude, the latter possibly caused by some circular
5947 dependency. Reported both to BTS to try to get someone to look at
5948 it.&lt;/p&gt;
5949 </description>
5950 </item>
5951
5952 <item>
5953 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
5954 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
5955 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
5956 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
5957 <description>&lt;p&gt;This is a
5958 &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;
5959 on my
5960 &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
5961 work&lt;/a&gt; on
5962 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
5963 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
5964
5965 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
5966 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5967 and dhcp3-server-ldap in Debian use the LDAP server. The two
5968 implementations are quite different in how they use LDAP.&lt;/p&gt;
5969
5970 To get this information, I started slapd with debugging enabled and
5971 dumped the debug output to a file to get the LDAP searches performed
5972 on a Debian Edu main-server. Here is a summary.
5973
5974 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
5975
5976 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
5977 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
5978 the web.
5979
5980 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
5981 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
5982 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
5983 reverse entries are in two different subtrees in LDAP with a structure
5984 based on the DNS names, as in tjener.intern and
5985 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5986
5987 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5988 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5989 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5990 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5991 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5992 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5993 forward entries, it is looking for attributes named dnsttl, arecord,
5994 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5995 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5996 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5997 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5998 spfrecord and modifytimestamp. For reverse entries it is looking for
5999 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6000 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6001 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6002 ldapsearch commands could look like this:&lt;/p&gt;
6003
6004 &lt;blockquote&gt;&lt;pre&gt;
6005 ldapsearch -h ldap \
6006 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6007 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6008 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6009 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6010 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6011 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6012
6013 ldapsearch -h ldap \
6014 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6015 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6016 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6017 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6018 srvrecord naptrrecord modifytimestamp
6019 &lt;/pre&gt;&lt;/blockquote&gt;
6020
6021 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6022 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6023 example LDAP objects used there. In addition to these objects, the
6024 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6025 also exist.&lt;/p&gt;
6026
6027 &lt;blockquote&gt;&lt;pre&gt;
6028 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6029 objectclass: top
6030 objectclass: dnsdomain
6031 objectclass: domainrelatedobject
6032 dc: tjener
6033 arecord: 10.0.2.2
6034 associateddomain: tjener.intern
6035
6036 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6037 objectclass: top
6038 objectclass: dnsdomain2
6039 objectclass: domainrelatedobject
6040 dc: 2
6041 ptrrecord: tjener.intern
6042 associateddomain: 2.2.0.10.in-addr.arpa
6043 &lt;/pre&gt;&lt;/blockquote&gt;
6044
6045 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6046 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6047 same base as in the tree mode for a object with filter
6048 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6049 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6050 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6051 naptrrecord and modifytimestamp. For reverse entires it also do a
6052 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6053 and the requested attributes are associateddomain, dnsttl and
6054 modifytimestamp. In short, in strict mode the objects with ptrrecord
6055 go away, and the arecord attribute in the forward object is used
6056 instead.&lt;/p&gt;
6057
6058 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6059 like this:&lt;/p&gt;
6060
6061 &lt;blockquote&gt;&lt;pre&gt;
6062 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6063 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6064 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6065 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6066 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6067 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6068
6069 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6070 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6071 &lt;/pre&gt;&lt;/blockquote&gt;
6072
6073 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6074 search for SOA records, which behave similar to the forward and
6075 reverse lookups.&lt;/p&gt;
6076
6077 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6078 specify any objectclass names, and instead look for the attributes it
6079 need to generate a DNS reply. This make it able to work with any
6080 objectclass that provide the needed attributes.&lt;/p&gt;
6081
6082 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6083 dnsdomain2 schemas. The latter is used for reverse entries like
6084 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6085
6086 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6087 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6088 attributes) and domainrelatedobject (for associatedDomain). The use
6089 of structural object classes make it impossible to combine these
6090 classes with the object classes used by DHCP.&lt;/p&gt;
6091
6092 &lt;p&gt;There are other schemas that could be used too, for example the
6093 dnszone structural object class used by Gosa and bind-sdb for the DNS
6094 attributes combined with the domainrelatedobject object class, but in
6095 this case some unused attributes would have to be included as well
6096 (zonename and relativedomainname).&lt;/p&gt;
6097
6098 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6099 mode and not use any of the existing objectclasses (dnsdomain,
6100 dnsdomain2 and dnszone) when one want to combine the DNS information
6101 with DHCP information, and instead create a auxiliary object class
6102 defined something like this (using the attributes defined for
6103 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6104
6105 &lt;blockquote&gt;&lt;pre&gt;
6106 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6107 SUP top
6108 AUXILIARY
6109 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6110 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6111 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6112 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6113 A6Record $ DNAMERecord
6114 ))
6115 &lt;/pre&gt;&lt;/blockquote&gt;
6116
6117 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6118 the domainrelatedobject object class, and allow any entity to include
6119 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6120 developers asking for their view on this schema and if they are
6121 interested in providing such schema with PowerDNS, and I hope my
6122 message will be accepted into their mailing list soon.&lt;/p&gt;
6123
6124 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6125
6126 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6127 the object attributes, and then uses the attributes it want. This
6128 make it harder to figure out exactly what attributes are used, but
6129 thanks to the working example in Debian Edu I can at least get an idea
6130 what is needed without having to read the source code.&lt;/p&gt;
6131
6132 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6133 search filter to use to locate the correct dhcpServer entity is
6134 stored. These are the relevant entries from
6135 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6136
6137 &lt;blockquote&gt;&lt;pre&gt;
6138 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6139 ldap-dhcp-server-cn &quot;dhcp&quot;;
6140 &lt;/pre&gt;&lt;/blockquote&gt;
6141
6142 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6143 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6144 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6145 search result is this entry:&lt;/p&gt;
6146
6147 &lt;blockquote&gt;&lt;pre&gt;
6148 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6149 cn: dhcp
6150 objectClass: top
6151 objectClass: dhcpServer
6152 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6153 &lt;/pre&gt;&lt;/blockquote&gt;
6154
6155 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6156 subtree with DHCP configuration. The DHCP configuration subtree base
6157 is located using a base scope search with base &quot;cn=DHCP
6158 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6159 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6160 The search result is this entry:&lt;/p&gt;
6161
6162 &lt;blockquote&gt;&lt;pre&gt;
6163 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6164 cn: DHCP Config
6165 objectClass: top
6166 objectClass: dhcpService
6167 objectClass: dhcpOptions
6168 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6169 dhcpStatements: ddns-update-style none
6170 dhcpStatements: authoritative
6171 dhcpOption: smtp-server code 69 = array of ip-address
6172 dhcpOption: www-server code 72 = array of ip-address
6173 dhcpOption: wpad-url code 252 = text
6174 &lt;/pre&gt;&lt;/blockquote&gt;
6175
6176 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6177 all the DHCP configuration is loaded, it is ready to receive requests.
6178 The subtree in Debian Edu contain objects with object classes
6179 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6180 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6181 and information about netmasks, dynamic range etc. Leaving out the
6182 details here because it is not relevant for the focus of my
6183 investigation, which is to see if it is possible to merge dns and dhcp
6184 related computer objects.&lt;/p&gt;
6185
6186 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6187 of the client (00:00:00:00:00:00 in this example), using a subtree
6188 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6189 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6190 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6191 like:&lt;/p&gt;
6192
6193 &lt;blockquote&gt;&lt;pre&gt;
6194 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6195 cn: hostname
6196 objectClass: top
6197 objectClass: dhcpHost
6198 dhcpHWAddress: ethernet 00:00:00:00:00:00
6199 dhcpStatements: fixed-address hostname
6200 &lt;/pre&gt;&lt;/blockquote&gt;
6201
6202 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6203 The object classes need to have fixed names, and the configuration
6204 need to be stored in a fairly specific LDAP structure. On the
6205 positive side, the invidiual dhcpHost entires can be anywhere without
6206 the DN pointed to by the dhcpServer entries. The latter should make
6207 it possible to group all host entries in a subtree next to the
6208 configuration entries, and this subtree can also be shared with the
6209 DNS server if the schema proposed above is combined with the dhcpHost
6210 structural object class.
6211
6212 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6213
6214 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6215 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6216 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6217 allowing DNS objects to be stored anywhere under the base cn specified
6218 in the configuration.&lt;/p&gt;
6219
6220 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6221 regarding which LDAP schemas to use and which LDAP structure to use.
6222 I guess one could implement ones own schema, as long as the
6223 objectclasses and attributes have the names used, but this do not
6224 really help when the DHCP subtree need to have a fairly fixed
6225 structure.&lt;/p&gt;
6226
6227 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6228 this might work for Debian Edu:&lt;/p&gt;
6229
6230 &lt;blockquote&gt;&lt;pre&gt;
6231 ou=services
6232 cn=machine-info (dhcpService) - dhcpServiceDN points here
6233 cn=dhcp (dhcpServer)
6234 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6235 cn=10.0.2.0 (dhcpSubnet)
6236 cn=group1 (dhcpGroup/dhcpOptions)
6237 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6238 cn=192.168.0.0 (dhcpSubnet)
6239 cn=group1 (dhcpGroup/dhcpOptions)
6240 ou=machines - PowerDNS base points here
6241 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6242 &lt;/pre&gt;&lt;/blockquote&gt;
6243
6244 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6245 entries to be in the dhcpGroup subtrees, the entries can be stored
6246 there instead of a common machines subtree, and the PowerDNS base
6247 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6248
6249 &lt;p&gt;The combined object under the machines subtree would look something
6250 like this:&lt;/p&gt;
6251
6252 &lt;blockquote&gt;&lt;pre&gt;
6253 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6254 dc: hostname
6255 objectClass: top
6256 objectClass: dhcpHost
6257 objectclass: domainrelatedobject
6258 objectclass: dnsDomainAux
6259 associateddomain: hostname.intern
6260 arecord: 10.11.12.13
6261 dhcpHWAddress: ethernet 00:00:00:00:00:00
6262 dhcpStatements: fixed-address hostname.intern
6263 &lt;/pre&gt;&lt;/blockquote&gt;
6264
6265 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6266 machine, as long as the required attributes are available in a
6267 auxiliary object class.&lt;/p&gt;
6268 </description>
6269 </item>
6270
6271 <item>
6272 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6273 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6274 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6275 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6276 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6277 DHCP services in Debian Edu to use the same LDAP objects for a given
6278 computer, to avoid the possibility of having a inconsistent state for
6279 a computer in LDAP (as in DHCP but no DNS entry or the other way
6280 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6281
6282 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6283 information finally found a solution that seem to work.&lt;/p&gt;
6284
6285 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6286 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6287 we switch powerdns to use its strict LDAP method (ldap-method=strict
6288 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6289 merged into one while making it impossible to transfer the reverse map
6290 to a slave DNS server.&lt;/p&gt;
6291
6292 &lt;p&gt;If we also replace the object class used to get the DNS related
6293 attributes to one allowing these attributes to be combined with the
6294 dhcphost object class, we can merge the DNS and DHCP entries into one.
6295 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6296 proper OIDs, but that is a minor issue), and tested the setup. It
6297 seem to work.&lt;/p&gt;
6298
6299 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6300 for both DNS and DHCP, and even the LTSP configuration I suggested in
6301 an earlier email. The combined LDAP object will look something like
6302 this:&lt;/p&gt;
6303
6304 &lt;blockquote&gt;&lt;pre&gt;
6305 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6306 cn: hostname
6307 objectClass: dhcphost
6308 objectclass: domainrelatedobject
6309 objectclass: dnsdomainaux
6310 associateddomain: hostname.intern
6311 arecord: 10.11.12.13
6312 dhcphwaddress: ethernet 00:00:00:00:00:00
6313 dhcpstatements: fixed-address hostname
6314 ldapconfigsound: Y
6315 &lt;/pre&gt;&lt;/blockquote&gt;
6316
6317 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6318 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6319 before asking DNS to resolve the fixed-adddress. LTSP will use
6320 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6321
6322 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6323 dhcphost in a different location, to allow us to put the objects
6324 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6325 that. If I can&#39;t figure out a way to do that, we can still get rid of
6326 the hosts subtree and move all its content into the DHCP Config tree
6327 (which probably should be renamed to be more related to the new
6328 content. I suspect cn=dnsdhcp,ou=services or something like that
6329 might be a good place to put it.&lt;/p&gt;
6330
6331 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6332 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6333 </description>
6334 </item>
6335
6336 <item>
6337 <title>Idea for storing LTSP configuration in LDAP</title>
6338 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6339 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6340 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6341 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6342 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6343 clients, and that this can be used to fetch configuration from LDAP if
6344 Debian Edu choose to store configuration there.&lt;/p&gt;
6345
6346 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6347 to get configuration from LDAP. The idea is to look up the MAC
6348 address of the client in LDAP, and look for attributes on the form
6349 ltspconfigsetting=value, and use this to export SETTING=value to the
6350 LTSP clients.&lt;/p&gt;
6351
6352 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6353 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6354 allowing us to store all information about a computer in one place.&lt;/p&gt;
6355
6356 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6357 this approach. A real LDAP schema for the ltspClientAux objectclass
6358 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6359
6360 &lt;blockquote&gt;&lt;pre&gt;
6361 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6362 #
6363 # Fetch LTSP client settings from LDAP based on MAC address
6364 #
6365 # Uses ethernet address as stored in the dhcpHost objectclass using
6366 # the dhcpHWAddress attribute or ethernet address stored in the
6367 # ieee802Device objectclass with the macAddress attribute.
6368 #
6369 # This module is written to be schema agnostic, and only depend on the
6370 # existence of attribute names.
6371 #
6372 # The LTSP configuration variables are saved directly using a
6373 # ltspConfig prefix and uppercasing the rest of the attribute name.
6374 # To set the SERVER variable, set the ltspConfigServer attribute.
6375 #
6376 # Some LDAP schema should be created with all the relevant
6377 # configuration settings. Something like this should work:
6378 #
6379 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6380 # SUP top
6381 # AUXILIARY
6382 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6383
6384 LDAPSERVER=$(debian-edu-ldapserver)
6385 if [ &quot;$LDAPSERVER&quot; ] ; then
6386 LDAPBASE=$(debian-edu-ldapserver -b)
6387 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6388 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6389 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6390 grep &#39;^ltspConfig&#39; | while read attr value ; do
6391 # Remove prefix and convert to upper case
6392 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6393 # bass value on to clients
6394 eval &quot;$attr=$value; export $attr&quot;
6395 done
6396 done
6397 fi
6398 &lt;/pre&gt;&lt;/blockquote&gt;
6399
6400 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6401 the while block might end up in a subshell causing the variables set
6402 there to not show up in ltsp-config, but if that is the case I am sure
6403 the code can be restructured to make sure the variables are passed on.
6404 I expect that can be solved with some testing. :)&lt;/p&gt;
6405
6406 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6407 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6408
6409 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6410 configuration in LDAP that was created around year 2000 by
6411 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6412 Xperience, Inc., 2000&lt;/a&gt;. I found its
6413 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6414 personal home page over at redhat.com.&lt;/p&gt;
6415 </description>
6416 </item>
6417
6418 <item>
6419 <title>jXplorer, a very nice LDAP GUI</title>
6420 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6421 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6422 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6423 <description>&lt;p&gt;Since
6424 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6425 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6426 LDAP GUI that is even better than luma. The java application
6427 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6428 moving LDAP objects and subtrees using drag-and-drop, and can
6429 authenticate using Kerberos. I have only tested the Kerberos
6430 authentication, but do not have a LDAP setup allowing me to rewrite
6431 LDAP with my test user yet. It is
6432 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6433 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6434 have with it is how it handle errors. If something go wrong, its
6435 non-intuitive behaviour require me to go through some query work list
6436 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6437 </description>
6438 </item>
6439
6440 <item>
6441 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6442 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6443 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6444 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6445 <description>&lt;p&gt;Here is a short update on my &lt;a
6446 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6447 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6448 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6449 not reporting the status for KDE, because the upgrade crashes when
6450 aptitude try because of missing conflicts
6451 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6452 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6453
6454 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6455 complete list of the installed packages. Based on this I see these
6456 differences when I did a test run today. As usual, I do not really
6457 know what the correct set of packages would be, but thought it best to
6458 publish the difference.&lt;/p&gt;
6459
6460 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6461
6462 &lt;blockquote&gt;&lt;p&gt;
6463 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6464 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6465 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6466 libgtksourceview-common libpt-1.10.10-plugins-alsa
6467 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6468 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6469 python-4suite-xml python-eggtrayicon python-gtkhtml2
6470 python-gtkmozembed svgalibg1 xserver-xephyr zip
6471 &lt;/p&gt;&lt;/blockquote&gt;
6472
6473 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6474
6475 &lt;blockquote&gt;&lt;p&gt;
6476 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6477 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6478 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6479 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6480 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6481 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6482 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6483 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6484 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6485 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6486 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6487 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6488 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6489 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6490 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6491 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6492 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6493 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6494 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6495 mysql-common swfdec-gnome totem-gstreamer wodim
6496 &lt;/p&gt;&lt;/blockquote&gt;
6497
6498 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6499
6500 &lt;blockquote&gt;&lt;p&gt;
6501 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6502 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6503 xserver-xorg-input-all xserver-xorg-input-evdev
6504 xserver-xorg-input-kbd xserver-xorg-input-mouse
6505 xserver-xorg-input-synaptics xserver-xorg-video-all
6506 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6507 xserver-xorg-video-chips xserver-xorg-video-cirrus
6508 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6509 xserver-xorg-video-glint xserver-xorg-video-i128
6510 xserver-xorg-video-i740 xserver-xorg-video-mach64
6511 xserver-xorg-video-mga xserver-xorg-video-neomagic
6512 xserver-xorg-video-nouveau xserver-xorg-video-nv
6513 xserver-xorg-video-r128 xserver-xorg-video-radeon
6514 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6515 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6516 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6517 xserver-xorg-video-sis xserver-xorg-video-sisusb
6518 xserver-xorg-video-tdfx xserver-xorg-video-tga
6519 xserver-xorg-video-trident xserver-xorg-video-tseng
6520 xserver-xorg-video-vesa xserver-xorg-video-vmware
6521 xserver-xorg-video-voodoo
6522 &lt;/p&gt;&lt;/blockquote&gt;
6523
6524 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6525
6526 &lt;blockquote&gt;&lt;p&gt;
6527 deskbar-applet xserver-xorg xserver-xorg-core
6528 xserver-xorg-input-wacom xserver-xorg-video-intel
6529 xserver-xorg-video-openchrome
6530 &lt;/p&gt;&lt;/blockquote&gt;
6531
6532 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6533 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6534 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6535 No idea when it hits Squeeze, but when it does I hope it will reduce
6536 the difference somewhat.
6537 </description>
6538 </item>
6539
6540 <item>
6541 <title>LUMA, a very nice LDAP GUI</title>
6542 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6543 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6544 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6545 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6546 directory in Debian Edu, and in the process I started to miss a GUI
6547 tool to browse the LDAP tree. The only one I was able to find in
6548 Debian/Squeeze and Lenny is
6549 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6550 be a great tool to get a overview of the current LDAP directory
6551 populated by default in Skolelinux. Thanks to it, I have been able to
6552 find empty and obsolete subtrees, misplaced objects and duplicate
6553 objects. It will be installed by default in Debian/Squeeze. If you
6554 are working with LDAP, give it a go. :)&lt;/p&gt;
6555
6556 &lt;p&gt;I did notice one problem with it I have not had time to report to
6557 the BTS yet. There is no .desktop file in the package, so the tool do
6558 not show up in the Gnome and KDE menus, but only deep down in in the
6559 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6560 released.&lt;/p&gt;
6561
6562 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6563 like to move objects and remove subtrees directly in the GUI, but have
6564 not found a way to do that with LUMA yet. So in the mean time, I use
6565 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6566
6567 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6568 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6569
6570 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6571 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6572 useful GUI alternative. It seem like a good tool, but is unmaintained
6573 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6574 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6575 </description>
6576 </item>
6577
6578 <item>
6579 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6580 <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>
6581 <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>
6582 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6583 <description>&lt;p&gt;A while back, I
6584 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6585 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6586 for storing DNS and DHCP information in LDAP to combine the two sets
6587 of information into one LDAP object representing a computer.&lt;/p&gt;
6588
6589 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6590 the dhcpHost object class auxiliary, to allow it to be combined with
6591 the dNSDomain object class, and thus forming one object for one
6592 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6593
6594 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6595 without also changing the assigned number for the object class, and I
6596 do not know enough about LDAP schema design to do that properly for
6597 Debian Edu.&lt;/p&gt;
6598
6599 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6600 the
6601 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6602 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6603 available today from IETF.&lt;/p&gt;
6604
6605 &lt;pre&gt;
6606 --- dhcp.schema (revision 65192)
6607 +++ dhcp.schema (working copy)
6608 @@ -376,7 +376,7 @@
6609 objectclass ( 2.16.840.1.113719.1.203.6.6
6610 NAME &#39;dhcpHost&#39;
6611 DESC &#39;This represents information about a particular client&#39;
6612 - SUP top
6613 + SUP top AUXILIARY
6614 MUST cn
6615 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6616 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6617 &lt;/pre&gt;
6618
6619 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6620 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6621 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6622
6623 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6624 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6625 </description>
6626 </item>
6627
6628 <item>
6629 <title>Calling tasksel like the installer, while still getting useful output</title>
6630 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6631 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6632 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6633 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6634 installs packages during the normal debian-installer run. Until now,
6635 I have ended up letting tasksel do the work, with the annoying problem
6636 of not getting any feedback at all when something fails (like a
6637 conffile question from dpkg or a download that fails), using code like
6638 this:
6639
6640 &lt;blockquote&gt;&lt;pre&gt;
6641 export DEBIAN_FRONTEND=noninteractive
6642 tasksel --new-install
6643 &lt;/pre&gt;&lt;/blockquote&gt;
6644
6645 This would invoke tasksel, let its automatic task selection pick the
6646 tasks to install, and continue to install the requested tasks without
6647 any output what so ever.
6648
6649 Recently I revisited this problem while working on the automatic
6650 package upgrade testing, because tasksel would some times hang without
6651 any useful feedback, and I want to see what is going on when it
6652 happen. Then it occured to me, I can parse the output from tasksel
6653 when asked to run in test mode, and use that aptitude command line
6654 printed by tasksel then to simulate the tasksel run. I ended up using
6655 code like this:
6656
6657 &lt;blockquote&gt;&lt;pre&gt;
6658 export DEBIAN_FRONTEND=noninteractive
6659 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6660 $cmd
6661 &lt;/pre&gt;&lt;/blockquote&gt;
6662
6663 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6664 --without-recommends -o APT::Install-Recommends=no -y install
6665 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6666 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6667 laptop task and all packages with priority standard , required and
6668 important, just like tasksel would have done it during
6669 installation.&lt;/p&gt;
6670
6671 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6672 install packages without using debconf-apt-progress, for use cases
6673 like this.&lt;/p&gt;
6674 </description>
6675 </item>
6676
6677 <item>
6678 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6679 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6680 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6681 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6682 <description>&lt;p&gt;My
6683 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6684 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6685 finally made the upgrade logs available from
6686 &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;.
6687 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6688 apt and aptitude, and found their differences interesting. This time
6689 I will only focus on their removal plans.&lt;/p&gt;
6690
6691 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6692 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6693 surprising part is that it want to remove xorg and all
6694 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6695 sure why. When asking aptitude to do the same, it want to remove 129
6696 packages, but most of them are library packages I suspect are no
6697 longer needed. Both of them want to remove bluetooth packages, which
6698 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6699
6700 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6701 which seem like a bad idea and xorg the same way as with Gnome. Asking
6702 aptitude for the same, it wants to remove 192 packages, none which are
6703 too surprising.&lt;/p&gt;
6704
6705 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6706 and avoided, and perhaps others as well. Here are the complete list
6707 of planned removals. The complete logs is available from the URL
6708 above. Note if you want to repeat these tests, that the upgrade test
6709 for kde+apt-get hung in the tasksel setup because of dpkg asking
6710 conffile questions. No idea why. I worked around it by using
6711 &#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
6712 continue.&lt;/p&gt;
6713
6714 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6715 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6716 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6717 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6718 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6719 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6720 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6721 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6722 xserver-xorg-input-kbd xserver-xorg-input-mouse
6723 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6724 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6725 xserver-xorg-video-ati xserver-xorg-video-chips
6726 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6727 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6728 xserver-xorg-video-glint xserver-xorg-video-i128
6729 xserver-xorg-video-i740 xserver-xorg-video-imstt
6730 xserver-xorg-video-intel xserver-xorg-video-mach64
6731 xserver-xorg-video-mga xserver-xorg-video-neomagic
6732 xserver-xorg-video-nsc xserver-xorg-video-nv
6733 xserver-xorg-video-openchrome xserver-xorg-video-r128
6734 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6735 xserver-xorg-video-rendition xserver-xorg-video-s3
6736 xserver-xorg-video-s3virge xserver-xorg-video-savage
6737 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6738 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6739 xserver-xorg-video-tga xserver-xorg-video-trident
6740 xserver-xorg-video-tseng xserver-xorg-video-v4l
6741 xserver-xorg-video-vesa xserver-xorg-video-vga
6742 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6743 xulrunner-1.9-gnome-support&lt;/p&gt;
6744
6745 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6746
6747 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6748 djvulibre-desktop finger gnome-app-install gnome-mount
6749 gnome-network-admin gnome-spell gnome-vfs-obexftp
6750 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6751 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6752 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6753 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6754 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6755 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6756 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6757 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6758 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6759 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6760 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6761 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6762 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6763 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6764 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6765 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6766 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6767 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6768 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6769 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6770 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6771 openoffice.org-writer2latex openssl-blacklist p7zip
6772 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6773 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6774 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6775 swfdec-mozilla totem-gstreamer update-manager wodim
6776 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6777 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6778 zip&lt;/p&gt;
6779
6780 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6781
6782 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6783 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6784 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6785 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6786 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6787 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6788 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6789 xserver-xorg-input-kbd xserver-xorg-input-mouse
6790 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6791 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6792 xserver-xorg-video-ati xserver-xorg-video-chips
6793 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6794 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6795 xserver-xorg-video-glint xserver-xorg-video-i128
6796 xserver-xorg-video-i740 xserver-xorg-video-imstt
6797 xserver-xorg-video-intel xserver-xorg-video-mach64
6798 xserver-xorg-video-mga xserver-xorg-video-neomagic
6799 xserver-xorg-video-nsc xserver-xorg-video-nv
6800 xserver-xorg-video-openchrome xserver-xorg-video-r128
6801 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6802 xserver-xorg-video-rendition xserver-xorg-video-s3
6803 xserver-xorg-video-s3virge xserver-xorg-video-savage
6804 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6805 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6806 xserver-xorg-video-tga xserver-xorg-video-trident
6807 xserver-xorg-video-tseng xserver-xorg-video-v4l
6808 xserver-xorg-video-vesa xserver-xorg-video-vga
6809 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6810
6811 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6812 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6813 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6814 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6815 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6816 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6817 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6818 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6819 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6820 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6821 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6822 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6823 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6824 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6825 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6826 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6827 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6828 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6829 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6830 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6831 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6832 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6833 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6834 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6835 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6836 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6837 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6838 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6839 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6840 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6841 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6842 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6843 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6844 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6845 texlive-common texlive-doc-base texlive-fonts-recommended
6846 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6847 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6848 xulrunner-1.9&lt;/p&gt;
6849
6850 </description>
6851 </item>
6852
6853 <item>
6854 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6855 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6856 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6857 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6858 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6859 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6860 have been discovered and reported in the process
6861 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6862 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6863 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6864 kdebase-workspace-data), and to get a more regular testing going on, I
6865 am working on a script to automate the test.&lt;/p&gt;
6866
6867 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6868 Gnome or KDE desktop installation inside the chroot before upgrading
6869 it. To ensure no services are started in the chroot, a policy-rc.d
6870 script is inserted. To make sure tasksel believe it is to install a
6871 desktop on a laptop, the tasksel tests are replaced in the chroot
6872 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
6873
6874 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6875 currently always fail because udev refuses to upgrade with the kernel
6876 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6877 is created. The bug report
6878 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
6879 this problem do not trigger in a chroot, but I touch the file anyway
6880 to make sure the upgrade go well. Testing on virtual and real
6881 hardware have failed me because of udev so far, and creating this file
6882 do the trick in such settings anyway. This is a
6883 &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
6884 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
6885 maintainer because he lack the resources to rewrite udev to keep
6886 working with old kernels or something like that. I really wish the
6887 udev upstream would keep udev backwards compatible, to avoid such
6888 upgrade problem, but given that they fail to do so, I guess
6889 documenting the way out of this mess is the best option we got for
6890 Debian Squeeze.&lt;/p&gt;
6891
6892 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
6893 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
6894 trick:&lt;/p&gt;
6895
6896 &lt;blockquote&gt;&lt;pre&gt;
6897 #!/bin/sh
6898 set -ex
6899
6900 if [ &quot;$1&quot; ] ; then
6901 desktop=$1
6902 else
6903 desktop=gnome
6904 fi
6905
6906 from=lenny
6907 to=squeeze
6908
6909 exec &amp;lt; /dev/null
6910 unset LANG
6911 mirror=http://ftp.skolelinux.org/debian
6912 tmpdir=chroot-$from-upgrade-$to-$desktop
6913 fuser -mv .
6914 debootstrap $from $tmpdir $mirror
6915 chroot $tmpdir aptitude update
6916 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
6917 #!/bin/sh
6918 exit 101
6919 EOF
6920 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6921 exit_cleanup() {
6922 umount $tmpdir/proc
6923 }
6924 mount -t proc proc $tmpdir/proc
6925 # Make sure proc is unmounted also on failure
6926 trap exit_cleanup EXIT INT
6927
6928 chroot $tmpdir aptitude -y install debconf-utils
6929
6930 # Make sure tasksel autoselection trigger. It need the test scripts
6931 # to return the correct answers.
6932 echo tasksel tasksel/desktop multiselect $desktop | \
6933 chroot $tmpdir debconf-set-selections
6934
6935 # Include the desktop and laptop task
6936 for test in desktop laptop ; do
6937 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
6938 #!/bin/sh
6939 exit 2
6940 EOF
6941 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6942 done
6943
6944 DEBIAN_FRONTEND=noninteractive
6945 DEBIAN_PRIORITY=critical
6946 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6947 chroot $tmpdir tasksel --new-install
6948
6949 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
6950 chroot $tmpdir aptitude update
6951 touch $tmpdir/etc/udev/kernel-upgrade
6952 chroot $tmpdir aptitude -y dist-upgrade
6953 fuser -mv
6954 &lt;/pre&gt;&lt;/blockquote&gt;
6955
6956 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
6957 with aptitude, but I have not had time to look at how they behave
6958 differently so far. I hope to get a cron job running to do the test
6959 regularly and post the result on the web. The Gnome upgrade currently
6960 work, while the KDE upgrade fail because of the bug in
6961 kdebase-workspace-data&lt;/p&gt;
6962
6963 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
6964 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
6965 post, so I will refrain from trying. I can report that for Gnome,
6966 aptitude report 760 packages upgraded, 448 newly installed, 129 to
6967 remove and 1 not upgraded and 1024MB need to be downloaded while for
6968 KDE the same numbers are 702 packages upgraded, 507 newly installed,
6969 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
6970
6971 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
6972 is able to migrate to dependency based boot sequencing and parallel
6973 booting without a hitch. Was unsure if there were still bugs with
6974 packages failing to clean up their obsolete init.d script during
6975 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6976 packages.&lt;/p&gt;
6977 </description>
6978 </item>
6979
6980 <item>
6981 <title>Upstart or sysvinit - as init.d scripts see it</title>
6982 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
6983 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
6984 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
6985 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6986 scripts to migrate (some of) their operations to upstart job while
6987 keeping the init.d for hurd and kfreebsd. The packages with such
6988 needs will need a way to get their init.d scripts to behave
6989 differently when used with sysvinit and with upstart. Because of
6990 this, I had a look at the environment variables set when a init.d
6991 script is running under upstart, and when it is not.&lt;/p&gt;
6992
6993 &lt;p&gt;With upstart, I notice these environment variables are set when a
6994 script is started from rcS.d/ (ignoring some irrelevant ones like
6995 COLUMNS):&lt;/p&gt;
6996
6997 &lt;blockquote&gt;&lt;pre&gt;
6998 DEFAULT_RUNLEVEL=2
6999 previous=N
7000 PREVLEVEL=
7001 RUNLEVEL=
7002 runlevel=S
7003 UPSTART_EVENTS=startup
7004 UPSTART_INSTANCE=
7005 UPSTART_JOB=rc-sysinit
7006 &lt;/pre&gt;&lt;/blockquote&gt;
7007
7008 &lt;p&gt;With sysvinit, these environment variables are set for the same
7009 script.&lt;/p&gt;
7010
7011 &lt;blockquote&gt;&lt;pre&gt;
7012 INIT_VERSION=sysvinit-2.88
7013 previous=N
7014 PREVLEVEL=N
7015 RUNLEVEL=S
7016 runlevel=S
7017 &lt;/pre&gt;&lt;/blockquote&gt;
7018
7019 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7020 sysvinit are not set by upstart. Not sure if it is intentional or not
7021 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7022
7023 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7024 looking for the UPSTART_JOB environment variable seem to be a good
7025 choice.&lt;/p&gt;
7026 </description>
7027 </item>
7028
7029 <item>
7030 <title>A manual for standards wars...</title>
7031 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7032 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7033 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7034 <description>&lt;p&gt;Via the
7035 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7036 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7037 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7038 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7039 following the standards wars of today.&lt;/p&gt;
7040 </description>
7041 </item>
7042
7043 <item>
7044 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7045 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7047 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7048 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7049 to get a list of the machine types in use thanks to the DMI
7050 information extracted from each machine. The script to do so is
7051 included in the sitesummary package, and here is example output from
7052 the Skolelinux build servers:&lt;/p&gt;
7053
7054 &lt;blockquote&gt;&lt;pre&gt;
7055 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7056 vendor count
7057 Dell Computer Corporation 1
7058 PowerEdge 1750 1
7059 IBM 1
7060 eserver xSeries 345 -[8670M1X]- 1
7061 Intel 2
7062 [no-dmi-info] 3
7063 maintainer:~#
7064 &lt;/pre&gt;&lt;/blockquote&gt;
7065
7066 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7067 provided in each machine. Here there are Intel machines without model
7068 information listed with Intel as vendor and no model, and virtual Xen
7069 machines listed as [no-dmi-info]. One can add -l as a command line
7070 option to list the individual machines.&lt;/p&gt;
7071
7072 &lt;p&gt;A larger list is
7073 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7074 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7075 provide the basic sitesummary report publicly. In their report there
7076 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7077 their machines, and as sitesummary is available in both distributions,
7078 it is trivial to get all of them to report to the same central
7079 collector.&lt;/p&gt;
7080 </description>
7081 </item>
7082
7083 <item>
7084 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7085 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7086 <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>
7087 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7088 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7089 start at boot when an NVidia video card is used is handled. The
7090 problem seem to be that the nvidia X.org driver uses a long time to
7091 initialize, and this duration is longer than kdm is configured to
7092 wait.&lt;/p&gt;
7093
7094 &lt;p&gt;I came across two bugs related to this issue,
7095 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7096 against initscripts and passed on to nvidia-glx when it became obvious
7097 that the nvidia drivers were involved, and
7098 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7099 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7100
7101 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7102 problem nvidia video card owners experience and make sure the Debian
7103 distribution work out of the box for these users. The nvidia driver
7104 maintainers expect kdm to be set up to wait longer, while kdm expect
7105 the nvidia driver maintainers to fix the driver to start faster, and
7106 while they wait for each other I guess the users end up switching to a
7107 distribution that work for them. I have no idea what the solution is,
7108 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7109
7110 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7111 </description>
7112 </item>
7113
7114 <item>
7115 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7116 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7118 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7119 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7120 The feature seem to hold up pretty well, but three fairly serious
7121 issues are known and should be solved:
7122
7123 &lt;p&gt;&lt;ul&gt;
7124
7125 &lt;li&gt;The wicd package seen to
7126 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7127 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7128 parallel booting is enabled. No idea why, but the wicd maintainer
7129 seem to be on the case.&lt;/li&gt;
7130
7131 &lt;li&gt;The nvidia X driver seem to
7132 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7133 triggered more easily when parallel booting is in effect. The
7134 maintainer is on the case.&lt;/li&gt;
7135
7136 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7137 sequencing (the shutdown is broken) when old file-rc users
7138 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7139 sysv-rc. One way to solve it would be for file-rc to create
7140 /etc/init.d/.legacy-bootordering, and another is to try to make
7141 sysv-rc more robust. Will investigate some more and probably upload a
7142 workaround in sysv-rc to help those trying to move from file-rc to
7143 sysv-rc get a working shutdown.&lt;/li&gt;
7144
7145 &lt;/ul&gt;&lt;/p&gt;
7146
7147 &lt;p&gt;All in all not many surprising issues, and all of them seem
7148 solvable before Squeeze is released. In addition to these there are
7149 some packages with bugs in their dependencies and run level settings,
7150 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7151
7152 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7153 the BTS, please usertag the report to get it to show up at
7154 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7155 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7156
7157 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7158 </description>
7159 </item>
7160
7161 <item>
7162 <title>More flexible firmware handling in debian-installer</title>
7163 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7164 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7165 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7166 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7167 found time today to return to the project. Having to spend less time
7168 working dependency based boot in debian, as it is almost complete now,
7169 definitely helped freeing some time.&lt;/p&gt;
7170
7171 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7172 include some firmware packages on the Debian Edu CDs, those needed to
7173 get disk and network controllers working. Without having these
7174 firmware packages available during installation, it is impossible to
7175 install Debian Edu on the given machine, and because our target group
7176 are non-technical people, asking them to provide firmware packages on
7177 an external medium is a support pain. Initially, I expected it to be
7178 enough to include the firmware packages on the CD to get
7179 debian-installer to find and use them. This proved to be wrong.
7180 Next, I hoped it was enough to symlink the relevant firmware packages
7181 to some useful location on the CD (tried /cdrom/ and
7182 /cdrom/firmware/). This also proved to not work, and at this point I
7183 found time to look at the debian-installer code to figure out what was
7184 going to work.&lt;/p&gt;
7185
7186 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7187 look revealed that it would only look for firmware packages outside
7188 the installation media, so the CD was never checked for firmware
7189 packages. It would only check USB sticks, floppies and other
7190 &quot;external&quot; media devices. Today I changed it to also look in the
7191 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7192 solve the problem I ran into with Debian edu. I also changed it to
7193 look in /firmware/, to make sure the installer also find firmware
7194 provided in the initrd when booting the installer via PXE, to allow us
7195 to provide the same feature in the PXE setup included in Debian
7196 Edu.&lt;/p&gt;
7197
7198 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7199 activated without asking if the license is accepted, I extended
7200 hw-detect to look for preinst scripts in the firmware packages, and
7201 run these before activating the firmware during installation. The
7202 license question is asked using debconf in the preinst, so this should
7203 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7204
7205 &lt;p&gt;If you want to discuss the details of these features, please
7206 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7207 </description>
7208 </item>
7209
7210 <item>
7211 <title>Parallellized boot is now the default in Debian/unstable</title>
7212 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7213 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7214 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7215 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7216 Debian/unstable for machines using dependency based boot sequencing.
7217 Apparently the testing of concurrent booting has been wider than
7218 expected, if I am to believe the
7219 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7220 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7221 with the feature this weekend, to give us some time to detect any
7222 remaining problems before Squeeze is frozen. If serious problems are
7223 detected, it is simple to change the default back to sequential boot.
7224 The upload of the new sysvinit package also activate a new upstream
7225 version.&lt;/p&gt;
7226
7227 More information about
7228 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7229 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7230 currently possible to disable parallel booting when one run into
7231 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7232
7233 &lt;blockquote&gt;&lt;pre&gt;
7234 CONCURRENCY=none
7235 &lt;/pre&gt;&lt;/blockquote&gt;
7236
7237 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7238 the BTS, please usertag the report to get it to show up at
7239 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7240 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7241 </description>
7242 </item>
7243
7244 <item>
7245 <title>Sitesummary tip: Listing MAC address of all clients</title>
7246 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7247 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7248 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7249 <description>&lt;p&gt;In the recent Debian Edu versions, the
7250 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7251 system&lt;/a&gt; is used to keep track of the machines in the school
7252 network. Each machine will automatically report its status to the
7253 central server after boot and once per night. The network setup is
7254 also reported, and using this information it is possible to get the
7255 MAC address of all network interfaces in the machines. This is useful
7256 to update the DHCP configuration.&lt;/p&gt;
7257
7258 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7259 ist all MAC addresses of all machines reporting to sitesummary. Run
7260 this on the collector host:&lt;/p&gt;
7261
7262 &lt;blockquote&gt;&lt;pre&gt;
7263 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7264 &lt;/pre&gt;&lt;/blockquote&gt;
7265
7266 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7267 line per machine and with space between the MAC addresses.&lt;/p&gt;
7268
7269 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7270 addresses for hosts, it would be possible to extend this to fetch
7271 machine information from sitesummary and update the DHCP and DNS
7272 tables in LDAP using this information. Such tool is unfortunately not
7273 written yet.&lt;/p&gt;
7274 </description>
7275 </item>
7276
7277 <item>
7278 <title>systemd, an interesting alternative to upstart</title>
7279 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7280 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7281 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7282 <description>&lt;p&gt;The last few days a new boot system called
7283 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7284 has been
7285 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7286
7287 to the free software world. I have not yet had time to play around
7288 with it, but it seem to be a very interesting alternative to
7289 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7290 a good alternative for Debian when we are able to switch to an event
7291 based boot system. Tollef is
7292 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7293 systemd into Debian, and I look forward to seeing how well it work. I
7294 like the fact that systemd handles init.d scripts with dependency
7295 information natively, allowing them to run in parallel where upstart
7296 at the moment do not.&lt;/p&gt;
7297
7298 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7299 platform support. It only work on recent Linux kernels, and also need
7300 some new kernel features enabled to function properly. This means
7301 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7302 system. Not sure how that will be handled if systemd proves to be the
7303 way forward.&lt;/p&gt;
7304
7305 &lt;p&gt;In the mean time, based on the
7306 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7307 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7308 decided to enable full parallel booting as the default in Debian as
7309 soon as possible (probably this weekend or early next week), to see if
7310 there are any remaining serious bugs in the init.d dependencies. A
7311 new version of the sysvinit package implementing this change is
7312 already in experimental. If all go well, Squeeze will be released
7313 with parallel booting enabled by default.&lt;/p&gt;
7314 </description>
7315 </item>
7316
7317 <item>
7318 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7319 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7320 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7321 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7322 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7323 complete, so complete that it is actually possible to run all the
7324 init.d scripts in parallell based on these dependencies. If you want
7325 to test your Squeeze system, make sure
7326 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7327 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7328 /etc/default/rcS:&lt;/p&gt;
7329
7330 &lt;blockquote&gt;&lt;pre&gt;
7331 CONCURRENCY=makefile
7332 &lt;/pre&gt;&lt;/blockquote&gt;
7333
7334 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7335 scripts in parallel using the dependency information stored in
7336 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7337 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7338 to try to start the kdm and gdm scripts as early as possible, and will
7339 start the facilities required by kdm or gdm as early as possible to
7340 make this happen.&lt;/p&gt;
7341
7342 &lt;p&gt;Give it a try, and see if you like the result. If some services
7343 fail to start properly, it is most likely because they have incomplete
7344 init.d script dependencies in their startup script (or some of their
7345 dependent scripts have incomplete dependencies). Report bugs and get
7346 the package maintainers to fix it. :)&lt;/p&gt;
7347
7348 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7349 manage to get the init.d script dependencies complete and correct. I
7350 expect we will get there in Squeeze+1, if we get manage to test and
7351 fix the remaining issues.&lt;/p&gt;
7352
7353 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7354 the BTS, please usertag the report to get it to show up at
7355 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7356 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7357 </description>
7358 </item>
7359
7360 <item>
7361 <title>Debian has switched to dependency based boot sequencing</title>
7362 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7363 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7364 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7365 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7366 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7367 have been migrated to using dependency based boot sequencing. This
7368 conclude work me and others have been doing for the last three days.
7369 It feels great to see this finally part of the default Debian
7370 installation. Now we just need to weed out the last few problems that
7371 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7372
7373 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7374 fixing the more fundamental problem of handing the event based
7375 non-predictable kernel in the early boot.&lt;/p&gt;
7376 </description>
7377 </item>
7378
7379 <item>
7380 <title>Taking over sysvinit development</title>
7381 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7382 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7383 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7384 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7385 the existing sysvinit upstream developer, I decided a few weeks ago to
7386 take over the package and become the new upstream. The number of
7387 patches to track for the Debian package was becoming a burden, and the
7388 lack of synchronization between the distribution made it hard to keep
7389 the package up to date.&lt;/p&gt;
7390
7391 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7392 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7393 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7394 and Fedora), based on the patches currently in use in these
7395 distributions. We Debian maintainers plan to move to this tarball as
7396 the new upstream as soon as we find time to do the merge. Since the
7397 new tarball was created, we agreed with Werner at SuSe to make a new
7398 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7399 development there. The project is registered and currently waiting
7400 for approval by the Savannah administrators, and as soon as it is
7401 approved, we will import the old versions from svn and continue
7402 working on the future release.&lt;/p&gt;
7403
7404 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7405 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7406 </description>
7407 </item>
7408
7409 <item>
7410 <title>Debian boots quicker and quicker</title>
7411 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7412 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7413 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7414 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7415 people involved in the boot system on Debian and Ubuntu, to see if we
7416 could find more ways to speed up the boot system. This was an Ubuntu
7417 funded
7418 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7419 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7420 of boot systems, and ways to handle the increasing number of boot
7421 issues introduced by the Linux kernel becoming more and more
7422 asynchronous and event base. The Ubuntu approach using udev and
7423 upstart might be a good way forward. Time will show.&lt;/p&gt;
7424
7425 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7426 process in Debian. All of these should be applied to get a quick
7427 boot:&lt;/p&gt;
7428
7429 &lt;ul&gt;
7430
7431 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7432
7433 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7434 clock is in UTC.&lt;/li&gt;
7435
7436 &lt;li&gt;Install and activate the insserv package to enable
7437 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7438 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7439
7440 &lt;/ul&gt;
7441
7442 These points are based on the Google summer of code work done by
7443 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7444 Villegas&lt;/a&gt;.
7445
7446 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7447 unstable yesterday. When we tested it, we were able to cut 6 seconds
7448 from the boot sequence. It depend on very correct dependency
7449 declaration in all init.d scripts, so I expect us to find edge cases
7450 where the dependences in some scripts are slightly wrong when we start
7451 using this.&lt;/p&gt;
7452
7453 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7454 introduced by Raphael Geissert today, one that could affect the
7455 startup speed as well. Instead of starting some scripts concurrently
7456 from rcS.d/ and another set of scripts from rc2.d/, it would be
7457 possible to run a of them in the same process. A quick way to test
7458 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7459 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7460 </description>
7461 </item>
7462
7463 <item>
7464 <title>BSAs påstander om piratkopiering møter motstand</title>
7465 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7466 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7467 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7468 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7469 programvareselskapene som Microsoft og Apple, publisert en rapport der
7470 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7471 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7472 dager siden kom
7473 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7474 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7475 dagene. Et spesielt interessant kommentar fra Sverige,
7476 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7477 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7478
7479 &lt;blockquote&gt;
7480 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7481 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7482 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7483 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7484 &lt;/blockquote&gt;
7485
7486 &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
7487 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7488 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7489 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7490 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7491
7492 &lt;p&gt;Fant lenkene via &lt;a
7493 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7494 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7495 </description>
7496 </item>
7497
7498 <item>
7499 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7500 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7501 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7502 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7503 <description>&lt;p&gt;Kom over
7504 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7505 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7506 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7507 jobber til daglig. En rask opptelling forteller meg at vi har 490
7508 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7509 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7510 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7511 </description>
7512 </item>
7513
7514 <item>
7515 <title>Kryptert harddisk - naturligvis</title>
7516 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7517 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7518 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7519 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7520 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7521 når en tar tap av arbeidstid, fortrolige dokumenter,
7522 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7523 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7524 til at jeg har kryptert harddisken på både kontormaskinen og min
7525 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7526 komme på avveie, den første informasjon relatert til jobben min ved
7527 Universitetet i Oslo, og den andre relatert til blant annet
7528 foreningsarbeide. Kryptering av diskene gjør at det er lite
7529 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7530 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7531 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7532 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7533 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7534 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7535 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7536 det er gjort slik jeg gjør det er minimale, og gevinstene er
7537 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7538 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7539
7540 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7541 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7542 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7543 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7544 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7545 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7546 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7547 betydelige.&lt;/p&gt;
7548 </description>
7549 </item>
7550
7551 <item>
7552 <title>Two projects that have improved the quality of free software a lot</title>
7553 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7554 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7555 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7556 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7557 quality of free software, and I wanted to mention both in case someone
7558 do not yet know them.&lt;/p&gt;
7559
7560 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7561 tool to detect and expose errors in the memory handling of programs.
7562 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7563 and it will report any problems on stdout. It is even better if the
7564 program include debug information. With debug information, it is able
7565 to report the source file name and line number where the problem
7566 occurs. It can report things like &#39;reading past memory block in file
7567 X line N, the memory block was allocated in file Y, line M&#39;, and
7568 &#39;using uninitialised value in control logic&#39;. This tool has made it
7569 trivial to investigate reproducible crash bugs in programs, and have
7570 reduced the number of this kind of bugs in free software a lot.
7571
7572 &lt;p&gt;The second one is
7573 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7574 a source code checker. It is able to process the source of a program
7575 and find problems in the logic without running the program. It
7576 started out as the Stanford Checker and became well known when it was
7577 used to find bugs in the Linux kernel. It is now a commercial tool
7578 and the company behind it is running
7579 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7580 free software community, where a lot of free software projects get
7581 their source checked for free. Several thousand defects have been
7582 found and fixed so far. It can find errors like &#39;lock L taken in file
7583 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7584 Y lines O to P can never be executed&#39;. The projects included in the
7585 community service project have managed to get rid of a lot of
7586 reliability problems thanks to Coverity.&lt;/p&gt;
7587
7588 &lt;p&gt;I believe tools like this, that are able to automatically find
7589 errors in the source, are vital to improve the quality of software and
7590 make sure we can get rid of the crashing and failing software we are
7591 surrounded by today.&lt;/p&gt;
7592 </description>
7593 </item>
7594
7595 <item>
7596 <title>No patch is not better than a useless patch</title>
7597 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7598 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7599 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7600 <description>&lt;p&gt;Julien Blache
7601 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7602 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7603 patch allow one to discuss a concrete and proposed solution, and also
7604 prove that the issue at hand is important enough for someone to spent
7605 time on fixing it. No patch do not provide any of these positive
7606 properties.&lt;/p&gt;
7607 </description>
7608 </item>
7609
7610 <item>
7611 <title>Standardize on protocols and formats, not vendors and applications</title>
7612 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7614 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7615 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7616 very good one to form a long lived computer infrastructure. It is the
7617 simple one, lost by many in todays computer industry: Standardize on
7618 open network protocols and open exchange/storage formats, not applications.
7619 Applications come and go, while protocols and files tend to stay, and
7620 thus one want to make it easy to change application and vendor, while
7621 avoiding conversion costs and locking users to a specific platform or
7622 application.&lt;/p&gt;
7623
7624 &lt;p&gt;This approach make it possible to replace the client applications
7625 independently of the server applications. One can even allow users to
7626 use several different applications as long as they handle the selected
7627 protocol and format. In the normal case, only one client application
7628 is recommended and users only get help if they choose to use this
7629 application, but those that want to deviate from the easy path are not
7630 blocked from doing so.&lt;/p&gt;
7631
7632 &lt;p&gt;It also allow us to replace the server side without forcing the
7633 users to replace their applications, and thus allow us to select the
7634 best server implementation at any moment, when scale and resouce
7635 requirements change.&lt;/p&gt;
7636
7637 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7638 open formats, but I would never recommend standardizing on a single
7639 application that do not use open network protocol or open formats.&lt;/p&gt;
7640 </description>
7641 </item>
7642
7643 <item>
7644 <title>Returning from Skolelinux developer gathering</title>
7645 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7646 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7647 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7648 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7649 Edu/Skolelinux development gathering. I got a bit done tuning the
7650 desktop, and looked into the dynamic service location protocol
7651 implementation avahi. It look like it could be useful for us. Almost
7652 30 people participated, and I believe it was a great environment to
7653 get to know the Skolelinux system. Walter Bender, involved in the
7654 development of the Sugar educational platform, presented his stuff and
7655 also helped me improve my OLPC installation. He also showed me that
7656 his Turtle Art application can be used in standalone mode, and we
7657 agreed that I would help getting it packaged for Debian. As a
7658 standalone application it would be great for Debian Edu. We also
7659 tried to get the video conferencing working with two OLPCs, but that
7660 proved to be too hard for us. The application seem to need more work
7661 before it is ready for me. I look forward to getting home and relax
7662 now. :)&lt;/p&gt;
7663 </description>
7664 </item>
7665
7666 <item>
7667 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7668 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7669 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7670 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7671 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7672 optimal. There is RFC 2307 documenting one way to store NIS maps in
7673 LDAP, and a modified version of this normally called RFC 2307bis, with
7674 some modifications to be compatible with Active Directory. The RFC
7675 specification handle the content of a lot of system databases, but do
7676 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7677
7678 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7679 we would like to store information about users, SMB clients/hosts,
7680 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7681 and LTSP configuration in LDAP. These objects have a lot in common,
7682 but with the current LDAP schemas it is not possible to have one
7683 object per entity. For example, one need to have at least three LDAP
7684 objects for a given computer, one with the SMB related stuff, one with
7685 DNS information and another with DHCP information. The schemas
7686 provided for DNS and DHCP are impossible to combine into one LDAP
7687 object. In addition, it is impossible to implement quick queries for
7688 netgroup membership, because of the way NIS triples are implemented.
7689 It just do not scale. I believe it is time for a few RFC
7690 specifications to cleam up this mess.&lt;/p&gt;
7691
7692 &lt;p&gt;I would like to have one LDAP object representing each computer in
7693 the network, and this object can then keep the SMB (ie host key), DHCP
7694 (mac address/name) and DNS (name/IP address) settings in one place.
7695 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7696
7697 &lt;p&gt;I would also like to have a quick way to map from a user or
7698 computer and to the net group this user or computer is a member.&lt;/p&gt;
7699
7700 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7701 in this regard, and the unix side need to catch up. Time to start a
7702 new IETF work group?&lt;/p&gt;
7703 </description>
7704 </item>
7705
7706 <item>
7707 <title>Endelig er Debian Lenny gitt ut</title>
7708 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7709 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7710 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7711 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7712 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7713 Et langt steg videre for Debian-prosjektet, og en rekke nye
7714 programpakker blir nå tilgjengelig for de av oss som bruker den
7715 stabile utgaven av Debian. Neste steg er nå å få
7716 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7717 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7718 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7719 slippes løs på skolene. Takk til alle debian-utviklerne som har
7720 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7721 bootsekvens tilgjengelig i stabil utgave, vha pakken
7722 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7723 </description>
7724 </item>
7725
7726 <item>
7727 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7728 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7730 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7731 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7732 Oslo. Most of Saturday was used for the general assemly for the
7733 member organization, but the rest of the weekend I used to tune the
7734 LTSP installation. LTSP now work out of the box on the 10-network.
7735 Acer Aspire One proved to be a very nice thin client, with both
7736 screen, mouse and keybard in a small box. Was working on getting the
7737 diskless workstation setup configured out of the box, but did not
7738 finish it before the weekend was up.&lt;/p&gt;
7739
7740 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7741 the Brazilian group, so that will have to wait for the next
7742 development gathering. Would love to have the Debian Edu installer
7743 automatically detect and configure a multiseat setup when it find one
7744 of these cards.&lt;/p&gt;
7745 </description>
7746 </item>
7747
7748 <item>
7749 <title>The sorry state of multimedia browser plugins in Debian</title>
7750 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7751 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7752 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7753 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7754 plugins available in Debian Lenny, to see which one we should use by
7755 default in Debian Edu. We need an embedded video playing plugin with
7756 control buttons to pause or stop the video, and capable of streaming
7757 all the multimedia content available on the web. The test results and
7758 notes are available on
7759 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7760 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7761 fill this need. My personal video player favorite, VLC, has a really
7762 bad plugin which fail on a lot of the test pages. A lot of the MIME
7763 types I would expect to work with any free software player (like
7764 video/ogg), just do not work. And simple formats like the
7765 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7766 totem and vlc plugins. I hope the situation will improve soon. No
7767 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7768
7769 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7770 be the only one fitting our needs. :/&lt;/p&gt;
7771 </description>
7772 </item>
7773
7774 </channel>
7775 </rss>