]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
3f49c33047cebc3752e692c865ff4e0fd556cead
[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>How to stay with sysvinit in Debian Jessie</title>
11 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
13 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
14 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
15 sysvinit as its boot system by default. But how can one keep using
16 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
17 courtesy of
18 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
19 Schubert&lt;/a&gt; and
20 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
21 McVittie&lt;/a&gt;.
22
23 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
24 keep sysvinit as your boot system, create a file
25 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
26 you upgrade:&lt;/p&gt;
27
28 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
29 Package: systemd-sysv
30 Pin: release o=Debian
31 Pin-Priority: -1
32 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
33
34 &lt;p&gt;This file content will tell apt and aptitude to not consider
35 installing systemd-sysv as part of any installation and upgrade
36 solution when resolving dependencies, and thus tell it to avoid
37 systemd as a default boot system. The end result should be that the
38 upgraded system keep using sysvinit.&lt;/p&gt;
39
40 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
41 get sysvinit installed by default (debootstrap used by
42 debian-installer have no option for this), but one can tell the
43 installer to switch to sysvinit before the first boot. Either by
44 using a kernel argument to the installer, or by adding a line to the
45 preseed file used. First, the kernel command line argument:
46
47 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
48 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
49 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
50
51 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
52
53 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
54 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
55 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
56
57 &lt;p&gt;One can of course also do this after the first boot by installing
58 the sysvinit-core package.&lt;/p&gt;
59
60 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
61 sysvinit boot sequence in Debian have several hardware specific bugs
62 on Linux caused by the fact that it is unpredictable when hardware
63 devices show up during boot. But on the other hand, the new default
64 boot system still have a few rough edges I hope will be fixed before
65 Jessie is released.&lt;/p&gt;
66
67 &lt;p&gt;Update 2014-11-26: Inspired by
68 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
69 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
70 line.&lt;/p&gt;
71 </description>
72 </item>
73
74 <item>
75 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
76 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
77 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
78 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
79 <description>&lt;p&gt;The right to communicate with your friends and family in private,
80 without anyone snooping, is a right every citicen have in a liberal
81 democracy. But this right is under serious attack these days.&lt;/p&gt;
82
83 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
84 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
85 the whisleblower Snowden) more expensive for Internet email,
86 is to deliver all email using SMTP via Tor. Such SMTP option would be
87 a nice addition to the FreedomBox project if we could send email
88 between FreedomBox machines without leaking metadata about the emails
89 to the people peeking on the wire. I
90 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
91 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
92 lot of useful feedback and suggestions. It also became obvious to me
93 that this was not a novel idea, as the same idea was tested and
94 documented by Johannes Berg as early as 2006, and both
95 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
96 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
97 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
98
99 &lt;p&gt;To implement such system one need to set up a Tor hidden service
100 providing the SMTP protocol on port 25, and use email addresses
101 looking like username@hidden-service-name.onion. With such addresses
102 the connections to port 25 on hidden-service-name.onion using Tor will
103 go to the correct SMTP server. To do this, one need to configure the
104 Tor daemon to provide the hidden service and the mail server to accept
105 emails for this .onion domain. To learn more about Exim configuration
106 in Debian and test the design provided by Johannes Berg in his FAQ, I
107 set out yesterday to create a Debian package for making it trivial to
108 set up such SMTP over Tor service based on Debian. Getting it to work
109 were fairly easy, and
110 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
111 source code for the Debian package&lt;/a&gt; is available from github. I
112 plan to move it into Debian if further testing prove this to be a
113 useful approach.&lt;/p&gt;
114
115 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
116 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
117 get rid of exim4). Install tor, clone the git repository mentioned
118 above, build the deb and install it on the machine. Next, run
119 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
120 the instructions to get the service up and running. Restart tor and
121 exim when it is done, and test mail delivery using swaks like
122 this:&lt;/p&gt;
123
124 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
125 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
126 --to fbx@dutlqrrmjhtfa3vp.onion
127 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
128
129 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
130 address with your own address to test your server. :)&lt;/p&gt;
131
132 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
133 easier and more automatic. Especially the tor setup need more work.
134 Also, the package include a tor-smtp tool written in C, but its task
135 should probably be rewritten in some script language to make the deb
136 architecture independent. It would probably also make the code easier
137 to review. The tor-smtp tool currently need to listen on a socket for
138 exim to talk to it and is started using xinetd. It would be better if
139 no daemon and no socket is needed. I suspect it is possible to get
140 exim to run a command line tool for delivery instead of talking to a
141 socket, and hope to figure out how in a future version of this
142 system.&lt;/p&gt;
143
144 &lt;p&gt;Until I wipe my test machine, I can be reached using the
145 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
146 SMTorP. :)&lt;/p&gt;
147 </description>
148 </item>
149
150 <item>
151 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
152 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
153 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
154 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
155 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
156 alioth.debian.org, you know the web interface is fairly slow to
157 operate. First you visit one web page, enter the moderation password
158 and get a new page shown with a list of all the messages to moderate
159 and various options for each email address. This take a while for
160 every list you moderate, and you need to do it regularly to do a good
161 job as a list moderator. But there is a quick alternative,
162 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
163 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
164 to moderate in a fraction of a second. Here is a test run on two
165 lists I recently took over:&lt;/p&gt;
166
167 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
168 % time listadmin xiph
169 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
170 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
171
172 real 0m1.709s
173 user 0m0.232s
174 sys 0m0.012s
175 %
176 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
177
178 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
179 there are no message in the moderation queue. Every morning I
180 currently moderate 68 mailman lists, and it normally take around two
181 minutes. When I took over the two pkg-xiph lists above a few days
182 ago, there were 400 emails waiting in the moderator queue. It took me
183 less than 15 minutes to process them all using the listadmin
184 program.&lt;/p&gt;
185
186 &lt;p&gt;If you install
187 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
188 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
189 with content like this, the moderation task is a breeze:&lt;/p&gt;
190
191 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
192 username username@example.org
193 spamlevel 23
194 default discard
195 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
196
197 password secret
198 adminurl https://{domain}/mailman/admindb/{list}
199 mailman-list@lists.example.com
200
201 password hidden
202 other-list@otherserver.example.org
203 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
204
205 &lt;p&gt;There are other options to set as well. Check the manual page to
206 learn the details.&lt;/p&gt;
207
208 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
209 the SSL certificate is self signed or not properly signed by a
210 generally accepted signing authority, you can set a environment
211 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
212
213 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
214 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
215 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
216
217 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
218 can provide an argument to the listadmin script like I do in the
219 initial screen dump (the xiph argument). Using an argument, only
220 lists matching the argument string will be processed. This make it
221 quick to accept messages if you notice the moderation request in your
222 email.&lt;/p&gt;
223
224 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
225 mailing lists, as I simply do not have time to spend on that if the
226 process was any slower. The listadmin program have saved me hours of
227 time I could spend elsewhere over the years. It truly is nice free
228 software.&lt;/p&gt;
229
230 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
231 activities, please send Bitcoin donations to my address
232 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
233
234 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
235 configuration example. Also, I&#39;ve been told that the
236 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
237 sure why.&lt;/p&gt;
238 </description>
239 </item>
240
241 <item>
242 <title>Debian Jessie, PXE and automatic firmware installation</title>
243 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
244 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
245 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
246 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
247 problem that the WiFi card require some firmware to work properly.
248 And it has been a pain to fix this using preseeding in Debian.
249 Normally something more is needed. But thanks to
250 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
251 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
252 to do this using simple preseeding.&lt;/p&gt;
253
254 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
255 firmware for the hardware found in the machine (actually, requested by
256 the kernel modules for the hardware). (It can also install user space
257 programs supporting the hardware detected, but that is not the focus
258 of this story.)&lt;/p&gt;
259
260 &lt;p&gt;To get this working in the default installation, two preeseding
261 values are needed. First, the isenkram-cli package must be installed
262 into the target chroot (aka the hard drive) before tasksel is executed
263 in the pkgsel step of the debian-installer system. This is done by
264 preseeding the base-installer/includes debconf value to include the
265 isenkram-cli package. The package name is next passed to debootstrap
266 for installation. With the isenkram-cli package in place, tasksel
267 will automatically use the isenkram tasks to detect hardware specific
268 packages for the machine being installed and install them, because
269 isenkram-cli contain tasksel tasks.&lt;/p&gt;
270
271 &lt;p&gt;Second, one need to enable the non-free APT repository, because
272 most firmware unfortunately is non-free. This is done by preseeding
273 the apt-mirror-setup step. This is unfortunate, but for a lot of
274 hardware it is the only option in Debian.&lt;/p&gt;
275
276 &lt;p&gt;The end result is two lines needed in your preseeding file to get
277 firmware installed automatically by the installer:&lt;/p&gt;
278
279 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
280 base-installer base-installer/includes string isenkram-cli
281 apt-mirror-setup apt-setup/non-free boolean true
282 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
283
284 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
285 both firmware and user space packages when using this method. It also
286 do not work well, so use version 0.15 or later. Installing both
287 firmware and user space packages might give you a bit more than you
288 want, so I decided to split the tasksel task in two, one for firmware
289 and one for user space programs. The firmware task is enabled by
290 default, while the one for user space programs is not. This split is
291 implemented in the package currently in unstable.&lt;/p&gt;
292
293 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
294 this recipe work for you. :)&lt;/p&gt;
295
296 &lt;p&gt;So, I bet you are wondering, how can this work. First and
297 foremost, it work because tasksel is modular, and driven by whatever
298 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
299 isenkram-cli package place two files for tasksel to find. First there
300 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
301
302 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
303 Task: isenkram-packages
304 Section: hardware
305 Description: Hardware specific packages (autodetected by isenkram)
306 Based on the detected hardware various hardware specific packages are
307 proposed.
308 Test-new-install: show show
309 Relevance: 8
310 Packages: for-current-hardware
311
312 Task: isenkram-firmware
313 Section: hardware
314 Description: Hardware specific firmware packages (autodetected by isenkram)
315 Based on the detected hardware various hardware specific firmware
316 packages are proposed.
317 Test-new-install: mark show
318 Relevance: 8
319 Packages: for-current-hardware-firmware
320 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
321
322 &lt;p&gt;The key parts are Test-new-install which indicate how the task
323 should be handled and the Packages line referencing to a script in
324 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
325 list of packages to install. The for-current-hardware-firmware script
326 look like this to list relevant firmware for the machine:
327
328 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
329 #!/bin/sh
330 #
331 PATH=/usr/sbin:$PATH
332 export PATH
333 isenkram-autoinstall-firmware -l
334 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
335
336 &lt;p&gt;With those two pieces in place, the firmware is installed by
337 tasksel during the normal d-i run. :)&lt;/p&gt;
338
339 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
340 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
341 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
342 install.&lt;/p&gt;
343
344 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
345 pilots in testing this feature, as isenkram is used there now to
346 install firmware, replacing the earlier scripts.&lt;/p&gt;
347 </description>
348 </item>
349
350 <item>
351 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
352 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
354 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
355 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
356 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
357 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
358 on a screen normally showing the bread types and prizes:&lt;/p&gt;
359
360 &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;
361
362 &lt;p&gt;If it had booted as it was supposed to, I would never had known
363 about this hidden Linux installation. It is interesting what
364 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
365 </description>
366 </item>
367
368 <item>
369 <title>New lsdvd release version 0.17 is ready</title>
370 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
371 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
372 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
373 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
374 got a new set of developers a few weeks ago, after the original
375 developer decided to step down and pass the project to fresh blood.
376 This project is now maintained by Petter Reinholdtsen and Steve
377 Dibb.&lt;/p&gt;
378
379 &lt;p&gt;I just wrapped up
380 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
381 new lsdvd release&lt;/a&gt;, available in git or from
382 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
383 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
384 0.17.&lt;/p&gt;
385
386 &lt;ul&gt;
387
388 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
389 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
390 non-existant, to work around additional copy protection&lt;/li&gt;
391 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
392 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
393 &lt;li&gt;Fix include orders&lt;/li&gt;
394 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
395 &lt;li&gt;Fix the chapter count&lt;/li&gt;
396 &lt;li&gt;Make sure the array size and the array limit used when initialising
397 the palette size is the same.&lt;/li&gt;
398 &lt;li&gt;Fix array printing.&lt;/li&gt;
399 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
400 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
401 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
402 with more GCC compiler warnings.&lt;/li&gt;
403
404 &lt;/ul&gt;
405
406 &lt;p&gt;This change bring together patches for lsdvd in use in various
407 Linux and Unix distributions, as well as patches submitted to the
408 project the last nine years. Please check it out. :)&lt;/p&gt;
409 </description>
410 </item>
411
412 <item>
413 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
414 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
415 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
416 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
417 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
418 project&lt;/a&gt; provide a Linux solution for schools, including a
419 powerful desktop with education software, a central server providing
420 web pages, user database, user home directories, central login and PXE
421 boot of both clients without disk and the installation to install Debian
422 Edu on machines with disk (and a few other services perhaps to small
423 to mention here). We in the Debian Edu team are currently working on
424 the Jessie based version, trying to get everything in shape before the
425 freeze, to avoid having to maintain our own package repository in the
426 future. The
427 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
428 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
429 work left. Some fatal problems block testing, breaking the installer,
430 but it is possible to work around these to get anyway. Here is a
431 recipe on how to get the installation limping along.&lt;/p&gt;
432
433 &lt;p&gt;First, download the test ISO via
434 &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;,
435 &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;
436 or rsync (use
437 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
438 The ISO build was broken on Tuesday, so we do not get a new ISO every
439 12 hours or so, but thankfully the ISO we already got we are able to
440 install with some tweaking.&lt;/p&gt;
441
442 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
443 (use Alt-Ctrl-F2), run&lt;/p&gt;
444
445 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
446 nano /usr/bin/edu-eatmydata-install
447 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
448
449 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
450 optimization. Return to the installation, select the profile you want
451 and continue. Without this change, exim4-config will fail to install
452 due to a known bug in eatmydata.&lt;/p&gt;
453
454 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
455 this do not work, figure out what your correct value would be. All my
456 test machines need /dev/sda, so I have no advice if it do not fit
457 your need.&lt;/p&gt;
458
459 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
460 root after the initial boot from hard drive, and install the
461 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
462 or mate. If you want several desktop options, install more than one
463 metapackage. Once this is done, reboot and you should have a working
464 graphical login screen. This workaround should no longer be needed
465 once the education-tasks package version 1.801 enter testing in two
466 days.&lt;/p&gt;
467
468 &lt;p&gt;I believe the ISO build will start working on two days when the new
469 tasksel package enter testing and Steve McIntyre get a chance to
470 update the debian-cd git repository. The eatmydata, grub and desktop
471 issues are already fixed in unstable and testing, and should show up
472 on the ISO as soon as the ISO build start working again. Well the
473 eatmydata optimization is really just disabled. The proper fix
474 require an upload by the eatmydata maintainer applying the patch
475 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
476 The rest have proper fixes in unstable.&lt;/p&gt;
477
478 &lt;p&gt;I hope this get you going with the installation testing, as we are
479 quickly running out of time trying to get our Jessie based
480 installation ready before the distribution freeze in a month.&lt;/p&gt;
481 </description>
482 </item>
483
484 <item>
485 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
486 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
487 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
488 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
489 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
490 to handle my fairly large DVD collection. It is a nice command line
491 tool to get details about a DVD, like title, tracks, track length,
492 etc, in XML, Perl or human readable format. But lsdvd have not seen
493 any new development since 2006 and had a few irritating bugs affecting
494 its use with some DVDs. Upstream seemed to be dead, and in January I
495 sent a small probe asking for a version control repository for the
496 project, without any reply. But I use it regularly and would like to
497 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
498 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
499 the project admin, and after getting a reply from him explaining that
500 he was no longer interested in the project, I asked if I could take
501 over. And yesterday, I became project admin.&lt;/p&gt;
502
503 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
504 maintainer interested in joining forces to maintain the upstream
505 project, and I hope we can get a new release out fairly quickly,
506 collecting the patches spread around on the internet into on place.
507 I&#39;ve added the relevant Debian patches to the freshly created git
508 repository, and expect the Gentoo patches to make it too. If you got
509 a DVD collection and care about command line tools, check out
510 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
511 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
512 list&lt;/a&gt;. :)&lt;/p&gt;
513 </description>
514 </item>
515
516 <item>
517 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
518 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
519 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
520 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
521 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
522 a lot quicker. When we install more than 2000 packages in
523 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
524 tasksel in the installer, unpacking the binary packages take forever.
525 A part of the slow I/O issue was discussed in
526 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
527 much file system sync-ing done by dpkg, which is the package
528 responsible for unpacking the binary packages. Other parts (like code
529 executed by postinst scripts) might also sync to disk during
530 installation. All this sync-ing to disk do not really make sense to
531 me. If the machine crash half-way through, I start over, I do not try
532 to salvage the half installed system. So the failure sync-ing is
533 supposed to protect against, hardware or system crash, is not really
534 relevant while the installer is running.&lt;/p&gt;
535
536 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
537 system sync()-ing in a fairly non-intrusive way, without the need to
538 change the code in several packages. The idea is not new, but I have
539 not heard anyone propose the approach using dpkg-divert before. It
540 depend on the small and clever package
541 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
542 uses LD_PRELOAD to replace the system functions for syncing data to
543 disk with functions doing nothing, thus allowing programs to live
544 dangerous while speeding up disk I/O significantly. Instead of
545 modifying the implementation of dpkg, apt and tasksel (which are the
546 packages responsible for selecting, fetching and installing packages),
547 it occurred to me that we could just divert the programs away, replace
548 them with a simple shell wrapper calling
549 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
550 Two days ago I decided to test the idea, and wrapped up a simple
551 implementation for the Debian Edu udeb.&lt;/p&gt;
552
553 &lt;p&gt;The effect was stunning. In my first test it reduced the running
554 time of the pkgsel step (installing tasks) from 64 to less than 44
555 minutes (20 minutes shaved off the installation) on an old Dell
556 Latitude D505 machine. I am not quite sure what the optimised time
557 would have been, as I messed up the testing a bit, causing the debconf
558 priority to get low enough for two questions to pop up during
559 installation. As soon as I saw the questions I moved the installation
560 along, but do not know how long the question were holding up the
561 installation. I did some more measurements using Debian Edu Jessie,
562 and got these results. The time measured is the time stamp in
563 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
564 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
565 yourself. In Debian Edu, the tasksel dialog do not show up, and the
566 timing thus do not depend on how quickly the user handle the tasksel
567 dialog.&lt;/p&gt;
568
569 &lt;p&gt;&lt;table&gt;
570
571 &lt;tr&gt;
572 &lt;th&gt;Machine/setup&lt;/th&gt;
573 &lt;th&gt;Original tasksel&lt;/th&gt;
574 &lt;th&gt;Optimised tasksel&lt;/th&gt;
575 &lt;th&gt;Reduction&lt;/th&gt;
576 &lt;/tr&gt;
577
578 &lt;tr&gt;
579 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
580 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
581 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
582 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
583 &lt;/tr&gt;
584
585 &lt;tr&gt;
586 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
587 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
588 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
589 &lt;td&gt;23 min 40%&lt;/td&gt;
590 &lt;/tr&gt;
591
592 &lt;tr&gt;
593 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
594 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
595 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
596 &lt;td&gt;11 min 50%&lt;/td&gt;
597 &lt;/tr&gt;
598
599 &lt;tr&gt;
600 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
601 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
602 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
603 &lt;td&gt;2 min 33%&lt;/td&gt;
604 &lt;/tr&gt;
605
606 &lt;tr&gt;
607 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
608 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
609 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
610 &lt;td&gt;4 min 21%&lt;/td&gt;
611 &lt;/tr&gt;
612
613 &lt;/table&gt;&lt;/p&gt;
614
615 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
616 time is spent downloading packages. The connection to the Internet
617 was 100Mbit/s during testing, so downloading should not be a
618 significant factor in the measurement. Download typically took a few
619 seconds to a few minutes, depending on the amount of packages being
620 installed.&lt;/p&gt;
621
622 &lt;p&gt;The speedup is implemented by using two hooks in
623 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
624 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
625 finish-install.d hook to remove the divert at the end of the
626 installation. I picked the pre-pkgsel.d hook instead of the
627 post-base-installer.d hook because I test using an ISO without the
628 eatmydata package included, and the post-base-installer.d hook in
629 Debian Edu can only operate on packages included in the ISO. The
630 negative effect of this is that I am unable to activate this
631 optimization for the kernel installation step in d-i. If the code is
632 moved to the post-base-installer.d hook, the speedup would be larger
633 for the entire installation.&lt;/p&gt;
634
635 &lt;p&gt;I&#39;ve implemented this in the
636 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
637 git repository, and plan to provide the optimization as part of the
638 Debian Edu installation. If you want to test this yourself, you can
639 create two files in the installer (or in an udeb). One shell script
640 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
641
642 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
643 #!/bin/sh
644 set -e
645 . /usr/share/debconf/confmodule
646 info() {
647 logger -t my-pkgsel &quot;info: $*&quot;
648 }
649 error() {
650 logger -t my-pkgsel &quot;error: $*&quot;
651 }
652 override_install() {
653 apt-install eatmydata || true
654 if [ -x /target/usr/bin/eatmydata ] ; then
655 for bin in dpkg apt-get aptitude tasksel ; do
656 file=/usr/bin/$bin
657 # Test that the file exist and have not been diverted already.
658 if [ -f /target$file ] ; then
659 info &quot;diverting $file using eatmydata&quot;
660 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
661 &gt; /target$file.edu
662 chmod 755 /target$file.edu
663 in-target dpkg-divert --package debian-edu-config \
664 --rename --quiet --add $file
665 ln -sf ./$bin.edu /target$file
666 else
667 error &quot;unable to divert $file, as it is missing.&quot;
668 fi
669 done
670 else
671 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
672 fi
673 }
674
675 override_install
676 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
677
678 &lt;p&gt;To clean up, another shell script should go into
679 /usr/lib/finish-install.d/ with code like this:
680
681 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
682 #! /bin/sh -e
683 . /usr/share/debconf/confmodule
684 error() {
685 logger -t my-finish-install &quot;error: $@&quot;
686 }
687 remove_install_override() {
688 for bin in dpkg apt-get aptitude tasksel ; do
689 file=/usr/bin/$bin
690 if [ -x /target$file.edu ] ; then
691 rm /target$file
692 in-target dpkg-divert --package debian-edu-config \
693 --rename --quiet --remove $file
694 rm /target$file.edu
695 else
696 error &quot;Missing divert for $file.&quot;
697 fi
698 done
699 sync # Flush file buffers before continuing
700 }
701
702 remove_install_override
703 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
704
705 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
706 edu-eatmydata-install and call it from the pre-pkgsel.d and
707 finish-install.d scripts.&lt;/p&gt;
708
709 &lt;p&gt;By now you might ask if this change should get into the normal
710 Debian installer too? I suspect it should, but am not sure the
711 current debian-installer coordinators find it useful enough. It also
712 depend on the side effects of the change. I&#39;m not aware of any, but I
713 guess we will see if the change is safe after some more testing.
714 Perhaps there is some package in Debian depending on sync() and
715 fsync() having effect? Perhaps it should go into its own udeb, to
716 allow those of us wanting to enable it to do so without affecting
717 everyone.&lt;/p&gt;
718
719 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
720 will break installation of all programs using gnutls because of
721 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
722 eatmydata package in Debian will solve it.&lt;/p&gt;
723
724 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
725 the optimization work again. And I have discovered that the
726 dpkg-divert trick is not really needed and implemented a slightly
727 simpler approach as part of the debian-edu-install package. See
728 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
729
730 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
731 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
732 triggering on i386 made it into testing, and broke this installation
733 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
734 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
735 </description>
736 </item>
737
738 <item>
739 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
740 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
741 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
742 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
743 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
744 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
745 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
746 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
747 learn that there is a large set of publicly available key servers to
748 use when looking for peoples public key. So far I have used
749 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
750 were misbehaving, but those days are ended. The servers I have used
751 up until yesterday have been slow and some times unavailable. I hope
752 those problems are gone now.&lt;/p&gt;
753
754 &lt;p&gt;Behind the round robin DNS entry of the
755 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
756 there is a pool of more than 100 keyservers which are checked every
757 day to ensure they are well connected and up to date. It must be
758 better than what I have used so far. :)&lt;/p&gt;
759
760 &lt;p&gt;Yesterdays speaker told me that the service is the default
761 keyserver provided by the default configuration in GnuPG, but this do
762 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
763
764 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
765 line:&lt;/p&gt;
766
767 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
768 keyserver pool.sks-keyservers.net
769 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
770
771 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
772 entries in DNS. Just for fun, I did just that at work, so now every
773 user of GnuPG at the University of Oslo should find a OpenGPG
774 keyserver automatically should their need it:&lt;/p&gt;
775
776 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
777 % host -t srv _pgpkey-http._tcp.uio.no
778 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
779 %
780 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
781
782 &lt;p&gt;Now if only
783 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
784 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
785 very happy. It can look up a given key or search for a user ID, but I
786 normally do not want that, but to find a trust path from my key to
787 another key. Given a user ID or key ID, I would like to find (and
788 download) the keys representing a signature path from my key to the
789 key in question, to be able to get a trust path between the two keys.
790 This is as far as I can tell not possible today. Perhaps something
791 for a future version of the protocol?&lt;/p&gt;
792 </description>
793 </item>
794
795 <item>
796 <title>From English wiki to translated PDF and epub via Docbook</title>
797 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
798 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
799 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
800 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
801 project&lt;/a&gt; provide an instruction manual for teachers, system
802 administrators and other users that contain useful tips for setting up
803 and maintaining a Debian Edu installation. This text is about how the
804 text processing of this manual is handled in the project.&lt;/p&gt;
805
806 &lt;p&gt;One goal of the project is to provide information in the native
807 language of its users, and for this we need to handle translations.
808 But we also want to make sure each language contain the same
809 information, so for this we need a good way to keep the translations
810 in sync. And we want it to be easy for our users to improve the
811 documentation, avoiding the need to learn special formats or tools to
812 contribute, and the obvious way to do this is to make it possible to
813 edit the documentation using a web browser. We also want it to be
814 easy for translators to keep the translation up to date, and give them
815 help in figuring out what need to be translated. Here is the list of
816 tools and the process we have found trying to reach all these
817 goals.&lt;/p&gt;
818
819 &lt;p&gt;We maintain the authoritative source of our manual in the
820 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
821 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
822 front page with references to the different chapters, several pages
823 for each chapter, and finally one &quot;collection page&quot; gluing all the
824 chapters together into one large web page (aka
825 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
826 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
827 processing and translations. Thanks to the fact that the
828 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
829 wiki.debian.org support exporting pages in
830 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
831 the list of pages to export using the raw version of the AllInOne
832 page, loop over each of them to generate a Docbook XML version of the
833 manual. This process also download images and transform image
834 references to use the locally downloaded images. The generated
835 Docbook XML files are slightly broken, so some post-processing is done
836 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
837 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
838 a handfull of images. The XML file can now be used to generate PDF, HTML
839 and epub versions of the English manual. This is the basic step of
840 our process, making PDF (using dblatex), HTML (using xsltproc) and
841 epub (using dbtoepub) version from Docbook XML, and the resulting files
842 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
843
844 &lt;p&gt;But English documentation is not enough for us. We want translated
845 documentation too, and we want to make it easy for translators to
846 track the English original. For this we use the
847 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
848 which allow us to transform the English Docbook XML file into a
849 translation file (a .pot file), usable with the normal gettext based
850 translation tools used by those translating free software. The pot
851 file is used to create and maintain translation files (several .po
852 files), which the translations update with the native language
853 translations of all titles, paragraphs and blocks of text in the
854 original. The next step is combining the original English Docbook XML
855 and the translation file (say debian-edu-wheezy-manual.nb.po), to
856 create a translated Docbook XML file (in this case
857 debian-edu-wheezy-manual.nb.xml). This translated (or partly
858 translated, if the translation is not complete) Docbook XML file can
859 then be used like the original to create a PDF, HTML and epub version
860 of the documentation.&lt;/p&gt;
861
862 &lt;p&gt;The translators use different tools to edit the .po files. We
863 recommend using
864 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
865 while some use emacs and vi, others can use web based editors like
866 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
867 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
868 is where the .po file end up, in our git repository. Updated
869 translations can either be committed directly to git, or submitted as
870 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
871 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
872
873 &lt;p&gt;One challenge is images, which both might need to be translated (if
874 they show translated user applications), and are needed in different
875 formats when creating PDF and HTML versions (epub is a HTML version in
876 this regard). For this we transform the original PNG images to the
877 needed density and format during build, and have a way to provide
878 translated images by storing translated versions in
879 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
880 package maintainers know more.&lt;/p&gt;
881
882 &lt;p&gt;If you wonder what the result look like, we provide
883 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
884 of the documentation packages on the web&lt;/a&gt;. See for example the
885 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
886 PDF version&lt;/a&gt; or the
887 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
888 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
889 but perhaps it will be done in the future.&lt;/p&gt;
890
891 &lt;p&gt;To learn more, check out
892 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
893 debian-edu-doc package&lt;/a&gt;,
894 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
895 manual on the wiki&lt;/a&gt; and
896 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
897 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
898 </description>
899 </item>
900
901 <item>
902 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
903 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
904 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
905 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
906 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
907 related packages relevant for the computer installed automatically.
908 So I implemented one, using
909 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
910 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
911 run tasksel as user root. You should be presented with a new option,
912 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
913 select it, tasksel will install the packages isenkram claim is fit for
914 the current hardware, hot pluggable or not.&lt;p&gt;
915
916 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
917 description, and the other is the script used to extract the list of
918 packages to install. The first part is in
919 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
920 this:&lt;/p&gt;
921
922 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
923 Task: isenkram
924 Section: hardware
925 Description: Hardware specific packages (autodetected by isenkram)
926 Based on the detected hardware various hardware specific packages are
927 proposed.
928 Test-new-install: mark show
929 Relevance: 8
930 Packages: for-current-hardware
931 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
932
933 &lt;p&gt;The second part is in
934 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
935 this:&lt;/p&gt;
936
937 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
938 #!/bin/sh
939 #
940 (
941 isenkram-lookup
942 isenkram-autoinstall-firmware -l
943 ) | sort -u
944 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
945
946 &lt;p&gt;All in all, a very short and simple implementation making it
947 trivial to install the hardware dependent package we all may want to
948 have installed on our machines. I&#39;ve not been able to find a way to
949 get tasksel to tell you exactly which packages it plan to install
950 before doing the installation. So if you are curious or careful,
951 check the output from the isenkram-* command line tools first.&lt;/p&gt;
952
953 &lt;p&gt;The information about which packages are handling which hardware is
954 fetched either from the isenkram package itself in
955 /usr/share/isenkram/, from git.debian.org or from the APT package
956 database (using the Modaliases header). The APT package database
957 parsing have caused a nasty resource leak in the isenkram daemon (bugs
958 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
959 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
960 the python-apt code (bug
961 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
962 workaround I was able to get rid of the file descriptor leak and
963 reduce the memory leak from ~30 MiB per hardware detection down to
964 around 2 MiB per hardware detection. It should make the desktop
965 daemon a lot more useful. The fix is in version 0.7 uploaded to
966 unstable today.&lt;/p&gt;
967
968 &lt;p&gt;I believe the current way of mapping hardware to packages in
969 Isenkram is is a good draft, but in the future I expect isenkram to
970 use the AppStream data source for this. A proposal for getting proper
971 AppStream support into Debian is floating around as
972 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
973 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
974 project&lt;/a&gt; will take place this summer to improve the situation. I
975 look forward to seeing the result, and welcome patches for isenkram to
976 start using the information when it is ready.&lt;/p&gt;
977
978 &lt;p&gt;If you want your package to map to some specific hardware, either
979 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
980 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
981 package&lt;/a&gt; or submit a bug report with the details to the isenkram
982 package. See also
983 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
984 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
985 the information will be migrated to AppStream eventually, but for the
986 moment I got no better place to store it.&lt;/p&gt;
987 </description>
988 </item>
989
990 <item>
991 <title>FreedomBox milestone - all packages now in Debian Sid</title>
992 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
993 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
994 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
995 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
996 project&lt;/a&gt; is working on providing the software and hardware to make
997 it easy for non-technical people to host their data and communication
998 at home, and being able to communicate with their friends and family
999 encrypted and away from prying eyes. It is still going strong, and
1000 today a major mile stone was reached.&lt;/p&gt;
1001
1002 &lt;p&gt;Today, the last of the packages currently used by the project to
1003 created the system images were accepted into Debian Unstable. It was
1004 the freedombox-setup package, which is used to configure the images
1005 during build and on the first boot. Now all one need to get going is
1006 the build code from the freedom-maker git repository and packages from
1007 Debian. And once the freedombox-setup package enter testing, we can
1008 build everything directly from Debian. :)&lt;/p&gt;
1009
1010 &lt;p&gt;Some key packages used by Freedombox are
1011 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1012 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1013 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1014 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1015 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1016 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1017 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1018 are plans to integrate more packages into the setup. User
1019 documentation is maintained on the Debian wiki. Please
1020 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1021 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1022
1023 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1024 setup, run this on a Debian machine using a user with sudo rights to
1025 become root:&lt;/p&gt;
1026
1027 &lt;p&gt;&lt;pre&gt;
1028 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1029 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1030 u-boot-tools
1031 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1032 freedom-maker
1033 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1034 &lt;/pre&gt;&lt;/p&gt;
1035
1036 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1037 devices. See the README in the freedom-maker git repo for more
1038 details on the build. If you do not want all three images, trim the
1039 make line. Note that the virtualbox-image target is not really
1040 virtualbox specific. It create a x86 image usable in kvm, qemu,
1041 vmware and any other x86 virtual machine environment. You might need
1042 the version of vmdebootstrap in Jessie to get the build working, as it
1043 include fixes for a race condition with kpartx.&lt;/p&gt;
1044
1045 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1046 method, boot a Debian Wheezy ISO and use this boot argument to load
1047 the preseed values:&lt;/p&gt;
1048
1049 &lt;p&gt;&lt;pre&gt;
1050 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;
1051 &lt;/pre&gt;&lt;/p&gt;
1052
1053 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1054 it still work.&lt;/p&gt;
1055
1056 &lt;p&gt;If you wonder how to help, one task you could look at is using
1057 systemd as the boot system. It will become the default for Linux in
1058 Jessie, so we need to make sure it is usable on the Freedombox. I did
1059 a simple test a few weeks ago, and noticed dnsmasq failed to start
1060 during boot when using systemd. I suspect there are other problems
1061 too. :) To detect problems, there is a test suite included, which can
1062 be run from the plinth web interface.&lt;/p&gt;
1063
1064 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1065 us get the new release published. :) Please join us on
1066 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1067 irc.debian.org)&lt;/a&gt; and
1068 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1069 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1070 </description>
1071 </item>
1072
1073 <item>
1074 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1075 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1076 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1077 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1078 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1079 solution for use at home. My requirements are simple, it must be
1080 cheap and locally encrypted (in other words, I keep the encryption
1081 keys, the storage provider do not have access to my private files).
1082 One idea me and my friends had many years ago, before the cloud
1083 storage providers showed up, was to use Google mail as storage,
1084 writing a Linux block device storing blocks as emails in the mail
1085 service provided by Google, and thus get heaps of free space. On top
1086 of this one can add encryption, RAID and volume management to have
1087 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1088 I never found time to implement such system. But the last few weeks I
1089 have looked at a system called
1090 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1091 mounted network backed file system with the features I need.&lt;/p&gt;
1092
1093 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1094 handling several different storage providers, any with Amazon S3,
1095 Google Drive or OpenStack API. There are heaps of such storage
1096 providers. S3QL can also use a local directory as storage, which
1097 combined with sshfs allow for file storage on any ssh server. S3QL
1098 include support for encryption, compression, de-duplication, snapshots
1099 and immutable file systems, allowing me to mount the remote storage as
1100 a local mount point, look at and use the files as if they were local,
1101 while the content is stored in the cloud as well. This allow me to
1102 have a backup that should survive fire. The file system can not be
1103 shared between several machines at the same time, as only one can
1104 mount it at the time, but any machine with the encryption key and
1105 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1106
1107 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1108 package is included already. So to get started, run &lt;tt&gt;apt-get
1109 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1110 Greenqloud, after reading their nice recipe on
1111 &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
1112 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1113 in Iceland more than those in USA when it come to keeping my personal
1114 data safe and private, and thus would rather spend money on a company
1115 in Iceland. Another nice recipe is available from the article
1116 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1117 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1118 Admin magazine. When the provider is picked, figure out how to get
1119 the API key needed to connect to the storage API. With Greencloud,
1120 the key did not show up until I had added payment details to my
1121 account.&lt;/p&gt;
1122
1123 &lt;p&gt;Armed with the API access details, it is time to create the file
1124 system. First, create a new bucket in the cloud. This bucket is the
1125 file system storage area. I picked a bucket name reflecting the
1126 machine that was going to store data there, but any name will do.
1127 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1128 the API login and password, and a locally created password. Store it
1129 all in ~root/.s3ql/authinfo2 like this:
1130
1131 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1132 [s3c]
1133 storage-url: s3c://s.greenqloud.com:443/bucket-name
1134 backend-login: API-login
1135 backend-password: API-password
1136 fs-passphrase: local-password
1137 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1138
1139 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1140 but any sensible way to create a fairly random password should do it.
1141 Armed with these details, it is now time to run mkfs, entering the API
1142 details and password to create it:&lt;/p&gt;
1143
1144 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1145 # mkdir -m 700 /var/lib/s3ql-cache
1146 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1147 --ssl s3c://s.greenqloud.com:443/bucket-name
1148 Enter backend login:
1149 Enter backend password:
1150 Before using S3QL, make sure to read the user&#39;s guide, especially
1151 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1152 Enter encryption password:
1153 Confirm encryption password:
1154 Generating random encryption key...
1155 Creating metadata tables...
1156 Dumping metadata...
1157 ..objects..
1158 ..blocks..
1159 ..inodes..
1160 ..inode_blocks..
1161 ..symlink_targets..
1162 ..names..
1163 ..contents..
1164 ..ext_attributes..
1165 Compressing and uploading metadata...
1166 Wrote 0.00 MB of compressed metadata.
1167 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1168
1169 &lt;p&gt;The next step is mounting the file system to make the storage available.
1170
1171 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1172 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1173 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1174 Using 4 upload threads.
1175 Downloading and decompressing metadata...
1176 Reading metadata...
1177 ..objects..
1178 ..blocks..
1179 ..inodes..
1180 ..inode_blocks..
1181 ..symlink_targets..
1182 ..names..
1183 ..contents..
1184 ..ext_attributes..
1185 Mounting filesystem...
1186 # df -h /s3ql
1187 Filesystem Size Used Avail Use% Mounted on
1188 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1189 #
1190 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1191
1192 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1193 backups in it, and as the metadata used by rsync is downloaded at
1194 mount time, no network traffic (and storage cost) is triggered by
1195 running rsync. To unmount, one should not use the normal umount
1196 command, as this will not flush the cache to the cloud storage, but
1197 instead running the umount.s3ql command like this:
1198
1199 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1200 # umount.s3ql /s3ql
1201 #
1202 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1203
1204 &lt;p&gt;There is a fsck command available to check the file system and
1205 correct any problems detected. This can be used if the local server
1206 crashes while the file system is mounted, to reset the &quot;already
1207 mounted&quot; flag. This is what it look like when processing a working
1208 file system:&lt;/p&gt;
1209
1210 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1211 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1212 Using cached metadata.
1213 File system seems clean, checking anyway.
1214 Checking DB integrity...
1215 Creating temporary extra indices...
1216 Checking lost+found...
1217 Checking cached objects...
1218 Checking names (refcounts)...
1219 Checking contents (names)...
1220 Checking contents (inodes)...
1221 Checking contents (parent inodes)...
1222 Checking objects (reference counts)...
1223 Checking objects (backend)...
1224 ..processed 5000 objects so far..
1225 ..processed 10000 objects so far..
1226 ..processed 15000 objects so far..
1227 Checking objects (sizes)...
1228 Checking blocks (referenced objects)...
1229 Checking blocks (refcounts)...
1230 Checking inode-block mapping (blocks)...
1231 Checking inode-block mapping (inodes)...
1232 Checking inodes (refcounts)...
1233 Checking inodes (sizes)...
1234 Checking extended attributes (names)...
1235 Checking extended attributes (inodes)...
1236 Checking symlinks (inodes)...
1237 Checking directory reachability...
1238 Checking unix conventions...
1239 Checking referential integrity...
1240 Dropping temporary indices...
1241 Backing up old metadata...
1242 Dumping metadata...
1243 ..objects..
1244 ..blocks..
1245 ..inodes..
1246 ..inode_blocks..
1247 ..symlink_targets..
1248 ..names..
1249 ..contents..
1250 ..ext_attributes..
1251 Compressing and uploading metadata...
1252 Wrote 0.89 MB of compressed metadata.
1253 #
1254 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1255
1256 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1257 quick, about the same speed as local file access. Uploading large
1258 amount of data is to me limited by the bandwidth out of and into my
1259 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1260 which is very close to my upload speed, and downloading the same
1261 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1262 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1263 network, not the file system code. I do not know what a good cache
1264 size would be, but suspect that the cache should e larger than your
1265 working set.&lt;/p&gt;
1266
1267 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1268 time. If another machine try, it is told that the file system is
1269 busy:&lt;/p&gt;
1270
1271 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1272 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1273 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1274 Using 8 upload threads.
1275 Backend reports that fs is still mounted elsewhere, aborting.
1276 #
1277 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1278
1279 &lt;p&gt;The file content is uploaded when the cache is full, while the
1280 metadata is uploaded once every 24 hour by default. To ensure the
1281 file system content is flushed to the cloud, one can either umount the
1282 file system, or ask S3QL to flush the cache and metadata using
1283 s3qlctrl:
1284
1285 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1286 # s3qlctrl upload-meta /s3ql
1287 # s3qlctrl flushcache /s3ql
1288 #
1289 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1290
1291 &lt;p&gt;If you are curious about how much space your data uses in the
1292 cloud, and how much compression and deduplication cut down on the
1293 storage usage, you can use s3qlstat on the mounted file system to get
1294 a report:&lt;/p&gt;
1295
1296 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1297 # s3qlstat /s3ql
1298 Directory entries: 9141
1299 Inodes: 9143
1300 Data blocks: 8851
1301 Total data size: 22049.38 MB
1302 After de-duplication: 21955.46 MB (99.57% of total)
1303 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1304 Database size: 2.39 MB (uncompressed)
1305 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1306 #
1307 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1308
1309 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1310 storage. I did not try to locate them all, but am aware of at least
1311 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1312 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1313 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1314 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1315 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1316 accept payment in Bitcoin. Pick one that suit your need. Some of
1317 them provide several GiB of free storage, but the prize models are
1318 quite different and you will have to figure out what suits you
1319 best.&lt;/p&gt;
1320
1321 &lt;p&gt;While researching this blog post, I had a look at research papers
1322 and posters discussing the S3QL file system. There are several, which
1323 told me that the file system is getting a critical check by the
1324 science community and increased my confidence in using it. One nice
1325 poster is titled
1326 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1327 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1328 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1329 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1330 and Pamela Smith. Please have a look.&lt;/p&gt;
1331
1332 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1333 check out the mounted S3QL file system to see if it would be usable as
1334 a home directory (in other word, that it provided POSIX semantics when
1335 it come to locking and umask handling etc). Running
1336 &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
1337 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1338 no error was found. So the file system can be used for home
1339 directories, if one chooses to do so.&lt;/p&gt;
1340
1341 &lt;p&gt;If you do not want a locally file system, and want something that
1342 work without the Linux fuse file system, I would like to mention the
1343 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1344 provide locally encrypted backup using a command line client. It have
1345 a nicer access control system, where one can split out read and write
1346 access, allowing some systems to write to the backup and others to
1347 only read from it.&lt;/p&gt;
1348
1349 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1350 activities, please send Bitcoin donations to my address
1351 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1352 </description>
1353 </item>
1354
1355 <item>
1356 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1357 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1358 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1359 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1360 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1361 project&lt;/a&gt; is working on providing the software and hardware for
1362 making it easy for non-technical people to host their data and
1363 communication at home, and being able to communicate with their
1364 friends and family encrypted and away from prying eyes. It has been
1365 going on for a while, and is slowly progressing towards a new test
1366 release (0.2).&lt;/p&gt;
1367
1368 &lt;p&gt;And what day could be better than the Pi day to announce that the
1369 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1370 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1371 system), and can also be installed using a Debian installer preseed
1372 file. The Debian based Freedombox is now based on Debian Jessie,
1373 where most of the needed packages used are already present. Only one,
1374 the freedombox-setup package, is missing. To try to build your own
1375 boot image to test the current status, fetch the freedom-maker scripts
1376 and build using
1377 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1378 with a user with sudo access to become root:
1379
1380 &lt;pre&gt;
1381 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1382 freedom-maker
1383 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1384 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1385 u-boot-tools
1386 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1387 &lt;/pre&gt;
1388
1389 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1390 devices. See the README for more details on the build. If you do not
1391 want all three images, trim the make line. But note that thanks to &lt;a
1392 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1393 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1394 kpartx call.&lt;/p&gt;
1395
1396 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1397 method, boot a Debian Wheezy ISO and use this boot argument to load
1398 the preseed values:&lt;/p&gt;
1399
1400 &lt;pre&gt;
1401 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;
1402 &lt;/pre&gt;
1403
1404 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1405 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1406 currently hang while setting up APT sources. Killing the
1407 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1408 installation will get the installation going. This affect all
1409 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1410
1411 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1412 us get the new release published. :) Please join us on
1413 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1414 irc.debian.org)&lt;/a&gt; and
1415 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1416 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1417 </description>
1418 </item>
1419
1420 <item>
1421 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1422 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1423 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1424 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1425 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1426 innetgr tools, because I needed them in
1427 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1428 ng-utils, and it has served me well. I placed the project under the
1429 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1430 repository. But many years ago, the CVS repository was dropped (lost,
1431 not migrated to new hardware, not sure), and the project have lacked a
1432 proper home since then.&lt;/p&gt;
1433
1434 &lt;p&gt;Last summer, I had a look at the package and made a new release
1435 fixing a irritating crash bug, but was unable to store the changes in
1436 a proper source control system. I applied for a project on
1437 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1438 to follow up on it. Until today. :)&lt;/p&gt;
1439
1440 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1441 now have a new home, and a git repository with the highlight of the
1442 history of the project. I published all release tarballs and imported
1443 them into the git repository. As the project is really stable and not
1444 expected to gain new features any time soon, I decided to make a new
1445 release and call it 1.0. Visit the new project home on
1446 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1447 if you want to check it out. The new version is also uploaded into
1448 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1449 </description>
1450 </item>
1451
1452 <item>
1453 <title>Testing sysvinit from experimental in Debian Hurd</title>
1454 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1456 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1457 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1458 their changes into sysvinit, to allow them to use the normal sysvinit
1459 boot system instead of their old one. This follow up on the
1460 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1461 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1462 get Debian on Hurd working more like Debian on Linux. To get started,
1463 I downloaded a prebuilt hard disk image from
1464 &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;,
1465 and started it using virt-manager.&lt;/p&gt;
1466
1467 &lt;p&gt;The first think I had to do after logging in (root without any
1468 password) was to get the network operational. I followed
1469 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1470 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1471 commands as root to get the machine to accept a IP address from the
1472 kvm internal DHCP server:&lt;/p&gt;
1473
1474 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1475 settrans -fgap /dev/netdde /hurd/netdde
1476 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1477 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1478 dhclient /dev/eth0
1479 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1480
1481 &lt;p&gt;After this, the machine had internet connectivity, and I could
1482 upgrade it and install the sysvinit packages from experimental and
1483 enable it as the default boot system in Hurd.&lt;/p&gt;
1484
1485 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1486 running on the machine it for ssh login to work a password need to be
1487 set. Also, note that a bug somewhere in openssh on Hurd block
1488 compression from working. Remember to turn that off on the client
1489 side.&lt;/p&gt;
1490
1491 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1492 stuff:&lt;/p&gt;
1493
1494 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1495 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1496 deb http://http.debian.net/debian/ experimental main
1497 EOF
1498 apt-get update
1499 apt-get dist-upgrade
1500 apt-get install -t experimental initscripts sysv-rc sysvinit \
1501 sysvinit-core sysvinit-utils
1502 update-alternatives --config runsystem
1503 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1504
1505 &lt;p&gt;To reboot after switching boot system, you have to use
1506 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1507 yet a sysvinit process able to receive the signals from the normal
1508 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1509 upgrading every package and rebooting, the network come up with DHCP
1510 after boot as it should, and the settrans/pkill hack mentioned at the
1511 start is no longer needed. But for some strange reason, there are no
1512 longer any login prompt in the virtual console, so I logged in using
1513 ssh instead.
1514
1515 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1516 fail some times. No idea what the cause is, but hope the Hurd porters
1517 figure it out. At least Justus said on IRC (#debian-hurd on
1518 irc.debian.org) that they are aware of the problem. A way to reduce
1519 the impact is to upgrade to the Hurd packages built by Justus by
1520 adding this repository to the machine:&lt;/p&gt;
1521
1522 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1523 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1524 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1525 EOF
1526 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1527
1528 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1529 http://ftp.debian-ports.org/debian, because some of the packages in
1530 unstable do not yet include the required patches that are lingering in
1531 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1532
1533 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1534 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1535 i emacs - GNU Emacs editor (metapackage)
1536 i gdb - GNU Debugger
1537 i hurd-recommended - Miscellaneous translators
1538 i isc-dhcp-client - ISC DHCP client
1539 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1540 i libc-bin - Embedded GNU C Library: Binaries
1541 i libc-dev-bin - Embedded GNU C Library: Development binaries
1542 i libc0.3 - Embedded GNU C Library: Shared libraries
1543 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1544 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1545 i multiarch-support - Transitional package to ensure multiarch compatibilit
1546 i A x11-common - X Window System (X.Org) infrastructure
1547 i xorg - X.Org X Window System
1548 i A xserver-xorg - X.Org X server
1549 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1550 #
1551 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1552
1553 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1554 X.org did not work out of the box and I never took the time to follow
1555 the porters instructions to fix it. This time I was interested in the
1556 command line stuff.&lt;p&gt;
1557 </description>
1558 </item>
1559
1560 <item>
1561 <title>New chrpath release 0.16</title>
1562 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1563 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1564 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1565 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1566 find problems in C, C++ and Java code using static source code
1567 analysis. It can detect a lot of different problems, and is very
1568 useful to find memory and locking bugs in the error handling part of
1569 the source. The company behind it provide
1570 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1571 a community service&lt;/a&gt;, and many hundred free software projects are
1572 already checked. A few days ago I decided to have a closer look at
1573 the Coverity system, and discovered that the
1574 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1575 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1576 projects I am involved with was already registered. But these are
1577 fairly big, and I would also like to have a small and easy project to
1578 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1579 checking of the chrpath project&lt;/a&gt;. It was
1580 added to the checker and discovered seven potential defects. Six of
1581 these were real, mostly resource &quot;leak&quot; when the program detected an
1582 error. Nothing serious, as the resources would be released a fraction
1583 of a second later when the program exited because of the error, but it
1584 is nice to do it right in case the source of the program some time in
1585 the future end up in a library. Having fixed all defects and added
1586 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1587 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1588 publish a new release. These are the release notes:&lt;/p&gt;
1589
1590 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1591
1592 &lt;ul&gt;
1593
1594 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1595 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1596 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1597
1598 &lt;/ul&gt;
1599
1600 &lt;p&gt;You can
1601 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1602 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1603 project if something is wrong with the new release. The test suite
1604 did not discover any old errors, so if you find a new one, please also
1605 include a test suite check.&lt;/p&gt;
1606 </description>
1607 </item>
1608
1609 <item>
1610 <title>New chrpath release 0.15</title>
1611 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1612 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1613 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1614 <description>&lt;p&gt;After many years break from the package and a vain hope that
1615 development would be continued by someone else, I finally pulled my
1616 acts together this morning and wrapped up a new release of chrpath,
1617 the command line tool to modify the rpath and runpath of already
1618 compiled ELF programs. The update was triggered by the persistence of
1619 Isha Vishnoi at IBM, which needed a new config.guess file to get
1620 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1621 is working on. I checked the
1622 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1623 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1624 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1625 packages for interesting patches (failed to find the source from
1626 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1627 These are the release notes:&lt;/p&gt;
1628
1629 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1630
1631 &lt;ul&gt;
1632
1633 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1634 with newer architectures. Thanks to isha vishnoi for the heads
1635 up.&lt;/li&gt;
1636
1637 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1638
1639 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1640 Matthias Klose.&lt;/li&gt;
1641
1642 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1643 Petr Machata found in Fedora.&lt;/li&gt;
1644
1645 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1646 .dynamic is a NULL terminated string. Based on patch found in
1647 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1648
1649 &lt;/ul&gt;
1650
1651 &lt;p&gt;You can
1652 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1653 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1654 project if something is wrong with the new release. The test suite
1655 did not discover any old errors, so if you find a new one, please also
1656 include a testsuite check.&lt;/p&gt;
1657 </description>
1658 </item>
1659
1660 <item>
1661 <title>Debian init.d boot script example for rsyslog</title>
1662 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1663 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1664 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1665 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1666 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1667 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1668 init.d scripts at all. Here is an example init.d script, ie a rewrite
1669 of /etc/init.d/rsyslog:&lt;/p&gt;
1670
1671 &lt;p&gt;&lt;pre&gt;
1672 #!/lib/init/init-d-script
1673 ### BEGIN INIT INFO
1674 # Provides: rsyslog
1675 # Required-Start: $remote_fs $time
1676 # Required-Stop: umountnfs $time
1677 # X-Stop-After: sendsigs
1678 # Default-Start: 2 3 4 5
1679 # Default-Stop: 0 1 6
1680 # Short-Description: enhanced syslogd
1681 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1682 # It is quite compatible to stock sysklogd and can be
1683 # used as a drop-in replacement.
1684 ### END INIT INFO
1685 DESC=&quot;enhanced syslogd&quot;
1686 DAEMON=/usr/sbin/rsyslogd
1687 &lt;/pre&gt;&lt;/p&gt;
1688
1689 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1690 script was 137 lines, and the above is just 15 lines, most of it meta
1691 info/comments.&lt;/p&gt;
1692
1693 &lt;p&gt;How to do this, you ask? Well, one create a new script
1694 /lib/init/init-d-script looking something like this:
1695
1696 &lt;p&gt;&lt;pre&gt;
1697 #!/bin/sh
1698
1699 # Define LSB log_* functions.
1700 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1701 # and status_of_proc is working.
1702 . /lib/lsb/init-functions
1703
1704 #
1705 # Function that starts the daemon/service
1706
1707 #
1708 do_start()
1709 {
1710 # Return
1711 # 0 if daemon has been started
1712 # 1 if daemon was already running
1713 # 2 if daemon could not be started
1714 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1715 || return 1
1716 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1717 $DAEMON_ARGS \
1718 || return 2
1719 # Add code here, if necessary, that waits for the process to be ready
1720 # to handle requests from services started subsequently which depend
1721 # on this one. As a last resort, sleep for some time.
1722 }
1723
1724 #
1725 # Function that stops the daemon/service
1726 #
1727 do_stop()
1728 {
1729 # Return
1730 # 0 if daemon has been stopped
1731 # 1 if daemon was already stopped
1732 # 2 if daemon could not be stopped
1733 # other if a failure occurred
1734 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1735 RETVAL=&quot;$?&quot;
1736 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1737 # Wait for children to finish too if this is a daemon that forks
1738 # and if the daemon is only ever run from this initscript.
1739 # If the above conditions are not satisfied then add some other code
1740 # that waits for the process to drop all resources that could be
1741 # needed by services started subsequently. A last resort is to
1742 # sleep for some time.
1743 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1744 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1745 # Many daemons don&#39;t delete their pidfiles when they exit.
1746 rm -f $PIDFILE
1747 return &quot;$RETVAL&quot;
1748 }
1749
1750 #
1751 # Function that sends a SIGHUP to the daemon/service
1752 #
1753 do_reload() {
1754 #
1755 # If the daemon can reload its configuration without
1756 # restarting (for example, when it is sent a SIGHUP),
1757 # then implement that here.
1758 #
1759 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1760 return 0
1761 }
1762
1763 SCRIPTNAME=$1
1764 scriptbasename=&quot;$(basename $1)&quot;
1765 echo &quot;SN: $scriptbasename&quot;
1766 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1767 script=&quot;$1&quot;
1768 shift
1769 . $script
1770 else
1771 exit 0
1772 fi
1773
1774 NAME=$(basename $DAEMON)
1775 PIDFILE=/var/run/$NAME.pid
1776
1777 # Exit if the package is not installed
1778 #[ -x &quot;$DAEMON&quot; ] || exit 0
1779
1780 # Read configuration variable file if it is present
1781 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
1782
1783 # Load the VERBOSE setting and other rcS variables
1784 . /lib/init/vars.sh
1785
1786 case &quot;$1&quot; in
1787 start)
1788 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
1789 do_start
1790 case &quot;$?&quot; in
1791 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1792 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1793 esac
1794 ;;
1795 stop)
1796 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
1797 do_stop
1798 case &quot;$?&quot; in
1799 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1800 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1801 esac
1802 ;;
1803 status)
1804 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
1805 ;;
1806 #reload|force-reload)
1807 #
1808 # If do_reload() is not implemented then leave this commented out
1809 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
1810 #
1811 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
1812 #do_reload
1813 #log_end_msg $?
1814 #;;
1815 restart|force-reload)
1816 #
1817 # If the &quot;reload&quot; option is implemented then remove the
1818 # &#39;force-reload&#39; alias
1819 #
1820 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
1821 do_stop
1822 case &quot;$?&quot; in
1823 0|1)
1824 do_start
1825 case &quot;$?&quot; in
1826 0) log_end_msg 0 ;;
1827 1) log_end_msg 1 ;; # Old process is still running
1828 *) log_end_msg 1 ;; # Failed to start
1829 esac
1830 ;;
1831 *)
1832 # Failed to stop
1833 log_end_msg 1
1834 ;;
1835 esac
1836 ;;
1837 *)
1838 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
1839 exit 3
1840 ;;
1841 esac
1842
1843 :
1844 &lt;/pre&gt;&lt;/p&gt;
1845
1846 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
1847 lot. I did not really polish the approach, so it might not always
1848 work out of the box, but you get the idea. I did not try very hard to
1849 optimize it nor make it more robust either.&lt;/p&gt;
1850
1851 &lt;p&gt;A better argument for switching init system in Debian than reducing
1852 the size of init scripts (which is a good thing to do anyway), is to
1853 get boot system that is able to handle the kernel events sensibly and
1854 robustly, and do not depend on the boot to run sequentially. The boot
1855 and the kernel have not behaved sequentially in years.&lt;/p&gt;
1856 </description>
1857 </item>
1858
1859 <item>
1860 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
1861 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
1862 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
1863 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
1864 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
1865 remote display access is the preferred solution with oVirt and RedHat
1866 Enterprise Virtualization, and I was sad to discover the other day
1867 that the browser plugin needed to use these systems seamlessly was
1868 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
1869 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
1870 2013-04-01, so I decided to wrap up a package based on the great work
1871 from Cajus Pollmeier and put it in a collab-maint maintained git
1872 repository to get a package I could use. I would very much like
1873 others to help me maintain the package (or just take over, I do not
1874 mind), but as no-one had volunteered so far, I just uploaded it to
1875 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
1876
1877 &lt;p&gt;The source is now available from
1878 &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;
1879 </description>
1880 </item>
1881
1882 <item>
1883 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
1884 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
1885 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
1886 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
1887 <description>&lt;p&gt;The
1888 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
1889 program is a a very nice system to create virtual machine images. It
1890 create a image file, add a partition table, mount it and run
1891 debootstrap in the mounted directory to create a Debian system on a
1892 stick. Yesterday, I decided to try to teach it how to make images for
1893 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1894 of a plan to simplify the build system for
1895 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1896 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1897 the virtualbox images, but its current build system made multistrap
1898 based system for Dreamplug images, and it is lacking support for
1899 Raspberry Pi.&lt;/p&gt;
1900
1901 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1902 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1903 code and adjusted it to be able to build armel images on my amd64
1904 Debian laptop. I ended up giving vmdebootstrap five new options,
1905 allowing me to replicate the image creation process I use to make
1906 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
1907 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
1908 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
1909 call debootstrap with --foreign and to copy the handler into the
1910 generated chroot before running the second stage. This allow
1911 vmdebootstrap to create armel images on an amd64 host. Next I added
1912 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
1913 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
1914 given file system type, allowing me to create an image with a vfat
1915 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
1916 variant&lt;/tt&gt; option to allow me to create smaller images without the
1917 Debian base system packages installed. Finally, I added an option
1918 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
1919 as a boot loader. It is not needed on the Raspberry Pi and probably
1920 most other non-x86 architectures. The changes were accepted by the
1921 upstream author of vmdebootstrap yesterday and today, and is now
1922 available from
1923 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
1924 upstream project page&lt;/a&gt;.&lt;/p&gt;
1925
1926 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
1927 create a small script (the customize script) to add the non-free
1928 binary blob needed to boot the Raspberry Pi and the APT source
1929 list:&lt;/p&gt;
1930
1931 &lt;p&gt;&lt;pre&gt;
1932 #!/bin/sh
1933 set -e # Exit on first error
1934 rootdir=&quot;$1&quot;
1935 cd &quot;$rootdir&quot;
1936 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
1937 deb http://http.debian.net/debian/ jessie main contrib non-free
1938 EOF
1939 # Install non-free binary blob needed to boot Raspberry Pi. This
1940 # install a kernel somewhere too.
1941 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1942 -O $rootdir/usr/bin/rpi-update
1943 chmod a+x $rootdir/usr/bin/rpi-update
1944 mkdir -p $rootdir/lib/modules
1945 touch $rootdir/boot/start.elf
1946 chroot $rootdir rpi-update
1947 &lt;/pre&gt;&lt;/p&gt;
1948
1949 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
1950 to build the image:&lt;/p&gt;
1951
1952 &lt;pre&gt;
1953 sudo ./vmdebootstrap \
1954 --variant minbase \
1955 --arch armel \
1956 --distribution jessie \
1957 --mirror http://http.debian.net/debian \
1958 --image test.img \
1959 --size 600M \
1960 --bootsize 64M \
1961 --boottype vfat \
1962 --log-level debug \
1963 --verbose \
1964 --no-kernel \
1965 --no-extlinux \
1966 --root-password raspberry \
1967 --hostname raspberrypi \
1968 --foreign /usr/bin/qemu-arm-static \
1969 --customize `pwd`/customize \
1970 --package netbase \
1971 --package git-core \
1972 --package binutils \
1973 --package ca-certificates \
1974 --package wget \
1975 --package kmod
1976 &lt;/pre&gt;&lt;/p&gt;
1977
1978 &lt;p&gt;The list of packages being installed are the ones needed by
1979 rpi-update to make the image bootable on the Raspberry Pi, with the
1980 exception of netbase, which is needed by debootstrap to find
1981 /etc/hosts with the minbase variant. I really wish there was a way to
1982 set up an Raspberry Pi using only packages in the Debian archive, but
1983 that is not possible as far as I know, because it boots from the GPU
1984 using a non-free binary blob.&lt;/p&gt;
1985
1986 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
1987 probably a few others installed. I have not checked the complete
1988 build dependency list.&lt;/p&gt;
1989
1990 &lt;p&gt;The resulting image will not use the hardware floating point unit
1991 on the Raspberry PI, because the armel architecture in Debian is not
1992 optimized for that use. So the images created will be a bit slower
1993 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
1994 </description>
1995 </item>
1996
1997 <item>
1998 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
1999 <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>
2000 <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>
2001 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2002 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2003 wider attention. I recommend signing and donating to each one of
2004 these. :)&lt;/p&gt;
2005
2006 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2007 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2008 Women program which is a Google Summer of Code like initiative to get
2009 more women involved in free software. One debian sponsor has offered
2010 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2011 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2012 hope you will to. :)&lt;/p&gt;
2013
2014 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2015 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2016 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2017 take place these days, and their need to fund the work. I&#39;ve already
2018 donated. Are you next?&lt;/p&gt;
2019
2020 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2021 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2022 statement under the heading
2023 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2024 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2025 Norwegian government. So far 499 signatures. I hope you will sign it
2026 too.&lt;/p&gt;
2027 </description>
2028 </item>
2029
2030 <item>
2031 <title>Videos about the Freedombox project - for inspiration and learning</title>
2032 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2033 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2034 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2035 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2036 project&lt;/a&gt; have been going on for a while, and have presented the
2037 vision, ideas and solution several places. Here is a little
2038 collection of videos of talks and presentation of the project.&lt;/p&gt;
2039
2040 &lt;ul&gt;
2041
2042 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2043 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2044
2045 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2046 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2047
2048 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2049 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2050 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2051 (Youtube)&lt;/li&gt;
2052
2053 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2054 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2055
2056 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2057 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2058
2059 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2060 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2061 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2062
2063 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2064 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2065 (Youtube)&lt;/li&gt;
2066
2067 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2068 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2069
2070 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2071 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2072
2073 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2074 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2075 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2076
2077 &lt;/ul&gt;
2078
2079 &lt;p&gt;A larger list is available from
2080 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2081 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2082
2083 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2084 Jessie is coming along quite well, and soon both Owncloud and using
2085 Tor should be available for testers of the Freedombox solution. :) In
2086 a few weeks I hope everything needed to test it is included in Debian.
2087 The withsqlite package is already in Debian, and the plinth package is
2088 pending in NEW. The third and vital part of that puzzle is the
2089 metapackage/setup framework, which is still pending an upload. Join
2090 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2091 (#freedombox on irc.debian.org)&lt;/a&gt; and
2092 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2093 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2094 </description>
2095 </item>
2096
2097 <item>
2098 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2099 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2100 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2101 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2102 <description>&lt;p&gt;I was introduced to the
2103 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2104 in 2010, when Eben Moglen presented his vision about serving the need
2105 of non-technical people to keep their personal information private and
2106 within the legal protection of their own homes. The idea is to give
2107 people back the power over their network and machines, and return
2108 Internet back to its intended peer-to-peer architecture. Instead of
2109 depending on a central service, the Freedombox will give everyone
2110 control over their own basic infrastructure.&lt;/p&gt;
2111
2112 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2113 taken priority. But this summers nasty news about the misuse of trust
2114 and privilege exercised by the &quot;western&quot; intelligence gathering
2115 communities increased my eagerness to contribute to a point where I
2116 actually started working on the project a while back.&lt;/p&gt;
2117
2118 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2119 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2120 create a simple and cheap Debian based appliance that anyone can hook
2121 up in their home and get access to secure and private services and
2122 communication. The initial deployment platform have been the
2123 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2124 which is a piece of hardware I do not own. So to be able to test what
2125 the current Freedombox setup look like, I had to come up with a way to install
2126 it on some hardware I do have access to. I have rewritten the
2127 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2128 image build framework to use .deb packages instead of only copying
2129 setup into the boot images, and thanks to this rewrite I am able to
2130 set up any machine supported by Debian Wheezy as a Freedombox, using
2131 the previously mentioned deb (and a few support debs for packages
2132 missing in Debian).&lt;/p&gt;
2133
2134 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2135 scripts
2136 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2137 and a administrative web interface
2138 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2139 withsqlite), as well as a privacy enhancing proxy based on
2140 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2141 (freedombox-privoxy). There is also a web/javascript based XMPP
2142 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2143 trying (unsuccessfully so far) to talk to the XMPP server
2144 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2145 web interface is pluggable, and the goal is to use it to enable OpenID
2146 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2147 this is really working yet, see
2148 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2149 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2150 on github at the moment. The HTTP proxy is operational out of the
2151 box, and the admin web interface can be used to add/remove plinth
2152 users. I&#39;ve not been able to do anything else with it so far, but
2153 know there are several branches spread around github and other places
2154 with lots of half baked features.&lt;/p&gt;
2155
2156 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2157 following recipes should work to give you a test machine to poke
2158 at.&lt;/p&gt;
2159
2160 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2161
2162 &lt;ol&gt;
2163
2164 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2165 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2166 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2167 to the Debian installer:&lt;p&gt;
2168 &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;
2169
2170 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2171 install on.&lt;/li&gt;
2172
2173 &lt;li&gt;When the installation is finished and the machine have rebooted a
2174 few times, your Freedombox is ready for testing.&lt;/li&gt;
2175
2176 &lt;/ol&gt;
2177
2178 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2179
2180 &lt;ol&gt;
2181
2182 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2183 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2184 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2185 &lt;pre&gt;
2186 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2187 &lt;/pre&gt;&lt;/li&gt;
2188 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2189 &lt;pre&gt;
2190 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2191 apt-key add -
2192 apt-get update
2193 apt-get install freedombox-setup
2194 /usr/lib/freedombox/setup
2195 &lt;/pre&gt;&lt;/li&gt;
2196 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2197
2198 &lt;/ol&gt;
2199
2200 &lt;p&gt;You can test it on other architectures too, but because the
2201 freedombox-privoxy package is binary, it will only work as intended on
2202 the architectures where I have had time to build the binary and put it
2203 in my APT repository. But do not let this stop you. It is only a
2204 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2205
2206 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2207 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2208 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2209 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2210
2211 &lt;p&gt;Please let me know if this works for you, or if you have any
2212 problems. We gather on the IRC channel
2213 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2214 irc.debian.org and the
2215 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2216 mailing list&lt;/a&gt;.&lt;/p&gt;
2217
2218 &lt;p&gt;Once you get your freedombox operational, you can visit
2219 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2220 welcome screen (dead end - do not be surprised if you are unable to
2221 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2222 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2223 default password is &#39;secret&#39;.&lt;/p&gt;
2224 </description>
2225 </item>
2226
2227 <item>
2228 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2229 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2230 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2231 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2232 <description>&lt;p&gt;Earlier, I reported about
2233 &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
2234 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2235 told by IBM that the original disk should be thrown away. And as
2236 there no longer was a problem if I bricked the firmware, I decided
2237 today to try to install Intel firmware to replace the Lenovo firmware
2238 currently on the disk.&lt;/p&gt;
2239
2240 &lt;p&gt;I searched the Intel site for firmware, and found
2241 &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;
2242 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2243 according to the site should contain the latest firmware for SSD
2244 disks. I inserted the broken disk in one of my spare laptops and
2245 booted the ISO from a USB stick. The disk was recognized, but the
2246 program claimed the newest firmware already were installed and refused
2247 to insert any Intel firmware. So no change, and the disk is still
2248 unable to handle write load. :( I guess the only way to get them
2249 working would be if Lenovo releases new firmware. No idea how likely
2250 that is. Anyway, just blogging about this test for completeness. I
2251 got a working Samsung disk, and see no point in spending more time on
2252 the broken disks.&lt;/p&gt;
2253 </description>
2254 </item>
2255
2256 <item>
2257 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2258 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2259 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2260 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2261 <description>&lt;p&gt;Today I switched to
2262 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2263 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2264 my new Thinkpad X230, which was delivered with an
2265 &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
2266 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2267 sustained writes. My hardware supplier have been very forthcoming in
2268 trying to find a solution, and after first trying with another
2269 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2270 disk instead to fix it once and for all. The Samsung disk survived
2271 the installation of Debian with encrypted disks (filling the disk with
2272 random data during installation killed the first two), and I thus
2273 decided to trust it with my data. I have installed it as a Debian Edu
2274 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2275 server at home using Kerberos and LDAP, and will use it as my work
2276 station from now on.&lt;/p&gt;
2277
2278 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2279 Debian Wheezy default installation need to be tuned a bit to increase
2280 performance and increase life time of the disk. The Linux kernel and
2281 user space applications do not yet adjust automatically to such
2282 environment. To make it easier for my self, I created a draft Debian
2283 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2284 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2285 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2286 is set up to adjust the setup of the machine by just installing the
2287 package. If there is any non-SSD disk in the machine, the package
2288 will refuse to install, as I did not try to write any logic to sort
2289 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2290
2291 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2292 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2293 where I set up the machine with one large encrypted partition (in
2294 addition to /boot), put LVM on top of this and set up partitions on
2295 top of this again. See the README file in the package source for the
2296 references I used to pick the settings. At the moment these
2297 parameters are tuned:&lt;/p&gt;
2298
2299 &lt;ul&gt;
2300
2301 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2302 (adding discard to /etc/crypttab)&lt;/li&gt;
2303
2304 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2305 this case a cryptsetup partition) by changing issue_discards from
2306 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2307
2308 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2309 systems.&lt;/li&gt;
2310
2311 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2312 /etc/fstab.&lt;/li&gt;
2313
2314 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2315
2316 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2317 cron.daily).&lt;/li&gt;
2318
2319 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2320 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2321
2322 &lt;/ul&gt;
2323
2324 &lt;p&gt;During installation, I cancelled the part where the installer fill
2325 the disk with random data, as this would kill the SSD performance for
2326 little gain. My goal with the encrypted file system is to ensure
2327 those stealing my laptop end up with a brick and not a working
2328 computer. I have no hope in keeping the really resourceful people
2329 from getting the data on the disk (see
2330 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2331 Thus I concluded that adding the discard option to crypttab is the
2332 right thing to do.&lt;/p&gt;
2333
2334 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2335 it for SSD, but others recommended deadline and a benchmark I found
2336 indicated that deadline might be better for interactive use.&lt;/p&gt;
2337
2338 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2339 and ext4, but read that it would give a performance hit ever time a
2340 file is removed, and thought it best to that that slowdown once a day
2341 instead of during my work.&lt;/p&gt;
2342
2343 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2344 this is already done by Debian Edu.&lt;/p&gt;
2345
2346 &lt;p&gt;I have not yet started on the user space tuning. I expect
2347 iceweasel need some tuning, and perhaps other applications too, but
2348 have not yet had time to investigate those parts.&lt;/p&gt;
2349
2350 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2351 there.&lt;/p&gt;
2352
2353 &lt;p&gt;As for the answer to the question in the title of this blog post,
2354 as far as I know, the only solution I know about is to replace the
2355 disk. It might be possible to flash it with Intel firmware instead of
2356 the Lenovo firmware. But I have not tried and did not want to do so
2357 without approval from Lenovo as I wanted to keep the warranty on the
2358 disk until a solution was found and they wanted the broken disks
2359 back.&lt;/p&gt;
2360 </description>
2361 </item>
2362
2363 <item>
2364 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2365 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2366 <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>
2367 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2368 <description>&lt;p&gt;A few days ago, I wrote about
2369 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2370 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2371 was dying during installation because it is unable to cope with
2372 sustained write. My supplier is in contact with
2373 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2374 replacement disk to try to fix the problem. They decided to send an
2375 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2376
2377 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2378 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2379 same firmware version as the original. This time my hope raised
2380 slightly as the installation progressed, as the original disk used to
2381 die after 4-7% of the disk was written to, while this time it kept
2382 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2383 died again and I was back on square one. I still do not have a new
2384 laptop with a disk I can trust. I can not live with a disk that might
2385 lock up when I download a new
2386 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2387 other large files. I look forward to hearing from my supplier with
2388 the next proposal from Lenovo.&lt;/p&gt;
2389
2390 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2391 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2392 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2393 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2394 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2395 P/N 45N8295, P0C38732.&lt;/p&gt;
2396
2397 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2398 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2399 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2400 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2401 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2402 P/N 45N8295, P0C38732.&lt;/p&gt;
2403
2404 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2405 SA, date and WNPP values. Mentioning all the details here in case
2406 someone is able to use the information to find a way to identify the
2407 failing disk among working ones (if any such working disk actually
2408 exist).&lt;/p&gt;
2409 </description>
2410 </item>
2411
2412 <item>
2413 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2414 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2415 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2416 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2417 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2418 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2419 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2420 member assosiation NUUG&lt;/a&gt; and
2421 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2422 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2423 Bitraf&lt;/a&gt;.&lt;/p&gt;
2424
2425 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2426 welcome, and there is no fee to participate. There is on the other
2427 hand limited space, and only room for 30 people. Please put your name
2428 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2429 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2430 </description>
2431 </item>
2432
2433 <item>
2434 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2435 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2436 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2437 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2438 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2439 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2440 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2441 time to spend on it, and it took a while to find a model I believe
2442 will do the job, but two days ago the replacement finally arrived. I
2443 ended up picking a
2444 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2445 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2446 a roaming workstation, and it seemed to work flawlessly. But my
2447 second installation with encrypted disk was not as successful. More
2448 on that below.&lt;/p&gt;
2449
2450 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2451 important requirements (robust and with a good keyboard) are never
2452 listed in the feature list. But I did get good help from the search
2453 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2454 allowed me to limit the list of interesting laptops based on my other
2455 requirements. A bit surprising that SSD disk are not disks according
2456 to that search interface, so I had to drop specifying the number of
2457 disks from my search parameters. I also asked around among friends to
2458 get their impression on keyboards and robustness.&lt;/p&gt;
2459
2460 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2461 X41. I am not quite convinced about the keyboard, as it is
2462 significantly wider than my old keyboard, and I have to stretch my
2463 hand a lot more to reach the edges. But the key response is fairly
2464 good and the individual key shape is fairly easy to handle, so I hope
2465 I will get used to it. My old X40 was starting to fail, and I really
2466 needed a new laptop now. :)&lt;/p&gt;
2467
2468 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2469 visit to the BIOS during boot it disable it.&lt;/p&gt;
2470
2471 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2472 lock up during load. And this happen when installing Debian Wheezy
2473 with encrypted disk, while the disk is being filled with random data.
2474 I also tested to install Ubuntu Raring, and it happen there too if I
2475 reenable the code to fill the disk with random data (it is disabled by
2476 default in Ubuntu). And the bug with is already known. It was
2477 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2478 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2479 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2480 kernel developers as
2481 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2482 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2483 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2484 Lenovo forums, both for
2485 &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
2486 2012-11-10&lt;/a&gt; and for
2487 &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
2488 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2489 reports state that the disk lock up during use if many writes are done
2490 on the disk, so it is much no use to work around the installation
2491 problem and end up with a computer that can lock up at any moment.
2492 There is even a
2493 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2494 available&lt;/a&gt; that will lock up the hard drive after running a few
2495 minutes by writing to a file.&lt;/p&gt;
2496
2497 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2498 contacting PCHELP Norway (request 01D1FDP) which handle support
2499 requests for Lenovo, his first suggestion was to upgrade the disk
2500 firmware. Unfortunately there is no newer firmware available from
2501 Lenovo, as my disk already have the most recent one (version LF1i). I
2502 hope to hear more from him today and hope the problem can be
2503 fixed. :)&lt;/p&gt;
2504 </description>
2505 </item>
2506
2507 <item>
2508 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2509 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2510 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2511 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2512 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2513 trusty old Thinkpad X41. Unfortunately I did not have much time to
2514 spend on it, but today the replacement finally arrived. I ended up
2515 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2516 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2517 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2518 this, it is installing what I hope will be a more final installation,
2519 with a encrypted hard drive to ensure any dope head stealing it end up
2520 with an expencive door stop.&lt;/p&gt;
2521
2522 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2523 important requirements (robust and with a good keyboard) are never
2524 listed in the feature list. But I did get good help from the search
2525 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2526 allowed me to limit the list of interesting laptops based on my other
2527 requirements. A bit surprising that SSD disk are not disks, so I had
2528 to drop number of disks from my search parameters.&lt;/p&gt;
2529
2530 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2531 wider than my old keyboard, and I have to stretch my hand a lot more
2532 to reach the edges. But the key response is fairly good and the
2533 individual key shape is fairly easy to handle, so I hope I will get
2534 used to it. My old X40 was starting to fail, and I really needed a
2535 new laptop now. :)&lt;/p&gt;
2536
2537 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2538 </description>
2539 </item>
2540
2541 <item>
2542 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2543 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2544 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2545 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2546 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2547 perfectly capable of, and I have to do it manually to get things
2548 working. One such task is to find out what firmware packages are
2549 needed to get the hardware on my computer working. Most often this
2550 affect the wifi card, but some times it even affect the RAID
2551 controller or the ethernet card. Today I pushed version 0.4 of the
2552 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2553 including a new script isenkram-autoinstall-firmware handling the
2554 process of asking all the loaded kernel modules what firmware files
2555 they want, find debian packages providing these files and install the
2556 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2557
2558 &lt;p&gt;&lt;pre&gt;
2559 # isenkram-autoinstall-firmware
2560 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2561 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2562 info: locating packages with the requested firmware files
2563 info: Updating APT sources after adding non-free APT source
2564 info: trying to install firmware-ipw2x00
2565 firmware-ipw2x00
2566 firmware-ipw2x00
2567 Preconfiguring packages ...
2568 Selecting previously deselected package firmware-ipw2x00.
2569 (Reading database ... 259727 files and directories currently installed.)
2570 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2571 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2572 #
2573 &lt;/pre&gt;&lt;/p&gt;
2574
2575 &lt;p&gt;When all the requested firmware is present, a simple message is
2576 printed instead:&lt;/p&gt;
2577
2578 &lt;p&gt;&lt;pre&gt;
2579 # isenkram-autoinstall-firmware
2580 info: did not find any firmware files requested by loaded kernel modules. exiting
2581 #
2582 &lt;/pre&gt;&lt;/p&gt;
2583
2584 &lt;p&gt;It could use some polish, but it is already working well and saving
2585 me some time when setting up new machines. :)&lt;/p&gt;
2586
2587 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2588 kernel modules, and look up each one of them using modinfo, to find
2589 the firmware files listed in the module meta-information. Next, it
2590 download the Contents file from a nearby APT mirror, and search for
2591 the firmware files in this file to locate the package with the
2592 requested firmware file. If the package is in the non-free section, a
2593 non-free APT source is added and the package is installed using
2594 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2595 machine.&lt;/p&gt;
2596
2597 &lt;p&gt;I hope someone find time to implement a more polished version of
2598 this script as part of the hw-detect debian-installer module, to
2599 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2600 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2601 firmware during a PXE install when the packages already are available
2602 from the nearby Debian mirror.&lt;/p&gt;
2603 </description>
2604 </item>
2605
2606 <item>
2607 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2608 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2609 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2610 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2611 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2612 the screen just turn black when Linux boot, either during installation
2613 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2614 last few years, but only recently understood the cause. I&#39;ve seen it
2615 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2616 The reason seem to be in the wiring of some laptops. The system to
2617 control the screen background light is inverted, so when Linux try to
2618 turn the brightness fully on, it end up turning it off instead. I do
2619 not know which Linux drivers are affected, but this post is about the
2620 i915 driver used by the
2621 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2622 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2623
2624 &lt;p&gt;The problem can be worked around two ways. Either by adding
2625 i915.invert_brightness=1 as a kernel option, or by adding a file in
2626 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2627 option when it load the i915 kernel module. On Debian and Ubuntu, it
2628 can be done by running these commands as root:&lt;/p&gt;
2629
2630 &lt;pre&gt;
2631 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2632 update-initramfs -u -k all
2633 &lt;/pre&gt;
2634
2635 &lt;p&gt;Since March 2012 there is
2636 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2637 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2638 hardware have this problem, and get the driver to invert the
2639 brightness setting automatically. To use it, one need to add a row in
2640 &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
2641 intel_quirks array&lt;/a&gt; in the driver source
2642 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2643 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2644 number (vendor number 8086 is assumed) and subdevice vendor and device
2645 number.&lt;/p&gt;
2646
2647 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2648 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2649
2650 &lt;p&gt;&lt;pre&gt;
2651 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2652 3rd Gen Core processor Graphics Controller [8086:0156] \
2653 (rev 09) (prog-if 00 [VGA controller])
2654 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2655 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2656 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2657 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2658 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2659 Latency: 0
2660 Interrupt: pin A routed to IRQ 42
2661 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2662 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2663 Region 4: I/O ports at 4000 [size=64]
2664 Expansion ROM at &lt;unassigned&gt; [disabled]
2665 Capabilities: &lt;access denied&gt;
2666 Kernel driver in use: i915
2667 &lt;/pre&gt;&lt;/p&gt;
2668
2669 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2670
2671 &lt;p&gt;&lt;pre&gt;
2672 struct intel_quirk intel_quirks[] = {
2673 ...
2674 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2675 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2676 ...
2677 }
2678 &lt;/pre&gt;&lt;/p&gt;
2679
2680 &lt;p&gt;According to the kernel module instructions (as seen using
2681 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2682 invert_brightness flag should be sent to the
2683 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2684 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2685 developers. But my email about the laptop sent 2013-06-03 have not
2686 yet shown up in
2687 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2688 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2689 emails from non-subscribers. Because of this, I sent my patch also to
2690 the Debian bug tracking system instead as
2691 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2692 sure the patch is not lost.&lt;/p&gt;
2693
2694 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2695 with this problem working properly with Linux. If you use Gnome, your
2696 worries should be over at this point. But if you use KDE, there is
2697 something in KDE ignoring the invert_brightness setting and turning on
2698 the screen during login. I&#39;ve reported it to Debian as
2699 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2700 have no idea yet how to figure out exactly what subsystem is doing
2701 this. Perhaps you can help? Perhaps you know what the Gnome
2702 developers did to handle this, and this can give a clue to the KDE
2703 developers? Or you know where in KDE the screen brightness is changed
2704 during login? If so, please update the BTS report (or get in touch if
2705 you do not know how to update BTS).&lt;/p&gt;
2706
2707 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2708 acpi_backlight=vendor, to disable ACPI backlight support completely,
2709 as the ACPI information on the machine is trash and it is better to
2710 leave it to the intel video driver to control the screen
2711 backlight.&lt;/p&gt;
2712 </description>
2713 </item>
2714
2715 <item>
2716 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2717 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2718 <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>
2719 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2720 <description>&lt;p&gt;Two days ago, I asked
2721 &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
2722 I could install Linux on a Packard Bell EasyNote LV computer
2723 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2724 with the obstacles put in the way of Linux users on a laptop with UEFI
2725 and Windows 8.&lt;/p&gt;
2726
2727 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2728 secure booting or fast boot. I suspect fast boot was the problem,
2729 causing the firmware to boot directly from HD without considering any
2730 key presses and alternative devices, but do not know UEFI settings
2731 enough to tell.&lt;/p&gt;
2732
2733 &lt;p&gt;There is no way to install Linux on the machine in question without
2734 opening the box and disconnecting the hard drive! This is as far as I
2735 can tell, the only way to get access to the firmware setup menu
2736 without accepting the Windows 8 license agreement. I am told (and
2737 found description on how to) that it is possible to configure the
2738 firmware setup once booted into Windows 8. But as I believe the terms
2739 of that agreement are completely unacceptable, accepting the license
2740 was never an alternative. I do not enter agreements I do not intend
2741 to follow.&lt;/p&gt;
2742
2743 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2744 waste many hours on this, but luckily there was a way to get it to
2745 work. But I would not recommend it to anyone planning to run Linux on
2746 it, and I have become sceptical to Windows 8 certified laptops. Is
2747 this the way Linux will be forced out of the market place, by making
2748 it close to impossible for &quot;normal&quot; users to install Linux without
2749 accepting the Microsoft Windows license terms? Or at least not
2750 without risking to loose the warranty?&lt;/p&gt;
2751
2752 &lt;p&gt;I&#39;ve updated the
2753 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2754 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2755 do not have to struggle as much as I did to get Linux into the
2756 machine.&lt;/p&gt;
2757
2758 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2759 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2760 </description>
2761 </item>
2762
2763 <item>
2764 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2765 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2766 <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>
2767 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2768 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2769 new laptops for my parents and a few others. I bought Packard Bell
2770 Easynote LV to run Kubuntu on and use as their home computer. But I
2771 am completely unable to figure out how to install Linux on it. The
2772 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2773 instead of a BIOS to boot.&lt;/p&gt;
2774
2775 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
2776 to get it to boot the Linux installer from my USB stick. I have yet
2777 to try the DVD install, and still hope it will work. when I turn on
2778 the computer, there is no information on what buttons to press to get
2779 the normal boot menu. I expect to get some boot menu to select PXE or
2780 USB stick booting. When booting, it first ask for the language to
2781 use, then for some regional settings, and finally if I will accept the
2782 Windows 8 terms of use. As these terms are completely unacceptable to
2783 me, I have no other choice but to turn off the computer and try again
2784 to get it to boot the Linux installer.&lt;/p&gt;
2785
2786 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
2787 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2788 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
2789 installed on this machine, please get in touch or update that wiki
2790 page. If I can&#39;t find a way to install Linux, I will have to return
2791 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
2792
2793 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
2794 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
2795 on new Laptops?&lt;/p&gt;
2796 </description>
2797 </item>
2798
2799 <item>
2800 <title>How to transform a Debian based system to a Debian Edu installation</title>
2801 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
2802 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
2803 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
2804 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
2805 an operating system based on Debian intended for use in schools. It
2806 contain a turn-key solution for the computer network provided to
2807 pupils in the primary schools. It provide both the central server,
2808 network boot servers and desktop environments with heaps of
2809 educational software. The project was founded almost 12 years ago,
2810 2001-07-02. If you want to support the project, which is in need for
2811 cash to fund developer gatherings and other project related activity,
2812 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
2813 donate some money&lt;/a&gt;.
2814
2815 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
2816 lists and elsewhere, is the question on how to transform a Debian or
2817 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
2818 hard, and last week I wrote a script to replicate the steps done by
2819 the Debian Edu installer.&lt;/p&gt;
2820
2821 &lt;p&gt;The script,
2822 &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;
2823 in the debian-edu-config package, will go through these six steps and
2824 transform an existing Debian Wheezy or Ubuntu (untested) installation
2825 into a Debian Edu Workstation:&lt;/p&gt;
2826
2827 &lt;ol&gt;
2828
2829 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
2830 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
2831 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
2832 our configuration.&lt;/li&gt;
2833 &lt;li&gt;Preseed debconf database with profile setup in
2834 /etc/debian-edu/config, and run tasksel to install packages
2835 according to the profile specified in the config above,
2836 overriding some of the Debian automation machinery.&lt;/li&gt;
2837 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
2838 that could not be done using preseeding.&lt;/li&gt;
2839 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
2840
2841 &lt;/ol&gt;
2842
2843 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
2844 replicated like this. Disk partitioning and LVM setup, for example.
2845 So this script just assume there is enough disk space to install all
2846 the needed packages.&lt;/p&gt;
2847
2848 &lt;p&gt;The script was created to help a Debian Edu student working on
2849 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
2850 Debian Edu client, and using it he can take the existing
2851 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
2852 transform it into a fully functioning Debian Edu Workstation (or
2853 Roaming Workstation, or whatever :).&lt;/p&gt;
2854
2855 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
2856 If a LXDE based Roaming workstation is wanted instead, modify the
2857 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
2858
2859 &lt;p&gt;&lt;pre&gt;
2860 PROFILE=&quot;Roaming-Workstation&quot;
2861 DESKTOP=&quot;lxde&quot;
2862 &lt;/pre&gt;&lt;/p&gt;
2863
2864 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
2865 the cloud, by starting with a virtual Debian installation at some
2866 virtual hosting service and setting up all the services on first
2867 boot.&lt;/p&gt;
2868 </description>
2869 </item>
2870
2871 <item>
2872 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
2873 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
2874 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
2875 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
2876 <description>&lt;P&gt;In January,
2877 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
2878 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
2879 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
2880 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
2881 marvellous construction system from Denmark. We also created
2882 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
2883 a place to take notes and write down our plans and hopes. And several
2884 people showed up to help. I was very happy to see the effect of my
2885 call. Since the small start, we have a debtags tag
2886 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
2887 tag for LEGO related packages, and now count 10 packages related to
2888 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
2889
2890 &lt;p&gt;&lt;table&gt;
2891 &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;
2892 &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;
2893 &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;
2894 &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;
2895 &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;
2896 &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;
2897 &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;
2898 &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;
2899 &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;
2900 &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;
2901 &lt;/table&gt;&lt;/p&gt;
2902
2903 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2904 currently available in Jessie/testing. leocad is so far only
2905 available in experimental.&lt;/p&gt;
2906
2907 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
2908 adding the rest of the great free software tools available on Linux
2909 for LEGO designers.&lt;/p&gt;
2910 </description>
2911 </item>
2912
2913 <item>
2914 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
2915 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
2916 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
2917 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
2918 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
2919 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
2920 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
2921 Debian release, and I expect to move my machines at home over to it fairly
2922 soon.&lt;/p&gt;
2923
2924 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
2925 in particular make me very happy to see included. The
2926 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
2927 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
2928 included for the first time. Alongside similar programs like
2929 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
2930 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
2931 it allow for visual programming where syntax errors can not happen,
2932 and a friendly programming environment for learning to control the
2933 computer. Scratch will also be included in the next release of Debian
2934 Edu.&lt;/a&gt;
2935
2936 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
2937 Edu/Skolelinux release too. The
2938 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
2939 alpha release&lt;/a&gt; went out last week, and the next should soon
2940 follow.&lt;p&gt;
2941 </description>
2942 </item>
2943
2944 <item>
2945 <title>Isenkram 0.2 finally in the Debian archive</title>
2946 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
2947 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
2948 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
2949 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
2950 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
2951 for many months. I uploaded it to the Debian experimental suite
2952 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
2953
2954 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
2955 install to work with a pluggable hardware device. The suggestion pop
2956 up when the device is plugged in. For example if a Lego Mindstorm NXT
2957 is inserted, it will suggest to install the program needed to program
2958 the NXT controller. Give it a go, and report bugs and suggestions to
2959 BTS. :)&lt;/p&gt;
2960 </description>
2961 </item>
2962
2963 <item>
2964 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
2965 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
2966 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
2967 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
2968 <description>&lt;p&gt;My
2969 &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
2970 bitcoin related blog post&lt;/a&gt; mentioned that the new
2971 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
2972 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2973 2013-01-19, and have been available in unstable since then. It was
2974 automatically copied to Ubuntu, and is available in their Raring
2975 version too.&lt;/p&gt;
2976
2977 &lt;p&gt;But there is a strange problem with the build that block this new
2978 version from being available on the i386 and kfreebsd-i386
2979 architectures. For some strange reason, the autobuilders in Debian
2980 for these architectures fail to run the test suite on these
2981 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
2982 We are so far unable to reproduce it when building it manually, and
2983 no-one have been able to propose a fix. If you got an idea what is
2984 failing, please let us know via the BTS.&lt;/p&gt;
2985
2986 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
2987 I often run low on disk space, is the fact that the client will exit
2988 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
2989 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
2990 it. :)&lt;/p&gt;
2991
2992 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
2993 activities, please send Bitcoin donations to my address
2994 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2995 </description>
2996 </item>
2997
2998 <item>
2999 <title>Welcome to the world, Isenkram!</title>
3000 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3001 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3002 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3003 <description>&lt;p&gt;Yesterday, I
3004 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3005 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3006 pluggable hardware devices, which I
3007 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3008 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3009 up, and caused me to really want to to open up the development to more
3010 people. But before I did this, I want to come up with a sensible name
3011 for this project. Today I finally decided on a new name, and I have
3012 renamed the project from hw-support-handler to this new name. In the
3013 process, I moved the source to git and made it available as a
3014 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3015 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3016 To fetch and build the latest version of the source, use&lt;/p&gt;
3017
3018 &lt;pre&gt;
3019 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3020 cd isenkram &amp;&amp; git-buildpackage -us -uc
3021 &lt;/pre&gt;
3022
3023 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3024 want to hack on the source or improve the package, please go ahead.
3025 But please talk to me first on IRC or via email before you do major
3026 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3027
3028 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3029 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3030 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3031 the German word eisenkram, for those that are familiar with that
3032 word.&lt;/p&gt;
3033
3034 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3035 instructions, to avoid confusing people with an error from the signing
3036 process.&lt;/p&gt;
3037
3038 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3039 clone argument to avoid the need for authentication.&lt;/p&gt;
3040 </description>
3041 </item>
3042
3043 <item>
3044 <title>First prototype ready making hardware easier to use in Debian</title>
3045 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3047 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3048 <description>&lt;p&gt;Early this month I set out to try to
3049 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3050 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3051 prototype is working, and it is ready for a larger audience. To test
3052 it, fetch the
3053 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3054 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3055 package. You might have to log out and in again activate the
3056 autostart script.&lt;/p&gt;
3057
3058 &lt;p&gt;The design is simple:&lt;/p&gt;
3059
3060 &lt;ul&gt;
3061
3062 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3063 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3064
3065 &lt;li&gt;This program listen for kernel events about new hardware (directly
3066 from the kernel like udev does), not using HAL dbus events as I
3067 initially did.&lt;/li&gt;
3068
3069 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3070 the APT database, a database
3071 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3072 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3073
3074 &lt;li&gt;If a package is mapped to the hardware in question, the package
3075 isn&#39;t installed yet and this is the first time the hardware was
3076 plugged in, show a desktop notification suggesting to install the
3077 package or packages.&lt;/li&gt;
3078
3079 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3080 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3081
3082 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3083 package while showing progress information in a window.&lt;/li&gt;
3084
3085 &lt;/ul&gt;
3086
3087 &lt;p&gt;I still need to come up with a better name for the system. Here
3088 are some screen shots showing the prototype in action. First the
3089 notification, then the password request, and finally the request to
3090 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3091
3092 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3093 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3094 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3095 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3096 &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;
3097
3098 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3099 is already useful. The database of hardware to package mappings also
3100 need more work. It is currently compatible with the Ubuntu way of
3101 storing such information in the package control file, but could be
3102 changed to use other formats instead or in addition to the current
3103 method. I&#39;ve dropped the use of discover for this mapping, as the
3104 modalias approach is more flexible and easier to use on Linux as long
3105 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3106
3107 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3108 here is the command required to check out and build the source: Use
3109 &#39;&lt;tt&gt;svn checkout
3110 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3111 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3112 devscripts package.&lt;/p&gt;
3113
3114 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3115 renamed to Isenkram and the source moved from the Debian Edu
3116 subversion repository to a Debian collab-maint git repository. See
3117 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3118 instructions&lt;/a&gt; for details.&lt;/p&gt;
3119 </description>
3120 </item>
3121
3122 <item>
3123 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3124 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3125 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3126 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3127 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3128 suddenly in bed. With a quiet whimper, it went completely quiet and
3129 black. The power button was no longer able to turn it on. It was a
3130 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3131 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3132 Compaq I had before that. Now I need to find a replacement. To keep
3133 going during Christmas, I moved the one year old SSD disk to my old
3134 X40 where it fitted (only one I had left that could use it), but it is
3135 not a durable solution.
3136
3137 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3138 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3139
3140 &lt;ul&gt;
3141
3142 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3143 than A4).&lt;/li&gt;
3144 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3145 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3146 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3147 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3148 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3149 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3150 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3151 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3152 size).&lt;/li&gt;
3153 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3154 X.org packages.&lt;/li&gt;
3155 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3156 the time).
3157
3158 &lt;/ul&gt;
3159
3160 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3161 list. The reason is simply that the specifications on laptops the
3162 last 10-15 years have been sufficient for my needs, and I have to look
3163 at other features to choose my laptop. But are there still made as
3164 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3165 robust, and Thinkpads seem to be heading in the wrong direction since
3166 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3167 still be useful.&lt;/p&gt;
3168
3169 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3170 external keyboard? I&#39;ll have to check the
3171 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3172 well-supported laptops, or perhaps just buy one preinstalled from one
3173 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3174 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3175 </description>
3176 </item>
3177
3178 <item>
3179 <title>How to find a browser plugin supporting a given MIME type</title>
3180 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3181 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3182 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3183 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3184 install to get support for a given MIME type. Thanks to
3185 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3186 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3187 Unfortunately, not very many packages provide the needed meta
3188 information, Anyway, here is a small script to look up all browser
3189 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3190
3191 &lt;pre&gt;
3192 #!/usr/bin/python
3193 import sys
3194 import apt
3195 def pkgs_handling_mimetype(mimetype):
3196 cache = apt.Cache()
3197 cache.open(None)
3198 thepkgs = []
3199 for pkg in cache:
3200 version = pkg.candidate
3201 if version is None:
3202 version = pkg.installed
3203 if version is None:
3204 continue
3205 record = version.record
3206 if not record.has_key(&#39;Npp-MimeType&#39;):
3207 continue
3208 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3209 for t in mime_types:
3210 t = t.rstrip().strip()
3211 if t == mimetype:
3212 thepkgs.append(pkg.name)
3213 return thepkgs
3214 mimetype = &quot;audio/ogg&quot;
3215 if 1 &lt; len(sys.argv):
3216 mimetype = sys.argv[1]
3217 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3218 for pkg in pkgs_handling_mimetype(mimetype):
3219 print &quot; %s&quot; %pkg
3220 &lt;/pre&gt;
3221
3222 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3223
3224 &lt;pre&gt;
3225 % ./apt-find-browserplug-for-mimetype
3226 Browser plugin packages supporting audio/ogg:
3227 gecko-mediaplayer
3228 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3229 Browser plugin packages supporting application/x-shockwave-flash:
3230 browser-plugin-gnash
3231 %
3232 &lt;/pre&gt;
3233
3234 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3235 itself to query for plugins and propose to install the needed
3236 packages. It would be great if Debian supported such feature too. Is
3237 anyone working on adding it?&lt;/p&gt;
3238
3239 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3240 request for icweasel support for this feature is
3241 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3242 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3243 of manpower and wish for a different design is the reason thus feature
3244 is not yet in iceweasel from Debian.&lt;/p&gt;
3245 </description>
3246 </item>
3247
3248 <item>
3249 <title>What is the most supported MIME type in Debian?</title>
3250 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3251 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3252 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3253 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3254 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3255 proposal to make it possible for a Desktop application to propose to
3256 the user some package to install to gain support for a given MIME
3257 type, font, library etc. that is currently missing. With such
3258 mechanism in place, it would be possible for the desktop to
3259 automatically propose and install leocad if some LDraw file is
3260 downloaded by the browser.&lt;/p&gt;
3261
3262 &lt;p&gt;To get some idea about the current content of the archive, I decided
3263 to write a simple program to extract all .desktop files from the
3264 Debian archive and look up the claimed MIME support there. The result
3265 can be found on the
3266 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3267 site&lt;/a&gt;. Using the collected information, it become possible to
3268 answer the question in the title. Here are the 20 most supported MIME
3269 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3270 The complete list is available from the link above.&lt;/p&gt;
3271
3272 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3273
3274 &lt;pre&gt;
3275 count MIME type
3276 ----- -----------------------
3277 32 text/plain
3278 30 audio/mpeg
3279 29 image/png
3280 28 image/jpeg
3281 27 application/ogg
3282 26 audio/x-mp3
3283 25 image/tiff
3284 25 image/gif
3285 22 image/bmp
3286 22 audio/x-wav
3287 20 audio/x-flac
3288 19 audio/x-mpegurl
3289 18 video/x-ms-asf
3290 18 audio/x-musepack
3291 18 audio/x-mpeg
3292 18 application/x-ogg
3293 17 video/mpeg
3294 17 audio/x-scpls
3295 17 audio/ogg
3296 16 video/x-ms-wmv
3297 &lt;/pre&gt;
3298
3299 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3300
3301 &lt;pre&gt;
3302 count MIME type
3303 ----- -----------------------
3304 33 text/plain
3305 32 image/png
3306 32 image/jpeg
3307 29 audio/mpeg
3308 27 image/gif
3309 26 image/tiff
3310 26 application/ogg
3311 25 audio/x-mp3
3312 22 image/bmp
3313 21 audio/x-wav
3314 19 audio/x-mpegurl
3315 19 audio/x-mpeg
3316 18 video/mpeg
3317 18 audio/x-scpls
3318 18 audio/x-flac
3319 18 application/x-ogg
3320 17 video/x-ms-asf
3321 17 text/html
3322 17 audio/x-musepack
3323 16 image/x-xbitmap
3324 &lt;/pre&gt;
3325
3326 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3327
3328 &lt;pre&gt;
3329 count MIME type
3330 ----- -----------------------
3331 31 text/plain
3332 31 image/png
3333 31 image/jpeg
3334 29 audio/mpeg
3335 28 application/ogg
3336 27 image/gif
3337 26 image/tiff
3338 26 audio/x-mp3
3339 23 audio/x-wav
3340 22 image/bmp
3341 21 audio/x-flac
3342 20 audio/x-mpegurl
3343 19 audio/x-mpeg
3344 18 video/x-ms-asf
3345 18 video/mpeg
3346 18 audio/x-scpls
3347 18 application/x-ogg
3348 17 audio/x-musepack
3349 16 video/x-ms-wmv
3350 16 video/x-msvideo
3351 &lt;/pre&gt;
3352
3353 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3354 information mentioned in DEP-11. I have not yet had time to look at
3355 it, but hope the PackageKit people in Debian are on top of these
3356 issues.&lt;/p&gt;
3357
3358 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3359 discovering a typo in my script.&lt;/p&gt;
3360 </description>
3361 </item>
3362
3363 <item>
3364 <title>Using modalias info to find packages handling my hardware</title>
3365 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3366 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3367 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3368 <description>&lt;p&gt;Yesterday, I wrote about the
3369 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3370 values provided by the Linux kernel&lt;/a&gt; following my hope for
3371 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3372 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3373 modalias values attached to package names can be used to map packages
3374 to hardware. This allow the system to look up and suggest relevant
3375 packages when I plug in some new hardware into my machine, and replace
3376 discover and discover-data as the database used to map hardware to
3377 packages.&lt;/p&gt;
3378
3379 &lt;p&gt;I create a modaliases file with entries like the following,
3380 containing package name, kernel module name (if relevant, otherwise
3381 the package name) and globs matching the relevant hardware
3382 modalias.&lt;/p&gt;
3383
3384 &lt;p&gt;&lt;blockquote&gt;
3385 Package: package-name
3386 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3387 &lt;/blockquote&gt;&lt;/p&gt;
3388
3389 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3390 for a given modalias value using this file.&lt;/p&gt;
3391
3392 &lt;p&gt;An entry like this would suggest the video and picture application
3393 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3394
3395 &lt;p&gt;&lt;blockquote&gt;
3396 Package: cheese
3397 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3398 &lt;/blockquote&gt;&lt;/p&gt;
3399
3400 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3401 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3402
3403 &lt;p&gt;&lt;blockquote&gt;
3404 Package: pcmciautils
3405 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3406 &lt;/blockquote&gt;&lt;/p&gt;
3407
3408 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3409 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3410
3411 &lt;p&gt;&lt;blockquote&gt;
3412 Package: colorhug-client
3413 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3414 &lt;/blockquote&gt;&lt;/p&gt;
3415
3416 &lt;p&gt;I believe the format is compatible with the format of the Packages
3417 file in the Debian archive. Ubuntu already uses their Packages file
3418 to store their mappings from packages to hardware.&lt;/p&gt;
3419
3420 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3421 announce the hardware it support in a way my prototype understand.
3422 This allow those publishing packages in an APT source outside the
3423 Debian archive as well as those backporting packages to make sure the
3424 hardware mapping are included in the package meta information. I&#39;ve
3425 tested such header in the pymissile package, and its modalias mapping
3426 is working as it should with my prototype. It even made it to Ubuntu
3427 Raring.&lt;/p&gt;
3428
3429 &lt;p&gt;To test if it was possible to look up supported hardware using only
3430 the shell tools available in the Debian installer, I wrote a shell
3431 implementation of the lookup code. The idea is to create files for
3432 each modalias and let the shell do the matching. Please check out and
3433 try the
3434 &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;
3435 shell script. It run without any extra dependencies and fetch the
3436 hardware mappings from the Debian archive and the subversion
3437 repository where I currently work on my prototype.&lt;/p&gt;
3438
3439 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3440 install yubikey-personalization:&lt;/p&gt;
3441
3442 &lt;p&gt;&lt;blockquote&gt;
3443 % ./hw-support-lookup
3444 &lt;br&gt;yubikey-personalization
3445 &lt;br&gt;%
3446 &lt;/blockquote&gt;&lt;/p&gt;
3447
3448 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3449 propose to install the pcmciautils package:&lt;/p&gt;
3450
3451 &lt;p&gt;&lt;blockquote&gt;
3452 % ./hw-support-lookup
3453 &lt;br&gt;pcmciautils
3454 &lt;br&gt;%
3455 &lt;/blockquote&gt;&lt;/p&gt;
3456
3457 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3458 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3459 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3460
3461 &lt;p&gt;It could be possible to generate several of the mappings between
3462 packages and hardware. One source would be to look at packages with
3463 kernel modules, ie packages with *.ko files in /lib/modules/, and
3464 extract their modalias information. Another would be to look at
3465 packages with udev rules, ie packages with files in
3466 /lib/udev/rules.d/, and extract their vendor/model information to
3467 generate a modalias matching rule. I have not tested any of these to
3468 see if it work.&lt;/p&gt;
3469
3470 &lt;p&gt;If you want to help implementing a system to let us propose what
3471 packages to install when new hardware is plugged into a Debian
3472 machine, please send me an email or talk to me on
3473 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3474 </description>
3475 </item>
3476
3477 <item>
3478 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3479 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3480 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3481 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3482 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3483 information, to find the packages that support a given piece of
3484 hardware, I refreshed my memory regarding modalias values, and decided
3485 to document the details. Here are my findings so far, also available
3486 in
3487 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3488 Debian Edu subversion repository&lt;/a&gt;:
3489
3490 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3491
3492 &lt;p&gt;This document try to explain what the different types of modalias
3493 values stands for. It is in part based on information from
3494 &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;,
3495 &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;,
3496 &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
3497 &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;.
3498
3499 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3500 this shell script:&lt;/p&gt;
3501
3502 &lt;pre&gt;
3503 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3504 &lt;/pre&gt;
3505
3506 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3507 using modinfo:&lt;/p&gt;
3508
3509 &lt;pre&gt;
3510 % /sbin/modinfo psmouse | grep alias:
3511 alias: serio:ty05pr*id*ex*
3512 alias: serio:ty01pr*id*ex*
3513 %
3514 &lt;/pre&gt;
3515
3516 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3517
3518 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3519 Bridge memory controller:&lt;/p&gt;
3520
3521 &lt;p&gt;&lt;blockquote&gt;
3522 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3523 &lt;/blockquote&gt;&lt;/p&gt;
3524
3525 &lt;p&gt;This represent these values:&lt;/p&gt;
3526
3527 &lt;pre&gt;
3528 v 00008086 (vendor)
3529 d 00002770 (device)
3530 sv 00001028 (subvendor)
3531 sd 000001AD (subdevice)
3532 bc 06 (bus class)
3533 sc 00 (bus subclass)
3534 i 00 (interface)
3535 &lt;/pre&gt;
3536
3537 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3538 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3539 0600. The 0600 class is a host bridge. Other useful bus values are
3540 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3541
3542 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3543 means.&lt;/p&gt;
3544
3545 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3546
3547 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3548 USB hub in a laptop:&lt;/p&gt;
3549
3550 &lt;p&gt;&lt;blockquote&gt;
3551 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3552 &lt;/blockquote&gt;&lt;/p&gt;
3553
3554 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3555
3556 &lt;pre&gt;
3557 v 1D6B (device vendor)
3558 p 0001 (device product)
3559 d 0206 (bcddevice)
3560 dc 09 (device class)
3561 dsc 00 (device subclass)
3562 dp 00 (device protocol)
3563 ic 09 (interface class)
3564 isc 00 (interface subclass)
3565 ip 00 (interface protocol)
3566 &lt;/pre&gt;
3567
3568 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3569 class is in the interface class section. For a simple USB web camera,
3570 these alias entries show up:&lt;/p&gt;
3571
3572 &lt;p&gt;&lt;blockquote&gt;
3573 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3574 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3575 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3576 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3577 &lt;/blockquote&gt;&lt;/p&gt;
3578
3579 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3580 camera), 0101 is audio control device and 0102 is audio streaming (aka
3581 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3582
3583 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3584
3585 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3586 receiver in a Thinkpad X40:&lt;/p&gt;
3587
3588 &lt;p&gt;&lt;blockquote&gt;
3589 acpi:IBM0071:PNP0511:
3590 &lt;/blockquote&gt;&lt;/p&gt;
3591
3592 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3593
3594 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3595
3596 &lt;p&gt;The DMI table contain lots of information about the computer case
3597 and model. This is an entry for a IBM Thinkpad X40, fetched from
3598 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3599
3600 &lt;p&gt;&lt;blockquote&gt;
3601 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3602 &lt;/blockquote&gt;&lt;/p&gt;
3603
3604 &lt;p&gt;The values present are&lt;/p&gt;
3605
3606 &lt;pre&gt;
3607 bvn IBM (BIOS vendor)
3608 bvr 1UETB6WW(1.66) (BIOS version)
3609 bd 06/15/2005 (BIOS date)
3610 svn IBM (system vendor)
3611 pn 2371H4G (product name)
3612 pvr ThinkPadX40 (product version)
3613 rvn IBM (board vendor)
3614 rn 2371H4G (board name)
3615 rvr NotAvailable (board version)
3616 cvn IBM (chassis vendor)
3617 ct 10 (chassis type)
3618 cvr NotAvailable (chassis version)
3619 &lt;/pre&gt;
3620
3621 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3622 found in the dmidecode source:&lt;/p&gt;
3623
3624 &lt;pre&gt;
3625 3 Desktop
3626 4 Low Profile Desktop
3627 5 Pizza Box
3628 6 Mini Tower
3629 7 Tower
3630 8 Portable
3631 9 Laptop
3632 10 Notebook
3633 11 Hand Held
3634 12 Docking Station
3635 13 All In One
3636 14 Sub Notebook
3637 15 Space-saving
3638 16 Lunch Box
3639 17 Main Server Chassis
3640 18 Expansion Chassis
3641 19 Sub Chassis
3642 20 Bus Expansion Chassis
3643 21 Peripheral Chassis
3644 22 RAID Chassis
3645 23 Rack Mount Chassis
3646 24 Sealed-case PC
3647 25 Multi-system
3648 26 CompactPCI
3649 27 AdvancedTCA
3650 28 Blade
3651 29 Blade Enclosing
3652 &lt;/pre&gt;
3653
3654 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3655 table. For example my home server is a tower, but the DMI modalias
3656 claim it is a desktop.&lt;/p&gt;
3657
3658 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3659
3660 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3661 test machine:&lt;/p&gt;
3662
3663 &lt;p&gt;&lt;blockquote&gt;
3664 serio:ty01pr00id00ex00
3665 &lt;/blockquote&gt;&lt;/p&gt;
3666
3667 &lt;p&gt;The values present are&lt;/p&gt;
3668
3669 &lt;pre&gt;
3670 ty 01 (type)
3671 pr 00 (prototype)
3672 id 00 (id)
3673 ex 00 (extra)
3674 &lt;/pre&gt;
3675
3676 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3677 the valid values are.&lt;/p&gt;
3678
3679 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3680
3681 &lt;p&gt;There are heaps of other modalias subtypes according to
3682 file2alias.c. There is the rest of the list from that source: amba,
3683 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3684 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3685 vmbus, x86cpu and zorro. I did not spend time documenting all of
3686 these, as they do not seem relevant for my intended use with mapping
3687 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3688
3689 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3690
3691 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3692 one can use the following shell script:&lt;/p&gt;
3693
3694 &lt;pre&gt;
3695 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3696 echo &quot;$id&quot; ; \
3697 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3698 done
3699 &lt;/pre&gt;
3700
3701 &lt;p&gt;The output can look like this (only the first few entries as the
3702 list is very long on my test machine):&lt;/p&gt;
3703
3704 &lt;pre&gt;
3705 acpi:ACPI0003:
3706 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3707 acpi:device:
3708 FATAL: Module acpi:device: not found.
3709 acpi:IBM0068:
3710 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3711 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3712 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3713 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3714 acpi:IBM0071:PNP0511:
3715 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3716 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3717 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3718 [...]
3719 &lt;/pre&gt;
3720
3721 &lt;p&gt;If you want to help implementing a system to let us propose what
3722 packages to install when new hardware is plugged into a Debian
3723 machine, please send me an email or talk to me on
3724 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3725
3726 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3727 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3728 in /sys/ with space in them.&lt;/p&gt;
3729 </description>
3730 </item>
3731
3732 <item>
3733 <title>Moved the pymissile Debian packaging to collab-maint</title>
3734 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3735 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3736 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3737 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3738 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3739 Launcher and updated the Debian package
3740 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3741 sure udev will fix the device permissions when it is plugged in. I
3742 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3743 hopefully make the package be proposed by jockey in Ubuntu when a user
3744 plug in his rocket launcher. In the process I moved the source to a
3745 git repository under collab-maint, to make it easier for any DD to
3746 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3747 is not very active, but the software still work for me even after five
3748 years of relative silence. The new git repository is not listed in
3749 the uploaded package yet, because I want to test the other changes a
3750 bit more before I upload the new version. If you want to check out
3751 the new version with a .desktop file included, visit the
3752 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3753 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3754 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3755 </description>
3756 </item>
3757
3758 <item>
3759 <title>Lets make hardware dongles easier to use in Debian</title>
3760 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3761 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3762 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3763 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3764 general, is that there is a great package management system with the
3765 ability to automatically install software packages by downloading them
3766 from the distribution mirrors, but no way to get it to automatically
3767 install the packages I need to use the hardware I plug into my
3768 machine. Even if the package to use it is easily available from the
3769 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3770 suggest to automatically install the python-nxt, nbc and t2n packages
3771 I need to talk to it. When I plug in a Yubikey, it could propose the
3772 yubikey-personalization package. The information required to do this
3773 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3774
3775 &lt;p&gt;Some years ago, I proposed to
3776 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
3777 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
3778 simple:
3779
3780 &lt;ul&gt;
3781
3782 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
3783 starting when a user log in.&lt;/li&gt;
3784
3785 &lt;li&gt;Set this program up to listen for kernel events emitted when new
3786 hardware is inserted into the computer.&lt;/li&gt;
3787
3788 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
3789 database mapping to packages, and take note of any non-installed
3790 packages.&lt;/li&gt;
3791
3792 &lt;li&gt;Show a message to the user proposing to install the discovered
3793 package, and make it easy to install it.&lt;/li&gt;
3794
3795 &lt;/ul&gt;
3796
3797 &lt;p&gt;I am not sure what the best way to implement this is, but my
3798 initial idea was to use dbus events to discover new hardware, the
3799 discover database to find packages and
3800 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
3801 packages.&lt;/p&gt;
3802
3803 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
3804 draft package is now checked into
3805 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3806 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
3807 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
3808 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3809 the relevant packages in Debian, and uploaded a new version
3810 2.2013.01.09 to unstable. I also discovered that the current
3811 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
3812 package in Debian no longer discovered any USB devices, because
3813 /proc/bus/usb/devices is no longer present. I ported it to use
3814 libusb as a fall back option to get it working. The fixed package
3815 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
3816 because of the freeze).&lt;/p&gt;
3817
3818 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
3819 desktop notification to show up (only once, the first time it is
3820 inserted):&lt;/p&gt;
3821
3822 &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;
3823
3824 &lt;p&gt;For this prototype to be really useful, some way to automatically
3825 install the proposed packages by pressing the &quot;Please install
3826 program(s)&quot; button should to be implemented.&lt;/p&gt;
3827
3828 &lt;p&gt;If this idea seem useful to you, and you want to help make it
3829 happen, please help me update the discover-data database with mappings
3830 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
3831 list the package you would like to have installed when a given
3832 hardware device is inserted into your computer, and report bugs using
3833 reportbug if it isn&#39;t. Or, if you know of a better way to provide
3834 such mapping, please let me know.&lt;/p&gt;
3835
3836 &lt;p&gt;This prototype need more work, and there are several questions that
3837 should be considered before it is ready for production use. Is dbus
3838 the correct way to detect new hardware? At the moment I look for HAL
3839 dbus events on the system bus, because that is the events I could see
3840 on my Debian Squeeze KDE desktop. Are there better events to use?
3841 How should the user be notified? Is the desktop notification
3842 mechanism the best option, or should the background daemon raise a
3843 popup instead? How should packages be installed? When should they
3844 not be installed?&lt;/p&gt;
3845
3846 &lt;p&gt;If you want to help getting such feature implemented in Debian,
3847 please send me an email. :)&lt;/p&gt;
3848 </description>
3849 </item>
3850
3851 <item>
3852 <title>New IRC channel for LEGO designers using Debian</title>
3853 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
3854 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
3855 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
3856 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
3857 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
3858 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
3859 discovered I had to build all the tools myself because none were
3860 already in Debian Squeeze. If Debian support for LEGO is something
3861 you care about, please join me on the IRC channel
3862 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
3863 irc.debian.org). There is a lot that could be done to improve the
3864 Debian support for LEGO designers. For example both CAD software
3865 and Mindstorm compilers are missing. :)&lt;/p&gt;
3866
3867 &lt;p&gt;Update 2012-01-03: A
3868 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
3869 including links to Lego related packages is now available.&lt;/p&gt;
3870 </description>
3871 </item>
3872
3873 <item>
3874 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
3875 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
3876 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
3877 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
3878 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
3879 year! I hope next year will prove to be a good year.&lt;/p&gt;
3880
3881 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
3882 decentralised &quot;currency&quot; that allow people to transfer bitcoins
3883 between each other with minimal overhead, is a very interesting
3884 experiment. And as I wrote a few days ago, the bitcoin situation in
3885 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
3886 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
3887 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
3888 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
3889 for one of the ftpmasters to approve the new bitcoin-qt package
3890 name.&lt;/p&gt;
3891
3892 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3893 team in Debian, you can easily test the package in Debian Squeeze
3894 using the following steps to get a set of working packages:&lt;/p&gt;
3895
3896 &lt;blockquote&gt;&lt;pre&gt;
3897 git clone git://git.debian.org/git/collab-maint/bitcoin
3898 cd bitcoin
3899 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3900 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3901 &lt;/pre&gt;&lt;/blockquote&gt;
3902
3903 &lt;p&gt;You might have to install some build dependencies as well. The
3904 list of commands should give you two packages, bitcoind and
3905 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3906 client will download the complete set of bitcoin &quot;blocks&quot;, which need
3907 around 5.6 GiB of data on my machine at the moment. Make sure your
3908 ~/.bitcoin/ directory have lots of spare room if you want to download
3909 all the blocks. The client will warn if the disk is getting full, so
3910 there is not really a problem if you got too little room, but you will
3911 not be able to get all the features out of the client.&lt;/p&gt;
3912
3913 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3914 activities, please send Bitcoin donations to my address
3915 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3916 </description>
3917 </item>
3918
3919 <item>
3920 <title>A word on bitcoin support in Debian</title>
3921 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
3922 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
3923 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
3924 <description>&lt;p&gt;It has been a while since I wrote about
3925 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
3926 peer-to-peer based crypto-currency, and the reason is simply that I
3927 have been busy elsewhere. But two days ago, I started looking at the
3928 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
3929 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
3930 is now maintained by a
3931 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
3932 people&lt;/a&gt;, and the grunt work had already been done by this team. We
3933 owe a huge thank you to all these team members. :)
3934 But I was sad to discover that the bitcoin client is missing in
3935 Wheezy. It is only available in Sid (and an outdated client from
3936 backports). The client had several RC bugs registered in BTS blocking
3937 it from entering testing. To try to help the team and improve the
3938 situation, I spent some time providing patches and triaging the bug
3939 reports. I also had a look at the bitcoin package available from Matt
3940 Corallo in a
3941 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
3942 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
3943 Debian package.&lt;/p&gt;
3944
3945 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
3946 IRC, I pushed several patches into the collab-maint git repository to
3947 improve the package. It now contains fixes for the RC issues (not from
3948 me, but fixed by Scott Howard), build rules for a Qt GUI client
3949 package, konqueror support for the bitcoin: URI and bash completion
3950 setup. As I work on Debian Squeeze, I also created
3951 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
3952 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
3953 it and try to integrate it into the git repository before uploading a
3954 new version to unstable.
3955
3956 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
3957 centralized control currently exercised in the monetary system. I
3958 find it completely unacceptable that the USA government is collecting
3959 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3960 that the major credit card companies can block legal money
3961 transactions to Wikileaks. But for bitcoin to succeed, more people
3962 need to use bitcoins, and more people need to accept bitcoins when
3963 they sell products and services. Improving the bitcoin support in
3964 Debian is a small step in the right direction, but not enough.
3965 Unfortunately the user experience when browsing the web and wanting to
3966 pay with bitcoin is still not very good. The bitcoin: URI is a step
3967 in the right direction, but need to work in most or every browser in
3968 use. Also the bitcoin-qt client is too heavy to fire up to do a
3969 quick transaction. I believe there are other clients available, but
3970 have not tested them.&lt;/p&gt;
3971
3972 &lt;p&gt;My
3973 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
3974 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
3975 I received 20.15 BTC so far on the address I provided in my blog two
3976 years ago, as can be
3977 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
3978 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
3979 donation. The blockexplorer service demonstrates quite well that
3980 bitcoin is not quite anonymous and untracked. :) I wonder if the
3981 number of users have gone up since then. If you use bitcoin and want
3982 to show your support of my activity, please send Bitcoin donations to
3983 the same address as last time,
3984 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3985 </description>
3986 </item>
3987
3988 <item>
3989 <title>Git repository for song book for Computer Scientists</title>
3990 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
3991 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
3992 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
3993 <description>&lt;p&gt;As I
3994 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
3995 this summer&lt;/a&gt;, I have created a Computer Science song book a few
3996 years ago, and today I finally found time to create a public
3997 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
3998 repository for the project&lt;/a&gt;.&lt;/p&gt;
3999
4000 &lt;p&gt;If you want to help out, please clone the source and submit patches
4001 to the HTML version. To generate the PDF and PostScript version,
4002 please use prince XML, or let me know about a useful free software
4003 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4004
4005 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4006 PostScript formats at
4007 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4008 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4009 </description>
4010 </item>
4011
4012 <item>
4013 <title>Gratulerer med 19-årsdagen, Debian!</title>
4014 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4015 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4016 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4017 <description>&lt;p&gt;I dag fyller
4018 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4019 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4020 si gratulerer med dagen, Debian!&lt;/p&gt;
4021 </description>
4022 </item>
4023
4024 <item>
4025 <title>Song book for Computer Scientists</title>
4026 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4028 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4029 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4030 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4031 collecting computer related songs for use at parties. The original
4032 version was written in LaTeX, but a few years ago I got help from
4033 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4034 while keeping the ability to create a nice book in PDF format. I have
4035 not had time to maintain the book for a while now, and guess I should
4036 put it up on some public version control repository where others can
4037 help me extend and update the book. If anyone is volunteering to help
4038 me with this, send me an email. Also let me know if there are songs
4039 missing in my book.&lt;/p&gt;
4040
4041 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4042 me today that I really should let all my readers share the joys of
4043 singing out load about programming, computers and computer networks.
4044 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4045 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4046 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4047 Computer Science Songbook&lt;/a&gt;.
4048 </description>
4049 </item>
4050
4051 <item>
4052 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4053 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4054 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4055 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4056 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4057 around 1000 at the moment. To be able to get help from the vendors
4058 when something go wrong, we want to keep the firmware on the servers
4059 up to date. If the firmware isn&#39;t the latest and greatest, the
4060 vendors typically refuse to start debugging any problems until the
4061 firmware is upgraded. So before every reboot, we want to upgrade the
4062 firmware, and we would really like everyone handling servers at the
4063 university to do this themselves when they plan to reboot a machine.
4064 For that to happen we at the unix server admin group need to provide
4065 the tools to do so.&lt;/p&gt;
4066
4067 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4068 fetch and install the latest firmware for the servers we got. Most of
4069 our hardware are from Dell and HP, so I have focused on these servers
4070 so far. This blog post is about the Dell part.&lt;/P&gt;
4071
4072 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4073 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4074 with firmware information for all 11th generation servers, listing
4075 which firmware should be used on a given model and where on the FTP
4076 site I can find it. Using a simple perl XML parser I can then
4077 download the shell scripts Dell provides to do firmware upgrades from
4078 within Linux and reboot when all the firmware is primed and ready to
4079 be activated on the first reboot.&lt;/p&gt;
4080
4081 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4082 Are there anyone working on similar tools for firmware upgrading all
4083 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4084
4085 &lt;p&gt;&lt;pre&gt;
4086 #!/usr/bin/perl
4087 use strict;
4088 use warnings;
4089 use File::Temp qw(tempdir);
4090 BEGIN {
4091 # Install needed RHEL packages if missing
4092 my %rhelmodules = (
4093 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4094 );
4095 for my $module (keys %rhelmodules) {
4096 eval &quot;use $module;&quot;;
4097 if ($@) {
4098 my $pkg = $rhelmodules{$module};
4099 system(&quot;yum install -y $pkg&quot;);
4100 eval &quot;use $module;&quot;;
4101 }
4102 }
4103 }
4104 my $errorsto = &#39;pere@hungry.com&#39;;
4105
4106 upgrade_dell();
4107
4108 exit 0;
4109
4110 sub run_firmware_script {
4111 my ($opts, $script) = @_;
4112 unless ($script) {
4113 print STDERR &quot;fail: missing script name\n&quot;;
4114 exit 1
4115 }
4116 print STDERR &quot;Running $script\n\n&quot;;
4117
4118 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4119 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4120 } else {
4121 print STDERR &quot;fail: firmware script returned error\n&quot;;
4122 }
4123 }
4124
4125 sub run_firmware_scripts {
4126 my ($opts, @dirs) = @_;
4127 # Run firmware packages
4128 for my $dir (@dirs) {
4129 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4130 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4131 while (my $s = readdir $dh) {
4132 next if $s =~ m/^\.\.?/;
4133 run_firmware_script($opts, &quot;$dir/$s&quot;);
4134 }
4135 closedir $dh;
4136 }
4137 }
4138
4139 sub download {
4140 my $url = shift;
4141 print STDERR &quot;info: Downloading $url\n&quot;;
4142 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4143 }
4144
4145 sub upgrade_dell {
4146 my @dirs;
4147 my $product = `dmidecode -s system-product-name`;
4148 chomp $product;
4149
4150 if ($product =~ m/PowerEdge/) {
4151
4152 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4153 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4154
4155 my $tmpdir = tempdir(
4156 CLEANUP =&gt; 1
4157 );
4158 chdir($tmpdir);
4159 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4160 system(&#39;gunzip Catalog.xml.gz&#39;);
4161 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4162 # -q is quiet, disabling interactivity and reducing console output
4163 my $fwopts = &quot;-q&quot;;
4164 if (@paths) {
4165 for my $url (@paths) {
4166 fetch_dell_fw($url);
4167 }
4168 run_firmware_scripts($fwopts, $tmpdir);
4169 } else {
4170 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4171 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4172 }
4173 chdir(&#39;/&#39;);
4174 } else {
4175 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4176 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4177 }
4178 }
4179
4180 sub fetch_dell_fw {
4181 my $path = shift;
4182 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4183 download($url);
4184 }
4185
4186 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4187 # firmware packages to download from Dell. Only work for Linux
4188 # machines and 11th generation Dell servers.
4189 sub fetch_dell_fw_list {
4190 my $filename = shift;
4191
4192 my $product = `dmidecode -s system-product-name`;
4193 chomp $product;
4194 my ($mybrand, $mymodel) = split(/\s+/, $product);
4195
4196 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4197
4198 my $xml = XMLin($filename);
4199 my @paths;
4200 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4201 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4202 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4203 my $oscode;
4204 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4205 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4206 } else {
4207 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4208 }
4209 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4210 {
4211 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4212 }
4213 }
4214 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4215 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4216
4217 # Drop application packages, only firmware and BIOS
4218 next if &#39;APAC&#39; eq $componenttype;
4219
4220 my $cpath = $component-&gt;{path};
4221 for my $path (@paths) {
4222 if ($cpath =~ m%/$path$%) {
4223 push(@paths, $cpath);
4224 }
4225 }
4226 }
4227 return @paths;
4228 }
4229 &lt;/pre&gt;
4230
4231 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4232 it could work on other platforms with some tweaking. Anyone know a
4233 index like Catalog.xml is available from HP for HP servers? At the
4234 moment I maintain a similar list manually and it is quickly getting
4235 outdated.&lt;/p&gt;
4236 </description>
4237 </item>
4238
4239 <item>
4240 <title>How is booting into runlevel 1 different from single user boots?</title>
4241 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4242 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4243 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4244 <description>&lt;p&gt;Wouter Verhelst have some
4245 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4246 comments and opinions&lt;/a&gt; on my blog post on
4247 &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
4248 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4249 &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
4250 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4251 small piece of his comment now, and though it best to address the
4252 misunderstanding he bring forward:&lt;/p&gt;
4253
4254 &lt;p&gt;&lt;blockquote&gt;
4255 Currently, a system admin has four options: [...] boot to a
4256 single-user system (by adding &#39;single&#39; to the kernel command line;
4257 this runs rcS and rc1 scripts)
4258 &lt;/blockquote&gt;&lt;/p&gt;
4259
4260 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4261 and booting into runlevel 1 is the same. I am not surprised he
4262 believe this, because it would make sense and is a quite sensible
4263 thing to believe. But because the boot in Debian is slightly broken,
4264 runlevel 1 do not work properly and it isn&#39;t the same as single user
4265 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4266 hard to explain.&lt;/p&gt;
4267
4268 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4269 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4270 executed in single user mode is sulogin. Single user mode is a boot
4271 state &quot;between&quot; the runlevels, and when booting into single user mode,
4272 only the scripts in /etc/rcS.d/ are executed before the init process
4273 enters the single user state. When switching to runlevel 1, the state
4274 is in fact not ending in runlevel 1, but it passes through runlevel 1
4275 and end up in the single user mode (see /etc/rc1.d/S03single, which
4276 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4277 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4278 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4279 mode).&lt;/p&gt;
4280
4281 &lt;p&gt;This summary might make it clearer. When booting for the first
4282 time into single user mode, the following commands are executed:
4283 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4284 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4285 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4286 trying to continue after visiting single user mode. Not all services
4287 are started again as they should, causing the machine to end up in an
4288 unpredicatble state. This is why Debian admins recommend rebooting
4289 after visiting single user mode.&lt;/p&gt;
4290
4291 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4292 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4293 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4294 stopped when passing through the scripts in /etc/rc1.d/, and not
4295 started again when switching away from runlevel 1 to the runlevels
4296 2-5. I believe the problem is best fixed by moving all the scripts
4297 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4298 functioning single user mode during boot.&lt;/p&gt;
4299
4300 &lt;p&gt;I have spent several years investigating the Debian boot system,
4301 and discovered this problem a few years ago. I suspect it originates
4302 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4303 </description>
4304 </item>
4305
4306 <item>
4307 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4308 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4309 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4310 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4311 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4312 are started from /etc/rcS.d/. In fact, there is a bite more of them
4313 than make sense, and this causes a few problems. What kind of
4314 problems, you might ask. There are at least two problems. The first
4315 is that it is not possible to recover a machine after switching to
4316 runlevel 1. One need to actually reboot to get the machine back to
4317 the expected state. The other is that single user boot will sometimes
4318 run into problems because some of the subsystems are activated before
4319 the root login is presented, causing problems when trying to recover a
4320 machine from a problem in that subsystem. A minor additional point is
4321 that moving more scripts out of rcS.d/ and into the other rc#.d/
4322 directories will increase the amount of scripts that can run in
4323 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4324
4325 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4326 scripts that _have_ to execute before the root login prompt is
4327 presented during a single user boot should go there. Everything else
4328 should go into the numeric runlevels. This means things like
4329 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4330 the numeric runlevels. Today in Debian, there are around 115 init.d
4331 scripts that are started from rcS.d/, and most of them should be moved
4332 out. Do your package have one of them? Please help us make single
4333 user and runlevel 1 better by moving it.&lt;/p&gt;
4334
4335 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4336 etc. should still be started from rcS.d/, but there is for example no
4337 need to have the network enabled before the single user login prompt
4338 is presented.&lt;/p&gt;
4339
4340 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4341 Debian systems working while scripts migrate and during upgrades, the
4342 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4343 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4344 and the next ones can only be moved when their dependencies have been
4345 moved first. This migration must be done sequentially while we ensure
4346 that the package system upgrade packages in the right order to keep
4347 the system state correct. This will require some coordination when it
4348 comes to network related packages, but most of the packages with
4349 scripts that should migrate do not have anything in rcS.d/ depending
4350 on them. Some packages have already been updated, like the sudo
4351 package, while others are still left to do. I wish I had time to work
4352 on this myself, but real live constrains make it unlikely that I will
4353 find time to push this forward.&lt;/p&gt;
4354 </description>
4355 </item>
4356
4357 <item>
4358 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4359 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4360 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4361 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4362 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4363 mentioned the issues I believe should be improved in Debian for its
4364 desktop to be useful for more people. The use case for this is my
4365 parents, which are currently running Kubuntu which solve the
4366 issues.&lt;/p&gt;
4367
4368 &lt;p&gt;I suspect these four missing features are not very hard to
4369 implement. After all, they are present in Ubuntu, so if we wanted to
4370 do this in Debian we would have a source.&lt;/p&gt;
4371
4372 &lt;ol&gt;
4373
4374 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4375 are new packages available for upgrades, a icon in the KDE status bar
4376 indicate this, and clicking on it will activate the simple upgrade
4377 tool to handle it. I have no problem guiding both of my parents
4378 through the process over the phone. If a kernel reboot is required,
4379 this too is indicated by the status bars and the upgrade tool. Last
4380 time I checked, nothing with the same features was working in KDE in
4381 Debian.&lt;/li&gt;
4382
4383 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4384 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4385 currently have a handler for, it will ask the user if the system
4386 should search for a package that would add support for this MIME type,
4387 and if the user say yes, the APT sources will be searched for packages
4388 advertising the MIME type in their control file (visible in the
4389 Packages file in the APT archive). If one or more packages are found,
4390 it is a simple click of the mouse to add support for the missing mime
4391 type. If the package require the user to accept some non-free
4392 license, this is explained to the user. The entire process make it
4393 more clear to the user why something do not work in the browser, and
4394 make the chances higher for the user to blame the web page authors and
4395 not the browser for any missing features.&lt;/li&gt;
4396
4397 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4398 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4399 it is not supporting, a dialog pop up asking the user if the system
4400 should search for a package that would add support for it. This
4401 happen with things like MP3, Windows Media or H.264. The selection
4402 and installation procedure is very similar to the Firefox browser
4403 plugin handling. This is as far as I know implemented using a
4404 gstreamer hook. The end result is that the user easily get access to
4405 the codecs that are present from the APT archives available, while
4406 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4407
4408 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4409 displaying a text/plain file in my Debian browser, it will propose to
4410 start emacs to show it. If I remember correctly, when doing the same
4411 in Kunbutu it show the file as a text file in the browser. At least I
4412 know Opera will show text files within the browser. I much prefer the
4413 latter behaviour.&lt;/li&gt;
4414
4415 &lt;/ol&gt;
4416
4417 &lt;p&gt;There are other nice features as well, like the simplified suite
4418 upgrader, but given that I am the one mostly doing the dist-upgrade,
4419 it do not matter much.&lt;/p&gt;
4420
4421 &lt;p&gt;I really hope we could get these features in place for the next
4422 Debian release. It would require the coordinated effort of several
4423 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4424 </description>
4425 </item>
4426
4427 <item>
4428 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4429 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4430 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4431 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4432 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4433 site is build on Debian/Squeeze, and this platform was chosen because
4434 I am most familiar with Debian (being a Debian Developer for around 10
4435 years) because it is the latest stable Debian release which should get
4436 security support for a few years.&lt;/p&gt;
4437
4438 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4439 that are missing in Debian at the moment. It would be great if these
4440 modules were added to the Debian archive, allowing anyone to set up
4441 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4442 in their own country using only Debian packages. The list of modules
4443 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4444 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4445 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4446 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4447 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4448 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4449 easier in the future.&lt;/p&gt;
4450
4451 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4452 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4453 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4454 with the responsibility of tracking security problems, which I really
4455 do not have time for.&lt;/p&gt;
4456 </description>
4457 </item>
4458
4459 <item>
4460 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4461 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4462 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4463 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4464 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4465 posts have been in Norwegian the last few weeks, so here is a short
4466 update in English.&lt;/p&gt;
4467
4468 &lt;p&gt;The kids still keep me too busy to get much free software work
4469 done, but I did manage to organise a project to get a Norwegian port
4470 of the British service
4471 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4472 and it has been running for a month now. The entire project has been
4473 organised by me and two others. Around Christmas we gathered sponsors
4474 to fund the development work. In January I drafted a contract with
4475 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4476 and in February the development took place. Most of it involved
4477 converting the source to use GPS coordinates instead of British
4478 easting/northing, and the resulting code should be a lot easier to get
4479 running in any country by now. The Norwegian
4480 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4481 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4482 source and the source for administrative borders in Norway, and
4483 support for this had to be added/fixed.&lt;/p&gt;
4484
4485 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4486 polishing the system before we announced it March 7th. The system is
4487 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4488 problem reports in a few weeks. Soon we hope to announce the Android
4489 and iPhone versions making it even easier to report problems with the
4490 public infrastructure.&lt;/p&gt;
4491
4492 &lt;p&gt;Perhaps something to consider for those of you in countries without
4493 such service?&lt;/p&gt;
4494 </description>
4495 </item>
4496
4497 <item>
4498 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4499 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4500 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4501 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4502 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4503 issues here at my work with the University of Oslo. My idea is that
4504 it should be possible to use the information about security issues
4505 available on the Internet, and check our locally
4506 maintained/distributed software against this information. It should
4507 allow us to verify that no known security issues are forgotten. The
4508 CVE database listing vulnerabilities seem like a great central point,
4509 and by using the package lists from Debian mapped to CVEs provided by
4510 the testing security team, I believed it should be possible to figure
4511 out which security holes were present in our free software
4512 collection.&lt;/p&gt;
4513
4514 &lt;p&gt;After reading up on the topic, it became obvious that the first
4515 building block is to be able to name software packages in a unique and
4516 consistent way across data sources. I considered several ways to do
4517 this, for example coming up with my own naming scheme like using URLs
4518 to project home pages or URLs to the Freshmeat entries, or using some
4519 existing naming scheme. And it seem like I am not the first one to
4520 come across this problem, as MITRE already proposed and implemented a
4521 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4522 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4523 software, hardware and other platform components. The CPE ids are
4524 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4525 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4526 issues for any CPE name. With this in place, all I need to do is to
4527 locate the CPE id for the software packages we use at the university.
4528 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4529 NVD entry if a CVE for the package exist).&lt;/p&gt;
4530
4531 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4532 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4533 check out, one could look up
4534 &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
4535 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4536 The most recent one is
4537 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4538 and at the bottom of the NVD page for this vulnerability the complete
4539 list of affected versions is provided.&lt;/p&gt;
4540
4541 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4542 for offline processing of issues. Using this dump, I&#39;ve written a
4543 small script taking a list of CPEs as input and list all CVEs
4544 affecting the packages represented by these CPEs. One give it CPEs
4545 with version numbers as specified above and get a list of open
4546 security issues out.&lt;/p&gt;
4547
4548 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4549 information need to be high. For that to happen, I believe as many as
4550 possible need to use and contribute to the NVD database. I notice
4551 RHEL is providing
4552 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4553 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4554 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4555
4556 &lt;p&gt;To get an idea about the quality for free software, I spent some
4557 time making it possible to compare the CVE database from Debian with
4558 the CVE database in NVD. The result look fairly good, but there are
4559 some inconsistencies in NVD (same software package having several
4560 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4561 Debian believe are affected by a CVE). Hope to find time to improve
4562 the quality of NVD, but that require being able to get in touch with
4563 someone maintaining it. So far my three emails with questions and
4564 corrections have not seen any reply, but I hope contact can be
4565 established soon.&lt;/p&gt;
4566
4567 &lt;p&gt;An interesting application for CPEs is cross platform package
4568 mapping. It would be useful to know which packages in for example
4569 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4570 this would be trivial if all linux distributions provided CPE entries
4571 for their packages.&lt;/p&gt;
4572 </description>
4573 </item>
4574
4575 <item>
4576 <title>Which module is loaded for a given PCI and USB device?</title>
4577 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4578 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4579 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4580 <description>&lt;p&gt;In the
4581 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4582 package in Debian, there is a script to report useful information
4583 about the running hardware for use when people report missing
4584 information. One part of this script that I find very useful when
4585 debugging hardware problems, is the part mapping loaded kernel module
4586 to the PCI device it claims. It allow me to quickly see if the kernel
4587 module I expect is driving the hardware I am struggling with. To see
4588 the output, make sure discover-data is installed and run
4589 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4590 one of my machines like this:&lt;/p&gt;
4591
4592 &lt;pre&gt;
4593 loaded modules:
4594 10de:03eb i2c_nforce2
4595 10de:03f1 ohci_hcd
4596 10de:03f2 ehci_hcd
4597 10de:03f0 snd_hda_intel
4598 10de:03ec pata_amd
4599 10de:03f6 sata_nv
4600 1022:1103 k8temp
4601 109e:036e bttv
4602 109e:0878 snd_bt87x
4603 11ab:4364 sky2
4604 &lt;/pre&gt;
4605
4606 &lt;p&gt;The code in question look like this, slightly modified for
4607 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4608
4609 &lt;pre&gt;
4610 if [ -d /sys/bus/pci/devices/ ] ; then
4611 echo loaded pci modules:
4612 (
4613 cd /sys/bus/pci/devices/
4614 for address in * ; do
4615 if [ -d &quot;$address/driver/module&quot; ] ; then
4616 module=`cd $address/driver/module ; pwd -P | xargs basename`
4617 if grep -q &quot;^$module &quot; /proc/modules ; then
4618 address=$(echo $address |sed s/0000://)
4619 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4620 echo &quot;$id $module&quot;
4621 fi
4622 fi
4623 done
4624 )
4625 echo
4626 fi
4627 &lt;/pre&gt;
4628
4629 &lt;p&gt;Similar code could be used to extract USB device module
4630 mappings:&lt;/p&gt;
4631
4632 &lt;pre&gt;
4633 if [ -d /sys/bus/usb/devices/ ] ; then
4634 echo loaded usb modules:
4635 (
4636 cd /sys/bus/usb/devices/
4637 for address in * ; do
4638 if [ -d &quot;$address/driver/module&quot; ] ; then
4639 module=`cd $address/driver/module ; pwd -P | xargs basename`
4640 if grep -q &quot;^$module &quot; /proc/modules ; then
4641 address=$(echo $address |sed s/0000://)
4642 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4643 if [ &quot;$id&quot; ] ; then
4644 echo &quot;$id $module&quot;
4645 fi
4646 fi
4647 fi
4648 done
4649 )
4650 echo
4651 fi
4652 &lt;/pre&gt;
4653
4654 &lt;p&gt;This might perhaps be something to include in other tools as
4655 well.&lt;/p&gt;
4656 </description>
4657 </item>
4658
4659 <item>
4660 <title>How to test if a laptop is working with Linux</title>
4661 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4662 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4663 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4664 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4665 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4666 batch of computers will work with Linux. Every year for the last few
4667 years the university have organised shared bid of a few thousand
4668 computers, and this year HP won the bid. Two different desktops and
4669 five different laptops are on the list this year. We in the UNIX
4670 group want to know which one of these computers work well with RHEL
4671 and Ubuntu, the two Linux distributions we currently handle at the
4672 university.&lt;/p&gt;
4673
4674 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4675 perhaps inspire others to test hardware as well. To test, I PXE
4676 install the OS version of choice, and log in as my normal user and run
4677 a few applications and plug in selected pieces of hardware. When
4678 something fail, I make a note about this in the test matrix and move
4679 on. If I have some spare time I try to report the bug to the OS
4680 vendor, but as I only have the machines for a short time, I rarely
4681 have the time to do this for all the problems I find.&lt;/p&gt;
4682
4683 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4684 I perform on a new model.&lt;/p&gt;
4685
4686 &lt;ul&gt;
4687
4688 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4689 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4690 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4691
4692 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4693 installation, X.org is working.&lt;/li&gt;
4694
4695 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4696 package mesa-utils on Ubuntu) and writing down the frames per second
4697 reported by the program.&lt;/li&gt;
4698
4699 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4700 logging in, and if I can hear this the test is successful. If there
4701 are several audio exits on the machine, I try them all and check if
4702 the Gnome/KDE audio mixer can control where to send the sound. I
4703 normally test this by playing
4704 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4705 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4706
4707 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4708 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4709
4710 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4711 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4712
4713 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4714 picture from the v4l device show up.&lt;/li&gt;
4715
4716 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4717 any bluetooth devices are discovered. In my office, I normally see a
4718 few.&lt;/li&gt;
4719
4720 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4721 memory modules lying around, and stick them in and see if Gnome/KDE
4722 notice this.&lt;/li&gt;
4723
4724 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4725 special button work, and if the laptop continue to work after
4726 resume.&lt;/li&gt;
4727
4728 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4729 adjusting background light, switching on/off external video output,
4730 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4731 laptop to laptop, so I just write down which are working and which are
4732 not.&lt;/li&gt;
4733
4734 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4735 acceleration sensors etc. I rarely test these, as I do not know how
4736 to quickly test if they are working or not, so I only document their
4737 existence.&lt;/li&gt;
4738
4739 &lt;/ul&gt;
4740
4741 &lt;p&gt;By now I suspect you are really curious what the test results are
4742 for the HP machines I am testing. I&#39;m not done yet, so I will report
4743 the test results later. For now I can report that HP 8100 Elite work
4744 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4745 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4746 can see, I have most machines left to test. One interesting
4747 observation is that Ubuntu Lucid has almost twice the frame rate than
4748 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4749 </description>
4750 </item>
4751
4752 <item>
4753 <title>Some thoughts on BitCoins</title>
4754 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4755 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4756 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4757 <description>&lt;p&gt;As I continue to explore
4758 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4759 what properties the system have, and how it will be affected by laws
4760 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4761
4762 &lt;p&gt;One interesting thing to note is that since the transactions are
4763 verified using a peer to peer network, all details about a transaction
4764 is known to everyone. This means that if a BitCoin address has been
4765 published like I did with mine in my initial post about BitCoin, it is
4766 possible for everyone to see how many BitCoins have been transfered to
4767 that address. There is even a web service to look at the details for
4768 all transactions. There I can see that my address
4769 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4770 have received 16.06 Bitcoin, the
4771 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4772 address of Simon Phipps have received 181.97 BitCoin and the address
4773 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4774 of EFF have received 2447.38 BitCoins so far. Thank you to each and
4775 every one of you that donated bitcoins to support my activity. The
4776 fact that anyone can see how much money was transfered to a given
4777 address make it more obvious why the BitCoin community recommend to
4778 generate and hand out a new address for each transaction. I&#39;m told
4779 there is no way to track which addresses belong to a given person or
4780 organisation without the person or organisation revealing it
4781 themselves, as Simon, EFF and I have done.&lt;/p&gt;
4782
4783 &lt;p&gt;In Norway, and in most other countries, there are laws and
4784 regulations limiting how much money one can transfer across the border
4785 without declaring it. There are money laundering, tax and accounting
4786 laws and regulations I would expect to apply to the use of BitCoin.
4787 If the Skolelinux foundation
4788 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
4789 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
4790 normal bank transfers like EFF is doing, how should this be accounted?
4791 Given that it is impossible to know if money can cross the border or
4792 not, should everything or nothing be declared? What exchange rate
4793 should be used when calculating taxes? Would receivers have to pay
4794 income tax if the foundation were to pay Skolelinux contributors in
4795 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
4796
4797 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
4798 accepted by a lot of users. It must be possible to get easy access to
4799 the currency (as a wage or using currency exchanges), and it must be
4800 easy to spend it. At the moment BitCoin seem fairly easy to get
4801 access to, but there are very few places to spend it. I am not really
4802 a regular user of any of the vendor types currently accepting BitCoin,
4803 so I wonder when my kind of shop would start accepting BitCoins. I
4804 would like to buy electronics, travels and subway tickets, not herbs
4805 and books. :) The currency is young, and this will improve over time
4806 if it become popular, but I suspect regular banks will start to lobby
4807 to get BitCoin declared illegal if it become popular. I&#39;m sure they
4808 will claim it is helping fund terrorism and money laundering (which
4809 probably would be true, as is any currency in existence), but I
4810 believe the problems should be solved elsewhere and not by blaming
4811 currencies.&lt;/p&gt;
4812
4813 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
4814 CPU intensive process that depend on a bit of luck as well (as one is
4815 competing against all the other miners currently spending CPU cycles
4816 to see which one get the next lump of cash). The &quot;winner&quot; get 50
4817 BitCoin when this happen. Yesterday I came across the obvious way to
4818 join forces to increase ones changes of getting at least some coins,
4819 by coordinating the work on mining BitCoins across several machines
4820 and people, and sharing the result if one is lucky and get the 50
4821 BitCoins. Check out
4822 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
4823 if this sounds interesting. I have not had time to try to set up a
4824 machine to participate there yet, but have seen that running on ones
4825 own for a few days have not yield any BitCoins througth mining
4826 yet.&lt;/p&gt;
4827
4828 &lt;p&gt;Update 2010-12-15: Found an &lt;a
4829 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
4830 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
4831 it was interesting to read. The arguments presented seem to be
4832 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
4833 </description>
4834 </item>
4835
4836 <item>
4837 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
4838 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
4839 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
4840 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
4841 <description>&lt;p&gt;With this weeks lawless
4842 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
4843 attacks&lt;/a&gt; on Wikileak and
4844 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
4845 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
4846 not be trusted to handle money transactions.
4847 A blog post from
4848 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
4849 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
4850 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
4851 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
4852 some help from my friend to get it all running, and he even handed me
4853 some bitcoins to get started. I even donated a few bitcoins to Simon
4854 for helping me remember BitCoin.&lt;/p&gt;
4855
4856 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
4857 crypto-currency, decentralised and handled using peer-to-peer
4858 networks. It allows anonymous transactions and prohibits central
4859 control over the transactions, making it impossible for governments
4860 and companies alike to block donations and other transactions. The
4861 source is free software, and while the key dependency wxWidgets 2.9
4862 for the graphical user interface is missing in Debian, the command
4863 line client builds just fine. Hopefully Jonas
4864 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
4865 Debian&lt;/a&gt; soon.&lt;/p&gt;
4866
4867 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
4868 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
4869 bitcoins&lt;/a&gt; when selling services and goods, and there are even
4870 currency &quot;stock&quot; markets where the exchange rate is decided. There
4871 are not many users so far, but the concept seems promising. If you
4872 want to get started and lack a friend with any bitcoins to spare,
4873 you can even get
4874 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
4875 bitcoin at the time of writing). Use
4876 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
4877 on the current exchange rates.&lt;/p&gt;
4878
4879 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
4880 machines. If you want to support my activity, please send Bitcoin
4881 donations to the address
4882 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
4883 </description>
4884 </item>
4885
4886 <item>
4887 <title>Why isn&#39;t Debian Edu using VLC?</title>
4888 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
4889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
4890 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
4891 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4892 presented, and the winner among the multimedia player were VLC.
4893 Personally, I like VLC, and it is my player of choice when I first try
4894 to play a video file or stream. Only if VLC fail will I drag out
4895 gmplayer to see if it can do better. The reason is mostly the failure
4896 model and trust. When VLC fail, it normally pop up a error message
4897 reporting the problem. When mplayer fail, it normally segfault or
4898 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4899
4900 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4901 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4902 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4903 plugin to play web videos seamlessly, and the VLC browser plugin is
4904 not very good. For example, it lack in-line control buttons, so there
4905 is no way for the user to pause the video. Also, when I
4906 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
4907 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
4908 failed on several video pages where mplayer based plugins worked. If
4909 the browser plugin for VLC was as good as the gecko-mediaplayer
4910 package (which uses mplayer), we would switch.&lt;/P&gt;
4911
4912 &lt;p&gt;While VLC is a good player, its user interface is slightly
4913 annoying. The most annoying feature is its inconsistent use of
4914 keyboard shortcuts. When the player is in full screen mode, its
4915 shortcuts are different from when it is playing the video in a window.
4916 For example, space only work as pause when in full screen mode. I
4917 wish it had consisten shortcuts and that space also would work when in
4918 window mode. Another nice shortcut in gmplayer is [enter] to restart
4919 the current video. It is very nice when playing short videos from the
4920 web and want to restart it when new people arrive to have a look at
4921 what is going on.&lt;/p&gt;
4922 </description>
4923 </item>
4924
4925 <item>
4926 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
4927 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
4928 <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>
4929 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
4930 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
4931 upgrade testing of the
4932 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4933 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
4934 This seem like a very good idea, so I adjusted by test scripts and
4935 can now present the updated result from today:&lt;/p&gt;
4936
4937 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4938
4939 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4940
4941 &lt;blockquote&gt;&lt;p&gt;
4942 apache2.2-bin
4943 aptdaemon
4944 baobab
4945 binfmt-support
4946 browser-plugin-gnash
4947 cheese-common
4948 cli-common
4949 cups-pk-helper
4950 dmz-cursor-theme
4951 empathy
4952 empathy-common
4953 freedesktop-sound-theme
4954 freeglut3
4955 gconf-defaults-service
4956 gdm-themes
4957 gedit-plugins
4958 geoclue
4959 geoclue-hostip
4960 geoclue-localnet
4961 geoclue-manual
4962 geoclue-yahoo
4963 gnash
4964 gnash-common
4965 gnome
4966 gnome-backgrounds
4967 gnome-cards-data
4968 gnome-codec-install
4969 gnome-core
4970 gnome-desktop-environment
4971 gnome-disk-utility
4972 gnome-screenshot
4973 gnome-search-tool
4974 gnome-session-canberra
4975 gnome-system-log
4976 gnome-themes-extras
4977 gnome-themes-more
4978 gnome-user-share
4979 gstreamer0.10-fluendo-mp3
4980 gstreamer0.10-tools
4981 gtk2-engines
4982 gtk2-engines-pixbuf
4983 gtk2-engines-smooth
4984 hamster-applet
4985 libapache2-mod-dnssd
4986 libapr1
4987 libaprutil1
4988 libaprutil1-dbd-sqlite3
4989 libaprutil1-ldap
4990 libart2.0-cil
4991 libboost-date-time1.42.0
4992 libboost-python1.42.0
4993 libboost-thread1.42.0
4994 libchamplain-0.4-0
4995 libchamplain-gtk-0.4-0
4996 libcheese-gtk18
4997 libclutter-gtk-0.10-0
4998 libcryptui0
4999 libdiscid0
5000 libelf1
5001 libepc-1.0-2
5002 libepc-common
5003 libepc-ui-1.0-2
5004 libfreerdp-plugins-standard
5005 libfreerdp0
5006 libgconf2.0-cil
5007 libgdata-common
5008 libgdata7
5009 libgdu-gtk0
5010 libgee2
5011 libgeoclue0
5012 libgexiv2-0
5013 libgif4
5014 libglade2.0-cil
5015 libglib2.0-cil
5016 libgmime2.4-cil
5017 libgnome-vfs2.0-cil
5018 libgnome2.24-cil
5019 libgnomepanel2.24-cil
5020 libgpod-common
5021 libgpod4
5022 libgtk2.0-cil
5023 libgtkglext1
5024 libgtksourceview2.0-common
5025 libmono-addins-gui0.2-cil
5026 libmono-addins0.2-cil
5027 libmono-cairo2.0-cil
5028 libmono-corlib2.0-cil
5029 libmono-i18n-west2.0-cil
5030 libmono-posix2.0-cil
5031 libmono-security2.0-cil
5032 libmono-sharpzip2.84-cil
5033 libmono-system2.0-cil
5034 libmtp8
5035 libmusicbrainz3-6
5036 libndesk-dbus-glib1.0-cil
5037 libndesk-dbus1.0-cil
5038 libopal3.6.8
5039 libpolkit-gtk-1-0
5040 libpt2.6.7
5041 libpython2.6
5042 librpm1
5043 librpmio1
5044 libsdl1.2debian
5045 libsrtp0
5046 libssh-4
5047 libtelepathy-farsight0
5048 libtelepathy-glib0
5049 libtidy-0.99-0
5050 media-player-info
5051 mesa-utils
5052 mono-2.0-gac
5053 mono-gac
5054 mono-runtime
5055 nautilus-sendto
5056 nautilus-sendto-empathy
5057 p7zip-full
5058 pkg-config
5059 python-aptdaemon
5060 python-aptdaemon-gtk
5061 python-axiom
5062 python-beautifulsoup
5063 python-bugbuddy
5064 python-clientform
5065 python-coherence
5066 python-configobj
5067 python-crypto
5068 python-cupshelpers
5069 python-elementtree
5070 python-epsilon
5071 python-evolution
5072 python-feedparser
5073 python-gdata
5074 python-gdbm
5075 python-gst0.10
5076 python-gtkglext1
5077 python-gtksourceview2
5078 python-httplib2
5079 python-louie
5080 python-mako
5081 python-markupsafe
5082 python-mechanize
5083 python-nevow
5084 python-notify
5085 python-opengl
5086 python-openssl
5087 python-pam
5088 python-pkg-resources
5089 python-pyasn1
5090 python-pysqlite2
5091 python-rdflib
5092 python-serial
5093 python-tagpy
5094 python-twisted-bin
5095 python-twisted-conch
5096 python-twisted-core
5097 python-twisted-web
5098 python-utidylib
5099 python-webkit
5100 python-xdg
5101 python-zope.interface
5102 remmina
5103 remmina-plugin-data
5104 remmina-plugin-rdp
5105 remmina-plugin-vnc
5106 rhythmbox-plugin-cdrecorder
5107 rhythmbox-plugins
5108 rpm-common
5109 rpm2cpio
5110 seahorse-plugins
5111 shotwell
5112 software-center
5113 system-config-printer-udev
5114 telepathy-gabble
5115 telepathy-mission-control-5
5116 telepathy-salut
5117 tomboy
5118 totem
5119 totem-coherence
5120 totem-mozilla
5121 totem-plugins
5122 transmission-common
5123 xdg-user-dirs
5124 xdg-user-dirs-gtk
5125 xserver-xephyr
5126 &lt;/p&gt;&lt;/blockquote&gt;
5127
5128 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5129
5130 &lt;blockquote&gt;&lt;p&gt;
5131 cheese
5132 ekiga
5133 eog
5134 epiphany-extensions
5135 evolution-exchange
5136 fast-user-switch-applet
5137 file-roller
5138 gcalctool
5139 gconf-editor
5140 gdm
5141 gedit
5142 gedit-common
5143 gnome-games
5144 gnome-games-data
5145 gnome-nettool
5146 gnome-system-tools
5147 gnome-themes
5148 gnuchess
5149 gucharmap
5150 guile-1.8-libs
5151 libavahi-ui0
5152 libdmx1
5153 libgalago3
5154 libgtk-vnc-1.0-0
5155 libgtksourceview2.0-0
5156 liblircclient0
5157 libsdl1.2debian-alsa
5158 libspeexdsp1
5159 libsvga1
5160 rhythmbox
5161 seahorse
5162 sound-juicer
5163 system-config-printer
5164 totem-common
5165 transmission-gtk
5166 vinagre
5167 vino
5168 &lt;/p&gt;&lt;/blockquote&gt;
5169
5170 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5171
5172 &lt;blockquote&gt;&lt;p&gt;
5173 gstreamer0.10-gnomevfs
5174 &lt;/p&gt;&lt;/blockquote&gt;
5175
5176 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5177
5178 &lt;blockquote&gt;&lt;p&gt;
5179 [nothing]
5180 &lt;/p&gt;&lt;/blockquote&gt;
5181
5182 &lt;p&gt;This is for KDE:&lt;/p&gt;
5183
5184 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5185
5186 &lt;blockquote&gt;&lt;p&gt;
5187 ksmserver
5188 &lt;/p&gt;&lt;/blockquote&gt;
5189
5190 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5191
5192 &lt;blockquote&gt;&lt;p&gt;
5193 kwin
5194 network-manager-kde
5195 &lt;/p&gt;&lt;/blockquote&gt;
5196
5197 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5198
5199 &lt;blockquote&gt;&lt;p&gt;
5200 arts
5201 dolphin
5202 freespacenotifier
5203 google-gadgets-gst
5204 google-gadgets-xul
5205 kappfinder
5206 kcalc
5207 kcharselect
5208 kde-core
5209 kde-plasma-desktop
5210 kde-standard
5211 kde-window-manager
5212 kdeartwork
5213 kdeartwork-emoticons
5214 kdeartwork-style
5215 kdeartwork-theme-icon
5216 kdebase
5217 kdebase-apps
5218 kdebase-workspace
5219 kdebase-workspace-bin
5220 kdebase-workspace-data
5221 kdeeject
5222 kdelibs
5223 kdeplasma-addons
5224 kdeutils
5225 kdewallpapers
5226 kdf
5227 kfloppy
5228 kgpg
5229 khelpcenter4
5230 kinfocenter
5231 konq-plugins-l10n
5232 konqueror-nsplugins
5233 kscreensaver
5234 kscreensaver-xsavers
5235 ktimer
5236 kwrite
5237 libgle3
5238 libkde4-ruby1.8
5239 libkonq5
5240 libkonq5-templates
5241 libnetpbm10
5242 libplasma-ruby
5243 libplasma-ruby1.8
5244 libqt4-ruby1.8
5245 marble-data
5246 marble-plugins
5247 netpbm
5248 nuvola-icon-theme
5249 plasma-dataengines-workspace
5250 plasma-desktop
5251 plasma-desktopthemes-artwork
5252 plasma-runners-addons
5253 plasma-scriptengine-googlegadgets
5254 plasma-scriptengine-python
5255 plasma-scriptengine-qedje
5256 plasma-scriptengine-ruby
5257 plasma-scriptengine-webkit
5258 plasma-scriptengines
5259 plasma-wallpapers-addons
5260 plasma-widget-folderview
5261 plasma-widget-networkmanagement
5262 ruby
5263 sweeper
5264 update-notifier-kde
5265 xscreensaver-data-extra
5266 xscreensaver-gl
5267 xscreensaver-gl-extra
5268 xscreensaver-screensaver-bsod
5269 &lt;/p&gt;&lt;/blockquote&gt;
5270
5271 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5272
5273 &lt;blockquote&gt;&lt;p&gt;
5274 ark
5275 google-gadgets-common
5276 google-gadgets-qt
5277 htdig
5278 kate
5279 kdebase-bin
5280 kdebase-data
5281 kdepasswd
5282 kfind
5283 klipper
5284 konq-plugins
5285 konqueror
5286 ksysguard
5287 ksysguardd
5288 libarchive1
5289 libcln6
5290 libeet1
5291 libeina-svn-06
5292 libggadget-1.0-0b
5293 libggadget-qt-1.0-0b
5294 libgps19
5295 libkdecorations4
5296 libkephal4
5297 libkonq4
5298 libkonqsidebarplugin4a
5299 libkscreensaver5
5300 libksgrd4
5301 libksignalplotter4
5302 libkunitconversion4
5303 libkwineffects1a
5304 libmarblewidget4
5305 libntrack-qt4-1
5306 libntrack0
5307 libplasma-geolocation-interface4
5308 libplasmaclock4a
5309 libplasmagenericshell4
5310 libprocesscore4a
5311 libprocessui4a
5312 libqalculate5
5313 libqedje0a
5314 libqtruby4shared2
5315 libqzion0a
5316 libruby1.8
5317 libscim8c2a
5318 libsmokekdecore4-3
5319 libsmokekdeui4-3
5320 libsmokekfile3
5321 libsmokekhtml3
5322 libsmokekio3
5323 libsmokeknewstuff2-3
5324 libsmokeknewstuff3-3
5325 libsmokekparts3
5326 libsmokektexteditor3
5327 libsmokekutils3
5328 libsmokenepomuk3
5329 libsmokephonon3
5330 libsmokeplasma3
5331 libsmokeqtcore4-3
5332 libsmokeqtdbus4-3
5333 libsmokeqtgui4-3
5334 libsmokeqtnetwork4-3
5335 libsmokeqtopengl4-3
5336 libsmokeqtscript4-3
5337 libsmokeqtsql4-3
5338 libsmokeqtsvg4-3
5339 libsmokeqttest4-3
5340 libsmokeqtuitools4-3
5341 libsmokeqtwebkit4-3
5342 libsmokeqtxml4-3
5343 libsmokesolid3
5344 libsmokesoprano3
5345 libtaskmanager4a
5346 libtidy-0.99-0
5347 libweather-ion4a
5348 libxklavier16
5349 libxxf86misc1
5350 okteta
5351 oxygencursors
5352 plasma-dataengines-addons
5353 plasma-scriptengine-superkaramba
5354 plasma-widget-lancelot
5355 plasma-widgets-addons
5356 plasma-widgets-workspace
5357 polkit-kde-1
5358 ruby1.8
5359 systemsettings
5360 update-notifier-common
5361 &lt;/p&gt;&lt;/blockquote&gt;
5362
5363 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5364 aptitude a bit more similar, but there are still quite a lott of
5365 differences. I have no idea what packages should be installed after
5366 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5367 </description>
5368 </item>
5369
5370 <item>
5371 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5372 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5373 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5374 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5375 <description>&lt;p&gt;Most of the computers in use by the
5376 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5377 are virtual machines. And they have been Xen machines running on a
5378 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5379 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5380 bit harder that it could have been, because we set up the Xen virtual
5381 machines to get the virtual partitions from LVM, which as far as I
5382 know is not supported by KVM. So to migrate, we had to convert
5383 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5384
5385 &lt;p&gt;I found
5386 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5387 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5388 migration. It uses qemu-img from the qemu package to make the disk
5389 image, parted to partition it, losetup and kpartx to present the disk
5390 image partions as devices, and dd to copy the data. I NFS mounted the
5391 new servers storage area on the old server to do the migration.&lt;/p&gt;
5392
5393 &lt;pre&gt;
5394 #!/bin/sh
5395
5396 # Based on
5397 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5398
5399 set -e
5400 set -x
5401
5402 if [ -z &quot;$1&quot; ] ; then
5403 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5404 exit 1
5405 else
5406 host=&quot;$1&quot;
5407 fi
5408
5409 if [ ! -e /dev/vg_data/$host-disk ] ; then
5410 echo &quot;error: unable to find LVM volume for $host&quot;
5411 exit 1
5412 fi
5413
5414 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5415 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5416 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5417 totalsize=$(( ( $disksize + $swapsize ) ))
5418
5419 img=$host.img
5420 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5421 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5422
5423 parted $img mklabel msdos
5424 parted $img mkpart primary linux-swap 0 $disksize
5425 parted $img mkpart primary ext2 $disksize $totalsize
5426 parted $img set 1 boot on
5427
5428 modprobe dm-mod
5429 losetup /dev/loop0 $img
5430 kpartx -a /dev/loop0
5431
5432 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5433 fsck.ext3 -f /dev/mapper/loop0p1 || true
5434 mkswap /dev/mapper/loop0p2
5435
5436 kpartx -d /dev/loop0
5437 losetup -d /dev/loop0
5438 &lt;/pre&gt;
5439
5440 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5441 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5442
5443 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5444 the new disk image attached, installed grub-pc and linux-image-686 and
5445 set up grub to boot from the disk image. After this, the KVM machines
5446 seem to work just fine.&lt;/p&gt;
5447 </description>
5448 </item>
5449
5450 <item>
5451 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5452 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5453 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5454 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5455 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5456 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5457 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5458 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5459
5460 &lt;p&gt;I still do not know what a correct migration should look like, so I
5461 report any differences between apt and aptitude and hope someone else
5462 can see if anything should be changed.&lt;/p&gt;
5463
5464 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5465
5466 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5467
5468 &lt;blockquote&gt;&lt;p&gt;
5469 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5470 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5471 dmz-cursor-theme empathy empathy-common finger
5472 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5473 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5474 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5475 gnome-cards-data gnome-codec-install gnome-core
5476 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5477 gnome-search-tool gnome-session-canberra gnome-spell
5478 gnome-system-log gnome-themes-extras gnome-themes-more
5479 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5480 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5481 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5482 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5483 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5484 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5485 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5486 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5487 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5488 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5489 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5490 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5491 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5492 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5493 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5494 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5495 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5496 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5497 libmono-security2.0-cil libmono-sharpzip2.84-cil
5498 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5499 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5500 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5501 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5502 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5503 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5504 libxalan2-java libxerces2-java media-player-info mesa-utils
5505 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5506 nautilus-sendto-empathy openoffice.org-writer2latex
5507 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5508 python-aptdaemon python-aptdaemon-gtk python-axiom
5509 python-beautifulsoup python-bugbuddy python-clientform
5510 python-coherence python-configobj python-crypto python-cupshelpers
5511 python-cupsutils python-eggtrayicon python-elementtree
5512 python-epsilon python-evolution python-feedparser python-gdata
5513 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5514 python-gtksourceview2 python-httplib2 python-louie python-mako
5515 python-markupsafe python-mechanize python-nevow python-notify
5516 python-opengl python-openssl python-pam python-pkg-resources
5517 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5518 python-tagpy python-twisted-bin python-twisted-conch
5519 python-twisted-core python-twisted-web python-utidylib python-webkit
5520 python-xdg python-zope.interface remmina remmina-plugin-data
5521 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5522 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5523 software-center svgalibg1 system-config-printer-udev
5524 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5525 totem totem-coherence totem-mozilla totem-plugins
5526 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5527 zip
5528 &lt;/p&gt;&lt;/blockquote&gt;
5529
5530 Installed using apt-get, removed with aptitude
5531
5532 &lt;blockquote&gt;&lt;p&gt;
5533 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5534 epiphany-extensions epiphany-gecko evolution-exchange
5535 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5536 gedit-common gnome-app-install gnome-games gnome-games-data
5537 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5538 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5539 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5540 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5541 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5542 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5543 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5544 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5545 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5546 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5547 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5548 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5549 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5550 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5551 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5552 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5553 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5554 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5555 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5556 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5557 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5558 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5559 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5560 sound-juicer swfdec-gnome system-config-printer totem-common
5561 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5562 &lt;/p&gt;&lt;/blockquote&gt;
5563
5564 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5565
5566 &lt;blockquote&gt;&lt;p&gt;
5567 gstreamer0.10-gnomevfs
5568 &lt;/p&gt;&lt;/blockquote&gt;
5569
5570 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5571
5572 &lt;blockquote&gt;&lt;p&gt;
5573 [nothing]
5574 &lt;/p&gt;&lt;/blockquote&gt;
5575
5576 &lt;p&gt;This is for KDE:&lt;/p&gt;
5577
5578 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5579
5580 &lt;blockquote&gt;&lt;p&gt;
5581 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5582 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5583 ghostscript-x git gnome-audio gnugo granatier gs-common
5584 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5585 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5586 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5587 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5588 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5589 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5590 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5591 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5592 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5593 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5594 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5595 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5596 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5597 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5598 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5599 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5600 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5601 libkrossui4 libmailtools-perl libmime-tools-perl
5602 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5603 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5604 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5605 lirc luatex marble networkstatus noatun-plugins
5606 openoffice.org-writer2latex palapeli palapeli-data parley
5607 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5608 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5609 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5610 ttf-sazanami-gothic
5611 &lt;/p&gt;&lt;/blockquote&gt;
5612
5613 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5614
5615 &lt;blockquote&gt;&lt;p&gt;
5616 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5617 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5618 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5619 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5620 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5621 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5622 kitchensync kiten kjumpingcube klatin klettres klickety klines
5623 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5624 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5625 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5626 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5627 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5628 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5629 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5630 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5631 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5632 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5633 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5634 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5635 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5636 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5637 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5638 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5639 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5640 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5641 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5642 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5643 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5644 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5645 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5646 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5647 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5648 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5649 &lt;/p&gt;&lt;/blockquote&gt;
5650
5651 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5652
5653 &lt;blockquote&gt;&lt;p&gt;
5654 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5655 kdeartwork kdebase kdebase-apps kdebase-workspace
5656 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5657 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5658 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5659 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5660 xscreensaver-screensaver-bsod
5661 &lt;/p&gt;&lt;/blockquote&gt;
5662
5663 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5664
5665 &lt;blockquote&gt;&lt;p&gt;
5666 kdebase-bin konq-plugins konqueror
5667 &lt;/p&gt;&lt;/blockquote&gt;
5668 </description>
5669 </item>
5670
5671 <item>
5672 <title>Gnash buildbot slave and Debian kfreebsd</title>
5673 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5674 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5675 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5676 <description>&lt;p&gt;Answering
5677 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5678 call from the Gnash project&lt;/a&gt; for
5679 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5680 current source, I have set up a virtual KVM machine on the Debian
5681 Edu/Skolelinux virtualization host to test the git source on
5682 Debian/Squeeze. I hope this can help the developers in getting new
5683 releases out more often.&lt;/p&gt;
5684
5685 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5686 I have considered setting up a &lt;a
5687 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5688 machine as well. I have also considered using the kfreebsd
5689 architecture in Debian as a file server in NUUG to get access to the 5
5690 TB zfs volume we currently use to store DV video. Because of this, I
5691 finally got around to do a test installation of Debian/Squeeze with
5692 kfreebsd. Installation went fairly smooth, thought I noticed some
5693 visual glitches in the cdebconf dialogs (black cursor left on the
5694 screen at random locations). Have not gotten very far with the
5695 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5696 fatal problem. Have to spend some more time on it to see if it is
5697 useful as a file server for NUUG. Will try to find time to set up a
5698 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5699 </description>
5700 </item>
5701
5702 <item>
5703 <title>Debian in 3D</title>
5704 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5705 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5706 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5707 <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;
5708
5709 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5710 3D linked in from
5711 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5712 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5713 </description>
5714 </item>
5715
5716 <item>
5717 <title>Software updates 2010-10-24</title>
5718 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5719 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5720 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5721 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5722
5723 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5724 raise money for the project is going well. The lower limit of 10
5725 signers was reached in 24 hours, and so far 13 people have signed it.
5726 More signers and more funding is most welcome, and I am really curious
5727 how far we can get before the time limit of December 24 is reached.
5728 :)&lt;/p&gt;
5729
5730 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5731 about what appear to be a great code coverage tool capable of
5732 generating code coverage stats without any changes to the source code.
5733 It is called
5734 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5735 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5736 It is missing in Debian, but the git source built just fine in Squeeze
5737 after I installed libelf-dev, libdwarf-dev, pkg-config and
5738 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5739 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5740
5741 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5742 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5743 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5744 alpha test release of the Squeeze based Debian Edu /
5745 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5746 release. Give it a try if you need a complete linux solution for your
5747 school, including central infrastructure server, workstations, thin
5748 client servers and diskless workstations. A nice touch added
5749 yesterday is RDP support on the thin client servers, for windows
5750 clients to get a Linux desktop on request.&lt;/p&gt;
5751 </description>
5752 </item>
5753
5754 <item>
5755 <title>Some notes on Flash in Debian and Debian Edu</title>
5756 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5757 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5758 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5759 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5760 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5761 second most popular used package that is missing in Debian. The sixth
5762 most popular is flashplayer-mozilla. This is a clear indication that
5763 working flash is important for Debian users. Around 10 percent of the
5764 users submitting data to popcon.debian.org have this package
5765 installed.&lt;/p&gt;
5766
5767 &lt;p&gt;In the report written by Lars Risan in August 2008
5768&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
5769 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5770 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5771 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5772 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5773 web sites require Flash to work, and lacking working Flash support in
5774 the web browser and the problems with installing it was perceived as a
5775 good reason to stay with Windows.&lt;/p&gt;
5776
5777 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
5778 said to be the retarded cousin that did not really understand
5779 everything you told him but could work fairly well. This was a
5780 comment regarding the problems Linux have with proprietary formats and
5781 non-standard web pages, and is sad because it exposes a fairly common
5782 understanding of whose fault it is if web pages that only work in for
5783 example Internet Explorer 6 fail to work on Firefox, and funny because
5784 it explain very well how annoying it is for users when Linux
5785 distributions do not work with the documents they receive or the web
5786 pages they want to visit.&lt;/p&gt;
5787
5788 &lt;p&gt;This is part of the reason why I believe it is important for Debian
5789 and Debian Edu to have a well working Flash implementation in the
5790 distribution, to get at least popular sites as Youtube and Google
5791 Video to working out of the box. For Squeeze, Debian have the chance
5792 to include the latest version of Gnash that will make this happen, as
5793 the new release 0.8.8 was published a few weeks ago and is resting in
5794 unstable. The new version work with more sites that version 0.8.7.
5795 The Gnash maintainers have asked for a freeze exception, but the
5796 release team have not had time to reply to it yet. I hope they agree
5797 with me that Flash is important for the Debian desktop users, and thus
5798 accept the new package into Squeeze.&lt;/p&gt;
5799 </description>
5800 </item>
5801
5802 <item>
5803 <title>Circular package dependencies harms apt recovery</title>
5804 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
5805 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
5806 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
5807 <description>&lt;p&gt;I discovered this while doing
5808 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
5809 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
5810 in Debian still got circular dependencies, and it is often claimed
5811 that apt and aptitude should be able to handle this just fine, but
5812 some times these dependency loops causes apt to fail.&lt;/p&gt;
5813
5814 &lt;p&gt;An example is from todays
5815 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
5816 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
5817 causes perl-modules to fail to upgrade. The cause is simple. If a
5818 package fail to unpack, then only part of packages with the circular
5819 dependency might end up being unpacked when unpacking aborts, and the
5820 ones already unpacked will fail to configure in the recovery phase
5821 because its dependencies are unavailable.&lt;/p&gt;
5822
5823 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
5824
5825 &lt;blockquote&gt;&lt;pre&gt;
5826 dpkg: dependency problems prevent configuration of perl-modules:
5827 perl-modules depends on perl (&gt;= 5.10.1-1); however:
5828 Version of perl on system is 5.10.0-19lenny2.
5829 dpkg: error processing perl-modules (--configure):
5830 dependency problems - leaving unconfigured
5831 &lt;/pre&gt;&lt;/blockquote&gt;
5832
5833 &lt;p&gt;The perl/perl-modules circular dependency is already
5834 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
5835 hopefully be solved as soon as possible, but it is not the only one,
5836 and each one of these loops in the dependency tree can cause similar
5837 failures. Of course, they only occur when there are bugs in other
5838 packages causing the unpacking to fail, but it is rather nasty when
5839 the failure of one package causes the problem to become worse because
5840 of dependency loops.&lt;/p&gt;
5841
5842 &lt;p&gt;Thanks to
5843 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
5844 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
5845 dependencies
5846 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
5847 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
5848
5849 &lt;p&gt;Todays testing also exposed a bug in
5850 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
5851 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
5852 apt-get and aptitude, the latter possibly caused by some circular
5853 dependency. Reported both to BTS to try to get someone to look at
5854 it.&lt;/p&gt;
5855 </description>
5856 </item>
5857
5858 <item>
5859 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
5860 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
5861 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
5862 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
5863 <description>&lt;p&gt;This is a
5864 &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;
5865 on my
5866 &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
5867 work&lt;/a&gt; on
5868 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
5869 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
5870
5871 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
5872 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5873 and dhcp3-server-ldap in Debian use the LDAP server. The two
5874 implementations are quite different in how they use LDAP.&lt;/p&gt;
5875
5876 To get this information, I started slapd with debugging enabled and
5877 dumped the debug output to a file to get the LDAP searches performed
5878 on a Debian Edu main-server. Here is a summary.
5879
5880 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
5881
5882 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
5883 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
5884 the web.
5885
5886 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
5887 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
5888 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
5889 reverse entries are in two different subtrees in LDAP with a structure
5890 based on the DNS names, as in tjener.intern and
5891 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5892
5893 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5894 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5895 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5896 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5897 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5898 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5899 forward entries, it is looking for attributes named dnsttl, arecord,
5900 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5901 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5902 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5903 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5904 spfrecord and modifytimestamp. For reverse entries it is looking for
5905 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5906 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5907 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5908 ldapsearch commands could look like this:&lt;/p&gt;
5909
5910 &lt;blockquote&gt;&lt;pre&gt;
5911 ldapsearch -h ldap \
5912 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5913 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5914 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5915 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5916 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5917 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5918
5919 ldapsearch -h ldap \
5920 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5921 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
5922 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5923 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5924 srvrecord naptrrecord modifytimestamp
5925 &lt;/pre&gt;&lt;/blockquote&gt;
5926
5927 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
5928 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5929 example LDAP objects used there. In addition to these objects, the
5930 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5931 also exist.&lt;/p&gt;
5932
5933 &lt;blockquote&gt;&lt;pre&gt;
5934 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5935 objectclass: top
5936 objectclass: dnsdomain
5937 objectclass: domainrelatedobject
5938 dc: tjener
5939 arecord: 10.0.2.2
5940 associateddomain: tjener.intern
5941
5942 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5943 objectclass: top
5944 objectclass: dnsdomain2
5945 objectclass: domainrelatedobject
5946 dc: 2
5947 ptrrecord: tjener.intern
5948 associateddomain: 2.2.0.10.in-addr.arpa
5949 &lt;/pre&gt;&lt;/blockquote&gt;
5950
5951 &lt;p&gt;In strict mode, the server behaves differently. When looking for
5952 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
5953 same base as in the tree mode for a object with filter
5954 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
5955 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5956 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5957 naptrrecord and modifytimestamp. For reverse entires it also do a
5958 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
5959 and the requested attributes are associateddomain, dnsttl and
5960 modifytimestamp. In short, in strict mode the objects with ptrrecord
5961 go away, and the arecord attribute in the forward object is used
5962 instead.&lt;/p&gt;
5963
5964 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
5965 like this:&lt;/p&gt;
5966
5967 &lt;blockquote&gt;&lt;pre&gt;
5968 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5969 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5970 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5971 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5972 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5973 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5974
5975 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5976 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
5977 &lt;/pre&gt;&lt;/blockquote&gt;
5978
5979 &lt;p&gt;In addition to the forward and reverse searches , there is also a
5980 search for SOA records, which behave similar to the forward and
5981 reverse lookups.&lt;/p&gt;
5982
5983 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
5984 specify any objectclass names, and instead look for the attributes it
5985 need to generate a DNS reply. This make it able to work with any
5986 objectclass that provide the needed attributes.&lt;/p&gt;
5987
5988 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
5989 dnsdomain2 schemas. The latter is used for reverse entries like
5990 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
5991
5992 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
5993 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5994 attributes) and domainrelatedobject (for associatedDomain). The use
5995 of structural object classes make it impossible to combine these
5996 classes with the object classes used by DHCP.&lt;/p&gt;
5997
5998 &lt;p&gt;There are other schemas that could be used too, for example the
5999 dnszone structural object class used by Gosa and bind-sdb for the DNS
6000 attributes combined with the domainrelatedobject object class, but in
6001 this case some unused attributes would have to be included as well
6002 (zonename and relativedomainname).&lt;/p&gt;
6003
6004 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6005 mode and not use any of the existing objectclasses (dnsdomain,
6006 dnsdomain2 and dnszone) when one want to combine the DNS information
6007 with DHCP information, and instead create a auxiliary object class
6008 defined something like this (using the attributes defined for
6009 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6010
6011 &lt;blockquote&gt;&lt;pre&gt;
6012 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6013 SUP top
6014 AUXILIARY
6015 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6016 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6017 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6018 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6019 A6Record $ DNAMERecord
6020 ))
6021 &lt;/pre&gt;&lt;/blockquote&gt;
6022
6023 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6024 the domainrelatedobject object class, and allow any entity to include
6025 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6026 developers asking for their view on this schema and if they are
6027 interested in providing such schema with PowerDNS, and I hope my
6028 message will be accepted into their mailing list soon.&lt;/p&gt;
6029
6030 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6031
6032 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6033 the object attributes, and then uses the attributes it want. This
6034 make it harder to figure out exactly what attributes are used, but
6035 thanks to the working example in Debian Edu I can at least get an idea
6036 what is needed without having to read the source code.&lt;/p&gt;
6037
6038 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6039 search filter to use to locate the correct dhcpServer entity is
6040 stored. These are the relevant entries from
6041 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6042
6043 &lt;blockquote&gt;&lt;pre&gt;
6044 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6045 ldap-dhcp-server-cn &quot;dhcp&quot;;
6046 &lt;/pre&gt;&lt;/blockquote&gt;
6047
6048 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6049 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6050 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6051 search result is this entry:&lt;/p&gt;
6052
6053 &lt;blockquote&gt;&lt;pre&gt;
6054 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6055 cn: dhcp
6056 objectClass: top
6057 objectClass: dhcpServer
6058 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6059 &lt;/pre&gt;&lt;/blockquote&gt;
6060
6061 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6062 subtree with DHCP configuration. The DHCP configuration subtree base
6063 is located using a base scope search with base &quot;cn=DHCP
6064 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6065 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6066 The search result is this entry:&lt;/p&gt;
6067
6068 &lt;blockquote&gt;&lt;pre&gt;
6069 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6070 cn: DHCP Config
6071 objectClass: top
6072 objectClass: dhcpService
6073 objectClass: dhcpOptions
6074 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6075 dhcpStatements: ddns-update-style none
6076 dhcpStatements: authoritative
6077 dhcpOption: smtp-server code 69 = array of ip-address
6078 dhcpOption: www-server code 72 = array of ip-address
6079 dhcpOption: wpad-url code 252 = text
6080 &lt;/pre&gt;&lt;/blockquote&gt;
6081
6082 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6083 all the DHCP configuration is loaded, it is ready to receive requests.
6084 The subtree in Debian Edu contain objects with object classes
6085 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6086 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6087 and information about netmasks, dynamic range etc. Leaving out the
6088 details here because it is not relevant for the focus of my
6089 investigation, which is to see if it is possible to merge dns and dhcp
6090 related computer objects.&lt;/p&gt;
6091
6092 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6093 of the client (00:00:00:00:00:00 in this example), using a subtree
6094 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6095 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6096 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6097 like:&lt;/p&gt;
6098
6099 &lt;blockquote&gt;&lt;pre&gt;
6100 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6101 cn: hostname
6102 objectClass: top
6103 objectClass: dhcpHost
6104 dhcpHWAddress: ethernet 00:00:00:00:00:00
6105 dhcpStatements: fixed-address hostname
6106 &lt;/pre&gt;&lt;/blockquote&gt;
6107
6108 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6109 The object classes need to have fixed names, and the configuration
6110 need to be stored in a fairly specific LDAP structure. On the
6111 positive side, the invidiual dhcpHost entires can be anywhere without
6112 the DN pointed to by the dhcpServer entries. The latter should make
6113 it possible to group all host entries in a subtree next to the
6114 configuration entries, and this subtree can also be shared with the
6115 DNS server if the schema proposed above is combined with the dhcpHost
6116 structural object class.
6117
6118 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6119
6120 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6121 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6122 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6123 allowing DNS objects to be stored anywhere under the base cn specified
6124 in the configuration.&lt;/p&gt;
6125
6126 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6127 regarding which LDAP schemas to use and which LDAP structure to use.
6128 I guess one could implement ones own schema, as long as the
6129 objectclasses and attributes have the names used, but this do not
6130 really help when the DHCP subtree need to have a fairly fixed
6131 structure.&lt;/p&gt;
6132
6133 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6134 this might work for Debian Edu:&lt;/p&gt;
6135
6136 &lt;blockquote&gt;&lt;pre&gt;
6137 ou=services
6138 cn=machine-info (dhcpService) - dhcpServiceDN points here
6139 cn=dhcp (dhcpServer)
6140 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6141 cn=10.0.2.0 (dhcpSubnet)
6142 cn=group1 (dhcpGroup/dhcpOptions)
6143 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6144 cn=192.168.0.0 (dhcpSubnet)
6145 cn=group1 (dhcpGroup/dhcpOptions)
6146 ou=machines - PowerDNS base points here
6147 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6148 &lt;/pre&gt;&lt;/blockquote&gt;
6149
6150 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6151 entries to be in the dhcpGroup subtrees, the entries can be stored
6152 there instead of a common machines subtree, and the PowerDNS base
6153 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6154
6155 &lt;p&gt;The combined object under the machines subtree would look something
6156 like this:&lt;/p&gt;
6157
6158 &lt;blockquote&gt;&lt;pre&gt;
6159 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6160 dc: hostname
6161 objectClass: top
6162 objectClass: dhcpHost
6163 objectclass: domainrelatedobject
6164 objectclass: dnsDomainAux
6165 associateddomain: hostname.intern
6166 arecord: 10.11.12.13
6167 dhcpHWAddress: ethernet 00:00:00:00:00:00
6168 dhcpStatements: fixed-address hostname.intern
6169 &lt;/pre&gt;&lt;/blockquote&gt;
6170
6171 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6172 machine, as long as the required attributes are available in a
6173 auxiliary object class.&lt;/p&gt;
6174 </description>
6175 </item>
6176
6177 <item>
6178 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6179 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6181 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6182 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6183 DHCP services in Debian Edu to use the same LDAP objects for a given
6184 computer, to avoid the possibility of having a inconsistent state for
6185 a computer in LDAP (as in DHCP but no DNS entry or the other way
6186 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6187
6188 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6189 information finally found a solution that seem to work.&lt;/p&gt;
6190
6191 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6192 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6193 we switch powerdns to use its strict LDAP method (ldap-method=strict
6194 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6195 merged into one while making it impossible to transfer the reverse map
6196 to a slave DNS server.&lt;/p&gt;
6197
6198 &lt;p&gt;If we also replace the object class used to get the DNS related
6199 attributes to one allowing these attributes to be combined with the
6200 dhcphost object class, we can merge the DNS and DHCP entries into one.
6201 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6202 proper OIDs, but that is a minor issue), and tested the setup. It
6203 seem to work.&lt;/p&gt;
6204
6205 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6206 for both DNS and DHCP, and even the LTSP configuration I suggested in
6207 an earlier email. The combined LDAP object will look something like
6208 this:&lt;/p&gt;
6209
6210 &lt;blockquote&gt;&lt;pre&gt;
6211 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6212 cn: hostname
6213 objectClass: dhcphost
6214 objectclass: domainrelatedobject
6215 objectclass: dnsdomainaux
6216 associateddomain: hostname.intern
6217 arecord: 10.11.12.13
6218 dhcphwaddress: ethernet 00:00:00:00:00:00
6219 dhcpstatements: fixed-address hostname
6220 ldapconfigsound: Y
6221 &lt;/pre&gt;&lt;/blockquote&gt;
6222
6223 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6224 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6225 before asking DNS to resolve the fixed-adddress. LTSP will use
6226 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6227
6228 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6229 dhcphost in a different location, to allow us to put the objects
6230 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6231 that. If I can&#39;t figure out a way to do that, we can still get rid of
6232 the hosts subtree and move all its content into the DHCP Config tree
6233 (which probably should be renamed to be more related to the new
6234 content. I suspect cn=dnsdhcp,ou=services or something like that
6235 might be a good place to put it.&lt;/p&gt;
6236
6237 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6238 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6239 </description>
6240 </item>
6241
6242 <item>
6243 <title>Idea for storing LTSP configuration in LDAP</title>
6244 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6245 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6246 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6247 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6248 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6249 clients, and that this can be used to fetch configuration from LDAP if
6250 Debian Edu choose to store configuration there.&lt;/p&gt;
6251
6252 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6253 to get configuration from LDAP. The idea is to look up the MAC
6254 address of the client in LDAP, and look for attributes on the form
6255 ltspconfigsetting=value, and use this to export SETTING=value to the
6256 LTSP clients.&lt;/p&gt;
6257
6258 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6259 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6260 allowing us to store all information about a computer in one place.&lt;/p&gt;
6261
6262 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6263 this approach. A real LDAP schema for the ltspClientAux objectclass
6264 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6265
6266 &lt;blockquote&gt;&lt;pre&gt;
6267 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6268 #
6269 # Fetch LTSP client settings from LDAP based on MAC address
6270 #
6271 # Uses ethernet address as stored in the dhcpHost objectclass using
6272 # the dhcpHWAddress attribute or ethernet address stored in the
6273 # ieee802Device objectclass with the macAddress attribute.
6274 #
6275 # This module is written to be schema agnostic, and only depend on the
6276 # existence of attribute names.
6277 #
6278 # The LTSP configuration variables are saved directly using a
6279 # ltspConfig prefix and uppercasing the rest of the attribute name.
6280 # To set the SERVER variable, set the ltspConfigServer attribute.
6281 #
6282 # Some LDAP schema should be created with all the relevant
6283 # configuration settings. Something like this should work:
6284 #
6285 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6286 # SUP top
6287 # AUXILIARY
6288 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6289
6290 LDAPSERVER=$(debian-edu-ldapserver)
6291 if [ &quot;$LDAPSERVER&quot; ] ; then
6292 LDAPBASE=$(debian-edu-ldapserver -b)
6293 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6294 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6295 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6296 grep &#39;^ltspConfig&#39; | while read attr value ; do
6297 # Remove prefix and convert to upper case
6298 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6299 # bass value on to clients
6300 eval &quot;$attr=$value; export $attr&quot;
6301 done
6302 done
6303 fi
6304 &lt;/pre&gt;&lt;/blockquote&gt;
6305
6306 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6307 the while block might end up in a subshell causing the variables set
6308 there to not show up in ltsp-config, but if that is the case I am sure
6309 the code can be restructured to make sure the variables are passed on.
6310 I expect that can be solved with some testing. :)&lt;/p&gt;
6311
6312 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6313 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6314
6315 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6316 configuration in LDAP that was created around year 2000 by
6317 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6318 Xperience, Inc., 2000&lt;/a&gt;. I found its
6319 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6320 personal home page over at redhat.com.&lt;/p&gt;
6321 </description>
6322 </item>
6323
6324 <item>
6325 <title>jXplorer, a very nice LDAP GUI</title>
6326 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6327 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6328 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6329 <description>&lt;p&gt;Since
6330 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6331 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6332 LDAP GUI that is even better than luma. The java application
6333 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6334 moving LDAP objects and subtrees using drag-and-drop, and can
6335 authenticate using Kerberos. I have only tested the Kerberos
6336 authentication, but do not have a LDAP setup allowing me to rewrite
6337 LDAP with my test user yet. It is
6338 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6339 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6340 have with it is how it handle errors. If something go wrong, its
6341 non-intuitive behaviour require me to go through some query work list
6342 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6343 </description>
6344 </item>
6345
6346 <item>
6347 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6348 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6349 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6350 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6351 <description>&lt;p&gt;Here is a short update on my &lt;a
6352 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6353 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6354 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6355 not reporting the status for KDE, because the upgrade crashes when
6356 aptitude try because of missing conflicts
6357 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6358 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6359
6360 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6361 complete list of the installed packages. Based on this I see these
6362 differences when I did a test run today. As usual, I do not really
6363 know what the correct set of packages would be, but thought it best to
6364 publish the difference.&lt;/p&gt;
6365
6366 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6367
6368 &lt;blockquote&gt;&lt;p&gt;
6369 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6370 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6371 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6372 libgtksourceview-common libpt-1.10.10-plugins-alsa
6373 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6374 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6375 python-4suite-xml python-eggtrayicon python-gtkhtml2
6376 python-gtkmozembed svgalibg1 xserver-xephyr zip
6377 &lt;/p&gt;&lt;/blockquote&gt;
6378
6379 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6380
6381 &lt;blockquote&gt;&lt;p&gt;
6382 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6383 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6384 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6385 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6386 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6387 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6388 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6389 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6390 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6391 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6392 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6393 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6394 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6395 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6396 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6397 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6398 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6399 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6400 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6401 mysql-common swfdec-gnome totem-gstreamer wodim
6402 &lt;/p&gt;&lt;/blockquote&gt;
6403
6404 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6405
6406 &lt;blockquote&gt;&lt;p&gt;
6407 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6408 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6409 xserver-xorg-input-all xserver-xorg-input-evdev
6410 xserver-xorg-input-kbd xserver-xorg-input-mouse
6411 xserver-xorg-input-synaptics xserver-xorg-video-all
6412 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6413 xserver-xorg-video-chips xserver-xorg-video-cirrus
6414 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6415 xserver-xorg-video-glint xserver-xorg-video-i128
6416 xserver-xorg-video-i740 xserver-xorg-video-mach64
6417 xserver-xorg-video-mga xserver-xorg-video-neomagic
6418 xserver-xorg-video-nouveau xserver-xorg-video-nv
6419 xserver-xorg-video-r128 xserver-xorg-video-radeon
6420 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6421 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6422 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6423 xserver-xorg-video-sis xserver-xorg-video-sisusb
6424 xserver-xorg-video-tdfx xserver-xorg-video-tga
6425 xserver-xorg-video-trident xserver-xorg-video-tseng
6426 xserver-xorg-video-vesa xserver-xorg-video-vmware
6427 xserver-xorg-video-voodoo
6428 &lt;/p&gt;&lt;/blockquote&gt;
6429
6430 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6431
6432 &lt;blockquote&gt;&lt;p&gt;
6433 deskbar-applet xserver-xorg xserver-xorg-core
6434 xserver-xorg-input-wacom xserver-xorg-video-intel
6435 xserver-xorg-video-openchrome
6436 &lt;/p&gt;&lt;/blockquote&gt;
6437
6438 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6439 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6440 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6441 No idea when it hits Squeeze, but when it does I hope it will reduce
6442 the difference somewhat.
6443 </description>
6444 </item>
6445
6446 <item>
6447 <title>LUMA, a very nice LDAP GUI</title>
6448 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6449 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6450 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6451 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6452 directory in Debian Edu, and in the process I started to miss a GUI
6453 tool to browse the LDAP tree. The only one I was able to find in
6454 Debian/Squeeze and Lenny is
6455 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6456 be a great tool to get a overview of the current LDAP directory
6457 populated by default in Skolelinux. Thanks to it, I have been able to
6458 find empty and obsolete subtrees, misplaced objects and duplicate
6459 objects. It will be installed by default in Debian/Squeeze. If you
6460 are working with LDAP, give it a go. :)&lt;/p&gt;
6461
6462 &lt;p&gt;I did notice one problem with it I have not had time to report to
6463 the BTS yet. There is no .desktop file in the package, so the tool do
6464 not show up in the Gnome and KDE menus, but only deep down in in the
6465 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6466 released.&lt;/p&gt;
6467
6468 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6469 like to move objects and remove subtrees directly in the GUI, but have
6470 not found a way to do that with LUMA yet. So in the mean time, I use
6471 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6472
6473 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6474 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6475
6476 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6477 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6478 useful GUI alternative. It seem like a good tool, but is unmaintained
6479 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6480 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6481 </description>
6482 </item>
6483
6484 <item>
6485 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6486 <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>
6487 <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>
6488 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6489 <description>&lt;p&gt;A while back, I
6490 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6491 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6492 for storing DNS and DHCP information in LDAP to combine the two sets
6493 of information into one LDAP object representing a computer.&lt;/p&gt;
6494
6495 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6496 the dhcpHost object class auxiliary, to allow it to be combined with
6497 the dNSDomain object class, and thus forming one object for one
6498 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6499
6500 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6501 without also changing the assigned number for the object class, and I
6502 do not know enough about LDAP schema design to do that properly for
6503 Debian Edu.&lt;/p&gt;
6504
6505 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6506 the
6507 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6508 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6509 available today from IETF.&lt;/p&gt;
6510
6511 &lt;pre&gt;
6512 --- dhcp.schema (revision 65192)
6513 +++ dhcp.schema (working copy)
6514 @@ -376,7 +376,7 @@
6515 objectclass ( 2.16.840.1.113719.1.203.6.6
6516 NAME &#39;dhcpHost&#39;
6517 DESC &#39;This represents information about a particular client&#39;
6518 - SUP top
6519 + SUP top AUXILIARY
6520 MUST cn
6521 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6522 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6523 &lt;/pre&gt;
6524
6525 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6526 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6527 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6528
6529 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6530 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6531 </description>
6532 </item>
6533
6534 <item>
6535 <title>Calling tasksel like the installer, while still getting useful output</title>
6536 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6537 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6538 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6539 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6540 installs packages during the normal debian-installer run. Until now,
6541 I have ended up letting tasksel do the work, with the annoying problem
6542 of not getting any feedback at all when something fails (like a
6543 conffile question from dpkg or a download that fails), using code like
6544 this:
6545
6546 &lt;blockquote&gt;&lt;pre&gt;
6547 export DEBIAN_FRONTEND=noninteractive
6548 tasksel --new-install
6549 &lt;/pre&gt;&lt;/blockquote&gt;
6550
6551 This would invoke tasksel, let its automatic task selection pick the
6552 tasks to install, and continue to install the requested tasks without
6553 any output what so ever.
6554
6555 Recently I revisited this problem while working on the automatic
6556 package upgrade testing, because tasksel would some times hang without
6557 any useful feedback, and I want to see what is going on when it
6558 happen. Then it occured to me, I can parse the output from tasksel
6559 when asked to run in test mode, and use that aptitude command line
6560 printed by tasksel then to simulate the tasksel run. I ended up using
6561 code like this:
6562
6563 &lt;blockquote&gt;&lt;pre&gt;
6564 export DEBIAN_FRONTEND=noninteractive
6565 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6566 $cmd
6567 &lt;/pre&gt;&lt;/blockquote&gt;
6568
6569 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6570 --without-recommends -o APT::Install-Recommends=no -y install
6571 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6572 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6573 laptop task and all packages with priority standard , required and
6574 important, just like tasksel would have done it during
6575 installation.&lt;/p&gt;
6576
6577 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6578 install packages without using debconf-apt-progress, for use cases
6579 like this.&lt;/p&gt;
6580 </description>
6581 </item>
6582
6583 <item>
6584 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6585 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6586 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6587 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6588 <description>&lt;p&gt;My
6589 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6590 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6591 finally made the upgrade logs available from
6592 &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;.
6593 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6594 apt and aptitude, and found their differences interesting. This time
6595 I will only focus on their removal plans.&lt;/p&gt;
6596
6597 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6598 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6599 surprising part is that it want to remove xorg and all
6600 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6601 sure why. When asking aptitude to do the same, it want to remove 129
6602 packages, but most of them are library packages I suspect are no
6603 longer needed. Both of them want to remove bluetooth packages, which
6604 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6605
6606 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6607 which seem like a bad idea and xorg the same way as with Gnome. Asking
6608 aptitude for the same, it wants to remove 192 packages, none which are
6609 too surprising.&lt;/p&gt;
6610
6611 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6612 and avoided, and perhaps others as well. Here are the complete list
6613 of planned removals. The complete logs is available from the URL
6614 above. Note if you want to repeat these tests, that the upgrade test
6615 for kde+apt-get hung in the tasksel setup because of dpkg asking
6616 conffile questions. No idea why. I worked around it by using
6617 &#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
6618 continue.&lt;/p&gt;
6619
6620 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6621 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6622 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6623 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6624 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6625 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6626 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6627 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6628 xserver-xorg-input-kbd xserver-xorg-input-mouse
6629 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6630 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6631 xserver-xorg-video-ati xserver-xorg-video-chips
6632 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6633 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6634 xserver-xorg-video-glint xserver-xorg-video-i128
6635 xserver-xorg-video-i740 xserver-xorg-video-imstt
6636 xserver-xorg-video-intel xserver-xorg-video-mach64
6637 xserver-xorg-video-mga xserver-xorg-video-neomagic
6638 xserver-xorg-video-nsc xserver-xorg-video-nv
6639 xserver-xorg-video-openchrome xserver-xorg-video-r128
6640 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6641 xserver-xorg-video-rendition xserver-xorg-video-s3
6642 xserver-xorg-video-s3virge xserver-xorg-video-savage
6643 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6644 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6645 xserver-xorg-video-tga xserver-xorg-video-trident
6646 xserver-xorg-video-tseng xserver-xorg-video-v4l
6647 xserver-xorg-video-vesa xserver-xorg-video-vga
6648 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6649 xulrunner-1.9-gnome-support&lt;/p&gt;
6650
6651 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6652
6653 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6654 djvulibre-desktop finger gnome-app-install gnome-mount
6655 gnome-network-admin gnome-spell gnome-vfs-obexftp
6656 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6657 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6658 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6659 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6660 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6661 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6662 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6663 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6664 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6665 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6666 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6667 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6668 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6669 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6670 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6671 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6672 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6673 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6674 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6675 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6676 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6677 openoffice.org-writer2latex openssl-blacklist p7zip
6678 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6679 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6680 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6681 swfdec-mozilla totem-gstreamer update-manager wodim
6682 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6683 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6684 zip&lt;/p&gt;
6685
6686 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6687
6688 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6689 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6690 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6691 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6692 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6693 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6694 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6695 xserver-xorg-input-kbd xserver-xorg-input-mouse
6696 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6697 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6698 xserver-xorg-video-ati xserver-xorg-video-chips
6699 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6700 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6701 xserver-xorg-video-glint xserver-xorg-video-i128
6702 xserver-xorg-video-i740 xserver-xorg-video-imstt
6703 xserver-xorg-video-intel xserver-xorg-video-mach64
6704 xserver-xorg-video-mga xserver-xorg-video-neomagic
6705 xserver-xorg-video-nsc xserver-xorg-video-nv
6706 xserver-xorg-video-openchrome xserver-xorg-video-r128
6707 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6708 xserver-xorg-video-rendition xserver-xorg-video-s3
6709 xserver-xorg-video-s3virge xserver-xorg-video-savage
6710 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6711 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6712 xserver-xorg-video-tga xserver-xorg-video-trident
6713 xserver-xorg-video-tseng xserver-xorg-video-v4l
6714 xserver-xorg-video-vesa xserver-xorg-video-vga
6715 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6716
6717 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6718 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6719 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6720 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6721 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6722 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6723 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6724 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6725 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6726 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6727 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6728 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6729 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6730 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6731 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6732 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6733 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6734 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6735 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6736 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6737 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6738 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6739 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6740 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6741 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6742 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6743 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6744 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6745 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6746 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6747 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6748 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6749 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6750 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6751 texlive-common texlive-doc-base texlive-fonts-recommended
6752 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6753 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6754 xulrunner-1.9&lt;/p&gt;
6755
6756 </description>
6757 </item>
6758
6759 <item>
6760 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6761 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6762 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6763 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6764 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6765 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6766 have been discovered and reported in the process
6767 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6768 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6769 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6770 kdebase-workspace-data), and to get a more regular testing going on, I
6771 am working on a script to automate the test.&lt;/p&gt;
6772
6773 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6774 Gnome or KDE desktop installation inside the chroot before upgrading
6775 it. To ensure no services are started in the chroot, a policy-rc.d
6776 script is inserted. To make sure tasksel believe it is to install a
6777 desktop on a laptop, the tasksel tests are replaced in the chroot
6778 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
6779
6780 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6781 currently always fail because udev refuses to upgrade with the kernel
6782 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6783 is created. The bug report
6784 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
6785 this problem do not trigger in a chroot, but I touch the file anyway
6786 to make sure the upgrade go well. Testing on virtual and real
6787 hardware have failed me because of udev so far, and creating this file
6788 do the trick in such settings anyway. This is a
6789 &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
6790 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
6791 maintainer because he lack the resources to rewrite udev to keep
6792 working with old kernels or something like that. I really wish the
6793 udev upstream would keep udev backwards compatible, to avoid such
6794 upgrade problem, but given that they fail to do so, I guess
6795 documenting the way out of this mess is the best option we got for
6796 Debian Squeeze.&lt;/p&gt;
6797
6798 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
6799 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
6800 trick:&lt;/p&gt;
6801
6802 &lt;blockquote&gt;&lt;pre&gt;
6803 #!/bin/sh
6804 set -ex
6805
6806 if [ &quot;$1&quot; ] ; then
6807 desktop=$1
6808 else
6809 desktop=gnome
6810 fi
6811
6812 from=lenny
6813 to=squeeze
6814
6815 exec &amp;lt; /dev/null
6816 unset LANG
6817 mirror=http://ftp.skolelinux.org/debian
6818 tmpdir=chroot-$from-upgrade-$to-$desktop
6819 fuser -mv .
6820 debootstrap $from $tmpdir $mirror
6821 chroot $tmpdir aptitude update
6822 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
6823 #!/bin/sh
6824 exit 101
6825 EOF
6826 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6827 exit_cleanup() {
6828 umount $tmpdir/proc
6829 }
6830 mount -t proc proc $tmpdir/proc
6831 # Make sure proc is unmounted also on failure
6832 trap exit_cleanup EXIT INT
6833
6834 chroot $tmpdir aptitude -y install debconf-utils
6835
6836 # Make sure tasksel autoselection trigger. It need the test scripts
6837 # to return the correct answers.
6838 echo tasksel tasksel/desktop multiselect $desktop | \
6839 chroot $tmpdir debconf-set-selections
6840
6841 # Include the desktop and laptop task
6842 for test in desktop laptop ; do
6843 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
6844 #!/bin/sh
6845 exit 2
6846 EOF
6847 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6848 done
6849
6850 DEBIAN_FRONTEND=noninteractive
6851 DEBIAN_PRIORITY=critical
6852 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6853 chroot $tmpdir tasksel --new-install
6854
6855 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
6856 chroot $tmpdir aptitude update
6857 touch $tmpdir/etc/udev/kernel-upgrade
6858 chroot $tmpdir aptitude -y dist-upgrade
6859 fuser -mv
6860 &lt;/pre&gt;&lt;/blockquote&gt;
6861
6862 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
6863 with aptitude, but I have not had time to look at how they behave
6864 differently so far. I hope to get a cron job running to do the test
6865 regularly and post the result on the web. The Gnome upgrade currently
6866 work, while the KDE upgrade fail because of the bug in
6867 kdebase-workspace-data&lt;/p&gt;
6868
6869 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
6870 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
6871 post, so I will refrain from trying. I can report that for Gnome,
6872 aptitude report 760 packages upgraded, 448 newly installed, 129 to
6873 remove and 1 not upgraded and 1024MB need to be downloaded while for
6874 KDE the same numbers are 702 packages upgraded, 507 newly installed,
6875 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
6876
6877 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
6878 is able to migrate to dependency based boot sequencing and parallel
6879 booting without a hitch. Was unsure if there were still bugs with
6880 packages failing to clean up their obsolete init.d script during
6881 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6882 packages.&lt;/p&gt;
6883 </description>
6884 </item>
6885
6886 <item>
6887 <title>Upstart or sysvinit - as init.d scripts see it</title>
6888 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
6889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
6890 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
6891 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6892 scripts to migrate (some of) their operations to upstart job while
6893 keeping the init.d for hurd and kfreebsd. The packages with such
6894 needs will need a way to get their init.d scripts to behave
6895 differently when used with sysvinit and with upstart. Because of
6896 this, I had a look at the environment variables set when a init.d
6897 script is running under upstart, and when it is not.&lt;/p&gt;
6898
6899 &lt;p&gt;With upstart, I notice these environment variables are set when a
6900 script is started from rcS.d/ (ignoring some irrelevant ones like
6901 COLUMNS):&lt;/p&gt;
6902
6903 &lt;blockquote&gt;&lt;pre&gt;
6904 DEFAULT_RUNLEVEL=2
6905 previous=N
6906 PREVLEVEL=
6907 RUNLEVEL=
6908 runlevel=S
6909 UPSTART_EVENTS=startup
6910 UPSTART_INSTANCE=
6911 UPSTART_JOB=rc-sysinit
6912 &lt;/pre&gt;&lt;/blockquote&gt;
6913
6914 &lt;p&gt;With sysvinit, these environment variables are set for the same
6915 script.&lt;/p&gt;
6916
6917 &lt;blockquote&gt;&lt;pre&gt;
6918 INIT_VERSION=sysvinit-2.88
6919 previous=N
6920 PREVLEVEL=N
6921 RUNLEVEL=S
6922 runlevel=S
6923 &lt;/pre&gt;&lt;/blockquote&gt;
6924
6925 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
6926 sysvinit are not set by upstart. Not sure if it is intentional or not
6927 to not be compatible with sysvinit in this regard.&lt;/p&gt;
6928
6929 &lt;p&gt;For scripts needing to behave differently when upstart is used,
6930 looking for the UPSTART_JOB environment variable seem to be a good
6931 choice.&lt;/p&gt;
6932 </description>
6933 </item>
6934
6935 <item>
6936 <title>A manual for standards wars...</title>
6937 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
6938 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
6939 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
6940 <description>&lt;p&gt;Via the
6941 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
6942 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
6943 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
6944 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
6945 following the standards wars of today.&lt;/p&gt;
6946 </description>
6947 </item>
6948
6949 <item>
6950 <title>Sitesummary tip: Listing computer hardware models used at site</title>
6951 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
6952 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
6953 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
6954 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
6955 to get a list of the machine types in use thanks to the DMI
6956 information extracted from each machine. The script to do so is
6957 included in the sitesummary package, and here is example output from
6958 the Skolelinux build servers:&lt;/p&gt;
6959
6960 &lt;blockquote&gt;&lt;pre&gt;
6961 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6962 vendor count
6963 Dell Computer Corporation 1
6964 PowerEdge 1750 1
6965 IBM 1
6966 eserver xSeries 345 -[8670M1X]- 1
6967 Intel 2
6968 [no-dmi-info] 3
6969 maintainer:~#
6970 &lt;/pre&gt;&lt;/blockquote&gt;
6971
6972 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
6973 provided in each machine. Here there are Intel machines without model
6974 information listed with Intel as vendor and no model, and virtual Xen
6975 machines listed as [no-dmi-info]. One can add -l as a command line
6976 option to list the individual machines.&lt;/p&gt;
6977
6978 &lt;p&gt;A larger list is
6979 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
6980 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
6981 provide the basic sitesummary report publicly. In their report there
6982 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
6983 their machines, and as sitesummary is available in both distributions,
6984 it is trivial to get all of them to report to the same central
6985 collector.&lt;/p&gt;
6986 </description>
6987 </item>
6988
6989 <item>
6990 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
6991 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
6992 <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>
6993 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
6994 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
6995 start at boot when an NVidia video card is used is handled. The
6996 problem seem to be that the nvidia X.org driver uses a long time to
6997 initialize, and this duration is longer than kdm is configured to
6998 wait.&lt;/p&gt;
6999
7000 &lt;p&gt;I came across two bugs related to this issue,
7001 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7002 against initscripts and passed on to nvidia-glx when it became obvious
7003 that the nvidia drivers were involved, and
7004 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7005 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7006
7007 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7008 problem nvidia video card owners experience and make sure the Debian
7009 distribution work out of the box for these users. The nvidia driver
7010 maintainers expect kdm to be set up to wait longer, while kdm expect
7011 the nvidia driver maintainers to fix the driver to start faster, and
7012 while they wait for each other I guess the users end up switching to a
7013 distribution that work for them. I have no idea what the solution is,
7014 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7015
7016 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7017 </description>
7018 </item>
7019
7020 <item>
7021 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7022 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7023 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7024 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7025 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7026 The feature seem to hold up pretty well, but three fairly serious
7027 issues are known and should be solved:
7028
7029 &lt;p&gt;&lt;ul&gt;
7030
7031 &lt;li&gt;The wicd package seen to
7032 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7033 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7034 parallel booting is enabled. No idea why, but the wicd maintainer
7035 seem to be on the case.&lt;/li&gt;
7036
7037 &lt;li&gt;The nvidia X driver seem to
7038 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7039 triggered more easily when parallel booting is in effect. The
7040 maintainer is on the case.&lt;/li&gt;
7041
7042 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7043 sequencing (the shutdown is broken) when old file-rc users
7044 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7045 sysv-rc. One way to solve it would be for file-rc to create
7046 /etc/init.d/.legacy-bootordering, and another is to try to make
7047 sysv-rc more robust. Will investigate some more and probably upload a
7048 workaround in sysv-rc to help those trying to move from file-rc to
7049 sysv-rc get a working shutdown.&lt;/li&gt;
7050
7051 &lt;/ul&gt;&lt;/p&gt;
7052
7053 &lt;p&gt;All in all not many surprising issues, and all of them seem
7054 solvable before Squeeze is released. In addition to these there are
7055 some packages with bugs in their dependencies and run level settings,
7056 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7057
7058 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7059 the BTS, please usertag the report to get it to show up at
7060 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7061 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7062
7063 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7064 </description>
7065 </item>
7066
7067 <item>
7068 <title>More flexible firmware handling in debian-installer</title>
7069 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7070 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7071 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7072 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7073 found time today to return to the project. Having to spend less time
7074 working dependency based boot in debian, as it is almost complete now,
7075 definitely helped freeing some time.&lt;/p&gt;
7076
7077 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7078 include some firmware packages on the Debian Edu CDs, those needed to
7079 get disk and network controllers working. Without having these
7080 firmware packages available during installation, it is impossible to
7081 install Debian Edu on the given machine, and because our target group
7082 are non-technical people, asking them to provide firmware packages on
7083 an external medium is a support pain. Initially, I expected it to be
7084 enough to include the firmware packages on the CD to get
7085 debian-installer to find and use them. This proved to be wrong.
7086 Next, I hoped it was enough to symlink the relevant firmware packages
7087 to some useful location on the CD (tried /cdrom/ and
7088 /cdrom/firmware/). This also proved to not work, and at this point I
7089 found time to look at the debian-installer code to figure out what was
7090 going to work.&lt;/p&gt;
7091
7092 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7093 look revealed that it would only look for firmware packages outside
7094 the installation media, so the CD was never checked for firmware
7095 packages. It would only check USB sticks, floppies and other
7096 &quot;external&quot; media devices. Today I changed it to also look in the
7097 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7098 solve the problem I ran into with Debian edu. I also changed it to
7099 look in /firmware/, to make sure the installer also find firmware
7100 provided in the initrd when booting the installer via PXE, to allow us
7101 to provide the same feature in the PXE setup included in Debian
7102 Edu.&lt;/p&gt;
7103
7104 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7105 activated without asking if the license is accepted, I extended
7106 hw-detect to look for preinst scripts in the firmware packages, and
7107 run these before activating the firmware during installation. The
7108 license question is asked using debconf in the preinst, so this should
7109 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7110
7111 &lt;p&gt;If you want to discuss the details of these features, please
7112 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7113 </description>
7114 </item>
7115
7116 <item>
7117 <title>Parallellized boot is now the default in Debian/unstable</title>
7118 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7119 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7120 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7121 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7122 Debian/unstable for machines using dependency based boot sequencing.
7123 Apparently the testing of concurrent booting has been wider than
7124 expected, if I am to believe the
7125 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7126 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7127 with the feature this weekend, to give us some time to detect any
7128 remaining problems before Squeeze is frozen. If serious problems are
7129 detected, it is simple to change the default back to sequential boot.
7130 The upload of the new sysvinit package also activate a new upstream
7131 version.&lt;/p&gt;
7132
7133 More information about
7134 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7135 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7136 currently possible to disable parallel booting when one run into
7137 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7138
7139 &lt;blockquote&gt;&lt;pre&gt;
7140 CONCURRENCY=none
7141 &lt;/pre&gt;&lt;/blockquote&gt;
7142
7143 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7144 the BTS, please usertag the report to get it to show up at
7145 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7146 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7147 </description>
7148 </item>
7149
7150 <item>
7151 <title>Sitesummary tip: Listing MAC address of all clients</title>
7152 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7153 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7154 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7155 <description>&lt;p&gt;In the recent Debian Edu versions, the
7156 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7157 system&lt;/a&gt; is used to keep track of the machines in the school
7158 network. Each machine will automatically report its status to the
7159 central server after boot and once per night. The network setup is
7160 also reported, and using this information it is possible to get the
7161 MAC address of all network interfaces in the machines. This is useful
7162 to update the DHCP configuration.&lt;/p&gt;
7163
7164 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7165 ist all MAC addresses of all machines reporting to sitesummary. Run
7166 this on the collector host:&lt;/p&gt;
7167
7168 &lt;blockquote&gt;&lt;pre&gt;
7169 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7170 &lt;/pre&gt;&lt;/blockquote&gt;
7171
7172 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7173 line per machine and with space between the MAC addresses.&lt;/p&gt;
7174
7175 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7176 addresses for hosts, it would be possible to extend this to fetch
7177 machine information from sitesummary and update the DHCP and DNS
7178 tables in LDAP using this information. Such tool is unfortunately not
7179 written yet.&lt;/p&gt;
7180 </description>
7181 </item>
7182
7183 <item>
7184 <title>systemd, an interesting alternative to upstart</title>
7185 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7186 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7187 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7188 <description>&lt;p&gt;The last few days a new boot system called
7189 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7190 has been
7191 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7192
7193 to the free software world. I have not yet had time to play around
7194 with it, but it seem to be a very interesting alternative to
7195 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7196 a good alternative for Debian when we are able to switch to an event
7197 based boot system. Tollef is
7198 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7199 systemd into Debian, and I look forward to seeing how well it work. I
7200 like the fact that systemd handles init.d scripts with dependency
7201 information natively, allowing them to run in parallel where upstart
7202 at the moment do not.&lt;/p&gt;
7203
7204 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7205 platform support. It only work on recent Linux kernels, and also need
7206 some new kernel features enabled to function properly. This means
7207 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7208 system. Not sure how that will be handled if systemd proves to be the
7209 way forward.&lt;/p&gt;
7210
7211 &lt;p&gt;In the mean time, based on the
7212 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7213 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7214 decided to enable full parallel booting as the default in Debian as
7215 soon as possible (probably this weekend or early next week), to see if
7216 there are any remaining serious bugs in the init.d dependencies. A
7217 new version of the sysvinit package implementing this change is
7218 already in experimental. If all go well, Squeeze will be released
7219 with parallel booting enabled by default.&lt;/p&gt;
7220 </description>
7221 </item>
7222
7223 <item>
7224 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7225 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7226 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7227 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7228 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7229 complete, so complete that it is actually possible to run all the
7230 init.d scripts in parallell based on these dependencies. If you want
7231 to test your Squeeze system, make sure
7232 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7233 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7234 /etc/default/rcS:&lt;/p&gt;
7235
7236 &lt;blockquote&gt;&lt;pre&gt;
7237 CONCURRENCY=makefile
7238 &lt;/pre&gt;&lt;/blockquote&gt;
7239
7240 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7241 scripts in parallel using the dependency information stored in
7242 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7243 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7244 to try to start the kdm and gdm scripts as early as possible, and will
7245 start the facilities required by kdm or gdm as early as possible to
7246 make this happen.&lt;/p&gt;
7247
7248 &lt;p&gt;Give it a try, and see if you like the result. If some services
7249 fail to start properly, it is most likely because they have incomplete
7250 init.d script dependencies in their startup script (or some of their
7251 dependent scripts have incomplete dependencies). Report bugs and get
7252 the package maintainers to fix it. :)&lt;/p&gt;
7253
7254 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7255 manage to get the init.d script dependencies complete and correct. I
7256 expect we will get there in Squeeze+1, if we get manage to test and
7257 fix the remaining issues.&lt;/p&gt;
7258
7259 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7260 the BTS, please usertag the report to get it to show up at
7261 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7262 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7263 </description>
7264 </item>
7265
7266 <item>
7267 <title>Debian has switched to dependency based boot sequencing</title>
7268 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7269 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7270 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7271 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7272 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7273 have been migrated to using dependency based boot sequencing. This
7274 conclude work me and others have been doing for the last three days.
7275 It feels great to see this finally part of the default Debian
7276 installation. Now we just need to weed out the last few problems that
7277 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7278
7279 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7280 fixing the more fundamental problem of handing the event based
7281 non-predictable kernel in the early boot.&lt;/p&gt;
7282 </description>
7283 </item>
7284
7285 <item>
7286 <title>Taking over sysvinit development</title>
7287 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7288 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7289 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7290 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7291 the existing sysvinit upstream developer, I decided a few weeks ago to
7292 take over the package and become the new upstream. The number of
7293 patches to track for the Debian package was becoming a burden, and the
7294 lack of synchronization between the distribution made it hard to keep
7295 the package up to date.&lt;/p&gt;
7296
7297 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7298 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7299 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7300 and Fedora), based on the patches currently in use in these
7301 distributions. We Debian maintainers plan to move to this tarball as
7302 the new upstream as soon as we find time to do the merge. Since the
7303 new tarball was created, we agreed with Werner at SuSe to make a new
7304 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7305 development there. The project is registered and currently waiting
7306 for approval by the Savannah administrators, and as soon as it is
7307 approved, we will import the old versions from svn and continue
7308 working on the future release.&lt;/p&gt;
7309
7310 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7311 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7312 </description>
7313 </item>
7314
7315 <item>
7316 <title>Debian boots quicker and quicker</title>
7317 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7318 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7319 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7320 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7321 people involved in the boot system on Debian and Ubuntu, to see if we
7322 could find more ways to speed up the boot system. This was an Ubuntu
7323 funded
7324 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7325 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7326 of boot systems, and ways to handle the increasing number of boot
7327 issues introduced by the Linux kernel becoming more and more
7328 asynchronous and event base. The Ubuntu approach using udev and
7329 upstart might be a good way forward. Time will show.&lt;/p&gt;
7330
7331 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7332 process in Debian. All of these should be applied to get a quick
7333 boot:&lt;/p&gt;
7334
7335 &lt;ul&gt;
7336
7337 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7338
7339 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7340 clock is in UTC.&lt;/li&gt;
7341
7342 &lt;li&gt;Install and activate the insserv package to enable
7343 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7344 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7345
7346 &lt;/ul&gt;
7347
7348 These points are based on the Google summer of code work done by
7349 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7350 Villegas&lt;/a&gt;.
7351
7352 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7353 unstable yesterday. When we tested it, we were able to cut 6 seconds
7354 from the boot sequence. It depend on very correct dependency
7355 declaration in all init.d scripts, so I expect us to find edge cases
7356 where the dependences in some scripts are slightly wrong when we start
7357 using this.&lt;/p&gt;
7358
7359 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7360 introduced by Raphael Geissert today, one that could affect the
7361 startup speed as well. Instead of starting some scripts concurrently
7362 from rcS.d/ and another set of scripts from rc2.d/, it would be
7363 possible to run a of them in the same process. A quick way to test
7364 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7365 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7366 </description>
7367 </item>
7368
7369 <item>
7370 <title>BSAs påstander om piratkopiering møter motstand</title>
7371 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7373 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7374 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7375 programvareselskapene som Microsoft og Apple, publisert en rapport der
7376 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7377 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7378 dager siden kom
7379 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7380 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7381 dagene. Et spesielt interessant kommentar fra Sverige,
7382 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7383 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7384
7385 &lt;blockquote&gt;
7386 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7387 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7388 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7389 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7390 &lt;/blockquote&gt;
7391
7392 &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
7393 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7394 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7395 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7396 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7397
7398 &lt;p&gt;Fant lenkene via &lt;a
7399 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7400 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7401 </description>
7402 </item>
7403
7404 <item>
7405 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7406 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7407 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7408 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7409 <description>&lt;p&gt;Kom over
7410 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7411 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7412 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7413 jobber til daglig. En rask opptelling forteller meg at vi har 490
7414 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7415 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7416 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7417 </description>
7418 </item>
7419
7420 <item>
7421 <title>Kryptert harddisk - naturligvis</title>
7422 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7423 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7424 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7425 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7426 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7427 når en tar tap av arbeidstid, fortrolige dokumenter,
7428 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7429 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7430 til at jeg har kryptert harddisken på både kontormaskinen og min
7431 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7432 komme på avveie, den første informasjon relatert til jobben min ved
7433 Universitetet i Oslo, og den andre relatert til blant annet
7434 foreningsarbeide. Kryptering av diskene gjør at det er lite
7435 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7436 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7437 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7438 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7439 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7440 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7441 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7442 det er gjort slik jeg gjør det er minimale, og gevinstene er
7443 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7444 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7445
7446 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7447 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7448 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7449 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7450 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7451 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7452 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7453 betydelige.&lt;/p&gt;
7454 </description>
7455 </item>
7456
7457 <item>
7458 <title>Two projects that have improved the quality of free software a lot</title>
7459 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7460 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7461 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7462 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7463 quality of free software, and I wanted to mention both in case someone
7464 do not yet know them.&lt;/p&gt;
7465
7466 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7467 tool to detect and expose errors in the memory handling of programs.
7468 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7469 and it will report any problems on stdout. It is even better if the
7470 program include debug information. With debug information, it is able
7471 to report the source file name and line number where the problem
7472 occurs. It can report things like &#39;reading past memory block in file
7473 X line N, the memory block was allocated in file Y, line M&#39;, and
7474 &#39;using uninitialised value in control logic&#39;. This tool has made it
7475 trivial to investigate reproducible crash bugs in programs, and have
7476 reduced the number of this kind of bugs in free software a lot.
7477
7478 &lt;p&gt;The second one is
7479 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7480 a source code checker. It is able to process the source of a program
7481 and find problems in the logic without running the program. It
7482 started out as the Stanford Checker and became well known when it was
7483 used to find bugs in the Linux kernel. It is now a commercial tool
7484 and the company behind it is running
7485 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7486 free software community, where a lot of free software projects get
7487 their source checked for free. Several thousand defects have been
7488 found and fixed so far. It can find errors like &#39;lock L taken in file
7489 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7490 Y lines O to P can never be executed&#39;. The projects included in the
7491 community service project have managed to get rid of a lot of
7492 reliability problems thanks to Coverity.&lt;/p&gt;
7493
7494 &lt;p&gt;I believe tools like this, that are able to automatically find
7495 errors in the source, are vital to improve the quality of software and
7496 make sure we can get rid of the crashing and failing software we are
7497 surrounded by today.&lt;/p&gt;
7498 </description>
7499 </item>
7500
7501 <item>
7502 <title>No patch is not better than a useless patch</title>
7503 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7504 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7505 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7506 <description>&lt;p&gt;Julien Blache
7507 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7508 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7509 patch allow one to discuss a concrete and proposed solution, and also
7510 prove that the issue at hand is important enough for someone to spent
7511 time on fixing it. No patch do not provide any of these positive
7512 properties.&lt;/p&gt;
7513 </description>
7514 </item>
7515
7516 <item>
7517 <title>Standardize on protocols and formats, not vendors and applications</title>
7518 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7519 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7520 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7521 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7522 very good one to form a long lived computer infrastructure. It is the
7523 simple one, lost by many in todays computer industry: Standardize on
7524 open network protocols and open exchange/storage formats, not applications.
7525 Applications come and go, while protocols and files tend to stay, and
7526 thus one want to make it easy to change application and vendor, while
7527 avoiding conversion costs and locking users to a specific platform or
7528 application.&lt;/p&gt;
7529
7530 &lt;p&gt;This approach make it possible to replace the client applications
7531 independently of the server applications. One can even allow users to
7532 use several different applications as long as they handle the selected
7533 protocol and format. In the normal case, only one client application
7534 is recommended and users only get help if they choose to use this
7535 application, but those that want to deviate from the easy path are not
7536 blocked from doing so.&lt;/p&gt;
7537
7538 &lt;p&gt;It also allow us to replace the server side without forcing the
7539 users to replace their applications, and thus allow us to select the
7540 best server implementation at any moment, when scale and resouce
7541 requirements change.&lt;/p&gt;
7542
7543 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7544 open formats, but I would never recommend standardizing on a single
7545 application that do not use open network protocol or open formats.&lt;/p&gt;
7546 </description>
7547 </item>
7548
7549 <item>
7550 <title>Returning from Skolelinux developer gathering</title>
7551 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7552 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7553 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7554 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7555 Edu/Skolelinux development gathering. I got a bit done tuning the
7556 desktop, and looked into the dynamic service location protocol
7557 implementation avahi. It look like it could be useful for us. Almost
7558 30 people participated, and I believe it was a great environment to
7559 get to know the Skolelinux system. Walter Bender, involved in the
7560 development of the Sugar educational platform, presented his stuff and
7561 also helped me improve my OLPC installation. He also showed me that
7562 his Turtle Art application can be used in standalone mode, and we
7563 agreed that I would help getting it packaged for Debian. As a
7564 standalone application it would be great for Debian Edu. We also
7565 tried to get the video conferencing working with two OLPCs, but that
7566 proved to be too hard for us. The application seem to need more work
7567 before it is ready for me. I look forward to getting home and relax
7568 now. :)&lt;/p&gt;
7569 </description>
7570 </item>
7571
7572 <item>
7573 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7574 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7575 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7576 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7577 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7578 optimal. There is RFC 2307 documenting one way to store NIS maps in
7579 LDAP, and a modified version of this normally called RFC 2307bis, with
7580 some modifications to be compatible with Active Directory. The RFC
7581 specification handle the content of a lot of system databases, but do
7582 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7583
7584 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7585 we would like to store information about users, SMB clients/hosts,
7586 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7587 and LTSP configuration in LDAP. These objects have a lot in common,
7588 but with the current LDAP schemas it is not possible to have one
7589 object per entity. For example, one need to have at least three LDAP
7590 objects for a given computer, one with the SMB related stuff, one with
7591 DNS information and another with DHCP information. The schemas
7592 provided for DNS and DHCP are impossible to combine into one LDAP
7593 object. In addition, it is impossible to implement quick queries for
7594 netgroup membership, because of the way NIS triples are implemented.
7595 It just do not scale. I believe it is time for a few RFC
7596 specifications to cleam up this mess.&lt;/p&gt;
7597
7598 &lt;p&gt;I would like to have one LDAP object representing each computer in
7599 the network, and this object can then keep the SMB (ie host key), DHCP
7600 (mac address/name) and DNS (name/IP address) settings in one place.
7601 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7602
7603 &lt;p&gt;I would also like to have a quick way to map from a user or
7604 computer and to the net group this user or computer is a member.&lt;/p&gt;
7605
7606 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7607 in this regard, and the unix side need to catch up. Time to start a
7608 new IETF work group?&lt;/p&gt;
7609 </description>
7610 </item>
7611
7612 <item>
7613 <title>Endelig er Debian Lenny gitt ut</title>
7614 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7615 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7616 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7617 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7618 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7619 Et langt steg videre for Debian-prosjektet, og en rekke nye
7620 programpakker blir nå tilgjengelig for de av oss som bruker den
7621 stabile utgaven av Debian. Neste steg er nå å få
7622 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7623 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7624 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7625 slippes løs på skolene. Takk til alle debian-utviklerne som har
7626 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7627 bootsekvens tilgjengelig i stabil utgave, vha pakken
7628 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7629 </description>
7630 </item>
7631
7632 <item>
7633 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7634 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7635 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7636 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7637 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7638 Oslo. Most of Saturday was used for the general assemly for the
7639 member organization, but the rest of the weekend I used to tune the
7640 LTSP installation. LTSP now work out of the box on the 10-network.
7641 Acer Aspire One proved to be a very nice thin client, with both
7642 screen, mouse and keybard in a small box. Was working on getting the
7643 diskless workstation setup configured out of the box, but did not
7644 finish it before the weekend was up.&lt;/p&gt;
7645
7646 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7647 the Brazilian group, so that will have to wait for the next
7648 development gathering. Would love to have the Debian Edu installer
7649 automatically detect and configure a multiseat setup when it find one
7650 of these cards.&lt;/p&gt;
7651 </description>
7652 </item>
7653
7654 <item>
7655 <title>The sorry state of multimedia browser plugins in Debian</title>
7656 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7657 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7658 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7659 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7660 plugins available in Debian Lenny, to see which one we should use by
7661 default in Debian Edu. We need an embedded video playing plugin with
7662 control buttons to pause or stop the video, and capable of streaming
7663 all the multimedia content available on the web. The test results and
7664 notes are available on
7665 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7666 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7667 fill this need. My personal video player favorite, VLC, has a really
7668 bad plugin which fail on a lot of the test pages. A lot of the MIME
7669 types I would expect to work with any free software player (like
7670 video/ogg), just do not work. And simple formats like the
7671 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7672 totem and vlc plugins. I hope the situation will improve soon. No
7673 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7674
7675 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7676 be the only one fitting our needs. :/&lt;/p&gt;
7677 </description>
7678 </item>
7679
7680 </channel>
7681 </rss>