]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
0e8d039717b641ec81c77a00e1ce9aab760df3a3
[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>Debian Jessie, PXE and automatic firmware installation</title>
11 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
13 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
14 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
15 problem that the WiFi card require some firmware to work properly.
16 And it has been a pain to fix this using preseeding in Debian.
17 Normally something more is needed. But thanks to
18 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
19 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
20 to do this using simple preseeding.&lt;/p&gt;
21
22 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
23 firmware for the hardware found in the machine (actually, requested by
24 the kernel modules for the hardware). (It can also install user space
25 programs supporting the hardware detected, but that is not the focus
26 of this story.)&lt;/p&gt;
27
28 &lt;p&gt;To get this working in the default installation, two preeseding
29 values are needed. First, the isenkram-cli package must be installed
30 into the target chroot (aka the hard drive) before tasksel is executed
31 in the pkgsel step of the debian-installer system. This is done by
32 preseeding the base-installer/includes debconf value to include the
33 isenkram-cli package. The package name is next passed to debootstrap
34 for installation. With the isenkram-cli package in place, tasksel
35 will automatically use the isenkram tasks to detect hardware specific
36 packages for the machine being installed and install them, because
37 isenkram-cli contain tasksel tasks.&lt;/p&gt;
38
39 &lt;p&gt;Second, one need to enable the non-free APT repository, because
40 most firmware unfortunately is non-free. This is done by preseeding
41 the apt-mirror-setup step. This is unfortunate, but for a lot of
42 hardware it is the only option in Debian.&lt;/p&gt;
43
44 &lt;p&gt;The end result is two lines needed in your preseeding file to get
45 firmware installed automatically by the installer:&lt;/p&gt;
46
47 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
48 base-installer base-installer/includes string isenkram-cli
49 apt-mirror-setup apt-setup/non-free boolean true
50 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
51
52 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
53 both firmware and user space packages when using this method. It also
54 do not work well, so use version 0.15 or later. Installing both
55 firmware and user space packages might give you a bit more than you
56 want, so I decided to split the tasksel task in two, one for firmware
57 and one for user space programs. The firmware task is enabled by
58 default, while the one for user space programs is not. This split is
59 implemented in the package currently in unstable.&lt;/p&gt;
60
61 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
62 this recipe work for you. :)&lt;/p&gt;
63
64 &lt;p&gt;So, I bet you are wondering, how can this work. First and
65 foremost, it work because tasksel is modular, and driven by whatever
66 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
67 isenkram-cli package place two files for tasksel to find. First there
68 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
69
70 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
71 Task: isenkram-packages
72 Section: hardware
73 Description: Hardware specific packages (autodetected by isenkram)
74 Based on the detected hardware various hardware specific packages are
75 proposed.
76 Test-new-install: show show
77 Relevance: 8
78 Packages: for-current-hardware
79
80 Task: isenkram-firmware
81 Section: hardware
82 Description: Hardware specific firmware packages (autodetected by isenkram)
83 Based on the detected hardware various hardware specific firmware
84 packages are proposed.
85 Test-new-install: mark show
86 Relevance: 8
87 Packages: for-current-hardware-firmware
88 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
89
90 &lt;p&gt;The key parts are Test-new-install which indicate how the task
91 should be handled and the Packages line referencing to a script in
92 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
93 list of packages to install. The for-current-hardware-firmware script
94 look like this to list relevant firmware for the machine:
95
96 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
97 #!/bin/sh
98 #
99 PATH=/usr/sbin:$PATH
100 export PATH
101 isenkram-autoinstall-firmware -l
102 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
103
104 &lt;p&gt;With those two pieces in place, the firmware is installed by
105 tasksel during the normal d-i run. :)&lt;/p&gt;
106
107 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
108 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
109 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
110 install.&lt;/p&gt;
111
112 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
113 pilots in testing this feature, as isenkram is used there now to
114 install firmware, replacing the earlier scripts.&lt;/p&gt;
115 </description>
116 </item>
117
118 <item>
119 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
120 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
121 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
122 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
123 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
124 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
125 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
126 on a screen normally showing the bread types and prizes:&lt;/p&gt;
127
128 &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;
129
130 &lt;p&gt;If it had booted as it was supposed to, I would never had known
131 about this hidden Linux installation. It is interesting what
132 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
133 </description>
134 </item>
135
136 <item>
137 <title>New lsdvd release version 0.17 is ready</title>
138 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
139 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
140 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
141 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
142 got a new set of developers a few weeks ago, after the original
143 developer decided to step down and pass the project to fresh blood.
144 This project is now maintained by Petter Reinholdtsen and Steve
145 Dibb.&lt;/p&gt;
146
147 &lt;p&gt;I just wrapped up
148 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
149 new lsdvd release&lt;/a&gt;, available in git or from
150 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
151 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
152 0.17.&lt;/p&gt;
153
154 &lt;ul&gt;
155
156 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
157 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
158 non-existant, to work around additional copy protection&lt;/li&gt;
159 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
160 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
161 &lt;li&gt;Fix include orders&lt;/li&gt;
162 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
163 &lt;li&gt;Fix the chapter count&lt;/li&gt;
164 &lt;li&gt;Make sure the array size and the array limit used when initialising
165 the palette size is the same.&lt;/li&gt;
166 &lt;li&gt;Fix array printing.&lt;/li&gt;
167 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
168 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
169 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
170 with more GCC compiler warnings.&lt;/li&gt;
171
172 &lt;/ul&gt;
173
174 &lt;p&gt;This change bring together patches for lsdvd in use in various
175 Linux and Unix distributions, as well as patches submitted to the
176 project the last nine years. Please check it out. :)&lt;/p&gt;
177 </description>
178 </item>
179
180 <item>
181 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
182 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
183 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
184 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
185 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
186 project&lt;/a&gt; provide a Linux solution for schools, including a
187 powerful desktop with education software, a central server providing
188 web pages, user database, user home directories, central login and PXE
189 boot of both clients without disk and the installation to install Debian
190 Edu on machines with disk (and a few other services perhaps to small
191 to mention here). We in the Debian Edu team are currently working on
192 the Jessie based version, trying to get everything in shape before the
193 freeze, to avoid having to maintain our own package repository in the
194 future. The
195 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
196 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
197 work left. Some fatal problems block testing, breaking the installer,
198 but it is possible to work around these to get anyway. Here is a
199 recipe on how to get the installation limping along.&lt;/p&gt;
200
201 &lt;p&gt;First, download the test ISO via
202 &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;,
203 &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;
204 or rsync (use
205 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
206 The ISO build was broken on Tuesday, so we do not get a new ISO every
207 12 hours or so, but thankfully the ISO we already got we are able to
208 install with some tweaking.&lt;/p&gt;
209
210 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
211 (use Alt-Ctrl-F2), run&lt;/p&gt;
212
213 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
214 nano /usr/bin/edu-eatmydata-install
215 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
216
217 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
218 optimization. Return to the installation, select the profile you want
219 and continue. Without this change, exim4-config will fail to install
220 due to a known bug in eatmydata.&lt;/p&gt;
221
222 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
223 this do not work, figure out what your correct value would be. All my
224 test machines need /dev/sda, so I have no advice if it do not fit
225 your need.&lt;/p&gt;
226
227 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
228 root after the initial boot from hard drive, and install the
229 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
230 or mate. If you want several desktop options, install more than one
231 metapackage. Once this is done, reboot and you should have a working
232 graphical login screen. This workaround should no longer be needed
233 once the education-tasks package version 1.801 enter testing in two
234 days.&lt;/p&gt;
235
236 &lt;p&gt;I believe the ISO build will start working on two days when the new
237 tasksel package enter testing and Steve McIntyre get a chance to
238 update the debian-cd git repository. The eatmydata, grub and desktop
239 issues are already fixed in unstable and testing, and should show up
240 on the ISO as soon as the ISO build start working again. Well the
241 eatmydata optimization is really just disabled. The proper fix
242 require an upload by the eatmydata maintainer applying the patch
243 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
244 The rest have proper fixes in unstable.&lt;/p&gt;
245
246 &lt;p&gt;I hope this get you going with the installation testing, as we are
247 quickly running out of time trying to get our Jessie based
248 installation ready before the distribution freeze in a month.&lt;/p&gt;
249 </description>
250 </item>
251
252 <item>
253 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
254 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
255 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
256 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
257 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
258 to handle my fairly large DVD collection. It is a nice command line
259 tool to get details about a DVD, like title, tracks, track length,
260 etc, in XML, Perl or human readable format. But lsdvd have not seen
261 any new development since 2006 and had a few irritating bugs affecting
262 its use with some DVDs. Upstream seemed to be dead, and in January I
263 sent a small probe asking for a version control repository for the
264 project, without any reply. But I use it regularly and would like to
265 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
266 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
267 the project admin, and after getting a reply from him explaining that
268 he was no longer interested in the project, I asked if I could take
269 over. And yesterday, I became project admin.&lt;/p&gt;
270
271 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
272 maintainer interested in joining forces to maintain the upstream
273 project, and I hope we can get a new release out fairly quickly,
274 collecting the patches spread around on the internet into on place.
275 I&#39;ve added the relevant Debian patches to the freshly created git
276 repository, and expect the Gentoo patches to make it too. If you got
277 a DVD collection and care about command line tools, check out
278 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
279 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
280 list&lt;/a&gt;. :)&lt;/p&gt;
281 </description>
282 </item>
283
284 <item>
285 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
286 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
287 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
288 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
289 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
290 a lot quicker. When we install more than 2000 packages in
291 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
292 tasksel in the installer, unpacking the binary packages take forever.
293 A part of the slow I/O issue was discussed in
294 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
295 much file system sync-ing done by dpkg, which is the package
296 responsible for unpacking the binary packages. Other parts (like code
297 executed by postinst scripts) might also sync to disk during
298 installation. All this sync-ing to disk do not really make sense to
299 me. If the machine crash half-way through, I start over, I do not try
300 to salvage the half installed system. So the failure sync-ing is
301 supposed to protect against, hardware or system crash, is not really
302 relevant while the installer is running.&lt;/p&gt;
303
304 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
305 system sync()-ing in a fairly non-intrusive way, without the need to
306 change the code in several packages. The idea is not new, but I have
307 not heard anyone propose the approach using dpkg-divert before. It
308 depend on the small and clever package
309 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
310 uses LD_PRELOAD to replace the system functions for syncing data to
311 disk with functions doing nothing, thus allowing programs to live
312 dangerous while speeding up disk I/O significantly. Instead of
313 modifying the implementation of dpkg, apt and tasksel (which are the
314 packages responsible for selecting, fetching and installing packages),
315 it occurred to me that we could just divert the programs away, replace
316 them with a simple shell wrapper calling
317 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
318 Two days ago I decided to test the idea, and wrapped up a simple
319 implementation for the Debian Edu udeb.&lt;/p&gt;
320
321 &lt;p&gt;The effect was stunning. In my first test it reduced the running
322 time of the pkgsel step (installing tasks) from 64 to less than 44
323 minutes (20 minutes shaved off the installation) on an old Dell
324 Latitude D505 machine. I am not quite sure what the optimised time
325 would have been, as I messed up the testing a bit, causing the debconf
326 priority to get low enough for two questions to pop up during
327 installation. As soon as I saw the questions I moved the installation
328 along, but do not know how long the question were holding up the
329 installation. I did some more measurements using Debian Edu Jessie,
330 and got these results. The time measured is the time stamp in
331 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
332 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
333 yourself. In Debian Edu, the tasksel dialog do not show up, and the
334 timing thus do not depend on how quickly the user handle the tasksel
335 dialog.&lt;/p&gt;
336
337 &lt;p&gt;&lt;table&gt;
338
339 &lt;tr&gt;
340 &lt;th&gt;Machine/setup&lt;/th&gt;
341 &lt;th&gt;Original tasksel&lt;/th&gt;
342 &lt;th&gt;Optimised tasksel&lt;/th&gt;
343 &lt;th&gt;Reduction&lt;/th&gt;
344 &lt;/tr&gt;
345
346 &lt;tr&gt;
347 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
348 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
349 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
350 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
351 &lt;/tr&gt;
352
353 &lt;tr&gt;
354 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
355 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
356 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
357 &lt;td&gt;23 min 40%&lt;/td&gt;
358 &lt;/tr&gt;
359
360 &lt;tr&gt;
361 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
362 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
363 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
364 &lt;td&gt;11 min 50%&lt;/td&gt;
365 &lt;/tr&gt;
366
367 &lt;tr&gt;
368 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
369 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
370 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
371 &lt;td&gt;2 min 33%&lt;/td&gt;
372 &lt;/tr&gt;
373
374 &lt;tr&gt;
375 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
376 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
377 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
378 &lt;td&gt;4 min 21%&lt;/td&gt;
379 &lt;/tr&gt;
380
381 &lt;/table&gt;&lt;/p&gt;
382
383 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
384 time is spent downloading packages. The connection to the Internet
385 was 100Mbit/s during testing, so downloading should not be a
386 significant factor in the measurement. Download typically took a few
387 seconds to a few minutes, depending on the amount of packages being
388 installed.&lt;/p&gt;
389
390 &lt;p&gt;The speedup is implemented by using two hooks in
391 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
392 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
393 finish-install.d hook to remove the divert at the end of the
394 installation. I picked the pre-pkgsel.d hook instead of the
395 post-base-installer.d hook because I test using an ISO without the
396 eatmydata package included, and the post-base-installer.d hook in
397 Debian Edu can only operate on packages included in the ISO. The
398 negative effect of this is that I am unable to activate this
399 optimization for the kernel installation step in d-i. If the code is
400 moved to the post-base-installer.d hook, the speedup would be larger
401 for the entire installation.&lt;/p&gt;
402
403 &lt;p&gt;I&#39;ve implemented this in the
404 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
405 git repository, and plan to provide the optimization as part of the
406 Debian Edu installation. If you want to test this yourself, you can
407 create two files in the installer (or in an udeb). One shell script
408 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
409
410 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
411 #!/bin/sh
412 set -e
413 . /usr/share/debconf/confmodule
414 info() {
415 logger -t my-pkgsel &quot;info: $*&quot;
416 }
417 error() {
418 logger -t my-pkgsel &quot;error: $*&quot;
419 }
420 override_install() {
421 apt-install eatmydata || true
422 if [ -x /target/usr/bin/eatmydata ] ; then
423 for bin in dpkg apt-get aptitude tasksel ; do
424 file=/usr/bin/$bin
425 # Test that the file exist and have not been diverted already.
426 if [ -f /target$file ] ; then
427 info &quot;diverting $file using eatmydata&quot;
428 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
429 &gt; /target$file.edu
430 chmod 755 /target$file.edu
431 in-target dpkg-divert --package debian-edu-config \
432 --rename --quiet --add $file
433 ln -sf ./$bin.edu /target$file
434 else
435 error &quot;unable to divert $file, as it is missing.&quot;
436 fi
437 done
438 else
439 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
440 fi
441 }
442
443 override_install
444 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
445
446 &lt;p&gt;To clean up, another shell script should go into
447 /usr/lib/finish-install.d/ with code like this:
448
449 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
450 #! /bin/sh -e
451 . /usr/share/debconf/confmodule
452 error() {
453 logger -t my-finish-install &quot;error: $@&quot;
454 }
455 remove_install_override() {
456 for bin in dpkg apt-get aptitude tasksel ; do
457 file=/usr/bin/$bin
458 if [ -x /target$file.edu ] ; then
459 rm /target$file
460 in-target dpkg-divert --package debian-edu-config \
461 --rename --quiet --remove $file
462 rm /target$file.edu
463 else
464 error &quot;Missing divert for $file.&quot;
465 fi
466 done
467 sync # Flush file buffers before continuing
468 }
469
470 remove_install_override
471 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
472
473 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
474 edu-eatmydata-install and call it from the pre-pkgsel.d and
475 finish-install.d scripts.&lt;/p&gt;
476
477 &lt;p&gt;By now you might ask if this change should get into the normal
478 Debian installer too? I suspect it should, but am not sure the
479 current debian-installer coordinators find it useful enough. It also
480 depend on the side effects of the change. I&#39;m not aware of any, but I
481 guess we will see if the change is safe after some more testing.
482 Perhaps there is some package in Debian depending on sync() and
483 fsync() having effect? Perhaps it should go into its own udeb, to
484 allow those of us wanting to enable it to do so without affecting
485 everyone.&lt;/p&gt;
486
487 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
488 will break installation of all programs using gnutls because of
489 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
490 eatmydata package in Debian will solve it.&lt;/p&gt;
491
492 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
493 the optimization work again. And I have discovered that the
494 dpkg-divert trick is not really needed and implemented a slightly
495 simpler approach as part of the debian-edu-install package. See
496 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
497 </description>
498 </item>
499
500 <item>
501 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
502 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
503 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
504 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
505 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
506 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
507 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
508 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
509 learn that there is a large set of publicly available key servers to
510 use when looking for peoples public key. So far I have used
511 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
512 were misbehaving, but those days are ended. The servers I have used
513 up until yesterday have been slow and some times unavailable. I hope
514 those problems are gone now.&lt;/p&gt;
515
516 &lt;p&gt;Behind the round robin DNS entry of the
517 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
518 there is a pool of more than 100 keyservers which are checked every
519 day to ensure they are well connected and up to date. It must be
520 better than what I have used so far. :)&lt;/p&gt;
521
522 &lt;p&gt;Yesterdays speaker told me that the service is the default
523 keyserver provided by the default configuration in GnuPG, but this do
524 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
525
526 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
527 line:&lt;/p&gt;
528
529 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
530 keyserver pool.sks-keyservers.net
531 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
532
533 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
534 entries in DNS. Just for fun, I did just that at work, so now every
535 user of GnuPG at the University of Oslo should find a OpenGPG
536 keyserver automatically should their need it:&lt;/p&gt;
537
538 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
539 % host -t srv _pgpkey-http._tcp.uio.no
540 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
541 %
542 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
543
544 &lt;p&gt;Now if only
545 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
546 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
547 very happy. It can look up a given key or search for a user ID, but I
548 normally do not want that, but to find a trust path from my key to
549 another key. Given a user ID or key ID, I would like to find (and
550 download) the keys representing a signature path from my key to the
551 key in question, to be able to get a trust path between the two keys.
552 This is as far as I can tell not possible today. Perhaps something
553 for a future version of the protocol?&lt;/p&gt;
554 </description>
555 </item>
556
557 <item>
558 <title>From English wiki to translated PDF and epub via Docbook</title>
559 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
560 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
561 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
562 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
563 project&lt;/a&gt; provide an instruction manual for teachers, system
564 administrators and other users that contain useful tips for setting up
565 and maintaining a Debian Edu installation. This text is about how the
566 text processing of this manual is handled in the project.&lt;/p&gt;
567
568 &lt;p&gt;One goal of the project is to provide information in the native
569 language of its users, and for this we need to handle translations.
570 But we also want to make sure each language contain the same
571 information, so for this we need a good way to keep the translations
572 in sync. And we want it to be easy for our users to improve the
573 documentation, avoiding the need to learn special formats or tools to
574 contribute, and the obvious way to do this is to make it possible to
575 edit the documentation using a web browser. We also want it to be
576 easy for translators to keep the translation up to date, and give them
577 help in figuring out what need to be translated. Here is the list of
578 tools and the process we have found trying to reach all these
579 goals.&lt;/p&gt;
580
581 &lt;p&gt;We maintain the authoritative source of our manual in the
582 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
583 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
584 front page with references to the different chapters, several pages
585 for each chapter, and finally one &quot;collection page&quot; gluing all the
586 chapters together into one large web page (aka
587 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
588 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
589 processing and translations. Thanks to the fact that the
590 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
591 wiki.debian.org support exporting pages in
592 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
593 the list of pages to export using the raw version of the AllInOne
594 page, loop over each of them to generate a Docbook XML version of the
595 manual. This process also download images and transform image
596 references to use the locally downloaded images. The generated
597 Docbook XML files are slightly broken, so some post-processing is done
598 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
599 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
600 a handfull of images. The XML file can now be used to generate PDF, HTML
601 and epub versions of the English manual. This is the basic step of
602 our process, making PDF (using dblatex), HTML (using xsltproc) and
603 epub (using dbtoepub) version from Docbook XML, and the resulting files
604 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
605
606 &lt;p&gt;But English documentation is not enough for us. We want translated
607 documentation too, and we want to make it easy for translators to
608 track the English original. For this we use the
609 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
610 which allow us to transform the English Docbook XML file into a
611 translation file (a .pot file), usable with the normal gettext based
612 translation tools used by those translating free software. The pot
613 file is used to create and maintain translation files (several .po
614 files), which the translations update with the native language
615 translations of all titles, paragraphs and blocks of text in the
616 original. The next step is combining the original English Docbook XML
617 and the translation file (say debian-edu-wheezy-manual.nb.po), to
618 create a translated Docbook XML file (in this case
619 debian-edu-wheezy-manual.nb.xml). This translated (or partly
620 translated, if the translation is not complete) Docbook XML file can
621 then be used like the original to create a PDF, HTML and epub version
622 of the documentation.&lt;/p&gt;
623
624 &lt;p&gt;The translators use different tools to edit the .po files. We
625 recommend using
626 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
627 while some use emacs and vi, others can use web based editors like
628 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
629 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
630 is where the .po file end up, in our git repository. Updated
631 translations can either be committed directly to git, or submitted as
632 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
633 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
634
635 &lt;p&gt;One challenge is images, which both might need to be translated (if
636 they show translated user applications), and are needed in different
637 formats when creating PDF and HTML versions (epub is a HTML version in
638 this regard). For this we transform the original PNG images to the
639 needed density and format during build, and have a way to provide
640 translated images by storing translated versions in
641 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
642 package maintainers know more.&lt;/p&gt;
643
644 &lt;p&gt;If you wonder what the result look like, we provide
645 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
646 of the documentation packages on the web&lt;/a&gt;. See for example the
647 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
648 PDF version&lt;/a&gt; or the
649 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
650 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
651 but perhaps it will be done in the future.&lt;/p&gt;
652
653 &lt;p&gt;To learn more, check out
654 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
655 debian-edu-doc package&lt;/a&gt;,
656 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
657 manual on the wiki&lt;/a&gt; and
658 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
659 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
660 </description>
661 </item>
662
663 <item>
664 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
665 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
666 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
667 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
668 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
669 related packages relevant for the computer installed automatically.
670 So I implemented one, using
671 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
672 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
673 run tasksel as user root. You should be presented with a new option,
674 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
675 select it, tasksel will install the packages isenkram claim is fit for
676 the current hardware, hot pluggable or not.&lt;p&gt;
677
678 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
679 description, and the other is the script used to extract the list of
680 packages to install. The first part is in
681 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
682 this:&lt;/p&gt;
683
684 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
685 Task: isenkram
686 Section: hardware
687 Description: Hardware specific packages (autodetected by isenkram)
688 Based on the detected hardware various hardware specific packages are
689 proposed.
690 Test-new-install: mark show
691 Relevance: 8
692 Packages: for-current-hardware
693 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
694
695 &lt;p&gt;The second part is in
696 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
697 this:&lt;/p&gt;
698
699 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
700 #!/bin/sh
701 #
702 (
703 isenkram-lookup
704 isenkram-autoinstall-firmware -l
705 ) | sort -u
706 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
707
708 &lt;p&gt;All in all, a very short and simple implementation making it
709 trivial to install the hardware dependent package we all may want to
710 have installed on our machines. I&#39;ve not been able to find a way to
711 get tasksel to tell you exactly which packages it plan to install
712 before doing the installation. So if you are curious or careful,
713 check the output from the isenkram-* command line tools first.&lt;/p&gt;
714
715 &lt;p&gt;The information about which packages are handling which hardware is
716 fetched either from the isenkram package itself in
717 /usr/share/isenkram/, from git.debian.org or from the APT package
718 database (using the Modaliases header). The APT package database
719 parsing have caused a nasty resource leak in the isenkram daemon (bugs
720 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
721 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
722 the python-apt code (bug
723 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
724 workaround I was able to get rid of the file descriptor leak and
725 reduce the memory leak from ~30 MiB per hardware detection down to
726 around 2 MiB per hardware detection. It should make the desktop
727 daemon a lot more useful. The fix is in version 0.7 uploaded to
728 unstable today.&lt;/p&gt;
729
730 &lt;p&gt;I believe the current way of mapping hardware to packages in
731 Isenkram is is a good draft, but in the future I expect isenkram to
732 use the AppStream data source for this. A proposal for getting proper
733 AppStream support into Debian is floating around as
734 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
735 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
736 project&lt;/a&gt; will take place this summer to improve the situation. I
737 look forward to seeing the result, and welcome patches for isenkram to
738 start using the information when it is ready.&lt;/p&gt;
739
740 &lt;p&gt;If you want your package to map to some specific hardware, either
741 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
742 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
743 package&lt;/a&gt; or submit a bug report with the details to the isenkram
744 package. See also
745 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
746 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
747 the information will be migrated to AppStream eventually, but for the
748 moment I got no better place to store it.&lt;/p&gt;
749 </description>
750 </item>
751
752 <item>
753 <title>FreedomBox milestone - all packages now in Debian Sid</title>
754 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
755 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
756 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
757 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
758 project&lt;/a&gt; is working on providing the software and hardware to make
759 it easy for non-technical people to host their data and communication
760 at home, and being able to communicate with their friends and family
761 encrypted and away from prying eyes. It is still going strong, and
762 today a major mile stone was reached.&lt;/p&gt;
763
764 &lt;p&gt;Today, the last of the packages currently used by the project to
765 created the system images were accepted into Debian Unstable. It was
766 the freedombox-setup package, which is used to configure the images
767 during build and on the first boot. Now all one need to get going is
768 the build code from the freedom-maker git repository and packages from
769 Debian. And once the freedombox-setup package enter testing, we can
770 build everything directly from Debian. :)&lt;/p&gt;
771
772 &lt;p&gt;Some key packages used by Freedombox are
773 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
774 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
775 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
776 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
777 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
778 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
779 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
780 are plans to integrate more packages into the setup. User
781 documentation is maintained on the Debian wiki. Please
782 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
783 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
784
785 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
786 setup, run this on a Debian machine using a user with sudo rights to
787 become root:&lt;/p&gt;
788
789 &lt;p&gt;&lt;pre&gt;
790 sudo apt-get install git vmdebootstrap mercurial python-docutils \
791 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
792 u-boot-tools
793 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
794 freedom-maker
795 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
796 &lt;/pre&gt;&lt;/p&gt;
797
798 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
799 devices. See the README in the freedom-maker git repo for more
800 details on the build. If you do not want all three images, trim the
801 make line. Note that the virtualbox-image target is not really
802 virtualbox specific. It create a x86 image usable in kvm, qemu,
803 vmware and any other x86 virtual machine environment. You might need
804 the version of vmdebootstrap in Jessie to get the build working, as it
805 include fixes for a race condition with kpartx.&lt;/p&gt;
806
807 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
808 method, boot a Debian Wheezy ISO and use this boot argument to load
809 the preseed values:&lt;/p&gt;
810
811 &lt;p&gt;&lt;pre&gt;
812 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;
813 &lt;/pre&gt;&lt;/p&gt;
814
815 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
816 it still work.&lt;/p&gt;
817
818 &lt;p&gt;If you wonder how to help, one task you could look at is using
819 systemd as the boot system. It will become the default for Linux in
820 Jessie, so we need to make sure it is usable on the Freedombox. I did
821 a simple test a few weeks ago, and noticed dnsmasq failed to start
822 during boot when using systemd. I suspect there are other problems
823 too. :) To detect problems, there is a test suite included, which can
824 be run from the plinth web interface.&lt;/p&gt;
825
826 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
827 us get the new release published. :) Please join us on
828 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
829 irc.debian.org)&lt;/a&gt; and
830 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
831 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
832 </description>
833 </item>
834
835 <item>
836 <title>S3QL, a locally mounted cloud file system - nice free software</title>
837 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
838 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
839 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
840 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
841 solution for use at home. My requirements are simple, it must be
842 cheap and locally encrypted (in other words, I keep the encryption
843 keys, the storage provider do not have access to my private files).
844 One idea me and my friends had many years ago, before the cloud
845 storage providers showed up, was to use Google mail as storage,
846 writing a Linux block device storing blocks as emails in the mail
847 service provided by Google, and thus get heaps of free space. On top
848 of this one can add encryption, RAID and volume management to have
849 lots of (fairly slow, I admit that) cheap and encrypted storage. But
850 I never found time to implement such system. But the last few weeks I
851 have looked at a system called
852 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
853 mounted network backed file system with the features I need.&lt;/p&gt;
854
855 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
856 handling several different storage providers, any with Amazon S3,
857 Google Drive or OpenStack API. There are heaps of such storage
858 providers. S3QL can also use a local directory as storage, which
859 combined with sshfs allow for file storage on any ssh server. S3QL
860 include support for encryption, compression, de-duplication, snapshots
861 and immutable file systems, allowing me to mount the remote storage as
862 a local mount point, look at and use the files as if they were local,
863 while the content is stored in the cloud as well. This allow me to
864 have a backup that should survive fire. The file system can not be
865 shared between several machines at the same time, as only one can
866 mount it at the time, but any machine with the encryption key and
867 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
868
869 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
870 package is included already. So to get started, run &lt;tt&gt;apt-get
871 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
872 Greenqloud, after reading their nice recipe on
873 &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
874 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
875 in Iceland more than those in USA when it come to keeping my personal
876 data safe and private, and thus would rather spend money on a company
877 in Iceland. Another nice recipe is available from the article
878 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
879 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
880 Admin magazine. When the provider is picked, figure out how to get
881 the API key needed to connect to the storage API. With Greencloud,
882 the key did not show up until I had added payment details to my
883 account.&lt;/p&gt;
884
885 &lt;p&gt;Armed with the API access details, it is time to create the file
886 system. First, create a new bucket in the cloud. This bucket is the
887 file system storage area. I picked a bucket name reflecting the
888 machine that was going to store data there, but any name will do.
889 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
890 the API login and password, and a locally created password. Store it
891 all in ~root/.s3ql/authinfo2 like this:
892
893 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
894 [s3c]
895 storage-url: s3c://s.greenqloud.com:443/bucket-name
896 backend-login: API-login
897 backend-password: API-password
898 fs-passphrase: local-password
899 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
900
901 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
902 but any sensible way to create a fairly random password should do it.
903 Armed with these details, it is now time to run mkfs, entering the API
904 details and password to create it:&lt;/p&gt;
905
906 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
907 # mkdir -m 700 /var/lib/s3ql-cache
908 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
909 --ssl s3c://s.greenqloud.com:443/bucket-name
910 Enter backend login:
911 Enter backend password:
912 Before using S3QL, make sure to read the user&#39;s guide, especially
913 the &#39;Important Rules to Avoid Loosing Data&#39; section.
914 Enter encryption password:
915 Confirm encryption password:
916 Generating random encryption key...
917 Creating metadata tables...
918 Dumping metadata...
919 ..objects..
920 ..blocks..
921 ..inodes..
922 ..inode_blocks..
923 ..symlink_targets..
924 ..names..
925 ..contents..
926 ..ext_attributes..
927 Compressing and uploading metadata...
928 Wrote 0.00 MB of compressed metadata.
929 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
930
931 &lt;p&gt;The next step is mounting the file system to make the storage available.
932
933 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
934 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
935 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
936 Using 4 upload threads.
937 Downloading and decompressing metadata...
938 Reading metadata...
939 ..objects..
940 ..blocks..
941 ..inodes..
942 ..inode_blocks..
943 ..symlink_targets..
944 ..names..
945 ..contents..
946 ..ext_attributes..
947 Mounting filesystem...
948 # df -h /s3ql
949 Filesystem Size Used Avail Use% Mounted on
950 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
951 #
952 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
953
954 &lt;p&gt;The file system is now ready for use. I use rsync to store my
955 backups in it, and as the metadata used by rsync is downloaded at
956 mount time, no network traffic (and storage cost) is triggered by
957 running rsync. To unmount, one should not use the normal umount
958 command, as this will not flush the cache to the cloud storage, but
959 instead running the umount.s3ql command like this:
960
961 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
962 # umount.s3ql /s3ql
963 #
964 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
965
966 &lt;p&gt;There is a fsck command available to check the file system and
967 correct any problems detected. This can be used if the local server
968 crashes while the file system is mounted, to reset the &quot;already
969 mounted&quot; flag. This is what it look like when processing a working
970 file system:&lt;/p&gt;
971
972 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
973 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
974 Using cached metadata.
975 File system seems clean, checking anyway.
976 Checking DB integrity...
977 Creating temporary extra indices...
978 Checking lost+found...
979 Checking cached objects...
980 Checking names (refcounts)...
981 Checking contents (names)...
982 Checking contents (inodes)...
983 Checking contents (parent inodes)...
984 Checking objects (reference counts)...
985 Checking objects (backend)...
986 ..processed 5000 objects so far..
987 ..processed 10000 objects so far..
988 ..processed 15000 objects so far..
989 Checking objects (sizes)...
990 Checking blocks (referenced objects)...
991 Checking blocks (refcounts)...
992 Checking inode-block mapping (blocks)...
993 Checking inode-block mapping (inodes)...
994 Checking inodes (refcounts)...
995 Checking inodes (sizes)...
996 Checking extended attributes (names)...
997 Checking extended attributes (inodes)...
998 Checking symlinks (inodes)...
999 Checking directory reachability...
1000 Checking unix conventions...
1001 Checking referential integrity...
1002 Dropping temporary indices...
1003 Backing up old metadata...
1004 Dumping metadata...
1005 ..objects..
1006 ..blocks..
1007 ..inodes..
1008 ..inode_blocks..
1009 ..symlink_targets..
1010 ..names..
1011 ..contents..
1012 ..ext_attributes..
1013 Compressing and uploading metadata...
1014 Wrote 0.89 MB of compressed metadata.
1015 #
1016 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1017
1018 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1019 quick, about the same speed as local file access. Uploading large
1020 amount of data is to me limited by the bandwidth out of and into my
1021 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1022 which is very close to my upload speed, and downloading the same
1023 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1024 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1025 network, not the file system code. I do not know what a good cache
1026 size would be, but suspect that the cache should e larger than your
1027 working set.&lt;/p&gt;
1028
1029 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1030 time. If another machine try, it is told that the file system is
1031 busy:&lt;/p&gt;
1032
1033 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1034 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1035 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1036 Using 8 upload threads.
1037 Backend reports that fs is still mounted elsewhere, aborting.
1038 #
1039 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1040
1041 &lt;p&gt;The file content is uploaded when the cache is full, while the
1042 metadata is uploaded once every 24 hour by default. To ensure the
1043 file system content is flushed to the cloud, one can either umount the
1044 file system, or ask S3QL to flush the cache and metadata using
1045 s3qlctrl:
1046
1047 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1048 # s3qlctrl upload-meta /s3ql
1049 # s3qlctrl flushcache /s3ql
1050 #
1051 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1052
1053 &lt;p&gt;If you are curious about how much space your data uses in the
1054 cloud, and how much compression and deduplication cut down on the
1055 storage usage, you can use s3qlstat on the mounted file system to get
1056 a report:&lt;/p&gt;
1057
1058 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1059 # s3qlstat /s3ql
1060 Directory entries: 9141
1061 Inodes: 9143
1062 Data blocks: 8851
1063 Total data size: 22049.38 MB
1064 After de-duplication: 21955.46 MB (99.57% of total)
1065 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1066 Database size: 2.39 MB (uncompressed)
1067 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1068 #
1069 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1070
1071 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1072 storage. I did not try to locate them all, but am aware of at least
1073 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1074 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1075 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1076 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1077 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1078 accept payment in Bitcoin. Pick one that suit your need. Some of
1079 them provide several GiB of free storage, but the prize models are
1080 quite different and you will have to figure out what suits you
1081 best.&lt;/p&gt;
1082
1083 &lt;p&gt;While researching this blog post, I had a look at research papers
1084 and posters discussing the S3QL file system. There are several, which
1085 told me that the file system is getting a critical check by the
1086 science community and increased my confidence in using it. One nice
1087 poster is titled
1088 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1089 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1090 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1091 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1092 and Pamela Smith. Please have a look.&lt;/p&gt;
1093
1094 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1095 check out the mounted S3QL file system to see if it would be usable as
1096 a home directory (in other word, that it provided POSIX semantics when
1097 it come to locking and umask handling etc). Running
1098 &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
1099 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1100 no error was found. So the file system can be used for home
1101 directories, if one chooses to do so.&lt;/p&gt;
1102
1103 &lt;p&gt;If you do not want a locally file system, and want something that
1104 work without the Linux fuse file system, I would like to mention the
1105 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1106 provide locally encrypted backup using a command line client. It have
1107 a nicer access control system, where one can split out read and write
1108 access, allowing some systems to write to the backup and others to
1109 only read from it.&lt;/p&gt;
1110
1111 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1112 activities, please send Bitcoin donations to my address
1113 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1114 </description>
1115 </item>
1116
1117 <item>
1118 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1119 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1120 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1121 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1122 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1123 project&lt;/a&gt; is working on providing the software and hardware for
1124 making it easy for non-technical people to host their data and
1125 communication at home, and being able to communicate with their
1126 friends and family encrypted and away from prying eyes. It has been
1127 going on for a while, and is slowly progressing towards a new test
1128 release (0.2).&lt;/p&gt;
1129
1130 &lt;p&gt;And what day could be better than the Pi day to announce that the
1131 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1132 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1133 system), and can also be installed using a Debian installer preseed
1134 file. The Debian based Freedombox is now based on Debian Jessie,
1135 where most of the needed packages used are already present. Only one,
1136 the freedombox-setup package, is missing. To try to build your own
1137 boot image to test the current status, fetch the freedom-maker scripts
1138 and build using
1139 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1140 with a user with sudo access to become root:
1141
1142 &lt;pre&gt;
1143 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1144 freedom-maker
1145 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1146 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1147 u-boot-tools
1148 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1149 &lt;/pre&gt;
1150
1151 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1152 devices. See the README for more details on the build. If you do not
1153 want all three images, trim the make line. But note that thanks to &lt;a
1154 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1155 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1156 kpartx call.&lt;/p&gt;
1157
1158 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1159 method, boot a Debian Wheezy ISO and use this boot argument to load
1160 the preseed values:&lt;/p&gt;
1161
1162 &lt;pre&gt;
1163 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;
1164 &lt;/pre&gt;
1165
1166 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1167 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1168 currently hang while setting up APT sources. Killing the
1169 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1170 installation will get the installation going. This affect all
1171 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1172
1173 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1174 us get the new release published. :) Please join us on
1175 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1176 irc.debian.org)&lt;/a&gt; and
1177 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1178 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1179 </description>
1180 </item>
1181
1182 <item>
1183 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1184 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1186 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1187 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1188 innetgr tools, because I needed them in
1189 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1190 ng-utils, and it has served me well. I placed the project under the
1191 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1192 repository. But many years ago, the CVS repository was dropped (lost,
1193 not migrated to new hardware, not sure), and the project have lacked a
1194 proper home since then.&lt;/p&gt;
1195
1196 &lt;p&gt;Last summer, I had a look at the package and made a new release
1197 fixing a irritating crash bug, but was unable to store the changes in
1198 a proper source control system. I applied for a project on
1199 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1200 to follow up on it. Until today. :)&lt;/p&gt;
1201
1202 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1203 now have a new home, and a git repository with the highlight of the
1204 history of the project. I published all release tarballs and imported
1205 them into the git repository. As the project is really stable and not
1206 expected to gain new features any time soon, I decided to make a new
1207 release and call it 1.0. Visit the new project home on
1208 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1209 if you want to check it out. The new version is also uploaded into
1210 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1211 </description>
1212 </item>
1213
1214 <item>
1215 <title>Testing sysvinit from experimental in Debian Hurd</title>
1216 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1217 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1218 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1219 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1220 their changes into sysvinit, to allow them to use the normal sysvinit
1221 boot system instead of their old one. This follow up on the
1222 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1223 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1224 get Debian on Hurd working more like Debian on Linux. To get started,
1225 I downloaded a prebuilt hard disk image from
1226 &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;,
1227 and started it using virt-manager.&lt;/p&gt;
1228
1229 &lt;p&gt;The first think I had to do after logging in (root without any
1230 password) was to get the network operational. I followed
1231 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1232 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1233 commands as root to get the machine to accept a IP address from the
1234 kvm internal DHCP server:&lt;/p&gt;
1235
1236 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1237 settrans -fgap /dev/netdde /hurd/netdde
1238 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1239 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1240 dhclient /dev/eth0
1241 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1242
1243 &lt;p&gt;After this, the machine had internet connectivity, and I could
1244 upgrade it and install the sysvinit packages from experimental and
1245 enable it as the default boot system in Hurd.&lt;/p&gt;
1246
1247 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1248 running on the machine it for ssh login to work a password need to be
1249 set. Also, note that a bug somewhere in openssh on Hurd block
1250 compression from working. Remember to turn that off on the client
1251 side.&lt;/p&gt;
1252
1253 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1254 stuff:&lt;/p&gt;
1255
1256 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1257 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1258 deb http://http.debian.net/debian/ experimental main
1259 EOF
1260 apt-get update
1261 apt-get dist-upgrade
1262 apt-get install -t experimental initscripts sysv-rc sysvinit \
1263 sysvinit-core sysvinit-utils
1264 update-alternatives --config runsystem
1265 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1266
1267 &lt;p&gt;To reboot after switching boot system, you have to use
1268 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1269 yet a sysvinit process able to receive the signals from the normal
1270 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1271 upgrading every package and rebooting, the network come up with DHCP
1272 after boot as it should, and the settrans/pkill hack mentioned at the
1273 start is no longer needed. But for some strange reason, there are no
1274 longer any login prompt in the virtual console, so I logged in using
1275 ssh instead.
1276
1277 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1278 fail some times. No idea what the cause is, but hope the Hurd porters
1279 figure it out. At least Justus said on IRC (#debian-hurd on
1280 irc.debian.org) that they are aware of the problem. A way to reduce
1281 the impact is to upgrade to the Hurd packages built by Justus by
1282 adding this repository to the machine:&lt;/p&gt;
1283
1284 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1285 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1286 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1287 EOF
1288 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1289
1290 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1291 http://ftp.debian-ports.org/debian, because some of the packages in
1292 unstable do not yet include the required patches that are lingering in
1293 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1294
1295 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1296 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1297 i emacs - GNU Emacs editor (metapackage)
1298 i gdb - GNU Debugger
1299 i hurd-recommended - Miscellaneous translators
1300 i isc-dhcp-client - ISC DHCP client
1301 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1302 i libc-bin - Embedded GNU C Library: Binaries
1303 i libc-dev-bin - Embedded GNU C Library: Development binaries
1304 i libc0.3 - Embedded GNU C Library: Shared libraries
1305 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1306 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1307 i multiarch-support - Transitional package to ensure multiarch compatibilit
1308 i A x11-common - X Window System (X.Org) infrastructure
1309 i xorg - X.Org X Window System
1310 i A xserver-xorg - X.Org X server
1311 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1312 #
1313 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1314
1315 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1316 X.org did not work out of the box and I never took the time to follow
1317 the porters instructions to fix it. This time I was interested in the
1318 command line stuff.&lt;p&gt;
1319 </description>
1320 </item>
1321
1322 <item>
1323 <title>New chrpath release 0.16</title>
1324 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1325 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1326 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1327 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1328 find problems in C, C++ and Java code using static source code
1329 analysis. It can detect a lot of different problems, and is very
1330 useful to find memory and locking bugs in the error handling part of
1331 the source. The company behind it provide
1332 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1333 a community service&lt;/a&gt;, and many hundred free software projects are
1334 already checked. A few days ago I decided to have a closer look at
1335 the Coverity system, and discovered that the
1336 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1337 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1338 projects I am involved with was already registered. But these are
1339 fairly big, and I would also like to have a small and easy project to
1340 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1341 checking of the chrpath project&lt;/a&gt;. It was
1342 added to the checker and discovered seven potential defects. Six of
1343 these were real, mostly resource &quot;leak&quot; when the program detected an
1344 error. Nothing serious, as the resources would be released a fraction
1345 of a second later when the program exited because of the error, but it
1346 is nice to do it right in case the source of the program some time in
1347 the future end up in a library. Having fixed all defects and added
1348 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1349 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1350 publish a new release. These are the release notes:&lt;/p&gt;
1351
1352 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1353
1354 &lt;ul&gt;
1355
1356 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1357 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1358 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1359
1360 &lt;/ul&gt;
1361
1362 &lt;p&gt;You can
1363 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1364 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1365 project if something is wrong with the new release. The test suite
1366 did not discover any old errors, so if you find a new one, please also
1367 include a test suite check.&lt;/p&gt;
1368 </description>
1369 </item>
1370
1371 <item>
1372 <title>New chrpath release 0.15</title>
1373 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1374 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1375 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1376 <description>&lt;p&gt;After many years break from the package and a vain hope that
1377 development would be continued by someone else, I finally pulled my
1378 acts together this morning and wrapped up a new release of chrpath,
1379 the command line tool to modify the rpath and runpath of already
1380 compiled ELF programs. The update was triggered by the persistence of
1381 Isha Vishnoi at IBM, which needed a new config.guess file to get
1382 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1383 is working on. I checked the
1384 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1385 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1386 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1387 packages for interesting patches (failed to find the source from
1388 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1389 These are the release notes:&lt;/p&gt;
1390
1391 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1392
1393 &lt;ul&gt;
1394
1395 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1396 with newer architectures. Thanks to isha vishnoi for the heads
1397 up.&lt;/li&gt;
1398
1399 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1400
1401 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1402 Matthias Klose.&lt;/li&gt;
1403
1404 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1405 Petr Machata found in Fedora.&lt;/li&gt;
1406
1407 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1408 .dynamic is a NULL terminated string. Based on patch found in
1409 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1410
1411 &lt;/ul&gt;
1412
1413 &lt;p&gt;You can
1414 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1415 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1416 project if something is wrong with the new release. The test suite
1417 did not discover any old errors, so if you find a new one, please also
1418 include a testsuite check.&lt;/p&gt;
1419 </description>
1420 </item>
1421
1422 <item>
1423 <title>Debian init.d boot script example for rsyslog</title>
1424 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1425 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1426 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1427 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1428 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1429 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1430 init.d scripts at all. Here is an example init.d script, ie a rewrite
1431 of /etc/init.d/rsyslog:&lt;/p&gt;
1432
1433 &lt;p&gt;&lt;pre&gt;
1434 #!/lib/init/init-d-script
1435 ### BEGIN INIT INFO
1436 # Provides: rsyslog
1437 # Required-Start: $remote_fs $time
1438 # Required-Stop: umountnfs $time
1439 # X-Stop-After: sendsigs
1440 # Default-Start: 2 3 4 5
1441 # Default-Stop: 0 1 6
1442 # Short-Description: enhanced syslogd
1443 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1444 # It is quite compatible to stock sysklogd and can be
1445 # used as a drop-in replacement.
1446 ### END INIT INFO
1447 DESC=&quot;enhanced syslogd&quot;
1448 DAEMON=/usr/sbin/rsyslogd
1449 &lt;/pre&gt;&lt;/p&gt;
1450
1451 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1452 script was 137 lines, and the above is just 15 lines, most of it meta
1453 info/comments.&lt;/p&gt;
1454
1455 &lt;p&gt;How to do this, you ask? Well, one create a new script
1456 /lib/init/init-d-script looking something like this:
1457
1458 &lt;p&gt;&lt;pre&gt;
1459 #!/bin/sh
1460
1461 # Define LSB log_* functions.
1462 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1463 # and status_of_proc is working.
1464 . /lib/lsb/init-functions
1465
1466 #
1467 # Function that starts the daemon/service
1468
1469 #
1470 do_start()
1471 {
1472 # Return
1473 # 0 if daemon has been started
1474 # 1 if daemon was already running
1475 # 2 if daemon could not be started
1476 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1477 || return 1
1478 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1479 $DAEMON_ARGS \
1480 || return 2
1481 # Add code here, if necessary, that waits for the process to be ready
1482 # to handle requests from services started subsequently which depend
1483 # on this one. As a last resort, sleep for some time.
1484 }
1485
1486 #
1487 # Function that stops the daemon/service
1488 #
1489 do_stop()
1490 {
1491 # Return
1492 # 0 if daemon has been stopped
1493 # 1 if daemon was already stopped
1494 # 2 if daemon could not be stopped
1495 # other if a failure occurred
1496 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1497 RETVAL=&quot;$?&quot;
1498 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1499 # Wait for children to finish too if this is a daemon that forks
1500 # and if the daemon is only ever run from this initscript.
1501 # If the above conditions are not satisfied then add some other code
1502 # that waits for the process to drop all resources that could be
1503 # needed by services started subsequently. A last resort is to
1504 # sleep for some time.
1505 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1506 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1507 # Many daemons don&#39;t delete their pidfiles when they exit.
1508 rm -f $PIDFILE
1509 return &quot;$RETVAL&quot;
1510 }
1511
1512 #
1513 # Function that sends a SIGHUP to the daemon/service
1514 #
1515 do_reload() {
1516 #
1517 # If the daemon can reload its configuration without
1518 # restarting (for example, when it is sent a SIGHUP),
1519 # then implement that here.
1520 #
1521 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1522 return 0
1523 }
1524
1525 SCRIPTNAME=$1
1526 scriptbasename=&quot;$(basename $1)&quot;
1527 echo &quot;SN: $scriptbasename&quot;
1528 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1529 script=&quot;$1&quot;
1530 shift
1531 . $script
1532 else
1533 exit 0
1534 fi
1535
1536 NAME=$(basename $DAEMON)
1537 PIDFILE=/var/run/$NAME.pid
1538
1539 # Exit if the package is not installed
1540 #[ -x &quot;$DAEMON&quot; ] || exit 0
1541
1542 # Read configuration variable file if it is present
1543 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
1544
1545 # Load the VERBOSE setting and other rcS variables
1546 . /lib/init/vars.sh
1547
1548 case &quot;$1&quot; in
1549 start)
1550 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
1551 do_start
1552 case &quot;$?&quot; in
1553 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1554 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1555 esac
1556 ;;
1557 stop)
1558 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
1559 do_stop
1560 case &quot;$?&quot; in
1561 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1562 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1563 esac
1564 ;;
1565 status)
1566 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
1567 ;;
1568 #reload|force-reload)
1569 #
1570 # If do_reload() is not implemented then leave this commented out
1571 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
1572 #
1573 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
1574 #do_reload
1575 #log_end_msg $?
1576 #;;
1577 restart|force-reload)
1578 #
1579 # If the &quot;reload&quot; option is implemented then remove the
1580 # &#39;force-reload&#39; alias
1581 #
1582 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
1583 do_stop
1584 case &quot;$?&quot; in
1585 0|1)
1586 do_start
1587 case &quot;$?&quot; in
1588 0) log_end_msg 0 ;;
1589 1) log_end_msg 1 ;; # Old process is still running
1590 *) log_end_msg 1 ;; # Failed to start
1591 esac
1592 ;;
1593 *)
1594 # Failed to stop
1595 log_end_msg 1
1596 ;;
1597 esac
1598 ;;
1599 *)
1600 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
1601 exit 3
1602 ;;
1603 esac
1604
1605 :
1606 &lt;/pre&gt;&lt;/p&gt;
1607
1608 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
1609 lot. I did not really polish the approach, so it might not always
1610 work out of the box, but you get the idea. I did not try very hard to
1611 optimize it nor make it more robust either.&lt;/p&gt;
1612
1613 &lt;p&gt;A better argument for switching init system in Debian than reducing
1614 the size of init scripts (which is a good thing to do anyway), is to
1615 get boot system that is able to handle the kernel events sensibly and
1616 robustly, and do not depend on the boot to run sequentially. The boot
1617 and the kernel have not behaved sequentially in years.&lt;/p&gt;
1618 </description>
1619 </item>
1620
1621 <item>
1622 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
1623 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
1624 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
1625 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
1626 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
1627 remote display access is the preferred solution with oVirt and RedHat
1628 Enterprise Virtualization, and I was sad to discover the other day
1629 that the browser plugin needed to use these systems seamlessly was
1630 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
1631 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
1632 2013-04-01, so I decided to wrap up a package based on the great work
1633 from Cajus Pollmeier and put it in a collab-maint maintained git
1634 repository to get a package I could use. I would very much like
1635 others to help me maintain the package (or just take over, I do not
1636 mind), but as no-one had volunteered so far, I just uploaded it to
1637 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
1638
1639 &lt;p&gt;The source is now available from
1640 &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;
1641 </description>
1642 </item>
1643
1644 <item>
1645 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
1646 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
1647 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
1648 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
1649 <description>&lt;p&gt;The
1650 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
1651 program is a a very nice system to create virtual machine images. It
1652 create a image file, add a partition table, mount it and run
1653 debootstrap in the mounted directory to create a Debian system on a
1654 stick. Yesterday, I decided to try to teach it how to make images for
1655 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1656 of a plan to simplify the build system for
1657 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1658 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1659 the virtualbox images, but its current build system made multistrap
1660 based system for Dreamplug images, and it is lacking support for
1661 Raspberry Pi.&lt;/p&gt;
1662
1663 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1664 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1665 code and adjusted it to be able to build armel images on my amd64
1666 Debian laptop. I ended up giving vmdebootstrap five new options,
1667 allowing me to replicate the image creation process I use to make
1668 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
1669 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
1670 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
1671 call debootstrap with --foreign and to copy the handler into the
1672 generated chroot before running the second stage. This allow
1673 vmdebootstrap to create armel images on an amd64 host. Next I added
1674 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
1675 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
1676 given file system type, allowing me to create an image with a vfat
1677 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
1678 variant&lt;/tt&gt; option to allow me to create smaller images without the
1679 Debian base system packages installed. Finally, I added an option
1680 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
1681 as a boot loader. It is not needed on the Raspberry Pi and probably
1682 most other non-x86 architectures. The changes were accepted by the
1683 upstream author of vmdebootstrap yesterday and today, and is now
1684 available from
1685 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
1686 upstream project page&lt;/a&gt;.&lt;/p&gt;
1687
1688 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
1689 create a small script (the customize script) to add the non-free
1690 binary blob needed to boot the Raspberry Pi and the APT source
1691 list:&lt;/p&gt;
1692
1693 &lt;p&gt;&lt;pre&gt;
1694 #!/bin/sh
1695 set -e # Exit on first error
1696 rootdir=&quot;$1&quot;
1697 cd &quot;$rootdir&quot;
1698 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
1699 deb http://http.debian.net/debian/ jessie main contrib non-free
1700 EOF
1701 # Install non-free binary blob needed to boot Raspberry Pi. This
1702 # install a kernel somewhere too.
1703 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1704 -O $rootdir/usr/bin/rpi-update
1705 chmod a+x $rootdir/usr/bin/rpi-update
1706 mkdir -p $rootdir/lib/modules
1707 touch $rootdir/boot/start.elf
1708 chroot $rootdir rpi-update
1709 &lt;/pre&gt;&lt;/p&gt;
1710
1711 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
1712 to build the image:&lt;/p&gt;
1713
1714 &lt;pre&gt;
1715 sudo ./vmdebootstrap \
1716 --variant minbase \
1717 --arch armel \
1718 --distribution jessie \
1719 --mirror http://http.debian.net/debian \
1720 --image test.img \
1721 --size 600M \
1722 --bootsize 64M \
1723 --boottype vfat \
1724 --log-level debug \
1725 --verbose \
1726 --no-kernel \
1727 --no-extlinux \
1728 --root-password raspberry \
1729 --hostname raspberrypi \
1730 --foreign /usr/bin/qemu-arm-static \
1731 --customize `pwd`/customize \
1732 --package netbase \
1733 --package git-core \
1734 --package binutils \
1735 --package ca-certificates \
1736 --package wget \
1737 --package kmod
1738 &lt;/pre&gt;&lt;/p&gt;
1739
1740 &lt;p&gt;The list of packages being installed are the ones needed by
1741 rpi-update to make the image bootable on the Raspberry Pi, with the
1742 exception of netbase, which is needed by debootstrap to find
1743 /etc/hosts with the minbase variant. I really wish there was a way to
1744 set up an Raspberry Pi using only packages in the Debian archive, but
1745 that is not possible as far as I know, because it boots from the GPU
1746 using a non-free binary blob.&lt;/p&gt;
1747
1748 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
1749 probably a few others installed. I have not checked the complete
1750 build dependency list.&lt;/p&gt;
1751
1752 &lt;p&gt;The resulting image will not use the hardware floating point unit
1753 on the Raspberry PI, because the armel architecture in Debian is not
1754 optimized for that use. So the images created will be a bit slower
1755 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
1756 </description>
1757 </item>
1758
1759 <item>
1760 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
1761 <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>
1762 <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>
1763 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
1764 <description>&lt;p&gt;The last few days I came across a few good causes that should get
1765 wider attention. I recommend signing and donating to each one of
1766 these. :)&lt;/p&gt;
1767
1768 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
1769 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
1770 Women program which is a Google Summer of Code like initiative to get
1771 more women involved in free software. One debian sponsor has offered
1772 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
1773 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
1774 hope you will to. :)&lt;/p&gt;
1775
1776 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
1777 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
1778 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
1779 take place these days, and their need to fund the work. I&#39;ve already
1780 donated. Are you next?&lt;/p&gt;
1781
1782 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
1783 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1784 statement under the heading
1785 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
1786 Access&lt;/a&gt; for those of us asking for more focus on open access in the
1787 Norwegian government. So far 499 signatures. I hope you will sign it
1788 too.&lt;/p&gt;
1789 </description>
1790 </item>
1791
1792 <item>
1793 <title>Videos about the Freedombox project - for inspiration and learning</title>
1794 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
1795 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
1796 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
1797 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
1798 project&lt;/a&gt; have been going on for a while, and have presented the
1799 vision, ideas and solution several places. Here is a little
1800 collection of videos of talks and presentation of the project.&lt;/p&gt;
1801
1802 &lt;ul&gt;
1803
1804 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
1805 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
1806
1807 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
1808 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1809
1810 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
1811 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1812 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
1813 (Youtube)&lt;/li&gt;
1814
1815 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
1816 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
1817
1818 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
1819 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1820
1821 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
1822 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1823 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
1824
1825 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
1826 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
1827 (Youtube)&lt;/li&gt;
1828
1829 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
1830 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
1831
1832 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
1833 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
1834
1835 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
1836 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1837 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
1838
1839 &lt;/ul&gt;
1840
1841 &lt;p&gt;A larger list is available from
1842 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
1843 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
1844
1845 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
1846 Jessie is coming along quite well, and soon both Owncloud and using
1847 Tor should be available for testers of the Freedombox solution. :) In
1848 a few weeks I hope everything needed to test it is included in Debian.
1849 The withsqlite package is already in Debian, and the plinth package is
1850 pending in NEW. The third and vital part of that puzzle is the
1851 metapackage/setup framework, which is still pending an upload. Join
1852 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
1853 (#freedombox on irc.debian.org)&lt;/a&gt; and
1854 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1855 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1856 </description>
1857 </item>
1858
1859 <item>
1860 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
1861 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
1862 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
1863 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
1864 <description>&lt;p&gt;I was introduced to the
1865 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
1866 in 2010, when Eben Moglen presented his vision about serving the need
1867 of non-technical people to keep their personal information private and
1868 within the legal protection of their own homes. The idea is to give
1869 people back the power over their network and machines, and return
1870 Internet back to its intended peer-to-peer architecture. Instead of
1871 depending on a central service, the Freedombox will give everyone
1872 control over their own basic infrastructure.&lt;/p&gt;
1873
1874 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
1875 taken priority. But this summers nasty news about the misuse of trust
1876 and privilege exercised by the &quot;western&quot; intelligence gathering
1877 communities increased my eagerness to contribute to a point where I
1878 actually started working on the project a while back.&lt;/p&gt;
1879
1880 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
1881 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
1882 create a simple and cheap Debian based appliance that anyone can hook
1883 up in their home and get access to secure and private services and
1884 communication. The initial deployment platform have been the
1885 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
1886 which is a piece of hardware I do not own. So to be able to test what
1887 the current Freedombox setup look like, I had to come up with a way to install
1888 it on some hardware I do have access to. I have rewritten the
1889 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
1890 image build framework to use .deb packages instead of only copying
1891 setup into the boot images, and thanks to this rewrite I am able to
1892 set up any machine supported by Debian Wheezy as a Freedombox, using
1893 the previously mentioned deb (and a few support debs for packages
1894 missing in Debian).&lt;/p&gt;
1895
1896 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
1897 scripts
1898 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
1899 and a administrative web interface
1900 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
1901 withsqlite), as well as a privacy enhancing proxy based on
1902 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
1903 (freedombox-privoxy). There is also a web/javascript based XMPP
1904 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
1905 trying (unsuccessfully so far) to talk to the XMPP server
1906 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
1907 web interface is pluggable, and the goal is to use it to enable OpenID
1908 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1909 this is really working yet, see
1910 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
1911 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
1912 on github at the moment. The HTTP proxy is operational out of the
1913 box, and the admin web interface can be used to add/remove plinth
1914 users. I&#39;ve not been able to do anything else with it so far, but
1915 know there are several branches spread around github and other places
1916 with lots of half baked features.&lt;/p&gt;
1917
1918 &lt;p&gt;Anyway, if you want to have a look at the current state, the
1919 following recipes should work to give you a test machine to poke
1920 at.&lt;/p&gt;
1921
1922 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
1923
1924 &lt;ol&gt;
1925
1926 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
1927 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
1928 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
1929 to the Debian installer:&lt;p&gt;
1930 &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;
1931
1932 &lt;li&gt;Answer the few language/region/password questions and pick disk to
1933 install on.&lt;/li&gt;
1934
1935 &lt;li&gt;When the installation is finished and the machine have rebooted a
1936 few times, your Freedombox is ready for testing.&lt;/li&gt;
1937
1938 &lt;/ol&gt;
1939
1940 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
1941
1942 &lt;ol&gt;
1943
1944 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
1945 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
1946 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
1947 &lt;pre&gt;
1948 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
1949 &lt;/pre&gt;&lt;/li&gt;
1950 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
1951 &lt;pre&gt;
1952 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
1953 apt-key add -
1954 apt-get update
1955 apt-get install freedombox-setup
1956 /usr/lib/freedombox/setup
1957 &lt;/pre&gt;&lt;/li&gt;
1958 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
1959
1960 &lt;/ol&gt;
1961
1962 &lt;p&gt;You can test it on other architectures too, but because the
1963 freedombox-privoxy package is binary, it will only work as intended on
1964 the architectures where I have had time to build the binary and put it
1965 in my APT repository. But do not let this stop you. It is only a
1966 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
1967
1968 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
1969 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
1970 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
1971 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
1972
1973 &lt;p&gt;Please let me know if this works for you, or if you have any
1974 problems. We gather on the IRC channel
1975 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
1976 irc.debian.org and the
1977 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
1978 mailing list&lt;/a&gt;.&lt;/p&gt;
1979
1980 &lt;p&gt;Once you get your freedombox operational, you can visit
1981 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
1982 welcome screen (dead end - do not be surprised if you are unable to
1983 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
1984 to look at the rest of plinth. The default user is &#39;admin&#39; and the
1985 default password is &#39;secret&#39;.&lt;/p&gt;
1986 </description>
1987 </item>
1988
1989 <item>
1990 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
1991 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
1992 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
1993 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
1994 <description>&lt;p&gt;Earlier, I reported about
1995 &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
1996 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
1997 told by IBM that the original disk should be thrown away. And as
1998 there no longer was a problem if I bricked the firmware, I decided
1999 today to try to install Intel firmware to replace the Lenovo firmware
2000 currently on the disk.&lt;/p&gt;
2001
2002 &lt;p&gt;I searched the Intel site for firmware, and found
2003 &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;
2004 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2005 according to the site should contain the latest firmware for SSD
2006 disks. I inserted the broken disk in one of my spare laptops and
2007 booted the ISO from a USB stick. The disk was recognized, but the
2008 program claimed the newest firmware already were installed and refused
2009 to insert any Intel firmware. So no change, and the disk is still
2010 unable to handle write load. :( I guess the only way to get them
2011 working would be if Lenovo releases new firmware. No idea how likely
2012 that is. Anyway, just blogging about this test for completeness. I
2013 got a working Samsung disk, and see no point in spending more time on
2014 the broken disks.&lt;/p&gt;
2015 </description>
2016 </item>
2017
2018 <item>
2019 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2020 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2021 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2022 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2023 <description>&lt;p&gt;Today I switched to
2024 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2025 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2026 my new Thinkpad X230, which was delivered with an
2027 &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
2028 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2029 sustained writes. My hardware supplier have been very forthcoming in
2030 trying to find a solution, and after first trying with another
2031 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2032 disk instead to fix it once and for all. The Samsung disk survived
2033 the installation of Debian with encrypted disks (filling the disk with
2034 random data during installation killed the first two), and I thus
2035 decided to trust it with my data. I have installed it as a Debian Edu
2036 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2037 server at home using Kerberos and LDAP, and will use it as my work
2038 station from now on.&lt;/p&gt;
2039
2040 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2041 Debian Wheezy default installation need to be tuned a bit to increase
2042 performance and increase life time of the disk. The Linux kernel and
2043 user space applications do not yet adjust automatically to such
2044 environment. To make it easier for my self, I created a draft Debian
2045 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2046 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2047 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2048 is set up to adjust the setup of the machine by just installing the
2049 package. If there is any non-SSD disk in the machine, the package
2050 will refuse to install, as I did not try to write any logic to sort
2051 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2052
2053 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2054 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2055 where I set up the machine with one large encrypted partition (in
2056 addition to /boot), put LVM on top of this and set up partitions on
2057 top of this again. See the README file in the package source for the
2058 references I used to pick the settings. At the moment these
2059 parameters are tuned:&lt;/p&gt;
2060
2061 &lt;ul&gt;
2062
2063 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2064 (adding discard to /etc/crypttab)&lt;/li&gt;
2065
2066 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2067 this case a cryptsetup partition) by changing issue_discards from
2068 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2069
2070 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2071 systems.&lt;/li&gt;
2072
2073 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2074 /etc/fstab.&lt;/li&gt;
2075
2076 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2077
2078 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2079 cron.daily).&lt;/li&gt;
2080
2081 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2082 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2083
2084 &lt;/ul&gt;
2085
2086 &lt;p&gt;During installation, I cancelled the part where the installer fill
2087 the disk with random data, as this would kill the SSD performance for
2088 little gain. My goal with the encrypted file system is to ensure
2089 those stealing my laptop end up with a brick and not a working
2090 computer. I have no hope in keeping the really resourceful people
2091 from getting the data on the disk (see
2092 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2093 Thus I concluded that adding the discard option to crypttab is the
2094 right thing to do.&lt;/p&gt;
2095
2096 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2097 it for SSD, but others recommended deadline and a benchmark I found
2098 indicated that deadline might be better for interactive use.&lt;/p&gt;
2099
2100 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2101 and ext4, but read that it would give a performance hit ever time a
2102 file is removed, and thought it best to that that slowdown once a day
2103 instead of during my work.&lt;/p&gt;
2104
2105 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2106 this is already done by Debian Edu.&lt;/p&gt;
2107
2108 &lt;p&gt;I have not yet started on the user space tuning. I expect
2109 iceweasel need some tuning, and perhaps other applications too, but
2110 have not yet had time to investigate those parts.&lt;/p&gt;
2111
2112 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2113 there.&lt;/p&gt;
2114
2115 &lt;p&gt;As for the answer to the question in the title of this blog post,
2116 as far as I know, the only solution I know about is to replace the
2117 disk. It might be possible to flash it with Intel firmware instead of
2118 the Lenovo firmware. But I have not tried and did not want to do so
2119 without approval from Lenovo as I wanted to keep the warranty on the
2120 disk until a solution was found and they wanted the broken disks
2121 back.&lt;/p&gt;
2122 </description>
2123 </item>
2124
2125 <item>
2126 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2127 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2128 <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>
2129 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2130 <description>&lt;p&gt;A few days ago, I wrote about
2131 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2132 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2133 was dying during installation because it is unable to cope with
2134 sustained write. My supplier is in contact with
2135 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2136 replacement disk to try to fix the problem. They decided to send an
2137 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2138
2139 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2140 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2141 same firmware version as the original. This time my hope raised
2142 slightly as the installation progressed, as the original disk used to
2143 die after 4-7% of the disk was written to, while this time it kept
2144 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2145 died again and I was back on square one. I still do not have a new
2146 laptop with a disk I can trust. I can not live with a disk that might
2147 lock up when I download a new
2148 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2149 other large files. I look forward to hearing from my supplier with
2150 the next proposal from Lenovo.&lt;/p&gt;
2151
2152 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2153 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2154 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2155 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2156 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2157 P/N 45N8295, P0C38732.&lt;/p&gt;
2158
2159 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2160 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2161 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2162 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2163 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2164 P/N 45N8295, P0C38732.&lt;/p&gt;
2165
2166 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2167 SA, date and WNPP values. Mentioning all the details here in case
2168 someone is able to use the information to find a way to identify the
2169 failing disk among working ones (if any such working disk actually
2170 exist).&lt;/p&gt;
2171 </description>
2172 </item>
2173
2174 <item>
2175 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2176 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2177 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2178 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2179 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2180 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2181 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2182 member assosiation NUUG&lt;/a&gt; and
2183 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2184 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2185 Bitraf&lt;/a&gt;.&lt;/p&gt;
2186
2187 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2188 welcome, and there is no fee to participate. There is on the other
2189 hand limited space, and only room for 30 people. Please put your name
2190 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2191 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2192 </description>
2193 </item>
2194
2195 <item>
2196 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2197 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2198 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2199 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2200 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2201 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2202 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2203 time to spend on it, and it took a while to find a model I believe
2204 will do the job, but two days ago the replacement finally arrived. I
2205 ended up picking a
2206 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2207 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2208 a roaming workstation, and it seemed to work flawlessly. But my
2209 second installation with encrypted disk was not as successful. More
2210 on that below.&lt;/p&gt;
2211
2212 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2213 important requirements (robust and with a good keyboard) are never
2214 listed in the feature list. But I did get good help from the search
2215 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2216 allowed me to limit the list of interesting laptops based on my other
2217 requirements. A bit surprising that SSD disk are not disks according
2218 to that search interface, so I had to drop specifying the number of
2219 disks from my search parameters. I also asked around among friends to
2220 get their impression on keyboards and robustness.&lt;/p&gt;
2221
2222 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2223 X41. I am not quite convinced about the keyboard, as it is
2224 significantly wider than my old keyboard, and I have to stretch my
2225 hand a lot more to reach the edges. But the key response is fairly
2226 good and the individual key shape is fairly easy to handle, so I hope
2227 I will get used to it. My old X40 was starting to fail, and I really
2228 needed a new laptop now. :)&lt;/p&gt;
2229
2230 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2231 visit to the BIOS during boot it disable it.&lt;/p&gt;
2232
2233 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2234 lock up during load. And this happen when installing Debian Wheezy
2235 with encrypted disk, while the disk is being filled with random data.
2236 I also tested to install Ubuntu Raring, and it happen there too if I
2237 reenable the code to fill the disk with random data (it is disabled by
2238 default in Ubuntu). And the bug with is already known. It was
2239 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2240 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2241 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2242 kernel developers as
2243 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2244 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2245 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2246 Lenovo forums, both for
2247 &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
2248 2012-11-10&lt;/a&gt; and for
2249 &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
2250 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2251 reports state that the disk lock up during use if many writes are done
2252 on the disk, so it is much no use to work around the installation
2253 problem and end up with a computer that can lock up at any moment.
2254 There is even a
2255 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2256 available&lt;/a&gt; that will lock up the hard drive after running a few
2257 minutes by writing to a file.&lt;/p&gt;
2258
2259 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2260 contacting PCHELP Norway (request 01D1FDP) which handle support
2261 requests for Lenovo, his first suggestion was to upgrade the disk
2262 firmware. Unfortunately there is no newer firmware available from
2263 Lenovo, as my disk already have the most recent one (version LF1i). I
2264 hope to hear more from him today and hope the problem can be
2265 fixed. :)&lt;/p&gt;
2266 </description>
2267 </item>
2268
2269 <item>
2270 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2271 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2272 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2273 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2274 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2275 trusty old Thinkpad X41. Unfortunately I did not have much time to
2276 spend on it, but today the replacement finally arrived. I ended up
2277 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2278 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2279 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2280 this, it is installing what I hope will be a more final installation,
2281 with a encrypted hard drive to ensure any dope head stealing it end up
2282 with an expencive door stop.&lt;/p&gt;
2283
2284 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2285 important requirements (robust and with a good keyboard) are never
2286 listed in the feature list. But I did get good help from the search
2287 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2288 allowed me to limit the list of interesting laptops based on my other
2289 requirements. A bit surprising that SSD disk are not disks, so I had
2290 to drop number of disks from my search parameters.&lt;/p&gt;
2291
2292 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2293 wider than my old keyboard, and I have to stretch my hand a lot more
2294 to reach the edges. But the key response is fairly good and the
2295 individual key shape is fairly easy to handle, so I hope I will get
2296 used to it. My old X40 was starting to fail, and I really needed a
2297 new laptop now. :)&lt;/p&gt;
2298
2299 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2300 </description>
2301 </item>
2302
2303 <item>
2304 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2305 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2306 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2307 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2308 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2309 perfectly capable of, and I have to do it manually to get things
2310 working. One such task is to find out what firmware packages are
2311 needed to get the hardware on my computer working. Most often this
2312 affect the wifi card, but some times it even affect the RAID
2313 controller or the ethernet card. Today I pushed version 0.4 of the
2314 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2315 including a new script isenkram-autoinstall-firmware handling the
2316 process of asking all the loaded kernel modules what firmware files
2317 they want, find debian packages providing these files and install the
2318 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2319
2320 &lt;p&gt;&lt;pre&gt;
2321 # isenkram-autoinstall-firmware
2322 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2323 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2324 info: locating packages with the requested firmware files
2325 info: Updating APT sources after adding non-free APT source
2326 info: trying to install firmware-ipw2x00
2327 firmware-ipw2x00
2328 firmware-ipw2x00
2329 Preconfiguring packages ...
2330 Selecting previously deselected package firmware-ipw2x00.
2331 (Reading database ... 259727 files and directories currently installed.)
2332 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2333 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2334 #
2335 &lt;/pre&gt;&lt;/p&gt;
2336
2337 &lt;p&gt;When all the requested firmware is present, a simple message is
2338 printed instead:&lt;/p&gt;
2339
2340 &lt;p&gt;&lt;pre&gt;
2341 # isenkram-autoinstall-firmware
2342 info: did not find any firmware files requested by loaded kernel modules. exiting
2343 #
2344 &lt;/pre&gt;&lt;/p&gt;
2345
2346 &lt;p&gt;It could use some polish, but it is already working well and saving
2347 me some time when setting up new machines. :)&lt;/p&gt;
2348
2349 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2350 kernel modules, and look up each one of them using modinfo, to find
2351 the firmware files listed in the module meta-information. Next, it
2352 download the Contents file from a nearby APT mirror, and search for
2353 the firmware files in this file to locate the package with the
2354 requested firmware file. If the package is in the non-free section, a
2355 non-free APT source is added and the package is installed using
2356 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2357 machine.&lt;/p&gt;
2358
2359 &lt;p&gt;I hope someone find time to implement a more polished version of
2360 this script as part of the hw-detect debian-installer module, to
2361 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2362 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2363 firmware during a PXE install when the packages already are available
2364 from the nearby Debian mirror.&lt;/p&gt;
2365 </description>
2366 </item>
2367
2368 <item>
2369 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2370 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2371 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2372 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2373 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2374 the screen just turn black when Linux boot, either during installation
2375 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2376 last few years, but only recently understood the cause. I&#39;ve seen it
2377 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2378 The reason seem to be in the wiring of some laptops. The system to
2379 control the screen background light is inverted, so when Linux try to
2380 turn the brightness fully on, it end up turning it off instead. I do
2381 not know which Linux drivers are affected, but this post is about the
2382 i915 driver used by the
2383 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2384 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2385
2386 &lt;p&gt;The problem can be worked around two ways. Either by adding
2387 i915.invert_brightness=1 as a kernel option, or by adding a file in
2388 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2389 option when it load the i915 kernel module. On Debian and Ubuntu, it
2390 can be done by running these commands as root:&lt;/p&gt;
2391
2392 &lt;pre&gt;
2393 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2394 update-initramfs -u -k all
2395 &lt;/pre&gt;
2396
2397 &lt;p&gt;Since March 2012 there is
2398 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2399 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2400 hardware have this problem, and get the driver to invert the
2401 brightness setting automatically. To use it, one need to add a row in
2402 &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
2403 intel_quirks array&lt;/a&gt; in the driver source
2404 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2405 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2406 number (vendor number 8086 is assumed) and subdevice vendor and device
2407 number.&lt;/p&gt;
2408
2409 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2410 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2411
2412 &lt;p&gt;&lt;pre&gt;
2413 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2414 3rd Gen Core processor Graphics Controller [8086:0156] \
2415 (rev 09) (prog-if 00 [VGA controller])
2416 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2417 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2418 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2419 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2420 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2421 Latency: 0
2422 Interrupt: pin A routed to IRQ 42
2423 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2424 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2425 Region 4: I/O ports at 4000 [size=64]
2426 Expansion ROM at &lt;unassigned&gt; [disabled]
2427 Capabilities: &lt;access denied&gt;
2428 Kernel driver in use: i915
2429 &lt;/pre&gt;&lt;/p&gt;
2430
2431 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2432
2433 &lt;p&gt;&lt;pre&gt;
2434 struct intel_quirk intel_quirks[] = {
2435 ...
2436 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2437 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2438 ...
2439 }
2440 &lt;/pre&gt;&lt;/p&gt;
2441
2442 &lt;p&gt;According to the kernel module instructions (as seen using
2443 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2444 invert_brightness flag should be sent to the
2445 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2446 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2447 developers. But my email about the laptop sent 2013-06-03 have not
2448 yet shown up in
2449 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2450 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2451 emails from non-subscribers. Because of this, I sent my patch also to
2452 the Debian bug tracking system instead as
2453 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2454 sure the patch is not lost.&lt;/p&gt;
2455
2456 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2457 with this problem working properly with Linux. If you use Gnome, your
2458 worries should be over at this point. But if you use KDE, there is
2459 something in KDE ignoring the invert_brightness setting and turning on
2460 the screen during login. I&#39;ve reported it to Debian as
2461 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2462 have no idea yet how to figure out exactly what subsystem is doing
2463 this. Perhaps you can help? Perhaps you know what the Gnome
2464 developers did to handle this, and this can give a clue to the KDE
2465 developers? Or you know where in KDE the screen brightness is changed
2466 during login? If so, please update the BTS report (or get in touch if
2467 you do not know how to update BTS).&lt;/p&gt;
2468
2469 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2470 acpi_backlight=vendor, to disable ACPI backlight support completely,
2471 as the ACPI information on the machine is trash and it is better to
2472 leave it to the intel video driver to control the screen
2473 backlight.&lt;/p&gt;
2474 </description>
2475 </item>
2476
2477 <item>
2478 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2479 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2480 <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>
2481 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2482 <description>&lt;p&gt;Two days ago, I asked
2483 &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
2484 I could install Linux on a Packard Bell EasyNote LV computer
2485 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2486 with the obstacles put in the way of Linux users on a laptop with UEFI
2487 and Windows 8.&lt;/p&gt;
2488
2489 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2490 secure booting or fast boot. I suspect fast boot was the problem,
2491 causing the firmware to boot directly from HD without considering any
2492 key presses and alternative devices, but do not know UEFI settings
2493 enough to tell.&lt;/p&gt;
2494
2495 &lt;p&gt;There is no way to install Linux on the machine in question without
2496 opening the box and disconnecting the hard drive! This is as far as I
2497 can tell, the only way to get access to the firmware setup menu
2498 without accepting the Windows 8 license agreement. I am told (and
2499 found description on how to) that it is possible to configure the
2500 firmware setup once booted into Windows 8. But as I believe the terms
2501 of that agreement are completely unacceptable, accepting the license
2502 was never an alternative. I do not enter agreements I do not intend
2503 to follow.&lt;/p&gt;
2504
2505 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2506 waste many hours on this, but luckily there was a way to get it to
2507 work. But I would not recommend it to anyone planning to run Linux on
2508 it, and I have become sceptical to Windows 8 certified laptops. Is
2509 this the way Linux will be forced out of the market place, by making
2510 it close to impossible for &quot;normal&quot; users to install Linux without
2511 accepting the Microsoft Windows license terms? Or at least not
2512 without risking to loose the warranty?&lt;/p&gt;
2513
2514 &lt;p&gt;I&#39;ve updated the
2515 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2516 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2517 do not have to struggle as much as I did to get Linux into the
2518 machine.&lt;/p&gt;
2519
2520 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2521 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2522 </description>
2523 </item>
2524
2525 <item>
2526 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2527 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2528 <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>
2529 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2530 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2531 new laptops for my parents and a few others. I bought Packard Bell
2532 Easynote LV to run Kubuntu on and use as their home computer. But I
2533 am completely unable to figure out how to install Linux on it. The
2534 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2535 instead of a BIOS to boot.&lt;/p&gt;
2536
2537 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
2538 to get it to boot the Linux installer from my USB stick. I have yet
2539 to try the DVD install, and still hope it will work. when I turn on
2540 the computer, there is no information on what buttons to press to get
2541 the normal boot menu. I expect to get some boot menu to select PXE or
2542 USB stick booting. When booting, it first ask for the language to
2543 use, then for some regional settings, and finally if I will accept the
2544 Windows 8 terms of use. As these terms are completely unacceptable to
2545 me, I have no other choice but to turn off the computer and try again
2546 to get it to boot the Linux installer.&lt;/p&gt;
2547
2548 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
2549 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2550 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
2551 installed on this machine, please get in touch or update that wiki
2552 page. If I can&#39;t find a way to install Linux, I will have to return
2553 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
2554
2555 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
2556 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
2557 on new Laptops?&lt;/p&gt;
2558 </description>
2559 </item>
2560
2561 <item>
2562 <title>How to transform a Debian based system to a Debian Edu installation</title>
2563 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
2564 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
2565 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
2566 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
2567 an operating system based on Debian intended for use in schools. It
2568 contain a turn-key solution for the computer network provided to
2569 pupils in the primary schools. It provide both the central server,
2570 network boot servers and desktop environments with heaps of
2571 educational software. The project was founded almost 12 years ago,
2572 2001-07-02. If you want to support the project, which is in need for
2573 cash to fund developer gatherings and other project related activity,
2574 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
2575 donate some money&lt;/a&gt;.
2576
2577 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
2578 lists and elsewhere, is the question on how to transform a Debian or
2579 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
2580 hard, and last week I wrote a script to replicate the steps done by
2581 the Debian Edu installer.&lt;/p&gt;
2582
2583 &lt;p&gt;The script,
2584 &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;
2585 in the debian-edu-config package, will go through these six steps and
2586 transform an existing Debian Wheezy or Ubuntu (untested) installation
2587 into a Debian Edu Workstation:&lt;/p&gt;
2588
2589 &lt;ol&gt;
2590
2591 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
2592 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
2593 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
2594 our configuration.&lt;/li&gt;
2595 &lt;li&gt;Preseed debconf database with profile setup in
2596 /etc/debian-edu/config, and run tasksel to install packages
2597 according to the profile specified in the config above,
2598 overriding some of the Debian automation machinery.&lt;/li&gt;
2599 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
2600 that could not be done using preseeding.&lt;/li&gt;
2601 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
2602
2603 &lt;/ol&gt;
2604
2605 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
2606 replicated like this. Disk partitioning and LVM setup, for example.
2607 So this script just assume there is enough disk space to install all
2608 the needed packages.&lt;/p&gt;
2609
2610 &lt;p&gt;The script was created to help a Debian Edu student working on
2611 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
2612 Debian Edu client, and using it he can take the existing
2613 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
2614 transform it into a fully functioning Debian Edu Workstation (or
2615 Roaming Workstation, or whatever :).&lt;/p&gt;
2616
2617 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
2618 If a LXDE based Roaming workstation is wanted instead, modify the
2619 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
2620
2621 &lt;p&gt;&lt;pre&gt;
2622 PROFILE=&quot;Roaming-Workstation&quot;
2623 DESKTOP=&quot;lxde&quot;
2624 &lt;/pre&gt;&lt;/p&gt;
2625
2626 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
2627 the cloud, by starting with a virtual Debian installation at some
2628 virtual hosting service and setting up all the services on first
2629 boot.&lt;/p&gt;
2630 </description>
2631 </item>
2632
2633 <item>
2634 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
2635 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
2636 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
2637 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
2638 <description>&lt;P&gt;In January,
2639 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
2640 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
2641 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
2642 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
2643 marvellous construction system from Denmark. We also created
2644 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
2645 a place to take notes and write down our plans and hopes. And several
2646 people showed up to help. I was very happy to see the effect of my
2647 call. Since the small start, we have a debtags tag
2648 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
2649 tag for LEGO related packages, and now count 10 packages related to
2650 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
2651
2652 &lt;p&gt;&lt;table&gt;
2653 &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;
2654 &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;
2655 &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;
2656 &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;
2657 &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;
2658 &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;
2659 &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;
2660 &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;
2661 &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;
2662 &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;
2663 &lt;/table&gt;&lt;/p&gt;
2664
2665 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2666 currently available in Jessie/testing. leocad is so far only
2667 available in experimental.&lt;/p&gt;
2668
2669 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
2670 adding the rest of the great free software tools available on Linux
2671 for LEGO designers.&lt;/p&gt;
2672 </description>
2673 </item>
2674
2675 <item>
2676 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
2677 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
2678 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
2679 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
2680 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
2681 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
2682 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
2683 Debian release, and I expect to move my machines at home over to it fairly
2684 soon.&lt;/p&gt;
2685
2686 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
2687 in particular make me very happy to see included. The
2688 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
2689 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
2690 included for the first time. Alongside similar programs like
2691 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
2692 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
2693 it allow for visual programming where syntax errors can not happen,
2694 and a friendly programming environment for learning to control the
2695 computer. Scratch will also be included in the next release of Debian
2696 Edu.&lt;/a&gt;
2697
2698 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
2699 Edu/Skolelinux release too. The
2700 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
2701 alpha release&lt;/a&gt; went out last week, and the next should soon
2702 follow.&lt;p&gt;
2703 </description>
2704 </item>
2705
2706 <item>
2707 <title>Isenkram 0.2 finally in the Debian archive</title>
2708 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
2709 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
2710 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
2711 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
2712 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
2713 for many months. I uploaded it to the Debian experimental suite
2714 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
2715
2716 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
2717 install to work with a pluggable hardware device. The suggestion pop
2718 up when the device is plugged in. For example if a Lego Mindstorm NXT
2719 is inserted, it will suggest to install the program needed to program
2720 the NXT controller. Give it a go, and report bugs and suggestions to
2721 BTS. :)&lt;/p&gt;
2722 </description>
2723 </item>
2724
2725 <item>
2726 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
2727 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
2728 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
2729 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
2730 <description>&lt;p&gt;My
2731 &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
2732 bitcoin related blog post&lt;/a&gt; mentioned that the new
2733 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
2734 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2735 2013-01-19, and have been available in unstable since then. It was
2736 automatically copied to Ubuntu, and is available in their Raring
2737 version too.&lt;/p&gt;
2738
2739 &lt;p&gt;But there is a strange problem with the build that block this new
2740 version from being available on the i386 and kfreebsd-i386
2741 architectures. For some strange reason, the autobuilders in Debian
2742 for these architectures fail to run the test suite on these
2743 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
2744 We are so far unable to reproduce it when building it manually, and
2745 no-one have been able to propose a fix. If you got an idea what is
2746 failing, please let us know via the BTS.&lt;/p&gt;
2747
2748 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
2749 I often run low on disk space, is the fact that the client will exit
2750 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
2751 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
2752 it. :)&lt;/p&gt;
2753
2754 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
2755 activities, please send Bitcoin donations to my address
2756 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2757 </description>
2758 </item>
2759
2760 <item>
2761 <title>Welcome to the world, Isenkram!</title>
2762 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
2763 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
2764 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
2765 <description>&lt;p&gt;Yesterday, I
2766 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
2767 for testers&lt;/a&gt; for my prototype for making Debian better at handling
2768 pluggable hardware devices, which I
2769 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
2770 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
2771 up, and caused me to really want to to open up the development to more
2772 people. But before I did this, I want to come up with a sensible name
2773 for this project. Today I finally decided on a new name, and I have
2774 renamed the project from hw-support-handler to this new name. In the
2775 process, I moved the source to git and made it available as a
2776 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
2777 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
2778 To fetch and build the latest version of the source, use&lt;/p&gt;
2779
2780 &lt;pre&gt;
2781 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2782 cd isenkram &amp;&amp; git-buildpackage -us -uc
2783 &lt;/pre&gt;
2784
2785 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
2786 want to hack on the source or improve the package, please go ahead.
2787 But please talk to me first on IRC or via email before you do major
2788 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
2789
2790 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
2791 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2792 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
2793 the German word eisenkram, for those that are familiar with that
2794 word.&lt;/p&gt;
2795
2796 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
2797 instructions, to avoid confusing people with an error from the signing
2798 process.&lt;/p&gt;
2799
2800 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
2801 clone argument to avoid the need for authentication.&lt;/p&gt;
2802 </description>
2803 </item>
2804
2805 <item>
2806 <title>First prototype ready making hardware easier to use in Debian</title>
2807 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
2808 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
2809 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
2810 <description>&lt;p&gt;Early this month I set out to try to
2811 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
2812 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
2813 prototype is working, and it is ready for a larger audience. To test
2814 it, fetch the
2815 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
2816 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
2817 package. You might have to log out and in again activate the
2818 autostart script.&lt;/p&gt;
2819
2820 &lt;p&gt;The design is simple:&lt;/p&gt;
2821
2822 &lt;ul&gt;
2823
2824 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
2825 hw-support-handlerd to start when the user log in.&lt;/li&gt;
2826
2827 &lt;li&gt;This program listen for kernel events about new hardware (directly
2828 from the kernel like udev does), not using HAL dbus events as I
2829 initially did.&lt;/li&gt;
2830
2831 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
2832 the APT database, a database
2833 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
2834 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
2835
2836 &lt;li&gt;If a package is mapped to the hardware in question, the package
2837 isn&#39;t installed yet and this is the first time the hardware was
2838 plugged in, show a desktop notification suggesting to install the
2839 package or packages.&lt;/li&gt;
2840
2841 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
2842 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
2843
2844 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
2845 package while showing progress information in a window.&lt;/li&gt;
2846
2847 &lt;/ul&gt;
2848
2849 &lt;p&gt;I still need to come up with a better name for the system. Here
2850 are some screen shots showing the prototype in action. First the
2851 notification, then the password request, and finally the request to
2852 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
2853
2854 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
2855 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
2856 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
2857 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
2858 &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;
2859
2860 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
2861 is already useful. The database of hardware to package mappings also
2862 need more work. It is currently compatible with the Ubuntu way of
2863 storing such information in the package control file, but could be
2864 changed to use other formats instead or in addition to the current
2865 method. I&#39;ve dropped the use of discover for this mapping, as the
2866 modalias approach is more flexible and easier to use on Linux as long
2867 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
2868
2869 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
2870 here is the command required to check out and build the source: Use
2871 &#39;&lt;tt&gt;svn checkout
2872 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2873 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
2874 devscripts package.&lt;/p&gt;
2875
2876 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
2877 renamed to Isenkram and the source moved from the Debian Edu
2878 subversion repository to a Debian collab-maint git repository. See
2879 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
2880 instructions&lt;/a&gt; for details.&lt;/p&gt;
2881 </description>
2882 </item>
2883
2884 <item>
2885 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
2886 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
2887 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
2888 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
2889 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
2890 suddenly in bed. With a quiet whimper, it went completely quiet and
2891 black. The power button was no longer able to turn it on. It was a
2892 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2893 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2894 Compaq I had before that. Now I need to find a replacement. To keep
2895 going during Christmas, I moved the one year old SSD disk to my old
2896 X40 where it fitted (only one I had left that could use it), but it is
2897 not a durable solution.
2898
2899 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
2900 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
2901
2902 &lt;ul&gt;
2903
2904 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
2905 than A4).&lt;/li&gt;
2906 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
2907 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
2908 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
2909 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
2910 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
2911 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
2912 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
2913 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
2914 size).&lt;/li&gt;
2915 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
2916 X.org packages.&lt;/li&gt;
2917 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
2918 the time).
2919
2920 &lt;/ul&gt;
2921
2922 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
2923 list. The reason is simply that the specifications on laptops the
2924 last 10-15 years have been sufficient for my needs, and I have to look
2925 at other features to choose my laptop. But are there still made as
2926 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
2927 robust, and Thinkpads seem to be heading in the wrong direction since
2928 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
2929 still be useful.&lt;/p&gt;
2930
2931 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
2932 external keyboard? I&#39;ll have to check the
2933 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
2934 well-supported laptops, or perhaps just buy one preinstalled from one
2935 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
2936 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
2937 </description>
2938 </item>
2939
2940 <item>
2941 <title>How to find a browser plugin supporting a given MIME type</title>
2942 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
2943 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
2944 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
2945 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
2946 install to get support for a given MIME type. Thanks to
2947 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
2948 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
2949 Unfortunately, not very many packages provide the needed meta
2950 information, Anyway, here is a small script to look up all browser
2951 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
2952
2953 &lt;pre&gt;
2954 #!/usr/bin/python
2955 import sys
2956 import apt
2957 def pkgs_handling_mimetype(mimetype):
2958 cache = apt.Cache()
2959 cache.open(None)
2960 thepkgs = []
2961 for pkg in cache:
2962 version = pkg.candidate
2963 if version is None:
2964 version = pkg.installed
2965 if version is None:
2966 continue
2967 record = version.record
2968 if not record.has_key(&#39;Npp-MimeType&#39;):
2969 continue
2970 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
2971 for t in mime_types:
2972 t = t.rstrip().strip()
2973 if t == mimetype:
2974 thepkgs.append(pkg.name)
2975 return thepkgs
2976 mimetype = &quot;audio/ogg&quot;
2977 if 1 &lt; len(sys.argv):
2978 mimetype = sys.argv[1]
2979 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
2980 for pkg in pkgs_handling_mimetype(mimetype):
2981 print &quot; %s&quot; %pkg
2982 &lt;/pre&gt;
2983
2984 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
2985
2986 &lt;pre&gt;
2987 % ./apt-find-browserplug-for-mimetype
2988 Browser plugin packages supporting audio/ogg:
2989 gecko-mediaplayer
2990 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
2991 Browser plugin packages supporting application/x-shockwave-flash:
2992 browser-plugin-gnash
2993 %
2994 &lt;/pre&gt;
2995
2996 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
2997 itself to query for plugins and propose to install the needed
2998 packages. It would be great if Debian supported such feature too. Is
2999 anyone working on adding it?&lt;/p&gt;
3000
3001 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3002 request for icweasel support for this feature is
3003 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3004 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3005 of manpower and wish for a different design is the reason thus feature
3006 is not yet in iceweasel from Debian.&lt;/p&gt;
3007 </description>
3008 </item>
3009
3010 <item>
3011 <title>What is the most supported MIME type in Debian?</title>
3012 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3013 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3014 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3015 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3016 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3017 proposal to make it possible for a Desktop application to propose to
3018 the user some package to install to gain support for a given MIME
3019 type, font, library etc. that is currently missing. With such
3020 mechanism in place, it would be possible for the desktop to
3021 automatically propose and install leocad if some LDraw file is
3022 downloaded by the browser.&lt;/p&gt;
3023
3024 &lt;p&gt;To get some idea about the current content of the archive, I decided
3025 to write a simple program to extract all .desktop files from the
3026 Debian archive and look up the claimed MIME support there. The result
3027 can be found on the
3028 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3029 site&lt;/a&gt;. Using the collected information, it become possible to
3030 answer the question in the title. Here are the 20 most supported MIME
3031 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3032 The complete list is available from the link above.&lt;/p&gt;
3033
3034 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3035
3036 &lt;pre&gt;
3037 count MIME type
3038 ----- -----------------------
3039 32 text/plain
3040 30 audio/mpeg
3041 29 image/png
3042 28 image/jpeg
3043 27 application/ogg
3044 26 audio/x-mp3
3045 25 image/tiff
3046 25 image/gif
3047 22 image/bmp
3048 22 audio/x-wav
3049 20 audio/x-flac
3050 19 audio/x-mpegurl
3051 18 video/x-ms-asf
3052 18 audio/x-musepack
3053 18 audio/x-mpeg
3054 18 application/x-ogg
3055 17 video/mpeg
3056 17 audio/x-scpls
3057 17 audio/ogg
3058 16 video/x-ms-wmv
3059 &lt;/pre&gt;
3060
3061 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3062
3063 &lt;pre&gt;
3064 count MIME type
3065 ----- -----------------------
3066 33 text/plain
3067 32 image/png
3068 32 image/jpeg
3069 29 audio/mpeg
3070 27 image/gif
3071 26 image/tiff
3072 26 application/ogg
3073 25 audio/x-mp3
3074 22 image/bmp
3075 21 audio/x-wav
3076 19 audio/x-mpegurl
3077 19 audio/x-mpeg
3078 18 video/mpeg
3079 18 audio/x-scpls
3080 18 audio/x-flac
3081 18 application/x-ogg
3082 17 video/x-ms-asf
3083 17 text/html
3084 17 audio/x-musepack
3085 16 image/x-xbitmap
3086 &lt;/pre&gt;
3087
3088 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3089
3090 &lt;pre&gt;
3091 count MIME type
3092 ----- -----------------------
3093 31 text/plain
3094 31 image/png
3095 31 image/jpeg
3096 29 audio/mpeg
3097 28 application/ogg
3098 27 image/gif
3099 26 image/tiff
3100 26 audio/x-mp3
3101 23 audio/x-wav
3102 22 image/bmp
3103 21 audio/x-flac
3104 20 audio/x-mpegurl
3105 19 audio/x-mpeg
3106 18 video/x-ms-asf
3107 18 video/mpeg
3108 18 audio/x-scpls
3109 18 application/x-ogg
3110 17 audio/x-musepack
3111 16 video/x-ms-wmv
3112 16 video/x-msvideo
3113 &lt;/pre&gt;
3114
3115 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3116 information mentioned in DEP-11. I have not yet had time to look at
3117 it, but hope the PackageKit people in Debian are on top of these
3118 issues.&lt;/p&gt;
3119
3120 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3121 discovering a typo in my script.&lt;/p&gt;
3122 </description>
3123 </item>
3124
3125 <item>
3126 <title>Using modalias info to find packages handling my hardware</title>
3127 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3128 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3129 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3130 <description>&lt;p&gt;Yesterday, I wrote about the
3131 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3132 values provided by the Linux kernel&lt;/a&gt; following my hope for
3133 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3134 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3135 modalias values attached to package names can be used to map packages
3136 to hardware. This allow the system to look up and suggest relevant
3137 packages when I plug in some new hardware into my machine, and replace
3138 discover and discover-data as the database used to map hardware to
3139 packages.&lt;/p&gt;
3140
3141 &lt;p&gt;I create a modaliases file with entries like the following,
3142 containing package name, kernel module name (if relevant, otherwise
3143 the package name) and globs matching the relevant hardware
3144 modalias.&lt;/p&gt;
3145
3146 &lt;p&gt;&lt;blockquote&gt;
3147 Package: package-name
3148 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3149 &lt;/blockquote&gt;&lt;/p&gt;
3150
3151 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3152 for a given modalias value using this file.&lt;/p&gt;
3153
3154 &lt;p&gt;An entry like this would suggest the video and picture application
3155 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3156
3157 &lt;p&gt;&lt;blockquote&gt;
3158 Package: cheese
3159 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3160 &lt;/blockquote&gt;&lt;/p&gt;
3161
3162 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3163 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3164
3165 &lt;p&gt;&lt;blockquote&gt;
3166 Package: pcmciautils
3167 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3168 &lt;/blockquote&gt;&lt;/p&gt;
3169
3170 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3171 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3172
3173 &lt;p&gt;&lt;blockquote&gt;
3174 Package: colorhug-client
3175 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3176 &lt;/blockquote&gt;&lt;/p&gt;
3177
3178 &lt;p&gt;I believe the format is compatible with the format of the Packages
3179 file in the Debian archive. Ubuntu already uses their Packages file
3180 to store their mappings from packages to hardware.&lt;/p&gt;
3181
3182 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3183 announce the hardware it support in a way my prototype understand.
3184 This allow those publishing packages in an APT source outside the
3185 Debian archive as well as those backporting packages to make sure the
3186 hardware mapping are included in the package meta information. I&#39;ve
3187 tested such header in the pymissile package, and its modalias mapping
3188 is working as it should with my prototype. It even made it to Ubuntu
3189 Raring.&lt;/p&gt;
3190
3191 &lt;p&gt;To test if it was possible to look up supported hardware using only
3192 the shell tools available in the Debian installer, I wrote a shell
3193 implementation of the lookup code. The idea is to create files for
3194 each modalias and let the shell do the matching. Please check out and
3195 try the
3196 &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;
3197 shell script. It run without any extra dependencies and fetch the
3198 hardware mappings from the Debian archive and the subversion
3199 repository where I currently work on my prototype.&lt;/p&gt;
3200
3201 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3202 install yubikey-personalization:&lt;/p&gt;
3203
3204 &lt;p&gt;&lt;blockquote&gt;
3205 % ./hw-support-lookup
3206 &lt;br&gt;yubikey-personalization
3207 &lt;br&gt;%
3208 &lt;/blockquote&gt;&lt;/p&gt;
3209
3210 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3211 propose to install the pcmciautils package:&lt;/p&gt;
3212
3213 &lt;p&gt;&lt;blockquote&gt;
3214 % ./hw-support-lookup
3215 &lt;br&gt;pcmciautils
3216 &lt;br&gt;%
3217 &lt;/blockquote&gt;&lt;/p&gt;
3218
3219 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3220 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3221 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3222
3223 &lt;p&gt;It could be possible to generate several of the mappings between
3224 packages and hardware. One source would be to look at packages with
3225 kernel modules, ie packages with *.ko files in /lib/modules/, and
3226 extract their modalias information. Another would be to look at
3227 packages with udev rules, ie packages with files in
3228 /lib/udev/rules.d/, and extract their vendor/model information to
3229 generate a modalias matching rule. I have not tested any of these to
3230 see if it work.&lt;/p&gt;
3231
3232 &lt;p&gt;If you want to help implementing a system to let us propose what
3233 packages to install when new hardware is plugged into a Debian
3234 machine, please send me an email or talk to me on
3235 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3236 </description>
3237 </item>
3238
3239 <item>
3240 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3241 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3242 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3243 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3244 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3245 information, to find the packages that support a given piece of
3246 hardware, I refreshed my memory regarding modalias values, and decided
3247 to document the details. Here are my findings so far, also available
3248 in
3249 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3250 Debian Edu subversion repository&lt;/a&gt;:
3251
3252 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3253
3254 &lt;p&gt;This document try to explain what the different types of modalias
3255 values stands for. It is in part based on information from
3256 &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;,
3257 &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;,
3258 &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
3259 &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;.
3260
3261 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3262 this shell script:&lt;/p&gt;
3263
3264 &lt;pre&gt;
3265 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3266 &lt;/pre&gt;
3267
3268 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3269 using modinfo:&lt;/p&gt;
3270
3271 &lt;pre&gt;
3272 % /sbin/modinfo psmouse | grep alias:
3273 alias: serio:ty05pr*id*ex*
3274 alias: serio:ty01pr*id*ex*
3275 %
3276 &lt;/pre&gt;
3277
3278 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3279
3280 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3281 Bridge memory controller:&lt;/p&gt;
3282
3283 &lt;p&gt;&lt;blockquote&gt;
3284 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3285 &lt;/blockquote&gt;&lt;/p&gt;
3286
3287 &lt;p&gt;This represent these values:&lt;/p&gt;
3288
3289 &lt;pre&gt;
3290 v 00008086 (vendor)
3291 d 00002770 (device)
3292 sv 00001028 (subvendor)
3293 sd 000001AD (subdevice)
3294 bc 06 (bus class)
3295 sc 00 (bus subclass)
3296 i 00 (interface)
3297 &lt;/pre&gt;
3298
3299 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3300 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3301 0600. The 0600 class is a host bridge. Other useful bus values are
3302 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3303
3304 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3305 means.&lt;/p&gt;
3306
3307 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3308
3309 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3310 USB hub in a laptop:&lt;/p&gt;
3311
3312 &lt;p&gt;&lt;blockquote&gt;
3313 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3314 &lt;/blockquote&gt;&lt;/p&gt;
3315
3316 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3317
3318 &lt;pre&gt;
3319 v 1D6B (device vendor)
3320 p 0001 (device product)
3321 d 0206 (bcddevice)
3322 dc 09 (device class)
3323 dsc 00 (device subclass)
3324 dp 00 (device protocol)
3325 ic 09 (interface class)
3326 isc 00 (interface subclass)
3327 ip 00 (interface protocol)
3328 &lt;/pre&gt;
3329
3330 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3331 class is in the interface class section. For a simple USB web camera,
3332 these alias entries show up:&lt;/p&gt;
3333
3334 &lt;p&gt;&lt;blockquote&gt;
3335 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3336 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3337 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3338 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3339 &lt;/blockquote&gt;&lt;/p&gt;
3340
3341 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3342 camera), 0101 is audio control device and 0102 is audio streaming (aka
3343 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3344
3345 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3346
3347 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3348 receiver in a Thinkpad X40:&lt;/p&gt;
3349
3350 &lt;p&gt;&lt;blockquote&gt;
3351 acpi:IBM0071:PNP0511:
3352 &lt;/blockquote&gt;&lt;/p&gt;
3353
3354 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3355
3356 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3357
3358 &lt;p&gt;The DMI table contain lots of information about the computer case
3359 and model. This is an entry for a IBM Thinkpad X40, fetched from
3360 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3361
3362 &lt;p&gt;&lt;blockquote&gt;
3363 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3364 &lt;/blockquote&gt;&lt;/p&gt;
3365
3366 &lt;p&gt;The values present are&lt;/p&gt;
3367
3368 &lt;pre&gt;
3369 bvn IBM (BIOS vendor)
3370 bvr 1UETB6WW(1.66) (BIOS version)
3371 bd 06/15/2005 (BIOS date)
3372 svn IBM (system vendor)
3373 pn 2371H4G (product name)
3374 pvr ThinkPadX40 (product version)
3375 rvn IBM (board vendor)
3376 rn 2371H4G (board name)
3377 rvr NotAvailable (board version)
3378 cvn IBM (chassis vendor)
3379 ct 10 (chassis type)
3380 cvr NotAvailable (chassis version)
3381 &lt;/pre&gt;
3382
3383 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3384 found in the dmidecode source:&lt;/p&gt;
3385
3386 &lt;pre&gt;
3387 3 Desktop
3388 4 Low Profile Desktop
3389 5 Pizza Box
3390 6 Mini Tower
3391 7 Tower
3392 8 Portable
3393 9 Laptop
3394 10 Notebook
3395 11 Hand Held
3396 12 Docking Station
3397 13 All In One
3398 14 Sub Notebook
3399 15 Space-saving
3400 16 Lunch Box
3401 17 Main Server Chassis
3402 18 Expansion Chassis
3403 19 Sub Chassis
3404 20 Bus Expansion Chassis
3405 21 Peripheral Chassis
3406 22 RAID Chassis
3407 23 Rack Mount Chassis
3408 24 Sealed-case PC
3409 25 Multi-system
3410 26 CompactPCI
3411 27 AdvancedTCA
3412 28 Blade
3413 29 Blade Enclosing
3414 &lt;/pre&gt;
3415
3416 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3417 table. For example my home server is a tower, but the DMI modalias
3418 claim it is a desktop.&lt;/p&gt;
3419
3420 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3421
3422 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3423 test machine:&lt;/p&gt;
3424
3425 &lt;p&gt;&lt;blockquote&gt;
3426 serio:ty01pr00id00ex00
3427 &lt;/blockquote&gt;&lt;/p&gt;
3428
3429 &lt;p&gt;The values present are&lt;/p&gt;
3430
3431 &lt;pre&gt;
3432 ty 01 (type)
3433 pr 00 (prototype)
3434 id 00 (id)
3435 ex 00 (extra)
3436 &lt;/pre&gt;
3437
3438 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3439 the valid values are.&lt;/p&gt;
3440
3441 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3442
3443 &lt;p&gt;There are heaps of other modalias subtypes according to
3444 file2alias.c. There is the rest of the list from that source: amba,
3445 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3446 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3447 vmbus, x86cpu and zorro. I did not spend time documenting all of
3448 these, as they do not seem relevant for my intended use with mapping
3449 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3450
3451 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3452
3453 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3454 one can use the following shell script:&lt;/p&gt;
3455
3456 &lt;pre&gt;
3457 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3458 echo &quot;$id&quot; ; \
3459 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3460 done
3461 &lt;/pre&gt;
3462
3463 &lt;p&gt;The output can look like this (only the first few entries as the
3464 list is very long on my test machine):&lt;/p&gt;
3465
3466 &lt;pre&gt;
3467 acpi:ACPI0003:
3468 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3469 acpi:device:
3470 FATAL: Module acpi:device: not found.
3471 acpi:IBM0068:
3472 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3473 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3474 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3475 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3476 acpi:IBM0071:PNP0511:
3477 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3478 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3479 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3480 [...]
3481 &lt;/pre&gt;
3482
3483 &lt;p&gt;If you want to help implementing a system to let us propose what
3484 packages to install when new hardware is plugged into a Debian
3485 machine, please send me an email or talk to me on
3486 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3487
3488 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3489 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3490 in /sys/ with space in them.&lt;/p&gt;
3491 </description>
3492 </item>
3493
3494 <item>
3495 <title>Moved the pymissile Debian packaging to collab-maint</title>
3496 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3497 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3498 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3499 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3500 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3501 Launcher and updated the Debian package
3502 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3503 sure udev will fix the device permissions when it is plugged in. I
3504 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3505 hopefully make the package be proposed by jockey in Ubuntu when a user
3506 plug in his rocket launcher. In the process I moved the source to a
3507 git repository under collab-maint, to make it easier for any DD to
3508 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3509 is not very active, but the software still work for me even after five
3510 years of relative silence. The new git repository is not listed in
3511 the uploaded package yet, because I want to test the other changes a
3512 bit more before I upload the new version. If you want to check out
3513 the new version with a .desktop file included, visit the
3514 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3515 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3516 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3517 </description>
3518 </item>
3519
3520 <item>
3521 <title>Lets make hardware dongles easier to use in Debian</title>
3522 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3524 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3525 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3526 general, is that there is a great package management system with the
3527 ability to automatically install software packages by downloading them
3528 from the distribution mirrors, but no way to get it to automatically
3529 install the packages I need to use the hardware I plug into my
3530 machine. Even if the package to use it is easily available from the
3531 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3532 suggest to automatically install the python-nxt, nbc and t2n packages
3533 I need to talk to it. When I plug in a Yubikey, it could propose the
3534 yubikey-personalization package. The information required to do this
3535 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3536
3537 &lt;p&gt;Some years ago, I proposed to
3538 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
3539 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
3540 simple:
3541
3542 &lt;ul&gt;
3543
3544 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
3545 starting when a user log in.&lt;/li&gt;
3546
3547 &lt;li&gt;Set this program up to listen for kernel events emitted when new
3548 hardware is inserted into the computer.&lt;/li&gt;
3549
3550 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
3551 database mapping to packages, and take note of any non-installed
3552 packages.&lt;/li&gt;
3553
3554 &lt;li&gt;Show a message to the user proposing to install the discovered
3555 package, and make it easy to install it.&lt;/li&gt;
3556
3557 &lt;/ul&gt;
3558
3559 &lt;p&gt;I am not sure what the best way to implement this is, but my
3560 initial idea was to use dbus events to discover new hardware, the
3561 discover database to find packages and
3562 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
3563 packages.&lt;/p&gt;
3564
3565 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
3566 draft package is now checked into
3567 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3568 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
3569 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
3570 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3571 the relevant packages in Debian, and uploaded a new version
3572 2.2013.01.09 to unstable. I also discovered that the current
3573 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
3574 package in Debian no longer discovered any USB devices, because
3575 /proc/bus/usb/devices is no longer present. I ported it to use
3576 libusb as a fall back option to get it working. The fixed package
3577 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
3578 because of the freeze).&lt;/p&gt;
3579
3580 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
3581 desktop notification to show up (only once, the first time it is
3582 inserted):&lt;/p&gt;
3583
3584 &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;
3585
3586 &lt;p&gt;For this prototype to be really useful, some way to automatically
3587 install the proposed packages by pressing the &quot;Please install
3588 program(s)&quot; button should to be implemented.&lt;/p&gt;
3589
3590 &lt;p&gt;If this idea seem useful to you, and you want to help make it
3591 happen, please help me update the discover-data database with mappings
3592 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
3593 list the package you would like to have installed when a given
3594 hardware device is inserted into your computer, and report bugs using
3595 reportbug if it isn&#39;t. Or, if you know of a better way to provide
3596 such mapping, please let me know.&lt;/p&gt;
3597
3598 &lt;p&gt;This prototype need more work, and there are several questions that
3599 should be considered before it is ready for production use. Is dbus
3600 the correct way to detect new hardware? At the moment I look for HAL
3601 dbus events on the system bus, because that is the events I could see
3602 on my Debian Squeeze KDE desktop. Are there better events to use?
3603 How should the user be notified? Is the desktop notification
3604 mechanism the best option, or should the background daemon raise a
3605 popup instead? How should packages be installed? When should they
3606 not be installed?&lt;/p&gt;
3607
3608 &lt;p&gt;If you want to help getting such feature implemented in Debian,
3609 please send me an email. :)&lt;/p&gt;
3610 </description>
3611 </item>
3612
3613 <item>
3614 <title>New IRC channel for LEGO designers using Debian</title>
3615 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
3616 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
3617 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
3618 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
3619 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
3620 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
3621 discovered I had to build all the tools myself because none were
3622 already in Debian Squeeze. If Debian support for LEGO is something
3623 you care about, please join me on the IRC channel
3624 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
3625 irc.debian.org). There is a lot that could be done to improve the
3626 Debian support for LEGO designers. For example both CAD software
3627 and Mindstorm compilers are missing. :)&lt;/p&gt;
3628
3629 &lt;p&gt;Update 2012-01-03: A
3630 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
3631 including links to Lego related packages is now available.&lt;/p&gt;
3632 </description>
3633 </item>
3634
3635 <item>
3636 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
3637 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
3638 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
3639 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
3640 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
3641 year! I hope next year will prove to be a good year.&lt;/p&gt;
3642
3643 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
3644 decentralised &quot;currency&quot; that allow people to transfer bitcoins
3645 between each other with minimal overhead, is a very interesting
3646 experiment. And as I wrote a few days ago, the bitcoin situation in
3647 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
3648 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
3649 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
3650 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
3651 for one of the ftpmasters to approve the new bitcoin-qt package
3652 name.&lt;/p&gt;
3653
3654 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3655 team in Debian, you can easily test the package in Debian Squeeze
3656 using the following steps to get a set of working packages:&lt;/p&gt;
3657
3658 &lt;blockquote&gt;&lt;pre&gt;
3659 git clone git://git.debian.org/git/collab-maint/bitcoin
3660 cd bitcoin
3661 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3662 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3663 &lt;/pre&gt;&lt;/blockquote&gt;
3664
3665 &lt;p&gt;You might have to install some build dependencies as well. The
3666 list of commands should give you two packages, bitcoind and
3667 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3668 client will download the complete set of bitcoin &quot;blocks&quot;, which need
3669 around 5.6 GiB of data on my machine at the moment. Make sure your
3670 ~/.bitcoin/ directory have lots of spare room if you want to download
3671 all the blocks. The client will warn if the disk is getting full, so
3672 there is not really a problem if you got too little room, but you will
3673 not be able to get all the features out of the client.&lt;/p&gt;
3674
3675 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3676 activities, please send Bitcoin donations to my address
3677 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3678 </description>
3679 </item>
3680
3681 <item>
3682 <title>A word on bitcoin support in Debian</title>
3683 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
3684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
3685 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
3686 <description>&lt;p&gt;It has been a while since I wrote about
3687 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
3688 peer-to-peer based crypto-currency, and the reason is simply that I
3689 have been busy elsewhere. But two days ago, I started looking at the
3690 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
3691 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
3692 is now maintained by a
3693 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
3694 people&lt;/a&gt;, and the grunt work had already been done by this team. We
3695 owe a huge thank you to all these team members. :)
3696 But I was sad to discover that the bitcoin client is missing in
3697 Wheezy. It is only available in Sid (and an outdated client from
3698 backports). The client had several RC bugs registered in BTS blocking
3699 it from entering testing. To try to help the team and improve the
3700 situation, I spent some time providing patches and triaging the bug
3701 reports. I also had a look at the bitcoin package available from Matt
3702 Corallo in a
3703 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
3704 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
3705 Debian package.&lt;/p&gt;
3706
3707 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
3708 IRC, I pushed several patches into the collab-maint git repository to
3709 improve the package. It now contains fixes for the RC issues (not from
3710 me, but fixed by Scott Howard), build rules for a Qt GUI client
3711 package, konqueror support for the bitcoin: URI and bash completion
3712 setup. As I work on Debian Squeeze, I also created
3713 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
3714 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
3715 it and try to integrate it into the git repository before uploading a
3716 new version to unstable.
3717
3718 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
3719 centralized control currently exercised in the monetary system. I
3720 find it completely unacceptable that the USA government is collecting
3721 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3722 that the major credit card companies can block legal money
3723 transactions to Wikileaks. But for bitcoin to succeed, more people
3724 need to use bitcoins, and more people need to accept bitcoins when
3725 they sell products and services. Improving the bitcoin support in
3726 Debian is a small step in the right direction, but not enough.
3727 Unfortunately the user experience when browsing the web and wanting to
3728 pay with bitcoin is still not very good. The bitcoin: URI is a step
3729 in the right direction, but need to work in most or every browser in
3730 use. Also the bitcoin-qt client is too heavy to fire up to do a
3731 quick transaction. I believe there are other clients available, but
3732 have not tested them.&lt;/p&gt;
3733
3734 &lt;p&gt;My
3735 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
3736 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
3737 I received 20.15 BTC so far on the address I provided in my blog two
3738 years ago, as can be
3739 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
3740 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
3741 donation. The blockexplorer service demonstrates quite well that
3742 bitcoin is not quite anonymous and untracked. :) I wonder if the
3743 number of users have gone up since then. If you use bitcoin and want
3744 to show your support of my activity, please send Bitcoin donations to
3745 the same address as last time,
3746 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3747 </description>
3748 </item>
3749
3750 <item>
3751 <title>Git repository for song book for Computer Scientists</title>
3752 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
3753 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
3754 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
3755 <description>&lt;p&gt;As I
3756 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
3757 this summer&lt;/a&gt;, I have created a Computer Science song book a few
3758 years ago, and today I finally found time to create a public
3759 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
3760 repository for the project&lt;/a&gt;.&lt;/p&gt;
3761
3762 &lt;p&gt;If you want to help out, please clone the source and submit patches
3763 to the HTML version. To generate the PDF and PostScript version,
3764 please use prince XML, or let me know about a useful free software
3765 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
3766
3767 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
3768 PostScript formats at
3769 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
3770 Science Songbook&lt;/a&gt;.&lt;/p&gt;
3771 </description>
3772 </item>
3773
3774 <item>
3775 <title>Gratulerer med 19-årsdagen, Debian!</title>
3776 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
3777 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
3778 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
3779 <description>&lt;p&gt;I dag fyller
3780 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
3781 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
3782 si gratulerer med dagen, Debian!&lt;/p&gt;
3783 </description>
3784 </item>
3785
3786 <item>
3787 <title>Song book for Computer Scientists</title>
3788 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
3789 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
3790 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
3791 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
3792 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
3793 collecting computer related songs for use at parties. The original
3794 version was written in LaTeX, but a few years ago I got help from
3795 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3796 while keeping the ability to create a nice book in PDF format. I have
3797 not had time to maintain the book for a while now, and guess I should
3798 put it up on some public version control repository where others can
3799 help me extend and update the book. If anyone is volunteering to help
3800 me with this, send me an email. Also let me know if there are songs
3801 missing in my book.&lt;/p&gt;
3802
3803 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
3804 me today that I really should let all my readers share the joys of
3805 singing out load about programming, computers and computer networks.
3806 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
3807 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
3808 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
3809 Computer Science Songbook&lt;/a&gt;.
3810 </description>
3811 </item>
3812
3813 <item>
3814 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
3815 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
3816 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
3817 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
3818 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
3819 around 1000 at the moment. To be able to get help from the vendors
3820 when something go wrong, we want to keep the firmware on the servers
3821 up to date. If the firmware isn&#39;t the latest and greatest, the
3822 vendors typically refuse to start debugging any problems until the
3823 firmware is upgraded. So before every reboot, we want to upgrade the
3824 firmware, and we would really like everyone handling servers at the
3825 university to do this themselves when they plan to reboot a machine.
3826 For that to happen we at the unix server admin group need to provide
3827 the tools to do so.&lt;/p&gt;
3828
3829 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
3830 fetch and install the latest firmware for the servers we got. Most of
3831 our hardware are from Dell and HP, so I have focused on these servers
3832 so far. This blog post is about the Dell part.&lt;/P&gt;
3833
3834 &lt;p&gt;On the Dell FTP site I was lucky enough to find
3835 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
3836 with firmware information for all 11th generation servers, listing
3837 which firmware should be used on a given model and where on the FTP
3838 site I can find it. Using a simple perl XML parser I can then
3839 download the shell scripts Dell provides to do firmware upgrades from
3840 within Linux and reboot when all the firmware is primed and ready to
3841 be activated on the first reboot.&lt;/p&gt;
3842
3843 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
3844 Are there anyone working on similar tools for firmware upgrading all
3845 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
3846
3847 &lt;p&gt;&lt;pre&gt;
3848 #!/usr/bin/perl
3849 use strict;
3850 use warnings;
3851 use File::Temp qw(tempdir);
3852 BEGIN {
3853 # Install needed RHEL packages if missing
3854 my %rhelmodules = (
3855 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
3856 );
3857 for my $module (keys %rhelmodules) {
3858 eval &quot;use $module;&quot;;
3859 if ($@) {
3860 my $pkg = $rhelmodules{$module};
3861 system(&quot;yum install -y $pkg&quot;);
3862 eval &quot;use $module;&quot;;
3863 }
3864 }
3865 }
3866 my $errorsto = &#39;pere@hungry.com&#39;;
3867
3868 upgrade_dell();
3869
3870 exit 0;
3871
3872 sub run_firmware_script {
3873 my ($opts, $script) = @_;
3874 unless ($script) {
3875 print STDERR &quot;fail: missing script name\n&quot;;
3876 exit 1
3877 }
3878 print STDERR &quot;Running $script\n\n&quot;;
3879
3880 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
3881 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
3882 } else {
3883 print STDERR &quot;fail: firmware script returned error\n&quot;;
3884 }
3885 }
3886
3887 sub run_firmware_scripts {
3888 my ($opts, @dirs) = @_;
3889 # Run firmware packages
3890 for my $dir (@dirs) {
3891 print STDERR &quot;info: Running scripts in $dir\n&quot;;
3892 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
3893 while (my $s = readdir $dh) {
3894 next if $s =~ m/^\.\.?/;
3895 run_firmware_script($opts, &quot;$dir/$s&quot;);
3896 }
3897 closedir $dh;
3898 }
3899 }
3900
3901 sub download {
3902 my $url = shift;
3903 print STDERR &quot;info: Downloading $url\n&quot;;
3904 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
3905 }
3906
3907 sub upgrade_dell {
3908 my @dirs;
3909 my $product = `dmidecode -s system-product-name`;
3910 chomp $product;
3911
3912 if ($product =~ m/PowerEdge/) {
3913
3914 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
3915 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
3916
3917 my $tmpdir = tempdir(
3918 CLEANUP =&gt; 1
3919 );
3920 chdir($tmpdir);
3921 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
3922 system(&#39;gunzip Catalog.xml.gz&#39;);
3923 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
3924 # -q is quiet, disabling interactivity and reducing console output
3925 my $fwopts = &quot;-q&quot;;
3926 if (@paths) {
3927 for my $url (@paths) {
3928 fetch_dell_fw($url);
3929 }
3930 run_firmware_scripts($fwopts, $tmpdir);
3931 } else {
3932 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3933 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3934 }
3935 chdir(&#39;/&#39;);
3936 } else {
3937 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3938 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3939 }
3940 }
3941
3942 sub fetch_dell_fw {
3943 my $path = shift;
3944 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
3945 download($url);
3946 }
3947
3948 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
3949 # firmware packages to download from Dell. Only work for Linux
3950 # machines and 11th generation Dell servers.
3951 sub fetch_dell_fw_list {
3952 my $filename = shift;
3953
3954 my $product = `dmidecode -s system-product-name`;
3955 chomp $product;
3956 my ($mybrand, $mymodel) = split(/\s+/, $product);
3957
3958 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
3959
3960 my $xml = XMLin($filename);
3961 my @paths;
3962 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
3963 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
3964 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
3965 my $oscode;
3966 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
3967 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
3968 } else {
3969 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
3970 }
3971 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
3972 {
3973 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
3974 }
3975 }
3976 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
3977 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
3978
3979 # Drop application packages, only firmware and BIOS
3980 next if &#39;APAC&#39; eq $componenttype;
3981
3982 my $cpath = $component-&gt;{path};
3983 for my $path (@paths) {
3984 if ($cpath =~ m%/$path$%) {
3985 push(@paths, $cpath);
3986 }
3987 }
3988 }
3989 return @paths;
3990 }
3991 &lt;/pre&gt;
3992
3993 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
3994 it could work on other platforms with some tweaking. Anyone know a
3995 index like Catalog.xml is available from HP for HP servers? At the
3996 moment I maintain a similar list manually and it is quickly getting
3997 outdated.&lt;/p&gt;
3998 </description>
3999 </item>
4000
4001 <item>
4002 <title>How is booting into runlevel 1 different from single user boots?</title>
4003 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4004 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4005 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4006 <description>&lt;p&gt;Wouter Verhelst have some
4007 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4008 comments and opinions&lt;/a&gt; on my blog post on
4009 &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
4010 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4011 &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
4012 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4013 small piece of his comment now, and though it best to address the
4014 misunderstanding he bring forward:&lt;/p&gt;
4015
4016 &lt;p&gt;&lt;blockquote&gt;
4017 Currently, a system admin has four options: [...] boot to a
4018 single-user system (by adding &#39;single&#39; to the kernel command line;
4019 this runs rcS and rc1 scripts)
4020 &lt;/blockquote&gt;&lt;/p&gt;
4021
4022 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4023 and booting into runlevel 1 is the same. I am not surprised he
4024 believe this, because it would make sense and is a quite sensible
4025 thing to believe. But because the boot in Debian is slightly broken,
4026 runlevel 1 do not work properly and it isn&#39;t the same as single user
4027 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4028 hard to explain.&lt;/p&gt;
4029
4030 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4031 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4032 executed in single user mode is sulogin. Single user mode is a boot
4033 state &quot;between&quot; the runlevels, and when booting into single user mode,
4034 only the scripts in /etc/rcS.d/ are executed before the init process
4035 enters the single user state. When switching to runlevel 1, the state
4036 is in fact not ending in runlevel 1, but it passes through runlevel 1
4037 and end up in the single user mode (see /etc/rc1.d/S03single, which
4038 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4039 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4040 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4041 mode).&lt;/p&gt;
4042
4043 &lt;p&gt;This summary might make it clearer. When booting for the first
4044 time into single user mode, the following commands are executed:
4045 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4046 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4047 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4048 trying to continue after visiting single user mode. Not all services
4049 are started again as they should, causing the machine to end up in an
4050 unpredicatble state. This is why Debian admins recommend rebooting
4051 after visiting single user mode.&lt;/p&gt;
4052
4053 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4054 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4055 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4056 stopped when passing through the scripts in /etc/rc1.d/, and not
4057 started again when switching away from runlevel 1 to the runlevels
4058 2-5. I believe the problem is best fixed by moving all the scripts
4059 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4060 functioning single user mode during boot.&lt;/p&gt;
4061
4062 &lt;p&gt;I have spent several years investigating the Debian boot system,
4063 and discovered this problem a few years ago. I suspect it originates
4064 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4065 </description>
4066 </item>
4067
4068 <item>
4069 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4070 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4071 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4072 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4073 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4074 are started from /etc/rcS.d/. In fact, there is a bite more of them
4075 than make sense, and this causes a few problems. What kind of
4076 problems, you might ask. There are at least two problems. The first
4077 is that it is not possible to recover a machine after switching to
4078 runlevel 1. One need to actually reboot to get the machine back to
4079 the expected state. The other is that single user boot will sometimes
4080 run into problems because some of the subsystems are activated before
4081 the root login is presented, causing problems when trying to recover a
4082 machine from a problem in that subsystem. A minor additional point is
4083 that moving more scripts out of rcS.d/ and into the other rc#.d/
4084 directories will increase the amount of scripts that can run in
4085 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4086
4087 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4088 scripts that _have_ to execute before the root login prompt is
4089 presented during a single user boot should go there. Everything else
4090 should go into the numeric runlevels. This means things like
4091 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4092 the numeric runlevels. Today in Debian, there are around 115 init.d
4093 scripts that are started from rcS.d/, and most of them should be moved
4094 out. Do your package have one of them? Please help us make single
4095 user and runlevel 1 better by moving it.&lt;/p&gt;
4096
4097 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4098 etc. should still be started from rcS.d/, but there is for example no
4099 need to have the network enabled before the single user login prompt
4100 is presented.&lt;/p&gt;
4101
4102 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4103 Debian systems working while scripts migrate and during upgrades, the
4104 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4105 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4106 and the next ones can only be moved when their dependencies have been
4107 moved first. This migration must be done sequentially while we ensure
4108 that the package system upgrade packages in the right order to keep
4109 the system state correct. This will require some coordination when it
4110 comes to network related packages, but most of the packages with
4111 scripts that should migrate do not have anything in rcS.d/ depending
4112 on them. Some packages have already been updated, like the sudo
4113 package, while others are still left to do. I wish I had time to work
4114 on this myself, but real live constrains make it unlikely that I will
4115 find time to push this forward.&lt;/p&gt;
4116 </description>
4117 </item>
4118
4119 <item>
4120 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4121 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4123 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4124 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4125 mentioned the issues I believe should be improved in Debian for its
4126 desktop to be useful for more people. The use case for this is my
4127 parents, which are currently running Kubuntu which solve the
4128 issues.&lt;/p&gt;
4129
4130 &lt;p&gt;I suspect these four missing features are not very hard to
4131 implement. After all, they are present in Ubuntu, so if we wanted to
4132 do this in Debian we would have a source.&lt;/p&gt;
4133
4134 &lt;ol&gt;
4135
4136 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4137 are new packages available for upgrades, a icon in the KDE status bar
4138 indicate this, and clicking on it will activate the simple upgrade
4139 tool to handle it. I have no problem guiding both of my parents
4140 through the process over the phone. If a kernel reboot is required,
4141 this too is indicated by the status bars and the upgrade tool. Last
4142 time I checked, nothing with the same features was working in KDE in
4143 Debian.&lt;/li&gt;
4144
4145 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4146 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4147 currently have a handler for, it will ask the user if the system
4148 should search for a package that would add support for this MIME type,
4149 and if the user say yes, the APT sources will be searched for packages
4150 advertising the MIME type in their control file (visible in the
4151 Packages file in the APT archive). If one or more packages are found,
4152 it is a simple click of the mouse to add support for the missing mime
4153 type. If the package require the user to accept some non-free
4154 license, this is explained to the user. The entire process make it
4155 more clear to the user why something do not work in the browser, and
4156 make the chances higher for the user to blame the web page authors and
4157 not the browser for any missing features.&lt;/li&gt;
4158
4159 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4160 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4161 it is not supporting, a dialog pop up asking the user if the system
4162 should search for a package that would add support for it. This
4163 happen with things like MP3, Windows Media or H.264. The selection
4164 and installation procedure is very similar to the Firefox browser
4165 plugin handling. This is as far as I know implemented using a
4166 gstreamer hook. The end result is that the user easily get access to
4167 the codecs that are present from the APT archives available, while
4168 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4169
4170 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4171 displaying a text/plain file in my Debian browser, it will propose to
4172 start emacs to show it. If I remember correctly, when doing the same
4173 in Kunbutu it show the file as a text file in the browser. At least I
4174 know Opera will show text files within the browser. I much prefer the
4175 latter behaviour.&lt;/li&gt;
4176
4177 &lt;/ol&gt;
4178
4179 &lt;p&gt;There are other nice features as well, like the simplified suite
4180 upgrader, but given that I am the one mostly doing the dist-upgrade,
4181 it do not matter much.&lt;/p&gt;
4182
4183 &lt;p&gt;I really hope we could get these features in place for the next
4184 Debian release. It would require the coordinated effort of several
4185 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4186 </description>
4187 </item>
4188
4189 <item>
4190 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4191 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4192 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4193 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4194 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4195 site is build on Debian/Squeeze, and this platform was chosen because
4196 I am most familiar with Debian (being a Debian Developer for around 10
4197 years) because it is the latest stable Debian release which should get
4198 security support for a few years.&lt;/p&gt;
4199
4200 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4201 that are missing in Debian at the moment. It would be great if these
4202 modules were added to the Debian archive, allowing anyone to set up
4203 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4204 in their own country using only Debian packages. The list of modules
4205 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4206 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4207 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4208 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4209 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4210 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4211 easier in the future.&lt;/p&gt;
4212
4213 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4214 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4215 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4216 with the responsibility of tracking security problems, which I really
4217 do not have time for.&lt;/p&gt;
4218 </description>
4219 </item>
4220
4221 <item>
4222 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4223 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4224 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4225 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4226 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4227 posts have been in Norwegian the last few weeks, so here is a short
4228 update in English.&lt;/p&gt;
4229
4230 &lt;p&gt;The kids still keep me too busy to get much free software work
4231 done, but I did manage to organise a project to get a Norwegian port
4232 of the British service
4233 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4234 and it has been running for a month now. The entire project has been
4235 organised by me and two others. Around Christmas we gathered sponsors
4236 to fund the development work. In January I drafted a contract with
4237 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4238 and in February the development took place. Most of it involved
4239 converting the source to use GPS coordinates instead of British
4240 easting/northing, and the resulting code should be a lot easier to get
4241 running in any country by now. The Norwegian
4242 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4243 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4244 source and the source for administrative borders in Norway, and
4245 support for this had to be added/fixed.&lt;/p&gt;
4246
4247 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4248 polishing the system before we announced it March 7th. The system is
4249 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4250 problem reports in a few weeks. Soon we hope to announce the Android
4251 and iPhone versions making it even easier to report problems with the
4252 public infrastructure.&lt;/p&gt;
4253
4254 &lt;p&gt;Perhaps something to consider for those of you in countries without
4255 such service?&lt;/p&gt;
4256 </description>
4257 </item>
4258
4259 <item>
4260 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4261 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4262 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4263 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4264 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4265 issues here at my work with the University of Oslo. My idea is that
4266 it should be possible to use the information about security issues
4267 available on the Internet, and check our locally
4268 maintained/distributed software against this information. It should
4269 allow us to verify that no known security issues are forgotten. The
4270 CVE database listing vulnerabilities seem like a great central point,
4271 and by using the package lists from Debian mapped to CVEs provided by
4272 the testing security team, I believed it should be possible to figure
4273 out which security holes were present in our free software
4274 collection.&lt;/p&gt;
4275
4276 &lt;p&gt;After reading up on the topic, it became obvious that the first
4277 building block is to be able to name software packages in a unique and
4278 consistent way across data sources. I considered several ways to do
4279 this, for example coming up with my own naming scheme like using URLs
4280 to project home pages or URLs to the Freshmeat entries, or using some
4281 existing naming scheme. And it seem like I am not the first one to
4282 come across this problem, as MITRE already proposed and implemented a
4283 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4284 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4285 software, hardware and other platform components. The CPE ids are
4286 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4287 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4288 issues for any CPE name. With this in place, all I need to do is to
4289 locate the CPE id for the software packages we use at the university.
4290 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4291 NVD entry if a CVE for the package exist).&lt;/p&gt;
4292
4293 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4294 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4295 check out, one could look up
4296 &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
4297 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4298 The most recent one is
4299 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4300 and at the bottom of the NVD page for this vulnerability the complete
4301 list of affected versions is provided.&lt;/p&gt;
4302
4303 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4304 for offline processing of issues. Using this dump, I&#39;ve written a
4305 small script taking a list of CPEs as input and list all CVEs
4306 affecting the packages represented by these CPEs. One give it CPEs
4307 with version numbers as specified above and get a list of open
4308 security issues out.&lt;/p&gt;
4309
4310 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4311 information need to be high. For that to happen, I believe as many as
4312 possible need to use and contribute to the NVD database. I notice
4313 RHEL is providing
4314 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4315 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4316 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4317
4318 &lt;p&gt;To get an idea about the quality for free software, I spent some
4319 time making it possible to compare the CVE database from Debian with
4320 the CVE database in NVD. The result look fairly good, but there are
4321 some inconsistencies in NVD (same software package having several
4322 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4323 Debian believe are affected by a CVE). Hope to find time to improve
4324 the quality of NVD, but that require being able to get in touch with
4325 someone maintaining it. So far my three emails with questions and
4326 corrections have not seen any reply, but I hope contact can be
4327 established soon.&lt;/p&gt;
4328
4329 &lt;p&gt;An interesting application for CPEs is cross platform package
4330 mapping. It would be useful to know which packages in for example
4331 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4332 this would be trivial if all linux distributions provided CPE entries
4333 for their packages.&lt;/p&gt;
4334 </description>
4335 </item>
4336
4337 <item>
4338 <title>Which module is loaded for a given PCI and USB device?</title>
4339 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4340 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4341 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4342 <description>&lt;p&gt;In the
4343 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4344 package in Debian, there is a script to report useful information
4345 about the running hardware for use when people report missing
4346 information. One part of this script that I find very useful when
4347 debugging hardware problems, is the part mapping loaded kernel module
4348 to the PCI device it claims. It allow me to quickly see if the kernel
4349 module I expect is driving the hardware I am struggling with. To see
4350 the output, make sure discover-data is installed and run
4351 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4352 one of my machines like this:&lt;/p&gt;
4353
4354 &lt;pre&gt;
4355 loaded modules:
4356 10de:03eb i2c_nforce2
4357 10de:03f1 ohci_hcd
4358 10de:03f2 ehci_hcd
4359 10de:03f0 snd_hda_intel
4360 10de:03ec pata_amd
4361 10de:03f6 sata_nv
4362 1022:1103 k8temp
4363 109e:036e bttv
4364 109e:0878 snd_bt87x
4365 11ab:4364 sky2
4366 &lt;/pre&gt;
4367
4368 &lt;p&gt;The code in question look like this, slightly modified for
4369 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4370
4371 &lt;pre&gt;
4372 if [ -d /sys/bus/pci/devices/ ] ; then
4373 echo loaded pci modules:
4374 (
4375 cd /sys/bus/pci/devices/
4376 for address in * ; do
4377 if [ -d &quot;$address/driver/module&quot; ] ; then
4378 module=`cd $address/driver/module ; pwd -P | xargs basename`
4379 if grep -q &quot;^$module &quot; /proc/modules ; then
4380 address=$(echo $address |sed s/0000://)
4381 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4382 echo &quot;$id $module&quot;
4383 fi
4384 fi
4385 done
4386 )
4387 echo
4388 fi
4389 &lt;/pre&gt;
4390
4391 &lt;p&gt;Similar code could be used to extract USB device module
4392 mappings:&lt;/p&gt;
4393
4394 &lt;pre&gt;
4395 if [ -d /sys/bus/usb/devices/ ] ; then
4396 echo loaded usb modules:
4397 (
4398 cd /sys/bus/usb/devices/
4399 for address in * ; do
4400 if [ -d &quot;$address/driver/module&quot; ] ; then
4401 module=`cd $address/driver/module ; pwd -P | xargs basename`
4402 if grep -q &quot;^$module &quot; /proc/modules ; then
4403 address=$(echo $address |sed s/0000://)
4404 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4405 if [ &quot;$id&quot; ] ; then
4406 echo &quot;$id $module&quot;
4407 fi
4408 fi
4409 fi
4410 done
4411 )
4412 echo
4413 fi
4414 &lt;/pre&gt;
4415
4416 &lt;p&gt;This might perhaps be something to include in other tools as
4417 well.&lt;/p&gt;
4418 </description>
4419 </item>
4420
4421 <item>
4422 <title>How to test if a laptop is working with Linux</title>
4423 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4424 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4425 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4426 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4427 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4428 batch of computers will work with Linux. Every year for the last few
4429 years the university have organised shared bid of a few thousand
4430 computers, and this year HP won the bid. Two different desktops and
4431 five different laptops are on the list this year. We in the UNIX
4432 group want to know which one of these computers work well with RHEL
4433 and Ubuntu, the two Linux distributions we currently handle at the
4434 university.&lt;/p&gt;
4435
4436 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4437 perhaps inspire others to test hardware as well. To test, I PXE
4438 install the OS version of choice, and log in as my normal user and run
4439 a few applications and plug in selected pieces of hardware. When
4440 something fail, I make a note about this in the test matrix and move
4441 on. If I have some spare time I try to report the bug to the OS
4442 vendor, but as I only have the machines for a short time, I rarely
4443 have the time to do this for all the problems I find.&lt;/p&gt;
4444
4445 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4446 I perform on a new model.&lt;/p&gt;
4447
4448 &lt;ul&gt;
4449
4450 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4451 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4452 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4453
4454 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4455 installation, X.org is working.&lt;/li&gt;
4456
4457 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4458 package mesa-utils on Ubuntu) and writing down the frames per second
4459 reported by the program.&lt;/li&gt;
4460
4461 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4462 logging in, and if I can hear this the test is successful. If there
4463 are several audio exits on the machine, I try them all and check if
4464 the Gnome/KDE audio mixer can control where to send the sound. I
4465 normally test this by playing
4466 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4467 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4468
4469 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4470 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4471
4472 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4473 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4474
4475 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4476 picture from the v4l device show up.&lt;/li&gt;
4477
4478 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4479 any bluetooth devices are discovered. In my office, I normally see a
4480 few.&lt;/li&gt;
4481
4482 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4483 memory modules lying around, and stick them in and see if Gnome/KDE
4484 notice this.&lt;/li&gt;
4485
4486 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4487 special button work, and if the laptop continue to work after
4488 resume.&lt;/li&gt;
4489
4490 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4491 adjusting background light, switching on/off external video output,
4492 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4493 laptop to laptop, so I just write down which are working and which are
4494 not.&lt;/li&gt;
4495
4496 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4497 acceleration sensors etc. I rarely test these, as I do not know how
4498 to quickly test if they are working or not, so I only document their
4499 existence.&lt;/li&gt;
4500
4501 &lt;/ul&gt;
4502
4503 &lt;p&gt;By now I suspect you are really curious what the test results are
4504 for the HP machines I am testing. I&#39;m not done yet, so I will report
4505 the test results later. For now I can report that HP 8100 Elite work
4506 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4507 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4508 can see, I have most machines left to test. One interesting
4509 observation is that Ubuntu Lucid has almost twice the frame rate than
4510 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4511 </description>
4512 </item>
4513
4514 <item>
4515 <title>Some thoughts on BitCoins</title>
4516 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4517 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4518 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4519 <description>&lt;p&gt;As I continue to explore
4520 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4521 what properties the system have, and how it will be affected by laws
4522 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4523
4524 &lt;p&gt;One interesting thing to note is that since the transactions are
4525 verified using a peer to peer network, all details about a transaction
4526 is known to everyone. This means that if a BitCoin address has been
4527 published like I did with mine in my initial post about BitCoin, it is
4528 possible for everyone to see how many BitCoins have been transfered to
4529 that address. There is even a web service to look at the details for
4530 all transactions. There I can see that my address
4531 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4532 have received 16.06 Bitcoin, the
4533 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4534 address of Simon Phipps have received 181.97 BitCoin and the address
4535 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4536 of EFF have received 2447.38 BitCoins so far. Thank you to each and
4537 every one of you that donated bitcoins to support my activity. The
4538 fact that anyone can see how much money was transfered to a given
4539 address make it more obvious why the BitCoin community recommend to
4540 generate and hand out a new address for each transaction. I&#39;m told
4541 there is no way to track which addresses belong to a given person or
4542 organisation without the person or organisation revealing it
4543 themselves, as Simon, EFF and I have done.&lt;/p&gt;
4544
4545 &lt;p&gt;In Norway, and in most other countries, there are laws and
4546 regulations limiting how much money one can transfer across the border
4547 without declaring it. There are money laundering, tax and accounting
4548 laws and regulations I would expect to apply to the use of BitCoin.
4549 If the Skolelinux foundation
4550 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
4551 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
4552 normal bank transfers like EFF is doing, how should this be accounted?
4553 Given that it is impossible to know if money can cross the border or
4554 not, should everything or nothing be declared? What exchange rate
4555 should be used when calculating taxes? Would receivers have to pay
4556 income tax if the foundation were to pay Skolelinux contributors in
4557 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
4558
4559 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
4560 accepted by a lot of users. It must be possible to get easy access to
4561 the currency (as a wage or using currency exchanges), and it must be
4562 easy to spend it. At the moment BitCoin seem fairly easy to get
4563 access to, but there are very few places to spend it. I am not really
4564 a regular user of any of the vendor types currently accepting BitCoin,
4565 so I wonder when my kind of shop would start accepting BitCoins. I
4566 would like to buy electronics, travels and subway tickets, not herbs
4567 and books. :) The currency is young, and this will improve over time
4568 if it become popular, but I suspect regular banks will start to lobby
4569 to get BitCoin declared illegal if it become popular. I&#39;m sure they
4570 will claim it is helping fund terrorism and money laundering (which
4571 probably would be true, as is any currency in existence), but I
4572 believe the problems should be solved elsewhere and not by blaming
4573 currencies.&lt;/p&gt;
4574
4575 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
4576 CPU intensive process that depend on a bit of luck as well (as one is
4577 competing against all the other miners currently spending CPU cycles
4578 to see which one get the next lump of cash). The &quot;winner&quot; get 50
4579 BitCoin when this happen. Yesterday I came across the obvious way to
4580 join forces to increase ones changes of getting at least some coins,
4581 by coordinating the work on mining BitCoins across several machines
4582 and people, and sharing the result if one is lucky and get the 50
4583 BitCoins. Check out
4584 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
4585 if this sounds interesting. I have not had time to try to set up a
4586 machine to participate there yet, but have seen that running on ones
4587 own for a few days have not yield any BitCoins througth mining
4588 yet.&lt;/p&gt;
4589
4590 &lt;p&gt;Update 2010-12-15: Found an &lt;a
4591 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
4592 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
4593 it was interesting to read. The arguments presented seem to be
4594 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
4595 </description>
4596 </item>
4597
4598 <item>
4599 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
4600 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
4601 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
4602 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
4603 <description>&lt;p&gt;With this weeks lawless
4604 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
4605 attacks&lt;/a&gt; on Wikileak and
4606 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
4607 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
4608 not be trusted to handle money transactions.
4609 A blog post from
4610 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
4611 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
4612 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
4613 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
4614 some help from my friend to get it all running, and he even handed me
4615 some bitcoins to get started. I even donated a few bitcoins to Simon
4616 for helping me remember BitCoin.&lt;/p&gt;
4617
4618 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
4619 crypto-currency, decentralised and handled using peer-to-peer
4620 networks. It allows anonymous transactions and prohibits central
4621 control over the transactions, making it impossible for governments
4622 and companies alike to block donations and other transactions. The
4623 source is free software, and while the key dependency wxWidgets 2.9
4624 for the graphical user interface is missing in Debian, the command
4625 line client builds just fine. Hopefully Jonas
4626 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
4627 Debian&lt;/a&gt; soon.&lt;/p&gt;
4628
4629 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
4630 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
4631 bitcoins&lt;/a&gt; when selling services and goods, and there are even
4632 currency &quot;stock&quot; markets where the exchange rate is decided. There
4633 are not many users so far, but the concept seems promising. If you
4634 want to get started and lack a friend with any bitcoins to spare,
4635 you can even get
4636 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
4637 bitcoin at the time of writing). Use
4638 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
4639 on the current exchange rates.&lt;/p&gt;
4640
4641 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
4642 machines. If you want to support my activity, please send Bitcoin
4643 donations to the address
4644 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
4645 </description>
4646 </item>
4647
4648 <item>
4649 <title>Why isn&#39;t Debian Edu using VLC?</title>
4650 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
4651 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
4652 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
4653 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4654 presented, and the winner among the multimedia player were VLC.
4655 Personally, I like VLC, and it is my player of choice when I first try
4656 to play a video file or stream. Only if VLC fail will I drag out
4657 gmplayer to see if it can do better. The reason is mostly the failure
4658 model and trust. When VLC fail, it normally pop up a error message
4659 reporting the problem. When mplayer fail, it normally segfault or
4660 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4661
4662 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4663 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4664 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4665 plugin to play web videos seamlessly, and the VLC browser plugin is
4666 not very good. For example, it lack in-line control buttons, so there
4667 is no way for the user to pause the video. Also, when I
4668 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
4669 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
4670 failed on several video pages where mplayer based plugins worked. If
4671 the browser plugin for VLC was as good as the gecko-mediaplayer
4672 package (which uses mplayer), we would switch.&lt;/P&gt;
4673
4674 &lt;p&gt;While VLC is a good player, its user interface is slightly
4675 annoying. The most annoying feature is its inconsistent use of
4676 keyboard shortcuts. When the player is in full screen mode, its
4677 shortcuts are different from when it is playing the video in a window.
4678 For example, space only work as pause when in full screen mode. I
4679 wish it had consisten shortcuts and that space also would work when in
4680 window mode. Another nice shortcut in gmplayer is [enter] to restart
4681 the current video. It is very nice when playing short videos from the
4682 web and want to restart it when new people arrive to have a look at
4683 what is going on.&lt;/p&gt;
4684 </description>
4685 </item>
4686
4687 <item>
4688 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
4689 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
4690 <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>
4691 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
4692 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
4693 upgrade testing of the
4694 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4695 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
4696 This seem like a very good idea, so I adjusted by test scripts and
4697 can now present the updated result from today:&lt;/p&gt;
4698
4699 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4700
4701 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4702
4703 &lt;blockquote&gt;&lt;p&gt;
4704 apache2.2-bin
4705 aptdaemon
4706 baobab
4707 binfmt-support
4708 browser-plugin-gnash
4709 cheese-common
4710 cli-common
4711 cups-pk-helper
4712 dmz-cursor-theme
4713 empathy
4714 empathy-common
4715 freedesktop-sound-theme
4716 freeglut3
4717 gconf-defaults-service
4718 gdm-themes
4719 gedit-plugins
4720 geoclue
4721 geoclue-hostip
4722 geoclue-localnet
4723 geoclue-manual
4724 geoclue-yahoo
4725 gnash
4726 gnash-common
4727 gnome
4728 gnome-backgrounds
4729 gnome-cards-data
4730 gnome-codec-install
4731 gnome-core
4732 gnome-desktop-environment
4733 gnome-disk-utility
4734 gnome-screenshot
4735 gnome-search-tool
4736 gnome-session-canberra
4737 gnome-system-log
4738 gnome-themes-extras
4739 gnome-themes-more
4740 gnome-user-share
4741 gstreamer0.10-fluendo-mp3
4742 gstreamer0.10-tools
4743 gtk2-engines
4744 gtk2-engines-pixbuf
4745 gtk2-engines-smooth
4746 hamster-applet
4747 libapache2-mod-dnssd
4748 libapr1
4749 libaprutil1
4750 libaprutil1-dbd-sqlite3
4751 libaprutil1-ldap
4752 libart2.0-cil
4753 libboost-date-time1.42.0
4754 libboost-python1.42.0
4755 libboost-thread1.42.0
4756 libchamplain-0.4-0
4757 libchamplain-gtk-0.4-0
4758 libcheese-gtk18
4759 libclutter-gtk-0.10-0
4760 libcryptui0
4761 libdiscid0
4762 libelf1
4763 libepc-1.0-2
4764 libepc-common
4765 libepc-ui-1.0-2
4766 libfreerdp-plugins-standard
4767 libfreerdp0
4768 libgconf2.0-cil
4769 libgdata-common
4770 libgdata7
4771 libgdu-gtk0
4772 libgee2
4773 libgeoclue0
4774 libgexiv2-0
4775 libgif4
4776 libglade2.0-cil
4777 libglib2.0-cil
4778 libgmime2.4-cil
4779 libgnome-vfs2.0-cil
4780 libgnome2.24-cil
4781 libgnomepanel2.24-cil
4782 libgpod-common
4783 libgpod4
4784 libgtk2.0-cil
4785 libgtkglext1
4786 libgtksourceview2.0-common
4787 libmono-addins-gui0.2-cil
4788 libmono-addins0.2-cil
4789 libmono-cairo2.0-cil
4790 libmono-corlib2.0-cil
4791 libmono-i18n-west2.0-cil
4792 libmono-posix2.0-cil
4793 libmono-security2.0-cil
4794 libmono-sharpzip2.84-cil
4795 libmono-system2.0-cil
4796 libmtp8
4797 libmusicbrainz3-6
4798 libndesk-dbus-glib1.0-cil
4799 libndesk-dbus1.0-cil
4800 libopal3.6.8
4801 libpolkit-gtk-1-0
4802 libpt2.6.7
4803 libpython2.6
4804 librpm1
4805 librpmio1
4806 libsdl1.2debian
4807 libsrtp0
4808 libssh-4
4809 libtelepathy-farsight0
4810 libtelepathy-glib0
4811 libtidy-0.99-0
4812 media-player-info
4813 mesa-utils
4814 mono-2.0-gac
4815 mono-gac
4816 mono-runtime
4817 nautilus-sendto
4818 nautilus-sendto-empathy
4819 p7zip-full
4820 pkg-config
4821 python-aptdaemon
4822 python-aptdaemon-gtk
4823 python-axiom
4824 python-beautifulsoup
4825 python-bugbuddy
4826 python-clientform
4827 python-coherence
4828 python-configobj
4829 python-crypto
4830 python-cupshelpers
4831 python-elementtree
4832 python-epsilon
4833 python-evolution
4834 python-feedparser
4835 python-gdata
4836 python-gdbm
4837 python-gst0.10
4838 python-gtkglext1
4839 python-gtksourceview2
4840 python-httplib2
4841 python-louie
4842 python-mako
4843 python-markupsafe
4844 python-mechanize
4845 python-nevow
4846 python-notify
4847 python-opengl
4848 python-openssl
4849 python-pam
4850 python-pkg-resources
4851 python-pyasn1
4852 python-pysqlite2
4853 python-rdflib
4854 python-serial
4855 python-tagpy
4856 python-twisted-bin
4857 python-twisted-conch
4858 python-twisted-core
4859 python-twisted-web
4860 python-utidylib
4861 python-webkit
4862 python-xdg
4863 python-zope.interface
4864 remmina
4865 remmina-plugin-data
4866 remmina-plugin-rdp
4867 remmina-plugin-vnc
4868 rhythmbox-plugin-cdrecorder
4869 rhythmbox-plugins
4870 rpm-common
4871 rpm2cpio
4872 seahorse-plugins
4873 shotwell
4874 software-center
4875 system-config-printer-udev
4876 telepathy-gabble
4877 telepathy-mission-control-5
4878 telepathy-salut
4879 tomboy
4880 totem
4881 totem-coherence
4882 totem-mozilla
4883 totem-plugins
4884 transmission-common
4885 xdg-user-dirs
4886 xdg-user-dirs-gtk
4887 xserver-xephyr
4888 &lt;/p&gt;&lt;/blockquote&gt;
4889
4890 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4891
4892 &lt;blockquote&gt;&lt;p&gt;
4893 cheese
4894 ekiga
4895 eog
4896 epiphany-extensions
4897 evolution-exchange
4898 fast-user-switch-applet
4899 file-roller
4900 gcalctool
4901 gconf-editor
4902 gdm
4903 gedit
4904 gedit-common
4905 gnome-games
4906 gnome-games-data
4907 gnome-nettool
4908 gnome-system-tools
4909 gnome-themes
4910 gnuchess
4911 gucharmap
4912 guile-1.8-libs
4913 libavahi-ui0
4914 libdmx1
4915 libgalago3
4916 libgtk-vnc-1.0-0
4917 libgtksourceview2.0-0
4918 liblircclient0
4919 libsdl1.2debian-alsa
4920 libspeexdsp1
4921 libsvga1
4922 rhythmbox
4923 seahorse
4924 sound-juicer
4925 system-config-printer
4926 totem-common
4927 transmission-gtk
4928 vinagre
4929 vino
4930 &lt;/p&gt;&lt;/blockquote&gt;
4931
4932 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4933
4934 &lt;blockquote&gt;&lt;p&gt;
4935 gstreamer0.10-gnomevfs
4936 &lt;/p&gt;&lt;/blockquote&gt;
4937
4938 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4939
4940 &lt;blockquote&gt;&lt;p&gt;
4941 [nothing]
4942 &lt;/p&gt;&lt;/blockquote&gt;
4943
4944 &lt;p&gt;This is for KDE:&lt;/p&gt;
4945
4946 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4947
4948 &lt;blockquote&gt;&lt;p&gt;
4949 ksmserver
4950 &lt;/p&gt;&lt;/blockquote&gt;
4951
4952 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4953
4954 &lt;blockquote&gt;&lt;p&gt;
4955 kwin
4956 network-manager-kde
4957 &lt;/p&gt;&lt;/blockquote&gt;
4958
4959 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4960
4961 &lt;blockquote&gt;&lt;p&gt;
4962 arts
4963 dolphin
4964 freespacenotifier
4965 google-gadgets-gst
4966 google-gadgets-xul
4967 kappfinder
4968 kcalc
4969 kcharselect
4970 kde-core
4971 kde-plasma-desktop
4972 kde-standard
4973 kde-window-manager
4974 kdeartwork
4975 kdeartwork-emoticons
4976 kdeartwork-style
4977 kdeartwork-theme-icon
4978 kdebase
4979 kdebase-apps
4980 kdebase-workspace
4981 kdebase-workspace-bin
4982 kdebase-workspace-data
4983 kdeeject
4984 kdelibs
4985 kdeplasma-addons
4986 kdeutils
4987 kdewallpapers
4988 kdf
4989 kfloppy
4990 kgpg
4991 khelpcenter4
4992 kinfocenter
4993 konq-plugins-l10n
4994 konqueror-nsplugins
4995 kscreensaver
4996 kscreensaver-xsavers
4997 ktimer
4998 kwrite
4999 libgle3
5000 libkde4-ruby1.8
5001 libkonq5
5002 libkonq5-templates
5003 libnetpbm10
5004 libplasma-ruby
5005 libplasma-ruby1.8
5006 libqt4-ruby1.8
5007 marble-data
5008 marble-plugins
5009 netpbm
5010 nuvola-icon-theme
5011 plasma-dataengines-workspace
5012 plasma-desktop
5013 plasma-desktopthemes-artwork
5014 plasma-runners-addons
5015 plasma-scriptengine-googlegadgets
5016 plasma-scriptengine-python
5017 plasma-scriptengine-qedje
5018 plasma-scriptengine-ruby
5019 plasma-scriptengine-webkit
5020 plasma-scriptengines
5021 plasma-wallpapers-addons
5022 plasma-widget-folderview
5023 plasma-widget-networkmanagement
5024 ruby
5025 sweeper
5026 update-notifier-kde
5027 xscreensaver-data-extra
5028 xscreensaver-gl
5029 xscreensaver-gl-extra
5030 xscreensaver-screensaver-bsod
5031 &lt;/p&gt;&lt;/blockquote&gt;
5032
5033 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5034
5035 &lt;blockquote&gt;&lt;p&gt;
5036 ark
5037 google-gadgets-common
5038 google-gadgets-qt
5039 htdig
5040 kate
5041 kdebase-bin
5042 kdebase-data
5043 kdepasswd
5044 kfind
5045 klipper
5046 konq-plugins
5047 konqueror
5048 ksysguard
5049 ksysguardd
5050 libarchive1
5051 libcln6
5052 libeet1
5053 libeina-svn-06
5054 libggadget-1.0-0b
5055 libggadget-qt-1.0-0b
5056 libgps19
5057 libkdecorations4
5058 libkephal4
5059 libkonq4
5060 libkonqsidebarplugin4a
5061 libkscreensaver5
5062 libksgrd4
5063 libksignalplotter4
5064 libkunitconversion4
5065 libkwineffects1a
5066 libmarblewidget4
5067 libntrack-qt4-1
5068 libntrack0
5069 libplasma-geolocation-interface4
5070 libplasmaclock4a
5071 libplasmagenericshell4
5072 libprocesscore4a
5073 libprocessui4a
5074 libqalculate5
5075 libqedje0a
5076 libqtruby4shared2
5077 libqzion0a
5078 libruby1.8
5079 libscim8c2a
5080 libsmokekdecore4-3
5081 libsmokekdeui4-3
5082 libsmokekfile3
5083 libsmokekhtml3
5084 libsmokekio3
5085 libsmokeknewstuff2-3
5086 libsmokeknewstuff3-3
5087 libsmokekparts3
5088 libsmokektexteditor3
5089 libsmokekutils3
5090 libsmokenepomuk3
5091 libsmokephonon3
5092 libsmokeplasma3
5093 libsmokeqtcore4-3
5094 libsmokeqtdbus4-3
5095 libsmokeqtgui4-3
5096 libsmokeqtnetwork4-3
5097 libsmokeqtopengl4-3
5098 libsmokeqtscript4-3
5099 libsmokeqtsql4-3
5100 libsmokeqtsvg4-3
5101 libsmokeqttest4-3
5102 libsmokeqtuitools4-3
5103 libsmokeqtwebkit4-3
5104 libsmokeqtxml4-3
5105 libsmokesolid3
5106 libsmokesoprano3
5107 libtaskmanager4a
5108 libtidy-0.99-0
5109 libweather-ion4a
5110 libxklavier16
5111 libxxf86misc1
5112 okteta
5113 oxygencursors
5114 plasma-dataengines-addons
5115 plasma-scriptengine-superkaramba
5116 plasma-widget-lancelot
5117 plasma-widgets-addons
5118 plasma-widgets-workspace
5119 polkit-kde-1
5120 ruby1.8
5121 systemsettings
5122 update-notifier-common
5123 &lt;/p&gt;&lt;/blockquote&gt;
5124
5125 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5126 aptitude a bit more similar, but there are still quite a lott of
5127 differences. I have no idea what packages should be installed after
5128 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5129 </description>
5130 </item>
5131
5132 <item>
5133 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5134 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5135 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5136 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5137 <description>&lt;p&gt;Most of the computers in use by the
5138 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5139 are virtual machines. And they have been Xen machines running on a
5140 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5141 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5142 bit harder that it could have been, because we set up the Xen virtual
5143 machines to get the virtual partitions from LVM, which as far as I
5144 know is not supported by KVM. So to migrate, we had to convert
5145 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5146
5147 &lt;p&gt;I found
5148 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5149 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5150 migration. It uses qemu-img from the qemu package to make the disk
5151 image, parted to partition it, losetup and kpartx to present the disk
5152 image partions as devices, and dd to copy the data. I NFS mounted the
5153 new servers storage area on the old server to do the migration.&lt;/p&gt;
5154
5155 &lt;pre&gt;
5156 #!/bin/sh
5157
5158 # Based on
5159 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5160
5161 set -e
5162 set -x
5163
5164 if [ -z &quot;$1&quot; ] ; then
5165 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5166 exit 1
5167 else
5168 host=&quot;$1&quot;
5169 fi
5170
5171 if [ ! -e /dev/vg_data/$host-disk ] ; then
5172 echo &quot;error: unable to find LVM volume for $host&quot;
5173 exit 1
5174 fi
5175
5176 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5177 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5178 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5179 totalsize=$(( ( $disksize + $swapsize ) ))
5180
5181 img=$host.img
5182 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5183 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5184
5185 parted $img mklabel msdos
5186 parted $img mkpart primary linux-swap 0 $disksize
5187 parted $img mkpart primary ext2 $disksize $totalsize
5188 parted $img set 1 boot on
5189
5190 modprobe dm-mod
5191 losetup /dev/loop0 $img
5192 kpartx -a /dev/loop0
5193
5194 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5195 fsck.ext3 -f /dev/mapper/loop0p1 || true
5196 mkswap /dev/mapper/loop0p2
5197
5198 kpartx -d /dev/loop0
5199 losetup -d /dev/loop0
5200 &lt;/pre&gt;
5201
5202 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5203 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5204
5205 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5206 the new disk image attached, installed grub-pc and linux-image-686 and
5207 set up grub to boot from the disk image. After this, the KVM machines
5208 seem to work just fine.&lt;/p&gt;
5209 </description>
5210 </item>
5211
5212 <item>
5213 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5214 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5215 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5216 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5217 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5218 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5219 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5220 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5221
5222 &lt;p&gt;I still do not know what a correct migration should look like, so I
5223 report any differences between apt and aptitude and hope someone else
5224 can see if anything should be changed.&lt;/p&gt;
5225
5226 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5227
5228 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5229
5230 &lt;blockquote&gt;&lt;p&gt;
5231 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5232 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5233 dmz-cursor-theme empathy empathy-common finger
5234 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5235 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5236 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5237 gnome-cards-data gnome-codec-install gnome-core
5238 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5239 gnome-search-tool gnome-session-canberra gnome-spell
5240 gnome-system-log gnome-themes-extras gnome-themes-more
5241 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5242 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5243 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5244 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5245 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5246 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5247 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5248 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5249 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5250 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5251 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5252 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5253 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5254 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5255 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5256 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5257 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5258 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5259 libmono-security2.0-cil libmono-sharpzip2.84-cil
5260 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5261 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5262 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5263 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5264 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5265 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5266 libxalan2-java libxerces2-java media-player-info mesa-utils
5267 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5268 nautilus-sendto-empathy openoffice.org-writer2latex
5269 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5270 python-aptdaemon python-aptdaemon-gtk python-axiom
5271 python-beautifulsoup python-bugbuddy python-clientform
5272 python-coherence python-configobj python-crypto python-cupshelpers
5273 python-cupsutils python-eggtrayicon python-elementtree
5274 python-epsilon python-evolution python-feedparser python-gdata
5275 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5276 python-gtksourceview2 python-httplib2 python-louie python-mako
5277 python-markupsafe python-mechanize python-nevow python-notify
5278 python-opengl python-openssl python-pam python-pkg-resources
5279 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5280 python-tagpy python-twisted-bin python-twisted-conch
5281 python-twisted-core python-twisted-web python-utidylib python-webkit
5282 python-xdg python-zope.interface remmina remmina-plugin-data
5283 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5284 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5285 software-center svgalibg1 system-config-printer-udev
5286 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5287 totem totem-coherence totem-mozilla totem-plugins
5288 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5289 zip
5290 &lt;/p&gt;&lt;/blockquote&gt;
5291
5292 Installed using apt-get, removed with aptitude
5293
5294 &lt;blockquote&gt;&lt;p&gt;
5295 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5296 epiphany-extensions epiphany-gecko evolution-exchange
5297 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5298 gedit-common gnome-app-install gnome-games gnome-games-data
5299 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5300 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5301 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5302 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5303 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5304 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5305 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5306 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5307 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5308 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5309 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5310 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5311 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5312 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5313 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5314 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5315 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5316 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5317 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5318 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5319 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5320 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5321 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5322 sound-juicer swfdec-gnome system-config-printer totem-common
5323 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5324 &lt;/p&gt;&lt;/blockquote&gt;
5325
5326 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5327
5328 &lt;blockquote&gt;&lt;p&gt;
5329 gstreamer0.10-gnomevfs
5330 &lt;/p&gt;&lt;/blockquote&gt;
5331
5332 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5333
5334 &lt;blockquote&gt;&lt;p&gt;
5335 [nothing]
5336 &lt;/p&gt;&lt;/blockquote&gt;
5337
5338 &lt;p&gt;This is for KDE:&lt;/p&gt;
5339
5340 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5341
5342 &lt;blockquote&gt;&lt;p&gt;
5343 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5344 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5345 ghostscript-x git gnome-audio gnugo granatier gs-common
5346 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5347 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5348 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5349 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5350 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5351 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5352 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5353 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5354 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5355 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5356 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5357 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5358 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5359 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5360 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5361 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5362 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5363 libkrossui4 libmailtools-perl libmime-tools-perl
5364 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5365 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5366 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5367 lirc luatex marble networkstatus noatun-plugins
5368 openoffice.org-writer2latex palapeli palapeli-data parley
5369 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5370 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5371 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5372 ttf-sazanami-gothic
5373 &lt;/p&gt;&lt;/blockquote&gt;
5374
5375 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5376
5377 &lt;blockquote&gt;&lt;p&gt;
5378 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5379 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5380 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5381 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5382 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5383 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5384 kitchensync kiten kjumpingcube klatin klettres klickety klines
5385 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5386 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5387 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5388 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5389 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5390 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5391 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5392 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5393 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5394 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5395 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5396 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5397 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5398 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5399 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5400 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5401 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5402 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5403 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5404 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5405 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5406 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5407 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5408 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5409 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5410 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5411 &lt;/p&gt;&lt;/blockquote&gt;
5412
5413 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5414
5415 &lt;blockquote&gt;&lt;p&gt;
5416 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5417 kdeartwork kdebase kdebase-apps kdebase-workspace
5418 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5419 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5420 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5421 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5422 xscreensaver-screensaver-bsod
5423 &lt;/p&gt;&lt;/blockquote&gt;
5424
5425 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5426
5427 &lt;blockquote&gt;&lt;p&gt;
5428 kdebase-bin konq-plugins konqueror
5429 &lt;/p&gt;&lt;/blockquote&gt;
5430 </description>
5431 </item>
5432
5433 <item>
5434 <title>Gnash buildbot slave and Debian kfreebsd</title>
5435 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5436 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5437 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5438 <description>&lt;p&gt;Answering
5439 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5440 call from the Gnash project&lt;/a&gt; for
5441 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5442 current source, I have set up a virtual KVM machine on the Debian
5443 Edu/Skolelinux virtualization host to test the git source on
5444 Debian/Squeeze. I hope this can help the developers in getting new
5445 releases out more often.&lt;/p&gt;
5446
5447 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5448 I have considered setting up a &lt;a
5449 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5450 machine as well. I have also considered using the kfreebsd
5451 architecture in Debian as a file server in NUUG to get access to the 5
5452 TB zfs volume we currently use to store DV video. Because of this, I
5453 finally got around to do a test installation of Debian/Squeeze with
5454 kfreebsd. Installation went fairly smooth, thought I noticed some
5455 visual glitches in the cdebconf dialogs (black cursor left on the
5456 screen at random locations). Have not gotten very far with the
5457 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5458 fatal problem. Have to spend some more time on it to see if it is
5459 useful as a file server for NUUG. Will try to find time to set up a
5460 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5461 </description>
5462 </item>
5463
5464 <item>
5465 <title>Debian in 3D</title>
5466 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5467 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5468 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5469 <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;
5470
5471 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5472 3D linked in from
5473 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5474 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5475 </description>
5476 </item>
5477
5478 <item>
5479 <title>Software updates 2010-10-24</title>
5480 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5481 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5482 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5483 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5484
5485 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5486 raise money for the project is going well. The lower limit of 10
5487 signers was reached in 24 hours, and so far 13 people have signed it.
5488 More signers and more funding is most welcome, and I am really curious
5489 how far we can get before the time limit of December 24 is reached.
5490 :)&lt;/p&gt;
5491
5492 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5493 about what appear to be a great code coverage tool capable of
5494 generating code coverage stats without any changes to the source code.
5495 It is called
5496 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5497 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5498 It is missing in Debian, but the git source built just fine in Squeeze
5499 after I installed libelf-dev, libdwarf-dev, pkg-config and
5500 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5501 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5502
5503 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5504 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5505 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5506 alpha test release of the Squeeze based Debian Edu /
5507 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5508 release. Give it a try if you need a complete linux solution for your
5509 school, including central infrastructure server, workstations, thin
5510 client servers and diskless workstations. A nice touch added
5511 yesterday is RDP support on the thin client servers, for windows
5512 clients to get a Linux desktop on request.&lt;/p&gt;
5513 </description>
5514 </item>
5515
5516 <item>
5517 <title>Some notes on Flash in Debian and Debian Edu</title>
5518 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5519 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5520 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5521 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5522 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5523 second most popular used package that is missing in Debian. The sixth
5524 most popular is flashplayer-mozilla. This is a clear indication that
5525 working flash is important for Debian users. Around 10 percent of the
5526 users submitting data to popcon.debian.org have this package
5527 installed.&lt;/p&gt;
5528
5529 &lt;p&gt;In the report written by Lars Risan in August 2008
5530&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
5531 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5532 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5533 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5534 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5535 web sites require Flash to work, and lacking working Flash support in
5536 the web browser and the problems with installing it was perceived as a
5537 good reason to stay with Windows.&lt;/p&gt;
5538
5539 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
5540 said to be the retarded cousin that did not really understand
5541 everything you told him but could work fairly well. This was a
5542 comment regarding the problems Linux have with proprietary formats and
5543 non-standard web pages, and is sad because it exposes a fairly common
5544 understanding of whose fault it is if web pages that only work in for
5545 example Internet Explorer 6 fail to work on Firefox, and funny because
5546 it explain very well how annoying it is for users when Linux
5547 distributions do not work with the documents they receive or the web
5548 pages they want to visit.&lt;/p&gt;
5549
5550 &lt;p&gt;This is part of the reason why I believe it is important for Debian
5551 and Debian Edu to have a well working Flash implementation in the
5552 distribution, to get at least popular sites as Youtube and Google
5553 Video to working out of the box. For Squeeze, Debian have the chance
5554 to include the latest version of Gnash that will make this happen, as
5555 the new release 0.8.8 was published a few weeks ago and is resting in
5556 unstable. The new version work with more sites that version 0.8.7.
5557 The Gnash maintainers have asked for a freeze exception, but the
5558 release team have not had time to reply to it yet. I hope they agree
5559 with me that Flash is important for the Debian desktop users, and thus
5560 accept the new package into Squeeze.&lt;/p&gt;
5561 </description>
5562 </item>
5563
5564 <item>
5565 <title>Circular package dependencies harms apt recovery</title>
5566 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
5567 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
5568 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
5569 <description>&lt;p&gt;I discovered this while doing
5570 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
5571 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
5572 in Debian still got circular dependencies, and it is often claimed
5573 that apt and aptitude should be able to handle this just fine, but
5574 some times these dependency loops causes apt to fail.&lt;/p&gt;
5575
5576 &lt;p&gt;An example is from todays
5577 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
5578 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
5579 causes perl-modules to fail to upgrade. The cause is simple. If a
5580 package fail to unpack, then only part of packages with the circular
5581 dependency might end up being unpacked when unpacking aborts, and the
5582 ones already unpacked will fail to configure in the recovery phase
5583 because its dependencies are unavailable.&lt;/p&gt;
5584
5585 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
5586
5587 &lt;blockquote&gt;&lt;pre&gt;
5588 dpkg: dependency problems prevent configuration of perl-modules:
5589 perl-modules depends on perl (&gt;= 5.10.1-1); however:
5590 Version of perl on system is 5.10.0-19lenny2.
5591 dpkg: error processing perl-modules (--configure):
5592 dependency problems - leaving unconfigured
5593 &lt;/pre&gt;&lt;/blockquote&gt;
5594
5595 &lt;p&gt;The perl/perl-modules circular dependency is already
5596 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
5597 hopefully be solved as soon as possible, but it is not the only one,
5598 and each one of these loops in the dependency tree can cause similar
5599 failures. Of course, they only occur when there are bugs in other
5600 packages causing the unpacking to fail, but it is rather nasty when
5601 the failure of one package causes the problem to become worse because
5602 of dependency loops.&lt;/p&gt;
5603
5604 &lt;p&gt;Thanks to
5605 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
5606 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
5607 dependencies
5608 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
5609 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
5610
5611 &lt;p&gt;Todays testing also exposed a bug in
5612 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
5613 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
5614 apt-get and aptitude, the latter possibly caused by some circular
5615 dependency. Reported both to BTS to try to get someone to look at
5616 it.&lt;/p&gt;
5617 </description>
5618 </item>
5619
5620 <item>
5621 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
5622 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
5623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
5624 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
5625 <description>&lt;p&gt;This is a
5626 &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;
5627 on my
5628 &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
5629 work&lt;/a&gt; on
5630 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
5631 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
5632
5633 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
5634 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5635 and dhcp3-server-ldap in Debian use the LDAP server. The two
5636 implementations are quite different in how they use LDAP.&lt;/p&gt;
5637
5638 To get this information, I started slapd with debugging enabled and
5639 dumped the debug output to a file to get the LDAP searches performed
5640 on a Debian Edu main-server. Here is a summary.
5641
5642 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
5643
5644 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
5645 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
5646 the web.
5647
5648 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
5649 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
5650 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
5651 reverse entries are in two different subtrees in LDAP with a structure
5652 based on the DNS names, as in tjener.intern and
5653 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5654
5655 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5656 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5657 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5658 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5659 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5660 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5661 forward entries, it is looking for attributes named dnsttl, arecord,
5662 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5663 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5664 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5665 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5666 spfrecord and modifytimestamp. For reverse entries it is looking for
5667 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5668 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5669 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5670 ldapsearch commands could look like this:&lt;/p&gt;
5671
5672 &lt;blockquote&gt;&lt;pre&gt;
5673 ldapsearch -h ldap \
5674 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5675 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5676 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5677 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5678 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5679 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5680
5681 ldapsearch -h ldap \
5682 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5683 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
5684 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5685 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5686 srvrecord naptrrecord modifytimestamp
5687 &lt;/pre&gt;&lt;/blockquote&gt;
5688
5689 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
5690 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5691 example LDAP objects used there. In addition to these objects, the
5692 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5693 also exist.&lt;/p&gt;
5694
5695 &lt;blockquote&gt;&lt;pre&gt;
5696 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5697 objectclass: top
5698 objectclass: dnsdomain
5699 objectclass: domainrelatedobject
5700 dc: tjener
5701 arecord: 10.0.2.2
5702 associateddomain: tjener.intern
5703
5704 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5705 objectclass: top
5706 objectclass: dnsdomain2
5707 objectclass: domainrelatedobject
5708 dc: 2
5709 ptrrecord: tjener.intern
5710 associateddomain: 2.2.0.10.in-addr.arpa
5711 &lt;/pre&gt;&lt;/blockquote&gt;
5712
5713 &lt;p&gt;In strict mode, the server behaves differently. When looking for
5714 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
5715 same base as in the tree mode for a object with filter
5716 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
5717 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5718 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5719 naptrrecord and modifytimestamp. For reverse entires it also do a
5720 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
5721 and the requested attributes are associateddomain, dnsttl and
5722 modifytimestamp. In short, in strict mode the objects with ptrrecord
5723 go away, and the arecord attribute in the forward object is used
5724 instead.&lt;/p&gt;
5725
5726 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
5727 like this:&lt;/p&gt;
5728
5729 &lt;blockquote&gt;&lt;pre&gt;
5730 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5731 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5732 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5733 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5734 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5735 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5736
5737 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5738 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
5739 &lt;/pre&gt;&lt;/blockquote&gt;
5740
5741 &lt;p&gt;In addition to the forward and reverse searches , there is also a
5742 search for SOA records, which behave similar to the forward and
5743 reverse lookups.&lt;/p&gt;
5744
5745 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
5746 specify any objectclass names, and instead look for the attributes it
5747 need to generate a DNS reply. This make it able to work with any
5748 objectclass that provide the needed attributes.&lt;/p&gt;
5749
5750 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
5751 dnsdomain2 schemas. The latter is used for reverse entries like
5752 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
5753
5754 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
5755 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5756 attributes) and domainrelatedobject (for associatedDomain). The use
5757 of structural object classes make it impossible to combine these
5758 classes with the object classes used by DHCP.&lt;/p&gt;
5759
5760 &lt;p&gt;There are other schemas that could be used too, for example the
5761 dnszone structural object class used by Gosa and bind-sdb for the DNS
5762 attributes combined with the domainrelatedobject object class, but in
5763 this case some unused attributes would have to be included as well
5764 (zonename and relativedomainname).&lt;/p&gt;
5765
5766 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
5767 mode and not use any of the existing objectclasses (dnsdomain,
5768 dnsdomain2 and dnszone) when one want to combine the DNS information
5769 with DHCP information, and instead create a auxiliary object class
5770 defined something like this (using the attributes defined for
5771 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
5772
5773 &lt;blockquote&gt;&lt;pre&gt;
5774 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
5775 SUP top
5776 AUXILIARY
5777 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5778 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5779 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5780 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5781 A6Record $ DNAMERecord
5782 ))
5783 &lt;/pre&gt;&lt;/blockquote&gt;
5784
5785 &lt;p&gt;This will allow any object to become a DNS entry when combined with
5786 the domainrelatedobject object class, and allow any entity to include
5787 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
5788 developers asking for their view on this schema and if they are
5789 interested in providing such schema with PowerDNS, and I hope my
5790 message will be accepted into their mailing list soon.&lt;/p&gt;
5791
5792 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
5793
5794 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
5795 the object attributes, and then uses the attributes it want. This
5796 make it harder to figure out exactly what attributes are used, but
5797 thanks to the working example in Debian Edu I can at least get an idea
5798 what is needed without having to read the source code.&lt;/p&gt;
5799
5800 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
5801 search filter to use to locate the correct dhcpServer entity is
5802 stored. These are the relevant entries from
5803 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
5804
5805 &lt;blockquote&gt;&lt;pre&gt;
5806 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
5807 ldap-dhcp-server-cn &quot;dhcp&quot;;
5808 &lt;/pre&gt;&lt;/blockquote&gt;
5809
5810 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
5811 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
5812 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
5813 search result is this entry:&lt;/p&gt;
5814
5815 &lt;blockquote&gt;&lt;pre&gt;
5816 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5817 cn: dhcp
5818 objectClass: top
5819 objectClass: dhcpServer
5820 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5821 &lt;/pre&gt;&lt;/blockquote&gt;
5822
5823 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
5824 subtree with DHCP configuration. The DHCP configuration subtree base
5825 is located using a base scope search with base &quot;cn=DHCP
5826 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
5827 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
5828 The search result is this entry:&lt;/p&gt;
5829
5830 &lt;blockquote&gt;&lt;pre&gt;
5831 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5832 cn: DHCP Config
5833 objectClass: top
5834 objectClass: dhcpService
5835 objectClass: dhcpOptions
5836 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5837 dhcpStatements: ddns-update-style none
5838 dhcpStatements: authoritative
5839 dhcpOption: smtp-server code 69 = array of ip-address
5840 dhcpOption: www-server code 72 = array of ip-address
5841 dhcpOption: wpad-url code 252 = text
5842 &lt;/pre&gt;&lt;/blockquote&gt;
5843
5844 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
5845 all the DHCP configuration is loaded, it is ready to receive requests.
5846 The subtree in Debian Edu contain objects with object classes
5847 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5848 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5849 and information about netmasks, dynamic range etc. Leaving out the
5850 details here because it is not relevant for the focus of my
5851 investigation, which is to see if it is possible to merge dns and dhcp
5852 related computer objects.&lt;/p&gt;
5853
5854 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
5855 of the client (00:00:00:00:00:00 in this example), using a subtree
5856 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
5857 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5858 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
5859 like:&lt;/p&gt;
5860
5861 &lt;blockquote&gt;&lt;pre&gt;
5862 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5863 cn: hostname
5864 objectClass: top
5865 objectClass: dhcpHost
5866 dhcpHWAddress: ethernet 00:00:00:00:00:00
5867 dhcpStatements: fixed-address hostname
5868 &lt;/pre&gt;&lt;/blockquote&gt;
5869
5870 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
5871 The object classes need to have fixed names, and the configuration
5872 need to be stored in a fairly specific LDAP structure. On the
5873 positive side, the invidiual dhcpHost entires can be anywhere without
5874 the DN pointed to by the dhcpServer entries. The latter should make
5875 it possible to group all host entries in a subtree next to the
5876 configuration entries, and this subtree can also be shared with the
5877 DNS server if the schema proposed above is combined with the dhcpHost
5878 structural object class.
5879
5880 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
5881
5882 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
5883 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
5884 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
5885 allowing DNS objects to be stored anywhere under the base cn specified
5886 in the configuration.&lt;/p&gt;
5887
5888 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
5889 regarding which LDAP schemas to use and which LDAP structure to use.
5890 I guess one could implement ones own schema, as long as the
5891 objectclasses and attributes have the names used, but this do not
5892 really help when the DHCP subtree need to have a fairly fixed
5893 structure.&lt;/p&gt;
5894
5895 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
5896 this might work for Debian Edu:&lt;/p&gt;
5897
5898 &lt;blockquote&gt;&lt;pre&gt;
5899 ou=services
5900 cn=machine-info (dhcpService) - dhcpServiceDN points here
5901 cn=dhcp (dhcpServer)
5902 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5903 cn=10.0.2.0 (dhcpSubnet)
5904 cn=group1 (dhcpGroup/dhcpOptions)
5905 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5906 cn=192.168.0.0 (dhcpSubnet)
5907 cn=group1 (dhcpGroup/dhcpOptions)
5908 ou=machines - PowerDNS base points here
5909 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5910 &lt;/pre&gt;&lt;/blockquote&gt;
5911
5912 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
5913 entries to be in the dhcpGroup subtrees, the entries can be stored
5914 there instead of a common machines subtree, and the PowerDNS base
5915 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
5916
5917 &lt;p&gt;The combined object under the machines subtree would look something
5918 like this:&lt;/p&gt;
5919
5920 &lt;blockquote&gt;&lt;pre&gt;
5921 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
5922 dc: hostname
5923 objectClass: top
5924 objectClass: dhcpHost
5925 objectclass: domainrelatedobject
5926 objectclass: dnsDomainAux
5927 associateddomain: hostname.intern
5928 arecord: 10.11.12.13
5929 dhcpHWAddress: ethernet 00:00:00:00:00:00
5930 dhcpStatements: fixed-address hostname.intern
5931 &lt;/pre&gt;&lt;/blockquote&gt;
5932
5933 &lt;/p&gt;One could even add the LTSP configuration associated with a given
5934 machine, as long as the required attributes are available in a
5935 auxiliary object class.&lt;/p&gt;
5936 </description>
5937 </item>
5938
5939 <item>
5940 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
5941 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
5942 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
5943 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
5944 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
5945 DHCP services in Debian Edu to use the same LDAP objects for a given
5946 computer, to avoid the possibility of having a inconsistent state for
5947 a computer in LDAP (as in DHCP but no DNS entry or the other way
5948 around) and make it easier to add computers to LDAP.&lt;/p&gt;
5949
5950 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
5951 information finally found a solution that seem to work.&lt;/p&gt;
5952
5953 &lt;p&gt;The old setup required three LDAP objects for a given computer.
5954 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
5955 we switch powerdns to use its strict LDAP method (ldap-method=strict
5956 in pdns-debian-edu.conf), the forward and reverse DNS entries are
5957 merged into one while making it impossible to transfer the reverse map
5958 to a slave DNS server.&lt;/p&gt;
5959
5960 &lt;p&gt;If we also replace the object class used to get the DNS related
5961 attributes to one allowing these attributes to be combined with the
5962 dhcphost object class, we can merge the DNS and DHCP entries into one.
5963 I&#39;ve written such object class in the dnsdomainaux.schema file (need
5964 proper OIDs, but that is a minor issue), and tested the setup. It
5965 seem to work.&lt;/p&gt;
5966
5967 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
5968 for both DNS and DHCP, and even the LTSP configuration I suggested in
5969 an earlier email. The combined LDAP object will look something like
5970 this:&lt;/p&gt;
5971
5972 &lt;blockquote&gt;&lt;pre&gt;
5973 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5974 cn: hostname
5975 objectClass: dhcphost
5976 objectclass: domainrelatedobject
5977 objectclass: dnsdomainaux
5978 associateddomain: hostname.intern
5979 arecord: 10.11.12.13
5980 dhcphwaddress: ethernet 00:00:00:00:00:00
5981 dhcpstatements: fixed-address hostname
5982 ldapconfigsound: Y
5983 &lt;/pre&gt;&lt;/blockquote&gt;
5984
5985 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
5986 the DHCP server uses the dhcphwaddress and dhcpstatements entries
5987 before asking DNS to resolve the fixed-adddress. LTSP will use
5988 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
5989
5990 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
5991 dhcphost in a different location, to allow us to put the objects
5992 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
5993 that. If I can&#39;t figure out a way to do that, we can still get rid of
5994 the hosts subtree and move all its content into the DHCP Config tree
5995 (which probably should be renamed to be more related to the new
5996 content. I suspect cn=dnsdhcp,ou=services or something like that
5997 might be a good place to put it.&lt;/p&gt;
5998
5999 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6000 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6001 </description>
6002 </item>
6003
6004 <item>
6005 <title>Idea for storing LTSP configuration in LDAP</title>
6006 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6007 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6008 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6009 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6010 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6011 clients, and that this can be used to fetch configuration from LDAP if
6012 Debian Edu choose to store configuration there.&lt;/p&gt;
6013
6014 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6015 to get configuration from LDAP. The idea is to look up the MAC
6016 address of the client in LDAP, and look for attributes on the form
6017 ltspconfigsetting=value, and use this to export SETTING=value to the
6018 LTSP clients.&lt;/p&gt;
6019
6020 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6021 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6022 allowing us to store all information about a computer in one place.&lt;/p&gt;
6023
6024 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6025 this approach. A real LDAP schema for the ltspClientAux objectclass
6026 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6027
6028 &lt;blockquote&gt;&lt;pre&gt;
6029 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6030 #
6031 # Fetch LTSP client settings from LDAP based on MAC address
6032 #
6033 # Uses ethernet address as stored in the dhcpHost objectclass using
6034 # the dhcpHWAddress attribute or ethernet address stored in the
6035 # ieee802Device objectclass with the macAddress attribute.
6036 #
6037 # This module is written to be schema agnostic, and only depend on the
6038 # existence of attribute names.
6039 #
6040 # The LTSP configuration variables are saved directly using a
6041 # ltspConfig prefix and uppercasing the rest of the attribute name.
6042 # To set the SERVER variable, set the ltspConfigServer attribute.
6043 #
6044 # Some LDAP schema should be created with all the relevant
6045 # configuration settings. Something like this should work:
6046 #
6047 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6048 # SUP top
6049 # AUXILIARY
6050 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6051
6052 LDAPSERVER=$(debian-edu-ldapserver)
6053 if [ &quot;$LDAPSERVER&quot; ] ; then
6054 LDAPBASE=$(debian-edu-ldapserver -b)
6055 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6056 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6057 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6058 grep &#39;^ltspConfig&#39; | while read attr value ; do
6059 # Remove prefix and convert to upper case
6060 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6061 # bass value on to clients
6062 eval &quot;$attr=$value; export $attr&quot;
6063 done
6064 done
6065 fi
6066 &lt;/pre&gt;&lt;/blockquote&gt;
6067
6068 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6069 the while block might end up in a subshell causing the variables set
6070 there to not show up in ltsp-config, but if that is the case I am sure
6071 the code can be restructured to make sure the variables are passed on.
6072 I expect that can be solved with some testing. :)&lt;/p&gt;
6073
6074 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6075 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6076
6077 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6078 configuration in LDAP that was created around year 2000 by
6079 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6080 Xperience, Inc., 2000&lt;/a&gt;. I found its
6081 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6082 personal home page over at redhat.com.&lt;/p&gt;
6083 </description>
6084 </item>
6085
6086 <item>
6087 <title>jXplorer, a very nice LDAP GUI</title>
6088 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6089 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6090 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6091 <description>&lt;p&gt;Since
6092 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6093 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6094 LDAP GUI that is even better than luma. The java application
6095 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6096 moving LDAP objects and subtrees using drag-and-drop, and can
6097 authenticate using Kerberos. I have only tested the Kerberos
6098 authentication, but do not have a LDAP setup allowing me to rewrite
6099 LDAP with my test user yet. It is
6100 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6101 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6102 have with it is how it handle errors. If something go wrong, its
6103 non-intuitive behaviour require me to go through some query work list
6104 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6105 </description>
6106 </item>
6107
6108 <item>
6109 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6110 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6111 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6112 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6113 <description>&lt;p&gt;Here is a short update on my &lt;a
6114 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6115 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6116 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6117 not reporting the status for KDE, because the upgrade crashes when
6118 aptitude try because of missing conflicts
6119 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6120 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6121
6122 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6123 complete list of the installed packages. Based on this I see these
6124 differences when I did a test run today. As usual, I do not really
6125 know what the correct set of packages would be, but thought it best to
6126 publish the difference.&lt;/p&gt;
6127
6128 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6129
6130 &lt;blockquote&gt;&lt;p&gt;
6131 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6132 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6133 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6134 libgtksourceview-common libpt-1.10.10-plugins-alsa
6135 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6136 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6137 python-4suite-xml python-eggtrayicon python-gtkhtml2
6138 python-gtkmozembed svgalibg1 xserver-xephyr zip
6139 &lt;/p&gt;&lt;/blockquote&gt;
6140
6141 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6142
6143 &lt;blockquote&gt;&lt;p&gt;
6144 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6145 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6146 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6147 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6148 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6149 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6150 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6151 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6152 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6153 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6154 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6155 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6156 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6157 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6158 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6159 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6160 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6161 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6162 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6163 mysql-common swfdec-gnome totem-gstreamer wodim
6164 &lt;/p&gt;&lt;/blockquote&gt;
6165
6166 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6167
6168 &lt;blockquote&gt;&lt;p&gt;
6169 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6170 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6171 xserver-xorg-input-all xserver-xorg-input-evdev
6172 xserver-xorg-input-kbd xserver-xorg-input-mouse
6173 xserver-xorg-input-synaptics xserver-xorg-video-all
6174 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6175 xserver-xorg-video-chips xserver-xorg-video-cirrus
6176 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6177 xserver-xorg-video-glint xserver-xorg-video-i128
6178 xserver-xorg-video-i740 xserver-xorg-video-mach64
6179 xserver-xorg-video-mga xserver-xorg-video-neomagic
6180 xserver-xorg-video-nouveau xserver-xorg-video-nv
6181 xserver-xorg-video-r128 xserver-xorg-video-radeon
6182 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6183 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6184 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6185 xserver-xorg-video-sis xserver-xorg-video-sisusb
6186 xserver-xorg-video-tdfx xserver-xorg-video-tga
6187 xserver-xorg-video-trident xserver-xorg-video-tseng
6188 xserver-xorg-video-vesa xserver-xorg-video-vmware
6189 xserver-xorg-video-voodoo
6190 &lt;/p&gt;&lt;/blockquote&gt;
6191
6192 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6193
6194 &lt;blockquote&gt;&lt;p&gt;
6195 deskbar-applet xserver-xorg xserver-xorg-core
6196 xserver-xorg-input-wacom xserver-xorg-video-intel
6197 xserver-xorg-video-openchrome
6198 &lt;/p&gt;&lt;/blockquote&gt;
6199
6200 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6201 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6202 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6203 No idea when it hits Squeeze, but when it does I hope it will reduce
6204 the difference somewhat.
6205 </description>
6206 </item>
6207
6208 <item>
6209 <title>LUMA, a very nice LDAP GUI</title>
6210 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6211 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6212 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6213 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6214 directory in Debian Edu, and in the process I started to miss a GUI
6215 tool to browse the LDAP tree. The only one I was able to find in
6216 Debian/Squeeze and Lenny is
6217 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6218 be a great tool to get a overview of the current LDAP directory
6219 populated by default in Skolelinux. Thanks to it, I have been able to
6220 find empty and obsolete subtrees, misplaced objects and duplicate
6221 objects. It will be installed by default in Debian/Squeeze. If you
6222 are working with LDAP, give it a go. :)&lt;/p&gt;
6223
6224 &lt;p&gt;I did notice one problem with it I have not had time to report to
6225 the BTS yet. There is no .desktop file in the package, so the tool do
6226 not show up in the Gnome and KDE menus, but only deep down in in the
6227 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6228 released.&lt;/p&gt;
6229
6230 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6231 like to move objects and remove subtrees directly in the GUI, but have
6232 not found a way to do that with LUMA yet. So in the mean time, I use
6233 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6234
6235 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6236 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6237
6238 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6239 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6240 useful GUI alternative. It seem like a good tool, but is unmaintained
6241 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6242 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6243 </description>
6244 </item>
6245
6246 <item>
6247 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6248 <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>
6249 <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>
6250 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6251 <description>&lt;p&gt;A while back, I
6252 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6253 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6254 for storing DNS and DHCP information in LDAP to combine the two sets
6255 of information into one LDAP object representing a computer.&lt;/p&gt;
6256
6257 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6258 the dhcpHost object class auxiliary, to allow it to be combined with
6259 the dNSDomain object class, and thus forming one object for one
6260 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6261
6262 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6263 without also changing the assigned number for the object class, and I
6264 do not know enough about LDAP schema design to do that properly for
6265 Debian Edu.&lt;/p&gt;
6266
6267 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6268 the
6269 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6270 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6271 available today from IETF.&lt;/p&gt;
6272
6273 &lt;pre&gt;
6274 --- dhcp.schema (revision 65192)
6275 +++ dhcp.schema (working copy)
6276 @@ -376,7 +376,7 @@
6277 objectclass ( 2.16.840.1.113719.1.203.6.6
6278 NAME &#39;dhcpHost&#39;
6279 DESC &#39;This represents information about a particular client&#39;
6280 - SUP top
6281 + SUP top AUXILIARY
6282 MUST cn
6283 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6284 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6285 &lt;/pre&gt;
6286
6287 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6288 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6289 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6290
6291 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6292 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6293 </description>
6294 </item>
6295
6296 <item>
6297 <title>Calling tasksel like the installer, while still getting useful output</title>
6298 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6299 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6300 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6301 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6302 installs packages during the normal debian-installer run. Until now,
6303 I have ended up letting tasksel do the work, with the annoying problem
6304 of not getting any feedback at all when something fails (like a
6305 conffile question from dpkg or a download that fails), using code like
6306 this:
6307
6308 &lt;blockquote&gt;&lt;pre&gt;
6309 export DEBIAN_FRONTEND=noninteractive
6310 tasksel --new-install
6311 &lt;/pre&gt;&lt;/blockquote&gt;
6312
6313 This would invoke tasksel, let its automatic task selection pick the
6314 tasks to install, and continue to install the requested tasks without
6315 any output what so ever.
6316
6317 Recently I revisited this problem while working on the automatic
6318 package upgrade testing, because tasksel would some times hang without
6319 any useful feedback, and I want to see what is going on when it
6320 happen. Then it occured to me, I can parse the output from tasksel
6321 when asked to run in test mode, and use that aptitude command line
6322 printed by tasksel then to simulate the tasksel run. I ended up using
6323 code like this:
6324
6325 &lt;blockquote&gt;&lt;pre&gt;
6326 export DEBIAN_FRONTEND=noninteractive
6327 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6328 $cmd
6329 &lt;/pre&gt;&lt;/blockquote&gt;
6330
6331 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6332 --without-recommends -o APT::Install-Recommends=no -y install
6333 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6334 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6335 laptop task and all packages with priority standard , required and
6336 important, just like tasksel would have done it during
6337 installation.&lt;/p&gt;
6338
6339 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6340 install packages without using debconf-apt-progress, for use cases
6341 like this.&lt;/p&gt;
6342 </description>
6343 </item>
6344
6345 <item>
6346 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6347 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6348 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6349 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6350 <description>&lt;p&gt;My
6351 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6352 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6353 finally made the upgrade logs available from
6354 &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;.
6355 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6356 apt and aptitude, and found their differences interesting. This time
6357 I will only focus on their removal plans.&lt;/p&gt;
6358
6359 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6360 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6361 surprising part is that it want to remove xorg and all
6362 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6363 sure why. When asking aptitude to do the same, it want to remove 129
6364 packages, but most of them are library packages I suspect are no
6365 longer needed. Both of them want to remove bluetooth packages, which
6366 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6367
6368 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6369 which seem like a bad idea and xorg the same way as with Gnome. Asking
6370 aptitude for the same, it wants to remove 192 packages, none which are
6371 too surprising.&lt;/p&gt;
6372
6373 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6374 and avoided, and perhaps others as well. Here are the complete list
6375 of planned removals. The complete logs is available from the URL
6376 above. Note if you want to repeat these tests, that the upgrade test
6377 for kde+apt-get hung in the tasksel setup because of dpkg asking
6378 conffile questions. No idea why. I worked around it by using
6379 &#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
6380 continue.&lt;/p&gt;
6381
6382 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6383 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6384 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6385 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6386 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6387 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6388 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6389 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6390 xserver-xorg-input-kbd xserver-xorg-input-mouse
6391 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6392 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6393 xserver-xorg-video-ati xserver-xorg-video-chips
6394 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6395 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6396 xserver-xorg-video-glint xserver-xorg-video-i128
6397 xserver-xorg-video-i740 xserver-xorg-video-imstt
6398 xserver-xorg-video-intel xserver-xorg-video-mach64
6399 xserver-xorg-video-mga xserver-xorg-video-neomagic
6400 xserver-xorg-video-nsc xserver-xorg-video-nv
6401 xserver-xorg-video-openchrome xserver-xorg-video-r128
6402 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6403 xserver-xorg-video-rendition xserver-xorg-video-s3
6404 xserver-xorg-video-s3virge xserver-xorg-video-savage
6405 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6406 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6407 xserver-xorg-video-tga xserver-xorg-video-trident
6408 xserver-xorg-video-tseng xserver-xorg-video-v4l
6409 xserver-xorg-video-vesa xserver-xorg-video-vga
6410 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6411 xulrunner-1.9-gnome-support&lt;/p&gt;
6412
6413 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6414
6415 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6416 djvulibre-desktop finger gnome-app-install gnome-mount
6417 gnome-network-admin gnome-spell gnome-vfs-obexftp
6418 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6419 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6420 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6421 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6422 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6423 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6424 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6425 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6426 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6427 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6428 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6429 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6430 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6431 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6432 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6433 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6434 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6435 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6436 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6437 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6438 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6439 openoffice.org-writer2latex openssl-blacklist p7zip
6440 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6441 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6442 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6443 swfdec-mozilla totem-gstreamer update-manager wodim
6444 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6445 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6446 zip&lt;/p&gt;
6447
6448 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6449
6450 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6451 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6452 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6453 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6454 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6455 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6456 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6457 xserver-xorg-input-kbd xserver-xorg-input-mouse
6458 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6459 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6460 xserver-xorg-video-ati xserver-xorg-video-chips
6461 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6462 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6463 xserver-xorg-video-glint xserver-xorg-video-i128
6464 xserver-xorg-video-i740 xserver-xorg-video-imstt
6465 xserver-xorg-video-intel xserver-xorg-video-mach64
6466 xserver-xorg-video-mga xserver-xorg-video-neomagic
6467 xserver-xorg-video-nsc xserver-xorg-video-nv
6468 xserver-xorg-video-openchrome xserver-xorg-video-r128
6469 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6470 xserver-xorg-video-rendition xserver-xorg-video-s3
6471 xserver-xorg-video-s3virge xserver-xorg-video-savage
6472 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6473 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6474 xserver-xorg-video-tga xserver-xorg-video-trident
6475 xserver-xorg-video-tseng xserver-xorg-video-v4l
6476 xserver-xorg-video-vesa xserver-xorg-video-vga
6477 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6478
6479 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6480 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6481 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6482 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6483 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6484 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6485 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6486 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6487 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6488 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6489 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6490 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6491 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6492 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6493 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6494 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6495 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6496 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6497 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6498 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6499 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6500 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6501 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6502 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6503 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6504 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6505 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6506 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6507 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6508 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6509 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6510 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6511 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6512 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6513 texlive-common texlive-doc-base texlive-fonts-recommended
6514 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6515 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6516 xulrunner-1.9&lt;/p&gt;
6517
6518 </description>
6519 </item>
6520
6521 <item>
6522 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6523 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6524 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6525 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6526 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6527 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6528 have been discovered and reported in the process
6529 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6530 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6531 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6532 kdebase-workspace-data), and to get a more regular testing going on, I
6533 am working on a script to automate the test.&lt;/p&gt;
6534
6535 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6536 Gnome or KDE desktop installation inside the chroot before upgrading
6537 it. To ensure no services are started in the chroot, a policy-rc.d
6538 script is inserted. To make sure tasksel believe it is to install a
6539 desktop on a laptop, the tasksel tests are replaced in the chroot
6540 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
6541
6542 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6543 currently always fail because udev refuses to upgrade with the kernel
6544 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6545 is created. The bug report
6546 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
6547 this problem do not trigger in a chroot, but I touch the file anyway
6548 to make sure the upgrade go well. Testing on virtual and real
6549 hardware have failed me because of udev so far, and creating this file
6550 do the trick in such settings anyway. This is a
6551 &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
6552 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
6553 maintainer because he lack the resources to rewrite udev to keep
6554 working with old kernels or something like that. I really wish the
6555 udev upstream would keep udev backwards compatible, to avoid such
6556 upgrade problem, but given that they fail to do so, I guess
6557 documenting the way out of this mess is the best option we got for
6558 Debian Squeeze.&lt;/p&gt;
6559
6560 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
6561 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
6562 trick:&lt;/p&gt;
6563
6564 &lt;blockquote&gt;&lt;pre&gt;
6565 #!/bin/sh
6566 set -ex
6567
6568 if [ &quot;$1&quot; ] ; then
6569 desktop=$1
6570 else
6571 desktop=gnome
6572 fi
6573
6574 from=lenny
6575 to=squeeze
6576
6577 exec &amp;lt; /dev/null
6578 unset LANG
6579 mirror=http://ftp.skolelinux.org/debian
6580 tmpdir=chroot-$from-upgrade-$to-$desktop
6581 fuser -mv .
6582 debootstrap $from $tmpdir $mirror
6583 chroot $tmpdir aptitude update
6584 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
6585 #!/bin/sh
6586 exit 101
6587 EOF
6588 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6589 exit_cleanup() {
6590 umount $tmpdir/proc
6591 }
6592 mount -t proc proc $tmpdir/proc
6593 # Make sure proc is unmounted also on failure
6594 trap exit_cleanup EXIT INT
6595
6596 chroot $tmpdir aptitude -y install debconf-utils
6597
6598 # Make sure tasksel autoselection trigger. It need the test scripts
6599 # to return the correct answers.
6600 echo tasksel tasksel/desktop multiselect $desktop | \
6601 chroot $tmpdir debconf-set-selections
6602
6603 # Include the desktop and laptop task
6604 for test in desktop laptop ; do
6605 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
6606 #!/bin/sh
6607 exit 2
6608 EOF
6609 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6610 done
6611
6612 DEBIAN_FRONTEND=noninteractive
6613 DEBIAN_PRIORITY=critical
6614 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6615 chroot $tmpdir tasksel --new-install
6616
6617 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
6618 chroot $tmpdir aptitude update
6619 touch $tmpdir/etc/udev/kernel-upgrade
6620 chroot $tmpdir aptitude -y dist-upgrade
6621 fuser -mv
6622 &lt;/pre&gt;&lt;/blockquote&gt;
6623
6624 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
6625 with aptitude, but I have not had time to look at how they behave
6626 differently so far. I hope to get a cron job running to do the test
6627 regularly and post the result on the web. The Gnome upgrade currently
6628 work, while the KDE upgrade fail because of the bug in
6629 kdebase-workspace-data&lt;/p&gt;
6630
6631 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
6632 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
6633 post, so I will refrain from trying. I can report that for Gnome,
6634 aptitude report 760 packages upgraded, 448 newly installed, 129 to
6635 remove and 1 not upgraded and 1024MB need to be downloaded while for
6636 KDE the same numbers are 702 packages upgraded, 507 newly installed,
6637 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
6638
6639 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
6640 is able to migrate to dependency based boot sequencing and parallel
6641 booting without a hitch. Was unsure if there were still bugs with
6642 packages failing to clean up their obsolete init.d script during
6643 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6644 packages.&lt;/p&gt;
6645 </description>
6646 </item>
6647
6648 <item>
6649 <title>Upstart or sysvinit - as init.d scripts see it</title>
6650 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
6651 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
6652 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
6653 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6654 scripts to migrate (some of) their operations to upstart job while
6655 keeping the init.d for hurd and kfreebsd. The packages with such
6656 needs will need a way to get their init.d scripts to behave
6657 differently when used with sysvinit and with upstart. Because of
6658 this, I had a look at the environment variables set when a init.d
6659 script is running under upstart, and when it is not.&lt;/p&gt;
6660
6661 &lt;p&gt;With upstart, I notice these environment variables are set when a
6662 script is started from rcS.d/ (ignoring some irrelevant ones like
6663 COLUMNS):&lt;/p&gt;
6664
6665 &lt;blockquote&gt;&lt;pre&gt;
6666 DEFAULT_RUNLEVEL=2
6667 previous=N
6668 PREVLEVEL=
6669 RUNLEVEL=
6670 runlevel=S
6671 UPSTART_EVENTS=startup
6672 UPSTART_INSTANCE=
6673 UPSTART_JOB=rc-sysinit
6674 &lt;/pre&gt;&lt;/blockquote&gt;
6675
6676 &lt;p&gt;With sysvinit, these environment variables are set for the same
6677 script.&lt;/p&gt;
6678
6679 &lt;blockquote&gt;&lt;pre&gt;
6680 INIT_VERSION=sysvinit-2.88
6681 previous=N
6682 PREVLEVEL=N
6683 RUNLEVEL=S
6684 runlevel=S
6685 &lt;/pre&gt;&lt;/blockquote&gt;
6686
6687 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
6688 sysvinit are not set by upstart. Not sure if it is intentional or not
6689 to not be compatible with sysvinit in this regard.&lt;/p&gt;
6690
6691 &lt;p&gt;For scripts needing to behave differently when upstart is used,
6692 looking for the UPSTART_JOB environment variable seem to be a good
6693 choice.&lt;/p&gt;
6694 </description>
6695 </item>
6696
6697 <item>
6698 <title>A manual for standards wars...</title>
6699 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
6700 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
6701 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
6702 <description>&lt;p&gt;Via the
6703 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
6704 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
6705 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
6706 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
6707 following the standards wars of today.&lt;/p&gt;
6708 </description>
6709 </item>
6710
6711 <item>
6712 <title>Sitesummary tip: Listing computer hardware models used at site</title>
6713 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
6714 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
6715 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
6716 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
6717 to get a list of the machine types in use thanks to the DMI
6718 information extracted from each machine. The script to do so is
6719 included in the sitesummary package, and here is example output from
6720 the Skolelinux build servers:&lt;/p&gt;
6721
6722 &lt;blockquote&gt;&lt;pre&gt;
6723 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6724 vendor count
6725 Dell Computer Corporation 1
6726 PowerEdge 1750 1
6727 IBM 1
6728 eserver xSeries 345 -[8670M1X]- 1
6729 Intel 2
6730 [no-dmi-info] 3
6731 maintainer:~#
6732 &lt;/pre&gt;&lt;/blockquote&gt;
6733
6734 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
6735 provided in each machine. Here there are Intel machines without model
6736 information listed with Intel as vendor and no model, and virtual Xen
6737 machines listed as [no-dmi-info]. One can add -l as a command line
6738 option to list the individual machines.&lt;/p&gt;
6739
6740 &lt;p&gt;A larger list is
6741 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
6742 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
6743 provide the basic sitesummary report publicly. In their report there
6744 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
6745 their machines, and as sitesummary is available in both distributions,
6746 it is trivial to get all of them to report to the same central
6747 collector.&lt;/p&gt;
6748 </description>
6749 </item>
6750
6751 <item>
6752 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
6753 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
6754 <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>
6755 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
6756 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
6757 start at boot when an NVidia video card is used is handled. The
6758 problem seem to be that the nvidia X.org driver uses a long time to
6759 initialize, and this duration is longer than kdm is configured to
6760 wait.&lt;/p&gt;
6761
6762 &lt;p&gt;I came across two bugs related to this issue,
6763 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
6764 against initscripts and passed on to nvidia-glx when it became obvious
6765 that the nvidia drivers were involved, and
6766 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
6767 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
6768
6769 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
6770 problem nvidia video card owners experience and make sure the Debian
6771 distribution work out of the box for these users. The nvidia driver
6772 maintainers expect kdm to be set up to wait longer, while kdm expect
6773 the nvidia driver maintainers to fix the driver to start faster, and
6774 while they wait for each other I guess the users end up switching to a
6775 distribution that work for them. I have no idea what the solution is,
6776 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
6777
6778 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
6779 </description>
6780 </item>
6781
6782 <item>
6783 <title>Parallellized boot seem to hold up well in Debian/testing</title>
6784 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
6785 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
6786 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
6787 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
6788 The feature seem to hold up pretty well, but three fairly serious
6789 issues are known and should be solved:
6790
6791 &lt;p&gt;&lt;ul&gt;
6792
6793 &lt;li&gt;The wicd package seen to
6794 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
6795 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
6796 parallel booting is enabled. No idea why, but the wicd maintainer
6797 seem to be on the case.&lt;/li&gt;
6798
6799 &lt;li&gt;The nvidia X driver seem to
6800 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
6801 triggered more easily when parallel booting is in effect. The
6802 maintainer is on the case.&lt;/li&gt;
6803
6804 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
6805 sequencing (the shutdown is broken) when old file-rc users
6806 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
6807 sysv-rc. One way to solve it would be for file-rc to create
6808 /etc/init.d/.legacy-bootordering, and another is to try to make
6809 sysv-rc more robust. Will investigate some more and probably upload a
6810 workaround in sysv-rc to help those trying to move from file-rc to
6811 sysv-rc get a working shutdown.&lt;/li&gt;
6812
6813 &lt;/ul&gt;&lt;/p&gt;
6814
6815 &lt;p&gt;All in all not many surprising issues, and all of them seem
6816 solvable before Squeeze is released. In addition to these there are
6817 some packages with bugs in their dependencies and run level settings,
6818 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
6819
6820 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6821 the BTS, please usertag the report to get it to show up at
6822 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6823 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6824
6825 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
6826 </description>
6827 </item>
6828
6829 <item>
6830 <title>More flexible firmware handling in debian-installer</title>
6831 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
6832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
6833 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
6834 <description>&lt;p&gt;After a long break from debian-installer development, I finally
6835 found time today to return to the project. Having to spend less time
6836 working dependency based boot in debian, as it is almost complete now,
6837 definitely helped freeing some time.&lt;/p&gt;
6838
6839 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
6840 include some firmware packages on the Debian Edu CDs, those needed to
6841 get disk and network controllers working. Without having these
6842 firmware packages available during installation, it is impossible to
6843 install Debian Edu on the given machine, and because our target group
6844 are non-technical people, asking them to provide firmware packages on
6845 an external medium is a support pain. Initially, I expected it to be
6846 enough to include the firmware packages on the CD to get
6847 debian-installer to find and use them. This proved to be wrong.
6848 Next, I hoped it was enough to symlink the relevant firmware packages
6849 to some useful location on the CD (tried /cdrom/ and
6850 /cdrom/firmware/). This also proved to not work, and at this point I
6851 found time to look at the debian-installer code to figure out what was
6852 going to work.&lt;/p&gt;
6853
6854 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
6855 look revealed that it would only look for firmware packages outside
6856 the installation media, so the CD was never checked for firmware
6857 packages. It would only check USB sticks, floppies and other
6858 &quot;external&quot; media devices. Today I changed it to also look in the
6859 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6860 solve the problem I ran into with Debian edu. I also changed it to
6861 look in /firmware/, to make sure the installer also find firmware
6862 provided in the initrd when booting the installer via PXE, to allow us
6863 to provide the same feature in the PXE setup included in Debian
6864 Edu.&lt;/p&gt;
6865
6866 &lt;p&gt;To make sure firmware deb packages with a license questions are not
6867 activated without asking if the license is accepted, I extended
6868 hw-detect to look for preinst scripts in the firmware packages, and
6869 run these before activating the firmware during installation. The
6870 license question is asked using debconf in the preinst, so this should
6871 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
6872
6873 &lt;p&gt;If you want to discuss the details of these features, please
6874 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
6875 </description>
6876 </item>
6877
6878 <item>
6879 <title>Parallellized boot is now the default in Debian/unstable</title>
6880 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
6881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
6882 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
6883 <description>&lt;p&gt;Since this evening, parallel booting is the default in
6884 Debian/unstable for machines using dependency based boot sequencing.
6885 Apparently the testing of concurrent booting has been wider than
6886 expected, if I am to believe the
6887 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6888 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
6889 with the feature this weekend, to give us some time to detect any
6890 remaining problems before Squeeze is frozen. If serious problems are
6891 detected, it is simple to change the default back to sequential boot.
6892 The upload of the new sysvinit package also activate a new upstream
6893 version.&lt;/p&gt;
6894
6895 More information about
6896 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6897 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
6898 currently possible to disable parallel booting when one run into
6899 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
6900
6901 &lt;blockquote&gt;&lt;pre&gt;
6902 CONCURRENCY=none
6903 &lt;/pre&gt;&lt;/blockquote&gt;
6904
6905 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6906 the BTS, please usertag the report to get it to show up at
6907 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6908 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6909 </description>
6910 </item>
6911
6912 <item>
6913 <title>Sitesummary tip: Listing MAC address of all clients</title>
6914 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
6915 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
6916 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
6917 <description>&lt;p&gt;In the recent Debian Edu versions, the
6918 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
6919 system&lt;/a&gt; is used to keep track of the machines in the school
6920 network. Each machine will automatically report its status to the
6921 central server after boot and once per night. The network setup is
6922 also reported, and using this information it is possible to get the
6923 MAC address of all network interfaces in the machines. This is useful
6924 to update the DHCP configuration.&lt;/p&gt;
6925
6926 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
6927 ist all MAC addresses of all machines reporting to sitesummary. Run
6928 this on the collector host:&lt;/p&gt;
6929
6930 &lt;blockquote&gt;&lt;pre&gt;
6931 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
6932 &lt;/pre&gt;&lt;/blockquote&gt;
6933
6934 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
6935 line per machine and with space between the MAC addresses.&lt;/p&gt;
6936
6937 &lt;p&gt;To allow system administrators easier job at adding static DHCP
6938 addresses for hosts, it would be possible to extend this to fetch
6939 machine information from sitesummary and update the DHCP and DNS
6940 tables in LDAP using this information. Such tool is unfortunately not
6941 written yet.&lt;/p&gt;
6942 </description>
6943 </item>
6944
6945 <item>
6946 <title>systemd, an interesting alternative to upstart</title>
6947 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
6948 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
6949 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
6950 <description>&lt;p&gt;The last few days a new boot system called
6951 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
6952 has been
6953 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
6954
6955 to the free software world. I have not yet had time to play around
6956 with it, but it seem to be a very interesting alternative to
6957 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
6958 a good alternative for Debian when we are able to switch to an event
6959 based boot system. Tollef is
6960 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
6961 systemd into Debian, and I look forward to seeing how well it work. I
6962 like the fact that systemd handles init.d scripts with dependency
6963 information natively, allowing them to run in parallel where upstart
6964 at the moment do not.&lt;/p&gt;
6965
6966 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
6967 platform support. It only work on recent Linux kernels, and also need
6968 some new kernel features enabled to function properly. This means
6969 kFreeBSD and Hurd ports of Debian will need a port or a different boot
6970 system. Not sure how that will be handled if systemd proves to be the
6971 way forward.&lt;/p&gt;
6972
6973 &lt;p&gt;In the mean time, based on the
6974 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6975 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
6976 decided to enable full parallel booting as the default in Debian as
6977 soon as possible (probably this weekend or early next week), to see if
6978 there are any remaining serious bugs in the init.d dependencies. A
6979 new version of the sysvinit package implementing this change is
6980 already in experimental. If all go well, Squeeze will be released
6981 with parallel booting enabled by default.&lt;/p&gt;
6982 </description>
6983 </item>
6984
6985 <item>
6986 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
6987 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
6988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
6989 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
6990 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
6991 complete, so complete that it is actually possible to run all the
6992 init.d scripts in parallell based on these dependencies. If you want
6993 to test your Squeeze system, make sure
6994 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6995 based boot sequencing&lt;/a&gt; is enabled, and add this line to
6996 /etc/default/rcS:&lt;/p&gt;
6997
6998 &lt;blockquote&gt;&lt;pre&gt;
6999 CONCURRENCY=makefile
7000 &lt;/pre&gt;&lt;/blockquote&gt;
7001
7002 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7003 scripts in parallel using the dependency information stored in
7004 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7005 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7006 to try to start the kdm and gdm scripts as early as possible, and will
7007 start the facilities required by kdm or gdm as early as possible to
7008 make this happen.&lt;/p&gt;
7009
7010 &lt;p&gt;Give it a try, and see if you like the result. If some services
7011 fail to start properly, it is most likely because they have incomplete
7012 init.d script dependencies in their startup script (or some of their
7013 dependent scripts have incomplete dependencies). Report bugs and get
7014 the package maintainers to fix it. :)&lt;/p&gt;
7015
7016 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7017 manage to get the init.d script dependencies complete and correct. I
7018 expect we will get there in Squeeze+1, if we get manage to test and
7019 fix the remaining issues.&lt;/p&gt;
7020
7021 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7022 the BTS, please usertag the report to get it to show up at
7023 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7024 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7025 </description>
7026 </item>
7027
7028 <item>
7029 <title>Debian has switched to dependency based boot sequencing</title>
7030 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7032 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7033 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7034 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7035 have been migrated to using dependency based boot sequencing. This
7036 conclude work me and others have been doing for the last three days.
7037 It feels great to see this finally part of the default Debian
7038 installation. Now we just need to weed out the last few problems that
7039 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7040
7041 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7042 fixing the more fundamental problem of handing the event based
7043 non-predictable kernel in the early boot.&lt;/p&gt;
7044 </description>
7045 </item>
7046
7047 <item>
7048 <title>Taking over sysvinit development</title>
7049 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7050 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7051 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7052 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7053 the existing sysvinit upstream developer, I decided a few weeks ago to
7054 take over the package and become the new upstream. The number of
7055 patches to track for the Debian package was becoming a burden, and the
7056 lack of synchronization between the distribution made it hard to keep
7057 the package up to date.&lt;/p&gt;
7058
7059 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7060 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7061 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7062 and Fedora), based on the patches currently in use in these
7063 distributions. We Debian maintainers plan to move to this tarball as
7064 the new upstream as soon as we find time to do the merge. Since the
7065 new tarball was created, we agreed with Werner at SuSe to make a new
7066 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7067 development there. The project is registered and currently waiting
7068 for approval by the Savannah administrators, and as soon as it is
7069 approved, we will import the old versions from svn and continue
7070 working on the future release.&lt;/p&gt;
7071
7072 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7073 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7074 </description>
7075 </item>
7076
7077 <item>
7078 <title>Debian boots quicker and quicker</title>
7079 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7080 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7081 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7082 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7083 people involved in the boot system on Debian and Ubuntu, to see if we
7084 could find more ways to speed up the boot system. This was an Ubuntu
7085 funded
7086 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7087 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7088 of boot systems, and ways to handle the increasing number of boot
7089 issues introduced by the Linux kernel becoming more and more
7090 asynchronous and event base. The Ubuntu approach using udev and
7091 upstart might be a good way forward. Time will show.&lt;/p&gt;
7092
7093 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7094 process in Debian. All of these should be applied to get a quick
7095 boot:&lt;/p&gt;
7096
7097 &lt;ul&gt;
7098
7099 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7100
7101 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7102 clock is in UTC.&lt;/li&gt;
7103
7104 &lt;li&gt;Install and activate the insserv package to enable
7105 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7106 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7107
7108 &lt;/ul&gt;
7109
7110 These points are based on the Google summer of code work done by
7111 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7112 Villegas&lt;/a&gt;.
7113
7114 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7115 unstable yesterday. When we tested it, we were able to cut 6 seconds
7116 from the boot sequence. It depend on very correct dependency
7117 declaration in all init.d scripts, so I expect us to find edge cases
7118 where the dependences in some scripts are slightly wrong when we start
7119 using this.&lt;/p&gt;
7120
7121 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7122 introduced by Raphael Geissert today, one that could affect the
7123 startup speed as well. Instead of starting some scripts concurrently
7124 from rcS.d/ and another set of scripts from rc2.d/, it would be
7125 possible to run a of them in the same process. A quick way to test
7126 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7127 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7128 </description>
7129 </item>
7130
7131 <item>
7132 <title>BSAs påstander om piratkopiering møter motstand</title>
7133 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7134 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7135 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7136 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7137 programvareselskapene som Microsoft og Apple, publisert en rapport der
7138 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7139 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7140 dager siden kom
7141 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7142 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7143 dagene. Et spesielt interessant kommentar fra Sverige,
7144 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7145 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7146
7147 &lt;blockquote&gt;
7148 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7149 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7150 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7151 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7152 &lt;/blockquote&gt;
7153
7154 &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
7155 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7156 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7157 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7158 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7159
7160 &lt;p&gt;Fant lenkene via &lt;a
7161 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7162 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7163 </description>
7164 </item>
7165
7166 <item>
7167 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7168 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7169 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7170 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7171 <description>&lt;p&gt;Kom over
7172 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7173 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7174 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7175 jobber til daglig. En rask opptelling forteller meg at vi har 490
7176 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7177 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7178 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7179 </description>
7180 </item>
7181
7182 <item>
7183 <title>Kryptert harddisk - naturligvis</title>
7184 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7186 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7187 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7188 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7189 når en tar tap av arbeidstid, fortrolige dokumenter,
7190 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7191 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7192 til at jeg har kryptert harddisken på både kontormaskinen og min
7193 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7194 komme på avveie, den første informasjon relatert til jobben min ved
7195 Universitetet i Oslo, og den andre relatert til blant annet
7196 foreningsarbeide. Kryptering av diskene gjør at det er lite
7197 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7198 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7199 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7200 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7201 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7202 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7203 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7204 det er gjort slik jeg gjør det er minimale, og gevinstene er
7205 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7206 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7207
7208 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7209 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7210 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7211 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7212 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7213 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7214 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7215 betydelige.&lt;/p&gt;
7216 </description>
7217 </item>
7218
7219 <item>
7220 <title>Two projects that have improved the quality of free software a lot</title>
7221 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7222 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7223 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7224 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7225 quality of free software, and I wanted to mention both in case someone
7226 do not yet know them.&lt;/p&gt;
7227
7228 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7229 tool to detect and expose errors in the memory handling of programs.
7230 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7231 and it will report any problems on stdout. It is even better if the
7232 program include debug information. With debug information, it is able
7233 to report the source file name and line number where the problem
7234 occurs. It can report things like &#39;reading past memory block in file
7235 X line N, the memory block was allocated in file Y, line M&#39;, and
7236 &#39;using uninitialised value in control logic&#39;. This tool has made it
7237 trivial to investigate reproducible crash bugs in programs, and have
7238 reduced the number of this kind of bugs in free software a lot.
7239
7240 &lt;p&gt;The second one is
7241 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7242 a source code checker. It is able to process the source of a program
7243 and find problems in the logic without running the program. It
7244 started out as the Stanford Checker and became well known when it was
7245 used to find bugs in the Linux kernel. It is now a commercial tool
7246 and the company behind it is running
7247 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7248 free software community, where a lot of free software projects get
7249 their source checked for free. Several thousand defects have been
7250 found and fixed so far. It can find errors like &#39;lock L taken in file
7251 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7252 Y lines O to P can never be executed&#39;. The projects included in the
7253 community service project have managed to get rid of a lot of
7254 reliability problems thanks to Coverity.&lt;/p&gt;
7255
7256 &lt;p&gt;I believe tools like this, that are able to automatically find
7257 errors in the source, are vital to improve the quality of software and
7258 make sure we can get rid of the crashing and failing software we are
7259 surrounded by today.&lt;/p&gt;
7260 </description>
7261 </item>
7262
7263 <item>
7264 <title>No patch is not better than a useless patch</title>
7265 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7266 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7267 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7268 <description>&lt;p&gt;Julien Blache
7269 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7270 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7271 patch allow one to discuss a concrete and proposed solution, and also
7272 prove that the issue at hand is important enough for someone to spent
7273 time on fixing it. No patch do not provide any of these positive
7274 properties.&lt;/p&gt;
7275 </description>
7276 </item>
7277
7278 <item>
7279 <title>Standardize on protocols and formats, not vendors and applications</title>
7280 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7281 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7282 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7283 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7284 very good one to form a long lived computer infrastructure. It is the
7285 simple one, lost by many in todays computer industry: Standardize on
7286 open network protocols and open exchange/storage formats, not applications.
7287 Applications come and go, while protocols and files tend to stay, and
7288 thus one want to make it easy to change application and vendor, while
7289 avoiding conversion costs and locking users to a specific platform or
7290 application.&lt;/p&gt;
7291
7292 &lt;p&gt;This approach make it possible to replace the client applications
7293 independently of the server applications. One can even allow users to
7294 use several different applications as long as they handle the selected
7295 protocol and format. In the normal case, only one client application
7296 is recommended and users only get help if they choose to use this
7297 application, but those that want to deviate from the easy path are not
7298 blocked from doing so.&lt;/p&gt;
7299
7300 &lt;p&gt;It also allow us to replace the server side without forcing the
7301 users to replace their applications, and thus allow us to select the
7302 best server implementation at any moment, when scale and resouce
7303 requirements change.&lt;/p&gt;
7304
7305 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7306 open formats, but I would never recommend standardizing on a single
7307 application that do not use open network protocol or open formats.&lt;/p&gt;
7308 </description>
7309 </item>
7310
7311 <item>
7312 <title>Returning from Skolelinux developer gathering</title>
7313 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7314 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7315 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7316 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7317 Edu/Skolelinux development gathering. I got a bit done tuning the
7318 desktop, and looked into the dynamic service location protocol
7319 implementation avahi. It look like it could be useful for us. Almost
7320 30 people participated, and I believe it was a great environment to
7321 get to know the Skolelinux system. Walter Bender, involved in the
7322 development of the Sugar educational platform, presented his stuff and
7323 also helped me improve my OLPC installation. He also showed me that
7324 his Turtle Art application can be used in standalone mode, and we
7325 agreed that I would help getting it packaged for Debian. As a
7326 standalone application it would be great for Debian Edu. We also
7327 tried to get the video conferencing working with two OLPCs, but that
7328 proved to be too hard for us. The application seem to need more work
7329 before it is ready for me. I look forward to getting home and relax
7330 now. :)&lt;/p&gt;
7331 </description>
7332 </item>
7333
7334 <item>
7335 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7336 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7337 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7338 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7339 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7340 optimal. There is RFC 2307 documenting one way to store NIS maps in
7341 LDAP, and a modified version of this normally called RFC 2307bis, with
7342 some modifications to be compatible with Active Directory. The RFC
7343 specification handle the content of a lot of system databases, but do
7344 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7345
7346 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7347 we would like to store information about users, SMB clients/hosts,
7348 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7349 and LTSP configuration in LDAP. These objects have a lot in common,
7350 but with the current LDAP schemas it is not possible to have one
7351 object per entity. For example, one need to have at least three LDAP
7352 objects for a given computer, one with the SMB related stuff, one with
7353 DNS information and another with DHCP information. The schemas
7354 provided for DNS and DHCP are impossible to combine into one LDAP
7355 object. In addition, it is impossible to implement quick queries for
7356 netgroup membership, because of the way NIS triples are implemented.
7357 It just do not scale. I believe it is time for a few RFC
7358 specifications to cleam up this mess.&lt;/p&gt;
7359
7360 &lt;p&gt;I would like to have one LDAP object representing each computer in
7361 the network, and this object can then keep the SMB (ie host key), DHCP
7362 (mac address/name) and DNS (name/IP address) settings in one place.
7363 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7364
7365 &lt;p&gt;I would also like to have a quick way to map from a user or
7366 computer and to the net group this user or computer is a member.&lt;/p&gt;
7367
7368 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7369 in this regard, and the unix side need to catch up. Time to start a
7370 new IETF work group?&lt;/p&gt;
7371 </description>
7372 </item>
7373
7374 <item>
7375 <title>Endelig er Debian Lenny gitt ut</title>
7376 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7378 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7379 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7380 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7381 Et langt steg videre for Debian-prosjektet, og en rekke nye
7382 programpakker blir nå tilgjengelig for de av oss som bruker den
7383 stabile utgaven av Debian. Neste steg er nå å få
7384 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7385 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7386 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7387 slippes løs på skolene. Takk til alle debian-utviklerne som har
7388 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7389 bootsekvens tilgjengelig i stabil utgave, vha pakken
7390 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7391 </description>
7392 </item>
7393
7394 <item>
7395 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7396 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7397 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7398 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7399 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7400 Oslo. Most of Saturday was used for the general assemly for the
7401 member organization, but the rest of the weekend I used to tune the
7402 LTSP installation. LTSP now work out of the box on the 10-network.
7403 Acer Aspire One proved to be a very nice thin client, with both
7404 screen, mouse and keybard in a small box. Was working on getting the
7405 diskless workstation setup configured out of the box, but did not
7406 finish it before the weekend was up.&lt;/p&gt;
7407
7408 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7409 the Brazilian group, so that will have to wait for the next
7410 development gathering. Would love to have the Debian Edu installer
7411 automatically detect and configure a multiseat setup when it find one
7412 of these cards.&lt;/p&gt;
7413 </description>
7414 </item>
7415
7416 <item>
7417 <title>The sorry state of multimedia browser plugins in Debian</title>
7418 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7419 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7420 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7421 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7422 plugins available in Debian Lenny, to see which one we should use by
7423 default in Debian Edu. We need an embedded video playing plugin with
7424 control buttons to pause or stop the video, and capable of streaming
7425 all the multimedia content available on the web. The test results and
7426 notes are available on
7427 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7428 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7429 fill this need. My personal video player favorite, VLC, has a really
7430 bad plugin which fail on a lot of the test pages. A lot of the MIME
7431 types I would expect to work with any free software player (like
7432 video/ogg), just do not work. And simple formats like the
7433 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7434 totem and vlc plugins. I hope the situation will improve soon. No
7435 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7436
7437 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7438 be the only one fitting our needs. :/&lt;/p&gt;
7439 </description>
7440 </item>
7441
7442 </channel>
7443 </rss>