]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
a3e6911e5084641ebae39f31fe64709c195a9618
[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 </description>
58 </item>
59
60 <item>
61 <title>Time to find a new laptop, as the old one is broken after only two years</title>
62 <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>
63 <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>
64 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
65 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
66 replacement soon. The left 5 cm of the screen on my Thinkpad X230
67 started flickering yesterday, and I suspect the cause is a broken
68 cable, as changing the angle of the screen some times get rid of the
69 flickering.&lt;/p&gt;
70
71 &lt;p&gt;My requirements have not really changed since I bought it, and is
72 still as
73 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
74 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
75 good help from
76 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
77 where I could select at least a few of the requirements (mouse pin,
78 wifi, weight) and go through the rest manually. Three button mouse
79 and a good keyboard is not available as an option, and all the three
80 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
81 G2) lack three mouse buttons). It is also unclear to me how good the
82 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
83 the keyboard, even if the quality and robustness in the X series have
84 deteriorated since X41.&lt;/p&gt;
85
86 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
87 seem sensible to me? Are there better services around to search the
88 set of available laptops for features? Please send me an email if you
89 have suggestions.&lt;/p&gt;
90 </description>
91 </item>
92
93 <item>
94 <title>How to stay with sysvinit in Debian Jessie</title>
95 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
96 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
97 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
98 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
99 sysvinit as its boot system by default. But how can one keep using
100 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
101 courtesy of
102 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
103 Schubert&lt;/a&gt; and
104 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
105 McVittie&lt;/a&gt;.
106
107 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
108 keep sysvinit as your boot system, create a file
109 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
110 you upgrade:&lt;/p&gt;
111
112 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
113 Package: systemd-sysv
114 Pin: release o=Debian
115 Pin-Priority: -1
116 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
117
118 &lt;p&gt;This file content will tell apt and aptitude to not consider
119 installing systemd-sysv as part of any installation and upgrade
120 solution when resolving dependencies, and thus tell it to avoid
121 systemd as a default boot system. The end result should be that the
122 upgraded system keep using sysvinit.&lt;/p&gt;
123
124 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
125 get sysvinit installed by default (debootstrap used by
126 debian-installer have no option for this), but one can tell the
127 installer to switch to sysvinit before the first boot. Either by
128 using a kernel argument to the installer, or by adding a line to the
129 preseed file used. First, the kernel command line argument:
130
131 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
132 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
133 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
134
135 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
136
137 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
138 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
139 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
140
141 &lt;p&gt;One can of course also do this after the first boot by installing
142 the sysvinit-core package.&lt;/p&gt;
143
144 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
145 sysvinit boot sequence in Debian have several hardware specific bugs
146 on Linux caused by the fact that it is unpredictable when hardware
147 devices show up during boot. But on the other hand, the new default
148 boot system still have a few rough edges I hope will be fixed before
149 Jessie is released.&lt;/p&gt;
150
151 &lt;p&gt;Update 2014-11-26: Inspired by
152 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
153 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
154 line.&lt;/p&gt;
155 </description>
156 </item>
157
158 <item>
159 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
160 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
161 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
162 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
163 <description>&lt;p&gt;The right to communicate with your friends and family in private,
164 without anyone snooping, is a right every citicen have in a liberal
165 democracy. But this right is under serious attack these days.&lt;/p&gt;
166
167 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
168 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
169 the whisleblower Snowden) more expensive for Internet email,
170 is to deliver all email using SMTP via Tor. Such SMTP option would be
171 a nice addition to the FreedomBox project if we could send email
172 between FreedomBox machines without leaking metadata about the emails
173 to the people peeking on the wire. I
174 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
175 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
176 lot of useful feedback and suggestions. It also became obvious to me
177 that this was not a novel idea, as the same idea was tested and
178 documented by Johannes Berg as early as 2006, and both
179 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
180 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
181 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
182
183 &lt;p&gt;To implement such system one need to set up a Tor hidden service
184 providing the SMTP protocol on port 25, and use email addresses
185 looking like username@hidden-service-name.onion. With such addresses
186 the connections to port 25 on hidden-service-name.onion using Tor will
187 go to the correct SMTP server. To do this, one need to configure the
188 Tor daemon to provide the hidden service and the mail server to accept
189 emails for this .onion domain. To learn more about Exim configuration
190 in Debian and test the design provided by Johannes Berg in his FAQ, I
191 set out yesterday to create a Debian package for making it trivial to
192 set up such SMTP over Tor service based on Debian. Getting it to work
193 were fairly easy, and
194 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
195 source code for the Debian package&lt;/a&gt; is available from github. I
196 plan to move it into Debian if further testing prove this to be a
197 useful approach.&lt;/p&gt;
198
199 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
200 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
201 get rid of exim4). Install tor, clone the git repository mentioned
202 above, build the deb and install it on the machine. Next, run
203 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
204 the instructions to get the service up and running. Restart tor and
205 exim when it is done, and test mail delivery using swaks like
206 this:&lt;/p&gt;
207
208 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
209 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
210 --to fbx@dutlqrrmjhtfa3vp.onion
211 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
212
213 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
214 address with your own address to test your server. :)&lt;/p&gt;
215
216 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
217 easier and more automatic. Especially the tor setup need more work.
218 Also, the package include a tor-smtp tool written in C, but its task
219 should probably be rewritten in some script language to make the deb
220 architecture independent. It would probably also make the code easier
221 to review. The tor-smtp tool currently need to listen on a socket for
222 exim to talk to it and is started using xinetd. It would be better if
223 no daemon and no socket is needed. I suspect it is possible to get
224 exim to run a command line tool for delivery instead of talking to a
225 socket, and hope to figure out how in a future version of this
226 system.&lt;/p&gt;
227
228 &lt;p&gt;Until I wipe my test machine, I can be reached using the
229 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
230 SMTorP. :)&lt;/p&gt;
231 </description>
232 </item>
233
234 <item>
235 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
236 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
237 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
238 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
239 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
240 alioth.debian.org, you know the web interface is fairly slow to
241 operate. First you visit one web page, enter the moderation password
242 and get a new page shown with a list of all the messages to moderate
243 and various options for each email address. This take a while for
244 every list you moderate, and you need to do it regularly to do a good
245 job as a list moderator. But there is a quick alternative,
246 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
247 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
248 to moderate in a fraction of a second. Here is a test run on two
249 lists I recently took over:&lt;/p&gt;
250
251 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
252 % time listadmin xiph
253 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
254 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
255
256 real 0m1.709s
257 user 0m0.232s
258 sys 0m0.012s
259 %
260 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
261
262 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
263 there are no message in the moderation queue. Every morning I
264 currently moderate 68 mailman lists, and it normally take around two
265 minutes. When I took over the two pkg-xiph lists above a few days
266 ago, there were 400 emails waiting in the moderator queue. It took me
267 less than 15 minutes to process them all using the listadmin
268 program.&lt;/p&gt;
269
270 &lt;p&gt;If you install
271 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
272 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
273 with content like this, the moderation task is a breeze:&lt;/p&gt;
274
275 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
276 username username@example.org
277 spamlevel 23
278 default discard
279 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
280
281 password secret
282 adminurl https://{domain}/mailman/admindb/{list}
283 mailman-list@lists.example.com
284
285 password hidden
286 other-list@otherserver.example.org
287 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
288
289 &lt;p&gt;There are other options to set as well. Check the manual page to
290 learn the details.&lt;/p&gt;
291
292 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
293 the SSL certificate is self signed or not properly signed by a
294 generally accepted signing authority, you can set a environment
295 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
296
297 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
298 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
299 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
300
301 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
302 can provide an argument to the listadmin script like I do in the
303 initial screen dump (the xiph argument). Using an argument, only
304 lists matching the argument string will be processed. This make it
305 quick to accept messages if you notice the moderation request in your
306 email.&lt;/p&gt;
307
308 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
309 mailing lists, as I simply do not have time to spend on that if the
310 process was any slower. The listadmin program have saved me hours of
311 time I could spend elsewhere over the years. It truly is nice free
312 software.&lt;/p&gt;
313
314 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
315 activities, please send Bitcoin donations to my address
316 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
317
318 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
319 configuration example. Also, I&#39;ve been told that the
320 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
321 sure why.&lt;/p&gt;
322 </description>
323 </item>
324
325 <item>
326 <title>Debian Jessie, PXE and automatic firmware installation</title>
327 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
328 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
329 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
330 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
331 problem that the WiFi card require some firmware to work properly.
332 And it has been a pain to fix this using preseeding in Debian.
333 Normally something more is needed. But thanks to
334 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
335 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
336 to do this using simple preseeding.&lt;/p&gt;
337
338 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
339 firmware for the hardware found in the machine (actually, requested by
340 the kernel modules for the hardware). (It can also install user space
341 programs supporting the hardware detected, but that is not the focus
342 of this story.)&lt;/p&gt;
343
344 &lt;p&gt;To get this working in the default installation, two preeseding
345 values are needed. First, the isenkram-cli package must be installed
346 into the target chroot (aka the hard drive) before tasksel is executed
347 in the pkgsel step of the debian-installer system. This is done by
348 preseeding the base-installer/includes debconf value to include the
349 isenkram-cli package. The package name is next passed to debootstrap
350 for installation. With the isenkram-cli package in place, tasksel
351 will automatically use the isenkram tasks to detect hardware specific
352 packages for the machine being installed and install them, because
353 isenkram-cli contain tasksel tasks.&lt;/p&gt;
354
355 &lt;p&gt;Second, one need to enable the non-free APT repository, because
356 most firmware unfortunately is non-free. This is done by preseeding
357 the apt-mirror-setup step. This is unfortunate, but for a lot of
358 hardware it is the only option in Debian.&lt;/p&gt;
359
360 &lt;p&gt;The end result is two lines needed in your preseeding file to get
361 firmware installed automatically by the installer:&lt;/p&gt;
362
363 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
364 base-installer base-installer/includes string isenkram-cli
365 apt-mirror-setup apt-setup/non-free boolean true
366 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
367
368 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
369 both firmware and user space packages when using this method. It also
370 do not work well, so use version 0.15 or later. Installing both
371 firmware and user space packages might give you a bit more than you
372 want, so I decided to split the tasksel task in two, one for firmware
373 and one for user space programs. The firmware task is enabled by
374 default, while the one for user space programs is not. This split is
375 implemented in the package currently in unstable.&lt;/p&gt;
376
377 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
378 this recipe work for you. :)&lt;/p&gt;
379
380 &lt;p&gt;So, I bet you are wondering, how can this work. First and
381 foremost, it work because tasksel is modular, and driven by whatever
382 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
383 isenkram-cli package place two files for tasksel to find. First there
384 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
385
386 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
387 Task: isenkram-packages
388 Section: hardware
389 Description: Hardware specific packages (autodetected by isenkram)
390 Based on the detected hardware various hardware specific packages are
391 proposed.
392 Test-new-install: show show
393 Relevance: 8
394 Packages: for-current-hardware
395
396 Task: isenkram-firmware
397 Section: hardware
398 Description: Hardware specific firmware packages (autodetected by isenkram)
399 Based on the detected hardware various hardware specific firmware
400 packages are proposed.
401 Test-new-install: mark show
402 Relevance: 8
403 Packages: for-current-hardware-firmware
404 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
405
406 &lt;p&gt;The key parts are Test-new-install which indicate how the task
407 should be handled and the Packages line referencing to a script in
408 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
409 list of packages to install. The for-current-hardware-firmware script
410 look like this to list relevant firmware for the machine:
411
412 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
413 #!/bin/sh
414 #
415 PATH=/usr/sbin:$PATH
416 export PATH
417 isenkram-autoinstall-firmware -l
418 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
419
420 &lt;p&gt;With those two pieces in place, the firmware is installed by
421 tasksel during the normal d-i run. :)&lt;/p&gt;
422
423 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
424 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
425 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
426 install.&lt;/p&gt;
427
428 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
429 pilots in testing this feature, as isenkram is used there now to
430 install firmware, replacing the earlier scripts.&lt;/p&gt;
431 </description>
432 </item>
433
434 <item>
435 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
436 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
437 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
438 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
439 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
440 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
441 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
442 on a screen normally showing the bread types and prizes:&lt;/p&gt;
443
444 &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;
445
446 &lt;p&gt;If it had booted as it was supposed to, I would never had known
447 about this hidden Linux installation. It is interesting what
448 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
449 </description>
450 </item>
451
452 <item>
453 <title>New lsdvd release version 0.17 is ready</title>
454 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
456 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
457 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
458 got a new set of developers a few weeks ago, after the original
459 developer decided to step down and pass the project to fresh blood.
460 This project is now maintained by Petter Reinholdtsen and Steve
461 Dibb.&lt;/p&gt;
462
463 &lt;p&gt;I just wrapped up
464 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
465 new lsdvd release&lt;/a&gt;, available in git or from
466 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
467 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
468 0.17.&lt;/p&gt;
469
470 &lt;ul&gt;
471
472 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
473 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
474 non-existant, to work around additional copy protection&lt;/li&gt;
475 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
476 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
477 &lt;li&gt;Fix include orders&lt;/li&gt;
478 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
479 &lt;li&gt;Fix the chapter count&lt;/li&gt;
480 &lt;li&gt;Make sure the array size and the array limit used when initialising
481 the palette size is the same.&lt;/li&gt;
482 &lt;li&gt;Fix array printing.&lt;/li&gt;
483 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
484 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
485 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
486 with more GCC compiler warnings.&lt;/li&gt;
487
488 &lt;/ul&gt;
489
490 &lt;p&gt;This change bring together patches for lsdvd in use in various
491 Linux and Unix distributions, as well as patches submitted to the
492 project the last nine years. Please check it out. :)&lt;/p&gt;
493 </description>
494 </item>
495
496 <item>
497 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
498 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
499 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
500 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
501 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
502 project&lt;/a&gt; provide a Linux solution for schools, including a
503 powerful desktop with education software, a central server providing
504 web pages, user database, user home directories, central login and PXE
505 boot of both clients without disk and the installation to install Debian
506 Edu on machines with disk (and a few other services perhaps to small
507 to mention here). We in the Debian Edu team are currently working on
508 the Jessie based version, trying to get everything in shape before the
509 freeze, to avoid having to maintain our own package repository in the
510 future. The
511 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
512 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
513 work left. Some fatal problems block testing, breaking the installer,
514 but it is possible to work around these to get anyway. Here is a
515 recipe on how to get the installation limping along.&lt;/p&gt;
516
517 &lt;p&gt;First, download the test ISO via
518 &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;,
519 &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;
520 or rsync (use
521 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
522 The ISO build was broken on Tuesday, so we do not get a new ISO every
523 12 hours or so, but thankfully the ISO we already got we are able to
524 install with some tweaking.&lt;/p&gt;
525
526 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
527 (use Alt-Ctrl-F2), run&lt;/p&gt;
528
529 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
530 nano /usr/bin/edu-eatmydata-install
531 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
532
533 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
534 optimization. Return to the installation, select the profile you want
535 and continue. Without this change, exim4-config will fail to install
536 due to a known bug in eatmydata.&lt;/p&gt;
537
538 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
539 this do not work, figure out what your correct value would be. All my
540 test machines need /dev/sda, so I have no advice if it do not fit
541 your need.&lt;/p&gt;
542
543 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
544 root after the initial boot from hard drive, and install the
545 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
546 or mate. If you want several desktop options, install more than one
547 metapackage. Once this is done, reboot and you should have a working
548 graphical login screen. This workaround should no longer be needed
549 once the education-tasks package version 1.801 enter testing in two
550 days.&lt;/p&gt;
551
552 &lt;p&gt;I believe the ISO build will start working on two days when the new
553 tasksel package enter testing and Steve McIntyre get a chance to
554 update the debian-cd git repository. The eatmydata, grub and desktop
555 issues are already fixed in unstable and testing, and should show up
556 on the ISO as soon as the ISO build start working again. Well the
557 eatmydata optimization is really just disabled. The proper fix
558 require an upload by the eatmydata maintainer applying the patch
559 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
560 The rest have proper fixes in unstable.&lt;/p&gt;
561
562 &lt;p&gt;I hope this get you going with the installation testing, as we are
563 quickly running out of time trying to get our Jessie based
564 installation ready before the distribution freeze in a month.&lt;/p&gt;
565 </description>
566 </item>
567
568 <item>
569 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
570 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
571 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
572 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
573 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
574 to handle my fairly large DVD collection. It is a nice command line
575 tool to get details about a DVD, like title, tracks, track length,
576 etc, in XML, Perl or human readable format. But lsdvd have not seen
577 any new development since 2006 and had a few irritating bugs affecting
578 its use with some DVDs. Upstream seemed to be dead, and in January I
579 sent a small probe asking for a version control repository for the
580 project, without any reply. But I use it regularly and would like to
581 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
582 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
583 the project admin, and after getting a reply from him explaining that
584 he was no longer interested in the project, I asked if I could take
585 over. And yesterday, I became project admin.&lt;/p&gt;
586
587 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
588 maintainer interested in joining forces to maintain the upstream
589 project, and I hope we can get a new release out fairly quickly,
590 collecting the patches spread around on the internet into on place.
591 I&#39;ve added the relevant Debian patches to the freshly created git
592 repository, and expect the Gentoo patches to make it too. If you got
593 a DVD collection and care about command line tools, check out
594 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
595 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
596 list&lt;/a&gt;. :)&lt;/p&gt;
597 </description>
598 </item>
599
600 <item>
601 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
602 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
603 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
604 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
605 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
606 a lot quicker. When we install more than 2000 packages in
607 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
608 tasksel in the installer, unpacking the binary packages take forever.
609 A part of the slow I/O issue was discussed in
610 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
611 much file system sync-ing done by dpkg, which is the package
612 responsible for unpacking the binary packages. Other parts (like code
613 executed by postinst scripts) might also sync to disk during
614 installation. All this sync-ing to disk do not really make sense to
615 me. If the machine crash half-way through, I start over, I do not try
616 to salvage the half installed system. So the failure sync-ing is
617 supposed to protect against, hardware or system crash, is not really
618 relevant while the installer is running.&lt;/p&gt;
619
620 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
621 system sync()-ing in a fairly non-intrusive way, without the need to
622 change the code in several packages. The idea is not new, but I have
623 not heard anyone propose the approach using dpkg-divert before. It
624 depend on the small and clever package
625 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
626 uses LD_PRELOAD to replace the system functions for syncing data to
627 disk with functions doing nothing, thus allowing programs to live
628 dangerous while speeding up disk I/O significantly. Instead of
629 modifying the implementation of dpkg, apt and tasksel (which are the
630 packages responsible for selecting, fetching and installing packages),
631 it occurred to me that we could just divert the programs away, replace
632 them with a simple shell wrapper calling
633 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
634 Two days ago I decided to test the idea, and wrapped up a simple
635 implementation for the Debian Edu udeb.&lt;/p&gt;
636
637 &lt;p&gt;The effect was stunning. In my first test it reduced the running
638 time of the pkgsel step (installing tasks) from 64 to less than 44
639 minutes (20 minutes shaved off the installation) on an old Dell
640 Latitude D505 machine. I am not quite sure what the optimised time
641 would have been, as I messed up the testing a bit, causing the debconf
642 priority to get low enough for two questions to pop up during
643 installation. As soon as I saw the questions I moved the installation
644 along, but do not know how long the question were holding up the
645 installation. I did some more measurements using Debian Edu Jessie,
646 and got these results. The time measured is the time stamp in
647 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
648 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
649 yourself. In Debian Edu, the tasksel dialog do not show up, and the
650 timing thus do not depend on how quickly the user handle the tasksel
651 dialog.&lt;/p&gt;
652
653 &lt;p&gt;&lt;table&gt;
654
655 &lt;tr&gt;
656 &lt;th&gt;Machine/setup&lt;/th&gt;
657 &lt;th&gt;Original tasksel&lt;/th&gt;
658 &lt;th&gt;Optimised tasksel&lt;/th&gt;
659 &lt;th&gt;Reduction&lt;/th&gt;
660 &lt;/tr&gt;
661
662 &lt;tr&gt;
663 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
664 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
665 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
666 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
667 &lt;/tr&gt;
668
669 &lt;tr&gt;
670 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
671 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
672 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
673 &lt;td&gt;23 min 40%&lt;/td&gt;
674 &lt;/tr&gt;
675
676 &lt;tr&gt;
677 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
678 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
679 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
680 &lt;td&gt;11 min 50%&lt;/td&gt;
681 &lt;/tr&gt;
682
683 &lt;tr&gt;
684 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
685 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
686 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
687 &lt;td&gt;2 min 33%&lt;/td&gt;
688 &lt;/tr&gt;
689
690 &lt;tr&gt;
691 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
692 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
693 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
694 &lt;td&gt;4 min 21%&lt;/td&gt;
695 &lt;/tr&gt;
696
697 &lt;/table&gt;&lt;/p&gt;
698
699 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
700 time is spent downloading packages. The connection to the Internet
701 was 100Mbit/s during testing, so downloading should not be a
702 significant factor in the measurement. Download typically took a few
703 seconds to a few minutes, depending on the amount of packages being
704 installed.&lt;/p&gt;
705
706 &lt;p&gt;The speedup is implemented by using two hooks in
707 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
708 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
709 finish-install.d hook to remove the divert at the end of the
710 installation. I picked the pre-pkgsel.d hook instead of the
711 post-base-installer.d hook because I test using an ISO without the
712 eatmydata package included, and the post-base-installer.d hook in
713 Debian Edu can only operate on packages included in the ISO. The
714 negative effect of this is that I am unable to activate this
715 optimization for the kernel installation step in d-i. If the code is
716 moved to the post-base-installer.d hook, the speedup would be larger
717 for the entire installation.&lt;/p&gt;
718
719 &lt;p&gt;I&#39;ve implemented this in the
720 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
721 git repository, and plan to provide the optimization as part of the
722 Debian Edu installation. If you want to test this yourself, you can
723 create two files in the installer (or in an udeb). One shell script
724 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
725
726 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
727 #!/bin/sh
728 set -e
729 . /usr/share/debconf/confmodule
730 info() {
731 logger -t my-pkgsel &quot;info: $*&quot;
732 }
733 error() {
734 logger -t my-pkgsel &quot;error: $*&quot;
735 }
736 override_install() {
737 apt-install eatmydata || true
738 if [ -x /target/usr/bin/eatmydata ] ; then
739 for bin in dpkg apt-get aptitude tasksel ; do
740 file=/usr/bin/$bin
741 # Test that the file exist and have not been diverted already.
742 if [ -f /target$file ] ; then
743 info &quot;diverting $file using eatmydata&quot;
744 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
745 &gt; /target$file.edu
746 chmod 755 /target$file.edu
747 in-target dpkg-divert --package debian-edu-config \
748 --rename --quiet --add $file
749 ln -sf ./$bin.edu /target$file
750 else
751 error &quot;unable to divert $file, as it is missing.&quot;
752 fi
753 done
754 else
755 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
756 fi
757 }
758
759 override_install
760 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
761
762 &lt;p&gt;To clean up, another shell script should go into
763 /usr/lib/finish-install.d/ with code like this:
764
765 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
766 #! /bin/sh -e
767 . /usr/share/debconf/confmodule
768 error() {
769 logger -t my-finish-install &quot;error: $@&quot;
770 }
771 remove_install_override() {
772 for bin in dpkg apt-get aptitude tasksel ; do
773 file=/usr/bin/$bin
774 if [ -x /target$file.edu ] ; then
775 rm /target$file
776 in-target dpkg-divert --package debian-edu-config \
777 --rename --quiet --remove $file
778 rm /target$file.edu
779 else
780 error &quot;Missing divert for $file.&quot;
781 fi
782 done
783 sync # Flush file buffers before continuing
784 }
785
786 remove_install_override
787 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
788
789 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
790 edu-eatmydata-install and call it from the pre-pkgsel.d and
791 finish-install.d scripts.&lt;/p&gt;
792
793 &lt;p&gt;By now you might ask if this change should get into the normal
794 Debian installer too? I suspect it should, but am not sure the
795 current debian-installer coordinators find it useful enough. It also
796 depend on the side effects of the change. I&#39;m not aware of any, but I
797 guess we will see if the change is safe after some more testing.
798 Perhaps there is some package in Debian depending on sync() and
799 fsync() having effect? Perhaps it should go into its own udeb, to
800 allow those of us wanting to enable it to do so without affecting
801 everyone.&lt;/p&gt;
802
803 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
804 will break installation of all programs using gnutls because of
805 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
806 eatmydata package in Debian will solve it.&lt;/p&gt;
807
808 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
809 the optimization work again. And I have discovered that the
810 dpkg-divert trick is not really needed and implemented a slightly
811 simpler approach as part of the debian-edu-install package. See
812 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
813
814 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
815 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
816 triggering on i386 made it into testing, and broke this installation
817 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
818 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
819 </description>
820 </item>
821
822 <item>
823 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
824 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
825 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
826 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
827 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
828 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
829 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
830 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
831 learn that there is a large set of publicly available key servers to
832 use when looking for peoples public key. So far I have used
833 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
834 were misbehaving, but those days are ended. The servers I have used
835 up until yesterday have been slow and some times unavailable. I hope
836 those problems are gone now.&lt;/p&gt;
837
838 &lt;p&gt;Behind the round robin DNS entry of the
839 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
840 there is a pool of more than 100 keyservers which are checked every
841 day to ensure they are well connected and up to date. It must be
842 better than what I have used so far. :)&lt;/p&gt;
843
844 &lt;p&gt;Yesterdays speaker told me that the service is the default
845 keyserver provided by the default configuration in GnuPG, but this do
846 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
847
848 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
849 line:&lt;/p&gt;
850
851 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
852 keyserver pool.sks-keyservers.net
853 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
854
855 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
856 entries in DNS. Just for fun, I did just that at work, so now every
857 user of GnuPG at the University of Oslo should find a OpenGPG
858 keyserver automatically should their need it:&lt;/p&gt;
859
860 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
861 % host -t srv _pgpkey-http._tcp.uio.no
862 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
863 %
864 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
865
866 &lt;p&gt;Now if only
867 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
868 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
869 very happy. It can look up a given key or search for a user ID, but I
870 normally do not want that, but to find a trust path from my key to
871 another key. Given a user ID or key ID, I would like to find (and
872 download) the keys representing a signature path from my key to the
873 key in question, to be able to get a trust path between the two keys.
874 This is as far as I can tell not possible today. Perhaps something
875 for a future version of the protocol?&lt;/p&gt;
876 </description>
877 </item>
878
879 <item>
880 <title>From English wiki to translated PDF and epub via Docbook</title>
881 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
882 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
883 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
884 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
885 project&lt;/a&gt; provide an instruction manual for teachers, system
886 administrators and other users that contain useful tips for setting up
887 and maintaining a Debian Edu installation. This text is about how the
888 text processing of this manual is handled in the project.&lt;/p&gt;
889
890 &lt;p&gt;One goal of the project is to provide information in the native
891 language of its users, and for this we need to handle translations.
892 But we also want to make sure each language contain the same
893 information, so for this we need a good way to keep the translations
894 in sync. And we want it to be easy for our users to improve the
895 documentation, avoiding the need to learn special formats or tools to
896 contribute, and the obvious way to do this is to make it possible to
897 edit the documentation using a web browser. We also want it to be
898 easy for translators to keep the translation up to date, and give them
899 help in figuring out what need to be translated. Here is the list of
900 tools and the process we have found trying to reach all these
901 goals.&lt;/p&gt;
902
903 &lt;p&gt;We maintain the authoritative source of our manual in the
904 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
905 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
906 front page with references to the different chapters, several pages
907 for each chapter, and finally one &quot;collection page&quot; gluing all the
908 chapters together into one large web page (aka
909 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
910 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
911 processing and translations. Thanks to the fact that the
912 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
913 wiki.debian.org support exporting pages in
914 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
915 the list of pages to export using the raw version of the AllInOne
916 page, loop over each of them to generate a Docbook XML version of the
917 manual. This process also download images and transform image
918 references to use the locally downloaded images. The generated
919 Docbook XML files are slightly broken, so some post-processing is done
920 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
921 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
922 a handfull of images. The XML file can now be used to generate PDF, HTML
923 and epub versions of the English manual. This is the basic step of
924 our process, making PDF (using dblatex), HTML (using xsltproc) and
925 epub (using dbtoepub) version from Docbook XML, and the resulting files
926 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
927
928 &lt;p&gt;But English documentation is not enough for us. We want translated
929 documentation too, and we want to make it easy for translators to
930 track the English original. For this we use the
931 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
932 which allow us to transform the English Docbook XML file into a
933 translation file (a .pot file), usable with the normal gettext based
934 translation tools used by those translating free software. The pot
935 file is used to create and maintain translation files (several .po
936 files), which the translations update with the native language
937 translations of all titles, paragraphs and blocks of text in the
938 original. The next step is combining the original English Docbook XML
939 and the translation file (say debian-edu-wheezy-manual.nb.po), to
940 create a translated Docbook XML file (in this case
941 debian-edu-wheezy-manual.nb.xml). This translated (or partly
942 translated, if the translation is not complete) Docbook XML file can
943 then be used like the original to create a PDF, HTML and epub version
944 of the documentation.&lt;/p&gt;
945
946 &lt;p&gt;The translators use different tools to edit the .po files. We
947 recommend using
948 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
949 while some use emacs and vi, others can use web based editors like
950 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
951 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
952 is where the .po file end up, in our git repository. Updated
953 translations can either be committed directly to git, or submitted as
954 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
955 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
956
957 &lt;p&gt;One challenge is images, which both might need to be translated (if
958 they show translated user applications), and are needed in different
959 formats when creating PDF and HTML versions (epub is a HTML version in
960 this regard). For this we transform the original PNG images to the
961 needed density and format during build, and have a way to provide
962 translated images by storing translated versions in
963 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
964 package maintainers know more.&lt;/p&gt;
965
966 &lt;p&gt;If you wonder what the result look like, we provide
967 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
968 of the documentation packages on the web&lt;/a&gt;. See for example the
969 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
970 PDF version&lt;/a&gt; or the
971 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
972 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
973 but perhaps it will be done in the future.&lt;/p&gt;
974
975 &lt;p&gt;To learn more, check out
976 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
977 debian-edu-doc package&lt;/a&gt;,
978 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
979 manual on the wiki&lt;/a&gt; and
980 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
981 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
982 </description>
983 </item>
984
985 <item>
986 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
987 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
989 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
990 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
991 related packages relevant for the computer installed automatically.
992 So I implemented one, using
993 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
994 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
995 run tasksel as user root. You should be presented with a new option,
996 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
997 select it, tasksel will install the packages isenkram claim is fit for
998 the current hardware, hot pluggable or not.&lt;p&gt;
999
1000 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1001 description, and the other is the script used to extract the list of
1002 packages to install. The first part is in
1003 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1004 this:&lt;/p&gt;
1005
1006 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1007 Task: isenkram
1008 Section: hardware
1009 Description: Hardware specific packages (autodetected by isenkram)
1010 Based on the detected hardware various hardware specific packages are
1011 proposed.
1012 Test-new-install: mark show
1013 Relevance: 8
1014 Packages: for-current-hardware
1015 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1016
1017 &lt;p&gt;The second part is in
1018 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1019 this:&lt;/p&gt;
1020
1021 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1022 #!/bin/sh
1023 #
1024 (
1025 isenkram-lookup
1026 isenkram-autoinstall-firmware -l
1027 ) | sort -u
1028 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1029
1030 &lt;p&gt;All in all, a very short and simple implementation making it
1031 trivial to install the hardware dependent package we all may want to
1032 have installed on our machines. I&#39;ve not been able to find a way to
1033 get tasksel to tell you exactly which packages it plan to install
1034 before doing the installation. So if you are curious or careful,
1035 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1036
1037 &lt;p&gt;The information about which packages are handling which hardware is
1038 fetched either from the isenkram package itself in
1039 /usr/share/isenkram/, from git.debian.org or from the APT package
1040 database (using the Modaliases header). The APT package database
1041 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1042 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1043 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1044 the python-apt code (bug
1045 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1046 workaround I was able to get rid of the file descriptor leak and
1047 reduce the memory leak from ~30 MiB per hardware detection down to
1048 around 2 MiB per hardware detection. It should make the desktop
1049 daemon a lot more useful. The fix is in version 0.7 uploaded to
1050 unstable today.&lt;/p&gt;
1051
1052 &lt;p&gt;I believe the current way of mapping hardware to packages in
1053 Isenkram is is a good draft, but in the future I expect isenkram to
1054 use the AppStream data source for this. A proposal for getting proper
1055 AppStream support into Debian is floating around as
1056 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1057 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1058 project&lt;/a&gt; will take place this summer to improve the situation. I
1059 look forward to seeing the result, and welcome patches for isenkram to
1060 start using the information when it is ready.&lt;/p&gt;
1061
1062 &lt;p&gt;If you want your package to map to some specific hardware, either
1063 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1064 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1065 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1066 package. See also
1067 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1068 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1069 the information will be migrated to AppStream eventually, but for the
1070 moment I got no better place to store it.&lt;/p&gt;
1071 </description>
1072 </item>
1073
1074 <item>
1075 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1076 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1077 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1078 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1079 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1080 project&lt;/a&gt; is working on providing the software and hardware to make
1081 it easy for non-technical people to host their data and communication
1082 at home, and being able to communicate with their friends and family
1083 encrypted and away from prying eyes. It is still going strong, and
1084 today a major mile stone was reached.&lt;/p&gt;
1085
1086 &lt;p&gt;Today, the last of the packages currently used by the project to
1087 created the system images were accepted into Debian Unstable. It was
1088 the freedombox-setup package, which is used to configure the images
1089 during build and on the first boot. Now all one need to get going is
1090 the build code from the freedom-maker git repository and packages from
1091 Debian. And once the freedombox-setup package enter testing, we can
1092 build everything directly from Debian. :)&lt;/p&gt;
1093
1094 &lt;p&gt;Some key packages used by Freedombox are
1095 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1096 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1097 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1098 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1099 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1100 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1101 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1102 are plans to integrate more packages into the setup. User
1103 documentation is maintained on the Debian wiki. Please
1104 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1105 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1106
1107 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1108 setup, run this on a Debian machine using a user with sudo rights to
1109 become root:&lt;/p&gt;
1110
1111 &lt;p&gt;&lt;pre&gt;
1112 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1113 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1114 u-boot-tools
1115 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1116 freedom-maker
1117 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1118 &lt;/pre&gt;&lt;/p&gt;
1119
1120 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1121 devices. See the README in the freedom-maker git repo for more
1122 details on the build. If you do not want all three images, trim the
1123 make line. Note that the virtualbox-image target is not really
1124 virtualbox specific. It create a x86 image usable in kvm, qemu,
1125 vmware and any other x86 virtual machine environment. You might need
1126 the version of vmdebootstrap in Jessie to get the build working, as it
1127 include fixes for a race condition with kpartx.&lt;/p&gt;
1128
1129 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1130 method, boot a Debian Wheezy ISO and use this boot argument to load
1131 the preseed values:&lt;/p&gt;
1132
1133 &lt;p&gt;&lt;pre&gt;
1134 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;
1135 &lt;/pre&gt;&lt;/p&gt;
1136
1137 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1138 it still work.&lt;/p&gt;
1139
1140 &lt;p&gt;If you wonder how to help, one task you could look at is using
1141 systemd as the boot system. It will become the default for Linux in
1142 Jessie, so we need to make sure it is usable on the Freedombox. I did
1143 a simple test a few weeks ago, and noticed dnsmasq failed to start
1144 during boot when using systemd. I suspect there are other problems
1145 too. :) To detect problems, there is a test suite included, which can
1146 be run from the plinth web interface.&lt;/p&gt;
1147
1148 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1149 us get the new release published. :) Please join us on
1150 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1151 irc.debian.org)&lt;/a&gt; and
1152 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1153 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1154 </description>
1155 </item>
1156
1157 <item>
1158 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1159 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1160 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1161 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1162 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1163 solution for use at home. My requirements are simple, it must be
1164 cheap and locally encrypted (in other words, I keep the encryption
1165 keys, the storage provider do not have access to my private files).
1166 One idea me and my friends had many years ago, before the cloud
1167 storage providers showed up, was to use Google mail as storage,
1168 writing a Linux block device storing blocks as emails in the mail
1169 service provided by Google, and thus get heaps of free space. On top
1170 of this one can add encryption, RAID and volume management to have
1171 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1172 I never found time to implement such system. But the last few weeks I
1173 have looked at a system called
1174 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1175 mounted network backed file system with the features I need.&lt;/p&gt;
1176
1177 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1178 handling several different storage providers, any with Amazon S3,
1179 Google Drive or OpenStack API. There are heaps of such storage
1180 providers. S3QL can also use a local directory as storage, which
1181 combined with sshfs allow for file storage on any ssh server. S3QL
1182 include support for encryption, compression, de-duplication, snapshots
1183 and immutable file systems, allowing me to mount the remote storage as
1184 a local mount point, look at and use the files as if they were local,
1185 while the content is stored in the cloud as well. This allow me to
1186 have a backup that should survive fire. The file system can not be
1187 shared between several machines at the same time, as only one can
1188 mount it at the time, but any machine with the encryption key and
1189 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1190
1191 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1192 package is included already. So to get started, run &lt;tt&gt;apt-get
1193 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1194 Greenqloud, after reading their nice recipe on
1195 &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
1196 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1197 in Iceland more than those in USA when it come to keeping my personal
1198 data safe and private, and thus would rather spend money on a company
1199 in Iceland. Another nice recipe is available from the article
1200 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1201 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1202 Admin magazine. When the provider is picked, figure out how to get
1203 the API key needed to connect to the storage API. With Greencloud,
1204 the key did not show up until I had added payment details to my
1205 account.&lt;/p&gt;
1206
1207 &lt;p&gt;Armed with the API access details, it is time to create the file
1208 system. First, create a new bucket in the cloud. This bucket is the
1209 file system storage area. I picked a bucket name reflecting the
1210 machine that was going to store data there, but any name will do.
1211 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1212 the API login and password, and a locally created password. Store it
1213 all in ~root/.s3ql/authinfo2 like this:
1214
1215 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1216 [s3c]
1217 storage-url: s3c://s.greenqloud.com:443/bucket-name
1218 backend-login: API-login
1219 backend-password: API-password
1220 fs-passphrase: local-password
1221 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1222
1223 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1224 but any sensible way to create a fairly random password should do it.
1225 Armed with these details, it is now time to run mkfs, entering the API
1226 details and password to create it:&lt;/p&gt;
1227
1228 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1229 # mkdir -m 700 /var/lib/s3ql-cache
1230 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1231 --ssl s3c://s.greenqloud.com:443/bucket-name
1232 Enter backend login:
1233 Enter backend password:
1234 Before using S3QL, make sure to read the user&#39;s guide, especially
1235 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1236 Enter encryption password:
1237 Confirm encryption password:
1238 Generating random encryption key...
1239 Creating metadata tables...
1240 Dumping metadata...
1241 ..objects..
1242 ..blocks..
1243 ..inodes..
1244 ..inode_blocks..
1245 ..symlink_targets..
1246 ..names..
1247 ..contents..
1248 ..ext_attributes..
1249 Compressing and uploading metadata...
1250 Wrote 0.00 MB of compressed metadata.
1251 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1252
1253 &lt;p&gt;The next step is mounting the file system to make the storage available.
1254
1255 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1256 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1257 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1258 Using 4 upload threads.
1259 Downloading and decompressing metadata...
1260 Reading metadata...
1261 ..objects..
1262 ..blocks..
1263 ..inodes..
1264 ..inode_blocks..
1265 ..symlink_targets..
1266 ..names..
1267 ..contents..
1268 ..ext_attributes..
1269 Mounting filesystem...
1270 # df -h /s3ql
1271 Filesystem Size Used Avail Use% Mounted on
1272 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1273 #
1274 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1275
1276 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1277 backups in it, and as the metadata used by rsync is downloaded at
1278 mount time, no network traffic (and storage cost) is triggered by
1279 running rsync. To unmount, one should not use the normal umount
1280 command, as this will not flush the cache to the cloud storage, but
1281 instead running the umount.s3ql command like this:
1282
1283 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1284 # umount.s3ql /s3ql
1285 #
1286 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1287
1288 &lt;p&gt;There is a fsck command available to check the file system and
1289 correct any problems detected. This can be used if the local server
1290 crashes while the file system is mounted, to reset the &quot;already
1291 mounted&quot; flag. This is what it look like when processing a working
1292 file system:&lt;/p&gt;
1293
1294 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1295 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1296 Using cached metadata.
1297 File system seems clean, checking anyway.
1298 Checking DB integrity...
1299 Creating temporary extra indices...
1300 Checking lost+found...
1301 Checking cached objects...
1302 Checking names (refcounts)...
1303 Checking contents (names)...
1304 Checking contents (inodes)...
1305 Checking contents (parent inodes)...
1306 Checking objects (reference counts)...
1307 Checking objects (backend)...
1308 ..processed 5000 objects so far..
1309 ..processed 10000 objects so far..
1310 ..processed 15000 objects so far..
1311 Checking objects (sizes)...
1312 Checking blocks (referenced objects)...
1313 Checking blocks (refcounts)...
1314 Checking inode-block mapping (blocks)...
1315 Checking inode-block mapping (inodes)...
1316 Checking inodes (refcounts)...
1317 Checking inodes (sizes)...
1318 Checking extended attributes (names)...
1319 Checking extended attributes (inodes)...
1320 Checking symlinks (inodes)...
1321 Checking directory reachability...
1322 Checking unix conventions...
1323 Checking referential integrity...
1324 Dropping temporary indices...
1325 Backing up old metadata...
1326 Dumping metadata...
1327 ..objects..
1328 ..blocks..
1329 ..inodes..
1330 ..inode_blocks..
1331 ..symlink_targets..
1332 ..names..
1333 ..contents..
1334 ..ext_attributes..
1335 Compressing and uploading metadata...
1336 Wrote 0.89 MB of compressed metadata.
1337 #
1338 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1339
1340 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1341 quick, about the same speed as local file access. Uploading large
1342 amount of data is to me limited by the bandwidth out of and into my
1343 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1344 which is very close to my upload speed, and downloading the same
1345 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1346 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1347 network, not the file system code. I do not know what a good cache
1348 size would be, but suspect that the cache should e larger than your
1349 working set.&lt;/p&gt;
1350
1351 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1352 time. If another machine try, it is told that the file system is
1353 busy:&lt;/p&gt;
1354
1355 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1356 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1357 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1358 Using 8 upload threads.
1359 Backend reports that fs is still mounted elsewhere, aborting.
1360 #
1361 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1362
1363 &lt;p&gt;The file content is uploaded when the cache is full, while the
1364 metadata is uploaded once every 24 hour by default. To ensure the
1365 file system content is flushed to the cloud, one can either umount the
1366 file system, or ask S3QL to flush the cache and metadata using
1367 s3qlctrl:
1368
1369 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1370 # s3qlctrl upload-meta /s3ql
1371 # s3qlctrl flushcache /s3ql
1372 #
1373 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1374
1375 &lt;p&gt;If you are curious about how much space your data uses in the
1376 cloud, and how much compression and deduplication cut down on the
1377 storage usage, you can use s3qlstat on the mounted file system to get
1378 a report:&lt;/p&gt;
1379
1380 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1381 # s3qlstat /s3ql
1382 Directory entries: 9141
1383 Inodes: 9143
1384 Data blocks: 8851
1385 Total data size: 22049.38 MB
1386 After de-duplication: 21955.46 MB (99.57% of total)
1387 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1388 Database size: 2.39 MB (uncompressed)
1389 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1390 #
1391 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1392
1393 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1394 storage. I did not try to locate them all, but am aware of at least
1395 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1396 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1397 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1398 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1399 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1400 accept payment in Bitcoin. Pick one that suit your need. Some of
1401 them provide several GiB of free storage, but the prize models are
1402 quite different and you will have to figure out what suits you
1403 best.&lt;/p&gt;
1404
1405 &lt;p&gt;While researching this blog post, I had a look at research papers
1406 and posters discussing the S3QL file system. There are several, which
1407 told me that the file system is getting a critical check by the
1408 science community and increased my confidence in using it. One nice
1409 poster is titled
1410 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1411 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1412 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1413 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1414 and Pamela Smith. Please have a look.&lt;/p&gt;
1415
1416 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1417 check out the mounted S3QL file system to see if it would be usable as
1418 a home directory (in other word, that it provided POSIX semantics when
1419 it come to locking and umask handling etc). Running
1420 &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
1421 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1422 no error was found. So the file system can be used for home
1423 directories, if one chooses to do so.&lt;/p&gt;
1424
1425 &lt;p&gt;If you do not want a locally file system, and want something that
1426 work without the Linux fuse file system, I would like to mention the
1427 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1428 provide locally encrypted backup using a command line client. It have
1429 a nicer access control system, where one can split out read and write
1430 access, allowing some systems to write to the backup and others to
1431 only read from it.&lt;/p&gt;
1432
1433 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1434 activities, please send Bitcoin donations to my address
1435 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1436 </description>
1437 </item>
1438
1439 <item>
1440 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1441 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1442 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1443 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1444 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1445 project&lt;/a&gt; is working on providing the software and hardware for
1446 making it easy for non-technical people to host their data and
1447 communication at home, and being able to communicate with their
1448 friends and family encrypted and away from prying eyes. It has been
1449 going on for a while, and is slowly progressing towards a new test
1450 release (0.2).&lt;/p&gt;
1451
1452 &lt;p&gt;And what day could be better than the Pi day to announce that the
1453 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1454 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1455 system), and can also be installed using a Debian installer preseed
1456 file. The Debian based Freedombox is now based on Debian Jessie,
1457 where most of the needed packages used are already present. Only one,
1458 the freedombox-setup package, is missing. To try to build your own
1459 boot image to test the current status, fetch the freedom-maker scripts
1460 and build using
1461 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1462 with a user with sudo access to become root:
1463
1464 &lt;pre&gt;
1465 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1466 freedom-maker
1467 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1468 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1469 u-boot-tools
1470 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1471 &lt;/pre&gt;
1472
1473 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1474 devices. See the README for more details on the build. If you do not
1475 want all three images, trim the make line. But note that thanks to &lt;a
1476 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1477 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1478 kpartx call.&lt;/p&gt;
1479
1480 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1481 method, boot a Debian Wheezy ISO and use this boot argument to load
1482 the preseed values:&lt;/p&gt;
1483
1484 &lt;pre&gt;
1485 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;
1486 &lt;/pre&gt;
1487
1488 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1489 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1490 currently hang while setting up APT sources. Killing the
1491 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1492 installation will get the installation going. This affect all
1493 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1494
1495 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1496 us get the new release published. :) Please join us on
1497 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1498 irc.debian.org)&lt;/a&gt; and
1499 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1500 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1501 </description>
1502 </item>
1503
1504 <item>
1505 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1506 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1507 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1508 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1509 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1510 innetgr tools, because I needed them in
1511 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1512 ng-utils, and it has served me well. I placed the project under the
1513 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1514 repository. But many years ago, the CVS repository was dropped (lost,
1515 not migrated to new hardware, not sure), and the project have lacked a
1516 proper home since then.&lt;/p&gt;
1517
1518 &lt;p&gt;Last summer, I had a look at the package and made a new release
1519 fixing a irritating crash bug, but was unable to store the changes in
1520 a proper source control system. I applied for a project on
1521 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1522 to follow up on it. Until today. :)&lt;/p&gt;
1523
1524 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1525 now have a new home, and a git repository with the highlight of the
1526 history of the project. I published all release tarballs and imported
1527 them into the git repository. As the project is really stable and not
1528 expected to gain new features any time soon, I decided to make a new
1529 release and call it 1.0. Visit the new project home on
1530 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1531 if you want to check it out. The new version is also uploaded into
1532 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1533 </description>
1534 </item>
1535
1536 <item>
1537 <title>Testing sysvinit from experimental in Debian Hurd</title>
1538 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1539 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1540 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1541 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1542 their changes into sysvinit, to allow them to use the normal sysvinit
1543 boot system instead of their old one. This follow up on the
1544 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1545 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1546 get Debian on Hurd working more like Debian on Linux. To get started,
1547 I downloaded a prebuilt hard disk image from
1548 &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;,
1549 and started it using virt-manager.&lt;/p&gt;
1550
1551 &lt;p&gt;The first think I had to do after logging in (root without any
1552 password) was to get the network operational. I followed
1553 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1554 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1555 commands as root to get the machine to accept a IP address from the
1556 kvm internal DHCP server:&lt;/p&gt;
1557
1558 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1559 settrans -fgap /dev/netdde /hurd/netdde
1560 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1561 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1562 dhclient /dev/eth0
1563 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1564
1565 &lt;p&gt;After this, the machine had internet connectivity, and I could
1566 upgrade it and install the sysvinit packages from experimental and
1567 enable it as the default boot system in Hurd.&lt;/p&gt;
1568
1569 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1570 running on the machine it for ssh login to work a password need to be
1571 set. Also, note that a bug somewhere in openssh on Hurd block
1572 compression from working. Remember to turn that off on the client
1573 side.&lt;/p&gt;
1574
1575 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1576 stuff:&lt;/p&gt;
1577
1578 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1579 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1580 deb http://http.debian.net/debian/ experimental main
1581 EOF
1582 apt-get update
1583 apt-get dist-upgrade
1584 apt-get install -t experimental initscripts sysv-rc sysvinit \
1585 sysvinit-core sysvinit-utils
1586 update-alternatives --config runsystem
1587 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1588
1589 &lt;p&gt;To reboot after switching boot system, you have to use
1590 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1591 yet a sysvinit process able to receive the signals from the normal
1592 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1593 upgrading every package and rebooting, the network come up with DHCP
1594 after boot as it should, and the settrans/pkill hack mentioned at the
1595 start is no longer needed. But for some strange reason, there are no
1596 longer any login prompt in the virtual console, so I logged in using
1597 ssh instead.
1598
1599 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1600 fail some times. No idea what the cause is, but hope the Hurd porters
1601 figure it out. At least Justus said on IRC (#debian-hurd on
1602 irc.debian.org) that they are aware of the problem. A way to reduce
1603 the impact is to upgrade to the Hurd packages built by Justus by
1604 adding this repository to the machine:&lt;/p&gt;
1605
1606 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1607 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1608 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1609 EOF
1610 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1611
1612 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1613 http://ftp.debian-ports.org/debian, because some of the packages in
1614 unstable do not yet include the required patches that are lingering in
1615 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1616
1617 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1618 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1619 i emacs - GNU Emacs editor (metapackage)
1620 i gdb - GNU Debugger
1621 i hurd-recommended - Miscellaneous translators
1622 i isc-dhcp-client - ISC DHCP client
1623 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1624 i libc-bin - Embedded GNU C Library: Binaries
1625 i libc-dev-bin - Embedded GNU C Library: Development binaries
1626 i libc0.3 - Embedded GNU C Library: Shared libraries
1627 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1628 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1629 i multiarch-support - Transitional package to ensure multiarch compatibilit
1630 i A x11-common - X Window System (X.Org) infrastructure
1631 i xorg - X.Org X Window System
1632 i A xserver-xorg - X.Org X server
1633 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1634 #
1635 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1636
1637 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1638 X.org did not work out of the box and I never took the time to follow
1639 the porters instructions to fix it. This time I was interested in the
1640 command line stuff.&lt;p&gt;
1641 </description>
1642 </item>
1643
1644 <item>
1645 <title>New chrpath release 0.16</title>
1646 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1647 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1648 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1649 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1650 find problems in C, C++ and Java code using static source code
1651 analysis. It can detect a lot of different problems, and is very
1652 useful to find memory and locking bugs in the error handling part of
1653 the source. The company behind it provide
1654 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1655 a community service&lt;/a&gt;, and many hundred free software projects are
1656 already checked. A few days ago I decided to have a closer look at
1657 the Coverity system, and discovered that the
1658 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1659 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1660 projects I am involved with was already registered. But these are
1661 fairly big, and I would also like to have a small and easy project to
1662 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1663 checking of the chrpath project&lt;/a&gt;. It was
1664 added to the checker and discovered seven potential defects. Six of
1665 these were real, mostly resource &quot;leak&quot; when the program detected an
1666 error. Nothing serious, as the resources would be released a fraction
1667 of a second later when the program exited because of the error, but it
1668 is nice to do it right in case the source of the program some time in
1669 the future end up in a library. Having fixed all defects and added
1670 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1671 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1672 publish a new release. These are the release notes:&lt;/p&gt;
1673
1674 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1675
1676 &lt;ul&gt;
1677
1678 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1679 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1680 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1681
1682 &lt;/ul&gt;
1683
1684 &lt;p&gt;You can
1685 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1686 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1687 project if something is wrong with the new release. The test suite
1688 did not discover any old errors, so if you find a new one, please also
1689 include a test suite check.&lt;/p&gt;
1690 </description>
1691 </item>
1692
1693 <item>
1694 <title>New chrpath release 0.15</title>
1695 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1696 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1697 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1698 <description>&lt;p&gt;After many years break from the package and a vain hope that
1699 development would be continued by someone else, I finally pulled my
1700 acts together this morning and wrapped up a new release of chrpath,
1701 the command line tool to modify the rpath and runpath of already
1702 compiled ELF programs. The update was triggered by the persistence of
1703 Isha Vishnoi at IBM, which needed a new config.guess file to get
1704 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1705 is working on. I checked the
1706 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1707 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1708 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1709 packages for interesting patches (failed to find the source from
1710 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1711 These are the release notes:&lt;/p&gt;
1712
1713 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1714
1715 &lt;ul&gt;
1716
1717 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1718 with newer architectures. Thanks to isha vishnoi for the heads
1719 up.&lt;/li&gt;
1720
1721 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1722
1723 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1724 Matthias Klose.&lt;/li&gt;
1725
1726 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1727 Petr Machata found in Fedora.&lt;/li&gt;
1728
1729 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1730 .dynamic is a NULL terminated string. Based on patch found in
1731 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1732
1733 &lt;/ul&gt;
1734
1735 &lt;p&gt;You can
1736 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1737 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1738 project if something is wrong with the new release. The test suite
1739 did not discover any old errors, so if you find a new one, please also
1740 include a testsuite check.&lt;/p&gt;
1741 </description>
1742 </item>
1743
1744 <item>
1745 <title>Debian init.d boot script example for rsyslog</title>
1746 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1747 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1748 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1749 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1750 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1751 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1752 init.d scripts at all. Here is an example init.d script, ie a rewrite
1753 of /etc/init.d/rsyslog:&lt;/p&gt;
1754
1755 &lt;p&gt;&lt;pre&gt;
1756 #!/lib/init/init-d-script
1757 ### BEGIN INIT INFO
1758 # Provides: rsyslog
1759 # Required-Start: $remote_fs $time
1760 # Required-Stop: umountnfs $time
1761 # X-Stop-After: sendsigs
1762 # Default-Start: 2 3 4 5
1763 # Default-Stop: 0 1 6
1764 # Short-Description: enhanced syslogd
1765 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1766 # It is quite compatible to stock sysklogd and can be
1767 # used as a drop-in replacement.
1768 ### END INIT INFO
1769 DESC=&quot;enhanced syslogd&quot;
1770 DAEMON=/usr/sbin/rsyslogd
1771 &lt;/pre&gt;&lt;/p&gt;
1772
1773 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1774 script was 137 lines, and the above is just 15 lines, most of it meta
1775 info/comments.&lt;/p&gt;
1776
1777 &lt;p&gt;How to do this, you ask? Well, one create a new script
1778 /lib/init/init-d-script looking something like this:
1779
1780 &lt;p&gt;&lt;pre&gt;
1781 #!/bin/sh
1782
1783 # Define LSB log_* functions.
1784 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1785 # and status_of_proc is working.
1786 . /lib/lsb/init-functions
1787
1788 #
1789 # Function that starts the daemon/service
1790
1791 #
1792 do_start()
1793 {
1794 # Return
1795 # 0 if daemon has been started
1796 # 1 if daemon was already running
1797 # 2 if daemon could not be started
1798 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1799 || return 1
1800 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1801 $DAEMON_ARGS \
1802 || return 2
1803 # Add code here, if necessary, that waits for the process to be ready
1804 # to handle requests from services started subsequently which depend
1805 # on this one. As a last resort, sleep for some time.
1806 }
1807
1808 #
1809 # Function that stops the daemon/service
1810 #
1811 do_stop()
1812 {
1813 # Return
1814 # 0 if daemon has been stopped
1815 # 1 if daemon was already stopped
1816 # 2 if daemon could not be stopped
1817 # other if a failure occurred
1818 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1819 RETVAL=&quot;$?&quot;
1820 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1821 # Wait for children to finish too if this is a daemon that forks
1822 # and if the daemon is only ever run from this initscript.
1823 # If the above conditions are not satisfied then add some other code
1824 # that waits for the process to drop all resources that could be
1825 # needed by services started subsequently. A last resort is to
1826 # sleep for some time.
1827 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1828 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1829 # Many daemons don&#39;t delete their pidfiles when they exit.
1830 rm -f $PIDFILE
1831 return &quot;$RETVAL&quot;
1832 }
1833
1834 #
1835 # Function that sends a SIGHUP to the daemon/service
1836 #
1837 do_reload() {
1838 #
1839 # If the daemon can reload its configuration without
1840 # restarting (for example, when it is sent a SIGHUP),
1841 # then implement that here.
1842 #
1843 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1844 return 0
1845 }
1846
1847 SCRIPTNAME=$1
1848 scriptbasename=&quot;$(basename $1)&quot;
1849 echo &quot;SN: $scriptbasename&quot;
1850 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1851 script=&quot;$1&quot;
1852 shift
1853 . $script
1854 else
1855 exit 0
1856 fi
1857
1858 NAME=$(basename $DAEMON)
1859 PIDFILE=/var/run/$NAME.pid
1860
1861 # Exit if the package is not installed
1862 #[ -x &quot;$DAEMON&quot; ] || exit 0
1863
1864 # Read configuration variable file if it is present
1865 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
1866
1867 # Load the VERBOSE setting and other rcS variables
1868 . /lib/init/vars.sh
1869
1870 case &quot;$1&quot; in
1871 start)
1872 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
1873 do_start
1874 case &quot;$?&quot; in
1875 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1876 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1877 esac
1878 ;;
1879 stop)
1880 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
1881 do_stop
1882 case &quot;$?&quot; in
1883 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1884 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1885 esac
1886 ;;
1887 status)
1888 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
1889 ;;
1890 #reload|force-reload)
1891 #
1892 # If do_reload() is not implemented then leave this commented out
1893 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
1894 #
1895 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
1896 #do_reload
1897 #log_end_msg $?
1898 #;;
1899 restart|force-reload)
1900 #
1901 # If the &quot;reload&quot; option is implemented then remove the
1902 # &#39;force-reload&#39; alias
1903 #
1904 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
1905 do_stop
1906 case &quot;$?&quot; in
1907 0|1)
1908 do_start
1909 case &quot;$?&quot; in
1910 0) log_end_msg 0 ;;
1911 1) log_end_msg 1 ;; # Old process is still running
1912 *) log_end_msg 1 ;; # Failed to start
1913 esac
1914 ;;
1915 *)
1916 # Failed to stop
1917 log_end_msg 1
1918 ;;
1919 esac
1920 ;;
1921 *)
1922 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
1923 exit 3
1924 ;;
1925 esac
1926
1927 :
1928 &lt;/pre&gt;&lt;/p&gt;
1929
1930 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
1931 lot. I did not really polish the approach, so it might not always
1932 work out of the box, but you get the idea. I did not try very hard to
1933 optimize it nor make it more robust either.&lt;/p&gt;
1934
1935 &lt;p&gt;A better argument for switching init system in Debian than reducing
1936 the size of init scripts (which is a good thing to do anyway), is to
1937 get boot system that is able to handle the kernel events sensibly and
1938 robustly, and do not depend on the boot to run sequentially. The boot
1939 and the kernel have not behaved sequentially in years.&lt;/p&gt;
1940 </description>
1941 </item>
1942
1943 <item>
1944 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
1945 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
1946 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
1947 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
1948 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
1949 remote display access is the preferred solution with oVirt and RedHat
1950 Enterprise Virtualization, and I was sad to discover the other day
1951 that the browser plugin needed to use these systems seamlessly was
1952 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
1953 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
1954 2013-04-01, so I decided to wrap up a package based on the great work
1955 from Cajus Pollmeier and put it in a collab-maint maintained git
1956 repository to get a package I could use. I would very much like
1957 others to help me maintain the package (or just take over, I do not
1958 mind), but as no-one had volunteered so far, I just uploaded it to
1959 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
1960
1961 &lt;p&gt;The source is now available from
1962 &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;
1963 </description>
1964 </item>
1965
1966 <item>
1967 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
1968 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
1969 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
1970 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
1971 <description>&lt;p&gt;The
1972 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
1973 program is a a very nice system to create virtual machine images. It
1974 create a image file, add a partition table, mount it and run
1975 debootstrap in the mounted directory to create a Debian system on a
1976 stick. Yesterday, I decided to try to teach it how to make images for
1977 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1978 of a plan to simplify the build system for
1979 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1980 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1981 the virtualbox images, but its current build system made multistrap
1982 based system for Dreamplug images, and it is lacking support for
1983 Raspberry Pi.&lt;/p&gt;
1984
1985 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1986 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1987 code and adjusted it to be able to build armel images on my amd64
1988 Debian laptop. I ended up giving vmdebootstrap five new options,
1989 allowing me to replicate the image creation process I use to make
1990 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
1991 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
1992 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
1993 call debootstrap with --foreign and to copy the handler into the
1994 generated chroot before running the second stage. This allow
1995 vmdebootstrap to create armel images on an amd64 host. Next I added
1996 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
1997 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
1998 given file system type, allowing me to create an image with a vfat
1999 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2000 variant&lt;/tt&gt; option to allow me to create smaller images without the
2001 Debian base system packages installed. Finally, I added an option
2002 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2003 as a boot loader. It is not needed on the Raspberry Pi and probably
2004 most other non-x86 architectures. The changes were accepted by the
2005 upstream author of vmdebootstrap yesterday and today, and is now
2006 available from
2007 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2008 upstream project page&lt;/a&gt;.&lt;/p&gt;
2009
2010 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2011 create a small script (the customize script) to add the non-free
2012 binary blob needed to boot the Raspberry Pi and the APT source
2013 list:&lt;/p&gt;
2014
2015 &lt;p&gt;&lt;pre&gt;
2016 #!/bin/sh
2017 set -e # Exit on first error
2018 rootdir=&quot;$1&quot;
2019 cd &quot;$rootdir&quot;
2020 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2021 deb http://http.debian.net/debian/ jessie main contrib non-free
2022 EOF
2023 # Install non-free binary blob needed to boot Raspberry Pi. This
2024 # install a kernel somewhere too.
2025 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2026 -O $rootdir/usr/bin/rpi-update
2027 chmod a+x $rootdir/usr/bin/rpi-update
2028 mkdir -p $rootdir/lib/modules
2029 touch $rootdir/boot/start.elf
2030 chroot $rootdir rpi-update
2031 &lt;/pre&gt;&lt;/p&gt;
2032
2033 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2034 to build the image:&lt;/p&gt;
2035
2036 &lt;pre&gt;
2037 sudo ./vmdebootstrap \
2038 --variant minbase \
2039 --arch armel \
2040 --distribution jessie \
2041 --mirror http://http.debian.net/debian \
2042 --image test.img \
2043 --size 600M \
2044 --bootsize 64M \
2045 --boottype vfat \
2046 --log-level debug \
2047 --verbose \
2048 --no-kernel \
2049 --no-extlinux \
2050 --root-password raspberry \
2051 --hostname raspberrypi \
2052 --foreign /usr/bin/qemu-arm-static \
2053 --customize `pwd`/customize \
2054 --package netbase \
2055 --package git-core \
2056 --package binutils \
2057 --package ca-certificates \
2058 --package wget \
2059 --package kmod
2060 &lt;/pre&gt;&lt;/p&gt;
2061
2062 &lt;p&gt;The list of packages being installed are the ones needed by
2063 rpi-update to make the image bootable on the Raspberry Pi, with the
2064 exception of netbase, which is needed by debootstrap to find
2065 /etc/hosts with the minbase variant. I really wish there was a way to
2066 set up an Raspberry Pi using only packages in the Debian archive, but
2067 that is not possible as far as I know, because it boots from the GPU
2068 using a non-free binary blob.&lt;/p&gt;
2069
2070 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2071 probably a few others installed. I have not checked the complete
2072 build dependency list.&lt;/p&gt;
2073
2074 &lt;p&gt;The resulting image will not use the hardware floating point unit
2075 on the Raspberry PI, because the armel architecture in Debian is not
2076 optimized for that use. So the images created will be a bit slower
2077 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2078 </description>
2079 </item>
2080
2081 <item>
2082 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2083 <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>
2084 <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>
2085 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2086 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2087 wider attention. I recommend signing and donating to each one of
2088 these. :)&lt;/p&gt;
2089
2090 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2091 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2092 Women program which is a Google Summer of Code like initiative to get
2093 more women involved in free software. One debian sponsor has offered
2094 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2095 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2096 hope you will to. :)&lt;/p&gt;
2097
2098 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2099 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2100 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2101 take place these days, and their need to fund the work. I&#39;ve already
2102 donated. Are you next?&lt;/p&gt;
2103
2104 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2105 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2106 statement under the heading
2107 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2108 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2109 Norwegian government. So far 499 signatures. I hope you will sign it
2110 too.&lt;/p&gt;
2111 </description>
2112 </item>
2113
2114 <item>
2115 <title>Videos about the Freedombox project - for inspiration and learning</title>
2116 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2118 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2119 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2120 project&lt;/a&gt; have been going on for a while, and have presented the
2121 vision, ideas and solution several places. Here is a little
2122 collection of videos of talks and presentation of the project.&lt;/p&gt;
2123
2124 &lt;ul&gt;
2125
2126 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2127 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2128
2129 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2130 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2131
2132 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2133 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2134 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2135 (Youtube)&lt;/li&gt;
2136
2137 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2138 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2139
2140 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2141 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2142
2143 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2144 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2145 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2146
2147 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2148 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2149 (Youtube)&lt;/li&gt;
2150
2151 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2152 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2153
2154 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2155 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2156
2157 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2158 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2159 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2160
2161 &lt;/ul&gt;
2162
2163 &lt;p&gt;A larger list is available from
2164 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2165 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2166
2167 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2168 Jessie is coming along quite well, and soon both Owncloud and using
2169 Tor should be available for testers of the Freedombox solution. :) In
2170 a few weeks I hope everything needed to test it is included in Debian.
2171 The withsqlite package is already in Debian, and the plinth package is
2172 pending in NEW. The third and vital part of that puzzle is the
2173 metapackage/setup framework, which is still pending an upload. Join
2174 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2175 (#freedombox on irc.debian.org)&lt;/a&gt; and
2176 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2177 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2178 </description>
2179 </item>
2180
2181 <item>
2182 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2183 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2185 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2186 <description>&lt;p&gt;I was introduced to the
2187 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2188 in 2010, when Eben Moglen presented his vision about serving the need
2189 of non-technical people to keep their personal information private and
2190 within the legal protection of their own homes. The idea is to give
2191 people back the power over their network and machines, and return
2192 Internet back to its intended peer-to-peer architecture. Instead of
2193 depending on a central service, the Freedombox will give everyone
2194 control over their own basic infrastructure.&lt;/p&gt;
2195
2196 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2197 taken priority. But this summers nasty news about the misuse of trust
2198 and privilege exercised by the &quot;western&quot; intelligence gathering
2199 communities increased my eagerness to contribute to a point where I
2200 actually started working on the project a while back.&lt;/p&gt;
2201
2202 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2203 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2204 create a simple and cheap Debian based appliance that anyone can hook
2205 up in their home and get access to secure and private services and
2206 communication. The initial deployment platform have been the
2207 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2208 which is a piece of hardware I do not own. So to be able to test what
2209 the current Freedombox setup look like, I had to come up with a way to install
2210 it on some hardware I do have access to. I have rewritten the
2211 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2212 image build framework to use .deb packages instead of only copying
2213 setup into the boot images, and thanks to this rewrite I am able to
2214 set up any machine supported by Debian Wheezy as a Freedombox, using
2215 the previously mentioned deb (and a few support debs for packages
2216 missing in Debian).&lt;/p&gt;
2217
2218 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2219 scripts
2220 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2221 and a administrative web interface
2222 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2223 withsqlite), as well as a privacy enhancing proxy based on
2224 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2225 (freedombox-privoxy). There is also a web/javascript based XMPP
2226 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2227 trying (unsuccessfully so far) to talk to the XMPP server
2228 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2229 web interface is pluggable, and the goal is to use it to enable OpenID
2230 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2231 this is really working yet, see
2232 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2233 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2234 on github at the moment. The HTTP proxy is operational out of the
2235 box, and the admin web interface can be used to add/remove plinth
2236 users. I&#39;ve not been able to do anything else with it so far, but
2237 know there are several branches spread around github and other places
2238 with lots of half baked features.&lt;/p&gt;
2239
2240 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2241 following recipes should work to give you a test machine to poke
2242 at.&lt;/p&gt;
2243
2244 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2245
2246 &lt;ol&gt;
2247
2248 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2249 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2250 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2251 to the Debian installer:&lt;p&gt;
2252 &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;
2253
2254 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2255 install on.&lt;/li&gt;
2256
2257 &lt;li&gt;When the installation is finished and the machine have rebooted a
2258 few times, your Freedombox is ready for testing.&lt;/li&gt;
2259
2260 &lt;/ol&gt;
2261
2262 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2263
2264 &lt;ol&gt;
2265
2266 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2267 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2268 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2269 &lt;pre&gt;
2270 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2271 &lt;/pre&gt;&lt;/li&gt;
2272 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2273 &lt;pre&gt;
2274 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2275 apt-key add -
2276 apt-get update
2277 apt-get install freedombox-setup
2278 /usr/lib/freedombox/setup
2279 &lt;/pre&gt;&lt;/li&gt;
2280 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2281
2282 &lt;/ol&gt;
2283
2284 &lt;p&gt;You can test it on other architectures too, but because the
2285 freedombox-privoxy package is binary, it will only work as intended on
2286 the architectures where I have had time to build the binary and put it
2287 in my APT repository. But do not let this stop you. It is only a
2288 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2289
2290 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2291 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2292 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2293 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2294
2295 &lt;p&gt;Please let me know if this works for you, or if you have any
2296 problems. We gather on the IRC channel
2297 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2298 irc.debian.org and the
2299 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2300 mailing list&lt;/a&gt;.&lt;/p&gt;
2301
2302 &lt;p&gt;Once you get your freedombox operational, you can visit
2303 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2304 welcome screen (dead end - do not be surprised if you are unable to
2305 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2306 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2307 default password is &#39;secret&#39;.&lt;/p&gt;
2308 </description>
2309 </item>
2310
2311 <item>
2312 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2313 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2314 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2315 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2316 <description>&lt;p&gt;Earlier, I reported about
2317 &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
2318 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2319 told by IBM that the original disk should be thrown away. And as
2320 there no longer was a problem if I bricked the firmware, I decided
2321 today to try to install Intel firmware to replace the Lenovo firmware
2322 currently on the disk.&lt;/p&gt;
2323
2324 &lt;p&gt;I searched the Intel site for firmware, and found
2325 &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;
2326 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2327 according to the site should contain the latest firmware for SSD
2328 disks. I inserted the broken disk in one of my spare laptops and
2329 booted the ISO from a USB stick. The disk was recognized, but the
2330 program claimed the newest firmware already were installed and refused
2331 to insert any Intel firmware. So no change, and the disk is still
2332 unable to handle write load. :( I guess the only way to get them
2333 working would be if Lenovo releases new firmware. No idea how likely
2334 that is. Anyway, just blogging about this test for completeness. I
2335 got a working Samsung disk, and see no point in spending more time on
2336 the broken disks.&lt;/p&gt;
2337 </description>
2338 </item>
2339
2340 <item>
2341 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2342 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2343 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2344 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2345 <description>&lt;p&gt;Today I switched to
2346 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2347 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2348 my new Thinkpad X230, which was delivered with an
2349 &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
2350 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2351 sustained writes. My hardware supplier have been very forthcoming in
2352 trying to find a solution, and after first trying with another
2353 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2354 disk instead to fix it once and for all. The Samsung disk survived
2355 the installation of Debian with encrypted disks (filling the disk with
2356 random data during installation killed the first two), and I thus
2357 decided to trust it with my data. I have installed it as a Debian Edu
2358 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2359 server at home using Kerberos and LDAP, and will use it as my work
2360 station from now on.&lt;/p&gt;
2361
2362 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2363 Debian Wheezy default installation need to be tuned a bit to increase
2364 performance and increase life time of the disk. The Linux kernel and
2365 user space applications do not yet adjust automatically to such
2366 environment. To make it easier for my self, I created a draft Debian
2367 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2368 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2369 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2370 is set up to adjust the setup of the machine by just installing the
2371 package. If there is any non-SSD disk in the machine, the package
2372 will refuse to install, as I did not try to write any logic to sort
2373 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2374
2375 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2376 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2377 where I set up the machine with one large encrypted partition (in
2378 addition to /boot), put LVM on top of this and set up partitions on
2379 top of this again. See the README file in the package source for the
2380 references I used to pick the settings. At the moment these
2381 parameters are tuned:&lt;/p&gt;
2382
2383 &lt;ul&gt;
2384
2385 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2386 (adding discard to /etc/crypttab)&lt;/li&gt;
2387
2388 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2389 this case a cryptsetup partition) by changing issue_discards from
2390 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2391
2392 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2393 systems.&lt;/li&gt;
2394
2395 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2396 /etc/fstab.&lt;/li&gt;
2397
2398 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2399
2400 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2401 cron.daily).&lt;/li&gt;
2402
2403 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2404 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2405
2406 &lt;/ul&gt;
2407
2408 &lt;p&gt;During installation, I cancelled the part where the installer fill
2409 the disk with random data, as this would kill the SSD performance for
2410 little gain. My goal with the encrypted file system is to ensure
2411 those stealing my laptop end up with a brick and not a working
2412 computer. I have no hope in keeping the really resourceful people
2413 from getting the data on the disk (see
2414 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2415 Thus I concluded that adding the discard option to crypttab is the
2416 right thing to do.&lt;/p&gt;
2417
2418 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2419 it for SSD, but others recommended deadline and a benchmark I found
2420 indicated that deadline might be better for interactive use.&lt;/p&gt;
2421
2422 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2423 and ext4, but read that it would give a performance hit ever time a
2424 file is removed, and thought it best to that that slowdown once a day
2425 instead of during my work.&lt;/p&gt;
2426
2427 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2428 this is already done by Debian Edu.&lt;/p&gt;
2429
2430 &lt;p&gt;I have not yet started on the user space tuning. I expect
2431 iceweasel need some tuning, and perhaps other applications too, but
2432 have not yet had time to investigate those parts.&lt;/p&gt;
2433
2434 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2435 there.&lt;/p&gt;
2436
2437 &lt;p&gt;As for the answer to the question in the title of this blog post,
2438 as far as I know, the only solution I know about is to replace the
2439 disk. It might be possible to flash it with Intel firmware instead of
2440 the Lenovo firmware. But I have not tried and did not want to do so
2441 without approval from Lenovo as I wanted to keep the warranty on the
2442 disk until a solution was found and they wanted the broken disks
2443 back.&lt;/p&gt;
2444 </description>
2445 </item>
2446
2447 <item>
2448 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2449 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2450 <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>
2451 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2452 <description>&lt;p&gt;A few days ago, I wrote about
2453 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2454 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2455 was dying during installation because it is unable to cope with
2456 sustained write. My supplier is in contact with
2457 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2458 replacement disk to try to fix the problem. They decided to send an
2459 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2460
2461 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2462 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2463 same firmware version as the original. This time my hope raised
2464 slightly as the installation progressed, as the original disk used to
2465 die after 4-7% of the disk was written to, while this time it kept
2466 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2467 died again and I was back on square one. I still do not have a new
2468 laptop with a disk I can trust. I can not live with a disk that might
2469 lock up when I download a new
2470 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2471 other large files. I look forward to hearing from my supplier with
2472 the next proposal from Lenovo.&lt;/p&gt;
2473
2474 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2475 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2476 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2477 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2478 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2479 P/N 45N8295, P0C38732.&lt;/p&gt;
2480
2481 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2482 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2483 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2484 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2485 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2486 P/N 45N8295, P0C38732.&lt;/p&gt;
2487
2488 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2489 SA, date and WNPP values. Mentioning all the details here in case
2490 someone is able to use the information to find a way to identify the
2491 failing disk among working ones (if any such working disk actually
2492 exist).&lt;/p&gt;
2493 </description>
2494 </item>
2495
2496 <item>
2497 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2498 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2499 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2500 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2501 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2502 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2503 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2504 member assosiation NUUG&lt;/a&gt; and
2505 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2506 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2507 Bitraf&lt;/a&gt;.&lt;/p&gt;
2508
2509 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2510 welcome, and there is no fee to participate. There is on the other
2511 hand limited space, and only room for 30 people. Please put your name
2512 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2513 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2514 </description>
2515 </item>
2516
2517 <item>
2518 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2519 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2520 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2521 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2522 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2523 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2524 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2525 time to spend on it, and it took a while to find a model I believe
2526 will do the job, but two days ago the replacement finally arrived. I
2527 ended up picking a
2528 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2529 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2530 a roaming workstation, and it seemed to work flawlessly. But my
2531 second installation with encrypted disk was not as successful. More
2532 on that below.&lt;/p&gt;
2533
2534 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2535 important requirements (robust and with a good keyboard) are never
2536 listed in the feature list. But I did get good help from the search
2537 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2538 allowed me to limit the list of interesting laptops based on my other
2539 requirements. A bit surprising that SSD disk are not disks according
2540 to that search interface, so I had to drop specifying the number of
2541 disks from my search parameters. I also asked around among friends to
2542 get their impression on keyboards and robustness.&lt;/p&gt;
2543
2544 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2545 X41. I am not quite convinced about the keyboard, as it is
2546 significantly wider than my old keyboard, and I have to stretch my
2547 hand a lot more to reach the edges. But the key response is fairly
2548 good and the individual key shape is fairly easy to handle, so I hope
2549 I will get used to it. My old X40 was starting to fail, and I really
2550 needed a new laptop now. :)&lt;/p&gt;
2551
2552 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2553 visit to the BIOS during boot it disable it.&lt;/p&gt;
2554
2555 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2556 lock up during load. And this happen when installing Debian Wheezy
2557 with encrypted disk, while the disk is being filled with random data.
2558 I also tested to install Ubuntu Raring, and it happen there too if I
2559 reenable the code to fill the disk with random data (it is disabled by
2560 default in Ubuntu). And the bug with is already known. It was
2561 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2562 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2563 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2564 kernel developers as
2565 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2566 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2567 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2568 Lenovo forums, both for
2569 &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
2570 2012-11-10&lt;/a&gt; and for
2571 &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
2572 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2573 reports state that the disk lock up during use if many writes are done
2574 on the disk, so it is much no use to work around the installation
2575 problem and end up with a computer that can lock up at any moment.
2576 There is even a
2577 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2578 available&lt;/a&gt; that will lock up the hard drive after running a few
2579 minutes by writing to a file.&lt;/p&gt;
2580
2581 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2582 contacting PCHELP Norway (request 01D1FDP) which handle support
2583 requests for Lenovo, his first suggestion was to upgrade the disk
2584 firmware. Unfortunately there is no newer firmware available from
2585 Lenovo, as my disk already have the most recent one (version LF1i). I
2586 hope to hear more from him today and hope the problem can be
2587 fixed. :)&lt;/p&gt;
2588 </description>
2589 </item>
2590
2591 <item>
2592 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2593 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2594 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2595 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2596 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2597 trusty old Thinkpad X41. Unfortunately I did not have much time to
2598 spend on it, but today the replacement finally arrived. I ended up
2599 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2600 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2601 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2602 this, it is installing what I hope will be a more final installation,
2603 with a encrypted hard drive to ensure any dope head stealing it end up
2604 with an expencive door stop.&lt;/p&gt;
2605
2606 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2607 important requirements (robust and with a good keyboard) are never
2608 listed in the feature list. But I did get good help from the search
2609 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2610 allowed me to limit the list of interesting laptops based on my other
2611 requirements. A bit surprising that SSD disk are not disks, so I had
2612 to drop number of disks from my search parameters.&lt;/p&gt;
2613
2614 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2615 wider than my old keyboard, and I have to stretch my hand a lot more
2616 to reach the edges. But the key response is fairly good and the
2617 individual key shape is fairly easy to handle, so I hope I will get
2618 used to it. My old X40 was starting to fail, and I really needed a
2619 new laptop now. :)&lt;/p&gt;
2620
2621 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2622 </description>
2623 </item>
2624
2625 <item>
2626 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2627 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2628 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2629 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2630 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2631 perfectly capable of, and I have to do it manually to get things
2632 working. One such task is to find out what firmware packages are
2633 needed to get the hardware on my computer working. Most often this
2634 affect the wifi card, but some times it even affect the RAID
2635 controller or the ethernet card. Today I pushed version 0.4 of the
2636 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2637 including a new script isenkram-autoinstall-firmware handling the
2638 process of asking all the loaded kernel modules what firmware files
2639 they want, find debian packages providing these files and install the
2640 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2641
2642 &lt;p&gt;&lt;pre&gt;
2643 # isenkram-autoinstall-firmware
2644 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2645 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2646 info: locating packages with the requested firmware files
2647 info: Updating APT sources after adding non-free APT source
2648 info: trying to install firmware-ipw2x00
2649 firmware-ipw2x00
2650 firmware-ipw2x00
2651 Preconfiguring packages ...
2652 Selecting previously deselected package firmware-ipw2x00.
2653 (Reading database ... 259727 files and directories currently installed.)
2654 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2655 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2656 #
2657 &lt;/pre&gt;&lt;/p&gt;
2658
2659 &lt;p&gt;When all the requested firmware is present, a simple message is
2660 printed instead:&lt;/p&gt;
2661
2662 &lt;p&gt;&lt;pre&gt;
2663 # isenkram-autoinstall-firmware
2664 info: did not find any firmware files requested by loaded kernel modules. exiting
2665 #
2666 &lt;/pre&gt;&lt;/p&gt;
2667
2668 &lt;p&gt;It could use some polish, but it is already working well and saving
2669 me some time when setting up new machines. :)&lt;/p&gt;
2670
2671 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2672 kernel modules, and look up each one of them using modinfo, to find
2673 the firmware files listed in the module meta-information. Next, it
2674 download the Contents file from a nearby APT mirror, and search for
2675 the firmware files in this file to locate the package with the
2676 requested firmware file. If the package is in the non-free section, a
2677 non-free APT source is added and the package is installed using
2678 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2679 machine.&lt;/p&gt;
2680
2681 &lt;p&gt;I hope someone find time to implement a more polished version of
2682 this script as part of the hw-detect debian-installer module, to
2683 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2684 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2685 firmware during a PXE install when the packages already are available
2686 from the nearby Debian mirror.&lt;/p&gt;
2687 </description>
2688 </item>
2689
2690 <item>
2691 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2692 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2693 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2694 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2695 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2696 the screen just turn black when Linux boot, either during installation
2697 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2698 last few years, but only recently understood the cause. I&#39;ve seen it
2699 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2700 The reason seem to be in the wiring of some laptops. The system to
2701 control the screen background light is inverted, so when Linux try to
2702 turn the brightness fully on, it end up turning it off instead. I do
2703 not know which Linux drivers are affected, but this post is about the
2704 i915 driver used by the
2705 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2706 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2707
2708 &lt;p&gt;The problem can be worked around two ways. Either by adding
2709 i915.invert_brightness=1 as a kernel option, or by adding a file in
2710 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2711 option when it load the i915 kernel module. On Debian and Ubuntu, it
2712 can be done by running these commands as root:&lt;/p&gt;
2713
2714 &lt;pre&gt;
2715 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2716 update-initramfs -u -k all
2717 &lt;/pre&gt;
2718
2719 &lt;p&gt;Since March 2012 there is
2720 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2721 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2722 hardware have this problem, and get the driver to invert the
2723 brightness setting automatically. To use it, one need to add a row in
2724 &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
2725 intel_quirks array&lt;/a&gt; in the driver source
2726 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2727 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2728 number (vendor number 8086 is assumed) and subdevice vendor and device
2729 number.&lt;/p&gt;
2730
2731 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2732 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2733
2734 &lt;p&gt;&lt;pre&gt;
2735 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2736 3rd Gen Core processor Graphics Controller [8086:0156] \
2737 (rev 09) (prog-if 00 [VGA controller])
2738 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2739 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2740 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2741 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2742 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2743 Latency: 0
2744 Interrupt: pin A routed to IRQ 42
2745 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2746 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2747 Region 4: I/O ports at 4000 [size=64]
2748 Expansion ROM at &lt;unassigned&gt; [disabled]
2749 Capabilities: &lt;access denied&gt;
2750 Kernel driver in use: i915
2751 &lt;/pre&gt;&lt;/p&gt;
2752
2753 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2754
2755 &lt;p&gt;&lt;pre&gt;
2756 struct intel_quirk intel_quirks[] = {
2757 ...
2758 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2759 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2760 ...
2761 }
2762 &lt;/pre&gt;&lt;/p&gt;
2763
2764 &lt;p&gt;According to the kernel module instructions (as seen using
2765 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2766 invert_brightness flag should be sent to the
2767 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2768 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2769 developers. But my email about the laptop sent 2013-06-03 have not
2770 yet shown up in
2771 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2772 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2773 emails from non-subscribers. Because of this, I sent my patch also to
2774 the Debian bug tracking system instead as
2775 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2776 sure the patch is not lost.&lt;/p&gt;
2777
2778 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2779 with this problem working properly with Linux. If you use Gnome, your
2780 worries should be over at this point. But if you use KDE, there is
2781 something in KDE ignoring the invert_brightness setting and turning on
2782 the screen during login. I&#39;ve reported it to Debian as
2783 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2784 have no idea yet how to figure out exactly what subsystem is doing
2785 this. Perhaps you can help? Perhaps you know what the Gnome
2786 developers did to handle this, and this can give a clue to the KDE
2787 developers? Or you know where in KDE the screen brightness is changed
2788 during login? If so, please update the BTS report (or get in touch if
2789 you do not know how to update BTS).&lt;/p&gt;
2790
2791 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2792 acpi_backlight=vendor, to disable ACPI backlight support completely,
2793 as the ACPI information on the machine is trash and it is better to
2794 leave it to the intel video driver to control the screen
2795 backlight.&lt;/p&gt;
2796 </description>
2797 </item>
2798
2799 <item>
2800 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2801 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2802 <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>
2803 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2804 <description>&lt;p&gt;Two days ago, I asked
2805 &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
2806 I could install Linux on a Packard Bell EasyNote LV computer
2807 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2808 with the obstacles put in the way of Linux users on a laptop with UEFI
2809 and Windows 8.&lt;/p&gt;
2810
2811 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2812 secure booting or fast boot. I suspect fast boot was the problem,
2813 causing the firmware to boot directly from HD without considering any
2814 key presses and alternative devices, but do not know UEFI settings
2815 enough to tell.&lt;/p&gt;
2816
2817 &lt;p&gt;There is no way to install Linux on the machine in question without
2818 opening the box and disconnecting the hard drive! This is as far as I
2819 can tell, the only way to get access to the firmware setup menu
2820 without accepting the Windows 8 license agreement. I am told (and
2821 found description on how to) that it is possible to configure the
2822 firmware setup once booted into Windows 8. But as I believe the terms
2823 of that agreement are completely unacceptable, accepting the license
2824 was never an alternative. I do not enter agreements I do not intend
2825 to follow.&lt;/p&gt;
2826
2827 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2828 waste many hours on this, but luckily there was a way to get it to
2829 work. But I would not recommend it to anyone planning to run Linux on
2830 it, and I have become sceptical to Windows 8 certified laptops. Is
2831 this the way Linux will be forced out of the market place, by making
2832 it close to impossible for &quot;normal&quot; users to install Linux without
2833 accepting the Microsoft Windows license terms? Or at least not
2834 without risking to loose the warranty?&lt;/p&gt;
2835
2836 &lt;p&gt;I&#39;ve updated the
2837 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2838 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2839 do not have to struggle as much as I did to get Linux into the
2840 machine.&lt;/p&gt;
2841
2842 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2843 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2844 </description>
2845 </item>
2846
2847 <item>
2848 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2849 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2850 <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>
2851 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2852 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2853 new laptops for my parents and a few others. I bought Packard Bell
2854 Easynote LV to run Kubuntu on and use as their home computer. But I
2855 am completely unable to figure out how to install Linux on it. The
2856 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2857 instead of a BIOS to boot.&lt;/p&gt;
2858
2859 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
2860 to get it to boot the Linux installer from my USB stick. I have yet
2861 to try the DVD install, and still hope it will work. when I turn on
2862 the computer, there is no information on what buttons to press to get
2863 the normal boot menu. I expect to get some boot menu to select PXE or
2864 USB stick booting. When booting, it first ask for the language to
2865 use, then for some regional settings, and finally if I will accept the
2866 Windows 8 terms of use. As these terms are completely unacceptable to
2867 me, I have no other choice but to turn off the computer and try again
2868 to get it to boot the Linux installer.&lt;/p&gt;
2869
2870 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
2871 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2872 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
2873 installed on this machine, please get in touch or update that wiki
2874 page. If I can&#39;t find a way to install Linux, I will have to return
2875 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
2876
2877 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
2878 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
2879 on new Laptops?&lt;/p&gt;
2880 </description>
2881 </item>
2882
2883 <item>
2884 <title>How to transform a Debian based system to a Debian Edu installation</title>
2885 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
2886 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
2887 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
2888 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
2889 an operating system based on Debian intended for use in schools. It
2890 contain a turn-key solution for the computer network provided to
2891 pupils in the primary schools. It provide both the central server,
2892 network boot servers and desktop environments with heaps of
2893 educational software. The project was founded almost 12 years ago,
2894 2001-07-02. If you want to support the project, which is in need for
2895 cash to fund developer gatherings and other project related activity,
2896 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
2897 donate some money&lt;/a&gt;.
2898
2899 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
2900 lists and elsewhere, is the question on how to transform a Debian or
2901 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
2902 hard, and last week I wrote a script to replicate the steps done by
2903 the Debian Edu installer.&lt;/p&gt;
2904
2905 &lt;p&gt;The script,
2906 &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;
2907 in the debian-edu-config package, will go through these six steps and
2908 transform an existing Debian Wheezy or Ubuntu (untested) installation
2909 into a Debian Edu Workstation:&lt;/p&gt;
2910
2911 &lt;ol&gt;
2912
2913 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
2914 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
2915 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
2916 our configuration.&lt;/li&gt;
2917 &lt;li&gt;Preseed debconf database with profile setup in
2918 /etc/debian-edu/config, and run tasksel to install packages
2919 according to the profile specified in the config above,
2920 overriding some of the Debian automation machinery.&lt;/li&gt;
2921 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
2922 that could not be done using preseeding.&lt;/li&gt;
2923 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
2924
2925 &lt;/ol&gt;
2926
2927 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
2928 replicated like this. Disk partitioning and LVM setup, for example.
2929 So this script just assume there is enough disk space to install all
2930 the needed packages.&lt;/p&gt;
2931
2932 &lt;p&gt;The script was created to help a Debian Edu student working on
2933 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
2934 Debian Edu client, and using it he can take the existing
2935 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
2936 transform it into a fully functioning Debian Edu Workstation (or
2937 Roaming Workstation, or whatever :).&lt;/p&gt;
2938
2939 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
2940 If a LXDE based Roaming workstation is wanted instead, modify the
2941 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
2942
2943 &lt;p&gt;&lt;pre&gt;
2944 PROFILE=&quot;Roaming-Workstation&quot;
2945 DESKTOP=&quot;lxde&quot;
2946 &lt;/pre&gt;&lt;/p&gt;
2947
2948 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
2949 the cloud, by starting with a virtual Debian installation at some
2950 virtual hosting service and setting up all the services on first
2951 boot.&lt;/p&gt;
2952 </description>
2953 </item>
2954
2955 <item>
2956 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
2957 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
2958 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
2959 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
2960 <description>&lt;P&gt;In January,
2961 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
2962 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
2963 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
2964 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
2965 marvellous construction system from Denmark. We also created
2966 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
2967 a place to take notes and write down our plans and hopes. And several
2968 people showed up to help. I was very happy to see the effect of my
2969 call. Since the small start, we have a debtags tag
2970 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
2971 tag for LEGO related packages, and now count 10 packages related to
2972 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
2973
2974 &lt;p&gt;&lt;table&gt;
2975 &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;
2976 &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;
2977 &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;
2978 &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;
2979 &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;
2980 &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;
2981 &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;
2982 &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;
2983 &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;
2984 &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;
2985 &lt;/table&gt;&lt;/p&gt;
2986
2987 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2988 currently available in Jessie/testing. leocad is so far only
2989 available in experimental.&lt;/p&gt;
2990
2991 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
2992 adding the rest of the great free software tools available on Linux
2993 for LEGO designers.&lt;/p&gt;
2994 </description>
2995 </item>
2996
2997 <item>
2998 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
2999 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3000 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3001 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3002 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3003 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3004 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3005 Debian release, and I expect to move my machines at home over to it fairly
3006 soon.&lt;/p&gt;
3007
3008 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3009 in particular make me very happy to see included. The
3010 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3011 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3012 included for the first time. Alongside similar programs like
3013 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3014 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3015 it allow for visual programming where syntax errors can not happen,
3016 and a friendly programming environment for learning to control the
3017 computer. Scratch will also be included in the next release of Debian
3018 Edu.&lt;/a&gt;
3019
3020 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3021 Edu/Skolelinux release too. The
3022 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3023 alpha release&lt;/a&gt; went out last week, and the next should soon
3024 follow.&lt;p&gt;
3025 </description>
3026 </item>
3027
3028 <item>
3029 <title>Isenkram 0.2 finally in the Debian archive</title>
3030 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3032 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3033 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3034 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3035 for many months. I uploaded it to the Debian experimental suite
3036 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3037
3038 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3039 install to work with a pluggable hardware device. The suggestion pop
3040 up when the device is plugged in. For example if a Lego Mindstorm NXT
3041 is inserted, it will suggest to install the program needed to program
3042 the NXT controller. Give it a go, and report bugs and suggestions to
3043 BTS. :)&lt;/p&gt;
3044 </description>
3045 </item>
3046
3047 <item>
3048 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3049 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3050 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3051 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3052 <description>&lt;p&gt;My
3053 &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
3054 bitcoin related blog post&lt;/a&gt; mentioned that the new
3055 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3056 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3057 2013-01-19, and have been available in unstable since then. It was
3058 automatically copied to Ubuntu, and is available in their Raring
3059 version too.&lt;/p&gt;
3060
3061 &lt;p&gt;But there is a strange problem with the build that block this new
3062 version from being available on the i386 and kfreebsd-i386
3063 architectures. For some strange reason, the autobuilders in Debian
3064 for these architectures fail to run the test suite on these
3065 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3066 We are so far unable to reproduce it when building it manually, and
3067 no-one have been able to propose a fix. If you got an idea what is
3068 failing, please let us know via the BTS.&lt;/p&gt;
3069
3070 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3071 I often run low on disk space, is the fact that the client will exit
3072 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3073 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3074 it. :)&lt;/p&gt;
3075
3076 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3077 activities, please send Bitcoin donations to my address
3078 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3079 </description>
3080 </item>
3081
3082 <item>
3083 <title>Welcome to the world, Isenkram!</title>
3084 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3085 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3086 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3087 <description>&lt;p&gt;Yesterday, I
3088 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3089 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3090 pluggable hardware devices, which I
3091 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3092 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3093 up, and caused me to really want to to open up the development to more
3094 people. But before I did this, I want to come up with a sensible name
3095 for this project. Today I finally decided on a new name, and I have
3096 renamed the project from hw-support-handler to this new name. In the
3097 process, I moved the source to git and made it available as a
3098 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3099 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3100 To fetch and build the latest version of the source, use&lt;/p&gt;
3101
3102 &lt;pre&gt;
3103 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3104 cd isenkram &amp;&amp; git-buildpackage -us -uc
3105 &lt;/pre&gt;
3106
3107 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3108 want to hack on the source or improve the package, please go ahead.
3109 But please talk to me first on IRC or via email before you do major
3110 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3111
3112 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3113 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3114 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3115 the German word eisenkram, for those that are familiar with that
3116 word.&lt;/p&gt;
3117
3118 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3119 instructions, to avoid confusing people with an error from the signing
3120 process.&lt;/p&gt;
3121
3122 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3123 clone argument to avoid the need for authentication.&lt;/p&gt;
3124 </description>
3125 </item>
3126
3127 <item>
3128 <title>First prototype ready making hardware easier to use in Debian</title>
3129 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3130 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3131 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3132 <description>&lt;p&gt;Early this month I set out to try to
3133 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3134 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3135 prototype is working, and it is ready for a larger audience. To test
3136 it, fetch the
3137 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3138 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3139 package. You might have to log out and in again activate the
3140 autostart script.&lt;/p&gt;
3141
3142 &lt;p&gt;The design is simple:&lt;/p&gt;
3143
3144 &lt;ul&gt;
3145
3146 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3147 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3148
3149 &lt;li&gt;This program listen for kernel events about new hardware (directly
3150 from the kernel like udev does), not using HAL dbus events as I
3151 initially did.&lt;/li&gt;
3152
3153 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3154 the APT database, a database
3155 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3156 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3157
3158 &lt;li&gt;If a package is mapped to the hardware in question, the package
3159 isn&#39;t installed yet and this is the first time the hardware was
3160 plugged in, show a desktop notification suggesting to install the
3161 package or packages.&lt;/li&gt;
3162
3163 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3164 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3165
3166 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3167 package while showing progress information in a window.&lt;/li&gt;
3168
3169 &lt;/ul&gt;
3170
3171 &lt;p&gt;I still need to come up with a better name for the system. Here
3172 are some screen shots showing the prototype in action. First the
3173 notification, then the password request, and finally the request to
3174 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3175
3176 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3177 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3178 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3179 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3180 &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;
3181
3182 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3183 is already useful. The database of hardware to package mappings also
3184 need more work. It is currently compatible with the Ubuntu way of
3185 storing such information in the package control file, but could be
3186 changed to use other formats instead or in addition to the current
3187 method. I&#39;ve dropped the use of discover for this mapping, as the
3188 modalias approach is more flexible and easier to use on Linux as long
3189 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3190
3191 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3192 here is the command required to check out and build the source: Use
3193 &#39;&lt;tt&gt;svn checkout
3194 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3195 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3196 devscripts package.&lt;/p&gt;
3197
3198 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3199 renamed to Isenkram and the source moved from the Debian Edu
3200 subversion repository to a Debian collab-maint git repository. See
3201 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3202 instructions&lt;/a&gt; for details.&lt;/p&gt;
3203 </description>
3204 </item>
3205
3206 <item>
3207 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3208 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3209 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3210 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3211 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3212 suddenly in bed. With a quiet whimper, it went completely quiet and
3213 black. The power button was no longer able to turn it on. It was a
3214 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3215 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3216 Compaq I had before that. Now I need to find a replacement. To keep
3217 going during Christmas, I moved the one year old SSD disk to my old
3218 X40 where it fitted (only one I had left that could use it), but it is
3219 not a durable solution.
3220
3221 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3222 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3223
3224 &lt;ul&gt;
3225
3226 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3227 than A4).&lt;/li&gt;
3228 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3229 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3230 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3231 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3232 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3233 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3234 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3235 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3236 size).&lt;/li&gt;
3237 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3238 X.org packages.&lt;/li&gt;
3239 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3240 the time).
3241
3242 &lt;/ul&gt;
3243
3244 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3245 list. The reason is simply that the specifications on laptops the
3246 last 10-15 years have been sufficient for my needs, and I have to look
3247 at other features to choose my laptop. But are there still made as
3248 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3249 robust, and Thinkpads seem to be heading in the wrong direction since
3250 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3251 still be useful.&lt;/p&gt;
3252
3253 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3254 external keyboard? I&#39;ll have to check the
3255 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3256 well-supported laptops, or perhaps just buy one preinstalled from one
3257 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3258 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3259 </description>
3260 </item>
3261
3262 <item>
3263 <title>How to find a browser plugin supporting a given MIME type</title>
3264 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3265 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3266 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3267 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3268 install to get support for a given MIME type. Thanks to
3269 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3270 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3271 Unfortunately, not very many packages provide the needed meta
3272 information, Anyway, here is a small script to look up all browser
3273 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3274
3275 &lt;pre&gt;
3276 #!/usr/bin/python
3277 import sys
3278 import apt
3279 def pkgs_handling_mimetype(mimetype):
3280 cache = apt.Cache()
3281 cache.open(None)
3282 thepkgs = []
3283 for pkg in cache:
3284 version = pkg.candidate
3285 if version is None:
3286 version = pkg.installed
3287 if version is None:
3288 continue
3289 record = version.record
3290 if not record.has_key(&#39;Npp-MimeType&#39;):
3291 continue
3292 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3293 for t in mime_types:
3294 t = t.rstrip().strip()
3295 if t == mimetype:
3296 thepkgs.append(pkg.name)
3297 return thepkgs
3298 mimetype = &quot;audio/ogg&quot;
3299 if 1 &lt; len(sys.argv):
3300 mimetype = sys.argv[1]
3301 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3302 for pkg in pkgs_handling_mimetype(mimetype):
3303 print &quot; %s&quot; %pkg
3304 &lt;/pre&gt;
3305
3306 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3307
3308 &lt;pre&gt;
3309 % ./apt-find-browserplug-for-mimetype
3310 Browser plugin packages supporting audio/ogg:
3311 gecko-mediaplayer
3312 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3313 Browser plugin packages supporting application/x-shockwave-flash:
3314 browser-plugin-gnash
3315 %
3316 &lt;/pre&gt;
3317
3318 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3319 itself to query for plugins and propose to install the needed
3320 packages. It would be great if Debian supported such feature too. Is
3321 anyone working on adding it?&lt;/p&gt;
3322
3323 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3324 request for icweasel support for this feature is
3325 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3326 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3327 of manpower and wish for a different design is the reason thus feature
3328 is not yet in iceweasel from Debian.&lt;/p&gt;
3329 </description>
3330 </item>
3331
3332 <item>
3333 <title>What is the most supported MIME type in Debian?</title>
3334 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3335 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3336 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3337 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3338 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3339 proposal to make it possible for a Desktop application to propose to
3340 the user some package to install to gain support for a given MIME
3341 type, font, library etc. that is currently missing. With such
3342 mechanism in place, it would be possible for the desktop to
3343 automatically propose and install leocad if some LDraw file is
3344 downloaded by the browser.&lt;/p&gt;
3345
3346 &lt;p&gt;To get some idea about the current content of the archive, I decided
3347 to write a simple program to extract all .desktop files from the
3348 Debian archive and look up the claimed MIME support there. The result
3349 can be found on the
3350 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3351 site&lt;/a&gt;. Using the collected information, it become possible to
3352 answer the question in the title. Here are the 20 most supported MIME
3353 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3354 The complete list is available from the link above.&lt;/p&gt;
3355
3356 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3357
3358 &lt;pre&gt;
3359 count MIME type
3360 ----- -----------------------
3361 32 text/plain
3362 30 audio/mpeg
3363 29 image/png
3364 28 image/jpeg
3365 27 application/ogg
3366 26 audio/x-mp3
3367 25 image/tiff
3368 25 image/gif
3369 22 image/bmp
3370 22 audio/x-wav
3371 20 audio/x-flac
3372 19 audio/x-mpegurl
3373 18 video/x-ms-asf
3374 18 audio/x-musepack
3375 18 audio/x-mpeg
3376 18 application/x-ogg
3377 17 video/mpeg
3378 17 audio/x-scpls
3379 17 audio/ogg
3380 16 video/x-ms-wmv
3381 &lt;/pre&gt;
3382
3383 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3384
3385 &lt;pre&gt;
3386 count MIME type
3387 ----- -----------------------
3388 33 text/plain
3389 32 image/png
3390 32 image/jpeg
3391 29 audio/mpeg
3392 27 image/gif
3393 26 image/tiff
3394 26 application/ogg
3395 25 audio/x-mp3
3396 22 image/bmp
3397 21 audio/x-wav
3398 19 audio/x-mpegurl
3399 19 audio/x-mpeg
3400 18 video/mpeg
3401 18 audio/x-scpls
3402 18 audio/x-flac
3403 18 application/x-ogg
3404 17 video/x-ms-asf
3405 17 text/html
3406 17 audio/x-musepack
3407 16 image/x-xbitmap
3408 &lt;/pre&gt;
3409
3410 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3411
3412 &lt;pre&gt;
3413 count MIME type
3414 ----- -----------------------
3415 31 text/plain
3416 31 image/png
3417 31 image/jpeg
3418 29 audio/mpeg
3419 28 application/ogg
3420 27 image/gif
3421 26 image/tiff
3422 26 audio/x-mp3
3423 23 audio/x-wav
3424 22 image/bmp
3425 21 audio/x-flac
3426 20 audio/x-mpegurl
3427 19 audio/x-mpeg
3428 18 video/x-ms-asf
3429 18 video/mpeg
3430 18 audio/x-scpls
3431 18 application/x-ogg
3432 17 audio/x-musepack
3433 16 video/x-ms-wmv
3434 16 video/x-msvideo
3435 &lt;/pre&gt;
3436
3437 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3438 information mentioned in DEP-11. I have not yet had time to look at
3439 it, but hope the PackageKit people in Debian are on top of these
3440 issues.&lt;/p&gt;
3441
3442 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3443 discovering a typo in my script.&lt;/p&gt;
3444 </description>
3445 </item>
3446
3447 <item>
3448 <title>Using modalias info to find packages handling my hardware</title>
3449 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3451 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3452 <description>&lt;p&gt;Yesterday, I wrote about the
3453 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3454 values provided by the Linux kernel&lt;/a&gt; following my hope for
3455 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3456 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3457 modalias values attached to package names can be used to map packages
3458 to hardware. This allow the system to look up and suggest relevant
3459 packages when I plug in some new hardware into my machine, and replace
3460 discover and discover-data as the database used to map hardware to
3461 packages.&lt;/p&gt;
3462
3463 &lt;p&gt;I create a modaliases file with entries like the following,
3464 containing package name, kernel module name (if relevant, otherwise
3465 the package name) and globs matching the relevant hardware
3466 modalias.&lt;/p&gt;
3467
3468 &lt;p&gt;&lt;blockquote&gt;
3469 Package: package-name
3470 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3471 &lt;/blockquote&gt;&lt;/p&gt;
3472
3473 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3474 for a given modalias value using this file.&lt;/p&gt;
3475
3476 &lt;p&gt;An entry like this would suggest the video and picture application
3477 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3478
3479 &lt;p&gt;&lt;blockquote&gt;
3480 Package: cheese
3481 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3482 &lt;/blockquote&gt;&lt;/p&gt;
3483
3484 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3485 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3486
3487 &lt;p&gt;&lt;blockquote&gt;
3488 Package: pcmciautils
3489 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3490 &lt;/blockquote&gt;&lt;/p&gt;
3491
3492 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3493 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3494
3495 &lt;p&gt;&lt;blockquote&gt;
3496 Package: colorhug-client
3497 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3498 &lt;/blockquote&gt;&lt;/p&gt;
3499
3500 &lt;p&gt;I believe the format is compatible with the format of the Packages
3501 file in the Debian archive. Ubuntu already uses their Packages file
3502 to store their mappings from packages to hardware.&lt;/p&gt;
3503
3504 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3505 announce the hardware it support in a way my prototype understand.
3506 This allow those publishing packages in an APT source outside the
3507 Debian archive as well as those backporting packages to make sure the
3508 hardware mapping are included in the package meta information. I&#39;ve
3509 tested such header in the pymissile package, and its modalias mapping
3510 is working as it should with my prototype. It even made it to Ubuntu
3511 Raring.&lt;/p&gt;
3512
3513 &lt;p&gt;To test if it was possible to look up supported hardware using only
3514 the shell tools available in the Debian installer, I wrote a shell
3515 implementation of the lookup code. The idea is to create files for
3516 each modalias and let the shell do the matching. Please check out and
3517 try the
3518 &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;
3519 shell script. It run without any extra dependencies and fetch the
3520 hardware mappings from the Debian archive and the subversion
3521 repository where I currently work on my prototype.&lt;/p&gt;
3522
3523 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3524 install yubikey-personalization:&lt;/p&gt;
3525
3526 &lt;p&gt;&lt;blockquote&gt;
3527 % ./hw-support-lookup
3528 &lt;br&gt;yubikey-personalization
3529 &lt;br&gt;%
3530 &lt;/blockquote&gt;&lt;/p&gt;
3531
3532 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3533 propose to install the pcmciautils package:&lt;/p&gt;
3534
3535 &lt;p&gt;&lt;blockquote&gt;
3536 % ./hw-support-lookup
3537 &lt;br&gt;pcmciautils
3538 &lt;br&gt;%
3539 &lt;/blockquote&gt;&lt;/p&gt;
3540
3541 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3542 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3543 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3544
3545 &lt;p&gt;It could be possible to generate several of the mappings between
3546 packages and hardware. One source would be to look at packages with
3547 kernel modules, ie packages with *.ko files in /lib/modules/, and
3548 extract their modalias information. Another would be to look at
3549 packages with udev rules, ie packages with files in
3550 /lib/udev/rules.d/, and extract their vendor/model information to
3551 generate a modalias matching rule. I have not tested any of these to
3552 see if it work.&lt;/p&gt;
3553
3554 &lt;p&gt;If you want to help implementing a system to let us propose what
3555 packages to install when new hardware is plugged into a Debian
3556 machine, please send me an email or talk to me on
3557 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3558 </description>
3559 </item>
3560
3561 <item>
3562 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3563 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3564 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3565 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3566 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3567 information, to find the packages that support a given piece of
3568 hardware, I refreshed my memory regarding modalias values, and decided
3569 to document the details. Here are my findings so far, also available
3570 in
3571 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3572 Debian Edu subversion repository&lt;/a&gt;:
3573
3574 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3575
3576 &lt;p&gt;This document try to explain what the different types of modalias
3577 values stands for. It is in part based on information from
3578 &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;,
3579 &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;,
3580 &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
3581 &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;.
3582
3583 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3584 this shell script:&lt;/p&gt;
3585
3586 &lt;pre&gt;
3587 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3588 &lt;/pre&gt;
3589
3590 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3591 using modinfo:&lt;/p&gt;
3592
3593 &lt;pre&gt;
3594 % /sbin/modinfo psmouse | grep alias:
3595 alias: serio:ty05pr*id*ex*
3596 alias: serio:ty01pr*id*ex*
3597 %
3598 &lt;/pre&gt;
3599
3600 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3601
3602 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3603 Bridge memory controller:&lt;/p&gt;
3604
3605 &lt;p&gt;&lt;blockquote&gt;
3606 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3607 &lt;/blockquote&gt;&lt;/p&gt;
3608
3609 &lt;p&gt;This represent these values:&lt;/p&gt;
3610
3611 &lt;pre&gt;
3612 v 00008086 (vendor)
3613 d 00002770 (device)
3614 sv 00001028 (subvendor)
3615 sd 000001AD (subdevice)
3616 bc 06 (bus class)
3617 sc 00 (bus subclass)
3618 i 00 (interface)
3619 &lt;/pre&gt;
3620
3621 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3622 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3623 0600. The 0600 class is a host bridge. Other useful bus values are
3624 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3625
3626 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3627 means.&lt;/p&gt;
3628
3629 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3630
3631 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3632 USB hub in a laptop:&lt;/p&gt;
3633
3634 &lt;p&gt;&lt;blockquote&gt;
3635 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3636 &lt;/blockquote&gt;&lt;/p&gt;
3637
3638 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3639
3640 &lt;pre&gt;
3641 v 1D6B (device vendor)
3642 p 0001 (device product)
3643 d 0206 (bcddevice)
3644 dc 09 (device class)
3645 dsc 00 (device subclass)
3646 dp 00 (device protocol)
3647 ic 09 (interface class)
3648 isc 00 (interface subclass)
3649 ip 00 (interface protocol)
3650 &lt;/pre&gt;
3651
3652 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3653 class is in the interface class section. For a simple USB web camera,
3654 these alias entries show up:&lt;/p&gt;
3655
3656 &lt;p&gt;&lt;blockquote&gt;
3657 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3658 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3659 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3660 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3661 &lt;/blockquote&gt;&lt;/p&gt;
3662
3663 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3664 camera), 0101 is audio control device and 0102 is audio streaming (aka
3665 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3666
3667 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3668
3669 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3670 receiver in a Thinkpad X40:&lt;/p&gt;
3671
3672 &lt;p&gt;&lt;blockquote&gt;
3673 acpi:IBM0071:PNP0511:
3674 &lt;/blockquote&gt;&lt;/p&gt;
3675
3676 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3677
3678 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3679
3680 &lt;p&gt;The DMI table contain lots of information about the computer case
3681 and model. This is an entry for a IBM Thinkpad X40, fetched from
3682 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3683
3684 &lt;p&gt;&lt;blockquote&gt;
3685 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3686 &lt;/blockquote&gt;&lt;/p&gt;
3687
3688 &lt;p&gt;The values present are&lt;/p&gt;
3689
3690 &lt;pre&gt;
3691 bvn IBM (BIOS vendor)
3692 bvr 1UETB6WW(1.66) (BIOS version)
3693 bd 06/15/2005 (BIOS date)
3694 svn IBM (system vendor)
3695 pn 2371H4G (product name)
3696 pvr ThinkPadX40 (product version)
3697 rvn IBM (board vendor)
3698 rn 2371H4G (board name)
3699 rvr NotAvailable (board version)
3700 cvn IBM (chassis vendor)
3701 ct 10 (chassis type)
3702 cvr NotAvailable (chassis version)
3703 &lt;/pre&gt;
3704
3705 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3706 found in the dmidecode source:&lt;/p&gt;
3707
3708 &lt;pre&gt;
3709 3 Desktop
3710 4 Low Profile Desktop
3711 5 Pizza Box
3712 6 Mini Tower
3713 7 Tower
3714 8 Portable
3715 9 Laptop
3716 10 Notebook
3717 11 Hand Held
3718 12 Docking Station
3719 13 All In One
3720 14 Sub Notebook
3721 15 Space-saving
3722 16 Lunch Box
3723 17 Main Server Chassis
3724 18 Expansion Chassis
3725 19 Sub Chassis
3726 20 Bus Expansion Chassis
3727 21 Peripheral Chassis
3728 22 RAID Chassis
3729 23 Rack Mount Chassis
3730 24 Sealed-case PC
3731 25 Multi-system
3732 26 CompactPCI
3733 27 AdvancedTCA
3734 28 Blade
3735 29 Blade Enclosing
3736 &lt;/pre&gt;
3737
3738 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3739 table. For example my home server is a tower, but the DMI modalias
3740 claim it is a desktop.&lt;/p&gt;
3741
3742 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3743
3744 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3745 test machine:&lt;/p&gt;
3746
3747 &lt;p&gt;&lt;blockquote&gt;
3748 serio:ty01pr00id00ex00
3749 &lt;/blockquote&gt;&lt;/p&gt;
3750
3751 &lt;p&gt;The values present are&lt;/p&gt;
3752
3753 &lt;pre&gt;
3754 ty 01 (type)
3755 pr 00 (prototype)
3756 id 00 (id)
3757 ex 00 (extra)
3758 &lt;/pre&gt;
3759
3760 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3761 the valid values are.&lt;/p&gt;
3762
3763 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3764
3765 &lt;p&gt;There are heaps of other modalias subtypes according to
3766 file2alias.c. There is the rest of the list from that source: amba,
3767 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3768 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3769 vmbus, x86cpu and zorro. I did not spend time documenting all of
3770 these, as they do not seem relevant for my intended use with mapping
3771 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3772
3773 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3774
3775 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3776 one can use the following shell script:&lt;/p&gt;
3777
3778 &lt;pre&gt;
3779 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3780 echo &quot;$id&quot; ; \
3781 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3782 done
3783 &lt;/pre&gt;
3784
3785 &lt;p&gt;The output can look like this (only the first few entries as the
3786 list is very long on my test machine):&lt;/p&gt;
3787
3788 &lt;pre&gt;
3789 acpi:ACPI0003:
3790 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3791 acpi:device:
3792 FATAL: Module acpi:device: not found.
3793 acpi:IBM0068:
3794 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3795 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3796 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3797 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3798 acpi:IBM0071:PNP0511:
3799 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3800 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3801 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3802 [...]
3803 &lt;/pre&gt;
3804
3805 &lt;p&gt;If you want to help implementing a system to let us propose what
3806 packages to install when new hardware is plugged into a Debian
3807 machine, please send me an email or talk to me on
3808 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3809
3810 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3811 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3812 in /sys/ with space in them.&lt;/p&gt;
3813 </description>
3814 </item>
3815
3816 <item>
3817 <title>Moved the pymissile Debian packaging to collab-maint</title>
3818 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3819 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3820 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3821 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3822 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3823 Launcher and updated the Debian package
3824 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3825 sure udev will fix the device permissions when it is plugged in. I
3826 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3827 hopefully make the package be proposed by jockey in Ubuntu when a user
3828 plug in his rocket launcher. In the process I moved the source to a
3829 git repository under collab-maint, to make it easier for any DD to
3830 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3831 is not very active, but the software still work for me even after five
3832 years of relative silence. The new git repository is not listed in
3833 the uploaded package yet, because I want to test the other changes a
3834 bit more before I upload the new version. If you want to check out
3835 the new version with a .desktop file included, visit the
3836 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3837 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3838 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3839 </description>
3840 </item>
3841
3842 <item>
3843 <title>Lets make hardware dongles easier to use in Debian</title>
3844 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3845 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3846 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3847 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3848 general, is that there is a great package management system with the
3849 ability to automatically install software packages by downloading them
3850 from the distribution mirrors, but no way to get it to automatically
3851 install the packages I need to use the hardware I plug into my
3852 machine. Even if the package to use it is easily available from the
3853 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3854 suggest to automatically install the python-nxt, nbc and t2n packages
3855 I need to talk to it. When I plug in a Yubikey, it could propose the
3856 yubikey-personalization package. The information required to do this
3857 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3858
3859 &lt;p&gt;Some years ago, I proposed to
3860 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
3861 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
3862 simple:
3863
3864 &lt;ul&gt;
3865
3866 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
3867 starting when a user log in.&lt;/li&gt;
3868
3869 &lt;li&gt;Set this program up to listen for kernel events emitted when new
3870 hardware is inserted into the computer.&lt;/li&gt;
3871
3872 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
3873 database mapping to packages, and take note of any non-installed
3874 packages.&lt;/li&gt;
3875
3876 &lt;li&gt;Show a message to the user proposing to install the discovered
3877 package, and make it easy to install it.&lt;/li&gt;
3878
3879 &lt;/ul&gt;
3880
3881 &lt;p&gt;I am not sure what the best way to implement this is, but my
3882 initial idea was to use dbus events to discover new hardware, the
3883 discover database to find packages and
3884 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
3885 packages.&lt;/p&gt;
3886
3887 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
3888 draft package is now checked into
3889 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3890 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
3891 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
3892 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3893 the relevant packages in Debian, and uploaded a new version
3894 2.2013.01.09 to unstable. I also discovered that the current
3895 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
3896 package in Debian no longer discovered any USB devices, because
3897 /proc/bus/usb/devices is no longer present. I ported it to use
3898 libusb as a fall back option to get it working. The fixed package
3899 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
3900 because of the freeze).&lt;/p&gt;
3901
3902 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
3903 desktop notification to show up (only once, the first time it is
3904 inserted):&lt;/p&gt;
3905
3906 &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;
3907
3908 &lt;p&gt;For this prototype to be really useful, some way to automatically
3909 install the proposed packages by pressing the &quot;Please install
3910 program(s)&quot; button should to be implemented.&lt;/p&gt;
3911
3912 &lt;p&gt;If this idea seem useful to you, and you want to help make it
3913 happen, please help me update the discover-data database with mappings
3914 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
3915 list the package you would like to have installed when a given
3916 hardware device is inserted into your computer, and report bugs using
3917 reportbug if it isn&#39;t. Or, if you know of a better way to provide
3918 such mapping, please let me know.&lt;/p&gt;
3919
3920 &lt;p&gt;This prototype need more work, and there are several questions that
3921 should be considered before it is ready for production use. Is dbus
3922 the correct way to detect new hardware? At the moment I look for HAL
3923 dbus events on the system bus, because that is the events I could see
3924 on my Debian Squeeze KDE desktop. Are there better events to use?
3925 How should the user be notified? Is the desktop notification
3926 mechanism the best option, or should the background daemon raise a
3927 popup instead? How should packages be installed? When should they
3928 not be installed?&lt;/p&gt;
3929
3930 &lt;p&gt;If you want to help getting such feature implemented in Debian,
3931 please send me an email. :)&lt;/p&gt;
3932 </description>
3933 </item>
3934
3935 <item>
3936 <title>New IRC channel for LEGO designers using Debian</title>
3937 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
3938 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
3939 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
3940 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
3941 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
3942 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
3943 discovered I had to build all the tools myself because none were
3944 already in Debian Squeeze. If Debian support for LEGO is something
3945 you care about, please join me on the IRC channel
3946 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
3947 irc.debian.org). There is a lot that could be done to improve the
3948 Debian support for LEGO designers. For example both CAD software
3949 and Mindstorm compilers are missing. :)&lt;/p&gt;
3950
3951 &lt;p&gt;Update 2012-01-03: A
3952 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
3953 including links to Lego related packages is now available.&lt;/p&gt;
3954 </description>
3955 </item>
3956
3957 <item>
3958 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
3959 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
3960 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
3961 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
3962 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
3963 year! I hope next year will prove to be a good year.&lt;/p&gt;
3964
3965 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
3966 decentralised &quot;currency&quot; that allow people to transfer bitcoins
3967 between each other with minimal overhead, is a very interesting
3968 experiment. And as I wrote a few days ago, the bitcoin situation in
3969 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
3970 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
3971 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
3972 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
3973 for one of the ftpmasters to approve the new bitcoin-qt package
3974 name.&lt;/p&gt;
3975
3976 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3977 team in Debian, you can easily test the package in Debian Squeeze
3978 using the following steps to get a set of working packages:&lt;/p&gt;
3979
3980 &lt;blockquote&gt;&lt;pre&gt;
3981 git clone git://git.debian.org/git/collab-maint/bitcoin
3982 cd bitcoin
3983 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3984 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3985 &lt;/pre&gt;&lt;/blockquote&gt;
3986
3987 &lt;p&gt;You might have to install some build dependencies as well. The
3988 list of commands should give you two packages, bitcoind and
3989 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3990 client will download the complete set of bitcoin &quot;blocks&quot;, which need
3991 around 5.6 GiB of data on my machine at the moment. Make sure your
3992 ~/.bitcoin/ directory have lots of spare room if you want to download
3993 all the blocks. The client will warn if the disk is getting full, so
3994 there is not really a problem if you got too little room, but you will
3995 not be able to get all the features out of the client.&lt;/p&gt;
3996
3997 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3998 activities, please send Bitcoin donations to my address
3999 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4000 </description>
4001 </item>
4002
4003 <item>
4004 <title>A word on bitcoin support in Debian</title>
4005 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4006 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4007 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4008 <description>&lt;p&gt;It has been a while since I wrote about
4009 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4010 peer-to-peer based crypto-currency, and the reason is simply that I
4011 have been busy elsewhere. But two days ago, I started looking at the
4012 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4013 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4014 is now maintained by a
4015 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4016 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4017 owe a huge thank you to all these team members. :)
4018 But I was sad to discover that the bitcoin client is missing in
4019 Wheezy. It is only available in Sid (and an outdated client from
4020 backports). The client had several RC bugs registered in BTS blocking
4021 it from entering testing. To try to help the team and improve the
4022 situation, I spent some time providing patches and triaging the bug
4023 reports. I also had a look at the bitcoin package available from Matt
4024 Corallo in a
4025 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4026 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4027 Debian package.&lt;/p&gt;
4028
4029 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4030 IRC, I pushed several patches into the collab-maint git repository to
4031 improve the package. It now contains fixes for the RC issues (not from
4032 me, but fixed by Scott Howard), build rules for a Qt GUI client
4033 package, konqueror support for the bitcoin: URI and bash completion
4034 setup. As I work on Debian Squeeze, I also created
4035 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4036 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4037 it and try to integrate it into the git repository before uploading a
4038 new version to unstable.
4039
4040 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4041 centralized control currently exercised in the monetary system. I
4042 find it completely unacceptable that the USA government is collecting
4043 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4044 that the major credit card companies can block legal money
4045 transactions to Wikileaks. But for bitcoin to succeed, more people
4046 need to use bitcoins, and more people need to accept bitcoins when
4047 they sell products and services. Improving the bitcoin support in
4048 Debian is a small step in the right direction, but not enough.
4049 Unfortunately the user experience when browsing the web and wanting to
4050 pay with bitcoin is still not very good. The bitcoin: URI is a step
4051 in the right direction, but need to work in most or every browser in
4052 use. Also the bitcoin-qt client is too heavy to fire up to do a
4053 quick transaction. I believe there are other clients available, but
4054 have not tested them.&lt;/p&gt;
4055
4056 &lt;p&gt;My
4057 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4058 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4059 I received 20.15 BTC so far on the address I provided in my blog two
4060 years ago, as can be
4061 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4062 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4063 donation. The blockexplorer service demonstrates quite well that
4064 bitcoin is not quite anonymous and untracked. :) I wonder if the
4065 number of users have gone up since then. If you use bitcoin and want
4066 to show your support of my activity, please send Bitcoin donations to
4067 the same address as last time,
4068 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4069 </description>
4070 </item>
4071
4072 <item>
4073 <title>Git repository for song book for Computer Scientists</title>
4074 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4075 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4076 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4077 <description>&lt;p&gt;As I
4078 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4079 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4080 years ago, and today I finally found time to create a public
4081 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4082 repository for the project&lt;/a&gt;.&lt;/p&gt;
4083
4084 &lt;p&gt;If you want to help out, please clone the source and submit patches
4085 to the HTML version. To generate the PDF and PostScript version,
4086 please use prince XML, or let me know about a useful free software
4087 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4088
4089 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4090 PostScript formats at
4091 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4092 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4093 </description>
4094 </item>
4095
4096 <item>
4097 <title>Gratulerer med 19-årsdagen, Debian!</title>
4098 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4099 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4100 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4101 <description>&lt;p&gt;I dag fyller
4102 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4103 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4104 si gratulerer med dagen, Debian!&lt;/p&gt;
4105 </description>
4106 </item>
4107
4108 <item>
4109 <title>Song book for Computer Scientists</title>
4110 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4111 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4112 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4113 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4114 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4115 collecting computer related songs for use at parties. The original
4116 version was written in LaTeX, but a few years ago I got help from
4117 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4118 while keeping the ability to create a nice book in PDF format. I have
4119 not had time to maintain the book for a while now, and guess I should
4120 put it up on some public version control repository where others can
4121 help me extend and update the book. If anyone is volunteering to help
4122 me with this, send me an email. Also let me know if there are songs
4123 missing in my book.&lt;/p&gt;
4124
4125 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4126 me today that I really should let all my readers share the joys of
4127 singing out load about programming, computers and computer networks.
4128 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4129 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4130 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4131 Computer Science Songbook&lt;/a&gt;.
4132 </description>
4133 </item>
4134
4135 <item>
4136 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4137 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4138 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4139 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4140 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4141 around 1000 at the moment. To be able to get help from the vendors
4142 when something go wrong, we want to keep the firmware on the servers
4143 up to date. If the firmware isn&#39;t the latest and greatest, the
4144 vendors typically refuse to start debugging any problems until the
4145 firmware is upgraded. So before every reboot, we want to upgrade the
4146 firmware, and we would really like everyone handling servers at the
4147 university to do this themselves when they plan to reboot a machine.
4148 For that to happen we at the unix server admin group need to provide
4149 the tools to do so.&lt;/p&gt;
4150
4151 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4152 fetch and install the latest firmware for the servers we got. Most of
4153 our hardware are from Dell and HP, so I have focused on these servers
4154 so far. This blog post is about the Dell part.&lt;/P&gt;
4155
4156 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4157 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4158 with firmware information for all 11th generation servers, listing
4159 which firmware should be used on a given model and where on the FTP
4160 site I can find it. Using a simple perl XML parser I can then
4161 download the shell scripts Dell provides to do firmware upgrades from
4162 within Linux and reboot when all the firmware is primed and ready to
4163 be activated on the first reboot.&lt;/p&gt;
4164
4165 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4166 Are there anyone working on similar tools for firmware upgrading all
4167 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4168
4169 &lt;p&gt;&lt;pre&gt;
4170 #!/usr/bin/perl
4171 use strict;
4172 use warnings;
4173 use File::Temp qw(tempdir);
4174 BEGIN {
4175 # Install needed RHEL packages if missing
4176 my %rhelmodules = (
4177 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4178 );
4179 for my $module (keys %rhelmodules) {
4180 eval &quot;use $module;&quot;;
4181 if ($@) {
4182 my $pkg = $rhelmodules{$module};
4183 system(&quot;yum install -y $pkg&quot;);
4184 eval &quot;use $module;&quot;;
4185 }
4186 }
4187 }
4188 my $errorsto = &#39;pere@hungry.com&#39;;
4189
4190 upgrade_dell();
4191
4192 exit 0;
4193
4194 sub run_firmware_script {
4195 my ($opts, $script) = @_;
4196 unless ($script) {
4197 print STDERR &quot;fail: missing script name\n&quot;;
4198 exit 1
4199 }
4200 print STDERR &quot;Running $script\n\n&quot;;
4201
4202 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4203 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4204 } else {
4205 print STDERR &quot;fail: firmware script returned error\n&quot;;
4206 }
4207 }
4208
4209 sub run_firmware_scripts {
4210 my ($opts, @dirs) = @_;
4211 # Run firmware packages
4212 for my $dir (@dirs) {
4213 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4214 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4215 while (my $s = readdir $dh) {
4216 next if $s =~ m/^\.\.?/;
4217 run_firmware_script($opts, &quot;$dir/$s&quot;);
4218 }
4219 closedir $dh;
4220 }
4221 }
4222
4223 sub download {
4224 my $url = shift;
4225 print STDERR &quot;info: Downloading $url\n&quot;;
4226 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4227 }
4228
4229 sub upgrade_dell {
4230 my @dirs;
4231 my $product = `dmidecode -s system-product-name`;
4232 chomp $product;
4233
4234 if ($product =~ m/PowerEdge/) {
4235
4236 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4237 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4238
4239 my $tmpdir = tempdir(
4240 CLEANUP =&gt; 1
4241 );
4242 chdir($tmpdir);
4243 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4244 system(&#39;gunzip Catalog.xml.gz&#39;);
4245 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4246 # -q is quiet, disabling interactivity and reducing console output
4247 my $fwopts = &quot;-q&quot;;
4248 if (@paths) {
4249 for my $url (@paths) {
4250 fetch_dell_fw($url);
4251 }
4252 run_firmware_scripts($fwopts, $tmpdir);
4253 } else {
4254 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4255 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4256 }
4257 chdir(&#39;/&#39;);
4258 } else {
4259 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4260 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4261 }
4262 }
4263
4264 sub fetch_dell_fw {
4265 my $path = shift;
4266 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4267 download($url);
4268 }
4269
4270 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4271 # firmware packages to download from Dell. Only work for Linux
4272 # machines and 11th generation Dell servers.
4273 sub fetch_dell_fw_list {
4274 my $filename = shift;
4275
4276 my $product = `dmidecode -s system-product-name`;
4277 chomp $product;
4278 my ($mybrand, $mymodel) = split(/\s+/, $product);
4279
4280 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4281
4282 my $xml = XMLin($filename);
4283 my @paths;
4284 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4285 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4286 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4287 my $oscode;
4288 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4289 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4290 } else {
4291 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4292 }
4293 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4294 {
4295 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4296 }
4297 }
4298 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4299 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4300
4301 # Drop application packages, only firmware and BIOS
4302 next if &#39;APAC&#39; eq $componenttype;
4303
4304 my $cpath = $component-&gt;{path};
4305 for my $path (@paths) {
4306 if ($cpath =~ m%/$path$%) {
4307 push(@paths, $cpath);
4308 }
4309 }
4310 }
4311 return @paths;
4312 }
4313 &lt;/pre&gt;
4314
4315 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4316 it could work on other platforms with some tweaking. Anyone know a
4317 index like Catalog.xml is available from HP for HP servers? At the
4318 moment I maintain a similar list manually and it is quickly getting
4319 outdated.&lt;/p&gt;
4320 </description>
4321 </item>
4322
4323 <item>
4324 <title>How is booting into runlevel 1 different from single user boots?</title>
4325 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4327 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4328 <description>&lt;p&gt;Wouter Verhelst have some
4329 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4330 comments and opinions&lt;/a&gt; on my blog post on
4331 &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
4332 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4333 &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
4334 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4335 small piece of his comment now, and though it best to address the
4336 misunderstanding he bring forward:&lt;/p&gt;
4337
4338 &lt;p&gt;&lt;blockquote&gt;
4339 Currently, a system admin has four options: [...] boot to a
4340 single-user system (by adding &#39;single&#39; to the kernel command line;
4341 this runs rcS and rc1 scripts)
4342 &lt;/blockquote&gt;&lt;/p&gt;
4343
4344 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4345 and booting into runlevel 1 is the same. I am not surprised he
4346 believe this, because it would make sense and is a quite sensible
4347 thing to believe. But because the boot in Debian is slightly broken,
4348 runlevel 1 do not work properly and it isn&#39;t the same as single user
4349 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4350 hard to explain.&lt;/p&gt;
4351
4352 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4353 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4354 executed in single user mode is sulogin. Single user mode is a boot
4355 state &quot;between&quot; the runlevels, and when booting into single user mode,
4356 only the scripts in /etc/rcS.d/ are executed before the init process
4357 enters the single user state. When switching to runlevel 1, the state
4358 is in fact not ending in runlevel 1, but it passes through runlevel 1
4359 and end up in the single user mode (see /etc/rc1.d/S03single, which
4360 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4361 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4362 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4363 mode).&lt;/p&gt;
4364
4365 &lt;p&gt;This summary might make it clearer. When booting for the first
4366 time into single user mode, the following commands are executed:
4367 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4368 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4369 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4370 trying to continue after visiting single user mode. Not all services
4371 are started again as they should, causing the machine to end up in an
4372 unpredicatble state. This is why Debian admins recommend rebooting
4373 after visiting single user mode.&lt;/p&gt;
4374
4375 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4376 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4377 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4378 stopped when passing through the scripts in /etc/rc1.d/, and not
4379 started again when switching away from runlevel 1 to the runlevels
4380 2-5. I believe the problem is best fixed by moving all the scripts
4381 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4382 functioning single user mode during boot.&lt;/p&gt;
4383
4384 &lt;p&gt;I have spent several years investigating the Debian boot system,
4385 and discovered this problem a few years ago. I suspect it originates
4386 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4387 </description>
4388 </item>
4389
4390 <item>
4391 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4392 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4393 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4394 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4395 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4396 are started from /etc/rcS.d/. In fact, there is a bite more of them
4397 than make sense, and this causes a few problems. What kind of
4398 problems, you might ask. There are at least two problems. The first
4399 is that it is not possible to recover a machine after switching to
4400 runlevel 1. One need to actually reboot to get the machine back to
4401 the expected state. The other is that single user boot will sometimes
4402 run into problems because some of the subsystems are activated before
4403 the root login is presented, causing problems when trying to recover a
4404 machine from a problem in that subsystem. A minor additional point is
4405 that moving more scripts out of rcS.d/ and into the other rc#.d/
4406 directories will increase the amount of scripts that can run in
4407 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4408
4409 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4410 scripts that _have_ to execute before the root login prompt is
4411 presented during a single user boot should go there. Everything else
4412 should go into the numeric runlevels. This means things like
4413 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4414 the numeric runlevels. Today in Debian, there are around 115 init.d
4415 scripts that are started from rcS.d/, and most of them should be moved
4416 out. Do your package have one of them? Please help us make single
4417 user and runlevel 1 better by moving it.&lt;/p&gt;
4418
4419 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4420 etc. should still be started from rcS.d/, but there is for example no
4421 need to have the network enabled before the single user login prompt
4422 is presented.&lt;/p&gt;
4423
4424 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4425 Debian systems working while scripts migrate and during upgrades, the
4426 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4427 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4428 and the next ones can only be moved when their dependencies have been
4429 moved first. This migration must be done sequentially while we ensure
4430 that the package system upgrade packages in the right order to keep
4431 the system state correct. This will require some coordination when it
4432 comes to network related packages, but most of the packages with
4433 scripts that should migrate do not have anything in rcS.d/ depending
4434 on them. Some packages have already been updated, like the sudo
4435 package, while others are still left to do. I wish I had time to work
4436 on this myself, but real live constrains make it unlikely that I will
4437 find time to push this forward.&lt;/p&gt;
4438 </description>
4439 </item>
4440
4441 <item>
4442 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4443 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4444 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4445 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4446 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4447 mentioned the issues I believe should be improved in Debian for its
4448 desktop to be useful for more people. The use case for this is my
4449 parents, which are currently running Kubuntu which solve the
4450 issues.&lt;/p&gt;
4451
4452 &lt;p&gt;I suspect these four missing features are not very hard to
4453 implement. After all, they are present in Ubuntu, so if we wanted to
4454 do this in Debian we would have a source.&lt;/p&gt;
4455
4456 &lt;ol&gt;
4457
4458 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4459 are new packages available for upgrades, a icon in the KDE status bar
4460 indicate this, and clicking on it will activate the simple upgrade
4461 tool to handle it. I have no problem guiding both of my parents
4462 through the process over the phone. If a kernel reboot is required,
4463 this too is indicated by the status bars and the upgrade tool. Last
4464 time I checked, nothing with the same features was working in KDE in
4465 Debian.&lt;/li&gt;
4466
4467 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4468 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4469 currently have a handler for, it will ask the user if the system
4470 should search for a package that would add support for this MIME type,
4471 and if the user say yes, the APT sources will be searched for packages
4472 advertising the MIME type in their control file (visible in the
4473 Packages file in the APT archive). If one or more packages are found,
4474 it is a simple click of the mouse to add support for the missing mime
4475 type. If the package require the user to accept some non-free
4476 license, this is explained to the user. The entire process make it
4477 more clear to the user why something do not work in the browser, and
4478 make the chances higher for the user to blame the web page authors and
4479 not the browser for any missing features.&lt;/li&gt;
4480
4481 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4482 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4483 it is not supporting, a dialog pop up asking the user if the system
4484 should search for a package that would add support for it. This
4485 happen with things like MP3, Windows Media or H.264. The selection
4486 and installation procedure is very similar to the Firefox browser
4487 plugin handling. This is as far as I know implemented using a
4488 gstreamer hook. The end result is that the user easily get access to
4489 the codecs that are present from the APT archives available, while
4490 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4491
4492 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4493 displaying a text/plain file in my Debian browser, it will propose to
4494 start emacs to show it. If I remember correctly, when doing the same
4495 in Kunbutu it show the file as a text file in the browser. At least I
4496 know Opera will show text files within the browser. I much prefer the
4497 latter behaviour.&lt;/li&gt;
4498
4499 &lt;/ol&gt;
4500
4501 &lt;p&gt;There are other nice features as well, like the simplified suite
4502 upgrader, but given that I am the one mostly doing the dist-upgrade,
4503 it do not matter much.&lt;/p&gt;
4504
4505 &lt;p&gt;I really hope we could get these features in place for the next
4506 Debian release. It would require the coordinated effort of several
4507 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4508 </description>
4509 </item>
4510
4511 <item>
4512 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4513 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4515 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4516 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4517 site is build on Debian/Squeeze, and this platform was chosen because
4518 I am most familiar with Debian (being a Debian Developer for around 10
4519 years) because it is the latest stable Debian release which should get
4520 security support for a few years.&lt;/p&gt;
4521
4522 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4523 that are missing in Debian at the moment. It would be great if these
4524 modules were added to the Debian archive, allowing anyone to set up
4525 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4526 in their own country using only Debian packages. The list of modules
4527 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4528 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4529 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4530 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4531 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4532 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4533 easier in the future.&lt;/p&gt;
4534
4535 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4536 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4537 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4538 with the responsibility of tracking security problems, which I really
4539 do not have time for.&lt;/p&gt;
4540 </description>
4541 </item>
4542
4543 <item>
4544 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4545 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4546 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4547 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4548 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4549 posts have been in Norwegian the last few weeks, so here is a short
4550 update in English.&lt;/p&gt;
4551
4552 &lt;p&gt;The kids still keep me too busy to get much free software work
4553 done, but I did manage to organise a project to get a Norwegian port
4554 of the British service
4555 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4556 and it has been running for a month now. The entire project has been
4557 organised by me and two others. Around Christmas we gathered sponsors
4558 to fund the development work. In January I drafted a contract with
4559 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4560 and in February the development took place. Most of it involved
4561 converting the source to use GPS coordinates instead of British
4562 easting/northing, and the resulting code should be a lot easier to get
4563 running in any country by now. The Norwegian
4564 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4565 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4566 source and the source for administrative borders in Norway, and
4567 support for this had to be added/fixed.&lt;/p&gt;
4568
4569 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4570 polishing the system before we announced it March 7th. The system is
4571 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4572 problem reports in a few weeks. Soon we hope to announce the Android
4573 and iPhone versions making it even easier to report problems with the
4574 public infrastructure.&lt;/p&gt;
4575
4576 &lt;p&gt;Perhaps something to consider for those of you in countries without
4577 such service?&lt;/p&gt;
4578 </description>
4579 </item>
4580
4581 <item>
4582 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4583 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4584 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4585 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4586 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4587 issues here at my work with the University of Oslo. My idea is that
4588 it should be possible to use the information about security issues
4589 available on the Internet, and check our locally
4590 maintained/distributed software against this information. It should
4591 allow us to verify that no known security issues are forgotten. The
4592 CVE database listing vulnerabilities seem like a great central point,
4593 and by using the package lists from Debian mapped to CVEs provided by
4594 the testing security team, I believed it should be possible to figure
4595 out which security holes were present in our free software
4596 collection.&lt;/p&gt;
4597
4598 &lt;p&gt;After reading up on the topic, it became obvious that the first
4599 building block is to be able to name software packages in a unique and
4600 consistent way across data sources. I considered several ways to do
4601 this, for example coming up with my own naming scheme like using URLs
4602 to project home pages or URLs to the Freshmeat entries, or using some
4603 existing naming scheme. And it seem like I am not the first one to
4604 come across this problem, as MITRE already proposed and implemented a
4605 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4606 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4607 software, hardware and other platform components. The CPE ids are
4608 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4609 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4610 issues for any CPE name. With this in place, all I need to do is to
4611 locate the CPE id for the software packages we use at the university.
4612 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4613 NVD entry if a CVE for the package exist).&lt;/p&gt;
4614
4615 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4616 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4617 check out, one could look up
4618 &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
4619 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4620 The most recent one is
4621 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4622 and at the bottom of the NVD page for this vulnerability the complete
4623 list of affected versions is provided.&lt;/p&gt;
4624
4625 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4626 for offline processing of issues. Using this dump, I&#39;ve written a
4627 small script taking a list of CPEs as input and list all CVEs
4628 affecting the packages represented by these CPEs. One give it CPEs
4629 with version numbers as specified above and get a list of open
4630 security issues out.&lt;/p&gt;
4631
4632 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4633 information need to be high. For that to happen, I believe as many as
4634 possible need to use and contribute to the NVD database. I notice
4635 RHEL is providing
4636 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4637 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4638 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4639
4640 &lt;p&gt;To get an idea about the quality for free software, I spent some
4641 time making it possible to compare the CVE database from Debian with
4642 the CVE database in NVD. The result look fairly good, but there are
4643 some inconsistencies in NVD (same software package having several
4644 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4645 Debian believe are affected by a CVE). Hope to find time to improve
4646 the quality of NVD, but that require being able to get in touch with
4647 someone maintaining it. So far my three emails with questions and
4648 corrections have not seen any reply, but I hope contact can be
4649 established soon.&lt;/p&gt;
4650
4651 &lt;p&gt;An interesting application for CPEs is cross platform package
4652 mapping. It would be useful to know which packages in for example
4653 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4654 this would be trivial if all linux distributions provided CPE entries
4655 for their packages.&lt;/p&gt;
4656 </description>
4657 </item>
4658
4659 <item>
4660 <title>Which module is loaded for a given PCI and USB device?</title>
4661 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4662 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4663 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4664 <description>&lt;p&gt;In the
4665 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4666 package in Debian, there is a script to report useful information
4667 about the running hardware for use when people report missing
4668 information. One part of this script that I find very useful when
4669 debugging hardware problems, is the part mapping loaded kernel module
4670 to the PCI device it claims. It allow me to quickly see if the kernel
4671 module I expect is driving the hardware I am struggling with. To see
4672 the output, make sure discover-data is installed and run
4673 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4674 one of my machines like this:&lt;/p&gt;
4675
4676 &lt;pre&gt;
4677 loaded modules:
4678 10de:03eb i2c_nforce2
4679 10de:03f1 ohci_hcd
4680 10de:03f2 ehci_hcd
4681 10de:03f0 snd_hda_intel
4682 10de:03ec pata_amd
4683 10de:03f6 sata_nv
4684 1022:1103 k8temp
4685 109e:036e bttv
4686 109e:0878 snd_bt87x
4687 11ab:4364 sky2
4688 &lt;/pre&gt;
4689
4690 &lt;p&gt;The code in question look like this, slightly modified for
4691 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4692
4693 &lt;pre&gt;
4694 if [ -d /sys/bus/pci/devices/ ] ; then
4695 echo loaded pci modules:
4696 (
4697 cd /sys/bus/pci/devices/
4698 for address in * ; do
4699 if [ -d &quot;$address/driver/module&quot; ] ; then
4700 module=`cd $address/driver/module ; pwd -P | xargs basename`
4701 if grep -q &quot;^$module &quot; /proc/modules ; then
4702 address=$(echo $address |sed s/0000://)
4703 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4704 echo &quot;$id $module&quot;
4705 fi
4706 fi
4707 done
4708 )
4709 echo
4710 fi
4711 &lt;/pre&gt;
4712
4713 &lt;p&gt;Similar code could be used to extract USB device module
4714 mappings:&lt;/p&gt;
4715
4716 &lt;pre&gt;
4717 if [ -d /sys/bus/usb/devices/ ] ; then
4718 echo loaded usb modules:
4719 (
4720 cd /sys/bus/usb/devices/
4721 for address in * ; do
4722 if [ -d &quot;$address/driver/module&quot; ] ; then
4723 module=`cd $address/driver/module ; pwd -P | xargs basename`
4724 if grep -q &quot;^$module &quot; /proc/modules ; then
4725 address=$(echo $address |sed s/0000://)
4726 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4727 if [ &quot;$id&quot; ] ; then
4728 echo &quot;$id $module&quot;
4729 fi
4730 fi
4731 fi
4732 done
4733 )
4734 echo
4735 fi
4736 &lt;/pre&gt;
4737
4738 &lt;p&gt;This might perhaps be something to include in other tools as
4739 well.&lt;/p&gt;
4740 </description>
4741 </item>
4742
4743 <item>
4744 <title>How to test if a laptop is working with Linux</title>
4745 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4746 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4747 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4748 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4749 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4750 batch of computers will work with Linux. Every year for the last few
4751 years the university have organised shared bid of a few thousand
4752 computers, and this year HP won the bid. Two different desktops and
4753 five different laptops are on the list this year. We in the UNIX
4754 group want to know which one of these computers work well with RHEL
4755 and Ubuntu, the two Linux distributions we currently handle at the
4756 university.&lt;/p&gt;
4757
4758 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4759 perhaps inspire others to test hardware as well. To test, I PXE
4760 install the OS version of choice, and log in as my normal user and run
4761 a few applications and plug in selected pieces of hardware. When
4762 something fail, I make a note about this in the test matrix and move
4763 on. If I have some spare time I try to report the bug to the OS
4764 vendor, but as I only have the machines for a short time, I rarely
4765 have the time to do this for all the problems I find.&lt;/p&gt;
4766
4767 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4768 I perform on a new model.&lt;/p&gt;
4769
4770 &lt;ul&gt;
4771
4772 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4773 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4774 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4775
4776 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4777 installation, X.org is working.&lt;/li&gt;
4778
4779 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4780 package mesa-utils on Ubuntu) and writing down the frames per second
4781 reported by the program.&lt;/li&gt;
4782
4783 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4784 logging in, and if I can hear this the test is successful. If there
4785 are several audio exits on the machine, I try them all and check if
4786 the Gnome/KDE audio mixer can control where to send the sound. I
4787 normally test this by playing
4788 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4789 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4790
4791 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4792 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4793
4794 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4795 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4796
4797 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4798 picture from the v4l device show up.&lt;/li&gt;
4799
4800 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4801 any bluetooth devices are discovered. In my office, I normally see a
4802 few.&lt;/li&gt;
4803
4804 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4805 memory modules lying around, and stick them in and see if Gnome/KDE
4806 notice this.&lt;/li&gt;
4807
4808 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4809 special button work, and if the laptop continue to work after
4810 resume.&lt;/li&gt;
4811
4812 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4813 adjusting background light, switching on/off external video output,
4814 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4815 laptop to laptop, so I just write down which are working and which are
4816 not.&lt;/li&gt;
4817
4818 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4819 acceleration sensors etc. I rarely test these, as I do not know how
4820 to quickly test if they are working or not, so I only document their
4821 existence.&lt;/li&gt;
4822
4823 &lt;/ul&gt;
4824
4825 &lt;p&gt;By now I suspect you are really curious what the test results are
4826 for the HP machines I am testing. I&#39;m not done yet, so I will report
4827 the test results later. For now I can report that HP 8100 Elite work
4828 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4829 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4830 can see, I have most machines left to test. One interesting
4831 observation is that Ubuntu Lucid has almost twice the frame rate than
4832 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4833 </description>
4834 </item>
4835
4836 <item>
4837 <title>Some thoughts on BitCoins</title>
4838 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4839 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4840 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4841 <description>&lt;p&gt;As I continue to explore
4842 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4843 what properties the system have, and how it will be affected by laws
4844 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4845
4846 &lt;p&gt;One interesting thing to note is that since the transactions are
4847 verified using a peer to peer network, all details about a transaction
4848 is known to everyone. This means that if a BitCoin address has been
4849 published like I did with mine in my initial post about BitCoin, it is
4850 possible for everyone to see how many BitCoins have been transfered to
4851 that address. There is even a web service to look at the details for
4852 all transactions. There I can see that my address
4853 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4854 have received 16.06 Bitcoin, the
4855 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4856 address of Simon Phipps have received 181.97 BitCoin and the address
4857 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4858 of EFF have received 2447.38 BitCoins so far. Thank you to each and
4859 every one of you that donated bitcoins to support my activity. The
4860 fact that anyone can see how much money was transfered to a given
4861 address make it more obvious why the BitCoin community recommend to
4862 generate and hand out a new address for each transaction. I&#39;m told
4863 there is no way to track which addresses belong to a given person or
4864 organisation without the person or organisation revealing it
4865 themselves, as Simon, EFF and I have done.&lt;/p&gt;
4866
4867 &lt;p&gt;In Norway, and in most other countries, there are laws and
4868 regulations limiting how much money one can transfer across the border
4869 without declaring it. There are money laundering, tax and accounting
4870 laws and regulations I would expect to apply to the use of BitCoin.
4871 If the Skolelinux foundation
4872 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
4873 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
4874 normal bank transfers like EFF is doing, how should this be accounted?
4875 Given that it is impossible to know if money can cross the border or
4876 not, should everything or nothing be declared? What exchange rate
4877 should be used when calculating taxes? Would receivers have to pay
4878 income tax if the foundation were to pay Skolelinux contributors in
4879 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
4880
4881 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
4882 accepted by a lot of users. It must be possible to get easy access to
4883 the currency (as a wage or using currency exchanges), and it must be
4884 easy to spend it. At the moment BitCoin seem fairly easy to get
4885 access to, but there are very few places to spend it. I am not really
4886 a regular user of any of the vendor types currently accepting BitCoin,
4887 so I wonder when my kind of shop would start accepting BitCoins. I
4888 would like to buy electronics, travels and subway tickets, not herbs
4889 and books. :) The currency is young, and this will improve over time
4890 if it become popular, but I suspect regular banks will start to lobby
4891 to get BitCoin declared illegal if it become popular. I&#39;m sure they
4892 will claim it is helping fund terrorism and money laundering (which
4893 probably would be true, as is any currency in existence), but I
4894 believe the problems should be solved elsewhere and not by blaming
4895 currencies.&lt;/p&gt;
4896
4897 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
4898 CPU intensive process that depend on a bit of luck as well (as one is
4899 competing against all the other miners currently spending CPU cycles
4900 to see which one get the next lump of cash). The &quot;winner&quot; get 50
4901 BitCoin when this happen. Yesterday I came across the obvious way to
4902 join forces to increase ones changes of getting at least some coins,
4903 by coordinating the work on mining BitCoins across several machines
4904 and people, and sharing the result if one is lucky and get the 50
4905 BitCoins. Check out
4906 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
4907 if this sounds interesting. I have not had time to try to set up a
4908 machine to participate there yet, but have seen that running on ones
4909 own for a few days have not yield any BitCoins througth mining
4910 yet.&lt;/p&gt;
4911
4912 &lt;p&gt;Update 2010-12-15: Found an &lt;a
4913 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
4914 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
4915 it was interesting to read. The arguments presented seem to be
4916 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
4917 </description>
4918 </item>
4919
4920 <item>
4921 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
4922 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
4923 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
4924 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
4925 <description>&lt;p&gt;With this weeks lawless
4926 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
4927 attacks&lt;/a&gt; on Wikileak and
4928 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
4929 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
4930 not be trusted to handle money transactions.
4931 A blog post from
4932 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
4933 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
4934 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
4935 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
4936 some help from my friend to get it all running, and he even handed me
4937 some bitcoins to get started. I even donated a few bitcoins to Simon
4938 for helping me remember BitCoin.&lt;/p&gt;
4939
4940 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
4941 crypto-currency, decentralised and handled using peer-to-peer
4942 networks. It allows anonymous transactions and prohibits central
4943 control over the transactions, making it impossible for governments
4944 and companies alike to block donations and other transactions. The
4945 source is free software, and while the key dependency wxWidgets 2.9
4946 for the graphical user interface is missing in Debian, the command
4947 line client builds just fine. Hopefully Jonas
4948 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
4949 Debian&lt;/a&gt; soon.&lt;/p&gt;
4950
4951 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
4952 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
4953 bitcoins&lt;/a&gt; when selling services and goods, and there are even
4954 currency &quot;stock&quot; markets where the exchange rate is decided. There
4955 are not many users so far, but the concept seems promising. If you
4956 want to get started and lack a friend with any bitcoins to spare,
4957 you can even get
4958 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
4959 bitcoin at the time of writing). Use
4960 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
4961 on the current exchange rates.&lt;/p&gt;
4962
4963 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
4964 machines. If you want to support my activity, please send Bitcoin
4965 donations to the address
4966 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
4967 </description>
4968 </item>
4969
4970 <item>
4971 <title>Why isn&#39;t Debian Edu using VLC?</title>
4972 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
4973 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
4974 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
4975 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4976 presented, and the winner among the multimedia player were VLC.
4977 Personally, I like VLC, and it is my player of choice when I first try
4978 to play a video file or stream. Only if VLC fail will I drag out
4979 gmplayer to see if it can do better. The reason is mostly the failure
4980 model and trust. When VLC fail, it normally pop up a error message
4981 reporting the problem. When mplayer fail, it normally segfault or
4982 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4983
4984 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4985 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4986 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4987 plugin to play web videos seamlessly, and the VLC browser plugin is
4988 not very good. For example, it lack in-line control buttons, so there
4989 is no way for the user to pause the video. Also, when I
4990 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
4991 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
4992 failed on several video pages where mplayer based plugins worked. If
4993 the browser plugin for VLC was as good as the gecko-mediaplayer
4994 package (which uses mplayer), we would switch.&lt;/P&gt;
4995
4996 &lt;p&gt;While VLC is a good player, its user interface is slightly
4997 annoying. The most annoying feature is its inconsistent use of
4998 keyboard shortcuts. When the player is in full screen mode, its
4999 shortcuts are different from when it is playing the video in a window.
5000 For example, space only work as pause when in full screen mode. I
5001 wish it had consisten shortcuts and that space also would work when in
5002 window mode. Another nice shortcut in gmplayer is [enter] to restart
5003 the current video. It is very nice when playing short videos from the
5004 web and want to restart it when new people arrive to have a look at
5005 what is going on.&lt;/p&gt;
5006 </description>
5007 </item>
5008
5009 <item>
5010 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5011 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5012 <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>
5013 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5014 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5015 upgrade testing of the
5016 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5017 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5018 This seem like a very good idea, so I adjusted by test scripts and
5019 can now present the updated result from today:&lt;/p&gt;
5020
5021 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5022
5023 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5024
5025 &lt;blockquote&gt;&lt;p&gt;
5026 apache2.2-bin
5027 aptdaemon
5028 baobab
5029 binfmt-support
5030 browser-plugin-gnash
5031 cheese-common
5032 cli-common
5033 cups-pk-helper
5034 dmz-cursor-theme
5035 empathy
5036 empathy-common
5037 freedesktop-sound-theme
5038 freeglut3
5039 gconf-defaults-service
5040 gdm-themes
5041 gedit-plugins
5042 geoclue
5043 geoclue-hostip
5044 geoclue-localnet
5045 geoclue-manual
5046 geoclue-yahoo
5047 gnash
5048 gnash-common
5049 gnome
5050 gnome-backgrounds
5051 gnome-cards-data
5052 gnome-codec-install
5053 gnome-core
5054 gnome-desktop-environment
5055 gnome-disk-utility
5056 gnome-screenshot
5057 gnome-search-tool
5058 gnome-session-canberra
5059 gnome-system-log
5060 gnome-themes-extras
5061 gnome-themes-more
5062 gnome-user-share
5063 gstreamer0.10-fluendo-mp3
5064 gstreamer0.10-tools
5065 gtk2-engines
5066 gtk2-engines-pixbuf
5067 gtk2-engines-smooth
5068 hamster-applet
5069 libapache2-mod-dnssd
5070 libapr1
5071 libaprutil1
5072 libaprutil1-dbd-sqlite3
5073 libaprutil1-ldap
5074 libart2.0-cil
5075 libboost-date-time1.42.0
5076 libboost-python1.42.0
5077 libboost-thread1.42.0
5078 libchamplain-0.4-0
5079 libchamplain-gtk-0.4-0
5080 libcheese-gtk18
5081 libclutter-gtk-0.10-0
5082 libcryptui0
5083 libdiscid0
5084 libelf1
5085 libepc-1.0-2
5086 libepc-common
5087 libepc-ui-1.0-2
5088 libfreerdp-plugins-standard
5089 libfreerdp0
5090 libgconf2.0-cil
5091 libgdata-common
5092 libgdata7
5093 libgdu-gtk0
5094 libgee2
5095 libgeoclue0
5096 libgexiv2-0
5097 libgif4
5098 libglade2.0-cil
5099 libglib2.0-cil
5100 libgmime2.4-cil
5101 libgnome-vfs2.0-cil
5102 libgnome2.24-cil
5103 libgnomepanel2.24-cil
5104 libgpod-common
5105 libgpod4
5106 libgtk2.0-cil
5107 libgtkglext1
5108 libgtksourceview2.0-common
5109 libmono-addins-gui0.2-cil
5110 libmono-addins0.2-cil
5111 libmono-cairo2.0-cil
5112 libmono-corlib2.0-cil
5113 libmono-i18n-west2.0-cil
5114 libmono-posix2.0-cil
5115 libmono-security2.0-cil
5116 libmono-sharpzip2.84-cil
5117 libmono-system2.0-cil
5118 libmtp8
5119 libmusicbrainz3-6
5120 libndesk-dbus-glib1.0-cil
5121 libndesk-dbus1.0-cil
5122 libopal3.6.8
5123 libpolkit-gtk-1-0
5124 libpt2.6.7
5125 libpython2.6
5126 librpm1
5127 librpmio1
5128 libsdl1.2debian
5129 libsrtp0
5130 libssh-4
5131 libtelepathy-farsight0
5132 libtelepathy-glib0
5133 libtidy-0.99-0
5134 media-player-info
5135 mesa-utils
5136 mono-2.0-gac
5137 mono-gac
5138 mono-runtime
5139 nautilus-sendto
5140 nautilus-sendto-empathy
5141 p7zip-full
5142 pkg-config
5143 python-aptdaemon
5144 python-aptdaemon-gtk
5145 python-axiom
5146 python-beautifulsoup
5147 python-bugbuddy
5148 python-clientform
5149 python-coherence
5150 python-configobj
5151 python-crypto
5152 python-cupshelpers
5153 python-elementtree
5154 python-epsilon
5155 python-evolution
5156 python-feedparser
5157 python-gdata
5158 python-gdbm
5159 python-gst0.10
5160 python-gtkglext1
5161 python-gtksourceview2
5162 python-httplib2
5163 python-louie
5164 python-mako
5165 python-markupsafe
5166 python-mechanize
5167 python-nevow
5168 python-notify
5169 python-opengl
5170 python-openssl
5171 python-pam
5172 python-pkg-resources
5173 python-pyasn1
5174 python-pysqlite2
5175 python-rdflib
5176 python-serial
5177 python-tagpy
5178 python-twisted-bin
5179 python-twisted-conch
5180 python-twisted-core
5181 python-twisted-web
5182 python-utidylib
5183 python-webkit
5184 python-xdg
5185 python-zope.interface
5186 remmina
5187 remmina-plugin-data
5188 remmina-plugin-rdp
5189 remmina-plugin-vnc
5190 rhythmbox-plugin-cdrecorder
5191 rhythmbox-plugins
5192 rpm-common
5193 rpm2cpio
5194 seahorse-plugins
5195 shotwell
5196 software-center
5197 system-config-printer-udev
5198 telepathy-gabble
5199 telepathy-mission-control-5
5200 telepathy-salut
5201 tomboy
5202 totem
5203 totem-coherence
5204 totem-mozilla
5205 totem-plugins
5206 transmission-common
5207 xdg-user-dirs
5208 xdg-user-dirs-gtk
5209 xserver-xephyr
5210 &lt;/p&gt;&lt;/blockquote&gt;
5211
5212 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5213
5214 &lt;blockquote&gt;&lt;p&gt;
5215 cheese
5216 ekiga
5217 eog
5218 epiphany-extensions
5219 evolution-exchange
5220 fast-user-switch-applet
5221 file-roller
5222 gcalctool
5223 gconf-editor
5224 gdm
5225 gedit
5226 gedit-common
5227 gnome-games
5228 gnome-games-data
5229 gnome-nettool
5230 gnome-system-tools
5231 gnome-themes
5232 gnuchess
5233 gucharmap
5234 guile-1.8-libs
5235 libavahi-ui0
5236 libdmx1
5237 libgalago3
5238 libgtk-vnc-1.0-0
5239 libgtksourceview2.0-0
5240 liblircclient0
5241 libsdl1.2debian-alsa
5242 libspeexdsp1
5243 libsvga1
5244 rhythmbox
5245 seahorse
5246 sound-juicer
5247 system-config-printer
5248 totem-common
5249 transmission-gtk
5250 vinagre
5251 vino
5252 &lt;/p&gt;&lt;/blockquote&gt;
5253
5254 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5255
5256 &lt;blockquote&gt;&lt;p&gt;
5257 gstreamer0.10-gnomevfs
5258 &lt;/p&gt;&lt;/blockquote&gt;
5259
5260 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5261
5262 &lt;blockquote&gt;&lt;p&gt;
5263 [nothing]
5264 &lt;/p&gt;&lt;/blockquote&gt;
5265
5266 &lt;p&gt;This is for KDE:&lt;/p&gt;
5267
5268 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5269
5270 &lt;blockquote&gt;&lt;p&gt;
5271 ksmserver
5272 &lt;/p&gt;&lt;/blockquote&gt;
5273
5274 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5275
5276 &lt;blockquote&gt;&lt;p&gt;
5277 kwin
5278 network-manager-kde
5279 &lt;/p&gt;&lt;/blockquote&gt;
5280
5281 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5282
5283 &lt;blockquote&gt;&lt;p&gt;
5284 arts
5285 dolphin
5286 freespacenotifier
5287 google-gadgets-gst
5288 google-gadgets-xul
5289 kappfinder
5290 kcalc
5291 kcharselect
5292 kde-core
5293 kde-plasma-desktop
5294 kde-standard
5295 kde-window-manager
5296 kdeartwork
5297 kdeartwork-emoticons
5298 kdeartwork-style
5299 kdeartwork-theme-icon
5300 kdebase
5301 kdebase-apps
5302 kdebase-workspace
5303 kdebase-workspace-bin
5304 kdebase-workspace-data
5305 kdeeject
5306 kdelibs
5307 kdeplasma-addons
5308 kdeutils
5309 kdewallpapers
5310 kdf
5311 kfloppy
5312 kgpg
5313 khelpcenter4
5314 kinfocenter
5315 konq-plugins-l10n
5316 konqueror-nsplugins
5317 kscreensaver
5318 kscreensaver-xsavers
5319 ktimer
5320 kwrite
5321 libgle3
5322 libkde4-ruby1.8
5323 libkonq5
5324 libkonq5-templates
5325 libnetpbm10
5326 libplasma-ruby
5327 libplasma-ruby1.8
5328 libqt4-ruby1.8
5329 marble-data
5330 marble-plugins
5331 netpbm
5332 nuvola-icon-theme
5333 plasma-dataengines-workspace
5334 plasma-desktop
5335 plasma-desktopthemes-artwork
5336 plasma-runners-addons
5337 plasma-scriptengine-googlegadgets
5338 plasma-scriptengine-python
5339 plasma-scriptengine-qedje
5340 plasma-scriptengine-ruby
5341 plasma-scriptengine-webkit
5342 plasma-scriptengines
5343 plasma-wallpapers-addons
5344 plasma-widget-folderview
5345 plasma-widget-networkmanagement
5346 ruby
5347 sweeper
5348 update-notifier-kde
5349 xscreensaver-data-extra
5350 xscreensaver-gl
5351 xscreensaver-gl-extra
5352 xscreensaver-screensaver-bsod
5353 &lt;/p&gt;&lt;/blockquote&gt;
5354
5355 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5356
5357 &lt;blockquote&gt;&lt;p&gt;
5358 ark
5359 google-gadgets-common
5360 google-gadgets-qt
5361 htdig
5362 kate
5363 kdebase-bin
5364 kdebase-data
5365 kdepasswd
5366 kfind
5367 klipper
5368 konq-plugins
5369 konqueror
5370 ksysguard
5371 ksysguardd
5372 libarchive1
5373 libcln6
5374 libeet1
5375 libeina-svn-06
5376 libggadget-1.0-0b
5377 libggadget-qt-1.0-0b
5378 libgps19
5379 libkdecorations4
5380 libkephal4
5381 libkonq4
5382 libkonqsidebarplugin4a
5383 libkscreensaver5
5384 libksgrd4
5385 libksignalplotter4
5386 libkunitconversion4
5387 libkwineffects1a
5388 libmarblewidget4
5389 libntrack-qt4-1
5390 libntrack0
5391 libplasma-geolocation-interface4
5392 libplasmaclock4a
5393 libplasmagenericshell4
5394 libprocesscore4a
5395 libprocessui4a
5396 libqalculate5
5397 libqedje0a
5398 libqtruby4shared2
5399 libqzion0a
5400 libruby1.8
5401 libscim8c2a
5402 libsmokekdecore4-3
5403 libsmokekdeui4-3
5404 libsmokekfile3
5405 libsmokekhtml3
5406 libsmokekio3
5407 libsmokeknewstuff2-3
5408 libsmokeknewstuff3-3
5409 libsmokekparts3
5410 libsmokektexteditor3
5411 libsmokekutils3
5412 libsmokenepomuk3
5413 libsmokephonon3
5414 libsmokeplasma3
5415 libsmokeqtcore4-3
5416 libsmokeqtdbus4-3
5417 libsmokeqtgui4-3
5418 libsmokeqtnetwork4-3
5419 libsmokeqtopengl4-3
5420 libsmokeqtscript4-3
5421 libsmokeqtsql4-3
5422 libsmokeqtsvg4-3
5423 libsmokeqttest4-3
5424 libsmokeqtuitools4-3
5425 libsmokeqtwebkit4-3
5426 libsmokeqtxml4-3
5427 libsmokesolid3
5428 libsmokesoprano3
5429 libtaskmanager4a
5430 libtidy-0.99-0
5431 libweather-ion4a
5432 libxklavier16
5433 libxxf86misc1
5434 okteta
5435 oxygencursors
5436 plasma-dataengines-addons
5437 plasma-scriptengine-superkaramba
5438 plasma-widget-lancelot
5439 plasma-widgets-addons
5440 plasma-widgets-workspace
5441 polkit-kde-1
5442 ruby1.8
5443 systemsettings
5444 update-notifier-common
5445 &lt;/p&gt;&lt;/blockquote&gt;
5446
5447 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5448 aptitude a bit more similar, but there are still quite a lott of
5449 differences. I have no idea what packages should be installed after
5450 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5451 </description>
5452 </item>
5453
5454 <item>
5455 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5456 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5457 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5458 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5459 <description>&lt;p&gt;Most of the computers in use by the
5460 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5461 are virtual machines. And they have been Xen machines running on a
5462 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5463 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5464 bit harder that it could have been, because we set up the Xen virtual
5465 machines to get the virtual partitions from LVM, which as far as I
5466 know is not supported by KVM. So to migrate, we had to convert
5467 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5468
5469 &lt;p&gt;I found
5470 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5471 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5472 migration. It uses qemu-img from the qemu package to make the disk
5473 image, parted to partition it, losetup and kpartx to present the disk
5474 image partions as devices, and dd to copy the data. I NFS mounted the
5475 new servers storage area on the old server to do the migration.&lt;/p&gt;
5476
5477 &lt;pre&gt;
5478 #!/bin/sh
5479
5480 # Based on
5481 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5482
5483 set -e
5484 set -x
5485
5486 if [ -z &quot;$1&quot; ] ; then
5487 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5488 exit 1
5489 else
5490 host=&quot;$1&quot;
5491 fi
5492
5493 if [ ! -e /dev/vg_data/$host-disk ] ; then
5494 echo &quot;error: unable to find LVM volume for $host&quot;
5495 exit 1
5496 fi
5497
5498 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5499 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5500 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5501 totalsize=$(( ( $disksize + $swapsize ) ))
5502
5503 img=$host.img
5504 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5505 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5506
5507 parted $img mklabel msdos
5508 parted $img mkpart primary linux-swap 0 $disksize
5509 parted $img mkpart primary ext2 $disksize $totalsize
5510 parted $img set 1 boot on
5511
5512 modprobe dm-mod
5513 losetup /dev/loop0 $img
5514 kpartx -a /dev/loop0
5515
5516 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5517 fsck.ext3 -f /dev/mapper/loop0p1 || true
5518 mkswap /dev/mapper/loop0p2
5519
5520 kpartx -d /dev/loop0
5521 losetup -d /dev/loop0
5522 &lt;/pre&gt;
5523
5524 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5525 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5526
5527 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5528 the new disk image attached, installed grub-pc and linux-image-686 and
5529 set up grub to boot from the disk image. After this, the KVM machines
5530 seem to work just fine.&lt;/p&gt;
5531 </description>
5532 </item>
5533
5534 <item>
5535 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5536 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5537 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5538 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5539 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5540 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5541 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5542 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5543
5544 &lt;p&gt;I still do not know what a correct migration should look like, so I
5545 report any differences between apt and aptitude and hope someone else
5546 can see if anything should be changed.&lt;/p&gt;
5547
5548 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5549
5550 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5551
5552 &lt;blockquote&gt;&lt;p&gt;
5553 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5554 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5555 dmz-cursor-theme empathy empathy-common finger
5556 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5557 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5558 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5559 gnome-cards-data gnome-codec-install gnome-core
5560 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5561 gnome-search-tool gnome-session-canberra gnome-spell
5562 gnome-system-log gnome-themes-extras gnome-themes-more
5563 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5564 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5565 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5566 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5567 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5568 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5569 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5570 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5571 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5572 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5573 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5574 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5575 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5576 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5577 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5578 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5579 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5580 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5581 libmono-security2.0-cil libmono-sharpzip2.84-cil
5582 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5583 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5584 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5585 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5586 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5587 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5588 libxalan2-java libxerces2-java media-player-info mesa-utils
5589 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5590 nautilus-sendto-empathy openoffice.org-writer2latex
5591 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5592 python-aptdaemon python-aptdaemon-gtk python-axiom
5593 python-beautifulsoup python-bugbuddy python-clientform
5594 python-coherence python-configobj python-crypto python-cupshelpers
5595 python-cupsutils python-eggtrayicon python-elementtree
5596 python-epsilon python-evolution python-feedparser python-gdata
5597 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5598 python-gtksourceview2 python-httplib2 python-louie python-mako
5599 python-markupsafe python-mechanize python-nevow python-notify
5600 python-opengl python-openssl python-pam python-pkg-resources
5601 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5602 python-tagpy python-twisted-bin python-twisted-conch
5603 python-twisted-core python-twisted-web python-utidylib python-webkit
5604 python-xdg python-zope.interface remmina remmina-plugin-data
5605 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5606 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5607 software-center svgalibg1 system-config-printer-udev
5608 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5609 totem totem-coherence totem-mozilla totem-plugins
5610 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5611 zip
5612 &lt;/p&gt;&lt;/blockquote&gt;
5613
5614 Installed using apt-get, removed with aptitude
5615
5616 &lt;blockquote&gt;&lt;p&gt;
5617 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5618 epiphany-extensions epiphany-gecko evolution-exchange
5619 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5620 gedit-common gnome-app-install gnome-games gnome-games-data
5621 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5622 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5623 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5624 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5625 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5626 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5627 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5628 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5629 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5630 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5631 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5632 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5633 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5634 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5635 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5636 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5637 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5638 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5639 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5640 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5641 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5642 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5643 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5644 sound-juicer swfdec-gnome system-config-printer totem-common
5645 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5646 &lt;/p&gt;&lt;/blockquote&gt;
5647
5648 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5649
5650 &lt;blockquote&gt;&lt;p&gt;
5651 gstreamer0.10-gnomevfs
5652 &lt;/p&gt;&lt;/blockquote&gt;
5653
5654 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5655
5656 &lt;blockquote&gt;&lt;p&gt;
5657 [nothing]
5658 &lt;/p&gt;&lt;/blockquote&gt;
5659
5660 &lt;p&gt;This is for KDE:&lt;/p&gt;
5661
5662 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5663
5664 &lt;blockquote&gt;&lt;p&gt;
5665 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5666 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5667 ghostscript-x git gnome-audio gnugo granatier gs-common
5668 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5669 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5670 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5671 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5672 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5673 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5674 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5675 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5676 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5677 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5678 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5679 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5680 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5681 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5682 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5683 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5684 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5685 libkrossui4 libmailtools-perl libmime-tools-perl
5686 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5687 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5688 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5689 lirc luatex marble networkstatus noatun-plugins
5690 openoffice.org-writer2latex palapeli palapeli-data parley
5691 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5692 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5693 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5694 ttf-sazanami-gothic
5695 &lt;/p&gt;&lt;/blockquote&gt;
5696
5697 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5698
5699 &lt;blockquote&gt;&lt;p&gt;
5700 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5701 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5702 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5703 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5704 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5705 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5706 kitchensync kiten kjumpingcube klatin klettres klickety klines
5707 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5708 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5709 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5710 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5711 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5712 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5713 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5714 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5715 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5716 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5717 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5718 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5719 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5720 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5721 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5722 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5723 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5724 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5725 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5726 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5727 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5728 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5729 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5730 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5731 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5732 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5733 &lt;/p&gt;&lt;/blockquote&gt;
5734
5735 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5736
5737 &lt;blockquote&gt;&lt;p&gt;
5738 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5739 kdeartwork kdebase kdebase-apps kdebase-workspace
5740 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5741 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5742 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5743 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5744 xscreensaver-screensaver-bsod
5745 &lt;/p&gt;&lt;/blockquote&gt;
5746
5747 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5748
5749 &lt;blockquote&gt;&lt;p&gt;
5750 kdebase-bin konq-plugins konqueror
5751 &lt;/p&gt;&lt;/blockquote&gt;
5752 </description>
5753 </item>
5754
5755 <item>
5756 <title>Gnash buildbot slave and Debian kfreebsd</title>
5757 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5758 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5759 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5760 <description>&lt;p&gt;Answering
5761 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5762 call from the Gnash project&lt;/a&gt; for
5763 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5764 current source, I have set up a virtual KVM machine on the Debian
5765 Edu/Skolelinux virtualization host to test the git source on
5766 Debian/Squeeze. I hope this can help the developers in getting new
5767 releases out more often.&lt;/p&gt;
5768
5769 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5770 I have considered setting up a &lt;a
5771 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5772 machine as well. I have also considered using the kfreebsd
5773 architecture in Debian as a file server in NUUG to get access to the 5
5774 TB zfs volume we currently use to store DV video. Because of this, I
5775 finally got around to do a test installation of Debian/Squeeze with
5776 kfreebsd. Installation went fairly smooth, thought I noticed some
5777 visual glitches in the cdebconf dialogs (black cursor left on the
5778 screen at random locations). Have not gotten very far with the
5779 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5780 fatal problem. Have to spend some more time on it to see if it is
5781 useful as a file server for NUUG. Will try to find time to set up a
5782 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5783 </description>
5784 </item>
5785
5786 <item>
5787 <title>Debian in 3D</title>
5788 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5789 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5790 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5791 <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;
5792
5793 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5794 3D linked in from
5795 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5796 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5797 </description>
5798 </item>
5799
5800 <item>
5801 <title>Software updates 2010-10-24</title>
5802 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5803 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5804 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5805 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5806
5807 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5808 raise money for the project is going well. The lower limit of 10
5809 signers was reached in 24 hours, and so far 13 people have signed it.
5810 More signers and more funding is most welcome, and I am really curious
5811 how far we can get before the time limit of December 24 is reached.
5812 :)&lt;/p&gt;
5813
5814 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5815 about what appear to be a great code coverage tool capable of
5816 generating code coverage stats without any changes to the source code.
5817 It is called
5818 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5819 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5820 It is missing in Debian, but the git source built just fine in Squeeze
5821 after I installed libelf-dev, libdwarf-dev, pkg-config and
5822 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5823 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5824
5825 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5826 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5827 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5828 alpha test release of the Squeeze based Debian Edu /
5829 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5830 release. Give it a try if you need a complete linux solution for your
5831 school, including central infrastructure server, workstations, thin
5832 client servers and diskless workstations. A nice touch added
5833 yesterday is RDP support on the thin client servers, for windows
5834 clients to get a Linux desktop on request.&lt;/p&gt;
5835 </description>
5836 </item>
5837
5838 <item>
5839 <title>Some notes on Flash in Debian and Debian Edu</title>
5840 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5841 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5842 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5843 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5844 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5845 second most popular used package that is missing in Debian. The sixth
5846 most popular is flashplayer-mozilla. This is a clear indication that
5847 working flash is important for Debian users. Around 10 percent of the
5848 users submitting data to popcon.debian.org have this package
5849 installed.&lt;/p&gt;
5850
5851 &lt;p&gt;In the report written by Lars Risan in August 2008
5852&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
5853 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5854 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5855 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5856 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5857 web sites require Flash to work, and lacking working Flash support in
5858 the web browser and the problems with installing it was perceived as a
5859 good reason to stay with Windows.&lt;/p&gt;
5860
5861 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
5862 said to be the retarded cousin that did not really understand
5863 everything you told him but could work fairly well. This was a
5864 comment regarding the problems Linux have with proprietary formats and
5865 non-standard web pages, and is sad because it exposes a fairly common
5866 understanding of whose fault it is if web pages that only work in for
5867 example Internet Explorer 6 fail to work on Firefox, and funny because
5868 it explain very well how annoying it is for users when Linux
5869 distributions do not work with the documents they receive or the web
5870 pages they want to visit.&lt;/p&gt;
5871
5872 &lt;p&gt;This is part of the reason why I believe it is important for Debian
5873 and Debian Edu to have a well working Flash implementation in the
5874 distribution, to get at least popular sites as Youtube and Google
5875 Video to working out of the box. For Squeeze, Debian have the chance
5876 to include the latest version of Gnash that will make this happen, as
5877 the new release 0.8.8 was published a few weeks ago and is resting in
5878 unstable. The new version work with more sites that version 0.8.7.
5879 The Gnash maintainers have asked for a freeze exception, but the
5880 release team have not had time to reply to it yet. I hope they agree
5881 with me that Flash is important for the Debian desktop users, and thus
5882 accept the new package into Squeeze.&lt;/p&gt;
5883 </description>
5884 </item>
5885
5886 <item>
5887 <title>Circular package dependencies harms apt recovery</title>
5888 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
5889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
5890 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
5891 <description>&lt;p&gt;I discovered this while doing
5892 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
5893 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
5894 in Debian still got circular dependencies, and it is often claimed
5895 that apt and aptitude should be able to handle this just fine, but
5896 some times these dependency loops causes apt to fail.&lt;/p&gt;
5897
5898 &lt;p&gt;An example is from todays
5899 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
5900 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
5901 causes perl-modules to fail to upgrade. The cause is simple. If a
5902 package fail to unpack, then only part of packages with the circular
5903 dependency might end up being unpacked when unpacking aborts, and the
5904 ones already unpacked will fail to configure in the recovery phase
5905 because its dependencies are unavailable.&lt;/p&gt;
5906
5907 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
5908
5909 &lt;blockquote&gt;&lt;pre&gt;
5910 dpkg: dependency problems prevent configuration of perl-modules:
5911 perl-modules depends on perl (&gt;= 5.10.1-1); however:
5912 Version of perl on system is 5.10.0-19lenny2.
5913 dpkg: error processing perl-modules (--configure):
5914 dependency problems - leaving unconfigured
5915 &lt;/pre&gt;&lt;/blockquote&gt;
5916
5917 &lt;p&gt;The perl/perl-modules circular dependency is already
5918 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
5919 hopefully be solved as soon as possible, but it is not the only one,
5920 and each one of these loops in the dependency tree can cause similar
5921 failures. Of course, they only occur when there are bugs in other
5922 packages causing the unpacking to fail, but it is rather nasty when
5923 the failure of one package causes the problem to become worse because
5924 of dependency loops.&lt;/p&gt;
5925
5926 &lt;p&gt;Thanks to
5927 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
5928 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
5929 dependencies
5930 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
5931 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
5932
5933 &lt;p&gt;Todays testing also exposed a bug in
5934 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
5935 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
5936 apt-get and aptitude, the latter possibly caused by some circular
5937 dependency. Reported both to BTS to try to get someone to look at
5938 it.&lt;/p&gt;
5939 </description>
5940 </item>
5941
5942 <item>
5943 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
5944 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
5945 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
5946 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
5947 <description>&lt;p&gt;This is a
5948 &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;
5949 on my
5950 &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
5951 work&lt;/a&gt; on
5952 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
5953 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
5954
5955 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
5956 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5957 and dhcp3-server-ldap in Debian use the LDAP server. The two
5958 implementations are quite different in how they use LDAP.&lt;/p&gt;
5959
5960 To get this information, I started slapd with debugging enabled and
5961 dumped the debug output to a file to get the LDAP searches performed
5962 on a Debian Edu main-server. Here is a summary.
5963
5964 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
5965
5966 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
5967 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
5968 the web.
5969
5970 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
5971 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
5972 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
5973 reverse entries are in two different subtrees in LDAP with a structure
5974 based on the DNS names, as in tjener.intern and
5975 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5976
5977 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5978 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5979 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5980 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5981 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5982 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5983 forward entries, it is looking for attributes named dnsttl, arecord,
5984 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5985 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5986 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5987 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5988 spfrecord and modifytimestamp. For reverse entries it is looking for
5989 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5990 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5991 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5992 ldapsearch commands could look like this:&lt;/p&gt;
5993
5994 &lt;blockquote&gt;&lt;pre&gt;
5995 ldapsearch -h ldap \
5996 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5997 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5998 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5999 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6000 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6001 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6002
6003 ldapsearch -h ldap \
6004 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6005 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6006 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6007 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6008 srvrecord naptrrecord modifytimestamp
6009 &lt;/pre&gt;&lt;/blockquote&gt;
6010
6011 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6012 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6013 example LDAP objects used there. In addition to these objects, the
6014 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6015 also exist.&lt;/p&gt;
6016
6017 &lt;blockquote&gt;&lt;pre&gt;
6018 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6019 objectclass: top
6020 objectclass: dnsdomain
6021 objectclass: domainrelatedobject
6022 dc: tjener
6023 arecord: 10.0.2.2
6024 associateddomain: tjener.intern
6025
6026 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6027 objectclass: top
6028 objectclass: dnsdomain2
6029 objectclass: domainrelatedobject
6030 dc: 2
6031 ptrrecord: tjener.intern
6032 associateddomain: 2.2.0.10.in-addr.arpa
6033 &lt;/pre&gt;&lt;/blockquote&gt;
6034
6035 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6036 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6037 same base as in the tree mode for a object with filter
6038 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6039 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6040 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6041 naptrrecord and modifytimestamp. For reverse entires it also do a
6042 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6043 and the requested attributes are associateddomain, dnsttl and
6044 modifytimestamp. In short, in strict mode the objects with ptrrecord
6045 go away, and the arecord attribute in the forward object is used
6046 instead.&lt;/p&gt;
6047
6048 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6049 like this:&lt;/p&gt;
6050
6051 &lt;blockquote&gt;&lt;pre&gt;
6052 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6053 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6054 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6055 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6056 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6057 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6058
6059 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6060 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6061 &lt;/pre&gt;&lt;/blockquote&gt;
6062
6063 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6064 search for SOA records, which behave similar to the forward and
6065 reverse lookups.&lt;/p&gt;
6066
6067 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6068 specify any objectclass names, and instead look for the attributes it
6069 need to generate a DNS reply. This make it able to work with any
6070 objectclass that provide the needed attributes.&lt;/p&gt;
6071
6072 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6073 dnsdomain2 schemas. The latter is used for reverse entries like
6074 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6075
6076 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6077 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6078 attributes) and domainrelatedobject (for associatedDomain). The use
6079 of structural object classes make it impossible to combine these
6080 classes with the object classes used by DHCP.&lt;/p&gt;
6081
6082 &lt;p&gt;There are other schemas that could be used too, for example the
6083 dnszone structural object class used by Gosa and bind-sdb for the DNS
6084 attributes combined with the domainrelatedobject object class, but in
6085 this case some unused attributes would have to be included as well
6086 (zonename and relativedomainname).&lt;/p&gt;
6087
6088 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6089 mode and not use any of the existing objectclasses (dnsdomain,
6090 dnsdomain2 and dnszone) when one want to combine the DNS information
6091 with DHCP information, and instead create a auxiliary object class
6092 defined something like this (using the attributes defined for
6093 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6094
6095 &lt;blockquote&gt;&lt;pre&gt;
6096 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6097 SUP top
6098 AUXILIARY
6099 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6100 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6101 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6102 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6103 A6Record $ DNAMERecord
6104 ))
6105 &lt;/pre&gt;&lt;/blockquote&gt;
6106
6107 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6108 the domainrelatedobject object class, and allow any entity to include
6109 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6110 developers asking for their view on this schema and if they are
6111 interested in providing such schema with PowerDNS, and I hope my
6112 message will be accepted into their mailing list soon.&lt;/p&gt;
6113
6114 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6115
6116 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6117 the object attributes, and then uses the attributes it want. This
6118 make it harder to figure out exactly what attributes are used, but
6119 thanks to the working example in Debian Edu I can at least get an idea
6120 what is needed without having to read the source code.&lt;/p&gt;
6121
6122 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6123 search filter to use to locate the correct dhcpServer entity is
6124 stored. These are the relevant entries from
6125 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6126
6127 &lt;blockquote&gt;&lt;pre&gt;
6128 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6129 ldap-dhcp-server-cn &quot;dhcp&quot;;
6130 &lt;/pre&gt;&lt;/blockquote&gt;
6131
6132 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6133 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6134 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6135 search result is this entry:&lt;/p&gt;
6136
6137 &lt;blockquote&gt;&lt;pre&gt;
6138 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6139 cn: dhcp
6140 objectClass: top
6141 objectClass: dhcpServer
6142 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6143 &lt;/pre&gt;&lt;/blockquote&gt;
6144
6145 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6146 subtree with DHCP configuration. The DHCP configuration subtree base
6147 is located using a base scope search with base &quot;cn=DHCP
6148 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6149 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6150 The search result is this entry:&lt;/p&gt;
6151
6152 &lt;blockquote&gt;&lt;pre&gt;
6153 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6154 cn: DHCP Config
6155 objectClass: top
6156 objectClass: dhcpService
6157 objectClass: dhcpOptions
6158 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6159 dhcpStatements: ddns-update-style none
6160 dhcpStatements: authoritative
6161 dhcpOption: smtp-server code 69 = array of ip-address
6162 dhcpOption: www-server code 72 = array of ip-address
6163 dhcpOption: wpad-url code 252 = text
6164 &lt;/pre&gt;&lt;/blockquote&gt;
6165
6166 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6167 all the DHCP configuration is loaded, it is ready to receive requests.
6168 The subtree in Debian Edu contain objects with object classes
6169 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6170 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6171 and information about netmasks, dynamic range etc. Leaving out the
6172 details here because it is not relevant for the focus of my
6173 investigation, which is to see if it is possible to merge dns and dhcp
6174 related computer objects.&lt;/p&gt;
6175
6176 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6177 of the client (00:00:00:00:00:00 in this example), using a subtree
6178 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6179 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6180 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6181 like:&lt;/p&gt;
6182
6183 &lt;blockquote&gt;&lt;pre&gt;
6184 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6185 cn: hostname
6186 objectClass: top
6187 objectClass: dhcpHost
6188 dhcpHWAddress: ethernet 00:00:00:00:00:00
6189 dhcpStatements: fixed-address hostname
6190 &lt;/pre&gt;&lt;/blockquote&gt;
6191
6192 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6193 The object classes need to have fixed names, and the configuration
6194 need to be stored in a fairly specific LDAP structure. On the
6195 positive side, the invidiual dhcpHost entires can be anywhere without
6196 the DN pointed to by the dhcpServer entries. The latter should make
6197 it possible to group all host entries in a subtree next to the
6198 configuration entries, and this subtree can also be shared with the
6199 DNS server if the schema proposed above is combined with the dhcpHost
6200 structural object class.
6201
6202 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6203
6204 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6205 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6206 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6207 allowing DNS objects to be stored anywhere under the base cn specified
6208 in the configuration.&lt;/p&gt;
6209
6210 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6211 regarding which LDAP schemas to use and which LDAP structure to use.
6212 I guess one could implement ones own schema, as long as the
6213 objectclasses and attributes have the names used, but this do not
6214 really help when the DHCP subtree need to have a fairly fixed
6215 structure.&lt;/p&gt;
6216
6217 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6218 this might work for Debian Edu:&lt;/p&gt;
6219
6220 &lt;blockquote&gt;&lt;pre&gt;
6221 ou=services
6222 cn=machine-info (dhcpService) - dhcpServiceDN points here
6223 cn=dhcp (dhcpServer)
6224 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6225 cn=10.0.2.0 (dhcpSubnet)
6226 cn=group1 (dhcpGroup/dhcpOptions)
6227 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6228 cn=192.168.0.0 (dhcpSubnet)
6229 cn=group1 (dhcpGroup/dhcpOptions)
6230 ou=machines - PowerDNS base points here
6231 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6232 &lt;/pre&gt;&lt;/blockquote&gt;
6233
6234 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6235 entries to be in the dhcpGroup subtrees, the entries can be stored
6236 there instead of a common machines subtree, and the PowerDNS base
6237 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6238
6239 &lt;p&gt;The combined object under the machines subtree would look something
6240 like this:&lt;/p&gt;
6241
6242 &lt;blockquote&gt;&lt;pre&gt;
6243 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6244 dc: hostname
6245 objectClass: top
6246 objectClass: dhcpHost
6247 objectclass: domainrelatedobject
6248 objectclass: dnsDomainAux
6249 associateddomain: hostname.intern
6250 arecord: 10.11.12.13
6251 dhcpHWAddress: ethernet 00:00:00:00:00:00
6252 dhcpStatements: fixed-address hostname.intern
6253 &lt;/pre&gt;&lt;/blockquote&gt;
6254
6255 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6256 machine, as long as the required attributes are available in a
6257 auxiliary object class.&lt;/p&gt;
6258 </description>
6259 </item>
6260
6261 <item>
6262 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6263 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6264 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6265 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6266 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6267 DHCP services in Debian Edu to use the same LDAP objects for a given
6268 computer, to avoid the possibility of having a inconsistent state for
6269 a computer in LDAP (as in DHCP but no DNS entry or the other way
6270 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6271
6272 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6273 information finally found a solution that seem to work.&lt;/p&gt;
6274
6275 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6276 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6277 we switch powerdns to use its strict LDAP method (ldap-method=strict
6278 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6279 merged into one while making it impossible to transfer the reverse map
6280 to a slave DNS server.&lt;/p&gt;
6281
6282 &lt;p&gt;If we also replace the object class used to get the DNS related
6283 attributes to one allowing these attributes to be combined with the
6284 dhcphost object class, we can merge the DNS and DHCP entries into one.
6285 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6286 proper OIDs, but that is a minor issue), and tested the setup. It
6287 seem to work.&lt;/p&gt;
6288
6289 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6290 for both DNS and DHCP, and even the LTSP configuration I suggested in
6291 an earlier email. The combined LDAP object will look something like
6292 this:&lt;/p&gt;
6293
6294 &lt;blockquote&gt;&lt;pre&gt;
6295 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6296 cn: hostname
6297 objectClass: dhcphost
6298 objectclass: domainrelatedobject
6299 objectclass: dnsdomainaux
6300 associateddomain: hostname.intern
6301 arecord: 10.11.12.13
6302 dhcphwaddress: ethernet 00:00:00:00:00:00
6303 dhcpstatements: fixed-address hostname
6304 ldapconfigsound: Y
6305 &lt;/pre&gt;&lt;/blockquote&gt;
6306
6307 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6308 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6309 before asking DNS to resolve the fixed-adddress. LTSP will use
6310 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6311
6312 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6313 dhcphost in a different location, to allow us to put the objects
6314 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6315 that. If I can&#39;t figure out a way to do that, we can still get rid of
6316 the hosts subtree and move all its content into the DHCP Config tree
6317 (which probably should be renamed to be more related to the new
6318 content. I suspect cn=dnsdhcp,ou=services or something like that
6319 might be a good place to put it.&lt;/p&gt;
6320
6321 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6322 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6323 </description>
6324 </item>
6325
6326 <item>
6327 <title>Idea for storing LTSP configuration in LDAP</title>
6328 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6329 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6330 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6331 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6332 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6333 clients, and that this can be used to fetch configuration from LDAP if
6334 Debian Edu choose to store configuration there.&lt;/p&gt;
6335
6336 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6337 to get configuration from LDAP. The idea is to look up the MAC
6338 address of the client in LDAP, and look for attributes on the form
6339 ltspconfigsetting=value, and use this to export SETTING=value to the
6340 LTSP clients.&lt;/p&gt;
6341
6342 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6343 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6344 allowing us to store all information about a computer in one place.&lt;/p&gt;
6345
6346 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6347 this approach. A real LDAP schema for the ltspClientAux objectclass
6348 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6349
6350 &lt;blockquote&gt;&lt;pre&gt;
6351 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6352 #
6353 # Fetch LTSP client settings from LDAP based on MAC address
6354 #
6355 # Uses ethernet address as stored in the dhcpHost objectclass using
6356 # the dhcpHWAddress attribute or ethernet address stored in the
6357 # ieee802Device objectclass with the macAddress attribute.
6358 #
6359 # This module is written to be schema agnostic, and only depend on the
6360 # existence of attribute names.
6361 #
6362 # The LTSP configuration variables are saved directly using a
6363 # ltspConfig prefix and uppercasing the rest of the attribute name.
6364 # To set the SERVER variable, set the ltspConfigServer attribute.
6365 #
6366 # Some LDAP schema should be created with all the relevant
6367 # configuration settings. Something like this should work:
6368 #
6369 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6370 # SUP top
6371 # AUXILIARY
6372 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6373
6374 LDAPSERVER=$(debian-edu-ldapserver)
6375 if [ &quot;$LDAPSERVER&quot; ] ; then
6376 LDAPBASE=$(debian-edu-ldapserver -b)
6377 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6378 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6379 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6380 grep &#39;^ltspConfig&#39; | while read attr value ; do
6381 # Remove prefix and convert to upper case
6382 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6383 # bass value on to clients
6384 eval &quot;$attr=$value; export $attr&quot;
6385 done
6386 done
6387 fi
6388 &lt;/pre&gt;&lt;/blockquote&gt;
6389
6390 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6391 the while block might end up in a subshell causing the variables set
6392 there to not show up in ltsp-config, but if that is the case I am sure
6393 the code can be restructured to make sure the variables are passed on.
6394 I expect that can be solved with some testing. :)&lt;/p&gt;
6395
6396 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6397 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6398
6399 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6400 configuration in LDAP that was created around year 2000 by
6401 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6402 Xperience, Inc., 2000&lt;/a&gt;. I found its
6403 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6404 personal home page over at redhat.com.&lt;/p&gt;
6405 </description>
6406 </item>
6407
6408 <item>
6409 <title>jXplorer, a very nice LDAP GUI</title>
6410 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6411 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6412 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6413 <description>&lt;p&gt;Since
6414 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6415 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6416 LDAP GUI that is even better than luma. The java application
6417 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6418 moving LDAP objects and subtrees using drag-and-drop, and can
6419 authenticate using Kerberos. I have only tested the Kerberos
6420 authentication, but do not have a LDAP setup allowing me to rewrite
6421 LDAP with my test user yet. It is
6422 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6423 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6424 have with it is how it handle errors. If something go wrong, its
6425 non-intuitive behaviour require me to go through some query work list
6426 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6427 </description>
6428 </item>
6429
6430 <item>
6431 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6432 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6433 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6434 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6435 <description>&lt;p&gt;Here is a short update on my &lt;a
6436 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6437 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6438 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6439 not reporting the status for KDE, because the upgrade crashes when
6440 aptitude try because of missing conflicts
6441 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6442 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6443
6444 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6445 complete list of the installed packages. Based on this I see these
6446 differences when I did a test run today. As usual, I do not really
6447 know what the correct set of packages would be, but thought it best to
6448 publish the difference.&lt;/p&gt;
6449
6450 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6451
6452 &lt;blockquote&gt;&lt;p&gt;
6453 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6454 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6455 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6456 libgtksourceview-common libpt-1.10.10-plugins-alsa
6457 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6458 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6459 python-4suite-xml python-eggtrayicon python-gtkhtml2
6460 python-gtkmozembed svgalibg1 xserver-xephyr zip
6461 &lt;/p&gt;&lt;/blockquote&gt;
6462
6463 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6464
6465 &lt;blockquote&gt;&lt;p&gt;
6466 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6467 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6468 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6469 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6470 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6471 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6472 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6473 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6474 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6475 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6476 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6477 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6478 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6479 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6480 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6481 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6482 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6483 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6484 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6485 mysql-common swfdec-gnome totem-gstreamer wodim
6486 &lt;/p&gt;&lt;/blockquote&gt;
6487
6488 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6489
6490 &lt;blockquote&gt;&lt;p&gt;
6491 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6492 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6493 xserver-xorg-input-all xserver-xorg-input-evdev
6494 xserver-xorg-input-kbd xserver-xorg-input-mouse
6495 xserver-xorg-input-synaptics xserver-xorg-video-all
6496 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6497 xserver-xorg-video-chips xserver-xorg-video-cirrus
6498 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6499 xserver-xorg-video-glint xserver-xorg-video-i128
6500 xserver-xorg-video-i740 xserver-xorg-video-mach64
6501 xserver-xorg-video-mga xserver-xorg-video-neomagic
6502 xserver-xorg-video-nouveau xserver-xorg-video-nv
6503 xserver-xorg-video-r128 xserver-xorg-video-radeon
6504 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6505 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6506 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6507 xserver-xorg-video-sis xserver-xorg-video-sisusb
6508 xserver-xorg-video-tdfx xserver-xorg-video-tga
6509 xserver-xorg-video-trident xserver-xorg-video-tseng
6510 xserver-xorg-video-vesa xserver-xorg-video-vmware
6511 xserver-xorg-video-voodoo
6512 &lt;/p&gt;&lt;/blockquote&gt;
6513
6514 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6515
6516 &lt;blockquote&gt;&lt;p&gt;
6517 deskbar-applet xserver-xorg xserver-xorg-core
6518 xserver-xorg-input-wacom xserver-xorg-video-intel
6519 xserver-xorg-video-openchrome
6520 &lt;/p&gt;&lt;/blockquote&gt;
6521
6522 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6523 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6524 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6525 No idea when it hits Squeeze, but when it does I hope it will reduce
6526 the difference somewhat.
6527 </description>
6528 </item>
6529
6530 <item>
6531 <title>LUMA, a very nice LDAP GUI</title>
6532 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6533 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6534 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6535 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6536 directory in Debian Edu, and in the process I started to miss a GUI
6537 tool to browse the LDAP tree. The only one I was able to find in
6538 Debian/Squeeze and Lenny is
6539 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6540 be a great tool to get a overview of the current LDAP directory
6541 populated by default in Skolelinux. Thanks to it, I have been able to
6542 find empty and obsolete subtrees, misplaced objects and duplicate
6543 objects. It will be installed by default in Debian/Squeeze. If you
6544 are working with LDAP, give it a go. :)&lt;/p&gt;
6545
6546 &lt;p&gt;I did notice one problem with it I have not had time to report to
6547 the BTS yet. There is no .desktop file in the package, so the tool do
6548 not show up in the Gnome and KDE menus, but only deep down in in the
6549 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6550 released.&lt;/p&gt;
6551
6552 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6553 like to move objects and remove subtrees directly in the GUI, but have
6554 not found a way to do that with LUMA yet. So in the mean time, I use
6555 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6556
6557 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6558 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6559
6560 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6561 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6562 useful GUI alternative. It seem like a good tool, but is unmaintained
6563 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6564 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6565 </description>
6566 </item>
6567
6568 <item>
6569 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6570 <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>
6571 <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>
6572 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6573 <description>&lt;p&gt;A while back, I
6574 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6575 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6576 for storing DNS and DHCP information in LDAP to combine the two sets
6577 of information into one LDAP object representing a computer.&lt;/p&gt;
6578
6579 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6580 the dhcpHost object class auxiliary, to allow it to be combined with
6581 the dNSDomain object class, and thus forming one object for one
6582 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6583
6584 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6585 without also changing the assigned number for the object class, and I
6586 do not know enough about LDAP schema design to do that properly for
6587 Debian Edu.&lt;/p&gt;
6588
6589 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6590 the
6591 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6592 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6593 available today from IETF.&lt;/p&gt;
6594
6595 &lt;pre&gt;
6596 --- dhcp.schema (revision 65192)
6597 +++ dhcp.schema (working copy)
6598 @@ -376,7 +376,7 @@
6599 objectclass ( 2.16.840.1.113719.1.203.6.6
6600 NAME &#39;dhcpHost&#39;
6601 DESC &#39;This represents information about a particular client&#39;
6602 - SUP top
6603 + SUP top AUXILIARY
6604 MUST cn
6605 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6606 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6607 &lt;/pre&gt;
6608
6609 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6610 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6611 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6612
6613 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6614 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6615 </description>
6616 </item>
6617
6618 <item>
6619 <title>Calling tasksel like the installer, while still getting useful output</title>
6620 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6621 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6622 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6623 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6624 installs packages during the normal debian-installer run. Until now,
6625 I have ended up letting tasksel do the work, with the annoying problem
6626 of not getting any feedback at all when something fails (like a
6627 conffile question from dpkg or a download that fails), using code like
6628 this:
6629
6630 &lt;blockquote&gt;&lt;pre&gt;
6631 export DEBIAN_FRONTEND=noninteractive
6632 tasksel --new-install
6633 &lt;/pre&gt;&lt;/blockquote&gt;
6634
6635 This would invoke tasksel, let its automatic task selection pick the
6636 tasks to install, and continue to install the requested tasks without
6637 any output what so ever.
6638
6639 Recently I revisited this problem while working on the automatic
6640 package upgrade testing, because tasksel would some times hang without
6641 any useful feedback, and I want to see what is going on when it
6642 happen. Then it occured to me, I can parse the output from tasksel
6643 when asked to run in test mode, and use that aptitude command line
6644 printed by tasksel then to simulate the tasksel run. I ended up using
6645 code like this:
6646
6647 &lt;blockquote&gt;&lt;pre&gt;
6648 export DEBIAN_FRONTEND=noninteractive
6649 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6650 $cmd
6651 &lt;/pre&gt;&lt;/blockquote&gt;
6652
6653 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6654 --without-recommends -o APT::Install-Recommends=no -y install
6655 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6656 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6657 laptop task and all packages with priority standard , required and
6658 important, just like tasksel would have done it during
6659 installation.&lt;/p&gt;
6660
6661 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6662 install packages without using debconf-apt-progress, for use cases
6663 like this.&lt;/p&gt;
6664 </description>
6665 </item>
6666
6667 <item>
6668 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6669 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6670 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6671 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6672 <description>&lt;p&gt;My
6673 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6674 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6675 finally made the upgrade logs available from
6676 &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;.
6677 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6678 apt and aptitude, and found their differences interesting. This time
6679 I will only focus on their removal plans.&lt;/p&gt;
6680
6681 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6682 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6683 surprising part is that it want to remove xorg and all
6684 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6685 sure why. When asking aptitude to do the same, it want to remove 129
6686 packages, but most of them are library packages I suspect are no
6687 longer needed. Both of them want to remove bluetooth packages, which
6688 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6689
6690 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6691 which seem like a bad idea and xorg the same way as with Gnome. Asking
6692 aptitude for the same, it wants to remove 192 packages, none which are
6693 too surprising.&lt;/p&gt;
6694
6695 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6696 and avoided, and perhaps others as well. Here are the complete list
6697 of planned removals. The complete logs is available from the URL
6698 above. Note if you want to repeat these tests, that the upgrade test
6699 for kde+apt-get hung in the tasksel setup because of dpkg asking
6700 conffile questions. No idea why. I worked around it by using
6701 &#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
6702 continue.&lt;/p&gt;
6703
6704 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6705 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6706 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6707 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6708 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6709 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6710 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6711 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6712 xserver-xorg-input-kbd xserver-xorg-input-mouse
6713 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6714 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6715 xserver-xorg-video-ati xserver-xorg-video-chips
6716 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6717 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6718 xserver-xorg-video-glint xserver-xorg-video-i128
6719 xserver-xorg-video-i740 xserver-xorg-video-imstt
6720 xserver-xorg-video-intel xserver-xorg-video-mach64
6721 xserver-xorg-video-mga xserver-xorg-video-neomagic
6722 xserver-xorg-video-nsc xserver-xorg-video-nv
6723 xserver-xorg-video-openchrome xserver-xorg-video-r128
6724 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6725 xserver-xorg-video-rendition xserver-xorg-video-s3
6726 xserver-xorg-video-s3virge xserver-xorg-video-savage
6727 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6728 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6729 xserver-xorg-video-tga xserver-xorg-video-trident
6730 xserver-xorg-video-tseng xserver-xorg-video-v4l
6731 xserver-xorg-video-vesa xserver-xorg-video-vga
6732 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6733 xulrunner-1.9-gnome-support&lt;/p&gt;
6734
6735 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6736
6737 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6738 djvulibre-desktop finger gnome-app-install gnome-mount
6739 gnome-network-admin gnome-spell gnome-vfs-obexftp
6740 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6741 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6742 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6743 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6744 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6745 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6746 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6747 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6748 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6749 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6750 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6751 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6752 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6753 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6754 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6755 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6756 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6757 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6758 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6759 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6760 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6761 openoffice.org-writer2latex openssl-blacklist p7zip
6762 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6763 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6764 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6765 swfdec-mozilla totem-gstreamer update-manager wodim
6766 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6767 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6768 zip&lt;/p&gt;
6769
6770 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6771
6772 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6773 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6774 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6775 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6776 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6777 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6778 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6779 xserver-xorg-input-kbd xserver-xorg-input-mouse
6780 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6781 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6782 xserver-xorg-video-ati xserver-xorg-video-chips
6783 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6784 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6785 xserver-xorg-video-glint xserver-xorg-video-i128
6786 xserver-xorg-video-i740 xserver-xorg-video-imstt
6787 xserver-xorg-video-intel xserver-xorg-video-mach64
6788 xserver-xorg-video-mga xserver-xorg-video-neomagic
6789 xserver-xorg-video-nsc xserver-xorg-video-nv
6790 xserver-xorg-video-openchrome xserver-xorg-video-r128
6791 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6792 xserver-xorg-video-rendition xserver-xorg-video-s3
6793 xserver-xorg-video-s3virge xserver-xorg-video-savage
6794 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6795 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6796 xserver-xorg-video-tga xserver-xorg-video-trident
6797 xserver-xorg-video-tseng xserver-xorg-video-v4l
6798 xserver-xorg-video-vesa xserver-xorg-video-vga
6799 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6800
6801 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6802 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6803 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6804 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6805 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6806 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6807 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6808 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6809 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6810 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6811 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6812 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6813 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6814 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6815 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6816 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6817 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6818 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6819 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6820 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6821 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6822 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6823 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6824 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6825 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6826 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6827 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6828 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6829 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6830 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6831 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6832 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6833 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6834 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6835 texlive-common texlive-doc-base texlive-fonts-recommended
6836 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6837 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6838 xulrunner-1.9&lt;/p&gt;
6839
6840 </description>
6841 </item>
6842
6843 <item>
6844 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6845 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6846 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6847 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6848 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6849 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6850 have been discovered and reported in the process
6851 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6852 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6853 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6854 kdebase-workspace-data), and to get a more regular testing going on, I
6855 am working on a script to automate the test.&lt;/p&gt;
6856
6857 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6858 Gnome or KDE desktop installation inside the chroot before upgrading
6859 it. To ensure no services are started in the chroot, a policy-rc.d
6860 script is inserted. To make sure tasksel believe it is to install a
6861 desktop on a laptop, the tasksel tests are replaced in the chroot
6862 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
6863
6864 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6865 currently always fail because udev refuses to upgrade with the kernel
6866 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6867 is created. The bug report
6868 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
6869 this problem do not trigger in a chroot, but I touch the file anyway
6870 to make sure the upgrade go well. Testing on virtual and real
6871 hardware have failed me because of udev so far, and creating this file
6872 do the trick in such settings anyway. This is a
6873 &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
6874 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
6875 maintainer because he lack the resources to rewrite udev to keep
6876 working with old kernels or something like that. I really wish the
6877 udev upstream would keep udev backwards compatible, to avoid such
6878 upgrade problem, but given that they fail to do so, I guess
6879 documenting the way out of this mess is the best option we got for
6880 Debian Squeeze.&lt;/p&gt;
6881
6882 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
6883 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
6884 trick:&lt;/p&gt;
6885
6886 &lt;blockquote&gt;&lt;pre&gt;
6887 #!/bin/sh
6888 set -ex
6889
6890 if [ &quot;$1&quot; ] ; then
6891 desktop=$1
6892 else
6893 desktop=gnome
6894 fi
6895
6896 from=lenny
6897 to=squeeze
6898
6899 exec &amp;lt; /dev/null
6900 unset LANG
6901 mirror=http://ftp.skolelinux.org/debian
6902 tmpdir=chroot-$from-upgrade-$to-$desktop
6903 fuser -mv .
6904 debootstrap $from $tmpdir $mirror
6905 chroot $tmpdir aptitude update
6906 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
6907 #!/bin/sh
6908 exit 101
6909 EOF
6910 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6911 exit_cleanup() {
6912 umount $tmpdir/proc
6913 }
6914 mount -t proc proc $tmpdir/proc
6915 # Make sure proc is unmounted also on failure
6916 trap exit_cleanup EXIT INT
6917
6918 chroot $tmpdir aptitude -y install debconf-utils
6919
6920 # Make sure tasksel autoselection trigger. It need the test scripts
6921 # to return the correct answers.
6922 echo tasksel tasksel/desktop multiselect $desktop | \
6923 chroot $tmpdir debconf-set-selections
6924
6925 # Include the desktop and laptop task
6926 for test in desktop laptop ; do
6927 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
6928 #!/bin/sh
6929 exit 2
6930 EOF
6931 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6932 done
6933
6934 DEBIAN_FRONTEND=noninteractive
6935 DEBIAN_PRIORITY=critical
6936 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6937 chroot $tmpdir tasksel --new-install
6938
6939 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
6940 chroot $tmpdir aptitude update
6941 touch $tmpdir/etc/udev/kernel-upgrade
6942 chroot $tmpdir aptitude -y dist-upgrade
6943 fuser -mv
6944 &lt;/pre&gt;&lt;/blockquote&gt;
6945
6946 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
6947 with aptitude, but I have not had time to look at how they behave
6948 differently so far. I hope to get a cron job running to do the test
6949 regularly and post the result on the web. The Gnome upgrade currently
6950 work, while the KDE upgrade fail because of the bug in
6951 kdebase-workspace-data&lt;/p&gt;
6952
6953 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
6954 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
6955 post, so I will refrain from trying. I can report that for Gnome,
6956 aptitude report 760 packages upgraded, 448 newly installed, 129 to
6957 remove and 1 not upgraded and 1024MB need to be downloaded while for
6958 KDE the same numbers are 702 packages upgraded, 507 newly installed,
6959 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
6960
6961 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
6962 is able to migrate to dependency based boot sequencing and parallel
6963 booting without a hitch. Was unsure if there were still bugs with
6964 packages failing to clean up their obsolete init.d script during
6965 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6966 packages.&lt;/p&gt;
6967 </description>
6968 </item>
6969
6970 <item>
6971 <title>Upstart or sysvinit - as init.d scripts see it</title>
6972 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
6973 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
6974 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
6975 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6976 scripts to migrate (some of) their operations to upstart job while
6977 keeping the init.d for hurd and kfreebsd. The packages with such
6978 needs will need a way to get their init.d scripts to behave
6979 differently when used with sysvinit and with upstart. Because of
6980 this, I had a look at the environment variables set when a init.d
6981 script is running under upstart, and when it is not.&lt;/p&gt;
6982
6983 &lt;p&gt;With upstart, I notice these environment variables are set when a
6984 script is started from rcS.d/ (ignoring some irrelevant ones like
6985 COLUMNS):&lt;/p&gt;
6986
6987 &lt;blockquote&gt;&lt;pre&gt;
6988 DEFAULT_RUNLEVEL=2
6989 previous=N
6990 PREVLEVEL=
6991 RUNLEVEL=
6992 runlevel=S
6993 UPSTART_EVENTS=startup
6994 UPSTART_INSTANCE=
6995 UPSTART_JOB=rc-sysinit
6996 &lt;/pre&gt;&lt;/blockquote&gt;
6997
6998 &lt;p&gt;With sysvinit, these environment variables are set for the same
6999 script.&lt;/p&gt;
7000
7001 &lt;blockquote&gt;&lt;pre&gt;
7002 INIT_VERSION=sysvinit-2.88
7003 previous=N
7004 PREVLEVEL=N
7005 RUNLEVEL=S
7006 runlevel=S
7007 &lt;/pre&gt;&lt;/blockquote&gt;
7008
7009 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7010 sysvinit are not set by upstart. Not sure if it is intentional or not
7011 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7012
7013 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7014 looking for the UPSTART_JOB environment variable seem to be a good
7015 choice.&lt;/p&gt;
7016 </description>
7017 </item>
7018
7019 <item>
7020 <title>A manual for standards wars...</title>
7021 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7022 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7023 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7024 <description>&lt;p&gt;Via the
7025 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7026 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7027 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7028 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7029 following the standards wars of today.&lt;/p&gt;
7030 </description>
7031 </item>
7032
7033 <item>
7034 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7035 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7036 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7037 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7038 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7039 to get a list of the machine types in use thanks to the DMI
7040 information extracted from each machine. The script to do so is
7041 included in the sitesummary package, and here is example output from
7042 the Skolelinux build servers:&lt;/p&gt;
7043
7044 &lt;blockquote&gt;&lt;pre&gt;
7045 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7046 vendor count
7047 Dell Computer Corporation 1
7048 PowerEdge 1750 1
7049 IBM 1
7050 eserver xSeries 345 -[8670M1X]- 1
7051 Intel 2
7052 [no-dmi-info] 3
7053 maintainer:~#
7054 &lt;/pre&gt;&lt;/blockquote&gt;
7055
7056 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7057 provided in each machine. Here there are Intel machines without model
7058 information listed with Intel as vendor and no model, and virtual Xen
7059 machines listed as [no-dmi-info]. One can add -l as a command line
7060 option to list the individual machines.&lt;/p&gt;
7061
7062 &lt;p&gt;A larger list is
7063 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7064 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7065 provide the basic sitesummary report publicly. In their report there
7066 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7067 their machines, and as sitesummary is available in both distributions,
7068 it is trivial to get all of them to report to the same central
7069 collector.&lt;/p&gt;
7070 </description>
7071 </item>
7072
7073 <item>
7074 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7075 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7076 <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>
7077 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7078 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7079 start at boot when an NVidia video card is used is handled. The
7080 problem seem to be that the nvidia X.org driver uses a long time to
7081 initialize, and this duration is longer than kdm is configured to
7082 wait.&lt;/p&gt;
7083
7084 &lt;p&gt;I came across two bugs related to this issue,
7085 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7086 against initscripts and passed on to nvidia-glx when it became obvious
7087 that the nvidia drivers were involved, and
7088 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7089 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7090
7091 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7092 problem nvidia video card owners experience and make sure the Debian
7093 distribution work out of the box for these users. The nvidia driver
7094 maintainers expect kdm to be set up to wait longer, while kdm expect
7095 the nvidia driver maintainers to fix the driver to start faster, and
7096 while they wait for each other I guess the users end up switching to a
7097 distribution that work for them. I have no idea what the solution is,
7098 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7099
7100 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7101 </description>
7102 </item>
7103
7104 <item>
7105 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7106 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7107 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7108 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7109 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7110 The feature seem to hold up pretty well, but three fairly serious
7111 issues are known and should be solved:
7112
7113 &lt;p&gt;&lt;ul&gt;
7114
7115 &lt;li&gt;The wicd package seen to
7116 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7117 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7118 parallel booting is enabled. No idea why, but the wicd maintainer
7119 seem to be on the case.&lt;/li&gt;
7120
7121 &lt;li&gt;The nvidia X driver seem to
7122 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7123 triggered more easily when parallel booting is in effect. The
7124 maintainer is on the case.&lt;/li&gt;
7125
7126 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7127 sequencing (the shutdown is broken) when old file-rc users
7128 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7129 sysv-rc. One way to solve it would be for file-rc to create
7130 /etc/init.d/.legacy-bootordering, and another is to try to make
7131 sysv-rc more robust. Will investigate some more and probably upload a
7132 workaround in sysv-rc to help those trying to move from file-rc to
7133 sysv-rc get a working shutdown.&lt;/li&gt;
7134
7135 &lt;/ul&gt;&lt;/p&gt;
7136
7137 &lt;p&gt;All in all not many surprising issues, and all of them seem
7138 solvable before Squeeze is released. In addition to these there are
7139 some packages with bugs in their dependencies and run level settings,
7140 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7141
7142 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7143 the BTS, please usertag the report to get it to show up at
7144 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7145 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7146
7147 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7148 </description>
7149 </item>
7150
7151 <item>
7152 <title>More flexible firmware handling in debian-installer</title>
7153 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7154 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7155 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7156 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7157 found time today to return to the project. Having to spend less time
7158 working dependency based boot in debian, as it is almost complete now,
7159 definitely helped freeing some time.&lt;/p&gt;
7160
7161 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7162 include some firmware packages on the Debian Edu CDs, those needed to
7163 get disk and network controllers working. Without having these
7164 firmware packages available during installation, it is impossible to
7165 install Debian Edu on the given machine, and because our target group
7166 are non-technical people, asking them to provide firmware packages on
7167 an external medium is a support pain. Initially, I expected it to be
7168 enough to include the firmware packages on the CD to get
7169 debian-installer to find and use them. This proved to be wrong.
7170 Next, I hoped it was enough to symlink the relevant firmware packages
7171 to some useful location on the CD (tried /cdrom/ and
7172 /cdrom/firmware/). This also proved to not work, and at this point I
7173 found time to look at the debian-installer code to figure out what was
7174 going to work.&lt;/p&gt;
7175
7176 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7177 look revealed that it would only look for firmware packages outside
7178 the installation media, so the CD was never checked for firmware
7179 packages. It would only check USB sticks, floppies and other
7180 &quot;external&quot; media devices. Today I changed it to also look in the
7181 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7182 solve the problem I ran into with Debian edu. I also changed it to
7183 look in /firmware/, to make sure the installer also find firmware
7184 provided in the initrd when booting the installer via PXE, to allow us
7185 to provide the same feature in the PXE setup included in Debian
7186 Edu.&lt;/p&gt;
7187
7188 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7189 activated without asking if the license is accepted, I extended
7190 hw-detect to look for preinst scripts in the firmware packages, and
7191 run these before activating the firmware during installation. The
7192 license question is asked using debconf in the preinst, so this should
7193 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7194
7195 &lt;p&gt;If you want to discuss the details of these features, please
7196 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7197 </description>
7198 </item>
7199
7200 <item>
7201 <title>Parallellized boot is now the default in Debian/unstable</title>
7202 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7203 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7204 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7205 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7206 Debian/unstable for machines using dependency based boot sequencing.
7207 Apparently the testing of concurrent booting has been wider than
7208 expected, if I am to believe the
7209 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7210 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7211 with the feature this weekend, to give us some time to detect any
7212 remaining problems before Squeeze is frozen. If serious problems are
7213 detected, it is simple to change the default back to sequential boot.
7214 The upload of the new sysvinit package also activate a new upstream
7215 version.&lt;/p&gt;
7216
7217 More information about
7218 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7219 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7220 currently possible to disable parallel booting when one run into
7221 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7222
7223 &lt;blockquote&gt;&lt;pre&gt;
7224 CONCURRENCY=none
7225 &lt;/pre&gt;&lt;/blockquote&gt;
7226
7227 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7228 the BTS, please usertag the report to get it to show up at
7229 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7230 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7231 </description>
7232 </item>
7233
7234 <item>
7235 <title>Sitesummary tip: Listing MAC address of all clients</title>
7236 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7237 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7238 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7239 <description>&lt;p&gt;In the recent Debian Edu versions, the
7240 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7241 system&lt;/a&gt; is used to keep track of the machines in the school
7242 network. Each machine will automatically report its status to the
7243 central server after boot and once per night. The network setup is
7244 also reported, and using this information it is possible to get the
7245 MAC address of all network interfaces in the machines. This is useful
7246 to update the DHCP configuration.&lt;/p&gt;
7247
7248 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7249 ist all MAC addresses of all machines reporting to sitesummary. Run
7250 this on the collector host:&lt;/p&gt;
7251
7252 &lt;blockquote&gt;&lt;pre&gt;
7253 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7254 &lt;/pre&gt;&lt;/blockquote&gt;
7255
7256 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7257 line per machine and with space between the MAC addresses.&lt;/p&gt;
7258
7259 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7260 addresses for hosts, it would be possible to extend this to fetch
7261 machine information from sitesummary and update the DHCP and DNS
7262 tables in LDAP using this information. Such tool is unfortunately not
7263 written yet.&lt;/p&gt;
7264 </description>
7265 </item>
7266
7267 <item>
7268 <title>systemd, an interesting alternative to upstart</title>
7269 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7271 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7272 <description>&lt;p&gt;The last few days a new boot system called
7273 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7274 has been
7275 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7276
7277 to the free software world. I have not yet had time to play around
7278 with it, but it seem to be a very interesting alternative to
7279 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7280 a good alternative for Debian when we are able to switch to an event
7281 based boot system. Tollef is
7282 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7283 systemd into Debian, and I look forward to seeing how well it work. I
7284 like the fact that systemd handles init.d scripts with dependency
7285 information natively, allowing them to run in parallel where upstart
7286 at the moment do not.&lt;/p&gt;
7287
7288 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7289 platform support. It only work on recent Linux kernels, and also need
7290 some new kernel features enabled to function properly. This means
7291 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7292 system. Not sure how that will be handled if systemd proves to be the
7293 way forward.&lt;/p&gt;
7294
7295 &lt;p&gt;In the mean time, based on the
7296 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7297 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7298 decided to enable full parallel booting as the default in Debian as
7299 soon as possible (probably this weekend or early next week), to see if
7300 there are any remaining serious bugs in the init.d dependencies. A
7301 new version of the sysvinit package implementing this change is
7302 already in experimental. If all go well, Squeeze will be released
7303 with parallel booting enabled by default.&lt;/p&gt;
7304 </description>
7305 </item>
7306
7307 <item>
7308 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7309 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7310 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7311 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7312 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7313 complete, so complete that it is actually possible to run all the
7314 init.d scripts in parallell based on these dependencies. If you want
7315 to test your Squeeze system, make sure
7316 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7317 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7318 /etc/default/rcS:&lt;/p&gt;
7319
7320 &lt;blockquote&gt;&lt;pre&gt;
7321 CONCURRENCY=makefile
7322 &lt;/pre&gt;&lt;/blockquote&gt;
7323
7324 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7325 scripts in parallel using the dependency information stored in
7326 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7327 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7328 to try to start the kdm and gdm scripts as early as possible, and will
7329 start the facilities required by kdm or gdm as early as possible to
7330 make this happen.&lt;/p&gt;
7331
7332 &lt;p&gt;Give it a try, and see if you like the result. If some services
7333 fail to start properly, it is most likely because they have incomplete
7334 init.d script dependencies in their startup script (or some of their
7335 dependent scripts have incomplete dependencies). Report bugs and get
7336 the package maintainers to fix it. :)&lt;/p&gt;
7337
7338 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7339 manage to get the init.d script dependencies complete and correct. I
7340 expect we will get there in Squeeze+1, if we get manage to test and
7341 fix the remaining issues.&lt;/p&gt;
7342
7343 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7344 the BTS, please usertag the report to get it to show up at
7345 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7346 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7347 </description>
7348 </item>
7349
7350 <item>
7351 <title>Debian has switched to dependency based boot sequencing</title>
7352 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7354 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7355 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7356 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7357 have been migrated to using dependency based boot sequencing. This
7358 conclude work me and others have been doing for the last three days.
7359 It feels great to see this finally part of the default Debian
7360 installation. Now we just need to weed out the last few problems that
7361 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7362
7363 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7364 fixing the more fundamental problem of handing the event based
7365 non-predictable kernel in the early boot.&lt;/p&gt;
7366 </description>
7367 </item>
7368
7369 <item>
7370 <title>Taking over sysvinit development</title>
7371 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7373 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7374 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7375 the existing sysvinit upstream developer, I decided a few weeks ago to
7376 take over the package and become the new upstream. The number of
7377 patches to track for the Debian package was becoming a burden, and the
7378 lack of synchronization between the distribution made it hard to keep
7379 the package up to date.&lt;/p&gt;
7380
7381 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7382 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7383 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7384 and Fedora), based on the patches currently in use in these
7385 distributions. We Debian maintainers plan to move to this tarball as
7386 the new upstream as soon as we find time to do the merge. Since the
7387 new tarball was created, we agreed with Werner at SuSe to make a new
7388 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7389 development there. The project is registered and currently waiting
7390 for approval by the Savannah administrators, and as soon as it is
7391 approved, we will import the old versions from svn and continue
7392 working on the future release.&lt;/p&gt;
7393
7394 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7395 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7396 </description>
7397 </item>
7398
7399 <item>
7400 <title>Debian boots quicker and quicker</title>
7401 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7403 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7404 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7405 people involved in the boot system on Debian and Ubuntu, to see if we
7406 could find more ways to speed up the boot system. This was an Ubuntu
7407 funded
7408 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7409 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7410 of boot systems, and ways to handle the increasing number of boot
7411 issues introduced by the Linux kernel becoming more and more
7412 asynchronous and event base. The Ubuntu approach using udev and
7413 upstart might be a good way forward. Time will show.&lt;/p&gt;
7414
7415 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7416 process in Debian. All of these should be applied to get a quick
7417 boot:&lt;/p&gt;
7418
7419 &lt;ul&gt;
7420
7421 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7422
7423 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7424 clock is in UTC.&lt;/li&gt;
7425
7426 &lt;li&gt;Install and activate the insserv package to enable
7427 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7428 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7429
7430 &lt;/ul&gt;
7431
7432 These points are based on the Google summer of code work done by
7433 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7434 Villegas&lt;/a&gt;.
7435
7436 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7437 unstable yesterday. When we tested it, we were able to cut 6 seconds
7438 from the boot sequence. It depend on very correct dependency
7439 declaration in all init.d scripts, so I expect us to find edge cases
7440 where the dependences in some scripts are slightly wrong when we start
7441 using this.&lt;/p&gt;
7442
7443 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7444 introduced by Raphael Geissert today, one that could affect the
7445 startup speed as well. Instead of starting some scripts concurrently
7446 from rcS.d/ and another set of scripts from rc2.d/, it would be
7447 possible to run a of them in the same process. A quick way to test
7448 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7449 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7450 </description>
7451 </item>
7452
7453 <item>
7454 <title>BSAs påstander om piratkopiering møter motstand</title>
7455 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7456 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7457 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7458 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7459 programvareselskapene som Microsoft og Apple, publisert en rapport der
7460 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7461 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7462 dager siden kom
7463 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7464 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7465 dagene. Et spesielt interessant kommentar fra Sverige,
7466 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7467 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7468
7469 &lt;blockquote&gt;
7470 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7471 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7472 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7473 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7474 &lt;/blockquote&gt;
7475
7476 &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
7477 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7478 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7479 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7480 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7481
7482 &lt;p&gt;Fant lenkene via &lt;a
7483 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7484 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7485 </description>
7486 </item>
7487
7488 <item>
7489 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7490 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7491 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7492 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7493 <description>&lt;p&gt;Kom over
7494 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7495 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7496 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7497 jobber til daglig. En rask opptelling forteller meg at vi har 490
7498 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7499 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7500 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7501 </description>
7502 </item>
7503
7504 <item>
7505 <title>Kryptert harddisk - naturligvis</title>
7506 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7507 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7508 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7509 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7510 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7511 når en tar tap av arbeidstid, fortrolige dokumenter,
7512 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7513 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7514 til at jeg har kryptert harddisken på både kontormaskinen og min
7515 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7516 komme på avveie, den første informasjon relatert til jobben min ved
7517 Universitetet i Oslo, og den andre relatert til blant annet
7518 foreningsarbeide. Kryptering av diskene gjør at det er lite
7519 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7520 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7521 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7522 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7523 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7524 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7525 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7526 det er gjort slik jeg gjør det er minimale, og gevinstene er
7527 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7528 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7529
7530 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7531 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7532 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7533 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7534 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7535 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7536 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7537 betydelige.&lt;/p&gt;
7538 </description>
7539 </item>
7540
7541 <item>
7542 <title>Two projects that have improved the quality of free software a lot</title>
7543 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7544 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7545 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7546 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7547 quality of free software, and I wanted to mention both in case someone
7548 do not yet know them.&lt;/p&gt;
7549
7550 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7551 tool to detect and expose errors in the memory handling of programs.
7552 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7553 and it will report any problems on stdout. It is even better if the
7554 program include debug information. With debug information, it is able
7555 to report the source file name and line number where the problem
7556 occurs. It can report things like &#39;reading past memory block in file
7557 X line N, the memory block was allocated in file Y, line M&#39;, and
7558 &#39;using uninitialised value in control logic&#39;. This tool has made it
7559 trivial to investigate reproducible crash bugs in programs, and have
7560 reduced the number of this kind of bugs in free software a lot.
7561
7562 &lt;p&gt;The second one is
7563 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7564 a source code checker. It is able to process the source of a program
7565 and find problems in the logic without running the program. It
7566 started out as the Stanford Checker and became well known when it was
7567 used to find bugs in the Linux kernel. It is now a commercial tool
7568 and the company behind it is running
7569 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7570 free software community, where a lot of free software projects get
7571 their source checked for free. Several thousand defects have been
7572 found and fixed so far. It can find errors like &#39;lock L taken in file
7573 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7574 Y lines O to P can never be executed&#39;. The projects included in the
7575 community service project have managed to get rid of a lot of
7576 reliability problems thanks to Coverity.&lt;/p&gt;
7577
7578 &lt;p&gt;I believe tools like this, that are able to automatically find
7579 errors in the source, are vital to improve the quality of software and
7580 make sure we can get rid of the crashing and failing software we are
7581 surrounded by today.&lt;/p&gt;
7582 </description>
7583 </item>
7584
7585 <item>
7586 <title>No patch is not better than a useless patch</title>
7587 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7588 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7589 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7590 <description>&lt;p&gt;Julien Blache
7591 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7592 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7593 patch allow one to discuss a concrete and proposed solution, and also
7594 prove that the issue at hand is important enough for someone to spent
7595 time on fixing it. No patch do not provide any of these positive
7596 properties.&lt;/p&gt;
7597 </description>
7598 </item>
7599
7600 <item>
7601 <title>Standardize on protocols and formats, not vendors and applications</title>
7602 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7603 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7604 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7605 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7606 very good one to form a long lived computer infrastructure. It is the
7607 simple one, lost by many in todays computer industry: Standardize on
7608 open network protocols and open exchange/storage formats, not applications.
7609 Applications come and go, while protocols and files tend to stay, and
7610 thus one want to make it easy to change application and vendor, while
7611 avoiding conversion costs and locking users to a specific platform or
7612 application.&lt;/p&gt;
7613
7614 &lt;p&gt;This approach make it possible to replace the client applications
7615 independently of the server applications. One can even allow users to
7616 use several different applications as long as they handle the selected
7617 protocol and format. In the normal case, only one client application
7618 is recommended and users only get help if they choose to use this
7619 application, but those that want to deviate from the easy path are not
7620 blocked from doing so.&lt;/p&gt;
7621
7622 &lt;p&gt;It also allow us to replace the server side without forcing the
7623 users to replace their applications, and thus allow us to select the
7624 best server implementation at any moment, when scale and resouce
7625 requirements change.&lt;/p&gt;
7626
7627 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7628 open formats, but I would never recommend standardizing on a single
7629 application that do not use open network protocol or open formats.&lt;/p&gt;
7630 </description>
7631 </item>
7632
7633 <item>
7634 <title>Returning from Skolelinux developer gathering</title>
7635 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7636 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7637 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7638 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7639 Edu/Skolelinux development gathering. I got a bit done tuning the
7640 desktop, and looked into the dynamic service location protocol
7641 implementation avahi. It look like it could be useful for us. Almost
7642 30 people participated, and I believe it was a great environment to
7643 get to know the Skolelinux system. Walter Bender, involved in the
7644 development of the Sugar educational platform, presented his stuff and
7645 also helped me improve my OLPC installation. He also showed me that
7646 his Turtle Art application can be used in standalone mode, and we
7647 agreed that I would help getting it packaged for Debian. As a
7648 standalone application it would be great for Debian Edu. We also
7649 tried to get the video conferencing working with two OLPCs, but that
7650 proved to be too hard for us. The application seem to need more work
7651 before it is ready for me. I look forward to getting home and relax
7652 now. :)&lt;/p&gt;
7653 </description>
7654 </item>
7655
7656 <item>
7657 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7658 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7659 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7660 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7661 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7662 optimal. There is RFC 2307 documenting one way to store NIS maps in
7663 LDAP, and a modified version of this normally called RFC 2307bis, with
7664 some modifications to be compatible with Active Directory. The RFC
7665 specification handle the content of a lot of system databases, but do
7666 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7667
7668 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7669 we would like to store information about users, SMB clients/hosts,
7670 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7671 and LTSP configuration in LDAP. These objects have a lot in common,
7672 but with the current LDAP schemas it is not possible to have one
7673 object per entity. For example, one need to have at least three LDAP
7674 objects for a given computer, one with the SMB related stuff, one with
7675 DNS information and another with DHCP information. The schemas
7676 provided for DNS and DHCP are impossible to combine into one LDAP
7677 object. In addition, it is impossible to implement quick queries for
7678 netgroup membership, because of the way NIS triples are implemented.
7679 It just do not scale. I believe it is time for a few RFC
7680 specifications to cleam up this mess.&lt;/p&gt;
7681
7682 &lt;p&gt;I would like to have one LDAP object representing each computer in
7683 the network, and this object can then keep the SMB (ie host key), DHCP
7684 (mac address/name) and DNS (name/IP address) settings in one place.
7685 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7686
7687 &lt;p&gt;I would also like to have a quick way to map from a user or
7688 computer and to the net group this user or computer is a member.&lt;/p&gt;
7689
7690 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7691 in this regard, and the unix side need to catch up. Time to start a
7692 new IETF work group?&lt;/p&gt;
7693 </description>
7694 </item>
7695
7696 <item>
7697 <title>Endelig er Debian Lenny gitt ut</title>
7698 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7699 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7700 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7701 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7702 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7703 Et langt steg videre for Debian-prosjektet, og en rekke nye
7704 programpakker blir nå tilgjengelig for de av oss som bruker den
7705 stabile utgaven av Debian. Neste steg er nå å få
7706 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7707 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7708 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7709 slippes løs på skolene. Takk til alle debian-utviklerne som har
7710 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7711 bootsekvens tilgjengelig i stabil utgave, vha pakken
7712 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7713 </description>
7714 </item>
7715
7716 <item>
7717 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7718 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7719 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7720 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7721 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7722 Oslo. Most of Saturday was used for the general assemly for the
7723 member organization, but the rest of the weekend I used to tune the
7724 LTSP installation. LTSP now work out of the box on the 10-network.
7725 Acer Aspire One proved to be a very nice thin client, with both
7726 screen, mouse and keybard in a small box. Was working on getting the
7727 diskless workstation setup configured out of the box, but did not
7728 finish it before the weekend was up.&lt;/p&gt;
7729
7730 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7731 the Brazilian group, so that will have to wait for the next
7732 development gathering. Would love to have the Debian Edu installer
7733 automatically detect and configure a multiseat setup when it find one
7734 of these cards.&lt;/p&gt;
7735 </description>
7736 </item>
7737
7738 <item>
7739 <title>The sorry state of multimedia browser plugins in Debian</title>
7740 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7741 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7742 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7743 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7744 plugins available in Debian Lenny, to see which one we should use by
7745 default in Debian Edu. We need an embedded video playing plugin with
7746 control buttons to pause or stop the video, and capable of streaming
7747 all the multimedia content available on the web. The test results and
7748 notes are available on
7749 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7750 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7751 fill this need. My personal video player favorite, VLC, has a really
7752 bad plugin which fail on a lot of the test pages. A lot of the MIME
7753 types I would expect to work with any free software player (like
7754 video/ogg), just do not work. And simple formats like the
7755 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7756 totem and vlc plugins. I hope the situation will improve soon. No
7757 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7758
7759 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7760 be the only one fitting our needs. :/&lt;/p&gt;
7761 </description>
7762 </item>
7763
7764 </channel>
7765 </rss>