]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
615d1fd1ed7029188f2650e7d16f615bc0bc4283
[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>listadmin, the quick way to moderate mailman lists - nice free software</title>
11 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
13 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
14 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
15 alioth.debian.org, you know the web interface is fairly slow to
16 operate. First you visit one web page, enter the moderation password
17 and get a new page shown with a list of all the messages to moderate
18 and various options for each email address. This take a while for
19 every list you moderate, and you need to do it regularly to do a good
20 job as a list moderator. But there is a quick alternative,
21 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
22 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
23 to moderate in a fraction of a second. Here is a test run on two
24 lists I recently took over:&lt;/p&gt;
25
26 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
27 % time listadmin xiph
28 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
29 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
30
31 real 0m1.709s
32 user 0m0.232s
33 sys 0m0.012s
34 %
35 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
36
37 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
38 there are no message in the moderation queue. Every morning I
39 currently moderate 68 mailman lists, and it normally take around two
40 minutes. When I took over the two pkg-xiph lists above a few days
41 ago, there were 400 emails waiting in the moderator queue. It took me
42 less than 15 minutes to process them all using the listadmin
43 program.&lt;/p&gt;
44
45 &lt;p&gt;If you install
46 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
47 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
48 with content like this, the moderation task is a breeze:&lt;/p&gt;
49
50 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
51 username@example.org
52 spamlevel 23
53 default discard
54 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
55
56 password secret
57 adminurl https://{domain}/mailman/admindb/{list}
58 mailman-list@lists.example.com
59
60 password hidden
61 other-list@otherserver.example.org
62 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
63
64 &lt;p&gt;There are other options to set as well. Check the manual page to
65 learn the details.&lt;/p&gt;
66
67 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
68 the SSL certificate is self signed or not properly signed by a
69 generally accepted signing authority, you can set a environment
70 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
71
72 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
73 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
74 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
75
76 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
77 can provide an argument to the listadmin script like I do in the
78 initial screen dump (the xiph argument). Using an argument, only
79 lists matching the argument string will be processed. This make it
80 quick to accept messages if you notice the moderation request in your
81 email.&lt;/p&gt;
82
83 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
84 mailing lists, as I simply do not have time to spend on that if the
85 process was any slower. The listadmin program have saved me hours of
86 time I could spend elsewhere over the years. It truly is nice free
87 software.&lt;/p&gt;
88
89 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
90 activities, please send Bitcoin donations to my address
91 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
92 </description>
93 </item>
94
95 <item>
96 <title>Debian Jessie, PXE and automatic firmware installation</title>
97 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
98 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
99 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
100 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
101 problem that the WiFi card require some firmware to work properly.
102 And it has been a pain to fix this using preseeding in Debian.
103 Normally something more is needed. But thanks to
104 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
105 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
106 to do this using simple preseeding.&lt;/p&gt;
107
108 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
109 firmware for the hardware found in the machine (actually, requested by
110 the kernel modules for the hardware). (It can also install user space
111 programs supporting the hardware detected, but that is not the focus
112 of this story.)&lt;/p&gt;
113
114 &lt;p&gt;To get this working in the default installation, two preeseding
115 values are needed. First, the isenkram-cli package must be installed
116 into the target chroot (aka the hard drive) before tasksel is executed
117 in the pkgsel step of the debian-installer system. This is done by
118 preseeding the base-installer/includes debconf value to include the
119 isenkram-cli package. The package name is next passed to debootstrap
120 for installation. With the isenkram-cli package in place, tasksel
121 will automatically use the isenkram tasks to detect hardware specific
122 packages for the machine being installed and install them, because
123 isenkram-cli contain tasksel tasks.&lt;/p&gt;
124
125 &lt;p&gt;Second, one need to enable the non-free APT repository, because
126 most firmware unfortunately is non-free. This is done by preseeding
127 the apt-mirror-setup step. This is unfortunate, but for a lot of
128 hardware it is the only option in Debian.&lt;/p&gt;
129
130 &lt;p&gt;The end result is two lines needed in your preseeding file to get
131 firmware installed automatically by the installer:&lt;/p&gt;
132
133 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
134 base-installer base-installer/includes string isenkram-cli
135 apt-mirror-setup apt-setup/non-free boolean true
136 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
137
138 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
139 both firmware and user space packages when using this method. It also
140 do not work well, so use version 0.15 or later. Installing both
141 firmware and user space packages might give you a bit more than you
142 want, so I decided to split the tasksel task in two, one for firmware
143 and one for user space programs. The firmware task is enabled by
144 default, while the one for user space programs is not. This split is
145 implemented in the package currently in unstable.&lt;/p&gt;
146
147 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
148 this recipe work for you. :)&lt;/p&gt;
149
150 &lt;p&gt;So, I bet you are wondering, how can this work. First and
151 foremost, it work because tasksel is modular, and driven by whatever
152 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
153 isenkram-cli package place two files for tasksel to find. First there
154 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
155
156 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
157 Task: isenkram-packages
158 Section: hardware
159 Description: Hardware specific packages (autodetected by isenkram)
160 Based on the detected hardware various hardware specific packages are
161 proposed.
162 Test-new-install: show show
163 Relevance: 8
164 Packages: for-current-hardware
165
166 Task: isenkram-firmware
167 Section: hardware
168 Description: Hardware specific firmware packages (autodetected by isenkram)
169 Based on the detected hardware various hardware specific firmware
170 packages are proposed.
171 Test-new-install: mark show
172 Relevance: 8
173 Packages: for-current-hardware-firmware
174 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
175
176 &lt;p&gt;The key parts are Test-new-install which indicate how the task
177 should be handled and the Packages line referencing to a script in
178 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
179 list of packages to install. The for-current-hardware-firmware script
180 look like this to list relevant firmware for the machine:
181
182 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
183 #!/bin/sh
184 #
185 PATH=/usr/sbin:$PATH
186 export PATH
187 isenkram-autoinstall-firmware -l
188 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
189
190 &lt;p&gt;With those two pieces in place, the firmware is installed by
191 tasksel during the normal d-i run. :)&lt;/p&gt;
192
193 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
194 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
195 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
196 install.&lt;/p&gt;
197
198 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
199 pilots in testing this feature, as isenkram is used there now to
200 install firmware, replacing the earlier scripts.&lt;/p&gt;
201 </description>
202 </item>
203
204 <item>
205 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
206 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
207 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
208 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
209 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
210 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
211 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
212 on a screen normally showing the bread types and prizes:&lt;/p&gt;
213
214 &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;
215
216 &lt;p&gt;If it had booted as it was supposed to, I would never had known
217 about this hidden Linux installation. It is interesting what
218 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
219 </description>
220 </item>
221
222 <item>
223 <title>New lsdvd release version 0.17 is ready</title>
224 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
225 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
226 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
227 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
228 got a new set of developers a few weeks ago, after the original
229 developer decided to step down and pass the project to fresh blood.
230 This project is now maintained by Petter Reinholdtsen and Steve
231 Dibb.&lt;/p&gt;
232
233 &lt;p&gt;I just wrapped up
234 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
235 new lsdvd release&lt;/a&gt;, available in git or from
236 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
237 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
238 0.17.&lt;/p&gt;
239
240 &lt;ul&gt;
241
242 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
243 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
244 non-existant, to work around additional copy protection&lt;/li&gt;
245 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
246 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
247 &lt;li&gt;Fix include orders&lt;/li&gt;
248 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
249 &lt;li&gt;Fix the chapter count&lt;/li&gt;
250 &lt;li&gt;Make sure the array size and the array limit used when initialising
251 the palette size is the same.&lt;/li&gt;
252 &lt;li&gt;Fix array printing.&lt;/li&gt;
253 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
254 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
255 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
256 with more GCC compiler warnings.&lt;/li&gt;
257
258 &lt;/ul&gt;
259
260 &lt;p&gt;This change bring together patches for lsdvd in use in various
261 Linux and Unix distributions, as well as patches submitted to the
262 project the last nine years. Please check it out. :)&lt;/p&gt;
263 </description>
264 </item>
265
266 <item>
267 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
268 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
269 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
270 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
271 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
272 project&lt;/a&gt; provide a Linux solution for schools, including a
273 powerful desktop with education software, a central server providing
274 web pages, user database, user home directories, central login and PXE
275 boot of both clients without disk and the installation to install Debian
276 Edu on machines with disk (and a few other services perhaps to small
277 to mention here). We in the Debian Edu team are currently working on
278 the Jessie based version, trying to get everything in shape before the
279 freeze, to avoid having to maintain our own package repository in the
280 future. The
281 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
282 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
283 work left. Some fatal problems block testing, breaking the installer,
284 but it is possible to work around these to get anyway. Here is a
285 recipe on how to get the installation limping along.&lt;/p&gt;
286
287 &lt;p&gt;First, download the test ISO via
288 &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;,
289 &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;
290 or rsync (use
291 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
292 The ISO build was broken on Tuesday, so we do not get a new ISO every
293 12 hours or so, but thankfully the ISO we already got we are able to
294 install with some tweaking.&lt;/p&gt;
295
296 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
297 (use Alt-Ctrl-F2), run&lt;/p&gt;
298
299 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
300 nano /usr/bin/edu-eatmydata-install
301 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
302
303 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
304 optimization. Return to the installation, select the profile you want
305 and continue. Without this change, exim4-config will fail to install
306 due to a known bug in eatmydata.&lt;/p&gt;
307
308 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
309 this do not work, figure out what your correct value would be. All my
310 test machines need /dev/sda, so I have no advice if it do not fit
311 your need.&lt;/p&gt;
312
313 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
314 root after the initial boot from hard drive, and install the
315 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
316 or mate. If you want several desktop options, install more than one
317 metapackage. Once this is done, reboot and you should have a working
318 graphical login screen. This workaround should no longer be needed
319 once the education-tasks package version 1.801 enter testing in two
320 days.&lt;/p&gt;
321
322 &lt;p&gt;I believe the ISO build will start working on two days when the new
323 tasksel package enter testing and Steve McIntyre get a chance to
324 update the debian-cd git repository. The eatmydata, grub and desktop
325 issues are already fixed in unstable and testing, and should show up
326 on the ISO as soon as the ISO build start working again. Well the
327 eatmydata optimization is really just disabled. The proper fix
328 require an upload by the eatmydata maintainer applying the patch
329 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
330 The rest have proper fixes in unstable.&lt;/p&gt;
331
332 &lt;p&gt;I hope this get you going with the installation testing, as we are
333 quickly running out of time trying to get our Jessie based
334 installation ready before the distribution freeze in a month.&lt;/p&gt;
335 </description>
336 </item>
337
338 <item>
339 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
340 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
341 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
342 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
343 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
344 to handle my fairly large DVD collection. It is a nice command line
345 tool to get details about a DVD, like title, tracks, track length,
346 etc, in XML, Perl or human readable format. But lsdvd have not seen
347 any new development since 2006 and had a few irritating bugs affecting
348 its use with some DVDs. Upstream seemed to be dead, and in January I
349 sent a small probe asking for a version control repository for the
350 project, without any reply. But I use it regularly and would like to
351 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
352 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
353 the project admin, and after getting a reply from him explaining that
354 he was no longer interested in the project, I asked if I could take
355 over. And yesterday, I became project admin.&lt;/p&gt;
356
357 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
358 maintainer interested in joining forces to maintain the upstream
359 project, and I hope we can get a new release out fairly quickly,
360 collecting the patches spread around on the internet into on place.
361 I&#39;ve added the relevant Debian patches to the freshly created git
362 repository, and expect the Gentoo patches to make it too. If you got
363 a DVD collection and care about command line tools, check out
364 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
365 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
366 list&lt;/a&gt;. :)&lt;/p&gt;
367 </description>
368 </item>
369
370 <item>
371 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
372 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
373 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
374 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
375 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
376 a lot quicker. When we install more than 2000 packages in
377 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
378 tasksel in the installer, unpacking the binary packages take forever.
379 A part of the slow I/O issue was discussed in
380 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
381 much file system sync-ing done by dpkg, which is the package
382 responsible for unpacking the binary packages. Other parts (like code
383 executed by postinst scripts) might also sync to disk during
384 installation. All this sync-ing to disk do not really make sense to
385 me. If the machine crash half-way through, I start over, I do not try
386 to salvage the half installed system. So the failure sync-ing is
387 supposed to protect against, hardware or system crash, is not really
388 relevant while the installer is running.&lt;/p&gt;
389
390 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
391 system sync()-ing in a fairly non-intrusive way, without the need to
392 change the code in several packages. The idea is not new, but I have
393 not heard anyone propose the approach using dpkg-divert before. It
394 depend on the small and clever package
395 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
396 uses LD_PRELOAD to replace the system functions for syncing data to
397 disk with functions doing nothing, thus allowing programs to live
398 dangerous while speeding up disk I/O significantly. Instead of
399 modifying the implementation of dpkg, apt and tasksel (which are the
400 packages responsible for selecting, fetching and installing packages),
401 it occurred to me that we could just divert the programs away, replace
402 them with a simple shell wrapper calling
403 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
404 Two days ago I decided to test the idea, and wrapped up a simple
405 implementation for the Debian Edu udeb.&lt;/p&gt;
406
407 &lt;p&gt;The effect was stunning. In my first test it reduced the running
408 time of the pkgsel step (installing tasks) from 64 to less than 44
409 minutes (20 minutes shaved off the installation) on an old Dell
410 Latitude D505 machine. I am not quite sure what the optimised time
411 would have been, as I messed up the testing a bit, causing the debconf
412 priority to get low enough for two questions to pop up during
413 installation. As soon as I saw the questions I moved the installation
414 along, but do not know how long the question were holding up the
415 installation. I did some more measurements using Debian Edu Jessie,
416 and got these results. The time measured is the time stamp in
417 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
418 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
419 yourself. In Debian Edu, the tasksel dialog do not show up, and the
420 timing thus do not depend on how quickly the user handle the tasksel
421 dialog.&lt;/p&gt;
422
423 &lt;p&gt;&lt;table&gt;
424
425 &lt;tr&gt;
426 &lt;th&gt;Machine/setup&lt;/th&gt;
427 &lt;th&gt;Original tasksel&lt;/th&gt;
428 &lt;th&gt;Optimised tasksel&lt;/th&gt;
429 &lt;th&gt;Reduction&lt;/th&gt;
430 &lt;/tr&gt;
431
432 &lt;tr&gt;
433 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
434 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
435 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
436 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
437 &lt;/tr&gt;
438
439 &lt;tr&gt;
440 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
441 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
442 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
443 &lt;td&gt;23 min 40%&lt;/td&gt;
444 &lt;/tr&gt;
445
446 &lt;tr&gt;
447 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
448 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
449 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
450 &lt;td&gt;11 min 50%&lt;/td&gt;
451 &lt;/tr&gt;
452
453 &lt;tr&gt;
454 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
455 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
456 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
457 &lt;td&gt;2 min 33%&lt;/td&gt;
458 &lt;/tr&gt;
459
460 &lt;tr&gt;
461 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
462 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
463 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
464 &lt;td&gt;4 min 21%&lt;/td&gt;
465 &lt;/tr&gt;
466
467 &lt;/table&gt;&lt;/p&gt;
468
469 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
470 time is spent downloading packages. The connection to the Internet
471 was 100Mbit/s during testing, so downloading should not be a
472 significant factor in the measurement. Download typically took a few
473 seconds to a few minutes, depending on the amount of packages being
474 installed.&lt;/p&gt;
475
476 &lt;p&gt;The speedup is implemented by using two hooks in
477 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
478 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
479 finish-install.d hook to remove the divert at the end of the
480 installation. I picked the pre-pkgsel.d hook instead of the
481 post-base-installer.d hook because I test using an ISO without the
482 eatmydata package included, and the post-base-installer.d hook in
483 Debian Edu can only operate on packages included in the ISO. The
484 negative effect of this is that I am unable to activate this
485 optimization for the kernel installation step in d-i. If the code is
486 moved to the post-base-installer.d hook, the speedup would be larger
487 for the entire installation.&lt;/p&gt;
488
489 &lt;p&gt;I&#39;ve implemented this in the
490 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
491 git repository, and plan to provide the optimization as part of the
492 Debian Edu installation. If you want to test this yourself, you can
493 create two files in the installer (or in an udeb). One shell script
494 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
495
496 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
497 #!/bin/sh
498 set -e
499 . /usr/share/debconf/confmodule
500 info() {
501 logger -t my-pkgsel &quot;info: $*&quot;
502 }
503 error() {
504 logger -t my-pkgsel &quot;error: $*&quot;
505 }
506 override_install() {
507 apt-install eatmydata || true
508 if [ -x /target/usr/bin/eatmydata ] ; then
509 for bin in dpkg apt-get aptitude tasksel ; do
510 file=/usr/bin/$bin
511 # Test that the file exist and have not been diverted already.
512 if [ -f /target$file ] ; then
513 info &quot;diverting $file using eatmydata&quot;
514 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
515 &gt; /target$file.edu
516 chmod 755 /target$file.edu
517 in-target dpkg-divert --package debian-edu-config \
518 --rename --quiet --add $file
519 ln -sf ./$bin.edu /target$file
520 else
521 error &quot;unable to divert $file, as it is missing.&quot;
522 fi
523 done
524 else
525 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
526 fi
527 }
528
529 override_install
530 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
531
532 &lt;p&gt;To clean up, another shell script should go into
533 /usr/lib/finish-install.d/ with code like this:
534
535 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
536 #! /bin/sh -e
537 . /usr/share/debconf/confmodule
538 error() {
539 logger -t my-finish-install &quot;error: $@&quot;
540 }
541 remove_install_override() {
542 for bin in dpkg apt-get aptitude tasksel ; do
543 file=/usr/bin/$bin
544 if [ -x /target$file.edu ] ; then
545 rm /target$file
546 in-target dpkg-divert --package debian-edu-config \
547 --rename --quiet --remove $file
548 rm /target$file.edu
549 else
550 error &quot;Missing divert for $file.&quot;
551 fi
552 done
553 sync # Flush file buffers before continuing
554 }
555
556 remove_install_override
557 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
558
559 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
560 edu-eatmydata-install and call it from the pre-pkgsel.d and
561 finish-install.d scripts.&lt;/p&gt;
562
563 &lt;p&gt;By now you might ask if this change should get into the normal
564 Debian installer too? I suspect it should, but am not sure the
565 current debian-installer coordinators find it useful enough. It also
566 depend on the side effects of the change. I&#39;m not aware of any, but I
567 guess we will see if the change is safe after some more testing.
568 Perhaps there is some package in Debian depending on sync() and
569 fsync() having effect? Perhaps it should go into its own udeb, to
570 allow those of us wanting to enable it to do so without affecting
571 everyone.&lt;/p&gt;
572
573 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
574 will break installation of all programs using gnutls because of
575 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
576 eatmydata package in Debian will solve it.&lt;/p&gt;
577
578 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
579 the optimization work again. And I have discovered that the
580 dpkg-divert trick is not really needed and implemented a slightly
581 simpler approach as part of the debian-edu-install package. See
582 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
583 </description>
584 </item>
585
586 <item>
587 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
588 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
589 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
590 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
591 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
592 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
593 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
594 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
595 learn that there is a large set of publicly available key servers to
596 use when looking for peoples public key. So far I have used
597 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
598 were misbehaving, but those days are ended. The servers I have used
599 up until yesterday have been slow and some times unavailable. I hope
600 those problems are gone now.&lt;/p&gt;
601
602 &lt;p&gt;Behind the round robin DNS entry of the
603 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
604 there is a pool of more than 100 keyservers which are checked every
605 day to ensure they are well connected and up to date. It must be
606 better than what I have used so far. :)&lt;/p&gt;
607
608 &lt;p&gt;Yesterdays speaker told me that the service is the default
609 keyserver provided by the default configuration in GnuPG, but this do
610 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
611
612 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
613 line:&lt;/p&gt;
614
615 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
616 keyserver pool.sks-keyservers.net
617 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
618
619 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
620 entries in DNS. Just for fun, I did just that at work, so now every
621 user of GnuPG at the University of Oslo should find a OpenGPG
622 keyserver automatically should their need it:&lt;/p&gt;
623
624 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
625 % host -t srv _pgpkey-http._tcp.uio.no
626 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
627 %
628 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
629
630 &lt;p&gt;Now if only
631 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
632 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
633 very happy. It can look up a given key or search for a user ID, but I
634 normally do not want that, but to find a trust path from my key to
635 another key. Given a user ID or key ID, I would like to find (and
636 download) the keys representing a signature path from my key to the
637 key in question, to be able to get a trust path between the two keys.
638 This is as far as I can tell not possible today. Perhaps something
639 for a future version of the protocol?&lt;/p&gt;
640 </description>
641 </item>
642
643 <item>
644 <title>From English wiki to translated PDF and epub via Docbook</title>
645 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
646 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
647 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
648 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
649 project&lt;/a&gt; provide an instruction manual for teachers, system
650 administrators and other users that contain useful tips for setting up
651 and maintaining a Debian Edu installation. This text is about how the
652 text processing of this manual is handled in the project.&lt;/p&gt;
653
654 &lt;p&gt;One goal of the project is to provide information in the native
655 language of its users, and for this we need to handle translations.
656 But we also want to make sure each language contain the same
657 information, so for this we need a good way to keep the translations
658 in sync. And we want it to be easy for our users to improve the
659 documentation, avoiding the need to learn special formats or tools to
660 contribute, and the obvious way to do this is to make it possible to
661 edit the documentation using a web browser. We also want it to be
662 easy for translators to keep the translation up to date, and give them
663 help in figuring out what need to be translated. Here is the list of
664 tools and the process we have found trying to reach all these
665 goals.&lt;/p&gt;
666
667 &lt;p&gt;We maintain the authoritative source of our manual in the
668 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
669 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
670 front page with references to the different chapters, several pages
671 for each chapter, and finally one &quot;collection page&quot; gluing all the
672 chapters together into one large web page (aka
673 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
674 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
675 processing and translations. Thanks to the fact that the
676 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
677 wiki.debian.org support exporting pages in
678 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
679 the list of pages to export using the raw version of the AllInOne
680 page, loop over each of them to generate a Docbook XML version of the
681 manual. This process also download images and transform image
682 references to use the locally downloaded images. The generated
683 Docbook XML files are slightly broken, so some post-processing is done
684 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
685 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
686 a handfull of images. The XML file can now be used to generate PDF, HTML
687 and epub versions of the English manual. This is the basic step of
688 our process, making PDF (using dblatex), HTML (using xsltproc) and
689 epub (using dbtoepub) version from Docbook XML, and the resulting files
690 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
691
692 &lt;p&gt;But English documentation is not enough for us. We want translated
693 documentation too, and we want to make it easy for translators to
694 track the English original. For this we use the
695 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
696 which allow us to transform the English Docbook XML file into a
697 translation file (a .pot file), usable with the normal gettext based
698 translation tools used by those translating free software. The pot
699 file is used to create and maintain translation files (several .po
700 files), which the translations update with the native language
701 translations of all titles, paragraphs and blocks of text in the
702 original. The next step is combining the original English Docbook XML
703 and the translation file (say debian-edu-wheezy-manual.nb.po), to
704 create a translated Docbook XML file (in this case
705 debian-edu-wheezy-manual.nb.xml). This translated (or partly
706 translated, if the translation is not complete) Docbook XML file can
707 then be used like the original to create a PDF, HTML and epub version
708 of the documentation.&lt;/p&gt;
709
710 &lt;p&gt;The translators use different tools to edit the .po files. We
711 recommend using
712 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
713 while some use emacs and vi, others can use web based editors like
714 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
715 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
716 is where the .po file end up, in our git repository. Updated
717 translations can either be committed directly to git, or submitted as
718 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
719 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
720
721 &lt;p&gt;One challenge is images, which both might need to be translated (if
722 they show translated user applications), and are needed in different
723 formats when creating PDF and HTML versions (epub is a HTML version in
724 this regard). For this we transform the original PNG images to the
725 needed density and format during build, and have a way to provide
726 translated images by storing translated versions in
727 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
728 package maintainers know more.&lt;/p&gt;
729
730 &lt;p&gt;If you wonder what the result look like, we provide
731 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
732 of the documentation packages on the web&lt;/a&gt;. See for example the
733 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
734 PDF version&lt;/a&gt; or the
735 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
736 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
737 but perhaps it will be done in the future.&lt;/p&gt;
738
739 &lt;p&gt;To learn more, check out
740 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
741 debian-edu-doc package&lt;/a&gt;,
742 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
743 manual on the wiki&lt;/a&gt; and
744 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
745 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
746 </description>
747 </item>
748
749 <item>
750 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
751 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
752 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
753 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
754 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
755 related packages relevant for the computer installed automatically.
756 So I implemented one, using
757 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
758 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
759 run tasksel as user root. You should be presented with a new option,
760 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
761 select it, tasksel will install the packages isenkram claim is fit for
762 the current hardware, hot pluggable or not.&lt;p&gt;
763
764 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
765 description, and the other is the script used to extract the list of
766 packages to install. The first part is in
767 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
768 this:&lt;/p&gt;
769
770 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
771 Task: isenkram
772 Section: hardware
773 Description: Hardware specific packages (autodetected by isenkram)
774 Based on the detected hardware various hardware specific packages are
775 proposed.
776 Test-new-install: mark show
777 Relevance: 8
778 Packages: for-current-hardware
779 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
780
781 &lt;p&gt;The second part is in
782 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
783 this:&lt;/p&gt;
784
785 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
786 #!/bin/sh
787 #
788 (
789 isenkram-lookup
790 isenkram-autoinstall-firmware -l
791 ) | sort -u
792 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
793
794 &lt;p&gt;All in all, a very short and simple implementation making it
795 trivial to install the hardware dependent package we all may want to
796 have installed on our machines. I&#39;ve not been able to find a way to
797 get tasksel to tell you exactly which packages it plan to install
798 before doing the installation. So if you are curious or careful,
799 check the output from the isenkram-* command line tools first.&lt;/p&gt;
800
801 &lt;p&gt;The information about which packages are handling which hardware is
802 fetched either from the isenkram package itself in
803 /usr/share/isenkram/, from git.debian.org or from the APT package
804 database (using the Modaliases header). The APT package database
805 parsing have caused a nasty resource leak in the isenkram daemon (bugs
806 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
807 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
808 the python-apt code (bug
809 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
810 workaround I was able to get rid of the file descriptor leak and
811 reduce the memory leak from ~30 MiB per hardware detection down to
812 around 2 MiB per hardware detection. It should make the desktop
813 daemon a lot more useful. The fix is in version 0.7 uploaded to
814 unstable today.&lt;/p&gt;
815
816 &lt;p&gt;I believe the current way of mapping hardware to packages in
817 Isenkram is is a good draft, but in the future I expect isenkram to
818 use the AppStream data source for this. A proposal for getting proper
819 AppStream support into Debian is floating around as
820 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
821 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
822 project&lt;/a&gt; will take place this summer to improve the situation. I
823 look forward to seeing the result, and welcome patches for isenkram to
824 start using the information when it is ready.&lt;/p&gt;
825
826 &lt;p&gt;If you want your package to map to some specific hardware, either
827 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
828 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
829 package&lt;/a&gt; or submit a bug report with the details to the isenkram
830 package. See also
831 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
832 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
833 the information will be migrated to AppStream eventually, but for the
834 moment I got no better place to store it.&lt;/p&gt;
835 </description>
836 </item>
837
838 <item>
839 <title>FreedomBox milestone - all packages now in Debian Sid</title>
840 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
841 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
842 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
843 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
844 project&lt;/a&gt; is working on providing the software and hardware to make
845 it easy for non-technical people to host their data and communication
846 at home, and being able to communicate with their friends and family
847 encrypted and away from prying eyes. It is still going strong, and
848 today a major mile stone was reached.&lt;/p&gt;
849
850 &lt;p&gt;Today, the last of the packages currently used by the project to
851 created the system images were accepted into Debian Unstable. It was
852 the freedombox-setup package, which is used to configure the images
853 during build and on the first boot. Now all one need to get going is
854 the build code from the freedom-maker git repository and packages from
855 Debian. And once the freedombox-setup package enter testing, we can
856 build everything directly from Debian. :)&lt;/p&gt;
857
858 &lt;p&gt;Some key packages used by Freedombox are
859 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
860 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
861 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
862 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
863 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
864 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
865 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
866 are plans to integrate more packages into the setup. User
867 documentation is maintained on the Debian wiki. Please
868 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
869 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
870
871 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
872 setup, run this on a Debian machine using a user with sudo rights to
873 become root:&lt;/p&gt;
874
875 &lt;p&gt;&lt;pre&gt;
876 sudo apt-get install git vmdebootstrap mercurial python-docutils \
877 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
878 u-boot-tools
879 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
880 freedom-maker
881 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
882 &lt;/pre&gt;&lt;/p&gt;
883
884 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
885 devices. See the README in the freedom-maker git repo for more
886 details on the build. If you do not want all three images, trim the
887 make line. Note that the virtualbox-image target is not really
888 virtualbox specific. It create a x86 image usable in kvm, qemu,
889 vmware and any other x86 virtual machine environment. You might need
890 the version of vmdebootstrap in Jessie to get the build working, as it
891 include fixes for a race condition with kpartx.&lt;/p&gt;
892
893 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
894 method, boot a Debian Wheezy ISO and use this boot argument to load
895 the preseed values:&lt;/p&gt;
896
897 &lt;p&gt;&lt;pre&gt;
898 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;
899 &lt;/pre&gt;&lt;/p&gt;
900
901 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
902 it still work.&lt;/p&gt;
903
904 &lt;p&gt;If you wonder how to help, one task you could look at is using
905 systemd as the boot system. It will become the default for Linux in
906 Jessie, so we need to make sure it is usable on the Freedombox. I did
907 a simple test a few weeks ago, and noticed dnsmasq failed to start
908 during boot when using systemd. I suspect there are other problems
909 too. :) To detect problems, there is a test suite included, which can
910 be run from the plinth web interface.&lt;/p&gt;
911
912 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
913 us get the new release published. :) Please join us on
914 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
915 irc.debian.org)&lt;/a&gt; and
916 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
917 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
918 </description>
919 </item>
920
921 <item>
922 <title>S3QL, a locally mounted cloud file system - nice free software</title>
923 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
924 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
925 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
926 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
927 solution for use at home. My requirements are simple, it must be
928 cheap and locally encrypted (in other words, I keep the encryption
929 keys, the storage provider do not have access to my private files).
930 One idea me and my friends had many years ago, before the cloud
931 storage providers showed up, was to use Google mail as storage,
932 writing a Linux block device storing blocks as emails in the mail
933 service provided by Google, and thus get heaps of free space. On top
934 of this one can add encryption, RAID and volume management to have
935 lots of (fairly slow, I admit that) cheap and encrypted storage. But
936 I never found time to implement such system. But the last few weeks I
937 have looked at a system called
938 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
939 mounted network backed file system with the features I need.&lt;/p&gt;
940
941 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
942 handling several different storage providers, any with Amazon S3,
943 Google Drive or OpenStack API. There are heaps of such storage
944 providers. S3QL can also use a local directory as storage, which
945 combined with sshfs allow for file storage on any ssh server. S3QL
946 include support for encryption, compression, de-duplication, snapshots
947 and immutable file systems, allowing me to mount the remote storage as
948 a local mount point, look at and use the files as if they were local,
949 while the content is stored in the cloud as well. This allow me to
950 have a backup that should survive fire. The file system can not be
951 shared between several machines at the same time, as only one can
952 mount it at the time, but any machine with the encryption key and
953 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
954
955 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
956 package is included already. So to get started, run &lt;tt&gt;apt-get
957 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
958 Greenqloud, after reading their nice recipe on
959 &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
960 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
961 in Iceland more than those in USA when it come to keeping my personal
962 data safe and private, and thus would rather spend money on a company
963 in Iceland. Another nice recipe is available from the article
964 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
965 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
966 Admin magazine. When the provider is picked, figure out how to get
967 the API key needed to connect to the storage API. With Greencloud,
968 the key did not show up until I had added payment details to my
969 account.&lt;/p&gt;
970
971 &lt;p&gt;Armed with the API access details, it is time to create the file
972 system. First, create a new bucket in the cloud. This bucket is the
973 file system storage area. I picked a bucket name reflecting the
974 machine that was going to store data there, but any name will do.
975 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
976 the API login and password, and a locally created password. Store it
977 all in ~root/.s3ql/authinfo2 like this:
978
979 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
980 [s3c]
981 storage-url: s3c://s.greenqloud.com:443/bucket-name
982 backend-login: API-login
983 backend-password: API-password
984 fs-passphrase: local-password
985 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
986
987 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
988 but any sensible way to create a fairly random password should do it.
989 Armed with these details, it is now time to run mkfs, entering the API
990 details and password to create it:&lt;/p&gt;
991
992 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
993 # mkdir -m 700 /var/lib/s3ql-cache
994 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
995 --ssl s3c://s.greenqloud.com:443/bucket-name
996 Enter backend login:
997 Enter backend password:
998 Before using S3QL, make sure to read the user&#39;s guide, especially
999 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1000 Enter encryption password:
1001 Confirm encryption password:
1002 Generating random encryption key...
1003 Creating metadata tables...
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.00 MB of compressed metadata.
1015 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1016
1017 &lt;p&gt;The next step is mounting the file system to make the storage available.
1018
1019 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1020 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1021 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1022 Using 4 upload threads.
1023 Downloading and decompressing metadata...
1024 Reading metadata...
1025 ..objects..
1026 ..blocks..
1027 ..inodes..
1028 ..inode_blocks..
1029 ..symlink_targets..
1030 ..names..
1031 ..contents..
1032 ..ext_attributes..
1033 Mounting filesystem...
1034 # df -h /s3ql
1035 Filesystem Size Used Avail Use% Mounted on
1036 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1037 #
1038 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1039
1040 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1041 backups in it, and as the metadata used by rsync is downloaded at
1042 mount time, no network traffic (and storage cost) is triggered by
1043 running rsync. To unmount, one should not use the normal umount
1044 command, as this will not flush the cache to the cloud storage, but
1045 instead running the umount.s3ql command like this:
1046
1047 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1048 # umount.s3ql /s3ql
1049 #
1050 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1051
1052 &lt;p&gt;There is a fsck command available to check the file system and
1053 correct any problems detected. This can be used if the local server
1054 crashes while the file system is mounted, to reset the &quot;already
1055 mounted&quot; flag. This is what it look like when processing a working
1056 file system:&lt;/p&gt;
1057
1058 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1059 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1060 Using cached metadata.
1061 File system seems clean, checking anyway.
1062 Checking DB integrity...
1063 Creating temporary extra indices...
1064 Checking lost+found...
1065 Checking cached objects...
1066 Checking names (refcounts)...
1067 Checking contents (names)...
1068 Checking contents (inodes)...
1069 Checking contents (parent inodes)...
1070 Checking objects (reference counts)...
1071 Checking objects (backend)...
1072 ..processed 5000 objects so far..
1073 ..processed 10000 objects so far..
1074 ..processed 15000 objects so far..
1075 Checking objects (sizes)...
1076 Checking blocks (referenced objects)...
1077 Checking blocks (refcounts)...
1078 Checking inode-block mapping (blocks)...
1079 Checking inode-block mapping (inodes)...
1080 Checking inodes (refcounts)...
1081 Checking inodes (sizes)...
1082 Checking extended attributes (names)...
1083 Checking extended attributes (inodes)...
1084 Checking symlinks (inodes)...
1085 Checking directory reachability...
1086 Checking unix conventions...
1087 Checking referential integrity...
1088 Dropping temporary indices...
1089 Backing up old metadata...
1090 Dumping metadata...
1091 ..objects..
1092 ..blocks..
1093 ..inodes..
1094 ..inode_blocks..
1095 ..symlink_targets..
1096 ..names..
1097 ..contents..
1098 ..ext_attributes..
1099 Compressing and uploading metadata...
1100 Wrote 0.89 MB of compressed metadata.
1101 #
1102 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1103
1104 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1105 quick, about the same speed as local file access. Uploading large
1106 amount of data is to me limited by the bandwidth out of and into my
1107 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1108 which is very close to my upload speed, and downloading the same
1109 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1110 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1111 network, not the file system code. I do not know what a good cache
1112 size would be, but suspect that the cache should e larger than your
1113 working set.&lt;/p&gt;
1114
1115 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1116 time. If another machine try, it is told that the file system is
1117 busy:&lt;/p&gt;
1118
1119 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1120 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1121 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1122 Using 8 upload threads.
1123 Backend reports that fs is still mounted elsewhere, aborting.
1124 #
1125 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1126
1127 &lt;p&gt;The file content is uploaded when the cache is full, while the
1128 metadata is uploaded once every 24 hour by default. To ensure the
1129 file system content is flushed to the cloud, one can either umount the
1130 file system, or ask S3QL to flush the cache and metadata using
1131 s3qlctrl:
1132
1133 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1134 # s3qlctrl upload-meta /s3ql
1135 # s3qlctrl flushcache /s3ql
1136 #
1137 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1138
1139 &lt;p&gt;If you are curious about how much space your data uses in the
1140 cloud, and how much compression and deduplication cut down on the
1141 storage usage, you can use s3qlstat on the mounted file system to get
1142 a report:&lt;/p&gt;
1143
1144 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1145 # s3qlstat /s3ql
1146 Directory entries: 9141
1147 Inodes: 9143
1148 Data blocks: 8851
1149 Total data size: 22049.38 MB
1150 After de-duplication: 21955.46 MB (99.57% of total)
1151 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1152 Database size: 2.39 MB (uncompressed)
1153 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1154 #
1155 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1156
1157 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1158 storage. I did not try to locate them all, but am aware of at least
1159 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1160 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1161 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1162 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1163 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1164 accept payment in Bitcoin. Pick one that suit your need. Some of
1165 them provide several GiB of free storage, but the prize models are
1166 quite different and you will have to figure out what suits you
1167 best.&lt;/p&gt;
1168
1169 &lt;p&gt;While researching this blog post, I had a look at research papers
1170 and posters discussing the S3QL file system. There are several, which
1171 told me that the file system is getting a critical check by the
1172 science community and increased my confidence in using it. One nice
1173 poster is titled
1174 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1175 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1176 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1177 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1178 and Pamela Smith. Please have a look.&lt;/p&gt;
1179
1180 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1181 check out the mounted S3QL file system to see if it would be usable as
1182 a home directory (in other word, that it provided POSIX semantics when
1183 it come to locking and umask handling etc). Running
1184 &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
1185 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1186 no error was found. So the file system can be used for home
1187 directories, if one chooses to do so.&lt;/p&gt;
1188
1189 &lt;p&gt;If you do not want a locally file system, and want something that
1190 work without the Linux fuse file system, I would like to mention the
1191 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1192 provide locally encrypted backup using a command line client. It have
1193 a nicer access control system, where one can split out read and write
1194 access, allowing some systems to write to the backup and others to
1195 only read from it.&lt;/p&gt;
1196
1197 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1198 activities, please send Bitcoin donations to my address
1199 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1200 </description>
1201 </item>
1202
1203 <item>
1204 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1205 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1206 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1207 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1208 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1209 project&lt;/a&gt; is working on providing the software and hardware for
1210 making it easy for non-technical people to host their data and
1211 communication at home, and being able to communicate with their
1212 friends and family encrypted and away from prying eyes. It has been
1213 going on for a while, and is slowly progressing towards a new test
1214 release (0.2).&lt;/p&gt;
1215
1216 &lt;p&gt;And what day could be better than the Pi day to announce that the
1217 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1218 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1219 system), and can also be installed using a Debian installer preseed
1220 file. The Debian based Freedombox is now based on Debian Jessie,
1221 where most of the needed packages used are already present. Only one,
1222 the freedombox-setup package, is missing. To try to build your own
1223 boot image to test the current status, fetch the freedom-maker scripts
1224 and build using
1225 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1226 with a user with sudo access to become root:
1227
1228 &lt;pre&gt;
1229 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1230 freedom-maker
1231 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1232 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1233 u-boot-tools
1234 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1235 &lt;/pre&gt;
1236
1237 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1238 devices. See the README for more details on the build. If you do not
1239 want all three images, trim the make line. But note that thanks to &lt;a
1240 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1241 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1242 kpartx call.&lt;/p&gt;
1243
1244 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1245 method, boot a Debian Wheezy ISO and use this boot argument to load
1246 the preseed values:&lt;/p&gt;
1247
1248 &lt;pre&gt;
1249 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;
1250 &lt;/pre&gt;
1251
1252 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1253 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1254 currently hang while setting up APT sources. Killing the
1255 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1256 installation will get the installation going. This affect all
1257 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1258
1259 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1260 us get the new release published. :) Please join us on
1261 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1262 irc.debian.org)&lt;/a&gt; and
1263 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1264 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1265 </description>
1266 </item>
1267
1268 <item>
1269 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1270 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1271 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1272 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1273 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1274 innetgr tools, because I needed them in
1275 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1276 ng-utils, and it has served me well. I placed the project under the
1277 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1278 repository. But many years ago, the CVS repository was dropped (lost,
1279 not migrated to new hardware, not sure), and the project have lacked a
1280 proper home since then.&lt;/p&gt;
1281
1282 &lt;p&gt;Last summer, I had a look at the package and made a new release
1283 fixing a irritating crash bug, but was unable to store the changes in
1284 a proper source control system. I applied for a project on
1285 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1286 to follow up on it. Until today. :)&lt;/p&gt;
1287
1288 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1289 now have a new home, and a git repository with the highlight of the
1290 history of the project. I published all release tarballs and imported
1291 them into the git repository. As the project is really stable and not
1292 expected to gain new features any time soon, I decided to make a new
1293 release and call it 1.0. Visit the new project home on
1294 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1295 if you want to check it out. The new version is also uploaded into
1296 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1297 </description>
1298 </item>
1299
1300 <item>
1301 <title>Testing sysvinit from experimental in Debian Hurd</title>
1302 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1304 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1305 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1306 their changes into sysvinit, to allow them to use the normal sysvinit
1307 boot system instead of their old one. This follow up on the
1308 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1309 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1310 get Debian on Hurd working more like Debian on Linux. To get started,
1311 I downloaded a prebuilt hard disk image from
1312 &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;,
1313 and started it using virt-manager.&lt;/p&gt;
1314
1315 &lt;p&gt;The first think I had to do after logging in (root without any
1316 password) was to get the network operational. I followed
1317 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1318 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1319 commands as root to get the machine to accept a IP address from the
1320 kvm internal DHCP server:&lt;/p&gt;
1321
1322 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1323 settrans -fgap /dev/netdde /hurd/netdde
1324 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1325 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1326 dhclient /dev/eth0
1327 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1328
1329 &lt;p&gt;After this, the machine had internet connectivity, and I could
1330 upgrade it and install the sysvinit packages from experimental and
1331 enable it as the default boot system in Hurd.&lt;/p&gt;
1332
1333 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1334 running on the machine it for ssh login to work a password need to be
1335 set. Also, note that a bug somewhere in openssh on Hurd block
1336 compression from working. Remember to turn that off on the client
1337 side.&lt;/p&gt;
1338
1339 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1340 stuff:&lt;/p&gt;
1341
1342 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1343 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1344 deb http://http.debian.net/debian/ experimental main
1345 EOF
1346 apt-get update
1347 apt-get dist-upgrade
1348 apt-get install -t experimental initscripts sysv-rc sysvinit \
1349 sysvinit-core sysvinit-utils
1350 update-alternatives --config runsystem
1351 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1352
1353 &lt;p&gt;To reboot after switching boot system, you have to use
1354 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1355 yet a sysvinit process able to receive the signals from the normal
1356 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1357 upgrading every package and rebooting, the network come up with DHCP
1358 after boot as it should, and the settrans/pkill hack mentioned at the
1359 start is no longer needed. But for some strange reason, there are no
1360 longer any login prompt in the virtual console, so I logged in using
1361 ssh instead.
1362
1363 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1364 fail some times. No idea what the cause is, but hope the Hurd porters
1365 figure it out. At least Justus said on IRC (#debian-hurd on
1366 irc.debian.org) that they are aware of the problem. A way to reduce
1367 the impact is to upgrade to the Hurd packages built by Justus by
1368 adding this repository to the machine:&lt;/p&gt;
1369
1370 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1371 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1372 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1373 EOF
1374 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1375
1376 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1377 http://ftp.debian-ports.org/debian, because some of the packages in
1378 unstable do not yet include the required patches that are lingering in
1379 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1380
1381 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1382 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1383 i emacs - GNU Emacs editor (metapackage)
1384 i gdb - GNU Debugger
1385 i hurd-recommended - Miscellaneous translators
1386 i isc-dhcp-client - ISC DHCP client
1387 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1388 i libc-bin - Embedded GNU C Library: Binaries
1389 i libc-dev-bin - Embedded GNU C Library: Development binaries
1390 i libc0.3 - Embedded GNU C Library: Shared libraries
1391 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1392 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1393 i multiarch-support - Transitional package to ensure multiarch compatibilit
1394 i A x11-common - X Window System (X.Org) infrastructure
1395 i xorg - X.Org X Window System
1396 i A xserver-xorg - X.Org X server
1397 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1398 #
1399 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1400
1401 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1402 X.org did not work out of the box and I never took the time to follow
1403 the porters instructions to fix it. This time I was interested in the
1404 command line stuff.&lt;p&gt;
1405 </description>
1406 </item>
1407
1408 <item>
1409 <title>New chrpath release 0.16</title>
1410 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1411 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1412 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1413 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1414 find problems in C, C++ and Java code using static source code
1415 analysis. It can detect a lot of different problems, and is very
1416 useful to find memory and locking bugs in the error handling part of
1417 the source. The company behind it provide
1418 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1419 a community service&lt;/a&gt;, and many hundred free software projects are
1420 already checked. A few days ago I decided to have a closer look at
1421 the Coverity system, and discovered that the
1422 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1423 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1424 projects I am involved with was already registered. But these are
1425 fairly big, and I would also like to have a small and easy project to
1426 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1427 checking of the chrpath project&lt;/a&gt;. It was
1428 added to the checker and discovered seven potential defects. Six of
1429 these were real, mostly resource &quot;leak&quot; when the program detected an
1430 error. Nothing serious, as the resources would be released a fraction
1431 of a second later when the program exited because of the error, but it
1432 is nice to do it right in case the source of the program some time in
1433 the future end up in a library. Having fixed all defects and added
1434 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1435 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1436 publish a new release. These are the release notes:&lt;/p&gt;
1437
1438 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1439
1440 &lt;ul&gt;
1441
1442 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1443 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1444 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1445
1446 &lt;/ul&gt;
1447
1448 &lt;p&gt;You can
1449 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1450 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1451 project if something is wrong with the new release. The test suite
1452 did not discover any old errors, so if you find a new one, please also
1453 include a test suite check.&lt;/p&gt;
1454 </description>
1455 </item>
1456
1457 <item>
1458 <title>New chrpath release 0.15</title>
1459 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1460 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1461 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1462 <description>&lt;p&gt;After many years break from the package and a vain hope that
1463 development would be continued by someone else, I finally pulled my
1464 acts together this morning and wrapped up a new release of chrpath,
1465 the command line tool to modify the rpath and runpath of already
1466 compiled ELF programs. The update was triggered by the persistence of
1467 Isha Vishnoi at IBM, which needed a new config.guess file to get
1468 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1469 is working on. I checked the
1470 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1471 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1472 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1473 packages for interesting patches (failed to find the source from
1474 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1475 These are the release notes:&lt;/p&gt;
1476
1477 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1478
1479 &lt;ul&gt;
1480
1481 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1482 with newer architectures. Thanks to isha vishnoi for the heads
1483 up.&lt;/li&gt;
1484
1485 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1486
1487 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1488 Matthias Klose.&lt;/li&gt;
1489
1490 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1491 Petr Machata found in Fedora.&lt;/li&gt;
1492
1493 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1494 .dynamic is a NULL terminated string. Based on patch found in
1495 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1496
1497 &lt;/ul&gt;
1498
1499 &lt;p&gt;You can
1500 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1501 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1502 project if something is wrong with the new release. The test suite
1503 did not discover any old errors, so if you find a new one, please also
1504 include a testsuite check.&lt;/p&gt;
1505 </description>
1506 </item>
1507
1508 <item>
1509 <title>Debian init.d boot script example for rsyslog</title>
1510 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1512 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1513 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1514 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1515 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1516 init.d scripts at all. Here is an example init.d script, ie a rewrite
1517 of /etc/init.d/rsyslog:&lt;/p&gt;
1518
1519 &lt;p&gt;&lt;pre&gt;
1520 #!/lib/init/init-d-script
1521 ### BEGIN INIT INFO
1522 # Provides: rsyslog
1523 # Required-Start: $remote_fs $time
1524 # Required-Stop: umountnfs $time
1525 # X-Stop-After: sendsigs
1526 # Default-Start: 2 3 4 5
1527 # Default-Stop: 0 1 6
1528 # Short-Description: enhanced syslogd
1529 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1530 # It is quite compatible to stock sysklogd and can be
1531 # used as a drop-in replacement.
1532 ### END INIT INFO
1533 DESC=&quot;enhanced syslogd&quot;
1534 DAEMON=/usr/sbin/rsyslogd
1535 &lt;/pre&gt;&lt;/p&gt;
1536
1537 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1538 script was 137 lines, and the above is just 15 lines, most of it meta
1539 info/comments.&lt;/p&gt;
1540
1541 &lt;p&gt;How to do this, you ask? Well, one create a new script
1542 /lib/init/init-d-script looking something like this:
1543
1544 &lt;p&gt;&lt;pre&gt;
1545 #!/bin/sh
1546
1547 # Define LSB log_* functions.
1548 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1549 # and status_of_proc is working.
1550 . /lib/lsb/init-functions
1551
1552 #
1553 # Function that starts the daemon/service
1554
1555 #
1556 do_start()
1557 {
1558 # Return
1559 # 0 if daemon has been started
1560 # 1 if daemon was already running
1561 # 2 if daemon could not be started
1562 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1563 || return 1
1564 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1565 $DAEMON_ARGS \
1566 || return 2
1567 # Add code here, if necessary, that waits for the process to be ready
1568 # to handle requests from services started subsequently which depend
1569 # on this one. As a last resort, sleep for some time.
1570 }
1571
1572 #
1573 # Function that stops the daemon/service
1574 #
1575 do_stop()
1576 {
1577 # Return
1578 # 0 if daemon has been stopped
1579 # 1 if daemon was already stopped
1580 # 2 if daemon could not be stopped
1581 # other if a failure occurred
1582 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1583 RETVAL=&quot;$?&quot;
1584 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1585 # Wait for children to finish too if this is a daemon that forks
1586 # and if the daemon is only ever run from this initscript.
1587 # If the above conditions are not satisfied then add some other code
1588 # that waits for the process to drop all resources that could be
1589 # needed by services started subsequently. A last resort is to
1590 # sleep for some time.
1591 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1592 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1593 # Many daemons don&#39;t delete their pidfiles when they exit.
1594 rm -f $PIDFILE
1595 return &quot;$RETVAL&quot;
1596 }
1597
1598 #
1599 # Function that sends a SIGHUP to the daemon/service
1600 #
1601 do_reload() {
1602 #
1603 # If the daemon can reload its configuration without
1604 # restarting (for example, when it is sent a SIGHUP),
1605 # then implement that here.
1606 #
1607 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1608 return 0
1609 }
1610
1611 SCRIPTNAME=$1
1612 scriptbasename=&quot;$(basename $1)&quot;
1613 echo &quot;SN: $scriptbasename&quot;
1614 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1615 script=&quot;$1&quot;
1616 shift
1617 . $script
1618 else
1619 exit 0
1620 fi
1621
1622 NAME=$(basename $DAEMON)
1623 PIDFILE=/var/run/$NAME.pid
1624
1625 # Exit if the package is not installed
1626 #[ -x &quot;$DAEMON&quot; ] || exit 0
1627
1628 # Read configuration variable file if it is present
1629 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
1630
1631 # Load the VERBOSE setting and other rcS variables
1632 . /lib/init/vars.sh
1633
1634 case &quot;$1&quot; in
1635 start)
1636 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
1637 do_start
1638 case &quot;$?&quot; in
1639 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1640 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1641 esac
1642 ;;
1643 stop)
1644 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
1645 do_stop
1646 case &quot;$?&quot; in
1647 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1648 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1649 esac
1650 ;;
1651 status)
1652 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
1653 ;;
1654 #reload|force-reload)
1655 #
1656 # If do_reload() is not implemented then leave this commented out
1657 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
1658 #
1659 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
1660 #do_reload
1661 #log_end_msg $?
1662 #;;
1663 restart|force-reload)
1664 #
1665 # If the &quot;reload&quot; option is implemented then remove the
1666 # &#39;force-reload&#39; alias
1667 #
1668 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
1669 do_stop
1670 case &quot;$?&quot; in
1671 0|1)
1672 do_start
1673 case &quot;$?&quot; in
1674 0) log_end_msg 0 ;;
1675 1) log_end_msg 1 ;; # Old process is still running
1676 *) log_end_msg 1 ;; # Failed to start
1677 esac
1678 ;;
1679 *)
1680 # Failed to stop
1681 log_end_msg 1
1682 ;;
1683 esac
1684 ;;
1685 *)
1686 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
1687 exit 3
1688 ;;
1689 esac
1690
1691 :
1692 &lt;/pre&gt;&lt;/p&gt;
1693
1694 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
1695 lot. I did not really polish the approach, so it might not always
1696 work out of the box, but you get the idea. I did not try very hard to
1697 optimize it nor make it more robust either.&lt;/p&gt;
1698
1699 &lt;p&gt;A better argument for switching init system in Debian than reducing
1700 the size of init scripts (which is a good thing to do anyway), is to
1701 get boot system that is able to handle the kernel events sensibly and
1702 robustly, and do not depend on the boot to run sequentially. The boot
1703 and the kernel have not behaved sequentially in years.&lt;/p&gt;
1704 </description>
1705 </item>
1706
1707 <item>
1708 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
1709 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
1710 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
1711 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
1712 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
1713 remote display access is the preferred solution with oVirt and RedHat
1714 Enterprise Virtualization, and I was sad to discover the other day
1715 that the browser plugin needed to use these systems seamlessly was
1716 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
1717 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
1718 2013-04-01, so I decided to wrap up a package based on the great work
1719 from Cajus Pollmeier and put it in a collab-maint maintained git
1720 repository to get a package I could use. I would very much like
1721 others to help me maintain the package (or just take over, I do not
1722 mind), but as no-one had volunteered so far, I just uploaded it to
1723 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
1724
1725 &lt;p&gt;The source is now available from
1726 &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;
1727 </description>
1728 </item>
1729
1730 <item>
1731 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
1732 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
1733 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
1734 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
1735 <description>&lt;p&gt;The
1736 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
1737 program is a a very nice system to create virtual machine images. It
1738 create a image file, add a partition table, mount it and run
1739 debootstrap in the mounted directory to create a Debian system on a
1740 stick. Yesterday, I decided to try to teach it how to make images for
1741 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1742 of a plan to simplify the build system for
1743 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1744 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1745 the virtualbox images, but its current build system made multistrap
1746 based system for Dreamplug images, and it is lacking support for
1747 Raspberry Pi.&lt;/p&gt;
1748
1749 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1750 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1751 code and adjusted it to be able to build armel images on my amd64
1752 Debian laptop. I ended up giving vmdebootstrap five new options,
1753 allowing me to replicate the image creation process I use to make
1754 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
1755 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
1756 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
1757 call debootstrap with --foreign and to copy the handler into the
1758 generated chroot before running the second stage. This allow
1759 vmdebootstrap to create armel images on an amd64 host. Next I added
1760 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
1761 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
1762 given file system type, allowing me to create an image with a vfat
1763 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
1764 variant&lt;/tt&gt; option to allow me to create smaller images without the
1765 Debian base system packages installed. Finally, I added an option
1766 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
1767 as a boot loader. It is not needed on the Raspberry Pi and probably
1768 most other non-x86 architectures. The changes were accepted by the
1769 upstream author of vmdebootstrap yesterday and today, and is now
1770 available from
1771 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
1772 upstream project page&lt;/a&gt;.&lt;/p&gt;
1773
1774 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
1775 create a small script (the customize script) to add the non-free
1776 binary blob needed to boot the Raspberry Pi and the APT source
1777 list:&lt;/p&gt;
1778
1779 &lt;p&gt;&lt;pre&gt;
1780 #!/bin/sh
1781 set -e # Exit on first error
1782 rootdir=&quot;$1&quot;
1783 cd &quot;$rootdir&quot;
1784 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
1785 deb http://http.debian.net/debian/ jessie main contrib non-free
1786 EOF
1787 # Install non-free binary blob needed to boot Raspberry Pi. This
1788 # install a kernel somewhere too.
1789 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1790 -O $rootdir/usr/bin/rpi-update
1791 chmod a+x $rootdir/usr/bin/rpi-update
1792 mkdir -p $rootdir/lib/modules
1793 touch $rootdir/boot/start.elf
1794 chroot $rootdir rpi-update
1795 &lt;/pre&gt;&lt;/p&gt;
1796
1797 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
1798 to build the image:&lt;/p&gt;
1799
1800 &lt;pre&gt;
1801 sudo ./vmdebootstrap \
1802 --variant minbase \
1803 --arch armel \
1804 --distribution jessie \
1805 --mirror http://http.debian.net/debian \
1806 --image test.img \
1807 --size 600M \
1808 --bootsize 64M \
1809 --boottype vfat \
1810 --log-level debug \
1811 --verbose \
1812 --no-kernel \
1813 --no-extlinux \
1814 --root-password raspberry \
1815 --hostname raspberrypi \
1816 --foreign /usr/bin/qemu-arm-static \
1817 --customize `pwd`/customize \
1818 --package netbase \
1819 --package git-core \
1820 --package binutils \
1821 --package ca-certificates \
1822 --package wget \
1823 --package kmod
1824 &lt;/pre&gt;&lt;/p&gt;
1825
1826 &lt;p&gt;The list of packages being installed are the ones needed by
1827 rpi-update to make the image bootable on the Raspberry Pi, with the
1828 exception of netbase, which is needed by debootstrap to find
1829 /etc/hosts with the minbase variant. I really wish there was a way to
1830 set up an Raspberry Pi using only packages in the Debian archive, but
1831 that is not possible as far as I know, because it boots from the GPU
1832 using a non-free binary blob.&lt;/p&gt;
1833
1834 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
1835 probably a few others installed. I have not checked the complete
1836 build dependency list.&lt;/p&gt;
1837
1838 &lt;p&gt;The resulting image will not use the hardware floating point unit
1839 on the Raspberry PI, because the armel architecture in Debian is not
1840 optimized for that use. So the images created will be a bit slower
1841 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
1842 </description>
1843 </item>
1844
1845 <item>
1846 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
1847 <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>
1848 <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>
1849 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
1850 <description>&lt;p&gt;The last few days I came across a few good causes that should get
1851 wider attention. I recommend signing and donating to each one of
1852 these. :)&lt;/p&gt;
1853
1854 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
1855 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
1856 Women program which is a Google Summer of Code like initiative to get
1857 more women involved in free software. One debian sponsor has offered
1858 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
1859 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
1860 hope you will to. :)&lt;/p&gt;
1861
1862 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
1863 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
1864 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
1865 take place these days, and their need to fund the work. I&#39;ve already
1866 donated. Are you next?&lt;/p&gt;
1867
1868 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
1869 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1870 statement under the heading
1871 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
1872 Access&lt;/a&gt; for those of us asking for more focus on open access in the
1873 Norwegian government. So far 499 signatures. I hope you will sign it
1874 too.&lt;/p&gt;
1875 </description>
1876 </item>
1877
1878 <item>
1879 <title>Videos about the Freedombox project - for inspiration and learning</title>
1880 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
1881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
1882 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
1883 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
1884 project&lt;/a&gt; have been going on for a while, and have presented the
1885 vision, ideas and solution several places. Here is a little
1886 collection of videos of talks and presentation of the project.&lt;/p&gt;
1887
1888 &lt;ul&gt;
1889
1890 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
1891 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
1892
1893 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
1894 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1895
1896 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
1897 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1898 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
1899 (Youtube)&lt;/li&gt;
1900
1901 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
1902 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
1903
1904 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
1905 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1906
1907 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
1908 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1909 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
1910
1911 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
1912 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
1913 (Youtube)&lt;/li&gt;
1914
1915 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
1916 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
1917
1918 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
1919 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
1920
1921 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
1922 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1923 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
1924
1925 &lt;/ul&gt;
1926
1927 &lt;p&gt;A larger list is available from
1928 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
1929 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
1930
1931 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
1932 Jessie is coming along quite well, and soon both Owncloud and using
1933 Tor should be available for testers of the Freedombox solution. :) In
1934 a few weeks I hope everything needed to test it is included in Debian.
1935 The withsqlite package is already in Debian, and the plinth package is
1936 pending in NEW. The third and vital part of that puzzle is the
1937 metapackage/setup framework, which is still pending an upload. Join
1938 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
1939 (#freedombox on irc.debian.org)&lt;/a&gt; and
1940 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1941 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1942 </description>
1943 </item>
1944
1945 <item>
1946 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
1947 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
1948 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
1949 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
1950 <description>&lt;p&gt;I was introduced to the
1951 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
1952 in 2010, when Eben Moglen presented his vision about serving the need
1953 of non-technical people to keep their personal information private and
1954 within the legal protection of their own homes. The idea is to give
1955 people back the power over their network and machines, and return
1956 Internet back to its intended peer-to-peer architecture. Instead of
1957 depending on a central service, the Freedombox will give everyone
1958 control over their own basic infrastructure.&lt;/p&gt;
1959
1960 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
1961 taken priority. But this summers nasty news about the misuse of trust
1962 and privilege exercised by the &quot;western&quot; intelligence gathering
1963 communities increased my eagerness to contribute to a point where I
1964 actually started working on the project a while back.&lt;/p&gt;
1965
1966 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
1967 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
1968 create a simple and cheap Debian based appliance that anyone can hook
1969 up in their home and get access to secure and private services and
1970 communication. The initial deployment platform have been the
1971 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
1972 which is a piece of hardware I do not own. So to be able to test what
1973 the current Freedombox setup look like, I had to come up with a way to install
1974 it on some hardware I do have access to. I have rewritten the
1975 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
1976 image build framework to use .deb packages instead of only copying
1977 setup into the boot images, and thanks to this rewrite I am able to
1978 set up any machine supported by Debian Wheezy as a Freedombox, using
1979 the previously mentioned deb (and a few support debs for packages
1980 missing in Debian).&lt;/p&gt;
1981
1982 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
1983 scripts
1984 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
1985 and a administrative web interface
1986 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
1987 withsqlite), as well as a privacy enhancing proxy based on
1988 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
1989 (freedombox-privoxy). There is also a web/javascript based XMPP
1990 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
1991 trying (unsuccessfully so far) to talk to the XMPP server
1992 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
1993 web interface is pluggable, and the goal is to use it to enable OpenID
1994 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1995 this is really working yet, see
1996 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
1997 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
1998 on github at the moment. The HTTP proxy is operational out of the
1999 box, and the admin web interface can be used to add/remove plinth
2000 users. I&#39;ve not been able to do anything else with it so far, but
2001 know there are several branches spread around github and other places
2002 with lots of half baked features.&lt;/p&gt;
2003
2004 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2005 following recipes should work to give you a test machine to poke
2006 at.&lt;/p&gt;
2007
2008 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2009
2010 &lt;ol&gt;
2011
2012 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2013 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2014 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2015 to the Debian installer:&lt;p&gt;
2016 &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;
2017
2018 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2019 install on.&lt;/li&gt;
2020
2021 &lt;li&gt;When the installation is finished and the machine have rebooted a
2022 few times, your Freedombox is ready for testing.&lt;/li&gt;
2023
2024 &lt;/ol&gt;
2025
2026 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2027
2028 &lt;ol&gt;
2029
2030 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2031 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2032 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2033 &lt;pre&gt;
2034 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2035 &lt;/pre&gt;&lt;/li&gt;
2036 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2037 &lt;pre&gt;
2038 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2039 apt-key add -
2040 apt-get update
2041 apt-get install freedombox-setup
2042 /usr/lib/freedombox/setup
2043 &lt;/pre&gt;&lt;/li&gt;
2044 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2045
2046 &lt;/ol&gt;
2047
2048 &lt;p&gt;You can test it on other architectures too, but because the
2049 freedombox-privoxy package is binary, it will only work as intended on
2050 the architectures where I have had time to build the binary and put it
2051 in my APT repository. But do not let this stop you. It is only a
2052 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2053
2054 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2055 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2056 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2057 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2058
2059 &lt;p&gt;Please let me know if this works for you, or if you have any
2060 problems. We gather on the IRC channel
2061 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2062 irc.debian.org and the
2063 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2064 mailing list&lt;/a&gt;.&lt;/p&gt;
2065
2066 &lt;p&gt;Once you get your freedombox operational, you can visit
2067 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2068 welcome screen (dead end - do not be surprised if you are unable to
2069 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2070 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2071 default password is &#39;secret&#39;.&lt;/p&gt;
2072 </description>
2073 </item>
2074
2075 <item>
2076 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2077 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2078 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2079 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2080 <description>&lt;p&gt;Earlier, I reported about
2081 &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
2082 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2083 told by IBM that the original disk should be thrown away. And as
2084 there no longer was a problem if I bricked the firmware, I decided
2085 today to try to install Intel firmware to replace the Lenovo firmware
2086 currently on the disk.&lt;/p&gt;
2087
2088 &lt;p&gt;I searched the Intel site for firmware, and found
2089 &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;
2090 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2091 according to the site should contain the latest firmware for SSD
2092 disks. I inserted the broken disk in one of my spare laptops and
2093 booted the ISO from a USB stick. The disk was recognized, but the
2094 program claimed the newest firmware already were installed and refused
2095 to insert any Intel firmware. So no change, and the disk is still
2096 unable to handle write load. :( I guess the only way to get them
2097 working would be if Lenovo releases new firmware. No idea how likely
2098 that is. Anyway, just blogging about this test for completeness. I
2099 got a working Samsung disk, and see no point in spending more time on
2100 the broken disks.&lt;/p&gt;
2101 </description>
2102 </item>
2103
2104 <item>
2105 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2106 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2107 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2108 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2109 <description>&lt;p&gt;Today I switched to
2110 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2111 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2112 my new Thinkpad X230, which was delivered with an
2113 &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
2114 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2115 sustained writes. My hardware supplier have been very forthcoming in
2116 trying to find a solution, and after first trying with another
2117 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2118 disk instead to fix it once and for all. The Samsung disk survived
2119 the installation of Debian with encrypted disks (filling the disk with
2120 random data during installation killed the first two), and I thus
2121 decided to trust it with my data. I have installed it as a Debian Edu
2122 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2123 server at home using Kerberos and LDAP, and will use it as my work
2124 station from now on.&lt;/p&gt;
2125
2126 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2127 Debian Wheezy default installation need to be tuned a bit to increase
2128 performance and increase life time of the disk. The Linux kernel and
2129 user space applications do not yet adjust automatically to such
2130 environment. To make it easier for my self, I created a draft Debian
2131 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2132 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2133 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2134 is set up to adjust the setup of the machine by just installing the
2135 package. If there is any non-SSD disk in the machine, the package
2136 will refuse to install, as I did not try to write any logic to sort
2137 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2138
2139 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2140 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2141 where I set up the machine with one large encrypted partition (in
2142 addition to /boot), put LVM on top of this and set up partitions on
2143 top of this again. See the README file in the package source for the
2144 references I used to pick the settings. At the moment these
2145 parameters are tuned:&lt;/p&gt;
2146
2147 &lt;ul&gt;
2148
2149 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2150 (adding discard to /etc/crypttab)&lt;/li&gt;
2151
2152 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2153 this case a cryptsetup partition) by changing issue_discards from
2154 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2155
2156 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2157 systems.&lt;/li&gt;
2158
2159 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2160 /etc/fstab.&lt;/li&gt;
2161
2162 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2163
2164 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2165 cron.daily).&lt;/li&gt;
2166
2167 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2168 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2169
2170 &lt;/ul&gt;
2171
2172 &lt;p&gt;During installation, I cancelled the part where the installer fill
2173 the disk with random data, as this would kill the SSD performance for
2174 little gain. My goal with the encrypted file system is to ensure
2175 those stealing my laptop end up with a brick and not a working
2176 computer. I have no hope in keeping the really resourceful people
2177 from getting the data on the disk (see
2178 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2179 Thus I concluded that adding the discard option to crypttab is the
2180 right thing to do.&lt;/p&gt;
2181
2182 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2183 it for SSD, but others recommended deadline and a benchmark I found
2184 indicated that deadline might be better for interactive use.&lt;/p&gt;
2185
2186 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2187 and ext4, but read that it would give a performance hit ever time a
2188 file is removed, and thought it best to that that slowdown once a day
2189 instead of during my work.&lt;/p&gt;
2190
2191 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2192 this is already done by Debian Edu.&lt;/p&gt;
2193
2194 &lt;p&gt;I have not yet started on the user space tuning. I expect
2195 iceweasel need some tuning, and perhaps other applications too, but
2196 have not yet had time to investigate those parts.&lt;/p&gt;
2197
2198 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2199 there.&lt;/p&gt;
2200
2201 &lt;p&gt;As for the answer to the question in the title of this blog post,
2202 as far as I know, the only solution I know about is to replace the
2203 disk. It might be possible to flash it with Intel firmware instead of
2204 the Lenovo firmware. But I have not tried and did not want to do so
2205 without approval from Lenovo as I wanted to keep the warranty on the
2206 disk until a solution was found and they wanted the broken disks
2207 back.&lt;/p&gt;
2208 </description>
2209 </item>
2210
2211 <item>
2212 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2213 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2214 <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>
2215 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2216 <description>&lt;p&gt;A few days ago, I wrote about
2217 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2218 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2219 was dying during installation because it is unable to cope with
2220 sustained write. My supplier is in contact with
2221 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2222 replacement disk to try to fix the problem. They decided to send an
2223 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2224
2225 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2226 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2227 same firmware version as the original. This time my hope raised
2228 slightly as the installation progressed, as the original disk used to
2229 die after 4-7% of the disk was written to, while this time it kept
2230 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2231 died again and I was back on square one. I still do not have a new
2232 laptop with a disk I can trust. I can not live with a disk that might
2233 lock up when I download a new
2234 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2235 other large files. I look forward to hearing from my supplier with
2236 the next proposal from Lenovo.&lt;/p&gt;
2237
2238 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2239 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2240 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2241 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2242 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2243 P/N 45N8295, P0C38732.&lt;/p&gt;
2244
2245 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2246 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2247 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2248 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2249 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2250 P/N 45N8295, P0C38732.&lt;/p&gt;
2251
2252 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2253 SA, date and WNPP values. Mentioning all the details here in case
2254 someone is able to use the information to find a way to identify the
2255 failing disk among working ones (if any such working disk actually
2256 exist).&lt;/p&gt;
2257 </description>
2258 </item>
2259
2260 <item>
2261 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2262 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2263 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2264 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2265 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2266 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2267 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2268 member assosiation NUUG&lt;/a&gt; and
2269 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2270 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2271 Bitraf&lt;/a&gt;.&lt;/p&gt;
2272
2273 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2274 welcome, and there is no fee to participate. There is on the other
2275 hand limited space, and only room for 30 people. Please put your name
2276 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2277 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2278 </description>
2279 </item>
2280
2281 <item>
2282 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2283 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2284 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2285 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2286 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2287 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2288 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2289 time to spend on it, and it took a while to find a model I believe
2290 will do the job, but two days ago the replacement finally arrived. I
2291 ended up picking a
2292 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2293 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2294 a roaming workstation, and it seemed to work flawlessly. But my
2295 second installation with encrypted disk was not as successful. More
2296 on that below.&lt;/p&gt;
2297
2298 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2299 important requirements (robust and with a good keyboard) are never
2300 listed in the feature list. But I did get good help from the search
2301 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2302 allowed me to limit the list of interesting laptops based on my other
2303 requirements. A bit surprising that SSD disk are not disks according
2304 to that search interface, so I had to drop specifying the number of
2305 disks from my search parameters. I also asked around among friends to
2306 get their impression on keyboards and robustness.&lt;/p&gt;
2307
2308 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2309 X41. I am not quite convinced about the keyboard, as it is
2310 significantly wider than my old keyboard, and I have to stretch my
2311 hand a lot more to reach the edges. But the key response is fairly
2312 good and the individual key shape is fairly easy to handle, so I hope
2313 I will get used to it. My old X40 was starting to fail, and I really
2314 needed a new laptop now. :)&lt;/p&gt;
2315
2316 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2317 visit to the BIOS during boot it disable it.&lt;/p&gt;
2318
2319 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2320 lock up during load. And this happen when installing Debian Wheezy
2321 with encrypted disk, while the disk is being filled with random data.
2322 I also tested to install Ubuntu Raring, and it happen there too if I
2323 reenable the code to fill the disk with random data (it is disabled by
2324 default in Ubuntu). And the bug with is already known. It was
2325 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2326 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2327 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2328 kernel developers as
2329 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2330 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2331 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2332 Lenovo forums, both for
2333 &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
2334 2012-11-10&lt;/a&gt; and for
2335 &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
2336 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2337 reports state that the disk lock up during use if many writes are done
2338 on the disk, so it is much no use to work around the installation
2339 problem and end up with a computer that can lock up at any moment.
2340 There is even a
2341 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2342 available&lt;/a&gt; that will lock up the hard drive after running a few
2343 minutes by writing to a file.&lt;/p&gt;
2344
2345 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2346 contacting PCHELP Norway (request 01D1FDP) which handle support
2347 requests for Lenovo, his first suggestion was to upgrade the disk
2348 firmware. Unfortunately there is no newer firmware available from
2349 Lenovo, as my disk already have the most recent one (version LF1i). I
2350 hope to hear more from him today and hope the problem can be
2351 fixed. :)&lt;/p&gt;
2352 </description>
2353 </item>
2354
2355 <item>
2356 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2357 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2358 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2359 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2360 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2361 trusty old Thinkpad X41. Unfortunately I did not have much time to
2362 spend on it, but today the replacement finally arrived. I ended up
2363 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2364 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2365 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2366 this, it is installing what I hope will be a more final installation,
2367 with a encrypted hard drive to ensure any dope head stealing it end up
2368 with an expencive door stop.&lt;/p&gt;
2369
2370 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2371 important requirements (robust and with a good keyboard) are never
2372 listed in the feature list. But I did get good help from the search
2373 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2374 allowed me to limit the list of interesting laptops based on my other
2375 requirements. A bit surprising that SSD disk are not disks, so I had
2376 to drop number of disks from my search parameters.&lt;/p&gt;
2377
2378 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2379 wider than my old keyboard, and I have to stretch my hand a lot more
2380 to reach the edges. But the key response is fairly good and the
2381 individual key shape is fairly easy to handle, so I hope I will get
2382 used to it. My old X40 was starting to fail, and I really needed a
2383 new laptop now. :)&lt;/p&gt;
2384
2385 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2386 </description>
2387 </item>
2388
2389 <item>
2390 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2391 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2392 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2393 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2394 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2395 perfectly capable of, and I have to do it manually to get things
2396 working. One such task is to find out what firmware packages are
2397 needed to get the hardware on my computer working. Most often this
2398 affect the wifi card, but some times it even affect the RAID
2399 controller or the ethernet card. Today I pushed version 0.4 of the
2400 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2401 including a new script isenkram-autoinstall-firmware handling the
2402 process of asking all the loaded kernel modules what firmware files
2403 they want, find debian packages providing these files and install the
2404 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2405
2406 &lt;p&gt;&lt;pre&gt;
2407 # isenkram-autoinstall-firmware
2408 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2409 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2410 info: locating packages with the requested firmware files
2411 info: Updating APT sources after adding non-free APT source
2412 info: trying to install firmware-ipw2x00
2413 firmware-ipw2x00
2414 firmware-ipw2x00
2415 Preconfiguring packages ...
2416 Selecting previously deselected package firmware-ipw2x00.
2417 (Reading database ... 259727 files and directories currently installed.)
2418 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2419 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2420 #
2421 &lt;/pre&gt;&lt;/p&gt;
2422
2423 &lt;p&gt;When all the requested firmware is present, a simple message is
2424 printed instead:&lt;/p&gt;
2425
2426 &lt;p&gt;&lt;pre&gt;
2427 # isenkram-autoinstall-firmware
2428 info: did not find any firmware files requested by loaded kernel modules. exiting
2429 #
2430 &lt;/pre&gt;&lt;/p&gt;
2431
2432 &lt;p&gt;It could use some polish, but it is already working well and saving
2433 me some time when setting up new machines. :)&lt;/p&gt;
2434
2435 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2436 kernel modules, and look up each one of them using modinfo, to find
2437 the firmware files listed in the module meta-information. Next, it
2438 download the Contents file from a nearby APT mirror, and search for
2439 the firmware files in this file to locate the package with the
2440 requested firmware file. If the package is in the non-free section, a
2441 non-free APT source is added and the package is installed using
2442 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2443 machine.&lt;/p&gt;
2444
2445 &lt;p&gt;I hope someone find time to implement a more polished version of
2446 this script as part of the hw-detect debian-installer module, to
2447 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2448 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2449 firmware during a PXE install when the packages already are available
2450 from the nearby Debian mirror.&lt;/p&gt;
2451 </description>
2452 </item>
2453
2454 <item>
2455 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2456 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2457 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2458 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2459 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2460 the screen just turn black when Linux boot, either during installation
2461 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2462 last few years, but only recently understood the cause. I&#39;ve seen it
2463 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2464 The reason seem to be in the wiring of some laptops. The system to
2465 control the screen background light is inverted, so when Linux try to
2466 turn the brightness fully on, it end up turning it off instead. I do
2467 not know which Linux drivers are affected, but this post is about the
2468 i915 driver used by the
2469 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2470 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2471
2472 &lt;p&gt;The problem can be worked around two ways. Either by adding
2473 i915.invert_brightness=1 as a kernel option, or by adding a file in
2474 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2475 option when it load the i915 kernel module. On Debian and Ubuntu, it
2476 can be done by running these commands as root:&lt;/p&gt;
2477
2478 &lt;pre&gt;
2479 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2480 update-initramfs -u -k all
2481 &lt;/pre&gt;
2482
2483 &lt;p&gt;Since March 2012 there is
2484 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2485 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2486 hardware have this problem, and get the driver to invert the
2487 brightness setting automatically. To use it, one need to add a row in
2488 &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
2489 intel_quirks array&lt;/a&gt; in the driver source
2490 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2491 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2492 number (vendor number 8086 is assumed) and subdevice vendor and device
2493 number.&lt;/p&gt;
2494
2495 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2496 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2497
2498 &lt;p&gt;&lt;pre&gt;
2499 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2500 3rd Gen Core processor Graphics Controller [8086:0156] \
2501 (rev 09) (prog-if 00 [VGA controller])
2502 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2503 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2504 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2505 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2506 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2507 Latency: 0
2508 Interrupt: pin A routed to IRQ 42
2509 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2510 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2511 Region 4: I/O ports at 4000 [size=64]
2512 Expansion ROM at &lt;unassigned&gt; [disabled]
2513 Capabilities: &lt;access denied&gt;
2514 Kernel driver in use: i915
2515 &lt;/pre&gt;&lt;/p&gt;
2516
2517 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2518
2519 &lt;p&gt;&lt;pre&gt;
2520 struct intel_quirk intel_quirks[] = {
2521 ...
2522 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2523 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2524 ...
2525 }
2526 &lt;/pre&gt;&lt;/p&gt;
2527
2528 &lt;p&gt;According to the kernel module instructions (as seen using
2529 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2530 invert_brightness flag should be sent to the
2531 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2532 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2533 developers. But my email about the laptop sent 2013-06-03 have not
2534 yet shown up in
2535 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2536 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2537 emails from non-subscribers. Because of this, I sent my patch also to
2538 the Debian bug tracking system instead as
2539 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2540 sure the patch is not lost.&lt;/p&gt;
2541
2542 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2543 with this problem working properly with Linux. If you use Gnome, your
2544 worries should be over at this point. But if you use KDE, there is
2545 something in KDE ignoring the invert_brightness setting and turning on
2546 the screen during login. I&#39;ve reported it to Debian as
2547 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2548 have no idea yet how to figure out exactly what subsystem is doing
2549 this. Perhaps you can help? Perhaps you know what the Gnome
2550 developers did to handle this, and this can give a clue to the KDE
2551 developers? Or you know where in KDE the screen brightness is changed
2552 during login? If so, please update the BTS report (or get in touch if
2553 you do not know how to update BTS).&lt;/p&gt;
2554
2555 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2556 acpi_backlight=vendor, to disable ACPI backlight support completely,
2557 as the ACPI information on the machine is trash and it is better to
2558 leave it to the intel video driver to control the screen
2559 backlight.&lt;/p&gt;
2560 </description>
2561 </item>
2562
2563 <item>
2564 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2565 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2566 <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>
2567 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2568 <description>&lt;p&gt;Two days ago, I asked
2569 &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
2570 I could install Linux on a Packard Bell EasyNote LV computer
2571 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2572 with the obstacles put in the way of Linux users on a laptop with UEFI
2573 and Windows 8.&lt;/p&gt;
2574
2575 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2576 secure booting or fast boot. I suspect fast boot was the problem,
2577 causing the firmware to boot directly from HD without considering any
2578 key presses and alternative devices, but do not know UEFI settings
2579 enough to tell.&lt;/p&gt;
2580
2581 &lt;p&gt;There is no way to install Linux on the machine in question without
2582 opening the box and disconnecting the hard drive! This is as far as I
2583 can tell, the only way to get access to the firmware setup menu
2584 without accepting the Windows 8 license agreement. I am told (and
2585 found description on how to) that it is possible to configure the
2586 firmware setup once booted into Windows 8. But as I believe the terms
2587 of that agreement are completely unacceptable, accepting the license
2588 was never an alternative. I do not enter agreements I do not intend
2589 to follow.&lt;/p&gt;
2590
2591 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2592 waste many hours on this, but luckily there was a way to get it to
2593 work. But I would not recommend it to anyone planning to run Linux on
2594 it, and I have become sceptical to Windows 8 certified laptops. Is
2595 this the way Linux will be forced out of the market place, by making
2596 it close to impossible for &quot;normal&quot; users to install Linux without
2597 accepting the Microsoft Windows license terms? Or at least not
2598 without risking to loose the warranty?&lt;/p&gt;
2599
2600 &lt;p&gt;I&#39;ve updated the
2601 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2602 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2603 do not have to struggle as much as I did to get Linux into the
2604 machine.&lt;/p&gt;
2605
2606 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2607 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2608 </description>
2609 </item>
2610
2611 <item>
2612 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2613 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2614 <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>
2615 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2616 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2617 new laptops for my parents and a few others. I bought Packard Bell
2618 Easynote LV to run Kubuntu on and use as their home computer. But I
2619 am completely unable to figure out how to install Linux on it. The
2620 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2621 instead of a BIOS to boot.&lt;/p&gt;
2622
2623 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
2624 to get it to boot the Linux installer from my USB stick. I have yet
2625 to try the DVD install, and still hope it will work. when I turn on
2626 the computer, there is no information on what buttons to press to get
2627 the normal boot menu. I expect to get some boot menu to select PXE or
2628 USB stick booting. When booting, it first ask for the language to
2629 use, then for some regional settings, and finally if I will accept the
2630 Windows 8 terms of use. As these terms are completely unacceptable to
2631 me, I have no other choice but to turn off the computer and try again
2632 to get it to boot the Linux installer.&lt;/p&gt;
2633
2634 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
2635 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2636 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
2637 installed on this machine, please get in touch or update that wiki
2638 page. If I can&#39;t find a way to install Linux, I will have to return
2639 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
2640
2641 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
2642 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
2643 on new Laptops?&lt;/p&gt;
2644 </description>
2645 </item>
2646
2647 <item>
2648 <title>How to transform a Debian based system to a Debian Edu installation</title>
2649 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
2650 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
2651 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
2652 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
2653 an operating system based on Debian intended for use in schools. It
2654 contain a turn-key solution for the computer network provided to
2655 pupils in the primary schools. It provide both the central server,
2656 network boot servers and desktop environments with heaps of
2657 educational software. The project was founded almost 12 years ago,
2658 2001-07-02. If you want to support the project, which is in need for
2659 cash to fund developer gatherings and other project related activity,
2660 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
2661 donate some money&lt;/a&gt;.
2662
2663 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
2664 lists and elsewhere, is the question on how to transform a Debian or
2665 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
2666 hard, and last week I wrote a script to replicate the steps done by
2667 the Debian Edu installer.&lt;/p&gt;
2668
2669 &lt;p&gt;The script,
2670 &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;
2671 in the debian-edu-config package, will go through these six steps and
2672 transform an existing Debian Wheezy or Ubuntu (untested) installation
2673 into a Debian Edu Workstation:&lt;/p&gt;
2674
2675 &lt;ol&gt;
2676
2677 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
2678 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
2679 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
2680 our configuration.&lt;/li&gt;
2681 &lt;li&gt;Preseed debconf database with profile setup in
2682 /etc/debian-edu/config, and run tasksel to install packages
2683 according to the profile specified in the config above,
2684 overriding some of the Debian automation machinery.&lt;/li&gt;
2685 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
2686 that could not be done using preseeding.&lt;/li&gt;
2687 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
2688
2689 &lt;/ol&gt;
2690
2691 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
2692 replicated like this. Disk partitioning and LVM setup, for example.
2693 So this script just assume there is enough disk space to install all
2694 the needed packages.&lt;/p&gt;
2695
2696 &lt;p&gt;The script was created to help a Debian Edu student working on
2697 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
2698 Debian Edu client, and using it he can take the existing
2699 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
2700 transform it into a fully functioning Debian Edu Workstation (or
2701 Roaming Workstation, or whatever :).&lt;/p&gt;
2702
2703 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
2704 If a LXDE based Roaming workstation is wanted instead, modify the
2705 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
2706
2707 &lt;p&gt;&lt;pre&gt;
2708 PROFILE=&quot;Roaming-Workstation&quot;
2709 DESKTOP=&quot;lxde&quot;
2710 &lt;/pre&gt;&lt;/p&gt;
2711
2712 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
2713 the cloud, by starting with a virtual Debian installation at some
2714 virtual hosting service and setting up all the services on first
2715 boot.&lt;/p&gt;
2716 </description>
2717 </item>
2718
2719 <item>
2720 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
2721 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
2722 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
2723 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
2724 <description>&lt;P&gt;In January,
2725 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
2726 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
2727 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
2728 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
2729 marvellous construction system from Denmark. We also created
2730 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
2731 a place to take notes and write down our plans and hopes. And several
2732 people showed up to help. I was very happy to see the effect of my
2733 call. Since the small start, we have a debtags tag
2734 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
2735 tag for LEGO related packages, and now count 10 packages related to
2736 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
2737
2738 &lt;p&gt;&lt;table&gt;
2739 &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;
2740 &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;
2741 &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;
2742 &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;
2743 &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;
2744 &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;
2745 &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;
2746 &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;
2747 &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;
2748 &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;
2749 &lt;/table&gt;&lt;/p&gt;
2750
2751 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2752 currently available in Jessie/testing. leocad is so far only
2753 available in experimental.&lt;/p&gt;
2754
2755 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
2756 adding the rest of the great free software tools available on Linux
2757 for LEGO designers.&lt;/p&gt;
2758 </description>
2759 </item>
2760
2761 <item>
2762 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
2763 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
2764 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
2765 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
2766 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
2767 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
2768 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
2769 Debian release, and I expect to move my machines at home over to it fairly
2770 soon.&lt;/p&gt;
2771
2772 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
2773 in particular make me very happy to see included. The
2774 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
2775 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
2776 included for the first time. Alongside similar programs like
2777 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
2778 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
2779 it allow for visual programming where syntax errors can not happen,
2780 and a friendly programming environment for learning to control the
2781 computer. Scratch will also be included in the next release of Debian
2782 Edu.&lt;/a&gt;
2783
2784 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
2785 Edu/Skolelinux release too. The
2786 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
2787 alpha release&lt;/a&gt; went out last week, and the next should soon
2788 follow.&lt;p&gt;
2789 </description>
2790 </item>
2791
2792 <item>
2793 <title>Isenkram 0.2 finally in the Debian archive</title>
2794 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
2795 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
2796 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
2797 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
2798 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
2799 for many months. I uploaded it to the Debian experimental suite
2800 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
2801
2802 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
2803 install to work with a pluggable hardware device. The suggestion pop
2804 up when the device is plugged in. For example if a Lego Mindstorm NXT
2805 is inserted, it will suggest to install the program needed to program
2806 the NXT controller. Give it a go, and report bugs and suggestions to
2807 BTS. :)&lt;/p&gt;
2808 </description>
2809 </item>
2810
2811 <item>
2812 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
2813 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
2814 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
2815 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
2816 <description>&lt;p&gt;My
2817 &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
2818 bitcoin related blog post&lt;/a&gt; mentioned that the new
2819 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
2820 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2821 2013-01-19, and have been available in unstable since then. It was
2822 automatically copied to Ubuntu, and is available in their Raring
2823 version too.&lt;/p&gt;
2824
2825 &lt;p&gt;But there is a strange problem with the build that block this new
2826 version from being available on the i386 and kfreebsd-i386
2827 architectures. For some strange reason, the autobuilders in Debian
2828 for these architectures fail to run the test suite on these
2829 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
2830 We are so far unable to reproduce it when building it manually, and
2831 no-one have been able to propose a fix. If you got an idea what is
2832 failing, please let us know via the BTS.&lt;/p&gt;
2833
2834 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
2835 I often run low on disk space, is the fact that the client will exit
2836 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
2837 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
2838 it. :)&lt;/p&gt;
2839
2840 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
2841 activities, please send Bitcoin donations to my address
2842 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2843 </description>
2844 </item>
2845
2846 <item>
2847 <title>Welcome to the world, Isenkram!</title>
2848 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
2849 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
2850 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
2851 <description>&lt;p&gt;Yesterday, I
2852 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
2853 for testers&lt;/a&gt; for my prototype for making Debian better at handling
2854 pluggable hardware devices, which I
2855 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
2856 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
2857 up, and caused me to really want to to open up the development to more
2858 people. But before I did this, I want to come up with a sensible name
2859 for this project. Today I finally decided on a new name, and I have
2860 renamed the project from hw-support-handler to this new name. In the
2861 process, I moved the source to git and made it available as a
2862 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
2863 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
2864 To fetch and build the latest version of the source, use&lt;/p&gt;
2865
2866 &lt;pre&gt;
2867 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2868 cd isenkram &amp;&amp; git-buildpackage -us -uc
2869 &lt;/pre&gt;
2870
2871 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
2872 want to hack on the source or improve the package, please go ahead.
2873 But please talk to me first on IRC or via email before you do major
2874 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
2875
2876 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
2877 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2878 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
2879 the German word eisenkram, for those that are familiar with that
2880 word.&lt;/p&gt;
2881
2882 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
2883 instructions, to avoid confusing people with an error from the signing
2884 process.&lt;/p&gt;
2885
2886 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
2887 clone argument to avoid the need for authentication.&lt;/p&gt;
2888 </description>
2889 </item>
2890
2891 <item>
2892 <title>First prototype ready making hardware easier to use in Debian</title>
2893 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
2894 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
2895 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
2896 <description>&lt;p&gt;Early this month I set out to try to
2897 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
2898 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
2899 prototype is working, and it is ready for a larger audience. To test
2900 it, fetch the
2901 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
2902 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
2903 package. You might have to log out and in again activate the
2904 autostart script.&lt;/p&gt;
2905
2906 &lt;p&gt;The design is simple:&lt;/p&gt;
2907
2908 &lt;ul&gt;
2909
2910 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
2911 hw-support-handlerd to start when the user log in.&lt;/li&gt;
2912
2913 &lt;li&gt;This program listen for kernel events about new hardware (directly
2914 from the kernel like udev does), not using HAL dbus events as I
2915 initially did.&lt;/li&gt;
2916
2917 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
2918 the APT database, a database
2919 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
2920 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
2921
2922 &lt;li&gt;If a package is mapped to the hardware in question, the package
2923 isn&#39;t installed yet and this is the first time the hardware was
2924 plugged in, show a desktop notification suggesting to install the
2925 package or packages.&lt;/li&gt;
2926
2927 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
2928 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
2929
2930 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
2931 package while showing progress information in a window.&lt;/li&gt;
2932
2933 &lt;/ul&gt;
2934
2935 &lt;p&gt;I still need to come up with a better name for the system. Here
2936 are some screen shots showing the prototype in action. First the
2937 notification, then the password request, and finally the request to
2938 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
2939
2940 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
2941 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
2942 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
2943 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
2944 &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;
2945
2946 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
2947 is already useful. The database of hardware to package mappings also
2948 need more work. It is currently compatible with the Ubuntu way of
2949 storing such information in the package control file, but could be
2950 changed to use other formats instead or in addition to the current
2951 method. I&#39;ve dropped the use of discover for this mapping, as the
2952 modalias approach is more flexible and easier to use on Linux as long
2953 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
2954
2955 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
2956 here is the command required to check out and build the source: Use
2957 &#39;&lt;tt&gt;svn checkout
2958 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2959 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
2960 devscripts package.&lt;/p&gt;
2961
2962 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
2963 renamed to Isenkram and the source moved from the Debian Edu
2964 subversion repository to a Debian collab-maint git repository. See
2965 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
2966 instructions&lt;/a&gt; for details.&lt;/p&gt;
2967 </description>
2968 </item>
2969
2970 <item>
2971 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
2972 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
2973 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
2974 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
2975 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
2976 suddenly in bed. With a quiet whimper, it went completely quiet and
2977 black. The power button was no longer able to turn it on. It was a
2978 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2979 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2980 Compaq I had before that. Now I need to find a replacement. To keep
2981 going during Christmas, I moved the one year old SSD disk to my old
2982 X40 where it fitted (only one I had left that could use it), but it is
2983 not a durable solution.
2984
2985 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
2986 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
2987
2988 &lt;ul&gt;
2989
2990 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
2991 than A4).&lt;/li&gt;
2992 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
2993 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
2994 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
2995 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
2996 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
2997 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
2998 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
2999 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3000 size).&lt;/li&gt;
3001 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3002 X.org packages.&lt;/li&gt;
3003 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3004 the time).
3005
3006 &lt;/ul&gt;
3007
3008 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3009 list. The reason is simply that the specifications on laptops the
3010 last 10-15 years have been sufficient for my needs, and I have to look
3011 at other features to choose my laptop. But are there still made as
3012 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3013 robust, and Thinkpads seem to be heading in the wrong direction since
3014 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3015 still be useful.&lt;/p&gt;
3016
3017 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3018 external keyboard? I&#39;ll have to check the
3019 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3020 well-supported laptops, or perhaps just buy one preinstalled from one
3021 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3022 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3023 </description>
3024 </item>
3025
3026 <item>
3027 <title>How to find a browser plugin supporting a given MIME type</title>
3028 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3029 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3030 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3031 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3032 install to get support for a given MIME type. Thanks to
3033 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3034 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3035 Unfortunately, not very many packages provide the needed meta
3036 information, Anyway, here is a small script to look up all browser
3037 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3038
3039 &lt;pre&gt;
3040 #!/usr/bin/python
3041 import sys
3042 import apt
3043 def pkgs_handling_mimetype(mimetype):
3044 cache = apt.Cache()
3045 cache.open(None)
3046 thepkgs = []
3047 for pkg in cache:
3048 version = pkg.candidate
3049 if version is None:
3050 version = pkg.installed
3051 if version is None:
3052 continue
3053 record = version.record
3054 if not record.has_key(&#39;Npp-MimeType&#39;):
3055 continue
3056 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3057 for t in mime_types:
3058 t = t.rstrip().strip()
3059 if t == mimetype:
3060 thepkgs.append(pkg.name)
3061 return thepkgs
3062 mimetype = &quot;audio/ogg&quot;
3063 if 1 &lt; len(sys.argv):
3064 mimetype = sys.argv[1]
3065 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3066 for pkg in pkgs_handling_mimetype(mimetype):
3067 print &quot; %s&quot; %pkg
3068 &lt;/pre&gt;
3069
3070 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3071
3072 &lt;pre&gt;
3073 % ./apt-find-browserplug-for-mimetype
3074 Browser plugin packages supporting audio/ogg:
3075 gecko-mediaplayer
3076 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3077 Browser plugin packages supporting application/x-shockwave-flash:
3078 browser-plugin-gnash
3079 %
3080 &lt;/pre&gt;
3081
3082 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3083 itself to query for plugins and propose to install the needed
3084 packages. It would be great if Debian supported such feature too. Is
3085 anyone working on adding it?&lt;/p&gt;
3086
3087 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3088 request for icweasel support for this feature is
3089 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3090 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3091 of manpower and wish for a different design is the reason thus feature
3092 is not yet in iceweasel from Debian.&lt;/p&gt;
3093 </description>
3094 </item>
3095
3096 <item>
3097 <title>What is the most supported MIME type in Debian?</title>
3098 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3099 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3100 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3101 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3102 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3103 proposal to make it possible for a Desktop application to propose to
3104 the user some package to install to gain support for a given MIME
3105 type, font, library etc. that is currently missing. With such
3106 mechanism in place, it would be possible for the desktop to
3107 automatically propose and install leocad if some LDraw file is
3108 downloaded by the browser.&lt;/p&gt;
3109
3110 &lt;p&gt;To get some idea about the current content of the archive, I decided
3111 to write a simple program to extract all .desktop files from the
3112 Debian archive and look up the claimed MIME support there. The result
3113 can be found on the
3114 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3115 site&lt;/a&gt;. Using the collected information, it become possible to
3116 answer the question in the title. Here are the 20 most supported MIME
3117 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3118 The complete list is available from the link above.&lt;/p&gt;
3119
3120 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3121
3122 &lt;pre&gt;
3123 count MIME type
3124 ----- -----------------------
3125 32 text/plain
3126 30 audio/mpeg
3127 29 image/png
3128 28 image/jpeg
3129 27 application/ogg
3130 26 audio/x-mp3
3131 25 image/tiff
3132 25 image/gif
3133 22 image/bmp
3134 22 audio/x-wav
3135 20 audio/x-flac
3136 19 audio/x-mpegurl
3137 18 video/x-ms-asf
3138 18 audio/x-musepack
3139 18 audio/x-mpeg
3140 18 application/x-ogg
3141 17 video/mpeg
3142 17 audio/x-scpls
3143 17 audio/ogg
3144 16 video/x-ms-wmv
3145 &lt;/pre&gt;
3146
3147 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3148
3149 &lt;pre&gt;
3150 count MIME type
3151 ----- -----------------------
3152 33 text/plain
3153 32 image/png
3154 32 image/jpeg
3155 29 audio/mpeg
3156 27 image/gif
3157 26 image/tiff
3158 26 application/ogg
3159 25 audio/x-mp3
3160 22 image/bmp
3161 21 audio/x-wav
3162 19 audio/x-mpegurl
3163 19 audio/x-mpeg
3164 18 video/mpeg
3165 18 audio/x-scpls
3166 18 audio/x-flac
3167 18 application/x-ogg
3168 17 video/x-ms-asf
3169 17 text/html
3170 17 audio/x-musepack
3171 16 image/x-xbitmap
3172 &lt;/pre&gt;
3173
3174 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3175
3176 &lt;pre&gt;
3177 count MIME type
3178 ----- -----------------------
3179 31 text/plain
3180 31 image/png
3181 31 image/jpeg
3182 29 audio/mpeg
3183 28 application/ogg
3184 27 image/gif
3185 26 image/tiff
3186 26 audio/x-mp3
3187 23 audio/x-wav
3188 22 image/bmp
3189 21 audio/x-flac
3190 20 audio/x-mpegurl
3191 19 audio/x-mpeg
3192 18 video/x-ms-asf
3193 18 video/mpeg
3194 18 audio/x-scpls
3195 18 application/x-ogg
3196 17 audio/x-musepack
3197 16 video/x-ms-wmv
3198 16 video/x-msvideo
3199 &lt;/pre&gt;
3200
3201 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3202 information mentioned in DEP-11. I have not yet had time to look at
3203 it, but hope the PackageKit people in Debian are on top of these
3204 issues.&lt;/p&gt;
3205
3206 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3207 discovering a typo in my script.&lt;/p&gt;
3208 </description>
3209 </item>
3210
3211 <item>
3212 <title>Using modalias info to find packages handling my hardware</title>
3213 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3214 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3215 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3216 <description>&lt;p&gt;Yesterday, I wrote about the
3217 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3218 values provided by the Linux kernel&lt;/a&gt; following my hope for
3219 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3220 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3221 modalias values attached to package names can be used to map packages
3222 to hardware. This allow the system to look up and suggest relevant
3223 packages when I plug in some new hardware into my machine, and replace
3224 discover and discover-data as the database used to map hardware to
3225 packages.&lt;/p&gt;
3226
3227 &lt;p&gt;I create a modaliases file with entries like the following,
3228 containing package name, kernel module name (if relevant, otherwise
3229 the package name) and globs matching the relevant hardware
3230 modalias.&lt;/p&gt;
3231
3232 &lt;p&gt;&lt;blockquote&gt;
3233 Package: package-name
3234 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3235 &lt;/blockquote&gt;&lt;/p&gt;
3236
3237 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3238 for a given modalias value using this file.&lt;/p&gt;
3239
3240 &lt;p&gt;An entry like this would suggest the video and picture application
3241 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3242
3243 &lt;p&gt;&lt;blockquote&gt;
3244 Package: cheese
3245 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3246 &lt;/blockquote&gt;&lt;/p&gt;
3247
3248 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3249 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3250
3251 &lt;p&gt;&lt;blockquote&gt;
3252 Package: pcmciautils
3253 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3254 &lt;/blockquote&gt;&lt;/p&gt;
3255
3256 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3257 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3258
3259 &lt;p&gt;&lt;blockquote&gt;
3260 Package: colorhug-client
3261 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3262 &lt;/blockquote&gt;&lt;/p&gt;
3263
3264 &lt;p&gt;I believe the format is compatible with the format of the Packages
3265 file in the Debian archive. Ubuntu already uses their Packages file
3266 to store their mappings from packages to hardware.&lt;/p&gt;
3267
3268 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3269 announce the hardware it support in a way my prototype understand.
3270 This allow those publishing packages in an APT source outside the
3271 Debian archive as well as those backporting packages to make sure the
3272 hardware mapping are included in the package meta information. I&#39;ve
3273 tested such header in the pymissile package, and its modalias mapping
3274 is working as it should with my prototype. It even made it to Ubuntu
3275 Raring.&lt;/p&gt;
3276
3277 &lt;p&gt;To test if it was possible to look up supported hardware using only
3278 the shell tools available in the Debian installer, I wrote a shell
3279 implementation of the lookup code. The idea is to create files for
3280 each modalias and let the shell do the matching. Please check out and
3281 try the
3282 &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;
3283 shell script. It run without any extra dependencies and fetch the
3284 hardware mappings from the Debian archive and the subversion
3285 repository where I currently work on my prototype.&lt;/p&gt;
3286
3287 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3288 install yubikey-personalization:&lt;/p&gt;
3289
3290 &lt;p&gt;&lt;blockquote&gt;
3291 % ./hw-support-lookup
3292 &lt;br&gt;yubikey-personalization
3293 &lt;br&gt;%
3294 &lt;/blockquote&gt;&lt;/p&gt;
3295
3296 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3297 propose to install the pcmciautils package:&lt;/p&gt;
3298
3299 &lt;p&gt;&lt;blockquote&gt;
3300 % ./hw-support-lookup
3301 &lt;br&gt;pcmciautils
3302 &lt;br&gt;%
3303 &lt;/blockquote&gt;&lt;/p&gt;
3304
3305 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3306 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3307 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3308
3309 &lt;p&gt;It could be possible to generate several of the mappings between
3310 packages and hardware. One source would be to look at packages with
3311 kernel modules, ie packages with *.ko files in /lib/modules/, and
3312 extract their modalias information. Another would be to look at
3313 packages with udev rules, ie packages with files in
3314 /lib/udev/rules.d/, and extract their vendor/model information to
3315 generate a modalias matching rule. I have not tested any of these to
3316 see if it work.&lt;/p&gt;
3317
3318 &lt;p&gt;If you want to help implementing a system to let us propose what
3319 packages to install when new hardware is plugged into a Debian
3320 machine, please send me an email or talk to me on
3321 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3322 </description>
3323 </item>
3324
3325 <item>
3326 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3327 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3328 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3329 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3330 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3331 information, to find the packages that support a given piece of
3332 hardware, I refreshed my memory regarding modalias values, and decided
3333 to document the details. Here are my findings so far, also available
3334 in
3335 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3336 Debian Edu subversion repository&lt;/a&gt;:
3337
3338 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3339
3340 &lt;p&gt;This document try to explain what the different types of modalias
3341 values stands for. It is in part based on information from
3342 &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;,
3343 &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;,
3344 &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
3345 &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;.
3346
3347 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3348 this shell script:&lt;/p&gt;
3349
3350 &lt;pre&gt;
3351 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3352 &lt;/pre&gt;
3353
3354 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3355 using modinfo:&lt;/p&gt;
3356
3357 &lt;pre&gt;
3358 % /sbin/modinfo psmouse | grep alias:
3359 alias: serio:ty05pr*id*ex*
3360 alias: serio:ty01pr*id*ex*
3361 %
3362 &lt;/pre&gt;
3363
3364 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3365
3366 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3367 Bridge memory controller:&lt;/p&gt;
3368
3369 &lt;p&gt;&lt;blockquote&gt;
3370 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3371 &lt;/blockquote&gt;&lt;/p&gt;
3372
3373 &lt;p&gt;This represent these values:&lt;/p&gt;
3374
3375 &lt;pre&gt;
3376 v 00008086 (vendor)
3377 d 00002770 (device)
3378 sv 00001028 (subvendor)
3379 sd 000001AD (subdevice)
3380 bc 06 (bus class)
3381 sc 00 (bus subclass)
3382 i 00 (interface)
3383 &lt;/pre&gt;
3384
3385 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3386 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3387 0600. The 0600 class is a host bridge. Other useful bus values are
3388 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3389
3390 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3391 means.&lt;/p&gt;
3392
3393 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3394
3395 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3396 USB hub in a laptop:&lt;/p&gt;
3397
3398 &lt;p&gt;&lt;blockquote&gt;
3399 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3400 &lt;/blockquote&gt;&lt;/p&gt;
3401
3402 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3403
3404 &lt;pre&gt;
3405 v 1D6B (device vendor)
3406 p 0001 (device product)
3407 d 0206 (bcddevice)
3408 dc 09 (device class)
3409 dsc 00 (device subclass)
3410 dp 00 (device protocol)
3411 ic 09 (interface class)
3412 isc 00 (interface subclass)
3413 ip 00 (interface protocol)
3414 &lt;/pre&gt;
3415
3416 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3417 class is in the interface class section. For a simple USB web camera,
3418 these alias entries show up:&lt;/p&gt;
3419
3420 &lt;p&gt;&lt;blockquote&gt;
3421 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3422 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3423 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3424 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3425 &lt;/blockquote&gt;&lt;/p&gt;
3426
3427 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3428 camera), 0101 is audio control device and 0102 is audio streaming (aka
3429 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3430
3431 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3432
3433 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3434 receiver in a Thinkpad X40:&lt;/p&gt;
3435
3436 &lt;p&gt;&lt;blockquote&gt;
3437 acpi:IBM0071:PNP0511:
3438 &lt;/blockquote&gt;&lt;/p&gt;
3439
3440 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3441
3442 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3443
3444 &lt;p&gt;The DMI table contain lots of information about the computer case
3445 and model. This is an entry for a IBM Thinkpad X40, fetched from
3446 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3447
3448 &lt;p&gt;&lt;blockquote&gt;
3449 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3450 &lt;/blockquote&gt;&lt;/p&gt;
3451
3452 &lt;p&gt;The values present are&lt;/p&gt;
3453
3454 &lt;pre&gt;
3455 bvn IBM (BIOS vendor)
3456 bvr 1UETB6WW(1.66) (BIOS version)
3457 bd 06/15/2005 (BIOS date)
3458 svn IBM (system vendor)
3459 pn 2371H4G (product name)
3460 pvr ThinkPadX40 (product version)
3461 rvn IBM (board vendor)
3462 rn 2371H4G (board name)
3463 rvr NotAvailable (board version)
3464 cvn IBM (chassis vendor)
3465 ct 10 (chassis type)
3466 cvr NotAvailable (chassis version)
3467 &lt;/pre&gt;
3468
3469 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3470 found in the dmidecode source:&lt;/p&gt;
3471
3472 &lt;pre&gt;
3473 3 Desktop
3474 4 Low Profile Desktop
3475 5 Pizza Box
3476 6 Mini Tower
3477 7 Tower
3478 8 Portable
3479 9 Laptop
3480 10 Notebook
3481 11 Hand Held
3482 12 Docking Station
3483 13 All In One
3484 14 Sub Notebook
3485 15 Space-saving
3486 16 Lunch Box
3487 17 Main Server Chassis
3488 18 Expansion Chassis
3489 19 Sub Chassis
3490 20 Bus Expansion Chassis
3491 21 Peripheral Chassis
3492 22 RAID Chassis
3493 23 Rack Mount Chassis
3494 24 Sealed-case PC
3495 25 Multi-system
3496 26 CompactPCI
3497 27 AdvancedTCA
3498 28 Blade
3499 29 Blade Enclosing
3500 &lt;/pre&gt;
3501
3502 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3503 table. For example my home server is a tower, but the DMI modalias
3504 claim it is a desktop.&lt;/p&gt;
3505
3506 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3507
3508 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3509 test machine:&lt;/p&gt;
3510
3511 &lt;p&gt;&lt;blockquote&gt;
3512 serio:ty01pr00id00ex00
3513 &lt;/blockquote&gt;&lt;/p&gt;
3514
3515 &lt;p&gt;The values present are&lt;/p&gt;
3516
3517 &lt;pre&gt;
3518 ty 01 (type)
3519 pr 00 (prototype)
3520 id 00 (id)
3521 ex 00 (extra)
3522 &lt;/pre&gt;
3523
3524 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3525 the valid values are.&lt;/p&gt;
3526
3527 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3528
3529 &lt;p&gt;There are heaps of other modalias subtypes according to
3530 file2alias.c. There is the rest of the list from that source: amba,
3531 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3532 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3533 vmbus, x86cpu and zorro. I did not spend time documenting all of
3534 these, as they do not seem relevant for my intended use with mapping
3535 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3536
3537 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3538
3539 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3540 one can use the following shell script:&lt;/p&gt;
3541
3542 &lt;pre&gt;
3543 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3544 echo &quot;$id&quot; ; \
3545 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3546 done
3547 &lt;/pre&gt;
3548
3549 &lt;p&gt;The output can look like this (only the first few entries as the
3550 list is very long on my test machine):&lt;/p&gt;
3551
3552 &lt;pre&gt;
3553 acpi:ACPI0003:
3554 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3555 acpi:device:
3556 FATAL: Module acpi:device: not found.
3557 acpi:IBM0068:
3558 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3559 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3560 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3561 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3562 acpi:IBM0071:PNP0511:
3563 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3564 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3565 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3566 [...]
3567 &lt;/pre&gt;
3568
3569 &lt;p&gt;If you want to help implementing a system to let us propose what
3570 packages to install when new hardware is plugged into a Debian
3571 machine, please send me an email or talk to me on
3572 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3573
3574 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3575 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3576 in /sys/ with space in them.&lt;/p&gt;
3577 </description>
3578 </item>
3579
3580 <item>
3581 <title>Moved the pymissile Debian packaging to collab-maint</title>
3582 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3583 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3584 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3585 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3586 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3587 Launcher and updated the Debian package
3588 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3589 sure udev will fix the device permissions when it is plugged in. I
3590 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3591 hopefully make the package be proposed by jockey in Ubuntu when a user
3592 plug in his rocket launcher. In the process I moved the source to a
3593 git repository under collab-maint, to make it easier for any DD to
3594 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3595 is not very active, but the software still work for me even after five
3596 years of relative silence. The new git repository is not listed in
3597 the uploaded package yet, because I want to test the other changes a
3598 bit more before I upload the new version. If you want to check out
3599 the new version with a .desktop file included, visit the
3600 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3601 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3602 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3603 </description>
3604 </item>
3605
3606 <item>
3607 <title>Lets make hardware dongles easier to use in Debian</title>
3608 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3609 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3610 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3611 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3612 general, is that there is a great package management system with the
3613 ability to automatically install software packages by downloading them
3614 from the distribution mirrors, but no way to get it to automatically
3615 install the packages I need to use the hardware I plug into my
3616 machine. Even if the package to use it is easily available from the
3617 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3618 suggest to automatically install the python-nxt, nbc and t2n packages
3619 I need to talk to it. When I plug in a Yubikey, it could propose the
3620 yubikey-personalization package. The information required to do this
3621 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3622
3623 &lt;p&gt;Some years ago, I proposed to
3624 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
3625 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
3626 simple:
3627
3628 &lt;ul&gt;
3629
3630 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
3631 starting when a user log in.&lt;/li&gt;
3632
3633 &lt;li&gt;Set this program up to listen for kernel events emitted when new
3634 hardware is inserted into the computer.&lt;/li&gt;
3635
3636 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
3637 database mapping to packages, and take note of any non-installed
3638 packages.&lt;/li&gt;
3639
3640 &lt;li&gt;Show a message to the user proposing to install the discovered
3641 package, and make it easy to install it.&lt;/li&gt;
3642
3643 &lt;/ul&gt;
3644
3645 &lt;p&gt;I am not sure what the best way to implement this is, but my
3646 initial idea was to use dbus events to discover new hardware, the
3647 discover database to find packages and
3648 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
3649 packages.&lt;/p&gt;
3650
3651 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
3652 draft package is now checked into
3653 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3654 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
3655 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
3656 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3657 the relevant packages in Debian, and uploaded a new version
3658 2.2013.01.09 to unstable. I also discovered that the current
3659 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
3660 package in Debian no longer discovered any USB devices, because
3661 /proc/bus/usb/devices is no longer present. I ported it to use
3662 libusb as a fall back option to get it working. The fixed package
3663 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
3664 because of the freeze).&lt;/p&gt;
3665
3666 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
3667 desktop notification to show up (only once, the first time it is
3668 inserted):&lt;/p&gt;
3669
3670 &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;
3671
3672 &lt;p&gt;For this prototype to be really useful, some way to automatically
3673 install the proposed packages by pressing the &quot;Please install
3674 program(s)&quot; button should to be implemented.&lt;/p&gt;
3675
3676 &lt;p&gt;If this idea seem useful to you, and you want to help make it
3677 happen, please help me update the discover-data database with mappings
3678 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
3679 list the package you would like to have installed when a given
3680 hardware device is inserted into your computer, and report bugs using
3681 reportbug if it isn&#39;t. Or, if you know of a better way to provide
3682 such mapping, please let me know.&lt;/p&gt;
3683
3684 &lt;p&gt;This prototype need more work, and there are several questions that
3685 should be considered before it is ready for production use. Is dbus
3686 the correct way to detect new hardware? At the moment I look for HAL
3687 dbus events on the system bus, because that is the events I could see
3688 on my Debian Squeeze KDE desktop. Are there better events to use?
3689 How should the user be notified? Is the desktop notification
3690 mechanism the best option, or should the background daemon raise a
3691 popup instead? How should packages be installed? When should they
3692 not be installed?&lt;/p&gt;
3693
3694 &lt;p&gt;If you want to help getting such feature implemented in Debian,
3695 please send me an email. :)&lt;/p&gt;
3696 </description>
3697 </item>
3698
3699 <item>
3700 <title>New IRC channel for LEGO designers using Debian</title>
3701 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
3702 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
3703 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
3704 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
3705 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
3706 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
3707 discovered I had to build all the tools myself because none were
3708 already in Debian Squeeze. If Debian support for LEGO is something
3709 you care about, please join me on the IRC channel
3710 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
3711 irc.debian.org). There is a lot that could be done to improve the
3712 Debian support for LEGO designers. For example both CAD software
3713 and Mindstorm compilers are missing. :)&lt;/p&gt;
3714
3715 &lt;p&gt;Update 2012-01-03: A
3716 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
3717 including links to Lego related packages is now available.&lt;/p&gt;
3718 </description>
3719 </item>
3720
3721 <item>
3722 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
3723 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
3724 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
3725 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
3726 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
3727 year! I hope next year will prove to be a good year.&lt;/p&gt;
3728
3729 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
3730 decentralised &quot;currency&quot; that allow people to transfer bitcoins
3731 between each other with minimal overhead, is a very interesting
3732 experiment. And as I wrote a few days ago, the bitcoin situation in
3733 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
3734 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
3735 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
3736 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
3737 for one of the ftpmasters to approve the new bitcoin-qt package
3738 name.&lt;/p&gt;
3739
3740 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3741 team in Debian, you can easily test the package in Debian Squeeze
3742 using the following steps to get a set of working packages:&lt;/p&gt;
3743
3744 &lt;blockquote&gt;&lt;pre&gt;
3745 git clone git://git.debian.org/git/collab-maint/bitcoin
3746 cd bitcoin
3747 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3748 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3749 &lt;/pre&gt;&lt;/blockquote&gt;
3750
3751 &lt;p&gt;You might have to install some build dependencies as well. The
3752 list of commands should give you two packages, bitcoind and
3753 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3754 client will download the complete set of bitcoin &quot;blocks&quot;, which need
3755 around 5.6 GiB of data on my machine at the moment. Make sure your
3756 ~/.bitcoin/ directory have lots of spare room if you want to download
3757 all the blocks. The client will warn if the disk is getting full, so
3758 there is not really a problem if you got too little room, but you will
3759 not be able to get all the features out of the client.&lt;/p&gt;
3760
3761 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3762 activities, please send Bitcoin donations to my address
3763 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3764 </description>
3765 </item>
3766
3767 <item>
3768 <title>A word on bitcoin support in Debian</title>
3769 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
3770 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
3771 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
3772 <description>&lt;p&gt;It has been a while since I wrote about
3773 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
3774 peer-to-peer based crypto-currency, and the reason is simply that I
3775 have been busy elsewhere. But two days ago, I started looking at the
3776 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
3777 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
3778 is now maintained by a
3779 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
3780 people&lt;/a&gt;, and the grunt work had already been done by this team. We
3781 owe a huge thank you to all these team members. :)
3782 But I was sad to discover that the bitcoin client is missing in
3783 Wheezy. It is only available in Sid (and an outdated client from
3784 backports). The client had several RC bugs registered in BTS blocking
3785 it from entering testing. To try to help the team and improve the
3786 situation, I spent some time providing patches and triaging the bug
3787 reports. I also had a look at the bitcoin package available from Matt
3788 Corallo in a
3789 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
3790 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
3791 Debian package.&lt;/p&gt;
3792
3793 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
3794 IRC, I pushed several patches into the collab-maint git repository to
3795 improve the package. It now contains fixes for the RC issues (not from
3796 me, but fixed by Scott Howard), build rules for a Qt GUI client
3797 package, konqueror support for the bitcoin: URI and bash completion
3798 setup. As I work on Debian Squeeze, I also created
3799 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
3800 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
3801 it and try to integrate it into the git repository before uploading a
3802 new version to unstable.
3803
3804 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
3805 centralized control currently exercised in the monetary system. I
3806 find it completely unacceptable that the USA government is collecting
3807 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3808 that the major credit card companies can block legal money
3809 transactions to Wikileaks. But for bitcoin to succeed, more people
3810 need to use bitcoins, and more people need to accept bitcoins when
3811 they sell products and services. Improving the bitcoin support in
3812 Debian is a small step in the right direction, but not enough.
3813 Unfortunately the user experience when browsing the web and wanting to
3814 pay with bitcoin is still not very good. The bitcoin: URI is a step
3815 in the right direction, but need to work in most or every browser in
3816 use. Also the bitcoin-qt client is too heavy to fire up to do a
3817 quick transaction. I believe there are other clients available, but
3818 have not tested them.&lt;/p&gt;
3819
3820 &lt;p&gt;My
3821 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
3822 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
3823 I received 20.15 BTC so far on the address I provided in my blog two
3824 years ago, as can be
3825 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
3826 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
3827 donation. The blockexplorer service demonstrates quite well that
3828 bitcoin is not quite anonymous and untracked. :) I wonder if the
3829 number of users have gone up since then. If you use bitcoin and want
3830 to show your support of my activity, please send Bitcoin donations to
3831 the same address as last time,
3832 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3833 </description>
3834 </item>
3835
3836 <item>
3837 <title>Git repository for song book for Computer Scientists</title>
3838 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
3839 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
3840 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
3841 <description>&lt;p&gt;As I
3842 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
3843 this summer&lt;/a&gt;, I have created a Computer Science song book a few
3844 years ago, and today I finally found time to create a public
3845 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
3846 repository for the project&lt;/a&gt;.&lt;/p&gt;
3847
3848 &lt;p&gt;If you want to help out, please clone the source and submit patches
3849 to the HTML version. To generate the PDF and PostScript version,
3850 please use prince XML, or let me know about a useful free software
3851 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
3852
3853 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
3854 PostScript formats at
3855 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
3856 Science Songbook&lt;/a&gt;.&lt;/p&gt;
3857 </description>
3858 </item>
3859
3860 <item>
3861 <title>Gratulerer med 19-årsdagen, Debian!</title>
3862 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
3863 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
3864 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
3865 <description>&lt;p&gt;I dag fyller
3866 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
3867 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
3868 si gratulerer med dagen, Debian!&lt;/p&gt;
3869 </description>
3870 </item>
3871
3872 <item>
3873 <title>Song book for Computer Scientists</title>
3874 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
3875 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
3876 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
3877 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
3878 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
3879 collecting computer related songs for use at parties. The original
3880 version was written in LaTeX, but a few years ago I got help from
3881 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3882 while keeping the ability to create a nice book in PDF format. I have
3883 not had time to maintain the book for a while now, and guess I should
3884 put it up on some public version control repository where others can
3885 help me extend and update the book. If anyone is volunteering to help
3886 me with this, send me an email. Also let me know if there are songs
3887 missing in my book.&lt;/p&gt;
3888
3889 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
3890 me today that I really should let all my readers share the joys of
3891 singing out load about programming, computers and computer networks.
3892 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
3893 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
3894 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
3895 Computer Science Songbook&lt;/a&gt;.
3896 </description>
3897 </item>
3898
3899 <item>
3900 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
3901 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
3902 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
3903 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
3904 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
3905 around 1000 at the moment. To be able to get help from the vendors
3906 when something go wrong, we want to keep the firmware on the servers
3907 up to date. If the firmware isn&#39;t the latest and greatest, the
3908 vendors typically refuse to start debugging any problems until the
3909 firmware is upgraded. So before every reboot, we want to upgrade the
3910 firmware, and we would really like everyone handling servers at the
3911 university to do this themselves when they plan to reboot a machine.
3912 For that to happen we at the unix server admin group need to provide
3913 the tools to do so.&lt;/p&gt;
3914
3915 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
3916 fetch and install the latest firmware for the servers we got. Most of
3917 our hardware are from Dell and HP, so I have focused on these servers
3918 so far. This blog post is about the Dell part.&lt;/P&gt;
3919
3920 &lt;p&gt;On the Dell FTP site I was lucky enough to find
3921 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
3922 with firmware information for all 11th generation servers, listing
3923 which firmware should be used on a given model and where on the FTP
3924 site I can find it. Using a simple perl XML parser I can then
3925 download the shell scripts Dell provides to do firmware upgrades from
3926 within Linux and reboot when all the firmware is primed and ready to
3927 be activated on the first reboot.&lt;/p&gt;
3928
3929 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
3930 Are there anyone working on similar tools for firmware upgrading all
3931 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
3932
3933 &lt;p&gt;&lt;pre&gt;
3934 #!/usr/bin/perl
3935 use strict;
3936 use warnings;
3937 use File::Temp qw(tempdir);
3938 BEGIN {
3939 # Install needed RHEL packages if missing
3940 my %rhelmodules = (
3941 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
3942 );
3943 for my $module (keys %rhelmodules) {
3944 eval &quot;use $module;&quot;;
3945 if ($@) {
3946 my $pkg = $rhelmodules{$module};
3947 system(&quot;yum install -y $pkg&quot;);
3948 eval &quot;use $module;&quot;;
3949 }
3950 }
3951 }
3952 my $errorsto = &#39;pere@hungry.com&#39;;
3953
3954 upgrade_dell();
3955
3956 exit 0;
3957
3958 sub run_firmware_script {
3959 my ($opts, $script) = @_;
3960 unless ($script) {
3961 print STDERR &quot;fail: missing script name\n&quot;;
3962 exit 1
3963 }
3964 print STDERR &quot;Running $script\n\n&quot;;
3965
3966 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
3967 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
3968 } else {
3969 print STDERR &quot;fail: firmware script returned error\n&quot;;
3970 }
3971 }
3972
3973 sub run_firmware_scripts {
3974 my ($opts, @dirs) = @_;
3975 # Run firmware packages
3976 for my $dir (@dirs) {
3977 print STDERR &quot;info: Running scripts in $dir\n&quot;;
3978 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
3979 while (my $s = readdir $dh) {
3980 next if $s =~ m/^\.\.?/;
3981 run_firmware_script($opts, &quot;$dir/$s&quot;);
3982 }
3983 closedir $dh;
3984 }
3985 }
3986
3987 sub download {
3988 my $url = shift;
3989 print STDERR &quot;info: Downloading $url\n&quot;;
3990 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
3991 }
3992
3993 sub upgrade_dell {
3994 my @dirs;
3995 my $product = `dmidecode -s system-product-name`;
3996 chomp $product;
3997
3998 if ($product =~ m/PowerEdge/) {
3999
4000 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4001 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4002
4003 my $tmpdir = tempdir(
4004 CLEANUP =&gt; 1
4005 );
4006 chdir($tmpdir);
4007 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4008 system(&#39;gunzip Catalog.xml.gz&#39;);
4009 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4010 # -q is quiet, disabling interactivity and reducing console output
4011 my $fwopts = &quot;-q&quot;;
4012 if (@paths) {
4013 for my $url (@paths) {
4014 fetch_dell_fw($url);
4015 }
4016 run_firmware_scripts($fwopts, $tmpdir);
4017 } else {
4018 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4019 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4020 }
4021 chdir(&#39;/&#39;);
4022 } else {
4023 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4024 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4025 }
4026 }
4027
4028 sub fetch_dell_fw {
4029 my $path = shift;
4030 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4031 download($url);
4032 }
4033
4034 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4035 # firmware packages to download from Dell. Only work for Linux
4036 # machines and 11th generation Dell servers.
4037 sub fetch_dell_fw_list {
4038 my $filename = shift;
4039
4040 my $product = `dmidecode -s system-product-name`;
4041 chomp $product;
4042 my ($mybrand, $mymodel) = split(/\s+/, $product);
4043
4044 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4045
4046 my $xml = XMLin($filename);
4047 my @paths;
4048 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4049 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4050 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4051 my $oscode;
4052 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4053 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4054 } else {
4055 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4056 }
4057 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4058 {
4059 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4060 }
4061 }
4062 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4063 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4064
4065 # Drop application packages, only firmware and BIOS
4066 next if &#39;APAC&#39; eq $componenttype;
4067
4068 my $cpath = $component-&gt;{path};
4069 for my $path (@paths) {
4070 if ($cpath =~ m%/$path$%) {
4071 push(@paths, $cpath);
4072 }
4073 }
4074 }
4075 return @paths;
4076 }
4077 &lt;/pre&gt;
4078
4079 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4080 it could work on other platforms with some tweaking. Anyone know a
4081 index like Catalog.xml is available from HP for HP servers? At the
4082 moment I maintain a similar list manually and it is quickly getting
4083 outdated.&lt;/p&gt;
4084 </description>
4085 </item>
4086
4087 <item>
4088 <title>How is booting into runlevel 1 different from single user boots?</title>
4089 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4090 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4091 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4092 <description>&lt;p&gt;Wouter Verhelst have some
4093 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4094 comments and opinions&lt;/a&gt; on my blog post on
4095 &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
4096 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4097 &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
4098 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4099 small piece of his comment now, and though it best to address the
4100 misunderstanding he bring forward:&lt;/p&gt;
4101
4102 &lt;p&gt;&lt;blockquote&gt;
4103 Currently, a system admin has four options: [...] boot to a
4104 single-user system (by adding &#39;single&#39; to the kernel command line;
4105 this runs rcS and rc1 scripts)
4106 &lt;/blockquote&gt;&lt;/p&gt;
4107
4108 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4109 and booting into runlevel 1 is the same. I am not surprised he
4110 believe this, because it would make sense and is a quite sensible
4111 thing to believe. But because the boot in Debian is slightly broken,
4112 runlevel 1 do not work properly and it isn&#39;t the same as single user
4113 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4114 hard to explain.&lt;/p&gt;
4115
4116 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4117 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4118 executed in single user mode is sulogin. Single user mode is a boot
4119 state &quot;between&quot; the runlevels, and when booting into single user mode,
4120 only the scripts in /etc/rcS.d/ are executed before the init process
4121 enters the single user state. When switching to runlevel 1, the state
4122 is in fact not ending in runlevel 1, but it passes through runlevel 1
4123 and end up in the single user mode (see /etc/rc1.d/S03single, which
4124 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4125 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4126 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4127 mode).&lt;/p&gt;
4128
4129 &lt;p&gt;This summary might make it clearer. When booting for the first
4130 time into single user mode, the following commands are executed:
4131 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4132 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4133 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4134 trying to continue after visiting single user mode. Not all services
4135 are started again as they should, causing the machine to end up in an
4136 unpredicatble state. This is why Debian admins recommend rebooting
4137 after visiting single user mode.&lt;/p&gt;
4138
4139 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4140 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4141 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4142 stopped when passing through the scripts in /etc/rc1.d/, and not
4143 started again when switching away from runlevel 1 to the runlevels
4144 2-5. I believe the problem is best fixed by moving all the scripts
4145 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4146 functioning single user mode during boot.&lt;/p&gt;
4147
4148 &lt;p&gt;I have spent several years investigating the Debian boot system,
4149 and discovered this problem a few years ago. I suspect it originates
4150 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4151 </description>
4152 </item>
4153
4154 <item>
4155 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4156 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4157 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4158 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4159 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4160 are started from /etc/rcS.d/. In fact, there is a bite more of them
4161 than make sense, and this causes a few problems. What kind of
4162 problems, you might ask. There are at least two problems. The first
4163 is that it is not possible to recover a machine after switching to
4164 runlevel 1. One need to actually reboot to get the machine back to
4165 the expected state. The other is that single user boot will sometimes
4166 run into problems because some of the subsystems are activated before
4167 the root login is presented, causing problems when trying to recover a
4168 machine from a problem in that subsystem. A minor additional point is
4169 that moving more scripts out of rcS.d/ and into the other rc#.d/
4170 directories will increase the amount of scripts that can run in
4171 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4172
4173 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4174 scripts that _have_ to execute before the root login prompt is
4175 presented during a single user boot should go there. Everything else
4176 should go into the numeric runlevels. This means things like
4177 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4178 the numeric runlevels. Today in Debian, there are around 115 init.d
4179 scripts that are started from rcS.d/, and most of them should be moved
4180 out. Do your package have one of them? Please help us make single
4181 user and runlevel 1 better by moving it.&lt;/p&gt;
4182
4183 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4184 etc. should still be started from rcS.d/, but there is for example no
4185 need to have the network enabled before the single user login prompt
4186 is presented.&lt;/p&gt;
4187
4188 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4189 Debian systems working while scripts migrate and during upgrades, the
4190 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4191 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4192 and the next ones can only be moved when their dependencies have been
4193 moved first. This migration must be done sequentially while we ensure
4194 that the package system upgrade packages in the right order to keep
4195 the system state correct. This will require some coordination when it
4196 comes to network related packages, but most of the packages with
4197 scripts that should migrate do not have anything in rcS.d/ depending
4198 on them. Some packages have already been updated, like the sudo
4199 package, while others are still left to do. I wish I had time to work
4200 on this myself, but real live constrains make it unlikely that I will
4201 find time to push this forward.&lt;/p&gt;
4202 </description>
4203 </item>
4204
4205 <item>
4206 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4207 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4209 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4210 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4211 mentioned the issues I believe should be improved in Debian for its
4212 desktop to be useful for more people. The use case for this is my
4213 parents, which are currently running Kubuntu which solve the
4214 issues.&lt;/p&gt;
4215
4216 &lt;p&gt;I suspect these four missing features are not very hard to
4217 implement. After all, they are present in Ubuntu, so if we wanted to
4218 do this in Debian we would have a source.&lt;/p&gt;
4219
4220 &lt;ol&gt;
4221
4222 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4223 are new packages available for upgrades, a icon in the KDE status bar
4224 indicate this, and clicking on it will activate the simple upgrade
4225 tool to handle it. I have no problem guiding both of my parents
4226 through the process over the phone. If a kernel reboot is required,
4227 this too is indicated by the status bars and the upgrade tool. Last
4228 time I checked, nothing with the same features was working in KDE in
4229 Debian.&lt;/li&gt;
4230
4231 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4232 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4233 currently have a handler for, it will ask the user if the system
4234 should search for a package that would add support for this MIME type,
4235 and if the user say yes, the APT sources will be searched for packages
4236 advertising the MIME type in their control file (visible in the
4237 Packages file in the APT archive). If one or more packages are found,
4238 it is a simple click of the mouse to add support for the missing mime
4239 type. If the package require the user to accept some non-free
4240 license, this is explained to the user. The entire process make it
4241 more clear to the user why something do not work in the browser, and
4242 make the chances higher for the user to blame the web page authors and
4243 not the browser for any missing features.&lt;/li&gt;
4244
4245 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4246 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4247 it is not supporting, a dialog pop up asking the user if the system
4248 should search for a package that would add support for it. This
4249 happen with things like MP3, Windows Media or H.264. The selection
4250 and installation procedure is very similar to the Firefox browser
4251 plugin handling. This is as far as I know implemented using a
4252 gstreamer hook. The end result is that the user easily get access to
4253 the codecs that are present from the APT archives available, while
4254 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4255
4256 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4257 displaying a text/plain file in my Debian browser, it will propose to
4258 start emacs to show it. If I remember correctly, when doing the same
4259 in Kunbutu it show the file as a text file in the browser. At least I
4260 know Opera will show text files within the browser. I much prefer the
4261 latter behaviour.&lt;/li&gt;
4262
4263 &lt;/ol&gt;
4264
4265 &lt;p&gt;There are other nice features as well, like the simplified suite
4266 upgrader, but given that I am the one mostly doing the dist-upgrade,
4267 it do not matter much.&lt;/p&gt;
4268
4269 &lt;p&gt;I really hope we could get these features in place for the next
4270 Debian release. It would require the coordinated effort of several
4271 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4272 </description>
4273 </item>
4274
4275 <item>
4276 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4277 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4278 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4279 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4280 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4281 site is build on Debian/Squeeze, and this platform was chosen because
4282 I am most familiar with Debian (being a Debian Developer for around 10
4283 years) because it is the latest stable Debian release which should get
4284 security support for a few years.&lt;/p&gt;
4285
4286 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4287 that are missing in Debian at the moment. It would be great if these
4288 modules were added to the Debian archive, allowing anyone to set up
4289 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4290 in their own country using only Debian packages. The list of modules
4291 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4292 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4293 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4294 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4295 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4296 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4297 easier in the future.&lt;/p&gt;
4298
4299 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4300 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4301 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4302 with the responsibility of tracking security problems, which I really
4303 do not have time for.&lt;/p&gt;
4304 </description>
4305 </item>
4306
4307 <item>
4308 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4309 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4310 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4311 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4312 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4313 posts have been in Norwegian the last few weeks, so here is a short
4314 update in English.&lt;/p&gt;
4315
4316 &lt;p&gt;The kids still keep me too busy to get much free software work
4317 done, but I did manage to organise a project to get a Norwegian port
4318 of the British service
4319 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4320 and it has been running for a month now. The entire project has been
4321 organised by me and two others. Around Christmas we gathered sponsors
4322 to fund the development work. In January I drafted a contract with
4323 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4324 and in February the development took place. Most of it involved
4325 converting the source to use GPS coordinates instead of British
4326 easting/northing, and the resulting code should be a lot easier to get
4327 running in any country by now. The Norwegian
4328 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4329 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4330 source and the source for administrative borders in Norway, and
4331 support for this had to be added/fixed.&lt;/p&gt;
4332
4333 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4334 polishing the system before we announced it March 7th. The system is
4335 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4336 problem reports in a few weeks. Soon we hope to announce the Android
4337 and iPhone versions making it even easier to report problems with the
4338 public infrastructure.&lt;/p&gt;
4339
4340 &lt;p&gt;Perhaps something to consider for those of you in countries without
4341 such service?&lt;/p&gt;
4342 </description>
4343 </item>
4344
4345 <item>
4346 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4347 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4348 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4349 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4350 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4351 issues here at my work with the University of Oslo. My idea is that
4352 it should be possible to use the information about security issues
4353 available on the Internet, and check our locally
4354 maintained/distributed software against this information. It should
4355 allow us to verify that no known security issues are forgotten. The
4356 CVE database listing vulnerabilities seem like a great central point,
4357 and by using the package lists from Debian mapped to CVEs provided by
4358 the testing security team, I believed it should be possible to figure
4359 out which security holes were present in our free software
4360 collection.&lt;/p&gt;
4361
4362 &lt;p&gt;After reading up on the topic, it became obvious that the first
4363 building block is to be able to name software packages in a unique and
4364 consistent way across data sources. I considered several ways to do
4365 this, for example coming up with my own naming scheme like using URLs
4366 to project home pages or URLs to the Freshmeat entries, or using some
4367 existing naming scheme. And it seem like I am not the first one to
4368 come across this problem, as MITRE already proposed and implemented a
4369 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4370 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4371 software, hardware and other platform components. The CPE ids are
4372 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4373 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4374 issues for any CPE name. With this in place, all I need to do is to
4375 locate the CPE id for the software packages we use at the university.
4376 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4377 NVD entry if a CVE for the package exist).&lt;/p&gt;
4378
4379 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4380 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4381 check out, one could look up
4382 &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
4383 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4384 The most recent one is
4385 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4386 and at the bottom of the NVD page for this vulnerability the complete
4387 list of affected versions is provided.&lt;/p&gt;
4388
4389 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4390 for offline processing of issues. Using this dump, I&#39;ve written a
4391 small script taking a list of CPEs as input and list all CVEs
4392 affecting the packages represented by these CPEs. One give it CPEs
4393 with version numbers as specified above and get a list of open
4394 security issues out.&lt;/p&gt;
4395
4396 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4397 information need to be high. For that to happen, I believe as many as
4398 possible need to use and contribute to the NVD database. I notice
4399 RHEL is providing
4400 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4401 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4402 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4403
4404 &lt;p&gt;To get an idea about the quality for free software, I spent some
4405 time making it possible to compare the CVE database from Debian with
4406 the CVE database in NVD. The result look fairly good, but there are
4407 some inconsistencies in NVD (same software package having several
4408 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4409 Debian believe are affected by a CVE). Hope to find time to improve
4410 the quality of NVD, but that require being able to get in touch with
4411 someone maintaining it. So far my three emails with questions and
4412 corrections have not seen any reply, but I hope contact can be
4413 established soon.&lt;/p&gt;
4414
4415 &lt;p&gt;An interesting application for CPEs is cross platform package
4416 mapping. It would be useful to know which packages in for example
4417 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4418 this would be trivial if all linux distributions provided CPE entries
4419 for their packages.&lt;/p&gt;
4420 </description>
4421 </item>
4422
4423 <item>
4424 <title>Which module is loaded for a given PCI and USB device?</title>
4425 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4426 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4427 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4428 <description>&lt;p&gt;In the
4429 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4430 package in Debian, there is a script to report useful information
4431 about the running hardware for use when people report missing
4432 information. One part of this script that I find very useful when
4433 debugging hardware problems, is the part mapping loaded kernel module
4434 to the PCI device it claims. It allow me to quickly see if the kernel
4435 module I expect is driving the hardware I am struggling with. To see
4436 the output, make sure discover-data is installed and run
4437 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4438 one of my machines like this:&lt;/p&gt;
4439
4440 &lt;pre&gt;
4441 loaded modules:
4442 10de:03eb i2c_nforce2
4443 10de:03f1 ohci_hcd
4444 10de:03f2 ehci_hcd
4445 10de:03f0 snd_hda_intel
4446 10de:03ec pata_amd
4447 10de:03f6 sata_nv
4448 1022:1103 k8temp
4449 109e:036e bttv
4450 109e:0878 snd_bt87x
4451 11ab:4364 sky2
4452 &lt;/pre&gt;
4453
4454 &lt;p&gt;The code in question look like this, slightly modified for
4455 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4456
4457 &lt;pre&gt;
4458 if [ -d /sys/bus/pci/devices/ ] ; then
4459 echo loaded pci modules:
4460 (
4461 cd /sys/bus/pci/devices/
4462 for address in * ; do
4463 if [ -d &quot;$address/driver/module&quot; ] ; then
4464 module=`cd $address/driver/module ; pwd -P | xargs basename`
4465 if grep -q &quot;^$module &quot; /proc/modules ; then
4466 address=$(echo $address |sed s/0000://)
4467 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4468 echo &quot;$id $module&quot;
4469 fi
4470 fi
4471 done
4472 )
4473 echo
4474 fi
4475 &lt;/pre&gt;
4476
4477 &lt;p&gt;Similar code could be used to extract USB device module
4478 mappings:&lt;/p&gt;
4479
4480 &lt;pre&gt;
4481 if [ -d /sys/bus/usb/devices/ ] ; then
4482 echo loaded usb modules:
4483 (
4484 cd /sys/bus/usb/devices/
4485 for address in * ; do
4486 if [ -d &quot;$address/driver/module&quot; ] ; then
4487 module=`cd $address/driver/module ; pwd -P | xargs basename`
4488 if grep -q &quot;^$module &quot; /proc/modules ; then
4489 address=$(echo $address |sed s/0000://)
4490 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4491 if [ &quot;$id&quot; ] ; then
4492 echo &quot;$id $module&quot;
4493 fi
4494 fi
4495 fi
4496 done
4497 )
4498 echo
4499 fi
4500 &lt;/pre&gt;
4501
4502 &lt;p&gt;This might perhaps be something to include in other tools as
4503 well.&lt;/p&gt;
4504 </description>
4505 </item>
4506
4507 <item>
4508 <title>How to test if a laptop is working with Linux</title>
4509 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4510 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4511 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4512 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4513 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4514 batch of computers will work with Linux. Every year for the last few
4515 years the university have organised shared bid of a few thousand
4516 computers, and this year HP won the bid. Two different desktops and
4517 five different laptops are on the list this year. We in the UNIX
4518 group want to know which one of these computers work well with RHEL
4519 and Ubuntu, the two Linux distributions we currently handle at the
4520 university.&lt;/p&gt;
4521
4522 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4523 perhaps inspire others to test hardware as well. To test, I PXE
4524 install the OS version of choice, and log in as my normal user and run
4525 a few applications and plug in selected pieces of hardware. When
4526 something fail, I make a note about this in the test matrix and move
4527 on. If I have some spare time I try to report the bug to the OS
4528 vendor, but as I only have the machines for a short time, I rarely
4529 have the time to do this for all the problems I find.&lt;/p&gt;
4530
4531 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4532 I perform on a new model.&lt;/p&gt;
4533
4534 &lt;ul&gt;
4535
4536 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4537 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4538 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4539
4540 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4541 installation, X.org is working.&lt;/li&gt;
4542
4543 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4544 package mesa-utils on Ubuntu) and writing down the frames per second
4545 reported by the program.&lt;/li&gt;
4546
4547 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4548 logging in, and if I can hear this the test is successful. If there
4549 are several audio exits on the machine, I try them all and check if
4550 the Gnome/KDE audio mixer can control where to send the sound. I
4551 normally test this by playing
4552 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4553 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4554
4555 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4556 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4557
4558 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4559 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4560
4561 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4562 picture from the v4l device show up.&lt;/li&gt;
4563
4564 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4565 any bluetooth devices are discovered. In my office, I normally see a
4566 few.&lt;/li&gt;
4567
4568 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4569 memory modules lying around, and stick them in and see if Gnome/KDE
4570 notice this.&lt;/li&gt;
4571
4572 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4573 special button work, and if the laptop continue to work after
4574 resume.&lt;/li&gt;
4575
4576 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4577 adjusting background light, switching on/off external video output,
4578 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4579 laptop to laptop, so I just write down which are working and which are
4580 not.&lt;/li&gt;
4581
4582 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4583 acceleration sensors etc. I rarely test these, as I do not know how
4584 to quickly test if they are working or not, so I only document their
4585 existence.&lt;/li&gt;
4586
4587 &lt;/ul&gt;
4588
4589 &lt;p&gt;By now I suspect you are really curious what the test results are
4590 for the HP machines I am testing. I&#39;m not done yet, so I will report
4591 the test results later. For now I can report that HP 8100 Elite work
4592 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4593 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4594 can see, I have most machines left to test. One interesting
4595 observation is that Ubuntu Lucid has almost twice the frame rate than
4596 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4597 </description>
4598 </item>
4599
4600 <item>
4601 <title>Some thoughts on BitCoins</title>
4602 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4603 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4604 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4605 <description>&lt;p&gt;As I continue to explore
4606 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4607 what properties the system have, and how it will be affected by laws
4608 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4609
4610 &lt;p&gt;One interesting thing to note is that since the transactions are
4611 verified using a peer to peer network, all details about a transaction
4612 is known to everyone. This means that if a BitCoin address has been
4613 published like I did with mine in my initial post about BitCoin, it is
4614 possible for everyone to see how many BitCoins have been transfered to
4615 that address. There is even a web service to look at the details for
4616 all transactions. There I can see that my address
4617 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4618 have received 16.06 Bitcoin, the
4619 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4620 address of Simon Phipps have received 181.97 BitCoin and the address
4621 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4622 of EFF have received 2447.38 BitCoins so far. Thank you to each and
4623 every one of you that donated bitcoins to support my activity. The
4624 fact that anyone can see how much money was transfered to a given
4625 address make it more obvious why the BitCoin community recommend to
4626 generate and hand out a new address for each transaction. I&#39;m told
4627 there is no way to track which addresses belong to a given person or
4628 organisation without the person or organisation revealing it
4629 themselves, as Simon, EFF and I have done.&lt;/p&gt;
4630
4631 &lt;p&gt;In Norway, and in most other countries, there are laws and
4632 regulations limiting how much money one can transfer across the border
4633 without declaring it. There are money laundering, tax and accounting
4634 laws and regulations I would expect to apply to the use of BitCoin.
4635 If the Skolelinux foundation
4636 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
4637 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
4638 normal bank transfers like EFF is doing, how should this be accounted?
4639 Given that it is impossible to know if money can cross the border or
4640 not, should everything or nothing be declared? What exchange rate
4641 should be used when calculating taxes? Would receivers have to pay
4642 income tax if the foundation were to pay Skolelinux contributors in
4643 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
4644
4645 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
4646 accepted by a lot of users. It must be possible to get easy access to
4647 the currency (as a wage or using currency exchanges), and it must be
4648 easy to spend it. At the moment BitCoin seem fairly easy to get
4649 access to, but there are very few places to spend it. I am not really
4650 a regular user of any of the vendor types currently accepting BitCoin,
4651 so I wonder when my kind of shop would start accepting BitCoins. I
4652 would like to buy electronics, travels and subway tickets, not herbs
4653 and books. :) The currency is young, and this will improve over time
4654 if it become popular, but I suspect regular banks will start to lobby
4655 to get BitCoin declared illegal if it become popular. I&#39;m sure they
4656 will claim it is helping fund terrorism and money laundering (which
4657 probably would be true, as is any currency in existence), but I
4658 believe the problems should be solved elsewhere and not by blaming
4659 currencies.&lt;/p&gt;
4660
4661 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
4662 CPU intensive process that depend on a bit of luck as well (as one is
4663 competing against all the other miners currently spending CPU cycles
4664 to see which one get the next lump of cash). The &quot;winner&quot; get 50
4665 BitCoin when this happen. Yesterday I came across the obvious way to
4666 join forces to increase ones changes of getting at least some coins,
4667 by coordinating the work on mining BitCoins across several machines
4668 and people, and sharing the result if one is lucky and get the 50
4669 BitCoins. Check out
4670 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
4671 if this sounds interesting. I have not had time to try to set up a
4672 machine to participate there yet, but have seen that running on ones
4673 own for a few days have not yield any BitCoins througth mining
4674 yet.&lt;/p&gt;
4675
4676 &lt;p&gt;Update 2010-12-15: Found an &lt;a
4677 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
4678 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
4679 it was interesting to read. The arguments presented seem to be
4680 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
4681 </description>
4682 </item>
4683
4684 <item>
4685 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
4686 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
4687 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
4688 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
4689 <description>&lt;p&gt;With this weeks lawless
4690 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
4691 attacks&lt;/a&gt; on Wikileak and
4692 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
4693 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
4694 not be trusted to handle money transactions.
4695 A blog post from
4696 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
4697 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
4698 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
4699 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
4700 some help from my friend to get it all running, and he even handed me
4701 some bitcoins to get started. I even donated a few bitcoins to Simon
4702 for helping me remember BitCoin.&lt;/p&gt;
4703
4704 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
4705 crypto-currency, decentralised and handled using peer-to-peer
4706 networks. It allows anonymous transactions and prohibits central
4707 control over the transactions, making it impossible for governments
4708 and companies alike to block donations and other transactions. The
4709 source is free software, and while the key dependency wxWidgets 2.9
4710 for the graphical user interface is missing in Debian, the command
4711 line client builds just fine. Hopefully Jonas
4712 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
4713 Debian&lt;/a&gt; soon.&lt;/p&gt;
4714
4715 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
4716 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
4717 bitcoins&lt;/a&gt; when selling services and goods, and there are even
4718 currency &quot;stock&quot; markets where the exchange rate is decided. There
4719 are not many users so far, but the concept seems promising. If you
4720 want to get started and lack a friend with any bitcoins to spare,
4721 you can even get
4722 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
4723 bitcoin at the time of writing). Use
4724 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
4725 on the current exchange rates.&lt;/p&gt;
4726
4727 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
4728 machines. If you want to support my activity, please send Bitcoin
4729 donations to the address
4730 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
4731 </description>
4732 </item>
4733
4734 <item>
4735 <title>Why isn&#39;t Debian Edu using VLC?</title>
4736 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
4737 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
4738 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
4739 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4740 presented, and the winner among the multimedia player were VLC.
4741 Personally, I like VLC, and it is my player of choice when I first try
4742 to play a video file or stream. Only if VLC fail will I drag out
4743 gmplayer to see if it can do better. The reason is mostly the failure
4744 model and trust. When VLC fail, it normally pop up a error message
4745 reporting the problem. When mplayer fail, it normally segfault or
4746 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4747
4748 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4749 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4750 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4751 plugin to play web videos seamlessly, and the VLC browser plugin is
4752 not very good. For example, it lack in-line control buttons, so there
4753 is no way for the user to pause the video. Also, when I
4754 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
4755 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
4756 failed on several video pages where mplayer based plugins worked. If
4757 the browser plugin for VLC was as good as the gecko-mediaplayer
4758 package (which uses mplayer), we would switch.&lt;/P&gt;
4759
4760 &lt;p&gt;While VLC is a good player, its user interface is slightly
4761 annoying. The most annoying feature is its inconsistent use of
4762 keyboard shortcuts. When the player is in full screen mode, its
4763 shortcuts are different from when it is playing the video in a window.
4764 For example, space only work as pause when in full screen mode. I
4765 wish it had consisten shortcuts and that space also would work when in
4766 window mode. Another nice shortcut in gmplayer is [enter] to restart
4767 the current video. It is very nice when playing short videos from the
4768 web and want to restart it when new people arrive to have a look at
4769 what is going on.&lt;/p&gt;
4770 </description>
4771 </item>
4772
4773 <item>
4774 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
4775 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
4776 <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>
4777 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
4778 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
4779 upgrade testing of the
4780 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4781 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
4782 This seem like a very good idea, so I adjusted by test scripts and
4783 can now present the updated result from today:&lt;/p&gt;
4784
4785 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4786
4787 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4788
4789 &lt;blockquote&gt;&lt;p&gt;
4790 apache2.2-bin
4791 aptdaemon
4792 baobab
4793 binfmt-support
4794 browser-plugin-gnash
4795 cheese-common
4796 cli-common
4797 cups-pk-helper
4798 dmz-cursor-theme
4799 empathy
4800 empathy-common
4801 freedesktop-sound-theme
4802 freeglut3
4803 gconf-defaults-service
4804 gdm-themes
4805 gedit-plugins
4806 geoclue
4807 geoclue-hostip
4808 geoclue-localnet
4809 geoclue-manual
4810 geoclue-yahoo
4811 gnash
4812 gnash-common
4813 gnome
4814 gnome-backgrounds
4815 gnome-cards-data
4816 gnome-codec-install
4817 gnome-core
4818 gnome-desktop-environment
4819 gnome-disk-utility
4820 gnome-screenshot
4821 gnome-search-tool
4822 gnome-session-canberra
4823 gnome-system-log
4824 gnome-themes-extras
4825 gnome-themes-more
4826 gnome-user-share
4827 gstreamer0.10-fluendo-mp3
4828 gstreamer0.10-tools
4829 gtk2-engines
4830 gtk2-engines-pixbuf
4831 gtk2-engines-smooth
4832 hamster-applet
4833 libapache2-mod-dnssd
4834 libapr1
4835 libaprutil1
4836 libaprutil1-dbd-sqlite3
4837 libaprutil1-ldap
4838 libart2.0-cil
4839 libboost-date-time1.42.0
4840 libboost-python1.42.0
4841 libboost-thread1.42.0
4842 libchamplain-0.4-0
4843 libchamplain-gtk-0.4-0
4844 libcheese-gtk18
4845 libclutter-gtk-0.10-0
4846 libcryptui0
4847 libdiscid0
4848 libelf1
4849 libepc-1.0-2
4850 libepc-common
4851 libepc-ui-1.0-2
4852 libfreerdp-plugins-standard
4853 libfreerdp0
4854 libgconf2.0-cil
4855 libgdata-common
4856 libgdata7
4857 libgdu-gtk0
4858 libgee2
4859 libgeoclue0
4860 libgexiv2-0
4861 libgif4
4862 libglade2.0-cil
4863 libglib2.0-cil
4864 libgmime2.4-cil
4865 libgnome-vfs2.0-cil
4866 libgnome2.24-cil
4867 libgnomepanel2.24-cil
4868 libgpod-common
4869 libgpod4
4870 libgtk2.0-cil
4871 libgtkglext1
4872 libgtksourceview2.0-common
4873 libmono-addins-gui0.2-cil
4874 libmono-addins0.2-cil
4875 libmono-cairo2.0-cil
4876 libmono-corlib2.0-cil
4877 libmono-i18n-west2.0-cil
4878 libmono-posix2.0-cil
4879 libmono-security2.0-cil
4880 libmono-sharpzip2.84-cil
4881 libmono-system2.0-cil
4882 libmtp8
4883 libmusicbrainz3-6
4884 libndesk-dbus-glib1.0-cil
4885 libndesk-dbus1.0-cil
4886 libopal3.6.8
4887 libpolkit-gtk-1-0
4888 libpt2.6.7
4889 libpython2.6
4890 librpm1
4891 librpmio1
4892 libsdl1.2debian
4893 libsrtp0
4894 libssh-4
4895 libtelepathy-farsight0
4896 libtelepathy-glib0
4897 libtidy-0.99-0
4898 media-player-info
4899 mesa-utils
4900 mono-2.0-gac
4901 mono-gac
4902 mono-runtime
4903 nautilus-sendto
4904 nautilus-sendto-empathy
4905 p7zip-full
4906 pkg-config
4907 python-aptdaemon
4908 python-aptdaemon-gtk
4909 python-axiom
4910 python-beautifulsoup
4911 python-bugbuddy
4912 python-clientform
4913 python-coherence
4914 python-configobj
4915 python-crypto
4916 python-cupshelpers
4917 python-elementtree
4918 python-epsilon
4919 python-evolution
4920 python-feedparser
4921 python-gdata
4922 python-gdbm
4923 python-gst0.10
4924 python-gtkglext1
4925 python-gtksourceview2
4926 python-httplib2
4927 python-louie
4928 python-mako
4929 python-markupsafe
4930 python-mechanize
4931 python-nevow
4932 python-notify
4933 python-opengl
4934 python-openssl
4935 python-pam
4936 python-pkg-resources
4937 python-pyasn1
4938 python-pysqlite2
4939 python-rdflib
4940 python-serial
4941 python-tagpy
4942 python-twisted-bin
4943 python-twisted-conch
4944 python-twisted-core
4945 python-twisted-web
4946 python-utidylib
4947 python-webkit
4948 python-xdg
4949 python-zope.interface
4950 remmina
4951 remmina-plugin-data
4952 remmina-plugin-rdp
4953 remmina-plugin-vnc
4954 rhythmbox-plugin-cdrecorder
4955 rhythmbox-plugins
4956 rpm-common
4957 rpm2cpio
4958 seahorse-plugins
4959 shotwell
4960 software-center
4961 system-config-printer-udev
4962 telepathy-gabble
4963 telepathy-mission-control-5
4964 telepathy-salut
4965 tomboy
4966 totem
4967 totem-coherence
4968 totem-mozilla
4969 totem-plugins
4970 transmission-common
4971 xdg-user-dirs
4972 xdg-user-dirs-gtk
4973 xserver-xephyr
4974 &lt;/p&gt;&lt;/blockquote&gt;
4975
4976 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4977
4978 &lt;blockquote&gt;&lt;p&gt;
4979 cheese
4980 ekiga
4981 eog
4982 epiphany-extensions
4983 evolution-exchange
4984 fast-user-switch-applet
4985 file-roller
4986 gcalctool
4987 gconf-editor
4988 gdm
4989 gedit
4990 gedit-common
4991 gnome-games
4992 gnome-games-data
4993 gnome-nettool
4994 gnome-system-tools
4995 gnome-themes
4996 gnuchess
4997 gucharmap
4998 guile-1.8-libs
4999 libavahi-ui0
5000 libdmx1
5001 libgalago3
5002 libgtk-vnc-1.0-0
5003 libgtksourceview2.0-0
5004 liblircclient0
5005 libsdl1.2debian-alsa
5006 libspeexdsp1
5007 libsvga1
5008 rhythmbox
5009 seahorse
5010 sound-juicer
5011 system-config-printer
5012 totem-common
5013 transmission-gtk
5014 vinagre
5015 vino
5016 &lt;/p&gt;&lt;/blockquote&gt;
5017
5018 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5019
5020 &lt;blockquote&gt;&lt;p&gt;
5021 gstreamer0.10-gnomevfs
5022 &lt;/p&gt;&lt;/blockquote&gt;
5023
5024 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5025
5026 &lt;blockquote&gt;&lt;p&gt;
5027 [nothing]
5028 &lt;/p&gt;&lt;/blockquote&gt;
5029
5030 &lt;p&gt;This is for KDE:&lt;/p&gt;
5031
5032 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5033
5034 &lt;blockquote&gt;&lt;p&gt;
5035 ksmserver
5036 &lt;/p&gt;&lt;/blockquote&gt;
5037
5038 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5039
5040 &lt;blockquote&gt;&lt;p&gt;
5041 kwin
5042 network-manager-kde
5043 &lt;/p&gt;&lt;/blockquote&gt;
5044
5045 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5046
5047 &lt;blockquote&gt;&lt;p&gt;
5048 arts
5049 dolphin
5050 freespacenotifier
5051 google-gadgets-gst
5052 google-gadgets-xul
5053 kappfinder
5054 kcalc
5055 kcharselect
5056 kde-core
5057 kde-plasma-desktop
5058 kde-standard
5059 kde-window-manager
5060 kdeartwork
5061 kdeartwork-emoticons
5062 kdeartwork-style
5063 kdeartwork-theme-icon
5064 kdebase
5065 kdebase-apps
5066 kdebase-workspace
5067 kdebase-workspace-bin
5068 kdebase-workspace-data
5069 kdeeject
5070 kdelibs
5071 kdeplasma-addons
5072 kdeutils
5073 kdewallpapers
5074 kdf
5075 kfloppy
5076 kgpg
5077 khelpcenter4
5078 kinfocenter
5079 konq-plugins-l10n
5080 konqueror-nsplugins
5081 kscreensaver
5082 kscreensaver-xsavers
5083 ktimer
5084 kwrite
5085 libgle3
5086 libkde4-ruby1.8
5087 libkonq5
5088 libkonq5-templates
5089 libnetpbm10
5090 libplasma-ruby
5091 libplasma-ruby1.8
5092 libqt4-ruby1.8
5093 marble-data
5094 marble-plugins
5095 netpbm
5096 nuvola-icon-theme
5097 plasma-dataengines-workspace
5098 plasma-desktop
5099 plasma-desktopthemes-artwork
5100 plasma-runners-addons
5101 plasma-scriptengine-googlegadgets
5102 plasma-scriptengine-python
5103 plasma-scriptengine-qedje
5104 plasma-scriptengine-ruby
5105 plasma-scriptengine-webkit
5106 plasma-scriptengines
5107 plasma-wallpapers-addons
5108 plasma-widget-folderview
5109 plasma-widget-networkmanagement
5110 ruby
5111 sweeper
5112 update-notifier-kde
5113 xscreensaver-data-extra
5114 xscreensaver-gl
5115 xscreensaver-gl-extra
5116 xscreensaver-screensaver-bsod
5117 &lt;/p&gt;&lt;/blockquote&gt;
5118
5119 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5120
5121 &lt;blockquote&gt;&lt;p&gt;
5122 ark
5123 google-gadgets-common
5124 google-gadgets-qt
5125 htdig
5126 kate
5127 kdebase-bin
5128 kdebase-data
5129 kdepasswd
5130 kfind
5131 klipper
5132 konq-plugins
5133 konqueror
5134 ksysguard
5135 ksysguardd
5136 libarchive1
5137 libcln6
5138 libeet1
5139 libeina-svn-06
5140 libggadget-1.0-0b
5141 libggadget-qt-1.0-0b
5142 libgps19
5143 libkdecorations4
5144 libkephal4
5145 libkonq4
5146 libkonqsidebarplugin4a
5147 libkscreensaver5
5148 libksgrd4
5149 libksignalplotter4
5150 libkunitconversion4
5151 libkwineffects1a
5152 libmarblewidget4
5153 libntrack-qt4-1
5154 libntrack0
5155 libplasma-geolocation-interface4
5156 libplasmaclock4a
5157 libplasmagenericshell4
5158 libprocesscore4a
5159 libprocessui4a
5160 libqalculate5
5161 libqedje0a
5162 libqtruby4shared2
5163 libqzion0a
5164 libruby1.8
5165 libscim8c2a
5166 libsmokekdecore4-3
5167 libsmokekdeui4-3
5168 libsmokekfile3
5169 libsmokekhtml3
5170 libsmokekio3
5171 libsmokeknewstuff2-3
5172 libsmokeknewstuff3-3
5173 libsmokekparts3
5174 libsmokektexteditor3
5175 libsmokekutils3
5176 libsmokenepomuk3
5177 libsmokephonon3
5178 libsmokeplasma3
5179 libsmokeqtcore4-3
5180 libsmokeqtdbus4-3
5181 libsmokeqtgui4-3
5182 libsmokeqtnetwork4-3
5183 libsmokeqtopengl4-3
5184 libsmokeqtscript4-3
5185 libsmokeqtsql4-3
5186 libsmokeqtsvg4-3
5187 libsmokeqttest4-3
5188 libsmokeqtuitools4-3
5189 libsmokeqtwebkit4-3
5190 libsmokeqtxml4-3
5191 libsmokesolid3
5192 libsmokesoprano3
5193 libtaskmanager4a
5194 libtidy-0.99-0
5195 libweather-ion4a
5196 libxklavier16
5197 libxxf86misc1
5198 okteta
5199 oxygencursors
5200 plasma-dataengines-addons
5201 plasma-scriptengine-superkaramba
5202 plasma-widget-lancelot
5203 plasma-widgets-addons
5204 plasma-widgets-workspace
5205 polkit-kde-1
5206 ruby1.8
5207 systemsettings
5208 update-notifier-common
5209 &lt;/p&gt;&lt;/blockquote&gt;
5210
5211 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5212 aptitude a bit more similar, but there are still quite a lott of
5213 differences. I have no idea what packages should be installed after
5214 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5215 </description>
5216 </item>
5217
5218 <item>
5219 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5220 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5222 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5223 <description>&lt;p&gt;Most of the computers in use by the
5224 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5225 are virtual machines. And they have been Xen machines running on a
5226 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5227 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5228 bit harder that it could have been, because we set up the Xen virtual
5229 machines to get the virtual partitions from LVM, which as far as I
5230 know is not supported by KVM. So to migrate, we had to convert
5231 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5232
5233 &lt;p&gt;I found
5234 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5235 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5236 migration. It uses qemu-img from the qemu package to make the disk
5237 image, parted to partition it, losetup and kpartx to present the disk
5238 image partions as devices, and dd to copy the data. I NFS mounted the
5239 new servers storage area on the old server to do the migration.&lt;/p&gt;
5240
5241 &lt;pre&gt;
5242 #!/bin/sh
5243
5244 # Based on
5245 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5246
5247 set -e
5248 set -x
5249
5250 if [ -z &quot;$1&quot; ] ; then
5251 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5252 exit 1
5253 else
5254 host=&quot;$1&quot;
5255 fi
5256
5257 if [ ! -e /dev/vg_data/$host-disk ] ; then
5258 echo &quot;error: unable to find LVM volume for $host&quot;
5259 exit 1
5260 fi
5261
5262 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5263 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5264 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5265 totalsize=$(( ( $disksize + $swapsize ) ))
5266
5267 img=$host.img
5268 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5269 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5270
5271 parted $img mklabel msdos
5272 parted $img mkpart primary linux-swap 0 $disksize
5273 parted $img mkpart primary ext2 $disksize $totalsize
5274 parted $img set 1 boot on
5275
5276 modprobe dm-mod
5277 losetup /dev/loop0 $img
5278 kpartx -a /dev/loop0
5279
5280 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5281 fsck.ext3 -f /dev/mapper/loop0p1 || true
5282 mkswap /dev/mapper/loop0p2
5283
5284 kpartx -d /dev/loop0
5285 losetup -d /dev/loop0
5286 &lt;/pre&gt;
5287
5288 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5289 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5290
5291 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5292 the new disk image attached, installed grub-pc and linux-image-686 and
5293 set up grub to boot from the disk image. After this, the KVM machines
5294 seem to work just fine.&lt;/p&gt;
5295 </description>
5296 </item>
5297
5298 <item>
5299 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5300 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5301 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5302 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5303 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5304 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5305 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5306 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5307
5308 &lt;p&gt;I still do not know what a correct migration should look like, so I
5309 report any differences between apt and aptitude and hope someone else
5310 can see if anything should be changed.&lt;/p&gt;
5311
5312 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5313
5314 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5315
5316 &lt;blockquote&gt;&lt;p&gt;
5317 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5318 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5319 dmz-cursor-theme empathy empathy-common finger
5320 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5321 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5322 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5323 gnome-cards-data gnome-codec-install gnome-core
5324 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5325 gnome-search-tool gnome-session-canberra gnome-spell
5326 gnome-system-log gnome-themes-extras gnome-themes-more
5327 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5328 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5329 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5330 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5331 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5332 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5333 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5334 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5335 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5336 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5337 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5338 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5339 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5340 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5341 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5342 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5343 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5344 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5345 libmono-security2.0-cil libmono-sharpzip2.84-cil
5346 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5347 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5348 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5349 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5350 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5351 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5352 libxalan2-java libxerces2-java media-player-info mesa-utils
5353 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5354 nautilus-sendto-empathy openoffice.org-writer2latex
5355 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5356 python-aptdaemon python-aptdaemon-gtk python-axiom
5357 python-beautifulsoup python-bugbuddy python-clientform
5358 python-coherence python-configobj python-crypto python-cupshelpers
5359 python-cupsutils python-eggtrayicon python-elementtree
5360 python-epsilon python-evolution python-feedparser python-gdata
5361 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5362 python-gtksourceview2 python-httplib2 python-louie python-mako
5363 python-markupsafe python-mechanize python-nevow python-notify
5364 python-opengl python-openssl python-pam python-pkg-resources
5365 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5366 python-tagpy python-twisted-bin python-twisted-conch
5367 python-twisted-core python-twisted-web python-utidylib python-webkit
5368 python-xdg python-zope.interface remmina remmina-plugin-data
5369 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5370 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5371 software-center svgalibg1 system-config-printer-udev
5372 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5373 totem totem-coherence totem-mozilla totem-plugins
5374 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5375 zip
5376 &lt;/p&gt;&lt;/blockquote&gt;
5377
5378 Installed using apt-get, removed with aptitude
5379
5380 &lt;blockquote&gt;&lt;p&gt;
5381 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5382 epiphany-extensions epiphany-gecko evolution-exchange
5383 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5384 gedit-common gnome-app-install gnome-games gnome-games-data
5385 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5386 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5387 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5388 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5389 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5390 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5391 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5392 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5393 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5394 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5395 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5396 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5397 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5398 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5399 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5400 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5401 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5402 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5403 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5404 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5405 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5406 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5407 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5408 sound-juicer swfdec-gnome system-config-printer totem-common
5409 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5410 &lt;/p&gt;&lt;/blockquote&gt;
5411
5412 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5413
5414 &lt;blockquote&gt;&lt;p&gt;
5415 gstreamer0.10-gnomevfs
5416 &lt;/p&gt;&lt;/blockquote&gt;
5417
5418 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5419
5420 &lt;blockquote&gt;&lt;p&gt;
5421 [nothing]
5422 &lt;/p&gt;&lt;/blockquote&gt;
5423
5424 &lt;p&gt;This is for KDE:&lt;/p&gt;
5425
5426 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5427
5428 &lt;blockquote&gt;&lt;p&gt;
5429 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5430 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5431 ghostscript-x git gnome-audio gnugo granatier gs-common
5432 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5433 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5434 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5435 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5436 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5437 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5438 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5439 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5440 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5441 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5442 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5443 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5444 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5445 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5446 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5447 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5448 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5449 libkrossui4 libmailtools-perl libmime-tools-perl
5450 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5451 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5452 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5453 lirc luatex marble networkstatus noatun-plugins
5454 openoffice.org-writer2latex palapeli palapeli-data parley
5455 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5456 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5457 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5458 ttf-sazanami-gothic
5459 &lt;/p&gt;&lt;/blockquote&gt;
5460
5461 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5462
5463 &lt;blockquote&gt;&lt;p&gt;
5464 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5465 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5466 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5467 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5468 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5469 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5470 kitchensync kiten kjumpingcube klatin klettres klickety klines
5471 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5472 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5473 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5474 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5475 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5476 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5477 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5478 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5479 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5480 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5481 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5482 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5483 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5484 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5485 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5486 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5487 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5488 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5489 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5490 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5491 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5492 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5493 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5494 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5495 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5496 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5497 &lt;/p&gt;&lt;/blockquote&gt;
5498
5499 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5500
5501 &lt;blockquote&gt;&lt;p&gt;
5502 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5503 kdeartwork kdebase kdebase-apps kdebase-workspace
5504 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5505 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5506 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5507 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5508 xscreensaver-screensaver-bsod
5509 &lt;/p&gt;&lt;/blockquote&gt;
5510
5511 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5512
5513 &lt;blockquote&gt;&lt;p&gt;
5514 kdebase-bin konq-plugins konqueror
5515 &lt;/p&gt;&lt;/blockquote&gt;
5516 </description>
5517 </item>
5518
5519 <item>
5520 <title>Gnash buildbot slave and Debian kfreebsd</title>
5521 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5522 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5523 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5524 <description>&lt;p&gt;Answering
5525 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5526 call from the Gnash project&lt;/a&gt; for
5527 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5528 current source, I have set up a virtual KVM machine on the Debian
5529 Edu/Skolelinux virtualization host to test the git source on
5530 Debian/Squeeze. I hope this can help the developers in getting new
5531 releases out more often.&lt;/p&gt;
5532
5533 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5534 I have considered setting up a &lt;a
5535 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5536 machine as well. I have also considered using the kfreebsd
5537 architecture in Debian as a file server in NUUG to get access to the 5
5538 TB zfs volume we currently use to store DV video. Because of this, I
5539 finally got around to do a test installation of Debian/Squeeze with
5540 kfreebsd. Installation went fairly smooth, thought I noticed some
5541 visual glitches in the cdebconf dialogs (black cursor left on the
5542 screen at random locations). Have not gotten very far with the
5543 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5544 fatal problem. Have to spend some more time on it to see if it is
5545 useful as a file server for NUUG. Will try to find time to set up a
5546 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5547 </description>
5548 </item>
5549
5550 <item>
5551 <title>Debian in 3D</title>
5552 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5553 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5554 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5555 <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;
5556
5557 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5558 3D linked in from
5559 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5560 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5561 </description>
5562 </item>
5563
5564 <item>
5565 <title>Software updates 2010-10-24</title>
5566 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5567 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5568 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5569 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5570
5571 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5572 raise money for the project is going well. The lower limit of 10
5573 signers was reached in 24 hours, and so far 13 people have signed it.
5574 More signers and more funding is most welcome, and I am really curious
5575 how far we can get before the time limit of December 24 is reached.
5576 :)&lt;/p&gt;
5577
5578 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5579 about what appear to be a great code coverage tool capable of
5580 generating code coverage stats without any changes to the source code.
5581 It is called
5582 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5583 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5584 It is missing in Debian, but the git source built just fine in Squeeze
5585 after I installed libelf-dev, libdwarf-dev, pkg-config and
5586 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5587 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5588
5589 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5590 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5591 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5592 alpha test release of the Squeeze based Debian Edu /
5593 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5594 release. Give it a try if you need a complete linux solution for your
5595 school, including central infrastructure server, workstations, thin
5596 client servers and diskless workstations. A nice touch added
5597 yesterday is RDP support on the thin client servers, for windows
5598 clients to get a Linux desktop on request.&lt;/p&gt;
5599 </description>
5600 </item>
5601
5602 <item>
5603 <title>Some notes on Flash in Debian and Debian Edu</title>
5604 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5605 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5606 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5607 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5608 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5609 second most popular used package that is missing in Debian. The sixth
5610 most popular is flashplayer-mozilla. This is a clear indication that
5611 working flash is important for Debian users. Around 10 percent of the
5612 users submitting data to popcon.debian.org have this package
5613 installed.&lt;/p&gt;
5614
5615 &lt;p&gt;In the report written by Lars Risan in August 2008
5616&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
5617 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5618 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5619 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5620 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5621 web sites require Flash to work, and lacking working Flash support in
5622 the web browser and the problems with installing it was perceived as a
5623 good reason to stay with Windows.&lt;/p&gt;
5624
5625 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
5626 said to be the retarded cousin that did not really understand
5627 everything you told him but could work fairly well. This was a
5628 comment regarding the problems Linux have with proprietary formats and
5629 non-standard web pages, and is sad because it exposes a fairly common
5630 understanding of whose fault it is if web pages that only work in for
5631 example Internet Explorer 6 fail to work on Firefox, and funny because
5632 it explain very well how annoying it is for users when Linux
5633 distributions do not work with the documents they receive or the web
5634 pages they want to visit.&lt;/p&gt;
5635
5636 &lt;p&gt;This is part of the reason why I believe it is important for Debian
5637 and Debian Edu to have a well working Flash implementation in the
5638 distribution, to get at least popular sites as Youtube and Google
5639 Video to working out of the box. For Squeeze, Debian have the chance
5640 to include the latest version of Gnash that will make this happen, as
5641 the new release 0.8.8 was published a few weeks ago and is resting in
5642 unstable. The new version work with more sites that version 0.8.7.
5643 The Gnash maintainers have asked for a freeze exception, but the
5644 release team have not had time to reply to it yet. I hope they agree
5645 with me that Flash is important for the Debian desktop users, and thus
5646 accept the new package into Squeeze.&lt;/p&gt;
5647 </description>
5648 </item>
5649
5650 <item>
5651 <title>Circular package dependencies harms apt recovery</title>
5652 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
5653 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
5654 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
5655 <description>&lt;p&gt;I discovered this while doing
5656 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
5657 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
5658 in Debian still got circular dependencies, and it is often claimed
5659 that apt and aptitude should be able to handle this just fine, but
5660 some times these dependency loops causes apt to fail.&lt;/p&gt;
5661
5662 &lt;p&gt;An example is from todays
5663 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
5664 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
5665 causes perl-modules to fail to upgrade. The cause is simple. If a
5666 package fail to unpack, then only part of packages with the circular
5667 dependency might end up being unpacked when unpacking aborts, and the
5668 ones already unpacked will fail to configure in the recovery phase
5669 because its dependencies are unavailable.&lt;/p&gt;
5670
5671 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
5672
5673 &lt;blockquote&gt;&lt;pre&gt;
5674 dpkg: dependency problems prevent configuration of perl-modules:
5675 perl-modules depends on perl (&gt;= 5.10.1-1); however:
5676 Version of perl on system is 5.10.0-19lenny2.
5677 dpkg: error processing perl-modules (--configure):
5678 dependency problems - leaving unconfigured
5679 &lt;/pre&gt;&lt;/blockquote&gt;
5680
5681 &lt;p&gt;The perl/perl-modules circular dependency is already
5682 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
5683 hopefully be solved as soon as possible, but it is not the only one,
5684 and each one of these loops in the dependency tree can cause similar
5685 failures. Of course, they only occur when there are bugs in other
5686 packages causing the unpacking to fail, but it is rather nasty when
5687 the failure of one package causes the problem to become worse because
5688 of dependency loops.&lt;/p&gt;
5689
5690 &lt;p&gt;Thanks to
5691 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
5692 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
5693 dependencies
5694 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
5695 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
5696
5697 &lt;p&gt;Todays testing also exposed a bug in
5698 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
5699 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
5700 apt-get and aptitude, the latter possibly caused by some circular
5701 dependency. Reported both to BTS to try to get someone to look at
5702 it.&lt;/p&gt;
5703 </description>
5704 </item>
5705
5706 <item>
5707 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
5708 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
5709 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
5710 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
5711 <description>&lt;p&gt;This is a
5712 &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;
5713 on my
5714 &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
5715 work&lt;/a&gt; on
5716 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
5717 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
5718
5719 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
5720 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5721 and dhcp3-server-ldap in Debian use the LDAP server. The two
5722 implementations are quite different in how they use LDAP.&lt;/p&gt;
5723
5724 To get this information, I started slapd with debugging enabled and
5725 dumped the debug output to a file to get the LDAP searches performed
5726 on a Debian Edu main-server. Here is a summary.
5727
5728 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
5729
5730 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
5731 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
5732 the web.
5733
5734 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
5735 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
5736 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
5737 reverse entries are in two different subtrees in LDAP with a structure
5738 based on the DNS names, as in tjener.intern and
5739 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5740
5741 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5742 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5743 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5744 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5745 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5746 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5747 forward entries, it is looking for attributes named dnsttl, arecord,
5748 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5749 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5750 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5751 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5752 spfrecord and modifytimestamp. For reverse entries it is looking for
5753 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5754 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5755 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5756 ldapsearch commands could look like this:&lt;/p&gt;
5757
5758 &lt;blockquote&gt;&lt;pre&gt;
5759 ldapsearch -h ldap \
5760 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5761 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5762 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5763 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5764 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5765 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5766
5767 ldapsearch -h ldap \
5768 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5769 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
5770 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5771 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5772 srvrecord naptrrecord modifytimestamp
5773 &lt;/pre&gt;&lt;/blockquote&gt;
5774
5775 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
5776 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5777 example LDAP objects used there. In addition to these objects, the
5778 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5779 also exist.&lt;/p&gt;
5780
5781 &lt;blockquote&gt;&lt;pre&gt;
5782 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5783 objectclass: top
5784 objectclass: dnsdomain
5785 objectclass: domainrelatedobject
5786 dc: tjener
5787 arecord: 10.0.2.2
5788 associateddomain: tjener.intern
5789
5790 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5791 objectclass: top
5792 objectclass: dnsdomain2
5793 objectclass: domainrelatedobject
5794 dc: 2
5795 ptrrecord: tjener.intern
5796 associateddomain: 2.2.0.10.in-addr.arpa
5797 &lt;/pre&gt;&lt;/blockquote&gt;
5798
5799 &lt;p&gt;In strict mode, the server behaves differently. When looking for
5800 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
5801 same base as in the tree mode for a object with filter
5802 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
5803 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5804 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5805 naptrrecord and modifytimestamp. For reverse entires it also do a
5806 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
5807 and the requested attributes are associateddomain, dnsttl and
5808 modifytimestamp. In short, in strict mode the objects with ptrrecord
5809 go away, and the arecord attribute in the forward object is used
5810 instead.&lt;/p&gt;
5811
5812 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
5813 like this:&lt;/p&gt;
5814
5815 &lt;blockquote&gt;&lt;pre&gt;
5816 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5817 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5818 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5819 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5820 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5821 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5822
5823 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5824 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
5825 &lt;/pre&gt;&lt;/blockquote&gt;
5826
5827 &lt;p&gt;In addition to the forward and reverse searches , there is also a
5828 search for SOA records, which behave similar to the forward and
5829 reverse lookups.&lt;/p&gt;
5830
5831 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
5832 specify any objectclass names, and instead look for the attributes it
5833 need to generate a DNS reply. This make it able to work with any
5834 objectclass that provide the needed attributes.&lt;/p&gt;
5835
5836 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
5837 dnsdomain2 schemas. The latter is used for reverse entries like
5838 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
5839
5840 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
5841 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5842 attributes) and domainrelatedobject (for associatedDomain). The use
5843 of structural object classes make it impossible to combine these
5844 classes with the object classes used by DHCP.&lt;/p&gt;
5845
5846 &lt;p&gt;There are other schemas that could be used too, for example the
5847 dnszone structural object class used by Gosa and bind-sdb for the DNS
5848 attributes combined with the domainrelatedobject object class, but in
5849 this case some unused attributes would have to be included as well
5850 (zonename and relativedomainname).&lt;/p&gt;
5851
5852 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
5853 mode and not use any of the existing objectclasses (dnsdomain,
5854 dnsdomain2 and dnszone) when one want to combine the DNS information
5855 with DHCP information, and instead create a auxiliary object class
5856 defined something like this (using the attributes defined for
5857 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
5858
5859 &lt;blockquote&gt;&lt;pre&gt;
5860 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
5861 SUP top
5862 AUXILIARY
5863 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5864 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5865 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5866 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5867 A6Record $ DNAMERecord
5868 ))
5869 &lt;/pre&gt;&lt;/blockquote&gt;
5870
5871 &lt;p&gt;This will allow any object to become a DNS entry when combined with
5872 the domainrelatedobject object class, and allow any entity to include
5873 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
5874 developers asking for their view on this schema and if they are
5875 interested in providing such schema with PowerDNS, and I hope my
5876 message will be accepted into their mailing list soon.&lt;/p&gt;
5877
5878 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
5879
5880 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
5881 the object attributes, and then uses the attributes it want. This
5882 make it harder to figure out exactly what attributes are used, but
5883 thanks to the working example in Debian Edu I can at least get an idea
5884 what is needed without having to read the source code.&lt;/p&gt;
5885
5886 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
5887 search filter to use to locate the correct dhcpServer entity is
5888 stored. These are the relevant entries from
5889 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
5890
5891 &lt;blockquote&gt;&lt;pre&gt;
5892 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
5893 ldap-dhcp-server-cn &quot;dhcp&quot;;
5894 &lt;/pre&gt;&lt;/blockquote&gt;
5895
5896 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
5897 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
5898 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
5899 search result is this entry:&lt;/p&gt;
5900
5901 &lt;blockquote&gt;&lt;pre&gt;
5902 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5903 cn: dhcp
5904 objectClass: top
5905 objectClass: dhcpServer
5906 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5907 &lt;/pre&gt;&lt;/blockquote&gt;
5908
5909 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
5910 subtree with DHCP configuration. The DHCP configuration subtree base
5911 is located using a base scope search with base &quot;cn=DHCP
5912 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
5913 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
5914 The search result is this entry:&lt;/p&gt;
5915
5916 &lt;blockquote&gt;&lt;pre&gt;
5917 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5918 cn: DHCP Config
5919 objectClass: top
5920 objectClass: dhcpService
5921 objectClass: dhcpOptions
5922 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5923 dhcpStatements: ddns-update-style none
5924 dhcpStatements: authoritative
5925 dhcpOption: smtp-server code 69 = array of ip-address
5926 dhcpOption: www-server code 72 = array of ip-address
5927 dhcpOption: wpad-url code 252 = text
5928 &lt;/pre&gt;&lt;/blockquote&gt;
5929
5930 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
5931 all the DHCP configuration is loaded, it is ready to receive requests.
5932 The subtree in Debian Edu contain objects with object classes
5933 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5934 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5935 and information about netmasks, dynamic range etc. Leaving out the
5936 details here because it is not relevant for the focus of my
5937 investigation, which is to see if it is possible to merge dns and dhcp
5938 related computer objects.&lt;/p&gt;
5939
5940 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
5941 of the client (00:00:00:00:00:00 in this example), using a subtree
5942 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
5943 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5944 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
5945 like:&lt;/p&gt;
5946
5947 &lt;blockquote&gt;&lt;pre&gt;
5948 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5949 cn: hostname
5950 objectClass: top
5951 objectClass: dhcpHost
5952 dhcpHWAddress: ethernet 00:00:00:00:00:00
5953 dhcpStatements: fixed-address hostname
5954 &lt;/pre&gt;&lt;/blockquote&gt;
5955
5956 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
5957 The object classes need to have fixed names, and the configuration
5958 need to be stored in a fairly specific LDAP structure. On the
5959 positive side, the invidiual dhcpHost entires can be anywhere without
5960 the DN pointed to by the dhcpServer entries. The latter should make
5961 it possible to group all host entries in a subtree next to the
5962 configuration entries, and this subtree can also be shared with the
5963 DNS server if the schema proposed above is combined with the dhcpHost
5964 structural object class.
5965
5966 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
5967
5968 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
5969 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
5970 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
5971 allowing DNS objects to be stored anywhere under the base cn specified
5972 in the configuration.&lt;/p&gt;
5973
5974 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
5975 regarding which LDAP schemas to use and which LDAP structure to use.
5976 I guess one could implement ones own schema, as long as the
5977 objectclasses and attributes have the names used, but this do not
5978 really help when the DHCP subtree need to have a fairly fixed
5979 structure.&lt;/p&gt;
5980
5981 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
5982 this might work for Debian Edu:&lt;/p&gt;
5983
5984 &lt;blockquote&gt;&lt;pre&gt;
5985 ou=services
5986 cn=machine-info (dhcpService) - dhcpServiceDN points here
5987 cn=dhcp (dhcpServer)
5988 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5989 cn=10.0.2.0 (dhcpSubnet)
5990 cn=group1 (dhcpGroup/dhcpOptions)
5991 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5992 cn=192.168.0.0 (dhcpSubnet)
5993 cn=group1 (dhcpGroup/dhcpOptions)
5994 ou=machines - PowerDNS base points here
5995 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5996 &lt;/pre&gt;&lt;/blockquote&gt;
5997
5998 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
5999 entries to be in the dhcpGroup subtrees, the entries can be stored
6000 there instead of a common machines subtree, and the PowerDNS base
6001 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6002
6003 &lt;p&gt;The combined object under the machines subtree would look something
6004 like this:&lt;/p&gt;
6005
6006 &lt;blockquote&gt;&lt;pre&gt;
6007 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6008 dc: hostname
6009 objectClass: top
6010 objectClass: dhcpHost
6011 objectclass: domainrelatedobject
6012 objectclass: dnsDomainAux
6013 associateddomain: hostname.intern
6014 arecord: 10.11.12.13
6015 dhcpHWAddress: ethernet 00:00:00:00:00:00
6016 dhcpStatements: fixed-address hostname.intern
6017 &lt;/pre&gt;&lt;/blockquote&gt;
6018
6019 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6020 machine, as long as the required attributes are available in a
6021 auxiliary object class.&lt;/p&gt;
6022 </description>
6023 </item>
6024
6025 <item>
6026 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6027 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6028 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6029 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6030 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6031 DHCP services in Debian Edu to use the same LDAP objects for a given
6032 computer, to avoid the possibility of having a inconsistent state for
6033 a computer in LDAP (as in DHCP but no DNS entry or the other way
6034 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6035
6036 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6037 information finally found a solution that seem to work.&lt;/p&gt;
6038
6039 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6040 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6041 we switch powerdns to use its strict LDAP method (ldap-method=strict
6042 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6043 merged into one while making it impossible to transfer the reverse map
6044 to a slave DNS server.&lt;/p&gt;
6045
6046 &lt;p&gt;If we also replace the object class used to get the DNS related
6047 attributes to one allowing these attributes to be combined with the
6048 dhcphost object class, we can merge the DNS and DHCP entries into one.
6049 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6050 proper OIDs, but that is a minor issue), and tested the setup. It
6051 seem to work.&lt;/p&gt;
6052
6053 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6054 for both DNS and DHCP, and even the LTSP configuration I suggested in
6055 an earlier email. The combined LDAP object will look something like
6056 this:&lt;/p&gt;
6057
6058 &lt;blockquote&gt;&lt;pre&gt;
6059 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6060 cn: hostname
6061 objectClass: dhcphost
6062 objectclass: domainrelatedobject
6063 objectclass: dnsdomainaux
6064 associateddomain: hostname.intern
6065 arecord: 10.11.12.13
6066 dhcphwaddress: ethernet 00:00:00:00:00:00
6067 dhcpstatements: fixed-address hostname
6068 ldapconfigsound: Y
6069 &lt;/pre&gt;&lt;/blockquote&gt;
6070
6071 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6072 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6073 before asking DNS to resolve the fixed-adddress. LTSP will use
6074 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6075
6076 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6077 dhcphost in a different location, to allow us to put the objects
6078 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6079 that. If I can&#39;t figure out a way to do that, we can still get rid of
6080 the hosts subtree and move all its content into the DHCP Config tree
6081 (which probably should be renamed to be more related to the new
6082 content. I suspect cn=dnsdhcp,ou=services or something like that
6083 might be a good place to put it.&lt;/p&gt;
6084
6085 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6086 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6087 </description>
6088 </item>
6089
6090 <item>
6091 <title>Idea for storing LTSP configuration in LDAP</title>
6092 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6093 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6094 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6095 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6096 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6097 clients, and that this can be used to fetch configuration from LDAP if
6098 Debian Edu choose to store configuration there.&lt;/p&gt;
6099
6100 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6101 to get configuration from LDAP. The idea is to look up the MAC
6102 address of the client in LDAP, and look for attributes on the form
6103 ltspconfigsetting=value, and use this to export SETTING=value to the
6104 LTSP clients.&lt;/p&gt;
6105
6106 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6107 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6108 allowing us to store all information about a computer in one place.&lt;/p&gt;
6109
6110 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6111 this approach. A real LDAP schema for the ltspClientAux objectclass
6112 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6113
6114 &lt;blockquote&gt;&lt;pre&gt;
6115 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6116 #
6117 # Fetch LTSP client settings from LDAP based on MAC address
6118 #
6119 # Uses ethernet address as stored in the dhcpHost objectclass using
6120 # the dhcpHWAddress attribute or ethernet address stored in the
6121 # ieee802Device objectclass with the macAddress attribute.
6122 #
6123 # This module is written to be schema agnostic, and only depend on the
6124 # existence of attribute names.
6125 #
6126 # The LTSP configuration variables are saved directly using a
6127 # ltspConfig prefix and uppercasing the rest of the attribute name.
6128 # To set the SERVER variable, set the ltspConfigServer attribute.
6129 #
6130 # Some LDAP schema should be created with all the relevant
6131 # configuration settings. Something like this should work:
6132 #
6133 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6134 # SUP top
6135 # AUXILIARY
6136 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6137
6138 LDAPSERVER=$(debian-edu-ldapserver)
6139 if [ &quot;$LDAPSERVER&quot; ] ; then
6140 LDAPBASE=$(debian-edu-ldapserver -b)
6141 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6142 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6143 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6144 grep &#39;^ltspConfig&#39; | while read attr value ; do
6145 # Remove prefix and convert to upper case
6146 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6147 # bass value on to clients
6148 eval &quot;$attr=$value; export $attr&quot;
6149 done
6150 done
6151 fi
6152 &lt;/pre&gt;&lt;/blockquote&gt;
6153
6154 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6155 the while block might end up in a subshell causing the variables set
6156 there to not show up in ltsp-config, but if that is the case I am sure
6157 the code can be restructured to make sure the variables are passed on.
6158 I expect that can be solved with some testing. :)&lt;/p&gt;
6159
6160 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6161 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6162
6163 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6164 configuration in LDAP that was created around year 2000 by
6165 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6166 Xperience, Inc., 2000&lt;/a&gt;. I found its
6167 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6168 personal home page over at redhat.com.&lt;/p&gt;
6169 </description>
6170 </item>
6171
6172 <item>
6173 <title>jXplorer, a very nice LDAP GUI</title>
6174 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6175 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6176 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6177 <description>&lt;p&gt;Since
6178 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6179 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6180 LDAP GUI that is even better than luma. The java application
6181 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6182 moving LDAP objects and subtrees using drag-and-drop, and can
6183 authenticate using Kerberos. I have only tested the Kerberos
6184 authentication, but do not have a LDAP setup allowing me to rewrite
6185 LDAP with my test user yet. It is
6186 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6187 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6188 have with it is how it handle errors. If something go wrong, its
6189 non-intuitive behaviour require me to go through some query work list
6190 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6191 </description>
6192 </item>
6193
6194 <item>
6195 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6196 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6197 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6198 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6199 <description>&lt;p&gt;Here is a short update on my &lt;a
6200 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6201 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6202 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6203 not reporting the status for KDE, because the upgrade crashes when
6204 aptitude try because of missing conflicts
6205 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6206 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6207
6208 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6209 complete list of the installed packages. Based on this I see these
6210 differences when I did a test run today. As usual, I do not really
6211 know what the correct set of packages would be, but thought it best to
6212 publish the difference.&lt;/p&gt;
6213
6214 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6215
6216 &lt;blockquote&gt;&lt;p&gt;
6217 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6218 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6219 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6220 libgtksourceview-common libpt-1.10.10-plugins-alsa
6221 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6222 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6223 python-4suite-xml python-eggtrayicon python-gtkhtml2
6224 python-gtkmozembed svgalibg1 xserver-xephyr zip
6225 &lt;/p&gt;&lt;/blockquote&gt;
6226
6227 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6228
6229 &lt;blockquote&gt;&lt;p&gt;
6230 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6231 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6232 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6233 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6234 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6235 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6236 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6237 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6238 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6239 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6240 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6241 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6242 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6243 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6244 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6245 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6246 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6247 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6248 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6249 mysql-common swfdec-gnome totem-gstreamer wodim
6250 &lt;/p&gt;&lt;/blockquote&gt;
6251
6252 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6253
6254 &lt;blockquote&gt;&lt;p&gt;
6255 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6256 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6257 xserver-xorg-input-all xserver-xorg-input-evdev
6258 xserver-xorg-input-kbd xserver-xorg-input-mouse
6259 xserver-xorg-input-synaptics xserver-xorg-video-all
6260 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6261 xserver-xorg-video-chips xserver-xorg-video-cirrus
6262 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6263 xserver-xorg-video-glint xserver-xorg-video-i128
6264 xserver-xorg-video-i740 xserver-xorg-video-mach64
6265 xserver-xorg-video-mga xserver-xorg-video-neomagic
6266 xserver-xorg-video-nouveau xserver-xorg-video-nv
6267 xserver-xorg-video-r128 xserver-xorg-video-radeon
6268 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6269 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6270 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6271 xserver-xorg-video-sis xserver-xorg-video-sisusb
6272 xserver-xorg-video-tdfx xserver-xorg-video-tga
6273 xserver-xorg-video-trident xserver-xorg-video-tseng
6274 xserver-xorg-video-vesa xserver-xorg-video-vmware
6275 xserver-xorg-video-voodoo
6276 &lt;/p&gt;&lt;/blockquote&gt;
6277
6278 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6279
6280 &lt;blockquote&gt;&lt;p&gt;
6281 deskbar-applet xserver-xorg xserver-xorg-core
6282 xserver-xorg-input-wacom xserver-xorg-video-intel
6283 xserver-xorg-video-openchrome
6284 &lt;/p&gt;&lt;/blockquote&gt;
6285
6286 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6287 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6288 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6289 No idea when it hits Squeeze, but when it does I hope it will reduce
6290 the difference somewhat.
6291 </description>
6292 </item>
6293
6294 <item>
6295 <title>LUMA, a very nice LDAP GUI</title>
6296 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6297 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6298 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6299 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6300 directory in Debian Edu, and in the process I started to miss a GUI
6301 tool to browse the LDAP tree. The only one I was able to find in
6302 Debian/Squeeze and Lenny is
6303 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6304 be a great tool to get a overview of the current LDAP directory
6305 populated by default in Skolelinux. Thanks to it, I have been able to
6306 find empty and obsolete subtrees, misplaced objects and duplicate
6307 objects. It will be installed by default in Debian/Squeeze. If you
6308 are working with LDAP, give it a go. :)&lt;/p&gt;
6309
6310 &lt;p&gt;I did notice one problem with it I have not had time to report to
6311 the BTS yet. There is no .desktop file in the package, so the tool do
6312 not show up in the Gnome and KDE menus, but only deep down in in the
6313 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6314 released.&lt;/p&gt;
6315
6316 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6317 like to move objects and remove subtrees directly in the GUI, but have
6318 not found a way to do that with LUMA yet. So in the mean time, I use
6319 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6320
6321 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6322 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6323
6324 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6325 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6326 useful GUI alternative. It seem like a good tool, but is unmaintained
6327 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6328 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6329 </description>
6330 </item>
6331
6332 <item>
6333 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6334 <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>
6335 <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>
6336 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6337 <description>&lt;p&gt;A while back, I
6338 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6339 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6340 for storing DNS and DHCP information in LDAP to combine the two sets
6341 of information into one LDAP object representing a computer.&lt;/p&gt;
6342
6343 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6344 the dhcpHost object class auxiliary, to allow it to be combined with
6345 the dNSDomain object class, and thus forming one object for one
6346 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6347
6348 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6349 without also changing the assigned number for the object class, and I
6350 do not know enough about LDAP schema design to do that properly for
6351 Debian Edu.&lt;/p&gt;
6352
6353 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6354 the
6355 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6356 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6357 available today from IETF.&lt;/p&gt;
6358
6359 &lt;pre&gt;
6360 --- dhcp.schema (revision 65192)
6361 +++ dhcp.schema (working copy)
6362 @@ -376,7 +376,7 @@
6363 objectclass ( 2.16.840.1.113719.1.203.6.6
6364 NAME &#39;dhcpHost&#39;
6365 DESC &#39;This represents information about a particular client&#39;
6366 - SUP top
6367 + SUP top AUXILIARY
6368 MUST cn
6369 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6370 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6371 &lt;/pre&gt;
6372
6373 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6374 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6375 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6376
6377 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6378 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6379 </description>
6380 </item>
6381
6382 <item>
6383 <title>Calling tasksel like the installer, while still getting useful output</title>
6384 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6386 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6387 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6388 installs packages during the normal debian-installer run. Until now,
6389 I have ended up letting tasksel do the work, with the annoying problem
6390 of not getting any feedback at all when something fails (like a
6391 conffile question from dpkg or a download that fails), using code like
6392 this:
6393
6394 &lt;blockquote&gt;&lt;pre&gt;
6395 export DEBIAN_FRONTEND=noninteractive
6396 tasksel --new-install
6397 &lt;/pre&gt;&lt;/blockquote&gt;
6398
6399 This would invoke tasksel, let its automatic task selection pick the
6400 tasks to install, and continue to install the requested tasks without
6401 any output what so ever.
6402
6403 Recently I revisited this problem while working on the automatic
6404 package upgrade testing, because tasksel would some times hang without
6405 any useful feedback, and I want to see what is going on when it
6406 happen. Then it occured to me, I can parse the output from tasksel
6407 when asked to run in test mode, and use that aptitude command line
6408 printed by tasksel then to simulate the tasksel run. I ended up using
6409 code like this:
6410
6411 &lt;blockquote&gt;&lt;pre&gt;
6412 export DEBIAN_FRONTEND=noninteractive
6413 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6414 $cmd
6415 &lt;/pre&gt;&lt;/blockquote&gt;
6416
6417 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6418 --without-recommends -o APT::Install-Recommends=no -y install
6419 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6420 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6421 laptop task and all packages with priority standard , required and
6422 important, just like tasksel would have done it during
6423 installation.&lt;/p&gt;
6424
6425 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6426 install packages without using debconf-apt-progress, for use cases
6427 like this.&lt;/p&gt;
6428 </description>
6429 </item>
6430
6431 <item>
6432 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6433 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6434 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6435 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6436 <description>&lt;p&gt;My
6437 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6438 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6439 finally made the upgrade logs available from
6440 &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;.
6441 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6442 apt and aptitude, and found their differences interesting. This time
6443 I will only focus on their removal plans.&lt;/p&gt;
6444
6445 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6446 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6447 surprising part is that it want to remove xorg and all
6448 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6449 sure why. When asking aptitude to do the same, it want to remove 129
6450 packages, but most of them are library packages I suspect are no
6451 longer needed. Both of them want to remove bluetooth packages, which
6452 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6453
6454 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6455 which seem like a bad idea and xorg the same way as with Gnome. Asking
6456 aptitude for the same, it wants to remove 192 packages, none which are
6457 too surprising.&lt;/p&gt;
6458
6459 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6460 and avoided, and perhaps others as well. Here are the complete list
6461 of planned removals. The complete logs is available from the URL
6462 above. Note if you want to repeat these tests, that the upgrade test
6463 for kde+apt-get hung in the tasksel setup because of dpkg asking
6464 conffile questions. No idea why. I worked around it by using
6465 &#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
6466 continue.&lt;/p&gt;
6467
6468 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6469 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6470 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6471 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6472 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6473 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6474 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6475 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6476 xserver-xorg-input-kbd xserver-xorg-input-mouse
6477 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6478 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6479 xserver-xorg-video-ati xserver-xorg-video-chips
6480 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6481 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6482 xserver-xorg-video-glint xserver-xorg-video-i128
6483 xserver-xorg-video-i740 xserver-xorg-video-imstt
6484 xserver-xorg-video-intel xserver-xorg-video-mach64
6485 xserver-xorg-video-mga xserver-xorg-video-neomagic
6486 xserver-xorg-video-nsc xserver-xorg-video-nv
6487 xserver-xorg-video-openchrome xserver-xorg-video-r128
6488 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6489 xserver-xorg-video-rendition xserver-xorg-video-s3
6490 xserver-xorg-video-s3virge xserver-xorg-video-savage
6491 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6492 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6493 xserver-xorg-video-tga xserver-xorg-video-trident
6494 xserver-xorg-video-tseng xserver-xorg-video-v4l
6495 xserver-xorg-video-vesa xserver-xorg-video-vga
6496 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6497 xulrunner-1.9-gnome-support&lt;/p&gt;
6498
6499 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6500
6501 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6502 djvulibre-desktop finger gnome-app-install gnome-mount
6503 gnome-network-admin gnome-spell gnome-vfs-obexftp
6504 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6505 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6506 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6507 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6508 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6509 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6510 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6511 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6512 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6513 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6514 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6515 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6516 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6517 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6518 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6519 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6520 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6521 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6522 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6523 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6524 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6525 openoffice.org-writer2latex openssl-blacklist p7zip
6526 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6527 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6528 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6529 swfdec-mozilla totem-gstreamer update-manager wodim
6530 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6531 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6532 zip&lt;/p&gt;
6533
6534 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6535
6536 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6537 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6538 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6539 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6540 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6541 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6542 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6543 xserver-xorg-input-kbd xserver-xorg-input-mouse
6544 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6545 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6546 xserver-xorg-video-ati xserver-xorg-video-chips
6547 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6548 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6549 xserver-xorg-video-glint xserver-xorg-video-i128
6550 xserver-xorg-video-i740 xserver-xorg-video-imstt
6551 xserver-xorg-video-intel xserver-xorg-video-mach64
6552 xserver-xorg-video-mga xserver-xorg-video-neomagic
6553 xserver-xorg-video-nsc xserver-xorg-video-nv
6554 xserver-xorg-video-openchrome xserver-xorg-video-r128
6555 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6556 xserver-xorg-video-rendition xserver-xorg-video-s3
6557 xserver-xorg-video-s3virge xserver-xorg-video-savage
6558 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6559 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6560 xserver-xorg-video-tga xserver-xorg-video-trident
6561 xserver-xorg-video-tseng xserver-xorg-video-v4l
6562 xserver-xorg-video-vesa xserver-xorg-video-vga
6563 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6564
6565 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6566 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6567 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6568 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6569 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6570 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6571 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6572 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6573 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6574 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6575 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6576 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6577 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6578 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6579 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6580 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6581 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6582 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6583 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6584 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6585 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6586 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6587 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6588 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6589 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6590 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6591 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6592 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6593 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6594 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6595 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6596 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6597 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6598 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6599 texlive-common texlive-doc-base texlive-fonts-recommended
6600 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6601 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6602 xulrunner-1.9&lt;/p&gt;
6603
6604 </description>
6605 </item>
6606
6607 <item>
6608 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6609 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6610 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6611 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6612 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6613 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6614 have been discovered and reported in the process
6615 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6616 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6617 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6618 kdebase-workspace-data), and to get a more regular testing going on, I
6619 am working on a script to automate the test.&lt;/p&gt;
6620
6621 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6622 Gnome or KDE desktop installation inside the chroot before upgrading
6623 it. To ensure no services are started in the chroot, a policy-rc.d
6624 script is inserted. To make sure tasksel believe it is to install a
6625 desktop on a laptop, the tasksel tests are replaced in the chroot
6626 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
6627
6628 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6629 currently always fail because udev refuses to upgrade with the kernel
6630 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6631 is created. The bug report
6632 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
6633 this problem do not trigger in a chroot, but I touch the file anyway
6634 to make sure the upgrade go well. Testing on virtual and real
6635 hardware have failed me because of udev so far, and creating this file
6636 do the trick in such settings anyway. This is a
6637 &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
6638 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
6639 maintainer because he lack the resources to rewrite udev to keep
6640 working with old kernels or something like that. I really wish the
6641 udev upstream would keep udev backwards compatible, to avoid such
6642 upgrade problem, but given that they fail to do so, I guess
6643 documenting the way out of this mess is the best option we got for
6644 Debian Squeeze.&lt;/p&gt;
6645
6646 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
6647 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
6648 trick:&lt;/p&gt;
6649
6650 &lt;blockquote&gt;&lt;pre&gt;
6651 #!/bin/sh
6652 set -ex
6653
6654 if [ &quot;$1&quot; ] ; then
6655 desktop=$1
6656 else
6657 desktop=gnome
6658 fi
6659
6660 from=lenny
6661 to=squeeze
6662
6663 exec &amp;lt; /dev/null
6664 unset LANG
6665 mirror=http://ftp.skolelinux.org/debian
6666 tmpdir=chroot-$from-upgrade-$to-$desktop
6667 fuser -mv .
6668 debootstrap $from $tmpdir $mirror
6669 chroot $tmpdir aptitude update
6670 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
6671 #!/bin/sh
6672 exit 101
6673 EOF
6674 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6675 exit_cleanup() {
6676 umount $tmpdir/proc
6677 }
6678 mount -t proc proc $tmpdir/proc
6679 # Make sure proc is unmounted also on failure
6680 trap exit_cleanup EXIT INT
6681
6682 chroot $tmpdir aptitude -y install debconf-utils
6683
6684 # Make sure tasksel autoselection trigger. It need the test scripts
6685 # to return the correct answers.
6686 echo tasksel tasksel/desktop multiselect $desktop | \
6687 chroot $tmpdir debconf-set-selections
6688
6689 # Include the desktop and laptop task
6690 for test in desktop laptop ; do
6691 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
6692 #!/bin/sh
6693 exit 2
6694 EOF
6695 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6696 done
6697
6698 DEBIAN_FRONTEND=noninteractive
6699 DEBIAN_PRIORITY=critical
6700 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6701 chroot $tmpdir tasksel --new-install
6702
6703 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
6704 chroot $tmpdir aptitude update
6705 touch $tmpdir/etc/udev/kernel-upgrade
6706 chroot $tmpdir aptitude -y dist-upgrade
6707 fuser -mv
6708 &lt;/pre&gt;&lt;/blockquote&gt;
6709
6710 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
6711 with aptitude, but I have not had time to look at how they behave
6712 differently so far. I hope to get a cron job running to do the test
6713 regularly and post the result on the web. The Gnome upgrade currently
6714 work, while the KDE upgrade fail because of the bug in
6715 kdebase-workspace-data&lt;/p&gt;
6716
6717 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
6718 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
6719 post, so I will refrain from trying. I can report that for Gnome,
6720 aptitude report 760 packages upgraded, 448 newly installed, 129 to
6721 remove and 1 not upgraded and 1024MB need to be downloaded while for
6722 KDE the same numbers are 702 packages upgraded, 507 newly installed,
6723 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
6724
6725 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
6726 is able to migrate to dependency based boot sequencing and parallel
6727 booting without a hitch. Was unsure if there were still bugs with
6728 packages failing to clean up their obsolete init.d script during
6729 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6730 packages.&lt;/p&gt;
6731 </description>
6732 </item>
6733
6734 <item>
6735 <title>Upstart or sysvinit - as init.d scripts see it</title>
6736 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
6737 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
6738 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
6739 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6740 scripts to migrate (some of) their operations to upstart job while
6741 keeping the init.d for hurd and kfreebsd. The packages with such
6742 needs will need a way to get their init.d scripts to behave
6743 differently when used with sysvinit and with upstart. Because of
6744 this, I had a look at the environment variables set when a init.d
6745 script is running under upstart, and when it is not.&lt;/p&gt;
6746
6747 &lt;p&gt;With upstart, I notice these environment variables are set when a
6748 script is started from rcS.d/ (ignoring some irrelevant ones like
6749 COLUMNS):&lt;/p&gt;
6750
6751 &lt;blockquote&gt;&lt;pre&gt;
6752 DEFAULT_RUNLEVEL=2
6753 previous=N
6754 PREVLEVEL=
6755 RUNLEVEL=
6756 runlevel=S
6757 UPSTART_EVENTS=startup
6758 UPSTART_INSTANCE=
6759 UPSTART_JOB=rc-sysinit
6760 &lt;/pre&gt;&lt;/blockquote&gt;
6761
6762 &lt;p&gt;With sysvinit, these environment variables are set for the same
6763 script.&lt;/p&gt;
6764
6765 &lt;blockquote&gt;&lt;pre&gt;
6766 INIT_VERSION=sysvinit-2.88
6767 previous=N
6768 PREVLEVEL=N
6769 RUNLEVEL=S
6770 runlevel=S
6771 &lt;/pre&gt;&lt;/blockquote&gt;
6772
6773 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
6774 sysvinit are not set by upstart. Not sure if it is intentional or not
6775 to not be compatible with sysvinit in this regard.&lt;/p&gt;
6776
6777 &lt;p&gt;For scripts needing to behave differently when upstart is used,
6778 looking for the UPSTART_JOB environment variable seem to be a good
6779 choice.&lt;/p&gt;
6780 </description>
6781 </item>
6782
6783 <item>
6784 <title>A manual for standards wars...</title>
6785 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
6786 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
6787 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
6788 <description>&lt;p&gt;Via the
6789 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
6790 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
6791 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
6792 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
6793 following the standards wars of today.&lt;/p&gt;
6794 </description>
6795 </item>
6796
6797 <item>
6798 <title>Sitesummary tip: Listing computer hardware models used at site</title>
6799 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
6800 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
6801 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
6802 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
6803 to get a list of the machine types in use thanks to the DMI
6804 information extracted from each machine. The script to do so is
6805 included in the sitesummary package, and here is example output from
6806 the Skolelinux build servers:&lt;/p&gt;
6807
6808 &lt;blockquote&gt;&lt;pre&gt;
6809 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6810 vendor count
6811 Dell Computer Corporation 1
6812 PowerEdge 1750 1
6813 IBM 1
6814 eserver xSeries 345 -[8670M1X]- 1
6815 Intel 2
6816 [no-dmi-info] 3
6817 maintainer:~#
6818 &lt;/pre&gt;&lt;/blockquote&gt;
6819
6820 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
6821 provided in each machine. Here there are Intel machines without model
6822 information listed with Intel as vendor and no model, and virtual Xen
6823 machines listed as [no-dmi-info]. One can add -l as a command line
6824 option to list the individual machines.&lt;/p&gt;
6825
6826 &lt;p&gt;A larger list is
6827 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
6828 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
6829 provide the basic sitesummary report publicly. In their report there
6830 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
6831 their machines, and as sitesummary is available in both distributions,
6832 it is trivial to get all of them to report to the same central
6833 collector.&lt;/p&gt;
6834 </description>
6835 </item>
6836
6837 <item>
6838 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
6839 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
6840 <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>
6841 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
6842 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
6843 start at boot when an NVidia video card is used is handled. The
6844 problem seem to be that the nvidia X.org driver uses a long time to
6845 initialize, and this duration is longer than kdm is configured to
6846 wait.&lt;/p&gt;
6847
6848 &lt;p&gt;I came across two bugs related to this issue,
6849 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
6850 against initscripts and passed on to nvidia-glx when it became obvious
6851 that the nvidia drivers were involved, and
6852 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
6853 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
6854
6855 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
6856 problem nvidia video card owners experience and make sure the Debian
6857 distribution work out of the box for these users. The nvidia driver
6858 maintainers expect kdm to be set up to wait longer, while kdm expect
6859 the nvidia driver maintainers to fix the driver to start faster, and
6860 while they wait for each other I guess the users end up switching to a
6861 distribution that work for them. I have no idea what the solution is,
6862 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
6863
6864 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
6865 </description>
6866 </item>
6867
6868 <item>
6869 <title>Parallellized boot seem to hold up well in Debian/testing</title>
6870 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
6871 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
6872 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
6873 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
6874 The feature seem to hold up pretty well, but three fairly serious
6875 issues are known and should be solved:
6876
6877 &lt;p&gt;&lt;ul&gt;
6878
6879 &lt;li&gt;The wicd package seen to
6880 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
6881 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
6882 parallel booting is enabled. No idea why, but the wicd maintainer
6883 seem to be on the case.&lt;/li&gt;
6884
6885 &lt;li&gt;The nvidia X driver seem to
6886 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
6887 triggered more easily when parallel booting is in effect. The
6888 maintainer is on the case.&lt;/li&gt;
6889
6890 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
6891 sequencing (the shutdown is broken) when old file-rc users
6892 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
6893 sysv-rc. One way to solve it would be for file-rc to create
6894 /etc/init.d/.legacy-bootordering, and another is to try to make
6895 sysv-rc more robust. Will investigate some more and probably upload a
6896 workaround in sysv-rc to help those trying to move from file-rc to
6897 sysv-rc get a working shutdown.&lt;/li&gt;
6898
6899 &lt;/ul&gt;&lt;/p&gt;
6900
6901 &lt;p&gt;All in all not many surprising issues, and all of them seem
6902 solvable before Squeeze is released. In addition to these there are
6903 some packages with bugs in their dependencies and run level settings,
6904 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
6905
6906 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6907 the BTS, please usertag the report to get it to show up at
6908 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6909 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6910
6911 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
6912 </description>
6913 </item>
6914
6915 <item>
6916 <title>More flexible firmware handling in debian-installer</title>
6917 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
6918 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
6919 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
6920 <description>&lt;p&gt;After a long break from debian-installer development, I finally
6921 found time today to return to the project. Having to spend less time
6922 working dependency based boot in debian, as it is almost complete now,
6923 definitely helped freeing some time.&lt;/p&gt;
6924
6925 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
6926 include some firmware packages on the Debian Edu CDs, those needed to
6927 get disk and network controllers working. Without having these
6928 firmware packages available during installation, it is impossible to
6929 install Debian Edu on the given machine, and because our target group
6930 are non-technical people, asking them to provide firmware packages on
6931 an external medium is a support pain. Initially, I expected it to be
6932 enough to include the firmware packages on the CD to get
6933 debian-installer to find and use them. This proved to be wrong.
6934 Next, I hoped it was enough to symlink the relevant firmware packages
6935 to some useful location on the CD (tried /cdrom/ and
6936 /cdrom/firmware/). This also proved to not work, and at this point I
6937 found time to look at the debian-installer code to figure out what was
6938 going to work.&lt;/p&gt;
6939
6940 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
6941 look revealed that it would only look for firmware packages outside
6942 the installation media, so the CD was never checked for firmware
6943 packages. It would only check USB sticks, floppies and other
6944 &quot;external&quot; media devices. Today I changed it to also look in the
6945 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6946 solve the problem I ran into with Debian edu. I also changed it to
6947 look in /firmware/, to make sure the installer also find firmware
6948 provided in the initrd when booting the installer via PXE, to allow us
6949 to provide the same feature in the PXE setup included in Debian
6950 Edu.&lt;/p&gt;
6951
6952 &lt;p&gt;To make sure firmware deb packages with a license questions are not
6953 activated without asking if the license is accepted, I extended
6954 hw-detect to look for preinst scripts in the firmware packages, and
6955 run these before activating the firmware during installation. The
6956 license question is asked using debconf in the preinst, so this should
6957 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
6958
6959 &lt;p&gt;If you want to discuss the details of these features, please
6960 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
6961 </description>
6962 </item>
6963
6964 <item>
6965 <title>Parallellized boot is now the default in Debian/unstable</title>
6966 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
6967 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
6968 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
6969 <description>&lt;p&gt;Since this evening, parallel booting is the default in
6970 Debian/unstable for machines using dependency based boot sequencing.
6971 Apparently the testing of concurrent booting has been wider than
6972 expected, if I am to believe the
6973 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6974 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
6975 with the feature this weekend, to give us some time to detect any
6976 remaining problems before Squeeze is frozen. If serious problems are
6977 detected, it is simple to change the default back to sequential boot.
6978 The upload of the new sysvinit package also activate a new upstream
6979 version.&lt;/p&gt;
6980
6981 More information about
6982 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6983 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
6984 currently possible to disable parallel booting when one run into
6985 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
6986
6987 &lt;blockquote&gt;&lt;pre&gt;
6988 CONCURRENCY=none
6989 &lt;/pre&gt;&lt;/blockquote&gt;
6990
6991 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6992 the BTS, please usertag the report to get it to show up at
6993 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6994 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6995 </description>
6996 </item>
6997
6998 <item>
6999 <title>Sitesummary tip: Listing MAC address of all clients</title>
7000 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7001 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7002 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7003 <description>&lt;p&gt;In the recent Debian Edu versions, the
7004 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7005 system&lt;/a&gt; is used to keep track of the machines in the school
7006 network. Each machine will automatically report its status to the
7007 central server after boot and once per night. The network setup is
7008 also reported, and using this information it is possible to get the
7009 MAC address of all network interfaces in the machines. This is useful
7010 to update the DHCP configuration.&lt;/p&gt;
7011
7012 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7013 ist all MAC addresses of all machines reporting to sitesummary. Run
7014 this on the collector host:&lt;/p&gt;
7015
7016 &lt;blockquote&gt;&lt;pre&gt;
7017 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7018 &lt;/pre&gt;&lt;/blockquote&gt;
7019
7020 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7021 line per machine and with space between the MAC addresses.&lt;/p&gt;
7022
7023 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7024 addresses for hosts, it would be possible to extend this to fetch
7025 machine information from sitesummary and update the DHCP and DNS
7026 tables in LDAP using this information. Such tool is unfortunately not
7027 written yet.&lt;/p&gt;
7028 </description>
7029 </item>
7030
7031 <item>
7032 <title>systemd, an interesting alternative to upstart</title>
7033 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7034 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7035 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7036 <description>&lt;p&gt;The last few days a new boot system called
7037 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7038 has been
7039 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7040
7041 to the free software world. I have not yet had time to play around
7042 with it, but it seem to be a very interesting alternative to
7043 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7044 a good alternative for Debian when we are able to switch to an event
7045 based boot system. Tollef is
7046 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7047 systemd into Debian, and I look forward to seeing how well it work. I
7048 like the fact that systemd handles init.d scripts with dependency
7049 information natively, allowing them to run in parallel where upstart
7050 at the moment do not.&lt;/p&gt;
7051
7052 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7053 platform support. It only work on recent Linux kernels, and also need
7054 some new kernel features enabled to function properly. This means
7055 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7056 system. Not sure how that will be handled if systemd proves to be the
7057 way forward.&lt;/p&gt;
7058
7059 &lt;p&gt;In the mean time, based on the
7060 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7061 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7062 decided to enable full parallel booting as the default in Debian as
7063 soon as possible (probably this weekend or early next week), to see if
7064 there are any remaining serious bugs in the init.d dependencies. A
7065 new version of the sysvinit package implementing this change is
7066 already in experimental. If all go well, Squeeze will be released
7067 with parallel booting enabled by default.&lt;/p&gt;
7068 </description>
7069 </item>
7070
7071 <item>
7072 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7073 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7074 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7075 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7076 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7077 complete, so complete that it is actually possible to run all the
7078 init.d scripts in parallell based on these dependencies. If you want
7079 to test your Squeeze system, make sure
7080 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7081 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7082 /etc/default/rcS:&lt;/p&gt;
7083
7084 &lt;blockquote&gt;&lt;pre&gt;
7085 CONCURRENCY=makefile
7086 &lt;/pre&gt;&lt;/blockquote&gt;
7087
7088 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7089 scripts in parallel using the dependency information stored in
7090 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7091 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7092 to try to start the kdm and gdm scripts as early as possible, and will
7093 start the facilities required by kdm or gdm as early as possible to
7094 make this happen.&lt;/p&gt;
7095
7096 &lt;p&gt;Give it a try, and see if you like the result. If some services
7097 fail to start properly, it is most likely because they have incomplete
7098 init.d script dependencies in their startup script (or some of their
7099 dependent scripts have incomplete dependencies). Report bugs and get
7100 the package maintainers to fix it. :)&lt;/p&gt;
7101
7102 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7103 manage to get the init.d script dependencies complete and correct. I
7104 expect we will get there in Squeeze+1, if we get manage to test and
7105 fix the remaining issues.&lt;/p&gt;
7106
7107 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7108 the BTS, please usertag the report to get it to show up at
7109 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7110 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7111 </description>
7112 </item>
7113
7114 <item>
7115 <title>Debian has switched to dependency based boot sequencing</title>
7116 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7118 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7119 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7120 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7121 have been migrated to using dependency based boot sequencing. This
7122 conclude work me and others have been doing for the last three days.
7123 It feels great to see this finally part of the default Debian
7124 installation. Now we just need to weed out the last few problems that
7125 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7126
7127 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7128 fixing the more fundamental problem of handing the event based
7129 non-predictable kernel in the early boot.&lt;/p&gt;
7130 </description>
7131 </item>
7132
7133 <item>
7134 <title>Taking over sysvinit development</title>
7135 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7136 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7137 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7138 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7139 the existing sysvinit upstream developer, I decided a few weeks ago to
7140 take over the package and become the new upstream. The number of
7141 patches to track for the Debian package was becoming a burden, and the
7142 lack of synchronization between the distribution made it hard to keep
7143 the package up to date.&lt;/p&gt;
7144
7145 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7146 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7147 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7148 and Fedora), based on the patches currently in use in these
7149 distributions. We Debian maintainers plan to move to this tarball as
7150 the new upstream as soon as we find time to do the merge. Since the
7151 new tarball was created, we agreed with Werner at SuSe to make a new
7152 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7153 development there. The project is registered and currently waiting
7154 for approval by the Savannah administrators, and as soon as it is
7155 approved, we will import the old versions from svn and continue
7156 working on the future release.&lt;/p&gt;
7157
7158 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7159 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7160 </description>
7161 </item>
7162
7163 <item>
7164 <title>Debian boots quicker and quicker</title>
7165 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7166 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7167 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7168 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7169 people involved in the boot system on Debian and Ubuntu, to see if we
7170 could find more ways to speed up the boot system. This was an Ubuntu
7171 funded
7172 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7173 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7174 of boot systems, and ways to handle the increasing number of boot
7175 issues introduced by the Linux kernel becoming more and more
7176 asynchronous and event base. The Ubuntu approach using udev and
7177 upstart might be a good way forward. Time will show.&lt;/p&gt;
7178
7179 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7180 process in Debian. All of these should be applied to get a quick
7181 boot:&lt;/p&gt;
7182
7183 &lt;ul&gt;
7184
7185 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7186
7187 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7188 clock is in UTC.&lt;/li&gt;
7189
7190 &lt;li&gt;Install and activate the insserv package to enable
7191 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7192 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7193
7194 &lt;/ul&gt;
7195
7196 These points are based on the Google summer of code work done by
7197 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7198 Villegas&lt;/a&gt;.
7199
7200 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7201 unstable yesterday. When we tested it, we were able to cut 6 seconds
7202 from the boot sequence. It depend on very correct dependency
7203 declaration in all init.d scripts, so I expect us to find edge cases
7204 where the dependences in some scripts are slightly wrong when we start
7205 using this.&lt;/p&gt;
7206
7207 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7208 introduced by Raphael Geissert today, one that could affect the
7209 startup speed as well. Instead of starting some scripts concurrently
7210 from rcS.d/ and another set of scripts from rc2.d/, it would be
7211 possible to run a of them in the same process. A quick way to test
7212 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7213 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7214 </description>
7215 </item>
7216
7217 <item>
7218 <title>BSAs påstander om piratkopiering møter motstand</title>
7219 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7220 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7221 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7222 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7223 programvareselskapene som Microsoft og Apple, publisert en rapport der
7224 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7225 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7226 dager siden kom
7227 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7228 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7229 dagene. Et spesielt interessant kommentar fra Sverige,
7230 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7231 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7232
7233 &lt;blockquote&gt;
7234 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7235 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7236 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7237 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7238 &lt;/blockquote&gt;
7239
7240 &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
7241 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7242 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7243 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7244 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7245
7246 &lt;p&gt;Fant lenkene via &lt;a
7247 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7248 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7249 </description>
7250 </item>
7251
7252 <item>
7253 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7254 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7255 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7256 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7257 <description>&lt;p&gt;Kom over
7258 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7259 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7260 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7261 jobber til daglig. En rask opptelling forteller meg at vi har 490
7262 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7263 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7264 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7265 </description>
7266 </item>
7267
7268 <item>
7269 <title>Kryptert harddisk - naturligvis</title>
7270 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7271 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7272 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7273 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7274 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7275 når en tar tap av arbeidstid, fortrolige dokumenter,
7276 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7277 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7278 til at jeg har kryptert harddisken på både kontormaskinen og min
7279 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7280 komme på avveie, den første informasjon relatert til jobben min ved
7281 Universitetet i Oslo, og den andre relatert til blant annet
7282 foreningsarbeide. Kryptering av diskene gjør at det er lite
7283 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7284 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7285 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7286 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7287 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7288 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7289 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7290 det er gjort slik jeg gjør det er minimale, og gevinstene er
7291 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7292 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7293
7294 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7295 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7296 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7297 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7298 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7299 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7300 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7301 betydelige.&lt;/p&gt;
7302 </description>
7303 </item>
7304
7305 <item>
7306 <title>Two projects that have improved the quality of free software a lot</title>
7307 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7308 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7309 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7310 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7311 quality of free software, and I wanted to mention both in case someone
7312 do not yet know them.&lt;/p&gt;
7313
7314 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7315 tool to detect and expose errors in the memory handling of programs.
7316 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7317 and it will report any problems on stdout. It is even better if the
7318 program include debug information. With debug information, it is able
7319 to report the source file name and line number where the problem
7320 occurs. It can report things like &#39;reading past memory block in file
7321 X line N, the memory block was allocated in file Y, line M&#39;, and
7322 &#39;using uninitialised value in control logic&#39;. This tool has made it
7323 trivial to investigate reproducible crash bugs in programs, and have
7324 reduced the number of this kind of bugs in free software a lot.
7325
7326 &lt;p&gt;The second one is
7327 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7328 a source code checker. It is able to process the source of a program
7329 and find problems in the logic without running the program. It
7330 started out as the Stanford Checker and became well known when it was
7331 used to find bugs in the Linux kernel. It is now a commercial tool
7332 and the company behind it is running
7333 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7334 free software community, where a lot of free software projects get
7335 their source checked for free. Several thousand defects have been
7336 found and fixed so far. It can find errors like &#39;lock L taken in file
7337 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7338 Y lines O to P can never be executed&#39;. The projects included in the
7339 community service project have managed to get rid of a lot of
7340 reliability problems thanks to Coverity.&lt;/p&gt;
7341
7342 &lt;p&gt;I believe tools like this, that are able to automatically find
7343 errors in the source, are vital to improve the quality of software and
7344 make sure we can get rid of the crashing and failing software we are
7345 surrounded by today.&lt;/p&gt;
7346 </description>
7347 </item>
7348
7349 <item>
7350 <title>No patch is not better than a useless patch</title>
7351 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7352 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7353 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7354 <description>&lt;p&gt;Julien Blache
7355 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7356 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7357 patch allow one to discuss a concrete and proposed solution, and also
7358 prove that the issue at hand is important enough for someone to spent
7359 time on fixing it. No patch do not provide any of these positive
7360 properties.&lt;/p&gt;
7361 </description>
7362 </item>
7363
7364 <item>
7365 <title>Standardize on protocols and formats, not vendors and applications</title>
7366 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7367 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7368 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7369 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7370 very good one to form a long lived computer infrastructure. It is the
7371 simple one, lost by many in todays computer industry: Standardize on
7372 open network protocols and open exchange/storage formats, not applications.
7373 Applications come and go, while protocols and files tend to stay, and
7374 thus one want to make it easy to change application and vendor, while
7375 avoiding conversion costs and locking users to a specific platform or
7376 application.&lt;/p&gt;
7377
7378 &lt;p&gt;This approach make it possible to replace the client applications
7379 independently of the server applications. One can even allow users to
7380 use several different applications as long as they handle the selected
7381 protocol and format. In the normal case, only one client application
7382 is recommended and users only get help if they choose to use this
7383 application, but those that want to deviate from the easy path are not
7384 blocked from doing so.&lt;/p&gt;
7385
7386 &lt;p&gt;It also allow us to replace the server side without forcing the
7387 users to replace their applications, and thus allow us to select the
7388 best server implementation at any moment, when scale and resouce
7389 requirements change.&lt;/p&gt;
7390
7391 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7392 open formats, but I would never recommend standardizing on a single
7393 application that do not use open network protocol or open formats.&lt;/p&gt;
7394 </description>
7395 </item>
7396
7397 <item>
7398 <title>Returning from Skolelinux developer gathering</title>
7399 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7400 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7401 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7402 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7403 Edu/Skolelinux development gathering. I got a bit done tuning the
7404 desktop, and looked into the dynamic service location protocol
7405 implementation avahi. It look like it could be useful for us. Almost
7406 30 people participated, and I believe it was a great environment to
7407 get to know the Skolelinux system. Walter Bender, involved in the
7408 development of the Sugar educational platform, presented his stuff and
7409 also helped me improve my OLPC installation. He also showed me that
7410 his Turtle Art application can be used in standalone mode, and we
7411 agreed that I would help getting it packaged for Debian. As a
7412 standalone application it would be great for Debian Edu. We also
7413 tried to get the video conferencing working with two OLPCs, but that
7414 proved to be too hard for us. The application seem to need more work
7415 before it is ready for me. I look forward to getting home and relax
7416 now. :)&lt;/p&gt;
7417 </description>
7418 </item>
7419
7420 <item>
7421 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7422 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7423 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7424 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7425 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7426 optimal. There is RFC 2307 documenting one way to store NIS maps in
7427 LDAP, and a modified version of this normally called RFC 2307bis, with
7428 some modifications to be compatible with Active Directory. The RFC
7429 specification handle the content of a lot of system databases, but do
7430 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7431
7432 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7433 we would like to store information about users, SMB clients/hosts,
7434 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7435 and LTSP configuration in LDAP. These objects have a lot in common,
7436 but with the current LDAP schemas it is not possible to have one
7437 object per entity. For example, one need to have at least three LDAP
7438 objects for a given computer, one with the SMB related stuff, one with
7439 DNS information and another with DHCP information. The schemas
7440 provided for DNS and DHCP are impossible to combine into one LDAP
7441 object. In addition, it is impossible to implement quick queries for
7442 netgroup membership, because of the way NIS triples are implemented.
7443 It just do not scale. I believe it is time for a few RFC
7444 specifications to cleam up this mess.&lt;/p&gt;
7445
7446 &lt;p&gt;I would like to have one LDAP object representing each computer in
7447 the network, and this object can then keep the SMB (ie host key), DHCP
7448 (mac address/name) and DNS (name/IP address) settings in one place.
7449 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7450
7451 &lt;p&gt;I would also like to have a quick way to map from a user or
7452 computer and to the net group this user or computer is a member.&lt;/p&gt;
7453
7454 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7455 in this regard, and the unix side need to catch up. Time to start a
7456 new IETF work group?&lt;/p&gt;
7457 </description>
7458 </item>
7459
7460 <item>
7461 <title>Endelig er Debian Lenny gitt ut</title>
7462 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7463 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7464 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7465 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7466 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7467 Et langt steg videre for Debian-prosjektet, og en rekke nye
7468 programpakker blir nå tilgjengelig for de av oss som bruker den
7469 stabile utgaven av Debian. Neste steg er nå å få
7470 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7471 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7472 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7473 slippes løs på skolene. Takk til alle debian-utviklerne som har
7474 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7475 bootsekvens tilgjengelig i stabil utgave, vha pakken
7476 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7477 </description>
7478 </item>
7479
7480 <item>
7481 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7482 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7483 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7484 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7485 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7486 Oslo. Most of Saturday was used for the general assemly for the
7487 member organization, but the rest of the weekend I used to tune the
7488 LTSP installation. LTSP now work out of the box on the 10-network.
7489 Acer Aspire One proved to be a very nice thin client, with both
7490 screen, mouse and keybard in a small box. Was working on getting the
7491 diskless workstation setup configured out of the box, but did not
7492 finish it before the weekend was up.&lt;/p&gt;
7493
7494 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7495 the Brazilian group, so that will have to wait for the next
7496 development gathering. Would love to have the Debian Edu installer
7497 automatically detect and configure a multiseat setup when it find one
7498 of these cards.&lt;/p&gt;
7499 </description>
7500 </item>
7501
7502 <item>
7503 <title>The sorry state of multimedia browser plugins in Debian</title>
7504 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7505 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7506 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7507 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7508 plugins available in Debian Lenny, to see which one we should use by
7509 default in Debian Edu. We need an embedded video playing plugin with
7510 control buttons to pause or stop the video, and capable of streaming
7511 all the multimedia content available on the web. The test results and
7512 notes are available on
7513 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7514 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7515 fill this need. My personal video player favorite, VLC, has a really
7516 bad plugin which fail on a lot of the test pages. A lot of the MIME
7517 types I would expect to work with any free software player (like
7518 video/ogg), just do not work. And simple formats like the
7519 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7520 totem and vlc plugins. I hope the situation will improve soon. No
7521 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7522
7523 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7524 be the only one fitting our needs. :/&lt;/p&gt;
7525 </description>
7526 </item>
7527
7528 </channel>
7529 </rss>