]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
10608dd02771a67138d36c4255e70b56438ea218
[homepage.git] / blog / tags / debian / debian.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged debian</title>
5 <description>Entries tagged debian</description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>Debian now with ZFS on Linux included</title>
11 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
13 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
14 <description>&lt;p&gt;Today, after many years of hard work from many people,
15 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
16 Debian. The package status can be seen on
17 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
18 for zfs-linux&lt;/a&gt;. and
19 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
20 team status page&lt;/a&gt;. If you want to help out, please join us.
21 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
22 source code&lt;/a&gt; is available via git on Alioth. It would also be
23 great if you could help out with
24 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
25 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
26 </description>
27 </item>
28
29 <item>
30 <title>What is the best multimedia player in Debian?</title>
31 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
32 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
33 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
34 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
35 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
36
37 &lt;p&gt;A few years ago, I had a look at the media support for Browser
38 plugins in Debian, to get an idea which plugins to include in Debian
39 Edu. I created a script to extract the set of supported MIME types
40 for each plugin, and used this to find out which multimedia browser
41 plugin supported most file formats / media types.
42 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
43 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
44 not been updated for a while. But browser plugins are less relevant
45 these days, so I thought it was time to look at standalone
46 players.&lt;/p&gt;
47
48 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
49 player when I wanted to play videos from the Norwegian National
50 Broadcasting Company, and decided to investigate why. The cause is a
51 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
52 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
53 of MIME types announced in the desktop file and the browser plugin,
54 only to discover that there is quite a large difference between the
55 two for VLC. This discovery made me dig up the script I used to
56 compare browser plugins, and adjust it to compare desktop files
57 instead, to try to figure out which multimedia player in Debian
58 support most file formats.&lt;/p&gt;
59
60 &lt;p&gt;The result can be seen on the Debian Wiki, as
61 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
62 table listing all MIME types supported by one of the packages included
63 in the table&lt;/a&gt;, with the package supporting most MIME types being
64 listed first in the table.&lt;/p&gt;
65
66 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
67 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
68 kmplayer. Time for the other players to update their announced MIME
69 support?&lt;/p&gt;
70 </description>
71 </item>
72
73 <item>
74 <title>The Pyra - handheld computer with Debian preinstalled</title>
75 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
76 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
77 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
78 <description>A friend of mine made me aware of
79 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
80 handheld computer which will be delivered with Debian preinstalled. I
81 would love to get one of those for my birthday. :)&lt;/p&gt;
82
83 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
84 plugs and many others connectors, and include a full keyboard and a 5&quot;
85 LCD touch screen. The 6000mAh battery is claimed to provide a whole
86 day of battery life time, but I have not seen any independent tests
87 confirming this. The vendor is still collecting preorders, and the
88 last I heard last night was that 22 more orders were needed before
89 production started.&lt;/p&gt;
90
91 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
92 Debian. Please let me know if you know of any others. Is it the
93 first computer being sold with Debian preinstalled?&lt;/p&gt;
94 </description>
95 </item>
96
97 <item>
98 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
99 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
100 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
101 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
102 <description>&lt;p&gt;During this weekends
103 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
104 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
105 to make sure there are good books about Debian available in Norwegian
106 Bokmål, and got in touch with the people behind the
107 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
108 project&lt;/a&gt; to get started. If you want to help out, please start
109 contributing using
110 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
111 hosted weblate project page&lt;/a&gt;, and get in touch using
112 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
113 translators mailing list&lt;/a&gt;. Please also check out
114 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
115 contributors&lt;/a&gt;.&lt;/p&gt;
116
117 &lt;p&gt;The book is already available on paper in English, French and
118 Japanese, and our goal is to get it available on paper in Norwegian
119 Bokmål too. In addition to the paper edition, there are also EPUB and
120 Mobi versions available. And there are incomplete translations
121 available for many more languages.&lt;/p&gt;
122 </description>
123 </item>
124
125 <item>
126 <title>One in two hundred Debian users using ZFS on Linux?</title>
127 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
128 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
129 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
130 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
131 packages in Debian, and was quite surprised with what I found. I use
132 ZFS myself at home, but did not really expect many others to do so.
133 But I might be wrong.&lt;/p&gt;
134
135 &lt;p&gt;According to
136 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
137 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
138 0.53% of the population, with the package installed. As far as I know
139 the only use of the spl-linux package is as a support library for ZFS
140 on Linux, so I use it here as proxy for measuring the number of ZFS
141 installation on Linux in Debian. In the kFreeBSD variant of Debian
142 the ZFS feature is already available, and there
143 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
144 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
145 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
146
147 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
148 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
149 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
150 cleared, the package is still not in Debian. The package is again in
151 the NEW queue. Several uploads have been rejected so far because the
152 debian/copyright file was incomplete or wrong, but there is no reason
153 to give up. The current status can be seen on
154 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
155 team status page&lt;/a&gt;, and
156 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
157 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
158
159 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
160 my home server can function in the future using only official Debian
161 packages, and the current blocker is to get the debian/copyright file
162 accepted by the FTP masters in Debian, I decided a while back to try
163 to help out the team. This was the background for my blog post about
164 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
165 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
166 used the techniques I explored there to try to find any errors in the
167 copyright file. It is not very easy to check every one of the around
168 2000 files in the source package, but I hope we this time got it
169 right. If you want to help out, check out the git source and try to
170 find missing entries in the debian/copyright file.&lt;/p&gt;
171 </description>
172 </item>
173
174 <item>
175 <title>Full battery stats collector is now available in Debian</title>
176 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
177 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
178 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
179 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
180 extended collector that will collect the complete battery history for
181 later processing and graphing. The original collector store the
182 battery level as percentage of last full level, while the new
183 collector also record battery vendor, model, serial number, design
184 full level, last full level and current battery level. This make it
185 possible to predict the lifetime of the battery as well as visualise
186 the energy flow when the battery is charging or discharging.&lt;/p&gt;
187
188 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
189 in the version 0.5.1 package in unstable. Get the new battery level graph
190 and lifetime prediction by running:
191
192 &lt;p&gt;&lt;pre&gt;
193 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
194 &lt;/pre&gt;&lt;/p&gt;
195
196 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
197
198 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
199 entry yet):&lt;/p&gt;
200
201 &lt;p&gt;&lt;pre&gt;
202 /usr/share/battery-stats/battery-stats-graph-flow
203 &lt;/pre&gt;&lt;/p&gt;
204
205 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
206 when there are few data points. The graphs look a bit better with a
207 few years of data.&lt;/p&gt;
208
209 &lt;p&gt;A while back one important feature I use in the battery stats
210 collector broke in Debian. The scripts in
211 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
212 suspect it happened when Jessie started using systemd, but I do not
213 know. The issue is reported as
214 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
215 pm-utils. I managed to work around it by adding an udev rule to call
216 the collector script every time the power connector is connected and
217 disconnected. With this fix in place it was finally time to make a
218 new release of the package, and get it into Debian.&lt;/p&gt;
219
220 &lt;p&gt;If you are interested in how your laptop battery is doing, please
221 check out the
222 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
223 in Debian unstable, or rebuild it on Jessie to get it working on
224 Debian stable. :) The upstream source is available from
225 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
226 As always, patches are very welcome.&lt;/p&gt;
227 </description>
228 </item>
229
230 <item>
231 <title>Making battery measurements a little easier in Debian</title>
232 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
233 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
234 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
235 <description>&lt;p&gt;Back in September, I blogged about
236 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
237 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
238 how it showed the decay and death of this battery (now replaced). I
239 created a simple deb package to handle the collection and graphing,
240 but did not want to upload it to Debian as there were already
241 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
242 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
243 a point of uploading a competing package when battery-stats could be
244 fixed instead. I reported a few bugs about its non-function, and
245 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
246
247 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
248 hands. The end result is that I am now the new upstream developer of
249 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
250 battery-stats in Debian, and the package in Debian unstable is finally
251 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
252 information provided by the Linux kernel. If you install the
253 battery-stats package from unstable now, you will be able to get a
254 graph of the current battery fill level, to get some idea about the
255 status of the battery. The source package build and work just fine in
256 Debian testing and stable (and probably oldstable too, but I have not
257 tested). The default graph you get for that system look like this:&lt;/p&gt;
258
259 &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;
260
261 &lt;p&gt;My plans for the future is to merge my old scripts into the
262 battery-stats package, as my old scripts collected a lot more details
263 about the battery. The scripts are merged into the upstream
264 battery-stats git repository already, but I am not convinced they work
265 yet, as I changed a lot of paths along the way. Will have to test a
266 bit more before I make a new release.&lt;/p&gt;
267
268 &lt;p&gt;I will also consider changing the file format slightly, as I
269 suspect the way I combine several values into one field might make it
270 impossible to know the type of the value when using it for processing
271 and graphing.&lt;/p&gt;
272
273 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
274 battery, check out the battery-stats package in
275 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
276 on
277 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
278 I would love some help to improve the system further.&lt;/p&gt;
279 </description>
280 </item>
281
282 <item>
283 <title>Creating, updating and checking debian/copyright semi-automatically</title>
284 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
285 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
286 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
287 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
288 details. And one of the details is the content of the
289 debian/copyright file, which should list all relevant licenses used by
290 the code in the package in question, preferably in
291 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
292 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
293
294 &lt;p&gt;For large packages with lots of contributors it is hard to write
295 and update this file manually, and if you get some detail wrong, the
296 package is normally rejected by the ftpmasters. So getting it right
297 the first time around get the package into Debian faster, and save
298 both you and the ftpmasters some work.. Today, while trying to figure
299 out what was wrong with
300 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
301 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
302 figuring out the options for doing this job automatically, or at least
303 semi-automatically.&lt;/p&gt;
304
305 &lt;p&gt;Lucikly, there are at least two tools available for generating the
306 file based on the code in the source package,
307 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
308 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
309 not sure which one of them came first, but both seem to be able to
310 create a sensible draft file. As far as I can tell, none of them can
311 be trusted to get the result just right, so the content need to be
312 polished a bit before the file is OK to upload. I found the debmake
313 option in
314 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
315 blog posts from 2014&lt;/a&gt;.
316
317 &lt;p&gt;To generate using debmake, use the -cc option:
318
319 &lt;p&gt;&lt;pre&gt;
320 debmake -cc &gt; debian/copyright
321 &lt;/pre&gt;&lt;/p&gt;
322
323 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
324 this might not be the best option.&lt;/p&gt;
325
326 &lt;p&gt;The cme option is based on a config parsing library, and I found
327 this approach in
328 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
329 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
330 dpkg-copyright&#39; option:
331
332 &lt;p&gt;&lt;pre&gt;
333 cme update dpkg-copyright
334 &lt;/pre&gt;&lt;/p&gt;
335
336 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
337 handle UTF-8 names better than debmake.&lt;/p&gt;
338
339 &lt;p&gt;When the copyright file is created, I would also like some help to
340 check if the file is correct. For this I found two good options,
341 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
342 to focus on license types and file matching, and is able to detect
343 ineffective blocks in the copyright file. The latter reports missing
344 copyright holders and years, but was confused by inconsistent license
345 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
346 fix all issues reported by them before uploading. But I do not know
347 if the tools and the ftpmasters agree on what is important to fix in a
348 copyright file, so the package might still be rejected.&lt;/p&gt;
349
350 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
351 will read through the source and try to find all copyright statements.
352 It is not comparing the result to the content of debian/copyright, but
353 can be useful when verifying the content of the copyright file.&lt;/p&gt;
354
355 &lt;p&gt;Are you aware of better tools in Debian to create and update
356 debian/copyright file. Please let me know, or blog about it on
357 planet.debian.org.&lt;/p&gt;
358
359 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
360 activities, please send Bitcoin donations to my address
361 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
362
363 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
364 on how to use licensecheck and cdbs to create a draft copyright file
365
366 &lt;p&gt;&lt;pre&gt;
367 licensecheck --copyright -r `find * -type f` | \
368 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
369 &lt;/pre&gt;&lt;/p&gt;
370
371 &lt;p&gt;He mentioned that he normally check the generated file into the
372 version control system to make it easier to discover license and
373 copyright changes in the upstream source. I will try to do the same
374 with my packages in the future.&lt;/p&gt;
375
376 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
377 against using -quiet for new users, so I removed it from the proposed
378 command line.&lt;/p&gt;
379 </description>
380 </item>
381
382 <item>
383 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
384 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
386 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
387 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
388 is taking shape in Debian, and one provided feature is a very
389 convenient way to tell you which package to install to make a given
390 firmware file available when the kernel is looking for it. This can
391 be done using apt-file too, but that is for someone else to blog
392 about. :)&lt;/p&gt;
393
394 &lt;p&gt;Here is a small recipe to find the package with a given firmware
395 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
396 picked from the set of firmware announced using appstream in Debian
397 unstable. In general you would be looking for the firmware requested
398 by the kernel during kernel module loading. To find the package
399 providing the example file, do like this:&lt;/p&gt;
400
401 &lt;blockquote&gt;&lt;pre&gt;
402 % apt install appstream
403 [...]
404 % apt update
405 [...]
406 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
407 awk &#39;/Package:/ {print $2}&#39;
408 firmware-qlogic
409 %
410 &lt;/pre&gt;&lt;/blockquote&gt;
411
412 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
413 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
414 a way appstream can use.&lt;/p&gt;
415
416 &lt;p&gt;This same approach can be used to find any package supporting a
417 given MIME type. This is very useful when you get a file you do not
418 know how to handle. First find the mime type using &lt;tt&gt;file
419 --mime-type&lt;/tt&gt;, and next look up the package providing support for
420 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
421 and you can find all packages handling this type like this:&lt;/p&gt;
422
423 &lt;blockquote&gt;&lt;pre&gt;
424 % apt install appstream
425 [...]
426 % apt update
427 [...]
428 % appstreamcli what-provides mimetype image/svg+xml | \
429 awk &#39;/Package:/ {print $2}&#39;
430 bkchem
431 phototonic
432 inkscape
433 shutter
434 tetzle
435 geeqie
436 xia
437 pinta
438 gthumb
439 karbon
440 comix
441 mirage
442 viewnior
443 postr
444 ristretto
445 kolourpaint4
446 eog
447 eom
448 gimagereader
449 midori
450 %
451 &lt;/pre&gt;&lt;/blockquote&gt;
452
453 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
454 packages providing appstream metadata.&lt;/p&gt;
455 </description>
456 </item>
457
458 <item>
459 <title>Creepy, visualise geotagged social media information - nice free software</title>
460 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
461 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
462 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
463 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
464 with the computerised radio beacon known as a mobile phone their
465 position is tracked by the phone company and often stored for a long
466 time (like every time a SMS is received or sent). And if their
467 computerised radio beacon is capable of running programs (often called
468 mobile apps) downloaded from the Internet, these programs are often
469 also capable of tracking their location (if the app requested access
470 during installation). And when these programs send out information to
471 central collection points, the location is often included, unless
472 extra care is taken to not send the location. The provided
473 information is used by several entities, for good and bad (what is
474 good and bad, depend on your point of view). What is certain, is that
475 the private sphere and the right to free movement is challenged and
476 perhaps even eradicated for those announcing their location this way,
477 when they share their whereabouts with private and public
478 entities.&lt;/p&gt;
479
480 &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;
481
482 &lt;p&gt;The phone company logs provide a register of locations to check out
483 when one want to figure out what the tracked person was doing. It is
484 unavailable for most of us, but provided to selected government
485 officials, company staff, those illegally buying information from
486 unfaithful servants and crackers stealing the information. But the
487 public information can be collected and analysed, and a free software
488 tool to do so is called
489 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
490 discovered it when I read
491 &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
492 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
493 November 2014, and decided to check if it was available in Debian.
494 The python program was in Debian, but
495 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
496 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
497 uploaded a new version which did not work quite right, but did not
498 have time to fix it then. This Christmas I decided to finally try to
499 get Creepy operational in Debian. Now a fixed version is available in
500 Debian unstable and testing, and almost all Debian specific patches
501 are now included
502 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
503
504 &lt;p&gt;The Creepy program visualises geolocation information fetched from
505 Twitter, Instagram, Flickr and Google+, and allow one to get a
506 complete picture of every social media message posted recently in a
507 given area, or track the movement of a given individual across all
508 these services. Earlier it was possible to use the search API of at
509 least some of these services without identifying oneself, but these
510 days it is impossible. This mean that to use Creepy, you need to
511 configure it to log in as yourself on these services, and provide
512 information to them about your search interests. This should be taken
513 into account when using Creepy, as it will also share information
514 about yourself with the services.&lt;/p&gt;
515
516 &lt;p&gt;The picture above show the twitter messages sent from (or at least
517 geotagged with a position from) the city centre of Oslo, the capital
518 of Norway. One useful way to use Creepy is to first look at
519 information tagged with an area of interest, and next look at all the
520 information provided by one or more individuals who was in the area.
521 I tested it by checking out which celebrity provide their location in
522 twitter messages by checkout out who sent twitter messages near a
523 Norwegian TV station, and next could track their position over time,
524 making it possible to locate their home and work place, among other
525 things. A similar technique have been
526 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
527 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
528 tool to discover lying governments, and a useful tool to help people
529 understand the value of the private information they provide to the
530 public.&lt;/p&gt;
531
532 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
533 it depend on several python modules currently missing in Jessie (at
534 least python-instagram, python-flickrapi and
535 python-requests-toolbelt).&lt;/p&gt;
536
537 &lt;p&gt;(I have uploaded
538 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
539 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
540 Creepy program in Debian.)&lt;/p&gt;
541 </description>
542 </item>
543
544 <item>
545 <title>Always download Debian packages using Tor - the simple recipe</title>
546 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
547 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
548 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
549 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
550 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
551 that those listening on the Internet lines would have good reason to
552 believe a computer have a given security hole&lt;/a&gt; if it download a
553 security fix from a Debian mirror. This is a good reason to always
554 use encrypted connections to the Debian mirror, to make sure those
555 listening do not know which IP address to attack. In August, Richard
556 Hartmann observed that encryption was not enough, when it was possible
557 to interfere download size to security patches or the fact that
558 download took place shortly after a security fix was released, and
559 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
560 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
561 was not the first to propose this, as the
562 &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;
563 package by Tim Retout already existed to make it easy to convince apt
564 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
565 aware of that package when I read the blog post from Richard.&lt;/p&gt;
566
567 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
568 sysadmins, and he set up a Tor hidden service on one of the central
569 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
570 it possible to download packages directly between two tor nodes,
571 making sure the network traffic always were encrypted.&lt;/p&gt;
572
573 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
574 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
575 urls with tor+http and tor+https, and using the hidden service instead
576 of the official Debian mirror site. I recommend installing
577 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
578 done in /etc/.&lt;/p&gt;
579
580 &lt;blockquote&gt;&lt;pre&gt;
581 apt install apt-transport-tor
582 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
583 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
584 &lt;/pre&gt;&lt;/blockquote&gt;
585
586 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
587 the sed commands for these too. The sed command is assuming your are
588 using the ftp.debian.org Debian mirror. Adjust the command (or just
589 edit the file manually) to match your mirror.&lt;/p&gt;
590
591 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
592 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
593 system, and do not work with these tor+http URLs. For
594 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
595 which need a recent apt version currently only in unstable. So if you
596 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
597
598 &lt;p&gt;Another advantage from this change is that your machine will start
599 using Tor regularly and at fairly random intervals (every time you
600 update the package lists or upgrade or install a new package), thus
601 masking other Tor traffic done from the same machine. Using Tor will
602 become normal for the machine in question.&lt;/p&gt;
603
604 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
605 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
606 enabled. It would be great if it was the default on any Debian
607 system.&lt;/p&gt;
608 </description>
609 </item>
610
611 <item>
612 <title>OpenALPR, find car license plates in video streams - nice free software</title>
613 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
614 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
615 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
616 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
617 call the car license plate numbers in those days. I would write the
618 numbers down in my little book and compare notes with the other kids
619 to see how many region codes we had seen and if we had seen some
620 exotic or special region codes and numbers. It was a fun game to pass
621 time, as we kids have plenty of it.&lt;/p&gt;
622
623 &lt;p&gt;A few days I came across
624 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
625 project&lt;/a&gt;, a free software project to automatically discover and
626 report license plates in images and video streams, and provide the
627 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
628 such system for a while now, because I believe it is a bad idea that the
629 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
630 number plate recognition&lt;/a&gt; tool only is available in the hands of
631 the powerful, and want it to be available also for the powerless to
632 even the score when it comes to surveillance and sousveillance. I
633 discovered the developer
634 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
635 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
636 help him get it into shape to get the package uploaded into the Debian
637 archive.&lt;/p&gt;
638
639 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
640 it into Debian, where it currently
641 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
642 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
643
644 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
645 for the common folks, ie those not running a large government
646 surveillance system? Well, I plan to put it in a computer on my bike
647 and in my car, tracking the cars nearby and allowing me to be notified
648 when number plates on my watch list are discovered. Another use case
649 was suggested by a friend of mine, who wanted to set it up at his home
650 to open the car port automatically when it discovered the plate on his
651 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
652 capable of placing his license plate number of a piece of cardboard to
653 open his car port, men replied that it was always unlocked anyway. I
654 guess for such use case it make sense. I am sure there are other use
655 cases too, for those with imagination and a vision.&lt;/p&gt;
656
657 &lt;p&gt;If you want to build your own version of the Debian package, check
658 out the upstream git source and symlink ./distros/debian to ./debian/
659 before running &quot;debuild&quot; to build the source. Or wait a bit until the
660 package show up in unstable.&lt;/p&gt;
661 </description>
662 </item>
663
664 <item>
665 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
666 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
667 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
668 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
669 <description>&lt;p&gt;Around three years ago, I created
670 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
671 system&lt;/a&gt; to get a more practical solution in Debian for handing
672 hardware related packages. A GUI system in the isenkram package will
673 present a pop-up dialog when some hardware dongle supported by
674 relevant packages in Debian is inserted into the machine. The same
675 lookup mechanism to detect packages is available as command line
676 tools in the isenkram-cli package. In addition to mapping hardware,
677 it will also map kernel firmware files to packages and make it easy to
678 install needed firmware packages automatically. The key for this
679 system to work is a good way to map hardware to packages, in other
680 words, allow packages to announce what hardware they will work
681 with.&lt;/p&gt;
682
683 &lt;p&gt;I started by providing data files in the isenkram source, and
684 adding code to download the latest version of these data files at run
685 time, to ensure every user had the most up to date mapping available.
686 I also added support for storing the mapping in the Packages file in
687 the apt repositories, but did not push this approach because while I
688 was trying to figure out how to best store hardware/package mappings,
689 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
690 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
691 add the hardware mapping into that data set to be able to use
692 appstream as a data source, and this was accepted at least for the
693 Debian version of appstream.&lt;/p&gt;
694
695 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
696 and today I uploaded a new version 0.20 of isenkram adding support for
697 appstream as a data source for mapping hardware to packages. The only
698 package so far using appstream to announce its hardware support is my
699 pymissile package. I got help from Matthias Klumpp with figuring out
700 how do add the required
701 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
702 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
703 this content:&lt;/p&gt;
704
705 &lt;blockquote&gt;&lt;pre&gt;
706 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
707 &amp;lt;component&amp;gt;
708 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
709 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
710 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
711 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
712 &amp;lt;description&amp;gt;
713 &amp;lt;p&amp;gt;
714 Pymissile provides a curses interface to control an original
715 Marks and Spencer / Striker USB Missile Launcher, as well as a
716 motion control script to allow a webcamera to control the
717 launcher.
718 &amp;lt;/p&amp;gt;
719 &amp;lt;/description&amp;gt;
720 &amp;lt;provides&amp;gt;
721 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
722 &amp;lt;/provides&amp;gt;
723 &amp;lt;/component&amp;gt;
724 &lt;/pre&gt;&lt;/blockquote&gt;
725
726 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
727 which is a glob style match rule for hardware specific strings
728 (modalias strings) provided by the Linux kernel. In this case, it
729 will map to all USB devices with vendor code 1130 and product code
730 0202.&lt;/p&gt;
731
732 &lt;p&gt;Note, it is important that the license of all the metadata files
733 are compatible to have permissions to aggregate them into archive wide
734 appstream files. Matthias suggested to use MIT or BSD licenses for
735 these files. A challenge is figuring out a good id for the data, as
736 it is supposed to be globally unique and shared across distributions
737 (in other words, best to coordinate with upstream what to use). But
738 it can be changed later or, so we went with the package name as
739 upstream for this project is dormant.&lt;/p&gt;
740
741 &lt;p&gt;To get the metadata file installed in the correct location for the
742 mirror update scripts to pick it up and include its content the
743 appstream data source, the file must be installed in the binary
744 package under /usr/share/appdata/. I did this by adding the following
745 line to debian/pymissile.install:&lt;/p&gt;
746
747 &lt;blockquote&gt;&lt;pre&gt;
748 debian/pymissile.metainfo.xml usr/share/appdata
749 &lt;/pre&gt;&lt;/blockquote&gt;
750
751 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
752 all packages useful on the current computer automatically, and the GUI
753 pop-up handler will propose to install the package not already
754 installed if a hardware dongle is inserted into the machine in
755 question.&lt;/p&gt;
756
757 &lt;p&gt;Details of the modalias field in appstream is available from the
758 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
759
760 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
761 try running this command on the command line:&lt;/p&gt;
762
763 &lt;blockquote&gt;&lt;pre&gt;
764 cat $(find /sys/devices/|grep modalias)
765 &lt;/pre&gt;&lt;/blockquote&gt;
766
767 &lt;p&gt;To learn more about the isenkram system, please check out
768 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
769 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
770 </description>
771 </item>
772
773 <item>
774 <title>The GNU General Public License is not magic pixie dust</title>
775 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
776 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
777 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
778 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
779 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
780 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
781 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
782 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
783
784 &lt;blockquote&gt;
785
786 &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;
787
788 &lt;blockquote&gt;
789 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
790
791 The first step is to choose a
792 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
793 code.&lt;br/&gt;
794
795 The next step is, when someone fails to follow that copyleft license,
796 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
797
798 and its a simple fact of our modern society that such type of
799 work&lt;br/&gt;
800
801 is incredibly expensive to do and incredibly difficult to do.
802 &lt;/blockquote&gt;
803
804 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
805 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
806 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
807 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
808
809 &lt;p&gt;As the Debian Website
810 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
811 &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;
812 imply, public domain and permissively licensed software can lead to
813 the production of more proprietary software as people discover useful
814 software, extend it and or incorporate it into their hardware or
815 software products. Copyleft licenses such as the GNU GPL were created
816 to close off this avenue to the production of proprietary software but
817 such licenses are not enough. With the ongoing adoption of Free
818 Software by individuals and groups, inevitably the community&#39;s
819 expectations of license compliance are violated, usually out of
820 ignorance of the way Free Software works, but not always. As Karen
821 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
822 Freedom&quot;&gt;FaiF&lt;/a&gt;
823 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
824 copyleft is nothing if no-one is willing and able to stand up in court
825 to protect it. The reality of today&#39;s world is that legal
826 representation is expensive, difficult and time consuming. With
827 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
828 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
829 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
830 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
831 of the Linux project, Debian and other groups against GPL violations.
832 In March the SFC supported a
833 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
834 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
835 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
836 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
837 kernel. Since then two of their sponsors pulled corporate funding and
838 conferences
839 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
840 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
841 less on corporate funding and more on the broad community of
842 individuals who support Free Software and copyleft. So the SFC has
843 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
844 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
845 a community of folks who stand up for copyleft and the GPL by
846 supporting their work on promoting and supporting copyleft and Free
847 Software.&lt;/p&gt;
848
849 &lt;p&gt;If you support Free Software,
850 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
851 what the SFC do, agree with their
852 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
853 principles&lt;/a&gt;, are happy about their
854 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
855 work on a project that is an SFC
856 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
857 just want to stand up for copyleft, please join
858 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
859 Allan Webber&lt;/a&gt;,
860 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
861 Smith&lt;/a&gt;,
862 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
863 Bacon&lt;/a&gt;, myself and
864 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
865 becoming a
866 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
867 next week your donation will be
868 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
869 by an anonymous donor. Please also consider asking your employer to
870 match your donation or become a sponsor of SFC. Don&#39;t forget to
871 spread the word about your support for SFC via email, your blog and or
872 social media accounts.&lt;/p&gt;
873
874 &lt;/blockquote&gt;
875
876 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
877 of Software Freedom Conservancy myself. Perhaps you should be a
878 supporter too?&lt;/p&gt;
879 </description>
880 </item>
881
882 <item>
883 <title>PGP key transition statement for key EE4E02F9</title>
884 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
885 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
886 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
887 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
888 set it up properly. I wanted to generate it offline and have it
889 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
890 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
891 time to sit down with an offline machine almost took forever. But
892 finally I&#39;ve been able to complete the process, and have now moved
893 from my old GPG key to a new GPG key. See
894 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
895 full transition statement, signed with both my old and new key&lt;/a&gt; for
896 the details. This is my new key:&lt;/p&gt;
897
898 &lt;pre&gt;
899 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]
900 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
901 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
902 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
903 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
904 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
905 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
906 &lt;/pre&gt;
907
908 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
909 my old key.&lt;/p&gt;
910
911 &lt;p&gt;If you signed my old key
912 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
913 I&#39;d very much appreciate a signature on my new key, details and
914 instructions in the transition statement. I m happy to reciprocate if
915 you have a similarly signed transition statement to present.&lt;/p&gt;
916 </description>
917 </item>
918
919 <item>
920 <title>The life and death of a laptop battery</title>
921 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
922 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
923 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
924 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
925 But this do not last. The last few laptops gave me a feeling that
926 within a year, the life time is just a fraction of what it used to be,
927 and it slowly become painful to use the laptop without power connected
928 all the time. Because of this, when I got a new Thinkpad X230 laptop
929 about two years ago, I decided to monitor its battery state to have
930 more hard facts when the battery started to fail.&lt;/p&gt;
931
932 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
933
934 &lt;p&gt;First I tried to find a sensible Debian package to record the
935 battery status, assuming that this must be a problem already handled
936 by someone else. I found
937 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
938 which collects statistics from the battery, but it was completely
939 broken. I sent a few suggestions to the maintainer, but decided to
940 write my own collector as a shell script while I waited for feedback
941 from him. Via
942 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
943 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
944 discovered
945 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
946 available in Debian.&lt;/p&gt;
947
948 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
949 battery stats ever since. Now my
950 /var/log/hjemmenett-battery-status.log file contain around 115,000
951 measurements, from the time the battery was working great until now,
952 when it is unable to charge above 7% of original capacity. My
953 collector shell script is quite simple and look like this:&lt;/p&gt;
954
955 &lt;pre&gt;
956 #!/bin/sh
957 # Inspired by
958 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
959 # See also
960 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
961 logfile=/var/log/hjemmenett-battery-status.log
962
963 files=&quot;manufacturer model_name technology serial_number \
964 energy_full energy_full_design energy_now cycle_count status&quot;
965
966 if [ ! -e &quot;$logfile&quot; ] ; then
967 (
968 printf &quot;timestamp,&quot;
969 for f in $files; do
970 printf &quot;%s,&quot; $f
971 done
972 echo
973 ) &gt; &quot;$logfile&quot;
974 fi
975
976 log_battery() {
977 # Print complete message in one echo call, to avoid race condition
978 # when several log processes run in parallel.
979 msg=$(printf &quot;%s,&quot; $(date +%s); \
980 for f in $files; do \
981 printf &quot;%s,&quot; $(cat $f); \
982 done)
983 echo &quot;$msg&quot;
984 }
985
986 cd /sys/class/power_supply
987
988 for bat in BAT*; do
989 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
990 done
991 &lt;/pre&gt;
992
993 &lt;p&gt;The script is called when the power management system detect a
994 change in the power status (power plug in or out), and when going into
995 and out of hibernation and suspend. In addition, it collect a value
996 every 10 minutes. This make it possible for me know when the battery
997 is discharging, charging and how the maximum charge change over time.
998 The code for the Debian package
999 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
1000 available on github&lt;/a&gt;.&lt;/p&gt;
1001
1002 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
1003
1004 &lt;pre&gt;
1005 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1006 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
1007 [...]
1008 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
1009 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
1010 &lt;/pre&gt;
1011
1012 &lt;p&gt;I wrote a small script to create a graph of the charge development
1013 over time. This graph depicted above show the slow death of my laptop
1014 battery.&lt;/p&gt;
1015
1016 &lt;p&gt;But why is this happening? Why are my laptop batteries always
1017 dying in a year or two, while the batteries of space probes and
1018 satellites keep working year after year. If we are to believe
1019 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
1020 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
1021 chance, and the fix is to not charge the Lithium-ion batteries to 100%
1022 all the time, but to stay below 90% of full charge most of the time.
1023 I&#39;ve been told that the Tesla electric cars
1024 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
1025 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
1026 100% when preparing for a longer trip (not that I would want a car
1027 like Tesla where rights to privacy is abandoned, but that is another
1028 story), which I guess is the option we should have for laptops on
1029 Linux too.&lt;/p&gt;
1030
1031 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
1032 stop charging at 80%, unless requested to charge to 100% once in
1033 preparation for a longer trip? I found
1034 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
1035 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1036 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
1037 load).&lt;/p&gt;
1038
1039 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
1040 at the start. I also wonder why the &quot;full capacity&quot; increases some
1041 times, and if it is possible to repeat the process to get the battery
1042 back to design capacity. And I wonder if the discharge and charge
1043 speed change over time, or if this stay the same. I did not yet try
1044 to write a tool to calculate the derivative values of the battery
1045 level, but suspect some interesting insights might be learned from
1046 those.&lt;/p&gt;
1047
1048 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
1049 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1050 packages instead of the tp-smapi-dkms package I had tried to use
1051 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
1052 and stop. I&#39;ve done so now, but expect my existing battery is toast
1053 and need to be replaced. The proposal is unfortunately Thinkpad
1054 specific.&lt;/p&gt;
1055 </description>
1056 </item>
1057
1058 <item>
1059 <title>New laptop - some more clues and ideas based on feedback</title>
1060 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
1061 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
1062 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
1063 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
1064 need for a new laptop, and provided very useful feedback. I wish to
1065 thank every one of these. Several pointed me to the possibility of
1066 fixing my X230, and I am already in the process of getting Lenovo to
1067 do so thanks to the on site, next day support contract covering the
1068 machine. But the battery is almost useless (I expect to replace it
1069 with a non-official battery) and I do not expect the machine to live
1070 for many more years, so it is time to plan its replacement. If I did
1071 not have a support contract, it was suggested to find replacement parts
1072 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
1073 might present a language barrier as I do not understand French.&lt;/p&gt;
1074
1075 &lt;p&gt;One tip I got was to use the
1076 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
1077 compare laptop models. It seem to have more models available than
1078 prisjakt.no. Another tip I got from someone I know have similar
1079 keyboard preferences was that the HP EliteBook 840 keyboard is not
1080 very good, and this matches my experience with earlier EliteBook
1081 keyboards I tested. Because of this, I will not consider it any further.
1082
1083 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
1084 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1085 (which is missing from the X240), and is working fairly well with
1086 Debian Sid/Unstable according to
1087 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
1088 got on the keyboard quality are not consistent. Some say the keyboard
1089 is good, others say it is ok, while others say it is not very good.
1090 Those with experience from X41 and and X60 agree that the X250
1091 keyboard is not as good as those trusty old laptops, and suggest I
1092 keep and fix my X230 instead of upgrading, or get a used X230 to
1093 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
1094 activity and battery status, which is very convenient on my X230. I&#39;m
1095 also told that the CPU fan is running very often, making it a bit
1096 noisy. In any case, the X250 do not work out of the box with Debian
1097 Stable/Jessie, one of my requirements.&lt;/p&gt;
1098
1099 &lt;p&gt;I have also gotten a few vendor proposals, one was
1100 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
1101 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
1102 The latter look very attractive to me.&lt;/p&gt;
1103
1104 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
1105 as I keep looking for a replacement.&lt;/p&gt;
1106
1107 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
1108 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
1109 different
1110 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
1111 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
1112 </description>
1113 </item>
1114
1115 <item>
1116 <title>Time to find a new laptop, as the old one is broken after only two years</title>
1117 <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>
1118 <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>
1119 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
1120 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
1121 replacement soon. The left 5 cm of the screen on my Thinkpad X230
1122 started flickering yesterday, and I suspect the cause is a broken
1123 cable, as changing the angle of the screen some times get rid of the
1124 flickering.&lt;/p&gt;
1125
1126 &lt;p&gt;My requirements have not really changed since I bought it, and is
1127 still as
1128 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
1129 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
1130 good help from
1131 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
1132 where I could select at least a few of the requirements (mouse pin,
1133 wifi, weight) and go through the rest manually. Three button mouse
1134 and a good keyboard is not available as an option, and all the three
1135 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
1136 G2) lack three mouse buttons). It is also unclear to me how good the
1137 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1138 the keyboard, even if the quality and robustness in the X series have
1139 deteriorated since X41.&lt;/p&gt;
1140
1141 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
1142 seem sensible to me? Are there better services around to search the
1143 set of available laptops for features? Please send me an email if you
1144 have suggestions.&lt;/p&gt;
1145
1146 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
1147 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
1148 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
1149 </description>
1150 </item>
1151
1152 <item>
1153 <title>How to stay with sysvinit in Debian Jessie</title>
1154 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
1155 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
1156 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
1157 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
1158 sysvinit as its boot system by default. But how can one keep using
1159 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1160 courtesy of
1161 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
1162 Schubert&lt;/a&gt; and
1163 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
1164 McVittie&lt;/a&gt;.
1165
1166 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
1167 keep sysvinit as your boot system, create a file
1168 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
1169 you upgrade:&lt;/p&gt;
1170
1171 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1172 Package: systemd-sysv
1173 Pin: release o=Debian
1174 Pin-Priority: -1
1175 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1176
1177 &lt;p&gt;This file content will tell apt and aptitude to not consider
1178 installing systemd-sysv as part of any installation and upgrade
1179 solution when resolving dependencies, and thus tell it to avoid
1180 systemd as a default boot system. The end result should be that the
1181 upgraded system keep using sysvinit.&lt;/p&gt;
1182
1183 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
1184 get sysvinit installed by default (debootstrap used by
1185 debian-installer have no option for this), but one can tell the
1186 installer to switch to sysvinit before the first boot. Either by
1187 using a kernel argument to the installer, or by adding a line to the
1188 preseed file used. First, the kernel command line argument:
1189
1190 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1191 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
1192 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1193
1194 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
1195
1196 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1197 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1198 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1199
1200 &lt;p&gt;One can of course also do this after the first boot by installing
1201 the sysvinit-core package.&lt;/p&gt;
1202
1203 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
1204 sysvinit boot sequence in Debian have several hardware specific bugs
1205 on Linux caused by the fact that it is unpredictable when hardware
1206 devices show up during boot. But on the other hand, the new default
1207 boot system still have a few rough edges I hope will be fixed before
1208 Jessie is released.&lt;/p&gt;
1209
1210 &lt;p&gt;Update 2014-11-26: Inspired by
1211 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
1212 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
1213 line.&lt;/p&gt;
1214 </description>
1215 </item>
1216
1217 <item>
1218 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
1219 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
1220 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
1221 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
1222 <description>&lt;p&gt;The right to communicate with your friends and family in private,
1223 without anyone snooping, is a right every citicen have in a liberal
1224 democracy. But this right is under serious attack these days.&lt;/p&gt;
1225
1226 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
1227 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1228 the whisleblower Snowden) more expensive for Internet email,
1229 is to deliver all email using SMTP via Tor. Such SMTP option would be
1230 a nice addition to the FreedomBox project if we could send email
1231 between FreedomBox machines without leaking metadata about the emails
1232 to the people peeking on the wire. I
1233 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
1234 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
1235 lot of useful feedback and suggestions. It also became obvious to me
1236 that this was not a novel idea, as the same idea was tested and
1237 documented by Johannes Berg as early as 2006, and both
1238 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
1239 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
1240 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
1241
1242 &lt;p&gt;To implement such system one need to set up a Tor hidden service
1243 providing the SMTP protocol on port 25, and use email addresses
1244 looking like username@hidden-service-name.onion. With such addresses
1245 the connections to port 25 on hidden-service-name.onion using Tor will
1246 go to the correct SMTP server. To do this, one need to configure the
1247 Tor daemon to provide the hidden service and the mail server to accept
1248 emails for this .onion domain. To learn more about Exim configuration
1249 in Debian and test the design provided by Johannes Berg in his FAQ, I
1250 set out yesterday to create a Debian package for making it trivial to
1251 set up such SMTP over Tor service based on Debian. Getting it to work
1252 were fairly easy, and
1253 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
1254 source code for the Debian package&lt;/a&gt; is available from github. I
1255 plan to move it into Debian if further testing prove this to be a
1256 useful approach.&lt;/p&gt;
1257
1258 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
1259 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
1260 get rid of exim4). Install tor, clone the git repository mentioned
1261 above, build the deb and install it on the machine. Next, run
1262 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
1263 the instructions to get the service up and running. Restart tor and
1264 exim when it is done, and test mail delivery using swaks like
1265 this:&lt;/p&gt;
1266
1267 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1268 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1269 --to fbx@dutlqrrmjhtfa3vp.onion
1270 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1271
1272 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
1273 address with your own address to test your server. :)&lt;/p&gt;
1274
1275 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
1276 easier and more automatic. Especially the tor setup need more work.
1277 Also, the package include a tor-smtp tool written in C, but its task
1278 should probably be rewritten in some script language to make the deb
1279 architecture independent. It would probably also make the code easier
1280 to review. The tor-smtp tool currently need to listen on a socket for
1281 exim to talk to it and is started using xinetd. It would be better if
1282 no daemon and no socket is needed. I suspect it is possible to get
1283 exim to run a command line tool for delivery instead of talking to a
1284 socket, and hope to figure out how in a future version of this
1285 system.&lt;/p&gt;
1286
1287 &lt;p&gt;Until I wipe my test machine, I can be reached using the
1288 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
1289 SMTorP. :)&lt;/p&gt;
1290 </description>
1291 </item>
1292
1293 <item>
1294 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
1295 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
1296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
1297 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
1298 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
1299 alioth.debian.org, you know the web interface is fairly slow to
1300 operate. First you visit one web page, enter the moderation password
1301 and get a new page shown with a list of all the messages to moderate
1302 and various options for each email address. This take a while for
1303 every list you moderate, and you need to do it regularly to do a good
1304 job as a list moderator. But there is a quick alternative,
1305 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
1306 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
1307 to moderate in a fraction of a second. Here is a test run on two
1308 lists I recently took over:&lt;/p&gt;
1309
1310 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1311 % time listadmin xiph
1312 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1313 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1314
1315 real 0m1.709s
1316 user 0m0.232s
1317 sys 0m0.012s
1318 %
1319 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1320
1321 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
1322 there are no message in the moderation queue. Every morning I
1323 currently moderate 68 mailman lists, and it normally take around two
1324 minutes. When I took over the two pkg-xiph lists above a few days
1325 ago, there were 400 emails waiting in the moderator queue. It took me
1326 less than 15 minutes to process them all using the listadmin
1327 program.&lt;/p&gt;
1328
1329 &lt;p&gt;If you install
1330 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
1331 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
1332 with content like this, the moderation task is a breeze:&lt;/p&gt;
1333
1334 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1335 username username@example.org
1336 spamlevel 23
1337 default discard
1338 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
1339
1340 password secret
1341 adminurl https://{domain}/mailman/admindb/{list}
1342 mailman-list@lists.example.com
1343
1344 password hidden
1345 other-list@otherserver.example.org
1346 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1347
1348 &lt;p&gt;There are other options to set as well. Check the manual page to
1349 learn the details.&lt;/p&gt;
1350
1351 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
1352 the SSL certificate is self signed or not properly signed by a
1353 generally accepted signing authority, you can set a environment
1354 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
1355
1356 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1357 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
1358 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1359
1360 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
1361 can provide an argument to the listadmin script like I do in the
1362 initial screen dump (the xiph argument). Using an argument, only
1363 lists matching the argument string will be processed. This make it
1364 quick to accept messages if you notice the moderation request in your
1365 email.&lt;/p&gt;
1366
1367 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
1368 mailing lists, as I simply do not have time to spend on that if the
1369 process was any slower. The listadmin program have saved me hours of
1370 time I could spend elsewhere over the years. It truly is nice free
1371 software.&lt;/p&gt;
1372
1373 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1374 activities, please send Bitcoin donations to my address
1375 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1376
1377 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1378 configuration example. Also, I&#39;ve been told that the
1379 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1380 sure why.&lt;/p&gt;
1381 </description>
1382 </item>
1383
1384 <item>
1385 <title>Debian Jessie, PXE and automatic firmware installation</title>
1386 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1387 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1388 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1389 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1390 problem that the WiFi card require some firmware to work properly.
1391 And it has been a pain to fix this using preseeding in Debian.
1392 Normally something more is needed. But thanks to
1393 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1394 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1395 to do this using simple preseeding.&lt;/p&gt;
1396
1397 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1398 firmware for the hardware found in the machine (actually, requested by
1399 the kernel modules for the hardware). (It can also install user space
1400 programs supporting the hardware detected, but that is not the focus
1401 of this story.)&lt;/p&gt;
1402
1403 &lt;p&gt;To get this working in the default installation, two preeseding
1404 values are needed. First, the isenkram-cli package must be installed
1405 into the target chroot (aka the hard drive) before tasksel is executed
1406 in the pkgsel step of the debian-installer system. This is done by
1407 preseeding the base-installer/includes debconf value to include the
1408 isenkram-cli package. The package name is next passed to debootstrap
1409 for installation. With the isenkram-cli package in place, tasksel
1410 will automatically use the isenkram tasks to detect hardware specific
1411 packages for the machine being installed and install them, because
1412 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1413
1414 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1415 most firmware unfortunately is non-free. This is done by preseeding
1416 the apt-mirror-setup step. This is unfortunate, but for a lot of
1417 hardware it is the only option in Debian.&lt;/p&gt;
1418
1419 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1420 firmware installed automatically by the installer:&lt;/p&gt;
1421
1422 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1423 base-installer base-installer/includes string isenkram-cli
1424 apt-mirror-setup apt-setup/non-free boolean true
1425 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1426
1427 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1428 both firmware and user space packages when using this method. It also
1429 do not work well, so use version 0.15 or later. Installing both
1430 firmware and user space packages might give you a bit more than you
1431 want, so I decided to split the tasksel task in two, one for firmware
1432 and one for user space programs. The firmware task is enabled by
1433 default, while the one for user space programs is not. This split is
1434 implemented in the package currently in unstable.&lt;/p&gt;
1435
1436 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1437 this recipe work for you. :)&lt;/p&gt;
1438
1439 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1440 foremost, it work because tasksel is modular, and driven by whatever
1441 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1442 isenkram-cli package place two files for tasksel to find. First there
1443 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1444
1445 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1446 Task: isenkram-packages
1447 Section: hardware
1448 Description: Hardware specific packages (autodetected by isenkram)
1449 Based on the detected hardware various hardware specific packages are
1450 proposed.
1451 Test-new-install: show show
1452 Relevance: 8
1453 Packages: for-current-hardware
1454
1455 Task: isenkram-firmware
1456 Section: hardware
1457 Description: Hardware specific firmware packages (autodetected by isenkram)
1458 Based on the detected hardware various hardware specific firmware
1459 packages are proposed.
1460 Test-new-install: mark show
1461 Relevance: 8
1462 Packages: for-current-hardware-firmware
1463 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1464
1465 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1466 should be handled and the Packages line referencing to a script in
1467 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1468 list of packages to install. The for-current-hardware-firmware script
1469 look like this to list relevant firmware for the machine:
1470
1471 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1472 #!/bin/sh
1473 #
1474 PATH=/usr/sbin:$PATH
1475 export PATH
1476 isenkram-autoinstall-firmware -l
1477 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1478
1479 &lt;p&gt;With those two pieces in place, the firmware is installed by
1480 tasksel during the normal d-i run. :)&lt;/p&gt;
1481
1482 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1483 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1484 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1485 install.&lt;/p&gt;
1486
1487 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1488 pilots in testing this feature, as isenkram is used there now to
1489 install firmware, replacing the earlier scripts.&lt;/p&gt;
1490 </description>
1491 </item>
1492
1493 <item>
1494 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1495 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1496 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1497 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1498 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1499 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1500 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1501 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1502
1503 &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;
1504
1505 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1506 about this hidden Linux installation. It is interesting what
1507 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1508 </description>
1509 </item>
1510
1511 <item>
1512 <title>New lsdvd release version 0.17 is ready</title>
1513 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1515 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1516 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1517 got a new set of developers a few weeks ago, after the original
1518 developer decided to step down and pass the project to fresh blood.
1519 This project is now maintained by Petter Reinholdtsen and Steve
1520 Dibb.&lt;/p&gt;
1521
1522 &lt;p&gt;I just wrapped up
1523 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1524 new lsdvd release&lt;/a&gt;, available in git or from
1525 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1526 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1527 0.17.&lt;/p&gt;
1528
1529 &lt;ul&gt;
1530
1531 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1532 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1533 non-existant, to work around additional copy protection&lt;/li&gt;
1534 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1535 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1536 &lt;li&gt;Fix include orders&lt;/li&gt;
1537 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1538 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1539 &lt;li&gt;Make sure the array size and the array limit used when initialising
1540 the palette size is the same.&lt;/li&gt;
1541 &lt;li&gt;Fix array printing.&lt;/li&gt;
1542 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1543 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1544 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1545 with more GCC compiler warnings.&lt;/li&gt;
1546
1547 &lt;/ul&gt;
1548
1549 &lt;p&gt;This change bring together patches for lsdvd in use in various
1550 Linux and Unix distributions, as well as patches submitted to the
1551 project the last nine years. Please check it out. :)&lt;/p&gt;
1552 </description>
1553 </item>
1554
1555 <item>
1556 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1557 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1558 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1559 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1560 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1561 project&lt;/a&gt; provide a Linux solution for schools, including a
1562 powerful desktop with education software, a central server providing
1563 web pages, user database, user home directories, central login and PXE
1564 boot of both clients without disk and the installation to install Debian
1565 Edu on machines with disk (and a few other services perhaps to small
1566 to mention here). We in the Debian Edu team are currently working on
1567 the Jessie based version, trying to get everything in shape before the
1568 freeze, to avoid having to maintain our own package repository in the
1569 future. The
1570 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1571 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1572 work left. Some fatal problems block testing, breaking the installer,
1573 but it is possible to work around these to get anyway. Here is a
1574 recipe on how to get the installation limping along.&lt;/p&gt;
1575
1576 &lt;p&gt;First, download the test ISO via
1577 &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;,
1578 &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;
1579 or rsync (use
1580 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1581 The ISO build was broken on Tuesday, so we do not get a new ISO every
1582 12 hours or so, but thankfully the ISO we already got we are able to
1583 install with some tweaking.&lt;/p&gt;
1584
1585 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1586 (use Alt-Ctrl-F2), run&lt;/p&gt;
1587
1588 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1589 nano /usr/bin/edu-eatmydata-install
1590 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1591
1592 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1593 optimization. Return to the installation, select the profile you want
1594 and continue. Without this change, exim4-config will fail to install
1595 due to a known bug in eatmydata.&lt;/p&gt;
1596
1597 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1598 this do not work, figure out what your correct value would be. All my
1599 test machines need /dev/sda, so I have no advice if it do not fit
1600 your need.&lt;/p&gt;
1601
1602 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1603 root after the initial boot from hard drive, and install the
1604 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1605 or mate. If you want several desktop options, install more than one
1606 metapackage. Once this is done, reboot and you should have a working
1607 graphical login screen. This workaround should no longer be needed
1608 once the education-tasks package version 1.801 enter testing in two
1609 days.&lt;/p&gt;
1610
1611 &lt;p&gt;I believe the ISO build will start working on two days when the new
1612 tasksel package enter testing and Steve McIntyre get a chance to
1613 update the debian-cd git repository. The eatmydata, grub and desktop
1614 issues are already fixed in unstable and testing, and should show up
1615 on the ISO as soon as the ISO build start working again. Well the
1616 eatmydata optimization is really just disabled. The proper fix
1617 require an upload by the eatmydata maintainer applying the patch
1618 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1619 The rest have proper fixes in unstable.&lt;/p&gt;
1620
1621 &lt;p&gt;I hope this get you going with the installation testing, as we are
1622 quickly running out of time trying to get our Jessie based
1623 installation ready before the distribution freeze in a month.&lt;/p&gt;
1624 </description>
1625 </item>
1626
1627 <item>
1628 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1629 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1631 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1632 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1633 to handle my fairly large DVD collection. It is a nice command line
1634 tool to get details about a DVD, like title, tracks, track length,
1635 etc, in XML, Perl or human readable format. But lsdvd have not seen
1636 any new development since 2006 and had a few irritating bugs affecting
1637 its use with some DVDs. Upstream seemed to be dead, and in January I
1638 sent a small probe asking for a version control repository for the
1639 project, without any reply. But I use it regularly and would like to
1640 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1641 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1642 the project admin, and after getting a reply from him explaining that
1643 he was no longer interested in the project, I asked if I could take
1644 over. And yesterday, I became project admin.&lt;/p&gt;
1645
1646 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1647 maintainer interested in joining forces to maintain the upstream
1648 project, and I hope we can get a new release out fairly quickly,
1649 collecting the patches spread around on the internet into on place.
1650 I&#39;ve added the relevant Debian patches to the freshly created git
1651 repository, and expect the Gentoo patches to make it too. If you got
1652 a DVD collection and care about command line tools, check out
1653 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1654 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1655 list&lt;/a&gt;. :)&lt;/p&gt;
1656 </description>
1657 </item>
1658
1659 <item>
1660 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1661 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1662 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1663 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1664 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1665 a lot quicker. When we install more than 2000 packages in
1666 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1667 tasksel in the installer, unpacking the binary packages take forever.
1668 A part of the slow I/O issue was discussed in
1669 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1670 much file system sync-ing done by dpkg, which is the package
1671 responsible for unpacking the binary packages. Other parts (like code
1672 executed by postinst scripts) might also sync to disk during
1673 installation. All this sync-ing to disk do not really make sense to
1674 me. If the machine crash half-way through, I start over, I do not try
1675 to salvage the half installed system. So the failure sync-ing is
1676 supposed to protect against, hardware or system crash, is not really
1677 relevant while the installer is running.&lt;/p&gt;
1678
1679 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1680 system sync()-ing in a fairly non-intrusive way, without the need to
1681 change the code in several packages. The idea is not new, but I have
1682 not heard anyone propose the approach using dpkg-divert before. It
1683 depend on the small and clever package
1684 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1685 uses LD_PRELOAD to replace the system functions for syncing data to
1686 disk with functions doing nothing, thus allowing programs to live
1687 dangerous while speeding up disk I/O significantly. Instead of
1688 modifying the implementation of dpkg, apt and tasksel (which are the
1689 packages responsible for selecting, fetching and installing packages),
1690 it occurred to me that we could just divert the programs away, replace
1691 them with a simple shell wrapper calling
1692 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1693 Two days ago I decided to test the idea, and wrapped up a simple
1694 implementation for the Debian Edu udeb.&lt;/p&gt;
1695
1696 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1697 time of the pkgsel step (installing tasks) from 64 to less than 44
1698 minutes (20 minutes shaved off the installation) on an old Dell
1699 Latitude D505 machine. I am not quite sure what the optimised time
1700 would have been, as I messed up the testing a bit, causing the debconf
1701 priority to get low enough for two questions to pop up during
1702 installation. As soon as I saw the questions I moved the installation
1703 along, but do not know how long the question were holding up the
1704 installation. I did some more measurements using Debian Edu Jessie,
1705 and got these results. The time measured is the time stamp in
1706 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1707 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1708 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1709 timing thus do not depend on how quickly the user handle the tasksel
1710 dialog.&lt;/p&gt;
1711
1712 &lt;p&gt;&lt;table&gt;
1713
1714 &lt;tr&gt;
1715 &lt;th&gt;Machine/setup&lt;/th&gt;
1716 &lt;th&gt;Original tasksel&lt;/th&gt;
1717 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1718 &lt;th&gt;Reduction&lt;/th&gt;
1719 &lt;/tr&gt;
1720
1721 &lt;tr&gt;
1722 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1723 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1724 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1725 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1726 &lt;/tr&gt;
1727
1728 &lt;tr&gt;
1729 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1730 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1731 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1732 &lt;td&gt;23 min 40%&lt;/td&gt;
1733 &lt;/tr&gt;
1734
1735 &lt;tr&gt;
1736 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1737 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1738 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1739 &lt;td&gt;11 min 50%&lt;/td&gt;
1740 &lt;/tr&gt;
1741
1742 &lt;tr&gt;
1743 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1744 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1745 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1746 &lt;td&gt;2 min 33%&lt;/td&gt;
1747 &lt;/tr&gt;
1748
1749 &lt;tr&gt;
1750 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1751 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1752 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1753 &lt;td&gt;4 min 21%&lt;/td&gt;
1754 &lt;/tr&gt;
1755
1756 &lt;/table&gt;&lt;/p&gt;
1757
1758 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1759 time is spent downloading packages. The connection to the Internet
1760 was 100Mbit/s during testing, so downloading should not be a
1761 significant factor in the measurement. Download typically took a few
1762 seconds to a few minutes, depending on the amount of packages being
1763 installed.&lt;/p&gt;
1764
1765 &lt;p&gt;The speedup is implemented by using two hooks in
1766 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1767 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1768 finish-install.d hook to remove the divert at the end of the
1769 installation. I picked the pre-pkgsel.d hook instead of the
1770 post-base-installer.d hook because I test using an ISO without the
1771 eatmydata package included, and the post-base-installer.d hook in
1772 Debian Edu can only operate on packages included in the ISO. The
1773 negative effect of this is that I am unable to activate this
1774 optimization for the kernel installation step in d-i. If the code is
1775 moved to the post-base-installer.d hook, the speedup would be larger
1776 for the entire installation.&lt;/p&gt;
1777
1778 &lt;p&gt;I&#39;ve implemented this in the
1779 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1780 git repository, and plan to provide the optimization as part of the
1781 Debian Edu installation. If you want to test this yourself, you can
1782 create two files in the installer (or in an udeb). One shell script
1783 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1784
1785 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1786 #!/bin/sh
1787 set -e
1788 . /usr/share/debconf/confmodule
1789 info() {
1790 logger -t my-pkgsel &quot;info: $*&quot;
1791 }
1792 error() {
1793 logger -t my-pkgsel &quot;error: $*&quot;
1794 }
1795 override_install() {
1796 apt-install eatmydata || true
1797 if [ -x /target/usr/bin/eatmydata ] ; then
1798 for bin in dpkg apt-get aptitude tasksel ; do
1799 file=/usr/bin/$bin
1800 # Test that the file exist and have not been diverted already.
1801 if [ -f /target$file ] ; then
1802 info &quot;diverting $file using eatmydata&quot;
1803 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1804 &gt; /target$file.edu
1805 chmod 755 /target$file.edu
1806 in-target dpkg-divert --package debian-edu-config \
1807 --rename --quiet --add $file
1808 ln -sf ./$bin.edu /target$file
1809 else
1810 error &quot;unable to divert $file, as it is missing.&quot;
1811 fi
1812 done
1813 else
1814 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1815 fi
1816 }
1817
1818 override_install
1819 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1820
1821 &lt;p&gt;To clean up, another shell script should go into
1822 /usr/lib/finish-install.d/ with code like this:
1823
1824 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1825 #! /bin/sh -e
1826 . /usr/share/debconf/confmodule
1827 error() {
1828 logger -t my-finish-install &quot;error: $@&quot;
1829 }
1830 remove_install_override() {
1831 for bin in dpkg apt-get aptitude tasksel ; do
1832 file=/usr/bin/$bin
1833 if [ -x /target$file.edu ] ; then
1834 rm /target$file
1835 in-target dpkg-divert --package debian-edu-config \
1836 --rename --quiet --remove $file
1837 rm /target$file.edu
1838 else
1839 error &quot;Missing divert for $file.&quot;
1840 fi
1841 done
1842 sync # Flush file buffers before continuing
1843 }
1844
1845 remove_install_override
1846 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1847
1848 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1849 edu-eatmydata-install and call it from the pre-pkgsel.d and
1850 finish-install.d scripts.&lt;/p&gt;
1851
1852 &lt;p&gt;By now you might ask if this change should get into the normal
1853 Debian installer too? I suspect it should, but am not sure the
1854 current debian-installer coordinators find it useful enough. It also
1855 depend on the side effects of the change. I&#39;m not aware of any, but I
1856 guess we will see if the change is safe after some more testing.
1857 Perhaps there is some package in Debian depending on sync() and
1858 fsync() having effect? Perhaps it should go into its own udeb, to
1859 allow those of us wanting to enable it to do so without affecting
1860 everyone.&lt;/p&gt;
1861
1862 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1863 will break installation of all programs using gnutls because of
1864 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1865 eatmydata package in Debian will solve it.&lt;/p&gt;
1866
1867 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1868 the optimization work again. And I have discovered that the
1869 dpkg-divert trick is not really needed and implemented a slightly
1870 simpler approach as part of the debian-edu-install package. See
1871 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1872
1873 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1874 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1875 triggering on i386 made it into testing, and broke this installation
1876 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1877 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1878 </description>
1879 </item>
1880
1881 <item>
1882 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1883 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1884 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1885 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1886 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1887 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1888 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1889 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1890 learn that there is a large set of publicly available key servers to
1891 use when looking for peoples public key. So far I have used
1892 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1893 were misbehaving, but those days are ended. The servers I have used
1894 up until yesterday have been slow and some times unavailable. I hope
1895 those problems are gone now.&lt;/p&gt;
1896
1897 &lt;p&gt;Behind the round robin DNS entry of the
1898 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1899 there is a pool of more than 100 keyservers which are checked every
1900 day to ensure they are well connected and up to date. It must be
1901 better than what I have used so far. :)&lt;/p&gt;
1902
1903 &lt;p&gt;Yesterdays speaker told me that the service is the default
1904 keyserver provided by the default configuration in GnuPG, but this do
1905 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1906
1907 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1908 line:&lt;/p&gt;
1909
1910 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1911 keyserver pool.sks-keyservers.net
1912 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1913
1914 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1915 entries in DNS. Just for fun, I did just that at work, so now every
1916 user of GnuPG at the University of Oslo should find a OpenGPG
1917 keyserver automatically should their need it:&lt;/p&gt;
1918
1919 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1920 % host -t srv _pgpkey-http._tcp.uio.no
1921 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1922 %
1923 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1924
1925 &lt;p&gt;Now if only
1926 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1927 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1928 very happy. It can look up a given key or search for a user ID, but I
1929 normally do not want that, but to find a trust path from my key to
1930 another key. Given a user ID or key ID, I would like to find (and
1931 download) the keys representing a signature path from my key to the
1932 key in question, to be able to get a trust path between the two keys.
1933 This is as far as I can tell not possible today. Perhaps something
1934 for a future version of the protocol?&lt;/p&gt;
1935 </description>
1936 </item>
1937
1938 <item>
1939 <title>From English wiki to translated PDF and epub via Docbook</title>
1940 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1941 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1942 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1943 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1944 project&lt;/a&gt; provide an instruction manual for teachers, system
1945 administrators and other users that contain useful tips for setting up
1946 and maintaining a Debian Edu installation. This text is about how the
1947 text processing of this manual is handled in the project.&lt;/p&gt;
1948
1949 &lt;p&gt;One goal of the project is to provide information in the native
1950 language of its users, and for this we need to handle translations.
1951 But we also want to make sure each language contain the same
1952 information, so for this we need a good way to keep the translations
1953 in sync. And we want it to be easy for our users to improve the
1954 documentation, avoiding the need to learn special formats or tools to
1955 contribute, and the obvious way to do this is to make it possible to
1956 edit the documentation using a web browser. We also want it to be
1957 easy for translators to keep the translation up to date, and give them
1958 help in figuring out what need to be translated. Here is the list of
1959 tools and the process we have found trying to reach all these
1960 goals.&lt;/p&gt;
1961
1962 &lt;p&gt;We maintain the authoritative source of our manual in the
1963 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1964 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1965 front page with references to the different chapters, several pages
1966 for each chapter, and finally one &quot;collection page&quot; gluing all the
1967 chapters together into one large web page (aka
1968 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1969 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1970 processing and translations. Thanks to the fact that the
1971 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1972 wiki.debian.org support exporting pages in
1973 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1974 the list of pages to export using the raw version of the AllInOne
1975 page, loop over each of them to generate a Docbook XML version of the
1976 manual. This process also download images and transform image
1977 references to use the locally downloaded images. The generated
1978 Docbook XML files are slightly broken, so some post-processing is done
1979 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1980 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1981 a handfull of images. The XML file can now be used to generate PDF, HTML
1982 and epub versions of the English manual. This is the basic step of
1983 our process, making PDF (using dblatex), HTML (using xsltproc) and
1984 epub (using dbtoepub) version from Docbook XML, and the resulting files
1985 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1986
1987 &lt;p&gt;But English documentation is not enough for us. We want translated
1988 documentation too, and we want to make it easy for translators to
1989 track the English original. For this we use the
1990 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1991 which allow us to transform the English Docbook XML file into a
1992 translation file (a .pot file), usable with the normal gettext based
1993 translation tools used by those translating free software. The pot
1994 file is used to create and maintain translation files (several .po
1995 files), which the translations update with the native language
1996 translations of all titles, paragraphs and blocks of text in the
1997 original. The next step is combining the original English Docbook XML
1998 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1999 create a translated Docbook XML file (in this case
2000 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2001 translated, if the translation is not complete) Docbook XML file can
2002 then be used like the original to create a PDF, HTML and epub version
2003 of the documentation.&lt;/p&gt;
2004
2005 &lt;p&gt;The translators use different tools to edit the .po files. We
2006 recommend using
2007 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
2008 while some use emacs and vi, others can use web based editors like
2009 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
2010 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
2011 is where the .po file end up, in our git repository. Updated
2012 translations can either be committed directly to git, or submitted as
2013 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
2014 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
2015
2016 &lt;p&gt;One challenge is images, which both might need to be translated (if
2017 they show translated user applications), and are needed in different
2018 formats when creating PDF and HTML versions (epub is a HTML version in
2019 this regard). For this we transform the original PNG images to the
2020 needed density and format during build, and have a way to provide
2021 translated images by storing translated versions in
2022 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2023 package maintainers know more.&lt;/p&gt;
2024
2025 &lt;p&gt;If you wonder what the result look like, we provide
2026 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
2027 of the documentation packages on the web&lt;/a&gt;. See for example the
2028 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
2029 PDF version&lt;/a&gt; or the
2030 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
2031 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
2032 but perhaps it will be done in the future.&lt;/p&gt;
2033
2034 &lt;p&gt;To learn more, check out
2035 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
2036 debian-edu-doc package&lt;/a&gt;,
2037 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
2038 manual on the wiki&lt;/a&gt; and
2039 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
2040 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
2041 </description>
2042 </item>
2043
2044 <item>
2045 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
2046 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
2047 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
2048 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
2049 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
2050 related packages relevant for the computer installed automatically.
2051 So I implemented one, using
2052 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
2053 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
2054 run tasksel as user root. You should be presented with a new option,
2055 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
2056 select it, tasksel will install the packages isenkram claim is fit for
2057 the current hardware, hot pluggable or not.&lt;p&gt;
2058
2059 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
2060 description, and the other is the script used to extract the list of
2061 packages to install. The first part is in
2062 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
2063 this:&lt;/p&gt;
2064
2065 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2066 Task: isenkram
2067 Section: hardware
2068 Description: Hardware specific packages (autodetected by isenkram)
2069 Based on the detected hardware various hardware specific packages are
2070 proposed.
2071 Test-new-install: mark show
2072 Relevance: 8
2073 Packages: for-current-hardware
2074 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2075
2076 &lt;p&gt;The second part is in
2077 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
2078 this:&lt;/p&gt;
2079
2080 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2081 #!/bin/sh
2082 #
2083 (
2084 isenkram-lookup
2085 isenkram-autoinstall-firmware -l
2086 ) | sort -u
2087 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2088
2089 &lt;p&gt;All in all, a very short and simple implementation making it
2090 trivial to install the hardware dependent package we all may want to
2091 have installed on our machines. I&#39;ve not been able to find a way to
2092 get tasksel to tell you exactly which packages it plan to install
2093 before doing the installation. So if you are curious or careful,
2094 check the output from the isenkram-* command line tools first.&lt;/p&gt;
2095
2096 &lt;p&gt;The information about which packages are handling which hardware is
2097 fetched either from the isenkram package itself in
2098 /usr/share/isenkram/, from git.debian.org or from the APT package
2099 database (using the Modaliases header). The APT package database
2100 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2101 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
2102 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
2103 the python-apt code (bug
2104 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
2105 workaround I was able to get rid of the file descriptor leak and
2106 reduce the memory leak from ~30 MiB per hardware detection down to
2107 around 2 MiB per hardware detection. It should make the desktop
2108 daemon a lot more useful. The fix is in version 0.7 uploaded to
2109 unstable today.&lt;/p&gt;
2110
2111 &lt;p&gt;I believe the current way of mapping hardware to packages in
2112 Isenkram is is a good draft, but in the future I expect isenkram to
2113 use the AppStream data source for this. A proposal for getting proper
2114 AppStream support into Debian is floating around as
2115 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
2116 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
2117 project&lt;/a&gt; will take place this summer to improve the situation. I
2118 look forward to seeing the result, and welcome patches for isenkram to
2119 start using the information when it is ready.&lt;/p&gt;
2120
2121 &lt;p&gt;If you want your package to map to some specific hardware, either
2122 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
2123 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
2124 package&lt;/a&gt; or submit a bug report with the details to the isenkram
2125 package. See also
2126 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
2127 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
2128 the information will be migrated to AppStream eventually, but for the
2129 moment I got no better place to store it.&lt;/p&gt;
2130 </description>
2131 </item>
2132
2133 <item>
2134 <title>FreedomBox milestone - all packages now in Debian Sid</title>
2135 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
2136 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
2137 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
2138 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2139 project&lt;/a&gt; is working on providing the software and hardware to make
2140 it easy for non-technical people to host their data and communication
2141 at home, and being able to communicate with their friends and family
2142 encrypted and away from prying eyes. It is still going strong, and
2143 today a major mile stone was reached.&lt;/p&gt;
2144
2145 &lt;p&gt;Today, the last of the packages currently used by the project to
2146 created the system images were accepted into Debian Unstable. It was
2147 the freedombox-setup package, which is used to configure the images
2148 during build and on the first boot. Now all one need to get going is
2149 the build code from the freedom-maker git repository and packages from
2150 Debian. And once the freedombox-setup package enter testing, we can
2151 build everything directly from Debian. :)&lt;/p&gt;
2152
2153 &lt;p&gt;Some key packages used by Freedombox are
2154 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
2155 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
2156 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
2157 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
2158 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
2159 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
2160 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
2161 are plans to integrate more packages into the setup. User
2162 documentation is maintained on the Debian wiki. Please
2163 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
2164 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
2165
2166 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
2167 setup, run this on a Debian machine using a user with sudo rights to
2168 become root:&lt;/p&gt;
2169
2170 &lt;p&gt;&lt;pre&gt;
2171 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2172 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2173 u-boot-tools
2174 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2175 freedom-maker
2176 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2177 &lt;/pre&gt;&lt;/p&gt;
2178
2179 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2180 devices. See the README in the freedom-maker git repo for more
2181 details on the build. If you do not want all three images, trim the
2182 make line. Note that the virtualbox-image target is not really
2183 virtualbox specific. It create a x86 image usable in kvm, qemu,
2184 vmware and any other x86 virtual machine environment. You might need
2185 the version of vmdebootstrap in Jessie to get the build working, as it
2186 include fixes for a race condition with kpartx.&lt;/p&gt;
2187
2188 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2189 method, boot a Debian Wheezy ISO and use this boot argument to load
2190 the preseed values:&lt;/p&gt;
2191
2192 &lt;p&gt;&lt;pre&gt;
2193 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;
2194 &lt;/pre&gt;&lt;/p&gt;
2195
2196 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
2197 it still work.&lt;/p&gt;
2198
2199 &lt;p&gt;If you wonder how to help, one task you could look at is using
2200 systemd as the boot system. It will become the default for Linux in
2201 Jessie, so we need to make sure it is usable on the Freedombox. I did
2202 a simple test a few weeks ago, and noticed dnsmasq failed to start
2203 during boot when using systemd. I suspect there are other problems
2204 too. :) To detect problems, there is a test suite included, which can
2205 be run from the plinth web interface.&lt;/p&gt;
2206
2207 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2208 us get the new release published. :) Please join us on
2209 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2210 irc.debian.org)&lt;/a&gt; and
2211 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2212 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2213 </description>
2214 </item>
2215
2216 <item>
2217 <title>S3QL, a locally mounted cloud file system - nice free software</title>
2218 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
2219 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
2220 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
2221 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
2222 solution for use at home. My requirements are simple, it must be
2223 cheap and locally encrypted (in other words, I keep the encryption
2224 keys, the storage provider do not have access to my private files).
2225 One idea me and my friends had many years ago, before the cloud
2226 storage providers showed up, was to use Google mail as storage,
2227 writing a Linux block device storing blocks as emails in the mail
2228 service provided by Google, and thus get heaps of free space. On top
2229 of this one can add encryption, RAID and volume management to have
2230 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2231 I never found time to implement such system. But the last few weeks I
2232 have looked at a system called
2233 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
2234 mounted network backed file system with the features I need.&lt;/p&gt;
2235
2236 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
2237 handling several different storage providers, any with Amazon S3,
2238 Google Drive or OpenStack API. There are heaps of such storage
2239 providers. S3QL can also use a local directory as storage, which
2240 combined with sshfs allow for file storage on any ssh server. S3QL
2241 include support for encryption, compression, de-duplication, snapshots
2242 and immutable file systems, allowing me to mount the remote storage as
2243 a local mount point, look at and use the files as if they were local,
2244 while the content is stored in the cloud as well. This allow me to
2245 have a backup that should survive fire. The file system can not be
2246 shared between several machines at the same time, as only one can
2247 mount it at the time, but any machine with the encryption key and
2248 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
2249
2250 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
2251 package is included already. So to get started, run &lt;tt&gt;apt-get
2252 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
2253 Greenqloud, after reading their nice recipe on
2254 &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
2255 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
2256 in Iceland more than those in USA when it come to keeping my personal
2257 data safe and private, and thus would rather spend money on a company
2258 in Iceland. Another nice recipe is available from the article
2259 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
2260 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
2261 Admin magazine. When the provider is picked, figure out how to get
2262 the API key needed to connect to the storage API. With Greencloud,
2263 the key did not show up until I had added payment details to my
2264 account.&lt;/p&gt;
2265
2266 &lt;p&gt;Armed with the API access details, it is time to create the file
2267 system. First, create a new bucket in the cloud. This bucket is the
2268 file system storage area. I picked a bucket name reflecting the
2269 machine that was going to store data there, but any name will do.
2270 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
2271 the API login and password, and a locally created password. Store it
2272 all in ~root/.s3ql/authinfo2 like this:
2273
2274 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2275 [s3c]
2276 storage-url: s3c://s.greenqloud.com:443/bucket-name
2277 backend-login: API-login
2278 backend-password: API-password
2279 fs-passphrase: local-password
2280 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2281
2282 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
2283 but any sensible way to create a fairly random password should do it.
2284 Armed with these details, it is now time to run mkfs, entering the API
2285 details and password to create it:&lt;/p&gt;
2286
2287 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2288 # mkdir -m 700 /var/lib/s3ql-cache
2289 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2290 --ssl s3c://s.greenqloud.com:443/bucket-name
2291 Enter backend login:
2292 Enter backend password:
2293 Before using S3QL, make sure to read the user&#39;s guide, especially
2294 the &#39;Important Rules to Avoid Loosing Data&#39; section.
2295 Enter encryption password:
2296 Confirm encryption password:
2297 Generating random encryption key...
2298 Creating metadata tables...
2299 Dumping metadata...
2300 ..objects..
2301 ..blocks..
2302 ..inodes..
2303 ..inode_blocks..
2304 ..symlink_targets..
2305 ..names..
2306 ..contents..
2307 ..ext_attributes..
2308 Compressing and uploading metadata...
2309 Wrote 0.00 MB of compressed metadata.
2310 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2311
2312 &lt;p&gt;The next step is mounting the file system to make the storage available.
2313
2314 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2315 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2316 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2317 Using 4 upload threads.
2318 Downloading and decompressing metadata...
2319 Reading metadata...
2320 ..objects..
2321 ..blocks..
2322 ..inodes..
2323 ..inode_blocks..
2324 ..symlink_targets..
2325 ..names..
2326 ..contents..
2327 ..ext_attributes..
2328 Mounting filesystem...
2329 # df -h /s3ql
2330 Filesystem Size Used Avail Use% Mounted on
2331 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
2332 #
2333 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2334
2335 &lt;p&gt;The file system is now ready for use. I use rsync to store my
2336 backups in it, and as the metadata used by rsync is downloaded at
2337 mount time, no network traffic (and storage cost) is triggered by
2338 running rsync. To unmount, one should not use the normal umount
2339 command, as this will not flush the cache to the cloud storage, but
2340 instead running the umount.s3ql command like this:
2341
2342 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2343 # umount.s3ql /s3ql
2344 #
2345 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2346
2347 &lt;p&gt;There is a fsck command available to check the file system and
2348 correct any problems detected. This can be used if the local server
2349 crashes while the file system is mounted, to reset the &quot;already
2350 mounted&quot; flag. This is what it look like when processing a working
2351 file system:&lt;/p&gt;
2352
2353 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2354 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
2355 Using cached metadata.
2356 File system seems clean, checking anyway.
2357 Checking DB integrity...
2358 Creating temporary extra indices...
2359 Checking lost+found...
2360 Checking cached objects...
2361 Checking names (refcounts)...
2362 Checking contents (names)...
2363 Checking contents (inodes)...
2364 Checking contents (parent inodes)...
2365 Checking objects (reference counts)...
2366 Checking objects (backend)...
2367 ..processed 5000 objects so far..
2368 ..processed 10000 objects so far..
2369 ..processed 15000 objects so far..
2370 Checking objects (sizes)...
2371 Checking blocks (referenced objects)...
2372 Checking blocks (refcounts)...
2373 Checking inode-block mapping (blocks)...
2374 Checking inode-block mapping (inodes)...
2375 Checking inodes (refcounts)...
2376 Checking inodes (sizes)...
2377 Checking extended attributes (names)...
2378 Checking extended attributes (inodes)...
2379 Checking symlinks (inodes)...
2380 Checking directory reachability...
2381 Checking unix conventions...
2382 Checking referential integrity...
2383 Dropping temporary indices...
2384 Backing up old metadata...
2385 Dumping metadata...
2386 ..objects..
2387 ..blocks..
2388 ..inodes..
2389 ..inode_blocks..
2390 ..symlink_targets..
2391 ..names..
2392 ..contents..
2393 ..ext_attributes..
2394 Compressing and uploading metadata...
2395 Wrote 0.89 MB of compressed metadata.
2396 #
2397 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2398
2399 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2400 quick, about the same speed as local file access. Uploading large
2401 amount of data is to me limited by the bandwidth out of and into my
2402 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2403 which is very close to my upload speed, and downloading the same
2404 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2405 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2406 network, not the file system code. I do not know what a good cache
2407 size would be, but suspect that the cache should e larger than your
2408 working set.&lt;/p&gt;
2409
2410 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2411 time. If another machine try, it is told that the file system is
2412 busy:&lt;/p&gt;
2413
2414 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2415 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2416 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2417 Using 8 upload threads.
2418 Backend reports that fs is still mounted elsewhere, aborting.
2419 #
2420 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2421
2422 &lt;p&gt;The file content is uploaded when the cache is full, while the
2423 metadata is uploaded once every 24 hour by default. To ensure the
2424 file system content is flushed to the cloud, one can either umount the
2425 file system, or ask S3QL to flush the cache and metadata using
2426 s3qlctrl:
2427
2428 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2429 # s3qlctrl upload-meta /s3ql
2430 # s3qlctrl flushcache /s3ql
2431 #
2432 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2433
2434 &lt;p&gt;If you are curious about how much space your data uses in the
2435 cloud, and how much compression and deduplication cut down on the
2436 storage usage, you can use s3qlstat on the mounted file system to get
2437 a report:&lt;/p&gt;
2438
2439 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2440 # s3qlstat /s3ql
2441 Directory entries: 9141
2442 Inodes: 9143
2443 Data blocks: 8851
2444 Total data size: 22049.38 MB
2445 After de-duplication: 21955.46 MB (99.57% of total)
2446 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2447 Database size: 2.39 MB (uncompressed)
2448 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2449 #
2450 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2451
2452 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2453 storage. I did not try to locate them all, but am aware of at least
2454 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2455 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2456 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2457 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2458 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2459 accept payment in Bitcoin. Pick one that suit your need. Some of
2460 them provide several GiB of free storage, but the prize models are
2461 quite different and you will have to figure out what suits you
2462 best.&lt;/p&gt;
2463
2464 &lt;p&gt;While researching this blog post, I had a look at research papers
2465 and posters discussing the S3QL file system. There are several, which
2466 told me that the file system is getting a critical check by the
2467 science community and increased my confidence in using it. One nice
2468 poster is titled
2469 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2470 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2471 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2472 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2473 and Pamela Smith. Please have a look.&lt;/p&gt;
2474
2475 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2476 check out the mounted S3QL file system to see if it would be usable as
2477 a home directory (in other word, that it provided POSIX semantics when
2478 it come to locking and umask handling etc). Running
2479 &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
2480 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2481 no error was found. So the file system can be used for home
2482 directories, if one chooses to do so.&lt;/p&gt;
2483
2484 &lt;p&gt;If you do not want a locally file system, and want something that
2485 work without the Linux fuse file system, I would like to mention the
2486 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2487 provide locally encrypted backup using a command line client. It have
2488 a nicer access control system, where one can split out read and write
2489 access, allowing some systems to write to the backup and others to
2490 only read from it.&lt;/p&gt;
2491
2492 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2493 activities, please send Bitcoin donations to my address
2494 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2495 </description>
2496 </item>
2497
2498 <item>
2499 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2500 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2501 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2502 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2503 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2504 project&lt;/a&gt; is working on providing the software and hardware for
2505 making it easy for non-technical people to host their data and
2506 communication at home, and being able to communicate with their
2507 friends and family encrypted and away from prying eyes. It has been
2508 going on for a while, and is slowly progressing towards a new test
2509 release (0.2).&lt;/p&gt;
2510
2511 &lt;p&gt;And what day could be better than the Pi day to announce that the
2512 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2513 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2514 system), and can also be installed using a Debian installer preseed
2515 file. The Debian based Freedombox is now based on Debian Jessie,
2516 where most of the needed packages used are already present. Only one,
2517 the freedombox-setup package, is missing. To try to build your own
2518 boot image to test the current status, fetch the freedom-maker scripts
2519 and build using
2520 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2521 with a user with sudo access to become root:
2522
2523 &lt;pre&gt;
2524 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2525 freedom-maker
2526 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2527 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2528 u-boot-tools
2529 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2530 &lt;/pre&gt;
2531
2532 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2533 devices. See the README for more details on the build. If you do not
2534 want all three images, trim the make line. But note that thanks to &lt;a
2535 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2536 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2537 kpartx call.&lt;/p&gt;
2538
2539 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2540 method, boot a Debian Wheezy ISO and use this boot argument to load
2541 the preseed values:&lt;/p&gt;
2542
2543 &lt;pre&gt;
2544 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;
2545 &lt;/pre&gt;
2546
2547 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2548 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2549 currently hang while setting up APT sources. Killing the
2550 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2551 installation will get the installation going. This affect all
2552 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2553
2554 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2555 us get the new release published. :) Please join us on
2556 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2557 irc.debian.org)&lt;/a&gt; and
2558 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2559 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2560 </description>
2561 </item>
2562
2563 <item>
2564 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2565 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2566 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2567 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2568 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2569 innetgr tools, because I needed them in
2570 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2571 ng-utils, and it has served me well. I placed the project under the
2572 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2573 repository. But many years ago, the CVS repository was dropped (lost,
2574 not migrated to new hardware, not sure), and the project have lacked a
2575 proper home since then.&lt;/p&gt;
2576
2577 &lt;p&gt;Last summer, I had a look at the package and made a new release
2578 fixing a irritating crash bug, but was unable to store the changes in
2579 a proper source control system. I applied for a project on
2580 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2581 to follow up on it. Until today. :)&lt;/p&gt;
2582
2583 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2584 now have a new home, and a git repository with the highlight of the
2585 history of the project. I published all release tarballs and imported
2586 them into the git repository. As the project is really stable and not
2587 expected to gain new features any time soon, I decided to make a new
2588 release and call it 1.0. Visit the new project home on
2589 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2590 if you want to check it out. The new version is also uploaded into
2591 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2592 </description>
2593 </item>
2594
2595 <item>
2596 <title>Testing sysvinit from experimental in Debian Hurd</title>
2597 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2598 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2599 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2600 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2601 their changes into sysvinit, to allow them to use the normal sysvinit
2602 boot system instead of their old one. This follow up on the
2603 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2604 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2605 get Debian on Hurd working more like Debian on Linux. To get started,
2606 I downloaded a prebuilt hard disk image from
2607 &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;,
2608 and started it using virt-manager.&lt;/p&gt;
2609
2610 &lt;p&gt;The first think I had to do after logging in (root without any
2611 password) was to get the network operational. I followed
2612 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2613 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2614 commands as root to get the machine to accept a IP address from the
2615 kvm internal DHCP server:&lt;/p&gt;
2616
2617 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2618 settrans -fgap /dev/netdde /hurd/netdde
2619 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2620 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2621 dhclient /dev/eth0
2622 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2623
2624 &lt;p&gt;After this, the machine had internet connectivity, and I could
2625 upgrade it and install the sysvinit packages from experimental and
2626 enable it as the default boot system in Hurd.&lt;/p&gt;
2627
2628 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2629 running on the machine it for ssh login to work a password need to be
2630 set. Also, note that a bug somewhere in openssh on Hurd block
2631 compression from working. Remember to turn that off on the client
2632 side.&lt;/p&gt;
2633
2634 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2635 stuff:&lt;/p&gt;
2636
2637 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2638 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2639 deb http://http.debian.net/debian/ experimental main
2640 EOF
2641 apt-get update
2642 apt-get dist-upgrade
2643 apt-get install -t experimental initscripts sysv-rc sysvinit \
2644 sysvinit-core sysvinit-utils
2645 update-alternatives --config runsystem
2646 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2647
2648 &lt;p&gt;To reboot after switching boot system, you have to use
2649 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2650 yet a sysvinit process able to receive the signals from the normal
2651 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2652 upgrading every package and rebooting, the network come up with DHCP
2653 after boot as it should, and the settrans/pkill hack mentioned at the
2654 start is no longer needed. But for some strange reason, there are no
2655 longer any login prompt in the virtual console, so I logged in using
2656 ssh instead.
2657
2658 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2659 fail some times. No idea what the cause is, but hope the Hurd porters
2660 figure it out. At least Justus said on IRC (#debian-hurd on
2661 irc.debian.org) that they are aware of the problem. A way to reduce
2662 the impact is to upgrade to the Hurd packages built by Justus by
2663 adding this repository to the machine:&lt;/p&gt;
2664
2665 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2666 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2667 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2668 EOF
2669 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2670
2671 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2672 http://ftp.debian-ports.org/debian, because some of the packages in
2673 unstable do not yet include the required patches that are lingering in
2674 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2675
2676 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2677 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2678 i emacs - GNU Emacs editor (metapackage)
2679 i gdb - GNU Debugger
2680 i hurd-recommended - Miscellaneous translators
2681 i isc-dhcp-client - ISC DHCP client
2682 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2683 i libc-bin - Embedded GNU C Library: Binaries
2684 i libc-dev-bin - Embedded GNU C Library: Development binaries
2685 i libc0.3 - Embedded GNU C Library: Shared libraries
2686 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2687 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2688 i multiarch-support - Transitional package to ensure multiarch compatibilit
2689 i A x11-common - X Window System (X.Org) infrastructure
2690 i xorg - X.Org X Window System
2691 i A xserver-xorg - X.Org X server
2692 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2693 #
2694 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2695
2696 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2697 X.org did not work out of the box and I never took the time to follow
2698 the porters instructions to fix it. This time I was interested in the
2699 command line stuff.&lt;p&gt;
2700 </description>
2701 </item>
2702
2703 <item>
2704 <title>New chrpath release 0.16</title>
2705 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2707 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2708 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2709 find problems in C, C++ and Java code using static source code
2710 analysis. It can detect a lot of different problems, and is very
2711 useful to find memory and locking bugs in the error handling part of
2712 the source. The company behind it provide
2713 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2714 a community service&lt;/a&gt;, and many hundred free software projects are
2715 already checked. A few days ago I decided to have a closer look at
2716 the Coverity system, and discovered that the
2717 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2718 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2719 projects I am involved with was already registered. But these are
2720 fairly big, and I would also like to have a small and easy project to
2721 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2722 checking of the chrpath project&lt;/a&gt;. It was
2723 added to the checker and discovered seven potential defects. Six of
2724 these were real, mostly resource &quot;leak&quot; when the program detected an
2725 error. Nothing serious, as the resources would be released a fraction
2726 of a second later when the program exited because of the error, but it
2727 is nice to do it right in case the source of the program some time in
2728 the future end up in a library. Having fixed all defects and added
2729 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2730 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2731 publish a new release. These are the release notes:&lt;/p&gt;
2732
2733 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2734
2735 &lt;ul&gt;
2736
2737 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2738 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2739 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2740
2741 &lt;/ul&gt;
2742
2743 &lt;p&gt;You can
2744 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2745 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2746 project if something is wrong with the new release. The test suite
2747 did not discover any old errors, so if you find a new one, please also
2748 include a test suite check.&lt;/p&gt;
2749 </description>
2750 </item>
2751
2752 <item>
2753 <title>New chrpath release 0.15</title>
2754 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2755 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2756 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2757 <description>&lt;p&gt;After many years break from the package and a vain hope that
2758 development would be continued by someone else, I finally pulled my
2759 acts together this morning and wrapped up a new release of chrpath,
2760 the command line tool to modify the rpath and runpath of already
2761 compiled ELF programs. The update was triggered by the persistence of
2762 Isha Vishnoi at IBM, which needed a new config.guess file to get
2763 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2764 is working on. I checked the
2765 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2766 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2767 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2768 packages for interesting patches (failed to find the source from
2769 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2770 These are the release notes:&lt;/p&gt;
2771
2772 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2773
2774 &lt;ul&gt;
2775
2776 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2777 with newer architectures. Thanks to isha vishnoi for the heads
2778 up.&lt;/li&gt;
2779
2780 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2781
2782 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2783 Matthias Klose.&lt;/li&gt;
2784
2785 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2786 Petr Machata found in Fedora.&lt;/li&gt;
2787
2788 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2789 .dynamic is a NULL terminated string. Based on patch found in
2790 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2791
2792 &lt;/ul&gt;
2793
2794 &lt;p&gt;You can
2795 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2796 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2797 project if something is wrong with the new release. The test suite
2798 did not discover any old errors, so if you find a new one, please also
2799 include a testsuite check.&lt;/p&gt;
2800 </description>
2801 </item>
2802
2803 <item>
2804 <title>Debian init.d boot script example for rsyslog</title>
2805 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2806 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2807 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2808 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2809 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2810 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2811 init.d scripts at all. Here is an example init.d script, ie a rewrite
2812 of /etc/init.d/rsyslog:&lt;/p&gt;
2813
2814 &lt;p&gt;&lt;pre&gt;
2815 #!/lib/init/init-d-script
2816 ### BEGIN INIT INFO
2817 # Provides: rsyslog
2818 # Required-Start: $remote_fs $time
2819 # Required-Stop: umountnfs $time
2820 # X-Stop-After: sendsigs
2821 # Default-Start: 2 3 4 5
2822 # Default-Stop: 0 1 6
2823 # Short-Description: enhanced syslogd
2824 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2825 # It is quite compatible to stock sysklogd and can be
2826 # used as a drop-in replacement.
2827 ### END INIT INFO
2828 DESC=&quot;enhanced syslogd&quot;
2829 DAEMON=/usr/sbin/rsyslogd
2830 &lt;/pre&gt;&lt;/p&gt;
2831
2832 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2833 script was 137 lines, and the above is just 15 lines, most of it meta
2834 info/comments.&lt;/p&gt;
2835
2836 &lt;p&gt;How to do this, you ask? Well, one create a new script
2837 /lib/init/init-d-script looking something like this:
2838
2839 &lt;p&gt;&lt;pre&gt;
2840 #!/bin/sh
2841
2842 # Define LSB log_* functions.
2843 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2844 # and status_of_proc is working.
2845 . /lib/lsb/init-functions
2846
2847 #
2848 # Function that starts the daemon/service
2849
2850 #
2851 do_start()
2852 {
2853 # Return
2854 # 0 if daemon has been started
2855 # 1 if daemon was already running
2856 # 2 if daemon could not be started
2857 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2858 || return 1
2859 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2860 $DAEMON_ARGS \
2861 || return 2
2862 # Add code here, if necessary, that waits for the process to be ready
2863 # to handle requests from services started subsequently which depend
2864 # on this one. As a last resort, sleep for some time.
2865 }
2866
2867 #
2868 # Function that stops the daemon/service
2869 #
2870 do_stop()
2871 {
2872 # Return
2873 # 0 if daemon has been stopped
2874 # 1 if daemon was already stopped
2875 # 2 if daemon could not be stopped
2876 # other if a failure occurred
2877 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2878 RETVAL=&quot;$?&quot;
2879 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2880 # Wait for children to finish too if this is a daemon that forks
2881 # and if the daemon is only ever run from this initscript.
2882 # If the above conditions are not satisfied then add some other code
2883 # that waits for the process to drop all resources that could be
2884 # needed by services started subsequently. A last resort is to
2885 # sleep for some time.
2886 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2887 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2888 # Many daemons don&#39;t delete their pidfiles when they exit.
2889 rm -f $PIDFILE
2890 return &quot;$RETVAL&quot;
2891 }
2892
2893 #
2894 # Function that sends a SIGHUP to the daemon/service
2895 #
2896 do_reload() {
2897 #
2898 # If the daemon can reload its configuration without
2899 # restarting (for example, when it is sent a SIGHUP),
2900 # then implement that here.
2901 #
2902 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2903 return 0
2904 }
2905
2906 SCRIPTNAME=$1
2907 scriptbasename=&quot;$(basename $1)&quot;
2908 echo &quot;SN: $scriptbasename&quot;
2909 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2910 script=&quot;$1&quot;
2911 shift
2912 . $script
2913 else
2914 exit 0
2915 fi
2916
2917 NAME=$(basename $DAEMON)
2918 PIDFILE=/var/run/$NAME.pid
2919
2920 # Exit if the package is not installed
2921 #[ -x &quot;$DAEMON&quot; ] || exit 0
2922
2923 # Read configuration variable file if it is present
2924 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2925
2926 # Load the VERBOSE setting and other rcS variables
2927 . /lib/init/vars.sh
2928
2929 case &quot;$1&quot; in
2930 start)
2931 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2932 do_start
2933 case &quot;$?&quot; in
2934 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2935 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2936 esac
2937 ;;
2938 stop)
2939 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2940 do_stop
2941 case &quot;$?&quot; in
2942 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2943 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2944 esac
2945 ;;
2946 status)
2947 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2948 ;;
2949 #reload|force-reload)
2950 #
2951 # If do_reload() is not implemented then leave this commented out
2952 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2953 #
2954 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2955 #do_reload
2956 #log_end_msg $?
2957 #;;
2958 restart|force-reload)
2959 #
2960 # If the &quot;reload&quot; option is implemented then remove the
2961 # &#39;force-reload&#39; alias
2962 #
2963 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2964 do_stop
2965 case &quot;$?&quot; in
2966 0|1)
2967 do_start
2968 case &quot;$?&quot; in
2969 0) log_end_msg 0 ;;
2970 1) log_end_msg 1 ;; # Old process is still running
2971 *) log_end_msg 1 ;; # Failed to start
2972 esac
2973 ;;
2974 *)
2975 # Failed to stop
2976 log_end_msg 1
2977 ;;
2978 esac
2979 ;;
2980 *)
2981 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2982 exit 3
2983 ;;
2984 esac
2985
2986 :
2987 &lt;/pre&gt;&lt;/p&gt;
2988
2989 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2990 lot. I did not really polish the approach, so it might not always
2991 work out of the box, but you get the idea. I did not try very hard to
2992 optimize it nor make it more robust either.&lt;/p&gt;
2993
2994 &lt;p&gt;A better argument for switching init system in Debian than reducing
2995 the size of init scripts (which is a good thing to do anyway), is to
2996 get boot system that is able to handle the kernel events sensibly and
2997 robustly, and do not depend on the boot to run sequentially. The boot
2998 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2999 </description>
3000 </item>
3001
3002 <item>
3003 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
3004 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
3005 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
3006 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
3007 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
3008 remote display access is the preferred solution with oVirt and RedHat
3009 Enterprise Virtualization, and I was sad to discover the other day
3010 that the browser plugin needed to use these systems seamlessly was
3011 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
3012 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
3013 2013-04-01, so I decided to wrap up a package based on the great work
3014 from Cajus Pollmeier and put it in a collab-maint maintained git
3015 repository to get a package I could use. I would very much like
3016 others to help me maintain the package (or just take over, I do not
3017 mind), but as no-one had volunteered so far, I just uploaded it to
3018 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
3019
3020 &lt;p&gt;The source is now available from
3021 &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;
3022 </description>
3023 </item>
3024
3025 <item>
3026 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
3027 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
3028 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
3029 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
3030 <description>&lt;p&gt;The
3031 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
3032 program is a a very nice system to create virtual machine images. It
3033 create a image file, add a partition table, mount it and run
3034 debootstrap in the mounted directory to create a Debian system on a
3035 stick. Yesterday, I decided to try to teach it how to make images for
3036 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
3037 of a plan to simplify the build system for
3038 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
3039 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
3040 the virtualbox images, but its current build system made multistrap
3041 based system for Dreamplug images, and it is lacking support for
3042 Raspberry Pi.&lt;/p&gt;
3043
3044 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
3045 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3046 code and adjusted it to be able to build armel images on my amd64
3047 Debian laptop. I ended up giving vmdebootstrap five new options,
3048 allowing me to replicate the image creation process I use to make
3049 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
3050 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
3051 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
3052 call debootstrap with --foreign and to copy the handler into the
3053 generated chroot before running the second stage. This allow
3054 vmdebootstrap to create armel images on an amd64 host. Next I added
3055 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
3056 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
3057 given file system type, allowing me to create an image with a vfat
3058 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
3059 variant&lt;/tt&gt; option to allow me to create smaller images without the
3060 Debian base system packages installed. Finally, I added an option
3061 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
3062 as a boot loader. It is not needed on the Raspberry Pi and probably
3063 most other non-x86 architectures. The changes were accepted by the
3064 upstream author of vmdebootstrap yesterday and today, and is now
3065 available from
3066 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
3067 upstream project page&lt;/a&gt;.&lt;/p&gt;
3068
3069 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
3070 create a small script (the customize script) to add the non-free
3071 binary blob needed to boot the Raspberry Pi and the APT source
3072 list:&lt;/p&gt;
3073
3074 &lt;p&gt;&lt;pre&gt;
3075 #!/bin/sh
3076 set -e # Exit on first error
3077 rootdir=&quot;$1&quot;
3078 cd &quot;$rootdir&quot;
3079 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
3080 deb http://http.debian.net/debian/ jessie main contrib non-free
3081 EOF
3082 # Install non-free binary blob needed to boot Raspberry Pi. This
3083 # install a kernel somewhere too.
3084 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3085 -O $rootdir/usr/bin/rpi-update
3086 chmod a+x $rootdir/usr/bin/rpi-update
3087 mkdir -p $rootdir/lib/modules
3088 touch $rootdir/boot/start.elf
3089 chroot $rootdir rpi-update
3090 &lt;/pre&gt;&lt;/p&gt;
3091
3092 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
3093 to build the image:&lt;/p&gt;
3094
3095 &lt;pre&gt;
3096 sudo ./vmdebootstrap \
3097 --variant minbase \
3098 --arch armel \
3099 --distribution jessie \
3100 --mirror http://http.debian.net/debian \
3101 --image test.img \
3102 --size 600M \
3103 --bootsize 64M \
3104 --boottype vfat \
3105 --log-level debug \
3106 --verbose \
3107 --no-kernel \
3108 --no-extlinux \
3109 --root-password raspberry \
3110 --hostname raspberrypi \
3111 --foreign /usr/bin/qemu-arm-static \
3112 --customize `pwd`/customize \
3113 --package netbase \
3114 --package git-core \
3115 --package binutils \
3116 --package ca-certificates \
3117 --package wget \
3118 --package kmod
3119 &lt;/pre&gt;&lt;/p&gt;
3120
3121 &lt;p&gt;The list of packages being installed are the ones needed by
3122 rpi-update to make the image bootable on the Raspberry Pi, with the
3123 exception of netbase, which is needed by debootstrap to find
3124 /etc/hosts with the minbase variant. I really wish there was a way to
3125 set up an Raspberry Pi using only packages in the Debian archive, but
3126 that is not possible as far as I know, because it boots from the GPU
3127 using a non-free binary blob.&lt;/p&gt;
3128
3129 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
3130 probably a few others installed. I have not checked the complete
3131 build dependency list.&lt;/p&gt;
3132
3133 &lt;p&gt;The resulting image will not use the hardware floating point unit
3134 on the Raspberry PI, because the armel architecture in Debian is not
3135 optimized for that use. So the images created will be a bit slower
3136 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
3137 </description>
3138 </item>
3139
3140 <item>
3141 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
3142 <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>
3143 <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>
3144 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
3145 <description>&lt;p&gt;The last few days I came across a few good causes that should get
3146 wider attention. I recommend signing and donating to each one of
3147 these. :)&lt;/p&gt;
3148
3149 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
3150 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
3151 Women program which is a Google Summer of Code like initiative to get
3152 more women involved in free software. One debian sponsor has offered
3153 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
3154 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
3155 hope you will to. :)&lt;/p&gt;
3156
3157 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
3158 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
3159 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
3160 take place these days, and their need to fund the work. I&#39;ve already
3161 donated. Are you next?&lt;/p&gt;
3162
3163 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
3164 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3165 statement under the heading
3166 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
3167 Access&lt;/a&gt; for those of us asking for more focus on open access in the
3168 Norwegian government. So far 499 signatures. I hope you will sign it
3169 too.&lt;/p&gt;
3170 </description>
3171 </item>
3172
3173 <item>
3174 <title>Videos about the Freedombox project - for inspiration and learning</title>
3175 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
3176 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
3177 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
3178 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
3179 project&lt;/a&gt; have been going on for a while, and have presented the
3180 vision, ideas and solution several places. Here is a little
3181 collection of videos of talks and presentation of the project.&lt;/p&gt;
3182
3183 &lt;ul&gt;
3184
3185 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
3186 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
3187
3188 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
3189 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3190
3191 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
3192 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3193 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
3194 (Youtube)&lt;/li&gt;
3195
3196 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
3197 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
3198
3199 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
3200 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3201
3202 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
3203 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3204 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
3205
3206 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
3207 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
3208 (Youtube)&lt;/li&gt;
3209
3210 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
3211 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
3212
3213 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
3214 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
3215
3216 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
3217 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3218 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
3219
3220 &lt;/ul&gt;
3221
3222 &lt;p&gt;A larger list is available from
3223 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
3224 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
3225
3226 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
3227 Jessie is coming along quite well, and soon both Owncloud and using
3228 Tor should be available for testers of the Freedombox solution. :) In
3229 a few weeks I hope everything needed to test it is included in Debian.
3230 The withsqlite package is already in Debian, and the plinth package is
3231 pending in NEW. The third and vital part of that puzzle is the
3232 metapackage/setup framework, which is still pending an upload. Join
3233 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
3234 (#freedombox on irc.debian.org)&lt;/a&gt; and
3235 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3236 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3237 </description>
3238 </item>
3239
3240 <item>
3241 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
3242 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
3243 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
3244 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
3245 <description>&lt;p&gt;I was introduced to the
3246 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
3247 in 2010, when Eben Moglen presented his vision about serving the need
3248 of non-technical people to keep their personal information private and
3249 within the legal protection of their own homes. The idea is to give
3250 people back the power over their network and machines, and return
3251 Internet back to its intended peer-to-peer architecture. Instead of
3252 depending on a central service, the Freedombox will give everyone
3253 control over their own basic infrastructure.&lt;/p&gt;
3254
3255 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
3256 taken priority. But this summers nasty news about the misuse of trust
3257 and privilege exercised by the &quot;western&quot; intelligence gathering
3258 communities increased my eagerness to contribute to a point where I
3259 actually started working on the project a while back.&lt;/p&gt;
3260
3261 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
3262 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
3263 create a simple and cheap Debian based appliance that anyone can hook
3264 up in their home and get access to secure and private services and
3265 communication. The initial deployment platform have been the
3266 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
3267 which is a piece of hardware I do not own. So to be able to test what
3268 the current Freedombox setup look like, I had to come up with a way to install
3269 it on some hardware I do have access to. I have rewritten the
3270 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
3271 image build framework to use .deb packages instead of only copying
3272 setup into the boot images, and thanks to this rewrite I am able to
3273 set up any machine supported by Debian Wheezy as a Freedombox, using
3274 the previously mentioned deb (and a few support debs for packages
3275 missing in Debian).&lt;/p&gt;
3276
3277 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
3278 scripts
3279 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
3280 and a administrative web interface
3281 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
3282 withsqlite), as well as a privacy enhancing proxy based on
3283 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
3284 (freedombox-privoxy). There is also a web/javascript based XMPP
3285 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
3286 trying (unsuccessfully so far) to talk to the XMPP server
3287 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
3288 web interface is pluggable, and the goal is to use it to enable OpenID
3289 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3290 this is really working yet, see
3291 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
3292 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
3293 on github at the moment. The HTTP proxy is operational out of the
3294 box, and the admin web interface can be used to add/remove plinth
3295 users. I&#39;ve not been able to do anything else with it so far, but
3296 know there are several branches spread around github and other places
3297 with lots of half baked features.&lt;/p&gt;
3298
3299 &lt;p&gt;Anyway, if you want to have a look at the current state, the
3300 following recipes should work to give you a test machine to poke
3301 at.&lt;/p&gt;
3302
3303 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
3304
3305 &lt;ol&gt;
3306
3307 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
3308 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
3309 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
3310 to the Debian installer:&lt;p&gt;
3311 &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;
3312
3313 &lt;li&gt;Answer the few language/region/password questions and pick disk to
3314 install on.&lt;/li&gt;
3315
3316 &lt;li&gt;When the installation is finished and the machine have rebooted a
3317 few times, your Freedombox is ready for testing.&lt;/li&gt;
3318
3319 &lt;/ol&gt;
3320
3321 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
3322
3323 &lt;ol&gt;
3324
3325 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
3326 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
3327 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
3328 &lt;pre&gt;
3329 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
3330 &lt;/pre&gt;&lt;/li&gt;
3331 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
3332 &lt;pre&gt;
3333 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3334 apt-key add -
3335 apt-get update
3336 apt-get install freedombox-setup
3337 /usr/lib/freedombox/setup
3338 &lt;/pre&gt;&lt;/li&gt;
3339 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
3340
3341 &lt;/ol&gt;
3342
3343 &lt;p&gt;You can test it on other architectures too, but because the
3344 freedombox-privoxy package is binary, it will only work as intended on
3345 the architectures where I have had time to build the binary and put it
3346 in my APT repository. But do not let this stop you. It is only a
3347 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
3348
3349 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
3350 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
3351 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
3352 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
3353
3354 &lt;p&gt;Please let me know if this works for you, or if you have any
3355 problems. We gather on the IRC channel
3356 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
3357 irc.debian.org and the
3358 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
3359 mailing list&lt;/a&gt;.&lt;/p&gt;
3360
3361 &lt;p&gt;Once you get your freedombox operational, you can visit
3362 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
3363 welcome screen (dead end - do not be surprised if you are unable to
3364 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
3365 to look at the rest of plinth. The default user is &#39;admin&#39; and the
3366 default password is &#39;secret&#39;.&lt;/p&gt;
3367 </description>
3368 </item>
3369
3370 <item>
3371 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
3372 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3373 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3374 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3375 <description>&lt;p&gt;Earlier, I reported about
3376 &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
3377 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3378 told by IBM that the original disk should be thrown away. And as
3379 there no longer was a problem if I bricked the firmware, I decided
3380 today to try to install Intel firmware to replace the Lenovo firmware
3381 currently on the disk.&lt;/p&gt;
3382
3383 &lt;p&gt;I searched the Intel site for firmware, and found
3384 &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;
3385 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3386 according to the site should contain the latest firmware for SSD
3387 disks. I inserted the broken disk in one of my spare laptops and
3388 booted the ISO from a USB stick. The disk was recognized, but the
3389 program claimed the newest firmware already were installed and refused
3390 to insert any Intel firmware. So no change, and the disk is still
3391 unable to handle write load. :( I guess the only way to get them
3392 working would be if Lenovo releases new firmware. No idea how likely
3393 that is. Anyway, just blogging about this test for completeness. I
3394 got a working Samsung disk, and see no point in spending more time on
3395 the broken disks.&lt;/p&gt;
3396 </description>
3397 </item>
3398
3399 <item>
3400 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3401 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3403 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3404 <description>&lt;p&gt;Today I switched to
3405 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3406 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3407 my new Thinkpad X230, which was delivered with an
3408 &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
3409 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3410 sustained writes. My hardware supplier have been very forthcoming in
3411 trying to find a solution, and after first trying with another
3412 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3413 disk instead to fix it once and for all. The Samsung disk survived
3414 the installation of Debian with encrypted disks (filling the disk with
3415 random data during installation killed the first two), and I thus
3416 decided to trust it with my data. I have installed it as a Debian Edu
3417 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3418 server at home using Kerberos and LDAP, and will use it as my work
3419 station from now on.&lt;/p&gt;
3420
3421 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3422 Debian Wheezy default installation need to be tuned a bit to increase
3423 performance and increase life time of the disk. The Linux kernel and
3424 user space applications do not yet adjust automatically to such
3425 environment. To make it easier for my self, I created a draft Debian
3426 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3427 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3428 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3429 is set up to adjust the setup of the machine by just installing the
3430 package. If there is any non-SSD disk in the machine, the package
3431 will refuse to install, as I did not try to write any logic to sort
3432 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3433
3434 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3435 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3436 where I set up the machine with one large encrypted partition (in
3437 addition to /boot), put LVM on top of this and set up partitions on
3438 top of this again. See the README file in the package source for the
3439 references I used to pick the settings. At the moment these
3440 parameters are tuned:&lt;/p&gt;
3441
3442 &lt;ul&gt;
3443
3444 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3445 (adding discard to /etc/crypttab)&lt;/li&gt;
3446
3447 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3448 this case a cryptsetup partition) by changing issue_discards from
3449 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3450
3451 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3452 systems.&lt;/li&gt;
3453
3454 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3455 /etc/fstab.&lt;/li&gt;
3456
3457 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3458
3459 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3460 cron.daily).&lt;/li&gt;
3461
3462 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3463 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3464
3465 &lt;/ul&gt;
3466
3467 &lt;p&gt;During installation, I cancelled the part where the installer fill
3468 the disk with random data, as this would kill the SSD performance for
3469 little gain. My goal with the encrypted file system is to ensure
3470 those stealing my laptop end up with a brick and not a working
3471 computer. I have no hope in keeping the really resourceful people
3472 from getting the data on the disk (see
3473 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3474 Thus I concluded that adding the discard option to crypttab is the
3475 right thing to do.&lt;/p&gt;
3476
3477 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3478 it for SSD, but others recommended deadline and a benchmark I found
3479 indicated that deadline might be better for interactive use.&lt;/p&gt;
3480
3481 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3482 and ext4, but read that it would give a performance hit ever time a
3483 file is removed, and thought it best to that that slowdown once a day
3484 instead of during my work.&lt;/p&gt;
3485
3486 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3487 this is already done by Debian Edu.&lt;/p&gt;
3488
3489 &lt;p&gt;I have not yet started on the user space tuning. I expect
3490 iceweasel need some tuning, and perhaps other applications too, but
3491 have not yet had time to investigate those parts.&lt;/p&gt;
3492
3493 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3494 there.&lt;/p&gt;
3495
3496 &lt;p&gt;As for the answer to the question in the title of this blog post,
3497 as far as I know, the only solution I know about is to replace the
3498 disk. It might be possible to flash it with Intel firmware instead of
3499 the Lenovo firmware. But I have not tried and did not want to do so
3500 without approval from Lenovo as I wanted to keep the warranty on the
3501 disk until a solution was found and they wanted the broken disks
3502 back.&lt;/p&gt;
3503 </description>
3504 </item>
3505
3506 <item>
3507 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3508 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3509 <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>
3510 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3511 <description>&lt;p&gt;A few days ago, I wrote about
3512 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3513 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3514 was dying during installation because it is unable to cope with
3515 sustained write. My supplier is in contact with
3516 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3517 replacement disk to try to fix the problem. They decided to send an
3518 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3519
3520 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3521 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3522 same firmware version as the original. This time my hope raised
3523 slightly as the installation progressed, as the original disk used to
3524 die after 4-7% of the disk was written to, while this time it kept
3525 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3526 died again and I was back on square one. I still do not have a new
3527 laptop with a disk I can trust. I can not live with a disk that might
3528 lock up when I download a new
3529 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3530 other large files. I look forward to hearing from my supplier with
3531 the next proposal from Lenovo.&lt;/p&gt;
3532
3533 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3534 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3535 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3536 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3537 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3538 P/N 45N8295, P0C38732.&lt;/p&gt;
3539
3540 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3541 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3542 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3543 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3544 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3545 P/N 45N8295, P0C38732.&lt;/p&gt;
3546
3547 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3548 SA, date and WNPP values. Mentioning all the details here in case
3549 someone is able to use the information to find a way to identify the
3550 failing disk among working ones (if any such working disk actually
3551 exist).&lt;/p&gt;
3552 </description>
3553 </item>
3554
3555 <item>
3556 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3557 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3558 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3559 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3560 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3561 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3562 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3563 member assosiation NUUG&lt;/a&gt; and
3564 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3565 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3566 Bitraf&lt;/a&gt;.&lt;/p&gt;
3567
3568 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3569 welcome, and there is no fee to participate. There is on the other
3570 hand limited space, and only room for 30 people. Please put your name
3571 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3572 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3573 </description>
3574 </item>
3575
3576 <item>
3577 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3578 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3579 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3580 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3581 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3582 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3583 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3584 time to spend on it, and it took a while to find a model I believe
3585 will do the job, but two days ago the replacement finally arrived. I
3586 ended up picking a
3587 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3588 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3589 a roaming workstation, and it seemed to work flawlessly. But my
3590 second installation with encrypted disk was not as successful. More
3591 on that below.&lt;/p&gt;
3592
3593 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3594 important requirements (robust and with a good keyboard) are never
3595 listed in the feature list. But I did get good help from the search
3596 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3597 allowed me to limit the list of interesting laptops based on my other
3598 requirements. A bit surprising that SSD disk are not disks according
3599 to that search interface, so I had to drop specifying the number of
3600 disks from my search parameters. I also asked around among friends to
3601 get their impression on keyboards and robustness.&lt;/p&gt;
3602
3603 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3604 X41. I am not quite convinced about the keyboard, as it is
3605 significantly wider than my old keyboard, and I have to stretch my
3606 hand a lot more to reach the edges. But the key response is fairly
3607 good and the individual key shape is fairly easy to handle, so I hope
3608 I will get used to it. My old X40 was starting to fail, and I really
3609 needed a new laptop now. :)&lt;/p&gt;
3610
3611 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3612 visit to the BIOS during boot it disable it.&lt;/p&gt;
3613
3614 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3615 lock up during load. And this happen when installing Debian Wheezy
3616 with encrypted disk, while the disk is being filled with random data.
3617 I also tested to install Ubuntu Raring, and it happen there too if I
3618 reenable the code to fill the disk with random data (it is disabled by
3619 default in Ubuntu). And the bug with is already known. It was
3620 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3621 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3622 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3623 kernel developers as
3624 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3625 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3626 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3627 Lenovo forums, both for
3628 &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
3629 2012-11-10&lt;/a&gt; and for
3630 &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
3631 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3632 reports state that the disk lock up during use if many writes are done
3633 on the disk, so it is much no use to work around the installation
3634 problem and end up with a computer that can lock up at any moment.
3635 There is even a
3636 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3637 available&lt;/a&gt; that will lock up the hard drive after running a few
3638 minutes by writing to a file.&lt;/p&gt;
3639
3640 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3641 contacting PCHELP Norway (request 01D1FDP) which handle support
3642 requests for Lenovo, his first suggestion was to upgrade the disk
3643 firmware. Unfortunately there is no newer firmware available from
3644 Lenovo, as my disk already have the most recent one (version LF1i). I
3645 hope to hear more from him today and hope the problem can be
3646 fixed. :)&lt;/p&gt;
3647 </description>
3648 </item>
3649
3650 <item>
3651 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3652 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3653 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3654 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3655 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3656 trusty old Thinkpad X41. Unfortunately I did not have much time to
3657 spend on it, but today the replacement finally arrived. I ended up
3658 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3659 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3660 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3661 this, it is installing what I hope will be a more final installation,
3662 with a encrypted hard drive to ensure any dope head stealing it end up
3663 with an expencive door stop.&lt;/p&gt;
3664
3665 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3666 important requirements (robust and with a good keyboard) are never
3667 listed in the feature list. But I did get good help from the search
3668 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3669 allowed me to limit the list of interesting laptops based on my other
3670 requirements. A bit surprising that SSD disk are not disks, so I had
3671 to drop number of disks from my search parameters.&lt;/p&gt;
3672
3673 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3674 wider than my old keyboard, and I have to stretch my hand a lot more
3675 to reach the edges. But the key response is fairly good and the
3676 individual key shape is fairly easy to handle, so I hope I will get
3677 used to it. My old X40 was starting to fail, and I really needed a
3678 new laptop now. :)&lt;/p&gt;
3679
3680 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3681 </description>
3682 </item>
3683
3684 <item>
3685 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3686 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3687 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3688 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3689 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3690 perfectly capable of, and I have to do it manually to get things
3691 working. One such task is to find out what firmware packages are
3692 needed to get the hardware on my computer working. Most often this
3693 affect the wifi card, but some times it even affect the RAID
3694 controller or the ethernet card. Today I pushed version 0.4 of the
3695 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3696 including a new script isenkram-autoinstall-firmware handling the
3697 process of asking all the loaded kernel modules what firmware files
3698 they want, find debian packages providing these files and install the
3699 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3700
3701 &lt;p&gt;&lt;pre&gt;
3702 # isenkram-autoinstall-firmware
3703 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3704 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3705 info: locating packages with the requested firmware files
3706 info: Updating APT sources after adding non-free APT source
3707 info: trying to install firmware-ipw2x00
3708 firmware-ipw2x00
3709 firmware-ipw2x00
3710 Preconfiguring packages ...
3711 Selecting previously deselected package firmware-ipw2x00.
3712 (Reading database ... 259727 files and directories currently installed.)
3713 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3714 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3715 #
3716 &lt;/pre&gt;&lt;/p&gt;
3717
3718 &lt;p&gt;When all the requested firmware is present, a simple message is
3719 printed instead:&lt;/p&gt;
3720
3721 &lt;p&gt;&lt;pre&gt;
3722 # isenkram-autoinstall-firmware
3723 info: did not find any firmware files requested by loaded kernel modules. exiting
3724 #
3725 &lt;/pre&gt;&lt;/p&gt;
3726
3727 &lt;p&gt;It could use some polish, but it is already working well and saving
3728 me some time when setting up new machines. :)&lt;/p&gt;
3729
3730 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3731 kernel modules, and look up each one of them using modinfo, to find
3732 the firmware files listed in the module meta-information. Next, it
3733 download the Contents file from a nearby APT mirror, and search for
3734 the firmware files in this file to locate the package with the
3735 requested firmware file. If the package is in the non-free section, a
3736 non-free APT source is added and the package is installed using
3737 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3738 machine.&lt;/p&gt;
3739
3740 &lt;p&gt;I hope someone find time to implement a more polished version of
3741 this script as part of the hw-detect debian-installer module, to
3742 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3743 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3744 firmware during a PXE install when the packages already are available
3745 from the nearby Debian mirror.&lt;/p&gt;
3746 </description>
3747 </item>
3748
3749 <item>
3750 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3751 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3752 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3753 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3754 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3755 the screen just turn black when Linux boot, either during installation
3756 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3757 last few years, but only recently understood the cause. I&#39;ve seen it
3758 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3759 The reason seem to be in the wiring of some laptops. The system to
3760 control the screen background light is inverted, so when Linux try to
3761 turn the brightness fully on, it end up turning it off instead. I do
3762 not know which Linux drivers are affected, but this post is about the
3763 i915 driver used by the
3764 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3765 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3766
3767 &lt;p&gt;The problem can be worked around two ways. Either by adding
3768 i915.invert_brightness=1 as a kernel option, or by adding a file in
3769 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3770 option when it load the i915 kernel module. On Debian and Ubuntu, it
3771 can be done by running these commands as root:&lt;/p&gt;
3772
3773 &lt;pre&gt;
3774 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3775 update-initramfs -u -k all
3776 &lt;/pre&gt;
3777
3778 &lt;p&gt;Since March 2012 there is
3779 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3780 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3781 hardware have this problem, and get the driver to invert the
3782 brightness setting automatically. To use it, one need to add a row in
3783 &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
3784 intel_quirks array&lt;/a&gt; in the driver source
3785 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3786 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3787 number (vendor number 8086 is assumed) and subdevice vendor and device
3788 number.&lt;/p&gt;
3789
3790 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3791 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3792
3793 &lt;p&gt;&lt;pre&gt;
3794 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3795 3rd Gen Core processor Graphics Controller [8086:0156] \
3796 (rev 09) (prog-if 00 [VGA controller])
3797 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3798 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3799 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3800 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3801 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3802 Latency: 0
3803 Interrupt: pin A routed to IRQ 42
3804 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3805 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3806 Region 4: I/O ports at 4000 [size=64]
3807 Expansion ROM at &lt;unassigned&gt; [disabled]
3808 Capabilities: &lt;access denied&gt;
3809 Kernel driver in use: i915
3810 &lt;/pre&gt;&lt;/p&gt;
3811
3812 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3813
3814 &lt;p&gt;&lt;pre&gt;
3815 struct intel_quirk intel_quirks[] = {
3816 ...
3817 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3818 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3819 ...
3820 }
3821 &lt;/pre&gt;&lt;/p&gt;
3822
3823 &lt;p&gt;According to the kernel module instructions (as seen using
3824 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3825 invert_brightness flag should be sent to the
3826 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3827 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3828 developers. But my email about the laptop sent 2013-06-03 have not
3829 yet shown up in
3830 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3831 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3832 emails from non-subscribers. Because of this, I sent my patch also to
3833 the Debian bug tracking system instead as
3834 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3835 sure the patch is not lost.&lt;/p&gt;
3836
3837 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3838 with this problem working properly with Linux. If you use Gnome, your
3839 worries should be over at this point. But if you use KDE, there is
3840 something in KDE ignoring the invert_brightness setting and turning on
3841 the screen during login. I&#39;ve reported it to Debian as
3842 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3843 have no idea yet how to figure out exactly what subsystem is doing
3844 this. Perhaps you can help? Perhaps you know what the Gnome
3845 developers did to handle this, and this can give a clue to the KDE
3846 developers? Or you know where in KDE the screen brightness is changed
3847 during login? If so, please update the BTS report (or get in touch if
3848 you do not know how to update BTS).&lt;/p&gt;
3849
3850 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3851 acpi_backlight=vendor, to disable ACPI backlight support completely,
3852 as the ACPI information on the machine is trash and it is better to
3853 leave it to the intel video driver to control the screen
3854 backlight.&lt;/p&gt;
3855 </description>
3856 </item>
3857
3858 <item>
3859 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3860 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3861 <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>
3862 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3863 <description>&lt;p&gt;Two days ago, I asked
3864 &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
3865 I could install Linux on a Packard Bell EasyNote LV computer
3866 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3867 with the obstacles put in the way of Linux users on a laptop with UEFI
3868 and Windows 8.&lt;/p&gt;
3869
3870 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3871 secure booting or fast boot. I suspect fast boot was the problem,
3872 causing the firmware to boot directly from HD without considering any
3873 key presses and alternative devices, but do not know UEFI settings
3874 enough to tell.&lt;/p&gt;
3875
3876 &lt;p&gt;There is no way to install Linux on the machine in question without
3877 opening the box and disconnecting the hard drive! This is as far as I
3878 can tell, the only way to get access to the firmware setup menu
3879 without accepting the Windows 8 license agreement. I am told (and
3880 found description on how to) that it is possible to configure the
3881 firmware setup once booted into Windows 8. But as I believe the terms
3882 of that agreement are completely unacceptable, accepting the license
3883 was never an alternative. I do not enter agreements I do not intend
3884 to follow.&lt;/p&gt;
3885
3886 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3887 waste many hours on this, but luckily there was a way to get it to
3888 work. But I would not recommend it to anyone planning to run Linux on
3889 it, and I have become sceptical to Windows 8 certified laptops. Is
3890 this the way Linux will be forced out of the market place, by making
3891 it close to impossible for &quot;normal&quot; users to install Linux without
3892 accepting the Microsoft Windows license terms? Or at least not
3893 without risking to loose the warranty?&lt;/p&gt;
3894
3895 &lt;p&gt;I&#39;ve updated the
3896 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3897 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3898 do not have to struggle as much as I did to get Linux into the
3899 machine.&lt;/p&gt;
3900
3901 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3902 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3903 </description>
3904 </item>
3905
3906 <item>
3907 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3908 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3909 <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>
3910 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3911 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3912 new laptops for my parents and a few others. I bought Packard Bell
3913 Easynote LV to run Kubuntu on and use as their home computer. But I
3914 am completely unable to figure out how to install Linux on it. The
3915 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3916 instead of a BIOS to boot.&lt;/p&gt;
3917
3918 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3919 to get it to boot the Linux installer from my USB stick. I have yet
3920 to try the DVD install, and still hope it will work. when I turn on
3921 the computer, there is no information on what buttons to press to get
3922 the normal boot menu. I expect to get some boot menu to select PXE or
3923 USB stick booting. When booting, it first ask for the language to
3924 use, then for some regional settings, and finally if I will accept the
3925 Windows 8 terms of use. As these terms are completely unacceptable to
3926 me, I have no other choice but to turn off the computer and try again
3927 to get it to boot the Linux installer.&lt;/p&gt;
3928
3929 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3930 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3931 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3932 installed on this machine, please get in touch or update that wiki
3933 page. If I can&#39;t find a way to install Linux, I will have to return
3934 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3935
3936 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3937 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3938 on new Laptops?&lt;/p&gt;
3939 </description>
3940 </item>
3941
3942 <item>
3943 <title>How to transform a Debian based system to a Debian Edu installation</title>
3944 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3945 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3946 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3947 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3948 an operating system based on Debian intended for use in schools. It
3949 contain a turn-key solution for the computer network provided to
3950 pupils in the primary schools. It provide both the central server,
3951 network boot servers and desktop environments with heaps of
3952 educational software. The project was founded almost 12 years ago,
3953 2001-07-02. If you want to support the project, which is in need for
3954 cash to fund developer gatherings and other project related activity,
3955 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3956 donate some money&lt;/a&gt;.
3957
3958 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3959 lists and elsewhere, is the question on how to transform a Debian or
3960 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3961 hard, and last week I wrote a script to replicate the steps done by
3962 the Debian Edu installer.&lt;/p&gt;
3963
3964 &lt;p&gt;The script,
3965 &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;
3966 in the debian-edu-config package, will go through these six steps and
3967 transform an existing Debian Wheezy or Ubuntu (untested) installation
3968 into a Debian Edu Workstation:&lt;/p&gt;
3969
3970 &lt;ol&gt;
3971
3972 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3973 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3974 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3975 our configuration.&lt;/li&gt;
3976 &lt;li&gt;Preseed debconf database with profile setup in
3977 /etc/debian-edu/config, and run tasksel to install packages
3978 according to the profile specified in the config above,
3979 overriding some of the Debian automation machinery.&lt;/li&gt;
3980 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3981 that could not be done using preseeding.&lt;/li&gt;
3982 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3983
3984 &lt;/ol&gt;
3985
3986 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3987 replicated like this. Disk partitioning and LVM setup, for example.
3988 So this script just assume there is enough disk space to install all
3989 the needed packages.&lt;/p&gt;
3990
3991 &lt;p&gt;The script was created to help a Debian Edu student working on
3992 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3993 Debian Edu client, and using it he can take the existing
3994 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3995 transform it into a fully functioning Debian Edu Workstation (or
3996 Roaming Workstation, or whatever :).&lt;/p&gt;
3997
3998 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3999 If a LXDE based Roaming workstation is wanted instead, modify the
4000 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
4001
4002 &lt;p&gt;&lt;pre&gt;
4003 PROFILE=&quot;Roaming-Workstation&quot;
4004 DESKTOP=&quot;lxde&quot;
4005 &lt;/pre&gt;&lt;/p&gt;
4006
4007 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
4008 the cloud, by starting with a virtual Debian installation at some
4009 virtual hosting service and setting up all the services on first
4010 boot.&lt;/p&gt;
4011 </description>
4012 </item>
4013
4014 <item>
4015 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
4016 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
4017 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
4018 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
4019 <description>&lt;P&gt;In January,
4020 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
4021 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
4022 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
4023 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
4024 marvellous construction system from Denmark. We also created
4025 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
4026 a place to take notes and write down our plans and hopes. And several
4027 people showed up to help. I was very happy to see the effect of my
4028 call. Since the small start, we have a debtags tag
4029 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
4030 tag for LEGO related packages, and now count 10 packages related to
4031 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
4032
4033 &lt;p&gt;&lt;table&gt;
4034 &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;
4035 &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;
4036 &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;
4037 &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;
4038 &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;
4039 &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;
4040 &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;
4041 &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;
4042 &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;
4043 &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;
4044 &lt;/table&gt;&lt;/p&gt;
4045
4046 &lt;p&gt;Some of these are available in Wheezy, and all but one are
4047 currently available in Jessie/testing. leocad is so far only
4048 available in experimental.&lt;/p&gt;
4049
4050 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
4051 adding the rest of the great free software tools available on Linux
4052 for LEGO designers.&lt;/p&gt;
4053 </description>
4054 </item>
4055
4056 <item>
4057 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
4058 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
4059 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
4060 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
4061 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
4062 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
4063 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
4064 Debian release, and I expect to move my machines at home over to it fairly
4065 soon.&lt;/p&gt;
4066
4067 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
4068 in particular make me very happy to see included. The
4069 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
4070 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
4071 included for the first time. Alongside similar programs like
4072 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
4073 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
4074 it allow for visual programming where syntax errors can not happen,
4075 and a friendly programming environment for learning to control the
4076 computer. Scratch will also be included in the next release of Debian
4077 Edu.&lt;/a&gt;
4078
4079 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
4080 Edu/Skolelinux release too. The
4081 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
4082 alpha release&lt;/a&gt; went out last week, and the next should soon
4083 follow.&lt;p&gt;
4084 </description>
4085 </item>
4086
4087 <item>
4088 <title>Isenkram 0.2 finally in the Debian archive</title>
4089 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
4090 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
4091 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
4092 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
4093 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
4094 for many months. I uploaded it to the Debian experimental suite
4095 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
4096
4097 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
4098 install to work with a pluggable hardware device. The suggestion pop
4099 up when the device is plugged in. For example if a Lego Mindstorm NXT
4100 is inserted, it will suggest to install the program needed to program
4101 the NXT controller. Give it a go, and report bugs and suggestions to
4102 BTS. :)&lt;/p&gt;
4103 </description>
4104 </item>
4105
4106 <item>
4107 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
4108 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
4109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
4110 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
4111 <description>&lt;p&gt;My
4112 &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
4113 bitcoin related blog post&lt;/a&gt; mentioned that the new
4114 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
4115 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4116 2013-01-19, and have been available in unstable since then. It was
4117 automatically copied to Ubuntu, and is available in their Raring
4118 version too.&lt;/p&gt;
4119
4120 &lt;p&gt;But there is a strange problem with the build that block this new
4121 version from being available on the i386 and kfreebsd-i386
4122 architectures. For some strange reason, the autobuilders in Debian
4123 for these architectures fail to run the test suite on these
4124 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
4125 We are so far unable to reproduce it when building it manually, and
4126 no-one have been able to propose a fix. If you got an idea what is
4127 failing, please let us know via the BTS.&lt;/p&gt;
4128
4129 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
4130 I often run low on disk space, is the fact that the client will exit
4131 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
4132 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
4133 it. :)&lt;/p&gt;
4134
4135 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4136 activities, please send Bitcoin donations to my address
4137 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4138 </description>
4139 </item>
4140
4141 <item>
4142 <title>Welcome to the world, Isenkram!</title>
4143 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
4144 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
4145 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
4146 <description>&lt;p&gt;Yesterday, I
4147 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
4148 for testers&lt;/a&gt; for my prototype for making Debian better at handling
4149 pluggable hardware devices, which I
4150 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
4151 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
4152 up, and caused me to really want to to open up the development to more
4153 people. But before I did this, I want to come up with a sensible name
4154 for this project. Today I finally decided on a new name, and I have
4155 renamed the project from hw-support-handler to this new name. In the
4156 process, I moved the source to git and made it available as a
4157 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
4158 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
4159 To fetch and build the latest version of the source, use&lt;/p&gt;
4160
4161 &lt;pre&gt;
4162 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4163 cd isenkram &amp;&amp; git-buildpackage -us -uc
4164 &lt;/pre&gt;
4165
4166 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
4167 want to hack on the source or improve the package, please go ahead.
4168 But please talk to me first on IRC or via email before you do major
4169 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
4170
4171 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
4172 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4173 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
4174 the German word eisenkram, for those that are familiar with that
4175 word.&lt;/p&gt;
4176
4177 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
4178 instructions, to avoid confusing people with an error from the signing
4179 process.&lt;/p&gt;
4180
4181 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
4182 clone argument to avoid the need for authentication.&lt;/p&gt;
4183 </description>
4184 </item>
4185
4186 <item>
4187 <title>First prototype ready making hardware easier to use in Debian</title>
4188 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
4189 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
4190 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
4191 <description>&lt;p&gt;Early this month I set out to try to
4192 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
4193 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
4194 prototype is working, and it is ready for a larger audience. To test
4195 it, fetch the
4196 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
4197 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
4198 package. You might have to log out and in again activate the
4199 autostart script.&lt;/p&gt;
4200
4201 &lt;p&gt;The design is simple:&lt;/p&gt;
4202
4203 &lt;ul&gt;
4204
4205 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
4206 hw-support-handlerd to start when the user log in.&lt;/li&gt;
4207
4208 &lt;li&gt;This program listen for kernel events about new hardware (directly
4209 from the kernel like udev does), not using HAL dbus events as I
4210 initially did.&lt;/li&gt;
4211
4212 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
4213 the APT database, a database
4214 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
4215 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
4216
4217 &lt;li&gt;If a package is mapped to the hardware in question, the package
4218 isn&#39;t installed yet and this is the first time the hardware was
4219 plugged in, show a desktop notification suggesting to install the
4220 package or packages.&lt;/li&gt;
4221
4222 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
4223 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
4224
4225 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
4226 package while showing progress information in a window.&lt;/li&gt;
4227
4228 &lt;/ul&gt;
4229
4230 &lt;p&gt;I still need to come up with a better name for the system. Here
4231 are some screen shots showing the prototype in action. First the
4232 notification, then the password request, and finally the request to
4233 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
4234
4235 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
4236 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
4237 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
4238 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
4239 &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;
4240
4241 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
4242 is already useful. The database of hardware to package mappings also
4243 need more work. It is currently compatible with the Ubuntu way of
4244 storing such information in the package control file, but could be
4245 changed to use other formats instead or in addition to the current
4246 method. I&#39;ve dropped the use of discover for this mapping, as the
4247 modalias approach is more flexible and easier to use on Linux as long
4248 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
4249
4250 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
4251 here is the command required to check out and build the source: Use
4252 &#39;&lt;tt&gt;svn checkout
4253 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4254 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
4255 devscripts package.&lt;/p&gt;
4256
4257 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
4258 renamed to Isenkram and the source moved from the Debian Edu
4259 subversion repository to a Debian collab-maint git repository. See
4260 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
4261 instructions&lt;/a&gt; for details.&lt;/p&gt;
4262 </description>
4263 </item>
4264
4265 <item>
4266 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
4267 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
4268 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
4269 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
4270 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
4271 suddenly in bed. With a quiet whimper, it went completely quiet and
4272 black. The power button was no longer able to turn it on. It was a
4273 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4274 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4275 Compaq I had before that. Now I need to find a replacement. To keep
4276 going during Christmas, I moved the one year old SSD disk to my old
4277 X40 where it fitted (only one I had left that could use it), but it is
4278 not a durable solution.
4279
4280 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
4281 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
4282
4283 &lt;ul&gt;
4284
4285 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
4286 than A4).&lt;/li&gt;
4287 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
4288 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
4289 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
4290 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
4291 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
4292 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
4293 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
4294 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
4295 size).&lt;/li&gt;
4296 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
4297 X.org packages.&lt;/li&gt;
4298 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
4299 the time).
4300
4301 &lt;/ul&gt;
4302
4303 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
4304 list. The reason is simply that the specifications on laptops the
4305 last 10-15 years have been sufficient for my needs, and I have to look
4306 at other features to choose my laptop. But are there still made as
4307 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4308 robust, and Thinkpads seem to be heading in the wrong direction since
4309 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
4310 still be useful.&lt;/p&gt;
4311
4312 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
4313 external keyboard? I&#39;ll have to check the
4314 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
4315 well-supported laptops, or perhaps just buy one preinstalled from one
4316 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
4317 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
4318 </description>
4319 </item>
4320
4321 <item>
4322 <title>How to find a browser plugin supporting a given MIME type</title>
4323 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
4324 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
4325 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
4326 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
4327 install to get support for a given MIME type. Thanks to
4328 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
4329 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
4330 Unfortunately, not very many packages provide the needed meta
4331 information, Anyway, here is a small script to look up all browser
4332 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
4333
4334 &lt;pre&gt;
4335 #!/usr/bin/python
4336 import sys
4337 import apt
4338 def pkgs_handling_mimetype(mimetype):
4339 cache = apt.Cache()
4340 cache.open(None)
4341 thepkgs = []
4342 for pkg in cache:
4343 version = pkg.candidate
4344 if version is None:
4345 version = pkg.installed
4346 if version is None:
4347 continue
4348 record = version.record
4349 if not record.has_key(&#39;Npp-MimeType&#39;):
4350 continue
4351 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
4352 for t in mime_types:
4353 t = t.rstrip().strip()
4354 if t == mimetype:
4355 thepkgs.append(pkg.name)
4356 return thepkgs
4357 mimetype = &quot;audio/ogg&quot;
4358 if 1 &lt; len(sys.argv):
4359 mimetype = sys.argv[1]
4360 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
4361 for pkg in pkgs_handling_mimetype(mimetype):
4362 print &quot; %s&quot; %pkg
4363 &lt;/pre&gt;
4364
4365 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
4366
4367 &lt;pre&gt;
4368 % ./apt-find-browserplug-for-mimetype
4369 Browser plugin packages supporting audio/ogg:
4370 gecko-mediaplayer
4371 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4372 Browser plugin packages supporting application/x-shockwave-flash:
4373 browser-plugin-gnash
4374 %
4375 &lt;/pre&gt;
4376
4377 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4378 itself to query for plugins and propose to install the needed
4379 packages. It would be great if Debian supported such feature too. Is
4380 anyone working on adding it?&lt;/p&gt;
4381
4382 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4383 request for icweasel support for this feature is
4384 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4385 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4386 of manpower and wish for a different design is the reason thus feature
4387 is not yet in iceweasel from Debian.&lt;/p&gt;
4388 </description>
4389 </item>
4390
4391 <item>
4392 <title>What is the most supported MIME type in Debian?</title>
4393 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4394 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4395 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4396 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4397 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4398 proposal to make it possible for a Desktop application to propose to
4399 the user some package to install to gain support for a given MIME
4400 type, font, library etc. that is currently missing. With such
4401 mechanism in place, it would be possible for the desktop to
4402 automatically propose and install leocad if some LDraw file is
4403 downloaded by the browser.&lt;/p&gt;
4404
4405 &lt;p&gt;To get some idea about the current content of the archive, I decided
4406 to write a simple program to extract all .desktop files from the
4407 Debian archive and look up the claimed MIME support there. The result
4408 can be found on the
4409 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4410 site&lt;/a&gt;. Using the collected information, it become possible to
4411 answer the question in the title. Here are the 20 most supported MIME
4412 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4413 The complete list is available from the link above.&lt;/p&gt;
4414
4415 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4416
4417 &lt;pre&gt;
4418 count MIME type
4419 ----- -----------------------
4420 32 text/plain
4421 30 audio/mpeg
4422 29 image/png
4423 28 image/jpeg
4424 27 application/ogg
4425 26 audio/x-mp3
4426 25 image/tiff
4427 25 image/gif
4428 22 image/bmp
4429 22 audio/x-wav
4430 20 audio/x-flac
4431 19 audio/x-mpegurl
4432 18 video/x-ms-asf
4433 18 audio/x-musepack
4434 18 audio/x-mpeg
4435 18 application/x-ogg
4436 17 video/mpeg
4437 17 audio/x-scpls
4438 17 audio/ogg
4439 16 video/x-ms-wmv
4440 &lt;/pre&gt;
4441
4442 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4443
4444 &lt;pre&gt;
4445 count MIME type
4446 ----- -----------------------
4447 33 text/plain
4448 32 image/png
4449 32 image/jpeg
4450 29 audio/mpeg
4451 27 image/gif
4452 26 image/tiff
4453 26 application/ogg
4454 25 audio/x-mp3
4455 22 image/bmp
4456 21 audio/x-wav
4457 19 audio/x-mpegurl
4458 19 audio/x-mpeg
4459 18 video/mpeg
4460 18 audio/x-scpls
4461 18 audio/x-flac
4462 18 application/x-ogg
4463 17 video/x-ms-asf
4464 17 text/html
4465 17 audio/x-musepack
4466 16 image/x-xbitmap
4467 &lt;/pre&gt;
4468
4469 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4470
4471 &lt;pre&gt;
4472 count MIME type
4473 ----- -----------------------
4474 31 text/plain
4475 31 image/png
4476 31 image/jpeg
4477 29 audio/mpeg
4478 28 application/ogg
4479 27 image/gif
4480 26 image/tiff
4481 26 audio/x-mp3
4482 23 audio/x-wav
4483 22 image/bmp
4484 21 audio/x-flac
4485 20 audio/x-mpegurl
4486 19 audio/x-mpeg
4487 18 video/x-ms-asf
4488 18 video/mpeg
4489 18 audio/x-scpls
4490 18 application/x-ogg
4491 17 audio/x-musepack
4492 16 video/x-ms-wmv
4493 16 video/x-msvideo
4494 &lt;/pre&gt;
4495
4496 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4497 information mentioned in DEP-11. I have not yet had time to look at
4498 it, but hope the PackageKit people in Debian are on top of these
4499 issues.&lt;/p&gt;
4500
4501 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4502 discovering a typo in my script.&lt;/p&gt;
4503 </description>
4504 </item>
4505
4506 <item>
4507 <title>Using modalias info to find packages handling my hardware</title>
4508 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4509 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4510 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4511 <description>&lt;p&gt;Yesterday, I wrote about the
4512 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4513 values provided by the Linux kernel&lt;/a&gt; following my hope for
4514 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4515 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4516 modalias values attached to package names can be used to map packages
4517 to hardware. This allow the system to look up and suggest relevant
4518 packages when I plug in some new hardware into my machine, and replace
4519 discover and discover-data as the database used to map hardware to
4520 packages.&lt;/p&gt;
4521
4522 &lt;p&gt;I create a modaliases file with entries like the following,
4523 containing package name, kernel module name (if relevant, otherwise
4524 the package name) and globs matching the relevant hardware
4525 modalias.&lt;/p&gt;
4526
4527 &lt;p&gt;&lt;blockquote&gt;
4528 Package: package-name
4529 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4530 &lt;/blockquote&gt;&lt;/p&gt;
4531
4532 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4533 for a given modalias value using this file.&lt;/p&gt;
4534
4535 &lt;p&gt;An entry like this would suggest the video and picture application
4536 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4537
4538 &lt;p&gt;&lt;blockquote&gt;
4539 Package: cheese
4540 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4541 &lt;/blockquote&gt;&lt;/p&gt;
4542
4543 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4544 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4545
4546 &lt;p&gt;&lt;blockquote&gt;
4547 Package: pcmciautils
4548 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4549 &lt;/blockquote&gt;&lt;/p&gt;
4550
4551 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4552 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4553
4554 &lt;p&gt;&lt;blockquote&gt;
4555 Package: colorhug-client
4556 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4557 &lt;/blockquote&gt;&lt;/p&gt;
4558
4559 &lt;p&gt;I believe the format is compatible with the format of the Packages
4560 file in the Debian archive. Ubuntu already uses their Packages file
4561 to store their mappings from packages to hardware.&lt;/p&gt;
4562
4563 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4564 announce the hardware it support in a way my prototype understand.
4565 This allow those publishing packages in an APT source outside the
4566 Debian archive as well as those backporting packages to make sure the
4567 hardware mapping are included in the package meta information. I&#39;ve
4568 tested such header in the pymissile package, and its modalias mapping
4569 is working as it should with my prototype. It even made it to Ubuntu
4570 Raring.&lt;/p&gt;
4571
4572 &lt;p&gt;To test if it was possible to look up supported hardware using only
4573 the shell tools available in the Debian installer, I wrote a shell
4574 implementation of the lookup code. The idea is to create files for
4575 each modalias and let the shell do the matching. Please check out and
4576 try the
4577 &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;
4578 shell script. It run without any extra dependencies and fetch the
4579 hardware mappings from the Debian archive and the subversion
4580 repository where I currently work on my prototype.&lt;/p&gt;
4581
4582 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4583 install yubikey-personalization:&lt;/p&gt;
4584
4585 &lt;p&gt;&lt;blockquote&gt;
4586 % ./hw-support-lookup
4587 &lt;br&gt;yubikey-personalization
4588 &lt;br&gt;%
4589 &lt;/blockquote&gt;&lt;/p&gt;
4590
4591 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4592 propose to install the pcmciautils package:&lt;/p&gt;
4593
4594 &lt;p&gt;&lt;blockquote&gt;
4595 % ./hw-support-lookup
4596 &lt;br&gt;pcmciautils
4597 &lt;br&gt;%
4598 &lt;/blockquote&gt;&lt;/p&gt;
4599
4600 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4601 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4602 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4603
4604 &lt;p&gt;It could be possible to generate several of the mappings between
4605 packages and hardware. One source would be to look at packages with
4606 kernel modules, ie packages with *.ko files in /lib/modules/, and
4607 extract their modalias information. Another would be to look at
4608 packages with udev rules, ie packages with files in
4609 /lib/udev/rules.d/, and extract their vendor/model information to
4610 generate a modalias matching rule. I have not tested any of these to
4611 see if it work.&lt;/p&gt;
4612
4613 &lt;p&gt;If you want to help implementing a system to let us propose what
4614 packages to install when new hardware is plugged into a Debian
4615 machine, please send me an email or talk to me on
4616 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4617 </description>
4618 </item>
4619
4620 <item>
4621 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4622 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4624 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4625 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4626 information, to find the packages that support a given piece of
4627 hardware, I refreshed my memory regarding modalias values, and decided
4628 to document the details. Here are my findings so far, also available
4629 in
4630 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4631 Debian Edu subversion repository&lt;/a&gt;:
4632
4633 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4634
4635 &lt;p&gt;This document try to explain what the different types of modalias
4636 values stands for. It is in part based on information from
4637 &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;,
4638 &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;,
4639 &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
4640 &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;.
4641
4642 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4643 this shell script:&lt;/p&gt;
4644
4645 &lt;pre&gt;
4646 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4647 &lt;/pre&gt;
4648
4649 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4650 using modinfo:&lt;/p&gt;
4651
4652 &lt;pre&gt;
4653 % /sbin/modinfo psmouse | grep alias:
4654 alias: serio:ty05pr*id*ex*
4655 alias: serio:ty01pr*id*ex*
4656 %
4657 &lt;/pre&gt;
4658
4659 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4660
4661 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4662 Bridge memory controller:&lt;/p&gt;
4663
4664 &lt;p&gt;&lt;blockquote&gt;
4665 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4666 &lt;/blockquote&gt;&lt;/p&gt;
4667
4668 &lt;p&gt;This represent these values:&lt;/p&gt;
4669
4670 &lt;pre&gt;
4671 v 00008086 (vendor)
4672 d 00002770 (device)
4673 sv 00001028 (subvendor)
4674 sd 000001AD (subdevice)
4675 bc 06 (bus class)
4676 sc 00 (bus subclass)
4677 i 00 (interface)
4678 &lt;/pre&gt;
4679
4680 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4681 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4682 0600. The 0600 class is a host bridge. Other useful bus values are
4683 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4684
4685 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4686 means.&lt;/p&gt;
4687
4688 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4689
4690 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4691 USB hub in a laptop:&lt;/p&gt;
4692
4693 &lt;p&gt;&lt;blockquote&gt;
4694 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4695 &lt;/blockquote&gt;&lt;/p&gt;
4696
4697 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4698
4699 &lt;pre&gt;
4700 v 1D6B (device vendor)
4701 p 0001 (device product)
4702 d 0206 (bcddevice)
4703 dc 09 (device class)
4704 dsc 00 (device subclass)
4705 dp 00 (device protocol)
4706 ic 09 (interface class)
4707 isc 00 (interface subclass)
4708 ip 00 (interface protocol)
4709 &lt;/pre&gt;
4710
4711 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4712 class is in the interface class section. For a simple USB web camera,
4713 these alias entries show up:&lt;/p&gt;
4714
4715 &lt;p&gt;&lt;blockquote&gt;
4716 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4717 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4718 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4719 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4720 &lt;/blockquote&gt;&lt;/p&gt;
4721
4722 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4723 camera), 0101 is audio control device and 0102 is audio streaming (aka
4724 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4725
4726 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4727
4728 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4729 receiver in a Thinkpad X40:&lt;/p&gt;
4730
4731 &lt;p&gt;&lt;blockquote&gt;
4732 acpi:IBM0071:PNP0511:
4733 &lt;/blockquote&gt;&lt;/p&gt;
4734
4735 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4736
4737 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4738
4739 &lt;p&gt;The DMI table contain lots of information about the computer case
4740 and model. This is an entry for a IBM Thinkpad X40, fetched from
4741 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4742
4743 &lt;p&gt;&lt;blockquote&gt;
4744 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4745 &lt;/blockquote&gt;&lt;/p&gt;
4746
4747 &lt;p&gt;The values present are&lt;/p&gt;
4748
4749 &lt;pre&gt;
4750 bvn IBM (BIOS vendor)
4751 bvr 1UETB6WW(1.66) (BIOS version)
4752 bd 06/15/2005 (BIOS date)
4753 svn IBM (system vendor)
4754 pn 2371H4G (product name)
4755 pvr ThinkPadX40 (product version)
4756 rvn IBM (board vendor)
4757 rn 2371H4G (board name)
4758 rvr NotAvailable (board version)
4759 cvn IBM (chassis vendor)
4760 ct 10 (chassis type)
4761 cvr NotAvailable (chassis version)
4762 &lt;/pre&gt;
4763
4764 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4765 found in the dmidecode source:&lt;/p&gt;
4766
4767 &lt;pre&gt;
4768 3 Desktop
4769 4 Low Profile Desktop
4770 5 Pizza Box
4771 6 Mini Tower
4772 7 Tower
4773 8 Portable
4774 9 Laptop
4775 10 Notebook
4776 11 Hand Held
4777 12 Docking Station
4778 13 All In One
4779 14 Sub Notebook
4780 15 Space-saving
4781 16 Lunch Box
4782 17 Main Server Chassis
4783 18 Expansion Chassis
4784 19 Sub Chassis
4785 20 Bus Expansion Chassis
4786 21 Peripheral Chassis
4787 22 RAID Chassis
4788 23 Rack Mount Chassis
4789 24 Sealed-case PC
4790 25 Multi-system
4791 26 CompactPCI
4792 27 AdvancedTCA
4793 28 Blade
4794 29 Blade Enclosing
4795 &lt;/pre&gt;
4796
4797 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4798 table. For example my home server is a tower, but the DMI modalias
4799 claim it is a desktop.&lt;/p&gt;
4800
4801 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4802
4803 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4804 test machine:&lt;/p&gt;
4805
4806 &lt;p&gt;&lt;blockquote&gt;
4807 serio:ty01pr00id00ex00
4808 &lt;/blockquote&gt;&lt;/p&gt;
4809
4810 &lt;p&gt;The values present are&lt;/p&gt;
4811
4812 &lt;pre&gt;
4813 ty 01 (type)
4814 pr 00 (prototype)
4815 id 00 (id)
4816 ex 00 (extra)
4817 &lt;/pre&gt;
4818
4819 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4820 the valid values are.&lt;/p&gt;
4821
4822 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4823
4824 &lt;p&gt;There are heaps of other modalias subtypes according to
4825 file2alias.c. There is the rest of the list from that source: amba,
4826 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4827 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4828 vmbus, x86cpu and zorro. I did not spend time documenting all of
4829 these, as they do not seem relevant for my intended use with mapping
4830 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4831
4832 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4833
4834 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4835 one can use the following shell script:&lt;/p&gt;
4836
4837 &lt;pre&gt;
4838 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4839 echo &quot;$id&quot; ; \
4840 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4841 done
4842 &lt;/pre&gt;
4843
4844 &lt;p&gt;The output can look like this (only the first few entries as the
4845 list is very long on my test machine):&lt;/p&gt;
4846
4847 &lt;pre&gt;
4848 acpi:ACPI0003:
4849 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4850 acpi:device:
4851 FATAL: Module acpi:device: not found.
4852 acpi:IBM0068:
4853 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4854 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4855 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4856 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4857 acpi:IBM0071:PNP0511:
4858 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4859 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4860 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4861 [...]
4862 &lt;/pre&gt;
4863
4864 &lt;p&gt;If you want to help implementing a system to let us propose what
4865 packages to install when new hardware is plugged into a Debian
4866 machine, please send me an email or talk to me on
4867 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4868
4869 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4870 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4871 in /sys/ with space in them.&lt;/p&gt;
4872 </description>
4873 </item>
4874
4875 <item>
4876 <title>Moved the pymissile Debian packaging to collab-maint</title>
4877 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4878 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4879 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4880 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4881 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4882 Launcher and updated the Debian package
4883 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4884 sure udev will fix the device permissions when it is plugged in. I
4885 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4886 hopefully make the package be proposed by jockey in Ubuntu when a user
4887 plug in his rocket launcher. In the process I moved the source to a
4888 git repository under collab-maint, to make it easier for any DD to
4889 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4890 is not very active, but the software still work for me even after five
4891 years of relative silence. The new git repository is not listed in
4892 the uploaded package yet, because I want to test the other changes a
4893 bit more before I upload the new version. If you want to check out
4894 the new version with a .desktop file included, visit the
4895 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4896 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4897 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4898 </description>
4899 </item>
4900
4901 <item>
4902 <title>Lets make hardware dongles easier to use in Debian</title>
4903 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4904 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4905 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4906 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4907 general, is that there is a great package management system with the
4908 ability to automatically install software packages by downloading them
4909 from the distribution mirrors, but no way to get it to automatically
4910 install the packages I need to use the hardware I plug into my
4911 machine. Even if the package to use it is easily available from the
4912 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4913 suggest to automatically install the python-nxt, nbc and t2n packages
4914 I need to talk to it. When I plug in a Yubikey, it could propose the
4915 yubikey-personalization package. The information required to do this
4916 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4917
4918 &lt;p&gt;Some years ago, I proposed to
4919 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4920 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4921 simple:
4922
4923 &lt;ul&gt;
4924
4925 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4926 starting when a user log in.&lt;/li&gt;
4927
4928 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4929 hardware is inserted into the computer.&lt;/li&gt;
4930
4931 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4932 database mapping to packages, and take note of any non-installed
4933 packages.&lt;/li&gt;
4934
4935 &lt;li&gt;Show a message to the user proposing to install the discovered
4936 package, and make it easy to install it.&lt;/li&gt;
4937
4938 &lt;/ul&gt;
4939
4940 &lt;p&gt;I am not sure what the best way to implement this is, but my
4941 initial idea was to use dbus events to discover new hardware, the
4942 discover database to find packages and
4943 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4944 packages.&lt;/p&gt;
4945
4946 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4947 draft package is now checked into
4948 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4949 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4950 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4951 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4952 the relevant packages in Debian, and uploaded a new version
4953 2.2013.01.09 to unstable. I also discovered that the current
4954 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4955 package in Debian no longer discovered any USB devices, because
4956 /proc/bus/usb/devices is no longer present. I ported it to use
4957 libusb as a fall back option to get it working. The fixed package
4958 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4959 because of the freeze).&lt;/p&gt;
4960
4961 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4962 desktop notification to show up (only once, the first time it is
4963 inserted):&lt;/p&gt;
4964
4965 &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;
4966
4967 &lt;p&gt;For this prototype to be really useful, some way to automatically
4968 install the proposed packages by pressing the &quot;Please install
4969 program(s)&quot; button should to be implemented.&lt;/p&gt;
4970
4971 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4972 happen, please help me update the discover-data database with mappings
4973 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4974 list the package you would like to have installed when a given
4975 hardware device is inserted into your computer, and report bugs using
4976 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4977 such mapping, please let me know.&lt;/p&gt;
4978
4979 &lt;p&gt;This prototype need more work, and there are several questions that
4980 should be considered before it is ready for production use. Is dbus
4981 the correct way to detect new hardware? At the moment I look for HAL
4982 dbus events on the system bus, because that is the events I could see
4983 on my Debian Squeeze KDE desktop. Are there better events to use?
4984 How should the user be notified? Is the desktop notification
4985 mechanism the best option, or should the background daemon raise a
4986 popup instead? How should packages be installed? When should they
4987 not be installed?&lt;/p&gt;
4988
4989 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4990 please send me an email. :)&lt;/p&gt;
4991 </description>
4992 </item>
4993
4994 <item>
4995 <title>New IRC channel for LEGO designers using Debian</title>
4996 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4997 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4998 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4999 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
5000 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
5001 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
5002 discovered I had to build all the tools myself because none were
5003 already in Debian Squeeze. If Debian support for LEGO is something
5004 you care about, please join me on the IRC channel
5005 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
5006 irc.debian.org). There is a lot that could be done to improve the
5007 Debian support for LEGO designers. For example both CAD software
5008 and Mindstorm compilers are missing. :)&lt;/p&gt;
5009
5010 &lt;p&gt;Update 2012-01-03: A
5011 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
5012 including links to Lego related packages is now available.&lt;/p&gt;
5013 </description>
5014 </item>
5015
5016 <item>
5017 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
5018 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
5019 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
5020 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
5021 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
5022 year! I hope next year will prove to be a good year.&lt;/p&gt;
5023
5024 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
5025 decentralised &quot;currency&quot; that allow people to transfer bitcoins
5026 between each other with minimal overhead, is a very interesting
5027 experiment. And as I wrote a few days ago, the bitcoin situation in
5028 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
5029 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
5030 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
5031 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
5032 for one of the ftpmasters to approve the new bitcoin-qt package
5033 name.&lt;/p&gt;
5034
5035 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
5036 team in Debian, you can easily test the package in Debian Squeeze
5037 using the following steps to get a set of working packages:&lt;/p&gt;
5038
5039 &lt;blockquote&gt;&lt;pre&gt;
5040 git clone git://git.debian.org/git/collab-maint/bitcoin
5041 cd bitcoin
5042 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5043 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5044 &lt;/pre&gt;&lt;/blockquote&gt;
5045
5046 &lt;p&gt;You might have to install some build dependencies as well. The
5047 list of commands should give you two packages, bitcoind and
5048 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5049 client will download the complete set of bitcoin &quot;blocks&quot;, which need
5050 around 5.6 GiB of data on my machine at the moment. Make sure your
5051 ~/.bitcoin/ directory have lots of spare room if you want to download
5052 all the blocks. The client will warn if the disk is getting full, so
5053 there is not really a problem if you got too little room, but you will
5054 not be able to get all the features out of the client.&lt;/p&gt;
5055
5056 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5057 activities, please send Bitcoin donations to my address
5058 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5059 </description>
5060 </item>
5061
5062 <item>
5063 <title>A word on bitcoin support in Debian</title>
5064 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
5065 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
5066 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
5067 <description>&lt;p&gt;It has been a while since I wrote about
5068 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
5069 peer-to-peer based crypto-currency, and the reason is simply that I
5070 have been busy elsewhere. But two days ago, I started looking at the
5071 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
5072 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
5073 is now maintained by a
5074 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
5075 people&lt;/a&gt;, and the grunt work had already been done by this team. We
5076 owe a huge thank you to all these team members. :)
5077 But I was sad to discover that the bitcoin client is missing in
5078 Wheezy. It is only available in Sid (and an outdated client from
5079 backports). The client had several RC bugs registered in BTS blocking
5080 it from entering testing. To try to help the team and improve the
5081 situation, I spent some time providing patches and triaging the bug
5082 reports. I also had a look at the bitcoin package available from Matt
5083 Corallo in a
5084 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
5085 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
5086 Debian package.&lt;/p&gt;
5087
5088 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
5089 IRC, I pushed several patches into the collab-maint git repository to
5090 improve the package. It now contains fixes for the RC issues (not from
5091 me, but fixed by Scott Howard), build rules for a Qt GUI client
5092 package, konqueror support for the bitcoin: URI and bash completion
5093 setup. As I work on Debian Squeeze, I also created
5094 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
5095 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
5096 it and try to integrate it into the git repository before uploading a
5097 new version to unstable.
5098
5099 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
5100 centralized control currently exercised in the monetary system. I
5101 find it completely unacceptable that the USA government is collecting
5102 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5103 that the major credit card companies can block legal money
5104 transactions to Wikileaks. But for bitcoin to succeed, more people
5105 need to use bitcoins, and more people need to accept bitcoins when
5106 they sell products and services. Improving the bitcoin support in
5107 Debian is a small step in the right direction, but not enough.
5108 Unfortunately the user experience when browsing the web and wanting to
5109 pay with bitcoin is still not very good. The bitcoin: URI is a step
5110 in the right direction, but need to work in most or every browser in
5111 use. Also the bitcoin-qt client is too heavy to fire up to do a
5112 quick transaction. I believe there are other clients available, but
5113 have not tested them.&lt;/p&gt;
5114
5115 &lt;p&gt;My
5116 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
5117 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
5118 I received 20.15 BTC so far on the address I provided in my blog two
5119 years ago, as can be
5120 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
5121 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
5122 donation. The blockexplorer service demonstrates quite well that
5123 bitcoin is not quite anonymous and untracked. :) I wonder if the
5124 number of users have gone up since then. If you use bitcoin and want
5125 to show your support of my activity, please send Bitcoin donations to
5126 the same address as last time,
5127 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5128 </description>
5129 </item>
5130
5131 <item>
5132 <title>Git repository for song book for Computer Scientists</title>
5133 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
5134 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
5135 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
5136 <description>&lt;p&gt;As I
5137 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
5138 this summer&lt;/a&gt;, I have created a Computer Science song book a few
5139 years ago, and today I finally found time to create a public
5140 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
5141 repository for the project&lt;/a&gt;.&lt;/p&gt;
5142
5143 &lt;p&gt;If you want to help out, please clone the source and submit patches
5144 to the HTML version. To generate the PDF and PostScript version,
5145 please use prince XML, or let me know about a useful free software
5146 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
5147
5148 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
5149 PostScript formats at
5150 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
5151 Science Songbook&lt;/a&gt;.&lt;/p&gt;
5152 </description>
5153 </item>
5154
5155 <item>
5156 <title>Gratulerer med 19-årsdagen, Debian!</title>
5157 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
5158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
5159 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
5160 <description>&lt;p&gt;I dag fyller
5161 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
5162 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
5163 si gratulerer med dagen, Debian!&lt;/p&gt;
5164 </description>
5165 </item>
5166
5167 <item>
5168 <title>Song book for Computer Scientists</title>
5169 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
5170 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
5171 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
5172 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
5173 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
5174 collecting computer related songs for use at parties. The original
5175 version was written in LaTeX, but a few years ago I got help from
5176 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5177 while keeping the ability to create a nice book in PDF format. I have
5178 not had time to maintain the book for a while now, and guess I should
5179 put it up on some public version control repository where others can
5180 help me extend and update the book. If anyone is volunteering to help
5181 me with this, send me an email. Also let me know if there are songs
5182 missing in my book.&lt;/p&gt;
5183
5184 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
5185 me today that I really should let all my readers share the joys of
5186 singing out load about programming, computers and computer networks.
5187 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
5188 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
5189 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
5190 Computer Science Songbook&lt;/a&gt;.
5191 </description>
5192 </item>
5193
5194 <item>
5195 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
5196 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
5197 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
5198 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
5199 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
5200 around 1000 at the moment. To be able to get help from the vendors
5201 when something go wrong, we want to keep the firmware on the servers
5202 up to date. If the firmware isn&#39;t the latest and greatest, the
5203 vendors typically refuse to start debugging any problems until the
5204 firmware is upgraded. So before every reboot, we want to upgrade the
5205 firmware, and we would really like everyone handling servers at the
5206 university to do this themselves when they plan to reboot a machine.
5207 For that to happen we at the unix server admin group need to provide
5208 the tools to do so.&lt;/p&gt;
5209
5210 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
5211 fetch and install the latest firmware for the servers we got. Most of
5212 our hardware are from Dell and HP, so I have focused on these servers
5213 so far. This blog post is about the Dell part.&lt;/P&gt;
5214
5215 &lt;p&gt;On the Dell FTP site I was lucky enough to find
5216 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
5217 with firmware information for all 11th generation servers, listing
5218 which firmware should be used on a given model and where on the FTP
5219 site I can find it. Using a simple perl XML parser I can then
5220 download the shell scripts Dell provides to do firmware upgrades from
5221 within Linux and reboot when all the firmware is primed and ready to
5222 be activated on the first reboot.&lt;/p&gt;
5223
5224 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
5225 Are there anyone working on similar tools for firmware upgrading all
5226 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
5227
5228 &lt;p&gt;&lt;pre&gt;
5229 #!/usr/bin/perl
5230 use strict;
5231 use warnings;
5232 use File::Temp qw(tempdir);
5233 BEGIN {
5234 # Install needed RHEL packages if missing
5235 my %rhelmodules = (
5236 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
5237 );
5238 for my $module (keys %rhelmodules) {
5239 eval &quot;use $module;&quot;;
5240 if ($@) {
5241 my $pkg = $rhelmodules{$module};
5242 system(&quot;yum install -y $pkg&quot;);
5243 eval &quot;use $module;&quot;;
5244 }
5245 }
5246 }
5247 my $errorsto = &#39;pere@hungry.com&#39;;
5248
5249 upgrade_dell();
5250
5251 exit 0;
5252
5253 sub run_firmware_script {
5254 my ($opts, $script) = @_;
5255 unless ($script) {
5256 print STDERR &quot;fail: missing script name\n&quot;;
5257 exit 1
5258 }
5259 print STDERR &quot;Running $script\n\n&quot;;
5260
5261 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
5262 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
5263 } else {
5264 print STDERR &quot;fail: firmware script returned error\n&quot;;
5265 }
5266 }
5267
5268 sub run_firmware_scripts {
5269 my ($opts, @dirs) = @_;
5270 # Run firmware packages
5271 for my $dir (@dirs) {
5272 print STDERR &quot;info: Running scripts in $dir\n&quot;;
5273 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
5274 while (my $s = readdir $dh) {
5275 next if $s =~ m/^\.\.?/;
5276 run_firmware_script($opts, &quot;$dir/$s&quot;);
5277 }
5278 closedir $dh;
5279 }
5280 }
5281
5282 sub download {
5283 my $url = shift;
5284 print STDERR &quot;info: Downloading $url\n&quot;;
5285 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
5286 }
5287
5288 sub upgrade_dell {
5289 my @dirs;
5290 my $product = `dmidecode -s system-product-name`;
5291 chomp $product;
5292
5293 if ($product =~ m/PowerEdge/) {
5294
5295 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5296 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
5297
5298 my $tmpdir = tempdir(
5299 CLEANUP =&gt; 1
5300 );
5301 chdir($tmpdir);
5302 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
5303 system(&#39;gunzip Catalog.xml.gz&#39;);
5304 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
5305 # -q is quiet, disabling interactivity and reducing console output
5306 my $fwopts = &quot;-q&quot;;
5307 if (@paths) {
5308 for my $url (@paths) {
5309 fetch_dell_fw($url);
5310 }
5311 run_firmware_scripts($fwopts, $tmpdir);
5312 } else {
5313 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5314 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5315 }
5316 chdir(&#39;/&#39;);
5317 } else {
5318 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5319 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5320 }
5321 }
5322
5323 sub fetch_dell_fw {
5324 my $path = shift;
5325 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
5326 download($url);
5327 }
5328
5329 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5330 # firmware packages to download from Dell. Only work for Linux
5331 # machines and 11th generation Dell servers.
5332 sub fetch_dell_fw_list {
5333 my $filename = shift;
5334
5335 my $product = `dmidecode -s system-product-name`;
5336 chomp $product;
5337 my ($mybrand, $mymodel) = split(/\s+/, $product);
5338
5339 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
5340
5341 my $xml = XMLin($filename);
5342 my @paths;
5343 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
5344 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
5345 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
5346 my $oscode;
5347 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
5348 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
5349 } else {
5350 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
5351 }
5352 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
5353 {
5354 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
5355 }
5356 }
5357 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
5358 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
5359
5360 # Drop application packages, only firmware and BIOS
5361 next if &#39;APAC&#39; eq $componenttype;
5362
5363 my $cpath = $component-&gt;{path};
5364 for my $path (@paths) {
5365 if ($cpath =~ m%/$path$%) {
5366 push(@paths, $cpath);
5367 }
5368 }
5369 }
5370 return @paths;
5371 }
5372 &lt;/pre&gt;
5373
5374 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5375 it could work on other platforms with some tweaking. Anyone know a
5376 index like Catalog.xml is available from HP for HP servers? At the
5377 moment I maintain a similar list manually and it is quickly getting
5378 outdated.&lt;/p&gt;
5379 </description>
5380 </item>
5381
5382 <item>
5383 <title>How is booting into runlevel 1 different from single user boots?</title>
5384 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5386 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5387 <description>&lt;p&gt;Wouter Verhelst have some
5388 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5389 comments and opinions&lt;/a&gt; on my blog post on
5390 &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
5391 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5392 &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
5393 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5394 small piece of his comment now, and though it best to address the
5395 misunderstanding he bring forward:&lt;/p&gt;
5396
5397 &lt;p&gt;&lt;blockquote&gt;
5398 Currently, a system admin has four options: [...] boot to a
5399 single-user system (by adding &#39;single&#39; to the kernel command line;
5400 this runs rcS and rc1 scripts)
5401 &lt;/blockquote&gt;&lt;/p&gt;
5402
5403 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5404 and booting into runlevel 1 is the same. I am not surprised he
5405 believe this, because it would make sense and is a quite sensible
5406 thing to believe. But because the boot in Debian is slightly broken,
5407 runlevel 1 do not work properly and it isn&#39;t the same as single user
5408 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5409 hard to explain.&lt;/p&gt;
5410
5411 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5412 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5413 executed in single user mode is sulogin. Single user mode is a boot
5414 state &quot;between&quot; the runlevels, and when booting into single user mode,
5415 only the scripts in /etc/rcS.d/ are executed before the init process
5416 enters the single user state. When switching to runlevel 1, the state
5417 is in fact not ending in runlevel 1, but it passes through runlevel 1
5418 and end up in the single user mode (see /etc/rc1.d/S03single, which
5419 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5420 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5421 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5422 mode).&lt;/p&gt;
5423
5424 &lt;p&gt;This summary might make it clearer. When booting for the first
5425 time into single user mode, the following commands are executed:
5426 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5427 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5428 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5429 trying to continue after visiting single user mode. Not all services
5430 are started again as they should, causing the machine to end up in an
5431 unpredicatble state. This is why Debian admins recommend rebooting
5432 after visiting single user mode.&lt;/p&gt;
5433
5434 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5435 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5436 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5437 stopped when passing through the scripts in /etc/rc1.d/, and not
5438 started again when switching away from runlevel 1 to the runlevels
5439 2-5. I believe the problem is best fixed by moving all the scripts
5440 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5441 functioning single user mode during boot.&lt;/p&gt;
5442
5443 &lt;p&gt;I have spent several years investigating the Debian boot system,
5444 and discovered this problem a few years ago. I suspect it originates
5445 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5446 </description>
5447 </item>
5448
5449 <item>
5450 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5451 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5452 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5453 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5454 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5455 are started from /etc/rcS.d/. In fact, there is a bite more of them
5456 than make sense, and this causes a few problems. What kind of
5457 problems, you might ask. There are at least two problems. The first
5458 is that it is not possible to recover a machine after switching to
5459 runlevel 1. One need to actually reboot to get the machine back to
5460 the expected state. The other is that single user boot will sometimes
5461 run into problems because some of the subsystems are activated before
5462 the root login is presented, causing problems when trying to recover a
5463 machine from a problem in that subsystem. A minor additional point is
5464 that moving more scripts out of rcS.d/ and into the other rc#.d/
5465 directories will increase the amount of scripts that can run in
5466 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5467
5468 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5469 scripts that _have_ to execute before the root login prompt is
5470 presented during a single user boot should go there. Everything else
5471 should go into the numeric runlevels. This means things like
5472 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5473 the numeric runlevels. Today in Debian, there are around 115 init.d
5474 scripts that are started from rcS.d/, and most of them should be moved
5475 out. Do your package have one of them? Please help us make single
5476 user and runlevel 1 better by moving it.&lt;/p&gt;
5477
5478 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5479 etc. should still be started from rcS.d/, but there is for example no
5480 need to have the network enabled before the single user login prompt
5481 is presented.&lt;/p&gt;
5482
5483 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5484 Debian systems working while scripts migrate and during upgrades, the
5485 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5486 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5487 and the next ones can only be moved when their dependencies have been
5488 moved first. This migration must be done sequentially while we ensure
5489 that the package system upgrade packages in the right order to keep
5490 the system state correct. This will require some coordination when it
5491 comes to network related packages, but most of the packages with
5492 scripts that should migrate do not have anything in rcS.d/ depending
5493 on them. Some packages have already been updated, like the sudo
5494 package, while others are still left to do. I wish I had time to work
5495 on this myself, but real live constrains make it unlikely that I will
5496 find time to push this forward.&lt;/p&gt;
5497 </description>
5498 </item>
5499
5500 <item>
5501 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5502 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5503 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5504 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5505 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5506 mentioned the issues I believe should be improved in Debian for its
5507 desktop to be useful for more people. The use case for this is my
5508 parents, which are currently running Kubuntu which solve the
5509 issues.&lt;/p&gt;
5510
5511 &lt;p&gt;I suspect these four missing features are not very hard to
5512 implement. After all, they are present in Ubuntu, so if we wanted to
5513 do this in Debian we would have a source.&lt;/p&gt;
5514
5515 &lt;ol&gt;
5516
5517 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5518 are new packages available for upgrades, a icon in the KDE status bar
5519 indicate this, and clicking on it will activate the simple upgrade
5520 tool to handle it. I have no problem guiding both of my parents
5521 through the process over the phone. If a kernel reboot is required,
5522 this too is indicated by the status bars and the upgrade tool. Last
5523 time I checked, nothing with the same features was working in KDE in
5524 Debian.&lt;/li&gt;
5525
5526 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5527 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5528 currently have a handler for, it will ask the user if the system
5529 should search for a package that would add support for this MIME type,
5530 and if the user say yes, the APT sources will be searched for packages
5531 advertising the MIME type in their control file (visible in the
5532 Packages file in the APT archive). If one or more packages are found,
5533 it is a simple click of the mouse to add support for the missing mime
5534 type. If the package require the user to accept some non-free
5535 license, this is explained to the user. The entire process make it
5536 more clear to the user why something do not work in the browser, and
5537 make the chances higher for the user to blame the web page authors and
5538 not the browser for any missing features.&lt;/li&gt;
5539
5540 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5541 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5542 it is not supporting, a dialog pop up asking the user if the system
5543 should search for a package that would add support for it. This
5544 happen with things like MP3, Windows Media or H.264. The selection
5545 and installation procedure is very similar to the Firefox browser
5546 plugin handling. This is as far as I know implemented using a
5547 gstreamer hook. The end result is that the user easily get access to
5548 the codecs that are present from the APT archives available, while
5549 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5550
5551 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5552 displaying a text/plain file in my Debian browser, it will propose to
5553 start emacs to show it. If I remember correctly, when doing the same
5554 in Kunbutu it show the file as a text file in the browser. At least I
5555 know Opera will show text files within the browser. I much prefer the
5556 latter behaviour.&lt;/li&gt;
5557
5558 &lt;/ol&gt;
5559
5560 &lt;p&gt;There are other nice features as well, like the simplified suite
5561 upgrader, but given that I am the one mostly doing the dist-upgrade,
5562 it do not matter much.&lt;/p&gt;
5563
5564 &lt;p&gt;I really hope we could get these features in place for the next
5565 Debian release. It would require the coordinated effort of several
5566 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5567 </description>
5568 </item>
5569
5570 <item>
5571 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5572 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5573 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5574 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5575 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5576 site is build on Debian/Squeeze, and this platform was chosen because
5577 I am most familiar with Debian (being a Debian Developer for around 10
5578 years) because it is the latest stable Debian release which should get
5579 security support for a few years.&lt;/p&gt;
5580
5581 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5582 that are missing in Debian at the moment. It would be great if these
5583 modules were added to the Debian archive, allowing anyone to set up
5584 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5585 in their own country using only Debian packages. The list of modules
5586 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5587 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5588 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5589 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5590 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5591 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5592 easier in the future.&lt;/p&gt;
5593
5594 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5595 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5596 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5597 with the responsibility of tracking security problems, which I really
5598 do not have time for.&lt;/p&gt;
5599 </description>
5600 </item>
5601
5602 <item>
5603 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5604 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5605 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5606 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5607 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5608 posts have been in Norwegian the last few weeks, so here is a short
5609 update in English.&lt;/p&gt;
5610
5611 &lt;p&gt;The kids still keep me too busy to get much free software work
5612 done, but I did manage to organise a project to get a Norwegian port
5613 of the British service
5614 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5615 and it has been running for a month now. The entire project has been
5616 organised by me and two others. Around Christmas we gathered sponsors
5617 to fund the development work. In January I drafted a contract with
5618 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5619 and in February the development took place. Most of it involved
5620 converting the source to use GPS coordinates instead of British
5621 easting/northing, and the resulting code should be a lot easier to get
5622 running in any country by now. The Norwegian
5623 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5624 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5625 source and the source for administrative borders in Norway, and
5626 support for this had to be added/fixed.&lt;/p&gt;
5627
5628 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5629 polishing the system before we announced it March 7th. The system is
5630 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5631 problem reports in a few weeks. Soon we hope to announce the Android
5632 and iPhone versions making it even easier to report problems with the
5633 public infrastructure.&lt;/p&gt;
5634
5635 &lt;p&gt;Perhaps something to consider for those of you in countries without
5636 such service?&lt;/p&gt;
5637 </description>
5638 </item>
5639
5640 <item>
5641 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5642 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5643 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5644 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5645 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5646 issues here at my work with the University of Oslo. My idea is that
5647 it should be possible to use the information about security issues
5648 available on the Internet, and check our locally
5649 maintained/distributed software against this information. It should
5650 allow us to verify that no known security issues are forgotten. The
5651 CVE database listing vulnerabilities seem like a great central point,
5652 and by using the package lists from Debian mapped to CVEs provided by
5653 the testing security team, I believed it should be possible to figure
5654 out which security holes were present in our free software
5655 collection.&lt;/p&gt;
5656
5657 &lt;p&gt;After reading up on the topic, it became obvious that the first
5658 building block is to be able to name software packages in a unique and
5659 consistent way across data sources. I considered several ways to do
5660 this, for example coming up with my own naming scheme like using URLs
5661 to project home pages or URLs to the Freshmeat entries, or using some
5662 existing naming scheme. And it seem like I am not the first one to
5663 come across this problem, as MITRE already proposed and implemented a
5664 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5665 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5666 software, hardware and other platform components. The CPE ids are
5667 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5668 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5669 issues for any CPE name. With this in place, all I need to do is to
5670 locate the CPE id for the software packages we use at the university.
5671 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5672 NVD entry if a CVE for the package exist).&lt;/p&gt;
5673
5674 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5675 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5676 check out, one could look up
5677 &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
5678 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5679 The most recent one is
5680 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5681 and at the bottom of the NVD page for this vulnerability the complete
5682 list of affected versions is provided.&lt;/p&gt;
5683
5684 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5685 for offline processing of issues. Using this dump, I&#39;ve written a
5686 small script taking a list of CPEs as input and list all CVEs
5687 affecting the packages represented by these CPEs. One give it CPEs
5688 with version numbers as specified above and get a list of open
5689 security issues out.&lt;/p&gt;
5690
5691 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5692 information need to be high. For that to happen, I believe as many as
5693 possible need to use and contribute to the NVD database. I notice
5694 RHEL is providing
5695 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5696 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5697 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5698
5699 &lt;p&gt;To get an idea about the quality for free software, I spent some
5700 time making it possible to compare the CVE database from Debian with
5701 the CVE database in NVD. The result look fairly good, but there are
5702 some inconsistencies in NVD (same software package having several
5703 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5704 Debian believe are affected by a CVE). Hope to find time to improve
5705 the quality of NVD, but that require being able to get in touch with
5706 someone maintaining it. So far my three emails with questions and
5707 corrections have not seen any reply, but I hope contact can be
5708 established soon.&lt;/p&gt;
5709
5710 &lt;p&gt;An interesting application for CPEs is cross platform package
5711 mapping. It would be useful to know which packages in for example
5712 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5713 this would be trivial if all linux distributions provided CPE entries
5714 for their packages.&lt;/p&gt;
5715 </description>
5716 </item>
5717
5718 <item>
5719 <title>Which module is loaded for a given PCI and USB device?</title>
5720 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5721 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5722 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5723 <description>&lt;p&gt;In the
5724 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5725 package in Debian, there is a script to report useful information
5726 about the running hardware for use when people report missing
5727 information. One part of this script that I find very useful when
5728 debugging hardware problems, is the part mapping loaded kernel module
5729 to the PCI device it claims. It allow me to quickly see if the kernel
5730 module I expect is driving the hardware I am struggling with. To see
5731 the output, make sure discover-data is installed and run
5732 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5733 one of my machines like this:&lt;/p&gt;
5734
5735 &lt;pre&gt;
5736 loaded modules:
5737 10de:03eb i2c_nforce2
5738 10de:03f1 ohci_hcd
5739 10de:03f2 ehci_hcd
5740 10de:03f0 snd_hda_intel
5741 10de:03ec pata_amd
5742 10de:03f6 sata_nv
5743 1022:1103 k8temp
5744 109e:036e bttv
5745 109e:0878 snd_bt87x
5746 11ab:4364 sky2
5747 &lt;/pre&gt;
5748
5749 &lt;p&gt;The code in question look like this, slightly modified for
5750 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5751
5752 &lt;pre&gt;
5753 if [ -d /sys/bus/pci/devices/ ] ; then
5754 echo loaded pci modules:
5755 (
5756 cd /sys/bus/pci/devices/
5757 for address in * ; do
5758 if [ -d &quot;$address/driver/module&quot; ] ; then
5759 module=`cd $address/driver/module ; pwd -P | xargs basename`
5760 if grep -q &quot;^$module &quot; /proc/modules ; then
5761 address=$(echo $address |sed s/0000://)
5762 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5763 echo &quot;$id $module&quot;
5764 fi
5765 fi
5766 done
5767 )
5768 echo
5769 fi
5770 &lt;/pre&gt;
5771
5772 &lt;p&gt;Similar code could be used to extract USB device module
5773 mappings:&lt;/p&gt;
5774
5775 &lt;pre&gt;
5776 if [ -d /sys/bus/usb/devices/ ] ; then
5777 echo loaded usb modules:
5778 (
5779 cd /sys/bus/usb/devices/
5780 for address in * ; do
5781 if [ -d &quot;$address/driver/module&quot; ] ; then
5782 module=`cd $address/driver/module ; pwd -P | xargs basename`
5783 if grep -q &quot;^$module &quot; /proc/modules ; then
5784 address=$(echo $address |sed s/0000://)
5785 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5786 if [ &quot;$id&quot; ] ; then
5787 echo &quot;$id $module&quot;
5788 fi
5789 fi
5790 fi
5791 done
5792 )
5793 echo
5794 fi
5795 &lt;/pre&gt;
5796
5797 &lt;p&gt;This might perhaps be something to include in other tools as
5798 well.&lt;/p&gt;
5799 </description>
5800 </item>
5801
5802 <item>
5803 <title>How to test if a laptop is working with Linux</title>
5804 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5805 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5806 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5807 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5808 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5809 batch of computers will work with Linux. Every year for the last few
5810 years the university have organised shared bid of a few thousand
5811 computers, and this year HP won the bid. Two different desktops and
5812 five different laptops are on the list this year. We in the UNIX
5813 group want to know which one of these computers work well with RHEL
5814 and Ubuntu, the two Linux distributions we currently handle at the
5815 university.&lt;/p&gt;
5816
5817 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5818 perhaps inspire others to test hardware as well. To test, I PXE
5819 install the OS version of choice, and log in as my normal user and run
5820 a few applications and plug in selected pieces of hardware. When
5821 something fail, I make a note about this in the test matrix and move
5822 on. If I have some spare time I try to report the bug to the OS
5823 vendor, but as I only have the machines for a short time, I rarely
5824 have the time to do this for all the problems I find.&lt;/p&gt;
5825
5826 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5827 I perform on a new model.&lt;/p&gt;
5828
5829 &lt;ul&gt;
5830
5831 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5832 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5833 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5834
5835 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5836 installation, X.org is working.&lt;/li&gt;
5837
5838 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5839 package mesa-utils on Ubuntu) and writing down the frames per second
5840 reported by the program.&lt;/li&gt;
5841
5842 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5843 logging in, and if I can hear this the test is successful. If there
5844 are several audio exits on the machine, I try them all and check if
5845 the Gnome/KDE audio mixer can control where to send the sound. I
5846 normally test this by playing
5847 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5848 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5849
5850 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5851 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5852
5853 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5854 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5855
5856 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5857 picture from the v4l device show up.&lt;/li&gt;
5858
5859 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5860 any bluetooth devices are discovered. In my office, I normally see a
5861 few.&lt;/li&gt;
5862
5863 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5864 memory modules lying around, and stick them in and see if Gnome/KDE
5865 notice this.&lt;/li&gt;
5866
5867 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5868 special button work, and if the laptop continue to work after
5869 resume.&lt;/li&gt;
5870
5871 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5872 adjusting background light, switching on/off external video output,
5873 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5874 laptop to laptop, so I just write down which are working and which are
5875 not.&lt;/li&gt;
5876
5877 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5878 acceleration sensors etc. I rarely test these, as I do not know how
5879 to quickly test if they are working or not, so I only document their
5880 existence.&lt;/li&gt;
5881
5882 &lt;/ul&gt;
5883
5884 &lt;p&gt;By now I suspect you are really curious what the test results are
5885 for the HP machines I am testing. I&#39;m not done yet, so I will report
5886 the test results later. For now I can report that HP 8100 Elite work
5887 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5888 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5889 can see, I have most machines left to test. One interesting
5890 observation is that Ubuntu Lucid has almost twice the frame rate than
5891 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5892 </description>
5893 </item>
5894
5895 <item>
5896 <title>Some thoughts on BitCoins</title>
5897 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5898 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5899 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5900 <description>&lt;p&gt;As I continue to explore
5901 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5902 what properties the system have, and how it will be affected by laws
5903 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5904
5905 &lt;p&gt;One interesting thing to note is that since the transactions are
5906 verified using a peer to peer network, all details about a transaction
5907 is known to everyone. This means that if a BitCoin address has been
5908 published like I did with mine in my initial post about BitCoin, it is
5909 possible for everyone to see how many BitCoins have been transfered to
5910 that address. There is even a web service to look at the details for
5911 all transactions. There I can see that my address
5912 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5913 have received 16.06 Bitcoin, the
5914 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5915 address of Simon Phipps have received 181.97 BitCoin and the address
5916 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5917 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5918 every one of you that donated bitcoins to support my activity. The
5919 fact that anyone can see how much money was transfered to a given
5920 address make it more obvious why the BitCoin community recommend to
5921 generate and hand out a new address for each transaction. I&#39;m told
5922 there is no way to track which addresses belong to a given person or
5923 organisation without the person or organisation revealing it
5924 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5925
5926 &lt;p&gt;In Norway, and in most other countries, there are laws and
5927 regulations limiting how much money one can transfer across the border
5928 without declaring it. There are money laundering, tax and accounting
5929 laws and regulations I would expect to apply to the use of BitCoin.
5930 If the Skolelinux foundation
5931 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5932 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5933 normal bank transfers like EFF is doing, how should this be accounted?
5934 Given that it is impossible to know if money can cross the border or
5935 not, should everything or nothing be declared? What exchange rate
5936 should be used when calculating taxes? Would receivers have to pay
5937 income tax if the foundation were to pay Skolelinux contributors in
5938 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5939
5940 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5941 accepted by a lot of users. It must be possible to get easy access to
5942 the currency (as a wage or using currency exchanges), and it must be
5943 easy to spend it. At the moment BitCoin seem fairly easy to get
5944 access to, but there are very few places to spend it. I am not really
5945 a regular user of any of the vendor types currently accepting BitCoin,
5946 so I wonder when my kind of shop would start accepting BitCoins. I
5947 would like to buy electronics, travels and subway tickets, not herbs
5948 and books. :) The currency is young, and this will improve over time
5949 if it become popular, but I suspect regular banks will start to lobby
5950 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5951 will claim it is helping fund terrorism and money laundering (which
5952 probably would be true, as is any currency in existence), but I
5953 believe the problems should be solved elsewhere and not by blaming
5954 currencies.&lt;/p&gt;
5955
5956 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5957 CPU intensive process that depend on a bit of luck as well (as one is
5958 competing against all the other miners currently spending CPU cycles
5959 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5960 BitCoin when this happen. Yesterday I came across the obvious way to
5961 join forces to increase ones changes of getting at least some coins,
5962 by coordinating the work on mining BitCoins across several machines
5963 and people, and sharing the result if one is lucky and get the 50
5964 BitCoins. Check out
5965 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5966 if this sounds interesting. I have not had time to try to set up a
5967 machine to participate there yet, but have seen that running on ones
5968 own for a few days have not yield any BitCoins througth mining
5969 yet.&lt;/p&gt;
5970
5971 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5972 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5973 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5974 it was interesting to read. The arguments presented seem to be
5975 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5976 </description>
5977 </item>
5978
5979 <item>
5980 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5981 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5982 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5983 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5984 <description>&lt;p&gt;With this weeks lawless
5985 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5986 attacks&lt;/a&gt; on Wikileak and
5987 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5988 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5989 not be trusted to handle money transactions.
5990 A blog post from
5991 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5992 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5993 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5994 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5995 some help from my friend to get it all running, and he even handed me
5996 some bitcoins to get started. I even donated a few bitcoins to Simon
5997 for helping me remember BitCoin.&lt;/p&gt;
5998
5999 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
6000 crypto-currency, decentralised and handled using peer-to-peer
6001 networks. It allows anonymous transactions and prohibits central
6002 control over the transactions, making it impossible for governments
6003 and companies alike to block donations and other transactions. The
6004 source is free software, and while the key dependency wxWidgets 2.9
6005 for the graphical user interface is missing in Debian, the command
6006 line client builds just fine. Hopefully Jonas
6007 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
6008 Debian&lt;/a&gt; soon.&lt;/p&gt;
6009
6010 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
6011 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
6012 bitcoins&lt;/a&gt; when selling services and goods, and there are even
6013 currency &quot;stock&quot; markets where the exchange rate is decided. There
6014 are not many users so far, but the concept seems promising. If you
6015 want to get started and lack a friend with any bitcoins to spare,
6016 you can even get
6017 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
6018 bitcoin at the time of writing). Use
6019 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
6020 on the current exchange rates.&lt;/p&gt;
6021
6022 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
6023 machines. If you want to support my activity, please send Bitcoin
6024 donations to the address
6025 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
6026 </description>
6027 </item>
6028
6029 <item>
6030 <title>Why isn&#39;t Debian Edu using VLC?</title>
6031 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
6032 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
6033 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
6034 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
6035 presented, and the winner among the multimedia player were VLC.
6036 Personally, I like VLC, and it is my player of choice when I first try
6037 to play a video file or stream. Only if VLC fail will I drag out
6038 gmplayer to see if it can do better. The reason is mostly the failure
6039 model and trust. When VLC fail, it normally pop up a error message
6040 reporting the problem. When mplayer fail, it normally segfault or
6041 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
6042
6043 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
6044 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6045 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
6046 plugin to play web videos seamlessly, and the VLC browser plugin is
6047 not very good. For example, it lack in-line control buttons, so there
6048 is no way for the user to pause the video. Also, when I
6049 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
6050 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
6051 failed on several video pages where mplayer based plugins worked. If
6052 the browser plugin for VLC was as good as the gecko-mediaplayer
6053 package (which uses mplayer), we would switch.&lt;/P&gt;
6054
6055 &lt;p&gt;While VLC is a good player, its user interface is slightly
6056 annoying. The most annoying feature is its inconsistent use of
6057 keyboard shortcuts. When the player is in full screen mode, its
6058 shortcuts are different from when it is playing the video in a window.
6059 For example, space only work as pause when in full screen mode. I
6060 wish it had consisten shortcuts and that space also would work when in
6061 window mode. Another nice shortcut in gmplayer is [enter] to restart
6062 the current video. It is very nice when playing short videos from the
6063 web and want to restart it when new people arrive to have a look at
6064 what is going on.&lt;/p&gt;
6065 </description>
6066 </item>
6067
6068 <item>
6069 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
6070 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
6071 <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>
6072 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
6073 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
6074 upgrade testing of the
6075 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6076 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
6077 This seem like a very good idea, so I adjusted by test scripts and
6078 can now present the updated result from today:&lt;/p&gt;
6079
6080 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6081
6082 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6083
6084 &lt;blockquote&gt;&lt;p&gt;
6085 apache2.2-bin
6086 aptdaemon
6087 baobab
6088 binfmt-support
6089 browser-plugin-gnash
6090 cheese-common
6091 cli-common
6092 cups-pk-helper
6093 dmz-cursor-theme
6094 empathy
6095 empathy-common
6096 freedesktop-sound-theme
6097 freeglut3
6098 gconf-defaults-service
6099 gdm-themes
6100 gedit-plugins
6101 geoclue
6102 geoclue-hostip
6103 geoclue-localnet
6104 geoclue-manual
6105 geoclue-yahoo
6106 gnash
6107 gnash-common
6108 gnome
6109 gnome-backgrounds
6110 gnome-cards-data
6111 gnome-codec-install
6112 gnome-core
6113 gnome-desktop-environment
6114 gnome-disk-utility
6115 gnome-screenshot
6116 gnome-search-tool
6117 gnome-session-canberra
6118 gnome-system-log
6119 gnome-themes-extras
6120 gnome-themes-more
6121 gnome-user-share
6122 gstreamer0.10-fluendo-mp3
6123 gstreamer0.10-tools
6124 gtk2-engines
6125 gtk2-engines-pixbuf
6126 gtk2-engines-smooth
6127 hamster-applet
6128 libapache2-mod-dnssd
6129 libapr1
6130 libaprutil1
6131 libaprutil1-dbd-sqlite3
6132 libaprutil1-ldap
6133 libart2.0-cil
6134 libboost-date-time1.42.0
6135 libboost-python1.42.0
6136 libboost-thread1.42.0
6137 libchamplain-0.4-0
6138 libchamplain-gtk-0.4-0
6139 libcheese-gtk18
6140 libclutter-gtk-0.10-0
6141 libcryptui0
6142 libdiscid0
6143 libelf1
6144 libepc-1.0-2
6145 libepc-common
6146 libepc-ui-1.0-2
6147 libfreerdp-plugins-standard
6148 libfreerdp0
6149 libgconf2.0-cil
6150 libgdata-common
6151 libgdata7
6152 libgdu-gtk0
6153 libgee2
6154 libgeoclue0
6155 libgexiv2-0
6156 libgif4
6157 libglade2.0-cil
6158 libglib2.0-cil
6159 libgmime2.4-cil
6160 libgnome-vfs2.0-cil
6161 libgnome2.24-cil
6162 libgnomepanel2.24-cil
6163 libgpod-common
6164 libgpod4
6165 libgtk2.0-cil
6166 libgtkglext1
6167 libgtksourceview2.0-common
6168 libmono-addins-gui0.2-cil
6169 libmono-addins0.2-cil
6170 libmono-cairo2.0-cil
6171 libmono-corlib2.0-cil
6172 libmono-i18n-west2.0-cil
6173 libmono-posix2.0-cil
6174 libmono-security2.0-cil
6175 libmono-sharpzip2.84-cil
6176 libmono-system2.0-cil
6177 libmtp8
6178 libmusicbrainz3-6
6179 libndesk-dbus-glib1.0-cil
6180 libndesk-dbus1.0-cil
6181 libopal3.6.8
6182 libpolkit-gtk-1-0
6183 libpt2.6.7
6184 libpython2.6
6185 librpm1
6186 librpmio1
6187 libsdl1.2debian
6188 libsrtp0
6189 libssh-4
6190 libtelepathy-farsight0
6191 libtelepathy-glib0
6192 libtidy-0.99-0
6193 media-player-info
6194 mesa-utils
6195 mono-2.0-gac
6196 mono-gac
6197 mono-runtime
6198 nautilus-sendto
6199 nautilus-sendto-empathy
6200 p7zip-full
6201 pkg-config
6202 python-aptdaemon
6203 python-aptdaemon-gtk
6204 python-axiom
6205 python-beautifulsoup
6206 python-bugbuddy
6207 python-clientform
6208 python-coherence
6209 python-configobj
6210 python-crypto
6211 python-cupshelpers
6212 python-elementtree
6213 python-epsilon
6214 python-evolution
6215 python-feedparser
6216 python-gdata
6217 python-gdbm
6218 python-gst0.10
6219 python-gtkglext1
6220 python-gtksourceview2
6221 python-httplib2
6222 python-louie
6223 python-mako
6224 python-markupsafe
6225 python-mechanize
6226 python-nevow
6227 python-notify
6228 python-opengl
6229 python-openssl
6230 python-pam
6231 python-pkg-resources
6232 python-pyasn1
6233 python-pysqlite2
6234 python-rdflib
6235 python-serial
6236 python-tagpy
6237 python-twisted-bin
6238 python-twisted-conch
6239 python-twisted-core
6240 python-twisted-web
6241 python-utidylib
6242 python-webkit
6243 python-xdg
6244 python-zope.interface
6245 remmina
6246 remmina-plugin-data
6247 remmina-plugin-rdp
6248 remmina-plugin-vnc
6249 rhythmbox-plugin-cdrecorder
6250 rhythmbox-plugins
6251 rpm-common
6252 rpm2cpio
6253 seahorse-plugins
6254 shotwell
6255 software-center
6256 system-config-printer-udev
6257 telepathy-gabble
6258 telepathy-mission-control-5
6259 telepathy-salut
6260 tomboy
6261 totem
6262 totem-coherence
6263 totem-mozilla
6264 totem-plugins
6265 transmission-common
6266 xdg-user-dirs
6267 xdg-user-dirs-gtk
6268 xserver-xephyr
6269 &lt;/p&gt;&lt;/blockquote&gt;
6270
6271 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6272
6273 &lt;blockquote&gt;&lt;p&gt;
6274 cheese
6275 ekiga
6276 eog
6277 epiphany-extensions
6278 evolution-exchange
6279 fast-user-switch-applet
6280 file-roller
6281 gcalctool
6282 gconf-editor
6283 gdm
6284 gedit
6285 gedit-common
6286 gnome-games
6287 gnome-games-data
6288 gnome-nettool
6289 gnome-system-tools
6290 gnome-themes
6291 gnuchess
6292 gucharmap
6293 guile-1.8-libs
6294 libavahi-ui0
6295 libdmx1
6296 libgalago3
6297 libgtk-vnc-1.0-0
6298 libgtksourceview2.0-0
6299 liblircclient0
6300 libsdl1.2debian-alsa
6301 libspeexdsp1
6302 libsvga1
6303 rhythmbox
6304 seahorse
6305 sound-juicer
6306 system-config-printer
6307 totem-common
6308 transmission-gtk
6309 vinagre
6310 vino
6311 &lt;/p&gt;&lt;/blockquote&gt;
6312
6313 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6314
6315 &lt;blockquote&gt;&lt;p&gt;
6316 gstreamer0.10-gnomevfs
6317 &lt;/p&gt;&lt;/blockquote&gt;
6318
6319 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6320
6321 &lt;blockquote&gt;&lt;p&gt;
6322 [nothing]
6323 &lt;/p&gt;&lt;/blockquote&gt;
6324
6325 &lt;p&gt;This is for KDE:&lt;/p&gt;
6326
6327 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6328
6329 &lt;blockquote&gt;&lt;p&gt;
6330 ksmserver
6331 &lt;/p&gt;&lt;/blockquote&gt;
6332
6333 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6334
6335 &lt;blockquote&gt;&lt;p&gt;
6336 kwin
6337 network-manager-kde
6338 &lt;/p&gt;&lt;/blockquote&gt;
6339
6340 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6341
6342 &lt;blockquote&gt;&lt;p&gt;
6343 arts
6344 dolphin
6345 freespacenotifier
6346 google-gadgets-gst
6347 google-gadgets-xul
6348 kappfinder
6349 kcalc
6350 kcharselect
6351 kde-core
6352 kde-plasma-desktop
6353 kde-standard
6354 kde-window-manager
6355 kdeartwork
6356 kdeartwork-emoticons
6357 kdeartwork-style
6358 kdeartwork-theme-icon
6359 kdebase
6360 kdebase-apps
6361 kdebase-workspace
6362 kdebase-workspace-bin
6363 kdebase-workspace-data
6364 kdeeject
6365 kdelibs
6366 kdeplasma-addons
6367 kdeutils
6368 kdewallpapers
6369 kdf
6370 kfloppy
6371 kgpg
6372 khelpcenter4
6373 kinfocenter
6374 konq-plugins-l10n
6375 konqueror-nsplugins
6376 kscreensaver
6377 kscreensaver-xsavers
6378 ktimer
6379 kwrite
6380 libgle3
6381 libkde4-ruby1.8
6382 libkonq5
6383 libkonq5-templates
6384 libnetpbm10
6385 libplasma-ruby
6386 libplasma-ruby1.8
6387 libqt4-ruby1.8
6388 marble-data
6389 marble-plugins
6390 netpbm
6391 nuvola-icon-theme
6392 plasma-dataengines-workspace
6393 plasma-desktop
6394 plasma-desktopthemes-artwork
6395 plasma-runners-addons
6396 plasma-scriptengine-googlegadgets
6397 plasma-scriptengine-python
6398 plasma-scriptengine-qedje
6399 plasma-scriptengine-ruby
6400 plasma-scriptengine-webkit
6401 plasma-scriptengines
6402 plasma-wallpapers-addons
6403 plasma-widget-folderview
6404 plasma-widget-networkmanagement
6405 ruby
6406 sweeper
6407 update-notifier-kde
6408 xscreensaver-data-extra
6409 xscreensaver-gl
6410 xscreensaver-gl-extra
6411 xscreensaver-screensaver-bsod
6412 &lt;/p&gt;&lt;/blockquote&gt;
6413
6414 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6415
6416 &lt;blockquote&gt;&lt;p&gt;
6417 ark
6418 google-gadgets-common
6419 google-gadgets-qt
6420 htdig
6421 kate
6422 kdebase-bin
6423 kdebase-data
6424 kdepasswd
6425 kfind
6426 klipper
6427 konq-plugins
6428 konqueror
6429 ksysguard
6430 ksysguardd
6431 libarchive1
6432 libcln6
6433 libeet1
6434 libeina-svn-06
6435 libggadget-1.0-0b
6436 libggadget-qt-1.0-0b
6437 libgps19
6438 libkdecorations4
6439 libkephal4
6440 libkonq4
6441 libkonqsidebarplugin4a
6442 libkscreensaver5
6443 libksgrd4
6444 libksignalplotter4
6445 libkunitconversion4
6446 libkwineffects1a
6447 libmarblewidget4
6448 libntrack-qt4-1
6449 libntrack0
6450 libplasma-geolocation-interface4
6451 libplasmaclock4a
6452 libplasmagenericshell4
6453 libprocesscore4a
6454 libprocessui4a
6455 libqalculate5
6456 libqedje0a
6457 libqtruby4shared2
6458 libqzion0a
6459 libruby1.8
6460 libscim8c2a
6461 libsmokekdecore4-3
6462 libsmokekdeui4-3
6463 libsmokekfile3
6464 libsmokekhtml3
6465 libsmokekio3
6466 libsmokeknewstuff2-3
6467 libsmokeknewstuff3-3
6468 libsmokekparts3
6469 libsmokektexteditor3
6470 libsmokekutils3
6471 libsmokenepomuk3
6472 libsmokephonon3
6473 libsmokeplasma3
6474 libsmokeqtcore4-3
6475 libsmokeqtdbus4-3
6476 libsmokeqtgui4-3
6477 libsmokeqtnetwork4-3
6478 libsmokeqtopengl4-3
6479 libsmokeqtscript4-3
6480 libsmokeqtsql4-3
6481 libsmokeqtsvg4-3
6482 libsmokeqttest4-3
6483 libsmokeqtuitools4-3
6484 libsmokeqtwebkit4-3
6485 libsmokeqtxml4-3
6486 libsmokesolid3
6487 libsmokesoprano3
6488 libtaskmanager4a
6489 libtidy-0.99-0
6490 libweather-ion4a
6491 libxklavier16
6492 libxxf86misc1
6493 okteta
6494 oxygencursors
6495 plasma-dataengines-addons
6496 plasma-scriptengine-superkaramba
6497 plasma-widget-lancelot
6498 plasma-widgets-addons
6499 plasma-widgets-workspace
6500 polkit-kde-1
6501 ruby1.8
6502 systemsettings
6503 update-notifier-common
6504 &lt;/p&gt;&lt;/blockquote&gt;
6505
6506 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6507 aptitude a bit more similar, but there are still quite a lott of
6508 differences. I have no idea what packages should be installed after
6509 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6510 </description>
6511 </item>
6512
6513 <item>
6514 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6515 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6516 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6517 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6518 <description>&lt;p&gt;Most of the computers in use by the
6519 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6520 are virtual machines. And they have been Xen machines running on a
6521 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6522 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6523 bit harder that it could have been, because we set up the Xen virtual
6524 machines to get the virtual partitions from LVM, which as far as I
6525 know is not supported by KVM. So to migrate, we had to convert
6526 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6527
6528 &lt;p&gt;I found
6529 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6530 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6531 migration. It uses qemu-img from the qemu package to make the disk
6532 image, parted to partition it, losetup and kpartx to present the disk
6533 image partions as devices, and dd to copy the data. I NFS mounted the
6534 new servers storage area on the old server to do the migration.&lt;/p&gt;
6535
6536 &lt;pre&gt;
6537 #!/bin/sh
6538
6539 # Based on
6540 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6541
6542 set -e
6543 set -x
6544
6545 if [ -z &quot;$1&quot; ] ; then
6546 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6547 exit 1
6548 else
6549 host=&quot;$1&quot;
6550 fi
6551
6552 if [ ! -e /dev/vg_data/$host-disk ] ; then
6553 echo &quot;error: unable to find LVM volume for $host&quot;
6554 exit 1
6555 fi
6556
6557 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6558 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6559 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6560 totalsize=$(( ( $disksize + $swapsize ) ))
6561
6562 img=$host.img
6563 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6564 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6565
6566 parted $img mklabel msdos
6567 parted $img mkpart primary linux-swap 0 $disksize
6568 parted $img mkpart primary ext2 $disksize $totalsize
6569 parted $img set 1 boot on
6570
6571 modprobe dm-mod
6572 losetup /dev/loop0 $img
6573 kpartx -a /dev/loop0
6574
6575 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6576 fsck.ext3 -f /dev/mapper/loop0p1 || true
6577 mkswap /dev/mapper/loop0p2
6578
6579 kpartx -d /dev/loop0
6580 losetup -d /dev/loop0
6581 &lt;/pre&gt;
6582
6583 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6584 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6585
6586 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6587 the new disk image attached, installed grub-pc and linux-image-686 and
6588 set up grub to boot from the disk image. After this, the KVM machines
6589 seem to work just fine.&lt;/p&gt;
6590 </description>
6591 </item>
6592
6593 <item>
6594 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6595 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6596 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6597 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6598 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6599 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6600 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6601 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6602
6603 &lt;p&gt;I still do not know what a correct migration should look like, so I
6604 report any differences between apt and aptitude and hope someone else
6605 can see if anything should be changed.&lt;/p&gt;
6606
6607 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6608
6609 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6610
6611 &lt;blockquote&gt;&lt;p&gt;
6612 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6613 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6614 dmz-cursor-theme empathy empathy-common finger
6615 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6616 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6617 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6618 gnome-cards-data gnome-codec-install gnome-core
6619 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6620 gnome-search-tool gnome-session-canberra gnome-spell
6621 gnome-system-log gnome-themes-extras gnome-themes-more
6622 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6623 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6624 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6625 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6626 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6627 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6628 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6629 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6630 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6631 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6632 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6633 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6634 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6635 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6636 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6637 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6638 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6639 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6640 libmono-security2.0-cil libmono-sharpzip2.84-cil
6641 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6642 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6643 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6644 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6645 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6646 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6647 libxalan2-java libxerces2-java media-player-info mesa-utils
6648 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6649 nautilus-sendto-empathy openoffice.org-writer2latex
6650 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6651 python-aptdaemon python-aptdaemon-gtk python-axiom
6652 python-beautifulsoup python-bugbuddy python-clientform
6653 python-coherence python-configobj python-crypto python-cupshelpers
6654 python-cupsutils python-eggtrayicon python-elementtree
6655 python-epsilon python-evolution python-feedparser python-gdata
6656 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6657 python-gtksourceview2 python-httplib2 python-louie python-mako
6658 python-markupsafe python-mechanize python-nevow python-notify
6659 python-opengl python-openssl python-pam python-pkg-resources
6660 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6661 python-tagpy python-twisted-bin python-twisted-conch
6662 python-twisted-core python-twisted-web python-utidylib python-webkit
6663 python-xdg python-zope.interface remmina remmina-plugin-data
6664 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6665 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6666 software-center svgalibg1 system-config-printer-udev
6667 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6668 totem totem-coherence totem-mozilla totem-plugins
6669 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6670 zip
6671 &lt;/p&gt;&lt;/blockquote&gt;
6672
6673 Installed using apt-get, removed with aptitude
6674
6675 &lt;blockquote&gt;&lt;p&gt;
6676 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6677 epiphany-extensions epiphany-gecko evolution-exchange
6678 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6679 gedit-common gnome-app-install gnome-games gnome-games-data
6680 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6681 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6682 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6683 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6684 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6685 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6686 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6687 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6688 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6689 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6690 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6691 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6692 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6693 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6694 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6695 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6696 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6697 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6698 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6699 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6700 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6701 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6702 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6703 sound-juicer swfdec-gnome system-config-printer totem-common
6704 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6705 &lt;/p&gt;&lt;/blockquote&gt;
6706
6707 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6708
6709 &lt;blockquote&gt;&lt;p&gt;
6710 gstreamer0.10-gnomevfs
6711 &lt;/p&gt;&lt;/blockquote&gt;
6712
6713 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6714
6715 &lt;blockquote&gt;&lt;p&gt;
6716 [nothing]
6717 &lt;/p&gt;&lt;/blockquote&gt;
6718
6719 &lt;p&gt;This is for KDE:&lt;/p&gt;
6720
6721 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6722
6723 &lt;blockquote&gt;&lt;p&gt;
6724 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6725 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6726 ghostscript-x git gnome-audio gnugo granatier gs-common
6727 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6728 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6729 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6730 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6731 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6732 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6733 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6734 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6735 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6736 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6737 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6738 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6739 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6740 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6741 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6742 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6743 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6744 libkrossui4 libmailtools-perl libmime-tools-perl
6745 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6746 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6747 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6748 lirc luatex marble networkstatus noatun-plugins
6749 openoffice.org-writer2latex palapeli palapeli-data parley
6750 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6751 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6752 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6753 ttf-sazanami-gothic
6754 &lt;/p&gt;&lt;/blockquote&gt;
6755
6756 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6757
6758 &lt;blockquote&gt;&lt;p&gt;
6759 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6760 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6761 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6762 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6763 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6764 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6765 kitchensync kiten kjumpingcube klatin klettres klickety klines
6766 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6767 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6768 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6769 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6770 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6771 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6772 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6773 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6774 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6775 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6776 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6777 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6778 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6779 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6780 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6781 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6782 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6783 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6784 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6785 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6786 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6787 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6788 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6789 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6790 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6791 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6792 &lt;/p&gt;&lt;/blockquote&gt;
6793
6794 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6795
6796 &lt;blockquote&gt;&lt;p&gt;
6797 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6798 kdeartwork kdebase kdebase-apps kdebase-workspace
6799 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6800 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6801 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6802 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6803 xscreensaver-screensaver-bsod
6804 &lt;/p&gt;&lt;/blockquote&gt;
6805
6806 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6807
6808 &lt;blockquote&gt;&lt;p&gt;
6809 kdebase-bin konq-plugins konqueror
6810 &lt;/p&gt;&lt;/blockquote&gt;
6811 </description>
6812 </item>
6813
6814 <item>
6815 <title>Gnash buildbot slave and Debian kfreebsd</title>
6816 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6817 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6818 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6819 <description>&lt;p&gt;Answering
6820 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6821 call from the Gnash project&lt;/a&gt; for
6822 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6823 current source, I have set up a virtual KVM machine on the Debian
6824 Edu/Skolelinux virtualization host to test the git source on
6825 Debian/Squeeze. I hope this can help the developers in getting new
6826 releases out more often.&lt;/p&gt;
6827
6828 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6829 I have considered setting up a &lt;a
6830 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6831 machine as well. I have also considered using the kfreebsd
6832 architecture in Debian as a file server in NUUG to get access to the 5
6833 TB zfs volume we currently use to store DV video. Because of this, I
6834 finally got around to do a test installation of Debian/Squeeze with
6835 kfreebsd. Installation went fairly smooth, thought I noticed some
6836 visual glitches in the cdebconf dialogs (black cursor left on the
6837 screen at random locations). Have not gotten very far with the
6838 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6839 fatal problem. Have to spend some more time on it to see if it is
6840 useful as a file server for NUUG. Will try to find time to set up a
6841 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6842 </description>
6843 </item>
6844
6845 <item>
6846 <title>Debian in 3D</title>
6847 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6848 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6849 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6850 <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;
6851
6852 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6853 3D linked in from
6854 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6855 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6856 </description>
6857 </item>
6858
6859 <item>
6860 <title>Software updates 2010-10-24</title>
6861 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6862 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6863 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6864 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6865
6866 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6867 raise money for the project is going well. The lower limit of 10
6868 signers was reached in 24 hours, and so far 13 people have signed it.
6869 More signers and more funding is most welcome, and I am really curious
6870 how far we can get before the time limit of December 24 is reached.
6871 :)&lt;/p&gt;
6872
6873 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6874 about what appear to be a great code coverage tool capable of
6875 generating code coverage stats without any changes to the source code.
6876 It is called
6877 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6878 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6879 It is missing in Debian, but the git source built just fine in Squeeze
6880 after I installed libelf-dev, libdwarf-dev, pkg-config and
6881 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6882 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6883
6884 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6885 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6886 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6887 alpha test release of the Squeeze based Debian Edu /
6888 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6889 release. Give it a try if you need a complete linux solution for your
6890 school, including central infrastructure server, workstations, thin
6891 client servers and diskless workstations. A nice touch added
6892 yesterday is RDP support on the thin client servers, for windows
6893 clients to get a Linux desktop on request.&lt;/p&gt;
6894 </description>
6895 </item>
6896
6897 <item>
6898 <title>Some notes on Flash in Debian and Debian Edu</title>
6899 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6900 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6901 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6902 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6903 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6904 second most popular used package that is missing in Debian. The sixth
6905 most popular is flashplayer-mozilla. This is a clear indication that
6906 working flash is important for Debian users. Around 10 percent of the
6907 users submitting data to popcon.debian.org have this package
6908 installed.&lt;/p&gt;
6909
6910 &lt;p&gt;In the report written by Lars Risan in August 2008
6911&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
6912 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6913 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6914 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6915 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6916 web sites require Flash to work, and lacking working Flash support in
6917 the web browser and the problems with installing it was perceived as a
6918 good reason to stay with Windows.&lt;/p&gt;
6919
6920 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6921 said to be the retarded cousin that did not really understand
6922 everything you told him but could work fairly well. This was a
6923 comment regarding the problems Linux have with proprietary formats and
6924 non-standard web pages, and is sad because it exposes a fairly common
6925 understanding of whose fault it is if web pages that only work in for
6926 example Internet Explorer 6 fail to work on Firefox, and funny because
6927 it explain very well how annoying it is for users when Linux
6928 distributions do not work with the documents they receive or the web
6929 pages they want to visit.&lt;/p&gt;
6930
6931 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6932 and Debian Edu to have a well working Flash implementation in the
6933 distribution, to get at least popular sites as Youtube and Google
6934 Video to working out of the box. For Squeeze, Debian have the chance
6935 to include the latest version of Gnash that will make this happen, as
6936 the new release 0.8.8 was published a few weeks ago and is resting in
6937 unstable. The new version work with more sites that version 0.8.7.
6938 The Gnash maintainers have asked for a freeze exception, but the
6939 release team have not had time to reply to it yet. I hope they agree
6940 with me that Flash is important for the Debian desktop users, and thus
6941 accept the new package into Squeeze.&lt;/p&gt;
6942 </description>
6943 </item>
6944
6945 <item>
6946 <title>Circular package dependencies harms apt recovery</title>
6947 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6948 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6949 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6950 <description>&lt;p&gt;I discovered this while doing
6951 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6952 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6953 in Debian still got circular dependencies, and it is often claimed
6954 that apt and aptitude should be able to handle this just fine, but
6955 some times these dependency loops causes apt to fail.&lt;/p&gt;
6956
6957 &lt;p&gt;An example is from todays
6958 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6959 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6960 causes perl-modules to fail to upgrade. The cause is simple. If a
6961 package fail to unpack, then only part of packages with the circular
6962 dependency might end up being unpacked when unpacking aborts, and the
6963 ones already unpacked will fail to configure in the recovery phase
6964 because its dependencies are unavailable.&lt;/p&gt;
6965
6966 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6967
6968 &lt;blockquote&gt;&lt;pre&gt;
6969 dpkg: dependency problems prevent configuration of perl-modules:
6970 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6971 Version of perl on system is 5.10.0-19lenny2.
6972 dpkg: error processing perl-modules (--configure):
6973 dependency problems - leaving unconfigured
6974 &lt;/pre&gt;&lt;/blockquote&gt;
6975
6976 &lt;p&gt;The perl/perl-modules circular dependency is already
6977 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6978 hopefully be solved as soon as possible, but it is not the only one,
6979 and each one of these loops in the dependency tree can cause similar
6980 failures. Of course, they only occur when there are bugs in other
6981 packages causing the unpacking to fail, but it is rather nasty when
6982 the failure of one package causes the problem to become worse because
6983 of dependency loops.&lt;/p&gt;
6984
6985 &lt;p&gt;Thanks to
6986 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6987 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6988 dependencies
6989 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6990 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6991
6992 &lt;p&gt;Todays testing also exposed a bug in
6993 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6994 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6995 apt-get and aptitude, the latter possibly caused by some circular
6996 dependency. Reported both to BTS to try to get someone to look at
6997 it.&lt;/p&gt;
6998 </description>
6999 </item>
7000
7001 <item>
7002 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
7003 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
7004 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
7005 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
7006 <description>&lt;p&gt;This is a
7007 &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;
7008 on my
7009 &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
7010 work&lt;/a&gt; on
7011 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
7012 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
7013
7014 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
7015 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7016 and dhcp3-server-ldap in Debian use the LDAP server. The two
7017 implementations are quite different in how they use LDAP.&lt;/p&gt;
7018
7019 To get this information, I started slapd with debugging enabled and
7020 dumped the debug output to a file to get the LDAP searches performed
7021 on a Debian Edu main-server. Here is a summary.
7022
7023 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
7024
7025 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
7026 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
7027 the web.
7028
7029 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
7030 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
7031 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
7032 reverse entries are in two different subtrees in LDAP with a structure
7033 based on the DNS names, as in tjener.intern and
7034 2.2.0.10.in-addr.arpa.&lt;/p&gt;
7035
7036 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
7037 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
7038 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
7039 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
7040 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
7041 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
7042 forward entries, it is looking for attributes named dnsttl, arecord,
7043 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7044 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7045 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7046 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7047 spfrecord and modifytimestamp. For reverse entries it is looking for
7048 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7049 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7050 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7051 ldapsearch commands could look like this:&lt;/p&gt;
7052
7053 &lt;blockquote&gt;&lt;pre&gt;
7054 ldapsearch -h ldap \
7055 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7056 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
7057 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7058 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7059 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7060 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7061
7062 ldapsearch -h ldap \
7063 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7064 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
7065 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7066 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7067 srvrecord naptrrecord modifytimestamp
7068 &lt;/pre&gt;&lt;/blockquote&gt;
7069
7070 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
7071 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7072 example LDAP objects used there. In addition to these objects, the
7073 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7074 also exist.&lt;/p&gt;
7075
7076 &lt;blockquote&gt;&lt;pre&gt;
7077 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7078 objectclass: top
7079 objectclass: dnsdomain
7080 objectclass: domainrelatedobject
7081 dc: tjener
7082 arecord: 10.0.2.2
7083 associateddomain: tjener.intern
7084
7085 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7086 objectclass: top
7087 objectclass: dnsdomain2
7088 objectclass: domainrelatedobject
7089 dc: 2
7090 ptrrecord: tjener.intern
7091 associateddomain: 2.2.0.10.in-addr.arpa
7092 &lt;/pre&gt;&lt;/blockquote&gt;
7093
7094 &lt;p&gt;In strict mode, the server behaves differently. When looking for
7095 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
7096 same base as in the tree mode for a object with filter
7097 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
7098 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7099 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7100 naptrrecord and modifytimestamp. For reverse entires it also do a
7101 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
7102 and the requested attributes are associateddomain, dnsttl and
7103 modifytimestamp. In short, in strict mode the objects with ptrrecord
7104 go away, and the arecord attribute in the forward object is used
7105 instead.&lt;/p&gt;
7106
7107 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
7108 like this:&lt;/p&gt;
7109
7110 &lt;blockquote&gt;&lt;pre&gt;
7111 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7112 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
7113 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7114 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7115 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7116 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7117
7118 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7119 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
7120 &lt;/pre&gt;&lt;/blockquote&gt;
7121
7122 &lt;p&gt;In addition to the forward and reverse searches , there is also a
7123 search for SOA records, which behave similar to the forward and
7124 reverse lookups.&lt;/p&gt;
7125
7126 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
7127 specify any objectclass names, and instead look for the attributes it
7128 need to generate a DNS reply. This make it able to work with any
7129 objectclass that provide the needed attributes.&lt;/p&gt;
7130
7131 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
7132 dnsdomain2 schemas. The latter is used for reverse entries like
7133 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
7134
7135 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
7136 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7137 attributes) and domainrelatedobject (for associatedDomain). The use
7138 of structural object classes make it impossible to combine these
7139 classes with the object classes used by DHCP.&lt;/p&gt;
7140
7141 &lt;p&gt;There are other schemas that could be used too, for example the
7142 dnszone structural object class used by Gosa and bind-sdb for the DNS
7143 attributes combined with the domainrelatedobject object class, but in
7144 this case some unused attributes would have to be included as well
7145 (zonename and relativedomainname).&lt;/p&gt;
7146
7147 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
7148 mode and not use any of the existing objectclasses (dnsdomain,
7149 dnsdomain2 and dnszone) when one want to combine the DNS information
7150 with DHCP information, and instead create a auxiliary object class
7151 defined something like this (using the attributes defined for
7152 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
7153
7154 &lt;blockquote&gt;&lt;pre&gt;
7155 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
7156 SUP top
7157 AUXILIARY
7158 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7159 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7160 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7161 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7162 A6Record $ DNAMERecord
7163 ))
7164 &lt;/pre&gt;&lt;/blockquote&gt;
7165
7166 &lt;p&gt;This will allow any object to become a DNS entry when combined with
7167 the domainrelatedobject object class, and allow any entity to include
7168 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
7169 developers asking for their view on this schema and if they are
7170 interested in providing such schema with PowerDNS, and I hope my
7171 message will be accepted into their mailing list soon.&lt;/p&gt;
7172
7173 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
7174
7175 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
7176 the object attributes, and then uses the attributes it want. This
7177 make it harder to figure out exactly what attributes are used, but
7178 thanks to the working example in Debian Edu I can at least get an idea
7179 what is needed without having to read the source code.&lt;/p&gt;
7180
7181 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
7182 search filter to use to locate the correct dhcpServer entity is
7183 stored. These are the relevant entries from
7184 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
7185
7186 &lt;blockquote&gt;&lt;pre&gt;
7187 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
7188 ldap-dhcp-server-cn &quot;dhcp&quot;;
7189 &lt;/pre&gt;&lt;/blockquote&gt;
7190
7191 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
7192 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
7193 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
7194 search result is this entry:&lt;/p&gt;
7195
7196 &lt;blockquote&gt;&lt;pre&gt;
7197 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7198 cn: dhcp
7199 objectClass: top
7200 objectClass: dhcpServer
7201 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7202 &lt;/pre&gt;&lt;/blockquote&gt;
7203
7204 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
7205 subtree with DHCP configuration. The DHCP configuration subtree base
7206 is located using a base scope search with base &quot;cn=DHCP
7207 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
7208 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
7209 The search result is this entry:&lt;/p&gt;
7210
7211 &lt;blockquote&gt;&lt;pre&gt;
7212 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7213 cn: DHCP Config
7214 objectClass: top
7215 objectClass: dhcpService
7216 objectClass: dhcpOptions
7217 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7218 dhcpStatements: ddns-update-style none
7219 dhcpStatements: authoritative
7220 dhcpOption: smtp-server code 69 = array of ip-address
7221 dhcpOption: www-server code 72 = array of ip-address
7222 dhcpOption: wpad-url code 252 = text
7223 &lt;/pre&gt;&lt;/blockquote&gt;
7224
7225 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
7226 all the DHCP configuration is loaded, it is ready to receive requests.
7227 The subtree in Debian Edu contain objects with object classes
7228 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7229 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7230 and information about netmasks, dynamic range etc. Leaving out the
7231 details here because it is not relevant for the focus of my
7232 investigation, which is to see if it is possible to merge dns and dhcp
7233 related computer objects.&lt;/p&gt;
7234
7235 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
7236 of the client (00:00:00:00:00:00 in this example), using a subtree
7237 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
7238 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7239 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
7240 like:&lt;/p&gt;
7241
7242 &lt;blockquote&gt;&lt;pre&gt;
7243 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7244 cn: hostname
7245 objectClass: top
7246 objectClass: dhcpHost
7247 dhcpHWAddress: ethernet 00:00:00:00:00:00
7248 dhcpStatements: fixed-address hostname
7249 &lt;/pre&gt;&lt;/blockquote&gt;
7250
7251 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
7252 The object classes need to have fixed names, and the configuration
7253 need to be stored in a fairly specific LDAP structure. On the
7254 positive side, the invidiual dhcpHost entires can be anywhere without
7255 the DN pointed to by the dhcpServer entries. The latter should make
7256 it possible to group all host entries in a subtree next to the
7257 configuration entries, and this subtree can also be shared with the
7258 DNS server if the schema proposed above is combined with the dhcpHost
7259 structural object class.
7260
7261 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
7262
7263 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
7264 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
7265 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
7266 allowing DNS objects to be stored anywhere under the base cn specified
7267 in the configuration.&lt;/p&gt;
7268
7269 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
7270 regarding which LDAP schemas to use and which LDAP structure to use.
7271 I guess one could implement ones own schema, as long as the
7272 objectclasses and attributes have the names used, but this do not
7273 really help when the DHCP subtree need to have a fairly fixed
7274 structure.&lt;/p&gt;
7275
7276 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
7277 this might work for Debian Edu:&lt;/p&gt;
7278
7279 &lt;blockquote&gt;&lt;pre&gt;
7280 ou=services
7281 cn=machine-info (dhcpService) - dhcpServiceDN points here
7282 cn=dhcp (dhcpServer)
7283 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7284 cn=10.0.2.0 (dhcpSubnet)
7285 cn=group1 (dhcpGroup/dhcpOptions)
7286 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7287 cn=192.168.0.0 (dhcpSubnet)
7288 cn=group1 (dhcpGroup/dhcpOptions)
7289 ou=machines - PowerDNS base points here
7290 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7291 &lt;/pre&gt;&lt;/blockquote&gt;
7292
7293 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
7294 entries to be in the dhcpGroup subtrees, the entries can be stored
7295 there instead of a common machines subtree, and the PowerDNS base
7296 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
7297
7298 &lt;p&gt;The combined object under the machines subtree would look something
7299 like this:&lt;/p&gt;
7300
7301 &lt;blockquote&gt;&lt;pre&gt;
7302 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7303 dc: hostname
7304 objectClass: top
7305 objectClass: dhcpHost
7306 objectclass: domainrelatedobject
7307 objectclass: dnsDomainAux
7308 associateddomain: hostname.intern
7309 arecord: 10.11.12.13
7310 dhcpHWAddress: ethernet 00:00:00:00:00:00
7311 dhcpStatements: fixed-address hostname.intern
7312 &lt;/pre&gt;&lt;/blockquote&gt;
7313
7314 &lt;/p&gt;One could even add the LTSP configuration associated with a given
7315 machine, as long as the required attributes are available in a
7316 auxiliary object class.&lt;/p&gt;
7317 </description>
7318 </item>
7319
7320 <item>
7321 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
7322 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
7323 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
7324 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
7325 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
7326 DHCP services in Debian Edu to use the same LDAP objects for a given
7327 computer, to avoid the possibility of having a inconsistent state for
7328 a computer in LDAP (as in DHCP but no DNS entry or the other way
7329 around) and make it easier to add computers to LDAP.&lt;/p&gt;
7330
7331 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
7332 information finally found a solution that seem to work.&lt;/p&gt;
7333
7334 &lt;p&gt;The old setup required three LDAP objects for a given computer.
7335 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7336 we switch powerdns to use its strict LDAP method (ldap-method=strict
7337 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7338 merged into one while making it impossible to transfer the reverse map
7339 to a slave DNS server.&lt;/p&gt;
7340
7341 &lt;p&gt;If we also replace the object class used to get the DNS related
7342 attributes to one allowing these attributes to be combined with the
7343 dhcphost object class, we can merge the DNS and DHCP entries into one.
7344 I&#39;ve written such object class in the dnsdomainaux.schema file (need
7345 proper OIDs, but that is a minor issue), and tested the setup. It
7346 seem to work.&lt;/p&gt;
7347
7348 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
7349 for both DNS and DHCP, and even the LTSP configuration I suggested in
7350 an earlier email. The combined LDAP object will look something like
7351 this:&lt;/p&gt;
7352
7353 &lt;blockquote&gt;&lt;pre&gt;
7354 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7355 cn: hostname
7356 objectClass: dhcphost
7357 objectclass: domainrelatedobject
7358 objectclass: dnsdomainaux
7359 associateddomain: hostname.intern
7360 arecord: 10.11.12.13
7361 dhcphwaddress: ethernet 00:00:00:00:00:00
7362 dhcpstatements: fixed-address hostname
7363 ldapconfigsound: Y
7364 &lt;/pre&gt;&lt;/blockquote&gt;
7365
7366 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
7367 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7368 before asking DNS to resolve the fixed-adddress. LTSP will use
7369 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
7370
7371 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
7372 dhcphost in a different location, to allow us to put the objects
7373 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7374 that. If I can&#39;t figure out a way to do that, we can still get rid of
7375 the hosts subtree and move all its content into the DHCP Config tree
7376 (which probably should be renamed to be more related to the new
7377 content. I suspect cn=dnsdhcp,ou=services or something like that
7378 might be a good place to put it.&lt;/p&gt;
7379
7380 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7381 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7382 </description>
7383 </item>
7384
7385 <item>
7386 <title>Idea for storing LTSP configuration in LDAP</title>
7387 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7389 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7390 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7391 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7392 clients, and that this can be used to fetch configuration from LDAP if
7393 Debian Edu choose to store configuration there.&lt;/p&gt;
7394
7395 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7396 to get configuration from LDAP. The idea is to look up the MAC
7397 address of the client in LDAP, and look for attributes on the form
7398 ltspconfigsetting=value, and use this to export SETTING=value to the
7399 LTSP clients.&lt;/p&gt;
7400
7401 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7402 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7403 allowing us to store all information about a computer in one place.&lt;/p&gt;
7404
7405 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7406 this approach. A real LDAP schema for the ltspClientAux objectclass
7407 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7408
7409 &lt;blockquote&gt;&lt;pre&gt;
7410 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7411 #
7412 # Fetch LTSP client settings from LDAP based on MAC address
7413 #
7414 # Uses ethernet address as stored in the dhcpHost objectclass using
7415 # the dhcpHWAddress attribute or ethernet address stored in the
7416 # ieee802Device objectclass with the macAddress attribute.
7417 #
7418 # This module is written to be schema agnostic, and only depend on the
7419 # existence of attribute names.
7420 #
7421 # The LTSP configuration variables are saved directly using a
7422 # ltspConfig prefix and uppercasing the rest of the attribute name.
7423 # To set the SERVER variable, set the ltspConfigServer attribute.
7424 #
7425 # Some LDAP schema should be created with all the relevant
7426 # configuration settings. Something like this should work:
7427 #
7428 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7429 # SUP top
7430 # AUXILIARY
7431 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7432
7433 LDAPSERVER=$(debian-edu-ldapserver)
7434 if [ &quot;$LDAPSERVER&quot; ] ; then
7435 LDAPBASE=$(debian-edu-ldapserver -b)
7436 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7437 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7438 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7439 grep &#39;^ltspConfig&#39; | while read attr value ; do
7440 # Remove prefix and convert to upper case
7441 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7442 # bass value on to clients
7443 eval &quot;$attr=$value; export $attr&quot;
7444 done
7445 done
7446 fi
7447 &lt;/pre&gt;&lt;/blockquote&gt;
7448
7449 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7450 the while block might end up in a subshell causing the variables set
7451 there to not show up in ltsp-config, but if that is the case I am sure
7452 the code can be restructured to make sure the variables are passed on.
7453 I expect that can be solved with some testing. :)&lt;/p&gt;
7454
7455 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7456 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7457
7458 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7459 configuration in LDAP that was created around year 2000 by
7460 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7461 Xperience, Inc., 2000&lt;/a&gt;. I found its
7462 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7463 personal home page over at redhat.com.&lt;/p&gt;
7464 </description>
7465 </item>
7466
7467 <item>
7468 <title>jXplorer, a very nice LDAP GUI</title>
7469 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7470 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7471 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7472 <description>&lt;p&gt;Since
7473 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7474 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7475 LDAP GUI that is even better than luma. The java application
7476 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7477 moving LDAP objects and subtrees using drag-and-drop, and can
7478 authenticate using Kerberos. I have only tested the Kerberos
7479 authentication, but do not have a LDAP setup allowing me to rewrite
7480 LDAP with my test user yet. It is
7481 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7482 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7483 have with it is how it handle errors. If something go wrong, its
7484 non-intuitive behaviour require me to go through some query work list
7485 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7486 </description>
7487 </item>
7488
7489 <item>
7490 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7491 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7492 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7493 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7494 <description>&lt;p&gt;Here is a short update on my &lt;a
7495 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7496 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7497 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7498 not reporting the status for KDE, because the upgrade crashes when
7499 aptitude try because of missing conflicts
7500 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7501 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7502
7503 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7504 complete list of the installed packages. Based on this I see these
7505 differences when I did a test run today. As usual, I do not really
7506 know what the correct set of packages would be, but thought it best to
7507 publish the difference.&lt;/p&gt;
7508
7509 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7510
7511 &lt;blockquote&gt;&lt;p&gt;
7512 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7513 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7514 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7515 libgtksourceview-common libpt-1.10.10-plugins-alsa
7516 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7517 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7518 python-4suite-xml python-eggtrayicon python-gtkhtml2
7519 python-gtkmozembed svgalibg1 xserver-xephyr zip
7520 &lt;/p&gt;&lt;/blockquote&gt;
7521
7522 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7523
7524 &lt;blockquote&gt;&lt;p&gt;
7525 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7526 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7527 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7528 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7529 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7530 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7531 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7532 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7533 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7534 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7535 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7536 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7537 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7538 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7539 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7540 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7541 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7542 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7543 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7544 mysql-common swfdec-gnome totem-gstreamer wodim
7545 &lt;/p&gt;&lt;/blockquote&gt;
7546
7547 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7548
7549 &lt;blockquote&gt;&lt;p&gt;
7550 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7551 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7552 xserver-xorg-input-all xserver-xorg-input-evdev
7553 xserver-xorg-input-kbd xserver-xorg-input-mouse
7554 xserver-xorg-input-synaptics xserver-xorg-video-all
7555 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7556 xserver-xorg-video-chips xserver-xorg-video-cirrus
7557 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7558 xserver-xorg-video-glint xserver-xorg-video-i128
7559 xserver-xorg-video-i740 xserver-xorg-video-mach64
7560 xserver-xorg-video-mga xserver-xorg-video-neomagic
7561 xserver-xorg-video-nouveau xserver-xorg-video-nv
7562 xserver-xorg-video-r128 xserver-xorg-video-radeon
7563 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7564 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7565 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7566 xserver-xorg-video-sis xserver-xorg-video-sisusb
7567 xserver-xorg-video-tdfx xserver-xorg-video-tga
7568 xserver-xorg-video-trident xserver-xorg-video-tseng
7569 xserver-xorg-video-vesa xserver-xorg-video-vmware
7570 xserver-xorg-video-voodoo
7571 &lt;/p&gt;&lt;/blockquote&gt;
7572
7573 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7574
7575 &lt;blockquote&gt;&lt;p&gt;
7576 deskbar-applet xserver-xorg xserver-xorg-core
7577 xserver-xorg-input-wacom xserver-xorg-video-intel
7578 xserver-xorg-video-openchrome
7579 &lt;/p&gt;&lt;/blockquote&gt;
7580
7581 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7582 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7583 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7584 No idea when it hits Squeeze, but when it does I hope it will reduce
7585 the difference somewhat.
7586 </description>
7587 </item>
7588
7589 <item>
7590 <title>LUMA, a very nice LDAP GUI</title>
7591 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7592 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7593 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7594 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7595 directory in Debian Edu, and in the process I started to miss a GUI
7596 tool to browse the LDAP tree. The only one I was able to find in
7597 Debian/Squeeze and Lenny is
7598 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7599 be a great tool to get a overview of the current LDAP directory
7600 populated by default in Skolelinux. Thanks to it, I have been able to
7601 find empty and obsolete subtrees, misplaced objects and duplicate
7602 objects. It will be installed by default in Debian/Squeeze. If you
7603 are working with LDAP, give it a go. :)&lt;/p&gt;
7604
7605 &lt;p&gt;I did notice one problem with it I have not had time to report to
7606 the BTS yet. There is no .desktop file in the package, so the tool do
7607 not show up in the Gnome and KDE menus, but only deep down in in the
7608 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7609 released.&lt;/p&gt;
7610
7611 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7612 like to move objects and remove subtrees directly in the GUI, but have
7613 not found a way to do that with LUMA yet. So in the mean time, I use
7614 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7615
7616 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7617 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7618
7619 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7620 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7621 useful GUI alternative. It seem like a good tool, but is unmaintained
7622 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7623 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7624 </description>
7625 </item>
7626
7627 <item>
7628 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7629 <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>
7630 <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>
7631 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7632 <description>&lt;p&gt;A while back, I
7633 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7634 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7635 for storing DNS and DHCP information in LDAP to combine the two sets
7636 of information into one LDAP object representing a computer.&lt;/p&gt;
7637
7638 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7639 the dhcpHost object class auxiliary, to allow it to be combined with
7640 the dNSDomain object class, and thus forming one object for one
7641 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7642
7643 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7644 without also changing the assigned number for the object class, and I
7645 do not know enough about LDAP schema design to do that properly for
7646 Debian Edu.&lt;/p&gt;
7647
7648 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7649 the
7650 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7651 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7652 available today from IETF.&lt;/p&gt;
7653
7654 &lt;pre&gt;
7655 --- dhcp.schema (revision 65192)
7656 +++ dhcp.schema (working copy)
7657 @@ -376,7 +376,7 @@
7658 objectclass ( 2.16.840.1.113719.1.203.6.6
7659 NAME &#39;dhcpHost&#39;
7660 DESC &#39;This represents information about a particular client&#39;
7661 - SUP top
7662 + SUP top AUXILIARY
7663 MUST cn
7664 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7665 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7666 &lt;/pre&gt;
7667
7668 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7669 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7670 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7671
7672 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7673 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7674 </description>
7675 </item>
7676
7677 <item>
7678 <title>Calling tasksel like the installer, while still getting useful output</title>
7679 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7680 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7681 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7682 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7683 installs packages during the normal debian-installer run. Until now,
7684 I have ended up letting tasksel do the work, with the annoying problem
7685 of not getting any feedback at all when something fails (like a
7686 conffile question from dpkg or a download that fails), using code like
7687 this:
7688
7689 &lt;blockquote&gt;&lt;pre&gt;
7690 export DEBIAN_FRONTEND=noninteractive
7691 tasksel --new-install
7692 &lt;/pre&gt;&lt;/blockquote&gt;
7693
7694 This would invoke tasksel, let its automatic task selection pick the
7695 tasks to install, and continue to install the requested tasks without
7696 any output what so ever.
7697
7698 Recently I revisited this problem while working on the automatic
7699 package upgrade testing, because tasksel would some times hang without
7700 any useful feedback, and I want to see what is going on when it
7701 happen. Then it occured to me, I can parse the output from tasksel
7702 when asked to run in test mode, and use that aptitude command line
7703 printed by tasksel then to simulate the tasksel run. I ended up using
7704 code like this:
7705
7706 &lt;blockquote&gt;&lt;pre&gt;
7707 export DEBIAN_FRONTEND=noninteractive
7708 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7709 $cmd
7710 &lt;/pre&gt;&lt;/blockquote&gt;
7711
7712 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7713 --without-recommends -o APT::Install-Recommends=no -y install
7714 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7715 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7716 laptop task and all packages with priority standard , required and
7717 important, just like tasksel would have done it during
7718 installation.&lt;/p&gt;
7719
7720 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7721 install packages without using debconf-apt-progress, for use cases
7722 like this.&lt;/p&gt;
7723 </description>
7724 </item>
7725
7726 <item>
7727 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7728 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7730 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7731 <description>&lt;p&gt;My
7732 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7733 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7734 finally made the upgrade logs available from
7735 &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;.
7736 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7737 apt and aptitude, and found their differences interesting. This time
7738 I will only focus on their removal plans.&lt;/p&gt;
7739
7740 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7741 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7742 surprising part is that it want to remove xorg and all
7743 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7744 sure why. When asking aptitude to do the same, it want to remove 129
7745 packages, but most of them are library packages I suspect are no
7746 longer needed. Both of them want to remove bluetooth packages, which
7747 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7748
7749 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7750 which seem like a bad idea and xorg the same way as with Gnome. Asking
7751 aptitude for the same, it wants to remove 192 packages, none which are
7752 too surprising.&lt;/p&gt;
7753
7754 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7755 and avoided, and perhaps others as well. Here are the complete list
7756 of planned removals. The complete logs is available from the URL
7757 above. Note if you want to repeat these tests, that the upgrade test
7758 for kde+apt-get hung in the tasksel setup because of dpkg asking
7759 conffile questions. No idea why. I worked around it by using
7760 &#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
7761 continue.&lt;/p&gt;
7762
7763 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7764 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7765 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7766 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7767 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7768 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7769 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7770 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7771 xserver-xorg-input-kbd xserver-xorg-input-mouse
7772 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7773 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7774 xserver-xorg-video-ati xserver-xorg-video-chips
7775 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7776 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7777 xserver-xorg-video-glint xserver-xorg-video-i128
7778 xserver-xorg-video-i740 xserver-xorg-video-imstt
7779 xserver-xorg-video-intel xserver-xorg-video-mach64
7780 xserver-xorg-video-mga xserver-xorg-video-neomagic
7781 xserver-xorg-video-nsc xserver-xorg-video-nv
7782 xserver-xorg-video-openchrome xserver-xorg-video-r128
7783 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7784 xserver-xorg-video-rendition xserver-xorg-video-s3
7785 xserver-xorg-video-s3virge xserver-xorg-video-savage
7786 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7787 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7788 xserver-xorg-video-tga xserver-xorg-video-trident
7789 xserver-xorg-video-tseng xserver-xorg-video-v4l
7790 xserver-xorg-video-vesa xserver-xorg-video-vga
7791 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7792 xulrunner-1.9-gnome-support&lt;/p&gt;
7793
7794 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7795
7796 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7797 djvulibre-desktop finger gnome-app-install gnome-mount
7798 gnome-network-admin gnome-spell gnome-vfs-obexftp
7799 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7800 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7801 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7802 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7803 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7804 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7805 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7806 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7807 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7808 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7809 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7810 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7811 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7812 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7813 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7814 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7815 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7816 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7817 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7818 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7819 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7820 openoffice.org-writer2latex openssl-blacklist p7zip
7821 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7822 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7823 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7824 swfdec-mozilla totem-gstreamer update-manager wodim
7825 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7826 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7827 zip&lt;/p&gt;
7828
7829 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7830
7831 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7832 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7833 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7834 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7835 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7836 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7837 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7838 xserver-xorg-input-kbd xserver-xorg-input-mouse
7839 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7840 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7841 xserver-xorg-video-ati xserver-xorg-video-chips
7842 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7843 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7844 xserver-xorg-video-glint xserver-xorg-video-i128
7845 xserver-xorg-video-i740 xserver-xorg-video-imstt
7846 xserver-xorg-video-intel xserver-xorg-video-mach64
7847 xserver-xorg-video-mga xserver-xorg-video-neomagic
7848 xserver-xorg-video-nsc xserver-xorg-video-nv
7849 xserver-xorg-video-openchrome xserver-xorg-video-r128
7850 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7851 xserver-xorg-video-rendition xserver-xorg-video-s3
7852 xserver-xorg-video-s3virge xserver-xorg-video-savage
7853 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7854 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7855 xserver-xorg-video-tga xserver-xorg-video-trident
7856 xserver-xorg-video-tseng xserver-xorg-video-v4l
7857 xserver-xorg-video-vesa xserver-xorg-video-vga
7858 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7859
7860 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7861 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7862 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7863 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7864 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7865 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7866 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7867 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7868 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7869 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7870 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7871 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7872 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7873 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7874 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7875 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7876 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7877 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7878 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7879 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7880 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7881 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7882 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7883 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7884 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7885 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7886 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7887 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7888 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7889 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7890 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7891 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7892 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7893 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7894 texlive-common texlive-doc-base texlive-fonts-recommended
7895 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7896 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7897 xulrunner-1.9&lt;/p&gt;
7898
7899 </description>
7900 </item>
7901
7902 <item>
7903 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7904 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7905 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7906 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7907 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7908 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7909 have been discovered and reported in the process
7910 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7911 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7912 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7913 kdebase-workspace-data), and to get a more regular testing going on, I
7914 am working on a script to automate the test.&lt;/p&gt;
7915
7916 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7917 Gnome or KDE desktop installation inside the chroot before upgrading
7918 it. To ensure no services are started in the chroot, a policy-rc.d
7919 script is inserted. To make sure tasksel believe it is to install a
7920 desktop on a laptop, the tasksel tests are replaced in the chroot
7921 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7922
7923 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7924 currently always fail because udev refuses to upgrade with the kernel
7925 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7926 is created. The bug report
7927 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7928 this problem do not trigger in a chroot, but I touch the file anyway
7929 to make sure the upgrade go well. Testing on virtual and real
7930 hardware have failed me because of udev so far, and creating this file
7931 do the trick in such settings anyway. This is a
7932 &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
7933 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7934 maintainer because he lack the resources to rewrite udev to keep
7935 working with old kernels or something like that. I really wish the
7936 udev upstream would keep udev backwards compatible, to avoid such
7937 upgrade problem, but given that they fail to do so, I guess
7938 documenting the way out of this mess is the best option we got for
7939 Debian Squeeze.&lt;/p&gt;
7940
7941 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7942 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7943 trick:&lt;/p&gt;
7944
7945 &lt;blockquote&gt;&lt;pre&gt;
7946 #!/bin/sh
7947 set -ex
7948
7949 if [ &quot;$1&quot; ] ; then
7950 desktop=$1
7951 else
7952 desktop=gnome
7953 fi
7954
7955 from=lenny
7956 to=squeeze
7957
7958 exec &amp;lt; /dev/null
7959 unset LANG
7960 mirror=http://ftp.skolelinux.org/debian
7961 tmpdir=chroot-$from-upgrade-$to-$desktop
7962 fuser -mv .
7963 debootstrap $from $tmpdir $mirror
7964 chroot $tmpdir aptitude update
7965 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7966 #!/bin/sh
7967 exit 101
7968 EOF
7969 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7970 exit_cleanup() {
7971 umount $tmpdir/proc
7972 }
7973 mount -t proc proc $tmpdir/proc
7974 # Make sure proc is unmounted also on failure
7975 trap exit_cleanup EXIT INT
7976
7977 chroot $tmpdir aptitude -y install debconf-utils
7978
7979 # Make sure tasksel autoselection trigger. It need the test scripts
7980 # to return the correct answers.
7981 echo tasksel tasksel/desktop multiselect $desktop | \
7982 chroot $tmpdir debconf-set-selections
7983
7984 # Include the desktop and laptop task
7985 for test in desktop laptop ; do
7986 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7987 #!/bin/sh
7988 exit 2
7989 EOF
7990 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7991 done
7992
7993 DEBIAN_FRONTEND=noninteractive
7994 DEBIAN_PRIORITY=critical
7995 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7996 chroot $tmpdir tasksel --new-install
7997
7998 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7999 chroot $tmpdir aptitude update
8000 touch $tmpdir/etc/udev/kernel-upgrade
8001 chroot $tmpdir aptitude -y dist-upgrade
8002 fuser -mv
8003 &lt;/pre&gt;&lt;/blockquote&gt;
8004
8005 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
8006 with aptitude, but I have not had time to look at how they behave
8007 differently so far. I hope to get a cron job running to do the test
8008 regularly and post the result on the web. The Gnome upgrade currently
8009 work, while the KDE upgrade fail because of the bug in
8010 kdebase-workspace-data&lt;/p&gt;
8011
8012 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
8013 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
8014 post, so I will refrain from trying. I can report that for Gnome,
8015 aptitude report 760 packages upgraded, 448 newly installed, 129 to
8016 remove and 1 not upgraded and 1024MB need to be downloaded while for
8017 KDE the same numbers are 702 packages upgraded, 507 newly installed,
8018 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
8019
8020 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
8021 is able to migrate to dependency based boot sequencing and parallel
8022 booting without a hitch. Was unsure if there were still bugs with
8023 packages failing to clean up their obsolete init.d script during
8024 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8025 packages.&lt;/p&gt;
8026 </description>
8027 </item>
8028
8029 <item>
8030 <title>Upstart or sysvinit - as init.d scripts see it</title>
8031 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
8032 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
8033 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
8034 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
8035 scripts to migrate (some of) their operations to upstart job while
8036 keeping the init.d for hurd and kfreebsd. The packages with such
8037 needs will need a way to get their init.d scripts to behave
8038 differently when used with sysvinit and with upstart. Because of
8039 this, I had a look at the environment variables set when a init.d
8040 script is running under upstart, and when it is not.&lt;/p&gt;
8041
8042 &lt;p&gt;With upstart, I notice these environment variables are set when a
8043 script is started from rcS.d/ (ignoring some irrelevant ones like
8044 COLUMNS):&lt;/p&gt;
8045
8046 &lt;blockquote&gt;&lt;pre&gt;
8047 DEFAULT_RUNLEVEL=2
8048 previous=N
8049 PREVLEVEL=
8050 RUNLEVEL=
8051 runlevel=S
8052 UPSTART_EVENTS=startup
8053 UPSTART_INSTANCE=
8054 UPSTART_JOB=rc-sysinit
8055 &lt;/pre&gt;&lt;/blockquote&gt;
8056
8057 &lt;p&gt;With sysvinit, these environment variables are set for the same
8058 script.&lt;/p&gt;
8059
8060 &lt;blockquote&gt;&lt;pre&gt;
8061 INIT_VERSION=sysvinit-2.88
8062 previous=N
8063 PREVLEVEL=N
8064 RUNLEVEL=S
8065 runlevel=S
8066 &lt;/pre&gt;&lt;/blockquote&gt;
8067
8068 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
8069 sysvinit are not set by upstart. Not sure if it is intentional or not
8070 to not be compatible with sysvinit in this regard.&lt;/p&gt;
8071
8072 &lt;p&gt;For scripts needing to behave differently when upstart is used,
8073 looking for the UPSTART_JOB environment variable seem to be a good
8074 choice.&lt;/p&gt;
8075 </description>
8076 </item>
8077
8078 <item>
8079 <title>A manual for standards wars...</title>
8080 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
8081 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
8082 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
8083 <description>&lt;p&gt;Via the
8084 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
8085 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
8086 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
8087 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
8088 following the standards wars of today.&lt;/p&gt;
8089 </description>
8090 </item>
8091
8092 <item>
8093 <title>Sitesummary tip: Listing computer hardware models used at site</title>
8094 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
8095 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
8096 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
8097 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
8098 to get a list of the machine types in use thanks to the DMI
8099 information extracted from each machine. The script to do so is
8100 included in the sitesummary package, and here is example output from
8101 the Skolelinux build servers:&lt;/p&gt;
8102
8103 &lt;blockquote&gt;&lt;pre&gt;
8104 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8105 vendor count
8106 Dell Computer Corporation 1
8107 PowerEdge 1750 1
8108 IBM 1
8109 eserver xSeries 345 -[8670M1X]- 1
8110 Intel 2
8111 [no-dmi-info] 3
8112 maintainer:~#
8113 &lt;/pre&gt;&lt;/blockquote&gt;
8114
8115 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
8116 provided in each machine. Here there are Intel machines without model
8117 information listed with Intel as vendor and no model, and virtual Xen
8118 machines listed as [no-dmi-info]. One can add -l as a command line
8119 option to list the individual machines.&lt;/p&gt;
8120
8121 &lt;p&gt;A larger list is
8122 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
8123 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
8124 provide the basic sitesummary report publicly. In their report there
8125 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
8126 their machines, and as sitesummary is available in both distributions,
8127 it is trivial to get all of them to report to the same central
8128 collector.&lt;/p&gt;
8129 </description>
8130 </item>
8131
8132 <item>
8133 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
8134 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
8135 <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>
8136 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
8137 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
8138 start at boot when an NVidia video card is used is handled. The
8139 problem seem to be that the nvidia X.org driver uses a long time to
8140 initialize, and this duration is longer than kdm is configured to
8141 wait.&lt;/p&gt;
8142
8143 &lt;p&gt;I came across two bugs related to this issue,
8144 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
8145 against initscripts and passed on to nvidia-glx when it became obvious
8146 that the nvidia drivers were involved, and
8147 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
8148 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
8149
8150 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
8151 problem nvidia video card owners experience and make sure the Debian
8152 distribution work out of the box for these users. The nvidia driver
8153 maintainers expect kdm to be set up to wait longer, while kdm expect
8154 the nvidia driver maintainers to fix the driver to start faster, and
8155 while they wait for each other I guess the users end up switching to a
8156 distribution that work for them. I have no idea what the solution is,
8157 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
8158
8159 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
8160 </description>
8161 </item>
8162
8163 <item>
8164 <title>Parallellized boot seem to hold up well in Debian/testing</title>
8165 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
8166 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
8167 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
8168 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
8169 The feature seem to hold up pretty well, but three fairly serious
8170 issues are known and should be solved:
8171
8172 &lt;p&gt;&lt;ul&gt;
8173
8174 &lt;li&gt;The wicd package seen to
8175 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
8176 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
8177 parallel booting is enabled. No idea why, but the wicd maintainer
8178 seem to be on the case.&lt;/li&gt;
8179
8180 &lt;li&gt;The nvidia X driver seem to
8181 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
8182 triggered more easily when parallel booting is in effect. The
8183 maintainer is on the case.&lt;/li&gt;
8184
8185 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
8186 sequencing (the shutdown is broken) when old file-rc users
8187 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
8188 sysv-rc. One way to solve it would be for file-rc to create
8189 /etc/init.d/.legacy-bootordering, and another is to try to make
8190 sysv-rc more robust. Will investigate some more and probably upload a
8191 workaround in sysv-rc to help those trying to move from file-rc to
8192 sysv-rc get a working shutdown.&lt;/li&gt;
8193
8194 &lt;/ul&gt;&lt;/p&gt;
8195
8196 &lt;p&gt;All in all not many surprising issues, and all of them seem
8197 solvable before Squeeze is released. In addition to these there are
8198 some packages with bugs in their dependencies and run level settings,
8199 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
8200
8201 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8202 the BTS, please usertag the report to get it to show up at
8203 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8204 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8205
8206 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
8207 </description>
8208 </item>
8209
8210 <item>
8211 <title>More flexible firmware handling in debian-installer</title>
8212 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
8213 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
8214 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
8215 <description>&lt;p&gt;After a long break from debian-installer development, I finally
8216 found time today to return to the project. Having to spend less time
8217 working dependency based boot in debian, as it is almost complete now,
8218 definitely helped freeing some time.&lt;/p&gt;
8219
8220 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
8221 include some firmware packages on the Debian Edu CDs, those needed to
8222 get disk and network controllers working. Without having these
8223 firmware packages available during installation, it is impossible to
8224 install Debian Edu on the given machine, and because our target group
8225 are non-technical people, asking them to provide firmware packages on
8226 an external medium is a support pain. Initially, I expected it to be
8227 enough to include the firmware packages on the CD to get
8228 debian-installer to find and use them. This proved to be wrong.
8229 Next, I hoped it was enough to symlink the relevant firmware packages
8230 to some useful location on the CD (tried /cdrom/ and
8231 /cdrom/firmware/). This also proved to not work, and at this point I
8232 found time to look at the debian-installer code to figure out what was
8233 going to work.&lt;/p&gt;
8234
8235 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
8236 look revealed that it would only look for firmware packages outside
8237 the installation media, so the CD was never checked for firmware
8238 packages. It would only check USB sticks, floppies and other
8239 &quot;external&quot; media devices. Today I changed it to also look in the
8240 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8241 solve the problem I ran into with Debian edu. I also changed it to
8242 look in /firmware/, to make sure the installer also find firmware
8243 provided in the initrd when booting the installer via PXE, to allow us
8244 to provide the same feature in the PXE setup included in Debian
8245 Edu.&lt;/p&gt;
8246
8247 &lt;p&gt;To make sure firmware deb packages with a license questions are not
8248 activated without asking if the license is accepted, I extended
8249 hw-detect to look for preinst scripts in the firmware packages, and
8250 run these before activating the firmware during installation. The
8251 license question is asked using debconf in the preinst, so this should
8252 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
8253
8254 &lt;p&gt;If you want to discuss the details of these features, please
8255 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
8256 </description>
8257 </item>
8258
8259 <item>
8260 <title>Parallellized boot is now the default in Debian/unstable</title>
8261 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
8262 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
8263 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
8264 <description>&lt;p&gt;Since this evening, parallel booting is the default in
8265 Debian/unstable for machines using dependency based boot sequencing.
8266 Apparently the testing of concurrent booting has been wider than
8267 expected, if I am to believe the
8268 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8269 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
8270 with the feature this weekend, to give us some time to detect any
8271 remaining problems before Squeeze is frozen. If serious problems are
8272 detected, it is simple to change the default back to sequential boot.
8273 The upload of the new sysvinit package also activate a new upstream
8274 version.&lt;/p&gt;
8275
8276 More information about
8277 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8278 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
8279 currently possible to disable parallel booting when one run into
8280 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
8281
8282 &lt;blockquote&gt;&lt;pre&gt;
8283 CONCURRENCY=none
8284 &lt;/pre&gt;&lt;/blockquote&gt;
8285
8286 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8287 the BTS, please usertag the report to get it to show up at
8288 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8289 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8290 </description>
8291 </item>
8292
8293 <item>
8294 <title>Sitesummary tip: Listing MAC address of all clients</title>
8295 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
8296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
8297 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
8298 <description>&lt;p&gt;In the recent Debian Edu versions, the
8299 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
8300 system&lt;/a&gt; is used to keep track of the machines in the school
8301 network. Each machine will automatically report its status to the
8302 central server after boot and once per night. The network setup is
8303 also reported, and using this information it is possible to get the
8304 MAC address of all network interfaces in the machines. This is useful
8305 to update the DHCP configuration.&lt;/p&gt;
8306
8307 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
8308 ist all MAC addresses of all machines reporting to sitesummary. Run
8309 this on the collector host:&lt;/p&gt;
8310
8311 &lt;blockquote&gt;&lt;pre&gt;
8312 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
8313 &lt;/pre&gt;&lt;/blockquote&gt;
8314
8315 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
8316 line per machine and with space between the MAC addresses.&lt;/p&gt;
8317
8318 &lt;p&gt;To allow system administrators easier job at adding static DHCP
8319 addresses for hosts, it would be possible to extend this to fetch
8320 machine information from sitesummary and update the DHCP and DNS
8321 tables in LDAP using this information. Such tool is unfortunately not
8322 written yet.&lt;/p&gt;
8323 </description>
8324 </item>
8325
8326 <item>
8327 <title>systemd, an interesting alternative to upstart</title>
8328 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
8329 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
8330 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
8331 <description>&lt;p&gt;The last few days a new boot system called
8332 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
8333 has been
8334 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
8335
8336 to the free software world. I have not yet had time to play around
8337 with it, but it seem to be a very interesting alternative to
8338 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
8339 a good alternative for Debian when we are able to switch to an event
8340 based boot system. Tollef is
8341 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
8342 systemd into Debian, and I look forward to seeing how well it work. I
8343 like the fact that systemd handles init.d scripts with dependency
8344 information natively, allowing them to run in parallel where upstart
8345 at the moment do not.&lt;/p&gt;
8346
8347 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
8348 platform support. It only work on recent Linux kernels, and also need
8349 some new kernel features enabled to function properly. This means
8350 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8351 system. Not sure how that will be handled if systemd proves to be the
8352 way forward.&lt;/p&gt;
8353
8354 &lt;p&gt;In the mean time, based on the
8355 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8356 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
8357 decided to enable full parallel booting as the default in Debian as
8358 soon as possible (probably this weekend or early next week), to see if
8359 there are any remaining serious bugs in the init.d dependencies. A
8360 new version of the sysvinit package implementing this change is
8361 already in experimental. If all go well, Squeeze will be released
8362 with parallel booting enabled by default.&lt;/p&gt;
8363 </description>
8364 </item>
8365
8366 <item>
8367 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
8368 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
8369 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
8370 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
8371 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
8372 complete, so complete that it is actually possible to run all the
8373 init.d scripts in parallell based on these dependencies. If you want
8374 to test your Squeeze system, make sure
8375 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8376 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8377 /etc/default/rcS:&lt;/p&gt;
8378
8379 &lt;blockquote&gt;&lt;pre&gt;
8380 CONCURRENCY=makefile
8381 &lt;/pre&gt;&lt;/blockquote&gt;
8382
8383 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8384 scripts in parallel using the dependency information stored in
8385 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8386 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8387 to try to start the kdm and gdm scripts as early as possible, and will
8388 start the facilities required by kdm or gdm as early as possible to
8389 make this happen.&lt;/p&gt;
8390
8391 &lt;p&gt;Give it a try, and see if you like the result. If some services
8392 fail to start properly, it is most likely because they have incomplete
8393 init.d script dependencies in their startup script (or some of their
8394 dependent scripts have incomplete dependencies). Report bugs and get
8395 the package maintainers to fix it. :)&lt;/p&gt;
8396
8397 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8398 manage to get the init.d script dependencies complete and correct. I
8399 expect we will get there in Squeeze+1, if we get manage to test and
8400 fix the remaining issues.&lt;/p&gt;
8401
8402 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8403 the BTS, please usertag the report to get it to show up at
8404 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8405 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8406 </description>
8407 </item>
8408
8409 <item>
8410 <title>Debian has switched to dependency based boot sequencing</title>
8411 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8412 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8413 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8414 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8415 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8416 have been migrated to using dependency based boot sequencing. This
8417 conclude work me and others have been doing for the last three days.
8418 It feels great to see this finally part of the default Debian
8419 installation. Now we just need to weed out the last few problems that
8420 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8421
8422 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8423 fixing the more fundamental problem of handing the event based
8424 non-predictable kernel in the early boot.&lt;/p&gt;
8425 </description>
8426 </item>
8427
8428 <item>
8429 <title>Taking over sysvinit development</title>
8430 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8431 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8432 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8433 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8434 the existing sysvinit upstream developer, I decided a few weeks ago to
8435 take over the package and become the new upstream. The number of
8436 patches to track for the Debian package was becoming a burden, and the
8437 lack of synchronization between the distribution made it hard to keep
8438 the package up to date.&lt;/p&gt;
8439
8440 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8441 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8442 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8443 and Fedora), based on the patches currently in use in these
8444 distributions. We Debian maintainers plan to move to this tarball as
8445 the new upstream as soon as we find time to do the merge. Since the
8446 new tarball was created, we agreed with Werner at SuSe to make a new
8447 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8448 development there. The project is registered and currently waiting
8449 for approval by the Savannah administrators, and as soon as it is
8450 approved, we will import the old versions from svn and continue
8451 working on the future release.&lt;/p&gt;
8452
8453 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8454 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8455 </description>
8456 </item>
8457
8458 <item>
8459 <title>Debian boots quicker and quicker</title>
8460 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8461 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8462 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8463 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8464 people involved in the boot system on Debian and Ubuntu, to see if we
8465 could find more ways to speed up the boot system. This was an Ubuntu
8466 funded
8467 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8468 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8469 of boot systems, and ways to handle the increasing number of boot
8470 issues introduced by the Linux kernel becoming more and more
8471 asynchronous and event base. The Ubuntu approach using udev and
8472 upstart might be a good way forward. Time will show.&lt;/p&gt;
8473
8474 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8475 process in Debian. All of these should be applied to get a quick
8476 boot:&lt;/p&gt;
8477
8478 &lt;ul&gt;
8479
8480 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8481
8482 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8483 clock is in UTC.&lt;/li&gt;
8484
8485 &lt;li&gt;Install and activate the insserv package to enable
8486 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8487 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8488
8489 &lt;/ul&gt;
8490
8491 These points are based on the Google summer of code work done by
8492 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8493 Villegas&lt;/a&gt;.
8494
8495 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8496 unstable yesterday. When we tested it, we were able to cut 6 seconds
8497 from the boot sequence. It depend on very correct dependency
8498 declaration in all init.d scripts, so I expect us to find edge cases
8499 where the dependences in some scripts are slightly wrong when we start
8500 using this.&lt;/p&gt;
8501
8502 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8503 introduced by Raphael Geissert today, one that could affect the
8504 startup speed as well. Instead of starting some scripts concurrently
8505 from rcS.d/ and another set of scripts from rc2.d/, it would be
8506 possible to run a of them in the same process. A quick way to test
8507 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8508 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8509 </description>
8510 </item>
8511
8512 <item>
8513 <title>BSAs påstander om piratkopiering møter motstand</title>
8514 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8516 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8517 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8518 programvareselskapene som Microsoft og Apple, publisert en rapport der
8519 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8520 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8521 dager siden kom
8522 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8523 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8524 dagene. Et spesielt interessant kommentar fra Sverige,
8525 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8526 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8527
8528 &lt;blockquote&gt;
8529 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8530 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8531 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8532 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8533 &lt;/blockquote&gt;
8534
8535 &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
8536 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8537 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8538 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8539 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8540
8541 &lt;p&gt;Fant lenkene via &lt;a
8542 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8543 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8544 </description>
8545 </item>
8546
8547 <item>
8548 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8549 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8550 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8551 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8552 <description>&lt;p&gt;Kom over
8553 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8554 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8555 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8556 jobber til daglig. En rask opptelling forteller meg at vi har 490
8557 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8558 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8559 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8560 </description>
8561 </item>
8562
8563 <item>
8564 <title>Kryptert harddisk - naturligvis</title>
8565 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8566 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8567 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8568 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8569 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8570 når en tar tap av arbeidstid, fortrolige dokumenter,
8571 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8572 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8573 til at jeg har kryptert harddisken på både kontormaskinen og min
8574 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8575 komme på avveie, den første informasjon relatert til jobben min ved
8576 Universitetet i Oslo, og den andre relatert til blant annet
8577 foreningsarbeide. Kryptering av diskene gjør at det er lite
8578 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8579 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8580 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8581 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8582 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8583 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8584 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8585 det er gjort slik jeg gjør det er minimale, og gevinstene er
8586 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8587 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8588
8589 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8590 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8591 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8592 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8593 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8594 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8595 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8596 betydelige.&lt;/p&gt;
8597 </description>
8598 </item>
8599
8600 <item>
8601 <title>Two projects that have improved the quality of free software a lot</title>
8602 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8603 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8604 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8605 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8606 quality of free software, and I wanted to mention both in case someone
8607 do not yet know them.&lt;/p&gt;
8608
8609 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8610 tool to detect and expose errors in the memory handling of programs.
8611 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8612 and it will report any problems on stdout. It is even better if the
8613 program include debug information. With debug information, it is able
8614 to report the source file name and line number where the problem
8615 occurs. It can report things like &#39;reading past memory block in file
8616 X line N, the memory block was allocated in file Y, line M&#39;, and
8617 &#39;using uninitialised value in control logic&#39;. This tool has made it
8618 trivial to investigate reproducible crash bugs in programs, and have
8619 reduced the number of this kind of bugs in free software a lot.
8620
8621 &lt;p&gt;The second one is
8622 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8623 a source code checker. It is able to process the source of a program
8624 and find problems in the logic without running the program. It
8625 started out as the Stanford Checker and became well known when it was
8626 used to find bugs in the Linux kernel. It is now a commercial tool
8627 and the company behind it is running
8628 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8629 free software community, where a lot of free software projects get
8630 their source checked for free. Several thousand defects have been
8631 found and fixed so far. It can find errors like &#39;lock L taken in file
8632 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8633 Y lines O to P can never be executed&#39;. The projects included in the
8634 community service project have managed to get rid of a lot of
8635 reliability problems thanks to Coverity.&lt;/p&gt;
8636
8637 &lt;p&gt;I believe tools like this, that are able to automatically find
8638 errors in the source, are vital to improve the quality of software and
8639 make sure we can get rid of the crashing and failing software we are
8640 surrounded by today.&lt;/p&gt;
8641 </description>
8642 </item>
8643
8644 <item>
8645 <title>No patch is not better than a useless patch</title>
8646 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8647 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8648 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8649 <description>&lt;p&gt;Julien Blache
8650 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8651 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8652 patch allow one to discuss a concrete and proposed solution, and also
8653 prove that the issue at hand is important enough for someone to spent
8654 time on fixing it. No patch do not provide any of these positive
8655 properties.&lt;/p&gt;
8656 </description>
8657 </item>
8658
8659 <item>
8660 <title>Standardize on protocols and formats, not vendors and applications</title>
8661 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8662 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8663 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8664 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8665 very good one to form a long lived computer infrastructure. It is the
8666 simple one, lost by many in todays computer industry: Standardize on
8667 open network protocols and open exchange/storage formats, not applications.
8668 Applications come and go, while protocols and files tend to stay, and
8669 thus one want to make it easy to change application and vendor, while
8670 avoiding conversion costs and locking users to a specific platform or
8671 application.&lt;/p&gt;
8672
8673 &lt;p&gt;This approach make it possible to replace the client applications
8674 independently of the server applications. One can even allow users to
8675 use several different applications as long as they handle the selected
8676 protocol and format. In the normal case, only one client application
8677 is recommended and users only get help if they choose to use this
8678 application, but those that want to deviate from the easy path are not
8679 blocked from doing so.&lt;/p&gt;
8680
8681 &lt;p&gt;It also allow us to replace the server side without forcing the
8682 users to replace their applications, and thus allow us to select the
8683 best server implementation at any moment, when scale and resouce
8684 requirements change.&lt;/p&gt;
8685
8686 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8687 open formats, but I would never recommend standardizing on a single
8688 application that do not use open network protocol or open formats.&lt;/p&gt;
8689 </description>
8690 </item>
8691
8692 <item>
8693 <title>Returning from Skolelinux developer gathering</title>
8694 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8695 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8696 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8697 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8698 Edu/Skolelinux development gathering. I got a bit done tuning the
8699 desktop, and looked into the dynamic service location protocol
8700 implementation avahi. It look like it could be useful for us. Almost
8701 30 people participated, and I believe it was a great environment to
8702 get to know the Skolelinux system. Walter Bender, involved in the
8703 development of the Sugar educational platform, presented his stuff and
8704 also helped me improve my OLPC installation. He also showed me that
8705 his Turtle Art application can be used in standalone mode, and we
8706 agreed that I would help getting it packaged for Debian. As a
8707 standalone application it would be great for Debian Edu. We also
8708 tried to get the video conferencing working with two OLPCs, but that
8709 proved to be too hard for us. The application seem to need more work
8710 before it is ready for me. I look forward to getting home and relax
8711 now. :)&lt;/p&gt;
8712 </description>
8713 </item>
8714
8715 <item>
8716 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8717 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8718 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8719 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8720 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8721 optimal. There is RFC 2307 documenting one way to store NIS maps in
8722 LDAP, and a modified version of this normally called RFC 2307bis, with
8723 some modifications to be compatible with Active Directory. The RFC
8724 specification handle the content of a lot of system databases, but do
8725 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8726
8727 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8728 we would like to store information about users, SMB clients/hosts,
8729 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8730 and LTSP configuration in LDAP. These objects have a lot in common,
8731 but with the current LDAP schemas it is not possible to have one
8732 object per entity. For example, one need to have at least three LDAP
8733 objects for a given computer, one with the SMB related stuff, one with
8734 DNS information and another with DHCP information. The schemas
8735 provided for DNS and DHCP are impossible to combine into one LDAP
8736 object. In addition, it is impossible to implement quick queries for
8737 netgroup membership, because of the way NIS triples are implemented.
8738 It just do not scale. I believe it is time for a few RFC
8739 specifications to cleam up this mess.&lt;/p&gt;
8740
8741 &lt;p&gt;I would like to have one LDAP object representing each computer in
8742 the network, and this object can then keep the SMB (ie host key), DHCP
8743 (mac address/name) and DNS (name/IP address) settings in one place.
8744 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8745
8746 &lt;p&gt;I would also like to have a quick way to map from a user or
8747 computer and to the net group this user or computer is a member.&lt;/p&gt;
8748
8749 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8750 in this regard, and the unix side need to catch up. Time to start a
8751 new IETF work group?&lt;/p&gt;
8752 </description>
8753 </item>
8754
8755 <item>
8756 <title>Endelig er Debian Lenny gitt ut</title>
8757 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8758 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8759 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8760 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8761 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8762 Et langt steg videre for Debian-prosjektet, og en rekke nye
8763 programpakker blir nå tilgjengelig for de av oss som bruker den
8764 stabile utgaven av Debian. Neste steg er nå å få
8765 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8766 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8767 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8768 slippes løs på skolene. Takk til alle debian-utviklerne som har
8769 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8770 bootsekvens tilgjengelig i stabil utgave, vha pakken
8771 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8772 </description>
8773 </item>
8774
8775 <item>
8776 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8777 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8778 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8779 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8780 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8781 Oslo. Most of Saturday was used for the general assemly for the
8782 member organization, but the rest of the weekend I used to tune the
8783 LTSP installation. LTSP now work out of the box on the 10-network.
8784 Acer Aspire One proved to be a very nice thin client, with both
8785 screen, mouse and keybard in a small box. Was working on getting the
8786 diskless workstation setup configured out of the box, but did not
8787 finish it before the weekend was up.&lt;/p&gt;
8788
8789 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8790 the Brazilian group, so that will have to wait for the next
8791 development gathering. Would love to have the Debian Edu installer
8792 automatically detect and configure a multiseat setup when it find one
8793 of these cards.&lt;/p&gt;
8794 </description>
8795 </item>
8796
8797 <item>
8798 <title>The sorry state of multimedia browser plugins in Debian</title>
8799 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8800 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8801 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8802 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8803 plugins available in Debian Lenny, to see which one we should use by
8804 default in Debian Edu. We need an embedded video playing plugin with
8805 control buttons to pause or stop the video, and capable of streaming
8806 all the multimedia content available on the web. The test results and
8807 notes are available on
8808 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8809 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8810 fill this need. My personal video player favorite, VLC, has a really
8811 bad plugin which fail on a lot of the test pages. A lot of the MIME
8812 types I would expect to work with any free software player (like
8813 video/ogg), just do not work. And simple formats like the
8814 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8815 totem and vlc plugins. I hope the situation will improve soon. No
8816 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8817
8818 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8819 be the only one fitting our needs. :/&lt;/p&gt;
8820 </description>
8821 </item>
8822
8823 </channel>
8824 </rss>