]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
ad14b3a86ad56fc1b8ec7ce4a358e8f12fda05b8
[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>The Pyra - handheld computer with Debian preinstalled</title>
11 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
13 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
14 <description>A friend of mine made me aware of
15 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
16 handheld computer which will be delivered with Debian preinstalled. I
17 would love to get one of those for my birthday. :)&lt;/p&gt;
18
19 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
20 plugs and many others connectors, and include a full keyboard and a 5&quot;
21 LCD touch screen. The 6000mAh battery is claimed to provide a whole
22 day of battery life time, but I have not seen any independent tests
23 confirming this. The vendor is still collecting preorders, and the
24 last I heard last night was that 22 more orders were needed before
25 production started.&lt;/p&gt;
26
27 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
28 Debian. Please let me know if you know of any others. Is it the
29 first computer being sold with Debian preinstalled?&lt;/p&gt;
30 </description>
31 </item>
32
33 <item>
34 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
35 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
36 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
37 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
38 <description>&lt;p&gt;During this weekends
39 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
40 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
41 to make sure there are good books about Debian available in Norwegian
42 Bokmål, and got in touch with the people behind the
43 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
44 project&lt;/a&gt; to get started. If you want to help out, please start
45 contributing using
46 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
47 hosted weblate project page&lt;/a&gt;, and get in touch using
48 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
49 translators mailing list&lt;/a&gt;. Please also check out
50 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
51 contributors&lt;/a&gt;.&lt;/p&gt;
52
53 &lt;p&gt;The book is already available on paper in English, French and
54 Japanese, and our goal is to get it available on paper in Norwegian
55 Bokmål too. In addition to the paper edition, there are also EPUB and
56 Mobi versions available. And there are incomplete translations
57 available for many more languages.&lt;/p&gt;
58 </description>
59 </item>
60
61 <item>
62 <title>One in two hundred Debian users using ZFS on Linux?</title>
63 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
64 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
65 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
66 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
67 packages in Debian, and was quite surprised with what I found. I use
68 ZFS myself at home, but did not really expect many others to do so.
69 But I might be wrong.&lt;/p&gt;
70
71 &lt;p&gt;According to
72 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
73 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
74 0.53% of the population, with the package installed. As far as I know
75 the only use of the spl-linux package is as a support library for ZFS
76 on Linux, so I use it here as proxy for measuring the number of ZFS
77 installation on Linux in Debian. In the kFreeBSD variant of Debian
78 the ZFS feature is already available, and there
79 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
80 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
81 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
82
83 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
84 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
85 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
86 cleared, the package is still not in Debian. The package is again in
87 the NEW queue. Several uploads have been rejected so far because the
88 debian/copyright file was incomplete or wrong, but there is no reason
89 to give up. The current status can be seen on
90 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
91 team status page&lt;/a&gt;, and
92 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
93 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
94
95 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
96 my home server can function in the future using only official Debian
97 packages, and the current blocker is to get the debian/copyright file
98 accepted by the FTP masters in Debian, I decided a while back to try
99 to help out the team. This was the background for my blog post about
100 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
101 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
102 used the techniques I explored there to try to find any errors in the
103 copyright file. It is not very easy to check every one of the around
104 2000 files in the source package, but I hope we this time got it
105 right. If you want to help out, check out the git source and try to
106 find missing entries in the debian/copyright file.&lt;/p&gt;
107 </description>
108 </item>
109
110 <item>
111 <title>Full battery stats collector is now available in Debian</title>
112 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
113 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
114 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
115 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
116 extended collector that will collect the complete battery history for
117 later processing and graphing. The original collector store the
118 battery level as percentage of last full level, while the new
119 collector also record battery vendor, model, serial number, design
120 full level, last full level and current battery level. This make it
121 possible to predict the lifetime of the battery as well as visualise
122 the energy flow when the battery is charging or discharging.&lt;/p&gt;
123
124 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
125 in the version 0.5.1 package in unstable. Get the new battery level graph
126 and lifetime prediction by running:
127
128 &lt;p&gt;&lt;pre&gt;
129 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
130 &lt;/pre&gt;&lt;/p&gt;
131
132 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
133
134 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
135 entry yet):&lt;/p&gt;
136
137 &lt;p&gt;&lt;pre&gt;
138 /usr/share/battery-stats/battery-stats-graph-flow
139 &lt;/pre&gt;&lt;/p&gt;
140
141 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
142 when there are few data points. The graphs look a bit better with a
143 few years of data.&lt;/p&gt;
144
145 &lt;p&gt;A while back one important feature I use in the battery stats
146 collector broke in Debian. The scripts in
147 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
148 suspect it happened when Jessie started using systemd, but I do not
149 know. The issue is reported as
150 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
151 pm-utils. I managed to work around it by adding an udev rule to call
152 the collector script every time the power connector is connected and
153 disconnected. With this fix in place it was finally time to make a
154 new release of the package, and get it into Debian.&lt;/p&gt;
155
156 &lt;p&gt;If you are interested in how your laptop battery is doing, please
157 check out the
158 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
159 in Debian unstable, or rebuild it on Jessie to get it working on
160 Debian stable. :) The upstream source is available from
161 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
162 As always, patches are very welcome.&lt;/p&gt;
163 </description>
164 </item>
165
166 <item>
167 <title>Making battery measurements a little easier in Debian</title>
168 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
169 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
170 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
171 <description>&lt;p&gt;Back in September, I blogged about
172 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
173 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
174 how it showed the decay and death of this battery (now replaced). I
175 created a simple deb package to handle the collection and graphing,
176 but did not want to upload it to Debian as there were already
177 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
178 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
179 a point of uploading a competing package when battery-stats could be
180 fixed instead. I reported a few bugs about its non-function, and
181 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
182
183 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
184 hands. The end result is that I am now the new upstream developer of
185 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
186 battery-stats in Debian, and the package in Debian unstable is finally
187 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
188 information provided by the Linux kernel. If you install the
189 battery-stats package from unstable now, you will be able to get a
190 graph of the current battery fill level, to get some idea about the
191 status of the battery. The source package build and work just fine in
192 Debian testing and stable (and probably oldstable too, but I have not
193 tested). The default graph you get for that system look like this:&lt;/p&gt;
194
195 &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;
196
197 &lt;p&gt;My plans for the future is to merge my old scripts into the
198 battery-stats package, as my old scripts collected a lot more details
199 about the battery. The scripts are merged into the upstream
200 battery-stats git repository already, but I am not convinced they work
201 yet, as I changed a lot of paths along the way. Will have to test a
202 bit more before I make a new release.&lt;/p&gt;
203
204 &lt;p&gt;I will also consider changing the file format slightly, as I
205 suspect the way I combine several values into one field might make it
206 impossible to know the type of the value when using it for processing
207 and graphing.&lt;/p&gt;
208
209 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
210 battery, check out the battery-stats package in
211 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
212 on
213 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
214 I would love some help to improve the system further.&lt;/p&gt;
215 </description>
216 </item>
217
218 <item>
219 <title>Creating, updating and checking debian/copyright semi-automatically</title>
220 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
222 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
223 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
224 details. And one of the details is the content of the
225 debian/copyright file, which should list all relevant licenses used by
226 the code in the package in question, preferably in
227 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
228 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
229
230 &lt;p&gt;For large packages with lots of contributors it is hard to write
231 and update this file manually, and if you get some detail wrong, the
232 package is normally rejected by the ftpmasters. So getting it right
233 the first time around get the package into Debian faster, and save
234 both you and the ftpmasters some work.. Today, while trying to figure
235 out what was wrong with
236 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
237 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
238 figuring out the options for doing this job automatically, or at least
239 semi-automatically.&lt;/p&gt;
240
241 &lt;p&gt;Lucikly, there are at least two tools available for generating the
242 file based on the code in the source package,
243 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
244 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
245 not sure which one of them came first, but both seem to be able to
246 create a sensible draft file. As far as I can tell, none of them can
247 be trusted to get the result just right, so the content need to be
248 polished a bit before the file is OK to upload. I found the debmake
249 option in
250 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
251 blog posts from 2014&lt;/a&gt;.
252
253 &lt;p&gt;To generate using debmake, use the -cc option:
254
255 &lt;p&gt;&lt;pre&gt;
256 debmake -cc &gt; debian/copyright
257 &lt;/pre&gt;&lt;/p&gt;
258
259 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
260 this might not be the best option.&lt;/p&gt;
261
262 &lt;p&gt;The cme option is based on a config parsing library, and I found
263 this approach in
264 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
265 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
266 dpkg-copyright&#39; option:
267
268 &lt;p&gt;&lt;pre&gt;
269 cme update dpkg-copyright
270 &lt;/pre&gt;&lt;/p&gt;
271
272 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
273 handle UTF-8 names better than debmake.&lt;/p&gt;
274
275 &lt;p&gt;When the copyright file is created, I would also like some help to
276 check if the file is correct. For this I found two good options,
277 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
278 to focus on license types and file matching, and is able to detect
279 ineffective blocks in the copyright file. The latter reports missing
280 copyright holders and years, but was confused by inconsistent license
281 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
282 fix all issues reported by them before uploading. But I do not know
283 if the tools and the ftpmasters agree on what is important to fix in a
284 copyright file, so the package might still be rejected.&lt;/p&gt;
285
286 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
287 will read through the source and try to find all copyright statements.
288 It is not comparing the result to the content of debian/copyright, but
289 can be useful when verifying the content of the copyright file.&lt;/p&gt;
290
291 &lt;p&gt;Are you aware of better tools in Debian to create and update
292 debian/copyright file. Please let me know, or blog about it on
293 planet.debian.org.&lt;/p&gt;
294
295 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
296 activities, please send Bitcoin donations to my address
297 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
298
299 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
300 on how to use licensecheck and cdbs to create a draft copyright file
301
302 &lt;p&gt;&lt;pre&gt;
303 licensecheck --copyright -r `find * -type f` | \
304 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
305 &lt;/pre&gt;&lt;/p&gt;
306
307 &lt;p&gt;He mentioned that he normally check the generated file into the
308 version control system to make it easier to discover license and
309 copyright changes in the upstream source. I will try to do the same
310 with my packages in the future.&lt;/p&gt;
311
312 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
313 against using -quiet for new users, so I removed it from the proposed
314 command line.&lt;/p&gt;
315 </description>
316 </item>
317
318 <item>
319 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
320 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
321 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
322 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
323 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
324 is taking shape in Debian, and one provided feature is a very
325 convenient way to tell you which package to install to make a given
326 firmware file available when the kernel is looking for it. This can
327 be done using apt-file too, but that is for someone else to blog
328 about. :)&lt;/p&gt;
329
330 &lt;p&gt;Here is a small recipe to find the package with a given firmware
331 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
332 picked from the set of firmware announced using appstream in Debian
333 unstable. In general you would be looking for the firmware requested
334 by the kernel during kernel module loading. To find the package
335 providing the example file, do like this:&lt;/p&gt;
336
337 &lt;blockquote&gt;&lt;pre&gt;
338 % apt install appstream
339 [...]
340 % apt update
341 [...]
342 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
343 awk &#39;/Package:/ {print $2}&#39;
344 firmware-qlogic
345 %
346 &lt;/pre&gt;&lt;/blockquote&gt;
347
348 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
349 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
350 a way appstream can use.&lt;/p&gt;
351
352 &lt;p&gt;This same approach can be used to find any package supporting a
353 given MIME type. This is very useful when you get a file you do not
354 know how to handle. First find the mime type using &lt;tt&gt;file
355 --mime-type&lt;/tt&gt;, and next look up the package providing support for
356 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
357 and you can find all packages handling this type like this:&lt;/p&gt;
358
359 &lt;blockquote&gt;&lt;pre&gt;
360 % apt install appstream
361 [...]
362 % apt update
363 [...]
364 % appstreamcli what-provides mimetype image/svg+xml | \
365 awk &#39;/Package:/ {print $2}&#39;
366 bkchem
367 phototonic
368 inkscape
369 shutter
370 tetzle
371 geeqie
372 xia
373 pinta
374 gthumb
375 karbon
376 comix
377 mirage
378 viewnior
379 postr
380 ristretto
381 kolourpaint4
382 eog
383 eom
384 gimagereader
385 midori
386 %
387 &lt;/pre&gt;&lt;/blockquote&gt;
388
389 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
390 packages providing appstream metadata.&lt;/p&gt;
391 </description>
392 </item>
393
394 <item>
395 <title>Creepy, visualise geotagged social media information - nice free software</title>
396 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
397 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
398 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
399 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
400 with the computerised radio beacon known as a mobile phone their
401 position is tracked by the phone company and often stored for a long
402 time (like every time a SMS is received or sent). And if their
403 computerised radio beacon is capable of running programs (often called
404 mobile apps) downloaded from the Internet, these programs are often
405 also capable of tracking their location (if the app requested access
406 during installation). And when these programs send out information to
407 central collection points, the location is often included, unless
408 extra care is taken to not send the location. The provided
409 information is used by several entities, for good and bad (what is
410 good and bad, depend on your point of view). What is certain, is that
411 the private sphere and the right to free movement is challenged and
412 perhaps even eradicated for those announcing their location this way,
413 when they share their whereabouts with private and public
414 entities.&lt;/p&gt;
415
416 &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;
417
418 &lt;p&gt;The phone company logs provide a register of locations to check out
419 when one want to figure out what the tracked person was doing. It is
420 unavailable for most of us, but provided to selected government
421 officials, company staff, those illegally buying information from
422 unfaithful servants and crackers stealing the information. But the
423 public information can be collected and analysed, and a free software
424 tool to do so is called
425 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
426 discovered it when I read
427 &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
428 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
429 November 2014, and decided to check if it was available in Debian.
430 The python program was in Debian, but
431 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
432 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
433 uploaded a new version which did not work quite right, but did not
434 have time to fix it then. This Christmas I decided to finally try to
435 get Creepy operational in Debian. Now a fixed version is available in
436 Debian unstable and testing, and almost all Debian specific patches
437 are now included
438 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
439
440 &lt;p&gt;The Creepy program visualises geolocation information fetched from
441 Twitter, Instagram, Flickr and Google+, and allow one to get a
442 complete picture of every social media message posted recently in a
443 given area, or track the movement of a given individual across all
444 these services. Earlier it was possible to use the search API of at
445 least some of these services without identifying oneself, but these
446 days it is impossible. This mean that to use Creepy, you need to
447 configure it to log in as yourself on these services, and provide
448 information to them about your search interests. This should be taken
449 into account when using Creepy, as it will also share information
450 about yourself with the services.&lt;/p&gt;
451
452 &lt;p&gt;The picture above show the twitter messages sent from (or at least
453 geotagged with a position from) the city centre of Oslo, the capital
454 of Norway. One useful way to use Creepy is to first look at
455 information tagged with an area of interest, and next look at all the
456 information provided by one or more individuals who was in the area.
457 I tested it by checking out which celebrity provide their location in
458 twitter messages by checkout out who sent twitter messages near a
459 Norwegian TV station, and next could track their position over time,
460 making it possible to locate their home and work place, among other
461 things. A similar technique have been
462 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
463 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
464 tool to discover lying governments, and a useful tool to help people
465 understand the value of the private information they provide to the
466 public.&lt;/p&gt;
467
468 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
469 it depend on several python modules currently missing in Jessie (at
470 least python-instagram, python-flickrapi and
471 python-requests-toolbelt).&lt;/p&gt;
472
473 &lt;p&gt;(I have uploaded
474 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
475 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
476 Creepy program in Debian.)&lt;/p&gt;
477 </description>
478 </item>
479
480 <item>
481 <title>Always download Debian packages using Tor - the simple recipe</title>
482 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
483 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
484 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
485 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
486 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
487 that those listening on the Internet lines would have good reason to
488 believe a computer have a given security hole&lt;/a&gt; if it download a
489 security fix from a Debian mirror. This is a good reason to always
490 use encrypted connections to the Debian mirror, to make sure those
491 listening do not know which IP address to attack. In August, Richard
492 Hartmann observed that encryption was not enough, when it was possible
493 to interfere download size to security patches or the fact that
494 download took place shortly after a security fix was released, and
495 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
496 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
497 was not the first to propose this, as the
498 &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;
499 package by Tim Retout already existed to make it easy to convince apt
500 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
501 aware of that package when I read the blog post from Richard.&lt;/p&gt;
502
503 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
504 sysadmins, and he set up a Tor hidden service on one of the central
505 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
506 it possible to download packages directly between two tor nodes,
507 making sure the network traffic always were encrypted.&lt;/p&gt;
508
509 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
510 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
511 urls with tor+http and tor+https, and using the hidden service instead
512 of the official Debian mirror site. I recommend installing
513 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
514 done in /etc/.&lt;/p&gt;
515
516 &lt;blockquote&gt;&lt;pre&gt;
517 apt install apt-transport-tor
518 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
519 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
520 &lt;/pre&gt;&lt;/blockquote&gt;
521
522 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
523 the sed commands for these too. The sed command is assuming your are
524 using the ftp.debian.org Debian mirror. Adjust the command (or just
525 edit the file manually) to match your mirror.&lt;/p&gt;
526
527 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
528 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
529 system, and do not work with these tor+http URLs. For
530 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
531 which need a recent apt version currently only in unstable. So if you
532 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
533
534 &lt;p&gt;Another advantage from this change is that your machine will start
535 using Tor regularly and at fairly random intervals (every time you
536 update the package lists or upgrade or install a new package), thus
537 masking other Tor traffic done from the same machine. Using Tor will
538 become normal for the machine in question.&lt;/p&gt;
539
540 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
541 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
542 enabled. It would be great if it was the default on any Debian
543 system.&lt;/p&gt;
544 </description>
545 </item>
546
547 <item>
548 <title>OpenALPR, find car license plates in video streams - nice free software</title>
549 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
550 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
551 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
552 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
553 call the car license plate numbers in those days. I would write the
554 numbers down in my little book and compare notes with the other kids
555 to see how many region codes we had seen and if we had seen some
556 exotic or special region codes and numbers. It was a fun game to pass
557 time, as we kids have plenty of it.&lt;/p&gt;
558
559 &lt;p&gt;A few days I came across
560 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
561 project&lt;/a&gt;, a free software project to automatically discover and
562 report license plates in images and video streams, and provide the
563 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
564 such system for a while now, because I believe it is a bad idea that the
565 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
566 number plate recognition&lt;/a&gt; tool only is available in the hands of
567 the powerful, and want it to be available also for the powerless to
568 even the score when it comes to surveillance and sousveillance. I
569 discovered the developer
570 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
571 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
572 help him get it into shape to get the package uploaded into the Debian
573 archive.&lt;/p&gt;
574
575 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
576 it into Debian, where it currently
577 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
578 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
579
580 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
581 for the common folks, ie those not running a large government
582 surveillance system? Well, I plan to put it in a computer on my bike
583 and in my car, tracking the cars nearby and allowing me to be notified
584 when number plates on my watch list are discovered. Another use case
585 was suggested by a friend of mine, who wanted to set it up at his home
586 to open the car port automatically when it discovered the plate on his
587 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
588 capable of placing his license plate number of a piece of cardboard to
589 open his car port, men replied that it was always unlocked anyway. I
590 guess for such use case it make sense. I am sure there are other use
591 cases too, for those with imagination and a vision.&lt;/p&gt;
592
593 &lt;p&gt;If you want to build your own version of the Debian package, check
594 out the upstream git source and symlink ./distros/debian to ./debian/
595 before running &quot;debuild&quot; to build the source. Or wait a bit until the
596 package show up in unstable.&lt;/p&gt;
597 </description>
598 </item>
599
600 <item>
601 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
602 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
603 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
604 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
605 <description>&lt;p&gt;Around three years ago, I created
606 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
607 system&lt;/a&gt; to get a more practical solution in Debian for handing
608 hardware related packages. A GUI system in the isenkram package will
609 present a pop-up dialog when some hardware dongle supported by
610 relevant packages in Debian is inserted into the machine. The same
611 lookup mechanism to detect packages is available as command line
612 tools in the isenkram-cli package. In addition to mapping hardware,
613 it will also map kernel firmware files to packages and make it easy to
614 install needed firmware packages automatically. The key for this
615 system to work is a good way to map hardware to packages, in other
616 words, allow packages to announce what hardware they will work
617 with.&lt;/p&gt;
618
619 &lt;p&gt;I started by providing data files in the isenkram source, and
620 adding code to download the latest version of these data files at run
621 time, to ensure every user had the most up to date mapping available.
622 I also added support for storing the mapping in the Packages file in
623 the apt repositories, but did not push this approach because while I
624 was trying to figure out how to best store hardware/package mappings,
625 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
626 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
627 add the hardware mapping into that data set to be able to use
628 appstream as a data source, and this was accepted at least for the
629 Debian version of appstream.&lt;/p&gt;
630
631 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
632 and today I uploaded a new version 0.20 of isenkram adding support for
633 appstream as a data source for mapping hardware to packages. The only
634 package so far using appstream to announce its hardware support is my
635 pymissile package. I got help from Matthias Klumpp with figuring out
636 how do add the required
637 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
638 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
639 this content:&lt;/p&gt;
640
641 &lt;blockquote&gt;&lt;pre&gt;
642 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
643 &amp;lt;component&amp;gt;
644 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
645 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
646 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
647 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
648 &amp;lt;description&amp;gt;
649 &amp;lt;p&amp;gt;
650 Pymissile provides a curses interface to control an original
651 Marks and Spencer / Striker USB Missile Launcher, as well as a
652 motion control script to allow a webcamera to control the
653 launcher.
654 &amp;lt;/p&amp;gt;
655 &amp;lt;/description&amp;gt;
656 &amp;lt;provides&amp;gt;
657 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
658 &amp;lt;/provides&amp;gt;
659 &amp;lt;/component&amp;gt;
660 &lt;/pre&gt;&lt;/blockquote&gt;
661
662 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
663 which is a glob style match rule for hardware specific strings
664 (modalias strings) provided by the Linux kernel. In this case, it
665 will map to all USB devices with vendor code 1130 and product code
666 0202.&lt;/p&gt;
667
668 &lt;p&gt;Note, it is important that the license of all the metadata files
669 are compatible to have permissions to aggregate them into archive wide
670 appstream files. Matthias suggested to use MIT or BSD licenses for
671 these files. A challenge is figuring out a good id for the data, as
672 it is supposed to be globally unique and shared across distributions
673 (in other words, best to coordinate with upstream what to use). But
674 it can be changed later or, so we went with the package name as
675 upstream for this project is dormant.&lt;/p&gt;
676
677 &lt;p&gt;To get the metadata file installed in the correct location for the
678 mirror update scripts to pick it up and include its content the
679 appstream data source, the file must be installed in the binary
680 package under /usr/share/appdata/. I did this by adding the following
681 line to debian/pymissile.install:&lt;/p&gt;
682
683 &lt;blockquote&gt;&lt;pre&gt;
684 debian/pymissile.metainfo.xml usr/share/appdata
685 &lt;/pre&gt;&lt;/blockquote&gt;
686
687 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
688 all packages useful on the current computer automatically, and the GUI
689 pop-up handler will propose to install the package not already
690 installed if a hardware dongle is inserted into the machine in
691 question.&lt;/p&gt;
692
693 &lt;p&gt;Details of the modalias field in appstream is available from the
694 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
695
696 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
697 try running this command on the command line:&lt;/p&gt;
698
699 &lt;blockquote&gt;&lt;pre&gt;
700 cat $(find /sys/devices/|grep modalias)
701 &lt;/pre&gt;&lt;/blockquote&gt;
702
703 &lt;p&gt;To learn more about the isenkram system, please check out
704 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
705 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
706 </description>
707 </item>
708
709 <item>
710 <title>The GNU General Public License is not magic pixie dust</title>
711 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
712 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
713 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
714 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
715 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
716 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
717 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
718 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
719
720 &lt;blockquote&gt;
721
722 &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;
723
724 &lt;blockquote&gt;
725 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
726
727 The first step is to choose a
728 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
729 code.&lt;br/&gt;
730
731 The next step is, when someone fails to follow that copyleft license,
732 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
733
734 and its a simple fact of our modern society that such type of
735 work&lt;br/&gt;
736
737 is incredibly expensive to do and incredibly difficult to do.
738 &lt;/blockquote&gt;
739
740 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
741 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
742 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
743 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
744
745 &lt;p&gt;As the Debian Website
746 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
747 &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;
748 imply, public domain and permissively licensed software can lead to
749 the production of more proprietary software as people discover useful
750 software, extend it and or incorporate it into their hardware or
751 software products. Copyleft licenses such as the GNU GPL were created
752 to close off this avenue to the production of proprietary software but
753 such licenses are not enough. With the ongoing adoption of Free
754 Software by individuals and groups, inevitably the community&#39;s
755 expectations of license compliance are violated, usually out of
756 ignorance of the way Free Software works, but not always. As Karen
757 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
758 Freedom&quot;&gt;FaiF&lt;/a&gt;
759 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
760 copyleft is nothing if no-one is willing and able to stand up in court
761 to protect it. The reality of today&#39;s world is that legal
762 representation is expensive, difficult and time consuming. With
763 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
764 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
765 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
766 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
767 of the Linux project, Debian and other groups against GPL violations.
768 In March the SFC supported a
769 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
770 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
771 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
772 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
773 kernel. Since then two of their sponsors pulled corporate funding and
774 conferences
775 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
776 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
777 less on corporate funding and more on the broad community of
778 individuals who support Free Software and copyleft. So the SFC has
779 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
780 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
781 a community of folks who stand up for copyleft and the GPL by
782 supporting their work on promoting and supporting copyleft and Free
783 Software.&lt;/p&gt;
784
785 &lt;p&gt;If you support Free Software,
786 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
787 what the SFC do, agree with their
788 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
789 principles&lt;/a&gt;, are happy about their
790 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
791 work on a project that is an SFC
792 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
793 just want to stand up for copyleft, please join
794 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
795 Allan Webber&lt;/a&gt;,
796 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
797 Smith&lt;/a&gt;,
798 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
799 Bacon&lt;/a&gt;, myself and
800 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
801 becoming a
802 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
803 next week your donation will be
804 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
805 by an anonymous donor. Please also consider asking your employer to
806 match your donation or become a sponsor of SFC. Don&#39;t forget to
807 spread the word about your support for SFC via email, your blog and or
808 social media accounts.&lt;/p&gt;
809
810 &lt;/blockquote&gt;
811
812 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
813 of Software Freedom Conservancy myself. Perhaps you should be a
814 supporter too?&lt;/p&gt;
815 </description>
816 </item>
817
818 <item>
819 <title>PGP key transition statement for key EE4E02F9</title>
820 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
821 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
822 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
823 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
824 set it up properly. I wanted to generate it offline and have it
825 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
826 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
827 time to sit down with an offline machine almost took forever. But
828 finally I&#39;ve been able to complete the process, and have now moved
829 from my old GPG key to a new GPG key. See
830 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
831 full transition statement, signed with both my old and new key&lt;/a&gt; for
832 the details. This is my new key:&lt;/p&gt;
833
834 &lt;pre&gt;
835 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]
836 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
837 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
838 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
839 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
840 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
841 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
842 &lt;/pre&gt;
843
844 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
845 my old key.&lt;/p&gt;
846
847 &lt;p&gt;If you signed my old key
848 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
849 I&#39;d very much appreciate a signature on my new key, details and
850 instructions in the transition statement. I m happy to reciprocate if
851 you have a similarly signed transition statement to present.&lt;/p&gt;
852 </description>
853 </item>
854
855 <item>
856 <title>The life and death of a laptop battery</title>
857 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
858 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
859 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
860 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
861 But this do not last. The last few laptops gave me a feeling that
862 within a year, the life time is just a fraction of what it used to be,
863 and it slowly become painful to use the laptop without power connected
864 all the time. Because of this, when I got a new Thinkpad X230 laptop
865 about two years ago, I decided to monitor its battery state to have
866 more hard facts when the battery started to fail.&lt;/p&gt;
867
868 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
869
870 &lt;p&gt;First I tried to find a sensible Debian package to record the
871 battery status, assuming that this must be a problem already handled
872 by someone else. I found
873 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
874 which collects statistics from the battery, but it was completely
875 broken. I sent a few suggestions to the maintainer, but decided to
876 write my own collector as a shell script while I waited for feedback
877 from him. Via
878 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
879 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
880 discovered
881 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
882 available in Debian.&lt;/p&gt;
883
884 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
885 battery stats ever since. Now my
886 /var/log/hjemmenett-battery-status.log file contain around 115,000
887 measurements, from the time the battery was working great until now,
888 when it is unable to charge above 7% of original capacity. My
889 collector shell script is quite simple and look like this:&lt;/p&gt;
890
891 &lt;pre&gt;
892 #!/bin/sh
893 # Inspired by
894 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
895 # See also
896 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
897 logfile=/var/log/hjemmenett-battery-status.log
898
899 files=&quot;manufacturer model_name technology serial_number \
900 energy_full energy_full_design energy_now cycle_count status&quot;
901
902 if [ ! -e &quot;$logfile&quot; ] ; then
903 (
904 printf &quot;timestamp,&quot;
905 for f in $files; do
906 printf &quot;%s,&quot; $f
907 done
908 echo
909 ) &gt; &quot;$logfile&quot;
910 fi
911
912 log_battery() {
913 # Print complete message in one echo call, to avoid race condition
914 # when several log processes run in parallel.
915 msg=$(printf &quot;%s,&quot; $(date +%s); \
916 for f in $files; do \
917 printf &quot;%s,&quot; $(cat $f); \
918 done)
919 echo &quot;$msg&quot;
920 }
921
922 cd /sys/class/power_supply
923
924 for bat in BAT*; do
925 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
926 done
927 &lt;/pre&gt;
928
929 &lt;p&gt;The script is called when the power management system detect a
930 change in the power status (power plug in or out), and when going into
931 and out of hibernation and suspend. In addition, it collect a value
932 every 10 minutes. This make it possible for me know when the battery
933 is discharging, charging and how the maximum charge change over time.
934 The code for the Debian package
935 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
936 available on github&lt;/a&gt;.&lt;/p&gt;
937
938 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
939
940 &lt;pre&gt;
941 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
942 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
943 [...]
944 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
945 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
946 &lt;/pre&gt;
947
948 &lt;p&gt;I wrote a small script to create a graph of the charge development
949 over time. This graph depicted above show the slow death of my laptop
950 battery.&lt;/p&gt;
951
952 &lt;p&gt;But why is this happening? Why are my laptop batteries always
953 dying in a year or two, while the batteries of space probes and
954 satellites keep working year after year. If we are to believe
955 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
956 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
957 chance, and the fix is to not charge the Lithium-ion batteries to 100%
958 all the time, but to stay below 90% of full charge most of the time.
959 I&#39;ve been told that the Tesla electric cars
960 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
961 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
962 100% when preparing for a longer trip (not that I would want a car
963 like Tesla where rights to privacy is abandoned, but that is another
964 story), which I guess is the option we should have for laptops on
965 Linux too.&lt;/p&gt;
966
967 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
968 stop charging at 80%, unless requested to charge to 100% once in
969 preparation for a longer trip? I found
970 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
971 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
972 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
973 load).&lt;/p&gt;
974
975 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
976 at the start. I also wonder why the &quot;full capacity&quot; increases some
977 times, and if it is possible to repeat the process to get the battery
978 back to design capacity. And I wonder if the discharge and charge
979 speed change over time, or if this stay the same. I did not yet try
980 to write a tool to calculate the derivative values of the battery
981 level, but suspect some interesting insights might be learned from
982 those.&lt;/p&gt;
983
984 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
985 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
986 packages instead of the tp-smapi-dkms package I had tried to use
987 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
988 and stop. I&#39;ve done so now, but expect my existing battery is toast
989 and need to be replaced. The proposal is unfortunately Thinkpad
990 specific.&lt;/p&gt;
991 </description>
992 </item>
993
994 <item>
995 <title>New laptop - some more clues and ideas based on feedback</title>
996 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
997 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
998 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
999 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
1000 need for a new laptop, and provided very useful feedback. I wish to
1001 thank every one of these. Several pointed me to the possibility of
1002 fixing my X230, and I am already in the process of getting Lenovo to
1003 do so thanks to the on site, next day support contract covering the
1004 machine. But the battery is almost useless (I expect to replace it
1005 with a non-official battery) and I do not expect the machine to live
1006 for many more years, so it is time to plan its replacement. If I did
1007 not have a support contract, it was suggested to find replacement parts
1008 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
1009 might present a language barrier as I do not understand French.&lt;/p&gt;
1010
1011 &lt;p&gt;One tip I got was to use the
1012 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
1013 compare laptop models. It seem to have more models available than
1014 prisjakt.no. Another tip I got from someone I know have similar
1015 keyboard preferences was that the HP EliteBook 840 keyboard is not
1016 very good, and this matches my experience with earlier EliteBook
1017 keyboards I tested. Because of this, I will not consider it any further.
1018
1019 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
1020 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1021 (which is missing from the X240), and is working fairly well with
1022 Debian Sid/Unstable according to
1023 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
1024 got on the keyboard quality are not consistent. Some say the keyboard
1025 is good, others say it is ok, while others say it is not very good.
1026 Those with experience from X41 and and X60 agree that the X250
1027 keyboard is not as good as those trusty old laptops, and suggest I
1028 keep and fix my X230 instead of upgrading, or get a used X230 to
1029 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
1030 activity and battery status, which is very convenient on my X230. I&#39;m
1031 also told that the CPU fan is running very often, making it a bit
1032 noisy. In any case, the X250 do not work out of the box with Debian
1033 Stable/Jessie, one of my requirements.&lt;/p&gt;
1034
1035 &lt;p&gt;I have also gotten a few vendor proposals, one was
1036 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
1037 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
1038 The latter look very attractive to me.&lt;/p&gt;
1039
1040 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
1041 as I keep looking for a replacement.&lt;/p&gt;
1042
1043 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
1044 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
1045 different
1046 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
1047 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
1048 </description>
1049 </item>
1050
1051 <item>
1052 <title>Time to find a new laptop, as the old one is broken after only two years</title>
1053 <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>
1054 <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>
1055 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
1056 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
1057 replacement soon. The left 5 cm of the screen on my Thinkpad X230
1058 started flickering yesterday, and I suspect the cause is a broken
1059 cable, as changing the angle of the screen some times get rid of the
1060 flickering.&lt;/p&gt;
1061
1062 &lt;p&gt;My requirements have not really changed since I bought it, and is
1063 still as
1064 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
1065 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
1066 good help from
1067 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
1068 where I could select at least a few of the requirements (mouse pin,
1069 wifi, weight) and go through the rest manually. Three button mouse
1070 and a good keyboard is not available as an option, and all the three
1071 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
1072 G2) lack three mouse buttons). It is also unclear to me how good the
1073 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1074 the keyboard, even if the quality and robustness in the X series have
1075 deteriorated since X41.&lt;/p&gt;
1076
1077 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
1078 seem sensible to me? Are there better services around to search the
1079 set of available laptops for features? Please send me an email if you
1080 have suggestions.&lt;/p&gt;
1081
1082 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
1083 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
1084 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
1085 </description>
1086 </item>
1087
1088 <item>
1089 <title>How to stay with sysvinit in Debian Jessie</title>
1090 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
1091 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
1092 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
1093 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
1094 sysvinit as its boot system by default. But how can one keep using
1095 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1096 courtesy of
1097 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
1098 Schubert&lt;/a&gt; and
1099 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
1100 McVittie&lt;/a&gt;.
1101
1102 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
1103 keep sysvinit as your boot system, create a file
1104 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
1105 you upgrade:&lt;/p&gt;
1106
1107 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1108 Package: systemd-sysv
1109 Pin: release o=Debian
1110 Pin-Priority: -1
1111 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1112
1113 &lt;p&gt;This file content will tell apt and aptitude to not consider
1114 installing systemd-sysv as part of any installation and upgrade
1115 solution when resolving dependencies, and thus tell it to avoid
1116 systemd as a default boot system. The end result should be that the
1117 upgraded system keep using sysvinit.&lt;/p&gt;
1118
1119 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
1120 get sysvinit installed by default (debootstrap used by
1121 debian-installer have no option for this), but one can tell the
1122 installer to switch to sysvinit before the first boot. Either by
1123 using a kernel argument to the installer, or by adding a line to the
1124 preseed file used. First, the kernel command line argument:
1125
1126 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1127 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
1128 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1129
1130 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
1131
1132 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1133 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1134 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1135
1136 &lt;p&gt;One can of course also do this after the first boot by installing
1137 the sysvinit-core package.&lt;/p&gt;
1138
1139 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
1140 sysvinit boot sequence in Debian have several hardware specific bugs
1141 on Linux caused by the fact that it is unpredictable when hardware
1142 devices show up during boot. But on the other hand, the new default
1143 boot system still have a few rough edges I hope will be fixed before
1144 Jessie is released.&lt;/p&gt;
1145
1146 &lt;p&gt;Update 2014-11-26: Inspired by
1147 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
1148 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
1149 line.&lt;/p&gt;
1150 </description>
1151 </item>
1152
1153 <item>
1154 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
1155 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
1156 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
1157 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
1158 <description>&lt;p&gt;The right to communicate with your friends and family in private,
1159 without anyone snooping, is a right every citicen have in a liberal
1160 democracy. But this right is under serious attack these days.&lt;/p&gt;
1161
1162 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
1163 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1164 the whisleblower Snowden) more expensive for Internet email,
1165 is to deliver all email using SMTP via Tor. Such SMTP option would be
1166 a nice addition to the FreedomBox project if we could send email
1167 between FreedomBox machines without leaking metadata about the emails
1168 to the people peeking on the wire. I
1169 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
1170 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
1171 lot of useful feedback and suggestions. It also became obvious to me
1172 that this was not a novel idea, as the same idea was tested and
1173 documented by Johannes Berg as early as 2006, and both
1174 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
1175 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
1176 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
1177
1178 &lt;p&gt;To implement such system one need to set up a Tor hidden service
1179 providing the SMTP protocol on port 25, and use email addresses
1180 looking like username@hidden-service-name.onion. With such addresses
1181 the connections to port 25 on hidden-service-name.onion using Tor will
1182 go to the correct SMTP server. To do this, one need to configure the
1183 Tor daemon to provide the hidden service and the mail server to accept
1184 emails for this .onion domain. To learn more about Exim configuration
1185 in Debian and test the design provided by Johannes Berg in his FAQ, I
1186 set out yesterday to create a Debian package for making it trivial to
1187 set up such SMTP over Tor service based on Debian. Getting it to work
1188 were fairly easy, and
1189 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
1190 source code for the Debian package&lt;/a&gt; is available from github. I
1191 plan to move it into Debian if further testing prove this to be a
1192 useful approach.&lt;/p&gt;
1193
1194 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
1195 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
1196 get rid of exim4). Install tor, clone the git repository mentioned
1197 above, build the deb and install it on the machine. Next, run
1198 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
1199 the instructions to get the service up and running. Restart tor and
1200 exim when it is done, and test mail delivery using swaks like
1201 this:&lt;/p&gt;
1202
1203 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1204 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1205 --to fbx@dutlqrrmjhtfa3vp.onion
1206 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1207
1208 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
1209 address with your own address to test your server. :)&lt;/p&gt;
1210
1211 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
1212 easier and more automatic. Especially the tor setup need more work.
1213 Also, the package include a tor-smtp tool written in C, but its task
1214 should probably be rewritten in some script language to make the deb
1215 architecture independent. It would probably also make the code easier
1216 to review. The tor-smtp tool currently need to listen on a socket for
1217 exim to talk to it and is started using xinetd. It would be better if
1218 no daemon and no socket is needed. I suspect it is possible to get
1219 exim to run a command line tool for delivery instead of talking to a
1220 socket, and hope to figure out how in a future version of this
1221 system.&lt;/p&gt;
1222
1223 &lt;p&gt;Until I wipe my test machine, I can be reached using the
1224 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
1225 SMTorP. :)&lt;/p&gt;
1226 </description>
1227 </item>
1228
1229 <item>
1230 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
1231 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
1232 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
1233 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
1234 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
1235 alioth.debian.org, you know the web interface is fairly slow to
1236 operate. First you visit one web page, enter the moderation password
1237 and get a new page shown with a list of all the messages to moderate
1238 and various options for each email address. This take a while for
1239 every list you moderate, and you need to do it regularly to do a good
1240 job as a list moderator. But there is a quick alternative,
1241 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
1242 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
1243 to moderate in a fraction of a second. Here is a test run on two
1244 lists I recently took over:&lt;/p&gt;
1245
1246 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1247 % time listadmin xiph
1248 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1249 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1250
1251 real 0m1.709s
1252 user 0m0.232s
1253 sys 0m0.012s
1254 %
1255 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1256
1257 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
1258 there are no message in the moderation queue. Every morning I
1259 currently moderate 68 mailman lists, and it normally take around two
1260 minutes. When I took over the two pkg-xiph lists above a few days
1261 ago, there were 400 emails waiting in the moderator queue. It took me
1262 less than 15 minutes to process them all using the listadmin
1263 program.&lt;/p&gt;
1264
1265 &lt;p&gt;If you install
1266 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
1267 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
1268 with content like this, the moderation task is a breeze:&lt;/p&gt;
1269
1270 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1271 username username@example.org
1272 spamlevel 23
1273 default discard
1274 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
1275
1276 password secret
1277 adminurl https://{domain}/mailman/admindb/{list}
1278 mailman-list@lists.example.com
1279
1280 password hidden
1281 other-list@otherserver.example.org
1282 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1283
1284 &lt;p&gt;There are other options to set as well. Check the manual page to
1285 learn the details.&lt;/p&gt;
1286
1287 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
1288 the SSL certificate is self signed or not properly signed by a
1289 generally accepted signing authority, you can set a environment
1290 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
1291
1292 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1293 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
1294 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1295
1296 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
1297 can provide an argument to the listadmin script like I do in the
1298 initial screen dump (the xiph argument). Using an argument, only
1299 lists matching the argument string will be processed. This make it
1300 quick to accept messages if you notice the moderation request in your
1301 email.&lt;/p&gt;
1302
1303 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
1304 mailing lists, as I simply do not have time to spend on that if the
1305 process was any slower. The listadmin program have saved me hours of
1306 time I could spend elsewhere over the years. It truly is nice free
1307 software.&lt;/p&gt;
1308
1309 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1310 activities, please send Bitcoin donations to my address
1311 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1312
1313 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1314 configuration example. Also, I&#39;ve been told that the
1315 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1316 sure why.&lt;/p&gt;
1317 </description>
1318 </item>
1319
1320 <item>
1321 <title>Debian Jessie, PXE and automatic firmware installation</title>
1322 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1323 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1324 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1325 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1326 problem that the WiFi card require some firmware to work properly.
1327 And it has been a pain to fix this using preseeding in Debian.
1328 Normally something more is needed. But thanks to
1329 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1330 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1331 to do this using simple preseeding.&lt;/p&gt;
1332
1333 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1334 firmware for the hardware found in the machine (actually, requested by
1335 the kernel modules for the hardware). (It can also install user space
1336 programs supporting the hardware detected, but that is not the focus
1337 of this story.)&lt;/p&gt;
1338
1339 &lt;p&gt;To get this working in the default installation, two preeseding
1340 values are needed. First, the isenkram-cli package must be installed
1341 into the target chroot (aka the hard drive) before tasksel is executed
1342 in the pkgsel step of the debian-installer system. This is done by
1343 preseeding the base-installer/includes debconf value to include the
1344 isenkram-cli package. The package name is next passed to debootstrap
1345 for installation. With the isenkram-cli package in place, tasksel
1346 will automatically use the isenkram tasks to detect hardware specific
1347 packages for the machine being installed and install them, because
1348 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1349
1350 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1351 most firmware unfortunately is non-free. This is done by preseeding
1352 the apt-mirror-setup step. This is unfortunate, but for a lot of
1353 hardware it is the only option in Debian.&lt;/p&gt;
1354
1355 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1356 firmware installed automatically by the installer:&lt;/p&gt;
1357
1358 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1359 base-installer base-installer/includes string isenkram-cli
1360 apt-mirror-setup apt-setup/non-free boolean true
1361 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1362
1363 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1364 both firmware and user space packages when using this method. It also
1365 do not work well, so use version 0.15 or later. Installing both
1366 firmware and user space packages might give you a bit more than you
1367 want, so I decided to split the tasksel task in two, one for firmware
1368 and one for user space programs. The firmware task is enabled by
1369 default, while the one for user space programs is not. This split is
1370 implemented in the package currently in unstable.&lt;/p&gt;
1371
1372 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1373 this recipe work for you. :)&lt;/p&gt;
1374
1375 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1376 foremost, it work because tasksel is modular, and driven by whatever
1377 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1378 isenkram-cli package place two files for tasksel to find. First there
1379 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1380
1381 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1382 Task: isenkram-packages
1383 Section: hardware
1384 Description: Hardware specific packages (autodetected by isenkram)
1385 Based on the detected hardware various hardware specific packages are
1386 proposed.
1387 Test-new-install: show show
1388 Relevance: 8
1389 Packages: for-current-hardware
1390
1391 Task: isenkram-firmware
1392 Section: hardware
1393 Description: Hardware specific firmware packages (autodetected by isenkram)
1394 Based on the detected hardware various hardware specific firmware
1395 packages are proposed.
1396 Test-new-install: mark show
1397 Relevance: 8
1398 Packages: for-current-hardware-firmware
1399 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1400
1401 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1402 should be handled and the Packages line referencing to a script in
1403 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1404 list of packages to install. The for-current-hardware-firmware script
1405 look like this to list relevant firmware for the machine:
1406
1407 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1408 #!/bin/sh
1409 #
1410 PATH=/usr/sbin:$PATH
1411 export PATH
1412 isenkram-autoinstall-firmware -l
1413 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1414
1415 &lt;p&gt;With those two pieces in place, the firmware is installed by
1416 tasksel during the normal d-i run. :)&lt;/p&gt;
1417
1418 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1419 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1420 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1421 install.&lt;/p&gt;
1422
1423 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1424 pilots in testing this feature, as isenkram is used there now to
1425 install firmware, replacing the earlier scripts.&lt;/p&gt;
1426 </description>
1427 </item>
1428
1429 <item>
1430 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1431 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1432 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1433 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1434 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1435 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1436 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1437 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1438
1439 &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;
1440
1441 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1442 about this hidden Linux installation. It is interesting what
1443 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1444 </description>
1445 </item>
1446
1447 <item>
1448 <title>New lsdvd release version 0.17 is ready</title>
1449 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1451 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1452 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1453 got a new set of developers a few weeks ago, after the original
1454 developer decided to step down and pass the project to fresh blood.
1455 This project is now maintained by Petter Reinholdtsen and Steve
1456 Dibb.&lt;/p&gt;
1457
1458 &lt;p&gt;I just wrapped up
1459 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1460 new lsdvd release&lt;/a&gt;, available in git or from
1461 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1462 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1463 0.17.&lt;/p&gt;
1464
1465 &lt;ul&gt;
1466
1467 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1468 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1469 non-existant, to work around additional copy protection&lt;/li&gt;
1470 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1471 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1472 &lt;li&gt;Fix include orders&lt;/li&gt;
1473 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1474 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1475 &lt;li&gt;Make sure the array size and the array limit used when initialising
1476 the palette size is the same.&lt;/li&gt;
1477 &lt;li&gt;Fix array printing.&lt;/li&gt;
1478 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1479 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1480 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1481 with more GCC compiler warnings.&lt;/li&gt;
1482
1483 &lt;/ul&gt;
1484
1485 &lt;p&gt;This change bring together patches for lsdvd in use in various
1486 Linux and Unix distributions, as well as patches submitted to the
1487 project the last nine years. Please check it out. :)&lt;/p&gt;
1488 </description>
1489 </item>
1490
1491 <item>
1492 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1493 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1494 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1495 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1496 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1497 project&lt;/a&gt; provide a Linux solution for schools, including a
1498 powerful desktop with education software, a central server providing
1499 web pages, user database, user home directories, central login and PXE
1500 boot of both clients without disk and the installation to install Debian
1501 Edu on machines with disk (and a few other services perhaps to small
1502 to mention here). We in the Debian Edu team are currently working on
1503 the Jessie based version, trying to get everything in shape before the
1504 freeze, to avoid having to maintain our own package repository in the
1505 future. The
1506 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1507 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1508 work left. Some fatal problems block testing, breaking the installer,
1509 but it is possible to work around these to get anyway. Here is a
1510 recipe on how to get the installation limping along.&lt;/p&gt;
1511
1512 &lt;p&gt;First, download the test ISO via
1513 &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;,
1514 &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;
1515 or rsync (use
1516 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1517 The ISO build was broken on Tuesday, so we do not get a new ISO every
1518 12 hours or so, but thankfully the ISO we already got we are able to
1519 install with some tweaking.&lt;/p&gt;
1520
1521 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1522 (use Alt-Ctrl-F2), run&lt;/p&gt;
1523
1524 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1525 nano /usr/bin/edu-eatmydata-install
1526 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1527
1528 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1529 optimization. Return to the installation, select the profile you want
1530 and continue. Without this change, exim4-config will fail to install
1531 due to a known bug in eatmydata.&lt;/p&gt;
1532
1533 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1534 this do not work, figure out what your correct value would be. All my
1535 test machines need /dev/sda, so I have no advice if it do not fit
1536 your need.&lt;/p&gt;
1537
1538 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1539 root after the initial boot from hard drive, and install the
1540 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1541 or mate. If you want several desktop options, install more than one
1542 metapackage. Once this is done, reboot and you should have a working
1543 graphical login screen. This workaround should no longer be needed
1544 once the education-tasks package version 1.801 enter testing in two
1545 days.&lt;/p&gt;
1546
1547 &lt;p&gt;I believe the ISO build will start working on two days when the new
1548 tasksel package enter testing and Steve McIntyre get a chance to
1549 update the debian-cd git repository. The eatmydata, grub and desktop
1550 issues are already fixed in unstable and testing, and should show up
1551 on the ISO as soon as the ISO build start working again. Well the
1552 eatmydata optimization is really just disabled. The proper fix
1553 require an upload by the eatmydata maintainer applying the patch
1554 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1555 The rest have proper fixes in unstable.&lt;/p&gt;
1556
1557 &lt;p&gt;I hope this get you going with the installation testing, as we are
1558 quickly running out of time trying to get our Jessie based
1559 installation ready before the distribution freeze in a month.&lt;/p&gt;
1560 </description>
1561 </item>
1562
1563 <item>
1564 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1565 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1566 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1567 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1568 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1569 to handle my fairly large DVD collection. It is a nice command line
1570 tool to get details about a DVD, like title, tracks, track length,
1571 etc, in XML, Perl or human readable format. But lsdvd have not seen
1572 any new development since 2006 and had a few irritating bugs affecting
1573 its use with some DVDs. Upstream seemed to be dead, and in January I
1574 sent a small probe asking for a version control repository for the
1575 project, without any reply. But I use it regularly and would like to
1576 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1577 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1578 the project admin, and after getting a reply from him explaining that
1579 he was no longer interested in the project, I asked if I could take
1580 over. And yesterday, I became project admin.&lt;/p&gt;
1581
1582 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1583 maintainer interested in joining forces to maintain the upstream
1584 project, and I hope we can get a new release out fairly quickly,
1585 collecting the patches spread around on the internet into on place.
1586 I&#39;ve added the relevant Debian patches to the freshly created git
1587 repository, and expect the Gentoo patches to make it too. If you got
1588 a DVD collection and care about command line tools, check out
1589 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1590 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1591 list&lt;/a&gt;. :)&lt;/p&gt;
1592 </description>
1593 </item>
1594
1595 <item>
1596 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1597 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1598 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1599 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1600 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1601 a lot quicker. When we install more than 2000 packages in
1602 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1603 tasksel in the installer, unpacking the binary packages take forever.
1604 A part of the slow I/O issue was discussed in
1605 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1606 much file system sync-ing done by dpkg, which is the package
1607 responsible for unpacking the binary packages. Other parts (like code
1608 executed by postinst scripts) might also sync to disk during
1609 installation. All this sync-ing to disk do not really make sense to
1610 me. If the machine crash half-way through, I start over, I do not try
1611 to salvage the half installed system. So the failure sync-ing is
1612 supposed to protect against, hardware or system crash, is not really
1613 relevant while the installer is running.&lt;/p&gt;
1614
1615 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1616 system sync()-ing in a fairly non-intrusive way, without the need to
1617 change the code in several packages. The idea is not new, but I have
1618 not heard anyone propose the approach using dpkg-divert before. It
1619 depend on the small and clever package
1620 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1621 uses LD_PRELOAD to replace the system functions for syncing data to
1622 disk with functions doing nothing, thus allowing programs to live
1623 dangerous while speeding up disk I/O significantly. Instead of
1624 modifying the implementation of dpkg, apt and tasksel (which are the
1625 packages responsible for selecting, fetching and installing packages),
1626 it occurred to me that we could just divert the programs away, replace
1627 them with a simple shell wrapper calling
1628 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1629 Two days ago I decided to test the idea, and wrapped up a simple
1630 implementation for the Debian Edu udeb.&lt;/p&gt;
1631
1632 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1633 time of the pkgsel step (installing tasks) from 64 to less than 44
1634 minutes (20 minutes shaved off the installation) on an old Dell
1635 Latitude D505 machine. I am not quite sure what the optimised time
1636 would have been, as I messed up the testing a bit, causing the debconf
1637 priority to get low enough for two questions to pop up during
1638 installation. As soon as I saw the questions I moved the installation
1639 along, but do not know how long the question were holding up the
1640 installation. I did some more measurements using Debian Edu Jessie,
1641 and got these results. The time measured is the time stamp in
1642 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1643 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1644 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1645 timing thus do not depend on how quickly the user handle the tasksel
1646 dialog.&lt;/p&gt;
1647
1648 &lt;p&gt;&lt;table&gt;
1649
1650 &lt;tr&gt;
1651 &lt;th&gt;Machine/setup&lt;/th&gt;
1652 &lt;th&gt;Original tasksel&lt;/th&gt;
1653 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1654 &lt;th&gt;Reduction&lt;/th&gt;
1655 &lt;/tr&gt;
1656
1657 &lt;tr&gt;
1658 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1659 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1660 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1661 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1662 &lt;/tr&gt;
1663
1664 &lt;tr&gt;
1665 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1666 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1667 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1668 &lt;td&gt;23 min 40%&lt;/td&gt;
1669 &lt;/tr&gt;
1670
1671 &lt;tr&gt;
1672 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1673 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1674 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1675 &lt;td&gt;11 min 50%&lt;/td&gt;
1676 &lt;/tr&gt;
1677
1678 &lt;tr&gt;
1679 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1680 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1681 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1682 &lt;td&gt;2 min 33%&lt;/td&gt;
1683 &lt;/tr&gt;
1684
1685 &lt;tr&gt;
1686 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1687 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1688 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1689 &lt;td&gt;4 min 21%&lt;/td&gt;
1690 &lt;/tr&gt;
1691
1692 &lt;/table&gt;&lt;/p&gt;
1693
1694 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1695 time is spent downloading packages. The connection to the Internet
1696 was 100Mbit/s during testing, so downloading should not be a
1697 significant factor in the measurement. Download typically took a few
1698 seconds to a few minutes, depending on the amount of packages being
1699 installed.&lt;/p&gt;
1700
1701 &lt;p&gt;The speedup is implemented by using two hooks in
1702 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1703 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1704 finish-install.d hook to remove the divert at the end of the
1705 installation. I picked the pre-pkgsel.d hook instead of the
1706 post-base-installer.d hook because I test using an ISO without the
1707 eatmydata package included, and the post-base-installer.d hook in
1708 Debian Edu can only operate on packages included in the ISO. The
1709 negative effect of this is that I am unable to activate this
1710 optimization for the kernel installation step in d-i. If the code is
1711 moved to the post-base-installer.d hook, the speedup would be larger
1712 for the entire installation.&lt;/p&gt;
1713
1714 &lt;p&gt;I&#39;ve implemented this in the
1715 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1716 git repository, and plan to provide the optimization as part of the
1717 Debian Edu installation. If you want to test this yourself, you can
1718 create two files in the installer (or in an udeb). One shell script
1719 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1720
1721 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1722 #!/bin/sh
1723 set -e
1724 . /usr/share/debconf/confmodule
1725 info() {
1726 logger -t my-pkgsel &quot;info: $*&quot;
1727 }
1728 error() {
1729 logger -t my-pkgsel &quot;error: $*&quot;
1730 }
1731 override_install() {
1732 apt-install eatmydata || true
1733 if [ -x /target/usr/bin/eatmydata ] ; then
1734 for bin in dpkg apt-get aptitude tasksel ; do
1735 file=/usr/bin/$bin
1736 # Test that the file exist and have not been diverted already.
1737 if [ -f /target$file ] ; then
1738 info &quot;diverting $file using eatmydata&quot;
1739 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1740 &gt; /target$file.edu
1741 chmod 755 /target$file.edu
1742 in-target dpkg-divert --package debian-edu-config \
1743 --rename --quiet --add $file
1744 ln -sf ./$bin.edu /target$file
1745 else
1746 error &quot;unable to divert $file, as it is missing.&quot;
1747 fi
1748 done
1749 else
1750 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1751 fi
1752 }
1753
1754 override_install
1755 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1756
1757 &lt;p&gt;To clean up, another shell script should go into
1758 /usr/lib/finish-install.d/ with code like this:
1759
1760 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1761 #! /bin/sh -e
1762 . /usr/share/debconf/confmodule
1763 error() {
1764 logger -t my-finish-install &quot;error: $@&quot;
1765 }
1766 remove_install_override() {
1767 for bin in dpkg apt-get aptitude tasksel ; do
1768 file=/usr/bin/$bin
1769 if [ -x /target$file.edu ] ; then
1770 rm /target$file
1771 in-target dpkg-divert --package debian-edu-config \
1772 --rename --quiet --remove $file
1773 rm /target$file.edu
1774 else
1775 error &quot;Missing divert for $file.&quot;
1776 fi
1777 done
1778 sync # Flush file buffers before continuing
1779 }
1780
1781 remove_install_override
1782 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1783
1784 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1785 edu-eatmydata-install and call it from the pre-pkgsel.d and
1786 finish-install.d scripts.&lt;/p&gt;
1787
1788 &lt;p&gt;By now you might ask if this change should get into the normal
1789 Debian installer too? I suspect it should, but am not sure the
1790 current debian-installer coordinators find it useful enough. It also
1791 depend on the side effects of the change. I&#39;m not aware of any, but I
1792 guess we will see if the change is safe after some more testing.
1793 Perhaps there is some package in Debian depending on sync() and
1794 fsync() having effect? Perhaps it should go into its own udeb, to
1795 allow those of us wanting to enable it to do so without affecting
1796 everyone.&lt;/p&gt;
1797
1798 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1799 will break installation of all programs using gnutls because of
1800 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1801 eatmydata package in Debian will solve it.&lt;/p&gt;
1802
1803 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1804 the optimization work again. And I have discovered that the
1805 dpkg-divert trick is not really needed and implemented a slightly
1806 simpler approach as part of the debian-edu-install package. See
1807 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1808
1809 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1810 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1811 triggering on i386 made it into testing, and broke this installation
1812 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1813 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1814 </description>
1815 </item>
1816
1817 <item>
1818 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1819 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1820 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1821 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1822 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1823 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1824 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1825 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1826 learn that there is a large set of publicly available key servers to
1827 use when looking for peoples public key. So far I have used
1828 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1829 were misbehaving, but those days are ended. The servers I have used
1830 up until yesterday have been slow and some times unavailable. I hope
1831 those problems are gone now.&lt;/p&gt;
1832
1833 &lt;p&gt;Behind the round robin DNS entry of the
1834 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1835 there is a pool of more than 100 keyservers which are checked every
1836 day to ensure they are well connected and up to date. It must be
1837 better than what I have used so far. :)&lt;/p&gt;
1838
1839 &lt;p&gt;Yesterdays speaker told me that the service is the default
1840 keyserver provided by the default configuration in GnuPG, but this do
1841 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1842
1843 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1844 line:&lt;/p&gt;
1845
1846 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1847 keyserver pool.sks-keyservers.net
1848 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1849
1850 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1851 entries in DNS. Just for fun, I did just that at work, so now every
1852 user of GnuPG at the University of Oslo should find a OpenGPG
1853 keyserver automatically should their need it:&lt;/p&gt;
1854
1855 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1856 % host -t srv _pgpkey-http._tcp.uio.no
1857 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1858 %
1859 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1860
1861 &lt;p&gt;Now if only
1862 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1863 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1864 very happy. It can look up a given key or search for a user ID, but I
1865 normally do not want that, but to find a trust path from my key to
1866 another key. Given a user ID or key ID, I would like to find (and
1867 download) the keys representing a signature path from my key to the
1868 key in question, to be able to get a trust path between the two keys.
1869 This is as far as I can tell not possible today. Perhaps something
1870 for a future version of the protocol?&lt;/p&gt;
1871 </description>
1872 </item>
1873
1874 <item>
1875 <title>From English wiki to translated PDF and epub via Docbook</title>
1876 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1877 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1878 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1879 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1880 project&lt;/a&gt; provide an instruction manual for teachers, system
1881 administrators and other users that contain useful tips for setting up
1882 and maintaining a Debian Edu installation. This text is about how the
1883 text processing of this manual is handled in the project.&lt;/p&gt;
1884
1885 &lt;p&gt;One goal of the project is to provide information in the native
1886 language of its users, and for this we need to handle translations.
1887 But we also want to make sure each language contain the same
1888 information, so for this we need a good way to keep the translations
1889 in sync. And we want it to be easy for our users to improve the
1890 documentation, avoiding the need to learn special formats or tools to
1891 contribute, and the obvious way to do this is to make it possible to
1892 edit the documentation using a web browser. We also want it to be
1893 easy for translators to keep the translation up to date, and give them
1894 help in figuring out what need to be translated. Here is the list of
1895 tools and the process we have found trying to reach all these
1896 goals.&lt;/p&gt;
1897
1898 &lt;p&gt;We maintain the authoritative source of our manual in the
1899 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1900 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1901 front page with references to the different chapters, several pages
1902 for each chapter, and finally one &quot;collection page&quot; gluing all the
1903 chapters together into one large web page (aka
1904 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1905 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1906 processing and translations. Thanks to the fact that the
1907 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1908 wiki.debian.org support exporting pages in
1909 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1910 the list of pages to export using the raw version of the AllInOne
1911 page, loop over each of them to generate a Docbook XML version of the
1912 manual. This process also download images and transform image
1913 references to use the locally downloaded images. The generated
1914 Docbook XML files are slightly broken, so some post-processing is done
1915 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1916 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1917 a handfull of images. The XML file can now be used to generate PDF, HTML
1918 and epub versions of the English manual. This is the basic step of
1919 our process, making PDF (using dblatex), HTML (using xsltproc) and
1920 epub (using dbtoepub) version from Docbook XML, and the resulting files
1921 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1922
1923 &lt;p&gt;But English documentation is not enough for us. We want translated
1924 documentation too, and we want to make it easy for translators to
1925 track the English original. For this we use the
1926 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1927 which allow us to transform the English Docbook XML file into a
1928 translation file (a .pot file), usable with the normal gettext based
1929 translation tools used by those translating free software. The pot
1930 file is used to create and maintain translation files (several .po
1931 files), which the translations update with the native language
1932 translations of all titles, paragraphs and blocks of text in the
1933 original. The next step is combining the original English Docbook XML
1934 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1935 create a translated Docbook XML file (in this case
1936 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1937 translated, if the translation is not complete) Docbook XML file can
1938 then be used like the original to create a PDF, HTML and epub version
1939 of the documentation.&lt;/p&gt;
1940
1941 &lt;p&gt;The translators use different tools to edit the .po files. We
1942 recommend using
1943 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1944 while some use emacs and vi, others can use web based editors like
1945 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1946 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1947 is where the .po file end up, in our git repository. Updated
1948 translations can either be committed directly to git, or submitted as
1949 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1950 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1951
1952 &lt;p&gt;One challenge is images, which both might need to be translated (if
1953 they show translated user applications), and are needed in different
1954 formats when creating PDF and HTML versions (epub is a HTML version in
1955 this regard). For this we transform the original PNG images to the
1956 needed density and format during build, and have a way to provide
1957 translated images by storing translated versions in
1958 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1959 package maintainers know more.&lt;/p&gt;
1960
1961 &lt;p&gt;If you wonder what the result look like, we provide
1962 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1963 of the documentation packages on the web&lt;/a&gt;. See for example the
1964 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1965 PDF version&lt;/a&gt; or the
1966 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1967 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1968 but perhaps it will be done in the future.&lt;/p&gt;
1969
1970 &lt;p&gt;To learn more, check out
1971 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1972 debian-edu-doc package&lt;/a&gt;,
1973 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1974 manual on the wiki&lt;/a&gt; and
1975 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1976 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1977 </description>
1978 </item>
1979
1980 <item>
1981 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1982 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1983 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1984 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1985 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1986 related packages relevant for the computer installed automatically.
1987 So I implemented one, using
1988 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1989 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1990 run tasksel as user root. You should be presented with a new option,
1991 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1992 select it, tasksel will install the packages isenkram claim is fit for
1993 the current hardware, hot pluggable or not.&lt;p&gt;
1994
1995 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1996 description, and the other is the script used to extract the list of
1997 packages to install. The first part is in
1998 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1999 this:&lt;/p&gt;
2000
2001 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2002 Task: isenkram
2003 Section: hardware
2004 Description: Hardware specific packages (autodetected by isenkram)
2005 Based on the detected hardware various hardware specific packages are
2006 proposed.
2007 Test-new-install: mark show
2008 Relevance: 8
2009 Packages: for-current-hardware
2010 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2011
2012 &lt;p&gt;The second part is in
2013 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
2014 this:&lt;/p&gt;
2015
2016 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2017 #!/bin/sh
2018 #
2019 (
2020 isenkram-lookup
2021 isenkram-autoinstall-firmware -l
2022 ) | sort -u
2023 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2024
2025 &lt;p&gt;All in all, a very short and simple implementation making it
2026 trivial to install the hardware dependent package we all may want to
2027 have installed on our machines. I&#39;ve not been able to find a way to
2028 get tasksel to tell you exactly which packages it plan to install
2029 before doing the installation. So if you are curious or careful,
2030 check the output from the isenkram-* command line tools first.&lt;/p&gt;
2031
2032 &lt;p&gt;The information about which packages are handling which hardware is
2033 fetched either from the isenkram package itself in
2034 /usr/share/isenkram/, from git.debian.org or from the APT package
2035 database (using the Modaliases header). The APT package database
2036 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2037 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
2038 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
2039 the python-apt code (bug
2040 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
2041 workaround I was able to get rid of the file descriptor leak and
2042 reduce the memory leak from ~30 MiB per hardware detection down to
2043 around 2 MiB per hardware detection. It should make the desktop
2044 daemon a lot more useful. The fix is in version 0.7 uploaded to
2045 unstable today.&lt;/p&gt;
2046
2047 &lt;p&gt;I believe the current way of mapping hardware to packages in
2048 Isenkram is is a good draft, but in the future I expect isenkram to
2049 use the AppStream data source for this. A proposal for getting proper
2050 AppStream support into Debian is floating around as
2051 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
2052 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
2053 project&lt;/a&gt; will take place this summer to improve the situation. I
2054 look forward to seeing the result, and welcome patches for isenkram to
2055 start using the information when it is ready.&lt;/p&gt;
2056
2057 &lt;p&gt;If you want your package to map to some specific hardware, either
2058 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
2059 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
2060 package&lt;/a&gt; or submit a bug report with the details to the isenkram
2061 package. See also
2062 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
2063 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
2064 the information will be migrated to AppStream eventually, but for the
2065 moment I got no better place to store it.&lt;/p&gt;
2066 </description>
2067 </item>
2068
2069 <item>
2070 <title>FreedomBox milestone - all packages now in Debian Sid</title>
2071 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
2072 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
2073 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
2074 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2075 project&lt;/a&gt; is working on providing the software and hardware to make
2076 it easy for non-technical people to host their data and communication
2077 at home, and being able to communicate with their friends and family
2078 encrypted and away from prying eyes. It is still going strong, and
2079 today a major mile stone was reached.&lt;/p&gt;
2080
2081 &lt;p&gt;Today, the last of the packages currently used by the project to
2082 created the system images were accepted into Debian Unstable. It was
2083 the freedombox-setup package, which is used to configure the images
2084 during build and on the first boot. Now all one need to get going is
2085 the build code from the freedom-maker git repository and packages from
2086 Debian. And once the freedombox-setup package enter testing, we can
2087 build everything directly from Debian. :)&lt;/p&gt;
2088
2089 &lt;p&gt;Some key packages used by Freedombox are
2090 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
2091 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
2092 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
2093 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
2094 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
2095 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
2096 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
2097 are plans to integrate more packages into the setup. User
2098 documentation is maintained on the Debian wiki. Please
2099 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
2100 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
2101
2102 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
2103 setup, run this on a Debian machine using a user with sudo rights to
2104 become root:&lt;/p&gt;
2105
2106 &lt;p&gt;&lt;pre&gt;
2107 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2108 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2109 u-boot-tools
2110 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2111 freedom-maker
2112 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2113 &lt;/pre&gt;&lt;/p&gt;
2114
2115 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2116 devices. See the README in the freedom-maker git repo for more
2117 details on the build. If you do not want all three images, trim the
2118 make line. Note that the virtualbox-image target is not really
2119 virtualbox specific. It create a x86 image usable in kvm, qemu,
2120 vmware and any other x86 virtual machine environment. You might need
2121 the version of vmdebootstrap in Jessie to get the build working, as it
2122 include fixes for a race condition with kpartx.&lt;/p&gt;
2123
2124 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2125 method, boot a Debian Wheezy ISO and use this boot argument to load
2126 the preseed values:&lt;/p&gt;
2127
2128 &lt;p&gt;&lt;pre&gt;
2129 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;
2130 &lt;/pre&gt;&lt;/p&gt;
2131
2132 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
2133 it still work.&lt;/p&gt;
2134
2135 &lt;p&gt;If you wonder how to help, one task you could look at is using
2136 systemd as the boot system. It will become the default for Linux in
2137 Jessie, so we need to make sure it is usable on the Freedombox. I did
2138 a simple test a few weeks ago, and noticed dnsmasq failed to start
2139 during boot when using systemd. I suspect there are other problems
2140 too. :) To detect problems, there is a test suite included, which can
2141 be run from the plinth web interface.&lt;/p&gt;
2142
2143 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2144 us get the new release published. :) Please join us on
2145 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2146 irc.debian.org)&lt;/a&gt; and
2147 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2148 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2149 </description>
2150 </item>
2151
2152 <item>
2153 <title>S3QL, a locally mounted cloud file system - nice free software</title>
2154 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
2155 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
2156 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
2157 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
2158 solution for use at home. My requirements are simple, it must be
2159 cheap and locally encrypted (in other words, I keep the encryption
2160 keys, the storage provider do not have access to my private files).
2161 One idea me and my friends had many years ago, before the cloud
2162 storage providers showed up, was to use Google mail as storage,
2163 writing a Linux block device storing blocks as emails in the mail
2164 service provided by Google, and thus get heaps of free space. On top
2165 of this one can add encryption, RAID and volume management to have
2166 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2167 I never found time to implement such system. But the last few weeks I
2168 have looked at a system called
2169 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
2170 mounted network backed file system with the features I need.&lt;/p&gt;
2171
2172 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
2173 handling several different storage providers, any with Amazon S3,
2174 Google Drive or OpenStack API. There are heaps of such storage
2175 providers. S3QL can also use a local directory as storage, which
2176 combined with sshfs allow for file storage on any ssh server. S3QL
2177 include support for encryption, compression, de-duplication, snapshots
2178 and immutable file systems, allowing me to mount the remote storage as
2179 a local mount point, look at and use the files as if they were local,
2180 while the content is stored in the cloud as well. This allow me to
2181 have a backup that should survive fire. The file system can not be
2182 shared between several machines at the same time, as only one can
2183 mount it at the time, but any machine with the encryption key and
2184 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
2185
2186 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
2187 package is included already. So to get started, run &lt;tt&gt;apt-get
2188 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
2189 Greenqloud, after reading their nice recipe on
2190 &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
2191 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
2192 in Iceland more than those in USA when it come to keeping my personal
2193 data safe and private, and thus would rather spend money on a company
2194 in Iceland. Another nice recipe is available from the article
2195 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
2196 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
2197 Admin magazine. When the provider is picked, figure out how to get
2198 the API key needed to connect to the storage API. With Greencloud,
2199 the key did not show up until I had added payment details to my
2200 account.&lt;/p&gt;
2201
2202 &lt;p&gt;Armed with the API access details, it is time to create the file
2203 system. First, create a new bucket in the cloud. This bucket is the
2204 file system storage area. I picked a bucket name reflecting the
2205 machine that was going to store data there, but any name will do.
2206 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
2207 the API login and password, and a locally created password. Store it
2208 all in ~root/.s3ql/authinfo2 like this:
2209
2210 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2211 [s3c]
2212 storage-url: s3c://s.greenqloud.com:443/bucket-name
2213 backend-login: API-login
2214 backend-password: API-password
2215 fs-passphrase: local-password
2216 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2217
2218 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
2219 but any sensible way to create a fairly random password should do it.
2220 Armed with these details, it is now time to run mkfs, entering the API
2221 details and password to create it:&lt;/p&gt;
2222
2223 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2224 # mkdir -m 700 /var/lib/s3ql-cache
2225 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2226 --ssl s3c://s.greenqloud.com:443/bucket-name
2227 Enter backend login:
2228 Enter backend password:
2229 Before using S3QL, make sure to read the user&#39;s guide, especially
2230 the &#39;Important Rules to Avoid Loosing Data&#39; section.
2231 Enter encryption password:
2232 Confirm encryption password:
2233 Generating random encryption key...
2234 Creating metadata tables...
2235 Dumping metadata...
2236 ..objects..
2237 ..blocks..
2238 ..inodes..
2239 ..inode_blocks..
2240 ..symlink_targets..
2241 ..names..
2242 ..contents..
2243 ..ext_attributes..
2244 Compressing and uploading metadata...
2245 Wrote 0.00 MB of compressed metadata.
2246 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2247
2248 &lt;p&gt;The next step is mounting the file system to make the storage available.
2249
2250 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2251 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2252 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2253 Using 4 upload threads.
2254 Downloading and decompressing metadata...
2255 Reading metadata...
2256 ..objects..
2257 ..blocks..
2258 ..inodes..
2259 ..inode_blocks..
2260 ..symlink_targets..
2261 ..names..
2262 ..contents..
2263 ..ext_attributes..
2264 Mounting filesystem...
2265 # df -h /s3ql
2266 Filesystem Size Used Avail Use% Mounted on
2267 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
2268 #
2269 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2270
2271 &lt;p&gt;The file system is now ready for use. I use rsync to store my
2272 backups in it, and as the metadata used by rsync is downloaded at
2273 mount time, no network traffic (and storage cost) is triggered by
2274 running rsync. To unmount, one should not use the normal umount
2275 command, as this will not flush the cache to the cloud storage, but
2276 instead running the umount.s3ql command like this:
2277
2278 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2279 # umount.s3ql /s3ql
2280 #
2281 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2282
2283 &lt;p&gt;There is a fsck command available to check the file system and
2284 correct any problems detected. This can be used if the local server
2285 crashes while the file system is mounted, to reset the &quot;already
2286 mounted&quot; flag. This is what it look like when processing a working
2287 file system:&lt;/p&gt;
2288
2289 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2290 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
2291 Using cached metadata.
2292 File system seems clean, checking anyway.
2293 Checking DB integrity...
2294 Creating temporary extra indices...
2295 Checking lost+found...
2296 Checking cached objects...
2297 Checking names (refcounts)...
2298 Checking contents (names)...
2299 Checking contents (inodes)...
2300 Checking contents (parent inodes)...
2301 Checking objects (reference counts)...
2302 Checking objects (backend)...
2303 ..processed 5000 objects so far..
2304 ..processed 10000 objects so far..
2305 ..processed 15000 objects so far..
2306 Checking objects (sizes)...
2307 Checking blocks (referenced objects)...
2308 Checking blocks (refcounts)...
2309 Checking inode-block mapping (blocks)...
2310 Checking inode-block mapping (inodes)...
2311 Checking inodes (refcounts)...
2312 Checking inodes (sizes)...
2313 Checking extended attributes (names)...
2314 Checking extended attributes (inodes)...
2315 Checking symlinks (inodes)...
2316 Checking directory reachability...
2317 Checking unix conventions...
2318 Checking referential integrity...
2319 Dropping temporary indices...
2320 Backing up old metadata...
2321 Dumping metadata...
2322 ..objects..
2323 ..blocks..
2324 ..inodes..
2325 ..inode_blocks..
2326 ..symlink_targets..
2327 ..names..
2328 ..contents..
2329 ..ext_attributes..
2330 Compressing and uploading metadata...
2331 Wrote 0.89 MB of compressed metadata.
2332 #
2333 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2334
2335 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2336 quick, about the same speed as local file access. Uploading large
2337 amount of data is to me limited by the bandwidth out of and into my
2338 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2339 which is very close to my upload speed, and downloading the same
2340 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2341 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2342 network, not the file system code. I do not know what a good cache
2343 size would be, but suspect that the cache should e larger than your
2344 working set.&lt;/p&gt;
2345
2346 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2347 time. If another machine try, it is told that the file system is
2348 busy:&lt;/p&gt;
2349
2350 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2351 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2352 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2353 Using 8 upload threads.
2354 Backend reports that fs is still mounted elsewhere, aborting.
2355 #
2356 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2357
2358 &lt;p&gt;The file content is uploaded when the cache is full, while the
2359 metadata is uploaded once every 24 hour by default. To ensure the
2360 file system content is flushed to the cloud, one can either umount the
2361 file system, or ask S3QL to flush the cache and metadata using
2362 s3qlctrl:
2363
2364 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2365 # s3qlctrl upload-meta /s3ql
2366 # s3qlctrl flushcache /s3ql
2367 #
2368 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2369
2370 &lt;p&gt;If you are curious about how much space your data uses in the
2371 cloud, and how much compression and deduplication cut down on the
2372 storage usage, you can use s3qlstat on the mounted file system to get
2373 a report:&lt;/p&gt;
2374
2375 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2376 # s3qlstat /s3ql
2377 Directory entries: 9141
2378 Inodes: 9143
2379 Data blocks: 8851
2380 Total data size: 22049.38 MB
2381 After de-duplication: 21955.46 MB (99.57% of total)
2382 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2383 Database size: 2.39 MB (uncompressed)
2384 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2385 #
2386 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2387
2388 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2389 storage. I did not try to locate them all, but am aware of at least
2390 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2391 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2392 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2393 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2394 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2395 accept payment in Bitcoin. Pick one that suit your need. Some of
2396 them provide several GiB of free storage, but the prize models are
2397 quite different and you will have to figure out what suits you
2398 best.&lt;/p&gt;
2399
2400 &lt;p&gt;While researching this blog post, I had a look at research papers
2401 and posters discussing the S3QL file system. There are several, which
2402 told me that the file system is getting a critical check by the
2403 science community and increased my confidence in using it. One nice
2404 poster is titled
2405 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2406 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2407 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2408 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2409 and Pamela Smith. Please have a look.&lt;/p&gt;
2410
2411 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2412 check out the mounted S3QL file system to see if it would be usable as
2413 a home directory (in other word, that it provided POSIX semantics when
2414 it come to locking and umask handling etc). Running
2415 &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
2416 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2417 no error was found. So the file system can be used for home
2418 directories, if one chooses to do so.&lt;/p&gt;
2419
2420 &lt;p&gt;If you do not want a locally file system, and want something that
2421 work without the Linux fuse file system, I would like to mention the
2422 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2423 provide locally encrypted backup using a command line client. It have
2424 a nicer access control system, where one can split out read and write
2425 access, allowing some systems to write to the backup and others to
2426 only read from it.&lt;/p&gt;
2427
2428 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2429 activities, please send Bitcoin donations to my address
2430 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2431 </description>
2432 </item>
2433
2434 <item>
2435 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2436 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2437 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2438 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2439 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2440 project&lt;/a&gt; is working on providing the software and hardware for
2441 making it easy for non-technical people to host their data and
2442 communication at home, and being able to communicate with their
2443 friends and family encrypted and away from prying eyes. It has been
2444 going on for a while, and is slowly progressing towards a new test
2445 release (0.2).&lt;/p&gt;
2446
2447 &lt;p&gt;And what day could be better than the Pi day to announce that the
2448 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2449 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2450 system), and can also be installed using a Debian installer preseed
2451 file. The Debian based Freedombox is now based on Debian Jessie,
2452 where most of the needed packages used are already present. Only one,
2453 the freedombox-setup package, is missing. To try to build your own
2454 boot image to test the current status, fetch the freedom-maker scripts
2455 and build using
2456 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2457 with a user with sudo access to become root:
2458
2459 &lt;pre&gt;
2460 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2461 freedom-maker
2462 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2463 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2464 u-boot-tools
2465 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2466 &lt;/pre&gt;
2467
2468 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2469 devices. See the README for more details on the build. If you do not
2470 want all three images, trim the make line. But note that thanks to &lt;a
2471 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2472 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2473 kpartx call.&lt;/p&gt;
2474
2475 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2476 method, boot a Debian Wheezy ISO and use this boot argument to load
2477 the preseed values:&lt;/p&gt;
2478
2479 &lt;pre&gt;
2480 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;
2481 &lt;/pre&gt;
2482
2483 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2484 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2485 currently hang while setting up APT sources. Killing the
2486 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2487 installation will get the installation going. This affect all
2488 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2489
2490 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2491 us get the new release published. :) Please join us on
2492 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2493 irc.debian.org)&lt;/a&gt; and
2494 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2495 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2496 </description>
2497 </item>
2498
2499 <item>
2500 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2501 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2502 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2503 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2504 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2505 innetgr tools, because I needed them in
2506 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2507 ng-utils, and it has served me well. I placed the project under the
2508 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2509 repository. But many years ago, the CVS repository was dropped (lost,
2510 not migrated to new hardware, not sure), and the project have lacked a
2511 proper home since then.&lt;/p&gt;
2512
2513 &lt;p&gt;Last summer, I had a look at the package and made a new release
2514 fixing a irritating crash bug, but was unable to store the changes in
2515 a proper source control system. I applied for a project on
2516 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2517 to follow up on it. Until today. :)&lt;/p&gt;
2518
2519 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2520 now have a new home, and a git repository with the highlight of the
2521 history of the project. I published all release tarballs and imported
2522 them into the git repository. As the project is really stable and not
2523 expected to gain new features any time soon, I decided to make a new
2524 release and call it 1.0. Visit the new project home on
2525 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2526 if you want to check it out. The new version is also uploaded into
2527 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2528 </description>
2529 </item>
2530
2531 <item>
2532 <title>Testing sysvinit from experimental in Debian Hurd</title>
2533 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2534 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2535 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2536 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2537 their changes into sysvinit, to allow them to use the normal sysvinit
2538 boot system instead of their old one. This follow up on the
2539 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2540 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2541 get Debian on Hurd working more like Debian on Linux. To get started,
2542 I downloaded a prebuilt hard disk image from
2543 &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;,
2544 and started it using virt-manager.&lt;/p&gt;
2545
2546 &lt;p&gt;The first think I had to do after logging in (root without any
2547 password) was to get the network operational. I followed
2548 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2549 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2550 commands as root to get the machine to accept a IP address from the
2551 kvm internal DHCP server:&lt;/p&gt;
2552
2553 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2554 settrans -fgap /dev/netdde /hurd/netdde
2555 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2556 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2557 dhclient /dev/eth0
2558 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2559
2560 &lt;p&gt;After this, the machine had internet connectivity, and I could
2561 upgrade it and install the sysvinit packages from experimental and
2562 enable it as the default boot system in Hurd.&lt;/p&gt;
2563
2564 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2565 running on the machine it for ssh login to work a password need to be
2566 set. Also, note that a bug somewhere in openssh on Hurd block
2567 compression from working. Remember to turn that off on the client
2568 side.&lt;/p&gt;
2569
2570 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2571 stuff:&lt;/p&gt;
2572
2573 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2574 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2575 deb http://http.debian.net/debian/ experimental main
2576 EOF
2577 apt-get update
2578 apt-get dist-upgrade
2579 apt-get install -t experimental initscripts sysv-rc sysvinit \
2580 sysvinit-core sysvinit-utils
2581 update-alternatives --config runsystem
2582 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2583
2584 &lt;p&gt;To reboot after switching boot system, you have to use
2585 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2586 yet a sysvinit process able to receive the signals from the normal
2587 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2588 upgrading every package and rebooting, the network come up with DHCP
2589 after boot as it should, and the settrans/pkill hack mentioned at the
2590 start is no longer needed. But for some strange reason, there are no
2591 longer any login prompt in the virtual console, so I logged in using
2592 ssh instead.
2593
2594 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2595 fail some times. No idea what the cause is, but hope the Hurd porters
2596 figure it out. At least Justus said on IRC (#debian-hurd on
2597 irc.debian.org) that they are aware of the problem. A way to reduce
2598 the impact is to upgrade to the Hurd packages built by Justus by
2599 adding this repository to the machine:&lt;/p&gt;
2600
2601 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2602 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2603 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2604 EOF
2605 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2606
2607 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2608 http://ftp.debian-ports.org/debian, because some of the packages in
2609 unstable do not yet include the required patches that are lingering in
2610 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2611
2612 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2613 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2614 i emacs - GNU Emacs editor (metapackage)
2615 i gdb - GNU Debugger
2616 i hurd-recommended - Miscellaneous translators
2617 i isc-dhcp-client - ISC DHCP client
2618 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2619 i libc-bin - Embedded GNU C Library: Binaries
2620 i libc-dev-bin - Embedded GNU C Library: Development binaries
2621 i libc0.3 - Embedded GNU C Library: Shared libraries
2622 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2623 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2624 i multiarch-support - Transitional package to ensure multiarch compatibilit
2625 i A x11-common - X Window System (X.Org) infrastructure
2626 i xorg - X.Org X Window System
2627 i A xserver-xorg - X.Org X server
2628 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2629 #
2630 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2631
2632 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2633 X.org did not work out of the box and I never took the time to follow
2634 the porters instructions to fix it. This time I was interested in the
2635 command line stuff.&lt;p&gt;
2636 </description>
2637 </item>
2638
2639 <item>
2640 <title>New chrpath release 0.16</title>
2641 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2642 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2643 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2644 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2645 find problems in C, C++ and Java code using static source code
2646 analysis. It can detect a lot of different problems, and is very
2647 useful to find memory and locking bugs in the error handling part of
2648 the source. The company behind it provide
2649 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2650 a community service&lt;/a&gt;, and many hundred free software projects are
2651 already checked. A few days ago I decided to have a closer look at
2652 the Coverity system, and discovered that the
2653 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2654 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2655 projects I am involved with was already registered. But these are
2656 fairly big, and I would also like to have a small and easy project to
2657 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2658 checking of the chrpath project&lt;/a&gt;. It was
2659 added to the checker and discovered seven potential defects. Six of
2660 these were real, mostly resource &quot;leak&quot; when the program detected an
2661 error. Nothing serious, as the resources would be released a fraction
2662 of a second later when the program exited because of the error, but it
2663 is nice to do it right in case the source of the program some time in
2664 the future end up in a library. Having fixed all defects and added
2665 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2666 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2667 publish a new release. These are the release notes:&lt;/p&gt;
2668
2669 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2670
2671 &lt;ul&gt;
2672
2673 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2674 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2675 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2676
2677 &lt;/ul&gt;
2678
2679 &lt;p&gt;You can
2680 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2681 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2682 project if something is wrong with the new release. The test suite
2683 did not discover any old errors, so if you find a new one, please also
2684 include a test suite check.&lt;/p&gt;
2685 </description>
2686 </item>
2687
2688 <item>
2689 <title>New chrpath release 0.15</title>
2690 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2691 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2692 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2693 <description>&lt;p&gt;After many years break from the package and a vain hope that
2694 development would be continued by someone else, I finally pulled my
2695 acts together this morning and wrapped up a new release of chrpath,
2696 the command line tool to modify the rpath and runpath of already
2697 compiled ELF programs. The update was triggered by the persistence of
2698 Isha Vishnoi at IBM, which needed a new config.guess file to get
2699 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2700 is working on. I checked the
2701 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2702 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2703 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2704 packages for interesting patches (failed to find the source from
2705 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2706 These are the release notes:&lt;/p&gt;
2707
2708 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2709
2710 &lt;ul&gt;
2711
2712 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2713 with newer architectures. Thanks to isha vishnoi for the heads
2714 up.&lt;/li&gt;
2715
2716 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2717
2718 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2719 Matthias Klose.&lt;/li&gt;
2720
2721 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2722 Petr Machata found in Fedora.&lt;/li&gt;
2723
2724 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2725 .dynamic is a NULL terminated string. Based on patch found in
2726 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2727
2728 &lt;/ul&gt;
2729
2730 &lt;p&gt;You can
2731 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2732 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2733 project if something is wrong with the new release. The test suite
2734 did not discover any old errors, so if you find a new one, please also
2735 include a testsuite check.&lt;/p&gt;
2736 </description>
2737 </item>
2738
2739 <item>
2740 <title>Debian init.d boot script example for rsyslog</title>
2741 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2742 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2743 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2744 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2745 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2746 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2747 init.d scripts at all. Here is an example init.d script, ie a rewrite
2748 of /etc/init.d/rsyslog:&lt;/p&gt;
2749
2750 &lt;p&gt;&lt;pre&gt;
2751 #!/lib/init/init-d-script
2752 ### BEGIN INIT INFO
2753 # Provides: rsyslog
2754 # Required-Start: $remote_fs $time
2755 # Required-Stop: umountnfs $time
2756 # X-Stop-After: sendsigs
2757 # Default-Start: 2 3 4 5
2758 # Default-Stop: 0 1 6
2759 # Short-Description: enhanced syslogd
2760 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2761 # It is quite compatible to stock sysklogd and can be
2762 # used as a drop-in replacement.
2763 ### END INIT INFO
2764 DESC=&quot;enhanced syslogd&quot;
2765 DAEMON=/usr/sbin/rsyslogd
2766 &lt;/pre&gt;&lt;/p&gt;
2767
2768 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2769 script was 137 lines, and the above is just 15 lines, most of it meta
2770 info/comments.&lt;/p&gt;
2771
2772 &lt;p&gt;How to do this, you ask? Well, one create a new script
2773 /lib/init/init-d-script looking something like this:
2774
2775 &lt;p&gt;&lt;pre&gt;
2776 #!/bin/sh
2777
2778 # Define LSB log_* functions.
2779 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2780 # and status_of_proc is working.
2781 . /lib/lsb/init-functions
2782
2783 #
2784 # Function that starts the daemon/service
2785
2786 #
2787 do_start()
2788 {
2789 # Return
2790 # 0 if daemon has been started
2791 # 1 if daemon was already running
2792 # 2 if daemon could not be started
2793 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2794 || return 1
2795 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2796 $DAEMON_ARGS \
2797 || return 2
2798 # Add code here, if necessary, that waits for the process to be ready
2799 # to handle requests from services started subsequently which depend
2800 # on this one. As a last resort, sleep for some time.
2801 }
2802
2803 #
2804 # Function that stops the daemon/service
2805 #
2806 do_stop()
2807 {
2808 # Return
2809 # 0 if daemon has been stopped
2810 # 1 if daemon was already stopped
2811 # 2 if daemon could not be stopped
2812 # other if a failure occurred
2813 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2814 RETVAL=&quot;$?&quot;
2815 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2816 # Wait for children to finish too if this is a daemon that forks
2817 # and if the daemon is only ever run from this initscript.
2818 # If the above conditions are not satisfied then add some other code
2819 # that waits for the process to drop all resources that could be
2820 # needed by services started subsequently. A last resort is to
2821 # sleep for some time.
2822 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2823 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2824 # Many daemons don&#39;t delete their pidfiles when they exit.
2825 rm -f $PIDFILE
2826 return &quot;$RETVAL&quot;
2827 }
2828
2829 #
2830 # Function that sends a SIGHUP to the daemon/service
2831 #
2832 do_reload() {
2833 #
2834 # If the daemon can reload its configuration without
2835 # restarting (for example, when it is sent a SIGHUP),
2836 # then implement that here.
2837 #
2838 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2839 return 0
2840 }
2841
2842 SCRIPTNAME=$1
2843 scriptbasename=&quot;$(basename $1)&quot;
2844 echo &quot;SN: $scriptbasename&quot;
2845 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2846 script=&quot;$1&quot;
2847 shift
2848 . $script
2849 else
2850 exit 0
2851 fi
2852
2853 NAME=$(basename $DAEMON)
2854 PIDFILE=/var/run/$NAME.pid
2855
2856 # Exit if the package is not installed
2857 #[ -x &quot;$DAEMON&quot; ] || exit 0
2858
2859 # Read configuration variable file if it is present
2860 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2861
2862 # Load the VERBOSE setting and other rcS variables
2863 . /lib/init/vars.sh
2864
2865 case &quot;$1&quot; in
2866 start)
2867 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2868 do_start
2869 case &quot;$?&quot; in
2870 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2871 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2872 esac
2873 ;;
2874 stop)
2875 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2876 do_stop
2877 case &quot;$?&quot; in
2878 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2879 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2880 esac
2881 ;;
2882 status)
2883 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2884 ;;
2885 #reload|force-reload)
2886 #
2887 # If do_reload() is not implemented then leave this commented out
2888 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2889 #
2890 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2891 #do_reload
2892 #log_end_msg $?
2893 #;;
2894 restart|force-reload)
2895 #
2896 # If the &quot;reload&quot; option is implemented then remove the
2897 # &#39;force-reload&#39; alias
2898 #
2899 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2900 do_stop
2901 case &quot;$?&quot; in
2902 0|1)
2903 do_start
2904 case &quot;$?&quot; in
2905 0) log_end_msg 0 ;;
2906 1) log_end_msg 1 ;; # Old process is still running
2907 *) log_end_msg 1 ;; # Failed to start
2908 esac
2909 ;;
2910 *)
2911 # Failed to stop
2912 log_end_msg 1
2913 ;;
2914 esac
2915 ;;
2916 *)
2917 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2918 exit 3
2919 ;;
2920 esac
2921
2922 :
2923 &lt;/pre&gt;&lt;/p&gt;
2924
2925 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2926 lot. I did not really polish the approach, so it might not always
2927 work out of the box, but you get the idea. I did not try very hard to
2928 optimize it nor make it more robust either.&lt;/p&gt;
2929
2930 &lt;p&gt;A better argument for switching init system in Debian than reducing
2931 the size of init scripts (which is a good thing to do anyway), is to
2932 get boot system that is able to handle the kernel events sensibly and
2933 robustly, and do not depend on the boot to run sequentially. The boot
2934 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2935 </description>
2936 </item>
2937
2938 <item>
2939 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2940 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2941 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2942 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2943 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2944 remote display access is the preferred solution with oVirt and RedHat
2945 Enterprise Virtualization, and I was sad to discover the other day
2946 that the browser plugin needed to use these systems seamlessly was
2947 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2948 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2949 2013-04-01, so I decided to wrap up a package based on the great work
2950 from Cajus Pollmeier and put it in a collab-maint maintained git
2951 repository to get a package I could use. I would very much like
2952 others to help me maintain the package (or just take over, I do not
2953 mind), but as no-one had volunteered so far, I just uploaded it to
2954 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2955
2956 &lt;p&gt;The source is now available from
2957 &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;
2958 </description>
2959 </item>
2960
2961 <item>
2962 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2963 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2964 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2965 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2966 <description>&lt;p&gt;The
2967 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2968 program is a a very nice system to create virtual machine images. It
2969 create a image file, add a partition table, mount it and run
2970 debootstrap in the mounted directory to create a Debian system on a
2971 stick. Yesterday, I decided to try to teach it how to make images for
2972 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2973 of a plan to simplify the build system for
2974 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2975 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2976 the virtualbox images, but its current build system made multistrap
2977 based system for Dreamplug images, and it is lacking support for
2978 Raspberry Pi.&lt;/p&gt;
2979
2980 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2981 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2982 code and adjusted it to be able to build armel images on my amd64
2983 Debian laptop. I ended up giving vmdebootstrap five new options,
2984 allowing me to replicate the image creation process I use to make
2985 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2986 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2987 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2988 call debootstrap with --foreign and to copy the handler into the
2989 generated chroot before running the second stage. This allow
2990 vmdebootstrap to create armel images on an amd64 host. Next I added
2991 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2992 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2993 given file system type, allowing me to create an image with a vfat
2994 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2995 variant&lt;/tt&gt; option to allow me to create smaller images without the
2996 Debian base system packages installed. Finally, I added an option
2997 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2998 as a boot loader. It is not needed on the Raspberry Pi and probably
2999 most other non-x86 architectures. The changes were accepted by the
3000 upstream author of vmdebootstrap yesterday and today, and is now
3001 available from
3002 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
3003 upstream project page&lt;/a&gt;.&lt;/p&gt;
3004
3005 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
3006 create a small script (the customize script) to add the non-free
3007 binary blob needed to boot the Raspberry Pi and the APT source
3008 list:&lt;/p&gt;
3009
3010 &lt;p&gt;&lt;pre&gt;
3011 #!/bin/sh
3012 set -e # Exit on first error
3013 rootdir=&quot;$1&quot;
3014 cd &quot;$rootdir&quot;
3015 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
3016 deb http://http.debian.net/debian/ jessie main contrib non-free
3017 EOF
3018 # Install non-free binary blob needed to boot Raspberry Pi. This
3019 # install a kernel somewhere too.
3020 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3021 -O $rootdir/usr/bin/rpi-update
3022 chmod a+x $rootdir/usr/bin/rpi-update
3023 mkdir -p $rootdir/lib/modules
3024 touch $rootdir/boot/start.elf
3025 chroot $rootdir rpi-update
3026 &lt;/pre&gt;&lt;/p&gt;
3027
3028 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
3029 to build the image:&lt;/p&gt;
3030
3031 &lt;pre&gt;
3032 sudo ./vmdebootstrap \
3033 --variant minbase \
3034 --arch armel \
3035 --distribution jessie \
3036 --mirror http://http.debian.net/debian \
3037 --image test.img \
3038 --size 600M \
3039 --bootsize 64M \
3040 --boottype vfat \
3041 --log-level debug \
3042 --verbose \
3043 --no-kernel \
3044 --no-extlinux \
3045 --root-password raspberry \
3046 --hostname raspberrypi \
3047 --foreign /usr/bin/qemu-arm-static \
3048 --customize `pwd`/customize \
3049 --package netbase \
3050 --package git-core \
3051 --package binutils \
3052 --package ca-certificates \
3053 --package wget \
3054 --package kmod
3055 &lt;/pre&gt;&lt;/p&gt;
3056
3057 &lt;p&gt;The list of packages being installed are the ones needed by
3058 rpi-update to make the image bootable on the Raspberry Pi, with the
3059 exception of netbase, which is needed by debootstrap to find
3060 /etc/hosts with the minbase variant. I really wish there was a way to
3061 set up an Raspberry Pi using only packages in the Debian archive, but
3062 that is not possible as far as I know, because it boots from the GPU
3063 using a non-free binary blob.&lt;/p&gt;
3064
3065 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
3066 probably a few others installed. I have not checked the complete
3067 build dependency list.&lt;/p&gt;
3068
3069 &lt;p&gt;The resulting image will not use the hardware floating point unit
3070 on the Raspberry PI, because the armel architecture in Debian is not
3071 optimized for that use. So the images created will be a bit slower
3072 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
3073 </description>
3074 </item>
3075
3076 <item>
3077 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
3078 <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>
3079 <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>
3080 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
3081 <description>&lt;p&gt;The last few days I came across a few good causes that should get
3082 wider attention. I recommend signing and donating to each one of
3083 these. :)&lt;/p&gt;
3084
3085 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
3086 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
3087 Women program which is a Google Summer of Code like initiative to get
3088 more women involved in free software. One debian sponsor has offered
3089 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
3090 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
3091 hope you will to. :)&lt;/p&gt;
3092
3093 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
3094 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
3095 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
3096 take place these days, and their need to fund the work. I&#39;ve already
3097 donated. Are you next?&lt;/p&gt;
3098
3099 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
3100 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3101 statement under the heading
3102 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
3103 Access&lt;/a&gt; for those of us asking for more focus on open access in the
3104 Norwegian government. So far 499 signatures. I hope you will sign it
3105 too.&lt;/p&gt;
3106 </description>
3107 </item>
3108
3109 <item>
3110 <title>Videos about the Freedombox project - for inspiration and learning</title>
3111 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
3112 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
3113 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
3114 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
3115 project&lt;/a&gt; have been going on for a while, and have presented the
3116 vision, ideas and solution several places. Here is a little
3117 collection of videos of talks and presentation of the project.&lt;/p&gt;
3118
3119 &lt;ul&gt;
3120
3121 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
3122 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
3123
3124 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
3125 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3126
3127 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
3128 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3129 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
3130 (Youtube)&lt;/li&gt;
3131
3132 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
3133 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
3134
3135 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
3136 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3137
3138 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
3139 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3140 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
3141
3142 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
3143 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
3144 (Youtube)&lt;/li&gt;
3145
3146 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
3147 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
3148
3149 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
3150 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
3151
3152 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
3153 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3154 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
3155
3156 &lt;/ul&gt;
3157
3158 &lt;p&gt;A larger list is available from
3159 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
3160 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
3161
3162 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
3163 Jessie is coming along quite well, and soon both Owncloud and using
3164 Tor should be available for testers of the Freedombox solution. :) In
3165 a few weeks I hope everything needed to test it is included in Debian.
3166 The withsqlite package is already in Debian, and the plinth package is
3167 pending in NEW. The third and vital part of that puzzle is the
3168 metapackage/setup framework, which is still pending an upload. Join
3169 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
3170 (#freedombox on irc.debian.org)&lt;/a&gt; and
3171 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3172 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3173 </description>
3174 </item>
3175
3176 <item>
3177 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
3178 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
3179 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
3180 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
3181 <description>&lt;p&gt;I was introduced to the
3182 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
3183 in 2010, when Eben Moglen presented his vision about serving the need
3184 of non-technical people to keep their personal information private and
3185 within the legal protection of their own homes. The idea is to give
3186 people back the power over their network and machines, and return
3187 Internet back to its intended peer-to-peer architecture. Instead of
3188 depending on a central service, the Freedombox will give everyone
3189 control over their own basic infrastructure.&lt;/p&gt;
3190
3191 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
3192 taken priority. But this summers nasty news about the misuse of trust
3193 and privilege exercised by the &quot;western&quot; intelligence gathering
3194 communities increased my eagerness to contribute to a point where I
3195 actually started working on the project a while back.&lt;/p&gt;
3196
3197 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
3198 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
3199 create a simple and cheap Debian based appliance that anyone can hook
3200 up in their home and get access to secure and private services and
3201 communication. The initial deployment platform have been the
3202 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
3203 which is a piece of hardware I do not own. So to be able to test what
3204 the current Freedombox setup look like, I had to come up with a way to install
3205 it on some hardware I do have access to. I have rewritten the
3206 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
3207 image build framework to use .deb packages instead of only copying
3208 setup into the boot images, and thanks to this rewrite I am able to
3209 set up any machine supported by Debian Wheezy as a Freedombox, using
3210 the previously mentioned deb (and a few support debs for packages
3211 missing in Debian).&lt;/p&gt;
3212
3213 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
3214 scripts
3215 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
3216 and a administrative web interface
3217 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
3218 withsqlite), as well as a privacy enhancing proxy based on
3219 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
3220 (freedombox-privoxy). There is also a web/javascript based XMPP
3221 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
3222 trying (unsuccessfully so far) to talk to the XMPP server
3223 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
3224 web interface is pluggable, and the goal is to use it to enable OpenID
3225 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3226 this is really working yet, see
3227 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
3228 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
3229 on github at the moment. The HTTP proxy is operational out of the
3230 box, and the admin web interface can be used to add/remove plinth
3231 users. I&#39;ve not been able to do anything else with it so far, but
3232 know there are several branches spread around github and other places
3233 with lots of half baked features.&lt;/p&gt;
3234
3235 &lt;p&gt;Anyway, if you want to have a look at the current state, the
3236 following recipes should work to give you a test machine to poke
3237 at.&lt;/p&gt;
3238
3239 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
3240
3241 &lt;ol&gt;
3242
3243 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
3244 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
3245 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
3246 to the Debian installer:&lt;p&gt;
3247 &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;
3248
3249 &lt;li&gt;Answer the few language/region/password questions and pick disk to
3250 install on.&lt;/li&gt;
3251
3252 &lt;li&gt;When the installation is finished and the machine have rebooted a
3253 few times, your Freedombox is ready for testing.&lt;/li&gt;
3254
3255 &lt;/ol&gt;
3256
3257 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
3258
3259 &lt;ol&gt;
3260
3261 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
3262 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
3263 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
3264 &lt;pre&gt;
3265 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
3266 &lt;/pre&gt;&lt;/li&gt;
3267 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
3268 &lt;pre&gt;
3269 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3270 apt-key add -
3271 apt-get update
3272 apt-get install freedombox-setup
3273 /usr/lib/freedombox/setup
3274 &lt;/pre&gt;&lt;/li&gt;
3275 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
3276
3277 &lt;/ol&gt;
3278
3279 &lt;p&gt;You can test it on other architectures too, but because the
3280 freedombox-privoxy package is binary, it will only work as intended on
3281 the architectures where I have had time to build the binary and put it
3282 in my APT repository. But do not let this stop you. It is only a
3283 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
3284
3285 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
3286 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
3287 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
3288 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
3289
3290 &lt;p&gt;Please let me know if this works for you, or if you have any
3291 problems. We gather on the IRC channel
3292 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
3293 irc.debian.org and the
3294 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
3295 mailing list&lt;/a&gt;.&lt;/p&gt;
3296
3297 &lt;p&gt;Once you get your freedombox operational, you can visit
3298 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
3299 welcome screen (dead end - do not be surprised if you are unable to
3300 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
3301 to look at the rest of plinth. The default user is &#39;admin&#39; and the
3302 default password is &#39;secret&#39;.&lt;/p&gt;
3303 </description>
3304 </item>
3305
3306 <item>
3307 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
3308 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3309 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3310 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3311 <description>&lt;p&gt;Earlier, I reported about
3312 &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
3313 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3314 told by IBM that the original disk should be thrown away. And as
3315 there no longer was a problem if I bricked the firmware, I decided
3316 today to try to install Intel firmware to replace the Lenovo firmware
3317 currently on the disk.&lt;/p&gt;
3318
3319 &lt;p&gt;I searched the Intel site for firmware, and found
3320 &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;
3321 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3322 according to the site should contain the latest firmware for SSD
3323 disks. I inserted the broken disk in one of my spare laptops and
3324 booted the ISO from a USB stick. The disk was recognized, but the
3325 program claimed the newest firmware already were installed and refused
3326 to insert any Intel firmware. So no change, and the disk is still
3327 unable to handle write load. :( I guess the only way to get them
3328 working would be if Lenovo releases new firmware. No idea how likely
3329 that is. Anyway, just blogging about this test for completeness. I
3330 got a working Samsung disk, and see no point in spending more time on
3331 the broken disks.&lt;/p&gt;
3332 </description>
3333 </item>
3334
3335 <item>
3336 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3337 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3339 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3340 <description>&lt;p&gt;Today I switched to
3341 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3342 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3343 my new Thinkpad X230, which was delivered with an
3344 &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
3345 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3346 sustained writes. My hardware supplier have been very forthcoming in
3347 trying to find a solution, and after first trying with another
3348 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3349 disk instead to fix it once and for all. The Samsung disk survived
3350 the installation of Debian with encrypted disks (filling the disk with
3351 random data during installation killed the first two), and I thus
3352 decided to trust it with my data. I have installed it as a Debian Edu
3353 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3354 server at home using Kerberos and LDAP, and will use it as my work
3355 station from now on.&lt;/p&gt;
3356
3357 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3358 Debian Wheezy default installation need to be tuned a bit to increase
3359 performance and increase life time of the disk. The Linux kernel and
3360 user space applications do not yet adjust automatically to such
3361 environment. To make it easier for my self, I created a draft Debian
3362 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3363 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3364 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3365 is set up to adjust the setup of the machine by just installing the
3366 package. If there is any non-SSD disk in the machine, the package
3367 will refuse to install, as I did not try to write any logic to sort
3368 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3369
3370 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3371 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3372 where I set up the machine with one large encrypted partition (in
3373 addition to /boot), put LVM on top of this and set up partitions on
3374 top of this again. See the README file in the package source for the
3375 references I used to pick the settings. At the moment these
3376 parameters are tuned:&lt;/p&gt;
3377
3378 &lt;ul&gt;
3379
3380 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3381 (adding discard to /etc/crypttab)&lt;/li&gt;
3382
3383 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3384 this case a cryptsetup partition) by changing issue_discards from
3385 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3386
3387 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3388 systems.&lt;/li&gt;
3389
3390 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3391 /etc/fstab.&lt;/li&gt;
3392
3393 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3394
3395 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3396 cron.daily).&lt;/li&gt;
3397
3398 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3399 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3400
3401 &lt;/ul&gt;
3402
3403 &lt;p&gt;During installation, I cancelled the part where the installer fill
3404 the disk with random data, as this would kill the SSD performance for
3405 little gain. My goal with the encrypted file system is to ensure
3406 those stealing my laptop end up with a brick and not a working
3407 computer. I have no hope in keeping the really resourceful people
3408 from getting the data on the disk (see
3409 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3410 Thus I concluded that adding the discard option to crypttab is the
3411 right thing to do.&lt;/p&gt;
3412
3413 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3414 it for SSD, but others recommended deadline and a benchmark I found
3415 indicated that deadline might be better for interactive use.&lt;/p&gt;
3416
3417 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3418 and ext4, but read that it would give a performance hit ever time a
3419 file is removed, and thought it best to that that slowdown once a day
3420 instead of during my work.&lt;/p&gt;
3421
3422 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3423 this is already done by Debian Edu.&lt;/p&gt;
3424
3425 &lt;p&gt;I have not yet started on the user space tuning. I expect
3426 iceweasel need some tuning, and perhaps other applications too, but
3427 have not yet had time to investigate those parts.&lt;/p&gt;
3428
3429 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3430 there.&lt;/p&gt;
3431
3432 &lt;p&gt;As for the answer to the question in the title of this blog post,
3433 as far as I know, the only solution I know about is to replace the
3434 disk. It might be possible to flash it with Intel firmware instead of
3435 the Lenovo firmware. But I have not tried and did not want to do so
3436 without approval from Lenovo as I wanted to keep the warranty on the
3437 disk until a solution was found and they wanted the broken disks
3438 back.&lt;/p&gt;
3439 </description>
3440 </item>
3441
3442 <item>
3443 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3444 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3445 <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>
3446 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3447 <description>&lt;p&gt;A few days ago, I wrote about
3448 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3449 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3450 was dying during installation because it is unable to cope with
3451 sustained write. My supplier is in contact with
3452 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3453 replacement disk to try to fix the problem. They decided to send an
3454 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3455
3456 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3457 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3458 same firmware version as the original. This time my hope raised
3459 slightly as the installation progressed, as the original disk used to
3460 die after 4-7% of the disk was written to, while this time it kept
3461 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3462 died again and I was back on square one. I still do not have a new
3463 laptop with a disk I can trust. I can not live with a disk that might
3464 lock up when I download a new
3465 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3466 other large files. I look forward to hearing from my supplier with
3467 the next proposal from Lenovo.&lt;/p&gt;
3468
3469 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3470 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3471 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3472 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3473 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3474 P/N 45N8295, P0C38732.&lt;/p&gt;
3475
3476 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3477 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3478 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3479 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3480 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3481 P/N 45N8295, P0C38732.&lt;/p&gt;
3482
3483 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3484 SA, date and WNPP values. Mentioning all the details here in case
3485 someone is able to use the information to find a way to identify the
3486 failing disk among working ones (if any such working disk actually
3487 exist).&lt;/p&gt;
3488 </description>
3489 </item>
3490
3491 <item>
3492 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3493 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3494 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3495 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3496 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3497 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3498 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3499 member assosiation NUUG&lt;/a&gt; and
3500 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3501 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3502 Bitraf&lt;/a&gt;.&lt;/p&gt;
3503
3504 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3505 welcome, and there is no fee to participate. There is on the other
3506 hand limited space, and only room for 30 people. Please put your name
3507 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3508 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3509 </description>
3510 </item>
3511
3512 <item>
3513 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3514 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3516 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3517 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3518 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3519 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3520 time to spend on it, and it took a while to find a model I believe
3521 will do the job, but two days ago the replacement finally arrived. I
3522 ended up picking a
3523 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3524 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3525 a roaming workstation, and it seemed to work flawlessly. But my
3526 second installation with encrypted disk was not as successful. More
3527 on that below.&lt;/p&gt;
3528
3529 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3530 important requirements (robust and with a good keyboard) are never
3531 listed in the feature list. But I did get good help from the search
3532 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3533 allowed me to limit the list of interesting laptops based on my other
3534 requirements. A bit surprising that SSD disk are not disks according
3535 to that search interface, so I had to drop specifying the number of
3536 disks from my search parameters. I also asked around among friends to
3537 get their impression on keyboards and robustness.&lt;/p&gt;
3538
3539 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3540 X41. I am not quite convinced about the keyboard, as it is
3541 significantly wider than my old keyboard, and I have to stretch my
3542 hand a lot more to reach the edges. But the key response is fairly
3543 good and the individual key shape is fairly easy to handle, so I hope
3544 I will get used to it. My old X40 was starting to fail, and I really
3545 needed a new laptop now. :)&lt;/p&gt;
3546
3547 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3548 visit to the BIOS during boot it disable it.&lt;/p&gt;
3549
3550 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3551 lock up during load. And this happen when installing Debian Wheezy
3552 with encrypted disk, while the disk is being filled with random data.
3553 I also tested to install Ubuntu Raring, and it happen there too if I
3554 reenable the code to fill the disk with random data (it is disabled by
3555 default in Ubuntu). And the bug with is already known. It was
3556 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3557 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3558 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3559 kernel developers as
3560 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3561 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3562 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3563 Lenovo forums, both for
3564 &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
3565 2012-11-10&lt;/a&gt; and for
3566 &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
3567 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3568 reports state that the disk lock up during use if many writes are done
3569 on the disk, so it is much no use to work around the installation
3570 problem and end up with a computer that can lock up at any moment.
3571 There is even a
3572 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3573 available&lt;/a&gt; that will lock up the hard drive after running a few
3574 minutes by writing to a file.&lt;/p&gt;
3575
3576 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3577 contacting PCHELP Norway (request 01D1FDP) which handle support
3578 requests for Lenovo, his first suggestion was to upgrade the disk
3579 firmware. Unfortunately there is no newer firmware available from
3580 Lenovo, as my disk already have the most recent one (version LF1i). I
3581 hope to hear more from him today and hope the problem can be
3582 fixed. :)&lt;/p&gt;
3583 </description>
3584 </item>
3585
3586 <item>
3587 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3588 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3589 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3590 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3591 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3592 trusty old Thinkpad X41. Unfortunately I did not have much time to
3593 spend on it, but today the replacement finally arrived. I ended up
3594 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3595 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3596 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3597 this, it is installing what I hope will be a more final installation,
3598 with a encrypted hard drive to ensure any dope head stealing it end up
3599 with an expencive door stop.&lt;/p&gt;
3600
3601 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3602 important requirements (robust and with a good keyboard) are never
3603 listed in the feature list. But I did get good help from the search
3604 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3605 allowed me to limit the list of interesting laptops based on my other
3606 requirements. A bit surprising that SSD disk are not disks, so I had
3607 to drop number of disks from my search parameters.&lt;/p&gt;
3608
3609 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3610 wider than my old keyboard, and I have to stretch my hand a lot more
3611 to reach the edges. But the key response is fairly good and the
3612 individual key shape is fairly easy to handle, so I hope I will get
3613 used to it. My old X40 was starting to fail, and I really needed a
3614 new laptop now. :)&lt;/p&gt;
3615
3616 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3617 </description>
3618 </item>
3619
3620 <item>
3621 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3622 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3624 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3625 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3626 perfectly capable of, and I have to do it manually to get things
3627 working. One such task is to find out what firmware packages are
3628 needed to get the hardware on my computer working. Most often this
3629 affect the wifi card, but some times it even affect the RAID
3630 controller or the ethernet card. Today I pushed version 0.4 of the
3631 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3632 including a new script isenkram-autoinstall-firmware handling the
3633 process of asking all the loaded kernel modules what firmware files
3634 they want, find debian packages providing these files and install the
3635 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3636
3637 &lt;p&gt;&lt;pre&gt;
3638 # isenkram-autoinstall-firmware
3639 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3640 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3641 info: locating packages with the requested firmware files
3642 info: Updating APT sources after adding non-free APT source
3643 info: trying to install firmware-ipw2x00
3644 firmware-ipw2x00
3645 firmware-ipw2x00
3646 Preconfiguring packages ...
3647 Selecting previously deselected package firmware-ipw2x00.
3648 (Reading database ... 259727 files and directories currently installed.)
3649 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3650 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3651 #
3652 &lt;/pre&gt;&lt;/p&gt;
3653
3654 &lt;p&gt;When all the requested firmware is present, a simple message is
3655 printed instead:&lt;/p&gt;
3656
3657 &lt;p&gt;&lt;pre&gt;
3658 # isenkram-autoinstall-firmware
3659 info: did not find any firmware files requested by loaded kernel modules. exiting
3660 #
3661 &lt;/pre&gt;&lt;/p&gt;
3662
3663 &lt;p&gt;It could use some polish, but it is already working well and saving
3664 me some time when setting up new machines. :)&lt;/p&gt;
3665
3666 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3667 kernel modules, and look up each one of them using modinfo, to find
3668 the firmware files listed in the module meta-information. Next, it
3669 download the Contents file from a nearby APT mirror, and search for
3670 the firmware files in this file to locate the package with the
3671 requested firmware file. If the package is in the non-free section, a
3672 non-free APT source is added and the package is installed using
3673 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3674 machine.&lt;/p&gt;
3675
3676 &lt;p&gt;I hope someone find time to implement a more polished version of
3677 this script as part of the hw-detect debian-installer module, to
3678 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3679 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3680 firmware during a PXE install when the packages already are available
3681 from the nearby Debian mirror.&lt;/p&gt;
3682 </description>
3683 </item>
3684
3685 <item>
3686 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3687 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3688 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3689 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3690 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3691 the screen just turn black when Linux boot, either during installation
3692 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3693 last few years, but only recently understood the cause. I&#39;ve seen it
3694 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3695 The reason seem to be in the wiring of some laptops. The system to
3696 control the screen background light is inverted, so when Linux try to
3697 turn the brightness fully on, it end up turning it off instead. I do
3698 not know which Linux drivers are affected, but this post is about the
3699 i915 driver used by the
3700 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3701 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3702
3703 &lt;p&gt;The problem can be worked around two ways. Either by adding
3704 i915.invert_brightness=1 as a kernel option, or by adding a file in
3705 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3706 option when it load the i915 kernel module. On Debian and Ubuntu, it
3707 can be done by running these commands as root:&lt;/p&gt;
3708
3709 &lt;pre&gt;
3710 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3711 update-initramfs -u -k all
3712 &lt;/pre&gt;
3713
3714 &lt;p&gt;Since March 2012 there is
3715 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3716 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3717 hardware have this problem, and get the driver to invert the
3718 brightness setting automatically. To use it, one need to add a row in
3719 &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
3720 intel_quirks array&lt;/a&gt; in the driver source
3721 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3722 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3723 number (vendor number 8086 is assumed) and subdevice vendor and device
3724 number.&lt;/p&gt;
3725
3726 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3727 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3728
3729 &lt;p&gt;&lt;pre&gt;
3730 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3731 3rd Gen Core processor Graphics Controller [8086:0156] \
3732 (rev 09) (prog-if 00 [VGA controller])
3733 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3734 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3735 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3736 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3737 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3738 Latency: 0
3739 Interrupt: pin A routed to IRQ 42
3740 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3741 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3742 Region 4: I/O ports at 4000 [size=64]
3743 Expansion ROM at &lt;unassigned&gt; [disabled]
3744 Capabilities: &lt;access denied&gt;
3745 Kernel driver in use: i915
3746 &lt;/pre&gt;&lt;/p&gt;
3747
3748 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3749
3750 &lt;p&gt;&lt;pre&gt;
3751 struct intel_quirk intel_quirks[] = {
3752 ...
3753 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3754 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3755 ...
3756 }
3757 &lt;/pre&gt;&lt;/p&gt;
3758
3759 &lt;p&gt;According to the kernel module instructions (as seen using
3760 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3761 invert_brightness flag should be sent to the
3762 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3763 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3764 developers. But my email about the laptop sent 2013-06-03 have not
3765 yet shown up in
3766 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3767 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3768 emails from non-subscribers. Because of this, I sent my patch also to
3769 the Debian bug tracking system instead as
3770 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3771 sure the patch is not lost.&lt;/p&gt;
3772
3773 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3774 with this problem working properly with Linux. If you use Gnome, your
3775 worries should be over at this point. But if you use KDE, there is
3776 something in KDE ignoring the invert_brightness setting and turning on
3777 the screen during login. I&#39;ve reported it to Debian as
3778 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3779 have no idea yet how to figure out exactly what subsystem is doing
3780 this. Perhaps you can help? Perhaps you know what the Gnome
3781 developers did to handle this, and this can give a clue to the KDE
3782 developers? Or you know where in KDE the screen brightness is changed
3783 during login? If so, please update the BTS report (or get in touch if
3784 you do not know how to update BTS).&lt;/p&gt;
3785
3786 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3787 acpi_backlight=vendor, to disable ACPI backlight support completely,
3788 as the ACPI information on the machine is trash and it is better to
3789 leave it to the intel video driver to control the screen
3790 backlight.&lt;/p&gt;
3791 </description>
3792 </item>
3793
3794 <item>
3795 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3796 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3797 <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>
3798 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3799 <description>&lt;p&gt;Two days ago, I asked
3800 &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
3801 I could install Linux on a Packard Bell EasyNote LV computer
3802 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3803 with the obstacles put in the way of Linux users on a laptop with UEFI
3804 and Windows 8.&lt;/p&gt;
3805
3806 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3807 secure booting or fast boot. I suspect fast boot was the problem,
3808 causing the firmware to boot directly from HD without considering any
3809 key presses and alternative devices, but do not know UEFI settings
3810 enough to tell.&lt;/p&gt;
3811
3812 &lt;p&gt;There is no way to install Linux on the machine in question without
3813 opening the box and disconnecting the hard drive! This is as far as I
3814 can tell, the only way to get access to the firmware setup menu
3815 without accepting the Windows 8 license agreement. I am told (and
3816 found description on how to) that it is possible to configure the
3817 firmware setup once booted into Windows 8. But as I believe the terms
3818 of that agreement are completely unacceptable, accepting the license
3819 was never an alternative. I do not enter agreements I do not intend
3820 to follow.&lt;/p&gt;
3821
3822 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3823 waste many hours on this, but luckily there was a way to get it to
3824 work. But I would not recommend it to anyone planning to run Linux on
3825 it, and I have become sceptical to Windows 8 certified laptops. Is
3826 this the way Linux will be forced out of the market place, by making
3827 it close to impossible for &quot;normal&quot; users to install Linux without
3828 accepting the Microsoft Windows license terms? Or at least not
3829 without risking to loose the warranty?&lt;/p&gt;
3830
3831 &lt;p&gt;I&#39;ve updated the
3832 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3833 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3834 do not have to struggle as much as I did to get Linux into the
3835 machine.&lt;/p&gt;
3836
3837 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3838 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3839 </description>
3840 </item>
3841
3842 <item>
3843 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3844 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3845 <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>
3846 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3847 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3848 new laptops for my parents and a few others. I bought Packard Bell
3849 Easynote LV to run Kubuntu on and use as their home computer. But I
3850 am completely unable to figure out how to install Linux on it. The
3851 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3852 instead of a BIOS to boot.&lt;/p&gt;
3853
3854 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3855 to get it to boot the Linux installer from my USB stick. I have yet
3856 to try the DVD install, and still hope it will work. when I turn on
3857 the computer, there is no information on what buttons to press to get
3858 the normal boot menu. I expect to get some boot menu to select PXE or
3859 USB stick booting. When booting, it first ask for the language to
3860 use, then for some regional settings, and finally if I will accept the
3861 Windows 8 terms of use. As these terms are completely unacceptable to
3862 me, I have no other choice but to turn off the computer and try again
3863 to get it to boot the Linux installer.&lt;/p&gt;
3864
3865 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3866 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3867 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3868 installed on this machine, please get in touch or update that wiki
3869 page. If I can&#39;t find a way to install Linux, I will have to return
3870 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3871
3872 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3873 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3874 on new Laptops?&lt;/p&gt;
3875 </description>
3876 </item>
3877
3878 <item>
3879 <title>How to transform a Debian based system to a Debian Edu installation</title>
3880 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3882 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3883 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3884 an operating system based on Debian intended for use in schools. It
3885 contain a turn-key solution for the computer network provided to
3886 pupils in the primary schools. It provide both the central server,
3887 network boot servers and desktop environments with heaps of
3888 educational software. The project was founded almost 12 years ago,
3889 2001-07-02. If you want to support the project, which is in need for
3890 cash to fund developer gatherings and other project related activity,
3891 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3892 donate some money&lt;/a&gt;.
3893
3894 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3895 lists and elsewhere, is the question on how to transform a Debian or
3896 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3897 hard, and last week I wrote a script to replicate the steps done by
3898 the Debian Edu installer.&lt;/p&gt;
3899
3900 &lt;p&gt;The script,
3901 &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;
3902 in the debian-edu-config package, will go through these six steps and
3903 transform an existing Debian Wheezy or Ubuntu (untested) installation
3904 into a Debian Edu Workstation:&lt;/p&gt;
3905
3906 &lt;ol&gt;
3907
3908 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3909 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3910 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3911 our configuration.&lt;/li&gt;
3912 &lt;li&gt;Preseed debconf database with profile setup in
3913 /etc/debian-edu/config, and run tasksel to install packages
3914 according to the profile specified in the config above,
3915 overriding some of the Debian automation machinery.&lt;/li&gt;
3916 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3917 that could not be done using preseeding.&lt;/li&gt;
3918 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3919
3920 &lt;/ol&gt;
3921
3922 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3923 replicated like this. Disk partitioning and LVM setup, for example.
3924 So this script just assume there is enough disk space to install all
3925 the needed packages.&lt;/p&gt;
3926
3927 &lt;p&gt;The script was created to help a Debian Edu student working on
3928 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3929 Debian Edu client, and using it he can take the existing
3930 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3931 transform it into a fully functioning Debian Edu Workstation (or
3932 Roaming Workstation, or whatever :).&lt;/p&gt;
3933
3934 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3935 If a LXDE based Roaming workstation is wanted instead, modify the
3936 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3937
3938 &lt;p&gt;&lt;pre&gt;
3939 PROFILE=&quot;Roaming-Workstation&quot;
3940 DESKTOP=&quot;lxde&quot;
3941 &lt;/pre&gt;&lt;/p&gt;
3942
3943 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3944 the cloud, by starting with a virtual Debian installation at some
3945 virtual hosting service and setting up all the services on first
3946 boot.&lt;/p&gt;
3947 </description>
3948 </item>
3949
3950 <item>
3951 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3952 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3953 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3954 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3955 <description>&lt;P&gt;In January,
3956 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3957 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3958 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3959 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3960 marvellous construction system from Denmark. We also created
3961 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3962 a place to take notes and write down our plans and hopes. And several
3963 people showed up to help. I was very happy to see the effect of my
3964 call. Since the small start, we have a debtags tag
3965 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3966 tag for LEGO related packages, and now count 10 packages related to
3967 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3968
3969 &lt;p&gt;&lt;table&gt;
3970 &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;
3971 &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;
3972 &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;
3973 &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;
3974 &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;
3975 &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;
3976 &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;
3977 &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;
3978 &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;
3979 &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;
3980 &lt;/table&gt;&lt;/p&gt;
3981
3982 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3983 currently available in Jessie/testing. leocad is so far only
3984 available in experimental.&lt;/p&gt;
3985
3986 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3987 adding the rest of the great free software tools available on Linux
3988 for LEGO designers.&lt;/p&gt;
3989 </description>
3990 </item>
3991
3992 <item>
3993 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3994 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3996 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3997 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3998 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3999 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
4000 Debian release, and I expect to move my machines at home over to it fairly
4001 soon.&lt;/p&gt;
4002
4003 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
4004 in particular make me very happy to see included. The
4005 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
4006 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
4007 included for the first time. Alongside similar programs like
4008 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
4009 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
4010 it allow for visual programming where syntax errors can not happen,
4011 and a friendly programming environment for learning to control the
4012 computer. Scratch will also be included in the next release of Debian
4013 Edu.&lt;/a&gt;
4014
4015 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
4016 Edu/Skolelinux release too. The
4017 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
4018 alpha release&lt;/a&gt; went out last week, and the next should soon
4019 follow.&lt;p&gt;
4020 </description>
4021 </item>
4022
4023 <item>
4024 <title>Isenkram 0.2 finally in the Debian archive</title>
4025 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
4026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
4027 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
4028 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
4029 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
4030 for many months. I uploaded it to the Debian experimental suite
4031 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
4032
4033 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
4034 install to work with a pluggable hardware device. The suggestion pop
4035 up when the device is plugged in. For example if a Lego Mindstorm NXT
4036 is inserted, it will suggest to install the program needed to program
4037 the NXT controller. Give it a go, and report bugs and suggestions to
4038 BTS. :)&lt;/p&gt;
4039 </description>
4040 </item>
4041
4042 <item>
4043 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
4044 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
4045 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
4046 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
4047 <description>&lt;p&gt;My
4048 &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
4049 bitcoin related blog post&lt;/a&gt; mentioned that the new
4050 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
4051 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4052 2013-01-19, and have been available in unstable since then. It was
4053 automatically copied to Ubuntu, and is available in their Raring
4054 version too.&lt;/p&gt;
4055
4056 &lt;p&gt;But there is a strange problem with the build that block this new
4057 version from being available on the i386 and kfreebsd-i386
4058 architectures. For some strange reason, the autobuilders in Debian
4059 for these architectures fail to run the test suite on these
4060 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
4061 We are so far unable to reproduce it when building it manually, and
4062 no-one have been able to propose a fix. If you got an idea what is
4063 failing, please let us know via the BTS.&lt;/p&gt;
4064
4065 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
4066 I often run low on disk space, is the fact that the client will exit
4067 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
4068 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
4069 it. :)&lt;/p&gt;
4070
4071 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4072 activities, please send Bitcoin donations to my address
4073 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4074 </description>
4075 </item>
4076
4077 <item>
4078 <title>Welcome to the world, Isenkram!</title>
4079 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
4080 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
4081 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
4082 <description>&lt;p&gt;Yesterday, I
4083 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
4084 for testers&lt;/a&gt; for my prototype for making Debian better at handling
4085 pluggable hardware devices, which I
4086 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
4087 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
4088 up, and caused me to really want to to open up the development to more
4089 people. But before I did this, I want to come up with a sensible name
4090 for this project. Today I finally decided on a new name, and I have
4091 renamed the project from hw-support-handler to this new name. In the
4092 process, I moved the source to git and made it available as a
4093 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
4094 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
4095 To fetch and build the latest version of the source, use&lt;/p&gt;
4096
4097 &lt;pre&gt;
4098 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4099 cd isenkram &amp;&amp; git-buildpackage -us -uc
4100 &lt;/pre&gt;
4101
4102 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
4103 want to hack on the source or improve the package, please go ahead.
4104 But please talk to me first on IRC or via email before you do major
4105 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
4106
4107 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
4108 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4109 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
4110 the German word eisenkram, for those that are familiar with that
4111 word.&lt;/p&gt;
4112
4113 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
4114 instructions, to avoid confusing people with an error from the signing
4115 process.&lt;/p&gt;
4116
4117 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
4118 clone argument to avoid the need for authentication.&lt;/p&gt;
4119 </description>
4120 </item>
4121
4122 <item>
4123 <title>First prototype ready making hardware easier to use in Debian</title>
4124 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
4125 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
4126 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
4127 <description>&lt;p&gt;Early this month I set out to try to
4128 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
4129 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
4130 prototype is working, and it is ready for a larger audience. To test
4131 it, fetch the
4132 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
4133 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
4134 package. You might have to log out and in again activate the
4135 autostart script.&lt;/p&gt;
4136
4137 &lt;p&gt;The design is simple:&lt;/p&gt;
4138
4139 &lt;ul&gt;
4140
4141 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
4142 hw-support-handlerd to start when the user log in.&lt;/li&gt;
4143
4144 &lt;li&gt;This program listen for kernel events about new hardware (directly
4145 from the kernel like udev does), not using HAL dbus events as I
4146 initially did.&lt;/li&gt;
4147
4148 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
4149 the APT database, a database
4150 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
4151 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
4152
4153 &lt;li&gt;If a package is mapped to the hardware in question, the package
4154 isn&#39;t installed yet and this is the first time the hardware was
4155 plugged in, show a desktop notification suggesting to install the
4156 package or packages.&lt;/li&gt;
4157
4158 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
4159 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
4160
4161 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
4162 package while showing progress information in a window.&lt;/li&gt;
4163
4164 &lt;/ul&gt;
4165
4166 &lt;p&gt;I still need to come up with a better name for the system. Here
4167 are some screen shots showing the prototype in action. First the
4168 notification, then the password request, and finally the request to
4169 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
4170
4171 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
4172 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
4173 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
4174 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
4175 &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;
4176
4177 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
4178 is already useful. The database of hardware to package mappings also
4179 need more work. It is currently compatible with the Ubuntu way of
4180 storing such information in the package control file, but could be
4181 changed to use other formats instead or in addition to the current
4182 method. I&#39;ve dropped the use of discover for this mapping, as the
4183 modalias approach is more flexible and easier to use on Linux as long
4184 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
4185
4186 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
4187 here is the command required to check out and build the source: Use
4188 &#39;&lt;tt&gt;svn checkout
4189 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4190 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
4191 devscripts package.&lt;/p&gt;
4192
4193 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
4194 renamed to Isenkram and the source moved from the Debian Edu
4195 subversion repository to a Debian collab-maint git repository. See
4196 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
4197 instructions&lt;/a&gt; for details.&lt;/p&gt;
4198 </description>
4199 </item>
4200
4201 <item>
4202 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
4203 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
4204 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
4205 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
4206 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
4207 suddenly in bed. With a quiet whimper, it went completely quiet and
4208 black. The power button was no longer able to turn it on. It was a
4209 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4210 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4211 Compaq I had before that. Now I need to find a replacement. To keep
4212 going during Christmas, I moved the one year old SSD disk to my old
4213 X40 where it fitted (only one I had left that could use it), but it is
4214 not a durable solution.
4215
4216 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
4217 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
4218
4219 &lt;ul&gt;
4220
4221 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
4222 than A4).&lt;/li&gt;
4223 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
4224 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
4225 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
4226 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
4227 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
4228 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
4229 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
4230 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
4231 size).&lt;/li&gt;
4232 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
4233 X.org packages.&lt;/li&gt;
4234 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
4235 the time).
4236
4237 &lt;/ul&gt;
4238
4239 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
4240 list. The reason is simply that the specifications on laptops the
4241 last 10-15 years have been sufficient for my needs, and I have to look
4242 at other features to choose my laptop. But are there still made as
4243 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4244 robust, and Thinkpads seem to be heading in the wrong direction since
4245 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
4246 still be useful.&lt;/p&gt;
4247
4248 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
4249 external keyboard? I&#39;ll have to check the
4250 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
4251 well-supported laptops, or perhaps just buy one preinstalled from one
4252 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
4253 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
4254 </description>
4255 </item>
4256
4257 <item>
4258 <title>How to find a browser plugin supporting a given MIME type</title>
4259 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
4260 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
4261 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
4262 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
4263 install to get support for a given MIME type. Thanks to
4264 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
4265 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
4266 Unfortunately, not very many packages provide the needed meta
4267 information, Anyway, here is a small script to look up all browser
4268 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
4269
4270 &lt;pre&gt;
4271 #!/usr/bin/python
4272 import sys
4273 import apt
4274 def pkgs_handling_mimetype(mimetype):
4275 cache = apt.Cache()
4276 cache.open(None)
4277 thepkgs = []
4278 for pkg in cache:
4279 version = pkg.candidate
4280 if version is None:
4281 version = pkg.installed
4282 if version is None:
4283 continue
4284 record = version.record
4285 if not record.has_key(&#39;Npp-MimeType&#39;):
4286 continue
4287 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
4288 for t in mime_types:
4289 t = t.rstrip().strip()
4290 if t == mimetype:
4291 thepkgs.append(pkg.name)
4292 return thepkgs
4293 mimetype = &quot;audio/ogg&quot;
4294 if 1 &lt; len(sys.argv):
4295 mimetype = sys.argv[1]
4296 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
4297 for pkg in pkgs_handling_mimetype(mimetype):
4298 print &quot; %s&quot; %pkg
4299 &lt;/pre&gt;
4300
4301 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
4302
4303 &lt;pre&gt;
4304 % ./apt-find-browserplug-for-mimetype
4305 Browser plugin packages supporting audio/ogg:
4306 gecko-mediaplayer
4307 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4308 Browser plugin packages supporting application/x-shockwave-flash:
4309 browser-plugin-gnash
4310 %
4311 &lt;/pre&gt;
4312
4313 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4314 itself to query for plugins and propose to install the needed
4315 packages. It would be great if Debian supported such feature too. Is
4316 anyone working on adding it?&lt;/p&gt;
4317
4318 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4319 request for icweasel support for this feature is
4320 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4321 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4322 of manpower and wish for a different design is the reason thus feature
4323 is not yet in iceweasel from Debian.&lt;/p&gt;
4324 </description>
4325 </item>
4326
4327 <item>
4328 <title>What is the most supported MIME type in Debian?</title>
4329 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4330 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4331 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4332 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4333 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4334 proposal to make it possible for a Desktop application to propose to
4335 the user some package to install to gain support for a given MIME
4336 type, font, library etc. that is currently missing. With such
4337 mechanism in place, it would be possible for the desktop to
4338 automatically propose and install leocad if some LDraw file is
4339 downloaded by the browser.&lt;/p&gt;
4340
4341 &lt;p&gt;To get some idea about the current content of the archive, I decided
4342 to write a simple program to extract all .desktop files from the
4343 Debian archive and look up the claimed MIME support there. The result
4344 can be found on the
4345 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4346 site&lt;/a&gt;. Using the collected information, it become possible to
4347 answer the question in the title. Here are the 20 most supported MIME
4348 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4349 The complete list is available from the link above.&lt;/p&gt;
4350
4351 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4352
4353 &lt;pre&gt;
4354 count MIME type
4355 ----- -----------------------
4356 32 text/plain
4357 30 audio/mpeg
4358 29 image/png
4359 28 image/jpeg
4360 27 application/ogg
4361 26 audio/x-mp3
4362 25 image/tiff
4363 25 image/gif
4364 22 image/bmp
4365 22 audio/x-wav
4366 20 audio/x-flac
4367 19 audio/x-mpegurl
4368 18 video/x-ms-asf
4369 18 audio/x-musepack
4370 18 audio/x-mpeg
4371 18 application/x-ogg
4372 17 video/mpeg
4373 17 audio/x-scpls
4374 17 audio/ogg
4375 16 video/x-ms-wmv
4376 &lt;/pre&gt;
4377
4378 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4379
4380 &lt;pre&gt;
4381 count MIME type
4382 ----- -----------------------
4383 33 text/plain
4384 32 image/png
4385 32 image/jpeg
4386 29 audio/mpeg
4387 27 image/gif
4388 26 image/tiff
4389 26 application/ogg
4390 25 audio/x-mp3
4391 22 image/bmp
4392 21 audio/x-wav
4393 19 audio/x-mpegurl
4394 19 audio/x-mpeg
4395 18 video/mpeg
4396 18 audio/x-scpls
4397 18 audio/x-flac
4398 18 application/x-ogg
4399 17 video/x-ms-asf
4400 17 text/html
4401 17 audio/x-musepack
4402 16 image/x-xbitmap
4403 &lt;/pre&gt;
4404
4405 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4406
4407 &lt;pre&gt;
4408 count MIME type
4409 ----- -----------------------
4410 31 text/plain
4411 31 image/png
4412 31 image/jpeg
4413 29 audio/mpeg
4414 28 application/ogg
4415 27 image/gif
4416 26 image/tiff
4417 26 audio/x-mp3
4418 23 audio/x-wav
4419 22 image/bmp
4420 21 audio/x-flac
4421 20 audio/x-mpegurl
4422 19 audio/x-mpeg
4423 18 video/x-ms-asf
4424 18 video/mpeg
4425 18 audio/x-scpls
4426 18 application/x-ogg
4427 17 audio/x-musepack
4428 16 video/x-ms-wmv
4429 16 video/x-msvideo
4430 &lt;/pre&gt;
4431
4432 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4433 information mentioned in DEP-11. I have not yet had time to look at
4434 it, but hope the PackageKit people in Debian are on top of these
4435 issues.&lt;/p&gt;
4436
4437 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4438 discovering a typo in my script.&lt;/p&gt;
4439 </description>
4440 </item>
4441
4442 <item>
4443 <title>Using modalias info to find packages handling my hardware</title>
4444 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4445 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4446 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4447 <description>&lt;p&gt;Yesterday, I wrote about the
4448 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4449 values provided by the Linux kernel&lt;/a&gt; following my hope for
4450 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4451 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4452 modalias values attached to package names can be used to map packages
4453 to hardware. This allow the system to look up and suggest relevant
4454 packages when I plug in some new hardware into my machine, and replace
4455 discover and discover-data as the database used to map hardware to
4456 packages.&lt;/p&gt;
4457
4458 &lt;p&gt;I create a modaliases file with entries like the following,
4459 containing package name, kernel module name (if relevant, otherwise
4460 the package name) and globs matching the relevant hardware
4461 modalias.&lt;/p&gt;
4462
4463 &lt;p&gt;&lt;blockquote&gt;
4464 Package: package-name
4465 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4466 &lt;/blockquote&gt;&lt;/p&gt;
4467
4468 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4469 for a given modalias value using this file.&lt;/p&gt;
4470
4471 &lt;p&gt;An entry like this would suggest the video and picture application
4472 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4473
4474 &lt;p&gt;&lt;blockquote&gt;
4475 Package: cheese
4476 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4477 &lt;/blockquote&gt;&lt;/p&gt;
4478
4479 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4480 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4481
4482 &lt;p&gt;&lt;blockquote&gt;
4483 Package: pcmciautils
4484 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4485 &lt;/blockquote&gt;&lt;/p&gt;
4486
4487 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4488 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4489
4490 &lt;p&gt;&lt;blockquote&gt;
4491 Package: colorhug-client
4492 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4493 &lt;/blockquote&gt;&lt;/p&gt;
4494
4495 &lt;p&gt;I believe the format is compatible with the format of the Packages
4496 file in the Debian archive. Ubuntu already uses their Packages file
4497 to store their mappings from packages to hardware.&lt;/p&gt;
4498
4499 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4500 announce the hardware it support in a way my prototype understand.
4501 This allow those publishing packages in an APT source outside the
4502 Debian archive as well as those backporting packages to make sure the
4503 hardware mapping are included in the package meta information. I&#39;ve
4504 tested such header in the pymissile package, and its modalias mapping
4505 is working as it should with my prototype. It even made it to Ubuntu
4506 Raring.&lt;/p&gt;
4507
4508 &lt;p&gt;To test if it was possible to look up supported hardware using only
4509 the shell tools available in the Debian installer, I wrote a shell
4510 implementation of the lookup code. The idea is to create files for
4511 each modalias and let the shell do the matching. Please check out and
4512 try the
4513 &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;
4514 shell script. It run without any extra dependencies and fetch the
4515 hardware mappings from the Debian archive and the subversion
4516 repository where I currently work on my prototype.&lt;/p&gt;
4517
4518 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4519 install yubikey-personalization:&lt;/p&gt;
4520
4521 &lt;p&gt;&lt;blockquote&gt;
4522 % ./hw-support-lookup
4523 &lt;br&gt;yubikey-personalization
4524 &lt;br&gt;%
4525 &lt;/blockquote&gt;&lt;/p&gt;
4526
4527 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4528 propose to install the pcmciautils package:&lt;/p&gt;
4529
4530 &lt;p&gt;&lt;blockquote&gt;
4531 % ./hw-support-lookup
4532 &lt;br&gt;pcmciautils
4533 &lt;br&gt;%
4534 &lt;/blockquote&gt;&lt;/p&gt;
4535
4536 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4537 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4538 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4539
4540 &lt;p&gt;It could be possible to generate several of the mappings between
4541 packages and hardware. One source would be to look at packages with
4542 kernel modules, ie packages with *.ko files in /lib/modules/, and
4543 extract their modalias information. Another would be to look at
4544 packages with udev rules, ie packages with files in
4545 /lib/udev/rules.d/, and extract their vendor/model information to
4546 generate a modalias matching rule. I have not tested any of these to
4547 see if it work.&lt;/p&gt;
4548
4549 &lt;p&gt;If you want to help implementing a system to let us propose what
4550 packages to install when new hardware is plugged into a Debian
4551 machine, please send me an email or talk to me on
4552 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4553 </description>
4554 </item>
4555
4556 <item>
4557 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4558 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4559 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4560 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4561 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4562 information, to find the packages that support a given piece of
4563 hardware, I refreshed my memory regarding modalias values, and decided
4564 to document the details. Here are my findings so far, also available
4565 in
4566 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4567 Debian Edu subversion repository&lt;/a&gt;:
4568
4569 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4570
4571 &lt;p&gt;This document try to explain what the different types of modalias
4572 values stands for. It is in part based on information from
4573 &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;,
4574 &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;,
4575 &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
4576 &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;.
4577
4578 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4579 this shell script:&lt;/p&gt;
4580
4581 &lt;pre&gt;
4582 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4583 &lt;/pre&gt;
4584
4585 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4586 using modinfo:&lt;/p&gt;
4587
4588 &lt;pre&gt;
4589 % /sbin/modinfo psmouse | grep alias:
4590 alias: serio:ty05pr*id*ex*
4591 alias: serio:ty01pr*id*ex*
4592 %
4593 &lt;/pre&gt;
4594
4595 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4596
4597 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4598 Bridge memory controller:&lt;/p&gt;
4599
4600 &lt;p&gt;&lt;blockquote&gt;
4601 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4602 &lt;/blockquote&gt;&lt;/p&gt;
4603
4604 &lt;p&gt;This represent these values:&lt;/p&gt;
4605
4606 &lt;pre&gt;
4607 v 00008086 (vendor)
4608 d 00002770 (device)
4609 sv 00001028 (subvendor)
4610 sd 000001AD (subdevice)
4611 bc 06 (bus class)
4612 sc 00 (bus subclass)
4613 i 00 (interface)
4614 &lt;/pre&gt;
4615
4616 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4617 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4618 0600. The 0600 class is a host bridge. Other useful bus values are
4619 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4620
4621 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4622 means.&lt;/p&gt;
4623
4624 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4625
4626 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4627 USB hub in a laptop:&lt;/p&gt;
4628
4629 &lt;p&gt;&lt;blockquote&gt;
4630 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4631 &lt;/blockquote&gt;&lt;/p&gt;
4632
4633 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4634
4635 &lt;pre&gt;
4636 v 1D6B (device vendor)
4637 p 0001 (device product)
4638 d 0206 (bcddevice)
4639 dc 09 (device class)
4640 dsc 00 (device subclass)
4641 dp 00 (device protocol)
4642 ic 09 (interface class)
4643 isc 00 (interface subclass)
4644 ip 00 (interface protocol)
4645 &lt;/pre&gt;
4646
4647 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4648 class is in the interface class section. For a simple USB web camera,
4649 these alias entries show up:&lt;/p&gt;
4650
4651 &lt;p&gt;&lt;blockquote&gt;
4652 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4653 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4654 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4655 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4656 &lt;/blockquote&gt;&lt;/p&gt;
4657
4658 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4659 camera), 0101 is audio control device and 0102 is audio streaming (aka
4660 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4661
4662 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4663
4664 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4665 receiver in a Thinkpad X40:&lt;/p&gt;
4666
4667 &lt;p&gt;&lt;blockquote&gt;
4668 acpi:IBM0071:PNP0511:
4669 &lt;/blockquote&gt;&lt;/p&gt;
4670
4671 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4672
4673 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4674
4675 &lt;p&gt;The DMI table contain lots of information about the computer case
4676 and model. This is an entry for a IBM Thinkpad X40, fetched from
4677 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4678
4679 &lt;p&gt;&lt;blockquote&gt;
4680 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4681 &lt;/blockquote&gt;&lt;/p&gt;
4682
4683 &lt;p&gt;The values present are&lt;/p&gt;
4684
4685 &lt;pre&gt;
4686 bvn IBM (BIOS vendor)
4687 bvr 1UETB6WW(1.66) (BIOS version)
4688 bd 06/15/2005 (BIOS date)
4689 svn IBM (system vendor)
4690 pn 2371H4G (product name)
4691 pvr ThinkPadX40 (product version)
4692 rvn IBM (board vendor)
4693 rn 2371H4G (board name)
4694 rvr NotAvailable (board version)
4695 cvn IBM (chassis vendor)
4696 ct 10 (chassis type)
4697 cvr NotAvailable (chassis version)
4698 &lt;/pre&gt;
4699
4700 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4701 found in the dmidecode source:&lt;/p&gt;
4702
4703 &lt;pre&gt;
4704 3 Desktop
4705 4 Low Profile Desktop
4706 5 Pizza Box
4707 6 Mini Tower
4708 7 Tower
4709 8 Portable
4710 9 Laptop
4711 10 Notebook
4712 11 Hand Held
4713 12 Docking Station
4714 13 All In One
4715 14 Sub Notebook
4716 15 Space-saving
4717 16 Lunch Box
4718 17 Main Server Chassis
4719 18 Expansion Chassis
4720 19 Sub Chassis
4721 20 Bus Expansion Chassis
4722 21 Peripheral Chassis
4723 22 RAID Chassis
4724 23 Rack Mount Chassis
4725 24 Sealed-case PC
4726 25 Multi-system
4727 26 CompactPCI
4728 27 AdvancedTCA
4729 28 Blade
4730 29 Blade Enclosing
4731 &lt;/pre&gt;
4732
4733 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4734 table. For example my home server is a tower, but the DMI modalias
4735 claim it is a desktop.&lt;/p&gt;
4736
4737 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4738
4739 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4740 test machine:&lt;/p&gt;
4741
4742 &lt;p&gt;&lt;blockquote&gt;
4743 serio:ty01pr00id00ex00
4744 &lt;/blockquote&gt;&lt;/p&gt;
4745
4746 &lt;p&gt;The values present are&lt;/p&gt;
4747
4748 &lt;pre&gt;
4749 ty 01 (type)
4750 pr 00 (prototype)
4751 id 00 (id)
4752 ex 00 (extra)
4753 &lt;/pre&gt;
4754
4755 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4756 the valid values are.&lt;/p&gt;
4757
4758 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4759
4760 &lt;p&gt;There are heaps of other modalias subtypes according to
4761 file2alias.c. There is the rest of the list from that source: amba,
4762 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4763 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4764 vmbus, x86cpu and zorro. I did not spend time documenting all of
4765 these, as they do not seem relevant for my intended use with mapping
4766 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4767
4768 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4769
4770 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4771 one can use the following shell script:&lt;/p&gt;
4772
4773 &lt;pre&gt;
4774 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4775 echo &quot;$id&quot; ; \
4776 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4777 done
4778 &lt;/pre&gt;
4779
4780 &lt;p&gt;The output can look like this (only the first few entries as the
4781 list is very long on my test machine):&lt;/p&gt;
4782
4783 &lt;pre&gt;
4784 acpi:ACPI0003:
4785 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4786 acpi:device:
4787 FATAL: Module acpi:device: not found.
4788 acpi:IBM0068:
4789 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4790 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4791 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4792 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4793 acpi:IBM0071:PNP0511:
4794 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4795 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4796 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4797 [...]
4798 &lt;/pre&gt;
4799
4800 &lt;p&gt;If you want to help implementing a system to let us propose what
4801 packages to install when new hardware is plugged into a Debian
4802 machine, please send me an email or talk to me on
4803 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4804
4805 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4806 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4807 in /sys/ with space in them.&lt;/p&gt;
4808 </description>
4809 </item>
4810
4811 <item>
4812 <title>Moved the pymissile Debian packaging to collab-maint</title>
4813 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4814 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4815 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4816 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4817 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4818 Launcher and updated the Debian package
4819 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4820 sure udev will fix the device permissions when it is plugged in. I
4821 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4822 hopefully make the package be proposed by jockey in Ubuntu when a user
4823 plug in his rocket launcher. In the process I moved the source to a
4824 git repository under collab-maint, to make it easier for any DD to
4825 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4826 is not very active, but the software still work for me even after five
4827 years of relative silence. The new git repository is not listed in
4828 the uploaded package yet, because I want to test the other changes a
4829 bit more before I upload the new version. If you want to check out
4830 the new version with a .desktop file included, visit the
4831 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4832 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4833 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4834 </description>
4835 </item>
4836
4837 <item>
4838 <title>Lets make hardware dongles easier to use in Debian</title>
4839 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4840 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4841 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4842 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4843 general, is that there is a great package management system with the
4844 ability to automatically install software packages by downloading them
4845 from the distribution mirrors, but no way to get it to automatically
4846 install the packages I need to use the hardware I plug into my
4847 machine. Even if the package to use it is easily available from the
4848 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4849 suggest to automatically install the python-nxt, nbc and t2n packages
4850 I need to talk to it. When I plug in a Yubikey, it could propose the
4851 yubikey-personalization package. The information required to do this
4852 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4853
4854 &lt;p&gt;Some years ago, I proposed to
4855 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4856 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4857 simple:
4858
4859 &lt;ul&gt;
4860
4861 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4862 starting when a user log in.&lt;/li&gt;
4863
4864 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4865 hardware is inserted into the computer.&lt;/li&gt;
4866
4867 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4868 database mapping to packages, and take note of any non-installed
4869 packages.&lt;/li&gt;
4870
4871 &lt;li&gt;Show a message to the user proposing to install the discovered
4872 package, and make it easy to install it.&lt;/li&gt;
4873
4874 &lt;/ul&gt;
4875
4876 &lt;p&gt;I am not sure what the best way to implement this is, but my
4877 initial idea was to use dbus events to discover new hardware, the
4878 discover database to find packages and
4879 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4880 packages.&lt;/p&gt;
4881
4882 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4883 draft package is now checked into
4884 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4885 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4886 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4887 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4888 the relevant packages in Debian, and uploaded a new version
4889 2.2013.01.09 to unstable. I also discovered that the current
4890 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4891 package in Debian no longer discovered any USB devices, because
4892 /proc/bus/usb/devices is no longer present. I ported it to use
4893 libusb as a fall back option to get it working. The fixed package
4894 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4895 because of the freeze).&lt;/p&gt;
4896
4897 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4898 desktop notification to show up (only once, the first time it is
4899 inserted):&lt;/p&gt;
4900
4901 &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;
4902
4903 &lt;p&gt;For this prototype to be really useful, some way to automatically
4904 install the proposed packages by pressing the &quot;Please install
4905 program(s)&quot; button should to be implemented.&lt;/p&gt;
4906
4907 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4908 happen, please help me update the discover-data database with mappings
4909 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4910 list the package you would like to have installed when a given
4911 hardware device is inserted into your computer, and report bugs using
4912 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4913 such mapping, please let me know.&lt;/p&gt;
4914
4915 &lt;p&gt;This prototype need more work, and there are several questions that
4916 should be considered before it is ready for production use. Is dbus
4917 the correct way to detect new hardware? At the moment I look for HAL
4918 dbus events on the system bus, because that is the events I could see
4919 on my Debian Squeeze KDE desktop. Are there better events to use?
4920 How should the user be notified? Is the desktop notification
4921 mechanism the best option, or should the background daemon raise a
4922 popup instead? How should packages be installed? When should they
4923 not be installed?&lt;/p&gt;
4924
4925 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4926 please send me an email. :)&lt;/p&gt;
4927 </description>
4928 </item>
4929
4930 <item>
4931 <title>New IRC channel for LEGO designers using Debian</title>
4932 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4933 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4934 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4935 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4936 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4937 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4938 discovered I had to build all the tools myself because none were
4939 already in Debian Squeeze. If Debian support for LEGO is something
4940 you care about, please join me on the IRC channel
4941 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4942 irc.debian.org). There is a lot that could be done to improve the
4943 Debian support for LEGO designers. For example both CAD software
4944 and Mindstorm compilers are missing. :)&lt;/p&gt;
4945
4946 &lt;p&gt;Update 2012-01-03: A
4947 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4948 including links to Lego related packages is now available.&lt;/p&gt;
4949 </description>
4950 </item>
4951
4952 <item>
4953 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4954 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4955 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4956 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4957 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4958 year! I hope next year will prove to be a good year.&lt;/p&gt;
4959
4960 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4961 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4962 between each other with minimal overhead, is a very interesting
4963 experiment. And as I wrote a few days ago, the bitcoin situation in
4964 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4965 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4966 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4967 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4968 for one of the ftpmasters to approve the new bitcoin-qt package
4969 name.&lt;/p&gt;
4970
4971 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4972 team in Debian, you can easily test the package in Debian Squeeze
4973 using the following steps to get a set of working packages:&lt;/p&gt;
4974
4975 &lt;blockquote&gt;&lt;pre&gt;
4976 git clone git://git.debian.org/git/collab-maint/bitcoin
4977 cd bitcoin
4978 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4979 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4980 &lt;/pre&gt;&lt;/blockquote&gt;
4981
4982 &lt;p&gt;You might have to install some build dependencies as well. The
4983 list of commands should give you two packages, bitcoind and
4984 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4985 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4986 around 5.6 GiB of data on my machine at the moment. Make sure your
4987 ~/.bitcoin/ directory have lots of spare room if you want to download
4988 all the blocks. The client will warn if the disk is getting full, so
4989 there is not really a problem if you got too little room, but you will
4990 not be able to get all the features out of the client.&lt;/p&gt;
4991
4992 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4993 activities, please send Bitcoin donations to my address
4994 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4995 </description>
4996 </item>
4997
4998 <item>
4999 <title>A word on bitcoin support in Debian</title>
5000 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
5001 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
5002 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
5003 <description>&lt;p&gt;It has been a while since I wrote about
5004 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
5005 peer-to-peer based crypto-currency, and the reason is simply that I
5006 have been busy elsewhere. But two days ago, I started looking at the
5007 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
5008 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
5009 is now maintained by a
5010 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
5011 people&lt;/a&gt;, and the grunt work had already been done by this team. We
5012 owe a huge thank you to all these team members. :)
5013 But I was sad to discover that the bitcoin client is missing in
5014 Wheezy. It is only available in Sid (and an outdated client from
5015 backports). The client had several RC bugs registered in BTS blocking
5016 it from entering testing. To try to help the team and improve the
5017 situation, I spent some time providing patches and triaging the bug
5018 reports. I also had a look at the bitcoin package available from Matt
5019 Corallo in a
5020 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
5021 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
5022 Debian package.&lt;/p&gt;
5023
5024 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
5025 IRC, I pushed several patches into the collab-maint git repository to
5026 improve the package. It now contains fixes for the RC issues (not from
5027 me, but fixed by Scott Howard), build rules for a Qt GUI client
5028 package, konqueror support for the bitcoin: URI and bash completion
5029 setup. As I work on Debian Squeeze, I also created
5030 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
5031 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
5032 it and try to integrate it into the git repository before uploading a
5033 new version to unstable.
5034
5035 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
5036 centralized control currently exercised in the monetary system. I
5037 find it completely unacceptable that the USA government is collecting
5038 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5039 that the major credit card companies can block legal money
5040 transactions to Wikileaks. But for bitcoin to succeed, more people
5041 need to use bitcoins, and more people need to accept bitcoins when
5042 they sell products and services. Improving the bitcoin support in
5043 Debian is a small step in the right direction, but not enough.
5044 Unfortunately the user experience when browsing the web and wanting to
5045 pay with bitcoin is still not very good. The bitcoin: URI is a step
5046 in the right direction, but need to work in most or every browser in
5047 use. Also the bitcoin-qt client is too heavy to fire up to do a
5048 quick transaction. I believe there are other clients available, but
5049 have not tested them.&lt;/p&gt;
5050
5051 &lt;p&gt;My
5052 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
5053 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
5054 I received 20.15 BTC so far on the address I provided in my blog two
5055 years ago, as can be
5056 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
5057 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
5058 donation. The blockexplorer service demonstrates quite well that
5059 bitcoin is not quite anonymous and untracked. :) I wonder if the
5060 number of users have gone up since then. If you use bitcoin and want
5061 to show your support of my activity, please send Bitcoin donations to
5062 the same address as last time,
5063 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5064 </description>
5065 </item>
5066
5067 <item>
5068 <title>Git repository for song book for Computer Scientists</title>
5069 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
5070 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
5071 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
5072 <description>&lt;p&gt;As I
5073 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
5074 this summer&lt;/a&gt;, I have created a Computer Science song book a few
5075 years ago, and today I finally found time to create a public
5076 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
5077 repository for the project&lt;/a&gt;.&lt;/p&gt;
5078
5079 &lt;p&gt;If you want to help out, please clone the source and submit patches
5080 to the HTML version. To generate the PDF and PostScript version,
5081 please use prince XML, or let me know about a useful free software
5082 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
5083
5084 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
5085 PostScript formats at
5086 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
5087 Science Songbook&lt;/a&gt;.&lt;/p&gt;
5088 </description>
5089 </item>
5090
5091 <item>
5092 <title>Gratulerer med 19-årsdagen, Debian!</title>
5093 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
5094 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
5095 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
5096 <description>&lt;p&gt;I dag fyller
5097 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
5098 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
5099 si gratulerer med dagen, Debian!&lt;/p&gt;
5100 </description>
5101 </item>
5102
5103 <item>
5104 <title>Song book for Computer Scientists</title>
5105 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
5106 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
5107 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
5108 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
5109 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
5110 collecting computer related songs for use at parties. The original
5111 version was written in LaTeX, but a few years ago I got help from
5112 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5113 while keeping the ability to create a nice book in PDF format. I have
5114 not had time to maintain the book for a while now, and guess I should
5115 put it up on some public version control repository where others can
5116 help me extend and update the book. If anyone is volunteering to help
5117 me with this, send me an email. Also let me know if there are songs
5118 missing in my book.&lt;/p&gt;
5119
5120 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
5121 me today that I really should let all my readers share the joys of
5122 singing out load about programming, computers and computer networks.
5123 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
5124 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
5125 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
5126 Computer Science Songbook&lt;/a&gt;.
5127 </description>
5128 </item>
5129
5130 <item>
5131 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
5132 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
5133 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
5134 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
5135 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
5136 around 1000 at the moment. To be able to get help from the vendors
5137 when something go wrong, we want to keep the firmware on the servers
5138 up to date. If the firmware isn&#39;t the latest and greatest, the
5139 vendors typically refuse to start debugging any problems until the
5140 firmware is upgraded. So before every reboot, we want to upgrade the
5141 firmware, and we would really like everyone handling servers at the
5142 university to do this themselves when they plan to reboot a machine.
5143 For that to happen we at the unix server admin group need to provide
5144 the tools to do so.&lt;/p&gt;
5145
5146 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
5147 fetch and install the latest firmware for the servers we got. Most of
5148 our hardware are from Dell and HP, so I have focused on these servers
5149 so far. This blog post is about the Dell part.&lt;/P&gt;
5150
5151 &lt;p&gt;On the Dell FTP site I was lucky enough to find
5152 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
5153 with firmware information for all 11th generation servers, listing
5154 which firmware should be used on a given model and where on the FTP
5155 site I can find it. Using a simple perl XML parser I can then
5156 download the shell scripts Dell provides to do firmware upgrades from
5157 within Linux and reboot when all the firmware is primed and ready to
5158 be activated on the first reboot.&lt;/p&gt;
5159
5160 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
5161 Are there anyone working on similar tools for firmware upgrading all
5162 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
5163
5164 &lt;p&gt;&lt;pre&gt;
5165 #!/usr/bin/perl
5166 use strict;
5167 use warnings;
5168 use File::Temp qw(tempdir);
5169 BEGIN {
5170 # Install needed RHEL packages if missing
5171 my %rhelmodules = (
5172 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
5173 );
5174 for my $module (keys %rhelmodules) {
5175 eval &quot;use $module;&quot;;
5176 if ($@) {
5177 my $pkg = $rhelmodules{$module};
5178 system(&quot;yum install -y $pkg&quot;);
5179 eval &quot;use $module;&quot;;
5180 }
5181 }
5182 }
5183 my $errorsto = &#39;pere@hungry.com&#39;;
5184
5185 upgrade_dell();
5186
5187 exit 0;
5188
5189 sub run_firmware_script {
5190 my ($opts, $script) = @_;
5191 unless ($script) {
5192 print STDERR &quot;fail: missing script name\n&quot;;
5193 exit 1
5194 }
5195 print STDERR &quot;Running $script\n\n&quot;;
5196
5197 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
5198 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
5199 } else {
5200 print STDERR &quot;fail: firmware script returned error\n&quot;;
5201 }
5202 }
5203
5204 sub run_firmware_scripts {
5205 my ($opts, @dirs) = @_;
5206 # Run firmware packages
5207 for my $dir (@dirs) {
5208 print STDERR &quot;info: Running scripts in $dir\n&quot;;
5209 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
5210 while (my $s = readdir $dh) {
5211 next if $s =~ m/^\.\.?/;
5212 run_firmware_script($opts, &quot;$dir/$s&quot;);
5213 }
5214 closedir $dh;
5215 }
5216 }
5217
5218 sub download {
5219 my $url = shift;
5220 print STDERR &quot;info: Downloading $url\n&quot;;
5221 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
5222 }
5223
5224 sub upgrade_dell {
5225 my @dirs;
5226 my $product = `dmidecode -s system-product-name`;
5227 chomp $product;
5228
5229 if ($product =~ m/PowerEdge/) {
5230
5231 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5232 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
5233
5234 my $tmpdir = tempdir(
5235 CLEANUP =&gt; 1
5236 );
5237 chdir($tmpdir);
5238 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
5239 system(&#39;gunzip Catalog.xml.gz&#39;);
5240 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
5241 # -q is quiet, disabling interactivity and reducing console output
5242 my $fwopts = &quot;-q&quot;;
5243 if (@paths) {
5244 for my $url (@paths) {
5245 fetch_dell_fw($url);
5246 }
5247 run_firmware_scripts($fwopts, $tmpdir);
5248 } else {
5249 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5250 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5251 }
5252 chdir(&#39;/&#39;);
5253 } else {
5254 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5255 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5256 }
5257 }
5258
5259 sub fetch_dell_fw {
5260 my $path = shift;
5261 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
5262 download($url);
5263 }
5264
5265 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5266 # firmware packages to download from Dell. Only work for Linux
5267 # machines and 11th generation Dell servers.
5268 sub fetch_dell_fw_list {
5269 my $filename = shift;
5270
5271 my $product = `dmidecode -s system-product-name`;
5272 chomp $product;
5273 my ($mybrand, $mymodel) = split(/\s+/, $product);
5274
5275 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
5276
5277 my $xml = XMLin($filename);
5278 my @paths;
5279 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
5280 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
5281 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
5282 my $oscode;
5283 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
5284 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
5285 } else {
5286 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
5287 }
5288 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
5289 {
5290 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
5291 }
5292 }
5293 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
5294 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
5295
5296 # Drop application packages, only firmware and BIOS
5297 next if &#39;APAC&#39; eq $componenttype;
5298
5299 my $cpath = $component-&gt;{path};
5300 for my $path (@paths) {
5301 if ($cpath =~ m%/$path$%) {
5302 push(@paths, $cpath);
5303 }
5304 }
5305 }
5306 return @paths;
5307 }
5308 &lt;/pre&gt;
5309
5310 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5311 it could work on other platforms with some tweaking. Anyone know a
5312 index like Catalog.xml is available from HP for HP servers? At the
5313 moment I maintain a similar list manually and it is quickly getting
5314 outdated.&lt;/p&gt;
5315 </description>
5316 </item>
5317
5318 <item>
5319 <title>How is booting into runlevel 1 different from single user boots?</title>
5320 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5321 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5322 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5323 <description>&lt;p&gt;Wouter Verhelst have some
5324 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5325 comments and opinions&lt;/a&gt; on my blog post on
5326 &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
5327 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5328 &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
5329 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5330 small piece of his comment now, and though it best to address the
5331 misunderstanding he bring forward:&lt;/p&gt;
5332
5333 &lt;p&gt;&lt;blockquote&gt;
5334 Currently, a system admin has four options: [...] boot to a
5335 single-user system (by adding &#39;single&#39; to the kernel command line;
5336 this runs rcS and rc1 scripts)
5337 &lt;/blockquote&gt;&lt;/p&gt;
5338
5339 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5340 and booting into runlevel 1 is the same. I am not surprised he
5341 believe this, because it would make sense and is a quite sensible
5342 thing to believe. But because the boot in Debian is slightly broken,
5343 runlevel 1 do not work properly and it isn&#39;t the same as single user
5344 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5345 hard to explain.&lt;/p&gt;
5346
5347 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5348 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5349 executed in single user mode is sulogin. Single user mode is a boot
5350 state &quot;between&quot; the runlevels, and when booting into single user mode,
5351 only the scripts in /etc/rcS.d/ are executed before the init process
5352 enters the single user state. When switching to runlevel 1, the state
5353 is in fact not ending in runlevel 1, but it passes through runlevel 1
5354 and end up in the single user mode (see /etc/rc1.d/S03single, which
5355 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5356 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5357 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5358 mode).&lt;/p&gt;
5359
5360 &lt;p&gt;This summary might make it clearer. When booting for the first
5361 time into single user mode, the following commands are executed:
5362 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5363 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5364 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5365 trying to continue after visiting single user mode. Not all services
5366 are started again as they should, causing the machine to end up in an
5367 unpredicatble state. This is why Debian admins recommend rebooting
5368 after visiting single user mode.&lt;/p&gt;
5369
5370 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5371 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5372 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5373 stopped when passing through the scripts in /etc/rc1.d/, and not
5374 started again when switching away from runlevel 1 to the runlevels
5375 2-5. I believe the problem is best fixed by moving all the scripts
5376 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5377 functioning single user mode during boot.&lt;/p&gt;
5378
5379 &lt;p&gt;I have spent several years investigating the Debian boot system,
5380 and discovered this problem a few years ago. I suspect it originates
5381 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5382 </description>
5383 </item>
5384
5385 <item>
5386 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5387 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5389 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5390 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5391 are started from /etc/rcS.d/. In fact, there is a bite more of them
5392 than make sense, and this causes a few problems. What kind of
5393 problems, you might ask. There are at least two problems. The first
5394 is that it is not possible to recover a machine after switching to
5395 runlevel 1. One need to actually reboot to get the machine back to
5396 the expected state. The other is that single user boot will sometimes
5397 run into problems because some of the subsystems are activated before
5398 the root login is presented, causing problems when trying to recover a
5399 machine from a problem in that subsystem. A minor additional point is
5400 that moving more scripts out of rcS.d/ and into the other rc#.d/
5401 directories will increase the amount of scripts that can run in
5402 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5403
5404 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5405 scripts that _have_ to execute before the root login prompt is
5406 presented during a single user boot should go there. Everything else
5407 should go into the numeric runlevels. This means things like
5408 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5409 the numeric runlevels. Today in Debian, there are around 115 init.d
5410 scripts that are started from rcS.d/, and most of them should be moved
5411 out. Do your package have one of them? Please help us make single
5412 user and runlevel 1 better by moving it.&lt;/p&gt;
5413
5414 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5415 etc. should still be started from rcS.d/, but there is for example no
5416 need to have the network enabled before the single user login prompt
5417 is presented.&lt;/p&gt;
5418
5419 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5420 Debian systems working while scripts migrate and during upgrades, the
5421 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5422 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5423 and the next ones can only be moved when their dependencies have been
5424 moved first. This migration must be done sequentially while we ensure
5425 that the package system upgrade packages in the right order to keep
5426 the system state correct. This will require some coordination when it
5427 comes to network related packages, but most of the packages with
5428 scripts that should migrate do not have anything in rcS.d/ depending
5429 on them. Some packages have already been updated, like the sudo
5430 package, while others are still left to do. I wish I had time to work
5431 on this myself, but real live constrains make it unlikely that I will
5432 find time to push this forward.&lt;/p&gt;
5433 </description>
5434 </item>
5435
5436 <item>
5437 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5438 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5439 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5440 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5441 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5442 mentioned the issues I believe should be improved in Debian for its
5443 desktop to be useful for more people. The use case for this is my
5444 parents, which are currently running Kubuntu which solve the
5445 issues.&lt;/p&gt;
5446
5447 &lt;p&gt;I suspect these four missing features are not very hard to
5448 implement. After all, they are present in Ubuntu, so if we wanted to
5449 do this in Debian we would have a source.&lt;/p&gt;
5450
5451 &lt;ol&gt;
5452
5453 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5454 are new packages available for upgrades, a icon in the KDE status bar
5455 indicate this, and clicking on it will activate the simple upgrade
5456 tool to handle it. I have no problem guiding both of my parents
5457 through the process over the phone. If a kernel reboot is required,
5458 this too is indicated by the status bars and the upgrade tool. Last
5459 time I checked, nothing with the same features was working in KDE in
5460 Debian.&lt;/li&gt;
5461
5462 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5463 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5464 currently have a handler for, it will ask the user if the system
5465 should search for a package that would add support for this MIME type,
5466 and if the user say yes, the APT sources will be searched for packages
5467 advertising the MIME type in their control file (visible in the
5468 Packages file in the APT archive). If one or more packages are found,
5469 it is a simple click of the mouse to add support for the missing mime
5470 type. If the package require the user to accept some non-free
5471 license, this is explained to the user. The entire process make it
5472 more clear to the user why something do not work in the browser, and
5473 make the chances higher for the user to blame the web page authors and
5474 not the browser for any missing features.&lt;/li&gt;
5475
5476 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5477 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5478 it is not supporting, a dialog pop up asking the user if the system
5479 should search for a package that would add support for it. This
5480 happen with things like MP3, Windows Media or H.264. The selection
5481 and installation procedure is very similar to the Firefox browser
5482 plugin handling. This is as far as I know implemented using a
5483 gstreamer hook. The end result is that the user easily get access to
5484 the codecs that are present from the APT archives available, while
5485 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5486
5487 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5488 displaying a text/plain file in my Debian browser, it will propose to
5489 start emacs to show it. If I remember correctly, when doing the same
5490 in Kunbutu it show the file as a text file in the browser. At least I
5491 know Opera will show text files within the browser. I much prefer the
5492 latter behaviour.&lt;/li&gt;
5493
5494 &lt;/ol&gt;
5495
5496 &lt;p&gt;There are other nice features as well, like the simplified suite
5497 upgrader, but given that I am the one mostly doing the dist-upgrade,
5498 it do not matter much.&lt;/p&gt;
5499
5500 &lt;p&gt;I really hope we could get these features in place for the next
5501 Debian release. It would require the coordinated effort of several
5502 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5503 </description>
5504 </item>
5505
5506 <item>
5507 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5508 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5509 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5510 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5511 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5512 site is build on Debian/Squeeze, and this platform was chosen because
5513 I am most familiar with Debian (being a Debian Developer for around 10
5514 years) because it is the latest stable Debian release which should get
5515 security support for a few years.&lt;/p&gt;
5516
5517 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5518 that are missing in Debian at the moment. It would be great if these
5519 modules were added to the Debian archive, allowing anyone to set up
5520 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5521 in their own country using only Debian packages. The list of modules
5522 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5523 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5524 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5525 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5526 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5527 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5528 easier in the future.&lt;/p&gt;
5529
5530 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5531 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5532 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5533 with the responsibility of tracking security problems, which I really
5534 do not have time for.&lt;/p&gt;
5535 </description>
5536 </item>
5537
5538 <item>
5539 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5540 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5541 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5542 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5543 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5544 posts have been in Norwegian the last few weeks, so here is a short
5545 update in English.&lt;/p&gt;
5546
5547 &lt;p&gt;The kids still keep me too busy to get much free software work
5548 done, but I did manage to organise a project to get a Norwegian port
5549 of the British service
5550 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5551 and it has been running for a month now. The entire project has been
5552 organised by me and two others. Around Christmas we gathered sponsors
5553 to fund the development work. In January I drafted a contract with
5554 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5555 and in February the development took place. Most of it involved
5556 converting the source to use GPS coordinates instead of British
5557 easting/northing, and the resulting code should be a lot easier to get
5558 running in any country by now. The Norwegian
5559 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5560 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5561 source and the source for administrative borders in Norway, and
5562 support for this had to be added/fixed.&lt;/p&gt;
5563
5564 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5565 polishing the system before we announced it March 7th. The system is
5566 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5567 problem reports in a few weeks. Soon we hope to announce the Android
5568 and iPhone versions making it even easier to report problems with the
5569 public infrastructure.&lt;/p&gt;
5570
5571 &lt;p&gt;Perhaps something to consider for those of you in countries without
5572 such service?&lt;/p&gt;
5573 </description>
5574 </item>
5575
5576 <item>
5577 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5578 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5579 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5580 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5581 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5582 issues here at my work with the University of Oslo. My idea is that
5583 it should be possible to use the information about security issues
5584 available on the Internet, and check our locally
5585 maintained/distributed software against this information. It should
5586 allow us to verify that no known security issues are forgotten. The
5587 CVE database listing vulnerabilities seem like a great central point,
5588 and by using the package lists from Debian mapped to CVEs provided by
5589 the testing security team, I believed it should be possible to figure
5590 out which security holes were present in our free software
5591 collection.&lt;/p&gt;
5592
5593 &lt;p&gt;After reading up on the topic, it became obvious that the first
5594 building block is to be able to name software packages in a unique and
5595 consistent way across data sources. I considered several ways to do
5596 this, for example coming up with my own naming scheme like using URLs
5597 to project home pages or URLs to the Freshmeat entries, or using some
5598 existing naming scheme. And it seem like I am not the first one to
5599 come across this problem, as MITRE already proposed and implemented a
5600 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5601 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5602 software, hardware and other platform components. The CPE ids are
5603 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5604 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5605 issues for any CPE name. With this in place, all I need to do is to
5606 locate the CPE id for the software packages we use at the university.
5607 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5608 NVD entry if a CVE for the package exist).&lt;/p&gt;
5609
5610 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5611 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5612 check out, one could look up
5613 &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
5614 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5615 The most recent one is
5616 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5617 and at the bottom of the NVD page for this vulnerability the complete
5618 list of affected versions is provided.&lt;/p&gt;
5619
5620 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5621 for offline processing of issues. Using this dump, I&#39;ve written a
5622 small script taking a list of CPEs as input and list all CVEs
5623 affecting the packages represented by these CPEs. One give it CPEs
5624 with version numbers as specified above and get a list of open
5625 security issues out.&lt;/p&gt;
5626
5627 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5628 information need to be high. For that to happen, I believe as many as
5629 possible need to use and contribute to the NVD database. I notice
5630 RHEL is providing
5631 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5632 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5633 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5634
5635 &lt;p&gt;To get an idea about the quality for free software, I spent some
5636 time making it possible to compare the CVE database from Debian with
5637 the CVE database in NVD. The result look fairly good, but there are
5638 some inconsistencies in NVD (same software package having several
5639 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5640 Debian believe are affected by a CVE). Hope to find time to improve
5641 the quality of NVD, but that require being able to get in touch with
5642 someone maintaining it. So far my three emails with questions and
5643 corrections have not seen any reply, but I hope contact can be
5644 established soon.&lt;/p&gt;
5645
5646 &lt;p&gt;An interesting application for CPEs is cross platform package
5647 mapping. It would be useful to know which packages in for example
5648 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5649 this would be trivial if all linux distributions provided CPE entries
5650 for their packages.&lt;/p&gt;
5651 </description>
5652 </item>
5653
5654 <item>
5655 <title>Which module is loaded for a given PCI and USB device?</title>
5656 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5657 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5658 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5659 <description>&lt;p&gt;In the
5660 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5661 package in Debian, there is a script to report useful information
5662 about the running hardware for use when people report missing
5663 information. One part of this script that I find very useful when
5664 debugging hardware problems, is the part mapping loaded kernel module
5665 to the PCI device it claims. It allow me to quickly see if the kernel
5666 module I expect is driving the hardware I am struggling with. To see
5667 the output, make sure discover-data is installed and run
5668 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5669 one of my machines like this:&lt;/p&gt;
5670
5671 &lt;pre&gt;
5672 loaded modules:
5673 10de:03eb i2c_nforce2
5674 10de:03f1 ohci_hcd
5675 10de:03f2 ehci_hcd
5676 10de:03f0 snd_hda_intel
5677 10de:03ec pata_amd
5678 10de:03f6 sata_nv
5679 1022:1103 k8temp
5680 109e:036e bttv
5681 109e:0878 snd_bt87x
5682 11ab:4364 sky2
5683 &lt;/pre&gt;
5684
5685 &lt;p&gt;The code in question look like this, slightly modified for
5686 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5687
5688 &lt;pre&gt;
5689 if [ -d /sys/bus/pci/devices/ ] ; then
5690 echo loaded pci modules:
5691 (
5692 cd /sys/bus/pci/devices/
5693 for address in * ; do
5694 if [ -d &quot;$address/driver/module&quot; ] ; then
5695 module=`cd $address/driver/module ; pwd -P | xargs basename`
5696 if grep -q &quot;^$module &quot; /proc/modules ; then
5697 address=$(echo $address |sed s/0000://)
5698 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5699 echo &quot;$id $module&quot;
5700 fi
5701 fi
5702 done
5703 )
5704 echo
5705 fi
5706 &lt;/pre&gt;
5707
5708 &lt;p&gt;Similar code could be used to extract USB device module
5709 mappings:&lt;/p&gt;
5710
5711 &lt;pre&gt;
5712 if [ -d /sys/bus/usb/devices/ ] ; then
5713 echo loaded usb modules:
5714 (
5715 cd /sys/bus/usb/devices/
5716 for address in * ; do
5717 if [ -d &quot;$address/driver/module&quot; ] ; then
5718 module=`cd $address/driver/module ; pwd -P | xargs basename`
5719 if grep -q &quot;^$module &quot; /proc/modules ; then
5720 address=$(echo $address |sed s/0000://)
5721 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5722 if [ &quot;$id&quot; ] ; then
5723 echo &quot;$id $module&quot;
5724 fi
5725 fi
5726 fi
5727 done
5728 )
5729 echo
5730 fi
5731 &lt;/pre&gt;
5732
5733 &lt;p&gt;This might perhaps be something to include in other tools as
5734 well.&lt;/p&gt;
5735 </description>
5736 </item>
5737
5738 <item>
5739 <title>How to test if a laptop is working with Linux</title>
5740 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5741 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5742 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5743 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5744 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5745 batch of computers will work with Linux. Every year for the last few
5746 years the university have organised shared bid of a few thousand
5747 computers, and this year HP won the bid. Two different desktops and
5748 five different laptops are on the list this year. We in the UNIX
5749 group want to know which one of these computers work well with RHEL
5750 and Ubuntu, the two Linux distributions we currently handle at the
5751 university.&lt;/p&gt;
5752
5753 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5754 perhaps inspire others to test hardware as well. To test, I PXE
5755 install the OS version of choice, and log in as my normal user and run
5756 a few applications and plug in selected pieces of hardware. When
5757 something fail, I make a note about this in the test matrix and move
5758 on. If I have some spare time I try to report the bug to the OS
5759 vendor, but as I only have the machines for a short time, I rarely
5760 have the time to do this for all the problems I find.&lt;/p&gt;
5761
5762 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5763 I perform on a new model.&lt;/p&gt;
5764
5765 &lt;ul&gt;
5766
5767 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5768 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5769 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5770
5771 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5772 installation, X.org is working.&lt;/li&gt;
5773
5774 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5775 package mesa-utils on Ubuntu) and writing down the frames per second
5776 reported by the program.&lt;/li&gt;
5777
5778 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5779 logging in, and if I can hear this the test is successful. If there
5780 are several audio exits on the machine, I try them all and check if
5781 the Gnome/KDE audio mixer can control where to send the sound. I
5782 normally test this by playing
5783 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5784 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5785
5786 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5787 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5788
5789 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5790 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5791
5792 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5793 picture from the v4l device show up.&lt;/li&gt;
5794
5795 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5796 any bluetooth devices are discovered. In my office, I normally see a
5797 few.&lt;/li&gt;
5798
5799 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5800 memory modules lying around, and stick them in and see if Gnome/KDE
5801 notice this.&lt;/li&gt;
5802
5803 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5804 special button work, and if the laptop continue to work after
5805 resume.&lt;/li&gt;
5806
5807 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5808 adjusting background light, switching on/off external video output,
5809 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5810 laptop to laptop, so I just write down which are working and which are
5811 not.&lt;/li&gt;
5812
5813 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5814 acceleration sensors etc. I rarely test these, as I do not know how
5815 to quickly test if they are working or not, so I only document their
5816 existence.&lt;/li&gt;
5817
5818 &lt;/ul&gt;
5819
5820 &lt;p&gt;By now I suspect you are really curious what the test results are
5821 for the HP machines I am testing. I&#39;m not done yet, so I will report
5822 the test results later. For now I can report that HP 8100 Elite work
5823 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5824 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5825 can see, I have most machines left to test. One interesting
5826 observation is that Ubuntu Lucid has almost twice the frame rate than
5827 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5828 </description>
5829 </item>
5830
5831 <item>
5832 <title>Some thoughts on BitCoins</title>
5833 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5834 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5835 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5836 <description>&lt;p&gt;As I continue to explore
5837 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5838 what properties the system have, and how it will be affected by laws
5839 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5840
5841 &lt;p&gt;One interesting thing to note is that since the transactions are
5842 verified using a peer to peer network, all details about a transaction
5843 is known to everyone. This means that if a BitCoin address has been
5844 published like I did with mine in my initial post about BitCoin, it is
5845 possible for everyone to see how many BitCoins have been transfered to
5846 that address. There is even a web service to look at the details for
5847 all transactions. There I can see that my address
5848 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5849 have received 16.06 Bitcoin, the
5850 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5851 address of Simon Phipps have received 181.97 BitCoin and the address
5852 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5853 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5854 every one of you that donated bitcoins to support my activity. The
5855 fact that anyone can see how much money was transfered to a given
5856 address make it more obvious why the BitCoin community recommend to
5857 generate and hand out a new address for each transaction. I&#39;m told
5858 there is no way to track which addresses belong to a given person or
5859 organisation without the person or organisation revealing it
5860 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5861
5862 &lt;p&gt;In Norway, and in most other countries, there are laws and
5863 regulations limiting how much money one can transfer across the border
5864 without declaring it. There are money laundering, tax and accounting
5865 laws and regulations I would expect to apply to the use of BitCoin.
5866 If the Skolelinux foundation
5867 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5868 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5869 normal bank transfers like EFF is doing, how should this be accounted?
5870 Given that it is impossible to know if money can cross the border or
5871 not, should everything or nothing be declared? What exchange rate
5872 should be used when calculating taxes? Would receivers have to pay
5873 income tax if the foundation were to pay Skolelinux contributors in
5874 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5875
5876 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5877 accepted by a lot of users. It must be possible to get easy access to
5878 the currency (as a wage or using currency exchanges), and it must be
5879 easy to spend it. At the moment BitCoin seem fairly easy to get
5880 access to, but there are very few places to spend it. I am not really
5881 a regular user of any of the vendor types currently accepting BitCoin,
5882 so I wonder when my kind of shop would start accepting BitCoins. I
5883 would like to buy electronics, travels and subway tickets, not herbs
5884 and books. :) The currency is young, and this will improve over time
5885 if it become popular, but I suspect regular banks will start to lobby
5886 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5887 will claim it is helping fund terrorism and money laundering (which
5888 probably would be true, as is any currency in existence), but I
5889 believe the problems should be solved elsewhere and not by blaming
5890 currencies.&lt;/p&gt;
5891
5892 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5893 CPU intensive process that depend on a bit of luck as well (as one is
5894 competing against all the other miners currently spending CPU cycles
5895 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5896 BitCoin when this happen. Yesterday I came across the obvious way to
5897 join forces to increase ones changes of getting at least some coins,
5898 by coordinating the work on mining BitCoins across several machines
5899 and people, and sharing the result if one is lucky and get the 50
5900 BitCoins. Check out
5901 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5902 if this sounds interesting. I have not had time to try to set up a
5903 machine to participate there yet, but have seen that running on ones
5904 own for a few days have not yield any BitCoins througth mining
5905 yet.&lt;/p&gt;
5906
5907 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5908 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5909 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5910 it was interesting to read. The arguments presented seem to be
5911 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5912 </description>
5913 </item>
5914
5915 <item>
5916 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5917 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5918 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5919 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5920 <description>&lt;p&gt;With this weeks lawless
5921 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5922 attacks&lt;/a&gt; on Wikileak and
5923 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5924 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5925 not be trusted to handle money transactions.
5926 A blog post from
5927 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5928 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5929 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5930 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5931 some help from my friend to get it all running, and he even handed me
5932 some bitcoins to get started. I even donated a few bitcoins to Simon
5933 for helping me remember BitCoin.&lt;/p&gt;
5934
5935 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5936 crypto-currency, decentralised and handled using peer-to-peer
5937 networks. It allows anonymous transactions and prohibits central
5938 control over the transactions, making it impossible for governments
5939 and companies alike to block donations and other transactions. The
5940 source is free software, and while the key dependency wxWidgets 2.9
5941 for the graphical user interface is missing in Debian, the command
5942 line client builds just fine. Hopefully Jonas
5943 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5944 Debian&lt;/a&gt; soon.&lt;/p&gt;
5945
5946 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5947 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5948 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5949 currency &quot;stock&quot; markets where the exchange rate is decided. There
5950 are not many users so far, but the concept seems promising. If you
5951 want to get started and lack a friend with any bitcoins to spare,
5952 you can even get
5953 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5954 bitcoin at the time of writing). Use
5955 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5956 on the current exchange rates.&lt;/p&gt;
5957
5958 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5959 machines. If you want to support my activity, please send Bitcoin
5960 donations to the address
5961 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5962 </description>
5963 </item>
5964
5965 <item>
5966 <title>Why isn&#39;t Debian Edu using VLC?</title>
5967 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5969 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5970 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5971 presented, and the winner among the multimedia player were VLC.
5972 Personally, I like VLC, and it is my player of choice when I first try
5973 to play a video file or stream. Only if VLC fail will I drag out
5974 gmplayer to see if it can do better. The reason is mostly the failure
5975 model and trust. When VLC fail, it normally pop up a error message
5976 reporting the problem. When mplayer fail, it normally segfault or
5977 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5978
5979 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5980 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5981 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5982 plugin to play web videos seamlessly, and the VLC browser plugin is
5983 not very good. For example, it lack in-line control buttons, so there
5984 is no way for the user to pause the video. Also, when I
5985 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5986 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5987 failed on several video pages where mplayer based plugins worked. If
5988 the browser plugin for VLC was as good as the gecko-mediaplayer
5989 package (which uses mplayer), we would switch.&lt;/P&gt;
5990
5991 &lt;p&gt;While VLC is a good player, its user interface is slightly
5992 annoying. The most annoying feature is its inconsistent use of
5993 keyboard shortcuts. When the player is in full screen mode, its
5994 shortcuts are different from when it is playing the video in a window.
5995 For example, space only work as pause when in full screen mode. I
5996 wish it had consisten shortcuts and that space also would work when in
5997 window mode. Another nice shortcut in gmplayer is [enter] to restart
5998 the current video. It is very nice when playing short videos from the
5999 web and want to restart it when new people arrive to have a look at
6000 what is going on.&lt;/p&gt;
6001 </description>
6002 </item>
6003
6004 <item>
6005 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
6006 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
6007 <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>
6008 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
6009 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
6010 upgrade testing of the
6011 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6012 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
6013 This seem like a very good idea, so I adjusted by test scripts and
6014 can now present the updated result from today:&lt;/p&gt;
6015
6016 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6017
6018 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6019
6020 &lt;blockquote&gt;&lt;p&gt;
6021 apache2.2-bin
6022 aptdaemon
6023 baobab
6024 binfmt-support
6025 browser-plugin-gnash
6026 cheese-common
6027 cli-common
6028 cups-pk-helper
6029 dmz-cursor-theme
6030 empathy
6031 empathy-common
6032 freedesktop-sound-theme
6033 freeglut3
6034 gconf-defaults-service
6035 gdm-themes
6036 gedit-plugins
6037 geoclue
6038 geoclue-hostip
6039 geoclue-localnet
6040 geoclue-manual
6041 geoclue-yahoo
6042 gnash
6043 gnash-common
6044 gnome
6045 gnome-backgrounds
6046 gnome-cards-data
6047 gnome-codec-install
6048 gnome-core
6049 gnome-desktop-environment
6050 gnome-disk-utility
6051 gnome-screenshot
6052 gnome-search-tool
6053 gnome-session-canberra
6054 gnome-system-log
6055 gnome-themes-extras
6056 gnome-themes-more
6057 gnome-user-share
6058 gstreamer0.10-fluendo-mp3
6059 gstreamer0.10-tools
6060 gtk2-engines
6061 gtk2-engines-pixbuf
6062 gtk2-engines-smooth
6063 hamster-applet
6064 libapache2-mod-dnssd
6065 libapr1
6066 libaprutil1
6067 libaprutil1-dbd-sqlite3
6068 libaprutil1-ldap
6069 libart2.0-cil
6070 libboost-date-time1.42.0
6071 libboost-python1.42.0
6072 libboost-thread1.42.0
6073 libchamplain-0.4-0
6074 libchamplain-gtk-0.4-0
6075 libcheese-gtk18
6076 libclutter-gtk-0.10-0
6077 libcryptui0
6078 libdiscid0
6079 libelf1
6080 libepc-1.0-2
6081 libepc-common
6082 libepc-ui-1.0-2
6083 libfreerdp-plugins-standard
6084 libfreerdp0
6085 libgconf2.0-cil
6086 libgdata-common
6087 libgdata7
6088 libgdu-gtk0
6089 libgee2
6090 libgeoclue0
6091 libgexiv2-0
6092 libgif4
6093 libglade2.0-cil
6094 libglib2.0-cil
6095 libgmime2.4-cil
6096 libgnome-vfs2.0-cil
6097 libgnome2.24-cil
6098 libgnomepanel2.24-cil
6099 libgpod-common
6100 libgpod4
6101 libgtk2.0-cil
6102 libgtkglext1
6103 libgtksourceview2.0-common
6104 libmono-addins-gui0.2-cil
6105 libmono-addins0.2-cil
6106 libmono-cairo2.0-cil
6107 libmono-corlib2.0-cil
6108 libmono-i18n-west2.0-cil
6109 libmono-posix2.0-cil
6110 libmono-security2.0-cil
6111 libmono-sharpzip2.84-cil
6112 libmono-system2.0-cil
6113 libmtp8
6114 libmusicbrainz3-6
6115 libndesk-dbus-glib1.0-cil
6116 libndesk-dbus1.0-cil
6117 libopal3.6.8
6118 libpolkit-gtk-1-0
6119 libpt2.6.7
6120 libpython2.6
6121 librpm1
6122 librpmio1
6123 libsdl1.2debian
6124 libsrtp0
6125 libssh-4
6126 libtelepathy-farsight0
6127 libtelepathy-glib0
6128 libtidy-0.99-0
6129 media-player-info
6130 mesa-utils
6131 mono-2.0-gac
6132 mono-gac
6133 mono-runtime
6134 nautilus-sendto
6135 nautilus-sendto-empathy
6136 p7zip-full
6137 pkg-config
6138 python-aptdaemon
6139 python-aptdaemon-gtk
6140 python-axiom
6141 python-beautifulsoup
6142 python-bugbuddy
6143 python-clientform
6144 python-coherence
6145 python-configobj
6146 python-crypto
6147 python-cupshelpers
6148 python-elementtree
6149 python-epsilon
6150 python-evolution
6151 python-feedparser
6152 python-gdata
6153 python-gdbm
6154 python-gst0.10
6155 python-gtkglext1
6156 python-gtksourceview2
6157 python-httplib2
6158 python-louie
6159 python-mako
6160 python-markupsafe
6161 python-mechanize
6162 python-nevow
6163 python-notify
6164 python-opengl
6165 python-openssl
6166 python-pam
6167 python-pkg-resources
6168 python-pyasn1
6169 python-pysqlite2
6170 python-rdflib
6171 python-serial
6172 python-tagpy
6173 python-twisted-bin
6174 python-twisted-conch
6175 python-twisted-core
6176 python-twisted-web
6177 python-utidylib
6178 python-webkit
6179 python-xdg
6180 python-zope.interface
6181 remmina
6182 remmina-plugin-data
6183 remmina-plugin-rdp
6184 remmina-plugin-vnc
6185 rhythmbox-plugin-cdrecorder
6186 rhythmbox-plugins
6187 rpm-common
6188 rpm2cpio
6189 seahorse-plugins
6190 shotwell
6191 software-center
6192 system-config-printer-udev
6193 telepathy-gabble
6194 telepathy-mission-control-5
6195 telepathy-salut
6196 tomboy
6197 totem
6198 totem-coherence
6199 totem-mozilla
6200 totem-plugins
6201 transmission-common
6202 xdg-user-dirs
6203 xdg-user-dirs-gtk
6204 xserver-xephyr
6205 &lt;/p&gt;&lt;/blockquote&gt;
6206
6207 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6208
6209 &lt;blockquote&gt;&lt;p&gt;
6210 cheese
6211 ekiga
6212 eog
6213 epiphany-extensions
6214 evolution-exchange
6215 fast-user-switch-applet
6216 file-roller
6217 gcalctool
6218 gconf-editor
6219 gdm
6220 gedit
6221 gedit-common
6222 gnome-games
6223 gnome-games-data
6224 gnome-nettool
6225 gnome-system-tools
6226 gnome-themes
6227 gnuchess
6228 gucharmap
6229 guile-1.8-libs
6230 libavahi-ui0
6231 libdmx1
6232 libgalago3
6233 libgtk-vnc-1.0-0
6234 libgtksourceview2.0-0
6235 liblircclient0
6236 libsdl1.2debian-alsa
6237 libspeexdsp1
6238 libsvga1
6239 rhythmbox
6240 seahorse
6241 sound-juicer
6242 system-config-printer
6243 totem-common
6244 transmission-gtk
6245 vinagre
6246 vino
6247 &lt;/p&gt;&lt;/blockquote&gt;
6248
6249 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6250
6251 &lt;blockquote&gt;&lt;p&gt;
6252 gstreamer0.10-gnomevfs
6253 &lt;/p&gt;&lt;/blockquote&gt;
6254
6255 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6256
6257 &lt;blockquote&gt;&lt;p&gt;
6258 [nothing]
6259 &lt;/p&gt;&lt;/blockquote&gt;
6260
6261 &lt;p&gt;This is for KDE:&lt;/p&gt;
6262
6263 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6264
6265 &lt;blockquote&gt;&lt;p&gt;
6266 ksmserver
6267 &lt;/p&gt;&lt;/blockquote&gt;
6268
6269 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6270
6271 &lt;blockquote&gt;&lt;p&gt;
6272 kwin
6273 network-manager-kde
6274 &lt;/p&gt;&lt;/blockquote&gt;
6275
6276 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6277
6278 &lt;blockquote&gt;&lt;p&gt;
6279 arts
6280 dolphin
6281 freespacenotifier
6282 google-gadgets-gst
6283 google-gadgets-xul
6284 kappfinder
6285 kcalc
6286 kcharselect
6287 kde-core
6288 kde-plasma-desktop
6289 kde-standard
6290 kde-window-manager
6291 kdeartwork
6292 kdeartwork-emoticons
6293 kdeartwork-style
6294 kdeartwork-theme-icon
6295 kdebase
6296 kdebase-apps
6297 kdebase-workspace
6298 kdebase-workspace-bin
6299 kdebase-workspace-data
6300 kdeeject
6301 kdelibs
6302 kdeplasma-addons
6303 kdeutils
6304 kdewallpapers
6305 kdf
6306 kfloppy
6307 kgpg
6308 khelpcenter4
6309 kinfocenter
6310 konq-plugins-l10n
6311 konqueror-nsplugins
6312 kscreensaver
6313 kscreensaver-xsavers
6314 ktimer
6315 kwrite
6316 libgle3
6317 libkde4-ruby1.8
6318 libkonq5
6319 libkonq5-templates
6320 libnetpbm10
6321 libplasma-ruby
6322 libplasma-ruby1.8
6323 libqt4-ruby1.8
6324 marble-data
6325 marble-plugins
6326 netpbm
6327 nuvola-icon-theme
6328 plasma-dataengines-workspace
6329 plasma-desktop
6330 plasma-desktopthemes-artwork
6331 plasma-runners-addons
6332 plasma-scriptengine-googlegadgets
6333 plasma-scriptengine-python
6334 plasma-scriptengine-qedje
6335 plasma-scriptengine-ruby
6336 plasma-scriptengine-webkit
6337 plasma-scriptengines
6338 plasma-wallpapers-addons
6339 plasma-widget-folderview
6340 plasma-widget-networkmanagement
6341 ruby
6342 sweeper
6343 update-notifier-kde
6344 xscreensaver-data-extra
6345 xscreensaver-gl
6346 xscreensaver-gl-extra
6347 xscreensaver-screensaver-bsod
6348 &lt;/p&gt;&lt;/blockquote&gt;
6349
6350 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6351
6352 &lt;blockquote&gt;&lt;p&gt;
6353 ark
6354 google-gadgets-common
6355 google-gadgets-qt
6356 htdig
6357 kate
6358 kdebase-bin
6359 kdebase-data
6360 kdepasswd
6361 kfind
6362 klipper
6363 konq-plugins
6364 konqueror
6365 ksysguard
6366 ksysguardd
6367 libarchive1
6368 libcln6
6369 libeet1
6370 libeina-svn-06
6371 libggadget-1.0-0b
6372 libggadget-qt-1.0-0b
6373 libgps19
6374 libkdecorations4
6375 libkephal4
6376 libkonq4
6377 libkonqsidebarplugin4a
6378 libkscreensaver5
6379 libksgrd4
6380 libksignalplotter4
6381 libkunitconversion4
6382 libkwineffects1a
6383 libmarblewidget4
6384 libntrack-qt4-1
6385 libntrack0
6386 libplasma-geolocation-interface4
6387 libplasmaclock4a
6388 libplasmagenericshell4
6389 libprocesscore4a
6390 libprocessui4a
6391 libqalculate5
6392 libqedje0a
6393 libqtruby4shared2
6394 libqzion0a
6395 libruby1.8
6396 libscim8c2a
6397 libsmokekdecore4-3
6398 libsmokekdeui4-3
6399 libsmokekfile3
6400 libsmokekhtml3
6401 libsmokekio3
6402 libsmokeknewstuff2-3
6403 libsmokeknewstuff3-3
6404 libsmokekparts3
6405 libsmokektexteditor3
6406 libsmokekutils3
6407 libsmokenepomuk3
6408 libsmokephonon3
6409 libsmokeplasma3
6410 libsmokeqtcore4-3
6411 libsmokeqtdbus4-3
6412 libsmokeqtgui4-3
6413 libsmokeqtnetwork4-3
6414 libsmokeqtopengl4-3
6415 libsmokeqtscript4-3
6416 libsmokeqtsql4-3
6417 libsmokeqtsvg4-3
6418 libsmokeqttest4-3
6419 libsmokeqtuitools4-3
6420 libsmokeqtwebkit4-3
6421 libsmokeqtxml4-3
6422 libsmokesolid3
6423 libsmokesoprano3
6424 libtaskmanager4a
6425 libtidy-0.99-0
6426 libweather-ion4a
6427 libxklavier16
6428 libxxf86misc1
6429 okteta
6430 oxygencursors
6431 plasma-dataengines-addons
6432 plasma-scriptengine-superkaramba
6433 plasma-widget-lancelot
6434 plasma-widgets-addons
6435 plasma-widgets-workspace
6436 polkit-kde-1
6437 ruby1.8
6438 systemsettings
6439 update-notifier-common
6440 &lt;/p&gt;&lt;/blockquote&gt;
6441
6442 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6443 aptitude a bit more similar, but there are still quite a lott of
6444 differences. I have no idea what packages should be installed after
6445 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6446 </description>
6447 </item>
6448
6449 <item>
6450 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6451 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6452 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6453 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6454 <description>&lt;p&gt;Most of the computers in use by the
6455 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6456 are virtual machines. And they have been Xen machines running on a
6457 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6458 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6459 bit harder that it could have been, because we set up the Xen virtual
6460 machines to get the virtual partitions from LVM, which as far as I
6461 know is not supported by KVM. So to migrate, we had to convert
6462 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6463
6464 &lt;p&gt;I found
6465 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6466 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6467 migration. It uses qemu-img from the qemu package to make the disk
6468 image, parted to partition it, losetup and kpartx to present the disk
6469 image partions as devices, and dd to copy the data. I NFS mounted the
6470 new servers storage area on the old server to do the migration.&lt;/p&gt;
6471
6472 &lt;pre&gt;
6473 #!/bin/sh
6474
6475 # Based on
6476 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6477
6478 set -e
6479 set -x
6480
6481 if [ -z &quot;$1&quot; ] ; then
6482 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6483 exit 1
6484 else
6485 host=&quot;$1&quot;
6486 fi
6487
6488 if [ ! -e /dev/vg_data/$host-disk ] ; then
6489 echo &quot;error: unable to find LVM volume for $host&quot;
6490 exit 1
6491 fi
6492
6493 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6494 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6495 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6496 totalsize=$(( ( $disksize + $swapsize ) ))
6497
6498 img=$host.img
6499 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6500 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6501
6502 parted $img mklabel msdos
6503 parted $img mkpart primary linux-swap 0 $disksize
6504 parted $img mkpart primary ext2 $disksize $totalsize
6505 parted $img set 1 boot on
6506
6507 modprobe dm-mod
6508 losetup /dev/loop0 $img
6509 kpartx -a /dev/loop0
6510
6511 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6512 fsck.ext3 -f /dev/mapper/loop0p1 || true
6513 mkswap /dev/mapper/loop0p2
6514
6515 kpartx -d /dev/loop0
6516 losetup -d /dev/loop0
6517 &lt;/pre&gt;
6518
6519 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6520 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6521
6522 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6523 the new disk image attached, installed grub-pc and linux-image-686 and
6524 set up grub to boot from the disk image. After this, the KVM machines
6525 seem to work just fine.&lt;/p&gt;
6526 </description>
6527 </item>
6528
6529 <item>
6530 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6531 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6533 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6534 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6535 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6536 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6537 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6538
6539 &lt;p&gt;I still do not know what a correct migration should look like, so I
6540 report any differences between apt and aptitude and hope someone else
6541 can see if anything should be changed.&lt;/p&gt;
6542
6543 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6544
6545 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6546
6547 &lt;blockquote&gt;&lt;p&gt;
6548 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6549 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6550 dmz-cursor-theme empathy empathy-common finger
6551 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6552 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6553 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6554 gnome-cards-data gnome-codec-install gnome-core
6555 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6556 gnome-search-tool gnome-session-canberra gnome-spell
6557 gnome-system-log gnome-themes-extras gnome-themes-more
6558 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6559 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6560 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6561 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6562 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6563 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6564 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6565 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6566 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6567 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6568 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6569 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6570 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6571 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6572 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6573 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6574 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6575 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6576 libmono-security2.0-cil libmono-sharpzip2.84-cil
6577 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6578 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6579 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6580 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6581 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6582 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6583 libxalan2-java libxerces2-java media-player-info mesa-utils
6584 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6585 nautilus-sendto-empathy openoffice.org-writer2latex
6586 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6587 python-aptdaemon python-aptdaemon-gtk python-axiom
6588 python-beautifulsoup python-bugbuddy python-clientform
6589 python-coherence python-configobj python-crypto python-cupshelpers
6590 python-cupsutils python-eggtrayicon python-elementtree
6591 python-epsilon python-evolution python-feedparser python-gdata
6592 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6593 python-gtksourceview2 python-httplib2 python-louie python-mako
6594 python-markupsafe python-mechanize python-nevow python-notify
6595 python-opengl python-openssl python-pam python-pkg-resources
6596 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6597 python-tagpy python-twisted-bin python-twisted-conch
6598 python-twisted-core python-twisted-web python-utidylib python-webkit
6599 python-xdg python-zope.interface remmina remmina-plugin-data
6600 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6601 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6602 software-center svgalibg1 system-config-printer-udev
6603 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6604 totem totem-coherence totem-mozilla totem-plugins
6605 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6606 zip
6607 &lt;/p&gt;&lt;/blockquote&gt;
6608
6609 Installed using apt-get, removed with aptitude
6610
6611 &lt;blockquote&gt;&lt;p&gt;
6612 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6613 epiphany-extensions epiphany-gecko evolution-exchange
6614 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6615 gedit-common gnome-app-install gnome-games gnome-games-data
6616 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6617 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6618 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6619 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6620 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6621 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6622 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6623 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6624 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6625 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6626 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6627 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6628 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6629 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6630 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6631 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6632 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6633 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6634 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6635 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6636 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6637 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6638 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6639 sound-juicer swfdec-gnome system-config-printer totem-common
6640 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6641 &lt;/p&gt;&lt;/blockquote&gt;
6642
6643 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6644
6645 &lt;blockquote&gt;&lt;p&gt;
6646 gstreamer0.10-gnomevfs
6647 &lt;/p&gt;&lt;/blockquote&gt;
6648
6649 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6650
6651 &lt;blockquote&gt;&lt;p&gt;
6652 [nothing]
6653 &lt;/p&gt;&lt;/blockquote&gt;
6654
6655 &lt;p&gt;This is for KDE:&lt;/p&gt;
6656
6657 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6658
6659 &lt;blockquote&gt;&lt;p&gt;
6660 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6661 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6662 ghostscript-x git gnome-audio gnugo granatier gs-common
6663 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6664 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6665 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6666 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6667 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6668 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6669 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6670 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6671 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6672 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6673 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6674 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6675 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6676 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6677 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6678 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6679 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6680 libkrossui4 libmailtools-perl libmime-tools-perl
6681 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6682 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6683 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6684 lirc luatex marble networkstatus noatun-plugins
6685 openoffice.org-writer2latex palapeli palapeli-data parley
6686 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6687 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6688 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6689 ttf-sazanami-gothic
6690 &lt;/p&gt;&lt;/blockquote&gt;
6691
6692 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6693
6694 &lt;blockquote&gt;&lt;p&gt;
6695 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6696 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6697 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6698 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6699 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6700 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6701 kitchensync kiten kjumpingcube klatin klettres klickety klines
6702 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6703 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6704 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6705 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6706 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6707 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6708 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6709 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6710 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6711 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6712 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6713 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6714 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6715 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6716 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6717 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6718 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6719 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6720 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6721 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6722 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6723 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6724 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6725 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6726 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6727 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6728 &lt;/p&gt;&lt;/blockquote&gt;
6729
6730 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6731
6732 &lt;blockquote&gt;&lt;p&gt;
6733 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6734 kdeartwork kdebase kdebase-apps kdebase-workspace
6735 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6736 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6737 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6738 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6739 xscreensaver-screensaver-bsod
6740 &lt;/p&gt;&lt;/blockquote&gt;
6741
6742 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6743
6744 &lt;blockquote&gt;&lt;p&gt;
6745 kdebase-bin konq-plugins konqueror
6746 &lt;/p&gt;&lt;/blockquote&gt;
6747 </description>
6748 </item>
6749
6750 <item>
6751 <title>Gnash buildbot slave and Debian kfreebsd</title>
6752 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6753 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6754 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6755 <description>&lt;p&gt;Answering
6756 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6757 call from the Gnash project&lt;/a&gt; for
6758 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6759 current source, I have set up a virtual KVM machine on the Debian
6760 Edu/Skolelinux virtualization host to test the git source on
6761 Debian/Squeeze. I hope this can help the developers in getting new
6762 releases out more often.&lt;/p&gt;
6763
6764 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6765 I have considered setting up a &lt;a
6766 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6767 machine as well. I have also considered using the kfreebsd
6768 architecture in Debian as a file server in NUUG to get access to the 5
6769 TB zfs volume we currently use to store DV video. Because of this, I
6770 finally got around to do a test installation of Debian/Squeeze with
6771 kfreebsd. Installation went fairly smooth, thought I noticed some
6772 visual glitches in the cdebconf dialogs (black cursor left on the
6773 screen at random locations). Have not gotten very far with the
6774 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6775 fatal problem. Have to spend some more time on it to see if it is
6776 useful as a file server for NUUG. Will try to find time to set up a
6777 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6778 </description>
6779 </item>
6780
6781 <item>
6782 <title>Debian in 3D</title>
6783 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6784 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6785 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6786 <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;
6787
6788 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6789 3D linked in from
6790 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6791 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6792 </description>
6793 </item>
6794
6795 <item>
6796 <title>Software updates 2010-10-24</title>
6797 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6798 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6799 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6800 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6801
6802 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6803 raise money for the project is going well. The lower limit of 10
6804 signers was reached in 24 hours, and so far 13 people have signed it.
6805 More signers and more funding is most welcome, and I am really curious
6806 how far we can get before the time limit of December 24 is reached.
6807 :)&lt;/p&gt;
6808
6809 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6810 about what appear to be a great code coverage tool capable of
6811 generating code coverage stats without any changes to the source code.
6812 It is called
6813 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6814 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6815 It is missing in Debian, but the git source built just fine in Squeeze
6816 after I installed libelf-dev, libdwarf-dev, pkg-config and
6817 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6818 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6819
6820 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6821 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6822 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6823 alpha test release of the Squeeze based Debian Edu /
6824 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6825 release. Give it a try if you need a complete linux solution for your
6826 school, including central infrastructure server, workstations, thin
6827 client servers and diskless workstations. A nice touch added
6828 yesterday is RDP support on the thin client servers, for windows
6829 clients to get a Linux desktop on request.&lt;/p&gt;
6830 </description>
6831 </item>
6832
6833 <item>
6834 <title>Some notes on Flash in Debian and Debian Edu</title>
6835 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6836 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6837 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6838 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6839 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6840 second most popular used package that is missing in Debian. The sixth
6841 most popular is flashplayer-mozilla. This is a clear indication that
6842 working flash is important for Debian users. Around 10 percent of the
6843 users submitting data to popcon.debian.org have this package
6844 installed.&lt;/p&gt;
6845
6846 &lt;p&gt;In the report written by Lars Risan in August 2008
6847&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
6848 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6849 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6850 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6851 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6852 web sites require Flash to work, and lacking working Flash support in
6853 the web browser and the problems with installing it was perceived as a
6854 good reason to stay with Windows.&lt;/p&gt;
6855
6856 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6857 said to be the retarded cousin that did not really understand
6858 everything you told him but could work fairly well. This was a
6859 comment regarding the problems Linux have with proprietary formats and
6860 non-standard web pages, and is sad because it exposes a fairly common
6861 understanding of whose fault it is if web pages that only work in for
6862 example Internet Explorer 6 fail to work on Firefox, and funny because
6863 it explain very well how annoying it is for users when Linux
6864 distributions do not work with the documents they receive or the web
6865 pages they want to visit.&lt;/p&gt;
6866
6867 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6868 and Debian Edu to have a well working Flash implementation in the
6869 distribution, to get at least popular sites as Youtube and Google
6870 Video to working out of the box. For Squeeze, Debian have the chance
6871 to include the latest version of Gnash that will make this happen, as
6872 the new release 0.8.8 was published a few weeks ago and is resting in
6873 unstable. The new version work with more sites that version 0.8.7.
6874 The Gnash maintainers have asked for a freeze exception, but the
6875 release team have not had time to reply to it yet. I hope they agree
6876 with me that Flash is important for the Debian desktop users, and thus
6877 accept the new package into Squeeze.&lt;/p&gt;
6878 </description>
6879 </item>
6880
6881 <item>
6882 <title>Circular package dependencies harms apt recovery</title>
6883 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6884 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6885 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6886 <description>&lt;p&gt;I discovered this while doing
6887 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6888 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6889 in Debian still got circular dependencies, and it is often claimed
6890 that apt and aptitude should be able to handle this just fine, but
6891 some times these dependency loops causes apt to fail.&lt;/p&gt;
6892
6893 &lt;p&gt;An example is from todays
6894 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6895 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6896 causes perl-modules to fail to upgrade. The cause is simple. If a
6897 package fail to unpack, then only part of packages with the circular
6898 dependency might end up being unpacked when unpacking aborts, and the
6899 ones already unpacked will fail to configure in the recovery phase
6900 because its dependencies are unavailable.&lt;/p&gt;
6901
6902 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6903
6904 &lt;blockquote&gt;&lt;pre&gt;
6905 dpkg: dependency problems prevent configuration of perl-modules:
6906 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6907 Version of perl on system is 5.10.0-19lenny2.
6908 dpkg: error processing perl-modules (--configure):
6909 dependency problems - leaving unconfigured
6910 &lt;/pre&gt;&lt;/blockquote&gt;
6911
6912 &lt;p&gt;The perl/perl-modules circular dependency is already
6913 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6914 hopefully be solved as soon as possible, but it is not the only one,
6915 and each one of these loops in the dependency tree can cause similar
6916 failures. Of course, they only occur when there are bugs in other
6917 packages causing the unpacking to fail, but it is rather nasty when
6918 the failure of one package causes the problem to become worse because
6919 of dependency loops.&lt;/p&gt;
6920
6921 &lt;p&gt;Thanks to
6922 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6923 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6924 dependencies
6925 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6926 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6927
6928 &lt;p&gt;Todays testing also exposed a bug in
6929 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6930 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6931 apt-get and aptitude, the latter possibly caused by some circular
6932 dependency. Reported both to BTS to try to get someone to look at
6933 it.&lt;/p&gt;
6934 </description>
6935 </item>
6936
6937 <item>
6938 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6939 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6940 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6941 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6942 <description>&lt;p&gt;This is a
6943 &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;
6944 on my
6945 &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
6946 work&lt;/a&gt; on
6947 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6948 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6949
6950 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6951 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6952 and dhcp3-server-ldap in Debian use the LDAP server. The two
6953 implementations are quite different in how they use LDAP.&lt;/p&gt;
6954
6955 To get this information, I started slapd with debugging enabled and
6956 dumped the debug output to a file to get the LDAP searches performed
6957 on a Debian Edu main-server. Here is a summary.
6958
6959 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6960
6961 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6962 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6963 the web.
6964
6965 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6966 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6967 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6968 reverse entries are in two different subtrees in LDAP with a structure
6969 based on the DNS names, as in tjener.intern and
6970 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6971
6972 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6973 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6974 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6975 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6976 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6977 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6978 forward entries, it is looking for attributes named dnsttl, arecord,
6979 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6980 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6981 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6982 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6983 spfrecord and modifytimestamp. For reverse entries it is looking for
6984 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6985 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6986 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6987 ldapsearch commands could look like this:&lt;/p&gt;
6988
6989 &lt;blockquote&gt;&lt;pre&gt;
6990 ldapsearch -h ldap \
6991 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6992 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6993 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6994 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6995 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6996 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6997
6998 ldapsearch -h ldap \
6999 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7000 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
7001 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7002 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7003 srvrecord naptrrecord modifytimestamp
7004 &lt;/pre&gt;&lt;/blockquote&gt;
7005
7006 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
7007 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7008 example LDAP objects used there. In addition to these objects, the
7009 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7010 also exist.&lt;/p&gt;
7011
7012 &lt;blockquote&gt;&lt;pre&gt;
7013 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7014 objectclass: top
7015 objectclass: dnsdomain
7016 objectclass: domainrelatedobject
7017 dc: tjener
7018 arecord: 10.0.2.2
7019 associateddomain: tjener.intern
7020
7021 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7022 objectclass: top
7023 objectclass: dnsdomain2
7024 objectclass: domainrelatedobject
7025 dc: 2
7026 ptrrecord: tjener.intern
7027 associateddomain: 2.2.0.10.in-addr.arpa
7028 &lt;/pre&gt;&lt;/blockquote&gt;
7029
7030 &lt;p&gt;In strict mode, the server behaves differently. When looking for
7031 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
7032 same base as in the tree mode for a object with filter
7033 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
7034 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7035 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7036 naptrrecord and modifytimestamp. For reverse entires it also do a
7037 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
7038 and the requested attributes are associateddomain, dnsttl and
7039 modifytimestamp. In short, in strict mode the objects with ptrrecord
7040 go away, and the arecord attribute in the forward object is used
7041 instead.&lt;/p&gt;
7042
7043 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
7044 like this:&lt;/p&gt;
7045
7046 &lt;blockquote&gt;&lt;pre&gt;
7047 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7048 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
7049 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7050 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7051 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7052 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7053
7054 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7055 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
7056 &lt;/pre&gt;&lt;/blockquote&gt;
7057
7058 &lt;p&gt;In addition to the forward and reverse searches , there is also a
7059 search for SOA records, which behave similar to the forward and
7060 reverse lookups.&lt;/p&gt;
7061
7062 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
7063 specify any objectclass names, and instead look for the attributes it
7064 need to generate a DNS reply. This make it able to work with any
7065 objectclass that provide the needed attributes.&lt;/p&gt;
7066
7067 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
7068 dnsdomain2 schemas. The latter is used for reverse entries like
7069 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
7070
7071 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
7072 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7073 attributes) and domainrelatedobject (for associatedDomain). The use
7074 of structural object classes make it impossible to combine these
7075 classes with the object classes used by DHCP.&lt;/p&gt;
7076
7077 &lt;p&gt;There are other schemas that could be used too, for example the
7078 dnszone structural object class used by Gosa and bind-sdb for the DNS
7079 attributes combined with the domainrelatedobject object class, but in
7080 this case some unused attributes would have to be included as well
7081 (zonename and relativedomainname).&lt;/p&gt;
7082
7083 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
7084 mode and not use any of the existing objectclasses (dnsdomain,
7085 dnsdomain2 and dnszone) when one want to combine the DNS information
7086 with DHCP information, and instead create a auxiliary object class
7087 defined something like this (using the attributes defined for
7088 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
7089
7090 &lt;blockquote&gt;&lt;pre&gt;
7091 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
7092 SUP top
7093 AUXILIARY
7094 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7095 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7096 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7097 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7098 A6Record $ DNAMERecord
7099 ))
7100 &lt;/pre&gt;&lt;/blockquote&gt;
7101
7102 &lt;p&gt;This will allow any object to become a DNS entry when combined with
7103 the domainrelatedobject object class, and allow any entity to include
7104 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
7105 developers asking for their view on this schema and if they are
7106 interested in providing such schema with PowerDNS, and I hope my
7107 message will be accepted into their mailing list soon.&lt;/p&gt;
7108
7109 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
7110
7111 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
7112 the object attributes, and then uses the attributes it want. This
7113 make it harder to figure out exactly what attributes are used, but
7114 thanks to the working example in Debian Edu I can at least get an idea
7115 what is needed without having to read the source code.&lt;/p&gt;
7116
7117 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
7118 search filter to use to locate the correct dhcpServer entity is
7119 stored. These are the relevant entries from
7120 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
7121
7122 &lt;blockquote&gt;&lt;pre&gt;
7123 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
7124 ldap-dhcp-server-cn &quot;dhcp&quot;;
7125 &lt;/pre&gt;&lt;/blockquote&gt;
7126
7127 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
7128 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
7129 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
7130 search result is this entry:&lt;/p&gt;
7131
7132 &lt;blockquote&gt;&lt;pre&gt;
7133 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7134 cn: dhcp
7135 objectClass: top
7136 objectClass: dhcpServer
7137 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7138 &lt;/pre&gt;&lt;/blockquote&gt;
7139
7140 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
7141 subtree with DHCP configuration. The DHCP configuration subtree base
7142 is located using a base scope search with base &quot;cn=DHCP
7143 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
7144 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
7145 The search result is this entry:&lt;/p&gt;
7146
7147 &lt;blockquote&gt;&lt;pre&gt;
7148 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7149 cn: DHCP Config
7150 objectClass: top
7151 objectClass: dhcpService
7152 objectClass: dhcpOptions
7153 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7154 dhcpStatements: ddns-update-style none
7155 dhcpStatements: authoritative
7156 dhcpOption: smtp-server code 69 = array of ip-address
7157 dhcpOption: www-server code 72 = array of ip-address
7158 dhcpOption: wpad-url code 252 = text
7159 &lt;/pre&gt;&lt;/blockquote&gt;
7160
7161 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
7162 all the DHCP configuration is loaded, it is ready to receive requests.
7163 The subtree in Debian Edu contain objects with object classes
7164 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7165 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7166 and information about netmasks, dynamic range etc. Leaving out the
7167 details here because it is not relevant for the focus of my
7168 investigation, which is to see if it is possible to merge dns and dhcp
7169 related computer objects.&lt;/p&gt;
7170
7171 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
7172 of the client (00:00:00:00:00:00 in this example), using a subtree
7173 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
7174 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7175 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
7176 like:&lt;/p&gt;
7177
7178 &lt;blockquote&gt;&lt;pre&gt;
7179 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7180 cn: hostname
7181 objectClass: top
7182 objectClass: dhcpHost
7183 dhcpHWAddress: ethernet 00:00:00:00:00:00
7184 dhcpStatements: fixed-address hostname
7185 &lt;/pre&gt;&lt;/blockquote&gt;
7186
7187 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
7188 The object classes need to have fixed names, and the configuration
7189 need to be stored in a fairly specific LDAP structure. On the
7190 positive side, the invidiual dhcpHost entires can be anywhere without
7191 the DN pointed to by the dhcpServer entries. The latter should make
7192 it possible to group all host entries in a subtree next to the
7193 configuration entries, and this subtree can also be shared with the
7194 DNS server if the schema proposed above is combined with the dhcpHost
7195 structural object class.
7196
7197 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
7198
7199 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
7200 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
7201 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
7202 allowing DNS objects to be stored anywhere under the base cn specified
7203 in the configuration.&lt;/p&gt;
7204
7205 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
7206 regarding which LDAP schemas to use and which LDAP structure to use.
7207 I guess one could implement ones own schema, as long as the
7208 objectclasses and attributes have the names used, but this do not
7209 really help when the DHCP subtree need to have a fairly fixed
7210 structure.&lt;/p&gt;
7211
7212 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
7213 this might work for Debian Edu:&lt;/p&gt;
7214
7215 &lt;blockquote&gt;&lt;pre&gt;
7216 ou=services
7217 cn=machine-info (dhcpService) - dhcpServiceDN points here
7218 cn=dhcp (dhcpServer)
7219 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7220 cn=10.0.2.0 (dhcpSubnet)
7221 cn=group1 (dhcpGroup/dhcpOptions)
7222 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7223 cn=192.168.0.0 (dhcpSubnet)
7224 cn=group1 (dhcpGroup/dhcpOptions)
7225 ou=machines - PowerDNS base points here
7226 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7227 &lt;/pre&gt;&lt;/blockquote&gt;
7228
7229 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
7230 entries to be in the dhcpGroup subtrees, the entries can be stored
7231 there instead of a common machines subtree, and the PowerDNS base
7232 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
7233
7234 &lt;p&gt;The combined object under the machines subtree would look something
7235 like this:&lt;/p&gt;
7236
7237 &lt;blockquote&gt;&lt;pre&gt;
7238 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7239 dc: hostname
7240 objectClass: top
7241 objectClass: dhcpHost
7242 objectclass: domainrelatedobject
7243 objectclass: dnsDomainAux
7244 associateddomain: hostname.intern
7245 arecord: 10.11.12.13
7246 dhcpHWAddress: ethernet 00:00:00:00:00:00
7247 dhcpStatements: fixed-address hostname.intern
7248 &lt;/pre&gt;&lt;/blockquote&gt;
7249
7250 &lt;/p&gt;One could even add the LTSP configuration associated with a given
7251 machine, as long as the required attributes are available in a
7252 auxiliary object class.&lt;/p&gt;
7253 </description>
7254 </item>
7255
7256 <item>
7257 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
7258 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
7259 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
7260 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
7261 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
7262 DHCP services in Debian Edu to use the same LDAP objects for a given
7263 computer, to avoid the possibility of having a inconsistent state for
7264 a computer in LDAP (as in DHCP but no DNS entry or the other way
7265 around) and make it easier to add computers to LDAP.&lt;/p&gt;
7266
7267 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
7268 information finally found a solution that seem to work.&lt;/p&gt;
7269
7270 &lt;p&gt;The old setup required three LDAP objects for a given computer.
7271 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7272 we switch powerdns to use its strict LDAP method (ldap-method=strict
7273 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7274 merged into one while making it impossible to transfer the reverse map
7275 to a slave DNS server.&lt;/p&gt;
7276
7277 &lt;p&gt;If we also replace the object class used to get the DNS related
7278 attributes to one allowing these attributes to be combined with the
7279 dhcphost object class, we can merge the DNS and DHCP entries into one.
7280 I&#39;ve written such object class in the dnsdomainaux.schema file (need
7281 proper OIDs, but that is a minor issue), and tested the setup. It
7282 seem to work.&lt;/p&gt;
7283
7284 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
7285 for both DNS and DHCP, and even the LTSP configuration I suggested in
7286 an earlier email. The combined LDAP object will look something like
7287 this:&lt;/p&gt;
7288
7289 &lt;blockquote&gt;&lt;pre&gt;
7290 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7291 cn: hostname
7292 objectClass: dhcphost
7293 objectclass: domainrelatedobject
7294 objectclass: dnsdomainaux
7295 associateddomain: hostname.intern
7296 arecord: 10.11.12.13
7297 dhcphwaddress: ethernet 00:00:00:00:00:00
7298 dhcpstatements: fixed-address hostname
7299 ldapconfigsound: Y
7300 &lt;/pre&gt;&lt;/blockquote&gt;
7301
7302 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
7303 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7304 before asking DNS to resolve the fixed-adddress. LTSP will use
7305 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
7306
7307 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
7308 dhcphost in a different location, to allow us to put the objects
7309 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7310 that. If I can&#39;t figure out a way to do that, we can still get rid of
7311 the hosts subtree and move all its content into the DHCP Config tree
7312 (which probably should be renamed to be more related to the new
7313 content. I suspect cn=dnsdhcp,ou=services or something like that
7314 might be a good place to put it.&lt;/p&gt;
7315
7316 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7317 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7318 </description>
7319 </item>
7320
7321 <item>
7322 <title>Idea for storing LTSP configuration in LDAP</title>
7323 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7324 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7325 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7326 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7327 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7328 clients, and that this can be used to fetch configuration from LDAP if
7329 Debian Edu choose to store configuration there.&lt;/p&gt;
7330
7331 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7332 to get configuration from LDAP. The idea is to look up the MAC
7333 address of the client in LDAP, and look for attributes on the form
7334 ltspconfigsetting=value, and use this to export SETTING=value to the
7335 LTSP clients.&lt;/p&gt;
7336
7337 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7338 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7339 allowing us to store all information about a computer in one place.&lt;/p&gt;
7340
7341 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7342 this approach. A real LDAP schema for the ltspClientAux objectclass
7343 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7344
7345 &lt;blockquote&gt;&lt;pre&gt;
7346 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7347 #
7348 # Fetch LTSP client settings from LDAP based on MAC address
7349 #
7350 # Uses ethernet address as stored in the dhcpHost objectclass using
7351 # the dhcpHWAddress attribute or ethernet address stored in the
7352 # ieee802Device objectclass with the macAddress attribute.
7353 #
7354 # This module is written to be schema agnostic, and only depend on the
7355 # existence of attribute names.
7356 #
7357 # The LTSP configuration variables are saved directly using a
7358 # ltspConfig prefix and uppercasing the rest of the attribute name.
7359 # To set the SERVER variable, set the ltspConfigServer attribute.
7360 #
7361 # Some LDAP schema should be created with all the relevant
7362 # configuration settings. Something like this should work:
7363 #
7364 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7365 # SUP top
7366 # AUXILIARY
7367 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7368
7369 LDAPSERVER=$(debian-edu-ldapserver)
7370 if [ &quot;$LDAPSERVER&quot; ] ; then
7371 LDAPBASE=$(debian-edu-ldapserver -b)
7372 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7373 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7374 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7375 grep &#39;^ltspConfig&#39; | while read attr value ; do
7376 # Remove prefix and convert to upper case
7377 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7378 # bass value on to clients
7379 eval &quot;$attr=$value; export $attr&quot;
7380 done
7381 done
7382 fi
7383 &lt;/pre&gt;&lt;/blockquote&gt;
7384
7385 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7386 the while block might end up in a subshell causing the variables set
7387 there to not show up in ltsp-config, but if that is the case I am sure
7388 the code can be restructured to make sure the variables are passed on.
7389 I expect that can be solved with some testing. :)&lt;/p&gt;
7390
7391 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7392 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7393
7394 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7395 configuration in LDAP that was created around year 2000 by
7396 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7397 Xperience, Inc., 2000&lt;/a&gt;. I found its
7398 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7399 personal home page over at redhat.com.&lt;/p&gt;
7400 </description>
7401 </item>
7402
7403 <item>
7404 <title>jXplorer, a very nice LDAP GUI</title>
7405 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7406 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7407 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7408 <description>&lt;p&gt;Since
7409 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7410 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7411 LDAP GUI that is even better than luma. The java application
7412 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7413 moving LDAP objects and subtrees using drag-and-drop, and can
7414 authenticate using Kerberos. I have only tested the Kerberos
7415 authentication, but do not have a LDAP setup allowing me to rewrite
7416 LDAP with my test user yet. It is
7417 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7418 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7419 have with it is how it handle errors. If something go wrong, its
7420 non-intuitive behaviour require me to go through some query work list
7421 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7422 </description>
7423 </item>
7424
7425 <item>
7426 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7427 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7428 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7429 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7430 <description>&lt;p&gt;Here is a short update on my &lt;a
7431 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7432 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7433 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7434 not reporting the status for KDE, because the upgrade crashes when
7435 aptitude try because of missing conflicts
7436 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7437 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7438
7439 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7440 complete list of the installed packages. Based on this I see these
7441 differences when I did a test run today. As usual, I do not really
7442 know what the correct set of packages would be, but thought it best to
7443 publish the difference.&lt;/p&gt;
7444
7445 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7446
7447 &lt;blockquote&gt;&lt;p&gt;
7448 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7449 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7450 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7451 libgtksourceview-common libpt-1.10.10-plugins-alsa
7452 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7453 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7454 python-4suite-xml python-eggtrayicon python-gtkhtml2
7455 python-gtkmozembed svgalibg1 xserver-xephyr zip
7456 &lt;/p&gt;&lt;/blockquote&gt;
7457
7458 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7459
7460 &lt;blockquote&gt;&lt;p&gt;
7461 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7462 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7463 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7464 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7465 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7466 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7467 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7468 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7469 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7470 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7471 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7472 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7473 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7474 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7475 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7476 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7477 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7478 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7479 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7480 mysql-common swfdec-gnome totem-gstreamer wodim
7481 &lt;/p&gt;&lt;/blockquote&gt;
7482
7483 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7484
7485 &lt;blockquote&gt;&lt;p&gt;
7486 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7487 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7488 xserver-xorg-input-all xserver-xorg-input-evdev
7489 xserver-xorg-input-kbd xserver-xorg-input-mouse
7490 xserver-xorg-input-synaptics xserver-xorg-video-all
7491 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7492 xserver-xorg-video-chips xserver-xorg-video-cirrus
7493 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7494 xserver-xorg-video-glint xserver-xorg-video-i128
7495 xserver-xorg-video-i740 xserver-xorg-video-mach64
7496 xserver-xorg-video-mga xserver-xorg-video-neomagic
7497 xserver-xorg-video-nouveau xserver-xorg-video-nv
7498 xserver-xorg-video-r128 xserver-xorg-video-radeon
7499 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7500 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7501 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7502 xserver-xorg-video-sis xserver-xorg-video-sisusb
7503 xserver-xorg-video-tdfx xserver-xorg-video-tga
7504 xserver-xorg-video-trident xserver-xorg-video-tseng
7505 xserver-xorg-video-vesa xserver-xorg-video-vmware
7506 xserver-xorg-video-voodoo
7507 &lt;/p&gt;&lt;/blockquote&gt;
7508
7509 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7510
7511 &lt;blockquote&gt;&lt;p&gt;
7512 deskbar-applet xserver-xorg xserver-xorg-core
7513 xserver-xorg-input-wacom xserver-xorg-video-intel
7514 xserver-xorg-video-openchrome
7515 &lt;/p&gt;&lt;/blockquote&gt;
7516
7517 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7518 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7519 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7520 No idea when it hits Squeeze, but when it does I hope it will reduce
7521 the difference somewhat.
7522 </description>
7523 </item>
7524
7525 <item>
7526 <title>LUMA, a very nice LDAP GUI</title>
7527 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7528 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7529 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7530 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7531 directory in Debian Edu, and in the process I started to miss a GUI
7532 tool to browse the LDAP tree. The only one I was able to find in
7533 Debian/Squeeze and Lenny is
7534 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7535 be a great tool to get a overview of the current LDAP directory
7536 populated by default in Skolelinux. Thanks to it, I have been able to
7537 find empty and obsolete subtrees, misplaced objects and duplicate
7538 objects. It will be installed by default in Debian/Squeeze. If you
7539 are working with LDAP, give it a go. :)&lt;/p&gt;
7540
7541 &lt;p&gt;I did notice one problem with it I have not had time to report to
7542 the BTS yet. There is no .desktop file in the package, so the tool do
7543 not show up in the Gnome and KDE menus, but only deep down in in the
7544 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7545 released.&lt;/p&gt;
7546
7547 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7548 like to move objects and remove subtrees directly in the GUI, but have
7549 not found a way to do that with LUMA yet. So in the mean time, I use
7550 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7551
7552 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7553 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7554
7555 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7556 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7557 useful GUI alternative. It seem like a good tool, but is unmaintained
7558 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7559 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7560 </description>
7561 </item>
7562
7563 <item>
7564 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7565 <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>
7566 <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>
7567 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7568 <description>&lt;p&gt;A while back, I
7569 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7570 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7571 for storing DNS and DHCP information in LDAP to combine the two sets
7572 of information into one LDAP object representing a computer.&lt;/p&gt;
7573
7574 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7575 the dhcpHost object class auxiliary, to allow it to be combined with
7576 the dNSDomain object class, and thus forming one object for one
7577 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7578
7579 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7580 without also changing the assigned number for the object class, and I
7581 do not know enough about LDAP schema design to do that properly for
7582 Debian Edu.&lt;/p&gt;
7583
7584 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7585 the
7586 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7587 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7588 available today from IETF.&lt;/p&gt;
7589
7590 &lt;pre&gt;
7591 --- dhcp.schema (revision 65192)
7592 +++ dhcp.schema (working copy)
7593 @@ -376,7 +376,7 @@
7594 objectclass ( 2.16.840.1.113719.1.203.6.6
7595 NAME &#39;dhcpHost&#39;
7596 DESC &#39;This represents information about a particular client&#39;
7597 - SUP top
7598 + SUP top AUXILIARY
7599 MUST cn
7600 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7601 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7602 &lt;/pre&gt;
7603
7604 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7605 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7606 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7607
7608 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7609 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7610 </description>
7611 </item>
7612
7613 <item>
7614 <title>Calling tasksel like the installer, while still getting useful output</title>
7615 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7616 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7617 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7618 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7619 installs packages during the normal debian-installer run. Until now,
7620 I have ended up letting tasksel do the work, with the annoying problem
7621 of not getting any feedback at all when something fails (like a
7622 conffile question from dpkg or a download that fails), using code like
7623 this:
7624
7625 &lt;blockquote&gt;&lt;pre&gt;
7626 export DEBIAN_FRONTEND=noninteractive
7627 tasksel --new-install
7628 &lt;/pre&gt;&lt;/blockquote&gt;
7629
7630 This would invoke tasksel, let its automatic task selection pick the
7631 tasks to install, and continue to install the requested tasks without
7632 any output what so ever.
7633
7634 Recently I revisited this problem while working on the automatic
7635 package upgrade testing, because tasksel would some times hang without
7636 any useful feedback, and I want to see what is going on when it
7637 happen. Then it occured to me, I can parse the output from tasksel
7638 when asked to run in test mode, and use that aptitude command line
7639 printed by tasksel then to simulate the tasksel run. I ended up using
7640 code like this:
7641
7642 &lt;blockquote&gt;&lt;pre&gt;
7643 export DEBIAN_FRONTEND=noninteractive
7644 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7645 $cmd
7646 &lt;/pre&gt;&lt;/blockquote&gt;
7647
7648 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7649 --without-recommends -o APT::Install-Recommends=no -y install
7650 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7651 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7652 laptop task and all packages with priority standard , required and
7653 important, just like tasksel would have done it during
7654 installation.&lt;/p&gt;
7655
7656 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7657 install packages without using debconf-apt-progress, for use cases
7658 like this.&lt;/p&gt;
7659 </description>
7660 </item>
7661
7662 <item>
7663 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7664 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7665 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7666 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7667 <description>&lt;p&gt;My
7668 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7669 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7670 finally made the upgrade logs available from
7671 &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;.
7672 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7673 apt and aptitude, and found their differences interesting. This time
7674 I will only focus on their removal plans.&lt;/p&gt;
7675
7676 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7677 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7678 surprising part is that it want to remove xorg and all
7679 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7680 sure why. When asking aptitude to do the same, it want to remove 129
7681 packages, but most of them are library packages I suspect are no
7682 longer needed. Both of them want to remove bluetooth packages, which
7683 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7684
7685 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7686 which seem like a bad idea and xorg the same way as with Gnome. Asking
7687 aptitude for the same, it wants to remove 192 packages, none which are
7688 too surprising.&lt;/p&gt;
7689
7690 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7691 and avoided, and perhaps others as well. Here are the complete list
7692 of planned removals. The complete logs is available from the URL
7693 above. Note if you want to repeat these tests, that the upgrade test
7694 for kde+apt-get hung in the tasksel setup because of dpkg asking
7695 conffile questions. No idea why. I worked around it by using
7696 &#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
7697 continue.&lt;/p&gt;
7698
7699 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7700 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7701 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7702 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7703 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7704 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7705 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7706 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7707 xserver-xorg-input-kbd xserver-xorg-input-mouse
7708 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7709 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7710 xserver-xorg-video-ati xserver-xorg-video-chips
7711 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7712 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7713 xserver-xorg-video-glint xserver-xorg-video-i128
7714 xserver-xorg-video-i740 xserver-xorg-video-imstt
7715 xserver-xorg-video-intel xserver-xorg-video-mach64
7716 xserver-xorg-video-mga xserver-xorg-video-neomagic
7717 xserver-xorg-video-nsc xserver-xorg-video-nv
7718 xserver-xorg-video-openchrome xserver-xorg-video-r128
7719 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7720 xserver-xorg-video-rendition xserver-xorg-video-s3
7721 xserver-xorg-video-s3virge xserver-xorg-video-savage
7722 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7723 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7724 xserver-xorg-video-tga xserver-xorg-video-trident
7725 xserver-xorg-video-tseng xserver-xorg-video-v4l
7726 xserver-xorg-video-vesa xserver-xorg-video-vga
7727 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7728 xulrunner-1.9-gnome-support&lt;/p&gt;
7729
7730 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7731
7732 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7733 djvulibre-desktop finger gnome-app-install gnome-mount
7734 gnome-network-admin gnome-spell gnome-vfs-obexftp
7735 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7736 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7737 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7738 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7739 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7740 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7741 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7742 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7743 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7744 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7745 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7746 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7747 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7748 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7749 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7750 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7751 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7752 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7753 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7754 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7755 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7756 openoffice.org-writer2latex openssl-blacklist p7zip
7757 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7758 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7759 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7760 swfdec-mozilla totem-gstreamer update-manager wodim
7761 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7762 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7763 zip&lt;/p&gt;
7764
7765 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7766
7767 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7768 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7769 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7770 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7771 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7772 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7773 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7774 xserver-xorg-input-kbd xserver-xorg-input-mouse
7775 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7776 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7777 xserver-xorg-video-ati xserver-xorg-video-chips
7778 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7779 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7780 xserver-xorg-video-glint xserver-xorg-video-i128
7781 xserver-xorg-video-i740 xserver-xorg-video-imstt
7782 xserver-xorg-video-intel xserver-xorg-video-mach64
7783 xserver-xorg-video-mga xserver-xorg-video-neomagic
7784 xserver-xorg-video-nsc xserver-xorg-video-nv
7785 xserver-xorg-video-openchrome xserver-xorg-video-r128
7786 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7787 xserver-xorg-video-rendition xserver-xorg-video-s3
7788 xserver-xorg-video-s3virge xserver-xorg-video-savage
7789 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7790 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7791 xserver-xorg-video-tga xserver-xorg-video-trident
7792 xserver-xorg-video-tseng xserver-xorg-video-v4l
7793 xserver-xorg-video-vesa xserver-xorg-video-vga
7794 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7795
7796 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7797 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7798 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7799 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7800 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7801 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7802 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7803 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7804 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7805 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7806 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7807 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7808 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7809 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7810 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7811 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7812 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7813 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7814 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7815 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7816 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7817 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7818 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7819 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7820 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7821 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7822 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7823 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7824 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7825 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7826 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7827 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7828 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7829 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7830 texlive-common texlive-doc-base texlive-fonts-recommended
7831 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7832 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7833 xulrunner-1.9&lt;/p&gt;
7834
7835 </description>
7836 </item>
7837
7838 <item>
7839 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7840 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7841 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7842 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7843 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7844 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7845 have been discovered and reported in the process
7846 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7847 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7848 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7849 kdebase-workspace-data), and to get a more regular testing going on, I
7850 am working on a script to automate the test.&lt;/p&gt;
7851
7852 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7853 Gnome or KDE desktop installation inside the chroot before upgrading
7854 it. To ensure no services are started in the chroot, a policy-rc.d
7855 script is inserted. To make sure tasksel believe it is to install a
7856 desktop on a laptop, the tasksel tests are replaced in the chroot
7857 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7858
7859 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7860 currently always fail because udev refuses to upgrade with the kernel
7861 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7862 is created. The bug report
7863 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7864 this problem do not trigger in a chroot, but I touch the file anyway
7865 to make sure the upgrade go well. Testing on virtual and real
7866 hardware have failed me because of udev so far, and creating this file
7867 do the trick in such settings anyway. This is a
7868 &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
7869 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7870 maintainer because he lack the resources to rewrite udev to keep
7871 working with old kernels or something like that. I really wish the
7872 udev upstream would keep udev backwards compatible, to avoid such
7873 upgrade problem, but given that they fail to do so, I guess
7874 documenting the way out of this mess is the best option we got for
7875 Debian Squeeze.&lt;/p&gt;
7876
7877 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7878 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7879 trick:&lt;/p&gt;
7880
7881 &lt;blockquote&gt;&lt;pre&gt;
7882 #!/bin/sh
7883 set -ex
7884
7885 if [ &quot;$1&quot; ] ; then
7886 desktop=$1
7887 else
7888 desktop=gnome
7889 fi
7890
7891 from=lenny
7892 to=squeeze
7893
7894 exec &amp;lt; /dev/null
7895 unset LANG
7896 mirror=http://ftp.skolelinux.org/debian
7897 tmpdir=chroot-$from-upgrade-$to-$desktop
7898 fuser -mv .
7899 debootstrap $from $tmpdir $mirror
7900 chroot $tmpdir aptitude update
7901 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7902 #!/bin/sh
7903 exit 101
7904 EOF
7905 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7906 exit_cleanup() {
7907 umount $tmpdir/proc
7908 }
7909 mount -t proc proc $tmpdir/proc
7910 # Make sure proc is unmounted also on failure
7911 trap exit_cleanup EXIT INT
7912
7913 chroot $tmpdir aptitude -y install debconf-utils
7914
7915 # Make sure tasksel autoselection trigger. It need the test scripts
7916 # to return the correct answers.
7917 echo tasksel tasksel/desktop multiselect $desktop | \
7918 chroot $tmpdir debconf-set-selections
7919
7920 # Include the desktop and laptop task
7921 for test in desktop laptop ; do
7922 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7923 #!/bin/sh
7924 exit 2
7925 EOF
7926 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7927 done
7928
7929 DEBIAN_FRONTEND=noninteractive
7930 DEBIAN_PRIORITY=critical
7931 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7932 chroot $tmpdir tasksel --new-install
7933
7934 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7935 chroot $tmpdir aptitude update
7936 touch $tmpdir/etc/udev/kernel-upgrade
7937 chroot $tmpdir aptitude -y dist-upgrade
7938 fuser -mv
7939 &lt;/pre&gt;&lt;/blockquote&gt;
7940
7941 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7942 with aptitude, but I have not had time to look at how they behave
7943 differently so far. I hope to get a cron job running to do the test
7944 regularly and post the result on the web. The Gnome upgrade currently
7945 work, while the KDE upgrade fail because of the bug in
7946 kdebase-workspace-data&lt;/p&gt;
7947
7948 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7949 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7950 post, so I will refrain from trying. I can report that for Gnome,
7951 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7952 remove and 1 not upgraded and 1024MB need to be downloaded while for
7953 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7954 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7955
7956 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7957 is able to migrate to dependency based boot sequencing and parallel
7958 booting without a hitch. Was unsure if there were still bugs with
7959 packages failing to clean up their obsolete init.d script during
7960 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7961 packages.&lt;/p&gt;
7962 </description>
7963 </item>
7964
7965 <item>
7966 <title>Upstart or sysvinit - as init.d scripts see it</title>
7967 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7969 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7970 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7971 scripts to migrate (some of) their operations to upstart job while
7972 keeping the init.d for hurd and kfreebsd. The packages with such
7973 needs will need a way to get their init.d scripts to behave
7974 differently when used with sysvinit and with upstart. Because of
7975 this, I had a look at the environment variables set when a init.d
7976 script is running under upstart, and when it is not.&lt;/p&gt;
7977
7978 &lt;p&gt;With upstart, I notice these environment variables are set when a
7979 script is started from rcS.d/ (ignoring some irrelevant ones like
7980 COLUMNS):&lt;/p&gt;
7981
7982 &lt;blockquote&gt;&lt;pre&gt;
7983 DEFAULT_RUNLEVEL=2
7984 previous=N
7985 PREVLEVEL=
7986 RUNLEVEL=
7987 runlevel=S
7988 UPSTART_EVENTS=startup
7989 UPSTART_INSTANCE=
7990 UPSTART_JOB=rc-sysinit
7991 &lt;/pre&gt;&lt;/blockquote&gt;
7992
7993 &lt;p&gt;With sysvinit, these environment variables are set for the same
7994 script.&lt;/p&gt;
7995
7996 &lt;blockquote&gt;&lt;pre&gt;
7997 INIT_VERSION=sysvinit-2.88
7998 previous=N
7999 PREVLEVEL=N
8000 RUNLEVEL=S
8001 runlevel=S
8002 &lt;/pre&gt;&lt;/blockquote&gt;
8003
8004 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
8005 sysvinit are not set by upstart. Not sure if it is intentional or not
8006 to not be compatible with sysvinit in this regard.&lt;/p&gt;
8007
8008 &lt;p&gt;For scripts needing to behave differently when upstart is used,
8009 looking for the UPSTART_JOB environment variable seem to be a good
8010 choice.&lt;/p&gt;
8011 </description>
8012 </item>
8013
8014 <item>
8015 <title>A manual for standards wars...</title>
8016 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
8017 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
8018 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
8019 <description>&lt;p&gt;Via the
8020 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
8021 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
8022 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
8023 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
8024 following the standards wars of today.&lt;/p&gt;
8025 </description>
8026 </item>
8027
8028 <item>
8029 <title>Sitesummary tip: Listing computer hardware models used at site</title>
8030 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
8031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
8032 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
8033 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
8034 to get a list of the machine types in use thanks to the DMI
8035 information extracted from each machine. The script to do so is
8036 included in the sitesummary package, and here is example output from
8037 the Skolelinux build servers:&lt;/p&gt;
8038
8039 &lt;blockquote&gt;&lt;pre&gt;
8040 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8041 vendor count
8042 Dell Computer Corporation 1
8043 PowerEdge 1750 1
8044 IBM 1
8045 eserver xSeries 345 -[8670M1X]- 1
8046 Intel 2
8047 [no-dmi-info] 3
8048 maintainer:~#
8049 &lt;/pre&gt;&lt;/blockquote&gt;
8050
8051 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
8052 provided in each machine. Here there are Intel machines without model
8053 information listed with Intel as vendor and no model, and virtual Xen
8054 machines listed as [no-dmi-info]. One can add -l as a command line
8055 option to list the individual machines.&lt;/p&gt;
8056
8057 &lt;p&gt;A larger list is
8058 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
8059 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
8060 provide the basic sitesummary report publicly. In their report there
8061 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
8062 their machines, and as sitesummary is available in both distributions,
8063 it is trivial to get all of them to report to the same central
8064 collector.&lt;/p&gt;
8065 </description>
8066 </item>
8067
8068 <item>
8069 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
8070 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
8071 <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>
8072 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
8073 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
8074 start at boot when an NVidia video card is used is handled. The
8075 problem seem to be that the nvidia X.org driver uses a long time to
8076 initialize, and this duration is longer than kdm is configured to
8077 wait.&lt;/p&gt;
8078
8079 &lt;p&gt;I came across two bugs related to this issue,
8080 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
8081 against initscripts and passed on to nvidia-glx when it became obvious
8082 that the nvidia drivers were involved, and
8083 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
8084 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
8085
8086 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
8087 problem nvidia video card owners experience and make sure the Debian
8088 distribution work out of the box for these users. The nvidia driver
8089 maintainers expect kdm to be set up to wait longer, while kdm expect
8090 the nvidia driver maintainers to fix the driver to start faster, and
8091 while they wait for each other I guess the users end up switching to a
8092 distribution that work for them. I have no idea what the solution is,
8093 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
8094
8095 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
8096 </description>
8097 </item>
8098
8099 <item>
8100 <title>Parallellized boot seem to hold up well in Debian/testing</title>
8101 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
8102 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
8103 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
8104 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
8105 The feature seem to hold up pretty well, but three fairly serious
8106 issues are known and should be solved:
8107
8108 &lt;p&gt;&lt;ul&gt;
8109
8110 &lt;li&gt;The wicd package seen to
8111 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
8112 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
8113 parallel booting is enabled. No idea why, but the wicd maintainer
8114 seem to be on the case.&lt;/li&gt;
8115
8116 &lt;li&gt;The nvidia X driver seem to
8117 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
8118 triggered more easily when parallel booting is in effect. The
8119 maintainer is on the case.&lt;/li&gt;
8120
8121 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
8122 sequencing (the shutdown is broken) when old file-rc users
8123 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
8124 sysv-rc. One way to solve it would be for file-rc to create
8125 /etc/init.d/.legacy-bootordering, and another is to try to make
8126 sysv-rc more robust. Will investigate some more and probably upload a
8127 workaround in sysv-rc to help those trying to move from file-rc to
8128 sysv-rc get a working shutdown.&lt;/li&gt;
8129
8130 &lt;/ul&gt;&lt;/p&gt;
8131
8132 &lt;p&gt;All in all not many surprising issues, and all of them seem
8133 solvable before Squeeze is released. In addition to these there are
8134 some packages with bugs in their dependencies and run level settings,
8135 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
8136
8137 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8138 the BTS, please usertag the report to get it to show up at
8139 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8140 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8141
8142 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
8143 </description>
8144 </item>
8145
8146 <item>
8147 <title>More flexible firmware handling in debian-installer</title>
8148 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
8149 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
8150 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
8151 <description>&lt;p&gt;After a long break from debian-installer development, I finally
8152 found time today to return to the project. Having to spend less time
8153 working dependency based boot in debian, as it is almost complete now,
8154 definitely helped freeing some time.&lt;/p&gt;
8155
8156 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
8157 include some firmware packages on the Debian Edu CDs, those needed to
8158 get disk and network controllers working. Without having these
8159 firmware packages available during installation, it is impossible to
8160 install Debian Edu on the given machine, and because our target group
8161 are non-technical people, asking them to provide firmware packages on
8162 an external medium is a support pain. Initially, I expected it to be
8163 enough to include the firmware packages on the CD to get
8164 debian-installer to find and use them. This proved to be wrong.
8165 Next, I hoped it was enough to symlink the relevant firmware packages
8166 to some useful location on the CD (tried /cdrom/ and
8167 /cdrom/firmware/). This also proved to not work, and at this point I
8168 found time to look at the debian-installer code to figure out what was
8169 going to work.&lt;/p&gt;
8170
8171 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
8172 look revealed that it would only look for firmware packages outside
8173 the installation media, so the CD was never checked for firmware
8174 packages. It would only check USB sticks, floppies and other
8175 &quot;external&quot; media devices. Today I changed it to also look in the
8176 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8177 solve the problem I ran into with Debian edu. I also changed it to
8178 look in /firmware/, to make sure the installer also find firmware
8179 provided in the initrd when booting the installer via PXE, to allow us
8180 to provide the same feature in the PXE setup included in Debian
8181 Edu.&lt;/p&gt;
8182
8183 &lt;p&gt;To make sure firmware deb packages with a license questions are not
8184 activated without asking if the license is accepted, I extended
8185 hw-detect to look for preinst scripts in the firmware packages, and
8186 run these before activating the firmware during installation. The
8187 license question is asked using debconf in the preinst, so this should
8188 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
8189
8190 &lt;p&gt;If you want to discuss the details of these features, please
8191 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
8192 </description>
8193 </item>
8194
8195 <item>
8196 <title>Parallellized boot is now the default in Debian/unstable</title>
8197 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
8198 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
8199 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
8200 <description>&lt;p&gt;Since this evening, parallel booting is the default in
8201 Debian/unstable for machines using dependency based boot sequencing.
8202 Apparently the testing of concurrent booting has been wider than
8203 expected, if I am to believe the
8204 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8205 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
8206 with the feature this weekend, to give us some time to detect any
8207 remaining problems before Squeeze is frozen. If serious problems are
8208 detected, it is simple to change the default back to sequential boot.
8209 The upload of the new sysvinit package also activate a new upstream
8210 version.&lt;/p&gt;
8211
8212 More information about
8213 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8214 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
8215 currently possible to disable parallel booting when one run into
8216 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
8217
8218 &lt;blockquote&gt;&lt;pre&gt;
8219 CONCURRENCY=none
8220 &lt;/pre&gt;&lt;/blockquote&gt;
8221
8222 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8223 the BTS, please usertag the report to get it to show up at
8224 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8225 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8226 </description>
8227 </item>
8228
8229 <item>
8230 <title>Sitesummary tip: Listing MAC address of all clients</title>
8231 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
8232 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
8233 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
8234 <description>&lt;p&gt;In the recent Debian Edu versions, the
8235 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
8236 system&lt;/a&gt; is used to keep track of the machines in the school
8237 network. Each machine will automatically report its status to the
8238 central server after boot and once per night. The network setup is
8239 also reported, and using this information it is possible to get the
8240 MAC address of all network interfaces in the machines. This is useful
8241 to update the DHCP configuration.&lt;/p&gt;
8242
8243 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
8244 ist all MAC addresses of all machines reporting to sitesummary. Run
8245 this on the collector host:&lt;/p&gt;
8246
8247 &lt;blockquote&gt;&lt;pre&gt;
8248 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
8249 &lt;/pre&gt;&lt;/blockquote&gt;
8250
8251 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
8252 line per machine and with space between the MAC addresses.&lt;/p&gt;
8253
8254 &lt;p&gt;To allow system administrators easier job at adding static DHCP
8255 addresses for hosts, it would be possible to extend this to fetch
8256 machine information from sitesummary and update the DHCP and DNS
8257 tables in LDAP using this information. Such tool is unfortunately not
8258 written yet.&lt;/p&gt;
8259 </description>
8260 </item>
8261
8262 <item>
8263 <title>systemd, an interesting alternative to upstart</title>
8264 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
8265 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
8266 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
8267 <description>&lt;p&gt;The last few days a new boot system called
8268 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
8269 has been
8270 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
8271
8272 to the free software world. I have not yet had time to play around
8273 with it, but it seem to be a very interesting alternative to
8274 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
8275 a good alternative for Debian when we are able to switch to an event
8276 based boot system. Tollef is
8277 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
8278 systemd into Debian, and I look forward to seeing how well it work. I
8279 like the fact that systemd handles init.d scripts with dependency
8280 information natively, allowing them to run in parallel where upstart
8281 at the moment do not.&lt;/p&gt;
8282
8283 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
8284 platform support. It only work on recent Linux kernels, and also need
8285 some new kernel features enabled to function properly. This means
8286 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8287 system. Not sure how that will be handled if systemd proves to be the
8288 way forward.&lt;/p&gt;
8289
8290 &lt;p&gt;In the mean time, based on the
8291 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8292 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
8293 decided to enable full parallel booting as the default in Debian as
8294 soon as possible (probably this weekend or early next week), to see if
8295 there are any remaining serious bugs in the init.d dependencies. A
8296 new version of the sysvinit package implementing this change is
8297 already in experimental. If all go well, Squeeze will be released
8298 with parallel booting enabled by default.&lt;/p&gt;
8299 </description>
8300 </item>
8301
8302 <item>
8303 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
8304 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
8305 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
8306 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
8307 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
8308 complete, so complete that it is actually possible to run all the
8309 init.d scripts in parallell based on these dependencies. If you want
8310 to test your Squeeze system, make sure
8311 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8312 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8313 /etc/default/rcS:&lt;/p&gt;
8314
8315 &lt;blockquote&gt;&lt;pre&gt;
8316 CONCURRENCY=makefile
8317 &lt;/pre&gt;&lt;/blockquote&gt;
8318
8319 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8320 scripts in parallel using the dependency information stored in
8321 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8322 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8323 to try to start the kdm and gdm scripts as early as possible, and will
8324 start the facilities required by kdm or gdm as early as possible to
8325 make this happen.&lt;/p&gt;
8326
8327 &lt;p&gt;Give it a try, and see if you like the result. If some services
8328 fail to start properly, it is most likely because they have incomplete
8329 init.d script dependencies in their startup script (or some of their
8330 dependent scripts have incomplete dependencies). Report bugs and get
8331 the package maintainers to fix it. :)&lt;/p&gt;
8332
8333 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8334 manage to get the init.d script dependencies complete and correct. I
8335 expect we will get there in Squeeze+1, if we get manage to test and
8336 fix the remaining issues.&lt;/p&gt;
8337
8338 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8339 the BTS, please usertag the report to get it to show up at
8340 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8341 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8342 </description>
8343 </item>
8344
8345 <item>
8346 <title>Debian has switched to dependency based boot sequencing</title>
8347 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8348 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8349 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8350 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8351 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8352 have been migrated to using dependency based boot sequencing. This
8353 conclude work me and others have been doing for the last three days.
8354 It feels great to see this finally part of the default Debian
8355 installation. Now we just need to weed out the last few problems that
8356 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8357
8358 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8359 fixing the more fundamental problem of handing the event based
8360 non-predictable kernel in the early boot.&lt;/p&gt;
8361 </description>
8362 </item>
8363
8364 <item>
8365 <title>Taking over sysvinit development</title>
8366 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8367 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8368 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8369 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8370 the existing sysvinit upstream developer, I decided a few weeks ago to
8371 take over the package and become the new upstream. The number of
8372 patches to track for the Debian package was becoming a burden, and the
8373 lack of synchronization between the distribution made it hard to keep
8374 the package up to date.&lt;/p&gt;
8375
8376 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8377 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8378 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8379 and Fedora), based on the patches currently in use in these
8380 distributions. We Debian maintainers plan to move to this tarball as
8381 the new upstream as soon as we find time to do the merge. Since the
8382 new tarball was created, we agreed with Werner at SuSe to make a new
8383 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8384 development there. The project is registered and currently waiting
8385 for approval by the Savannah administrators, and as soon as it is
8386 approved, we will import the old versions from svn and continue
8387 working on the future release.&lt;/p&gt;
8388
8389 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8390 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8391 </description>
8392 </item>
8393
8394 <item>
8395 <title>Debian boots quicker and quicker</title>
8396 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8397 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8398 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8399 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8400 people involved in the boot system on Debian and Ubuntu, to see if we
8401 could find more ways to speed up the boot system. This was an Ubuntu
8402 funded
8403 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8404 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8405 of boot systems, and ways to handle the increasing number of boot
8406 issues introduced by the Linux kernel becoming more and more
8407 asynchronous and event base. The Ubuntu approach using udev and
8408 upstart might be a good way forward. Time will show.&lt;/p&gt;
8409
8410 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8411 process in Debian. All of these should be applied to get a quick
8412 boot:&lt;/p&gt;
8413
8414 &lt;ul&gt;
8415
8416 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8417
8418 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8419 clock is in UTC.&lt;/li&gt;
8420
8421 &lt;li&gt;Install and activate the insserv package to enable
8422 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8423 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8424
8425 &lt;/ul&gt;
8426
8427 These points are based on the Google summer of code work done by
8428 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8429 Villegas&lt;/a&gt;.
8430
8431 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8432 unstable yesterday. When we tested it, we were able to cut 6 seconds
8433 from the boot sequence. It depend on very correct dependency
8434 declaration in all init.d scripts, so I expect us to find edge cases
8435 where the dependences in some scripts are slightly wrong when we start
8436 using this.&lt;/p&gt;
8437
8438 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8439 introduced by Raphael Geissert today, one that could affect the
8440 startup speed as well. Instead of starting some scripts concurrently
8441 from rcS.d/ and another set of scripts from rc2.d/, it would be
8442 possible to run a of them in the same process. A quick way to test
8443 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8444 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8445 </description>
8446 </item>
8447
8448 <item>
8449 <title>BSAs påstander om piratkopiering møter motstand</title>
8450 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8451 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8452 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8453 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8454 programvareselskapene som Microsoft og Apple, publisert en rapport der
8455 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8456 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8457 dager siden kom
8458 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8459 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8460 dagene. Et spesielt interessant kommentar fra Sverige,
8461 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8462 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8463
8464 &lt;blockquote&gt;
8465 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8466 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8467 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8468 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8469 &lt;/blockquote&gt;
8470
8471 &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
8472 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8473 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8474 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8475 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8476
8477 &lt;p&gt;Fant lenkene via &lt;a
8478 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8479 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8480 </description>
8481 </item>
8482
8483 <item>
8484 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8485 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8486 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8487 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8488 <description>&lt;p&gt;Kom over
8489 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8490 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8491 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8492 jobber til daglig. En rask opptelling forteller meg at vi har 490
8493 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8494 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8495 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8496 </description>
8497 </item>
8498
8499 <item>
8500 <title>Kryptert harddisk - naturligvis</title>
8501 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8502 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8503 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8504 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8505 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8506 når en tar tap av arbeidstid, fortrolige dokumenter,
8507 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8508 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8509 til at jeg har kryptert harddisken på både kontormaskinen og min
8510 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8511 komme på avveie, den første informasjon relatert til jobben min ved
8512 Universitetet i Oslo, og den andre relatert til blant annet
8513 foreningsarbeide. Kryptering av diskene gjør at det er lite
8514 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8515 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8516 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8517 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8518 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8519 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8520 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8521 det er gjort slik jeg gjør det er minimale, og gevinstene er
8522 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8523 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8524
8525 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8526 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8527 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8528 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8529 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8530 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8531 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8532 betydelige.&lt;/p&gt;
8533 </description>
8534 </item>
8535
8536 <item>
8537 <title>Two projects that have improved the quality of free software a lot</title>
8538 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8539 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8540 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8541 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8542 quality of free software, and I wanted to mention both in case someone
8543 do not yet know them.&lt;/p&gt;
8544
8545 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8546 tool to detect and expose errors in the memory handling of programs.
8547 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8548 and it will report any problems on stdout. It is even better if the
8549 program include debug information. With debug information, it is able
8550 to report the source file name and line number where the problem
8551 occurs. It can report things like &#39;reading past memory block in file
8552 X line N, the memory block was allocated in file Y, line M&#39;, and
8553 &#39;using uninitialised value in control logic&#39;. This tool has made it
8554 trivial to investigate reproducible crash bugs in programs, and have
8555 reduced the number of this kind of bugs in free software a lot.
8556
8557 &lt;p&gt;The second one is
8558 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8559 a source code checker. It is able to process the source of a program
8560 and find problems in the logic without running the program. It
8561 started out as the Stanford Checker and became well known when it was
8562 used to find bugs in the Linux kernel. It is now a commercial tool
8563 and the company behind it is running
8564 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8565 free software community, where a lot of free software projects get
8566 their source checked for free. Several thousand defects have been
8567 found and fixed so far. It can find errors like &#39;lock L taken in file
8568 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8569 Y lines O to P can never be executed&#39;. The projects included in the
8570 community service project have managed to get rid of a lot of
8571 reliability problems thanks to Coverity.&lt;/p&gt;
8572
8573 &lt;p&gt;I believe tools like this, that are able to automatically find
8574 errors in the source, are vital to improve the quality of software and
8575 make sure we can get rid of the crashing and failing software we are
8576 surrounded by today.&lt;/p&gt;
8577 </description>
8578 </item>
8579
8580 <item>
8581 <title>No patch is not better than a useless patch</title>
8582 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8583 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8584 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8585 <description>&lt;p&gt;Julien Blache
8586 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8587 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8588 patch allow one to discuss a concrete and proposed solution, and also
8589 prove that the issue at hand is important enough for someone to spent
8590 time on fixing it. No patch do not provide any of these positive
8591 properties.&lt;/p&gt;
8592 </description>
8593 </item>
8594
8595 <item>
8596 <title>Standardize on protocols and formats, not vendors and applications</title>
8597 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8598 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8599 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8600 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8601 very good one to form a long lived computer infrastructure. It is the
8602 simple one, lost by many in todays computer industry: Standardize on
8603 open network protocols and open exchange/storage formats, not applications.
8604 Applications come and go, while protocols and files tend to stay, and
8605 thus one want to make it easy to change application and vendor, while
8606 avoiding conversion costs and locking users to a specific platform or
8607 application.&lt;/p&gt;
8608
8609 &lt;p&gt;This approach make it possible to replace the client applications
8610 independently of the server applications. One can even allow users to
8611 use several different applications as long as they handle the selected
8612 protocol and format. In the normal case, only one client application
8613 is recommended and users only get help if they choose to use this
8614 application, but those that want to deviate from the easy path are not
8615 blocked from doing so.&lt;/p&gt;
8616
8617 &lt;p&gt;It also allow us to replace the server side without forcing the
8618 users to replace their applications, and thus allow us to select the
8619 best server implementation at any moment, when scale and resouce
8620 requirements change.&lt;/p&gt;
8621
8622 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8623 open formats, but I would never recommend standardizing on a single
8624 application that do not use open network protocol or open formats.&lt;/p&gt;
8625 </description>
8626 </item>
8627
8628 <item>
8629 <title>Returning from Skolelinux developer gathering</title>
8630 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8631 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8632 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8633 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8634 Edu/Skolelinux development gathering. I got a bit done tuning the
8635 desktop, and looked into the dynamic service location protocol
8636 implementation avahi. It look like it could be useful for us. Almost
8637 30 people participated, and I believe it was a great environment to
8638 get to know the Skolelinux system. Walter Bender, involved in the
8639 development of the Sugar educational platform, presented his stuff and
8640 also helped me improve my OLPC installation. He also showed me that
8641 his Turtle Art application can be used in standalone mode, and we
8642 agreed that I would help getting it packaged for Debian. As a
8643 standalone application it would be great for Debian Edu. We also
8644 tried to get the video conferencing working with two OLPCs, but that
8645 proved to be too hard for us. The application seem to need more work
8646 before it is ready for me. I look forward to getting home and relax
8647 now. :)&lt;/p&gt;
8648 </description>
8649 </item>
8650
8651 <item>
8652 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8653 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8654 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8655 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8656 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8657 optimal. There is RFC 2307 documenting one way to store NIS maps in
8658 LDAP, and a modified version of this normally called RFC 2307bis, with
8659 some modifications to be compatible with Active Directory. The RFC
8660 specification handle the content of a lot of system databases, but do
8661 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8662
8663 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8664 we would like to store information about users, SMB clients/hosts,
8665 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8666 and LTSP configuration in LDAP. These objects have a lot in common,
8667 but with the current LDAP schemas it is not possible to have one
8668 object per entity. For example, one need to have at least three LDAP
8669 objects for a given computer, one with the SMB related stuff, one with
8670 DNS information and another with DHCP information. The schemas
8671 provided for DNS and DHCP are impossible to combine into one LDAP
8672 object. In addition, it is impossible to implement quick queries for
8673 netgroup membership, because of the way NIS triples are implemented.
8674 It just do not scale. I believe it is time for a few RFC
8675 specifications to cleam up this mess.&lt;/p&gt;
8676
8677 &lt;p&gt;I would like to have one LDAP object representing each computer in
8678 the network, and this object can then keep the SMB (ie host key), DHCP
8679 (mac address/name) and DNS (name/IP address) settings in one place.
8680 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8681
8682 &lt;p&gt;I would also like to have a quick way to map from a user or
8683 computer and to the net group this user or computer is a member.&lt;/p&gt;
8684
8685 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8686 in this regard, and the unix side need to catch up. Time to start a
8687 new IETF work group?&lt;/p&gt;
8688 </description>
8689 </item>
8690
8691 <item>
8692 <title>Endelig er Debian Lenny gitt ut</title>
8693 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8695 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8696 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8697 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8698 Et langt steg videre for Debian-prosjektet, og en rekke nye
8699 programpakker blir nå tilgjengelig for de av oss som bruker den
8700 stabile utgaven av Debian. Neste steg er nå å få
8701 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8702 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8703 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8704 slippes løs på skolene. Takk til alle debian-utviklerne som har
8705 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8706 bootsekvens tilgjengelig i stabil utgave, vha pakken
8707 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8708 </description>
8709 </item>
8710
8711 <item>
8712 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8713 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8714 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8715 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8716 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8717 Oslo. Most of Saturday was used for the general assemly for the
8718 member organization, but the rest of the weekend I used to tune the
8719 LTSP installation. LTSP now work out of the box on the 10-network.
8720 Acer Aspire One proved to be a very nice thin client, with both
8721 screen, mouse and keybard in a small box. Was working on getting the
8722 diskless workstation setup configured out of the box, but did not
8723 finish it before the weekend was up.&lt;/p&gt;
8724
8725 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8726 the Brazilian group, so that will have to wait for the next
8727 development gathering. Would love to have the Debian Edu installer
8728 automatically detect and configure a multiseat setup when it find one
8729 of these cards.&lt;/p&gt;
8730 </description>
8731 </item>
8732
8733 <item>
8734 <title>The sorry state of multimedia browser plugins in Debian</title>
8735 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8736 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8737 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8738 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8739 plugins available in Debian Lenny, to see which one we should use by
8740 default in Debian Edu. We need an embedded video playing plugin with
8741 control buttons to pause or stop the video, and capable of streaming
8742 all the multimedia content available on the web. The test results and
8743 notes are available on
8744 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8745 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8746 fill this need. My personal video player favorite, VLC, has a really
8747 bad plugin which fail on a lot of the test pages. A lot of the MIME
8748 types I would expect to work with any free software player (like
8749 video/ogg), just do not work. And simple formats like the
8750 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8751 totem and vlc plugins. I hope the situation will improve soon. No
8752 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8753
8754 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8755 be the only one fitting our needs. :/&lt;/p&gt;
8756 </description>
8757 </item>
8758
8759 </channel>
8760 </rss>