]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
f564d9d705ef1e33076912bb9bb568d1e1f3a6bd
[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>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
11 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
13 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
14 <description>&lt;p&gt;During this weekends
15 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
16 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
17 to make sure there are good books about Debian available in Norwegian
18 Bokmål, and got in touch with the people behind the
19 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
20 project&lt;/a&gt; to get started. If you want to help out, please start
21 contributing using
22 &lt;a href=&quot;https://hosted.weblate.org/translate/debian-handbook/&quot;&gt;the
23 hosted weblate project page&lt;/a&gt;, and get in touch using
24 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
25 translators mailing list&lt;/a&gt;. Please also check out
26 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
27 contributors&lt;/a&gt;.&lt;/p&gt;
28
29 &lt;p&gt;The book is already available on paper in English, French and
30 Japanese, and our goal is to get it available on paper in Norwegian
31 Bokmål too. In addition to the paper edition, there are also EPUB and
32 Mobi versions available. And there are incomplete translations
33 available for many more languages.&lt;/p&gt;
34 </description>
35 </item>
36
37 <item>
38 <title>One in two hundred Debian users using ZFS on Linux?</title>
39 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
40 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
41 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
42 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
43 packages in Debian, and was quite surprised with what I found. I use
44 ZFS myself at home, but did not really expect many others to do so.
45 But I might be wrong.&lt;/p&gt;
46
47 &lt;p&gt;According to
48 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
49 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
50 0.53% of the population, with the package installed. As far as I know
51 the only use of the spl-linux package is as a support library for ZFS
52 on Linux, so I use it here as proxy for measuring the number of ZFS
53 installation on Linux in Debian. In the kFreeBSD variant of Debian
54 the ZFS feature is already available, and there
55 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
56 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
57 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
58
59 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
60 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
61 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
62 cleared, the package is still not in Debian. The package is again in
63 the NEW queue. Several uploads have been rejected so far because the
64 debian/copyright file was incomplete or wrong, but there is no reason
65 to give up. The current status can be seen on
66 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
67 team status page&lt;/a&gt;, and
68 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
69 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
70
71 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
72 my home server can function in the future using only official Debian
73 packages, and the current blocker is to get the debian/copyright file
74 accepted by the FTP masters in Debian, I decided a while back to try
75 to help out the team. This was the background for my blog post about
76 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
77 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
78 used the techniques I explored there to try to find any errors in the
79 copyright file. It is not very easy to check every one of the around
80 2000 files in the source package, but I hope we this time got it
81 right. If you want to help out, check out the git source and try to
82 find missing entries in the debian/copyright file.&lt;/p&gt;
83 </description>
84 </item>
85
86 <item>
87 <title>Full battery stats collector is now available in Debian</title>
88 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
89 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
90 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
91 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
92 extended collector that will collect the complete battery history for
93 later processing and graphing. The original collector store the
94 battery level as percentage of last full level, while the new
95 collector also record battery vendor, model, serial number, design
96 full level, last full level and current battery level. This make it
97 possible to predict the lifetime of the battery as well as visualise
98 the energy flow when the battery is charging or discharging.&lt;/p&gt;
99
100 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
101 in the version 0.5.1 package in unstable. Get the new battery level graph
102 and lifetime prediction by running:
103
104 &lt;p&gt;&lt;pre&gt;
105 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
106 &lt;/pre&gt;&lt;/p&gt;
107
108 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
109
110 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
111 entry yet):&lt;/p&gt;
112
113 &lt;p&gt;&lt;pre&gt;
114 /usr/share/battery-stats/battery-stats-graph-flow
115 &lt;/pre&gt;&lt;/p&gt;
116
117 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
118 when there are few data points. The graphs look a bit better with a
119 few years of data.&lt;/p&gt;
120
121 &lt;p&gt;A while back one important feature I use in the battery stats
122 collector broke in Debian. The scripts in
123 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
124 suspect it happened when Jessie started using systemd, but I do not
125 know. The issue is reported as
126 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
127 pm-utils. I managed to work around it by adding an udev rule to call
128 the collector script every time the power connector is connected and
129 disconnected. With this fix in place it was finally time to make a
130 new release of the package, and get it into Debian.&lt;/p&gt;
131
132 &lt;p&gt;If you are interested in how your laptop battery is doing, please
133 check out the
134 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
135 in Debian unstable, or rebuild it on Jessie to get it working on
136 Debian stable. :) The upstream source is available from
137 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
138 As always, patches are very welcome.&lt;/p&gt;
139 </description>
140 </item>
141
142 <item>
143 <title>Making battery measurements a little easier in Debian</title>
144 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
145 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
146 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
147 <description>&lt;p&gt;Back in September, I blogged about
148 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
149 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
150 how it showed the decay and death of this battery (now replaced). I
151 created a simple deb package to handle the collection and graphing,
152 but did not want to upload it to Debian as there were already
153 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
154 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
155 a point of uploading a competing package when battery-stats could be
156 fixed instead. I reported a few bugs about its non-function, and
157 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
158
159 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
160 hands. The end result is that I am now the new upstream developer of
161 battery stats (&lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;available from github&lt;/a&gt;) and part of the team maintaining
162 battery-stats in Debian, and the package in Debian unstable is finally
163 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
164 information provided by the Linux kernel. If you install the
165 battery-stats package from unstable now, you will be able to get a
166 graph of the current battery fill level, to get some idea about the
167 status of the battery. The source package build and work just fine in
168 Debian testing and stable (and probably oldstable too, but I have not
169 tested). The default graph you get for that system look like this:&lt;/p&gt;
170
171 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png&quot; width=&quot;70%&quot; align=&quot;center&quot;&gt;&lt;/p&gt;
172
173 &lt;p&gt;My plans for the future is to merge my old scripts into the
174 battery-stats package, as my old scripts collected a lot more details
175 about the battery. The scripts are merged into the upstream
176 battery-stats git repository already, but I am not convinced they work
177 yet, as I changed a lot of paths along the way. Will have to test a
178 bit more before I make a new release.&lt;/p&gt;
179
180 &lt;p&gt;I will also consider changing the file format slightly, as I
181 suspect the way I combine several values into one field might make it
182 impossible to know the type of the value when using it for processing
183 and graphing.&lt;/p&gt;
184
185 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
186 battery, check out the battery-stats package in
187 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
188 on
189 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
190 I would love some help to improve the system further.&lt;/p&gt;
191 </description>
192 </item>
193
194 <item>
195 <title>Creating, updating and checking debian/copyright semi-automatically</title>
196 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
197 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
198 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
199 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
200 details. And one of the details is the content of the
201 debian/copyright file, which should list all relevant licenses used by
202 the code in the package in question, preferably in
203 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
204 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
205
206 &lt;p&gt;For large packages with lots of contributors it is hard to write
207 and update this file manually, and if you get some detail wrong, the
208 package is normally rejected by the ftpmasters. So getting it right
209 the first time around get the package into Debian faster, and save
210 both you and the ftpmasters some work.. Today, while trying to figure
211 out what was wrong with
212 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
213 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
214 figuring out the options for doing this job automatically, or at least
215 semi-automatically.&lt;/p&gt;
216
217 &lt;p&gt;Lucikly, there are at least two tools available for generating the
218 file based on the code in the source package,
219 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
220 and &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/cme&quot;&gt;cme&lt;/a&gt;&lt;/tt&gt;. I&#39;m
221 not sure which one of them came first, but both seem to be able to
222 create a sensible draft file. As far as I can tell, none of them can
223 be trusted to get the result just right, so the content need to be
224 polished a bit before the file is OK to upload. I found the debmake
225 option in
226 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
227 blog posts from 2014&lt;/a&gt;.
228
229 &lt;p&gt;To generate using debmake, use the -cc option:
230
231 &lt;p&gt;&lt;pre&gt;
232 debmake -cc &gt; debian/copyright
233 &lt;/pre&gt;&lt;/p&gt;
234
235 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
236 this might not be the best option.&lt;/p&gt;
237
238 &lt;p&gt;The cme option is based on a config parsing library, and I found
239 this approach in
240 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
241 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
242 dpkg-copyright&#39; option:
243
244 &lt;p&gt;&lt;pre&gt;
245 cme update dpkg-copyright
246 &lt;/pre&gt;&lt;/p&gt;
247
248 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
249 handle UTF-8 names better than debmake.&lt;/p&gt;
250
251 &lt;p&gt;When the copyright file is created, I would also like some help to
252 check if the file is correct. For this I found two good options,
253 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
254 to focus on license types and file matching, and is able to detect
255 ineffective blocks in the copyright file. The latter reports missing
256 copyright holders and years, but was confused by inconsistent license
257 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
258 fix all issues reported by them before uploading. But I do not know
259 if the tools and the ftpmasters agree on what is important to fix in a
260 copyright file, so the package might still be rejected.&lt;/p&gt;
261
262 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
263 will read through the source and try to find all copyright statements.
264 It is not comparing the result to the content of debian/copyright, but
265 can be useful when verifying the content of the copyright file.&lt;/p&gt;
266
267 &lt;p&gt;Are you aware of better tools in Debian to create and update
268 debian/copyright file. Please let me know, or blog about it on
269 planet.debian.org.&lt;/p&gt;
270
271 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
272 activities, please send Bitcoin donations to my address
273 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
274
275 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
276 on how to use licensecheck and cdbs to create a draft copyright file
277
278 &lt;p&gt;&lt;pre&gt;
279 licensecheck --copyright -r `find * -type f` | \
280 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
281 &lt;/pre&gt;&lt;/p&gt;
282
283 &lt;p&gt;He mentioned that he normally check the generated file into the
284 version control system to make it easier to discover license and
285 copyright changes in the upstream source. I will try to do the same
286 with my packages in the future.&lt;/p&gt;
287
288 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
289 against using -quiet for new users, so I removed it from the proposed
290 command line.&lt;/p&gt;
291 </description>
292 </item>
293
294 <item>
295 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
296 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
297 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
298 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
299 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
300 is taking shape in Debian, and one provided feature is a very
301 convenient way to tell you which package to install to make a given
302 firmware file available when the kernel is looking for it. This can
303 be done using apt-file too, but that is for someone else to blog
304 about. :)&lt;/p&gt;
305
306 &lt;p&gt;Here is a small recipe to find the package with a given firmware
307 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
308 picked from the set of firmware announced using appstream in Debian
309 unstable. In general you would be looking for the firmware requested
310 by the kernel during kernel module loading. To find the package
311 providing the example file, do like this:&lt;/p&gt;
312
313 &lt;blockquote&gt;&lt;pre&gt;
314 % apt install appstream
315 [...]
316 % apt update
317 [...]
318 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
319 awk &#39;/Package:/ {print $2}&#39;
320 firmware-qlogic
321 %
322 &lt;/pre&gt;&lt;/blockquote&gt;
323
324 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
325 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
326 a way appstream can use.&lt;/p&gt;
327
328 &lt;p&gt;This same approach can be used to find any package supporting a
329 given MIME type. This is very useful when you get a file you do not
330 know how to handle. First find the mime type using &lt;tt&gt;file
331 --mime-type&lt;/tt&gt;, and next look up the package providing support for
332 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
333 and you can find all packages handling this type like this:&lt;/p&gt;
334
335 &lt;blockquote&gt;&lt;pre&gt;
336 % apt install appstream
337 [...]
338 % apt update
339 [...]
340 % appstreamcli what-provides mimetype image/svg+xml | \
341 awk &#39;/Package:/ {print $2}&#39;
342 bkchem
343 phototonic
344 inkscape
345 shutter
346 tetzle
347 geeqie
348 xia
349 pinta
350 gthumb
351 karbon
352 comix
353 mirage
354 viewnior
355 postr
356 ristretto
357 kolourpaint4
358 eog
359 eom
360 gimagereader
361 midori
362 %
363 &lt;/pre&gt;&lt;/blockquote&gt;
364
365 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
366 packages providing appstream metadata.&lt;/p&gt;
367 </description>
368 </item>
369
370 <item>
371 <title>Creepy, visualise geotagged social media information - nice free software</title>
372 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
373 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
374 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
375 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
376 with the computerised radio beacon known as a mobile phone their
377 position is tracked by the phone company and often stored for a long
378 time (like every time a SMS is received or sent). And if their
379 computerised radio beacon is capable of running programs (often called
380 mobile apps) downloaded from the Internet, these programs are often
381 also capable of tracking their location (if the app requested access
382 during installation). And when these programs send out information to
383 central collection points, the location is often included, unless
384 extra care is taken to not send the location. The provided
385 information is used by several entities, for good and bad (what is
386 good and bad, depend on your point of view). What is certain, is that
387 the private sphere and the right to free movement is challenged and
388 perhaps even eradicated for those announcing their location this way,
389 when they share their whereabouts with private and public
390 entities.&lt;/p&gt;
391
392 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png&quot;&gt;&lt;/p&gt;
393
394 &lt;p&gt;The phone company logs provide a register of locations to check out
395 when one want to figure out what the tracked person was doing. It is
396 unavailable for most of us, but provided to selected government
397 officials, company staff, those illegally buying information from
398 unfaithful servants and crackers stealing the information. But the
399 public information can be collected and analysed, and a free software
400 tool to do so is called
401 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
402 discovered it when I read
403 &lt;a href=&quot;http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html&quot;&gt;an
404 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
405 November 2014, and decided to check if it was available in Debian.
406 The python program was in Debian, but
407 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
408 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
409 uploaded a new version which did not work quite right, but did not
410 have time to fix it then. This Christmas I decided to finally try to
411 get Creepy operational in Debian. Now a fixed version is available in
412 Debian unstable and testing, and almost all Debian specific patches
413 are now included
414 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
415
416 &lt;p&gt;The Creepy program visualises geolocation information fetched from
417 Twitter, Instagram, Flickr and Google+, and allow one to get a
418 complete picture of every social media message posted recently in a
419 given area, or track the movement of a given individual across all
420 these services. Earlier it was possible to use the search API of at
421 least some of these services without identifying oneself, but these
422 days it is impossible. This mean that to use Creepy, you need to
423 configure it to log in as yourself on these services, and provide
424 information to them about your search interests. This should be taken
425 into account when using Creepy, as it will also share information
426 about yourself with the services.&lt;/p&gt;
427
428 &lt;p&gt;The picture above show the twitter messages sent from (or at least
429 geotagged with a position from) the city centre of Oslo, the capital
430 of Norway. One useful way to use Creepy is to first look at
431 information tagged with an area of interest, and next look at all the
432 information provided by one or more individuals who was in the area.
433 I tested it by checking out which celebrity provide their location in
434 twitter messages by checkout out who sent twitter messages near a
435 Norwegian TV station, and next could track their position over time,
436 making it possible to locate their home and work place, among other
437 things. A similar technique have been
438 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
439 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
440 tool to discover lying governments, and a useful tool to help people
441 understand the value of the private information they provide to the
442 public.&lt;/p&gt;
443
444 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
445 it depend on several python modules currently missing in Jessie (at
446 least python-instagram, python-flickrapi and
447 python-requests-toolbelt).&lt;/p&gt;
448
449 &lt;p&gt;(I have uploaded
450 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
451 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
452 Creepy program in Debian.)&lt;/p&gt;
453 </description>
454 </item>
455
456 <item>
457 <title>Always download Debian packages using Tor - the simple recipe</title>
458 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
460 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
461 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
462 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
463 that those listening on the Internet lines would have good reason to
464 believe a computer have a given security hole&lt;/a&gt; if it download a
465 security fix from a Debian mirror. This is a good reason to always
466 use encrypted connections to the Debian mirror, to make sure those
467 listening do not know which IP address to attack. In August, Richard
468 Hartmann observed that encryption was not enough, when it was possible
469 to interfere download size to security patches or the fact that
470 download took place shortly after a security fix was released, and
471 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
472 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
473 was not the first to propose this, as the
474 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/apt-transport-tor&quot;&gt;apt-transport-tor&lt;/a&gt;&lt;/tt&gt;
475 package by Tim Retout already existed to make it easy to convince apt
476 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
477 aware of that package when I read the blog post from Richard.&lt;/p&gt;
478
479 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
480 sysadmins, and he set up a Tor hidden service on one of the central
481 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
482 it possible to download packages directly between two tor nodes,
483 making sure the network traffic always were encrypted.&lt;/p&gt;
484
485 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
486 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
487 urls with tor+http and tor+https, and using the hidden service instead
488 of the official Debian mirror site. I recommend installing
489 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
490 done in /etc/.&lt;/p&gt;
491
492 &lt;blockquote&gt;&lt;pre&gt;
493 apt install apt-transport-tor
494 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
495 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
496 &lt;/pre&gt;&lt;/blockquote&gt;
497
498 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
499 the sed commands for these too. The sed command is assuming your are
500 using the ftp.debian.org Debian mirror. Adjust the command (or just
501 edit the file manually) to match your mirror.&lt;/p&gt;
502
503 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
504 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
505 system, and do not work with these tor+http URLs. For
506 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
507 which need a recent apt version currently only in unstable. So if you
508 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
509
510 &lt;p&gt;Another advantage from this change is that your machine will start
511 using Tor regularly and at fairly random intervals (every time you
512 update the package lists or upgrade or install a new package), thus
513 masking other Tor traffic done from the same machine. Using Tor will
514 become normal for the machine in question.&lt;/p&gt;
515
516 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
517 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
518 enabled. It would be great if it was the default on any Debian
519 system.&lt;/p&gt;
520 </description>
521 </item>
522
523 <item>
524 <title>OpenALPR, find car license plates in video streams - nice free software</title>
525 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
526 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
527 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
528 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
529 call the car license plate numbers in those days. I would write the
530 numbers down in my little book and compare notes with the other kids
531 to see how many region codes we had seen and if we had seen some
532 exotic or special region codes and numbers. It was a fun game to pass
533 time, as we kids have plenty of it.&lt;/p&gt;
534
535 &lt;p&gt;A few days I came across
536 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
537 project&lt;/a&gt;, a free software project to automatically discover and
538 report license plates in images and video streams, and provide the
539 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
540 such system for a while now, because I believe it is a bad idea that the
541 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
542 number plate recognition&lt;/a&gt; tool only is available in the hands of
543 the powerful, and want it to be available also for the powerless to
544 even the score when it comes to surveillance and sousveillance. I
545 discovered the developer
546 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
547 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
548 help him get it into shape to get the package uploaded into the Debian
549 archive.&lt;/p&gt;
550
551 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
552 it into Debian, where it currently
553 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
554 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
555
556 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
557 for the common folks, ie those not running a large government
558 surveillance system? Well, I plan to put it in a computer on my bike
559 and in my car, tracking the cars nearby and allowing me to be notified
560 when number plates on my watch list are discovered. Another use case
561 was suggested by a friend of mine, who wanted to set it up at his home
562 to open the car port automatically when it discovered the plate on his
563 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
564 capable of placing his license plate number of a piece of cardboard to
565 open his car port, men replied that it was always unlocked anyway. I
566 guess for such use case it make sense. I am sure there are other use
567 cases too, for those with imagination and a vision.&lt;/p&gt;
568
569 &lt;p&gt;If you want to build your own version of the Debian package, check
570 out the upstream git source and symlink ./distros/debian to ./debian/
571 before running &quot;debuild&quot; to build the source. Or wait a bit until the
572 package show up in unstable.&lt;/p&gt;
573 </description>
574 </item>
575
576 <item>
577 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
578 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
579 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
580 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
581 <description>&lt;p&gt;Around three years ago, I created
582 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
583 system&lt;/a&gt; to get a more practical solution in Debian for handing
584 hardware related packages. A GUI system in the isenkram package will
585 present a pop-up dialog when some hardware dongle supported by
586 relevant packages in Debian is inserted into the machine. The same
587 lookup mechanism to detect packages is available as command line
588 tools in the isenkram-cli package. In addition to mapping hardware,
589 it will also map kernel firmware files to packages and make it easy to
590 install needed firmware packages automatically. The key for this
591 system to work is a good way to map hardware to packages, in other
592 words, allow packages to announce what hardware they will work
593 with.&lt;/p&gt;
594
595 &lt;p&gt;I started by providing data files in the isenkram source, and
596 adding code to download the latest version of these data files at run
597 time, to ensure every user had the most up to date mapping available.
598 I also added support for storing the mapping in the Packages file in
599 the apt repositories, but did not push this approach because while I
600 was trying to figure out how to best store hardware/package mappings,
601 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
602 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
603 add the hardware mapping into that data set to be able to use
604 appstream as a data source, and this was accepted at least for the
605 Debian version of appstream.&lt;/p&gt;
606
607 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
608 and today I uploaded a new version 0.20 of isenkram adding support for
609 appstream as a data source for mapping hardware to packages. The only
610 package so far using appstream to announce its hardware support is my
611 pymissile package. I got help from Matthias Klumpp with figuring out
612 how do add the required
613 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
614 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
615 this content:&lt;/p&gt;
616
617 &lt;blockquote&gt;&lt;pre&gt;
618 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
619 &amp;lt;component&amp;gt;
620 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
621 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
622 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
623 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
624 &amp;lt;description&amp;gt;
625 &amp;lt;p&amp;gt;
626 Pymissile provides a curses interface to control an original
627 Marks and Spencer / Striker USB Missile Launcher, as well as a
628 motion control script to allow a webcamera to control the
629 launcher.
630 &amp;lt;/p&amp;gt;
631 &amp;lt;/description&amp;gt;
632 &amp;lt;provides&amp;gt;
633 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
634 &amp;lt;/provides&amp;gt;
635 &amp;lt;/component&amp;gt;
636 &lt;/pre&gt;&lt;/blockquote&gt;
637
638 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
639 which is a glob style match rule for hardware specific strings
640 (modalias strings) provided by the Linux kernel. In this case, it
641 will map to all USB devices with vendor code 1130 and product code
642 0202.&lt;/p&gt;
643
644 &lt;p&gt;Note, it is important that the license of all the metadata files
645 are compatible to have permissions to aggregate them into archive wide
646 appstream files. Matthias suggested to use MIT or BSD licenses for
647 these files. A challenge is figuring out a good id for the data, as
648 it is supposed to be globally unique and shared across distributions
649 (in other words, best to coordinate with upstream what to use). But
650 it can be changed later or, so we went with the package name as
651 upstream for this project is dormant.&lt;/p&gt;
652
653 &lt;p&gt;To get the metadata file installed in the correct location for the
654 mirror update scripts to pick it up and include its content the
655 appstream data source, the file must be installed in the binary
656 package under /usr/share/appdata/. I did this by adding the following
657 line to debian/pymissile.install:&lt;/p&gt;
658
659 &lt;blockquote&gt;&lt;pre&gt;
660 debian/pymissile.metainfo.xml usr/share/appdata
661 &lt;/pre&gt;&lt;/blockquote&gt;
662
663 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
664 all packages useful on the current computer automatically, and the GUI
665 pop-up handler will propose to install the package not already
666 installed if a hardware dongle is inserted into the machine in
667 question.&lt;/p&gt;
668
669 &lt;p&gt;Details of the modalias field in appstream is available from the
670 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
671
672 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
673 try running this command on the command line:&lt;/p&gt;
674
675 &lt;blockquote&gt;&lt;pre&gt;
676 cat $(find /sys/devices/|grep modalias)
677 &lt;/pre&gt;&lt;/blockquote&gt;
678
679 &lt;p&gt;To learn more about the isenkram system, please check out
680 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
681 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
682 </description>
683 </item>
684
685 <item>
686 <title>The GNU General Public License is not magic pixie dust</title>
687 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
688 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
689 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
690 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
691 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
692 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
693 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
694 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
695
696 &lt;blockquote&gt;
697
698 &lt;p&gt;&lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;&lt;img src=&quot;https://sfconservancy.org/img/supporter-badge.png&quot; width=&quot;194&quot; height=&quot;90&quot; alt=&quot;Become a Software Freedom Conservancy Supporter!&quot; align=&quot;right&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
699
700 &lt;blockquote&gt;
701 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
702
703 The first step is to choose a
704 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
705 code.&lt;br/&gt;
706
707 The next step is, when someone fails to follow that copyleft license,
708 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
709
710 and its a simple fact of our modern society that such type of
711 work&lt;br/&gt;
712
713 is incredibly expensive to do and incredibly difficult to do.
714 &lt;/blockquote&gt;
715
716 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
717 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
718 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
719 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
720
721 &lt;p&gt;As the Debian Website
722 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
723 &lt;a href=&quot;https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&amp;amp;r2=1.25&quot;&gt;to&lt;/a&gt;
724 imply, public domain and permissively licensed software can lead to
725 the production of more proprietary software as people discover useful
726 software, extend it and or incorporate it into their hardware or
727 software products. Copyleft licenses such as the GNU GPL were created
728 to close off this avenue to the production of proprietary software but
729 such licenses are not enough. With the ongoing adoption of Free
730 Software by individuals and groups, inevitably the community&#39;s
731 expectations of license compliance are violated, usually out of
732 ignorance of the way Free Software works, but not always. As Karen
733 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
734 Freedom&quot;&gt;FaiF&lt;/a&gt;
735 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
736 copyleft is nothing if no-one is willing and able to stand up in court
737 to protect it. The reality of today&#39;s world is that legal
738 representation is expensive, difficult and time consuming. With
739 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
740 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
741 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
742 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
743 of the Linux project, Debian and other groups against GPL violations.
744 In March the SFC supported a
745 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
746 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
747 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
748 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
749 kernel. Since then two of their sponsors pulled corporate funding and
750 conferences
751 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
752 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
753 less on corporate funding and more on the broad community of
754 individuals who support Free Software and copyleft. So the SFC has
755 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
756 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
757 a community of folks who stand up for copyleft and the GPL by
758 supporting their work on promoting and supporting copyleft and Free
759 Software.&lt;/p&gt;
760
761 &lt;p&gt;If you support Free Software,
762 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
763 what the SFC do, agree with their
764 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
765 principles&lt;/a&gt;, are happy about their
766 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
767 work on a project that is an SFC
768 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
769 just want to stand up for copyleft, please join
770 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
771 Allan Webber&lt;/a&gt;,
772 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
773 Smith&lt;/a&gt;,
774 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
775 Bacon&lt;/a&gt;, myself and
776 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
777 becoming a
778 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
779 next week your donation will be
780 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
781 by an anonymous donor. Please also consider asking your employer to
782 match your donation or become a sponsor of SFC. Don&#39;t forget to
783 spread the word about your support for SFC via email, your blog and or
784 social media accounts.&lt;/p&gt;
785
786 &lt;/blockquote&gt;
787
788 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
789 of Software Freedom Conservancy myself. Perhaps you should be a
790 supporter too?&lt;/p&gt;
791 </description>
792 </item>
793
794 <item>
795 <title>PGP key transition statement for key EE4E02F9</title>
796 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
797 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
798 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
799 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
800 set it up properly. I wanted to generate it offline and have it
801 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
802 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
803 time to sit down with an offline machine almost took forever. But
804 finally I&#39;ve been able to complete the process, and have now moved
805 from my old GPG key to a new GPG key. See
806 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
807 full transition statement, signed with both my old and new key&lt;/a&gt; for
808 the details. This is my new key:&lt;/p&gt;
809
810 &lt;pre&gt;
811 pub 3936R/&lt;a href=&quot;http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html&quot;&gt;111D6B29EE4E02F9&lt;/a&gt; 2015-11-03 [expires: 2019-11-14]
812 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
813 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
814 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
815 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
816 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
817 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
818 &lt;/pre&gt;
819
820 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
821 my old key.&lt;/p&gt;
822
823 &lt;p&gt;If you signed my old key
824 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
825 I&#39;d very much appreciate a signature on my new key, details and
826 instructions in the transition statement. I m happy to reciprocate if
827 you have a similarly signed transition statement to present.&lt;/p&gt;
828 </description>
829 </item>
830
831 <item>
832 <title>The life and death of a laptop battery</title>
833 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
834 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
835 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
836 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
837 But this do not last. The last few laptops gave me a feeling that
838 within a year, the life time is just a fraction of what it used to be,
839 and it slowly become painful to use the laptop without power connected
840 all the time. Because of this, when I got a new Thinkpad X230 laptop
841 about two years ago, I decided to monitor its battery state to have
842 more hard facts when the battery started to fail.&lt;/p&gt;
843
844 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
845
846 &lt;p&gt;First I tried to find a sensible Debian package to record the
847 battery status, assuming that this must be a problem already handled
848 by someone else. I found
849 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
850 which collects statistics from the battery, but it was completely
851 broken. I sent a few suggestions to the maintainer, but decided to
852 write my own collector as a shell script while I waited for feedback
853 from him. Via
854 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
855 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
856 discovered
857 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
858 available in Debian.&lt;/p&gt;
859
860 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
861 battery stats ever since. Now my
862 /var/log/hjemmenett-battery-status.log file contain around 115,000
863 measurements, from the time the battery was working great until now,
864 when it is unable to charge above 7% of original capacity. My
865 collector shell script is quite simple and look like this:&lt;/p&gt;
866
867 &lt;pre&gt;
868 #!/bin/sh
869 # Inspired by
870 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
871 # See also
872 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
873 logfile=/var/log/hjemmenett-battery-status.log
874
875 files=&quot;manufacturer model_name technology serial_number \
876 energy_full energy_full_design energy_now cycle_count status&quot;
877
878 if [ ! -e &quot;$logfile&quot; ] ; then
879 (
880 printf &quot;timestamp,&quot;
881 for f in $files; do
882 printf &quot;%s,&quot; $f
883 done
884 echo
885 ) &gt; &quot;$logfile&quot;
886 fi
887
888 log_battery() {
889 # Print complete message in one echo call, to avoid race condition
890 # when several log processes run in parallel.
891 msg=$(printf &quot;%s,&quot; $(date +%s); \
892 for f in $files; do \
893 printf &quot;%s,&quot; $(cat $f); \
894 done)
895 echo &quot;$msg&quot;
896 }
897
898 cd /sys/class/power_supply
899
900 for bat in BAT*; do
901 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
902 done
903 &lt;/pre&gt;
904
905 &lt;p&gt;The script is called when the power management system detect a
906 change in the power status (power plug in or out), and when going into
907 and out of hibernation and suspend. In addition, it collect a value
908 every 10 minutes. This make it possible for me know when the battery
909 is discharging, charging and how the maximum charge change over time.
910 The code for the Debian package
911 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
912 available on github&lt;/a&gt;.&lt;/p&gt;
913
914 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
915
916 &lt;pre&gt;
917 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
918 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
919 [...]
920 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
921 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
922 &lt;/pre&gt;
923
924 &lt;p&gt;I wrote a small script to create a graph of the charge development
925 over time. This graph depicted above show the slow death of my laptop
926 battery.&lt;/p&gt;
927
928 &lt;p&gt;But why is this happening? Why are my laptop batteries always
929 dying in a year or two, while the batteries of space probes and
930 satellites keep working year after year. If we are to believe
931 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
932 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
933 chance, and the fix is to not charge the Lithium-ion batteries to 100%
934 all the time, but to stay below 90% of full charge most of the time.
935 I&#39;ve been told that the Tesla electric cars
936 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
937 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
938 100% when preparing for a longer trip (not that I would want a car
939 like Tesla where rights to privacy is abandoned, but that is another
940 story), which I guess is the option we should have for laptops on
941 Linux too.&lt;/p&gt;
942
943 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
944 stop charging at 80%, unless requested to charge to 100% once in
945 preparation for a longer trip? I found
946 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
947 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
948 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
949 load).&lt;/p&gt;
950
951 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
952 at the start. I also wonder why the &quot;full capacity&quot; increases some
953 times, and if it is possible to repeat the process to get the battery
954 back to design capacity. And I wonder if the discharge and charge
955 speed change over time, or if this stay the same. I did not yet try
956 to write a tool to calculate the derivative values of the battery
957 level, but suspect some interesting insights might be learned from
958 those.&lt;/p&gt;
959
960 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
961 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
962 packages instead of the tp-smapi-dkms package I had tried to use
963 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
964 and stop. I&#39;ve done so now, but expect my existing battery is toast
965 and need to be replaced. The proposal is unfortunately Thinkpad
966 specific.&lt;/p&gt;
967 </description>
968 </item>
969
970 <item>
971 <title>New laptop - some more clues and ideas based on feedback</title>
972 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
973 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
974 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
975 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
976 need for a new laptop, and provided very useful feedback. I wish to
977 thank every one of these. Several pointed me to the possibility of
978 fixing my X230, and I am already in the process of getting Lenovo to
979 do so thanks to the on site, next day support contract covering the
980 machine. But the battery is almost useless (I expect to replace it
981 with a non-official battery) and I do not expect the machine to live
982 for many more years, so it is time to plan its replacement. If I did
983 not have a support contract, it was suggested to find replacement parts
984 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
985 might present a language barrier as I do not understand French.&lt;/p&gt;
986
987 &lt;p&gt;One tip I got was to use the
988 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
989 compare laptop models. It seem to have more models available than
990 prisjakt.no. Another tip I got from someone I know have similar
991 keyboard preferences was that the HP EliteBook 840 keyboard is not
992 very good, and this matches my experience with earlier EliteBook
993 keyboards I tested. Because of this, I will not consider it any further.
994
995 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
996 newest Thinkpad X model. The keyboard reintroduces mouse buttons
997 (which is missing from the X240), and is working fairly well with
998 Debian Sid/Unstable according to
999 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
1000 got on the keyboard quality are not consistent. Some say the keyboard
1001 is good, others say it is ok, while others say it is not very good.
1002 Those with experience from X41 and and X60 agree that the X250
1003 keyboard is not as good as those trusty old laptops, and suggest I
1004 keep and fix my X230 instead of upgrading, or get a used X230 to
1005 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
1006 activity and battery status, which is very convenient on my X230. I&#39;m
1007 also told that the CPU fan is running very often, making it a bit
1008 noisy. In any case, the X250 do not work out of the box with Debian
1009 Stable/Jessie, one of my requirements.&lt;/p&gt;
1010
1011 &lt;p&gt;I have also gotten a few vendor proposals, one was
1012 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
1013 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
1014 The latter look very attractive to me.&lt;/p&gt;
1015
1016 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
1017 as I keep looking for a replacement.&lt;/p&gt;
1018
1019 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
1020 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
1021 different
1022 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
1023 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
1024 </description>
1025 </item>
1026
1027 <item>
1028 <title>Time to find a new laptop, as the old one is broken after only two years</title>
1029 <link>http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</link>
1030 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</guid>
1031 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
1032 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
1033 replacement soon. The left 5 cm of the screen on my Thinkpad X230
1034 started flickering yesterday, and I suspect the cause is a broken
1035 cable, as changing the angle of the screen some times get rid of the
1036 flickering.&lt;/p&gt;
1037
1038 &lt;p&gt;My requirements have not really changed since I bought it, and is
1039 still as
1040 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
1041 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
1042 good help from
1043 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
1044 where I could select at least a few of the requirements (mouse pin,
1045 wifi, weight) and go through the rest manually. Three button mouse
1046 and a good keyboard is not available as an option, and all the three
1047 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
1048 G2) lack three mouse buttons). It is also unclear to me how good the
1049 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1050 the keyboard, even if the quality and robustness in the X series have
1051 deteriorated since X41.&lt;/p&gt;
1052
1053 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
1054 seem sensible to me? Are there better services around to search the
1055 set of available laptops for features? Please send me an email if you
1056 have suggestions.&lt;/p&gt;
1057
1058 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
1059 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
1060 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
1061 </description>
1062 </item>
1063
1064 <item>
1065 <title>How to stay with sysvinit in Debian Jessie</title>
1066 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
1067 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
1068 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
1069 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
1070 sysvinit as its boot system by default. But how can one keep using
1071 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1072 courtesy of
1073 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
1074 Schubert&lt;/a&gt; and
1075 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
1076 McVittie&lt;/a&gt;.
1077
1078 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
1079 keep sysvinit as your boot system, create a file
1080 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
1081 you upgrade:&lt;/p&gt;
1082
1083 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1084 Package: systemd-sysv
1085 Pin: release o=Debian
1086 Pin-Priority: -1
1087 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1088
1089 &lt;p&gt;This file content will tell apt and aptitude to not consider
1090 installing systemd-sysv as part of any installation and upgrade
1091 solution when resolving dependencies, and thus tell it to avoid
1092 systemd as a default boot system. The end result should be that the
1093 upgraded system keep using sysvinit.&lt;/p&gt;
1094
1095 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
1096 get sysvinit installed by default (debootstrap used by
1097 debian-installer have no option for this), but one can tell the
1098 installer to switch to sysvinit before the first boot. Either by
1099 using a kernel argument to the installer, or by adding a line to the
1100 preseed file used. First, the kernel command line argument:
1101
1102 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1103 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
1104 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1105
1106 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
1107
1108 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1109 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1110 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1111
1112 &lt;p&gt;One can of course also do this after the first boot by installing
1113 the sysvinit-core package.&lt;/p&gt;
1114
1115 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
1116 sysvinit boot sequence in Debian have several hardware specific bugs
1117 on Linux caused by the fact that it is unpredictable when hardware
1118 devices show up during boot. But on the other hand, the new default
1119 boot system still have a few rough edges I hope will be fixed before
1120 Jessie is released.&lt;/p&gt;
1121
1122 &lt;p&gt;Update 2014-11-26: Inspired by
1123 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
1124 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
1125 line.&lt;/p&gt;
1126 </description>
1127 </item>
1128
1129 <item>
1130 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
1131 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
1132 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
1133 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
1134 <description>&lt;p&gt;The right to communicate with your friends and family in private,
1135 without anyone snooping, is a right every citicen have in a liberal
1136 democracy. But this right is under serious attack these days.&lt;/p&gt;
1137
1138 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
1139 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1140 the whisleblower Snowden) more expensive for Internet email,
1141 is to deliver all email using SMTP via Tor. Such SMTP option would be
1142 a nice addition to the FreedomBox project if we could send email
1143 between FreedomBox machines without leaking metadata about the emails
1144 to the people peeking on the wire. I
1145 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
1146 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
1147 lot of useful feedback and suggestions. It also became obvious to me
1148 that this was not a novel idea, as the same idea was tested and
1149 documented by Johannes Berg as early as 2006, and both
1150 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
1151 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
1152 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
1153
1154 &lt;p&gt;To implement such system one need to set up a Tor hidden service
1155 providing the SMTP protocol on port 25, and use email addresses
1156 looking like username@hidden-service-name.onion. With such addresses
1157 the connections to port 25 on hidden-service-name.onion using Tor will
1158 go to the correct SMTP server. To do this, one need to configure the
1159 Tor daemon to provide the hidden service and the mail server to accept
1160 emails for this .onion domain. To learn more about Exim configuration
1161 in Debian and test the design provided by Johannes Berg in his FAQ, I
1162 set out yesterday to create a Debian package for making it trivial to
1163 set up such SMTP over Tor service based on Debian. Getting it to work
1164 were fairly easy, and
1165 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
1166 source code for the Debian package&lt;/a&gt; is available from github. I
1167 plan to move it into Debian if further testing prove this to be a
1168 useful approach.&lt;/p&gt;
1169
1170 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
1171 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
1172 get rid of exim4). Install tor, clone the git repository mentioned
1173 above, build the deb and install it on the machine. Next, run
1174 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
1175 the instructions to get the service up and running. Restart tor and
1176 exim when it is done, and test mail delivery using swaks like
1177 this:&lt;/p&gt;
1178
1179 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1180 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1181 --to fbx@dutlqrrmjhtfa3vp.onion
1182 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1183
1184 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
1185 address with your own address to test your server. :)&lt;/p&gt;
1186
1187 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
1188 easier and more automatic. Especially the tor setup need more work.
1189 Also, the package include a tor-smtp tool written in C, but its task
1190 should probably be rewritten in some script language to make the deb
1191 architecture independent. It would probably also make the code easier
1192 to review. The tor-smtp tool currently need to listen on a socket for
1193 exim to talk to it and is started using xinetd. It would be better if
1194 no daemon and no socket is needed. I suspect it is possible to get
1195 exim to run a command line tool for delivery instead of talking to a
1196 socket, and hope to figure out how in a future version of this
1197 system.&lt;/p&gt;
1198
1199 &lt;p&gt;Until I wipe my test machine, I can be reached using the
1200 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
1201 SMTorP. :)&lt;/p&gt;
1202 </description>
1203 </item>
1204
1205 <item>
1206 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
1207 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
1208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
1209 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
1210 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
1211 alioth.debian.org, you know the web interface is fairly slow to
1212 operate. First you visit one web page, enter the moderation password
1213 and get a new page shown with a list of all the messages to moderate
1214 and various options for each email address. This take a while for
1215 every list you moderate, and you need to do it regularly to do a good
1216 job as a list moderator. But there is a quick alternative,
1217 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
1218 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
1219 to moderate in a fraction of a second. Here is a test run on two
1220 lists I recently took over:&lt;/p&gt;
1221
1222 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1223 % time listadmin xiph
1224 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1225 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1226
1227 real 0m1.709s
1228 user 0m0.232s
1229 sys 0m0.012s
1230 %
1231 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1232
1233 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
1234 there are no message in the moderation queue. Every morning I
1235 currently moderate 68 mailman lists, and it normally take around two
1236 minutes. When I took over the two pkg-xiph lists above a few days
1237 ago, there were 400 emails waiting in the moderator queue. It took me
1238 less than 15 minutes to process them all using the listadmin
1239 program.&lt;/p&gt;
1240
1241 &lt;p&gt;If you install
1242 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
1243 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
1244 with content like this, the moderation task is a breeze:&lt;/p&gt;
1245
1246 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1247 username username@example.org
1248 spamlevel 23
1249 default discard
1250 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
1251
1252 password secret
1253 adminurl https://{domain}/mailman/admindb/{list}
1254 mailman-list@lists.example.com
1255
1256 password hidden
1257 other-list@otherserver.example.org
1258 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1259
1260 &lt;p&gt;There are other options to set as well. Check the manual page to
1261 learn the details.&lt;/p&gt;
1262
1263 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
1264 the SSL certificate is self signed or not properly signed by a
1265 generally accepted signing authority, you can set a environment
1266 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
1267
1268 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1269 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
1270 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1271
1272 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
1273 can provide an argument to the listadmin script like I do in the
1274 initial screen dump (the xiph argument). Using an argument, only
1275 lists matching the argument string will be processed. This make it
1276 quick to accept messages if you notice the moderation request in your
1277 email.&lt;/p&gt;
1278
1279 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
1280 mailing lists, as I simply do not have time to spend on that if the
1281 process was any slower. The listadmin program have saved me hours of
1282 time I could spend elsewhere over the years. It truly is nice free
1283 software.&lt;/p&gt;
1284
1285 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1286 activities, please send Bitcoin donations to my address
1287 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1288
1289 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1290 configuration example. Also, I&#39;ve been told that the
1291 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1292 sure why.&lt;/p&gt;
1293 </description>
1294 </item>
1295
1296 <item>
1297 <title>Debian Jessie, PXE and automatic firmware installation</title>
1298 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1299 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1300 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1301 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1302 problem that the WiFi card require some firmware to work properly.
1303 And it has been a pain to fix this using preseeding in Debian.
1304 Normally something more is needed. But thanks to
1305 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1306 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1307 to do this using simple preseeding.&lt;/p&gt;
1308
1309 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1310 firmware for the hardware found in the machine (actually, requested by
1311 the kernel modules for the hardware). (It can also install user space
1312 programs supporting the hardware detected, but that is not the focus
1313 of this story.)&lt;/p&gt;
1314
1315 &lt;p&gt;To get this working in the default installation, two preeseding
1316 values are needed. First, the isenkram-cli package must be installed
1317 into the target chroot (aka the hard drive) before tasksel is executed
1318 in the pkgsel step of the debian-installer system. This is done by
1319 preseeding the base-installer/includes debconf value to include the
1320 isenkram-cli package. The package name is next passed to debootstrap
1321 for installation. With the isenkram-cli package in place, tasksel
1322 will automatically use the isenkram tasks to detect hardware specific
1323 packages for the machine being installed and install them, because
1324 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1325
1326 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1327 most firmware unfortunately is non-free. This is done by preseeding
1328 the apt-mirror-setup step. This is unfortunate, but for a lot of
1329 hardware it is the only option in Debian.&lt;/p&gt;
1330
1331 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1332 firmware installed automatically by the installer:&lt;/p&gt;
1333
1334 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1335 base-installer base-installer/includes string isenkram-cli
1336 apt-mirror-setup apt-setup/non-free boolean true
1337 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1338
1339 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1340 both firmware and user space packages when using this method. It also
1341 do not work well, so use version 0.15 or later. Installing both
1342 firmware and user space packages might give you a bit more than you
1343 want, so I decided to split the tasksel task in two, one for firmware
1344 and one for user space programs. The firmware task is enabled by
1345 default, while the one for user space programs is not. This split is
1346 implemented in the package currently in unstable.&lt;/p&gt;
1347
1348 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1349 this recipe work for you. :)&lt;/p&gt;
1350
1351 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1352 foremost, it work because tasksel is modular, and driven by whatever
1353 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1354 isenkram-cli package place two files for tasksel to find. First there
1355 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1356
1357 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1358 Task: isenkram-packages
1359 Section: hardware
1360 Description: Hardware specific packages (autodetected by isenkram)
1361 Based on the detected hardware various hardware specific packages are
1362 proposed.
1363 Test-new-install: show show
1364 Relevance: 8
1365 Packages: for-current-hardware
1366
1367 Task: isenkram-firmware
1368 Section: hardware
1369 Description: Hardware specific firmware packages (autodetected by isenkram)
1370 Based on the detected hardware various hardware specific firmware
1371 packages are proposed.
1372 Test-new-install: mark show
1373 Relevance: 8
1374 Packages: for-current-hardware-firmware
1375 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1376
1377 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1378 should be handled and the Packages line referencing to a script in
1379 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1380 list of packages to install. The for-current-hardware-firmware script
1381 look like this to list relevant firmware for the machine:
1382
1383 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1384 #!/bin/sh
1385 #
1386 PATH=/usr/sbin:$PATH
1387 export PATH
1388 isenkram-autoinstall-firmware -l
1389 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1390
1391 &lt;p&gt;With those two pieces in place, the firmware is installed by
1392 tasksel during the normal d-i run. :)&lt;/p&gt;
1393
1394 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1395 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1396 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1397 install.&lt;/p&gt;
1398
1399 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1400 pilots in testing this feature, as isenkram is used there now to
1401 install firmware, replacing the earlier scripts.&lt;/p&gt;
1402 </description>
1403 </item>
1404
1405 <item>
1406 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1407 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1408 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1409 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1410 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1411 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1412 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1413 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1414
1415 &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;
1416
1417 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1418 about this hidden Linux installation. It is interesting what
1419 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1420 </description>
1421 </item>
1422
1423 <item>
1424 <title>New lsdvd release version 0.17 is ready</title>
1425 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1426 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1427 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1428 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1429 got a new set of developers a few weeks ago, after the original
1430 developer decided to step down and pass the project to fresh blood.
1431 This project is now maintained by Petter Reinholdtsen and Steve
1432 Dibb.&lt;/p&gt;
1433
1434 &lt;p&gt;I just wrapped up
1435 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1436 new lsdvd release&lt;/a&gt;, available in git or from
1437 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1438 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1439 0.17.&lt;/p&gt;
1440
1441 &lt;ul&gt;
1442
1443 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1444 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1445 non-existant, to work around additional copy protection&lt;/li&gt;
1446 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1447 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1448 &lt;li&gt;Fix include orders&lt;/li&gt;
1449 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1450 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1451 &lt;li&gt;Make sure the array size and the array limit used when initialising
1452 the palette size is the same.&lt;/li&gt;
1453 &lt;li&gt;Fix array printing.&lt;/li&gt;
1454 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1455 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1456 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1457 with more GCC compiler warnings.&lt;/li&gt;
1458
1459 &lt;/ul&gt;
1460
1461 &lt;p&gt;This change bring together patches for lsdvd in use in various
1462 Linux and Unix distributions, as well as patches submitted to the
1463 project the last nine years. Please check it out. :)&lt;/p&gt;
1464 </description>
1465 </item>
1466
1467 <item>
1468 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1469 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1470 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1471 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1472 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1473 project&lt;/a&gt; provide a Linux solution for schools, including a
1474 powerful desktop with education software, a central server providing
1475 web pages, user database, user home directories, central login and PXE
1476 boot of both clients without disk and the installation to install Debian
1477 Edu on machines with disk (and a few other services perhaps to small
1478 to mention here). We in the Debian Edu team are currently working on
1479 the Jessie based version, trying to get everything in shape before the
1480 freeze, to avoid having to maintain our own package repository in the
1481 future. The
1482 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1483 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1484 work left. Some fatal problems block testing, breaking the installer,
1485 but it is possible to work around these to get anyway. Here is a
1486 recipe on how to get the installation limping along.&lt;/p&gt;
1487
1488 &lt;p&gt;First, download the test ISO via
1489 &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;,
1490 &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;
1491 or rsync (use
1492 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1493 The ISO build was broken on Tuesday, so we do not get a new ISO every
1494 12 hours or so, but thankfully the ISO we already got we are able to
1495 install with some tweaking.&lt;/p&gt;
1496
1497 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1498 (use Alt-Ctrl-F2), run&lt;/p&gt;
1499
1500 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1501 nano /usr/bin/edu-eatmydata-install
1502 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1503
1504 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1505 optimization. Return to the installation, select the profile you want
1506 and continue. Without this change, exim4-config will fail to install
1507 due to a known bug in eatmydata.&lt;/p&gt;
1508
1509 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1510 this do not work, figure out what your correct value would be. All my
1511 test machines need /dev/sda, so I have no advice if it do not fit
1512 your need.&lt;/p&gt;
1513
1514 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1515 root after the initial boot from hard drive, and install the
1516 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1517 or mate. If you want several desktop options, install more than one
1518 metapackage. Once this is done, reboot and you should have a working
1519 graphical login screen. This workaround should no longer be needed
1520 once the education-tasks package version 1.801 enter testing in two
1521 days.&lt;/p&gt;
1522
1523 &lt;p&gt;I believe the ISO build will start working on two days when the new
1524 tasksel package enter testing and Steve McIntyre get a chance to
1525 update the debian-cd git repository. The eatmydata, grub and desktop
1526 issues are already fixed in unstable and testing, and should show up
1527 on the ISO as soon as the ISO build start working again. Well the
1528 eatmydata optimization is really just disabled. The proper fix
1529 require an upload by the eatmydata maintainer applying the patch
1530 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1531 The rest have proper fixes in unstable.&lt;/p&gt;
1532
1533 &lt;p&gt;I hope this get you going with the installation testing, as we are
1534 quickly running out of time trying to get our Jessie based
1535 installation ready before the distribution freeze in a month.&lt;/p&gt;
1536 </description>
1537 </item>
1538
1539 <item>
1540 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1541 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1542 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1543 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1544 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1545 to handle my fairly large DVD collection. It is a nice command line
1546 tool to get details about a DVD, like title, tracks, track length,
1547 etc, in XML, Perl or human readable format. But lsdvd have not seen
1548 any new development since 2006 and had a few irritating bugs affecting
1549 its use with some DVDs. Upstream seemed to be dead, and in January I
1550 sent a small probe asking for a version control repository for the
1551 project, without any reply. But I use it regularly and would like to
1552 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1553 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1554 the project admin, and after getting a reply from him explaining that
1555 he was no longer interested in the project, I asked if I could take
1556 over. And yesterday, I became project admin.&lt;/p&gt;
1557
1558 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1559 maintainer interested in joining forces to maintain the upstream
1560 project, and I hope we can get a new release out fairly quickly,
1561 collecting the patches spread around on the internet into on place.
1562 I&#39;ve added the relevant Debian patches to the freshly created git
1563 repository, and expect the Gentoo patches to make it too. If you got
1564 a DVD collection and care about command line tools, check out
1565 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1566 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1567 list&lt;/a&gt;. :)&lt;/p&gt;
1568 </description>
1569 </item>
1570
1571 <item>
1572 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1573 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1575 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1576 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1577 a lot quicker. When we install more than 2000 packages in
1578 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1579 tasksel in the installer, unpacking the binary packages take forever.
1580 A part of the slow I/O issue was discussed in
1581 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1582 much file system sync-ing done by dpkg, which is the package
1583 responsible for unpacking the binary packages. Other parts (like code
1584 executed by postinst scripts) might also sync to disk during
1585 installation. All this sync-ing to disk do not really make sense to
1586 me. If the machine crash half-way through, I start over, I do not try
1587 to salvage the half installed system. So the failure sync-ing is
1588 supposed to protect against, hardware or system crash, is not really
1589 relevant while the installer is running.&lt;/p&gt;
1590
1591 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1592 system sync()-ing in a fairly non-intrusive way, without the need to
1593 change the code in several packages. The idea is not new, but I have
1594 not heard anyone propose the approach using dpkg-divert before. It
1595 depend on the small and clever package
1596 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1597 uses LD_PRELOAD to replace the system functions for syncing data to
1598 disk with functions doing nothing, thus allowing programs to live
1599 dangerous while speeding up disk I/O significantly. Instead of
1600 modifying the implementation of dpkg, apt and tasksel (which are the
1601 packages responsible for selecting, fetching and installing packages),
1602 it occurred to me that we could just divert the programs away, replace
1603 them with a simple shell wrapper calling
1604 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1605 Two days ago I decided to test the idea, and wrapped up a simple
1606 implementation for the Debian Edu udeb.&lt;/p&gt;
1607
1608 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1609 time of the pkgsel step (installing tasks) from 64 to less than 44
1610 minutes (20 minutes shaved off the installation) on an old Dell
1611 Latitude D505 machine. I am not quite sure what the optimised time
1612 would have been, as I messed up the testing a bit, causing the debconf
1613 priority to get low enough for two questions to pop up during
1614 installation. As soon as I saw the questions I moved the installation
1615 along, but do not know how long the question were holding up the
1616 installation. I did some more measurements using Debian Edu Jessie,
1617 and got these results. The time measured is the time stamp in
1618 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1619 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1620 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1621 timing thus do not depend on how quickly the user handle the tasksel
1622 dialog.&lt;/p&gt;
1623
1624 &lt;p&gt;&lt;table&gt;
1625
1626 &lt;tr&gt;
1627 &lt;th&gt;Machine/setup&lt;/th&gt;
1628 &lt;th&gt;Original tasksel&lt;/th&gt;
1629 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1630 &lt;th&gt;Reduction&lt;/th&gt;
1631 &lt;/tr&gt;
1632
1633 &lt;tr&gt;
1634 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1635 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1636 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1637 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1638 &lt;/tr&gt;
1639
1640 &lt;tr&gt;
1641 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1642 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1643 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1644 &lt;td&gt;23 min 40%&lt;/td&gt;
1645 &lt;/tr&gt;
1646
1647 &lt;tr&gt;
1648 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1649 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1650 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1651 &lt;td&gt;11 min 50%&lt;/td&gt;
1652 &lt;/tr&gt;
1653
1654 &lt;tr&gt;
1655 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1656 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1657 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1658 &lt;td&gt;2 min 33%&lt;/td&gt;
1659 &lt;/tr&gt;
1660
1661 &lt;tr&gt;
1662 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1663 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1664 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1665 &lt;td&gt;4 min 21%&lt;/td&gt;
1666 &lt;/tr&gt;
1667
1668 &lt;/table&gt;&lt;/p&gt;
1669
1670 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1671 time is spent downloading packages. The connection to the Internet
1672 was 100Mbit/s during testing, so downloading should not be a
1673 significant factor in the measurement. Download typically took a few
1674 seconds to a few minutes, depending on the amount of packages being
1675 installed.&lt;/p&gt;
1676
1677 &lt;p&gt;The speedup is implemented by using two hooks in
1678 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1679 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1680 finish-install.d hook to remove the divert at the end of the
1681 installation. I picked the pre-pkgsel.d hook instead of the
1682 post-base-installer.d hook because I test using an ISO without the
1683 eatmydata package included, and the post-base-installer.d hook in
1684 Debian Edu can only operate on packages included in the ISO. The
1685 negative effect of this is that I am unable to activate this
1686 optimization for the kernel installation step in d-i. If the code is
1687 moved to the post-base-installer.d hook, the speedup would be larger
1688 for the entire installation.&lt;/p&gt;
1689
1690 &lt;p&gt;I&#39;ve implemented this in the
1691 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1692 git repository, and plan to provide the optimization as part of the
1693 Debian Edu installation. If you want to test this yourself, you can
1694 create two files in the installer (or in an udeb). One shell script
1695 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1696
1697 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1698 #!/bin/sh
1699 set -e
1700 . /usr/share/debconf/confmodule
1701 info() {
1702 logger -t my-pkgsel &quot;info: $*&quot;
1703 }
1704 error() {
1705 logger -t my-pkgsel &quot;error: $*&quot;
1706 }
1707 override_install() {
1708 apt-install eatmydata || true
1709 if [ -x /target/usr/bin/eatmydata ] ; then
1710 for bin in dpkg apt-get aptitude tasksel ; do
1711 file=/usr/bin/$bin
1712 # Test that the file exist and have not been diverted already.
1713 if [ -f /target$file ] ; then
1714 info &quot;diverting $file using eatmydata&quot;
1715 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1716 &gt; /target$file.edu
1717 chmod 755 /target$file.edu
1718 in-target dpkg-divert --package debian-edu-config \
1719 --rename --quiet --add $file
1720 ln -sf ./$bin.edu /target$file
1721 else
1722 error &quot;unable to divert $file, as it is missing.&quot;
1723 fi
1724 done
1725 else
1726 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1727 fi
1728 }
1729
1730 override_install
1731 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1732
1733 &lt;p&gt;To clean up, another shell script should go into
1734 /usr/lib/finish-install.d/ with code like this:
1735
1736 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1737 #! /bin/sh -e
1738 . /usr/share/debconf/confmodule
1739 error() {
1740 logger -t my-finish-install &quot;error: $@&quot;
1741 }
1742 remove_install_override() {
1743 for bin in dpkg apt-get aptitude tasksel ; do
1744 file=/usr/bin/$bin
1745 if [ -x /target$file.edu ] ; then
1746 rm /target$file
1747 in-target dpkg-divert --package debian-edu-config \
1748 --rename --quiet --remove $file
1749 rm /target$file.edu
1750 else
1751 error &quot;Missing divert for $file.&quot;
1752 fi
1753 done
1754 sync # Flush file buffers before continuing
1755 }
1756
1757 remove_install_override
1758 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1759
1760 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1761 edu-eatmydata-install and call it from the pre-pkgsel.d and
1762 finish-install.d scripts.&lt;/p&gt;
1763
1764 &lt;p&gt;By now you might ask if this change should get into the normal
1765 Debian installer too? I suspect it should, but am not sure the
1766 current debian-installer coordinators find it useful enough. It also
1767 depend on the side effects of the change. I&#39;m not aware of any, but I
1768 guess we will see if the change is safe after some more testing.
1769 Perhaps there is some package in Debian depending on sync() and
1770 fsync() having effect? Perhaps it should go into its own udeb, to
1771 allow those of us wanting to enable it to do so without affecting
1772 everyone.&lt;/p&gt;
1773
1774 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1775 will break installation of all programs using gnutls because of
1776 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1777 eatmydata package in Debian will solve it.&lt;/p&gt;
1778
1779 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1780 the optimization work again. And I have discovered that the
1781 dpkg-divert trick is not really needed and implemented a slightly
1782 simpler approach as part of the debian-edu-install package. See
1783 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1784
1785 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1786 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1787 triggering on i386 made it into testing, and broke this installation
1788 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1789 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1790 </description>
1791 </item>
1792
1793 <item>
1794 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1795 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1796 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1797 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1798 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1799 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1800 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1801 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1802 learn that there is a large set of publicly available key servers to
1803 use when looking for peoples public key. So far I have used
1804 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1805 were misbehaving, but those days are ended. The servers I have used
1806 up until yesterday have been slow and some times unavailable. I hope
1807 those problems are gone now.&lt;/p&gt;
1808
1809 &lt;p&gt;Behind the round robin DNS entry of the
1810 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1811 there is a pool of more than 100 keyservers which are checked every
1812 day to ensure they are well connected and up to date. It must be
1813 better than what I have used so far. :)&lt;/p&gt;
1814
1815 &lt;p&gt;Yesterdays speaker told me that the service is the default
1816 keyserver provided by the default configuration in GnuPG, but this do
1817 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1818
1819 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1820 line:&lt;/p&gt;
1821
1822 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1823 keyserver pool.sks-keyservers.net
1824 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1825
1826 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1827 entries in DNS. Just for fun, I did just that at work, so now every
1828 user of GnuPG at the University of Oslo should find a OpenGPG
1829 keyserver automatically should their need it:&lt;/p&gt;
1830
1831 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1832 % host -t srv _pgpkey-http._tcp.uio.no
1833 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1834 %
1835 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1836
1837 &lt;p&gt;Now if only
1838 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1839 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1840 very happy. It can look up a given key or search for a user ID, but I
1841 normally do not want that, but to find a trust path from my key to
1842 another key. Given a user ID or key ID, I would like to find (and
1843 download) the keys representing a signature path from my key to the
1844 key in question, to be able to get a trust path between the two keys.
1845 This is as far as I can tell not possible today. Perhaps something
1846 for a future version of the protocol?&lt;/p&gt;
1847 </description>
1848 </item>
1849
1850 <item>
1851 <title>From English wiki to translated PDF and epub via Docbook</title>
1852 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1853 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1854 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1855 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1856 project&lt;/a&gt; provide an instruction manual for teachers, system
1857 administrators and other users that contain useful tips for setting up
1858 and maintaining a Debian Edu installation. This text is about how the
1859 text processing of this manual is handled in the project.&lt;/p&gt;
1860
1861 &lt;p&gt;One goal of the project is to provide information in the native
1862 language of its users, and for this we need to handle translations.
1863 But we also want to make sure each language contain the same
1864 information, so for this we need a good way to keep the translations
1865 in sync. And we want it to be easy for our users to improve the
1866 documentation, avoiding the need to learn special formats or tools to
1867 contribute, and the obvious way to do this is to make it possible to
1868 edit the documentation using a web browser. We also want it to be
1869 easy for translators to keep the translation up to date, and give them
1870 help in figuring out what need to be translated. Here is the list of
1871 tools and the process we have found trying to reach all these
1872 goals.&lt;/p&gt;
1873
1874 &lt;p&gt;We maintain the authoritative source of our manual in the
1875 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1876 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1877 front page with references to the different chapters, several pages
1878 for each chapter, and finally one &quot;collection page&quot; gluing all the
1879 chapters together into one large web page (aka
1880 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1881 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1882 processing and translations. Thanks to the fact that the
1883 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1884 wiki.debian.org support exporting pages in
1885 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1886 the list of pages to export using the raw version of the AllInOne
1887 page, loop over each of them to generate a Docbook XML version of the
1888 manual. This process also download images and transform image
1889 references to use the locally downloaded images. The generated
1890 Docbook XML files are slightly broken, so some post-processing is done
1891 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1892 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1893 a handfull of images. The XML file can now be used to generate PDF, HTML
1894 and epub versions of the English manual. This is the basic step of
1895 our process, making PDF (using dblatex), HTML (using xsltproc) and
1896 epub (using dbtoepub) version from Docbook XML, and the resulting files
1897 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1898
1899 &lt;p&gt;But English documentation is not enough for us. We want translated
1900 documentation too, and we want to make it easy for translators to
1901 track the English original. For this we use the
1902 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1903 which allow us to transform the English Docbook XML file into a
1904 translation file (a .pot file), usable with the normal gettext based
1905 translation tools used by those translating free software. The pot
1906 file is used to create and maintain translation files (several .po
1907 files), which the translations update with the native language
1908 translations of all titles, paragraphs and blocks of text in the
1909 original. The next step is combining the original English Docbook XML
1910 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1911 create a translated Docbook XML file (in this case
1912 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1913 translated, if the translation is not complete) Docbook XML file can
1914 then be used like the original to create a PDF, HTML and epub version
1915 of the documentation.&lt;/p&gt;
1916
1917 &lt;p&gt;The translators use different tools to edit the .po files. We
1918 recommend using
1919 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1920 while some use emacs and vi, others can use web based editors like
1921 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1922 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1923 is where the .po file end up, in our git repository. Updated
1924 translations can either be committed directly to git, or submitted as
1925 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1926 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1927
1928 &lt;p&gt;One challenge is images, which both might need to be translated (if
1929 they show translated user applications), and are needed in different
1930 formats when creating PDF and HTML versions (epub is a HTML version in
1931 this regard). For this we transform the original PNG images to the
1932 needed density and format during build, and have a way to provide
1933 translated images by storing translated versions in
1934 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1935 package maintainers know more.&lt;/p&gt;
1936
1937 &lt;p&gt;If you wonder what the result look like, we provide
1938 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1939 of the documentation packages on the web&lt;/a&gt;. See for example the
1940 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1941 PDF version&lt;/a&gt; or the
1942 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1943 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1944 but perhaps it will be done in the future.&lt;/p&gt;
1945
1946 &lt;p&gt;To learn more, check out
1947 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1948 debian-edu-doc package&lt;/a&gt;,
1949 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1950 manual on the wiki&lt;/a&gt; and
1951 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1952 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1953 </description>
1954 </item>
1955
1956 <item>
1957 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1958 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1959 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1960 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1961 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1962 related packages relevant for the computer installed automatically.
1963 So I implemented one, using
1964 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1965 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1966 run tasksel as user root. You should be presented with a new option,
1967 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1968 select it, tasksel will install the packages isenkram claim is fit for
1969 the current hardware, hot pluggable or not.&lt;p&gt;
1970
1971 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1972 description, and the other is the script used to extract the list of
1973 packages to install. The first part is in
1974 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1975 this:&lt;/p&gt;
1976
1977 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1978 Task: isenkram
1979 Section: hardware
1980 Description: Hardware specific packages (autodetected by isenkram)
1981 Based on the detected hardware various hardware specific packages are
1982 proposed.
1983 Test-new-install: mark show
1984 Relevance: 8
1985 Packages: for-current-hardware
1986 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1987
1988 &lt;p&gt;The second part is in
1989 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1990 this:&lt;/p&gt;
1991
1992 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1993 #!/bin/sh
1994 #
1995 (
1996 isenkram-lookup
1997 isenkram-autoinstall-firmware -l
1998 ) | sort -u
1999 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2000
2001 &lt;p&gt;All in all, a very short and simple implementation making it
2002 trivial to install the hardware dependent package we all may want to
2003 have installed on our machines. I&#39;ve not been able to find a way to
2004 get tasksel to tell you exactly which packages it plan to install
2005 before doing the installation. So if you are curious or careful,
2006 check the output from the isenkram-* command line tools first.&lt;/p&gt;
2007
2008 &lt;p&gt;The information about which packages are handling which hardware is
2009 fetched either from the isenkram package itself in
2010 /usr/share/isenkram/, from git.debian.org or from the APT package
2011 database (using the Modaliases header). The APT package database
2012 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2013 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
2014 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
2015 the python-apt code (bug
2016 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
2017 workaround I was able to get rid of the file descriptor leak and
2018 reduce the memory leak from ~30 MiB per hardware detection down to
2019 around 2 MiB per hardware detection. It should make the desktop
2020 daemon a lot more useful. The fix is in version 0.7 uploaded to
2021 unstable today.&lt;/p&gt;
2022
2023 &lt;p&gt;I believe the current way of mapping hardware to packages in
2024 Isenkram is is a good draft, but in the future I expect isenkram to
2025 use the AppStream data source for this. A proposal for getting proper
2026 AppStream support into Debian is floating around as
2027 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
2028 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
2029 project&lt;/a&gt; will take place this summer to improve the situation. I
2030 look forward to seeing the result, and welcome patches for isenkram to
2031 start using the information when it is ready.&lt;/p&gt;
2032
2033 &lt;p&gt;If you want your package to map to some specific hardware, either
2034 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
2035 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
2036 package&lt;/a&gt; or submit a bug report with the details to the isenkram
2037 package. See also
2038 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
2039 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
2040 the information will be migrated to AppStream eventually, but for the
2041 moment I got no better place to store it.&lt;/p&gt;
2042 </description>
2043 </item>
2044
2045 <item>
2046 <title>FreedomBox milestone - all packages now in Debian Sid</title>
2047 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
2048 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
2049 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
2050 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2051 project&lt;/a&gt; is working on providing the software and hardware to make
2052 it easy for non-technical people to host their data and communication
2053 at home, and being able to communicate with their friends and family
2054 encrypted and away from prying eyes. It is still going strong, and
2055 today a major mile stone was reached.&lt;/p&gt;
2056
2057 &lt;p&gt;Today, the last of the packages currently used by the project to
2058 created the system images were accepted into Debian Unstable. It was
2059 the freedombox-setup package, which is used to configure the images
2060 during build and on the first boot. Now all one need to get going is
2061 the build code from the freedom-maker git repository and packages from
2062 Debian. And once the freedombox-setup package enter testing, we can
2063 build everything directly from Debian. :)&lt;/p&gt;
2064
2065 &lt;p&gt;Some key packages used by Freedombox are
2066 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
2067 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
2068 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
2069 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
2070 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
2071 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
2072 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
2073 are plans to integrate more packages into the setup. User
2074 documentation is maintained on the Debian wiki. Please
2075 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
2076 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
2077
2078 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
2079 setup, run this on a Debian machine using a user with sudo rights to
2080 become root:&lt;/p&gt;
2081
2082 &lt;p&gt;&lt;pre&gt;
2083 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2084 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2085 u-boot-tools
2086 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2087 freedom-maker
2088 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2089 &lt;/pre&gt;&lt;/p&gt;
2090
2091 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2092 devices. See the README in the freedom-maker git repo for more
2093 details on the build. If you do not want all three images, trim the
2094 make line. Note that the virtualbox-image target is not really
2095 virtualbox specific. It create a x86 image usable in kvm, qemu,
2096 vmware and any other x86 virtual machine environment. You might need
2097 the version of vmdebootstrap in Jessie to get the build working, as it
2098 include fixes for a race condition with kpartx.&lt;/p&gt;
2099
2100 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2101 method, boot a Debian Wheezy ISO and use this boot argument to load
2102 the preseed values:&lt;/p&gt;
2103
2104 &lt;p&gt;&lt;pre&gt;
2105 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;
2106 &lt;/pre&gt;&lt;/p&gt;
2107
2108 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
2109 it still work.&lt;/p&gt;
2110
2111 &lt;p&gt;If you wonder how to help, one task you could look at is using
2112 systemd as the boot system. It will become the default for Linux in
2113 Jessie, so we need to make sure it is usable on the Freedombox. I did
2114 a simple test a few weeks ago, and noticed dnsmasq failed to start
2115 during boot when using systemd. I suspect there are other problems
2116 too. :) To detect problems, there is a test suite included, which can
2117 be run from the plinth web interface.&lt;/p&gt;
2118
2119 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2120 us get the new release published. :) Please join us on
2121 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2122 irc.debian.org)&lt;/a&gt; and
2123 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2124 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2125 </description>
2126 </item>
2127
2128 <item>
2129 <title>S3QL, a locally mounted cloud file system - nice free software</title>
2130 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
2131 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
2132 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
2133 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
2134 solution for use at home. My requirements are simple, it must be
2135 cheap and locally encrypted (in other words, I keep the encryption
2136 keys, the storage provider do not have access to my private files).
2137 One idea me and my friends had many years ago, before the cloud
2138 storage providers showed up, was to use Google mail as storage,
2139 writing a Linux block device storing blocks as emails in the mail
2140 service provided by Google, and thus get heaps of free space. On top
2141 of this one can add encryption, RAID and volume management to have
2142 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2143 I never found time to implement such system. But the last few weeks I
2144 have looked at a system called
2145 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
2146 mounted network backed file system with the features I need.&lt;/p&gt;
2147
2148 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
2149 handling several different storage providers, any with Amazon S3,
2150 Google Drive or OpenStack API. There are heaps of such storage
2151 providers. S3QL can also use a local directory as storage, which
2152 combined with sshfs allow for file storage on any ssh server. S3QL
2153 include support for encryption, compression, de-duplication, snapshots
2154 and immutable file systems, allowing me to mount the remote storage as
2155 a local mount point, look at and use the files as if they were local,
2156 while the content is stored in the cloud as well. This allow me to
2157 have a backup that should survive fire. The file system can not be
2158 shared between several machines at the same time, as only one can
2159 mount it at the time, but any machine with the encryption key and
2160 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
2161
2162 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
2163 package is included already. So to get started, run &lt;tt&gt;apt-get
2164 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
2165 Greenqloud, after reading their nice recipe on
2166 &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
2167 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
2168 in Iceland more than those in USA when it come to keeping my personal
2169 data safe and private, and thus would rather spend money on a company
2170 in Iceland. Another nice recipe is available from the article
2171 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
2172 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
2173 Admin magazine. When the provider is picked, figure out how to get
2174 the API key needed to connect to the storage API. With Greencloud,
2175 the key did not show up until I had added payment details to my
2176 account.&lt;/p&gt;
2177
2178 &lt;p&gt;Armed with the API access details, it is time to create the file
2179 system. First, create a new bucket in the cloud. This bucket is the
2180 file system storage area. I picked a bucket name reflecting the
2181 machine that was going to store data there, but any name will do.
2182 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
2183 the API login and password, and a locally created password. Store it
2184 all in ~root/.s3ql/authinfo2 like this:
2185
2186 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2187 [s3c]
2188 storage-url: s3c://s.greenqloud.com:443/bucket-name
2189 backend-login: API-login
2190 backend-password: API-password
2191 fs-passphrase: local-password
2192 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2193
2194 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
2195 but any sensible way to create a fairly random password should do it.
2196 Armed with these details, it is now time to run mkfs, entering the API
2197 details and password to create it:&lt;/p&gt;
2198
2199 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2200 # mkdir -m 700 /var/lib/s3ql-cache
2201 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2202 --ssl s3c://s.greenqloud.com:443/bucket-name
2203 Enter backend login:
2204 Enter backend password:
2205 Before using S3QL, make sure to read the user&#39;s guide, especially
2206 the &#39;Important Rules to Avoid Loosing Data&#39; section.
2207 Enter encryption password:
2208 Confirm encryption password:
2209 Generating random encryption key...
2210 Creating metadata tables...
2211 Dumping metadata...
2212 ..objects..
2213 ..blocks..
2214 ..inodes..
2215 ..inode_blocks..
2216 ..symlink_targets..
2217 ..names..
2218 ..contents..
2219 ..ext_attributes..
2220 Compressing and uploading metadata...
2221 Wrote 0.00 MB of compressed metadata.
2222 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2223
2224 &lt;p&gt;The next step is mounting the file system to make the storage available.
2225
2226 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2227 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2228 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2229 Using 4 upload threads.
2230 Downloading and decompressing metadata...
2231 Reading metadata...
2232 ..objects..
2233 ..blocks..
2234 ..inodes..
2235 ..inode_blocks..
2236 ..symlink_targets..
2237 ..names..
2238 ..contents..
2239 ..ext_attributes..
2240 Mounting filesystem...
2241 # df -h /s3ql
2242 Filesystem Size Used Avail Use% Mounted on
2243 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
2244 #
2245 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2246
2247 &lt;p&gt;The file system is now ready for use. I use rsync to store my
2248 backups in it, and as the metadata used by rsync is downloaded at
2249 mount time, no network traffic (and storage cost) is triggered by
2250 running rsync. To unmount, one should not use the normal umount
2251 command, as this will not flush the cache to the cloud storage, but
2252 instead running the umount.s3ql command like this:
2253
2254 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2255 # umount.s3ql /s3ql
2256 #
2257 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2258
2259 &lt;p&gt;There is a fsck command available to check the file system and
2260 correct any problems detected. This can be used if the local server
2261 crashes while the file system is mounted, to reset the &quot;already
2262 mounted&quot; flag. This is what it look like when processing a working
2263 file system:&lt;/p&gt;
2264
2265 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2266 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
2267 Using cached metadata.
2268 File system seems clean, checking anyway.
2269 Checking DB integrity...
2270 Creating temporary extra indices...
2271 Checking lost+found...
2272 Checking cached objects...
2273 Checking names (refcounts)...
2274 Checking contents (names)...
2275 Checking contents (inodes)...
2276 Checking contents (parent inodes)...
2277 Checking objects (reference counts)...
2278 Checking objects (backend)...
2279 ..processed 5000 objects so far..
2280 ..processed 10000 objects so far..
2281 ..processed 15000 objects so far..
2282 Checking objects (sizes)...
2283 Checking blocks (referenced objects)...
2284 Checking blocks (refcounts)...
2285 Checking inode-block mapping (blocks)...
2286 Checking inode-block mapping (inodes)...
2287 Checking inodes (refcounts)...
2288 Checking inodes (sizes)...
2289 Checking extended attributes (names)...
2290 Checking extended attributes (inodes)...
2291 Checking symlinks (inodes)...
2292 Checking directory reachability...
2293 Checking unix conventions...
2294 Checking referential integrity...
2295 Dropping temporary indices...
2296 Backing up old metadata...
2297 Dumping metadata...
2298 ..objects..
2299 ..blocks..
2300 ..inodes..
2301 ..inode_blocks..
2302 ..symlink_targets..
2303 ..names..
2304 ..contents..
2305 ..ext_attributes..
2306 Compressing and uploading metadata...
2307 Wrote 0.89 MB of compressed metadata.
2308 #
2309 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2310
2311 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2312 quick, about the same speed as local file access. Uploading large
2313 amount of data is to me limited by the bandwidth out of and into my
2314 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2315 which is very close to my upload speed, and downloading the same
2316 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2317 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2318 network, not the file system code. I do not know what a good cache
2319 size would be, but suspect that the cache should e larger than your
2320 working set.&lt;/p&gt;
2321
2322 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2323 time. If another machine try, it is told that the file system is
2324 busy:&lt;/p&gt;
2325
2326 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2327 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2328 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2329 Using 8 upload threads.
2330 Backend reports that fs is still mounted elsewhere, aborting.
2331 #
2332 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2333
2334 &lt;p&gt;The file content is uploaded when the cache is full, while the
2335 metadata is uploaded once every 24 hour by default. To ensure the
2336 file system content is flushed to the cloud, one can either umount the
2337 file system, or ask S3QL to flush the cache and metadata using
2338 s3qlctrl:
2339
2340 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2341 # s3qlctrl upload-meta /s3ql
2342 # s3qlctrl flushcache /s3ql
2343 #
2344 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2345
2346 &lt;p&gt;If you are curious about how much space your data uses in the
2347 cloud, and how much compression and deduplication cut down on the
2348 storage usage, you can use s3qlstat on the mounted file system to get
2349 a report:&lt;/p&gt;
2350
2351 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2352 # s3qlstat /s3ql
2353 Directory entries: 9141
2354 Inodes: 9143
2355 Data blocks: 8851
2356 Total data size: 22049.38 MB
2357 After de-duplication: 21955.46 MB (99.57% of total)
2358 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2359 Database size: 2.39 MB (uncompressed)
2360 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2361 #
2362 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2363
2364 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2365 storage. I did not try to locate them all, but am aware of at least
2366 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2367 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2368 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2369 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2370 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2371 accept payment in Bitcoin. Pick one that suit your need. Some of
2372 them provide several GiB of free storage, but the prize models are
2373 quite different and you will have to figure out what suits you
2374 best.&lt;/p&gt;
2375
2376 &lt;p&gt;While researching this blog post, I had a look at research papers
2377 and posters discussing the S3QL file system. There are several, which
2378 told me that the file system is getting a critical check by the
2379 science community and increased my confidence in using it. One nice
2380 poster is titled
2381 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2382 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2383 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2384 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2385 and Pamela Smith. Please have a look.&lt;/p&gt;
2386
2387 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2388 check out the mounted S3QL file system to see if it would be usable as
2389 a home directory (in other word, that it provided POSIX semantics when
2390 it come to locking and umask handling etc). Running
2391 &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
2392 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2393 no error was found. So the file system can be used for home
2394 directories, if one chooses to do so.&lt;/p&gt;
2395
2396 &lt;p&gt;If you do not want a locally file system, and want something that
2397 work without the Linux fuse file system, I would like to mention the
2398 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2399 provide locally encrypted backup using a command line client. It have
2400 a nicer access control system, where one can split out read and write
2401 access, allowing some systems to write to the backup and others to
2402 only read from it.&lt;/p&gt;
2403
2404 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2405 activities, please send Bitcoin donations to my address
2406 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2407 </description>
2408 </item>
2409
2410 <item>
2411 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2412 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2413 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2414 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2415 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2416 project&lt;/a&gt; is working on providing the software and hardware for
2417 making it easy for non-technical people to host their data and
2418 communication at home, and being able to communicate with their
2419 friends and family encrypted and away from prying eyes. It has been
2420 going on for a while, and is slowly progressing towards a new test
2421 release (0.2).&lt;/p&gt;
2422
2423 &lt;p&gt;And what day could be better than the Pi day to announce that the
2424 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2425 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2426 system), and can also be installed using a Debian installer preseed
2427 file. The Debian based Freedombox is now based on Debian Jessie,
2428 where most of the needed packages used are already present. Only one,
2429 the freedombox-setup package, is missing. To try to build your own
2430 boot image to test the current status, fetch the freedom-maker scripts
2431 and build using
2432 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2433 with a user with sudo access to become root:
2434
2435 &lt;pre&gt;
2436 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2437 freedom-maker
2438 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2439 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2440 u-boot-tools
2441 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2442 &lt;/pre&gt;
2443
2444 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2445 devices. See the README for more details on the build. If you do not
2446 want all three images, trim the make line. But note that thanks to &lt;a
2447 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2448 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2449 kpartx call.&lt;/p&gt;
2450
2451 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2452 method, boot a Debian Wheezy ISO and use this boot argument to load
2453 the preseed values:&lt;/p&gt;
2454
2455 &lt;pre&gt;
2456 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;
2457 &lt;/pre&gt;
2458
2459 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2460 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2461 currently hang while setting up APT sources. Killing the
2462 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2463 installation will get the installation going. This affect all
2464 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2465
2466 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2467 us get the new release published. :) Please join us on
2468 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2469 irc.debian.org)&lt;/a&gt; and
2470 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2471 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2472 </description>
2473 </item>
2474
2475 <item>
2476 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2477 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2478 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2479 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2480 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2481 innetgr tools, because I needed them in
2482 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2483 ng-utils, and it has served me well. I placed the project under the
2484 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2485 repository. But many years ago, the CVS repository was dropped (lost,
2486 not migrated to new hardware, not sure), and the project have lacked a
2487 proper home since then.&lt;/p&gt;
2488
2489 &lt;p&gt;Last summer, I had a look at the package and made a new release
2490 fixing a irritating crash bug, but was unable to store the changes in
2491 a proper source control system. I applied for a project on
2492 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2493 to follow up on it. Until today. :)&lt;/p&gt;
2494
2495 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2496 now have a new home, and a git repository with the highlight of the
2497 history of the project. I published all release tarballs and imported
2498 them into the git repository. As the project is really stable and not
2499 expected to gain new features any time soon, I decided to make a new
2500 release and call it 1.0. Visit the new project home on
2501 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2502 if you want to check it out. The new version is also uploaded into
2503 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2504 </description>
2505 </item>
2506
2507 <item>
2508 <title>Testing sysvinit from experimental in Debian Hurd</title>
2509 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2510 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2511 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2512 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2513 their changes into sysvinit, to allow them to use the normal sysvinit
2514 boot system instead of their old one. This follow up on the
2515 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2516 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2517 get Debian on Hurd working more like Debian on Linux. To get started,
2518 I downloaded a prebuilt hard disk image from
2519 &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;,
2520 and started it using virt-manager.&lt;/p&gt;
2521
2522 &lt;p&gt;The first think I had to do after logging in (root without any
2523 password) was to get the network operational. I followed
2524 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2525 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2526 commands as root to get the machine to accept a IP address from the
2527 kvm internal DHCP server:&lt;/p&gt;
2528
2529 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2530 settrans -fgap /dev/netdde /hurd/netdde
2531 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2532 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2533 dhclient /dev/eth0
2534 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2535
2536 &lt;p&gt;After this, the machine had internet connectivity, and I could
2537 upgrade it and install the sysvinit packages from experimental and
2538 enable it as the default boot system in Hurd.&lt;/p&gt;
2539
2540 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2541 running on the machine it for ssh login to work a password need to be
2542 set. Also, note that a bug somewhere in openssh on Hurd block
2543 compression from working. Remember to turn that off on the client
2544 side.&lt;/p&gt;
2545
2546 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2547 stuff:&lt;/p&gt;
2548
2549 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2550 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2551 deb http://http.debian.net/debian/ experimental main
2552 EOF
2553 apt-get update
2554 apt-get dist-upgrade
2555 apt-get install -t experimental initscripts sysv-rc sysvinit \
2556 sysvinit-core sysvinit-utils
2557 update-alternatives --config runsystem
2558 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2559
2560 &lt;p&gt;To reboot after switching boot system, you have to use
2561 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2562 yet a sysvinit process able to receive the signals from the normal
2563 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2564 upgrading every package and rebooting, the network come up with DHCP
2565 after boot as it should, and the settrans/pkill hack mentioned at the
2566 start is no longer needed. But for some strange reason, there are no
2567 longer any login prompt in the virtual console, so I logged in using
2568 ssh instead.
2569
2570 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2571 fail some times. No idea what the cause is, but hope the Hurd porters
2572 figure it out. At least Justus said on IRC (#debian-hurd on
2573 irc.debian.org) that they are aware of the problem. A way to reduce
2574 the impact is to upgrade to the Hurd packages built by Justus by
2575 adding this repository to the machine:&lt;/p&gt;
2576
2577 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2578 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2579 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2580 EOF
2581 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2582
2583 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2584 http://ftp.debian-ports.org/debian, because some of the packages in
2585 unstable do not yet include the required patches that are lingering in
2586 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2587
2588 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2589 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2590 i emacs - GNU Emacs editor (metapackage)
2591 i gdb - GNU Debugger
2592 i hurd-recommended - Miscellaneous translators
2593 i isc-dhcp-client - ISC DHCP client
2594 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2595 i libc-bin - Embedded GNU C Library: Binaries
2596 i libc-dev-bin - Embedded GNU C Library: Development binaries
2597 i libc0.3 - Embedded GNU C Library: Shared libraries
2598 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2599 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2600 i multiarch-support - Transitional package to ensure multiarch compatibilit
2601 i A x11-common - X Window System (X.Org) infrastructure
2602 i xorg - X.Org X Window System
2603 i A xserver-xorg - X.Org X server
2604 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2605 #
2606 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2607
2608 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2609 X.org did not work out of the box and I never took the time to follow
2610 the porters instructions to fix it. This time I was interested in the
2611 command line stuff.&lt;p&gt;
2612 </description>
2613 </item>
2614
2615 <item>
2616 <title>New chrpath release 0.16</title>
2617 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2619 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2620 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2621 find problems in C, C++ and Java code using static source code
2622 analysis. It can detect a lot of different problems, and is very
2623 useful to find memory and locking bugs in the error handling part of
2624 the source. The company behind it provide
2625 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2626 a community service&lt;/a&gt;, and many hundred free software projects are
2627 already checked. A few days ago I decided to have a closer look at
2628 the Coverity system, and discovered that the
2629 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2630 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2631 projects I am involved with was already registered. But these are
2632 fairly big, and I would also like to have a small and easy project to
2633 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2634 checking of the chrpath project&lt;/a&gt;. It was
2635 added to the checker and discovered seven potential defects. Six of
2636 these were real, mostly resource &quot;leak&quot; when the program detected an
2637 error. Nothing serious, as the resources would be released a fraction
2638 of a second later when the program exited because of the error, but it
2639 is nice to do it right in case the source of the program some time in
2640 the future end up in a library. Having fixed all defects and added
2641 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2642 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2643 publish a new release. These are the release notes:&lt;/p&gt;
2644
2645 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2646
2647 &lt;ul&gt;
2648
2649 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2650 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2651 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2652
2653 &lt;/ul&gt;
2654
2655 &lt;p&gt;You can
2656 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2657 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2658 project if something is wrong with the new release. The test suite
2659 did not discover any old errors, so if you find a new one, please also
2660 include a test suite check.&lt;/p&gt;
2661 </description>
2662 </item>
2663
2664 <item>
2665 <title>New chrpath release 0.15</title>
2666 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2667 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2668 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2669 <description>&lt;p&gt;After many years break from the package and a vain hope that
2670 development would be continued by someone else, I finally pulled my
2671 acts together this morning and wrapped up a new release of chrpath,
2672 the command line tool to modify the rpath and runpath of already
2673 compiled ELF programs. The update was triggered by the persistence of
2674 Isha Vishnoi at IBM, which needed a new config.guess file to get
2675 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2676 is working on. I checked the
2677 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2678 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2679 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2680 packages for interesting patches (failed to find the source from
2681 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2682 These are the release notes:&lt;/p&gt;
2683
2684 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2685
2686 &lt;ul&gt;
2687
2688 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2689 with newer architectures. Thanks to isha vishnoi for the heads
2690 up.&lt;/li&gt;
2691
2692 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2693
2694 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2695 Matthias Klose.&lt;/li&gt;
2696
2697 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2698 Petr Machata found in Fedora.&lt;/li&gt;
2699
2700 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2701 .dynamic is a NULL terminated string. Based on patch found in
2702 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2703
2704 &lt;/ul&gt;
2705
2706 &lt;p&gt;You can
2707 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2708 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2709 project if something is wrong with the new release. The test suite
2710 did not discover any old errors, so if you find a new one, please also
2711 include a testsuite check.&lt;/p&gt;
2712 </description>
2713 </item>
2714
2715 <item>
2716 <title>Debian init.d boot script example for rsyslog</title>
2717 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2718 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2719 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2720 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2721 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2722 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2723 init.d scripts at all. Here is an example init.d script, ie a rewrite
2724 of /etc/init.d/rsyslog:&lt;/p&gt;
2725
2726 &lt;p&gt;&lt;pre&gt;
2727 #!/lib/init/init-d-script
2728 ### BEGIN INIT INFO
2729 # Provides: rsyslog
2730 # Required-Start: $remote_fs $time
2731 # Required-Stop: umountnfs $time
2732 # X-Stop-After: sendsigs
2733 # Default-Start: 2 3 4 5
2734 # Default-Stop: 0 1 6
2735 # Short-Description: enhanced syslogd
2736 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2737 # It is quite compatible to stock sysklogd and can be
2738 # used as a drop-in replacement.
2739 ### END INIT INFO
2740 DESC=&quot;enhanced syslogd&quot;
2741 DAEMON=/usr/sbin/rsyslogd
2742 &lt;/pre&gt;&lt;/p&gt;
2743
2744 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2745 script was 137 lines, and the above is just 15 lines, most of it meta
2746 info/comments.&lt;/p&gt;
2747
2748 &lt;p&gt;How to do this, you ask? Well, one create a new script
2749 /lib/init/init-d-script looking something like this:
2750
2751 &lt;p&gt;&lt;pre&gt;
2752 #!/bin/sh
2753
2754 # Define LSB log_* functions.
2755 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2756 # and status_of_proc is working.
2757 . /lib/lsb/init-functions
2758
2759 #
2760 # Function that starts the daemon/service
2761
2762 #
2763 do_start()
2764 {
2765 # Return
2766 # 0 if daemon has been started
2767 # 1 if daemon was already running
2768 # 2 if daemon could not be started
2769 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2770 || return 1
2771 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2772 $DAEMON_ARGS \
2773 || return 2
2774 # Add code here, if necessary, that waits for the process to be ready
2775 # to handle requests from services started subsequently which depend
2776 # on this one. As a last resort, sleep for some time.
2777 }
2778
2779 #
2780 # Function that stops the daemon/service
2781 #
2782 do_stop()
2783 {
2784 # Return
2785 # 0 if daemon has been stopped
2786 # 1 if daemon was already stopped
2787 # 2 if daemon could not be stopped
2788 # other if a failure occurred
2789 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2790 RETVAL=&quot;$?&quot;
2791 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2792 # Wait for children to finish too if this is a daemon that forks
2793 # and if the daemon is only ever run from this initscript.
2794 # If the above conditions are not satisfied then add some other code
2795 # that waits for the process to drop all resources that could be
2796 # needed by services started subsequently. A last resort is to
2797 # sleep for some time.
2798 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2799 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2800 # Many daemons don&#39;t delete their pidfiles when they exit.
2801 rm -f $PIDFILE
2802 return &quot;$RETVAL&quot;
2803 }
2804
2805 #
2806 # Function that sends a SIGHUP to the daemon/service
2807 #
2808 do_reload() {
2809 #
2810 # If the daemon can reload its configuration without
2811 # restarting (for example, when it is sent a SIGHUP),
2812 # then implement that here.
2813 #
2814 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2815 return 0
2816 }
2817
2818 SCRIPTNAME=$1
2819 scriptbasename=&quot;$(basename $1)&quot;
2820 echo &quot;SN: $scriptbasename&quot;
2821 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2822 script=&quot;$1&quot;
2823 shift
2824 . $script
2825 else
2826 exit 0
2827 fi
2828
2829 NAME=$(basename $DAEMON)
2830 PIDFILE=/var/run/$NAME.pid
2831
2832 # Exit if the package is not installed
2833 #[ -x &quot;$DAEMON&quot; ] || exit 0
2834
2835 # Read configuration variable file if it is present
2836 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2837
2838 # Load the VERBOSE setting and other rcS variables
2839 . /lib/init/vars.sh
2840
2841 case &quot;$1&quot; in
2842 start)
2843 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2844 do_start
2845 case &quot;$?&quot; in
2846 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2847 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2848 esac
2849 ;;
2850 stop)
2851 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2852 do_stop
2853 case &quot;$?&quot; in
2854 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2855 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2856 esac
2857 ;;
2858 status)
2859 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2860 ;;
2861 #reload|force-reload)
2862 #
2863 # If do_reload() is not implemented then leave this commented out
2864 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2865 #
2866 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2867 #do_reload
2868 #log_end_msg $?
2869 #;;
2870 restart|force-reload)
2871 #
2872 # If the &quot;reload&quot; option is implemented then remove the
2873 # &#39;force-reload&#39; alias
2874 #
2875 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2876 do_stop
2877 case &quot;$?&quot; in
2878 0|1)
2879 do_start
2880 case &quot;$?&quot; in
2881 0) log_end_msg 0 ;;
2882 1) log_end_msg 1 ;; # Old process is still running
2883 *) log_end_msg 1 ;; # Failed to start
2884 esac
2885 ;;
2886 *)
2887 # Failed to stop
2888 log_end_msg 1
2889 ;;
2890 esac
2891 ;;
2892 *)
2893 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2894 exit 3
2895 ;;
2896 esac
2897
2898 :
2899 &lt;/pre&gt;&lt;/p&gt;
2900
2901 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2902 lot. I did not really polish the approach, so it might not always
2903 work out of the box, but you get the idea. I did not try very hard to
2904 optimize it nor make it more robust either.&lt;/p&gt;
2905
2906 &lt;p&gt;A better argument for switching init system in Debian than reducing
2907 the size of init scripts (which is a good thing to do anyway), is to
2908 get boot system that is able to handle the kernel events sensibly and
2909 robustly, and do not depend on the boot to run sequentially. The boot
2910 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2911 </description>
2912 </item>
2913
2914 <item>
2915 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2916 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2917 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2918 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2919 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2920 remote display access is the preferred solution with oVirt and RedHat
2921 Enterprise Virtualization, and I was sad to discover the other day
2922 that the browser plugin needed to use these systems seamlessly was
2923 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2924 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2925 2013-04-01, so I decided to wrap up a package based on the great work
2926 from Cajus Pollmeier and put it in a collab-maint maintained git
2927 repository to get a package I could use. I would very much like
2928 others to help me maintain the package (or just take over, I do not
2929 mind), but as no-one had volunteered so far, I just uploaded it to
2930 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2931
2932 &lt;p&gt;The source is now available from
2933 &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;
2934 </description>
2935 </item>
2936
2937 <item>
2938 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2939 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2940 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2941 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2942 <description>&lt;p&gt;The
2943 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2944 program is a a very nice system to create virtual machine images. It
2945 create a image file, add a partition table, mount it and run
2946 debootstrap in the mounted directory to create a Debian system on a
2947 stick. Yesterday, I decided to try to teach it how to make images for
2948 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2949 of a plan to simplify the build system for
2950 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2951 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2952 the virtualbox images, but its current build system made multistrap
2953 based system for Dreamplug images, and it is lacking support for
2954 Raspberry Pi.&lt;/p&gt;
2955
2956 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2957 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2958 code and adjusted it to be able to build armel images on my amd64
2959 Debian laptop. I ended up giving vmdebootstrap five new options,
2960 allowing me to replicate the image creation process I use to make
2961 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2962 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2963 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2964 call debootstrap with --foreign and to copy the handler into the
2965 generated chroot before running the second stage. This allow
2966 vmdebootstrap to create armel images on an amd64 host. Next I added
2967 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2968 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2969 given file system type, allowing me to create an image with a vfat
2970 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2971 variant&lt;/tt&gt; option to allow me to create smaller images without the
2972 Debian base system packages installed. Finally, I added an option
2973 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2974 as a boot loader. It is not needed on the Raspberry Pi and probably
2975 most other non-x86 architectures. The changes were accepted by the
2976 upstream author of vmdebootstrap yesterday and today, and is now
2977 available from
2978 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2979 upstream project page&lt;/a&gt;.&lt;/p&gt;
2980
2981 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2982 create a small script (the customize script) to add the non-free
2983 binary blob needed to boot the Raspberry Pi and the APT source
2984 list:&lt;/p&gt;
2985
2986 &lt;p&gt;&lt;pre&gt;
2987 #!/bin/sh
2988 set -e # Exit on first error
2989 rootdir=&quot;$1&quot;
2990 cd &quot;$rootdir&quot;
2991 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2992 deb http://http.debian.net/debian/ jessie main contrib non-free
2993 EOF
2994 # Install non-free binary blob needed to boot Raspberry Pi. This
2995 # install a kernel somewhere too.
2996 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2997 -O $rootdir/usr/bin/rpi-update
2998 chmod a+x $rootdir/usr/bin/rpi-update
2999 mkdir -p $rootdir/lib/modules
3000 touch $rootdir/boot/start.elf
3001 chroot $rootdir rpi-update
3002 &lt;/pre&gt;&lt;/p&gt;
3003
3004 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
3005 to build the image:&lt;/p&gt;
3006
3007 &lt;pre&gt;
3008 sudo ./vmdebootstrap \
3009 --variant minbase \
3010 --arch armel \
3011 --distribution jessie \
3012 --mirror http://http.debian.net/debian \
3013 --image test.img \
3014 --size 600M \
3015 --bootsize 64M \
3016 --boottype vfat \
3017 --log-level debug \
3018 --verbose \
3019 --no-kernel \
3020 --no-extlinux \
3021 --root-password raspberry \
3022 --hostname raspberrypi \
3023 --foreign /usr/bin/qemu-arm-static \
3024 --customize `pwd`/customize \
3025 --package netbase \
3026 --package git-core \
3027 --package binutils \
3028 --package ca-certificates \
3029 --package wget \
3030 --package kmod
3031 &lt;/pre&gt;&lt;/p&gt;
3032
3033 &lt;p&gt;The list of packages being installed are the ones needed by
3034 rpi-update to make the image bootable on the Raspberry Pi, with the
3035 exception of netbase, which is needed by debootstrap to find
3036 /etc/hosts with the minbase variant. I really wish there was a way to
3037 set up an Raspberry Pi using only packages in the Debian archive, but
3038 that is not possible as far as I know, because it boots from the GPU
3039 using a non-free binary blob.&lt;/p&gt;
3040
3041 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
3042 probably a few others installed. I have not checked the complete
3043 build dependency list.&lt;/p&gt;
3044
3045 &lt;p&gt;The resulting image will not use the hardware floating point unit
3046 on the Raspberry PI, because the armel architecture in Debian is not
3047 optimized for that use. So the images created will be a bit slower
3048 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
3049 </description>
3050 </item>
3051
3052 <item>
3053 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
3054 <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>
3055 <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>
3056 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
3057 <description>&lt;p&gt;The last few days I came across a few good causes that should get
3058 wider attention. I recommend signing and donating to each one of
3059 these. :)&lt;/p&gt;
3060
3061 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
3062 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
3063 Women program which is a Google Summer of Code like initiative to get
3064 more women involved in free software. One debian sponsor has offered
3065 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
3066 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
3067 hope you will to. :)&lt;/p&gt;
3068
3069 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
3070 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
3071 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
3072 take place these days, and their need to fund the work. I&#39;ve already
3073 donated. Are you next?&lt;/p&gt;
3074
3075 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
3076 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3077 statement under the heading
3078 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
3079 Access&lt;/a&gt; for those of us asking for more focus on open access in the
3080 Norwegian government. So far 499 signatures. I hope you will sign it
3081 too.&lt;/p&gt;
3082 </description>
3083 </item>
3084
3085 <item>
3086 <title>Videos about the Freedombox project - for inspiration and learning</title>
3087 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
3088 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
3089 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
3090 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
3091 project&lt;/a&gt; have been going on for a while, and have presented the
3092 vision, ideas and solution several places. Here is a little
3093 collection of videos of talks and presentation of the project.&lt;/p&gt;
3094
3095 &lt;ul&gt;
3096
3097 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
3098 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
3099
3100 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
3101 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3102
3103 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
3104 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3105 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
3106 (Youtube)&lt;/li&gt;
3107
3108 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
3109 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
3110
3111 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
3112 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3113
3114 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
3115 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3116 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
3117
3118 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
3119 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
3120 (Youtube)&lt;/li&gt;
3121
3122 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
3123 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
3124
3125 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
3126 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
3127
3128 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
3129 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3130 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
3131
3132 &lt;/ul&gt;
3133
3134 &lt;p&gt;A larger list is available from
3135 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
3136 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
3137
3138 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
3139 Jessie is coming along quite well, and soon both Owncloud and using
3140 Tor should be available for testers of the Freedombox solution. :) In
3141 a few weeks I hope everything needed to test it is included in Debian.
3142 The withsqlite package is already in Debian, and the plinth package is
3143 pending in NEW. The third and vital part of that puzzle is the
3144 metapackage/setup framework, which is still pending an upload. Join
3145 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
3146 (#freedombox on irc.debian.org)&lt;/a&gt; and
3147 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3148 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3149 </description>
3150 </item>
3151
3152 <item>
3153 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
3154 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
3155 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
3156 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
3157 <description>&lt;p&gt;I was introduced to the
3158 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
3159 in 2010, when Eben Moglen presented his vision about serving the need
3160 of non-technical people to keep their personal information private and
3161 within the legal protection of their own homes. The idea is to give
3162 people back the power over their network and machines, and return
3163 Internet back to its intended peer-to-peer architecture. Instead of
3164 depending on a central service, the Freedombox will give everyone
3165 control over their own basic infrastructure.&lt;/p&gt;
3166
3167 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
3168 taken priority. But this summers nasty news about the misuse of trust
3169 and privilege exercised by the &quot;western&quot; intelligence gathering
3170 communities increased my eagerness to contribute to a point where I
3171 actually started working on the project a while back.&lt;/p&gt;
3172
3173 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
3174 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
3175 create a simple and cheap Debian based appliance that anyone can hook
3176 up in their home and get access to secure and private services and
3177 communication. The initial deployment platform have been the
3178 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
3179 which is a piece of hardware I do not own. So to be able to test what
3180 the current Freedombox setup look like, I had to come up with a way to install
3181 it on some hardware I do have access to. I have rewritten the
3182 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
3183 image build framework to use .deb packages instead of only copying
3184 setup into the boot images, and thanks to this rewrite I am able to
3185 set up any machine supported by Debian Wheezy as a Freedombox, using
3186 the previously mentioned deb (and a few support debs for packages
3187 missing in Debian).&lt;/p&gt;
3188
3189 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
3190 scripts
3191 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
3192 and a administrative web interface
3193 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
3194 withsqlite), as well as a privacy enhancing proxy based on
3195 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
3196 (freedombox-privoxy). There is also a web/javascript based XMPP
3197 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
3198 trying (unsuccessfully so far) to talk to the XMPP server
3199 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
3200 web interface is pluggable, and the goal is to use it to enable OpenID
3201 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3202 this is really working yet, see
3203 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
3204 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
3205 on github at the moment. The HTTP proxy is operational out of the
3206 box, and the admin web interface can be used to add/remove plinth
3207 users. I&#39;ve not been able to do anything else with it so far, but
3208 know there are several branches spread around github and other places
3209 with lots of half baked features.&lt;/p&gt;
3210
3211 &lt;p&gt;Anyway, if you want to have a look at the current state, the
3212 following recipes should work to give you a test machine to poke
3213 at.&lt;/p&gt;
3214
3215 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
3216
3217 &lt;ol&gt;
3218
3219 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
3220 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
3221 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
3222 to the Debian installer:&lt;p&gt;
3223 &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;
3224
3225 &lt;li&gt;Answer the few language/region/password questions and pick disk to
3226 install on.&lt;/li&gt;
3227
3228 &lt;li&gt;When the installation is finished and the machine have rebooted a
3229 few times, your Freedombox is ready for testing.&lt;/li&gt;
3230
3231 &lt;/ol&gt;
3232
3233 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
3234
3235 &lt;ol&gt;
3236
3237 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
3238 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
3239 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
3240 &lt;pre&gt;
3241 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
3242 &lt;/pre&gt;&lt;/li&gt;
3243 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
3244 &lt;pre&gt;
3245 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3246 apt-key add -
3247 apt-get update
3248 apt-get install freedombox-setup
3249 /usr/lib/freedombox/setup
3250 &lt;/pre&gt;&lt;/li&gt;
3251 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
3252
3253 &lt;/ol&gt;
3254
3255 &lt;p&gt;You can test it on other architectures too, but because the
3256 freedombox-privoxy package is binary, it will only work as intended on
3257 the architectures where I have had time to build the binary and put it
3258 in my APT repository. But do not let this stop you. It is only a
3259 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
3260
3261 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
3262 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
3263 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
3264 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
3265
3266 &lt;p&gt;Please let me know if this works for you, or if you have any
3267 problems. We gather on the IRC channel
3268 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
3269 irc.debian.org and the
3270 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
3271 mailing list&lt;/a&gt;.&lt;/p&gt;
3272
3273 &lt;p&gt;Once you get your freedombox operational, you can visit
3274 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
3275 welcome screen (dead end - do not be surprised if you are unable to
3276 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
3277 to look at the rest of plinth. The default user is &#39;admin&#39; and the
3278 default password is &#39;secret&#39;.&lt;/p&gt;
3279 </description>
3280 </item>
3281
3282 <item>
3283 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
3284 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3285 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3286 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3287 <description>&lt;p&gt;Earlier, I reported about
3288 &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
3289 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3290 told by IBM that the original disk should be thrown away. And as
3291 there no longer was a problem if I bricked the firmware, I decided
3292 today to try to install Intel firmware to replace the Lenovo firmware
3293 currently on the disk.&lt;/p&gt;
3294
3295 &lt;p&gt;I searched the Intel site for firmware, and found
3296 &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;
3297 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3298 according to the site should contain the latest firmware for SSD
3299 disks. I inserted the broken disk in one of my spare laptops and
3300 booted the ISO from a USB stick. The disk was recognized, but the
3301 program claimed the newest firmware already were installed and refused
3302 to insert any Intel firmware. So no change, and the disk is still
3303 unable to handle write load. :( I guess the only way to get them
3304 working would be if Lenovo releases new firmware. No idea how likely
3305 that is. Anyway, just blogging about this test for completeness. I
3306 got a working Samsung disk, and see no point in spending more time on
3307 the broken disks.&lt;/p&gt;
3308 </description>
3309 </item>
3310
3311 <item>
3312 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3313 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3314 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3315 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3316 <description>&lt;p&gt;Today I switched to
3317 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3318 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3319 my new Thinkpad X230, which was delivered with an
3320 &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
3321 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3322 sustained writes. My hardware supplier have been very forthcoming in
3323 trying to find a solution, and after first trying with another
3324 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3325 disk instead to fix it once and for all. The Samsung disk survived
3326 the installation of Debian with encrypted disks (filling the disk with
3327 random data during installation killed the first two), and I thus
3328 decided to trust it with my data. I have installed it as a Debian Edu
3329 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3330 server at home using Kerberos and LDAP, and will use it as my work
3331 station from now on.&lt;/p&gt;
3332
3333 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3334 Debian Wheezy default installation need to be tuned a bit to increase
3335 performance and increase life time of the disk. The Linux kernel and
3336 user space applications do not yet adjust automatically to such
3337 environment. To make it easier for my self, I created a draft Debian
3338 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3339 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3340 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3341 is set up to adjust the setup of the machine by just installing the
3342 package. If there is any non-SSD disk in the machine, the package
3343 will refuse to install, as I did not try to write any logic to sort
3344 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3345
3346 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3347 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3348 where I set up the machine with one large encrypted partition (in
3349 addition to /boot), put LVM on top of this and set up partitions on
3350 top of this again. See the README file in the package source for the
3351 references I used to pick the settings. At the moment these
3352 parameters are tuned:&lt;/p&gt;
3353
3354 &lt;ul&gt;
3355
3356 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3357 (adding discard to /etc/crypttab)&lt;/li&gt;
3358
3359 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3360 this case a cryptsetup partition) by changing issue_discards from
3361 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3362
3363 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3364 systems.&lt;/li&gt;
3365
3366 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3367 /etc/fstab.&lt;/li&gt;
3368
3369 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3370
3371 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3372 cron.daily).&lt;/li&gt;
3373
3374 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3375 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3376
3377 &lt;/ul&gt;
3378
3379 &lt;p&gt;During installation, I cancelled the part where the installer fill
3380 the disk with random data, as this would kill the SSD performance for
3381 little gain. My goal with the encrypted file system is to ensure
3382 those stealing my laptop end up with a brick and not a working
3383 computer. I have no hope in keeping the really resourceful people
3384 from getting the data on the disk (see
3385 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3386 Thus I concluded that adding the discard option to crypttab is the
3387 right thing to do.&lt;/p&gt;
3388
3389 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3390 it for SSD, but others recommended deadline and a benchmark I found
3391 indicated that deadline might be better for interactive use.&lt;/p&gt;
3392
3393 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3394 and ext4, but read that it would give a performance hit ever time a
3395 file is removed, and thought it best to that that slowdown once a day
3396 instead of during my work.&lt;/p&gt;
3397
3398 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3399 this is already done by Debian Edu.&lt;/p&gt;
3400
3401 &lt;p&gt;I have not yet started on the user space tuning. I expect
3402 iceweasel need some tuning, and perhaps other applications too, but
3403 have not yet had time to investigate those parts.&lt;/p&gt;
3404
3405 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3406 there.&lt;/p&gt;
3407
3408 &lt;p&gt;As for the answer to the question in the title of this blog post,
3409 as far as I know, the only solution I know about is to replace the
3410 disk. It might be possible to flash it with Intel firmware instead of
3411 the Lenovo firmware. But I have not tried and did not want to do so
3412 without approval from Lenovo as I wanted to keep the warranty on the
3413 disk until a solution was found and they wanted the broken disks
3414 back.&lt;/p&gt;
3415 </description>
3416 </item>
3417
3418 <item>
3419 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3420 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3421 <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>
3422 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3423 <description>&lt;p&gt;A few days ago, I wrote about
3424 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3425 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3426 was dying during installation because it is unable to cope with
3427 sustained write. My supplier is in contact with
3428 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3429 replacement disk to try to fix the problem. They decided to send an
3430 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3431
3432 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3433 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3434 same firmware version as the original. This time my hope raised
3435 slightly as the installation progressed, as the original disk used to
3436 die after 4-7% of the disk was written to, while this time it kept
3437 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3438 died again and I was back on square one. I still do not have a new
3439 laptop with a disk I can trust. I can not live with a disk that might
3440 lock up when I download a new
3441 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3442 other large files. I look forward to hearing from my supplier with
3443 the next proposal from Lenovo.&lt;/p&gt;
3444
3445 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3446 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3447 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3448 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3449 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3450 P/N 45N8295, P0C38732.&lt;/p&gt;
3451
3452 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3453 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3454 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3455 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3456 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3457 P/N 45N8295, P0C38732.&lt;/p&gt;
3458
3459 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3460 SA, date and WNPP values. Mentioning all the details here in case
3461 someone is able to use the information to find a way to identify the
3462 failing disk among working ones (if any such working disk actually
3463 exist).&lt;/p&gt;
3464 </description>
3465 </item>
3466
3467 <item>
3468 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3469 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3470 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3471 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3472 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3473 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3474 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3475 member assosiation NUUG&lt;/a&gt; and
3476 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3477 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3478 Bitraf&lt;/a&gt;.&lt;/p&gt;
3479
3480 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3481 welcome, and there is no fee to participate. There is on the other
3482 hand limited space, and only room for 30 people. Please put your name
3483 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3484 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3485 </description>
3486 </item>
3487
3488 <item>
3489 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3490 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3491 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3492 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3493 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3494 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3495 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3496 time to spend on it, and it took a while to find a model I believe
3497 will do the job, but two days ago the replacement finally arrived. I
3498 ended up picking a
3499 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3500 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3501 a roaming workstation, and it seemed to work flawlessly. But my
3502 second installation with encrypted disk was not as successful. More
3503 on that below.&lt;/p&gt;
3504
3505 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3506 important requirements (robust and with a good keyboard) are never
3507 listed in the feature list. But I did get good help from the search
3508 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3509 allowed me to limit the list of interesting laptops based on my other
3510 requirements. A bit surprising that SSD disk are not disks according
3511 to that search interface, so I had to drop specifying the number of
3512 disks from my search parameters. I also asked around among friends to
3513 get their impression on keyboards and robustness.&lt;/p&gt;
3514
3515 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3516 X41. I am not quite convinced about the keyboard, as it is
3517 significantly wider than my old keyboard, and I have to stretch my
3518 hand a lot more to reach the edges. But the key response is fairly
3519 good and the individual key shape is fairly easy to handle, so I hope
3520 I will get used to it. My old X40 was starting to fail, and I really
3521 needed a new laptop now. :)&lt;/p&gt;
3522
3523 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3524 visit to the BIOS during boot it disable it.&lt;/p&gt;
3525
3526 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3527 lock up during load. And this happen when installing Debian Wheezy
3528 with encrypted disk, while the disk is being filled with random data.
3529 I also tested to install Ubuntu Raring, and it happen there too if I
3530 reenable the code to fill the disk with random data (it is disabled by
3531 default in Ubuntu). And the bug with is already known. It was
3532 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3533 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3534 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3535 kernel developers as
3536 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3537 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3538 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3539 Lenovo forums, both for
3540 &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
3541 2012-11-10&lt;/a&gt; and for
3542 &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
3543 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3544 reports state that the disk lock up during use if many writes are done
3545 on the disk, so it is much no use to work around the installation
3546 problem and end up with a computer that can lock up at any moment.
3547 There is even a
3548 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3549 available&lt;/a&gt; that will lock up the hard drive after running a few
3550 minutes by writing to a file.&lt;/p&gt;
3551
3552 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3553 contacting PCHELP Norway (request 01D1FDP) which handle support
3554 requests for Lenovo, his first suggestion was to upgrade the disk
3555 firmware. Unfortunately there is no newer firmware available from
3556 Lenovo, as my disk already have the most recent one (version LF1i). I
3557 hope to hear more from him today and hope the problem can be
3558 fixed. :)&lt;/p&gt;
3559 </description>
3560 </item>
3561
3562 <item>
3563 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3564 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3565 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3566 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3567 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3568 trusty old Thinkpad X41. Unfortunately I did not have much time to
3569 spend on it, but today the replacement finally arrived. I ended up
3570 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3571 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3572 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3573 this, it is installing what I hope will be a more final installation,
3574 with a encrypted hard drive to ensure any dope head stealing it end up
3575 with an expencive door stop.&lt;/p&gt;
3576
3577 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3578 important requirements (robust and with a good keyboard) are never
3579 listed in the feature list. But I did get good help from the search
3580 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3581 allowed me to limit the list of interesting laptops based on my other
3582 requirements. A bit surprising that SSD disk are not disks, so I had
3583 to drop number of disks from my search parameters.&lt;/p&gt;
3584
3585 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3586 wider than my old keyboard, and I have to stretch my hand a lot more
3587 to reach the edges. But the key response is fairly good and the
3588 individual key shape is fairly easy to handle, so I hope I will get
3589 used to it. My old X40 was starting to fail, and I really needed a
3590 new laptop now. :)&lt;/p&gt;
3591
3592 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3593 </description>
3594 </item>
3595
3596 <item>
3597 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3598 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3599 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3600 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3601 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3602 perfectly capable of, and I have to do it manually to get things
3603 working. One such task is to find out what firmware packages are
3604 needed to get the hardware on my computer working. Most often this
3605 affect the wifi card, but some times it even affect the RAID
3606 controller or the ethernet card. Today I pushed version 0.4 of the
3607 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3608 including a new script isenkram-autoinstall-firmware handling the
3609 process of asking all the loaded kernel modules what firmware files
3610 they want, find debian packages providing these files and install the
3611 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3612
3613 &lt;p&gt;&lt;pre&gt;
3614 # isenkram-autoinstall-firmware
3615 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3616 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3617 info: locating packages with the requested firmware files
3618 info: Updating APT sources after adding non-free APT source
3619 info: trying to install firmware-ipw2x00
3620 firmware-ipw2x00
3621 firmware-ipw2x00
3622 Preconfiguring packages ...
3623 Selecting previously deselected package firmware-ipw2x00.
3624 (Reading database ... 259727 files and directories currently installed.)
3625 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3626 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3627 #
3628 &lt;/pre&gt;&lt;/p&gt;
3629
3630 &lt;p&gt;When all the requested firmware is present, a simple message is
3631 printed instead:&lt;/p&gt;
3632
3633 &lt;p&gt;&lt;pre&gt;
3634 # isenkram-autoinstall-firmware
3635 info: did not find any firmware files requested by loaded kernel modules. exiting
3636 #
3637 &lt;/pre&gt;&lt;/p&gt;
3638
3639 &lt;p&gt;It could use some polish, but it is already working well and saving
3640 me some time when setting up new machines. :)&lt;/p&gt;
3641
3642 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3643 kernel modules, and look up each one of them using modinfo, to find
3644 the firmware files listed in the module meta-information. Next, it
3645 download the Contents file from a nearby APT mirror, and search for
3646 the firmware files in this file to locate the package with the
3647 requested firmware file. If the package is in the non-free section, a
3648 non-free APT source is added and the package is installed using
3649 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3650 machine.&lt;/p&gt;
3651
3652 &lt;p&gt;I hope someone find time to implement a more polished version of
3653 this script as part of the hw-detect debian-installer module, to
3654 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3655 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3656 firmware during a PXE install when the packages already are available
3657 from the nearby Debian mirror.&lt;/p&gt;
3658 </description>
3659 </item>
3660
3661 <item>
3662 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3663 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3664 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3665 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3666 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3667 the screen just turn black when Linux boot, either during installation
3668 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3669 last few years, but only recently understood the cause. I&#39;ve seen it
3670 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3671 The reason seem to be in the wiring of some laptops. The system to
3672 control the screen background light is inverted, so when Linux try to
3673 turn the brightness fully on, it end up turning it off instead. I do
3674 not know which Linux drivers are affected, but this post is about the
3675 i915 driver used by the
3676 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3677 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3678
3679 &lt;p&gt;The problem can be worked around two ways. Either by adding
3680 i915.invert_brightness=1 as a kernel option, or by adding a file in
3681 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3682 option when it load the i915 kernel module. On Debian and Ubuntu, it
3683 can be done by running these commands as root:&lt;/p&gt;
3684
3685 &lt;pre&gt;
3686 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3687 update-initramfs -u -k all
3688 &lt;/pre&gt;
3689
3690 &lt;p&gt;Since March 2012 there is
3691 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3692 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3693 hardware have this problem, and get the driver to invert the
3694 brightness setting automatically. To use it, one need to add a row in
3695 &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
3696 intel_quirks array&lt;/a&gt; in the driver source
3697 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3698 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3699 number (vendor number 8086 is assumed) and subdevice vendor and device
3700 number.&lt;/p&gt;
3701
3702 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3703 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3704
3705 &lt;p&gt;&lt;pre&gt;
3706 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3707 3rd Gen Core processor Graphics Controller [8086:0156] \
3708 (rev 09) (prog-if 00 [VGA controller])
3709 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3710 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3711 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3712 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3713 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3714 Latency: 0
3715 Interrupt: pin A routed to IRQ 42
3716 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3717 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3718 Region 4: I/O ports at 4000 [size=64]
3719 Expansion ROM at &lt;unassigned&gt; [disabled]
3720 Capabilities: &lt;access denied&gt;
3721 Kernel driver in use: i915
3722 &lt;/pre&gt;&lt;/p&gt;
3723
3724 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3725
3726 &lt;p&gt;&lt;pre&gt;
3727 struct intel_quirk intel_quirks[] = {
3728 ...
3729 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3730 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3731 ...
3732 }
3733 &lt;/pre&gt;&lt;/p&gt;
3734
3735 &lt;p&gt;According to the kernel module instructions (as seen using
3736 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3737 invert_brightness flag should be sent to the
3738 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3739 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3740 developers. But my email about the laptop sent 2013-06-03 have not
3741 yet shown up in
3742 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3743 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3744 emails from non-subscribers. Because of this, I sent my patch also to
3745 the Debian bug tracking system instead as
3746 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3747 sure the patch is not lost.&lt;/p&gt;
3748
3749 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3750 with this problem working properly with Linux. If you use Gnome, your
3751 worries should be over at this point. But if you use KDE, there is
3752 something in KDE ignoring the invert_brightness setting and turning on
3753 the screen during login. I&#39;ve reported it to Debian as
3754 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3755 have no idea yet how to figure out exactly what subsystem is doing
3756 this. Perhaps you can help? Perhaps you know what the Gnome
3757 developers did to handle this, and this can give a clue to the KDE
3758 developers? Or you know where in KDE the screen brightness is changed
3759 during login? If so, please update the BTS report (or get in touch if
3760 you do not know how to update BTS).&lt;/p&gt;
3761
3762 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3763 acpi_backlight=vendor, to disable ACPI backlight support completely,
3764 as the ACPI information on the machine is trash and it is better to
3765 leave it to the intel video driver to control the screen
3766 backlight.&lt;/p&gt;
3767 </description>
3768 </item>
3769
3770 <item>
3771 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3772 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3773 <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>
3774 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3775 <description>&lt;p&gt;Two days ago, I asked
3776 &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
3777 I could install Linux on a Packard Bell EasyNote LV computer
3778 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3779 with the obstacles put in the way of Linux users on a laptop with UEFI
3780 and Windows 8.&lt;/p&gt;
3781
3782 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3783 secure booting or fast boot. I suspect fast boot was the problem,
3784 causing the firmware to boot directly from HD without considering any
3785 key presses and alternative devices, but do not know UEFI settings
3786 enough to tell.&lt;/p&gt;
3787
3788 &lt;p&gt;There is no way to install Linux on the machine in question without
3789 opening the box and disconnecting the hard drive! This is as far as I
3790 can tell, the only way to get access to the firmware setup menu
3791 without accepting the Windows 8 license agreement. I am told (and
3792 found description on how to) that it is possible to configure the
3793 firmware setup once booted into Windows 8. But as I believe the terms
3794 of that agreement are completely unacceptable, accepting the license
3795 was never an alternative. I do not enter agreements I do not intend
3796 to follow.&lt;/p&gt;
3797
3798 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3799 waste many hours on this, but luckily there was a way to get it to
3800 work. But I would not recommend it to anyone planning to run Linux on
3801 it, and I have become sceptical to Windows 8 certified laptops. Is
3802 this the way Linux will be forced out of the market place, by making
3803 it close to impossible for &quot;normal&quot; users to install Linux without
3804 accepting the Microsoft Windows license terms? Or at least not
3805 without risking to loose the warranty?&lt;/p&gt;
3806
3807 &lt;p&gt;I&#39;ve updated the
3808 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3809 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3810 do not have to struggle as much as I did to get Linux into the
3811 machine.&lt;/p&gt;
3812
3813 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3814 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3815 </description>
3816 </item>
3817
3818 <item>
3819 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3820 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3821 <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>
3822 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3823 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3824 new laptops for my parents and a few others. I bought Packard Bell
3825 Easynote LV to run Kubuntu on and use as their home computer. But I
3826 am completely unable to figure out how to install Linux on it. The
3827 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3828 instead of a BIOS to boot.&lt;/p&gt;
3829
3830 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3831 to get it to boot the Linux installer from my USB stick. I have yet
3832 to try the DVD install, and still hope it will work. when I turn on
3833 the computer, there is no information on what buttons to press to get
3834 the normal boot menu. I expect to get some boot menu to select PXE or
3835 USB stick booting. When booting, it first ask for the language to
3836 use, then for some regional settings, and finally if I will accept the
3837 Windows 8 terms of use. As these terms are completely unacceptable to
3838 me, I have no other choice but to turn off the computer and try again
3839 to get it to boot the Linux installer.&lt;/p&gt;
3840
3841 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3842 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3843 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3844 installed on this machine, please get in touch or update that wiki
3845 page. If I can&#39;t find a way to install Linux, I will have to return
3846 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3847
3848 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3849 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3850 on new Laptops?&lt;/p&gt;
3851 </description>
3852 </item>
3853
3854 <item>
3855 <title>How to transform a Debian based system to a Debian Edu installation</title>
3856 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3857 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3858 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3859 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3860 an operating system based on Debian intended for use in schools. It
3861 contain a turn-key solution for the computer network provided to
3862 pupils in the primary schools. It provide both the central server,
3863 network boot servers and desktop environments with heaps of
3864 educational software. The project was founded almost 12 years ago,
3865 2001-07-02. If you want to support the project, which is in need for
3866 cash to fund developer gatherings and other project related activity,
3867 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3868 donate some money&lt;/a&gt;.
3869
3870 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3871 lists and elsewhere, is the question on how to transform a Debian or
3872 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3873 hard, and last week I wrote a script to replicate the steps done by
3874 the Debian Edu installer.&lt;/p&gt;
3875
3876 &lt;p&gt;The script,
3877 &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;
3878 in the debian-edu-config package, will go through these six steps and
3879 transform an existing Debian Wheezy or Ubuntu (untested) installation
3880 into a Debian Edu Workstation:&lt;/p&gt;
3881
3882 &lt;ol&gt;
3883
3884 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3885 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3886 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3887 our configuration.&lt;/li&gt;
3888 &lt;li&gt;Preseed debconf database with profile setup in
3889 /etc/debian-edu/config, and run tasksel to install packages
3890 according to the profile specified in the config above,
3891 overriding some of the Debian automation machinery.&lt;/li&gt;
3892 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3893 that could not be done using preseeding.&lt;/li&gt;
3894 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3895
3896 &lt;/ol&gt;
3897
3898 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3899 replicated like this. Disk partitioning and LVM setup, for example.
3900 So this script just assume there is enough disk space to install all
3901 the needed packages.&lt;/p&gt;
3902
3903 &lt;p&gt;The script was created to help a Debian Edu student working on
3904 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3905 Debian Edu client, and using it he can take the existing
3906 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3907 transform it into a fully functioning Debian Edu Workstation (or
3908 Roaming Workstation, or whatever :).&lt;/p&gt;
3909
3910 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3911 If a LXDE based Roaming workstation is wanted instead, modify the
3912 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3913
3914 &lt;p&gt;&lt;pre&gt;
3915 PROFILE=&quot;Roaming-Workstation&quot;
3916 DESKTOP=&quot;lxde&quot;
3917 &lt;/pre&gt;&lt;/p&gt;
3918
3919 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3920 the cloud, by starting with a virtual Debian installation at some
3921 virtual hosting service and setting up all the services on first
3922 boot.&lt;/p&gt;
3923 </description>
3924 </item>
3925
3926 <item>
3927 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3928 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3929 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3930 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3931 <description>&lt;P&gt;In January,
3932 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3933 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3934 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3935 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3936 marvellous construction system from Denmark. We also created
3937 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3938 a place to take notes and write down our plans and hopes. And several
3939 people showed up to help. I was very happy to see the effect of my
3940 call. Since the small start, we have a debtags tag
3941 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3942 tag for LEGO related packages, and now count 10 packages related to
3943 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3944
3945 &lt;p&gt;&lt;table&gt;
3946 &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;
3947 &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;
3948 &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;
3949 &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;
3950 &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;
3951 &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;
3952 &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;
3953 &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;
3954 &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;
3955 &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;
3956 &lt;/table&gt;&lt;/p&gt;
3957
3958 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3959 currently available in Jessie/testing. leocad is so far only
3960 available in experimental.&lt;/p&gt;
3961
3962 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3963 adding the rest of the great free software tools available on Linux
3964 for LEGO designers.&lt;/p&gt;
3965 </description>
3966 </item>
3967
3968 <item>
3969 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3970 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3971 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3972 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3973 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3974 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3975 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3976 Debian release, and I expect to move my machines at home over to it fairly
3977 soon.&lt;/p&gt;
3978
3979 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3980 in particular make me very happy to see included. The
3981 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3982 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3983 included for the first time. Alongside similar programs like
3984 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3985 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3986 it allow for visual programming where syntax errors can not happen,
3987 and a friendly programming environment for learning to control the
3988 computer. Scratch will also be included in the next release of Debian
3989 Edu.&lt;/a&gt;
3990
3991 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3992 Edu/Skolelinux release too. The
3993 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3994 alpha release&lt;/a&gt; went out last week, and the next should soon
3995 follow.&lt;p&gt;
3996 </description>
3997 </item>
3998
3999 <item>
4000 <title>Isenkram 0.2 finally in the Debian archive</title>
4001 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
4002 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
4003 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
4004 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
4005 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
4006 for many months. I uploaded it to the Debian experimental suite
4007 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
4008
4009 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
4010 install to work with a pluggable hardware device. The suggestion pop
4011 up when the device is plugged in. For example if a Lego Mindstorm NXT
4012 is inserted, it will suggest to install the program needed to program
4013 the NXT controller. Give it a go, and report bugs and suggestions to
4014 BTS. :)&lt;/p&gt;
4015 </description>
4016 </item>
4017
4018 <item>
4019 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
4020 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
4021 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
4022 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
4023 <description>&lt;p&gt;My
4024 &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
4025 bitcoin related blog post&lt;/a&gt; mentioned that the new
4026 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
4027 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4028 2013-01-19, and have been available in unstable since then. It was
4029 automatically copied to Ubuntu, and is available in their Raring
4030 version too.&lt;/p&gt;
4031
4032 &lt;p&gt;But there is a strange problem with the build that block this new
4033 version from being available on the i386 and kfreebsd-i386
4034 architectures. For some strange reason, the autobuilders in Debian
4035 for these architectures fail to run the test suite on these
4036 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
4037 We are so far unable to reproduce it when building it manually, and
4038 no-one have been able to propose a fix. If you got an idea what is
4039 failing, please let us know via the BTS.&lt;/p&gt;
4040
4041 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
4042 I often run low on disk space, is the fact that the client will exit
4043 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
4044 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
4045 it. :)&lt;/p&gt;
4046
4047 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4048 activities, please send Bitcoin donations to my address
4049 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4050 </description>
4051 </item>
4052
4053 <item>
4054 <title>Welcome to the world, Isenkram!</title>
4055 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
4056 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
4057 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
4058 <description>&lt;p&gt;Yesterday, I
4059 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
4060 for testers&lt;/a&gt; for my prototype for making Debian better at handling
4061 pluggable hardware devices, which I
4062 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
4063 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
4064 up, and caused me to really want to to open up the development to more
4065 people. But before I did this, I want to come up with a sensible name
4066 for this project. Today I finally decided on a new name, and I have
4067 renamed the project from hw-support-handler to this new name. In the
4068 process, I moved the source to git and made it available as a
4069 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
4070 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
4071 To fetch and build the latest version of the source, use&lt;/p&gt;
4072
4073 &lt;pre&gt;
4074 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4075 cd isenkram &amp;&amp; git-buildpackage -us -uc
4076 &lt;/pre&gt;
4077
4078 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
4079 want to hack on the source or improve the package, please go ahead.
4080 But please talk to me first on IRC or via email before you do major
4081 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
4082
4083 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
4084 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4085 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
4086 the German word eisenkram, for those that are familiar with that
4087 word.&lt;/p&gt;
4088
4089 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
4090 instructions, to avoid confusing people with an error from the signing
4091 process.&lt;/p&gt;
4092
4093 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
4094 clone argument to avoid the need for authentication.&lt;/p&gt;
4095 </description>
4096 </item>
4097
4098 <item>
4099 <title>First prototype ready making hardware easier to use in Debian</title>
4100 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
4101 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
4102 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
4103 <description>&lt;p&gt;Early this month I set out to try to
4104 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
4105 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
4106 prototype is working, and it is ready for a larger audience. To test
4107 it, fetch the
4108 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
4109 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
4110 package. You might have to log out and in again activate the
4111 autostart script.&lt;/p&gt;
4112
4113 &lt;p&gt;The design is simple:&lt;/p&gt;
4114
4115 &lt;ul&gt;
4116
4117 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
4118 hw-support-handlerd to start when the user log in.&lt;/li&gt;
4119
4120 &lt;li&gt;This program listen for kernel events about new hardware (directly
4121 from the kernel like udev does), not using HAL dbus events as I
4122 initially did.&lt;/li&gt;
4123
4124 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
4125 the APT database, a database
4126 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
4127 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
4128
4129 &lt;li&gt;If a package is mapped to the hardware in question, the package
4130 isn&#39;t installed yet and this is the first time the hardware was
4131 plugged in, show a desktop notification suggesting to install the
4132 package or packages.&lt;/li&gt;
4133
4134 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
4135 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
4136
4137 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
4138 package while showing progress information in a window.&lt;/li&gt;
4139
4140 &lt;/ul&gt;
4141
4142 &lt;p&gt;I still need to come up with a better name for the system. Here
4143 are some screen shots showing the prototype in action. First the
4144 notification, then the password request, and finally the request to
4145 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
4146
4147 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
4148 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
4149 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
4150 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
4151 &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;
4152
4153 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
4154 is already useful. The database of hardware to package mappings also
4155 need more work. It is currently compatible with the Ubuntu way of
4156 storing such information in the package control file, but could be
4157 changed to use other formats instead or in addition to the current
4158 method. I&#39;ve dropped the use of discover for this mapping, as the
4159 modalias approach is more flexible and easier to use on Linux as long
4160 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
4161
4162 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
4163 here is the command required to check out and build the source: Use
4164 &#39;&lt;tt&gt;svn checkout
4165 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4166 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
4167 devscripts package.&lt;/p&gt;
4168
4169 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
4170 renamed to Isenkram and the source moved from the Debian Edu
4171 subversion repository to a Debian collab-maint git repository. See
4172 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
4173 instructions&lt;/a&gt; for details.&lt;/p&gt;
4174 </description>
4175 </item>
4176
4177 <item>
4178 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
4179 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
4180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
4181 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
4182 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
4183 suddenly in bed. With a quiet whimper, it went completely quiet and
4184 black. The power button was no longer able to turn it on. It was a
4185 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4186 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4187 Compaq I had before that. Now I need to find a replacement. To keep
4188 going during Christmas, I moved the one year old SSD disk to my old
4189 X40 where it fitted (only one I had left that could use it), but it is
4190 not a durable solution.
4191
4192 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
4193 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
4194
4195 &lt;ul&gt;
4196
4197 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
4198 than A4).&lt;/li&gt;
4199 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
4200 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
4201 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
4202 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
4203 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
4204 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
4205 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
4206 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
4207 size).&lt;/li&gt;
4208 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
4209 X.org packages.&lt;/li&gt;
4210 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
4211 the time).
4212
4213 &lt;/ul&gt;
4214
4215 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
4216 list. The reason is simply that the specifications on laptops the
4217 last 10-15 years have been sufficient for my needs, and I have to look
4218 at other features to choose my laptop. But are there still made as
4219 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4220 robust, and Thinkpads seem to be heading in the wrong direction since
4221 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
4222 still be useful.&lt;/p&gt;
4223
4224 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
4225 external keyboard? I&#39;ll have to check the
4226 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
4227 well-supported laptops, or perhaps just buy one preinstalled from one
4228 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
4229 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
4230 </description>
4231 </item>
4232
4233 <item>
4234 <title>How to find a browser plugin supporting a given MIME type</title>
4235 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
4236 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
4237 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
4238 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
4239 install to get support for a given MIME type. Thanks to
4240 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
4241 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
4242 Unfortunately, not very many packages provide the needed meta
4243 information, Anyway, here is a small script to look up all browser
4244 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
4245
4246 &lt;pre&gt;
4247 #!/usr/bin/python
4248 import sys
4249 import apt
4250 def pkgs_handling_mimetype(mimetype):
4251 cache = apt.Cache()
4252 cache.open(None)
4253 thepkgs = []
4254 for pkg in cache:
4255 version = pkg.candidate
4256 if version is None:
4257 version = pkg.installed
4258 if version is None:
4259 continue
4260 record = version.record
4261 if not record.has_key(&#39;Npp-MimeType&#39;):
4262 continue
4263 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
4264 for t in mime_types:
4265 t = t.rstrip().strip()
4266 if t == mimetype:
4267 thepkgs.append(pkg.name)
4268 return thepkgs
4269 mimetype = &quot;audio/ogg&quot;
4270 if 1 &lt; len(sys.argv):
4271 mimetype = sys.argv[1]
4272 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
4273 for pkg in pkgs_handling_mimetype(mimetype):
4274 print &quot; %s&quot; %pkg
4275 &lt;/pre&gt;
4276
4277 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
4278
4279 &lt;pre&gt;
4280 % ./apt-find-browserplug-for-mimetype
4281 Browser plugin packages supporting audio/ogg:
4282 gecko-mediaplayer
4283 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4284 Browser plugin packages supporting application/x-shockwave-flash:
4285 browser-plugin-gnash
4286 %
4287 &lt;/pre&gt;
4288
4289 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4290 itself to query for plugins and propose to install the needed
4291 packages. It would be great if Debian supported such feature too. Is
4292 anyone working on adding it?&lt;/p&gt;
4293
4294 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4295 request for icweasel support for this feature is
4296 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4297 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4298 of manpower and wish for a different design is the reason thus feature
4299 is not yet in iceweasel from Debian.&lt;/p&gt;
4300 </description>
4301 </item>
4302
4303 <item>
4304 <title>What is the most supported MIME type in Debian?</title>
4305 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4306 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4307 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4308 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4309 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4310 proposal to make it possible for a Desktop application to propose to
4311 the user some package to install to gain support for a given MIME
4312 type, font, library etc. that is currently missing. With such
4313 mechanism in place, it would be possible for the desktop to
4314 automatically propose and install leocad if some LDraw file is
4315 downloaded by the browser.&lt;/p&gt;
4316
4317 &lt;p&gt;To get some idea about the current content of the archive, I decided
4318 to write a simple program to extract all .desktop files from the
4319 Debian archive and look up the claimed MIME support there. The result
4320 can be found on the
4321 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4322 site&lt;/a&gt;. Using the collected information, it become possible to
4323 answer the question in the title. Here are the 20 most supported MIME
4324 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4325 The complete list is available from the link above.&lt;/p&gt;
4326
4327 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4328
4329 &lt;pre&gt;
4330 count MIME type
4331 ----- -----------------------
4332 32 text/plain
4333 30 audio/mpeg
4334 29 image/png
4335 28 image/jpeg
4336 27 application/ogg
4337 26 audio/x-mp3
4338 25 image/tiff
4339 25 image/gif
4340 22 image/bmp
4341 22 audio/x-wav
4342 20 audio/x-flac
4343 19 audio/x-mpegurl
4344 18 video/x-ms-asf
4345 18 audio/x-musepack
4346 18 audio/x-mpeg
4347 18 application/x-ogg
4348 17 video/mpeg
4349 17 audio/x-scpls
4350 17 audio/ogg
4351 16 video/x-ms-wmv
4352 &lt;/pre&gt;
4353
4354 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4355
4356 &lt;pre&gt;
4357 count MIME type
4358 ----- -----------------------
4359 33 text/plain
4360 32 image/png
4361 32 image/jpeg
4362 29 audio/mpeg
4363 27 image/gif
4364 26 image/tiff
4365 26 application/ogg
4366 25 audio/x-mp3
4367 22 image/bmp
4368 21 audio/x-wav
4369 19 audio/x-mpegurl
4370 19 audio/x-mpeg
4371 18 video/mpeg
4372 18 audio/x-scpls
4373 18 audio/x-flac
4374 18 application/x-ogg
4375 17 video/x-ms-asf
4376 17 text/html
4377 17 audio/x-musepack
4378 16 image/x-xbitmap
4379 &lt;/pre&gt;
4380
4381 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4382
4383 &lt;pre&gt;
4384 count MIME type
4385 ----- -----------------------
4386 31 text/plain
4387 31 image/png
4388 31 image/jpeg
4389 29 audio/mpeg
4390 28 application/ogg
4391 27 image/gif
4392 26 image/tiff
4393 26 audio/x-mp3
4394 23 audio/x-wav
4395 22 image/bmp
4396 21 audio/x-flac
4397 20 audio/x-mpegurl
4398 19 audio/x-mpeg
4399 18 video/x-ms-asf
4400 18 video/mpeg
4401 18 audio/x-scpls
4402 18 application/x-ogg
4403 17 audio/x-musepack
4404 16 video/x-ms-wmv
4405 16 video/x-msvideo
4406 &lt;/pre&gt;
4407
4408 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4409 information mentioned in DEP-11. I have not yet had time to look at
4410 it, but hope the PackageKit people in Debian are on top of these
4411 issues.&lt;/p&gt;
4412
4413 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4414 discovering a typo in my script.&lt;/p&gt;
4415 </description>
4416 </item>
4417
4418 <item>
4419 <title>Using modalias info to find packages handling my hardware</title>
4420 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4421 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4422 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4423 <description>&lt;p&gt;Yesterday, I wrote about the
4424 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4425 values provided by the Linux kernel&lt;/a&gt; following my hope for
4426 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4427 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4428 modalias values attached to package names can be used to map packages
4429 to hardware. This allow the system to look up and suggest relevant
4430 packages when I plug in some new hardware into my machine, and replace
4431 discover and discover-data as the database used to map hardware to
4432 packages.&lt;/p&gt;
4433
4434 &lt;p&gt;I create a modaliases file with entries like the following,
4435 containing package name, kernel module name (if relevant, otherwise
4436 the package name) and globs matching the relevant hardware
4437 modalias.&lt;/p&gt;
4438
4439 &lt;p&gt;&lt;blockquote&gt;
4440 Package: package-name
4441 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4442 &lt;/blockquote&gt;&lt;/p&gt;
4443
4444 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4445 for a given modalias value using this file.&lt;/p&gt;
4446
4447 &lt;p&gt;An entry like this would suggest the video and picture application
4448 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4449
4450 &lt;p&gt;&lt;blockquote&gt;
4451 Package: cheese
4452 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4453 &lt;/blockquote&gt;&lt;/p&gt;
4454
4455 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4456 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4457
4458 &lt;p&gt;&lt;blockquote&gt;
4459 Package: pcmciautils
4460 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4461 &lt;/blockquote&gt;&lt;/p&gt;
4462
4463 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4464 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4465
4466 &lt;p&gt;&lt;blockquote&gt;
4467 Package: colorhug-client
4468 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4469 &lt;/blockquote&gt;&lt;/p&gt;
4470
4471 &lt;p&gt;I believe the format is compatible with the format of the Packages
4472 file in the Debian archive. Ubuntu already uses their Packages file
4473 to store their mappings from packages to hardware.&lt;/p&gt;
4474
4475 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4476 announce the hardware it support in a way my prototype understand.
4477 This allow those publishing packages in an APT source outside the
4478 Debian archive as well as those backporting packages to make sure the
4479 hardware mapping are included in the package meta information. I&#39;ve
4480 tested such header in the pymissile package, and its modalias mapping
4481 is working as it should with my prototype. It even made it to Ubuntu
4482 Raring.&lt;/p&gt;
4483
4484 &lt;p&gt;To test if it was possible to look up supported hardware using only
4485 the shell tools available in the Debian installer, I wrote a shell
4486 implementation of the lookup code. The idea is to create files for
4487 each modalias and let the shell do the matching. Please check out and
4488 try the
4489 &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;
4490 shell script. It run without any extra dependencies and fetch the
4491 hardware mappings from the Debian archive and the subversion
4492 repository where I currently work on my prototype.&lt;/p&gt;
4493
4494 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4495 install yubikey-personalization:&lt;/p&gt;
4496
4497 &lt;p&gt;&lt;blockquote&gt;
4498 % ./hw-support-lookup
4499 &lt;br&gt;yubikey-personalization
4500 &lt;br&gt;%
4501 &lt;/blockquote&gt;&lt;/p&gt;
4502
4503 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4504 propose to install the pcmciautils package:&lt;/p&gt;
4505
4506 &lt;p&gt;&lt;blockquote&gt;
4507 % ./hw-support-lookup
4508 &lt;br&gt;pcmciautils
4509 &lt;br&gt;%
4510 &lt;/blockquote&gt;&lt;/p&gt;
4511
4512 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4513 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4514 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4515
4516 &lt;p&gt;It could be possible to generate several of the mappings between
4517 packages and hardware. One source would be to look at packages with
4518 kernel modules, ie packages with *.ko files in /lib/modules/, and
4519 extract their modalias information. Another would be to look at
4520 packages with udev rules, ie packages with files in
4521 /lib/udev/rules.d/, and extract their vendor/model information to
4522 generate a modalias matching rule. I have not tested any of these to
4523 see if it work.&lt;/p&gt;
4524
4525 &lt;p&gt;If you want to help implementing a system to let us propose what
4526 packages to install when new hardware is plugged into a Debian
4527 machine, please send me an email or talk to me on
4528 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4529 </description>
4530 </item>
4531
4532 <item>
4533 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4534 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4535 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4536 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4537 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4538 information, to find the packages that support a given piece of
4539 hardware, I refreshed my memory regarding modalias values, and decided
4540 to document the details. Here are my findings so far, also available
4541 in
4542 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4543 Debian Edu subversion repository&lt;/a&gt;:
4544
4545 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4546
4547 &lt;p&gt;This document try to explain what the different types of modalias
4548 values stands for. It is in part based on information from
4549 &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;,
4550 &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;,
4551 &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
4552 &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;.
4553
4554 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4555 this shell script:&lt;/p&gt;
4556
4557 &lt;pre&gt;
4558 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4559 &lt;/pre&gt;
4560
4561 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4562 using modinfo:&lt;/p&gt;
4563
4564 &lt;pre&gt;
4565 % /sbin/modinfo psmouse | grep alias:
4566 alias: serio:ty05pr*id*ex*
4567 alias: serio:ty01pr*id*ex*
4568 %
4569 &lt;/pre&gt;
4570
4571 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4572
4573 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4574 Bridge memory controller:&lt;/p&gt;
4575
4576 &lt;p&gt;&lt;blockquote&gt;
4577 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4578 &lt;/blockquote&gt;&lt;/p&gt;
4579
4580 &lt;p&gt;This represent these values:&lt;/p&gt;
4581
4582 &lt;pre&gt;
4583 v 00008086 (vendor)
4584 d 00002770 (device)
4585 sv 00001028 (subvendor)
4586 sd 000001AD (subdevice)
4587 bc 06 (bus class)
4588 sc 00 (bus subclass)
4589 i 00 (interface)
4590 &lt;/pre&gt;
4591
4592 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4593 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4594 0600. The 0600 class is a host bridge. Other useful bus values are
4595 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4596
4597 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4598 means.&lt;/p&gt;
4599
4600 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4601
4602 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4603 USB hub in a laptop:&lt;/p&gt;
4604
4605 &lt;p&gt;&lt;blockquote&gt;
4606 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4607 &lt;/blockquote&gt;&lt;/p&gt;
4608
4609 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4610
4611 &lt;pre&gt;
4612 v 1D6B (device vendor)
4613 p 0001 (device product)
4614 d 0206 (bcddevice)
4615 dc 09 (device class)
4616 dsc 00 (device subclass)
4617 dp 00 (device protocol)
4618 ic 09 (interface class)
4619 isc 00 (interface subclass)
4620 ip 00 (interface protocol)
4621 &lt;/pre&gt;
4622
4623 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4624 class is in the interface class section. For a simple USB web camera,
4625 these alias entries show up:&lt;/p&gt;
4626
4627 &lt;p&gt;&lt;blockquote&gt;
4628 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4629 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4630 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4631 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4632 &lt;/blockquote&gt;&lt;/p&gt;
4633
4634 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4635 camera), 0101 is audio control device and 0102 is audio streaming (aka
4636 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4637
4638 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4639
4640 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4641 receiver in a Thinkpad X40:&lt;/p&gt;
4642
4643 &lt;p&gt;&lt;blockquote&gt;
4644 acpi:IBM0071:PNP0511:
4645 &lt;/blockquote&gt;&lt;/p&gt;
4646
4647 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4648
4649 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4650
4651 &lt;p&gt;The DMI table contain lots of information about the computer case
4652 and model. This is an entry for a IBM Thinkpad X40, fetched from
4653 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4654
4655 &lt;p&gt;&lt;blockquote&gt;
4656 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4657 &lt;/blockquote&gt;&lt;/p&gt;
4658
4659 &lt;p&gt;The values present are&lt;/p&gt;
4660
4661 &lt;pre&gt;
4662 bvn IBM (BIOS vendor)
4663 bvr 1UETB6WW(1.66) (BIOS version)
4664 bd 06/15/2005 (BIOS date)
4665 svn IBM (system vendor)
4666 pn 2371H4G (product name)
4667 pvr ThinkPadX40 (product version)
4668 rvn IBM (board vendor)
4669 rn 2371H4G (board name)
4670 rvr NotAvailable (board version)
4671 cvn IBM (chassis vendor)
4672 ct 10 (chassis type)
4673 cvr NotAvailable (chassis version)
4674 &lt;/pre&gt;
4675
4676 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4677 found in the dmidecode source:&lt;/p&gt;
4678
4679 &lt;pre&gt;
4680 3 Desktop
4681 4 Low Profile Desktop
4682 5 Pizza Box
4683 6 Mini Tower
4684 7 Tower
4685 8 Portable
4686 9 Laptop
4687 10 Notebook
4688 11 Hand Held
4689 12 Docking Station
4690 13 All In One
4691 14 Sub Notebook
4692 15 Space-saving
4693 16 Lunch Box
4694 17 Main Server Chassis
4695 18 Expansion Chassis
4696 19 Sub Chassis
4697 20 Bus Expansion Chassis
4698 21 Peripheral Chassis
4699 22 RAID Chassis
4700 23 Rack Mount Chassis
4701 24 Sealed-case PC
4702 25 Multi-system
4703 26 CompactPCI
4704 27 AdvancedTCA
4705 28 Blade
4706 29 Blade Enclosing
4707 &lt;/pre&gt;
4708
4709 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4710 table. For example my home server is a tower, but the DMI modalias
4711 claim it is a desktop.&lt;/p&gt;
4712
4713 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4714
4715 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4716 test machine:&lt;/p&gt;
4717
4718 &lt;p&gt;&lt;blockquote&gt;
4719 serio:ty01pr00id00ex00
4720 &lt;/blockquote&gt;&lt;/p&gt;
4721
4722 &lt;p&gt;The values present are&lt;/p&gt;
4723
4724 &lt;pre&gt;
4725 ty 01 (type)
4726 pr 00 (prototype)
4727 id 00 (id)
4728 ex 00 (extra)
4729 &lt;/pre&gt;
4730
4731 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4732 the valid values are.&lt;/p&gt;
4733
4734 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4735
4736 &lt;p&gt;There are heaps of other modalias subtypes according to
4737 file2alias.c. There is the rest of the list from that source: amba,
4738 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4739 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4740 vmbus, x86cpu and zorro. I did not spend time documenting all of
4741 these, as they do not seem relevant for my intended use with mapping
4742 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4743
4744 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4745
4746 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4747 one can use the following shell script:&lt;/p&gt;
4748
4749 &lt;pre&gt;
4750 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4751 echo &quot;$id&quot; ; \
4752 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4753 done
4754 &lt;/pre&gt;
4755
4756 &lt;p&gt;The output can look like this (only the first few entries as the
4757 list is very long on my test machine):&lt;/p&gt;
4758
4759 &lt;pre&gt;
4760 acpi:ACPI0003:
4761 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4762 acpi:device:
4763 FATAL: Module acpi:device: not found.
4764 acpi:IBM0068:
4765 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4766 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4767 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4768 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4769 acpi:IBM0071:PNP0511:
4770 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4771 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4772 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4773 [...]
4774 &lt;/pre&gt;
4775
4776 &lt;p&gt;If you want to help implementing a system to let us propose what
4777 packages to install when new hardware is plugged into a Debian
4778 machine, please send me an email or talk to me on
4779 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4780
4781 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4782 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4783 in /sys/ with space in them.&lt;/p&gt;
4784 </description>
4785 </item>
4786
4787 <item>
4788 <title>Moved the pymissile Debian packaging to collab-maint</title>
4789 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4790 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4791 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4792 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4793 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4794 Launcher and updated the Debian package
4795 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4796 sure udev will fix the device permissions when it is plugged in. I
4797 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4798 hopefully make the package be proposed by jockey in Ubuntu when a user
4799 plug in his rocket launcher. In the process I moved the source to a
4800 git repository under collab-maint, to make it easier for any DD to
4801 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4802 is not very active, but the software still work for me even after five
4803 years of relative silence. The new git repository is not listed in
4804 the uploaded package yet, because I want to test the other changes a
4805 bit more before I upload the new version. If you want to check out
4806 the new version with a .desktop file included, visit the
4807 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4808 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4809 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4810 </description>
4811 </item>
4812
4813 <item>
4814 <title>Lets make hardware dongles easier to use in Debian</title>
4815 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4816 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4817 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4818 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4819 general, is that there is a great package management system with the
4820 ability to automatically install software packages by downloading them
4821 from the distribution mirrors, but no way to get it to automatically
4822 install the packages I need to use the hardware I plug into my
4823 machine. Even if the package to use it is easily available from the
4824 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4825 suggest to automatically install the python-nxt, nbc and t2n packages
4826 I need to talk to it. When I plug in a Yubikey, it could propose the
4827 yubikey-personalization package. The information required to do this
4828 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4829
4830 &lt;p&gt;Some years ago, I proposed to
4831 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4832 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4833 simple:
4834
4835 &lt;ul&gt;
4836
4837 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4838 starting when a user log in.&lt;/li&gt;
4839
4840 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4841 hardware is inserted into the computer.&lt;/li&gt;
4842
4843 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4844 database mapping to packages, and take note of any non-installed
4845 packages.&lt;/li&gt;
4846
4847 &lt;li&gt;Show a message to the user proposing to install the discovered
4848 package, and make it easy to install it.&lt;/li&gt;
4849
4850 &lt;/ul&gt;
4851
4852 &lt;p&gt;I am not sure what the best way to implement this is, but my
4853 initial idea was to use dbus events to discover new hardware, the
4854 discover database to find packages and
4855 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4856 packages.&lt;/p&gt;
4857
4858 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4859 draft package is now checked into
4860 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4861 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4862 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4863 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4864 the relevant packages in Debian, and uploaded a new version
4865 2.2013.01.09 to unstable. I also discovered that the current
4866 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4867 package in Debian no longer discovered any USB devices, because
4868 /proc/bus/usb/devices is no longer present. I ported it to use
4869 libusb as a fall back option to get it working. The fixed package
4870 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4871 because of the freeze).&lt;/p&gt;
4872
4873 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4874 desktop notification to show up (only once, the first time it is
4875 inserted):&lt;/p&gt;
4876
4877 &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;
4878
4879 &lt;p&gt;For this prototype to be really useful, some way to automatically
4880 install the proposed packages by pressing the &quot;Please install
4881 program(s)&quot; button should to be implemented.&lt;/p&gt;
4882
4883 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4884 happen, please help me update the discover-data database with mappings
4885 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4886 list the package you would like to have installed when a given
4887 hardware device is inserted into your computer, and report bugs using
4888 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4889 such mapping, please let me know.&lt;/p&gt;
4890
4891 &lt;p&gt;This prototype need more work, and there are several questions that
4892 should be considered before it is ready for production use. Is dbus
4893 the correct way to detect new hardware? At the moment I look for HAL
4894 dbus events on the system bus, because that is the events I could see
4895 on my Debian Squeeze KDE desktop. Are there better events to use?
4896 How should the user be notified? Is the desktop notification
4897 mechanism the best option, or should the background daemon raise a
4898 popup instead? How should packages be installed? When should they
4899 not be installed?&lt;/p&gt;
4900
4901 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4902 please send me an email. :)&lt;/p&gt;
4903 </description>
4904 </item>
4905
4906 <item>
4907 <title>New IRC channel for LEGO designers using Debian</title>
4908 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4909 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4910 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4911 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4912 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4913 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4914 discovered I had to build all the tools myself because none were
4915 already in Debian Squeeze. If Debian support for LEGO is something
4916 you care about, please join me on the IRC channel
4917 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4918 irc.debian.org). There is a lot that could be done to improve the
4919 Debian support for LEGO designers. For example both CAD software
4920 and Mindstorm compilers are missing. :)&lt;/p&gt;
4921
4922 &lt;p&gt;Update 2012-01-03: A
4923 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4924 including links to Lego related packages is now available.&lt;/p&gt;
4925 </description>
4926 </item>
4927
4928 <item>
4929 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4930 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4932 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4933 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4934 year! I hope next year will prove to be a good year.&lt;/p&gt;
4935
4936 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4937 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4938 between each other with minimal overhead, is a very interesting
4939 experiment. And as I wrote a few days ago, the bitcoin situation in
4940 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4941 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4942 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4943 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4944 for one of the ftpmasters to approve the new bitcoin-qt package
4945 name.&lt;/p&gt;
4946
4947 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4948 team in Debian, you can easily test the package in Debian Squeeze
4949 using the following steps to get a set of working packages:&lt;/p&gt;
4950
4951 &lt;blockquote&gt;&lt;pre&gt;
4952 git clone git://git.debian.org/git/collab-maint/bitcoin
4953 cd bitcoin
4954 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4955 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4956 &lt;/pre&gt;&lt;/blockquote&gt;
4957
4958 &lt;p&gt;You might have to install some build dependencies as well. The
4959 list of commands should give you two packages, bitcoind and
4960 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4961 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4962 around 5.6 GiB of data on my machine at the moment. Make sure your
4963 ~/.bitcoin/ directory have lots of spare room if you want to download
4964 all the blocks. The client will warn if the disk is getting full, so
4965 there is not really a problem if you got too little room, but you will
4966 not be able to get all the features out of the client.&lt;/p&gt;
4967
4968 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4969 activities, please send Bitcoin donations to my address
4970 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4971 </description>
4972 </item>
4973
4974 <item>
4975 <title>A word on bitcoin support in Debian</title>
4976 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4977 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4978 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4979 <description>&lt;p&gt;It has been a while since I wrote about
4980 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4981 peer-to-peer based crypto-currency, and the reason is simply that I
4982 have been busy elsewhere. But two days ago, I started looking at the
4983 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4984 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4985 is now maintained by a
4986 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4987 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4988 owe a huge thank you to all these team members. :)
4989 But I was sad to discover that the bitcoin client is missing in
4990 Wheezy. It is only available in Sid (and an outdated client from
4991 backports). The client had several RC bugs registered in BTS blocking
4992 it from entering testing. To try to help the team and improve the
4993 situation, I spent some time providing patches and triaging the bug
4994 reports. I also had a look at the bitcoin package available from Matt
4995 Corallo in a
4996 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4997 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4998 Debian package.&lt;/p&gt;
4999
5000 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
5001 IRC, I pushed several patches into the collab-maint git repository to
5002 improve the package. It now contains fixes for the RC issues (not from
5003 me, but fixed by Scott Howard), build rules for a Qt GUI client
5004 package, konqueror support for the bitcoin: URI and bash completion
5005 setup. As I work on Debian Squeeze, I also created
5006 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
5007 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
5008 it and try to integrate it into the git repository before uploading a
5009 new version to unstable.
5010
5011 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
5012 centralized control currently exercised in the monetary system. I
5013 find it completely unacceptable that the USA government is collecting
5014 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5015 that the major credit card companies can block legal money
5016 transactions to Wikileaks. But for bitcoin to succeed, more people
5017 need to use bitcoins, and more people need to accept bitcoins when
5018 they sell products and services. Improving the bitcoin support in
5019 Debian is a small step in the right direction, but not enough.
5020 Unfortunately the user experience when browsing the web and wanting to
5021 pay with bitcoin is still not very good. The bitcoin: URI is a step
5022 in the right direction, but need to work in most or every browser in
5023 use. Also the bitcoin-qt client is too heavy to fire up to do a
5024 quick transaction. I believe there are other clients available, but
5025 have not tested them.&lt;/p&gt;
5026
5027 &lt;p&gt;My
5028 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
5029 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
5030 I received 20.15 BTC so far on the address I provided in my blog two
5031 years ago, as can be
5032 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
5033 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
5034 donation. The blockexplorer service demonstrates quite well that
5035 bitcoin is not quite anonymous and untracked. :) I wonder if the
5036 number of users have gone up since then. If you use bitcoin and want
5037 to show your support of my activity, please send Bitcoin donations to
5038 the same address as last time,
5039 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5040 </description>
5041 </item>
5042
5043 <item>
5044 <title>Git repository for song book for Computer Scientists</title>
5045 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
5046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
5047 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
5048 <description>&lt;p&gt;As I
5049 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
5050 this summer&lt;/a&gt;, I have created a Computer Science song book a few
5051 years ago, and today I finally found time to create a public
5052 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
5053 repository for the project&lt;/a&gt;.&lt;/p&gt;
5054
5055 &lt;p&gt;If you want to help out, please clone the source and submit patches
5056 to the HTML version. To generate the PDF and PostScript version,
5057 please use prince XML, or let me know about a useful free software
5058 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
5059
5060 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
5061 PostScript formats at
5062 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
5063 Science Songbook&lt;/a&gt;.&lt;/p&gt;
5064 </description>
5065 </item>
5066
5067 <item>
5068 <title>Gratulerer med 19-årsdagen, Debian!</title>
5069 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
5070 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
5071 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
5072 <description>&lt;p&gt;I dag fyller
5073 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
5074 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
5075 si gratulerer med dagen, Debian!&lt;/p&gt;
5076 </description>
5077 </item>
5078
5079 <item>
5080 <title>Song book for Computer Scientists</title>
5081 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
5082 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
5083 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
5084 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
5085 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
5086 collecting computer related songs for use at parties. The original
5087 version was written in LaTeX, but a few years ago I got help from
5088 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5089 while keeping the ability to create a nice book in PDF format. I have
5090 not had time to maintain the book for a while now, and guess I should
5091 put it up on some public version control repository where others can
5092 help me extend and update the book. If anyone is volunteering to help
5093 me with this, send me an email. Also let me know if there are songs
5094 missing in my book.&lt;/p&gt;
5095
5096 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
5097 me today that I really should let all my readers share the joys of
5098 singing out load about programming, computers and computer networks.
5099 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
5100 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
5101 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
5102 Computer Science Songbook&lt;/a&gt;.
5103 </description>
5104 </item>
5105
5106 <item>
5107 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
5108 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
5109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
5110 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
5111 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
5112 around 1000 at the moment. To be able to get help from the vendors
5113 when something go wrong, we want to keep the firmware on the servers
5114 up to date. If the firmware isn&#39;t the latest and greatest, the
5115 vendors typically refuse to start debugging any problems until the
5116 firmware is upgraded. So before every reboot, we want to upgrade the
5117 firmware, and we would really like everyone handling servers at the
5118 university to do this themselves when they plan to reboot a machine.
5119 For that to happen we at the unix server admin group need to provide
5120 the tools to do so.&lt;/p&gt;
5121
5122 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
5123 fetch and install the latest firmware for the servers we got. Most of
5124 our hardware are from Dell and HP, so I have focused on these servers
5125 so far. This blog post is about the Dell part.&lt;/P&gt;
5126
5127 &lt;p&gt;On the Dell FTP site I was lucky enough to find
5128 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
5129 with firmware information for all 11th generation servers, listing
5130 which firmware should be used on a given model and where on the FTP
5131 site I can find it. Using a simple perl XML parser I can then
5132 download the shell scripts Dell provides to do firmware upgrades from
5133 within Linux and reboot when all the firmware is primed and ready to
5134 be activated on the first reboot.&lt;/p&gt;
5135
5136 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
5137 Are there anyone working on similar tools for firmware upgrading all
5138 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
5139
5140 &lt;p&gt;&lt;pre&gt;
5141 #!/usr/bin/perl
5142 use strict;
5143 use warnings;
5144 use File::Temp qw(tempdir);
5145 BEGIN {
5146 # Install needed RHEL packages if missing
5147 my %rhelmodules = (
5148 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
5149 );
5150 for my $module (keys %rhelmodules) {
5151 eval &quot;use $module;&quot;;
5152 if ($@) {
5153 my $pkg = $rhelmodules{$module};
5154 system(&quot;yum install -y $pkg&quot;);
5155 eval &quot;use $module;&quot;;
5156 }
5157 }
5158 }
5159 my $errorsto = &#39;pere@hungry.com&#39;;
5160
5161 upgrade_dell();
5162
5163 exit 0;
5164
5165 sub run_firmware_script {
5166 my ($opts, $script) = @_;
5167 unless ($script) {
5168 print STDERR &quot;fail: missing script name\n&quot;;
5169 exit 1
5170 }
5171 print STDERR &quot;Running $script\n\n&quot;;
5172
5173 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
5174 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
5175 } else {
5176 print STDERR &quot;fail: firmware script returned error\n&quot;;
5177 }
5178 }
5179
5180 sub run_firmware_scripts {
5181 my ($opts, @dirs) = @_;
5182 # Run firmware packages
5183 for my $dir (@dirs) {
5184 print STDERR &quot;info: Running scripts in $dir\n&quot;;
5185 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
5186 while (my $s = readdir $dh) {
5187 next if $s =~ m/^\.\.?/;
5188 run_firmware_script($opts, &quot;$dir/$s&quot;);
5189 }
5190 closedir $dh;
5191 }
5192 }
5193
5194 sub download {
5195 my $url = shift;
5196 print STDERR &quot;info: Downloading $url\n&quot;;
5197 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
5198 }
5199
5200 sub upgrade_dell {
5201 my @dirs;
5202 my $product = `dmidecode -s system-product-name`;
5203 chomp $product;
5204
5205 if ($product =~ m/PowerEdge/) {
5206
5207 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5208 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
5209
5210 my $tmpdir = tempdir(
5211 CLEANUP =&gt; 1
5212 );
5213 chdir($tmpdir);
5214 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
5215 system(&#39;gunzip Catalog.xml.gz&#39;);
5216 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
5217 # -q is quiet, disabling interactivity and reducing console output
5218 my $fwopts = &quot;-q&quot;;
5219 if (@paths) {
5220 for my $url (@paths) {
5221 fetch_dell_fw($url);
5222 }
5223 run_firmware_scripts($fwopts, $tmpdir);
5224 } else {
5225 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5226 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5227 }
5228 chdir(&#39;/&#39;);
5229 } else {
5230 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5231 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5232 }
5233 }
5234
5235 sub fetch_dell_fw {
5236 my $path = shift;
5237 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
5238 download($url);
5239 }
5240
5241 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5242 # firmware packages to download from Dell. Only work for Linux
5243 # machines and 11th generation Dell servers.
5244 sub fetch_dell_fw_list {
5245 my $filename = shift;
5246
5247 my $product = `dmidecode -s system-product-name`;
5248 chomp $product;
5249 my ($mybrand, $mymodel) = split(/\s+/, $product);
5250
5251 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
5252
5253 my $xml = XMLin($filename);
5254 my @paths;
5255 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
5256 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
5257 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
5258 my $oscode;
5259 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
5260 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
5261 } else {
5262 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
5263 }
5264 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
5265 {
5266 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
5267 }
5268 }
5269 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
5270 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
5271
5272 # Drop application packages, only firmware and BIOS
5273 next if &#39;APAC&#39; eq $componenttype;
5274
5275 my $cpath = $component-&gt;{path};
5276 for my $path (@paths) {
5277 if ($cpath =~ m%/$path$%) {
5278 push(@paths, $cpath);
5279 }
5280 }
5281 }
5282 return @paths;
5283 }
5284 &lt;/pre&gt;
5285
5286 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5287 it could work on other platforms with some tweaking. Anyone know a
5288 index like Catalog.xml is available from HP for HP servers? At the
5289 moment I maintain a similar list manually and it is quickly getting
5290 outdated.&lt;/p&gt;
5291 </description>
5292 </item>
5293
5294 <item>
5295 <title>How is booting into runlevel 1 different from single user boots?</title>
5296 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5297 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5298 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5299 <description>&lt;p&gt;Wouter Verhelst have some
5300 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5301 comments and opinions&lt;/a&gt; on my blog post on
5302 &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
5303 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5304 &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
5305 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5306 small piece of his comment now, and though it best to address the
5307 misunderstanding he bring forward:&lt;/p&gt;
5308
5309 &lt;p&gt;&lt;blockquote&gt;
5310 Currently, a system admin has four options: [...] boot to a
5311 single-user system (by adding &#39;single&#39; to the kernel command line;
5312 this runs rcS and rc1 scripts)
5313 &lt;/blockquote&gt;&lt;/p&gt;
5314
5315 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5316 and booting into runlevel 1 is the same. I am not surprised he
5317 believe this, because it would make sense and is a quite sensible
5318 thing to believe. But because the boot in Debian is slightly broken,
5319 runlevel 1 do not work properly and it isn&#39;t the same as single user
5320 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5321 hard to explain.&lt;/p&gt;
5322
5323 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5324 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5325 executed in single user mode is sulogin. Single user mode is a boot
5326 state &quot;between&quot; the runlevels, and when booting into single user mode,
5327 only the scripts in /etc/rcS.d/ are executed before the init process
5328 enters the single user state. When switching to runlevel 1, the state
5329 is in fact not ending in runlevel 1, but it passes through runlevel 1
5330 and end up in the single user mode (see /etc/rc1.d/S03single, which
5331 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5332 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5333 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5334 mode).&lt;/p&gt;
5335
5336 &lt;p&gt;This summary might make it clearer. When booting for the first
5337 time into single user mode, the following commands are executed:
5338 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5339 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5340 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5341 trying to continue after visiting single user mode. Not all services
5342 are started again as they should, causing the machine to end up in an
5343 unpredicatble state. This is why Debian admins recommend rebooting
5344 after visiting single user mode.&lt;/p&gt;
5345
5346 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5347 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5348 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5349 stopped when passing through the scripts in /etc/rc1.d/, and not
5350 started again when switching away from runlevel 1 to the runlevels
5351 2-5. I believe the problem is best fixed by moving all the scripts
5352 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5353 functioning single user mode during boot.&lt;/p&gt;
5354
5355 &lt;p&gt;I have spent several years investigating the Debian boot system,
5356 and discovered this problem a few years ago. I suspect it originates
5357 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5358 </description>
5359 </item>
5360
5361 <item>
5362 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5363 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5364 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5365 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5366 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5367 are started from /etc/rcS.d/. In fact, there is a bite more of them
5368 than make sense, and this causes a few problems. What kind of
5369 problems, you might ask. There are at least two problems. The first
5370 is that it is not possible to recover a machine after switching to
5371 runlevel 1. One need to actually reboot to get the machine back to
5372 the expected state. The other is that single user boot will sometimes
5373 run into problems because some of the subsystems are activated before
5374 the root login is presented, causing problems when trying to recover a
5375 machine from a problem in that subsystem. A minor additional point is
5376 that moving more scripts out of rcS.d/ and into the other rc#.d/
5377 directories will increase the amount of scripts that can run in
5378 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5379
5380 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5381 scripts that _have_ to execute before the root login prompt is
5382 presented during a single user boot should go there. Everything else
5383 should go into the numeric runlevels. This means things like
5384 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5385 the numeric runlevels. Today in Debian, there are around 115 init.d
5386 scripts that are started from rcS.d/, and most of them should be moved
5387 out. Do your package have one of them? Please help us make single
5388 user and runlevel 1 better by moving it.&lt;/p&gt;
5389
5390 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5391 etc. should still be started from rcS.d/, but there is for example no
5392 need to have the network enabled before the single user login prompt
5393 is presented.&lt;/p&gt;
5394
5395 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5396 Debian systems working while scripts migrate and during upgrades, the
5397 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5398 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5399 and the next ones can only be moved when their dependencies have been
5400 moved first. This migration must be done sequentially while we ensure
5401 that the package system upgrade packages in the right order to keep
5402 the system state correct. This will require some coordination when it
5403 comes to network related packages, but most of the packages with
5404 scripts that should migrate do not have anything in rcS.d/ depending
5405 on them. Some packages have already been updated, like the sudo
5406 package, while others are still left to do. I wish I had time to work
5407 on this myself, but real live constrains make it unlikely that I will
5408 find time to push this forward.&lt;/p&gt;
5409 </description>
5410 </item>
5411
5412 <item>
5413 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5414 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5415 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5416 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5417 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5418 mentioned the issues I believe should be improved in Debian for its
5419 desktop to be useful for more people. The use case for this is my
5420 parents, which are currently running Kubuntu which solve the
5421 issues.&lt;/p&gt;
5422
5423 &lt;p&gt;I suspect these four missing features are not very hard to
5424 implement. After all, they are present in Ubuntu, so if we wanted to
5425 do this in Debian we would have a source.&lt;/p&gt;
5426
5427 &lt;ol&gt;
5428
5429 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5430 are new packages available for upgrades, a icon in the KDE status bar
5431 indicate this, and clicking on it will activate the simple upgrade
5432 tool to handle it. I have no problem guiding both of my parents
5433 through the process over the phone. If a kernel reboot is required,
5434 this too is indicated by the status bars and the upgrade tool. Last
5435 time I checked, nothing with the same features was working in KDE in
5436 Debian.&lt;/li&gt;
5437
5438 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5439 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5440 currently have a handler for, it will ask the user if the system
5441 should search for a package that would add support for this MIME type,
5442 and if the user say yes, the APT sources will be searched for packages
5443 advertising the MIME type in their control file (visible in the
5444 Packages file in the APT archive). If one or more packages are found,
5445 it is a simple click of the mouse to add support for the missing mime
5446 type. If the package require the user to accept some non-free
5447 license, this is explained to the user. The entire process make it
5448 more clear to the user why something do not work in the browser, and
5449 make the chances higher for the user to blame the web page authors and
5450 not the browser for any missing features.&lt;/li&gt;
5451
5452 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5453 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5454 it is not supporting, a dialog pop up asking the user if the system
5455 should search for a package that would add support for it. This
5456 happen with things like MP3, Windows Media or H.264. The selection
5457 and installation procedure is very similar to the Firefox browser
5458 plugin handling. This is as far as I know implemented using a
5459 gstreamer hook. The end result is that the user easily get access to
5460 the codecs that are present from the APT archives available, while
5461 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5462
5463 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5464 displaying a text/plain file in my Debian browser, it will propose to
5465 start emacs to show it. If I remember correctly, when doing the same
5466 in Kunbutu it show the file as a text file in the browser. At least I
5467 know Opera will show text files within the browser. I much prefer the
5468 latter behaviour.&lt;/li&gt;
5469
5470 &lt;/ol&gt;
5471
5472 &lt;p&gt;There are other nice features as well, like the simplified suite
5473 upgrader, but given that I am the one mostly doing the dist-upgrade,
5474 it do not matter much.&lt;/p&gt;
5475
5476 &lt;p&gt;I really hope we could get these features in place for the next
5477 Debian release. It would require the coordinated effort of several
5478 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5479 </description>
5480 </item>
5481
5482 <item>
5483 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5484 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5485 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5486 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5487 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5488 site is build on Debian/Squeeze, and this platform was chosen because
5489 I am most familiar with Debian (being a Debian Developer for around 10
5490 years) because it is the latest stable Debian release which should get
5491 security support for a few years.&lt;/p&gt;
5492
5493 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5494 that are missing in Debian at the moment. It would be great if these
5495 modules were added to the Debian archive, allowing anyone to set up
5496 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5497 in their own country using only Debian packages. The list of modules
5498 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5499 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5500 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5501 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5502 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5503 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5504 easier in the future.&lt;/p&gt;
5505
5506 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5507 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5508 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5509 with the responsibility of tracking security problems, which I really
5510 do not have time for.&lt;/p&gt;
5511 </description>
5512 </item>
5513
5514 <item>
5515 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5516 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5517 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5518 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5519 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5520 posts have been in Norwegian the last few weeks, so here is a short
5521 update in English.&lt;/p&gt;
5522
5523 &lt;p&gt;The kids still keep me too busy to get much free software work
5524 done, but I did manage to organise a project to get a Norwegian port
5525 of the British service
5526 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5527 and it has been running for a month now. The entire project has been
5528 organised by me and two others. Around Christmas we gathered sponsors
5529 to fund the development work. In January I drafted a contract with
5530 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5531 and in February the development took place. Most of it involved
5532 converting the source to use GPS coordinates instead of British
5533 easting/northing, and the resulting code should be a lot easier to get
5534 running in any country by now. The Norwegian
5535 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5536 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5537 source and the source for administrative borders in Norway, and
5538 support for this had to be added/fixed.&lt;/p&gt;
5539
5540 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5541 polishing the system before we announced it March 7th. The system is
5542 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5543 problem reports in a few weeks. Soon we hope to announce the Android
5544 and iPhone versions making it even easier to report problems with the
5545 public infrastructure.&lt;/p&gt;
5546
5547 &lt;p&gt;Perhaps something to consider for those of you in countries without
5548 such service?&lt;/p&gt;
5549 </description>
5550 </item>
5551
5552 <item>
5553 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5554 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5555 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5556 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5557 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5558 issues here at my work with the University of Oslo. My idea is that
5559 it should be possible to use the information about security issues
5560 available on the Internet, and check our locally
5561 maintained/distributed software against this information. It should
5562 allow us to verify that no known security issues are forgotten. The
5563 CVE database listing vulnerabilities seem like a great central point,
5564 and by using the package lists from Debian mapped to CVEs provided by
5565 the testing security team, I believed it should be possible to figure
5566 out which security holes were present in our free software
5567 collection.&lt;/p&gt;
5568
5569 &lt;p&gt;After reading up on the topic, it became obvious that the first
5570 building block is to be able to name software packages in a unique and
5571 consistent way across data sources. I considered several ways to do
5572 this, for example coming up with my own naming scheme like using URLs
5573 to project home pages or URLs to the Freshmeat entries, or using some
5574 existing naming scheme. And it seem like I am not the first one to
5575 come across this problem, as MITRE already proposed and implemented a
5576 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5577 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5578 software, hardware and other platform components. The CPE ids are
5579 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5580 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5581 issues for any CPE name. With this in place, all I need to do is to
5582 locate the CPE id for the software packages we use at the university.
5583 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5584 NVD entry if a CVE for the package exist).&lt;/p&gt;
5585
5586 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5587 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5588 check out, one could look up
5589 &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
5590 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5591 The most recent one is
5592 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5593 and at the bottom of the NVD page for this vulnerability the complete
5594 list of affected versions is provided.&lt;/p&gt;
5595
5596 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5597 for offline processing of issues. Using this dump, I&#39;ve written a
5598 small script taking a list of CPEs as input and list all CVEs
5599 affecting the packages represented by these CPEs. One give it CPEs
5600 with version numbers as specified above and get a list of open
5601 security issues out.&lt;/p&gt;
5602
5603 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5604 information need to be high. For that to happen, I believe as many as
5605 possible need to use and contribute to the NVD database. I notice
5606 RHEL is providing
5607 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5608 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5609 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5610
5611 &lt;p&gt;To get an idea about the quality for free software, I spent some
5612 time making it possible to compare the CVE database from Debian with
5613 the CVE database in NVD. The result look fairly good, but there are
5614 some inconsistencies in NVD (same software package having several
5615 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5616 Debian believe are affected by a CVE). Hope to find time to improve
5617 the quality of NVD, but that require being able to get in touch with
5618 someone maintaining it. So far my three emails with questions and
5619 corrections have not seen any reply, but I hope contact can be
5620 established soon.&lt;/p&gt;
5621
5622 &lt;p&gt;An interesting application for CPEs is cross platform package
5623 mapping. It would be useful to know which packages in for example
5624 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5625 this would be trivial if all linux distributions provided CPE entries
5626 for their packages.&lt;/p&gt;
5627 </description>
5628 </item>
5629
5630 <item>
5631 <title>Which module is loaded for a given PCI and USB device?</title>
5632 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5633 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5634 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5635 <description>&lt;p&gt;In the
5636 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5637 package in Debian, there is a script to report useful information
5638 about the running hardware for use when people report missing
5639 information. One part of this script that I find very useful when
5640 debugging hardware problems, is the part mapping loaded kernel module
5641 to the PCI device it claims. It allow me to quickly see if the kernel
5642 module I expect is driving the hardware I am struggling with. To see
5643 the output, make sure discover-data is installed and run
5644 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5645 one of my machines like this:&lt;/p&gt;
5646
5647 &lt;pre&gt;
5648 loaded modules:
5649 10de:03eb i2c_nforce2
5650 10de:03f1 ohci_hcd
5651 10de:03f2 ehci_hcd
5652 10de:03f0 snd_hda_intel
5653 10de:03ec pata_amd
5654 10de:03f6 sata_nv
5655 1022:1103 k8temp
5656 109e:036e bttv
5657 109e:0878 snd_bt87x
5658 11ab:4364 sky2
5659 &lt;/pre&gt;
5660
5661 &lt;p&gt;The code in question look like this, slightly modified for
5662 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5663
5664 &lt;pre&gt;
5665 if [ -d /sys/bus/pci/devices/ ] ; then
5666 echo loaded pci modules:
5667 (
5668 cd /sys/bus/pci/devices/
5669 for address in * ; do
5670 if [ -d &quot;$address/driver/module&quot; ] ; then
5671 module=`cd $address/driver/module ; pwd -P | xargs basename`
5672 if grep -q &quot;^$module &quot; /proc/modules ; then
5673 address=$(echo $address |sed s/0000://)
5674 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5675 echo &quot;$id $module&quot;
5676 fi
5677 fi
5678 done
5679 )
5680 echo
5681 fi
5682 &lt;/pre&gt;
5683
5684 &lt;p&gt;Similar code could be used to extract USB device module
5685 mappings:&lt;/p&gt;
5686
5687 &lt;pre&gt;
5688 if [ -d /sys/bus/usb/devices/ ] ; then
5689 echo loaded usb modules:
5690 (
5691 cd /sys/bus/usb/devices/
5692 for address in * ; do
5693 if [ -d &quot;$address/driver/module&quot; ] ; then
5694 module=`cd $address/driver/module ; pwd -P | xargs basename`
5695 if grep -q &quot;^$module &quot; /proc/modules ; then
5696 address=$(echo $address |sed s/0000://)
5697 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5698 if [ &quot;$id&quot; ] ; then
5699 echo &quot;$id $module&quot;
5700 fi
5701 fi
5702 fi
5703 done
5704 )
5705 echo
5706 fi
5707 &lt;/pre&gt;
5708
5709 &lt;p&gt;This might perhaps be something to include in other tools as
5710 well.&lt;/p&gt;
5711 </description>
5712 </item>
5713
5714 <item>
5715 <title>How to test if a laptop is working with Linux</title>
5716 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5717 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5718 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5719 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5720 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5721 batch of computers will work with Linux. Every year for the last few
5722 years the university have organised shared bid of a few thousand
5723 computers, and this year HP won the bid. Two different desktops and
5724 five different laptops are on the list this year. We in the UNIX
5725 group want to know which one of these computers work well with RHEL
5726 and Ubuntu, the two Linux distributions we currently handle at the
5727 university.&lt;/p&gt;
5728
5729 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5730 perhaps inspire others to test hardware as well. To test, I PXE
5731 install the OS version of choice, and log in as my normal user and run
5732 a few applications and plug in selected pieces of hardware. When
5733 something fail, I make a note about this in the test matrix and move
5734 on. If I have some spare time I try to report the bug to the OS
5735 vendor, but as I only have the machines for a short time, I rarely
5736 have the time to do this for all the problems I find.&lt;/p&gt;
5737
5738 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5739 I perform on a new model.&lt;/p&gt;
5740
5741 &lt;ul&gt;
5742
5743 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5744 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5745 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5746
5747 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5748 installation, X.org is working.&lt;/li&gt;
5749
5750 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5751 package mesa-utils on Ubuntu) and writing down the frames per second
5752 reported by the program.&lt;/li&gt;
5753
5754 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5755 logging in, and if I can hear this the test is successful. If there
5756 are several audio exits on the machine, I try them all and check if
5757 the Gnome/KDE audio mixer can control where to send the sound. I
5758 normally test this by playing
5759 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5760 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5761
5762 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5763 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5764
5765 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5766 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5767
5768 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5769 picture from the v4l device show up.&lt;/li&gt;
5770
5771 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5772 any bluetooth devices are discovered. In my office, I normally see a
5773 few.&lt;/li&gt;
5774
5775 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5776 memory modules lying around, and stick them in and see if Gnome/KDE
5777 notice this.&lt;/li&gt;
5778
5779 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5780 special button work, and if the laptop continue to work after
5781 resume.&lt;/li&gt;
5782
5783 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5784 adjusting background light, switching on/off external video output,
5785 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5786 laptop to laptop, so I just write down which are working and which are
5787 not.&lt;/li&gt;
5788
5789 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5790 acceleration sensors etc. I rarely test these, as I do not know how
5791 to quickly test if they are working or not, so I only document their
5792 existence.&lt;/li&gt;
5793
5794 &lt;/ul&gt;
5795
5796 &lt;p&gt;By now I suspect you are really curious what the test results are
5797 for the HP machines I am testing. I&#39;m not done yet, so I will report
5798 the test results later. For now I can report that HP 8100 Elite work
5799 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5800 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5801 can see, I have most machines left to test. One interesting
5802 observation is that Ubuntu Lucid has almost twice the frame rate than
5803 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5804 </description>
5805 </item>
5806
5807 <item>
5808 <title>Some thoughts on BitCoins</title>
5809 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5810 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5811 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5812 <description>&lt;p&gt;As I continue to explore
5813 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5814 what properties the system have, and how it will be affected by laws
5815 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5816
5817 &lt;p&gt;One interesting thing to note is that since the transactions are
5818 verified using a peer to peer network, all details about a transaction
5819 is known to everyone. This means that if a BitCoin address has been
5820 published like I did with mine in my initial post about BitCoin, it is
5821 possible for everyone to see how many BitCoins have been transfered to
5822 that address. There is even a web service to look at the details for
5823 all transactions. There I can see that my address
5824 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5825 have received 16.06 Bitcoin, the
5826 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5827 address of Simon Phipps have received 181.97 BitCoin and the address
5828 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5829 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5830 every one of you that donated bitcoins to support my activity. The
5831 fact that anyone can see how much money was transfered to a given
5832 address make it more obvious why the BitCoin community recommend to
5833 generate and hand out a new address for each transaction. I&#39;m told
5834 there is no way to track which addresses belong to a given person or
5835 organisation without the person or organisation revealing it
5836 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5837
5838 &lt;p&gt;In Norway, and in most other countries, there are laws and
5839 regulations limiting how much money one can transfer across the border
5840 without declaring it. There are money laundering, tax and accounting
5841 laws and regulations I would expect to apply to the use of BitCoin.
5842 If the Skolelinux foundation
5843 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5844 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5845 normal bank transfers like EFF is doing, how should this be accounted?
5846 Given that it is impossible to know if money can cross the border or
5847 not, should everything or nothing be declared? What exchange rate
5848 should be used when calculating taxes? Would receivers have to pay
5849 income tax if the foundation were to pay Skolelinux contributors in
5850 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5851
5852 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5853 accepted by a lot of users. It must be possible to get easy access to
5854 the currency (as a wage or using currency exchanges), and it must be
5855 easy to spend it. At the moment BitCoin seem fairly easy to get
5856 access to, but there are very few places to spend it. I am not really
5857 a regular user of any of the vendor types currently accepting BitCoin,
5858 so I wonder when my kind of shop would start accepting BitCoins. I
5859 would like to buy electronics, travels and subway tickets, not herbs
5860 and books. :) The currency is young, and this will improve over time
5861 if it become popular, but I suspect regular banks will start to lobby
5862 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5863 will claim it is helping fund terrorism and money laundering (which
5864 probably would be true, as is any currency in existence), but I
5865 believe the problems should be solved elsewhere and not by blaming
5866 currencies.&lt;/p&gt;
5867
5868 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5869 CPU intensive process that depend on a bit of luck as well (as one is
5870 competing against all the other miners currently spending CPU cycles
5871 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5872 BitCoin when this happen. Yesterday I came across the obvious way to
5873 join forces to increase ones changes of getting at least some coins,
5874 by coordinating the work on mining BitCoins across several machines
5875 and people, and sharing the result if one is lucky and get the 50
5876 BitCoins. Check out
5877 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5878 if this sounds interesting. I have not had time to try to set up a
5879 machine to participate there yet, but have seen that running on ones
5880 own for a few days have not yield any BitCoins througth mining
5881 yet.&lt;/p&gt;
5882
5883 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5884 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5885 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5886 it was interesting to read. The arguments presented seem to be
5887 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5888 </description>
5889 </item>
5890
5891 <item>
5892 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5893 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5894 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5895 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5896 <description>&lt;p&gt;With this weeks lawless
5897 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5898 attacks&lt;/a&gt; on Wikileak and
5899 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5900 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5901 not be trusted to handle money transactions.
5902 A blog post from
5903 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5904 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5905 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5906 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5907 some help from my friend to get it all running, and he even handed me
5908 some bitcoins to get started. I even donated a few bitcoins to Simon
5909 for helping me remember BitCoin.&lt;/p&gt;
5910
5911 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5912 crypto-currency, decentralised and handled using peer-to-peer
5913 networks. It allows anonymous transactions and prohibits central
5914 control over the transactions, making it impossible for governments
5915 and companies alike to block donations and other transactions. The
5916 source is free software, and while the key dependency wxWidgets 2.9
5917 for the graphical user interface is missing in Debian, the command
5918 line client builds just fine. Hopefully Jonas
5919 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5920 Debian&lt;/a&gt; soon.&lt;/p&gt;
5921
5922 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5923 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5924 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5925 currency &quot;stock&quot; markets where the exchange rate is decided. There
5926 are not many users so far, but the concept seems promising. If you
5927 want to get started and lack a friend with any bitcoins to spare,
5928 you can even get
5929 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5930 bitcoin at the time of writing). Use
5931 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5932 on the current exchange rates.&lt;/p&gt;
5933
5934 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5935 machines. If you want to support my activity, please send Bitcoin
5936 donations to the address
5937 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5938 </description>
5939 </item>
5940
5941 <item>
5942 <title>Why isn&#39;t Debian Edu using VLC?</title>
5943 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5944 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5945 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5946 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5947 presented, and the winner among the multimedia player were VLC.
5948 Personally, I like VLC, and it is my player of choice when I first try
5949 to play a video file or stream. Only if VLC fail will I drag out
5950 gmplayer to see if it can do better. The reason is mostly the failure
5951 model and trust. When VLC fail, it normally pop up a error message
5952 reporting the problem. When mplayer fail, it normally segfault or
5953 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5954
5955 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5956 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5957 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5958 plugin to play web videos seamlessly, and the VLC browser plugin is
5959 not very good. For example, it lack in-line control buttons, so there
5960 is no way for the user to pause the video. Also, when I
5961 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5962 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5963 failed on several video pages where mplayer based plugins worked. If
5964 the browser plugin for VLC was as good as the gecko-mediaplayer
5965 package (which uses mplayer), we would switch.&lt;/P&gt;
5966
5967 &lt;p&gt;While VLC is a good player, its user interface is slightly
5968 annoying. The most annoying feature is its inconsistent use of
5969 keyboard shortcuts. When the player is in full screen mode, its
5970 shortcuts are different from when it is playing the video in a window.
5971 For example, space only work as pause when in full screen mode. I
5972 wish it had consisten shortcuts and that space also would work when in
5973 window mode. Another nice shortcut in gmplayer is [enter] to restart
5974 the current video. It is very nice when playing short videos from the
5975 web and want to restart it when new people arrive to have a look at
5976 what is going on.&lt;/p&gt;
5977 </description>
5978 </item>
5979
5980 <item>
5981 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5982 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5983 <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>
5984 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5985 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5986 upgrade testing of the
5987 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5988 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5989 This seem like a very good idea, so I adjusted by test scripts and
5990 can now present the updated result from today:&lt;/p&gt;
5991
5992 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5993
5994 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5995
5996 &lt;blockquote&gt;&lt;p&gt;
5997 apache2.2-bin
5998 aptdaemon
5999 baobab
6000 binfmt-support
6001 browser-plugin-gnash
6002 cheese-common
6003 cli-common
6004 cups-pk-helper
6005 dmz-cursor-theme
6006 empathy
6007 empathy-common
6008 freedesktop-sound-theme
6009 freeglut3
6010 gconf-defaults-service
6011 gdm-themes
6012 gedit-plugins
6013 geoclue
6014 geoclue-hostip
6015 geoclue-localnet
6016 geoclue-manual
6017 geoclue-yahoo
6018 gnash
6019 gnash-common
6020 gnome
6021 gnome-backgrounds
6022 gnome-cards-data
6023 gnome-codec-install
6024 gnome-core
6025 gnome-desktop-environment
6026 gnome-disk-utility
6027 gnome-screenshot
6028 gnome-search-tool
6029 gnome-session-canberra
6030 gnome-system-log
6031 gnome-themes-extras
6032 gnome-themes-more
6033 gnome-user-share
6034 gstreamer0.10-fluendo-mp3
6035 gstreamer0.10-tools
6036 gtk2-engines
6037 gtk2-engines-pixbuf
6038 gtk2-engines-smooth
6039 hamster-applet
6040 libapache2-mod-dnssd
6041 libapr1
6042 libaprutil1
6043 libaprutil1-dbd-sqlite3
6044 libaprutil1-ldap
6045 libart2.0-cil
6046 libboost-date-time1.42.0
6047 libboost-python1.42.0
6048 libboost-thread1.42.0
6049 libchamplain-0.4-0
6050 libchamplain-gtk-0.4-0
6051 libcheese-gtk18
6052 libclutter-gtk-0.10-0
6053 libcryptui0
6054 libdiscid0
6055 libelf1
6056 libepc-1.0-2
6057 libepc-common
6058 libepc-ui-1.0-2
6059 libfreerdp-plugins-standard
6060 libfreerdp0
6061 libgconf2.0-cil
6062 libgdata-common
6063 libgdata7
6064 libgdu-gtk0
6065 libgee2
6066 libgeoclue0
6067 libgexiv2-0
6068 libgif4
6069 libglade2.0-cil
6070 libglib2.0-cil
6071 libgmime2.4-cil
6072 libgnome-vfs2.0-cil
6073 libgnome2.24-cil
6074 libgnomepanel2.24-cil
6075 libgpod-common
6076 libgpod4
6077 libgtk2.0-cil
6078 libgtkglext1
6079 libgtksourceview2.0-common
6080 libmono-addins-gui0.2-cil
6081 libmono-addins0.2-cil
6082 libmono-cairo2.0-cil
6083 libmono-corlib2.0-cil
6084 libmono-i18n-west2.0-cil
6085 libmono-posix2.0-cil
6086 libmono-security2.0-cil
6087 libmono-sharpzip2.84-cil
6088 libmono-system2.0-cil
6089 libmtp8
6090 libmusicbrainz3-6
6091 libndesk-dbus-glib1.0-cil
6092 libndesk-dbus1.0-cil
6093 libopal3.6.8
6094 libpolkit-gtk-1-0
6095 libpt2.6.7
6096 libpython2.6
6097 librpm1
6098 librpmio1
6099 libsdl1.2debian
6100 libsrtp0
6101 libssh-4
6102 libtelepathy-farsight0
6103 libtelepathy-glib0
6104 libtidy-0.99-0
6105 media-player-info
6106 mesa-utils
6107 mono-2.0-gac
6108 mono-gac
6109 mono-runtime
6110 nautilus-sendto
6111 nautilus-sendto-empathy
6112 p7zip-full
6113 pkg-config
6114 python-aptdaemon
6115 python-aptdaemon-gtk
6116 python-axiom
6117 python-beautifulsoup
6118 python-bugbuddy
6119 python-clientform
6120 python-coherence
6121 python-configobj
6122 python-crypto
6123 python-cupshelpers
6124 python-elementtree
6125 python-epsilon
6126 python-evolution
6127 python-feedparser
6128 python-gdata
6129 python-gdbm
6130 python-gst0.10
6131 python-gtkglext1
6132 python-gtksourceview2
6133 python-httplib2
6134 python-louie
6135 python-mako
6136 python-markupsafe
6137 python-mechanize
6138 python-nevow
6139 python-notify
6140 python-opengl
6141 python-openssl
6142 python-pam
6143 python-pkg-resources
6144 python-pyasn1
6145 python-pysqlite2
6146 python-rdflib
6147 python-serial
6148 python-tagpy
6149 python-twisted-bin
6150 python-twisted-conch
6151 python-twisted-core
6152 python-twisted-web
6153 python-utidylib
6154 python-webkit
6155 python-xdg
6156 python-zope.interface
6157 remmina
6158 remmina-plugin-data
6159 remmina-plugin-rdp
6160 remmina-plugin-vnc
6161 rhythmbox-plugin-cdrecorder
6162 rhythmbox-plugins
6163 rpm-common
6164 rpm2cpio
6165 seahorse-plugins
6166 shotwell
6167 software-center
6168 system-config-printer-udev
6169 telepathy-gabble
6170 telepathy-mission-control-5
6171 telepathy-salut
6172 tomboy
6173 totem
6174 totem-coherence
6175 totem-mozilla
6176 totem-plugins
6177 transmission-common
6178 xdg-user-dirs
6179 xdg-user-dirs-gtk
6180 xserver-xephyr
6181 &lt;/p&gt;&lt;/blockquote&gt;
6182
6183 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6184
6185 &lt;blockquote&gt;&lt;p&gt;
6186 cheese
6187 ekiga
6188 eog
6189 epiphany-extensions
6190 evolution-exchange
6191 fast-user-switch-applet
6192 file-roller
6193 gcalctool
6194 gconf-editor
6195 gdm
6196 gedit
6197 gedit-common
6198 gnome-games
6199 gnome-games-data
6200 gnome-nettool
6201 gnome-system-tools
6202 gnome-themes
6203 gnuchess
6204 gucharmap
6205 guile-1.8-libs
6206 libavahi-ui0
6207 libdmx1
6208 libgalago3
6209 libgtk-vnc-1.0-0
6210 libgtksourceview2.0-0
6211 liblircclient0
6212 libsdl1.2debian-alsa
6213 libspeexdsp1
6214 libsvga1
6215 rhythmbox
6216 seahorse
6217 sound-juicer
6218 system-config-printer
6219 totem-common
6220 transmission-gtk
6221 vinagre
6222 vino
6223 &lt;/p&gt;&lt;/blockquote&gt;
6224
6225 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6226
6227 &lt;blockquote&gt;&lt;p&gt;
6228 gstreamer0.10-gnomevfs
6229 &lt;/p&gt;&lt;/blockquote&gt;
6230
6231 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6232
6233 &lt;blockquote&gt;&lt;p&gt;
6234 [nothing]
6235 &lt;/p&gt;&lt;/blockquote&gt;
6236
6237 &lt;p&gt;This is for KDE:&lt;/p&gt;
6238
6239 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6240
6241 &lt;blockquote&gt;&lt;p&gt;
6242 ksmserver
6243 &lt;/p&gt;&lt;/blockquote&gt;
6244
6245 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6246
6247 &lt;blockquote&gt;&lt;p&gt;
6248 kwin
6249 network-manager-kde
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 arts
6256 dolphin
6257 freespacenotifier
6258 google-gadgets-gst
6259 google-gadgets-xul
6260 kappfinder
6261 kcalc
6262 kcharselect
6263 kde-core
6264 kde-plasma-desktop
6265 kde-standard
6266 kde-window-manager
6267 kdeartwork
6268 kdeartwork-emoticons
6269 kdeartwork-style
6270 kdeartwork-theme-icon
6271 kdebase
6272 kdebase-apps
6273 kdebase-workspace
6274 kdebase-workspace-bin
6275 kdebase-workspace-data
6276 kdeeject
6277 kdelibs
6278 kdeplasma-addons
6279 kdeutils
6280 kdewallpapers
6281 kdf
6282 kfloppy
6283 kgpg
6284 khelpcenter4
6285 kinfocenter
6286 konq-plugins-l10n
6287 konqueror-nsplugins
6288 kscreensaver
6289 kscreensaver-xsavers
6290 ktimer
6291 kwrite
6292 libgle3
6293 libkde4-ruby1.8
6294 libkonq5
6295 libkonq5-templates
6296 libnetpbm10
6297 libplasma-ruby
6298 libplasma-ruby1.8
6299 libqt4-ruby1.8
6300 marble-data
6301 marble-plugins
6302 netpbm
6303 nuvola-icon-theme
6304 plasma-dataengines-workspace
6305 plasma-desktop
6306 plasma-desktopthemes-artwork
6307 plasma-runners-addons
6308 plasma-scriptengine-googlegadgets
6309 plasma-scriptengine-python
6310 plasma-scriptengine-qedje
6311 plasma-scriptengine-ruby
6312 plasma-scriptengine-webkit
6313 plasma-scriptengines
6314 plasma-wallpapers-addons
6315 plasma-widget-folderview
6316 plasma-widget-networkmanagement
6317 ruby
6318 sweeper
6319 update-notifier-kde
6320 xscreensaver-data-extra
6321 xscreensaver-gl
6322 xscreensaver-gl-extra
6323 xscreensaver-screensaver-bsod
6324 &lt;/p&gt;&lt;/blockquote&gt;
6325
6326 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6327
6328 &lt;blockquote&gt;&lt;p&gt;
6329 ark
6330 google-gadgets-common
6331 google-gadgets-qt
6332 htdig
6333 kate
6334 kdebase-bin
6335 kdebase-data
6336 kdepasswd
6337 kfind
6338 klipper
6339 konq-plugins
6340 konqueror
6341 ksysguard
6342 ksysguardd
6343 libarchive1
6344 libcln6
6345 libeet1
6346 libeina-svn-06
6347 libggadget-1.0-0b
6348 libggadget-qt-1.0-0b
6349 libgps19
6350 libkdecorations4
6351 libkephal4
6352 libkonq4
6353 libkonqsidebarplugin4a
6354 libkscreensaver5
6355 libksgrd4
6356 libksignalplotter4
6357 libkunitconversion4
6358 libkwineffects1a
6359 libmarblewidget4
6360 libntrack-qt4-1
6361 libntrack0
6362 libplasma-geolocation-interface4
6363 libplasmaclock4a
6364 libplasmagenericshell4
6365 libprocesscore4a
6366 libprocessui4a
6367 libqalculate5
6368 libqedje0a
6369 libqtruby4shared2
6370 libqzion0a
6371 libruby1.8
6372 libscim8c2a
6373 libsmokekdecore4-3
6374 libsmokekdeui4-3
6375 libsmokekfile3
6376 libsmokekhtml3
6377 libsmokekio3
6378 libsmokeknewstuff2-3
6379 libsmokeknewstuff3-3
6380 libsmokekparts3
6381 libsmokektexteditor3
6382 libsmokekutils3
6383 libsmokenepomuk3
6384 libsmokephonon3
6385 libsmokeplasma3
6386 libsmokeqtcore4-3
6387 libsmokeqtdbus4-3
6388 libsmokeqtgui4-3
6389 libsmokeqtnetwork4-3
6390 libsmokeqtopengl4-3
6391 libsmokeqtscript4-3
6392 libsmokeqtsql4-3
6393 libsmokeqtsvg4-3
6394 libsmokeqttest4-3
6395 libsmokeqtuitools4-3
6396 libsmokeqtwebkit4-3
6397 libsmokeqtxml4-3
6398 libsmokesolid3
6399 libsmokesoprano3
6400 libtaskmanager4a
6401 libtidy-0.99-0
6402 libweather-ion4a
6403 libxklavier16
6404 libxxf86misc1
6405 okteta
6406 oxygencursors
6407 plasma-dataengines-addons
6408 plasma-scriptengine-superkaramba
6409 plasma-widget-lancelot
6410 plasma-widgets-addons
6411 plasma-widgets-workspace
6412 polkit-kde-1
6413 ruby1.8
6414 systemsettings
6415 update-notifier-common
6416 &lt;/p&gt;&lt;/blockquote&gt;
6417
6418 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6419 aptitude a bit more similar, but there are still quite a lott of
6420 differences. I have no idea what packages should be installed after
6421 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6422 </description>
6423 </item>
6424
6425 <item>
6426 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6427 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6428 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6429 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6430 <description>&lt;p&gt;Most of the computers in use by the
6431 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6432 are virtual machines. And they have been Xen machines running on a
6433 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6434 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6435 bit harder that it could have been, because we set up the Xen virtual
6436 machines to get the virtual partitions from LVM, which as far as I
6437 know is not supported by KVM. So to migrate, we had to convert
6438 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6439
6440 &lt;p&gt;I found
6441 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6442 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6443 migration. It uses qemu-img from the qemu package to make the disk
6444 image, parted to partition it, losetup and kpartx to present the disk
6445 image partions as devices, and dd to copy the data. I NFS mounted the
6446 new servers storage area on the old server to do the migration.&lt;/p&gt;
6447
6448 &lt;pre&gt;
6449 #!/bin/sh
6450
6451 # Based on
6452 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6453
6454 set -e
6455 set -x
6456
6457 if [ -z &quot;$1&quot; ] ; then
6458 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6459 exit 1
6460 else
6461 host=&quot;$1&quot;
6462 fi
6463
6464 if [ ! -e /dev/vg_data/$host-disk ] ; then
6465 echo &quot;error: unable to find LVM volume for $host&quot;
6466 exit 1
6467 fi
6468
6469 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6470 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6471 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6472 totalsize=$(( ( $disksize + $swapsize ) ))
6473
6474 img=$host.img
6475 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6476 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6477
6478 parted $img mklabel msdos
6479 parted $img mkpart primary linux-swap 0 $disksize
6480 parted $img mkpart primary ext2 $disksize $totalsize
6481 parted $img set 1 boot on
6482
6483 modprobe dm-mod
6484 losetup /dev/loop0 $img
6485 kpartx -a /dev/loop0
6486
6487 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6488 fsck.ext3 -f /dev/mapper/loop0p1 || true
6489 mkswap /dev/mapper/loop0p2
6490
6491 kpartx -d /dev/loop0
6492 losetup -d /dev/loop0
6493 &lt;/pre&gt;
6494
6495 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6496 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6497
6498 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6499 the new disk image attached, installed grub-pc and linux-image-686 and
6500 set up grub to boot from the disk image. After this, the KVM machines
6501 seem to work just fine.&lt;/p&gt;
6502 </description>
6503 </item>
6504
6505 <item>
6506 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6507 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6508 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6509 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6510 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6511 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6512 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6513 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6514
6515 &lt;p&gt;I still do not know what a correct migration should look like, so I
6516 report any differences between apt and aptitude and hope someone else
6517 can see if anything should be changed.&lt;/p&gt;
6518
6519 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6520
6521 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6522
6523 &lt;blockquote&gt;&lt;p&gt;
6524 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6525 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6526 dmz-cursor-theme empathy empathy-common finger
6527 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6528 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6529 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6530 gnome-cards-data gnome-codec-install gnome-core
6531 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6532 gnome-search-tool gnome-session-canberra gnome-spell
6533 gnome-system-log gnome-themes-extras gnome-themes-more
6534 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6535 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6536 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6537 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6538 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6539 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6540 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6541 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6542 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6543 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6544 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6545 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6546 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6547 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6548 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6549 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6550 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6551 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6552 libmono-security2.0-cil libmono-sharpzip2.84-cil
6553 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6554 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6555 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6556 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6557 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6558 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6559 libxalan2-java libxerces2-java media-player-info mesa-utils
6560 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6561 nautilus-sendto-empathy openoffice.org-writer2latex
6562 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6563 python-aptdaemon python-aptdaemon-gtk python-axiom
6564 python-beautifulsoup python-bugbuddy python-clientform
6565 python-coherence python-configobj python-crypto python-cupshelpers
6566 python-cupsutils python-eggtrayicon python-elementtree
6567 python-epsilon python-evolution python-feedparser python-gdata
6568 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6569 python-gtksourceview2 python-httplib2 python-louie python-mako
6570 python-markupsafe python-mechanize python-nevow python-notify
6571 python-opengl python-openssl python-pam python-pkg-resources
6572 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6573 python-tagpy python-twisted-bin python-twisted-conch
6574 python-twisted-core python-twisted-web python-utidylib python-webkit
6575 python-xdg python-zope.interface remmina remmina-plugin-data
6576 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6577 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6578 software-center svgalibg1 system-config-printer-udev
6579 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6580 totem totem-coherence totem-mozilla totem-plugins
6581 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6582 zip
6583 &lt;/p&gt;&lt;/blockquote&gt;
6584
6585 Installed using apt-get, removed with aptitude
6586
6587 &lt;blockquote&gt;&lt;p&gt;
6588 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6589 epiphany-extensions epiphany-gecko evolution-exchange
6590 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6591 gedit-common gnome-app-install gnome-games gnome-games-data
6592 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6593 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6594 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6595 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6596 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6597 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6598 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6599 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6600 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6601 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6602 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6603 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6604 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6605 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6606 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6607 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6608 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6609 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6610 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6611 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6612 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6613 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6614 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6615 sound-juicer swfdec-gnome system-config-printer totem-common
6616 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6617 &lt;/p&gt;&lt;/blockquote&gt;
6618
6619 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6620
6621 &lt;blockquote&gt;&lt;p&gt;
6622 gstreamer0.10-gnomevfs
6623 &lt;/p&gt;&lt;/blockquote&gt;
6624
6625 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6626
6627 &lt;blockquote&gt;&lt;p&gt;
6628 [nothing]
6629 &lt;/p&gt;&lt;/blockquote&gt;
6630
6631 &lt;p&gt;This is for KDE:&lt;/p&gt;
6632
6633 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6634
6635 &lt;blockquote&gt;&lt;p&gt;
6636 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6637 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6638 ghostscript-x git gnome-audio gnugo granatier gs-common
6639 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6640 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6641 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6642 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6643 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6644 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6645 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6646 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6647 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6648 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6649 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6650 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6651 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6652 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6653 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6654 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6655 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6656 libkrossui4 libmailtools-perl libmime-tools-perl
6657 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6658 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6659 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6660 lirc luatex marble networkstatus noatun-plugins
6661 openoffice.org-writer2latex palapeli palapeli-data parley
6662 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6663 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6664 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6665 ttf-sazanami-gothic
6666 &lt;/p&gt;&lt;/blockquote&gt;
6667
6668 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6669
6670 &lt;blockquote&gt;&lt;p&gt;
6671 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6672 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6673 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6674 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6675 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6676 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6677 kitchensync kiten kjumpingcube klatin klettres klickety klines
6678 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6679 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6680 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6681 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6682 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6683 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6684 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6685 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6686 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6687 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6688 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6689 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6690 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6691 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6692 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6693 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6694 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6695 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6696 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6697 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6698 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6699 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6700 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6701 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6702 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6703 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6704 &lt;/p&gt;&lt;/blockquote&gt;
6705
6706 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6707
6708 &lt;blockquote&gt;&lt;p&gt;
6709 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6710 kdeartwork kdebase kdebase-apps kdebase-workspace
6711 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6712 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6713 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6714 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6715 xscreensaver-screensaver-bsod
6716 &lt;/p&gt;&lt;/blockquote&gt;
6717
6718 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6719
6720 &lt;blockquote&gt;&lt;p&gt;
6721 kdebase-bin konq-plugins konqueror
6722 &lt;/p&gt;&lt;/blockquote&gt;
6723 </description>
6724 </item>
6725
6726 <item>
6727 <title>Gnash buildbot slave and Debian kfreebsd</title>
6728 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6730 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6731 <description>&lt;p&gt;Answering
6732 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6733 call from the Gnash project&lt;/a&gt; for
6734 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6735 current source, I have set up a virtual KVM machine on the Debian
6736 Edu/Skolelinux virtualization host to test the git source on
6737 Debian/Squeeze. I hope this can help the developers in getting new
6738 releases out more often.&lt;/p&gt;
6739
6740 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6741 I have considered setting up a &lt;a
6742 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6743 machine as well. I have also considered using the kfreebsd
6744 architecture in Debian as a file server in NUUG to get access to the 5
6745 TB zfs volume we currently use to store DV video. Because of this, I
6746 finally got around to do a test installation of Debian/Squeeze with
6747 kfreebsd. Installation went fairly smooth, thought I noticed some
6748 visual glitches in the cdebconf dialogs (black cursor left on the
6749 screen at random locations). Have not gotten very far with the
6750 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6751 fatal problem. Have to spend some more time on it to see if it is
6752 useful as a file server for NUUG. Will try to find time to set up a
6753 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6754 </description>
6755 </item>
6756
6757 <item>
6758 <title>Debian in 3D</title>
6759 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6760 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6761 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6762 <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;
6763
6764 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6765 3D linked in from
6766 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6767 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6768 </description>
6769 </item>
6770
6771 <item>
6772 <title>Software updates 2010-10-24</title>
6773 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6774 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6775 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6776 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6777
6778 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6779 raise money for the project is going well. The lower limit of 10
6780 signers was reached in 24 hours, and so far 13 people have signed it.
6781 More signers and more funding is most welcome, and I am really curious
6782 how far we can get before the time limit of December 24 is reached.
6783 :)&lt;/p&gt;
6784
6785 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6786 about what appear to be a great code coverage tool capable of
6787 generating code coverage stats without any changes to the source code.
6788 It is called
6789 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6790 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6791 It is missing in Debian, but the git source built just fine in Squeeze
6792 after I installed libelf-dev, libdwarf-dev, pkg-config and
6793 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6794 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6795
6796 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6797 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6798 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6799 alpha test release of the Squeeze based Debian Edu /
6800 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6801 release. Give it a try if you need a complete linux solution for your
6802 school, including central infrastructure server, workstations, thin
6803 client servers and diskless workstations. A nice touch added
6804 yesterday is RDP support on the thin client servers, for windows
6805 clients to get a Linux desktop on request.&lt;/p&gt;
6806 </description>
6807 </item>
6808
6809 <item>
6810 <title>Some notes on Flash in Debian and Debian Edu</title>
6811 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6812 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6813 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6814 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6815 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6816 second most popular used package that is missing in Debian. The sixth
6817 most popular is flashplayer-mozilla. This is a clear indication that
6818 working flash is important for Debian users. Around 10 percent of the
6819 users submitting data to popcon.debian.org have this package
6820 installed.&lt;/p&gt;
6821
6822 &lt;p&gt;In the report written by Lars Risan in August 2008
6823&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
6824 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6825 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6826 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6827 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6828 web sites require Flash to work, and lacking working Flash support in
6829 the web browser and the problems with installing it was perceived as a
6830 good reason to stay with Windows.&lt;/p&gt;
6831
6832 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6833 said to be the retarded cousin that did not really understand
6834 everything you told him but could work fairly well. This was a
6835 comment regarding the problems Linux have with proprietary formats and
6836 non-standard web pages, and is sad because it exposes a fairly common
6837 understanding of whose fault it is if web pages that only work in for
6838 example Internet Explorer 6 fail to work on Firefox, and funny because
6839 it explain very well how annoying it is for users when Linux
6840 distributions do not work with the documents they receive or the web
6841 pages they want to visit.&lt;/p&gt;
6842
6843 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6844 and Debian Edu to have a well working Flash implementation in the
6845 distribution, to get at least popular sites as Youtube and Google
6846 Video to working out of the box. For Squeeze, Debian have the chance
6847 to include the latest version of Gnash that will make this happen, as
6848 the new release 0.8.8 was published a few weeks ago and is resting in
6849 unstable. The new version work with more sites that version 0.8.7.
6850 The Gnash maintainers have asked for a freeze exception, but the
6851 release team have not had time to reply to it yet. I hope they agree
6852 with me that Flash is important for the Debian desktop users, and thus
6853 accept the new package into Squeeze.&lt;/p&gt;
6854 </description>
6855 </item>
6856
6857 <item>
6858 <title>Circular package dependencies harms apt recovery</title>
6859 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6860 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6861 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6862 <description>&lt;p&gt;I discovered this while doing
6863 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6864 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6865 in Debian still got circular dependencies, and it is often claimed
6866 that apt and aptitude should be able to handle this just fine, but
6867 some times these dependency loops causes apt to fail.&lt;/p&gt;
6868
6869 &lt;p&gt;An example is from todays
6870 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6871 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6872 causes perl-modules to fail to upgrade. The cause is simple. If a
6873 package fail to unpack, then only part of packages with the circular
6874 dependency might end up being unpacked when unpacking aborts, and the
6875 ones already unpacked will fail to configure in the recovery phase
6876 because its dependencies are unavailable.&lt;/p&gt;
6877
6878 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6879
6880 &lt;blockquote&gt;&lt;pre&gt;
6881 dpkg: dependency problems prevent configuration of perl-modules:
6882 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6883 Version of perl on system is 5.10.0-19lenny2.
6884 dpkg: error processing perl-modules (--configure):
6885 dependency problems - leaving unconfigured
6886 &lt;/pre&gt;&lt;/blockquote&gt;
6887
6888 &lt;p&gt;The perl/perl-modules circular dependency is already
6889 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6890 hopefully be solved as soon as possible, but it is not the only one,
6891 and each one of these loops in the dependency tree can cause similar
6892 failures. Of course, they only occur when there are bugs in other
6893 packages causing the unpacking to fail, but it is rather nasty when
6894 the failure of one package causes the problem to become worse because
6895 of dependency loops.&lt;/p&gt;
6896
6897 &lt;p&gt;Thanks to
6898 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6899 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6900 dependencies
6901 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6902 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6903
6904 &lt;p&gt;Todays testing also exposed a bug in
6905 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6906 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6907 apt-get and aptitude, the latter possibly caused by some circular
6908 dependency. Reported both to BTS to try to get someone to look at
6909 it.&lt;/p&gt;
6910 </description>
6911 </item>
6912
6913 <item>
6914 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6915 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6916 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6917 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6918 <description>&lt;p&gt;This is a
6919 &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;
6920 on my
6921 &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
6922 work&lt;/a&gt; on
6923 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6924 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6925
6926 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6927 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6928 and dhcp3-server-ldap in Debian use the LDAP server. The two
6929 implementations are quite different in how they use LDAP.&lt;/p&gt;
6930
6931 To get this information, I started slapd with debugging enabled and
6932 dumped the debug output to a file to get the LDAP searches performed
6933 on a Debian Edu main-server. Here is a summary.
6934
6935 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6936
6937 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6938 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6939 the web.
6940
6941 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6942 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6943 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6944 reverse entries are in two different subtrees in LDAP with a structure
6945 based on the DNS names, as in tjener.intern and
6946 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6947
6948 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6949 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6950 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6951 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6952 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6953 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6954 forward entries, it is looking for attributes named dnsttl, arecord,
6955 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6956 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6957 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6958 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6959 spfrecord and modifytimestamp. For reverse entries it is looking for
6960 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6961 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6962 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6963 ldapsearch commands could look like this:&lt;/p&gt;
6964
6965 &lt;blockquote&gt;&lt;pre&gt;
6966 ldapsearch -h ldap \
6967 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6968 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6969 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6970 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6971 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6972 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6973
6974 ldapsearch -h ldap \
6975 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6976 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6977 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6978 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6979 srvrecord naptrrecord modifytimestamp
6980 &lt;/pre&gt;&lt;/blockquote&gt;
6981
6982 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6983 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6984 example LDAP objects used there. In addition to these objects, the
6985 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6986 also exist.&lt;/p&gt;
6987
6988 &lt;blockquote&gt;&lt;pre&gt;
6989 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6990 objectclass: top
6991 objectclass: dnsdomain
6992 objectclass: domainrelatedobject
6993 dc: tjener
6994 arecord: 10.0.2.2
6995 associateddomain: tjener.intern
6996
6997 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6998 objectclass: top
6999 objectclass: dnsdomain2
7000 objectclass: domainrelatedobject
7001 dc: 2
7002 ptrrecord: tjener.intern
7003 associateddomain: 2.2.0.10.in-addr.arpa
7004 &lt;/pre&gt;&lt;/blockquote&gt;
7005
7006 &lt;p&gt;In strict mode, the server behaves differently. When looking for
7007 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
7008 same base as in the tree mode for a object with filter
7009 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
7010 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7011 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7012 naptrrecord and modifytimestamp. For reverse entires it also do a
7013 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
7014 and the requested attributes are associateddomain, dnsttl and
7015 modifytimestamp. In short, in strict mode the objects with ptrrecord
7016 go away, and the arecord attribute in the forward object is used
7017 instead.&lt;/p&gt;
7018
7019 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
7020 like this:&lt;/p&gt;
7021
7022 &lt;blockquote&gt;&lt;pre&gt;
7023 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7024 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
7025 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7026 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7027 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7028 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7029
7030 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7031 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
7032 &lt;/pre&gt;&lt;/blockquote&gt;
7033
7034 &lt;p&gt;In addition to the forward and reverse searches , there is also a
7035 search for SOA records, which behave similar to the forward and
7036 reverse lookups.&lt;/p&gt;
7037
7038 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
7039 specify any objectclass names, and instead look for the attributes it
7040 need to generate a DNS reply. This make it able to work with any
7041 objectclass that provide the needed attributes.&lt;/p&gt;
7042
7043 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
7044 dnsdomain2 schemas. The latter is used for reverse entries like
7045 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
7046
7047 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
7048 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7049 attributes) and domainrelatedobject (for associatedDomain). The use
7050 of structural object classes make it impossible to combine these
7051 classes with the object classes used by DHCP.&lt;/p&gt;
7052
7053 &lt;p&gt;There are other schemas that could be used too, for example the
7054 dnszone structural object class used by Gosa and bind-sdb for the DNS
7055 attributes combined with the domainrelatedobject object class, but in
7056 this case some unused attributes would have to be included as well
7057 (zonename and relativedomainname).&lt;/p&gt;
7058
7059 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
7060 mode and not use any of the existing objectclasses (dnsdomain,
7061 dnsdomain2 and dnszone) when one want to combine the DNS information
7062 with DHCP information, and instead create a auxiliary object class
7063 defined something like this (using the attributes defined for
7064 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
7065
7066 &lt;blockquote&gt;&lt;pre&gt;
7067 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
7068 SUP top
7069 AUXILIARY
7070 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7071 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7072 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7073 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7074 A6Record $ DNAMERecord
7075 ))
7076 &lt;/pre&gt;&lt;/blockquote&gt;
7077
7078 &lt;p&gt;This will allow any object to become a DNS entry when combined with
7079 the domainrelatedobject object class, and allow any entity to include
7080 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
7081 developers asking for their view on this schema and if they are
7082 interested in providing such schema with PowerDNS, and I hope my
7083 message will be accepted into their mailing list soon.&lt;/p&gt;
7084
7085 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
7086
7087 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
7088 the object attributes, and then uses the attributes it want. This
7089 make it harder to figure out exactly what attributes are used, but
7090 thanks to the working example in Debian Edu I can at least get an idea
7091 what is needed without having to read the source code.&lt;/p&gt;
7092
7093 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
7094 search filter to use to locate the correct dhcpServer entity is
7095 stored. These are the relevant entries from
7096 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
7097
7098 &lt;blockquote&gt;&lt;pre&gt;
7099 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
7100 ldap-dhcp-server-cn &quot;dhcp&quot;;
7101 &lt;/pre&gt;&lt;/blockquote&gt;
7102
7103 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
7104 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
7105 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
7106 search result is this entry:&lt;/p&gt;
7107
7108 &lt;blockquote&gt;&lt;pre&gt;
7109 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7110 cn: dhcp
7111 objectClass: top
7112 objectClass: dhcpServer
7113 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7114 &lt;/pre&gt;&lt;/blockquote&gt;
7115
7116 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
7117 subtree with DHCP configuration. The DHCP configuration subtree base
7118 is located using a base scope search with base &quot;cn=DHCP
7119 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
7120 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
7121 The search result is this entry:&lt;/p&gt;
7122
7123 &lt;blockquote&gt;&lt;pre&gt;
7124 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7125 cn: DHCP Config
7126 objectClass: top
7127 objectClass: dhcpService
7128 objectClass: dhcpOptions
7129 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7130 dhcpStatements: ddns-update-style none
7131 dhcpStatements: authoritative
7132 dhcpOption: smtp-server code 69 = array of ip-address
7133 dhcpOption: www-server code 72 = array of ip-address
7134 dhcpOption: wpad-url code 252 = text
7135 &lt;/pre&gt;&lt;/blockquote&gt;
7136
7137 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
7138 all the DHCP configuration is loaded, it is ready to receive requests.
7139 The subtree in Debian Edu contain objects with object classes
7140 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7141 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7142 and information about netmasks, dynamic range etc. Leaving out the
7143 details here because it is not relevant for the focus of my
7144 investigation, which is to see if it is possible to merge dns and dhcp
7145 related computer objects.&lt;/p&gt;
7146
7147 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
7148 of the client (00:00:00:00:00:00 in this example), using a subtree
7149 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
7150 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7151 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
7152 like:&lt;/p&gt;
7153
7154 &lt;blockquote&gt;&lt;pre&gt;
7155 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7156 cn: hostname
7157 objectClass: top
7158 objectClass: dhcpHost
7159 dhcpHWAddress: ethernet 00:00:00:00:00:00
7160 dhcpStatements: fixed-address hostname
7161 &lt;/pre&gt;&lt;/blockquote&gt;
7162
7163 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
7164 The object classes need to have fixed names, and the configuration
7165 need to be stored in a fairly specific LDAP structure. On the
7166 positive side, the invidiual dhcpHost entires can be anywhere without
7167 the DN pointed to by the dhcpServer entries. The latter should make
7168 it possible to group all host entries in a subtree next to the
7169 configuration entries, and this subtree can also be shared with the
7170 DNS server if the schema proposed above is combined with the dhcpHost
7171 structural object class.
7172
7173 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
7174
7175 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
7176 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
7177 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
7178 allowing DNS objects to be stored anywhere under the base cn specified
7179 in the configuration.&lt;/p&gt;
7180
7181 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
7182 regarding which LDAP schemas to use and which LDAP structure to use.
7183 I guess one could implement ones own schema, as long as the
7184 objectclasses and attributes have the names used, but this do not
7185 really help when the DHCP subtree need to have a fairly fixed
7186 structure.&lt;/p&gt;
7187
7188 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
7189 this might work for Debian Edu:&lt;/p&gt;
7190
7191 &lt;blockquote&gt;&lt;pre&gt;
7192 ou=services
7193 cn=machine-info (dhcpService) - dhcpServiceDN points here
7194 cn=dhcp (dhcpServer)
7195 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7196 cn=10.0.2.0 (dhcpSubnet)
7197 cn=group1 (dhcpGroup/dhcpOptions)
7198 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7199 cn=192.168.0.0 (dhcpSubnet)
7200 cn=group1 (dhcpGroup/dhcpOptions)
7201 ou=machines - PowerDNS base points here
7202 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7203 &lt;/pre&gt;&lt;/blockquote&gt;
7204
7205 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
7206 entries to be in the dhcpGroup subtrees, the entries can be stored
7207 there instead of a common machines subtree, and the PowerDNS base
7208 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
7209
7210 &lt;p&gt;The combined object under the machines subtree would look something
7211 like this:&lt;/p&gt;
7212
7213 &lt;blockquote&gt;&lt;pre&gt;
7214 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7215 dc: hostname
7216 objectClass: top
7217 objectClass: dhcpHost
7218 objectclass: domainrelatedobject
7219 objectclass: dnsDomainAux
7220 associateddomain: hostname.intern
7221 arecord: 10.11.12.13
7222 dhcpHWAddress: ethernet 00:00:00:00:00:00
7223 dhcpStatements: fixed-address hostname.intern
7224 &lt;/pre&gt;&lt;/blockquote&gt;
7225
7226 &lt;/p&gt;One could even add the LTSP configuration associated with a given
7227 machine, as long as the required attributes are available in a
7228 auxiliary object class.&lt;/p&gt;
7229 </description>
7230 </item>
7231
7232 <item>
7233 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
7234 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
7235 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
7236 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
7237 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
7238 DHCP services in Debian Edu to use the same LDAP objects for a given
7239 computer, to avoid the possibility of having a inconsistent state for
7240 a computer in LDAP (as in DHCP but no DNS entry or the other way
7241 around) and make it easier to add computers to LDAP.&lt;/p&gt;
7242
7243 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
7244 information finally found a solution that seem to work.&lt;/p&gt;
7245
7246 &lt;p&gt;The old setup required three LDAP objects for a given computer.
7247 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7248 we switch powerdns to use its strict LDAP method (ldap-method=strict
7249 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7250 merged into one while making it impossible to transfer the reverse map
7251 to a slave DNS server.&lt;/p&gt;
7252
7253 &lt;p&gt;If we also replace the object class used to get the DNS related
7254 attributes to one allowing these attributes to be combined with the
7255 dhcphost object class, we can merge the DNS and DHCP entries into one.
7256 I&#39;ve written such object class in the dnsdomainaux.schema file (need
7257 proper OIDs, but that is a minor issue), and tested the setup. It
7258 seem to work.&lt;/p&gt;
7259
7260 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
7261 for both DNS and DHCP, and even the LTSP configuration I suggested in
7262 an earlier email. The combined LDAP object will look something like
7263 this:&lt;/p&gt;
7264
7265 &lt;blockquote&gt;&lt;pre&gt;
7266 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7267 cn: hostname
7268 objectClass: dhcphost
7269 objectclass: domainrelatedobject
7270 objectclass: dnsdomainaux
7271 associateddomain: hostname.intern
7272 arecord: 10.11.12.13
7273 dhcphwaddress: ethernet 00:00:00:00:00:00
7274 dhcpstatements: fixed-address hostname
7275 ldapconfigsound: Y
7276 &lt;/pre&gt;&lt;/blockquote&gt;
7277
7278 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
7279 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7280 before asking DNS to resolve the fixed-adddress. LTSP will use
7281 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
7282
7283 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
7284 dhcphost in a different location, to allow us to put the objects
7285 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7286 that. If I can&#39;t figure out a way to do that, we can still get rid of
7287 the hosts subtree and move all its content into the DHCP Config tree
7288 (which probably should be renamed to be more related to the new
7289 content. I suspect cn=dnsdhcp,ou=services or something like that
7290 might be a good place to put it.&lt;/p&gt;
7291
7292 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7293 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7294 </description>
7295 </item>
7296
7297 <item>
7298 <title>Idea for storing LTSP configuration in LDAP</title>
7299 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7300 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7301 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7302 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7303 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7304 clients, and that this can be used to fetch configuration from LDAP if
7305 Debian Edu choose to store configuration there.&lt;/p&gt;
7306
7307 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7308 to get configuration from LDAP. The idea is to look up the MAC
7309 address of the client in LDAP, and look for attributes on the form
7310 ltspconfigsetting=value, and use this to export SETTING=value to the
7311 LTSP clients.&lt;/p&gt;
7312
7313 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7314 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7315 allowing us to store all information about a computer in one place.&lt;/p&gt;
7316
7317 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7318 this approach. A real LDAP schema for the ltspClientAux objectclass
7319 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7320
7321 &lt;blockquote&gt;&lt;pre&gt;
7322 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7323 #
7324 # Fetch LTSP client settings from LDAP based on MAC address
7325 #
7326 # Uses ethernet address as stored in the dhcpHost objectclass using
7327 # the dhcpHWAddress attribute or ethernet address stored in the
7328 # ieee802Device objectclass with the macAddress attribute.
7329 #
7330 # This module is written to be schema agnostic, and only depend on the
7331 # existence of attribute names.
7332 #
7333 # The LTSP configuration variables are saved directly using a
7334 # ltspConfig prefix and uppercasing the rest of the attribute name.
7335 # To set the SERVER variable, set the ltspConfigServer attribute.
7336 #
7337 # Some LDAP schema should be created with all the relevant
7338 # configuration settings. Something like this should work:
7339 #
7340 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7341 # SUP top
7342 # AUXILIARY
7343 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7344
7345 LDAPSERVER=$(debian-edu-ldapserver)
7346 if [ &quot;$LDAPSERVER&quot; ] ; then
7347 LDAPBASE=$(debian-edu-ldapserver -b)
7348 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7349 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7350 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7351 grep &#39;^ltspConfig&#39; | while read attr value ; do
7352 # Remove prefix and convert to upper case
7353 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7354 # bass value on to clients
7355 eval &quot;$attr=$value; export $attr&quot;
7356 done
7357 done
7358 fi
7359 &lt;/pre&gt;&lt;/blockquote&gt;
7360
7361 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7362 the while block might end up in a subshell causing the variables set
7363 there to not show up in ltsp-config, but if that is the case I am sure
7364 the code can be restructured to make sure the variables are passed on.
7365 I expect that can be solved with some testing. :)&lt;/p&gt;
7366
7367 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7368 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7369
7370 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7371 configuration in LDAP that was created around year 2000 by
7372 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7373 Xperience, Inc., 2000&lt;/a&gt;. I found its
7374 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7375 personal home page over at redhat.com.&lt;/p&gt;
7376 </description>
7377 </item>
7378
7379 <item>
7380 <title>jXplorer, a very nice LDAP GUI</title>
7381 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7382 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7383 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7384 <description>&lt;p&gt;Since
7385 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7386 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7387 LDAP GUI that is even better than luma. The java application
7388 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7389 moving LDAP objects and subtrees using drag-and-drop, and can
7390 authenticate using Kerberos. I have only tested the Kerberos
7391 authentication, but do not have a LDAP setup allowing me to rewrite
7392 LDAP with my test user yet. It is
7393 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7394 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7395 have with it is how it handle errors. If something go wrong, its
7396 non-intuitive behaviour require me to go through some query work list
7397 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7398 </description>
7399 </item>
7400
7401 <item>
7402 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7403 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7404 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7405 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7406 <description>&lt;p&gt;Here is a short update on my &lt;a
7407 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7408 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7409 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7410 not reporting the status for KDE, because the upgrade crashes when
7411 aptitude try because of missing conflicts
7412 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7413 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7414
7415 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7416 complete list of the installed packages. Based on this I see these
7417 differences when I did a test run today. As usual, I do not really
7418 know what the correct set of packages would be, but thought it best to
7419 publish the difference.&lt;/p&gt;
7420
7421 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7422
7423 &lt;blockquote&gt;&lt;p&gt;
7424 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7425 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7426 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7427 libgtksourceview-common libpt-1.10.10-plugins-alsa
7428 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7429 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7430 python-4suite-xml python-eggtrayicon python-gtkhtml2
7431 python-gtkmozembed svgalibg1 xserver-xephyr zip
7432 &lt;/p&gt;&lt;/blockquote&gt;
7433
7434 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7435
7436 &lt;blockquote&gt;&lt;p&gt;
7437 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7438 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7439 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7440 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7441 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7442 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7443 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7444 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7445 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7446 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7447 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7448 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7449 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7450 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7451 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7452 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7453 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7454 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7455 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7456 mysql-common swfdec-gnome totem-gstreamer wodim
7457 &lt;/p&gt;&lt;/blockquote&gt;
7458
7459 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7460
7461 &lt;blockquote&gt;&lt;p&gt;
7462 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7463 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7464 xserver-xorg-input-all xserver-xorg-input-evdev
7465 xserver-xorg-input-kbd xserver-xorg-input-mouse
7466 xserver-xorg-input-synaptics xserver-xorg-video-all
7467 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7468 xserver-xorg-video-chips xserver-xorg-video-cirrus
7469 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7470 xserver-xorg-video-glint xserver-xorg-video-i128
7471 xserver-xorg-video-i740 xserver-xorg-video-mach64
7472 xserver-xorg-video-mga xserver-xorg-video-neomagic
7473 xserver-xorg-video-nouveau xserver-xorg-video-nv
7474 xserver-xorg-video-r128 xserver-xorg-video-radeon
7475 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7476 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7477 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7478 xserver-xorg-video-sis xserver-xorg-video-sisusb
7479 xserver-xorg-video-tdfx xserver-xorg-video-tga
7480 xserver-xorg-video-trident xserver-xorg-video-tseng
7481 xserver-xorg-video-vesa xserver-xorg-video-vmware
7482 xserver-xorg-video-voodoo
7483 &lt;/p&gt;&lt;/blockquote&gt;
7484
7485 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7486
7487 &lt;blockquote&gt;&lt;p&gt;
7488 deskbar-applet xserver-xorg xserver-xorg-core
7489 xserver-xorg-input-wacom xserver-xorg-video-intel
7490 xserver-xorg-video-openchrome
7491 &lt;/p&gt;&lt;/blockquote&gt;
7492
7493 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7494 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7495 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7496 No idea when it hits Squeeze, but when it does I hope it will reduce
7497 the difference somewhat.
7498 </description>
7499 </item>
7500
7501 <item>
7502 <title>LUMA, a very nice LDAP GUI</title>
7503 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7504 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7505 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7506 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7507 directory in Debian Edu, and in the process I started to miss a GUI
7508 tool to browse the LDAP tree. The only one I was able to find in
7509 Debian/Squeeze and Lenny is
7510 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7511 be a great tool to get a overview of the current LDAP directory
7512 populated by default in Skolelinux. Thanks to it, I have been able to
7513 find empty and obsolete subtrees, misplaced objects and duplicate
7514 objects. It will be installed by default in Debian/Squeeze. If you
7515 are working with LDAP, give it a go. :)&lt;/p&gt;
7516
7517 &lt;p&gt;I did notice one problem with it I have not had time to report to
7518 the BTS yet. There is no .desktop file in the package, so the tool do
7519 not show up in the Gnome and KDE menus, but only deep down in in the
7520 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7521 released.&lt;/p&gt;
7522
7523 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7524 like to move objects and remove subtrees directly in the GUI, but have
7525 not found a way to do that with LUMA yet. So in the mean time, I use
7526 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7527
7528 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7529 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7530
7531 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7532 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7533 useful GUI alternative. It seem like a good tool, but is unmaintained
7534 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7535 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7536 </description>
7537 </item>
7538
7539 <item>
7540 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7541 <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>
7542 <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>
7543 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7544 <description>&lt;p&gt;A while back, I
7545 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7546 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7547 for storing DNS and DHCP information in LDAP to combine the two sets
7548 of information into one LDAP object representing a computer.&lt;/p&gt;
7549
7550 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7551 the dhcpHost object class auxiliary, to allow it to be combined with
7552 the dNSDomain object class, and thus forming one object for one
7553 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7554
7555 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7556 without also changing the assigned number for the object class, and I
7557 do not know enough about LDAP schema design to do that properly for
7558 Debian Edu.&lt;/p&gt;
7559
7560 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7561 the
7562 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7563 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7564 available today from IETF.&lt;/p&gt;
7565
7566 &lt;pre&gt;
7567 --- dhcp.schema (revision 65192)
7568 +++ dhcp.schema (working copy)
7569 @@ -376,7 +376,7 @@
7570 objectclass ( 2.16.840.1.113719.1.203.6.6
7571 NAME &#39;dhcpHost&#39;
7572 DESC &#39;This represents information about a particular client&#39;
7573 - SUP top
7574 + SUP top AUXILIARY
7575 MUST cn
7576 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7577 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7578 &lt;/pre&gt;
7579
7580 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7581 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7582 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7583
7584 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7585 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7586 </description>
7587 </item>
7588
7589 <item>
7590 <title>Calling tasksel like the installer, while still getting useful output</title>
7591 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7592 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7593 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7594 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7595 installs packages during the normal debian-installer run. Until now,
7596 I have ended up letting tasksel do the work, with the annoying problem
7597 of not getting any feedback at all when something fails (like a
7598 conffile question from dpkg or a download that fails), using code like
7599 this:
7600
7601 &lt;blockquote&gt;&lt;pre&gt;
7602 export DEBIAN_FRONTEND=noninteractive
7603 tasksel --new-install
7604 &lt;/pre&gt;&lt;/blockquote&gt;
7605
7606 This would invoke tasksel, let its automatic task selection pick the
7607 tasks to install, and continue to install the requested tasks without
7608 any output what so ever.
7609
7610 Recently I revisited this problem while working on the automatic
7611 package upgrade testing, because tasksel would some times hang without
7612 any useful feedback, and I want to see what is going on when it
7613 happen. Then it occured to me, I can parse the output from tasksel
7614 when asked to run in test mode, and use that aptitude command line
7615 printed by tasksel then to simulate the tasksel run. I ended up using
7616 code like this:
7617
7618 &lt;blockquote&gt;&lt;pre&gt;
7619 export DEBIAN_FRONTEND=noninteractive
7620 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7621 $cmd
7622 &lt;/pre&gt;&lt;/blockquote&gt;
7623
7624 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7625 --without-recommends -o APT::Install-Recommends=no -y install
7626 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7627 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7628 laptop task and all packages with priority standard , required and
7629 important, just like tasksel would have done it during
7630 installation.&lt;/p&gt;
7631
7632 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7633 install packages without using debconf-apt-progress, for use cases
7634 like this.&lt;/p&gt;
7635 </description>
7636 </item>
7637
7638 <item>
7639 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7640 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7641 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7642 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7643 <description>&lt;p&gt;My
7644 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7645 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7646 finally made the upgrade logs available from
7647 &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;.
7648 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7649 apt and aptitude, and found their differences interesting. This time
7650 I will only focus on their removal plans.&lt;/p&gt;
7651
7652 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7653 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7654 surprising part is that it want to remove xorg and all
7655 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7656 sure why. When asking aptitude to do the same, it want to remove 129
7657 packages, but most of them are library packages I suspect are no
7658 longer needed. Both of them want to remove bluetooth packages, which
7659 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7660
7661 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7662 which seem like a bad idea and xorg the same way as with Gnome. Asking
7663 aptitude for the same, it wants to remove 192 packages, none which are
7664 too surprising.&lt;/p&gt;
7665
7666 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7667 and avoided, and perhaps others as well. Here are the complete list
7668 of planned removals. The complete logs is available from the URL
7669 above. Note if you want to repeat these tests, that the upgrade test
7670 for kde+apt-get hung in the tasksel setup because of dpkg asking
7671 conffile questions. No idea why. I worked around it by using
7672 &#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
7673 continue.&lt;/p&gt;
7674
7675 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7676 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7677 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7678 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7679 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7680 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7681 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7682 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7683 xserver-xorg-input-kbd xserver-xorg-input-mouse
7684 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7685 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7686 xserver-xorg-video-ati xserver-xorg-video-chips
7687 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7688 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7689 xserver-xorg-video-glint xserver-xorg-video-i128
7690 xserver-xorg-video-i740 xserver-xorg-video-imstt
7691 xserver-xorg-video-intel xserver-xorg-video-mach64
7692 xserver-xorg-video-mga xserver-xorg-video-neomagic
7693 xserver-xorg-video-nsc xserver-xorg-video-nv
7694 xserver-xorg-video-openchrome xserver-xorg-video-r128
7695 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7696 xserver-xorg-video-rendition xserver-xorg-video-s3
7697 xserver-xorg-video-s3virge xserver-xorg-video-savage
7698 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7699 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7700 xserver-xorg-video-tga xserver-xorg-video-trident
7701 xserver-xorg-video-tseng xserver-xorg-video-v4l
7702 xserver-xorg-video-vesa xserver-xorg-video-vga
7703 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7704 xulrunner-1.9-gnome-support&lt;/p&gt;
7705
7706 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7707
7708 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7709 djvulibre-desktop finger gnome-app-install gnome-mount
7710 gnome-network-admin gnome-spell gnome-vfs-obexftp
7711 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7712 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7713 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7714 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7715 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7716 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7717 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7718 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7719 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7720 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7721 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7722 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7723 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7724 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7725 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7726 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7727 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7728 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7729 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7730 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7731 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7732 openoffice.org-writer2latex openssl-blacklist p7zip
7733 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7734 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7735 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7736 swfdec-mozilla totem-gstreamer update-manager wodim
7737 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7738 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7739 zip&lt;/p&gt;
7740
7741 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7742
7743 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7744 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7745 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7746 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7747 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7748 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7749 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7750 xserver-xorg-input-kbd xserver-xorg-input-mouse
7751 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7752 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7753 xserver-xorg-video-ati xserver-xorg-video-chips
7754 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7755 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7756 xserver-xorg-video-glint xserver-xorg-video-i128
7757 xserver-xorg-video-i740 xserver-xorg-video-imstt
7758 xserver-xorg-video-intel xserver-xorg-video-mach64
7759 xserver-xorg-video-mga xserver-xorg-video-neomagic
7760 xserver-xorg-video-nsc xserver-xorg-video-nv
7761 xserver-xorg-video-openchrome xserver-xorg-video-r128
7762 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7763 xserver-xorg-video-rendition xserver-xorg-video-s3
7764 xserver-xorg-video-s3virge xserver-xorg-video-savage
7765 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7766 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7767 xserver-xorg-video-tga xserver-xorg-video-trident
7768 xserver-xorg-video-tseng xserver-xorg-video-v4l
7769 xserver-xorg-video-vesa xserver-xorg-video-vga
7770 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7771
7772 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7773 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7774 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7775 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7776 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7777 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7778 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7779 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7780 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7781 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7782 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7783 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7784 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7785 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7786 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7787 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7788 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7789 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7790 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7791 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7792 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7793 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7794 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7795 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7796 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7797 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7798 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7799 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7800 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7801 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7802 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7803 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7804 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7805 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7806 texlive-common texlive-doc-base texlive-fonts-recommended
7807 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7808 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7809 xulrunner-1.9&lt;/p&gt;
7810
7811 </description>
7812 </item>
7813
7814 <item>
7815 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7816 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7817 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7818 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7819 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7820 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7821 have been discovered and reported in the process
7822 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7823 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7824 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7825 kdebase-workspace-data), and to get a more regular testing going on, I
7826 am working on a script to automate the test.&lt;/p&gt;
7827
7828 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7829 Gnome or KDE desktop installation inside the chroot before upgrading
7830 it. To ensure no services are started in the chroot, a policy-rc.d
7831 script is inserted. To make sure tasksel believe it is to install a
7832 desktop on a laptop, the tasksel tests are replaced in the chroot
7833 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7834
7835 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7836 currently always fail because udev refuses to upgrade with the kernel
7837 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7838 is created. The bug report
7839 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7840 this problem do not trigger in a chroot, but I touch the file anyway
7841 to make sure the upgrade go well. Testing on virtual and real
7842 hardware have failed me because of udev so far, and creating this file
7843 do the trick in such settings anyway. This is a
7844 &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
7845 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7846 maintainer because he lack the resources to rewrite udev to keep
7847 working with old kernels or something like that. I really wish the
7848 udev upstream would keep udev backwards compatible, to avoid such
7849 upgrade problem, but given that they fail to do so, I guess
7850 documenting the way out of this mess is the best option we got for
7851 Debian Squeeze.&lt;/p&gt;
7852
7853 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7854 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7855 trick:&lt;/p&gt;
7856
7857 &lt;blockquote&gt;&lt;pre&gt;
7858 #!/bin/sh
7859 set -ex
7860
7861 if [ &quot;$1&quot; ] ; then
7862 desktop=$1
7863 else
7864 desktop=gnome
7865 fi
7866
7867 from=lenny
7868 to=squeeze
7869
7870 exec &amp;lt; /dev/null
7871 unset LANG
7872 mirror=http://ftp.skolelinux.org/debian
7873 tmpdir=chroot-$from-upgrade-$to-$desktop
7874 fuser -mv .
7875 debootstrap $from $tmpdir $mirror
7876 chroot $tmpdir aptitude update
7877 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7878 #!/bin/sh
7879 exit 101
7880 EOF
7881 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7882 exit_cleanup() {
7883 umount $tmpdir/proc
7884 }
7885 mount -t proc proc $tmpdir/proc
7886 # Make sure proc is unmounted also on failure
7887 trap exit_cleanup EXIT INT
7888
7889 chroot $tmpdir aptitude -y install debconf-utils
7890
7891 # Make sure tasksel autoselection trigger. It need the test scripts
7892 # to return the correct answers.
7893 echo tasksel tasksel/desktop multiselect $desktop | \
7894 chroot $tmpdir debconf-set-selections
7895
7896 # Include the desktop and laptop task
7897 for test in desktop laptop ; do
7898 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7899 #!/bin/sh
7900 exit 2
7901 EOF
7902 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7903 done
7904
7905 DEBIAN_FRONTEND=noninteractive
7906 DEBIAN_PRIORITY=critical
7907 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7908 chroot $tmpdir tasksel --new-install
7909
7910 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7911 chroot $tmpdir aptitude update
7912 touch $tmpdir/etc/udev/kernel-upgrade
7913 chroot $tmpdir aptitude -y dist-upgrade
7914 fuser -mv
7915 &lt;/pre&gt;&lt;/blockquote&gt;
7916
7917 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7918 with aptitude, but I have not had time to look at how they behave
7919 differently so far. I hope to get a cron job running to do the test
7920 regularly and post the result on the web. The Gnome upgrade currently
7921 work, while the KDE upgrade fail because of the bug in
7922 kdebase-workspace-data&lt;/p&gt;
7923
7924 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7925 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7926 post, so I will refrain from trying. I can report that for Gnome,
7927 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7928 remove and 1 not upgraded and 1024MB need to be downloaded while for
7929 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7930 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7931
7932 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7933 is able to migrate to dependency based boot sequencing and parallel
7934 booting without a hitch. Was unsure if there were still bugs with
7935 packages failing to clean up their obsolete init.d script during
7936 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7937 packages.&lt;/p&gt;
7938 </description>
7939 </item>
7940
7941 <item>
7942 <title>Upstart or sysvinit - as init.d scripts see it</title>
7943 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7944 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7945 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7946 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7947 scripts to migrate (some of) their operations to upstart job while
7948 keeping the init.d for hurd and kfreebsd. The packages with such
7949 needs will need a way to get their init.d scripts to behave
7950 differently when used with sysvinit and with upstart. Because of
7951 this, I had a look at the environment variables set when a init.d
7952 script is running under upstart, and when it is not.&lt;/p&gt;
7953
7954 &lt;p&gt;With upstart, I notice these environment variables are set when a
7955 script is started from rcS.d/ (ignoring some irrelevant ones like
7956 COLUMNS):&lt;/p&gt;
7957
7958 &lt;blockquote&gt;&lt;pre&gt;
7959 DEFAULT_RUNLEVEL=2
7960 previous=N
7961 PREVLEVEL=
7962 RUNLEVEL=
7963 runlevel=S
7964 UPSTART_EVENTS=startup
7965 UPSTART_INSTANCE=
7966 UPSTART_JOB=rc-sysinit
7967 &lt;/pre&gt;&lt;/blockquote&gt;
7968
7969 &lt;p&gt;With sysvinit, these environment variables are set for the same
7970 script.&lt;/p&gt;
7971
7972 &lt;blockquote&gt;&lt;pre&gt;
7973 INIT_VERSION=sysvinit-2.88
7974 previous=N
7975 PREVLEVEL=N
7976 RUNLEVEL=S
7977 runlevel=S
7978 &lt;/pre&gt;&lt;/blockquote&gt;
7979
7980 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7981 sysvinit are not set by upstart. Not sure if it is intentional or not
7982 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7983
7984 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7985 looking for the UPSTART_JOB environment variable seem to be a good
7986 choice.&lt;/p&gt;
7987 </description>
7988 </item>
7989
7990 <item>
7991 <title>A manual for standards wars...</title>
7992 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7993 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7994 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7995 <description>&lt;p&gt;Via the
7996 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7997 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7998 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7999 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
8000 following the standards wars of today.&lt;/p&gt;
8001 </description>
8002 </item>
8003
8004 <item>
8005 <title>Sitesummary tip: Listing computer hardware models used at site</title>
8006 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
8007 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
8008 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
8009 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
8010 to get a list of the machine types in use thanks to the DMI
8011 information extracted from each machine. The script to do so is
8012 included in the sitesummary package, and here is example output from
8013 the Skolelinux build servers:&lt;/p&gt;
8014
8015 &lt;blockquote&gt;&lt;pre&gt;
8016 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8017 vendor count
8018 Dell Computer Corporation 1
8019 PowerEdge 1750 1
8020 IBM 1
8021 eserver xSeries 345 -[8670M1X]- 1
8022 Intel 2
8023 [no-dmi-info] 3
8024 maintainer:~#
8025 &lt;/pre&gt;&lt;/blockquote&gt;
8026
8027 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
8028 provided in each machine. Here there are Intel machines without model
8029 information listed with Intel as vendor and no model, and virtual Xen
8030 machines listed as [no-dmi-info]. One can add -l as a command line
8031 option to list the individual machines.&lt;/p&gt;
8032
8033 &lt;p&gt;A larger list is
8034 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
8035 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
8036 provide the basic sitesummary report publicly. In their report there
8037 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
8038 their machines, and as sitesummary is available in both distributions,
8039 it is trivial to get all of them to report to the same central
8040 collector.&lt;/p&gt;
8041 </description>
8042 </item>
8043
8044 <item>
8045 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
8046 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
8047 <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>
8048 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
8049 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
8050 start at boot when an NVidia video card is used is handled. The
8051 problem seem to be that the nvidia X.org driver uses a long time to
8052 initialize, and this duration is longer than kdm is configured to
8053 wait.&lt;/p&gt;
8054
8055 &lt;p&gt;I came across two bugs related to this issue,
8056 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
8057 against initscripts and passed on to nvidia-glx when it became obvious
8058 that the nvidia drivers were involved, and
8059 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
8060 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
8061
8062 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
8063 problem nvidia video card owners experience and make sure the Debian
8064 distribution work out of the box for these users. The nvidia driver
8065 maintainers expect kdm to be set up to wait longer, while kdm expect
8066 the nvidia driver maintainers to fix the driver to start faster, and
8067 while they wait for each other I guess the users end up switching to a
8068 distribution that work for them. I have no idea what the solution is,
8069 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
8070
8071 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
8072 </description>
8073 </item>
8074
8075 <item>
8076 <title>Parallellized boot seem to hold up well in Debian/testing</title>
8077 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
8078 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
8079 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
8080 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
8081 The feature seem to hold up pretty well, but three fairly serious
8082 issues are known and should be solved:
8083
8084 &lt;p&gt;&lt;ul&gt;
8085
8086 &lt;li&gt;The wicd package seen to
8087 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
8088 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
8089 parallel booting is enabled. No idea why, but the wicd maintainer
8090 seem to be on the case.&lt;/li&gt;
8091
8092 &lt;li&gt;The nvidia X driver seem to
8093 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
8094 triggered more easily when parallel booting is in effect. The
8095 maintainer is on the case.&lt;/li&gt;
8096
8097 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
8098 sequencing (the shutdown is broken) when old file-rc users
8099 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
8100 sysv-rc. One way to solve it would be for file-rc to create
8101 /etc/init.d/.legacy-bootordering, and another is to try to make
8102 sysv-rc more robust. Will investigate some more and probably upload a
8103 workaround in sysv-rc to help those trying to move from file-rc to
8104 sysv-rc get a working shutdown.&lt;/li&gt;
8105
8106 &lt;/ul&gt;&lt;/p&gt;
8107
8108 &lt;p&gt;All in all not many surprising issues, and all of them seem
8109 solvable before Squeeze is released. In addition to these there are
8110 some packages with bugs in their dependencies and run level settings,
8111 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
8112
8113 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8114 the BTS, please usertag the report to get it to show up at
8115 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8116 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8117
8118 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
8119 </description>
8120 </item>
8121
8122 <item>
8123 <title>More flexible firmware handling in debian-installer</title>
8124 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
8125 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
8126 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
8127 <description>&lt;p&gt;After a long break from debian-installer development, I finally
8128 found time today to return to the project. Having to spend less time
8129 working dependency based boot in debian, as it is almost complete now,
8130 definitely helped freeing some time.&lt;/p&gt;
8131
8132 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
8133 include some firmware packages on the Debian Edu CDs, those needed to
8134 get disk and network controllers working. Without having these
8135 firmware packages available during installation, it is impossible to
8136 install Debian Edu on the given machine, and because our target group
8137 are non-technical people, asking them to provide firmware packages on
8138 an external medium is a support pain. Initially, I expected it to be
8139 enough to include the firmware packages on the CD to get
8140 debian-installer to find and use them. This proved to be wrong.
8141 Next, I hoped it was enough to symlink the relevant firmware packages
8142 to some useful location on the CD (tried /cdrom/ and
8143 /cdrom/firmware/). This also proved to not work, and at this point I
8144 found time to look at the debian-installer code to figure out what was
8145 going to work.&lt;/p&gt;
8146
8147 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
8148 look revealed that it would only look for firmware packages outside
8149 the installation media, so the CD was never checked for firmware
8150 packages. It would only check USB sticks, floppies and other
8151 &quot;external&quot; media devices. Today I changed it to also look in the
8152 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8153 solve the problem I ran into with Debian edu. I also changed it to
8154 look in /firmware/, to make sure the installer also find firmware
8155 provided in the initrd when booting the installer via PXE, to allow us
8156 to provide the same feature in the PXE setup included in Debian
8157 Edu.&lt;/p&gt;
8158
8159 &lt;p&gt;To make sure firmware deb packages with a license questions are not
8160 activated without asking if the license is accepted, I extended
8161 hw-detect to look for preinst scripts in the firmware packages, and
8162 run these before activating the firmware during installation. The
8163 license question is asked using debconf in the preinst, so this should
8164 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
8165
8166 &lt;p&gt;If you want to discuss the details of these features, please
8167 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
8168 </description>
8169 </item>
8170
8171 <item>
8172 <title>Parallellized boot is now the default in Debian/unstable</title>
8173 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
8174 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
8175 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
8176 <description>&lt;p&gt;Since this evening, parallel booting is the default in
8177 Debian/unstable for machines using dependency based boot sequencing.
8178 Apparently the testing of concurrent booting has been wider than
8179 expected, if I am to believe the
8180 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8181 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
8182 with the feature this weekend, to give us some time to detect any
8183 remaining problems before Squeeze is frozen. If serious problems are
8184 detected, it is simple to change the default back to sequential boot.
8185 The upload of the new sysvinit package also activate a new upstream
8186 version.&lt;/p&gt;
8187
8188 More information about
8189 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8190 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
8191 currently possible to disable parallel booting when one run into
8192 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
8193
8194 &lt;blockquote&gt;&lt;pre&gt;
8195 CONCURRENCY=none
8196 &lt;/pre&gt;&lt;/blockquote&gt;
8197
8198 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8199 the BTS, please usertag the report to get it to show up at
8200 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8201 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8202 </description>
8203 </item>
8204
8205 <item>
8206 <title>Sitesummary tip: Listing MAC address of all clients</title>
8207 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
8208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
8209 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
8210 <description>&lt;p&gt;In the recent Debian Edu versions, the
8211 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
8212 system&lt;/a&gt; is used to keep track of the machines in the school
8213 network. Each machine will automatically report its status to the
8214 central server after boot and once per night. The network setup is
8215 also reported, and using this information it is possible to get the
8216 MAC address of all network interfaces in the machines. This is useful
8217 to update the DHCP configuration.&lt;/p&gt;
8218
8219 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
8220 ist all MAC addresses of all machines reporting to sitesummary. Run
8221 this on the collector host:&lt;/p&gt;
8222
8223 &lt;blockquote&gt;&lt;pre&gt;
8224 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
8225 &lt;/pre&gt;&lt;/blockquote&gt;
8226
8227 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
8228 line per machine and with space between the MAC addresses.&lt;/p&gt;
8229
8230 &lt;p&gt;To allow system administrators easier job at adding static DHCP
8231 addresses for hosts, it would be possible to extend this to fetch
8232 machine information from sitesummary and update the DHCP and DNS
8233 tables in LDAP using this information. Such tool is unfortunately not
8234 written yet.&lt;/p&gt;
8235 </description>
8236 </item>
8237
8238 <item>
8239 <title>systemd, an interesting alternative to upstart</title>
8240 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
8241 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
8242 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
8243 <description>&lt;p&gt;The last few days a new boot system called
8244 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
8245 has been
8246 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
8247
8248 to the free software world. I have not yet had time to play around
8249 with it, but it seem to be a very interesting alternative to
8250 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
8251 a good alternative for Debian when we are able to switch to an event
8252 based boot system. Tollef is
8253 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
8254 systemd into Debian, and I look forward to seeing how well it work. I
8255 like the fact that systemd handles init.d scripts with dependency
8256 information natively, allowing them to run in parallel where upstart
8257 at the moment do not.&lt;/p&gt;
8258
8259 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
8260 platform support. It only work on recent Linux kernels, and also need
8261 some new kernel features enabled to function properly. This means
8262 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8263 system. Not sure how that will be handled if systemd proves to be the
8264 way forward.&lt;/p&gt;
8265
8266 &lt;p&gt;In the mean time, based on the
8267 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8268 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
8269 decided to enable full parallel booting as the default in Debian as
8270 soon as possible (probably this weekend or early next week), to see if
8271 there are any remaining serious bugs in the init.d dependencies. A
8272 new version of the sysvinit package implementing this change is
8273 already in experimental. If all go well, Squeeze will be released
8274 with parallel booting enabled by default.&lt;/p&gt;
8275 </description>
8276 </item>
8277
8278 <item>
8279 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
8280 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
8281 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
8282 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
8283 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
8284 complete, so complete that it is actually possible to run all the
8285 init.d scripts in parallell based on these dependencies. If you want
8286 to test your Squeeze system, make sure
8287 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8288 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8289 /etc/default/rcS:&lt;/p&gt;
8290
8291 &lt;blockquote&gt;&lt;pre&gt;
8292 CONCURRENCY=makefile
8293 &lt;/pre&gt;&lt;/blockquote&gt;
8294
8295 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8296 scripts in parallel using the dependency information stored in
8297 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8298 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8299 to try to start the kdm and gdm scripts as early as possible, and will
8300 start the facilities required by kdm or gdm as early as possible to
8301 make this happen.&lt;/p&gt;
8302
8303 &lt;p&gt;Give it a try, and see if you like the result. If some services
8304 fail to start properly, it is most likely because they have incomplete
8305 init.d script dependencies in their startup script (or some of their
8306 dependent scripts have incomplete dependencies). Report bugs and get
8307 the package maintainers to fix it. :)&lt;/p&gt;
8308
8309 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8310 manage to get the init.d script dependencies complete and correct. I
8311 expect we will get there in Squeeze+1, if we get manage to test and
8312 fix the remaining issues.&lt;/p&gt;
8313
8314 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8315 the BTS, please usertag the report to get it to show up at
8316 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8317 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8318 </description>
8319 </item>
8320
8321 <item>
8322 <title>Debian has switched to dependency based boot sequencing</title>
8323 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8324 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8325 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8326 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8327 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8328 have been migrated to using dependency based boot sequencing. This
8329 conclude work me and others have been doing for the last three days.
8330 It feels great to see this finally part of the default Debian
8331 installation. Now we just need to weed out the last few problems that
8332 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8333
8334 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8335 fixing the more fundamental problem of handing the event based
8336 non-predictable kernel in the early boot.&lt;/p&gt;
8337 </description>
8338 </item>
8339
8340 <item>
8341 <title>Taking over sysvinit development</title>
8342 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8343 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8344 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8345 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8346 the existing sysvinit upstream developer, I decided a few weeks ago to
8347 take over the package and become the new upstream. The number of
8348 patches to track for the Debian package was becoming a burden, and the
8349 lack of synchronization between the distribution made it hard to keep
8350 the package up to date.&lt;/p&gt;
8351
8352 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8353 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8354 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8355 and Fedora), based on the patches currently in use in these
8356 distributions. We Debian maintainers plan to move to this tarball as
8357 the new upstream as soon as we find time to do the merge. Since the
8358 new tarball was created, we agreed with Werner at SuSe to make a new
8359 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8360 development there. The project is registered and currently waiting
8361 for approval by the Savannah administrators, and as soon as it is
8362 approved, we will import the old versions from svn and continue
8363 working on the future release.&lt;/p&gt;
8364
8365 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8366 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8367 </description>
8368 </item>
8369
8370 <item>
8371 <title>Debian boots quicker and quicker</title>
8372 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8373 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8374 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8375 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8376 people involved in the boot system on Debian and Ubuntu, to see if we
8377 could find more ways to speed up the boot system. This was an Ubuntu
8378 funded
8379 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8380 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8381 of boot systems, and ways to handle the increasing number of boot
8382 issues introduced by the Linux kernel becoming more and more
8383 asynchronous and event base. The Ubuntu approach using udev and
8384 upstart might be a good way forward. Time will show.&lt;/p&gt;
8385
8386 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8387 process in Debian. All of these should be applied to get a quick
8388 boot:&lt;/p&gt;
8389
8390 &lt;ul&gt;
8391
8392 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8393
8394 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8395 clock is in UTC.&lt;/li&gt;
8396
8397 &lt;li&gt;Install and activate the insserv package to enable
8398 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8399 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8400
8401 &lt;/ul&gt;
8402
8403 These points are based on the Google summer of code work done by
8404 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8405 Villegas&lt;/a&gt;.
8406
8407 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8408 unstable yesterday. When we tested it, we were able to cut 6 seconds
8409 from the boot sequence. It depend on very correct dependency
8410 declaration in all init.d scripts, so I expect us to find edge cases
8411 where the dependences in some scripts are slightly wrong when we start
8412 using this.&lt;/p&gt;
8413
8414 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8415 introduced by Raphael Geissert today, one that could affect the
8416 startup speed as well. Instead of starting some scripts concurrently
8417 from rcS.d/ and another set of scripts from rc2.d/, it would be
8418 possible to run a of them in the same process. A quick way to test
8419 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8420 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8421 </description>
8422 </item>
8423
8424 <item>
8425 <title>BSAs påstander om piratkopiering møter motstand</title>
8426 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8427 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8428 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8429 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8430 programvareselskapene som Microsoft og Apple, publisert en rapport der
8431 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8432 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8433 dager siden kom
8434 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8435 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8436 dagene. Et spesielt interessant kommentar fra Sverige,
8437 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8438 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8439
8440 &lt;blockquote&gt;
8441 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8442 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8443 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8444 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8445 &lt;/blockquote&gt;
8446
8447 &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
8448 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8449 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8450 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8451 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8452
8453 &lt;p&gt;Fant lenkene via &lt;a
8454 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8455 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8456 </description>
8457 </item>
8458
8459 <item>
8460 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8461 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8462 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8463 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8464 <description>&lt;p&gt;Kom over
8465 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8466 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8467 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8468 jobber til daglig. En rask opptelling forteller meg at vi har 490
8469 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8470 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8471 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8472 </description>
8473 </item>
8474
8475 <item>
8476 <title>Kryptert harddisk - naturligvis</title>
8477 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8478 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8479 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8480 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8481 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8482 når en tar tap av arbeidstid, fortrolige dokumenter,
8483 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8484 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8485 til at jeg har kryptert harddisken på både kontormaskinen og min
8486 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8487 komme på avveie, den første informasjon relatert til jobben min ved
8488 Universitetet i Oslo, og den andre relatert til blant annet
8489 foreningsarbeide. Kryptering av diskene gjør at det er lite
8490 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8491 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8492 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8493 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8494 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8495 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8496 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8497 det er gjort slik jeg gjør det er minimale, og gevinstene er
8498 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8499 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8500
8501 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8502 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8503 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8504 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8505 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8506 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8507 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8508 betydelige.&lt;/p&gt;
8509 </description>
8510 </item>
8511
8512 <item>
8513 <title>Two projects that have improved the quality of free software a lot</title>
8514 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8516 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8517 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8518 quality of free software, and I wanted to mention both in case someone
8519 do not yet know them.&lt;/p&gt;
8520
8521 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8522 tool to detect and expose errors in the memory handling of programs.
8523 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8524 and it will report any problems on stdout. It is even better if the
8525 program include debug information. With debug information, it is able
8526 to report the source file name and line number where the problem
8527 occurs. It can report things like &#39;reading past memory block in file
8528 X line N, the memory block was allocated in file Y, line M&#39;, and
8529 &#39;using uninitialised value in control logic&#39;. This tool has made it
8530 trivial to investigate reproducible crash bugs in programs, and have
8531 reduced the number of this kind of bugs in free software a lot.
8532
8533 &lt;p&gt;The second one is
8534 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8535 a source code checker. It is able to process the source of a program
8536 and find problems in the logic without running the program. It
8537 started out as the Stanford Checker and became well known when it was
8538 used to find bugs in the Linux kernel. It is now a commercial tool
8539 and the company behind it is running
8540 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8541 free software community, where a lot of free software projects get
8542 their source checked for free. Several thousand defects have been
8543 found and fixed so far. It can find errors like &#39;lock L taken in file
8544 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8545 Y lines O to P can never be executed&#39;. The projects included in the
8546 community service project have managed to get rid of a lot of
8547 reliability problems thanks to Coverity.&lt;/p&gt;
8548
8549 &lt;p&gt;I believe tools like this, that are able to automatically find
8550 errors in the source, are vital to improve the quality of software and
8551 make sure we can get rid of the crashing and failing software we are
8552 surrounded by today.&lt;/p&gt;
8553 </description>
8554 </item>
8555
8556 <item>
8557 <title>No patch is not better than a useless patch</title>
8558 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8559 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8560 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8561 <description>&lt;p&gt;Julien Blache
8562 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8563 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8564 patch allow one to discuss a concrete and proposed solution, and also
8565 prove that the issue at hand is important enough for someone to spent
8566 time on fixing it. No patch do not provide any of these positive
8567 properties.&lt;/p&gt;
8568 </description>
8569 </item>
8570
8571 <item>
8572 <title>Standardize on protocols and formats, not vendors and applications</title>
8573 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8575 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8576 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8577 very good one to form a long lived computer infrastructure. It is the
8578 simple one, lost by many in todays computer industry: Standardize on
8579 open network protocols and open exchange/storage formats, not applications.
8580 Applications come and go, while protocols and files tend to stay, and
8581 thus one want to make it easy to change application and vendor, while
8582 avoiding conversion costs and locking users to a specific platform or
8583 application.&lt;/p&gt;
8584
8585 &lt;p&gt;This approach make it possible to replace the client applications
8586 independently of the server applications. One can even allow users to
8587 use several different applications as long as they handle the selected
8588 protocol and format. In the normal case, only one client application
8589 is recommended and users only get help if they choose to use this
8590 application, but those that want to deviate from the easy path are not
8591 blocked from doing so.&lt;/p&gt;
8592
8593 &lt;p&gt;It also allow us to replace the server side without forcing the
8594 users to replace their applications, and thus allow us to select the
8595 best server implementation at any moment, when scale and resouce
8596 requirements change.&lt;/p&gt;
8597
8598 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8599 open formats, but I would never recommend standardizing on a single
8600 application that do not use open network protocol or open formats.&lt;/p&gt;
8601 </description>
8602 </item>
8603
8604 <item>
8605 <title>Returning from Skolelinux developer gathering</title>
8606 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8607 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8608 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8609 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8610 Edu/Skolelinux development gathering. I got a bit done tuning the
8611 desktop, and looked into the dynamic service location protocol
8612 implementation avahi. It look like it could be useful for us. Almost
8613 30 people participated, and I believe it was a great environment to
8614 get to know the Skolelinux system. Walter Bender, involved in the
8615 development of the Sugar educational platform, presented his stuff and
8616 also helped me improve my OLPC installation. He also showed me that
8617 his Turtle Art application can be used in standalone mode, and we
8618 agreed that I would help getting it packaged for Debian. As a
8619 standalone application it would be great for Debian Edu. We also
8620 tried to get the video conferencing working with two OLPCs, but that
8621 proved to be too hard for us. The application seem to need more work
8622 before it is ready for me. I look forward to getting home and relax
8623 now. :)&lt;/p&gt;
8624 </description>
8625 </item>
8626
8627 <item>
8628 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8629 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8631 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8632 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8633 optimal. There is RFC 2307 documenting one way to store NIS maps in
8634 LDAP, and a modified version of this normally called RFC 2307bis, with
8635 some modifications to be compatible with Active Directory. The RFC
8636 specification handle the content of a lot of system databases, but do
8637 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8638
8639 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8640 we would like to store information about users, SMB clients/hosts,
8641 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8642 and LTSP configuration in LDAP. These objects have a lot in common,
8643 but with the current LDAP schemas it is not possible to have one
8644 object per entity. For example, one need to have at least three LDAP
8645 objects for a given computer, one with the SMB related stuff, one with
8646 DNS information and another with DHCP information. The schemas
8647 provided for DNS and DHCP are impossible to combine into one LDAP
8648 object. In addition, it is impossible to implement quick queries for
8649 netgroup membership, because of the way NIS triples are implemented.
8650 It just do not scale. I believe it is time for a few RFC
8651 specifications to cleam up this mess.&lt;/p&gt;
8652
8653 &lt;p&gt;I would like to have one LDAP object representing each computer in
8654 the network, and this object can then keep the SMB (ie host key), DHCP
8655 (mac address/name) and DNS (name/IP address) settings in one place.
8656 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8657
8658 &lt;p&gt;I would also like to have a quick way to map from a user or
8659 computer and to the net group this user or computer is a member.&lt;/p&gt;
8660
8661 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8662 in this regard, and the unix side need to catch up. Time to start a
8663 new IETF work group?&lt;/p&gt;
8664 </description>
8665 </item>
8666
8667 <item>
8668 <title>Endelig er Debian Lenny gitt ut</title>
8669 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8670 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8671 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8672 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8673 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8674 Et langt steg videre for Debian-prosjektet, og en rekke nye
8675 programpakker blir nå tilgjengelig for de av oss som bruker den
8676 stabile utgaven av Debian. Neste steg er nå å få
8677 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8678 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8679 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8680 slippes løs på skolene. Takk til alle debian-utviklerne som har
8681 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8682 bootsekvens tilgjengelig i stabil utgave, vha pakken
8683 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8684 </description>
8685 </item>
8686
8687 <item>
8688 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8689 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8690 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8691 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8692 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8693 Oslo. Most of Saturday was used for the general assemly for the
8694 member organization, but the rest of the weekend I used to tune the
8695 LTSP installation. LTSP now work out of the box on the 10-network.
8696 Acer Aspire One proved to be a very nice thin client, with both
8697 screen, mouse and keybard in a small box. Was working on getting the
8698 diskless workstation setup configured out of the box, but did not
8699 finish it before the weekend was up.&lt;/p&gt;
8700
8701 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8702 the Brazilian group, so that will have to wait for the next
8703 development gathering. Would love to have the Debian Edu installer
8704 automatically detect and configure a multiseat setup when it find one
8705 of these cards.&lt;/p&gt;
8706 </description>
8707 </item>
8708
8709 <item>
8710 <title>The sorry state of multimedia browser plugins in Debian</title>
8711 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8712 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8713 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8714 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8715 plugins available in Debian Lenny, to see which one we should use by
8716 default in Debian Edu. We need an embedded video playing plugin with
8717 control buttons to pause or stop the video, and capable of streaming
8718 all the multimedia content available on the web. The test results and
8719 notes are available on
8720 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8721 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8722 fill this need. My personal video player favorite, VLC, has a really
8723 bad plugin which fail on a lot of the test pages. A lot of the MIME
8724 types I would expect to work with any free software player (like
8725 video/ogg), just do not work. And simple formats like the
8726 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8727 totem and vlc plugins. I hope the situation will improve soon. No
8728 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8729
8730 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8731 be the only one fitting our needs. :/&lt;/p&gt;
8732 </description>
8733 </item>
8734
8735 </channel>
8736 </rss>