]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
9ed87e2a3e9a9d0068b9aea66bd8113dcc03fba3
[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>One in two hundred Debian users using ZFS on Linux?</title>
11 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
13 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
14 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
15 packages in Debian, and was quite surprised with what I found. I use
16 ZFS myself at home, but did not really expect many others to do so.
17 But I might be wrong.&lt;/p&gt;
18
19 &lt;p&gt;According to
20 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
21 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
22 0.53% of the population, with the package installed. As far as I know
23 the only use of the spl-linux package is as a support library for ZFS
24 on Linux, so I use it here as proxy for measuring the number of ZFS
25 installation on Linux in Debian. In the kFreeBSD variant of Debian
26 the ZFS feature is already available, and there
27 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
28 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
29 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
30
31 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
32 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
33 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
34 cleared, the package is still not in Debian. The package is again in
35 the NEW queue. Several uploads have been rejected so far because the
36 debian/copyright file was incomplete or wrong, but there is no reason
37 to give up. The current status can be seen on
38 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
39 team status page&lt;/a&gt;, and
40 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
41 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
42
43 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
44 my home server can function in the future using only official Debian
45 packages, and the current blocker is to get the debian/copyright file
46 accepted by the FTP masters in Debian, I decided a while back to try
47 to help out the team. This was the background for my blog post about
48 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
49 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
50 used the techniques I explored there to try to find any errors in the
51 copyright file. It is not very easy to check every one of the around
52 2000 files in the source package, but I hope we this time got it
53 right. If you want to help out, check out the git source and try to
54 find missing entries in the debian/copyright file.&lt;/p&gt;
55 </description>
56 </item>
57
58 <item>
59 <title>Full battery stats collector is now available in Debian</title>
60 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
61 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
62 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
63 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
64 extended collector that will collect the complete battery history for
65 later processing and graphing. The original collector store the
66 battery level as percentage of last full level, while the new
67 collector also record battery vendor, model, serial number, design
68 full level, last full level and current battery level. This make it
69 possible to predict the lifetime of the battery as well as visualise
70 the energy flow when the battery is charging or discharging.&lt;/p&gt;
71
72 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
73 in the version 0.5.1 package in unstable. Get the new battery level graph
74 and lifetime prediction by running:
75
76 &lt;p&gt;&lt;pre&gt;
77 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
78 &lt;/pre&gt;&lt;/p&gt;
79
80 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
81
82 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
83 entry yet):&lt;/p&gt;
84
85 &lt;p&gt;&lt;pre&gt;
86 /usr/share/battery-stats/battery-stats-graph-flow
87 &lt;/pre&gt;&lt;/p&gt;
88
89 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
90 when there are few data points. The graphs look a bit better with a
91 few years of data.&lt;/p&gt;
92
93 &lt;p&gt;A while back one important feature I use in the battery stats
94 collector broke in Debian. The scripts in
95 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
96 suspect it happened when Jessie started using systemd, but I do not
97 know. The issue is reported as
98 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
99 pm-utils. I managed to work around it by adding an udev rule to call
100 the collector script every time the power connector is connected and
101 disconnected. With this fix in place it was finally time to make a
102 new release of the package, and get it into Debian.&lt;/p&gt;
103
104 &lt;p&gt;If you are interested in how your laptop battery is doing, please
105 check out the
106 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
107 in Debian unstable, or rebuild it on Jessie to get it working on
108 Debian stable. :) The upstream source is available from
109 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
110 As always, patches are very welcome.&lt;/p&gt;
111 </description>
112 </item>
113
114 <item>
115 <title>Making battery measurements a little easier in Debian</title>
116 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
118 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
119 <description>&lt;p&gt;Back in September, I blogged about
120 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
121 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
122 how it showed the decay and death of this battery (now replaced). I
123 created a simple deb package to handle the collection and graphing,
124 but did not want to upload it to Debian as there were already
125 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
126 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
127 a point of uploading a competing package when battery-stats could be
128 fixed instead. I reported a few bugs about its non-function, and
129 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
130
131 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
132 hands. The end result is that I am now the new upstream developer of
133 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
134 battery-stats in Debian, and the package in Debian unstable is finally
135 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
136 information provided by the Linux kernel. If you install the
137 battery-stats package from unstable now, you will be able to get a
138 graph of the current battery fill level, to get some idea about the
139 status of the battery. The source package build and work just fine in
140 Debian testing and stable (and probably oldstable too, but I have not
141 tested). The default graph you get for that system look like this:&lt;/p&gt;
142
143 &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;
144
145 &lt;p&gt;My plans for the future is to merge my old scripts into the
146 battery-stats package, as my old scripts collected a lot more details
147 about the battery. The scripts are merged into the upstream
148 battery-stats git repository already, but I am not convinced they work
149 yet, as I changed a lot of paths along the way. Will have to test a
150 bit more before I make a new release.&lt;/p&gt;
151
152 &lt;p&gt;I will also consider changing the file format slightly, as I
153 suspect the way I combine several values into one field might make it
154 impossible to know the type of the value when using it for processing
155 and graphing.&lt;/p&gt;
156
157 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
158 battery, check out the battery-stats package in
159 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
160 on
161 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
162 I would love some help to improve the system further.&lt;/p&gt;
163 </description>
164 </item>
165
166 <item>
167 <title>Creating, updating and checking debian/copyright semi-automatically</title>
168 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
169 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
170 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
171 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
172 details. And one of the details is the content of the
173 debian/copyright file, which should list all relevant licenses used by
174 the code in the package in question, preferably in
175 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
176 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
177
178 &lt;p&gt;For large packages with lots of contributors it is hard to write
179 and update this file manually, and if you get some detail wrong, the
180 package is normally rejected by the ftpmasters. So getting it right
181 the first time around get the package into Debian faster, and save
182 both you and the ftpmasters some work.. Today, while trying to figure
183 out what was wrong with
184 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
185 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
186 figuring out the options for doing this job automatically, or at least
187 semi-automatically.&lt;/p&gt;
188
189 &lt;p&gt;Lucikly, there are at least two tools available for generating the
190 file based on the code in the source package,
191 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
192 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
193 not sure which one of them came first, but both seem to be able to
194 create a sensible draft file. As far as I can tell, none of them can
195 be trusted to get the result just right, so the content need to be
196 polished a bit before the file is OK to upload. I found the debmake
197 option in
198 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
199 blog posts from 2014&lt;/a&gt;.
200
201 &lt;p&gt;To generate using debmake, use the -cc option:
202
203 &lt;p&gt;&lt;pre&gt;
204 debmake -cc &gt; debian/copyright
205 &lt;/pre&gt;&lt;/p&gt;
206
207 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
208 this might not be the best option.&lt;/p&gt;
209
210 &lt;p&gt;The cme option is based on a config parsing library, and I found
211 this approach in
212 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
213 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
214 dpkg-copyright&#39; option:
215
216 &lt;p&gt;&lt;pre&gt;
217 cme update dpkg-copyright
218 &lt;/pre&gt;&lt;/p&gt;
219
220 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
221 handle UTF-8 names better than debmake.&lt;/p&gt;
222
223 &lt;p&gt;When the copyright file is created, I would also like some help to
224 check if the file is correct. For this I found two good options,
225 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
226 to focus on license types and file matching, and is able to detect
227 ineffective blocks in the copyright file. The latter reports missing
228 copyright holders and years, but was confused by inconsistent license
229 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
230 fix all issues reported by them before uploading. But I do not know
231 if the tools and the ftpmasters agree on what is important to fix in a
232 copyright file, so the package might still be rejected.&lt;/p&gt;
233
234 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
235 will read through the source and try to find all copyright statements.
236 It is not comparing the result to the content of debian/copyright, but
237 can be useful when verifying the content of the copyright file.&lt;/p&gt;
238
239 &lt;p&gt;Are you aware of better tools in Debian to create and update
240 debian/copyright file. Please let me know, or blog about it on
241 planet.debian.org.&lt;/p&gt;
242
243 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
244 activities, please send Bitcoin donations to my address
245 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
246
247 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
248 on how to use licensecheck and cdbs to create a draft copyright file
249
250 &lt;p&gt;&lt;pre&gt;
251 licensecheck --copyright -r `find * -type f` | \
252 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
253 &lt;/pre&gt;&lt;/p&gt;
254
255 &lt;p&gt;He mentioned that he normally check the generated file into the
256 version control system to make it easier to discover license and
257 copyright changes in the upstream source. I will try to do the same
258 with my packages in the future.&lt;/p&gt;
259
260 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
261 against using -quiet for new users, so I removed it from the proposed
262 command line.&lt;/p&gt;
263 </description>
264 </item>
265
266 <item>
267 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
268 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
269 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
270 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
271 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
272 is taking shape in Debian, and one provided feature is a very
273 convenient way to tell you which package to install to make a given
274 firmware file available when the kernel is looking for it. This can
275 be done using apt-file too, but that is for someone else to blog
276 about. :)&lt;/p&gt;
277
278 &lt;p&gt;Here is a small recipe to find the package with a given firmware
279 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
280 picked from the set of firmware announced using appstream in Debian
281 unstable. In general you would be looking for the firmware requested
282 by the kernel during kernel module loading. To find the package
283 providing the example file, do like this:&lt;/p&gt;
284
285 &lt;blockquote&gt;&lt;pre&gt;
286 % apt install appstream
287 [...]
288 % apt update
289 [...]
290 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
291 awk &#39;/Package:/ {print $2}&#39;
292 firmware-qlogic
293 %
294 &lt;/pre&gt;&lt;/blockquote&gt;
295
296 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
297 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
298 a way appstream can use.&lt;/p&gt;
299
300 &lt;p&gt;This same approach can be used to find any package supporting a
301 given MIME type. This is very useful when you get a file you do not
302 know how to handle. First find the mime type using &lt;tt&gt;file
303 --mime-type&lt;/tt&gt;, and next look up the package providing support for
304 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
305 and you can find all packages handling this type like this:&lt;/p&gt;
306
307 &lt;blockquote&gt;&lt;pre&gt;
308 % apt install appstream
309 [...]
310 % apt update
311 [...]
312 % appstreamcli what-provides mimetype image/svg+xml | \
313 awk &#39;/Package:/ {print $2}&#39;
314 bkchem
315 phototonic
316 inkscape
317 shutter
318 tetzle
319 geeqie
320 xia
321 pinta
322 gthumb
323 karbon
324 comix
325 mirage
326 viewnior
327 postr
328 ristretto
329 kolourpaint4
330 eog
331 eom
332 gimagereader
333 midori
334 %
335 &lt;/pre&gt;&lt;/blockquote&gt;
336
337 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
338 packages providing appstream metadata.&lt;/p&gt;
339 </description>
340 </item>
341
342 <item>
343 <title>Creepy, visualise geotagged social media information - nice free software</title>
344 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
346 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
347 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
348 with the computerised radio beacon known as a mobile phone their
349 position is tracked by the phone company and often stored for a long
350 time (like every time a SMS is received or sent). And if their
351 computerised radio beacon is capable of running programs (often called
352 mobile apps) downloaded from the Internet, these programs are often
353 also capable of tracking their location (if the app requested access
354 during installation). And when these programs send out information to
355 central collection points, the location is often included, unless
356 extra care is taken to not send the location. The provided
357 information is used by several entities, for good and bad (what is
358 good and bad, depend on your point of view). What is certain, is that
359 the private sphere and the right to free movement is challenged and
360 perhaps even eradicated for those announcing their location this way,
361 when they share their whereabouts with private and public
362 entities.&lt;/p&gt;
363
364 &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;
365
366 &lt;p&gt;The phone company logs provide a register of locations to check out
367 when one want to figure out what the tracked person was doing. It is
368 unavailable for most of us, but provided to selected government
369 officials, company staff, those illegally buying information from
370 unfaithful servants and crackers stealing the information. But the
371 public information can be collected and analysed, and a free software
372 tool to do so is called
373 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
374 discovered it when I read
375 &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
376 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
377 November 2014, and decided to check if it was available in Debian.
378 The python program was in Debian, but
379 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
380 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
381 uploaded a new version which did not work quite right, but did not
382 have time to fix it then. This Christmas I decided to finally try to
383 get Creepy operational in Debian. Now a fixed version is available in
384 Debian unstable and testing, and almost all Debian specific patches
385 are now included
386 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
387
388 &lt;p&gt;The Creepy program visualises geolocation information fetched from
389 Twitter, Instagram, Flickr and Google+, and allow one to get a
390 complete picture of every social media message posted recently in a
391 given area, or track the movement of a given individual across all
392 these services. Earlier it was possible to use the search API of at
393 least some of these services without identifying oneself, but these
394 days it is impossible. This mean that to use Creepy, you need to
395 configure it to log in as yourself on these services, and provide
396 information to them about your search interests. This should be taken
397 into account when using Creepy, as it will also share information
398 about yourself with the services.&lt;/p&gt;
399
400 &lt;p&gt;The picture above show the twitter messages sent from (or at least
401 geotagged with a position from) the city centre of Oslo, the capital
402 of Norway. One useful way to use Creepy is to first look at
403 information tagged with an area of interest, and next look at all the
404 information provided by one or more individuals who was in the area.
405 I tested it by checking out which celebrity provide their location in
406 twitter messages by checkout out who sent twitter messages near a
407 Norwegian TV station, and next could track their position over time,
408 making it possible to locate their home and work place, among other
409 things. A similar technique have been
410 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
411 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
412 tool to discover lying governments, and a useful tool to help people
413 understand the value of the private information they provide to the
414 public.&lt;/p&gt;
415
416 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
417 it depend on several python modules currently missing in Jessie (at
418 least python-instagram, python-flickrapi and
419 python-requests-toolbelt).&lt;/p&gt;
420
421 &lt;p&gt;(I have uploaded
422 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
423 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
424 Creepy program in Debian.)&lt;/p&gt;
425 </description>
426 </item>
427
428 <item>
429 <title>Always download Debian packages using Tor - the simple recipe</title>
430 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
431 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
432 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
433 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
434 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
435 that those listening on the Internet lines would have good reason to
436 believe a computer have a given security hole&lt;/a&gt; if it download a
437 security fix from a Debian mirror. This is a good reason to always
438 use encrypted connections to the Debian mirror, to make sure those
439 listening do not know which IP address to attack. In August, Richard
440 Hartmann observed that encryption was not enough, when it was possible
441 to interfere download size to security patches or the fact that
442 download took place shortly after a security fix was released, and
443 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
444 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
445 was not the first to propose this, as the
446 &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;
447 package by Tim Retout already existed to make it easy to convince apt
448 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
449 aware of that package when I read the blog post from Richard.&lt;/p&gt;
450
451 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
452 sysadmins, and he set up a Tor hidden service on one of the central
453 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
454 it possible to download packages directly between two tor nodes,
455 making sure the network traffic always were encrypted.&lt;/p&gt;
456
457 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
458 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
459 urls with tor+http and tor+https, and using the hidden service instead
460 of the official Debian mirror site. I recommend installing
461 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
462 done in /etc/.&lt;/p&gt;
463
464 &lt;blockquote&gt;&lt;pre&gt;
465 apt install apt-transport-tor
466 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
467 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
468 &lt;/pre&gt;&lt;/blockquote&gt;
469
470 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
471 the sed commands for these too. The sed command is assuming your are
472 using the ftp.debian.org Debian mirror. Adjust the command (or just
473 edit the file manually) to match your mirror.&lt;/p&gt;
474
475 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
476 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
477 system, and do not work with these tor+http URLs. For
478 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
479 which need a recent apt version currently only in unstable. So if you
480 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
481
482 &lt;p&gt;Another advantage from this change is that your machine will start
483 using Tor regularly and at fairly random intervals (every time you
484 update the package lists or upgrade or install a new package), thus
485 masking other Tor traffic done from the same machine. Using Tor will
486 become normal for the machine in question.&lt;/p&gt;
487
488 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
489 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
490 enabled. It would be great if it was the default on any Debian
491 system.&lt;/p&gt;
492 </description>
493 </item>
494
495 <item>
496 <title>OpenALPR, find car license plates in video streams - nice free software</title>
497 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
498 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
499 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
500 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
501 call the car license plate numbers in those days. I would write the
502 numbers down in my little book and compare notes with the other kids
503 to see how many region codes we had seen and if we had seen some
504 exotic or special region codes and numbers. It was a fun game to pass
505 time, as we kids have plenty of it.&lt;/p&gt;
506
507 &lt;p&gt;A few days I came across
508 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
509 project&lt;/a&gt;, a free software project to automatically discover and
510 report license plates in images and video streams, and provide the
511 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
512 such system for a while now, because I believe it is a bad idea that the
513 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
514 number plate recognition&lt;/a&gt; tool only is available in the hands of
515 the powerful, and want it to be available also for the powerless to
516 even the score when it comes to surveillance and sousveillance. I
517 discovered the developer
518 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
519 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
520 help him get it into shape to get the package uploaded into the Debian
521 archive.&lt;/p&gt;
522
523 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
524 it into Debian, where it currently
525 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
526 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
527
528 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
529 for the common folks, ie those not running a large government
530 surveillance system? Well, I plan to put it in a computer on my bike
531 and in my car, tracking the cars nearby and allowing me to be notified
532 when number plates on my watch list are discovered. Another use case
533 was suggested by a friend of mine, who wanted to set it up at his home
534 to open the car port automatically when it discovered the plate on his
535 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
536 capable of placing his license plate number of a piece of cardboard to
537 open his car port, men replied that it was always unlocked anyway. I
538 guess for such use case it make sense. I am sure there are other use
539 cases too, for those with imagination and a vision.&lt;/p&gt;
540
541 &lt;p&gt;If you want to build your own version of the Debian package, check
542 out the upstream git source and symlink ./distros/debian to ./debian/
543 before running &quot;debuild&quot; to build the source. Or wait a bit until the
544 package show up in unstable.&lt;/p&gt;
545 </description>
546 </item>
547
548 <item>
549 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
550 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
551 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
552 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
553 <description>&lt;p&gt;Around three years ago, I created
554 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
555 system&lt;/a&gt; to get a more practical solution in Debian for handing
556 hardware related packages. A GUI system in the isenkram package will
557 present a pop-up dialog when some hardware dongle supported by
558 relevant packages in Debian is inserted into the machine. The same
559 lookup mechanism to detect packages is available as command line
560 tools in the isenkram-cli package. In addition to mapping hardware,
561 it will also map kernel firmware files to packages and make it easy to
562 install needed firmware packages automatically. The key for this
563 system to work is a good way to map hardware to packages, in other
564 words, allow packages to announce what hardware they will work
565 with.&lt;/p&gt;
566
567 &lt;p&gt;I started by providing data files in the isenkram source, and
568 adding code to download the latest version of these data files at run
569 time, to ensure every user had the most up to date mapping available.
570 I also added support for storing the mapping in the Packages file in
571 the apt repositories, but did not push this approach because while I
572 was trying to figure out how to best store hardware/package mappings,
573 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
574 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
575 add the hardware mapping into that data set to be able to use
576 appstream as a data source, and this was accepted at least for the
577 Debian version of appstream.&lt;/p&gt;
578
579 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
580 and today I uploaded a new version 0.20 of isenkram adding support for
581 appstream as a data source for mapping hardware to packages. The only
582 package so far using appstream to announce its hardware support is my
583 pymissile package. I got help from Matthias Klumpp with figuring out
584 how do add the required
585 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
586 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
587 this content:&lt;/p&gt;
588
589 &lt;blockquote&gt;&lt;pre&gt;
590 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
591 &amp;lt;component&amp;gt;
592 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
593 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
594 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
595 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
596 &amp;lt;description&amp;gt;
597 &amp;lt;p&amp;gt;
598 Pymissile provides a curses interface to control an original
599 Marks and Spencer / Striker USB Missile Launcher, as well as a
600 motion control script to allow a webcamera to control the
601 launcher.
602 &amp;lt;/p&amp;gt;
603 &amp;lt;/description&amp;gt;
604 &amp;lt;provides&amp;gt;
605 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
606 &amp;lt;/provides&amp;gt;
607 &amp;lt;/component&amp;gt;
608 &lt;/pre&gt;&lt;/blockquote&gt;
609
610 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
611 which is a glob style match rule for hardware specific strings
612 (modalias strings) provided by the Linux kernel. In this case, it
613 will map to all USB devices with vendor code 1130 and product code
614 0202.&lt;/p&gt;
615
616 &lt;p&gt;Note, it is important that the license of all the metadata files
617 are compatible to have permissions to aggregate them into archive wide
618 appstream files. Matthias suggested to use MIT or BSD licenses for
619 these files. A challenge is figuring out a good id for the data, as
620 it is supposed to be globally unique and shared across distributions
621 (in other words, best to coordinate with upstream what to use). But
622 it can be changed later or, so we went with the package name as
623 upstream for this project is dormant.&lt;/p&gt;
624
625 &lt;p&gt;To get the metadata file installed in the correct location for the
626 mirror update scripts to pick it up and include its content the
627 appstream data source, the file must be installed in the binary
628 package under /usr/share/appdata/. I did this by adding the following
629 line to debian/pymissile.install:&lt;/p&gt;
630
631 &lt;blockquote&gt;&lt;pre&gt;
632 debian/pymissile.metainfo.xml usr/share/appdata
633 &lt;/pre&gt;&lt;/blockquote&gt;
634
635 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
636 all packages useful on the current computer automatically, and the GUI
637 pop-up handler will propose to install the package not already
638 installed if a hardware dongle is inserted into the machine in
639 question.&lt;/p&gt;
640
641 &lt;p&gt;Details of the modalias field in appstream is available from the
642 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
643
644 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
645 try running this command on the command line:&lt;/p&gt;
646
647 &lt;blockquote&gt;&lt;pre&gt;
648 cat $(find /sys/devices/|grep modalias)
649 &lt;/pre&gt;&lt;/blockquote&gt;
650
651 &lt;p&gt;To learn more about the isenkram system, please check out
652 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
653 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
654 </description>
655 </item>
656
657 <item>
658 <title>The GNU General Public License is not magic pixie dust</title>
659 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
660 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
661 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
662 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
663 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
664 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
665 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
666 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
667
668 &lt;blockquote&gt;
669
670 &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;
671
672 &lt;blockquote&gt;
673 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
674
675 The first step is to choose a
676 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
677 code.&lt;br/&gt;
678
679 The next step is, when someone fails to follow that copyleft license,
680 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
681
682 and its a simple fact of our modern society that such type of
683 work&lt;br/&gt;
684
685 is incredibly expensive to do and incredibly difficult to do.
686 &lt;/blockquote&gt;
687
688 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
689 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
690 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
691 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
692
693 &lt;p&gt;As the Debian Website
694 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
695 &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;
696 imply, public domain and permissively licensed software can lead to
697 the production of more proprietary software as people discover useful
698 software, extend it and or incorporate it into their hardware or
699 software products. Copyleft licenses such as the GNU GPL were created
700 to close off this avenue to the production of proprietary software but
701 such licenses are not enough. With the ongoing adoption of Free
702 Software by individuals and groups, inevitably the community&#39;s
703 expectations of license compliance are violated, usually out of
704 ignorance of the way Free Software works, but not always. As Karen
705 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
706 Freedom&quot;&gt;FaiF&lt;/a&gt;
707 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
708 copyleft is nothing if no-one is willing and able to stand up in court
709 to protect it. The reality of today&#39;s world is that legal
710 representation is expensive, difficult and time consuming. With
711 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
712 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
713 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
714 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
715 of the Linux project, Debian and other groups against GPL violations.
716 In March the SFC supported a
717 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
718 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
719 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
720 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
721 kernel. Since then two of their sponsors pulled corporate funding and
722 conferences
723 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
724 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
725 less on corporate funding and more on the broad community of
726 individuals who support Free Software and copyleft. So the SFC has
727 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
728 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
729 a community of folks who stand up for copyleft and the GPL by
730 supporting their work on promoting and supporting copyleft and Free
731 Software.&lt;/p&gt;
732
733 &lt;p&gt;If you support Free Software,
734 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
735 what the SFC do, agree with their
736 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
737 principles&lt;/a&gt;, are happy about their
738 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
739 work on a project that is an SFC
740 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
741 just want to stand up for copyleft, please join
742 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
743 Allan Webber&lt;/a&gt;,
744 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
745 Smith&lt;/a&gt;,
746 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
747 Bacon&lt;/a&gt;, myself and
748 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
749 becoming a
750 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
751 next week your donation will be
752 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
753 by an anonymous donor. Please also consider asking your employer to
754 match your donation or become a sponsor of SFC. Don&#39;t forget to
755 spread the word about your support for SFC via email, your blog and or
756 social media accounts.&lt;/p&gt;
757
758 &lt;/blockquote&gt;
759
760 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
761 of Software Freedom Conservancy myself. Perhaps you should be a
762 supporter too?&lt;/p&gt;
763 </description>
764 </item>
765
766 <item>
767 <title>PGP key transition statement for key EE4E02F9</title>
768 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
770 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
771 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
772 set it up properly. I wanted to generate it offline and have it
773 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
774 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
775 time to sit down with an offline machine almost took forever. But
776 finally I&#39;ve been able to complete the process, and have now moved
777 from my old GPG key to a new GPG key. See
778 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
779 full transition statement, signed with both my old and new key&lt;/a&gt; for
780 the details. This is my new key:&lt;/p&gt;
781
782 &lt;pre&gt;
783 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]
784 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
785 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
786 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
787 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
788 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
789 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
790 &lt;/pre&gt;
791
792 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
793 my old key.&lt;/p&gt;
794
795 &lt;p&gt;If you signed my old key
796 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
797 I&#39;d very much appreciate a signature on my new key, details and
798 instructions in the transition statement. I m happy to reciprocate if
799 you have a similarly signed transition statement to present.&lt;/p&gt;
800 </description>
801 </item>
802
803 <item>
804 <title>The life and death of a laptop battery</title>
805 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
806 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
807 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
808 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
809 But this do not last. The last few laptops gave me a feeling that
810 within a year, the life time is just a fraction of what it used to be,
811 and it slowly become painful to use the laptop without power connected
812 all the time. Because of this, when I got a new Thinkpad X230 laptop
813 about two years ago, I decided to monitor its battery state to have
814 more hard facts when the battery started to fail.&lt;/p&gt;
815
816 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
817
818 &lt;p&gt;First I tried to find a sensible Debian package to record the
819 battery status, assuming that this must be a problem already handled
820 by someone else. I found
821 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
822 which collects statistics from the battery, but it was completely
823 broken. I sent a few suggestions to the maintainer, but decided to
824 write my own collector as a shell script while I waited for feedback
825 from him. Via
826 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
827 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
828 discovered
829 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
830 available in Debian.&lt;/p&gt;
831
832 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
833 battery stats ever since. Now my
834 /var/log/hjemmenett-battery-status.log file contain around 115,000
835 measurements, from the time the battery was working great until now,
836 when it is unable to charge above 7% of original capacity. My
837 collector shell script is quite simple and look like this:&lt;/p&gt;
838
839 &lt;pre&gt;
840 #!/bin/sh
841 # Inspired by
842 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
843 # See also
844 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
845 logfile=/var/log/hjemmenett-battery-status.log
846
847 files=&quot;manufacturer model_name technology serial_number \
848 energy_full energy_full_design energy_now cycle_count status&quot;
849
850 if [ ! -e &quot;$logfile&quot; ] ; then
851 (
852 printf &quot;timestamp,&quot;
853 for f in $files; do
854 printf &quot;%s,&quot; $f
855 done
856 echo
857 ) &gt; &quot;$logfile&quot;
858 fi
859
860 log_battery() {
861 # Print complete message in one echo call, to avoid race condition
862 # when several log processes run in parallel.
863 msg=$(printf &quot;%s,&quot; $(date +%s); \
864 for f in $files; do \
865 printf &quot;%s,&quot; $(cat $f); \
866 done)
867 echo &quot;$msg&quot;
868 }
869
870 cd /sys/class/power_supply
871
872 for bat in BAT*; do
873 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
874 done
875 &lt;/pre&gt;
876
877 &lt;p&gt;The script is called when the power management system detect a
878 change in the power status (power plug in or out), and when going into
879 and out of hibernation and suspend. In addition, it collect a value
880 every 10 minutes. This make it possible for me know when the battery
881 is discharging, charging and how the maximum charge change over time.
882 The code for the Debian package
883 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
884 available on github&lt;/a&gt;.&lt;/p&gt;
885
886 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
887
888 &lt;pre&gt;
889 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
890 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
891 [...]
892 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
893 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
894 &lt;/pre&gt;
895
896 &lt;p&gt;I wrote a small script to create a graph of the charge development
897 over time. This graph depicted above show the slow death of my laptop
898 battery.&lt;/p&gt;
899
900 &lt;p&gt;But why is this happening? Why are my laptop batteries always
901 dying in a year or two, while the batteries of space probes and
902 satellites keep working year after year. If we are to believe
903 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
904 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
905 chance, and the fix is to not charge the Lithium-ion batteries to 100%
906 all the time, but to stay below 90% of full charge most of the time.
907 I&#39;ve been told that the Tesla electric cars
908 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
909 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
910 100% when preparing for a longer trip (not that I would want a car
911 like Tesla where rights to privacy is abandoned, but that is another
912 story), which I guess is the option we should have for laptops on
913 Linux too.&lt;/p&gt;
914
915 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
916 stop charging at 80%, unless requested to charge to 100% once in
917 preparation for a longer trip? I found
918 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
919 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
920 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
921 load).&lt;/p&gt;
922
923 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
924 at the start. I also wonder why the &quot;full capacity&quot; increases some
925 times, and if it is possible to repeat the process to get the battery
926 back to design capacity. And I wonder if the discharge and charge
927 speed change over time, or if this stay the same. I did not yet try
928 to write a tool to calculate the derivative values of the battery
929 level, but suspect some interesting insights might be learned from
930 those.&lt;/p&gt;
931
932 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
933 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
934 packages instead of the tp-smapi-dkms package I had tried to use
935 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
936 and stop. I&#39;ve done so now, but expect my existing battery is toast
937 and need to be replaced. The proposal is unfortunately Thinkpad
938 specific.&lt;/p&gt;
939 </description>
940 </item>
941
942 <item>
943 <title>New laptop - some more clues and ideas based on feedback</title>
944 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
945 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
946 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
947 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
948 need for a new laptop, and provided very useful feedback. I wish to
949 thank every one of these. Several pointed me to the possibility of
950 fixing my X230, and I am already in the process of getting Lenovo to
951 do so thanks to the on site, next day support contract covering the
952 machine. But the battery is almost useless (I expect to replace it
953 with a non-official battery) and I do not expect the machine to live
954 for many more years, so it is time to plan its replacement. If I did
955 not have a support contract, it was suggested to find replacement parts
956 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
957 might present a language barrier as I do not understand French.&lt;/p&gt;
958
959 &lt;p&gt;One tip I got was to use the
960 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
961 compare laptop models. It seem to have more models available than
962 prisjakt.no. Another tip I got from someone I know have similar
963 keyboard preferences was that the HP EliteBook 840 keyboard is not
964 very good, and this matches my experience with earlier EliteBook
965 keyboards I tested. Because of this, I will not consider it any further.
966
967 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
968 newest Thinkpad X model. The keyboard reintroduces mouse buttons
969 (which is missing from the X240), and is working fairly well with
970 Debian Sid/Unstable according to
971 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
972 got on the keyboard quality are not consistent. Some say the keyboard
973 is good, others say it is ok, while others say it is not very good.
974 Those with experience from X41 and and X60 agree that the X250
975 keyboard is not as good as those trusty old laptops, and suggest I
976 keep and fix my X230 instead of upgrading, or get a used X230 to
977 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
978 activity and battery status, which is very convenient on my X230. I&#39;m
979 also told that the CPU fan is running very often, making it a bit
980 noisy. In any case, the X250 do not work out of the box with Debian
981 Stable/Jessie, one of my requirements.&lt;/p&gt;
982
983 &lt;p&gt;I have also gotten a few vendor proposals, one was
984 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
985 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
986 The latter look very attractive to me.&lt;/p&gt;
987
988 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
989 as I keep looking for a replacement.&lt;/p&gt;
990
991 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
992 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
993 different
994 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
995 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
996 </description>
997 </item>
998
999 <item>
1000 <title>Time to find a new laptop, as the old one is broken after only two years</title>
1001 <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>
1002 <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>
1003 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
1004 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
1005 replacement soon. The left 5 cm of the screen on my Thinkpad X230
1006 started flickering yesterday, and I suspect the cause is a broken
1007 cable, as changing the angle of the screen some times get rid of the
1008 flickering.&lt;/p&gt;
1009
1010 &lt;p&gt;My requirements have not really changed since I bought it, and is
1011 still as
1012 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
1013 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
1014 good help from
1015 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
1016 where I could select at least a few of the requirements (mouse pin,
1017 wifi, weight) and go through the rest manually. Three button mouse
1018 and a good keyboard is not available as an option, and all the three
1019 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
1020 G2) lack three mouse buttons). It is also unclear to me how good the
1021 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1022 the keyboard, even if the quality and robustness in the X series have
1023 deteriorated since X41.&lt;/p&gt;
1024
1025 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
1026 seem sensible to me? Are there better services around to search the
1027 set of available laptops for features? Please send me an email if you
1028 have suggestions.&lt;/p&gt;
1029
1030 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
1031 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
1032 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
1033 </description>
1034 </item>
1035
1036 <item>
1037 <title>How to stay with sysvinit in Debian Jessie</title>
1038 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
1039 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
1040 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
1041 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
1042 sysvinit as its boot system by default. But how can one keep using
1043 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1044 courtesy of
1045 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
1046 Schubert&lt;/a&gt; and
1047 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
1048 McVittie&lt;/a&gt;.
1049
1050 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
1051 keep sysvinit as your boot system, create a file
1052 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
1053 you upgrade:&lt;/p&gt;
1054
1055 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1056 Package: systemd-sysv
1057 Pin: release o=Debian
1058 Pin-Priority: -1
1059 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1060
1061 &lt;p&gt;This file content will tell apt and aptitude to not consider
1062 installing systemd-sysv as part of any installation and upgrade
1063 solution when resolving dependencies, and thus tell it to avoid
1064 systemd as a default boot system. The end result should be that the
1065 upgraded system keep using sysvinit.&lt;/p&gt;
1066
1067 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
1068 get sysvinit installed by default (debootstrap used by
1069 debian-installer have no option for this), but one can tell the
1070 installer to switch to sysvinit before the first boot. Either by
1071 using a kernel argument to the installer, or by adding a line to the
1072 preseed file used. First, the kernel command line argument:
1073
1074 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1075 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
1076 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1077
1078 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
1079
1080 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1081 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1082 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1083
1084 &lt;p&gt;One can of course also do this after the first boot by installing
1085 the sysvinit-core package.&lt;/p&gt;
1086
1087 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
1088 sysvinit boot sequence in Debian have several hardware specific bugs
1089 on Linux caused by the fact that it is unpredictable when hardware
1090 devices show up during boot. But on the other hand, the new default
1091 boot system still have a few rough edges I hope will be fixed before
1092 Jessie is released.&lt;/p&gt;
1093
1094 &lt;p&gt;Update 2014-11-26: Inspired by
1095 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
1096 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
1097 line.&lt;/p&gt;
1098 </description>
1099 </item>
1100
1101 <item>
1102 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
1103 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
1104 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
1105 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
1106 <description>&lt;p&gt;The right to communicate with your friends and family in private,
1107 without anyone snooping, is a right every citicen have in a liberal
1108 democracy. But this right is under serious attack these days.&lt;/p&gt;
1109
1110 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
1111 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1112 the whisleblower Snowden) more expensive for Internet email,
1113 is to deliver all email using SMTP via Tor. Such SMTP option would be
1114 a nice addition to the FreedomBox project if we could send email
1115 between FreedomBox machines without leaking metadata about the emails
1116 to the people peeking on the wire. I
1117 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
1118 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
1119 lot of useful feedback and suggestions. It also became obvious to me
1120 that this was not a novel idea, as the same idea was tested and
1121 documented by Johannes Berg as early as 2006, and both
1122 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
1123 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
1124 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
1125
1126 &lt;p&gt;To implement such system one need to set up a Tor hidden service
1127 providing the SMTP protocol on port 25, and use email addresses
1128 looking like username@hidden-service-name.onion. With such addresses
1129 the connections to port 25 on hidden-service-name.onion using Tor will
1130 go to the correct SMTP server. To do this, one need to configure the
1131 Tor daemon to provide the hidden service and the mail server to accept
1132 emails for this .onion domain. To learn more about Exim configuration
1133 in Debian and test the design provided by Johannes Berg in his FAQ, I
1134 set out yesterday to create a Debian package for making it trivial to
1135 set up such SMTP over Tor service based on Debian. Getting it to work
1136 were fairly easy, and
1137 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
1138 source code for the Debian package&lt;/a&gt; is available from github. I
1139 plan to move it into Debian if further testing prove this to be a
1140 useful approach.&lt;/p&gt;
1141
1142 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
1143 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
1144 get rid of exim4). Install tor, clone the git repository mentioned
1145 above, build the deb and install it on the machine. Next, run
1146 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
1147 the instructions to get the service up and running. Restart tor and
1148 exim when it is done, and test mail delivery using swaks like
1149 this:&lt;/p&gt;
1150
1151 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1152 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1153 --to fbx@dutlqrrmjhtfa3vp.onion
1154 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1155
1156 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
1157 address with your own address to test your server. :)&lt;/p&gt;
1158
1159 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
1160 easier and more automatic. Especially the tor setup need more work.
1161 Also, the package include a tor-smtp tool written in C, but its task
1162 should probably be rewritten in some script language to make the deb
1163 architecture independent. It would probably also make the code easier
1164 to review. The tor-smtp tool currently need to listen on a socket for
1165 exim to talk to it and is started using xinetd. It would be better if
1166 no daemon and no socket is needed. I suspect it is possible to get
1167 exim to run a command line tool for delivery instead of talking to a
1168 socket, and hope to figure out how in a future version of this
1169 system.&lt;/p&gt;
1170
1171 &lt;p&gt;Until I wipe my test machine, I can be reached using the
1172 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
1173 SMTorP. :)&lt;/p&gt;
1174 </description>
1175 </item>
1176
1177 <item>
1178 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
1179 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
1180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
1181 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
1182 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
1183 alioth.debian.org, you know the web interface is fairly slow to
1184 operate. First you visit one web page, enter the moderation password
1185 and get a new page shown with a list of all the messages to moderate
1186 and various options for each email address. This take a while for
1187 every list you moderate, and you need to do it regularly to do a good
1188 job as a list moderator. But there is a quick alternative,
1189 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
1190 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
1191 to moderate in a fraction of a second. Here is a test run on two
1192 lists I recently took over:&lt;/p&gt;
1193
1194 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1195 % time listadmin xiph
1196 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1197 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1198
1199 real 0m1.709s
1200 user 0m0.232s
1201 sys 0m0.012s
1202 %
1203 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1204
1205 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
1206 there are no message in the moderation queue. Every morning I
1207 currently moderate 68 mailman lists, and it normally take around two
1208 minutes. When I took over the two pkg-xiph lists above a few days
1209 ago, there were 400 emails waiting in the moderator queue. It took me
1210 less than 15 minutes to process them all using the listadmin
1211 program.&lt;/p&gt;
1212
1213 &lt;p&gt;If you install
1214 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
1215 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
1216 with content like this, the moderation task is a breeze:&lt;/p&gt;
1217
1218 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1219 username username@example.org
1220 spamlevel 23
1221 default discard
1222 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
1223
1224 password secret
1225 adminurl https://{domain}/mailman/admindb/{list}
1226 mailman-list@lists.example.com
1227
1228 password hidden
1229 other-list@otherserver.example.org
1230 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1231
1232 &lt;p&gt;There are other options to set as well. Check the manual page to
1233 learn the details.&lt;/p&gt;
1234
1235 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
1236 the SSL certificate is self signed or not properly signed by a
1237 generally accepted signing authority, you can set a environment
1238 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
1239
1240 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1241 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
1242 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1243
1244 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
1245 can provide an argument to the listadmin script like I do in the
1246 initial screen dump (the xiph argument). Using an argument, only
1247 lists matching the argument string will be processed. This make it
1248 quick to accept messages if you notice the moderation request in your
1249 email.&lt;/p&gt;
1250
1251 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
1252 mailing lists, as I simply do not have time to spend on that if the
1253 process was any slower. The listadmin program have saved me hours of
1254 time I could spend elsewhere over the years. It truly is nice free
1255 software.&lt;/p&gt;
1256
1257 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1258 activities, please send Bitcoin donations to my address
1259 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1260
1261 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1262 configuration example. Also, I&#39;ve been told that the
1263 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1264 sure why.&lt;/p&gt;
1265 </description>
1266 </item>
1267
1268 <item>
1269 <title>Debian Jessie, PXE and automatic firmware installation</title>
1270 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1271 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1272 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1273 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1274 problem that the WiFi card require some firmware to work properly.
1275 And it has been a pain to fix this using preseeding in Debian.
1276 Normally something more is needed. But thanks to
1277 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1278 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1279 to do this using simple preseeding.&lt;/p&gt;
1280
1281 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1282 firmware for the hardware found in the machine (actually, requested by
1283 the kernel modules for the hardware). (It can also install user space
1284 programs supporting the hardware detected, but that is not the focus
1285 of this story.)&lt;/p&gt;
1286
1287 &lt;p&gt;To get this working in the default installation, two preeseding
1288 values are needed. First, the isenkram-cli package must be installed
1289 into the target chroot (aka the hard drive) before tasksel is executed
1290 in the pkgsel step of the debian-installer system. This is done by
1291 preseeding the base-installer/includes debconf value to include the
1292 isenkram-cli package. The package name is next passed to debootstrap
1293 for installation. With the isenkram-cli package in place, tasksel
1294 will automatically use the isenkram tasks to detect hardware specific
1295 packages for the machine being installed and install them, because
1296 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1297
1298 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1299 most firmware unfortunately is non-free. This is done by preseeding
1300 the apt-mirror-setup step. This is unfortunate, but for a lot of
1301 hardware it is the only option in Debian.&lt;/p&gt;
1302
1303 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1304 firmware installed automatically by the installer:&lt;/p&gt;
1305
1306 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1307 base-installer base-installer/includes string isenkram-cli
1308 apt-mirror-setup apt-setup/non-free boolean true
1309 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1310
1311 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1312 both firmware and user space packages when using this method. It also
1313 do not work well, so use version 0.15 or later. Installing both
1314 firmware and user space packages might give you a bit more than you
1315 want, so I decided to split the tasksel task in two, one for firmware
1316 and one for user space programs. The firmware task is enabled by
1317 default, while the one for user space programs is not. This split is
1318 implemented in the package currently in unstable.&lt;/p&gt;
1319
1320 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1321 this recipe work for you. :)&lt;/p&gt;
1322
1323 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1324 foremost, it work because tasksel is modular, and driven by whatever
1325 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1326 isenkram-cli package place two files for tasksel to find. First there
1327 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1328
1329 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1330 Task: isenkram-packages
1331 Section: hardware
1332 Description: Hardware specific packages (autodetected by isenkram)
1333 Based on the detected hardware various hardware specific packages are
1334 proposed.
1335 Test-new-install: show show
1336 Relevance: 8
1337 Packages: for-current-hardware
1338
1339 Task: isenkram-firmware
1340 Section: hardware
1341 Description: Hardware specific firmware packages (autodetected by isenkram)
1342 Based on the detected hardware various hardware specific firmware
1343 packages are proposed.
1344 Test-new-install: mark show
1345 Relevance: 8
1346 Packages: for-current-hardware-firmware
1347 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1348
1349 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1350 should be handled and the Packages line referencing to a script in
1351 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1352 list of packages to install. The for-current-hardware-firmware script
1353 look like this to list relevant firmware for the machine:
1354
1355 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1356 #!/bin/sh
1357 #
1358 PATH=/usr/sbin:$PATH
1359 export PATH
1360 isenkram-autoinstall-firmware -l
1361 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1362
1363 &lt;p&gt;With those two pieces in place, the firmware is installed by
1364 tasksel during the normal d-i run. :)&lt;/p&gt;
1365
1366 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1367 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1368 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1369 install.&lt;/p&gt;
1370
1371 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1372 pilots in testing this feature, as isenkram is used there now to
1373 install firmware, replacing the earlier scripts.&lt;/p&gt;
1374 </description>
1375 </item>
1376
1377 <item>
1378 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1379 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1380 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1381 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1382 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1383 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1384 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1385 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1386
1387 &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;
1388
1389 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1390 about this hidden Linux installation. It is interesting what
1391 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1392 </description>
1393 </item>
1394
1395 <item>
1396 <title>New lsdvd release version 0.17 is ready</title>
1397 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1398 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1399 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1400 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1401 got a new set of developers a few weeks ago, after the original
1402 developer decided to step down and pass the project to fresh blood.
1403 This project is now maintained by Petter Reinholdtsen and Steve
1404 Dibb.&lt;/p&gt;
1405
1406 &lt;p&gt;I just wrapped up
1407 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1408 new lsdvd release&lt;/a&gt;, available in git or from
1409 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1410 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1411 0.17.&lt;/p&gt;
1412
1413 &lt;ul&gt;
1414
1415 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1416 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1417 non-existant, to work around additional copy protection&lt;/li&gt;
1418 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1419 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1420 &lt;li&gt;Fix include orders&lt;/li&gt;
1421 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1422 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1423 &lt;li&gt;Make sure the array size and the array limit used when initialising
1424 the palette size is the same.&lt;/li&gt;
1425 &lt;li&gt;Fix array printing.&lt;/li&gt;
1426 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1427 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1428 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1429 with more GCC compiler warnings.&lt;/li&gt;
1430
1431 &lt;/ul&gt;
1432
1433 &lt;p&gt;This change bring together patches for lsdvd in use in various
1434 Linux and Unix distributions, as well as patches submitted to the
1435 project the last nine years. Please check it out. :)&lt;/p&gt;
1436 </description>
1437 </item>
1438
1439 <item>
1440 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1441 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1442 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1443 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1444 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1445 project&lt;/a&gt; provide a Linux solution for schools, including a
1446 powerful desktop with education software, a central server providing
1447 web pages, user database, user home directories, central login and PXE
1448 boot of both clients without disk and the installation to install Debian
1449 Edu on machines with disk (and a few other services perhaps to small
1450 to mention here). We in the Debian Edu team are currently working on
1451 the Jessie based version, trying to get everything in shape before the
1452 freeze, to avoid having to maintain our own package repository in the
1453 future. The
1454 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1455 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1456 work left. Some fatal problems block testing, breaking the installer,
1457 but it is possible to work around these to get anyway. Here is a
1458 recipe on how to get the installation limping along.&lt;/p&gt;
1459
1460 &lt;p&gt;First, download the test ISO via
1461 &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;,
1462 &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;
1463 or rsync (use
1464 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1465 The ISO build was broken on Tuesday, so we do not get a new ISO every
1466 12 hours or so, but thankfully the ISO we already got we are able to
1467 install with some tweaking.&lt;/p&gt;
1468
1469 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1470 (use Alt-Ctrl-F2), run&lt;/p&gt;
1471
1472 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1473 nano /usr/bin/edu-eatmydata-install
1474 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1475
1476 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1477 optimization. Return to the installation, select the profile you want
1478 and continue. Without this change, exim4-config will fail to install
1479 due to a known bug in eatmydata.&lt;/p&gt;
1480
1481 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1482 this do not work, figure out what your correct value would be. All my
1483 test machines need /dev/sda, so I have no advice if it do not fit
1484 your need.&lt;/p&gt;
1485
1486 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1487 root after the initial boot from hard drive, and install the
1488 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1489 or mate. If you want several desktop options, install more than one
1490 metapackage. Once this is done, reboot and you should have a working
1491 graphical login screen. This workaround should no longer be needed
1492 once the education-tasks package version 1.801 enter testing in two
1493 days.&lt;/p&gt;
1494
1495 &lt;p&gt;I believe the ISO build will start working on two days when the new
1496 tasksel package enter testing and Steve McIntyre get a chance to
1497 update the debian-cd git repository. The eatmydata, grub and desktop
1498 issues are already fixed in unstable and testing, and should show up
1499 on the ISO as soon as the ISO build start working again. Well the
1500 eatmydata optimization is really just disabled. The proper fix
1501 require an upload by the eatmydata maintainer applying the patch
1502 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1503 The rest have proper fixes in unstable.&lt;/p&gt;
1504
1505 &lt;p&gt;I hope this get you going with the installation testing, as we are
1506 quickly running out of time trying to get our Jessie based
1507 installation ready before the distribution freeze in a month.&lt;/p&gt;
1508 </description>
1509 </item>
1510
1511 <item>
1512 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1513 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1515 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1516 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1517 to handle my fairly large DVD collection. It is a nice command line
1518 tool to get details about a DVD, like title, tracks, track length,
1519 etc, in XML, Perl or human readable format. But lsdvd have not seen
1520 any new development since 2006 and had a few irritating bugs affecting
1521 its use with some DVDs. Upstream seemed to be dead, and in January I
1522 sent a small probe asking for a version control repository for the
1523 project, without any reply. But I use it regularly and would like to
1524 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1525 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1526 the project admin, and after getting a reply from him explaining that
1527 he was no longer interested in the project, I asked if I could take
1528 over. And yesterday, I became project admin.&lt;/p&gt;
1529
1530 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1531 maintainer interested in joining forces to maintain the upstream
1532 project, and I hope we can get a new release out fairly quickly,
1533 collecting the patches spread around on the internet into on place.
1534 I&#39;ve added the relevant Debian patches to the freshly created git
1535 repository, and expect the Gentoo patches to make it too. If you got
1536 a DVD collection and care about command line tools, check out
1537 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1538 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1539 list&lt;/a&gt;. :)&lt;/p&gt;
1540 </description>
1541 </item>
1542
1543 <item>
1544 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1545 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1546 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1547 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1548 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1549 a lot quicker. When we install more than 2000 packages in
1550 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1551 tasksel in the installer, unpacking the binary packages take forever.
1552 A part of the slow I/O issue was discussed in
1553 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1554 much file system sync-ing done by dpkg, which is the package
1555 responsible for unpacking the binary packages. Other parts (like code
1556 executed by postinst scripts) might also sync to disk during
1557 installation. All this sync-ing to disk do not really make sense to
1558 me. If the machine crash half-way through, I start over, I do not try
1559 to salvage the half installed system. So the failure sync-ing is
1560 supposed to protect against, hardware or system crash, is not really
1561 relevant while the installer is running.&lt;/p&gt;
1562
1563 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1564 system sync()-ing in a fairly non-intrusive way, without the need to
1565 change the code in several packages. The idea is not new, but I have
1566 not heard anyone propose the approach using dpkg-divert before. It
1567 depend on the small and clever package
1568 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1569 uses LD_PRELOAD to replace the system functions for syncing data to
1570 disk with functions doing nothing, thus allowing programs to live
1571 dangerous while speeding up disk I/O significantly. Instead of
1572 modifying the implementation of dpkg, apt and tasksel (which are the
1573 packages responsible for selecting, fetching and installing packages),
1574 it occurred to me that we could just divert the programs away, replace
1575 them with a simple shell wrapper calling
1576 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1577 Two days ago I decided to test the idea, and wrapped up a simple
1578 implementation for the Debian Edu udeb.&lt;/p&gt;
1579
1580 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1581 time of the pkgsel step (installing tasks) from 64 to less than 44
1582 minutes (20 minutes shaved off the installation) on an old Dell
1583 Latitude D505 machine. I am not quite sure what the optimised time
1584 would have been, as I messed up the testing a bit, causing the debconf
1585 priority to get low enough for two questions to pop up during
1586 installation. As soon as I saw the questions I moved the installation
1587 along, but do not know how long the question were holding up the
1588 installation. I did some more measurements using Debian Edu Jessie,
1589 and got these results. The time measured is the time stamp in
1590 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1591 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1592 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1593 timing thus do not depend on how quickly the user handle the tasksel
1594 dialog.&lt;/p&gt;
1595
1596 &lt;p&gt;&lt;table&gt;
1597
1598 &lt;tr&gt;
1599 &lt;th&gt;Machine/setup&lt;/th&gt;
1600 &lt;th&gt;Original tasksel&lt;/th&gt;
1601 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1602 &lt;th&gt;Reduction&lt;/th&gt;
1603 &lt;/tr&gt;
1604
1605 &lt;tr&gt;
1606 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1607 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1608 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1609 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1610 &lt;/tr&gt;
1611
1612 &lt;tr&gt;
1613 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1614 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1615 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1616 &lt;td&gt;23 min 40%&lt;/td&gt;
1617 &lt;/tr&gt;
1618
1619 &lt;tr&gt;
1620 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1621 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1622 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1623 &lt;td&gt;11 min 50%&lt;/td&gt;
1624 &lt;/tr&gt;
1625
1626 &lt;tr&gt;
1627 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1628 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1629 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1630 &lt;td&gt;2 min 33%&lt;/td&gt;
1631 &lt;/tr&gt;
1632
1633 &lt;tr&gt;
1634 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1635 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1636 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1637 &lt;td&gt;4 min 21%&lt;/td&gt;
1638 &lt;/tr&gt;
1639
1640 &lt;/table&gt;&lt;/p&gt;
1641
1642 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1643 time is spent downloading packages. The connection to the Internet
1644 was 100Mbit/s during testing, so downloading should not be a
1645 significant factor in the measurement. Download typically took a few
1646 seconds to a few minutes, depending on the amount of packages being
1647 installed.&lt;/p&gt;
1648
1649 &lt;p&gt;The speedup is implemented by using two hooks in
1650 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1651 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1652 finish-install.d hook to remove the divert at the end of the
1653 installation. I picked the pre-pkgsel.d hook instead of the
1654 post-base-installer.d hook because I test using an ISO without the
1655 eatmydata package included, and the post-base-installer.d hook in
1656 Debian Edu can only operate on packages included in the ISO. The
1657 negative effect of this is that I am unable to activate this
1658 optimization for the kernel installation step in d-i. If the code is
1659 moved to the post-base-installer.d hook, the speedup would be larger
1660 for the entire installation.&lt;/p&gt;
1661
1662 &lt;p&gt;I&#39;ve implemented this in the
1663 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1664 git repository, and plan to provide the optimization as part of the
1665 Debian Edu installation. If you want to test this yourself, you can
1666 create two files in the installer (or in an udeb). One shell script
1667 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1668
1669 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1670 #!/bin/sh
1671 set -e
1672 . /usr/share/debconf/confmodule
1673 info() {
1674 logger -t my-pkgsel &quot;info: $*&quot;
1675 }
1676 error() {
1677 logger -t my-pkgsel &quot;error: $*&quot;
1678 }
1679 override_install() {
1680 apt-install eatmydata || true
1681 if [ -x /target/usr/bin/eatmydata ] ; then
1682 for bin in dpkg apt-get aptitude tasksel ; do
1683 file=/usr/bin/$bin
1684 # Test that the file exist and have not been diverted already.
1685 if [ -f /target$file ] ; then
1686 info &quot;diverting $file using eatmydata&quot;
1687 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1688 &gt; /target$file.edu
1689 chmod 755 /target$file.edu
1690 in-target dpkg-divert --package debian-edu-config \
1691 --rename --quiet --add $file
1692 ln -sf ./$bin.edu /target$file
1693 else
1694 error &quot;unable to divert $file, as it is missing.&quot;
1695 fi
1696 done
1697 else
1698 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1699 fi
1700 }
1701
1702 override_install
1703 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1704
1705 &lt;p&gt;To clean up, another shell script should go into
1706 /usr/lib/finish-install.d/ with code like this:
1707
1708 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1709 #! /bin/sh -e
1710 . /usr/share/debconf/confmodule
1711 error() {
1712 logger -t my-finish-install &quot;error: $@&quot;
1713 }
1714 remove_install_override() {
1715 for bin in dpkg apt-get aptitude tasksel ; do
1716 file=/usr/bin/$bin
1717 if [ -x /target$file.edu ] ; then
1718 rm /target$file
1719 in-target dpkg-divert --package debian-edu-config \
1720 --rename --quiet --remove $file
1721 rm /target$file.edu
1722 else
1723 error &quot;Missing divert for $file.&quot;
1724 fi
1725 done
1726 sync # Flush file buffers before continuing
1727 }
1728
1729 remove_install_override
1730 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1731
1732 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1733 edu-eatmydata-install and call it from the pre-pkgsel.d and
1734 finish-install.d scripts.&lt;/p&gt;
1735
1736 &lt;p&gt;By now you might ask if this change should get into the normal
1737 Debian installer too? I suspect it should, but am not sure the
1738 current debian-installer coordinators find it useful enough. It also
1739 depend on the side effects of the change. I&#39;m not aware of any, but I
1740 guess we will see if the change is safe after some more testing.
1741 Perhaps there is some package in Debian depending on sync() and
1742 fsync() having effect? Perhaps it should go into its own udeb, to
1743 allow those of us wanting to enable it to do so without affecting
1744 everyone.&lt;/p&gt;
1745
1746 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1747 will break installation of all programs using gnutls because of
1748 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1749 eatmydata package in Debian will solve it.&lt;/p&gt;
1750
1751 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1752 the optimization work again. And I have discovered that the
1753 dpkg-divert trick is not really needed and implemented a slightly
1754 simpler approach as part of the debian-edu-install package. See
1755 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1756
1757 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1758 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1759 triggering on i386 made it into testing, and broke this installation
1760 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1761 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1762 </description>
1763 </item>
1764
1765 <item>
1766 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1767 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1768 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1769 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1770 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1771 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1772 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1773 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1774 learn that there is a large set of publicly available key servers to
1775 use when looking for peoples public key. So far I have used
1776 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1777 were misbehaving, but those days are ended. The servers I have used
1778 up until yesterday have been slow and some times unavailable. I hope
1779 those problems are gone now.&lt;/p&gt;
1780
1781 &lt;p&gt;Behind the round robin DNS entry of the
1782 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1783 there is a pool of more than 100 keyservers which are checked every
1784 day to ensure they are well connected and up to date. It must be
1785 better than what I have used so far. :)&lt;/p&gt;
1786
1787 &lt;p&gt;Yesterdays speaker told me that the service is the default
1788 keyserver provided by the default configuration in GnuPG, but this do
1789 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1790
1791 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1792 line:&lt;/p&gt;
1793
1794 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1795 keyserver pool.sks-keyservers.net
1796 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1797
1798 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1799 entries in DNS. Just for fun, I did just that at work, so now every
1800 user of GnuPG at the University of Oslo should find a OpenGPG
1801 keyserver automatically should their need it:&lt;/p&gt;
1802
1803 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1804 % host -t srv _pgpkey-http._tcp.uio.no
1805 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1806 %
1807 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1808
1809 &lt;p&gt;Now if only
1810 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1811 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1812 very happy. It can look up a given key or search for a user ID, but I
1813 normally do not want that, but to find a trust path from my key to
1814 another key. Given a user ID or key ID, I would like to find (and
1815 download) the keys representing a signature path from my key to the
1816 key in question, to be able to get a trust path between the two keys.
1817 This is as far as I can tell not possible today. Perhaps something
1818 for a future version of the protocol?&lt;/p&gt;
1819 </description>
1820 </item>
1821
1822 <item>
1823 <title>From English wiki to translated PDF and epub via Docbook</title>
1824 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1825 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1826 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1827 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1828 project&lt;/a&gt; provide an instruction manual for teachers, system
1829 administrators and other users that contain useful tips for setting up
1830 and maintaining a Debian Edu installation. This text is about how the
1831 text processing of this manual is handled in the project.&lt;/p&gt;
1832
1833 &lt;p&gt;One goal of the project is to provide information in the native
1834 language of its users, and for this we need to handle translations.
1835 But we also want to make sure each language contain the same
1836 information, so for this we need a good way to keep the translations
1837 in sync. And we want it to be easy for our users to improve the
1838 documentation, avoiding the need to learn special formats or tools to
1839 contribute, and the obvious way to do this is to make it possible to
1840 edit the documentation using a web browser. We also want it to be
1841 easy for translators to keep the translation up to date, and give them
1842 help in figuring out what need to be translated. Here is the list of
1843 tools and the process we have found trying to reach all these
1844 goals.&lt;/p&gt;
1845
1846 &lt;p&gt;We maintain the authoritative source of our manual in the
1847 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1848 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1849 front page with references to the different chapters, several pages
1850 for each chapter, and finally one &quot;collection page&quot; gluing all the
1851 chapters together into one large web page (aka
1852 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1853 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1854 processing and translations. Thanks to the fact that the
1855 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1856 wiki.debian.org support exporting pages in
1857 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1858 the list of pages to export using the raw version of the AllInOne
1859 page, loop over each of them to generate a Docbook XML version of the
1860 manual. This process also download images and transform image
1861 references to use the locally downloaded images. The generated
1862 Docbook XML files are slightly broken, so some post-processing is done
1863 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1864 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1865 a handfull of images. The XML file can now be used to generate PDF, HTML
1866 and epub versions of the English manual. This is the basic step of
1867 our process, making PDF (using dblatex), HTML (using xsltproc) and
1868 epub (using dbtoepub) version from Docbook XML, and the resulting files
1869 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1870
1871 &lt;p&gt;But English documentation is not enough for us. We want translated
1872 documentation too, and we want to make it easy for translators to
1873 track the English original. For this we use the
1874 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1875 which allow us to transform the English Docbook XML file into a
1876 translation file (a .pot file), usable with the normal gettext based
1877 translation tools used by those translating free software. The pot
1878 file is used to create and maintain translation files (several .po
1879 files), which the translations update with the native language
1880 translations of all titles, paragraphs and blocks of text in the
1881 original. The next step is combining the original English Docbook XML
1882 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1883 create a translated Docbook XML file (in this case
1884 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1885 translated, if the translation is not complete) Docbook XML file can
1886 then be used like the original to create a PDF, HTML and epub version
1887 of the documentation.&lt;/p&gt;
1888
1889 &lt;p&gt;The translators use different tools to edit the .po files. We
1890 recommend using
1891 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1892 while some use emacs and vi, others can use web based editors like
1893 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1894 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1895 is where the .po file end up, in our git repository. Updated
1896 translations can either be committed directly to git, or submitted as
1897 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1898 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1899
1900 &lt;p&gt;One challenge is images, which both might need to be translated (if
1901 they show translated user applications), and are needed in different
1902 formats when creating PDF and HTML versions (epub is a HTML version in
1903 this regard). For this we transform the original PNG images to the
1904 needed density and format during build, and have a way to provide
1905 translated images by storing translated versions in
1906 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1907 package maintainers know more.&lt;/p&gt;
1908
1909 &lt;p&gt;If you wonder what the result look like, we provide
1910 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1911 of the documentation packages on the web&lt;/a&gt;. See for example the
1912 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1913 PDF version&lt;/a&gt; or the
1914 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1915 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1916 but perhaps it will be done in the future.&lt;/p&gt;
1917
1918 &lt;p&gt;To learn more, check out
1919 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1920 debian-edu-doc package&lt;/a&gt;,
1921 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1922 manual on the wiki&lt;/a&gt; and
1923 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1924 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1925 </description>
1926 </item>
1927
1928 <item>
1929 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1930 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1932 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1933 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1934 related packages relevant for the computer installed automatically.
1935 So I implemented one, using
1936 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1937 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1938 run tasksel as user root. You should be presented with a new option,
1939 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1940 select it, tasksel will install the packages isenkram claim is fit for
1941 the current hardware, hot pluggable or not.&lt;p&gt;
1942
1943 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1944 description, and the other is the script used to extract the list of
1945 packages to install. The first part is in
1946 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1947 this:&lt;/p&gt;
1948
1949 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1950 Task: isenkram
1951 Section: hardware
1952 Description: Hardware specific packages (autodetected by isenkram)
1953 Based on the detected hardware various hardware specific packages are
1954 proposed.
1955 Test-new-install: mark show
1956 Relevance: 8
1957 Packages: for-current-hardware
1958 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1959
1960 &lt;p&gt;The second part is in
1961 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1962 this:&lt;/p&gt;
1963
1964 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1965 #!/bin/sh
1966 #
1967 (
1968 isenkram-lookup
1969 isenkram-autoinstall-firmware -l
1970 ) | sort -u
1971 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1972
1973 &lt;p&gt;All in all, a very short and simple implementation making it
1974 trivial to install the hardware dependent package we all may want to
1975 have installed on our machines. I&#39;ve not been able to find a way to
1976 get tasksel to tell you exactly which packages it plan to install
1977 before doing the installation. So if you are curious or careful,
1978 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1979
1980 &lt;p&gt;The information about which packages are handling which hardware is
1981 fetched either from the isenkram package itself in
1982 /usr/share/isenkram/, from git.debian.org or from the APT package
1983 database (using the Modaliases header). The APT package database
1984 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1985 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1986 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1987 the python-apt code (bug
1988 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1989 workaround I was able to get rid of the file descriptor leak and
1990 reduce the memory leak from ~30 MiB per hardware detection down to
1991 around 2 MiB per hardware detection. It should make the desktop
1992 daemon a lot more useful. The fix is in version 0.7 uploaded to
1993 unstable today.&lt;/p&gt;
1994
1995 &lt;p&gt;I believe the current way of mapping hardware to packages in
1996 Isenkram is is a good draft, but in the future I expect isenkram to
1997 use the AppStream data source for this. A proposal for getting proper
1998 AppStream support into Debian is floating around as
1999 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
2000 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
2001 project&lt;/a&gt; will take place this summer to improve the situation. I
2002 look forward to seeing the result, and welcome patches for isenkram to
2003 start using the information when it is ready.&lt;/p&gt;
2004
2005 &lt;p&gt;If you want your package to map to some specific hardware, either
2006 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
2007 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
2008 package&lt;/a&gt; or submit a bug report with the details to the isenkram
2009 package. See also
2010 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
2011 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
2012 the information will be migrated to AppStream eventually, but for the
2013 moment I got no better place to store it.&lt;/p&gt;
2014 </description>
2015 </item>
2016
2017 <item>
2018 <title>FreedomBox milestone - all packages now in Debian Sid</title>
2019 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
2020 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
2021 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
2022 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2023 project&lt;/a&gt; is working on providing the software and hardware to make
2024 it easy for non-technical people to host their data and communication
2025 at home, and being able to communicate with their friends and family
2026 encrypted and away from prying eyes. It is still going strong, and
2027 today a major mile stone was reached.&lt;/p&gt;
2028
2029 &lt;p&gt;Today, the last of the packages currently used by the project to
2030 created the system images were accepted into Debian Unstable. It was
2031 the freedombox-setup package, which is used to configure the images
2032 during build and on the first boot. Now all one need to get going is
2033 the build code from the freedom-maker git repository and packages from
2034 Debian. And once the freedombox-setup package enter testing, we can
2035 build everything directly from Debian. :)&lt;/p&gt;
2036
2037 &lt;p&gt;Some key packages used by Freedombox are
2038 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
2039 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
2040 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
2041 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
2042 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
2043 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
2044 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
2045 are plans to integrate more packages into the setup. User
2046 documentation is maintained on the Debian wiki. Please
2047 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
2048 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
2049
2050 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
2051 setup, run this on a Debian machine using a user with sudo rights to
2052 become root:&lt;/p&gt;
2053
2054 &lt;p&gt;&lt;pre&gt;
2055 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2056 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2057 u-boot-tools
2058 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2059 freedom-maker
2060 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2061 &lt;/pre&gt;&lt;/p&gt;
2062
2063 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2064 devices. See the README in the freedom-maker git repo for more
2065 details on the build. If you do not want all three images, trim the
2066 make line. Note that the virtualbox-image target is not really
2067 virtualbox specific. It create a x86 image usable in kvm, qemu,
2068 vmware and any other x86 virtual machine environment. You might need
2069 the version of vmdebootstrap in Jessie to get the build working, as it
2070 include fixes for a race condition with kpartx.&lt;/p&gt;
2071
2072 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2073 method, boot a Debian Wheezy ISO and use this boot argument to load
2074 the preseed values:&lt;/p&gt;
2075
2076 &lt;p&gt;&lt;pre&gt;
2077 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;
2078 &lt;/pre&gt;&lt;/p&gt;
2079
2080 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
2081 it still work.&lt;/p&gt;
2082
2083 &lt;p&gt;If you wonder how to help, one task you could look at is using
2084 systemd as the boot system. It will become the default for Linux in
2085 Jessie, so we need to make sure it is usable on the Freedombox. I did
2086 a simple test a few weeks ago, and noticed dnsmasq failed to start
2087 during boot when using systemd. I suspect there are other problems
2088 too. :) To detect problems, there is a test suite included, which can
2089 be run from the plinth web interface.&lt;/p&gt;
2090
2091 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2092 us get the new release published. :) Please join us on
2093 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2094 irc.debian.org)&lt;/a&gt; and
2095 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2096 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2097 </description>
2098 </item>
2099
2100 <item>
2101 <title>S3QL, a locally mounted cloud file system - nice free software</title>
2102 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
2103 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
2104 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
2105 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
2106 solution for use at home. My requirements are simple, it must be
2107 cheap and locally encrypted (in other words, I keep the encryption
2108 keys, the storage provider do not have access to my private files).
2109 One idea me and my friends had many years ago, before the cloud
2110 storage providers showed up, was to use Google mail as storage,
2111 writing a Linux block device storing blocks as emails in the mail
2112 service provided by Google, and thus get heaps of free space. On top
2113 of this one can add encryption, RAID and volume management to have
2114 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2115 I never found time to implement such system. But the last few weeks I
2116 have looked at a system called
2117 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
2118 mounted network backed file system with the features I need.&lt;/p&gt;
2119
2120 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
2121 handling several different storage providers, any with Amazon S3,
2122 Google Drive or OpenStack API. There are heaps of such storage
2123 providers. S3QL can also use a local directory as storage, which
2124 combined with sshfs allow for file storage on any ssh server. S3QL
2125 include support for encryption, compression, de-duplication, snapshots
2126 and immutable file systems, allowing me to mount the remote storage as
2127 a local mount point, look at and use the files as if they were local,
2128 while the content is stored in the cloud as well. This allow me to
2129 have a backup that should survive fire. The file system can not be
2130 shared between several machines at the same time, as only one can
2131 mount it at the time, but any machine with the encryption key and
2132 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
2133
2134 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
2135 package is included already. So to get started, run &lt;tt&gt;apt-get
2136 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
2137 Greenqloud, after reading their nice recipe on
2138 &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
2139 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
2140 in Iceland more than those in USA when it come to keeping my personal
2141 data safe and private, and thus would rather spend money on a company
2142 in Iceland. Another nice recipe is available from the article
2143 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
2144 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
2145 Admin magazine. When the provider is picked, figure out how to get
2146 the API key needed to connect to the storage API. With Greencloud,
2147 the key did not show up until I had added payment details to my
2148 account.&lt;/p&gt;
2149
2150 &lt;p&gt;Armed with the API access details, it is time to create the file
2151 system. First, create a new bucket in the cloud. This bucket is the
2152 file system storage area. I picked a bucket name reflecting the
2153 machine that was going to store data there, but any name will do.
2154 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
2155 the API login and password, and a locally created password. Store it
2156 all in ~root/.s3ql/authinfo2 like this:
2157
2158 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2159 [s3c]
2160 storage-url: s3c://s.greenqloud.com:443/bucket-name
2161 backend-login: API-login
2162 backend-password: API-password
2163 fs-passphrase: local-password
2164 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2165
2166 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
2167 but any sensible way to create a fairly random password should do it.
2168 Armed with these details, it is now time to run mkfs, entering the API
2169 details and password to create it:&lt;/p&gt;
2170
2171 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2172 # mkdir -m 700 /var/lib/s3ql-cache
2173 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2174 --ssl s3c://s.greenqloud.com:443/bucket-name
2175 Enter backend login:
2176 Enter backend password:
2177 Before using S3QL, make sure to read the user&#39;s guide, especially
2178 the &#39;Important Rules to Avoid Loosing Data&#39; section.
2179 Enter encryption password:
2180 Confirm encryption password:
2181 Generating random encryption key...
2182 Creating metadata tables...
2183 Dumping metadata...
2184 ..objects..
2185 ..blocks..
2186 ..inodes..
2187 ..inode_blocks..
2188 ..symlink_targets..
2189 ..names..
2190 ..contents..
2191 ..ext_attributes..
2192 Compressing and uploading metadata...
2193 Wrote 0.00 MB of compressed metadata.
2194 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2195
2196 &lt;p&gt;The next step is mounting the file system to make the storage available.
2197
2198 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2199 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2200 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2201 Using 4 upload threads.
2202 Downloading and decompressing metadata...
2203 Reading metadata...
2204 ..objects..
2205 ..blocks..
2206 ..inodes..
2207 ..inode_blocks..
2208 ..symlink_targets..
2209 ..names..
2210 ..contents..
2211 ..ext_attributes..
2212 Mounting filesystem...
2213 # df -h /s3ql
2214 Filesystem Size Used Avail Use% Mounted on
2215 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
2216 #
2217 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2218
2219 &lt;p&gt;The file system is now ready for use. I use rsync to store my
2220 backups in it, and as the metadata used by rsync is downloaded at
2221 mount time, no network traffic (and storage cost) is triggered by
2222 running rsync. To unmount, one should not use the normal umount
2223 command, as this will not flush the cache to the cloud storage, but
2224 instead running the umount.s3ql command like this:
2225
2226 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2227 # umount.s3ql /s3ql
2228 #
2229 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2230
2231 &lt;p&gt;There is a fsck command available to check the file system and
2232 correct any problems detected. This can be used if the local server
2233 crashes while the file system is mounted, to reset the &quot;already
2234 mounted&quot; flag. This is what it look like when processing a working
2235 file system:&lt;/p&gt;
2236
2237 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2238 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
2239 Using cached metadata.
2240 File system seems clean, checking anyway.
2241 Checking DB integrity...
2242 Creating temporary extra indices...
2243 Checking lost+found...
2244 Checking cached objects...
2245 Checking names (refcounts)...
2246 Checking contents (names)...
2247 Checking contents (inodes)...
2248 Checking contents (parent inodes)...
2249 Checking objects (reference counts)...
2250 Checking objects (backend)...
2251 ..processed 5000 objects so far..
2252 ..processed 10000 objects so far..
2253 ..processed 15000 objects so far..
2254 Checking objects (sizes)...
2255 Checking blocks (referenced objects)...
2256 Checking blocks (refcounts)...
2257 Checking inode-block mapping (blocks)...
2258 Checking inode-block mapping (inodes)...
2259 Checking inodes (refcounts)...
2260 Checking inodes (sizes)...
2261 Checking extended attributes (names)...
2262 Checking extended attributes (inodes)...
2263 Checking symlinks (inodes)...
2264 Checking directory reachability...
2265 Checking unix conventions...
2266 Checking referential integrity...
2267 Dropping temporary indices...
2268 Backing up old metadata...
2269 Dumping metadata...
2270 ..objects..
2271 ..blocks..
2272 ..inodes..
2273 ..inode_blocks..
2274 ..symlink_targets..
2275 ..names..
2276 ..contents..
2277 ..ext_attributes..
2278 Compressing and uploading metadata...
2279 Wrote 0.89 MB of compressed metadata.
2280 #
2281 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2282
2283 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2284 quick, about the same speed as local file access. Uploading large
2285 amount of data is to me limited by the bandwidth out of and into my
2286 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2287 which is very close to my upload speed, and downloading the same
2288 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2289 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2290 network, not the file system code. I do not know what a good cache
2291 size would be, but suspect that the cache should e larger than your
2292 working set.&lt;/p&gt;
2293
2294 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2295 time. If another machine try, it is told that the file system is
2296 busy:&lt;/p&gt;
2297
2298 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2299 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2300 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2301 Using 8 upload threads.
2302 Backend reports that fs is still mounted elsewhere, aborting.
2303 #
2304 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2305
2306 &lt;p&gt;The file content is uploaded when the cache is full, while the
2307 metadata is uploaded once every 24 hour by default. To ensure the
2308 file system content is flushed to the cloud, one can either umount the
2309 file system, or ask S3QL to flush the cache and metadata using
2310 s3qlctrl:
2311
2312 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2313 # s3qlctrl upload-meta /s3ql
2314 # s3qlctrl flushcache /s3ql
2315 #
2316 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2317
2318 &lt;p&gt;If you are curious about how much space your data uses in the
2319 cloud, and how much compression and deduplication cut down on the
2320 storage usage, you can use s3qlstat on the mounted file system to get
2321 a report:&lt;/p&gt;
2322
2323 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2324 # s3qlstat /s3ql
2325 Directory entries: 9141
2326 Inodes: 9143
2327 Data blocks: 8851
2328 Total data size: 22049.38 MB
2329 After de-duplication: 21955.46 MB (99.57% of total)
2330 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2331 Database size: 2.39 MB (uncompressed)
2332 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2333 #
2334 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2335
2336 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2337 storage. I did not try to locate them all, but am aware of at least
2338 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2339 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2340 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2341 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2342 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2343 accept payment in Bitcoin. Pick one that suit your need. Some of
2344 them provide several GiB of free storage, but the prize models are
2345 quite different and you will have to figure out what suits you
2346 best.&lt;/p&gt;
2347
2348 &lt;p&gt;While researching this blog post, I had a look at research papers
2349 and posters discussing the S3QL file system. There are several, which
2350 told me that the file system is getting a critical check by the
2351 science community and increased my confidence in using it. One nice
2352 poster is titled
2353 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2354 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2355 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2356 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2357 and Pamela Smith. Please have a look.&lt;/p&gt;
2358
2359 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2360 check out the mounted S3QL file system to see if it would be usable as
2361 a home directory (in other word, that it provided POSIX semantics when
2362 it come to locking and umask handling etc). Running
2363 &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
2364 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2365 no error was found. So the file system can be used for home
2366 directories, if one chooses to do so.&lt;/p&gt;
2367
2368 &lt;p&gt;If you do not want a locally file system, and want something that
2369 work without the Linux fuse file system, I would like to mention the
2370 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2371 provide locally encrypted backup using a command line client. It have
2372 a nicer access control system, where one can split out read and write
2373 access, allowing some systems to write to the backup and others to
2374 only read from it.&lt;/p&gt;
2375
2376 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2377 activities, please send Bitcoin donations to my address
2378 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2379 </description>
2380 </item>
2381
2382 <item>
2383 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2384 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2386 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2387 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2388 project&lt;/a&gt; is working on providing the software and hardware for
2389 making it easy for non-technical people to host their data and
2390 communication at home, and being able to communicate with their
2391 friends and family encrypted and away from prying eyes. It has been
2392 going on for a while, and is slowly progressing towards a new test
2393 release (0.2).&lt;/p&gt;
2394
2395 &lt;p&gt;And what day could be better than the Pi day to announce that the
2396 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2397 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2398 system), and can also be installed using a Debian installer preseed
2399 file. The Debian based Freedombox is now based on Debian Jessie,
2400 where most of the needed packages used are already present. Only one,
2401 the freedombox-setup package, is missing. To try to build your own
2402 boot image to test the current status, fetch the freedom-maker scripts
2403 and build using
2404 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2405 with a user with sudo access to become root:
2406
2407 &lt;pre&gt;
2408 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2409 freedom-maker
2410 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2411 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2412 u-boot-tools
2413 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2414 &lt;/pre&gt;
2415
2416 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2417 devices. See the README for more details on the build. If you do not
2418 want all three images, trim the make line. But note that thanks to &lt;a
2419 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2420 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2421 kpartx call.&lt;/p&gt;
2422
2423 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2424 method, boot a Debian Wheezy ISO and use this boot argument to load
2425 the preseed values:&lt;/p&gt;
2426
2427 &lt;pre&gt;
2428 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;
2429 &lt;/pre&gt;
2430
2431 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2432 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2433 currently hang while setting up APT sources. Killing the
2434 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2435 installation will get the installation going. This affect all
2436 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2437
2438 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2439 us get the new release published. :) Please join us on
2440 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2441 irc.debian.org)&lt;/a&gt; and
2442 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2443 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2444 </description>
2445 </item>
2446
2447 <item>
2448 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2449 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2451 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2452 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2453 innetgr tools, because I needed them in
2454 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2455 ng-utils, and it has served me well. I placed the project under the
2456 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2457 repository. But many years ago, the CVS repository was dropped (lost,
2458 not migrated to new hardware, not sure), and the project have lacked a
2459 proper home since then.&lt;/p&gt;
2460
2461 &lt;p&gt;Last summer, I had a look at the package and made a new release
2462 fixing a irritating crash bug, but was unable to store the changes in
2463 a proper source control system. I applied for a project on
2464 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2465 to follow up on it. Until today. :)&lt;/p&gt;
2466
2467 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2468 now have a new home, and a git repository with the highlight of the
2469 history of the project. I published all release tarballs and imported
2470 them into the git repository. As the project is really stable and not
2471 expected to gain new features any time soon, I decided to make a new
2472 release and call it 1.0. Visit the new project home on
2473 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2474 if you want to check it out. The new version is also uploaded into
2475 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2476 </description>
2477 </item>
2478
2479 <item>
2480 <title>Testing sysvinit from experimental in Debian Hurd</title>
2481 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2482 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2483 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2484 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2485 their changes into sysvinit, to allow them to use the normal sysvinit
2486 boot system instead of their old one. This follow up on the
2487 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2488 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2489 get Debian on Hurd working more like Debian on Linux. To get started,
2490 I downloaded a prebuilt hard disk image from
2491 &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;,
2492 and started it using virt-manager.&lt;/p&gt;
2493
2494 &lt;p&gt;The first think I had to do after logging in (root without any
2495 password) was to get the network operational. I followed
2496 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2497 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2498 commands as root to get the machine to accept a IP address from the
2499 kvm internal DHCP server:&lt;/p&gt;
2500
2501 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2502 settrans -fgap /dev/netdde /hurd/netdde
2503 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2504 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2505 dhclient /dev/eth0
2506 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2507
2508 &lt;p&gt;After this, the machine had internet connectivity, and I could
2509 upgrade it and install the sysvinit packages from experimental and
2510 enable it as the default boot system in Hurd.&lt;/p&gt;
2511
2512 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2513 running on the machine it for ssh login to work a password need to be
2514 set. Also, note that a bug somewhere in openssh on Hurd block
2515 compression from working. Remember to turn that off on the client
2516 side.&lt;/p&gt;
2517
2518 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2519 stuff:&lt;/p&gt;
2520
2521 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2522 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2523 deb http://http.debian.net/debian/ experimental main
2524 EOF
2525 apt-get update
2526 apt-get dist-upgrade
2527 apt-get install -t experimental initscripts sysv-rc sysvinit \
2528 sysvinit-core sysvinit-utils
2529 update-alternatives --config runsystem
2530 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2531
2532 &lt;p&gt;To reboot after switching boot system, you have to use
2533 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2534 yet a sysvinit process able to receive the signals from the normal
2535 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2536 upgrading every package and rebooting, the network come up with DHCP
2537 after boot as it should, and the settrans/pkill hack mentioned at the
2538 start is no longer needed. But for some strange reason, there are no
2539 longer any login prompt in the virtual console, so I logged in using
2540 ssh instead.
2541
2542 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2543 fail some times. No idea what the cause is, but hope the Hurd porters
2544 figure it out. At least Justus said on IRC (#debian-hurd on
2545 irc.debian.org) that they are aware of the problem. A way to reduce
2546 the impact is to upgrade to the Hurd packages built by Justus by
2547 adding this repository to the machine:&lt;/p&gt;
2548
2549 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2550 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2551 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2552 EOF
2553 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2554
2555 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2556 http://ftp.debian-ports.org/debian, because some of the packages in
2557 unstable do not yet include the required patches that are lingering in
2558 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2559
2560 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2561 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2562 i emacs - GNU Emacs editor (metapackage)
2563 i gdb - GNU Debugger
2564 i hurd-recommended - Miscellaneous translators
2565 i isc-dhcp-client - ISC DHCP client
2566 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2567 i libc-bin - Embedded GNU C Library: Binaries
2568 i libc-dev-bin - Embedded GNU C Library: Development binaries
2569 i libc0.3 - Embedded GNU C Library: Shared libraries
2570 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2571 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2572 i multiarch-support - Transitional package to ensure multiarch compatibilit
2573 i A x11-common - X Window System (X.Org) infrastructure
2574 i xorg - X.Org X Window System
2575 i A xserver-xorg - X.Org X server
2576 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2577 #
2578 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2579
2580 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2581 X.org did not work out of the box and I never took the time to follow
2582 the porters instructions to fix it. This time I was interested in the
2583 command line stuff.&lt;p&gt;
2584 </description>
2585 </item>
2586
2587 <item>
2588 <title>New chrpath release 0.16</title>
2589 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2590 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2591 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2592 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2593 find problems in C, C++ and Java code using static source code
2594 analysis. It can detect a lot of different problems, and is very
2595 useful to find memory and locking bugs in the error handling part of
2596 the source. The company behind it provide
2597 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2598 a community service&lt;/a&gt;, and many hundred free software projects are
2599 already checked. A few days ago I decided to have a closer look at
2600 the Coverity system, and discovered that the
2601 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2602 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2603 projects I am involved with was already registered. But these are
2604 fairly big, and I would also like to have a small and easy project to
2605 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2606 checking of the chrpath project&lt;/a&gt;. It was
2607 added to the checker and discovered seven potential defects. Six of
2608 these were real, mostly resource &quot;leak&quot; when the program detected an
2609 error. Nothing serious, as the resources would be released a fraction
2610 of a second later when the program exited because of the error, but it
2611 is nice to do it right in case the source of the program some time in
2612 the future end up in a library. Having fixed all defects and added
2613 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2614 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2615 publish a new release. These are the release notes:&lt;/p&gt;
2616
2617 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2618
2619 &lt;ul&gt;
2620
2621 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2622 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2623 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2624
2625 &lt;/ul&gt;
2626
2627 &lt;p&gt;You can
2628 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2629 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2630 project if something is wrong with the new release. The test suite
2631 did not discover any old errors, so if you find a new one, please also
2632 include a test suite check.&lt;/p&gt;
2633 </description>
2634 </item>
2635
2636 <item>
2637 <title>New chrpath release 0.15</title>
2638 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2639 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2640 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2641 <description>&lt;p&gt;After many years break from the package and a vain hope that
2642 development would be continued by someone else, I finally pulled my
2643 acts together this morning and wrapped up a new release of chrpath,
2644 the command line tool to modify the rpath and runpath of already
2645 compiled ELF programs. The update was triggered by the persistence of
2646 Isha Vishnoi at IBM, which needed a new config.guess file to get
2647 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2648 is working on. I checked the
2649 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2650 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2651 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2652 packages for interesting patches (failed to find the source from
2653 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2654 These are the release notes:&lt;/p&gt;
2655
2656 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2657
2658 &lt;ul&gt;
2659
2660 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2661 with newer architectures. Thanks to isha vishnoi for the heads
2662 up.&lt;/li&gt;
2663
2664 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2665
2666 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2667 Matthias Klose.&lt;/li&gt;
2668
2669 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2670 Petr Machata found in Fedora.&lt;/li&gt;
2671
2672 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2673 .dynamic is a NULL terminated string. Based on patch found in
2674 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2675
2676 &lt;/ul&gt;
2677
2678 &lt;p&gt;You can
2679 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2680 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2681 project if something is wrong with the new release. The test suite
2682 did not discover any old errors, so if you find a new one, please also
2683 include a testsuite check.&lt;/p&gt;
2684 </description>
2685 </item>
2686
2687 <item>
2688 <title>Debian init.d boot script example for rsyslog</title>
2689 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2690 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2691 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2692 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2693 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2694 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2695 init.d scripts at all. Here is an example init.d script, ie a rewrite
2696 of /etc/init.d/rsyslog:&lt;/p&gt;
2697
2698 &lt;p&gt;&lt;pre&gt;
2699 #!/lib/init/init-d-script
2700 ### BEGIN INIT INFO
2701 # Provides: rsyslog
2702 # Required-Start: $remote_fs $time
2703 # Required-Stop: umountnfs $time
2704 # X-Stop-After: sendsigs
2705 # Default-Start: 2 3 4 5
2706 # Default-Stop: 0 1 6
2707 # Short-Description: enhanced syslogd
2708 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2709 # It is quite compatible to stock sysklogd and can be
2710 # used as a drop-in replacement.
2711 ### END INIT INFO
2712 DESC=&quot;enhanced syslogd&quot;
2713 DAEMON=/usr/sbin/rsyslogd
2714 &lt;/pre&gt;&lt;/p&gt;
2715
2716 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2717 script was 137 lines, and the above is just 15 lines, most of it meta
2718 info/comments.&lt;/p&gt;
2719
2720 &lt;p&gt;How to do this, you ask? Well, one create a new script
2721 /lib/init/init-d-script looking something like this:
2722
2723 &lt;p&gt;&lt;pre&gt;
2724 #!/bin/sh
2725
2726 # Define LSB log_* functions.
2727 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2728 # and status_of_proc is working.
2729 . /lib/lsb/init-functions
2730
2731 #
2732 # Function that starts the daemon/service
2733
2734 #
2735 do_start()
2736 {
2737 # Return
2738 # 0 if daemon has been started
2739 # 1 if daemon was already running
2740 # 2 if daemon could not be started
2741 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2742 || return 1
2743 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2744 $DAEMON_ARGS \
2745 || return 2
2746 # Add code here, if necessary, that waits for the process to be ready
2747 # to handle requests from services started subsequently which depend
2748 # on this one. As a last resort, sleep for some time.
2749 }
2750
2751 #
2752 # Function that stops the daemon/service
2753 #
2754 do_stop()
2755 {
2756 # Return
2757 # 0 if daemon has been stopped
2758 # 1 if daemon was already stopped
2759 # 2 if daemon could not be stopped
2760 # other if a failure occurred
2761 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2762 RETVAL=&quot;$?&quot;
2763 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2764 # Wait for children to finish too if this is a daemon that forks
2765 # and if the daemon is only ever run from this initscript.
2766 # If the above conditions are not satisfied then add some other code
2767 # that waits for the process to drop all resources that could be
2768 # needed by services started subsequently. A last resort is to
2769 # sleep for some time.
2770 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2771 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2772 # Many daemons don&#39;t delete their pidfiles when they exit.
2773 rm -f $PIDFILE
2774 return &quot;$RETVAL&quot;
2775 }
2776
2777 #
2778 # Function that sends a SIGHUP to the daemon/service
2779 #
2780 do_reload() {
2781 #
2782 # If the daemon can reload its configuration without
2783 # restarting (for example, when it is sent a SIGHUP),
2784 # then implement that here.
2785 #
2786 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2787 return 0
2788 }
2789
2790 SCRIPTNAME=$1
2791 scriptbasename=&quot;$(basename $1)&quot;
2792 echo &quot;SN: $scriptbasename&quot;
2793 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2794 script=&quot;$1&quot;
2795 shift
2796 . $script
2797 else
2798 exit 0
2799 fi
2800
2801 NAME=$(basename $DAEMON)
2802 PIDFILE=/var/run/$NAME.pid
2803
2804 # Exit if the package is not installed
2805 #[ -x &quot;$DAEMON&quot; ] || exit 0
2806
2807 # Read configuration variable file if it is present
2808 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2809
2810 # Load the VERBOSE setting and other rcS variables
2811 . /lib/init/vars.sh
2812
2813 case &quot;$1&quot; in
2814 start)
2815 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2816 do_start
2817 case &quot;$?&quot; in
2818 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2819 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2820 esac
2821 ;;
2822 stop)
2823 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2824 do_stop
2825 case &quot;$?&quot; in
2826 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2827 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2828 esac
2829 ;;
2830 status)
2831 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2832 ;;
2833 #reload|force-reload)
2834 #
2835 # If do_reload() is not implemented then leave this commented out
2836 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2837 #
2838 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2839 #do_reload
2840 #log_end_msg $?
2841 #;;
2842 restart|force-reload)
2843 #
2844 # If the &quot;reload&quot; option is implemented then remove the
2845 # &#39;force-reload&#39; alias
2846 #
2847 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2848 do_stop
2849 case &quot;$?&quot; in
2850 0|1)
2851 do_start
2852 case &quot;$?&quot; in
2853 0) log_end_msg 0 ;;
2854 1) log_end_msg 1 ;; # Old process is still running
2855 *) log_end_msg 1 ;; # Failed to start
2856 esac
2857 ;;
2858 *)
2859 # Failed to stop
2860 log_end_msg 1
2861 ;;
2862 esac
2863 ;;
2864 *)
2865 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2866 exit 3
2867 ;;
2868 esac
2869
2870 :
2871 &lt;/pre&gt;&lt;/p&gt;
2872
2873 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2874 lot. I did not really polish the approach, so it might not always
2875 work out of the box, but you get the idea. I did not try very hard to
2876 optimize it nor make it more robust either.&lt;/p&gt;
2877
2878 &lt;p&gt;A better argument for switching init system in Debian than reducing
2879 the size of init scripts (which is a good thing to do anyway), is to
2880 get boot system that is able to handle the kernel events sensibly and
2881 robustly, and do not depend on the boot to run sequentially. The boot
2882 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2883 </description>
2884 </item>
2885
2886 <item>
2887 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2888 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2890 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2891 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2892 remote display access is the preferred solution with oVirt and RedHat
2893 Enterprise Virtualization, and I was sad to discover the other day
2894 that the browser plugin needed to use these systems seamlessly was
2895 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2896 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2897 2013-04-01, so I decided to wrap up a package based on the great work
2898 from Cajus Pollmeier and put it in a collab-maint maintained git
2899 repository to get a package I could use. I would very much like
2900 others to help me maintain the package (or just take over, I do not
2901 mind), but as no-one had volunteered so far, I just uploaded it to
2902 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2903
2904 &lt;p&gt;The source is now available from
2905 &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;
2906 </description>
2907 </item>
2908
2909 <item>
2910 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2911 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2912 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2913 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2914 <description>&lt;p&gt;The
2915 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2916 program is a a very nice system to create virtual machine images. It
2917 create a image file, add a partition table, mount it and run
2918 debootstrap in the mounted directory to create a Debian system on a
2919 stick. Yesterday, I decided to try to teach it how to make images for
2920 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2921 of a plan to simplify the build system for
2922 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2923 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2924 the virtualbox images, but its current build system made multistrap
2925 based system for Dreamplug images, and it is lacking support for
2926 Raspberry Pi.&lt;/p&gt;
2927
2928 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2929 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2930 code and adjusted it to be able to build armel images on my amd64
2931 Debian laptop. I ended up giving vmdebootstrap five new options,
2932 allowing me to replicate the image creation process I use to make
2933 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2934 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2935 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2936 call debootstrap with --foreign and to copy the handler into the
2937 generated chroot before running the second stage. This allow
2938 vmdebootstrap to create armel images on an amd64 host. Next I added
2939 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2940 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2941 given file system type, allowing me to create an image with a vfat
2942 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2943 variant&lt;/tt&gt; option to allow me to create smaller images without the
2944 Debian base system packages installed. Finally, I added an option
2945 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2946 as a boot loader. It is not needed on the Raspberry Pi and probably
2947 most other non-x86 architectures. The changes were accepted by the
2948 upstream author of vmdebootstrap yesterday and today, and is now
2949 available from
2950 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2951 upstream project page&lt;/a&gt;.&lt;/p&gt;
2952
2953 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2954 create a small script (the customize script) to add the non-free
2955 binary blob needed to boot the Raspberry Pi and the APT source
2956 list:&lt;/p&gt;
2957
2958 &lt;p&gt;&lt;pre&gt;
2959 #!/bin/sh
2960 set -e # Exit on first error
2961 rootdir=&quot;$1&quot;
2962 cd &quot;$rootdir&quot;
2963 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2964 deb http://http.debian.net/debian/ jessie main contrib non-free
2965 EOF
2966 # Install non-free binary blob needed to boot Raspberry Pi. This
2967 # install a kernel somewhere too.
2968 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2969 -O $rootdir/usr/bin/rpi-update
2970 chmod a+x $rootdir/usr/bin/rpi-update
2971 mkdir -p $rootdir/lib/modules
2972 touch $rootdir/boot/start.elf
2973 chroot $rootdir rpi-update
2974 &lt;/pre&gt;&lt;/p&gt;
2975
2976 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2977 to build the image:&lt;/p&gt;
2978
2979 &lt;pre&gt;
2980 sudo ./vmdebootstrap \
2981 --variant minbase \
2982 --arch armel \
2983 --distribution jessie \
2984 --mirror http://http.debian.net/debian \
2985 --image test.img \
2986 --size 600M \
2987 --bootsize 64M \
2988 --boottype vfat \
2989 --log-level debug \
2990 --verbose \
2991 --no-kernel \
2992 --no-extlinux \
2993 --root-password raspberry \
2994 --hostname raspberrypi \
2995 --foreign /usr/bin/qemu-arm-static \
2996 --customize `pwd`/customize \
2997 --package netbase \
2998 --package git-core \
2999 --package binutils \
3000 --package ca-certificates \
3001 --package wget \
3002 --package kmod
3003 &lt;/pre&gt;&lt;/p&gt;
3004
3005 &lt;p&gt;The list of packages being installed are the ones needed by
3006 rpi-update to make the image bootable on the Raspberry Pi, with the
3007 exception of netbase, which is needed by debootstrap to find
3008 /etc/hosts with the minbase variant. I really wish there was a way to
3009 set up an Raspberry Pi using only packages in the Debian archive, but
3010 that is not possible as far as I know, because it boots from the GPU
3011 using a non-free binary blob.&lt;/p&gt;
3012
3013 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
3014 probably a few others installed. I have not checked the complete
3015 build dependency list.&lt;/p&gt;
3016
3017 &lt;p&gt;The resulting image will not use the hardware floating point unit
3018 on the Raspberry PI, because the armel architecture in Debian is not
3019 optimized for that use. So the images created will be a bit slower
3020 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
3021 </description>
3022 </item>
3023
3024 <item>
3025 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
3026 <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>
3027 <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>
3028 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
3029 <description>&lt;p&gt;The last few days I came across a few good causes that should get
3030 wider attention. I recommend signing and donating to each one of
3031 these. :)&lt;/p&gt;
3032
3033 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
3034 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
3035 Women program which is a Google Summer of Code like initiative to get
3036 more women involved in free software. One debian sponsor has offered
3037 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
3038 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
3039 hope you will to. :)&lt;/p&gt;
3040
3041 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
3042 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
3043 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
3044 take place these days, and their need to fund the work. I&#39;ve already
3045 donated. Are you next?&lt;/p&gt;
3046
3047 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
3048 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3049 statement under the heading
3050 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
3051 Access&lt;/a&gt; for those of us asking for more focus on open access in the
3052 Norwegian government. So far 499 signatures. I hope you will sign it
3053 too.&lt;/p&gt;
3054 </description>
3055 </item>
3056
3057 <item>
3058 <title>Videos about the Freedombox project - for inspiration and learning</title>
3059 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
3060 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
3061 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
3062 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
3063 project&lt;/a&gt; have been going on for a while, and have presented the
3064 vision, ideas and solution several places. Here is a little
3065 collection of videos of talks and presentation of the project.&lt;/p&gt;
3066
3067 &lt;ul&gt;
3068
3069 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
3070 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
3071
3072 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
3073 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3074
3075 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
3076 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3077 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
3078 (Youtube)&lt;/li&gt;
3079
3080 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
3081 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
3082
3083 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
3084 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3085
3086 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
3087 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3088 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
3089
3090 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
3091 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
3092 (Youtube)&lt;/li&gt;
3093
3094 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
3095 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
3096
3097 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
3098 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
3099
3100 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
3101 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3102 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
3103
3104 &lt;/ul&gt;
3105
3106 &lt;p&gt;A larger list is available from
3107 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
3108 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
3109
3110 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
3111 Jessie is coming along quite well, and soon both Owncloud and using
3112 Tor should be available for testers of the Freedombox solution. :) In
3113 a few weeks I hope everything needed to test it is included in Debian.
3114 The withsqlite package is already in Debian, and the plinth package is
3115 pending in NEW. The third and vital part of that puzzle is the
3116 metapackage/setup framework, which is still pending an upload. Join
3117 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
3118 (#freedombox on irc.debian.org)&lt;/a&gt; and
3119 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3120 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3121 </description>
3122 </item>
3123
3124 <item>
3125 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
3126 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
3127 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
3128 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
3129 <description>&lt;p&gt;I was introduced to the
3130 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
3131 in 2010, when Eben Moglen presented his vision about serving the need
3132 of non-technical people to keep their personal information private and
3133 within the legal protection of their own homes. The idea is to give
3134 people back the power over their network and machines, and return
3135 Internet back to its intended peer-to-peer architecture. Instead of
3136 depending on a central service, the Freedombox will give everyone
3137 control over their own basic infrastructure.&lt;/p&gt;
3138
3139 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
3140 taken priority. But this summers nasty news about the misuse of trust
3141 and privilege exercised by the &quot;western&quot; intelligence gathering
3142 communities increased my eagerness to contribute to a point where I
3143 actually started working on the project a while back.&lt;/p&gt;
3144
3145 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
3146 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
3147 create a simple and cheap Debian based appliance that anyone can hook
3148 up in their home and get access to secure and private services and
3149 communication. The initial deployment platform have been the
3150 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
3151 which is a piece of hardware I do not own. So to be able to test what
3152 the current Freedombox setup look like, I had to come up with a way to install
3153 it on some hardware I do have access to. I have rewritten the
3154 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
3155 image build framework to use .deb packages instead of only copying
3156 setup into the boot images, and thanks to this rewrite I am able to
3157 set up any machine supported by Debian Wheezy as a Freedombox, using
3158 the previously mentioned deb (and a few support debs for packages
3159 missing in Debian).&lt;/p&gt;
3160
3161 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
3162 scripts
3163 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
3164 and a administrative web interface
3165 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
3166 withsqlite), as well as a privacy enhancing proxy based on
3167 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
3168 (freedombox-privoxy). There is also a web/javascript based XMPP
3169 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
3170 trying (unsuccessfully so far) to talk to the XMPP server
3171 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
3172 web interface is pluggable, and the goal is to use it to enable OpenID
3173 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3174 this is really working yet, see
3175 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
3176 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
3177 on github at the moment. The HTTP proxy is operational out of the
3178 box, and the admin web interface can be used to add/remove plinth
3179 users. I&#39;ve not been able to do anything else with it so far, but
3180 know there are several branches spread around github and other places
3181 with lots of half baked features.&lt;/p&gt;
3182
3183 &lt;p&gt;Anyway, if you want to have a look at the current state, the
3184 following recipes should work to give you a test machine to poke
3185 at.&lt;/p&gt;
3186
3187 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
3188
3189 &lt;ol&gt;
3190
3191 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
3192 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
3193 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
3194 to the Debian installer:&lt;p&gt;
3195 &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;
3196
3197 &lt;li&gt;Answer the few language/region/password questions and pick disk to
3198 install on.&lt;/li&gt;
3199
3200 &lt;li&gt;When the installation is finished and the machine have rebooted a
3201 few times, your Freedombox is ready for testing.&lt;/li&gt;
3202
3203 &lt;/ol&gt;
3204
3205 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
3206
3207 &lt;ol&gt;
3208
3209 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
3210 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
3211 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
3212 &lt;pre&gt;
3213 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
3214 &lt;/pre&gt;&lt;/li&gt;
3215 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
3216 &lt;pre&gt;
3217 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3218 apt-key add -
3219 apt-get update
3220 apt-get install freedombox-setup
3221 /usr/lib/freedombox/setup
3222 &lt;/pre&gt;&lt;/li&gt;
3223 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
3224
3225 &lt;/ol&gt;
3226
3227 &lt;p&gt;You can test it on other architectures too, but because the
3228 freedombox-privoxy package is binary, it will only work as intended on
3229 the architectures where I have had time to build the binary and put it
3230 in my APT repository. But do not let this stop you. It is only a
3231 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
3232
3233 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
3234 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
3235 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
3236 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
3237
3238 &lt;p&gt;Please let me know if this works for you, or if you have any
3239 problems. We gather on the IRC channel
3240 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
3241 irc.debian.org and the
3242 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
3243 mailing list&lt;/a&gt;.&lt;/p&gt;
3244
3245 &lt;p&gt;Once you get your freedombox operational, you can visit
3246 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
3247 welcome screen (dead end - do not be surprised if you are unable to
3248 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
3249 to look at the rest of plinth. The default user is &#39;admin&#39; and the
3250 default password is &#39;secret&#39;.&lt;/p&gt;
3251 </description>
3252 </item>
3253
3254 <item>
3255 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
3256 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3257 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3258 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3259 <description>&lt;p&gt;Earlier, I reported about
3260 &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
3261 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3262 told by IBM that the original disk should be thrown away. And as
3263 there no longer was a problem if I bricked the firmware, I decided
3264 today to try to install Intel firmware to replace the Lenovo firmware
3265 currently on the disk.&lt;/p&gt;
3266
3267 &lt;p&gt;I searched the Intel site for firmware, and found
3268 &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;
3269 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3270 according to the site should contain the latest firmware for SSD
3271 disks. I inserted the broken disk in one of my spare laptops and
3272 booted the ISO from a USB stick. The disk was recognized, but the
3273 program claimed the newest firmware already were installed and refused
3274 to insert any Intel firmware. So no change, and the disk is still
3275 unable to handle write load. :( I guess the only way to get them
3276 working would be if Lenovo releases new firmware. No idea how likely
3277 that is. Anyway, just blogging about this test for completeness. I
3278 got a working Samsung disk, and see no point in spending more time on
3279 the broken disks.&lt;/p&gt;
3280 </description>
3281 </item>
3282
3283 <item>
3284 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3285 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3286 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3287 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3288 <description>&lt;p&gt;Today I switched to
3289 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3290 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3291 my new Thinkpad X230, which was delivered with an
3292 &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
3293 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3294 sustained writes. My hardware supplier have been very forthcoming in
3295 trying to find a solution, and after first trying with another
3296 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3297 disk instead to fix it once and for all. The Samsung disk survived
3298 the installation of Debian with encrypted disks (filling the disk with
3299 random data during installation killed the first two), and I thus
3300 decided to trust it with my data. I have installed it as a Debian Edu
3301 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3302 server at home using Kerberos and LDAP, and will use it as my work
3303 station from now on.&lt;/p&gt;
3304
3305 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3306 Debian Wheezy default installation need to be tuned a bit to increase
3307 performance and increase life time of the disk. The Linux kernel and
3308 user space applications do not yet adjust automatically to such
3309 environment. To make it easier for my self, I created a draft Debian
3310 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3311 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3312 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3313 is set up to adjust the setup of the machine by just installing the
3314 package. If there is any non-SSD disk in the machine, the package
3315 will refuse to install, as I did not try to write any logic to sort
3316 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3317
3318 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3319 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3320 where I set up the machine with one large encrypted partition (in
3321 addition to /boot), put LVM on top of this and set up partitions on
3322 top of this again. See the README file in the package source for the
3323 references I used to pick the settings. At the moment these
3324 parameters are tuned:&lt;/p&gt;
3325
3326 &lt;ul&gt;
3327
3328 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3329 (adding discard to /etc/crypttab)&lt;/li&gt;
3330
3331 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3332 this case a cryptsetup partition) by changing issue_discards from
3333 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3334
3335 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3336 systems.&lt;/li&gt;
3337
3338 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3339 /etc/fstab.&lt;/li&gt;
3340
3341 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3342
3343 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3344 cron.daily).&lt;/li&gt;
3345
3346 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3347 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3348
3349 &lt;/ul&gt;
3350
3351 &lt;p&gt;During installation, I cancelled the part where the installer fill
3352 the disk with random data, as this would kill the SSD performance for
3353 little gain. My goal with the encrypted file system is to ensure
3354 those stealing my laptop end up with a brick and not a working
3355 computer. I have no hope in keeping the really resourceful people
3356 from getting the data on the disk (see
3357 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3358 Thus I concluded that adding the discard option to crypttab is the
3359 right thing to do.&lt;/p&gt;
3360
3361 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3362 it for SSD, but others recommended deadline and a benchmark I found
3363 indicated that deadline might be better for interactive use.&lt;/p&gt;
3364
3365 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3366 and ext4, but read that it would give a performance hit ever time a
3367 file is removed, and thought it best to that that slowdown once a day
3368 instead of during my work.&lt;/p&gt;
3369
3370 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3371 this is already done by Debian Edu.&lt;/p&gt;
3372
3373 &lt;p&gt;I have not yet started on the user space tuning. I expect
3374 iceweasel need some tuning, and perhaps other applications too, but
3375 have not yet had time to investigate those parts.&lt;/p&gt;
3376
3377 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3378 there.&lt;/p&gt;
3379
3380 &lt;p&gt;As for the answer to the question in the title of this blog post,
3381 as far as I know, the only solution I know about is to replace the
3382 disk. It might be possible to flash it with Intel firmware instead of
3383 the Lenovo firmware. But I have not tried and did not want to do so
3384 without approval from Lenovo as I wanted to keep the warranty on the
3385 disk until a solution was found and they wanted the broken disks
3386 back.&lt;/p&gt;
3387 </description>
3388 </item>
3389
3390 <item>
3391 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3392 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3393 <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>
3394 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3395 <description>&lt;p&gt;A few days ago, I wrote about
3396 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3397 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3398 was dying during installation because it is unable to cope with
3399 sustained write. My supplier is in contact with
3400 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3401 replacement disk to try to fix the problem. They decided to send an
3402 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3403
3404 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3405 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3406 same firmware version as the original. This time my hope raised
3407 slightly as the installation progressed, as the original disk used to
3408 die after 4-7% of the disk was written to, while this time it kept
3409 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3410 died again and I was back on square one. I still do not have a new
3411 laptop with a disk I can trust. I can not live with a disk that might
3412 lock up when I download a new
3413 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3414 other large files. I look forward to hearing from my supplier with
3415 the next proposal from Lenovo.&lt;/p&gt;
3416
3417 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3418 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3419 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3420 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3421 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3422 P/N 45N8295, P0C38732.&lt;/p&gt;
3423
3424 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3425 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3426 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3427 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3428 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3429 P/N 45N8295, P0C38732.&lt;/p&gt;
3430
3431 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3432 SA, date and WNPP values. Mentioning all the details here in case
3433 someone is able to use the information to find a way to identify the
3434 failing disk among working ones (if any such working disk actually
3435 exist).&lt;/p&gt;
3436 </description>
3437 </item>
3438
3439 <item>
3440 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3441 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3442 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3443 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3444 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3445 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3446 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3447 member assosiation NUUG&lt;/a&gt; and
3448 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3449 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3450 Bitraf&lt;/a&gt;.&lt;/p&gt;
3451
3452 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3453 welcome, and there is no fee to participate. There is on the other
3454 hand limited space, and only room for 30 people. Please put your name
3455 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3456 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3457 </description>
3458 </item>
3459
3460 <item>
3461 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3462 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3463 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3464 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3465 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3466 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3467 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3468 time to spend on it, and it took a while to find a model I believe
3469 will do the job, but two days ago the replacement finally arrived. I
3470 ended up picking a
3471 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3472 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3473 a roaming workstation, and it seemed to work flawlessly. But my
3474 second installation with encrypted disk was not as successful. More
3475 on that below.&lt;/p&gt;
3476
3477 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3478 important requirements (robust and with a good keyboard) are never
3479 listed in the feature list. But I did get good help from the search
3480 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3481 allowed me to limit the list of interesting laptops based on my other
3482 requirements. A bit surprising that SSD disk are not disks according
3483 to that search interface, so I had to drop specifying the number of
3484 disks from my search parameters. I also asked around among friends to
3485 get their impression on keyboards and robustness.&lt;/p&gt;
3486
3487 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3488 X41. I am not quite convinced about the keyboard, as it is
3489 significantly wider than my old keyboard, and I have to stretch my
3490 hand a lot more to reach the edges. But the key response is fairly
3491 good and the individual key shape is fairly easy to handle, so I hope
3492 I will get used to it. My old X40 was starting to fail, and I really
3493 needed a new laptop now. :)&lt;/p&gt;
3494
3495 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3496 visit to the BIOS during boot it disable it.&lt;/p&gt;
3497
3498 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3499 lock up during load. And this happen when installing Debian Wheezy
3500 with encrypted disk, while the disk is being filled with random data.
3501 I also tested to install Ubuntu Raring, and it happen there too if I
3502 reenable the code to fill the disk with random data (it is disabled by
3503 default in Ubuntu). And the bug with is already known. It was
3504 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3505 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3506 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3507 kernel developers as
3508 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3509 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3510 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3511 Lenovo forums, both for
3512 &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
3513 2012-11-10&lt;/a&gt; and for
3514 &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
3515 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3516 reports state that the disk lock up during use if many writes are done
3517 on the disk, so it is much no use to work around the installation
3518 problem and end up with a computer that can lock up at any moment.
3519 There is even a
3520 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3521 available&lt;/a&gt; that will lock up the hard drive after running a few
3522 minutes by writing to a file.&lt;/p&gt;
3523
3524 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3525 contacting PCHELP Norway (request 01D1FDP) which handle support
3526 requests for Lenovo, his first suggestion was to upgrade the disk
3527 firmware. Unfortunately there is no newer firmware available from
3528 Lenovo, as my disk already have the most recent one (version LF1i). I
3529 hope to hear more from him today and hope the problem can be
3530 fixed. :)&lt;/p&gt;
3531 </description>
3532 </item>
3533
3534 <item>
3535 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3536 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3537 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3538 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3539 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3540 trusty old Thinkpad X41. Unfortunately I did not have much time to
3541 spend on it, but today the replacement finally arrived. I ended up
3542 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3543 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3544 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3545 this, it is installing what I hope will be a more final installation,
3546 with a encrypted hard drive to ensure any dope head stealing it end up
3547 with an expencive door stop.&lt;/p&gt;
3548
3549 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3550 important requirements (robust and with a good keyboard) are never
3551 listed in the feature list. But I did get good help from the search
3552 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3553 allowed me to limit the list of interesting laptops based on my other
3554 requirements. A bit surprising that SSD disk are not disks, so I had
3555 to drop number of disks from my search parameters.&lt;/p&gt;
3556
3557 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3558 wider than my old keyboard, and I have to stretch my hand a lot more
3559 to reach the edges. But the key response is fairly good and the
3560 individual key shape is fairly easy to handle, so I hope I will get
3561 used to it. My old X40 was starting to fail, and I really needed a
3562 new laptop now. :)&lt;/p&gt;
3563
3564 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3565 </description>
3566 </item>
3567
3568 <item>
3569 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3570 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3571 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3572 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3573 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3574 perfectly capable of, and I have to do it manually to get things
3575 working. One such task is to find out what firmware packages are
3576 needed to get the hardware on my computer working. Most often this
3577 affect the wifi card, but some times it even affect the RAID
3578 controller or the ethernet card. Today I pushed version 0.4 of the
3579 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3580 including a new script isenkram-autoinstall-firmware handling the
3581 process of asking all the loaded kernel modules what firmware files
3582 they want, find debian packages providing these files and install the
3583 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3584
3585 &lt;p&gt;&lt;pre&gt;
3586 # isenkram-autoinstall-firmware
3587 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3588 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3589 info: locating packages with the requested firmware files
3590 info: Updating APT sources after adding non-free APT source
3591 info: trying to install firmware-ipw2x00
3592 firmware-ipw2x00
3593 firmware-ipw2x00
3594 Preconfiguring packages ...
3595 Selecting previously deselected package firmware-ipw2x00.
3596 (Reading database ... 259727 files and directories currently installed.)
3597 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3598 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3599 #
3600 &lt;/pre&gt;&lt;/p&gt;
3601
3602 &lt;p&gt;When all the requested firmware is present, a simple message is
3603 printed instead:&lt;/p&gt;
3604
3605 &lt;p&gt;&lt;pre&gt;
3606 # isenkram-autoinstall-firmware
3607 info: did not find any firmware files requested by loaded kernel modules. exiting
3608 #
3609 &lt;/pre&gt;&lt;/p&gt;
3610
3611 &lt;p&gt;It could use some polish, but it is already working well and saving
3612 me some time when setting up new machines. :)&lt;/p&gt;
3613
3614 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3615 kernel modules, and look up each one of them using modinfo, to find
3616 the firmware files listed in the module meta-information. Next, it
3617 download the Contents file from a nearby APT mirror, and search for
3618 the firmware files in this file to locate the package with the
3619 requested firmware file. If the package is in the non-free section, a
3620 non-free APT source is added and the package is installed using
3621 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3622 machine.&lt;/p&gt;
3623
3624 &lt;p&gt;I hope someone find time to implement a more polished version of
3625 this script as part of the hw-detect debian-installer module, to
3626 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3627 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3628 firmware during a PXE install when the packages already are available
3629 from the nearby Debian mirror.&lt;/p&gt;
3630 </description>
3631 </item>
3632
3633 <item>
3634 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3635 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3636 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3637 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3638 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3639 the screen just turn black when Linux boot, either during installation
3640 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3641 last few years, but only recently understood the cause. I&#39;ve seen it
3642 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3643 The reason seem to be in the wiring of some laptops. The system to
3644 control the screen background light is inverted, so when Linux try to
3645 turn the brightness fully on, it end up turning it off instead. I do
3646 not know which Linux drivers are affected, but this post is about the
3647 i915 driver used by the
3648 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3649 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3650
3651 &lt;p&gt;The problem can be worked around two ways. Either by adding
3652 i915.invert_brightness=1 as a kernel option, or by adding a file in
3653 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3654 option when it load the i915 kernel module. On Debian and Ubuntu, it
3655 can be done by running these commands as root:&lt;/p&gt;
3656
3657 &lt;pre&gt;
3658 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3659 update-initramfs -u -k all
3660 &lt;/pre&gt;
3661
3662 &lt;p&gt;Since March 2012 there is
3663 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3664 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3665 hardware have this problem, and get the driver to invert the
3666 brightness setting automatically. To use it, one need to add a row in
3667 &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
3668 intel_quirks array&lt;/a&gt; in the driver source
3669 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3670 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3671 number (vendor number 8086 is assumed) and subdevice vendor and device
3672 number.&lt;/p&gt;
3673
3674 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3675 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3676
3677 &lt;p&gt;&lt;pre&gt;
3678 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3679 3rd Gen Core processor Graphics Controller [8086:0156] \
3680 (rev 09) (prog-if 00 [VGA controller])
3681 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3682 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3683 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3684 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3685 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3686 Latency: 0
3687 Interrupt: pin A routed to IRQ 42
3688 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3689 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3690 Region 4: I/O ports at 4000 [size=64]
3691 Expansion ROM at &lt;unassigned&gt; [disabled]
3692 Capabilities: &lt;access denied&gt;
3693 Kernel driver in use: i915
3694 &lt;/pre&gt;&lt;/p&gt;
3695
3696 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3697
3698 &lt;p&gt;&lt;pre&gt;
3699 struct intel_quirk intel_quirks[] = {
3700 ...
3701 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3702 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3703 ...
3704 }
3705 &lt;/pre&gt;&lt;/p&gt;
3706
3707 &lt;p&gt;According to the kernel module instructions (as seen using
3708 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3709 invert_brightness flag should be sent to the
3710 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3711 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3712 developers. But my email about the laptop sent 2013-06-03 have not
3713 yet shown up in
3714 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3715 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3716 emails from non-subscribers. Because of this, I sent my patch also to
3717 the Debian bug tracking system instead as
3718 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3719 sure the patch is not lost.&lt;/p&gt;
3720
3721 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3722 with this problem working properly with Linux. If you use Gnome, your
3723 worries should be over at this point. But if you use KDE, there is
3724 something in KDE ignoring the invert_brightness setting and turning on
3725 the screen during login. I&#39;ve reported it to Debian as
3726 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3727 have no idea yet how to figure out exactly what subsystem is doing
3728 this. Perhaps you can help? Perhaps you know what the Gnome
3729 developers did to handle this, and this can give a clue to the KDE
3730 developers? Or you know where in KDE the screen brightness is changed
3731 during login? If so, please update the BTS report (or get in touch if
3732 you do not know how to update BTS).&lt;/p&gt;
3733
3734 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3735 acpi_backlight=vendor, to disable ACPI backlight support completely,
3736 as the ACPI information on the machine is trash and it is better to
3737 leave it to the intel video driver to control the screen
3738 backlight.&lt;/p&gt;
3739 </description>
3740 </item>
3741
3742 <item>
3743 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3744 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3745 <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>
3746 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3747 <description>&lt;p&gt;Two days ago, I asked
3748 &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
3749 I could install Linux on a Packard Bell EasyNote LV computer
3750 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3751 with the obstacles put in the way of Linux users on a laptop with UEFI
3752 and Windows 8.&lt;/p&gt;
3753
3754 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3755 secure booting or fast boot. I suspect fast boot was the problem,
3756 causing the firmware to boot directly from HD without considering any
3757 key presses and alternative devices, but do not know UEFI settings
3758 enough to tell.&lt;/p&gt;
3759
3760 &lt;p&gt;There is no way to install Linux on the machine in question without
3761 opening the box and disconnecting the hard drive! This is as far as I
3762 can tell, the only way to get access to the firmware setup menu
3763 without accepting the Windows 8 license agreement. I am told (and
3764 found description on how to) that it is possible to configure the
3765 firmware setup once booted into Windows 8. But as I believe the terms
3766 of that agreement are completely unacceptable, accepting the license
3767 was never an alternative. I do not enter agreements I do not intend
3768 to follow.&lt;/p&gt;
3769
3770 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3771 waste many hours on this, but luckily there was a way to get it to
3772 work. But I would not recommend it to anyone planning to run Linux on
3773 it, and I have become sceptical to Windows 8 certified laptops. Is
3774 this the way Linux will be forced out of the market place, by making
3775 it close to impossible for &quot;normal&quot; users to install Linux without
3776 accepting the Microsoft Windows license terms? Or at least not
3777 without risking to loose the warranty?&lt;/p&gt;
3778
3779 &lt;p&gt;I&#39;ve updated the
3780 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3781 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3782 do not have to struggle as much as I did to get Linux into the
3783 machine.&lt;/p&gt;
3784
3785 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3786 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3787 </description>
3788 </item>
3789
3790 <item>
3791 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3792 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3793 <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>
3794 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3795 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3796 new laptops for my parents and a few others. I bought Packard Bell
3797 Easynote LV to run Kubuntu on and use as their home computer. But I
3798 am completely unable to figure out how to install Linux on it. The
3799 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3800 instead of a BIOS to boot.&lt;/p&gt;
3801
3802 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3803 to get it to boot the Linux installer from my USB stick. I have yet
3804 to try the DVD install, and still hope it will work. when I turn on
3805 the computer, there is no information on what buttons to press to get
3806 the normal boot menu. I expect to get some boot menu to select PXE or
3807 USB stick booting. When booting, it first ask for the language to
3808 use, then for some regional settings, and finally if I will accept the
3809 Windows 8 terms of use. As these terms are completely unacceptable to
3810 me, I have no other choice but to turn off the computer and try again
3811 to get it to boot the Linux installer.&lt;/p&gt;
3812
3813 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3814 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3815 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3816 installed on this machine, please get in touch or update that wiki
3817 page. If I can&#39;t find a way to install Linux, I will have to return
3818 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3819
3820 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3821 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3822 on new Laptops?&lt;/p&gt;
3823 </description>
3824 </item>
3825
3826 <item>
3827 <title>How to transform a Debian based system to a Debian Edu installation</title>
3828 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3829 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3830 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3831 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3832 an operating system based on Debian intended for use in schools. It
3833 contain a turn-key solution for the computer network provided to
3834 pupils in the primary schools. It provide both the central server,
3835 network boot servers and desktop environments with heaps of
3836 educational software. The project was founded almost 12 years ago,
3837 2001-07-02. If you want to support the project, which is in need for
3838 cash to fund developer gatherings and other project related activity,
3839 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3840 donate some money&lt;/a&gt;.
3841
3842 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3843 lists and elsewhere, is the question on how to transform a Debian or
3844 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3845 hard, and last week I wrote a script to replicate the steps done by
3846 the Debian Edu installer.&lt;/p&gt;
3847
3848 &lt;p&gt;The script,
3849 &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;
3850 in the debian-edu-config package, will go through these six steps and
3851 transform an existing Debian Wheezy or Ubuntu (untested) installation
3852 into a Debian Edu Workstation:&lt;/p&gt;
3853
3854 &lt;ol&gt;
3855
3856 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3857 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3858 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3859 our configuration.&lt;/li&gt;
3860 &lt;li&gt;Preseed debconf database with profile setup in
3861 /etc/debian-edu/config, and run tasksel to install packages
3862 according to the profile specified in the config above,
3863 overriding some of the Debian automation machinery.&lt;/li&gt;
3864 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3865 that could not be done using preseeding.&lt;/li&gt;
3866 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3867
3868 &lt;/ol&gt;
3869
3870 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3871 replicated like this. Disk partitioning and LVM setup, for example.
3872 So this script just assume there is enough disk space to install all
3873 the needed packages.&lt;/p&gt;
3874
3875 &lt;p&gt;The script was created to help a Debian Edu student working on
3876 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3877 Debian Edu client, and using it he can take the existing
3878 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3879 transform it into a fully functioning Debian Edu Workstation (or
3880 Roaming Workstation, or whatever :).&lt;/p&gt;
3881
3882 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3883 If a LXDE based Roaming workstation is wanted instead, modify the
3884 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3885
3886 &lt;p&gt;&lt;pre&gt;
3887 PROFILE=&quot;Roaming-Workstation&quot;
3888 DESKTOP=&quot;lxde&quot;
3889 &lt;/pre&gt;&lt;/p&gt;
3890
3891 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3892 the cloud, by starting with a virtual Debian installation at some
3893 virtual hosting service and setting up all the services on first
3894 boot.&lt;/p&gt;
3895 </description>
3896 </item>
3897
3898 <item>
3899 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3900 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3901 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3902 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3903 <description>&lt;P&gt;In January,
3904 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3905 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3906 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3907 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3908 marvellous construction system from Denmark. We also created
3909 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3910 a place to take notes and write down our plans and hopes. And several
3911 people showed up to help. I was very happy to see the effect of my
3912 call. Since the small start, we have a debtags tag
3913 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3914 tag for LEGO related packages, and now count 10 packages related to
3915 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3916
3917 &lt;p&gt;&lt;table&gt;
3918 &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;
3919 &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;
3920 &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;
3921 &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;
3922 &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;
3923 &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;
3924 &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;
3925 &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;
3926 &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;
3927 &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;
3928 &lt;/table&gt;&lt;/p&gt;
3929
3930 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3931 currently available in Jessie/testing. leocad is so far only
3932 available in experimental.&lt;/p&gt;
3933
3934 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3935 adding the rest of the great free software tools available on Linux
3936 for LEGO designers.&lt;/p&gt;
3937 </description>
3938 </item>
3939
3940 <item>
3941 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3942 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3943 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3944 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3945 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3946 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3947 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3948 Debian release, and I expect to move my machines at home over to it fairly
3949 soon.&lt;/p&gt;
3950
3951 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3952 in particular make me very happy to see included. The
3953 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3954 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3955 included for the first time. Alongside similar programs like
3956 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3957 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3958 it allow for visual programming where syntax errors can not happen,
3959 and a friendly programming environment for learning to control the
3960 computer. Scratch will also be included in the next release of Debian
3961 Edu.&lt;/a&gt;
3962
3963 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3964 Edu/Skolelinux release too. The
3965 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3966 alpha release&lt;/a&gt; went out last week, and the next should soon
3967 follow.&lt;p&gt;
3968 </description>
3969 </item>
3970
3971 <item>
3972 <title>Isenkram 0.2 finally in the Debian archive</title>
3973 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3974 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3975 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3976 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3977 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3978 for many months. I uploaded it to the Debian experimental suite
3979 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3980
3981 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3982 install to work with a pluggable hardware device. The suggestion pop
3983 up when the device is plugged in. For example if a Lego Mindstorm NXT
3984 is inserted, it will suggest to install the program needed to program
3985 the NXT controller. Give it a go, and report bugs and suggestions to
3986 BTS. :)&lt;/p&gt;
3987 </description>
3988 </item>
3989
3990 <item>
3991 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3992 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3993 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3994 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3995 <description>&lt;p&gt;My
3996 &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
3997 bitcoin related blog post&lt;/a&gt; mentioned that the new
3998 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3999 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4000 2013-01-19, and have been available in unstable since then. It was
4001 automatically copied to Ubuntu, and is available in their Raring
4002 version too.&lt;/p&gt;
4003
4004 &lt;p&gt;But there is a strange problem with the build that block this new
4005 version from being available on the i386 and kfreebsd-i386
4006 architectures. For some strange reason, the autobuilders in Debian
4007 for these architectures fail to run the test suite on these
4008 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
4009 We are so far unable to reproduce it when building it manually, and
4010 no-one have been able to propose a fix. If you got an idea what is
4011 failing, please let us know via the BTS.&lt;/p&gt;
4012
4013 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
4014 I often run low on disk space, is the fact that the client will exit
4015 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
4016 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
4017 it. :)&lt;/p&gt;
4018
4019 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4020 activities, please send Bitcoin donations to my address
4021 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4022 </description>
4023 </item>
4024
4025 <item>
4026 <title>Welcome to the world, Isenkram!</title>
4027 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
4028 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
4029 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
4030 <description>&lt;p&gt;Yesterday, I
4031 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
4032 for testers&lt;/a&gt; for my prototype for making Debian better at handling
4033 pluggable hardware devices, which I
4034 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
4035 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
4036 up, and caused me to really want to to open up the development to more
4037 people. But before I did this, I want to come up with a sensible name
4038 for this project. Today I finally decided on a new name, and I have
4039 renamed the project from hw-support-handler to this new name. In the
4040 process, I moved the source to git and made it available as a
4041 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
4042 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
4043 To fetch and build the latest version of the source, use&lt;/p&gt;
4044
4045 &lt;pre&gt;
4046 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4047 cd isenkram &amp;&amp; git-buildpackage -us -uc
4048 &lt;/pre&gt;
4049
4050 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
4051 want to hack on the source or improve the package, please go ahead.
4052 But please talk to me first on IRC or via email before you do major
4053 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
4054
4055 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
4056 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4057 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
4058 the German word eisenkram, for those that are familiar with that
4059 word.&lt;/p&gt;
4060
4061 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
4062 instructions, to avoid confusing people with an error from the signing
4063 process.&lt;/p&gt;
4064
4065 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
4066 clone argument to avoid the need for authentication.&lt;/p&gt;
4067 </description>
4068 </item>
4069
4070 <item>
4071 <title>First prototype ready making hardware easier to use in Debian</title>
4072 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
4073 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
4074 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
4075 <description>&lt;p&gt;Early this month I set out to try to
4076 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
4077 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
4078 prototype is working, and it is ready for a larger audience. To test
4079 it, fetch the
4080 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
4081 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
4082 package. You might have to log out and in again activate the
4083 autostart script.&lt;/p&gt;
4084
4085 &lt;p&gt;The design is simple:&lt;/p&gt;
4086
4087 &lt;ul&gt;
4088
4089 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
4090 hw-support-handlerd to start when the user log in.&lt;/li&gt;
4091
4092 &lt;li&gt;This program listen for kernel events about new hardware (directly
4093 from the kernel like udev does), not using HAL dbus events as I
4094 initially did.&lt;/li&gt;
4095
4096 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
4097 the APT database, a database
4098 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
4099 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
4100
4101 &lt;li&gt;If a package is mapped to the hardware in question, the package
4102 isn&#39;t installed yet and this is the first time the hardware was
4103 plugged in, show a desktop notification suggesting to install the
4104 package or packages.&lt;/li&gt;
4105
4106 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
4107 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
4108
4109 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
4110 package while showing progress information in a window.&lt;/li&gt;
4111
4112 &lt;/ul&gt;
4113
4114 &lt;p&gt;I still need to come up with a better name for the system. Here
4115 are some screen shots showing the prototype in action. First the
4116 notification, then the password request, and finally the request to
4117 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
4118
4119 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
4120 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
4121 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
4122 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
4123 &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;
4124
4125 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
4126 is already useful. The database of hardware to package mappings also
4127 need more work. It is currently compatible with the Ubuntu way of
4128 storing such information in the package control file, but could be
4129 changed to use other formats instead or in addition to the current
4130 method. I&#39;ve dropped the use of discover for this mapping, as the
4131 modalias approach is more flexible and easier to use on Linux as long
4132 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
4133
4134 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
4135 here is the command required to check out and build the source: Use
4136 &#39;&lt;tt&gt;svn checkout
4137 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4138 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
4139 devscripts package.&lt;/p&gt;
4140
4141 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
4142 renamed to Isenkram and the source moved from the Debian Edu
4143 subversion repository to a Debian collab-maint git repository. See
4144 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
4145 instructions&lt;/a&gt; for details.&lt;/p&gt;
4146 </description>
4147 </item>
4148
4149 <item>
4150 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
4151 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
4152 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
4153 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
4154 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
4155 suddenly in bed. With a quiet whimper, it went completely quiet and
4156 black. The power button was no longer able to turn it on. It was a
4157 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4158 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4159 Compaq I had before that. Now I need to find a replacement. To keep
4160 going during Christmas, I moved the one year old SSD disk to my old
4161 X40 where it fitted (only one I had left that could use it), but it is
4162 not a durable solution.
4163
4164 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
4165 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
4166
4167 &lt;ul&gt;
4168
4169 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
4170 than A4).&lt;/li&gt;
4171 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
4172 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
4173 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
4174 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
4175 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
4176 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
4177 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
4178 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
4179 size).&lt;/li&gt;
4180 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
4181 X.org packages.&lt;/li&gt;
4182 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
4183 the time).
4184
4185 &lt;/ul&gt;
4186
4187 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
4188 list. The reason is simply that the specifications on laptops the
4189 last 10-15 years have been sufficient for my needs, and I have to look
4190 at other features to choose my laptop. But are there still made as
4191 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4192 robust, and Thinkpads seem to be heading in the wrong direction since
4193 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
4194 still be useful.&lt;/p&gt;
4195
4196 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
4197 external keyboard? I&#39;ll have to check the
4198 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
4199 well-supported laptops, or perhaps just buy one preinstalled from one
4200 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
4201 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
4202 </description>
4203 </item>
4204
4205 <item>
4206 <title>How to find a browser plugin supporting a given MIME type</title>
4207 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
4208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
4209 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
4210 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
4211 install to get support for a given MIME type. Thanks to
4212 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
4213 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
4214 Unfortunately, not very many packages provide the needed meta
4215 information, Anyway, here is a small script to look up all browser
4216 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
4217
4218 &lt;pre&gt;
4219 #!/usr/bin/python
4220 import sys
4221 import apt
4222 def pkgs_handling_mimetype(mimetype):
4223 cache = apt.Cache()
4224 cache.open(None)
4225 thepkgs = []
4226 for pkg in cache:
4227 version = pkg.candidate
4228 if version is None:
4229 version = pkg.installed
4230 if version is None:
4231 continue
4232 record = version.record
4233 if not record.has_key(&#39;Npp-MimeType&#39;):
4234 continue
4235 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
4236 for t in mime_types:
4237 t = t.rstrip().strip()
4238 if t == mimetype:
4239 thepkgs.append(pkg.name)
4240 return thepkgs
4241 mimetype = &quot;audio/ogg&quot;
4242 if 1 &lt; len(sys.argv):
4243 mimetype = sys.argv[1]
4244 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
4245 for pkg in pkgs_handling_mimetype(mimetype):
4246 print &quot; %s&quot; %pkg
4247 &lt;/pre&gt;
4248
4249 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
4250
4251 &lt;pre&gt;
4252 % ./apt-find-browserplug-for-mimetype
4253 Browser plugin packages supporting audio/ogg:
4254 gecko-mediaplayer
4255 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4256 Browser plugin packages supporting application/x-shockwave-flash:
4257 browser-plugin-gnash
4258 %
4259 &lt;/pre&gt;
4260
4261 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4262 itself to query for plugins and propose to install the needed
4263 packages. It would be great if Debian supported such feature too. Is
4264 anyone working on adding it?&lt;/p&gt;
4265
4266 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4267 request for icweasel support for this feature is
4268 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4269 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4270 of manpower and wish for a different design is the reason thus feature
4271 is not yet in iceweasel from Debian.&lt;/p&gt;
4272 </description>
4273 </item>
4274
4275 <item>
4276 <title>What is the most supported MIME type in Debian?</title>
4277 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4278 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4279 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4280 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4281 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4282 proposal to make it possible for a Desktop application to propose to
4283 the user some package to install to gain support for a given MIME
4284 type, font, library etc. that is currently missing. With such
4285 mechanism in place, it would be possible for the desktop to
4286 automatically propose and install leocad if some LDraw file is
4287 downloaded by the browser.&lt;/p&gt;
4288
4289 &lt;p&gt;To get some idea about the current content of the archive, I decided
4290 to write a simple program to extract all .desktop files from the
4291 Debian archive and look up the claimed MIME support there. The result
4292 can be found on the
4293 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4294 site&lt;/a&gt;. Using the collected information, it become possible to
4295 answer the question in the title. Here are the 20 most supported MIME
4296 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4297 The complete list is available from the link above.&lt;/p&gt;
4298
4299 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4300
4301 &lt;pre&gt;
4302 count MIME type
4303 ----- -----------------------
4304 32 text/plain
4305 30 audio/mpeg
4306 29 image/png
4307 28 image/jpeg
4308 27 application/ogg
4309 26 audio/x-mp3
4310 25 image/tiff
4311 25 image/gif
4312 22 image/bmp
4313 22 audio/x-wav
4314 20 audio/x-flac
4315 19 audio/x-mpegurl
4316 18 video/x-ms-asf
4317 18 audio/x-musepack
4318 18 audio/x-mpeg
4319 18 application/x-ogg
4320 17 video/mpeg
4321 17 audio/x-scpls
4322 17 audio/ogg
4323 16 video/x-ms-wmv
4324 &lt;/pre&gt;
4325
4326 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4327
4328 &lt;pre&gt;
4329 count MIME type
4330 ----- -----------------------
4331 33 text/plain
4332 32 image/png
4333 32 image/jpeg
4334 29 audio/mpeg
4335 27 image/gif
4336 26 image/tiff
4337 26 application/ogg
4338 25 audio/x-mp3
4339 22 image/bmp
4340 21 audio/x-wav
4341 19 audio/x-mpegurl
4342 19 audio/x-mpeg
4343 18 video/mpeg
4344 18 audio/x-scpls
4345 18 audio/x-flac
4346 18 application/x-ogg
4347 17 video/x-ms-asf
4348 17 text/html
4349 17 audio/x-musepack
4350 16 image/x-xbitmap
4351 &lt;/pre&gt;
4352
4353 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4354
4355 &lt;pre&gt;
4356 count MIME type
4357 ----- -----------------------
4358 31 text/plain
4359 31 image/png
4360 31 image/jpeg
4361 29 audio/mpeg
4362 28 application/ogg
4363 27 image/gif
4364 26 image/tiff
4365 26 audio/x-mp3
4366 23 audio/x-wav
4367 22 image/bmp
4368 21 audio/x-flac
4369 20 audio/x-mpegurl
4370 19 audio/x-mpeg
4371 18 video/x-ms-asf
4372 18 video/mpeg
4373 18 audio/x-scpls
4374 18 application/x-ogg
4375 17 audio/x-musepack
4376 16 video/x-ms-wmv
4377 16 video/x-msvideo
4378 &lt;/pre&gt;
4379
4380 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4381 information mentioned in DEP-11. I have not yet had time to look at
4382 it, but hope the PackageKit people in Debian are on top of these
4383 issues.&lt;/p&gt;
4384
4385 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4386 discovering a typo in my script.&lt;/p&gt;
4387 </description>
4388 </item>
4389
4390 <item>
4391 <title>Using modalias info to find packages handling my hardware</title>
4392 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4393 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4394 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4395 <description>&lt;p&gt;Yesterday, I wrote about the
4396 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4397 values provided by the Linux kernel&lt;/a&gt; following my hope for
4398 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4399 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4400 modalias values attached to package names can be used to map packages
4401 to hardware. This allow the system to look up and suggest relevant
4402 packages when I plug in some new hardware into my machine, and replace
4403 discover and discover-data as the database used to map hardware to
4404 packages.&lt;/p&gt;
4405
4406 &lt;p&gt;I create a modaliases file with entries like the following,
4407 containing package name, kernel module name (if relevant, otherwise
4408 the package name) and globs matching the relevant hardware
4409 modalias.&lt;/p&gt;
4410
4411 &lt;p&gt;&lt;blockquote&gt;
4412 Package: package-name
4413 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4414 &lt;/blockquote&gt;&lt;/p&gt;
4415
4416 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4417 for a given modalias value using this file.&lt;/p&gt;
4418
4419 &lt;p&gt;An entry like this would suggest the video and picture application
4420 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4421
4422 &lt;p&gt;&lt;blockquote&gt;
4423 Package: cheese
4424 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4425 &lt;/blockquote&gt;&lt;/p&gt;
4426
4427 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4428 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4429
4430 &lt;p&gt;&lt;blockquote&gt;
4431 Package: pcmciautils
4432 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4433 &lt;/blockquote&gt;&lt;/p&gt;
4434
4435 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4436 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4437
4438 &lt;p&gt;&lt;blockquote&gt;
4439 Package: colorhug-client
4440 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4441 &lt;/blockquote&gt;&lt;/p&gt;
4442
4443 &lt;p&gt;I believe the format is compatible with the format of the Packages
4444 file in the Debian archive. Ubuntu already uses their Packages file
4445 to store their mappings from packages to hardware.&lt;/p&gt;
4446
4447 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4448 announce the hardware it support in a way my prototype understand.
4449 This allow those publishing packages in an APT source outside the
4450 Debian archive as well as those backporting packages to make sure the
4451 hardware mapping are included in the package meta information. I&#39;ve
4452 tested such header in the pymissile package, and its modalias mapping
4453 is working as it should with my prototype. It even made it to Ubuntu
4454 Raring.&lt;/p&gt;
4455
4456 &lt;p&gt;To test if it was possible to look up supported hardware using only
4457 the shell tools available in the Debian installer, I wrote a shell
4458 implementation of the lookup code. The idea is to create files for
4459 each modalias and let the shell do the matching. Please check out and
4460 try the
4461 &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;
4462 shell script. It run without any extra dependencies and fetch the
4463 hardware mappings from the Debian archive and the subversion
4464 repository where I currently work on my prototype.&lt;/p&gt;
4465
4466 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4467 install yubikey-personalization:&lt;/p&gt;
4468
4469 &lt;p&gt;&lt;blockquote&gt;
4470 % ./hw-support-lookup
4471 &lt;br&gt;yubikey-personalization
4472 &lt;br&gt;%
4473 &lt;/blockquote&gt;&lt;/p&gt;
4474
4475 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4476 propose to install the pcmciautils package:&lt;/p&gt;
4477
4478 &lt;p&gt;&lt;blockquote&gt;
4479 % ./hw-support-lookup
4480 &lt;br&gt;pcmciautils
4481 &lt;br&gt;%
4482 &lt;/blockquote&gt;&lt;/p&gt;
4483
4484 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4485 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4486 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4487
4488 &lt;p&gt;It could be possible to generate several of the mappings between
4489 packages and hardware. One source would be to look at packages with
4490 kernel modules, ie packages with *.ko files in /lib/modules/, and
4491 extract their modalias information. Another would be to look at
4492 packages with udev rules, ie packages with files in
4493 /lib/udev/rules.d/, and extract their vendor/model information to
4494 generate a modalias matching rule. I have not tested any of these to
4495 see if it work.&lt;/p&gt;
4496
4497 &lt;p&gt;If you want to help implementing a system to let us propose what
4498 packages to install when new hardware is plugged into a Debian
4499 machine, please send me an email or talk to me on
4500 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4501 </description>
4502 </item>
4503
4504 <item>
4505 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4506 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4507 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4508 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4509 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4510 information, to find the packages that support a given piece of
4511 hardware, I refreshed my memory regarding modalias values, and decided
4512 to document the details. Here are my findings so far, also available
4513 in
4514 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4515 Debian Edu subversion repository&lt;/a&gt;:
4516
4517 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4518
4519 &lt;p&gt;This document try to explain what the different types of modalias
4520 values stands for. It is in part based on information from
4521 &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;,
4522 &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;,
4523 &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
4524 &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;.
4525
4526 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4527 this shell script:&lt;/p&gt;
4528
4529 &lt;pre&gt;
4530 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4531 &lt;/pre&gt;
4532
4533 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4534 using modinfo:&lt;/p&gt;
4535
4536 &lt;pre&gt;
4537 % /sbin/modinfo psmouse | grep alias:
4538 alias: serio:ty05pr*id*ex*
4539 alias: serio:ty01pr*id*ex*
4540 %
4541 &lt;/pre&gt;
4542
4543 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4544
4545 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4546 Bridge memory controller:&lt;/p&gt;
4547
4548 &lt;p&gt;&lt;blockquote&gt;
4549 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4550 &lt;/blockquote&gt;&lt;/p&gt;
4551
4552 &lt;p&gt;This represent these values:&lt;/p&gt;
4553
4554 &lt;pre&gt;
4555 v 00008086 (vendor)
4556 d 00002770 (device)
4557 sv 00001028 (subvendor)
4558 sd 000001AD (subdevice)
4559 bc 06 (bus class)
4560 sc 00 (bus subclass)
4561 i 00 (interface)
4562 &lt;/pre&gt;
4563
4564 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4565 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4566 0600. The 0600 class is a host bridge. Other useful bus values are
4567 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4568
4569 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4570 means.&lt;/p&gt;
4571
4572 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4573
4574 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4575 USB hub in a laptop:&lt;/p&gt;
4576
4577 &lt;p&gt;&lt;blockquote&gt;
4578 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4579 &lt;/blockquote&gt;&lt;/p&gt;
4580
4581 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4582
4583 &lt;pre&gt;
4584 v 1D6B (device vendor)
4585 p 0001 (device product)
4586 d 0206 (bcddevice)
4587 dc 09 (device class)
4588 dsc 00 (device subclass)
4589 dp 00 (device protocol)
4590 ic 09 (interface class)
4591 isc 00 (interface subclass)
4592 ip 00 (interface protocol)
4593 &lt;/pre&gt;
4594
4595 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4596 class is in the interface class section. For a simple USB web camera,
4597 these alias entries show up:&lt;/p&gt;
4598
4599 &lt;p&gt;&lt;blockquote&gt;
4600 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4601 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4602 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4603 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4604 &lt;/blockquote&gt;&lt;/p&gt;
4605
4606 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4607 camera), 0101 is audio control device and 0102 is audio streaming (aka
4608 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4609
4610 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4611
4612 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4613 receiver in a Thinkpad X40:&lt;/p&gt;
4614
4615 &lt;p&gt;&lt;blockquote&gt;
4616 acpi:IBM0071:PNP0511:
4617 &lt;/blockquote&gt;&lt;/p&gt;
4618
4619 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4620
4621 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4622
4623 &lt;p&gt;The DMI table contain lots of information about the computer case
4624 and model. This is an entry for a IBM Thinkpad X40, fetched from
4625 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4626
4627 &lt;p&gt;&lt;blockquote&gt;
4628 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4629 &lt;/blockquote&gt;&lt;/p&gt;
4630
4631 &lt;p&gt;The values present are&lt;/p&gt;
4632
4633 &lt;pre&gt;
4634 bvn IBM (BIOS vendor)
4635 bvr 1UETB6WW(1.66) (BIOS version)
4636 bd 06/15/2005 (BIOS date)
4637 svn IBM (system vendor)
4638 pn 2371H4G (product name)
4639 pvr ThinkPadX40 (product version)
4640 rvn IBM (board vendor)
4641 rn 2371H4G (board name)
4642 rvr NotAvailable (board version)
4643 cvn IBM (chassis vendor)
4644 ct 10 (chassis type)
4645 cvr NotAvailable (chassis version)
4646 &lt;/pre&gt;
4647
4648 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4649 found in the dmidecode source:&lt;/p&gt;
4650
4651 &lt;pre&gt;
4652 3 Desktop
4653 4 Low Profile Desktop
4654 5 Pizza Box
4655 6 Mini Tower
4656 7 Tower
4657 8 Portable
4658 9 Laptop
4659 10 Notebook
4660 11 Hand Held
4661 12 Docking Station
4662 13 All In One
4663 14 Sub Notebook
4664 15 Space-saving
4665 16 Lunch Box
4666 17 Main Server Chassis
4667 18 Expansion Chassis
4668 19 Sub Chassis
4669 20 Bus Expansion Chassis
4670 21 Peripheral Chassis
4671 22 RAID Chassis
4672 23 Rack Mount Chassis
4673 24 Sealed-case PC
4674 25 Multi-system
4675 26 CompactPCI
4676 27 AdvancedTCA
4677 28 Blade
4678 29 Blade Enclosing
4679 &lt;/pre&gt;
4680
4681 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4682 table. For example my home server is a tower, but the DMI modalias
4683 claim it is a desktop.&lt;/p&gt;
4684
4685 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4686
4687 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4688 test machine:&lt;/p&gt;
4689
4690 &lt;p&gt;&lt;blockquote&gt;
4691 serio:ty01pr00id00ex00
4692 &lt;/blockquote&gt;&lt;/p&gt;
4693
4694 &lt;p&gt;The values present are&lt;/p&gt;
4695
4696 &lt;pre&gt;
4697 ty 01 (type)
4698 pr 00 (prototype)
4699 id 00 (id)
4700 ex 00 (extra)
4701 &lt;/pre&gt;
4702
4703 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4704 the valid values are.&lt;/p&gt;
4705
4706 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4707
4708 &lt;p&gt;There are heaps of other modalias subtypes according to
4709 file2alias.c. There is the rest of the list from that source: amba,
4710 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4711 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4712 vmbus, x86cpu and zorro. I did not spend time documenting all of
4713 these, as they do not seem relevant for my intended use with mapping
4714 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4715
4716 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4717
4718 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4719 one can use the following shell script:&lt;/p&gt;
4720
4721 &lt;pre&gt;
4722 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4723 echo &quot;$id&quot; ; \
4724 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4725 done
4726 &lt;/pre&gt;
4727
4728 &lt;p&gt;The output can look like this (only the first few entries as the
4729 list is very long on my test machine):&lt;/p&gt;
4730
4731 &lt;pre&gt;
4732 acpi:ACPI0003:
4733 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4734 acpi:device:
4735 FATAL: Module acpi:device: not found.
4736 acpi:IBM0068:
4737 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4738 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4739 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4740 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4741 acpi:IBM0071:PNP0511:
4742 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4743 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4744 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4745 [...]
4746 &lt;/pre&gt;
4747
4748 &lt;p&gt;If you want to help implementing a system to let us propose what
4749 packages to install when new hardware is plugged into a Debian
4750 machine, please send me an email or talk to me on
4751 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4752
4753 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4754 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4755 in /sys/ with space in them.&lt;/p&gt;
4756 </description>
4757 </item>
4758
4759 <item>
4760 <title>Moved the pymissile Debian packaging to collab-maint</title>
4761 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4762 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4763 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4764 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4765 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4766 Launcher and updated the Debian package
4767 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4768 sure udev will fix the device permissions when it is plugged in. I
4769 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4770 hopefully make the package be proposed by jockey in Ubuntu when a user
4771 plug in his rocket launcher. In the process I moved the source to a
4772 git repository under collab-maint, to make it easier for any DD to
4773 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4774 is not very active, but the software still work for me even after five
4775 years of relative silence. The new git repository is not listed in
4776 the uploaded package yet, because I want to test the other changes a
4777 bit more before I upload the new version. If you want to check out
4778 the new version with a .desktop file included, visit the
4779 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4780 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4781 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4782 </description>
4783 </item>
4784
4785 <item>
4786 <title>Lets make hardware dongles easier to use in Debian</title>
4787 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4789 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4790 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4791 general, is that there is a great package management system with the
4792 ability to automatically install software packages by downloading them
4793 from the distribution mirrors, but no way to get it to automatically
4794 install the packages I need to use the hardware I plug into my
4795 machine. Even if the package to use it is easily available from the
4796 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4797 suggest to automatically install the python-nxt, nbc and t2n packages
4798 I need to talk to it. When I plug in a Yubikey, it could propose the
4799 yubikey-personalization package. The information required to do this
4800 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4801
4802 &lt;p&gt;Some years ago, I proposed to
4803 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4804 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4805 simple:
4806
4807 &lt;ul&gt;
4808
4809 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4810 starting when a user log in.&lt;/li&gt;
4811
4812 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4813 hardware is inserted into the computer.&lt;/li&gt;
4814
4815 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4816 database mapping to packages, and take note of any non-installed
4817 packages.&lt;/li&gt;
4818
4819 &lt;li&gt;Show a message to the user proposing to install the discovered
4820 package, and make it easy to install it.&lt;/li&gt;
4821
4822 &lt;/ul&gt;
4823
4824 &lt;p&gt;I am not sure what the best way to implement this is, but my
4825 initial idea was to use dbus events to discover new hardware, the
4826 discover database to find packages and
4827 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4828 packages.&lt;/p&gt;
4829
4830 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4831 draft package is now checked into
4832 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4833 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4834 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4835 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4836 the relevant packages in Debian, and uploaded a new version
4837 2.2013.01.09 to unstable. I also discovered that the current
4838 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4839 package in Debian no longer discovered any USB devices, because
4840 /proc/bus/usb/devices is no longer present. I ported it to use
4841 libusb as a fall back option to get it working. The fixed package
4842 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4843 because of the freeze).&lt;/p&gt;
4844
4845 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4846 desktop notification to show up (only once, the first time it is
4847 inserted):&lt;/p&gt;
4848
4849 &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;
4850
4851 &lt;p&gt;For this prototype to be really useful, some way to automatically
4852 install the proposed packages by pressing the &quot;Please install
4853 program(s)&quot; button should to be implemented.&lt;/p&gt;
4854
4855 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4856 happen, please help me update the discover-data database with mappings
4857 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4858 list the package you would like to have installed when a given
4859 hardware device is inserted into your computer, and report bugs using
4860 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4861 such mapping, please let me know.&lt;/p&gt;
4862
4863 &lt;p&gt;This prototype need more work, and there are several questions that
4864 should be considered before it is ready for production use. Is dbus
4865 the correct way to detect new hardware? At the moment I look for HAL
4866 dbus events on the system bus, because that is the events I could see
4867 on my Debian Squeeze KDE desktop. Are there better events to use?
4868 How should the user be notified? Is the desktop notification
4869 mechanism the best option, or should the background daemon raise a
4870 popup instead? How should packages be installed? When should they
4871 not be installed?&lt;/p&gt;
4872
4873 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4874 please send me an email. :)&lt;/p&gt;
4875 </description>
4876 </item>
4877
4878 <item>
4879 <title>New IRC channel for LEGO designers using Debian</title>
4880 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4882 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4883 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4884 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4885 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4886 discovered I had to build all the tools myself because none were
4887 already in Debian Squeeze. If Debian support for LEGO is something
4888 you care about, please join me on the IRC channel
4889 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4890 irc.debian.org). There is a lot that could be done to improve the
4891 Debian support for LEGO designers. For example both CAD software
4892 and Mindstorm compilers are missing. :)&lt;/p&gt;
4893
4894 &lt;p&gt;Update 2012-01-03: A
4895 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4896 including links to Lego related packages is now available.&lt;/p&gt;
4897 </description>
4898 </item>
4899
4900 <item>
4901 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4902 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4903 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4904 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4905 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4906 year! I hope next year will prove to be a good year.&lt;/p&gt;
4907
4908 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4909 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4910 between each other with minimal overhead, is a very interesting
4911 experiment. And as I wrote a few days ago, the bitcoin situation in
4912 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4913 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4914 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4915 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4916 for one of the ftpmasters to approve the new bitcoin-qt package
4917 name.&lt;/p&gt;
4918
4919 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4920 team in Debian, you can easily test the package in Debian Squeeze
4921 using the following steps to get a set of working packages:&lt;/p&gt;
4922
4923 &lt;blockquote&gt;&lt;pre&gt;
4924 git clone git://git.debian.org/git/collab-maint/bitcoin
4925 cd bitcoin
4926 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4927 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4928 &lt;/pre&gt;&lt;/blockquote&gt;
4929
4930 &lt;p&gt;You might have to install some build dependencies as well. The
4931 list of commands should give you two packages, bitcoind and
4932 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4933 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4934 around 5.6 GiB of data on my machine at the moment. Make sure your
4935 ~/.bitcoin/ directory have lots of spare room if you want to download
4936 all the blocks. The client will warn if the disk is getting full, so
4937 there is not really a problem if you got too little room, but you will
4938 not be able to get all the features out of the client.&lt;/p&gt;
4939
4940 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4941 activities, please send Bitcoin donations to my address
4942 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4943 </description>
4944 </item>
4945
4946 <item>
4947 <title>A word on bitcoin support in Debian</title>
4948 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4949 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4950 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4951 <description>&lt;p&gt;It has been a while since I wrote about
4952 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4953 peer-to-peer based crypto-currency, and the reason is simply that I
4954 have been busy elsewhere. But two days ago, I started looking at the
4955 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4956 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4957 is now maintained by a
4958 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4959 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4960 owe a huge thank you to all these team members. :)
4961 But I was sad to discover that the bitcoin client is missing in
4962 Wheezy. It is only available in Sid (and an outdated client from
4963 backports). The client had several RC bugs registered in BTS blocking
4964 it from entering testing. To try to help the team and improve the
4965 situation, I spent some time providing patches and triaging the bug
4966 reports. I also had a look at the bitcoin package available from Matt
4967 Corallo in a
4968 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4969 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4970 Debian package.&lt;/p&gt;
4971
4972 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4973 IRC, I pushed several patches into the collab-maint git repository to
4974 improve the package. It now contains fixes for the RC issues (not from
4975 me, but fixed by Scott Howard), build rules for a Qt GUI client
4976 package, konqueror support for the bitcoin: URI and bash completion
4977 setup. As I work on Debian Squeeze, I also created
4978 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4979 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4980 it and try to integrate it into the git repository before uploading a
4981 new version to unstable.
4982
4983 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4984 centralized control currently exercised in the monetary system. I
4985 find it completely unacceptable that the USA government is collecting
4986 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4987 that the major credit card companies can block legal money
4988 transactions to Wikileaks. But for bitcoin to succeed, more people
4989 need to use bitcoins, and more people need to accept bitcoins when
4990 they sell products and services. Improving the bitcoin support in
4991 Debian is a small step in the right direction, but not enough.
4992 Unfortunately the user experience when browsing the web and wanting to
4993 pay with bitcoin is still not very good. The bitcoin: URI is a step
4994 in the right direction, but need to work in most or every browser in
4995 use. Also the bitcoin-qt client is too heavy to fire up to do a
4996 quick transaction. I believe there are other clients available, but
4997 have not tested them.&lt;/p&gt;
4998
4999 &lt;p&gt;My
5000 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
5001 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
5002 I received 20.15 BTC so far on the address I provided in my blog two
5003 years ago, as can be
5004 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
5005 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
5006 donation. The blockexplorer service demonstrates quite well that
5007 bitcoin is not quite anonymous and untracked. :) I wonder if the
5008 number of users have gone up since then. If you use bitcoin and want
5009 to show your support of my activity, please send Bitcoin donations to
5010 the same address as last time,
5011 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5012 </description>
5013 </item>
5014
5015 <item>
5016 <title>Git repository for song book for Computer Scientists</title>
5017 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
5018 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
5019 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
5020 <description>&lt;p&gt;As I
5021 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
5022 this summer&lt;/a&gt;, I have created a Computer Science song book a few
5023 years ago, and today I finally found time to create a public
5024 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
5025 repository for the project&lt;/a&gt;.&lt;/p&gt;
5026
5027 &lt;p&gt;If you want to help out, please clone the source and submit patches
5028 to the HTML version. To generate the PDF and PostScript version,
5029 please use prince XML, or let me know about a useful free software
5030 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
5031
5032 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
5033 PostScript formats at
5034 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
5035 Science Songbook&lt;/a&gt;.&lt;/p&gt;
5036 </description>
5037 </item>
5038
5039 <item>
5040 <title>Gratulerer med 19-årsdagen, Debian!</title>
5041 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
5042 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
5043 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
5044 <description>&lt;p&gt;I dag fyller
5045 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
5046 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
5047 si gratulerer med dagen, Debian!&lt;/p&gt;
5048 </description>
5049 </item>
5050
5051 <item>
5052 <title>Song book for Computer Scientists</title>
5053 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
5054 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
5055 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
5056 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
5057 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
5058 collecting computer related songs for use at parties. The original
5059 version was written in LaTeX, but a few years ago I got help from
5060 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5061 while keeping the ability to create a nice book in PDF format. I have
5062 not had time to maintain the book for a while now, and guess I should
5063 put it up on some public version control repository where others can
5064 help me extend and update the book. If anyone is volunteering to help
5065 me with this, send me an email. Also let me know if there are songs
5066 missing in my book.&lt;/p&gt;
5067
5068 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
5069 me today that I really should let all my readers share the joys of
5070 singing out load about programming, computers and computer networks.
5071 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
5072 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
5073 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
5074 Computer Science Songbook&lt;/a&gt;.
5075 </description>
5076 </item>
5077
5078 <item>
5079 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
5080 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
5081 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
5082 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
5083 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
5084 around 1000 at the moment. To be able to get help from the vendors
5085 when something go wrong, we want to keep the firmware on the servers
5086 up to date. If the firmware isn&#39;t the latest and greatest, the
5087 vendors typically refuse to start debugging any problems until the
5088 firmware is upgraded. So before every reboot, we want to upgrade the
5089 firmware, and we would really like everyone handling servers at the
5090 university to do this themselves when they plan to reboot a machine.
5091 For that to happen we at the unix server admin group need to provide
5092 the tools to do so.&lt;/p&gt;
5093
5094 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
5095 fetch and install the latest firmware for the servers we got. Most of
5096 our hardware are from Dell and HP, so I have focused on these servers
5097 so far. This blog post is about the Dell part.&lt;/P&gt;
5098
5099 &lt;p&gt;On the Dell FTP site I was lucky enough to find
5100 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
5101 with firmware information for all 11th generation servers, listing
5102 which firmware should be used on a given model and where on the FTP
5103 site I can find it. Using a simple perl XML parser I can then
5104 download the shell scripts Dell provides to do firmware upgrades from
5105 within Linux and reboot when all the firmware is primed and ready to
5106 be activated on the first reboot.&lt;/p&gt;
5107
5108 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
5109 Are there anyone working on similar tools for firmware upgrading all
5110 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
5111
5112 &lt;p&gt;&lt;pre&gt;
5113 #!/usr/bin/perl
5114 use strict;
5115 use warnings;
5116 use File::Temp qw(tempdir);
5117 BEGIN {
5118 # Install needed RHEL packages if missing
5119 my %rhelmodules = (
5120 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
5121 );
5122 for my $module (keys %rhelmodules) {
5123 eval &quot;use $module;&quot;;
5124 if ($@) {
5125 my $pkg = $rhelmodules{$module};
5126 system(&quot;yum install -y $pkg&quot;);
5127 eval &quot;use $module;&quot;;
5128 }
5129 }
5130 }
5131 my $errorsto = &#39;pere@hungry.com&#39;;
5132
5133 upgrade_dell();
5134
5135 exit 0;
5136
5137 sub run_firmware_script {
5138 my ($opts, $script) = @_;
5139 unless ($script) {
5140 print STDERR &quot;fail: missing script name\n&quot;;
5141 exit 1
5142 }
5143 print STDERR &quot;Running $script\n\n&quot;;
5144
5145 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
5146 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
5147 } else {
5148 print STDERR &quot;fail: firmware script returned error\n&quot;;
5149 }
5150 }
5151
5152 sub run_firmware_scripts {
5153 my ($opts, @dirs) = @_;
5154 # Run firmware packages
5155 for my $dir (@dirs) {
5156 print STDERR &quot;info: Running scripts in $dir\n&quot;;
5157 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
5158 while (my $s = readdir $dh) {
5159 next if $s =~ m/^\.\.?/;
5160 run_firmware_script($opts, &quot;$dir/$s&quot;);
5161 }
5162 closedir $dh;
5163 }
5164 }
5165
5166 sub download {
5167 my $url = shift;
5168 print STDERR &quot;info: Downloading $url\n&quot;;
5169 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
5170 }
5171
5172 sub upgrade_dell {
5173 my @dirs;
5174 my $product = `dmidecode -s system-product-name`;
5175 chomp $product;
5176
5177 if ($product =~ m/PowerEdge/) {
5178
5179 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5180 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
5181
5182 my $tmpdir = tempdir(
5183 CLEANUP =&gt; 1
5184 );
5185 chdir($tmpdir);
5186 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
5187 system(&#39;gunzip Catalog.xml.gz&#39;);
5188 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
5189 # -q is quiet, disabling interactivity and reducing console output
5190 my $fwopts = &quot;-q&quot;;
5191 if (@paths) {
5192 for my $url (@paths) {
5193 fetch_dell_fw($url);
5194 }
5195 run_firmware_scripts($fwopts, $tmpdir);
5196 } else {
5197 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5198 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5199 }
5200 chdir(&#39;/&#39;);
5201 } else {
5202 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5203 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5204 }
5205 }
5206
5207 sub fetch_dell_fw {
5208 my $path = shift;
5209 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
5210 download($url);
5211 }
5212
5213 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5214 # firmware packages to download from Dell. Only work for Linux
5215 # machines and 11th generation Dell servers.
5216 sub fetch_dell_fw_list {
5217 my $filename = shift;
5218
5219 my $product = `dmidecode -s system-product-name`;
5220 chomp $product;
5221 my ($mybrand, $mymodel) = split(/\s+/, $product);
5222
5223 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
5224
5225 my $xml = XMLin($filename);
5226 my @paths;
5227 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
5228 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
5229 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
5230 my $oscode;
5231 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
5232 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
5233 } else {
5234 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
5235 }
5236 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
5237 {
5238 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
5239 }
5240 }
5241 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
5242 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
5243
5244 # Drop application packages, only firmware and BIOS
5245 next if &#39;APAC&#39; eq $componenttype;
5246
5247 my $cpath = $component-&gt;{path};
5248 for my $path (@paths) {
5249 if ($cpath =~ m%/$path$%) {
5250 push(@paths, $cpath);
5251 }
5252 }
5253 }
5254 return @paths;
5255 }
5256 &lt;/pre&gt;
5257
5258 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5259 it could work on other platforms with some tweaking. Anyone know a
5260 index like Catalog.xml is available from HP for HP servers? At the
5261 moment I maintain a similar list manually and it is quickly getting
5262 outdated.&lt;/p&gt;
5263 </description>
5264 </item>
5265
5266 <item>
5267 <title>How is booting into runlevel 1 different from single user boots?</title>
5268 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5269 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5270 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5271 <description>&lt;p&gt;Wouter Verhelst have some
5272 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5273 comments and opinions&lt;/a&gt; on my blog post on
5274 &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
5275 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5276 &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
5277 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5278 small piece of his comment now, and though it best to address the
5279 misunderstanding he bring forward:&lt;/p&gt;
5280
5281 &lt;p&gt;&lt;blockquote&gt;
5282 Currently, a system admin has four options: [...] boot to a
5283 single-user system (by adding &#39;single&#39; to the kernel command line;
5284 this runs rcS and rc1 scripts)
5285 &lt;/blockquote&gt;&lt;/p&gt;
5286
5287 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5288 and booting into runlevel 1 is the same. I am not surprised he
5289 believe this, because it would make sense and is a quite sensible
5290 thing to believe. But because the boot in Debian is slightly broken,
5291 runlevel 1 do not work properly and it isn&#39;t the same as single user
5292 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5293 hard to explain.&lt;/p&gt;
5294
5295 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5296 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5297 executed in single user mode is sulogin. Single user mode is a boot
5298 state &quot;between&quot; the runlevels, and when booting into single user mode,
5299 only the scripts in /etc/rcS.d/ are executed before the init process
5300 enters the single user state. When switching to runlevel 1, the state
5301 is in fact not ending in runlevel 1, but it passes through runlevel 1
5302 and end up in the single user mode (see /etc/rc1.d/S03single, which
5303 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5304 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5305 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5306 mode).&lt;/p&gt;
5307
5308 &lt;p&gt;This summary might make it clearer. When booting for the first
5309 time into single user mode, the following commands are executed:
5310 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5311 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5312 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5313 trying to continue after visiting single user mode. Not all services
5314 are started again as they should, causing the machine to end up in an
5315 unpredicatble state. This is why Debian admins recommend rebooting
5316 after visiting single user mode.&lt;/p&gt;
5317
5318 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5319 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5320 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5321 stopped when passing through the scripts in /etc/rc1.d/, and not
5322 started again when switching away from runlevel 1 to the runlevels
5323 2-5. I believe the problem is best fixed by moving all the scripts
5324 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5325 functioning single user mode during boot.&lt;/p&gt;
5326
5327 &lt;p&gt;I have spent several years investigating the Debian boot system,
5328 and discovered this problem a few years ago. I suspect it originates
5329 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5330 </description>
5331 </item>
5332
5333 <item>
5334 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5335 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5336 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5337 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5338 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5339 are started from /etc/rcS.d/. In fact, there is a bite more of them
5340 than make sense, and this causes a few problems. What kind of
5341 problems, you might ask. There are at least two problems. The first
5342 is that it is not possible to recover a machine after switching to
5343 runlevel 1. One need to actually reboot to get the machine back to
5344 the expected state. The other is that single user boot will sometimes
5345 run into problems because some of the subsystems are activated before
5346 the root login is presented, causing problems when trying to recover a
5347 machine from a problem in that subsystem. A minor additional point is
5348 that moving more scripts out of rcS.d/ and into the other rc#.d/
5349 directories will increase the amount of scripts that can run in
5350 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5351
5352 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5353 scripts that _have_ to execute before the root login prompt is
5354 presented during a single user boot should go there. Everything else
5355 should go into the numeric runlevels. This means things like
5356 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5357 the numeric runlevels. Today in Debian, there are around 115 init.d
5358 scripts that are started from rcS.d/, and most of them should be moved
5359 out. Do your package have one of them? Please help us make single
5360 user and runlevel 1 better by moving it.&lt;/p&gt;
5361
5362 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5363 etc. should still be started from rcS.d/, but there is for example no
5364 need to have the network enabled before the single user login prompt
5365 is presented.&lt;/p&gt;
5366
5367 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5368 Debian systems working while scripts migrate and during upgrades, the
5369 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5370 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5371 and the next ones can only be moved when their dependencies have been
5372 moved first. This migration must be done sequentially while we ensure
5373 that the package system upgrade packages in the right order to keep
5374 the system state correct. This will require some coordination when it
5375 comes to network related packages, but most of the packages with
5376 scripts that should migrate do not have anything in rcS.d/ depending
5377 on them. Some packages have already been updated, like the sudo
5378 package, while others are still left to do. I wish I had time to work
5379 on this myself, but real live constrains make it unlikely that I will
5380 find time to push this forward.&lt;/p&gt;
5381 </description>
5382 </item>
5383
5384 <item>
5385 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5386 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5387 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5388 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5389 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5390 mentioned the issues I believe should be improved in Debian for its
5391 desktop to be useful for more people. The use case for this is my
5392 parents, which are currently running Kubuntu which solve the
5393 issues.&lt;/p&gt;
5394
5395 &lt;p&gt;I suspect these four missing features are not very hard to
5396 implement. After all, they are present in Ubuntu, so if we wanted to
5397 do this in Debian we would have a source.&lt;/p&gt;
5398
5399 &lt;ol&gt;
5400
5401 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5402 are new packages available for upgrades, a icon in the KDE status bar
5403 indicate this, and clicking on it will activate the simple upgrade
5404 tool to handle it. I have no problem guiding both of my parents
5405 through the process over the phone. If a kernel reboot is required,
5406 this too is indicated by the status bars and the upgrade tool. Last
5407 time I checked, nothing with the same features was working in KDE in
5408 Debian.&lt;/li&gt;
5409
5410 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5411 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5412 currently have a handler for, it will ask the user if the system
5413 should search for a package that would add support for this MIME type,
5414 and if the user say yes, the APT sources will be searched for packages
5415 advertising the MIME type in their control file (visible in the
5416 Packages file in the APT archive). If one or more packages are found,
5417 it is a simple click of the mouse to add support for the missing mime
5418 type. If the package require the user to accept some non-free
5419 license, this is explained to the user. The entire process make it
5420 more clear to the user why something do not work in the browser, and
5421 make the chances higher for the user to blame the web page authors and
5422 not the browser for any missing features.&lt;/li&gt;
5423
5424 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5425 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5426 it is not supporting, a dialog pop up asking the user if the system
5427 should search for a package that would add support for it. This
5428 happen with things like MP3, Windows Media or H.264. The selection
5429 and installation procedure is very similar to the Firefox browser
5430 plugin handling. This is as far as I know implemented using a
5431 gstreamer hook. The end result is that the user easily get access to
5432 the codecs that are present from the APT archives available, while
5433 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5434
5435 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5436 displaying a text/plain file in my Debian browser, it will propose to
5437 start emacs to show it. If I remember correctly, when doing the same
5438 in Kunbutu it show the file as a text file in the browser. At least I
5439 know Opera will show text files within the browser. I much prefer the
5440 latter behaviour.&lt;/li&gt;
5441
5442 &lt;/ol&gt;
5443
5444 &lt;p&gt;There are other nice features as well, like the simplified suite
5445 upgrader, but given that I am the one mostly doing the dist-upgrade,
5446 it do not matter much.&lt;/p&gt;
5447
5448 &lt;p&gt;I really hope we could get these features in place for the next
5449 Debian release. It would require the coordinated effort of several
5450 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5451 </description>
5452 </item>
5453
5454 <item>
5455 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5456 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5457 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5458 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5459 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5460 site is build on Debian/Squeeze, and this platform was chosen because
5461 I am most familiar with Debian (being a Debian Developer for around 10
5462 years) because it is the latest stable Debian release which should get
5463 security support for a few years.&lt;/p&gt;
5464
5465 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5466 that are missing in Debian at the moment. It would be great if these
5467 modules were added to the Debian archive, allowing anyone to set up
5468 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5469 in their own country using only Debian packages. The list of modules
5470 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5471 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5472 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5473 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5474 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5475 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5476 easier in the future.&lt;/p&gt;
5477
5478 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5479 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5480 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5481 with the responsibility of tracking security problems, which I really
5482 do not have time for.&lt;/p&gt;
5483 </description>
5484 </item>
5485
5486 <item>
5487 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5488 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5489 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5490 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5491 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5492 posts have been in Norwegian the last few weeks, so here is a short
5493 update in English.&lt;/p&gt;
5494
5495 &lt;p&gt;The kids still keep me too busy to get much free software work
5496 done, but I did manage to organise a project to get a Norwegian port
5497 of the British service
5498 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5499 and it has been running for a month now. The entire project has been
5500 organised by me and two others. Around Christmas we gathered sponsors
5501 to fund the development work. In January I drafted a contract with
5502 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5503 and in February the development took place. Most of it involved
5504 converting the source to use GPS coordinates instead of British
5505 easting/northing, and the resulting code should be a lot easier to get
5506 running in any country by now. The Norwegian
5507 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5508 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5509 source and the source for administrative borders in Norway, and
5510 support for this had to be added/fixed.&lt;/p&gt;
5511
5512 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5513 polishing the system before we announced it March 7th. The system is
5514 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5515 problem reports in a few weeks. Soon we hope to announce the Android
5516 and iPhone versions making it even easier to report problems with the
5517 public infrastructure.&lt;/p&gt;
5518
5519 &lt;p&gt;Perhaps something to consider for those of you in countries without
5520 such service?&lt;/p&gt;
5521 </description>
5522 </item>
5523
5524 <item>
5525 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5526 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5527 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5528 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5529 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5530 issues here at my work with the University of Oslo. My idea is that
5531 it should be possible to use the information about security issues
5532 available on the Internet, and check our locally
5533 maintained/distributed software against this information. It should
5534 allow us to verify that no known security issues are forgotten. The
5535 CVE database listing vulnerabilities seem like a great central point,
5536 and by using the package lists from Debian mapped to CVEs provided by
5537 the testing security team, I believed it should be possible to figure
5538 out which security holes were present in our free software
5539 collection.&lt;/p&gt;
5540
5541 &lt;p&gt;After reading up on the topic, it became obvious that the first
5542 building block is to be able to name software packages in a unique and
5543 consistent way across data sources. I considered several ways to do
5544 this, for example coming up with my own naming scheme like using URLs
5545 to project home pages or URLs to the Freshmeat entries, or using some
5546 existing naming scheme. And it seem like I am not the first one to
5547 come across this problem, as MITRE already proposed and implemented a
5548 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5549 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5550 software, hardware and other platform components. The CPE ids are
5551 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5552 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5553 issues for any CPE name. With this in place, all I need to do is to
5554 locate the CPE id for the software packages we use at the university.
5555 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5556 NVD entry if a CVE for the package exist).&lt;/p&gt;
5557
5558 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5559 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5560 check out, one could look up
5561 &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
5562 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5563 The most recent one is
5564 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5565 and at the bottom of the NVD page for this vulnerability the complete
5566 list of affected versions is provided.&lt;/p&gt;
5567
5568 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5569 for offline processing of issues. Using this dump, I&#39;ve written a
5570 small script taking a list of CPEs as input and list all CVEs
5571 affecting the packages represented by these CPEs. One give it CPEs
5572 with version numbers as specified above and get a list of open
5573 security issues out.&lt;/p&gt;
5574
5575 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5576 information need to be high. For that to happen, I believe as many as
5577 possible need to use and contribute to the NVD database. I notice
5578 RHEL is providing
5579 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5580 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5581 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5582
5583 &lt;p&gt;To get an idea about the quality for free software, I spent some
5584 time making it possible to compare the CVE database from Debian with
5585 the CVE database in NVD. The result look fairly good, but there are
5586 some inconsistencies in NVD (same software package having several
5587 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5588 Debian believe are affected by a CVE). Hope to find time to improve
5589 the quality of NVD, but that require being able to get in touch with
5590 someone maintaining it. So far my three emails with questions and
5591 corrections have not seen any reply, but I hope contact can be
5592 established soon.&lt;/p&gt;
5593
5594 &lt;p&gt;An interesting application for CPEs is cross platform package
5595 mapping. It would be useful to know which packages in for example
5596 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5597 this would be trivial if all linux distributions provided CPE entries
5598 for their packages.&lt;/p&gt;
5599 </description>
5600 </item>
5601
5602 <item>
5603 <title>Which module is loaded for a given PCI and USB device?</title>
5604 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5605 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5606 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5607 <description>&lt;p&gt;In the
5608 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5609 package in Debian, there is a script to report useful information
5610 about the running hardware for use when people report missing
5611 information. One part of this script that I find very useful when
5612 debugging hardware problems, is the part mapping loaded kernel module
5613 to the PCI device it claims. It allow me to quickly see if the kernel
5614 module I expect is driving the hardware I am struggling with. To see
5615 the output, make sure discover-data is installed and run
5616 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5617 one of my machines like this:&lt;/p&gt;
5618
5619 &lt;pre&gt;
5620 loaded modules:
5621 10de:03eb i2c_nforce2
5622 10de:03f1 ohci_hcd
5623 10de:03f2 ehci_hcd
5624 10de:03f0 snd_hda_intel
5625 10de:03ec pata_amd
5626 10de:03f6 sata_nv
5627 1022:1103 k8temp
5628 109e:036e bttv
5629 109e:0878 snd_bt87x
5630 11ab:4364 sky2
5631 &lt;/pre&gt;
5632
5633 &lt;p&gt;The code in question look like this, slightly modified for
5634 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5635
5636 &lt;pre&gt;
5637 if [ -d /sys/bus/pci/devices/ ] ; then
5638 echo loaded pci modules:
5639 (
5640 cd /sys/bus/pci/devices/
5641 for address in * ; do
5642 if [ -d &quot;$address/driver/module&quot; ] ; then
5643 module=`cd $address/driver/module ; pwd -P | xargs basename`
5644 if grep -q &quot;^$module &quot; /proc/modules ; then
5645 address=$(echo $address |sed s/0000://)
5646 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5647 echo &quot;$id $module&quot;
5648 fi
5649 fi
5650 done
5651 )
5652 echo
5653 fi
5654 &lt;/pre&gt;
5655
5656 &lt;p&gt;Similar code could be used to extract USB device module
5657 mappings:&lt;/p&gt;
5658
5659 &lt;pre&gt;
5660 if [ -d /sys/bus/usb/devices/ ] ; then
5661 echo loaded usb modules:
5662 (
5663 cd /sys/bus/usb/devices/
5664 for address in * ; do
5665 if [ -d &quot;$address/driver/module&quot; ] ; then
5666 module=`cd $address/driver/module ; pwd -P | xargs basename`
5667 if grep -q &quot;^$module &quot; /proc/modules ; then
5668 address=$(echo $address |sed s/0000://)
5669 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5670 if [ &quot;$id&quot; ] ; then
5671 echo &quot;$id $module&quot;
5672 fi
5673 fi
5674 fi
5675 done
5676 )
5677 echo
5678 fi
5679 &lt;/pre&gt;
5680
5681 &lt;p&gt;This might perhaps be something to include in other tools as
5682 well.&lt;/p&gt;
5683 </description>
5684 </item>
5685
5686 <item>
5687 <title>How to test if a laptop is working with Linux</title>
5688 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5689 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5690 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5691 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5692 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5693 batch of computers will work with Linux. Every year for the last few
5694 years the university have organised shared bid of a few thousand
5695 computers, and this year HP won the bid. Two different desktops and
5696 five different laptops are on the list this year. We in the UNIX
5697 group want to know which one of these computers work well with RHEL
5698 and Ubuntu, the two Linux distributions we currently handle at the
5699 university.&lt;/p&gt;
5700
5701 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5702 perhaps inspire others to test hardware as well. To test, I PXE
5703 install the OS version of choice, and log in as my normal user and run
5704 a few applications and plug in selected pieces of hardware. When
5705 something fail, I make a note about this in the test matrix and move
5706 on. If I have some spare time I try to report the bug to the OS
5707 vendor, but as I only have the machines for a short time, I rarely
5708 have the time to do this for all the problems I find.&lt;/p&gt;
5709
5710 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5711 I perform on a new model.&lt;/p&gt;
5712
5713 &lt;ul&gt;
5714
5715 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5716 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5717 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5718
5719 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5720 installation, X.org is working.&lt;/li&gt;
5721
5722 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5723 package mesa-utils on Ubuntu) and writing down the frames per second
5724 reported by the program.&lt;/li&gt;
5725
5726 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5727 logging in, and if I can hear this the test is successful. If there
5728 are several audio exits on the machine, I try them all and check if
5729 the Gnome/KDE audio mixer can control where to send the sound. I
5730 normally test this by playing
5731 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5732 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5733
5734 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5735 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5736
5737 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5738 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5739
5740 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5741 picture from the v4l device show up.&lt;/li&gt;
5742
5743 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5744 any bluetooth devices are discovered. In my office, I normally see a
5745 few.&lt;/li&gt;
5746
5747 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5748 memory modules lying around, and stick them in and see if Gnome/KDE
5749 notice this.&lt;/li&gt;
5750
5751 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5752 special button work, and if the laptop continue to work after
5753 resume.&lt;/li&gt;
5754
5755 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5756 adjusting background light, switching on/off external video output,
5757 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5758 laptop to laptop, so I just write down which are working and which are
5759 not.&lt;/li&gt;
5760
5761 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5762 acceleration sensors etc. I rarely test these, as I do not know how
5763 to quickly test if they are working or not, so I only document their
5764 existence.&lt;/li&gt;
5765
5766 &lt;/ul&gt;
5767
5768 &lt;p&gt;By now I suspect you are really curious what the test results are
5769 for the HP machines I am testing. I&#39;m not done yet, so I will report
5770 the test results later. For now I can report that HP 8100 Elite work
5771 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5772 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5773 can see, I have most machines left to test. One interesting
5774 observation is that Ubuntu Lucid has almost twice the frame rate than
5775 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5776 </description>
5777 </item>
5778
5779 <item>
5780 <title>Some thoughts on BitCoins</title>
5781 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5782 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5783 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5784 <description>&lt;p&gt;As I continue to explore
5785 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5786 what properties the system have, and how it will be affected by laws
5787 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5788
5789 &lt;p&gt;One interesting thing to note is that since the transactions are
5790 verified using a peer to peer network, all details about a transaction
5791 is known to everyone. This means that if a BitCoin address has been
5792 published like I did with mine in my initial post about BitCoin, it is
5793 possible for everyone to see how many BitCoins have been transfered to
5794 that address. There is even a web service to look at the details for
5795 all transactions. There I can see that my address
5796 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5797 have received 16.06 Bitcoin, the
5798 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5799 address of Simon Phipps have received 181.97 BitCoin and the address
5800 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5801 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5802 every one of you that donated bitcoins to support my activity. The
5803 fact that anyone can see how much money was transfered to a given
5804 address make it more obvious why the BitCoin community recommend to
5805 generate and hand out a new address for each transaction. I&#39;m told
5806 there is no way to track which addresses belong to a given person or
5807 organisation without the person or organisation revealing it
5808 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5809
5810 &lt;p&gt;In Norway, and in most other countries, there are laws and
5811 regulations limiting how much money one can transfer across the border
5812 without declaring it. There are money laundering, tax and accounting
5813 laws and regulations I would expect to apply to the use of BitCoin.
5814 If the Skolelinux foundation
5815 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5816 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5817 normal bank transfers like EFF is doing, how should this be accounted?
5818 Given that it is impossible to know if money can cross the border or
5819 not, should everything or nothing be declared? What exchange rate
5820 should be used when calculating taxes? Would receivers have to pay
5821 income tax if the foundation were to pay Skolelinux contributors in
5822 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5823
5824 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5825 accepted by a lot of users. It must be possible to get easy access to
5826 the currency (as a wage or using currency exchanges), and it must be
5827 easy to spend it. At the moment BitCoin seem fairly easy to get
5828 access to, but there are very few places to spend it. I am not really
5829 a regular user of any of the vendor types currently accepting BitCoin,
5830 so I wonder when my kind of shop would start accepting BitCoins. I
5831 would like to buy electronics, travels and subway tickets, not herbs
5832 and books. :) The currency is young, and this will improve over time
5833 if it become popular, but I suspect regular banks will start to lobby
5834 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5835 will claim it is helping fund terrorism and money laundering (which
5836 probably would be true, as is any currency in existence), but I
5837 believe the problems should be solved elsewhere and not by blaming
5838 currencies.&lt;/p&gt;
5839
5840 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5841 CPU intensive process that depend on a bit of luck as well (as one is
5842 competing against all the other miners currently spending CPU cycles
5843 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5844 BitCoin when this happen. Yesterday I came across the obvious way to
5845 join forces to increase ones changes of getting at least some coins,
5846 by coordinating the work on mining BitCoins across several machines
5847 and people, and sharing the result if one is lucky and get the 50
5848 BitCoins. Check out
5849 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5850 if this sounds interesting. I have not had time to try to set up a
5851 machine to participate there yet, but have seen that running on ones
5852 own for a few days have not yield any BitCoins througth mining
5853 yet.&lt;/p&gt;
5854
5855 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5856 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5857 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5858 it was interesting to read. The arguments presented seem to be
5859 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5860 </description>
5861 </item>
5862
5863 <item>
5864 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5865 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5866 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5867 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5868 <description>&lt;p&gt;With this weeks lawless
5869 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5870 attacks&lt;/a&gt; on Wikileak and
5871 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5872 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5873 not be trusted to handle money transactions.
5874 A blog post from
5875 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5876 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5877 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5878 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5879 some help from my friend to get it all running, and he even handed me
5880 some bitcoins to get started. I even donated a few bitcoins to Simon
5881 for helping me remember BitCoin.&lt;/p&gt;
5882
5883 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5884 crypto-currency, decentralised and handled using peer-to-peer
5885 networks. It allows anonymous transactions and prohibits central
5886 control over the transactions, making it impossible for governments
5887 and companies alike to block donations and other transactions. The
5888 source is free software, and while the key dependency wxWidgets 2.9
5889 for the graphical user interface is missing in Debian, the command
5890 line client builds just fine. Hopefully Jonas
5891 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5892 Debian&lt;/a&gt; soon.&lt;/p&gt;
5893
5894 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5895 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5896 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5897 currency &quot;stock&quot; markets where the exchange rate is decided. There
5898 are not many users so far, but the concept seems promising. If you
5899 want to get started and lack a friend with any bitcoins to spare,
5900 you can even get
5901 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5902 bitcoin at the time of writing). Use
5903 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5904 on the current exchange rates.&lt;/p&gt;
5905
5906 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5907 machines. If you want to support my activity, please send Bitcoin
5908 donations to the address
5909 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5910 </description>
5911 </item>
5912
5913 <item>
5914 <title>Why isn&#39;t Debian Edu using VLC?</title>
5915 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5916 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5917 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5918 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5919 presented, and the winner among the multimedia player were VLC.
5920 Personally, I like VLC, and it is my player of choice when I first try
5921 to play a video file or stream. Only if VLC fail will I drag out
5922 gmplayer to see if it can do better. The reason is mostly the failure
5923 model and trust. When VLC fail, it normally pop up a error message
5924 reporting the problem. When mplayer fail, it normally segfault or
5925 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5926
5927 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5928 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5929 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5930 plugin to play web videos seamlessly, and the VLC browser plugin is
5931 not very good. For example, it lack in-line control buttons, so there
5932 is no way for the user to pause the video. Also, when I
5933 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5934 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5935 failed on several video pages where mplayer based plugins worked. If
5936 the browser plugin for VLC was as good as the gecko-mediaplayer
5937 package (which uses mplayer), we would switch.&lt;/P&gt;
5938
5939 &lt;p&gt;While VLC is a good player, its user interface is slightly
5940 annoying. The most annoying feature is its inconsistent use of
5941 keyboard shortcuts. When the player is in full screen mode, its
5942 shortcuts are different from when it is playing the video in a window.
5943 For example, space only work as pause when in full screen mode. I
5944 wish it had consisten shortcuts and that space also would work when in
5945 window mode. Another nice shortcut in gmplayer is [enter] to restart
5946 the current video. It is very nice when playing short videos from the
5947 web and want to restart it when new people arrive to have a look at
5948 what is going on.&lt;/p&gt;
5949 </description>
5950 </item>
5951
5952 <item>
5953 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5954 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5955 <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>
5956 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5957 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5958 upgrade testing of the
5959 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5960 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5961 This seem like a very good idea, so I adjusted by test scripts and
5962 can now present the updated result from today:&lt;/p&gt;
5963
5964 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5965
5966 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5967
5968 &lt;blockquote&gt;&lt;p&gt;
5969 apache2.2-bin
5970 aptdaemon
5971 baobab
5972 binfmt-support
5973 browser-plugin-gnash
5974 cheese-common
5975 cli-common
5976 cups-pk-helper
5977 dmz-cursor-theme
5978 empathy
5979 empathy-common
5980 freedesktop-sound-theme
5981 freeglut3
5982 gconf-defaults-service
5983 gdm-themes
5984 gedit-plugins
5985 geoclue
5986 geoclue-hostip
5987 geoclue-localnet
5988 geoclue-manual
5989 geoclue-yahoo
5990 gnash
5991 gnash-common
5992 gnome
5993 gnome-backgrounds
5994 gnome-cards-data
5995 gnome-codec-install
5996 gnome-core
5997 gnome-desktop-environment
5998 gnome-disk-utility
5999 gnome-screenshot
6000 gnome-search-tool
6001 gnome-session-canberra
6002 gnome-system-log
6003 gnome-themes-extras
6004 gnome-themes-more
6005 gnome-user-share
6006 gstreamer0.10-fluendo-mp3
6007 gstreamer0.10-tools
6008 gtk2-engines
6009 gtk2-engines-pixbuf
6010 gtk2-engines-smooth
6011 hamster-applet
6012 libapache2-mod-dnssd
6013 libapr1
6014 libaprutil1
6015 libaprutil1-dbd-sqlite3
6016 libaprutil1-ldap
6017 libart2.0-cil
6018 libboost-date-time1.42.0
6019 libboost-python1.42.0
6020 libboost-thread1.42.0
6021 libchamplain-0.4-0
6022 libchamplain-gtk-0.4-0
6023 libcheese-gtk18
6024 libclutter-gtk-0.10-0
6025 libcryptui0
6026 libdiscid0
6027 libelf1
6028 libepc-1.0-2
6029 libepc-common
6030 libepc-ui-1.0-2
6031 libfreerdp-plugins-standard
6032 libfreerdp0
6033 libgconf2.0-cil
6034 libgdata-common
6035 libgdata7
6036 libgdu-gtk0
6037 libgee2
6038 libgeoclue0
6039 libgexiv2-0
6040 libgif4
6041 libglade2.0-cil
6042 libglib2.0-cil
6043 libgmime2.4-cil
6044 libgnome-vfs2.0-cil
6045 libgnome2.24-cil
6046 libgnomepanel2.24-cil
6047 libgpod-common
6048 libgpod4
6049 libgtk2.0-cil
6050 libgtkglext1
6051 libgtksourceview2.0-common
6052 libmono-addins-gui0.2-cil
6053 libmono-addins0.2-cil
6054 libmono-cairo2.0-cil
6055 libmono-corlib2.0-cil
6056 libmono-i18n-west2.0-cil
6057 libmono-posix2.0-cil
6058 libmono-security2.0-cil
6059 libmono-sharpzip2.84-cil
6060 libmono-system2.0-cil
6061 libmtp8
6062 libmusicbrainz3-6
6063 libndesk-dbus-glib1.0-cil
6064 libndesk-dbus1.0-cil
6065 libopal3.6.8
6066 libpolkit-gtk-1-0
6067 libpt2.6.7
6068 libpython2.6
6069 librpm1
6070 librpmio1
6071 libsdl1.2debian
6072 libsrtp0
6073 libssh-4
6074 libtelepathy-farsight0
6075 libtelepathy-glib0
6076 libtidy-0.99-0
6077 media-player-info
6078 mesa-utils
6079 mono-2.0-gac
6080 mono-gac
6081 mono-runtime
6082 nautilus-sendto
6083 nautilus-sendto-empathy
6084 p7zip-full
6085 pkg-config
6086 python-aptdaemon
6087 python-aptdaemon-gtk
6088 python-axiom
6089 python-beautifulsoup
6090 python-bugbuddy
6091 python-clientform
6092 python-coherence
6093 python-configobj
6094 python-crypto
6095 python-cupshelpers
6096 python-elementtree
6097 python-epsilon
6098 python-evolution
6099 python-feedparser
6100 python-gdata
6101 python-gdbm
6102 python-gst0.10
6103 python-gtkglext1
6104 python-gtksourceview2
6105 python-httplib2
6106 python-louie
6107 python-mako
6108 python-markupsafe
6109 python-mechanize
6110 python-nevow
6111 python-notify
6112 python-opengl
6113 python-openssl
6114 python-pam
6115 python-pkg-resources
6116 python-pyasn1
6117 python-pysqlite2
6118 python-rdflib
6119 python-serial
6120 python-tagpy
6121 python-twisted-bin
6122 python-twisted-conch
6123 python-twisted-core
6124 python-twisted-web
6125 python-utidylib
6126 python-webkit
6127 python-xdg
6128 python-zope.interface
6129 remmina
6130 remmina-plugin-data
6131 remmina-plugin-rdp
6132 remmina-plugin-vnc
6133 rhythmbox-plugin-cdrecorder
6134 rhythmbox-plugins
6135 rpm-common
6136 rpm2cpio
6137 seahorse-plugins
6138 shotwell
6139 software-center
6140 system-config-printer-udev
6141 telepathy-gabble
6142 telepathy-mission-control-5
6143 telepathy-salut
6144 tomboy
6145 totem
6146 totem-coherence
6147 totem-mozilla
6148 totem-plugins
6149 transmission-common
6150 xdg-user-dirs
6151 xdg-user-dirs-gtk
6152 xserver-xephyr
6153 &lt;/p&gt;&lt;/blockquote&gt;
6154
6155 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6156
6157 &lt;blockquote&gt;&lt;p&gt;
6158 cheese
6159 ekiga
6160 eog
6161 epiphany-extensions
6162 evolution-exchange
6163 fast-user-switch-applet
6164 file-roller
6165 gcalctool
6166 gconf-editor
6167 gdm
6168 gedit
6169 gedit-common
6170 gnome-games
6171 gnome-games-data
6172 gnome-nettool
6173 gnome-system-tools
6174 gnome-themes
6175 gnuchess
6176 gucharmap
6177 guile-1.8-libs
6178 libavahi-ui0
6179 libdmx1
6180 libgalago3
6181 libgtk-vnc-1.0-0
6182 libgtksourceview2.0-0
6183 liblircclient0
6184 libsdl1.2debian-alsa
6185 libspeexdsp1
6186 libsvga1
6187 rhythmbox
6188 seahorse
6189 sound-juicer
6190 system-config-printer
6191 totem-common
6192 transmission-gtk
6193 vinagre
6194 vino
6195 &lt;/p&gt;&lt;/blockquote&gt;
6196
6197 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6198
6199 &lt;blockquote&gt;&lt;p&gt;
6200 gstreamer0.10-gnomevfs
6201 &lt;/p&gt;&lt;/blockquote&gt;
6202
6203 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6204
6205 &lt;blockquote&gt;&lt;p&gt;
6206 [nothing]
6207 &lt;/p&gt;&lt;/blockquote&gt;
6208
6209 &lt;p&gt;This is for KDE:&lt;/p&gt;
6210
6211 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6212
6213 &lt;blockquote&gt;&lt;p&gt;
6214 ksmserver
6215 &lt;/p&gt;&lt;/blockquote&gt;
6216
6217 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6218
6219 &lt;blockquote&gt;&lt;p&gt;
6220 kwin
6221 network-manager-kde
6222 &lt;/p&gt;&lt;/blockquote&gt;
6223
6224 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6225
6226 &lt;blockquote&gt;&lt;p&gt;
6227 arts
6228 dolphin
6229 freespacenotifier
6230 google-gadgets-gst
6231 google-gadgets-xul
6232 kappfinder
6233 kcalc
6234 kcharselect
6235 kde-core
6236 kde-plasma-desktop
6237 kde-standard
6238 kde-window-manager
6239 kdeartwork
6240 kdeartwork-emoticons
6241 kdeartwork-style
6242 kdeartwork-theme-icon
6243 kdebase
6244 kdebase-apps
6245 kdebase-workspace
6246 kdebase-workspace-bin
6247 kdebase-workspace-data
6248 kdeeject
6249 kdelibs
6250 kdeplasma-addons
6251 kdeutils
6252 kdewallpapers
6253 kdf
6254 kfloppy
6255 kgpg
6256 khelpcenter4
6257 kinfocenter
6258 konq-plugins-l10n
6259 konqueror-nsplugins
6260 kscreensaver
6261 kscreensaver-xsavers
6262 ktimer
6263 kwrite
6264 libgle3
6265 libkde4-ruby1.8
6266 libkonq5
6267 libkonq5-templates
6268 libnetpbm10
6269 libplasma-ruby
6270 libplasma-ruby1.8
6271 libqt4-ruby1.8
6272 marble-data
6273 marble-plugins
6274 netpbm
6275 nuvola-icon-theme
6276 plasma-dataengines-workspace
6277 plasma-desktop
6278 plasma-desktopthemes-artwork
6279 plasma-runners-addons
6280 plasma-scriptengine-googlegadgets
6281 plasma-scriptengine-python
6282 plasma-scriptengine-qedje
6283 plasma-scriptengine-ruby
6284 plasma-scriptengine-webkit
6285 plasma-scriptengines
6286 plasma-wallpapers-addons
6287 plasma-widget-folderview
6288 plasma-widget-networkmanagement
6289 ruby
6290 sweeper
6291 update-notifier-kde
6292 xscreensaver-data-extra
6293 xscreensaver-gl
6294 xscreensaver-gl-extra
6295 xscreensaver-screensaver-bsod
6296 &lt;/p&gt;&lt;/blockquote&gt;
6297
6298 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6299
6300 &lt;blockquote&gt;&lt;p&gt;
6301 ark
6302 google-gadgets-common
6303 google-gadgets-qt
6304 htdig
6305 kate
6306 kdebase-bin
6307 kdebase-data
6308 kdepasswd
6309 kfind
6310 klipper
6311 konq-plugins
6312 konqueror
6313 ksysguard
6314 ksysguardd
6315 libarchive1
6316 libcln6
6317 libeet1
6318 libeina-svn-06
6319 libggadget-1.0-0b
6320 libggadget-qt-1.0-0b
6321 libgps19
6322 libkdecorations4
6323 libkephal4
6324 libkonq4
6325 libkonqsidebarplugin4a
6326 libkscreensaver5
6327 libksgrd4
6328 libksignalplotter4
6329 libkunitconversion4
6330 libkwineffects1a
6331 libmarblewidget4
6332 libntrack-qt4-1
6333 libntrack0
6334 libplasma-geolocation-interface4
6335 libplasmaclock4a
6336 libplasmagenericshell4
6337 libprocesscore4a
6338 libprocessui4a
6339 libqalculate5
6340 libqedje0a
6341 libqtruby4shared2
6342 libqzion0a
6343 libruby1.8
6344 libscim8c2a
6345 libsmokekdecore4-3
6346 libsmokekdeui4-3
6347 libsmokekfile3
6348 libsmokekhtml3
6349 libsmokekio3
6350 libsmokeknewstuff2-3
6351 libsmokeknewstuff3-3
6352 libsmokekparts3
6353 libsmokektexteditor3
6354 libsmokekutils3
6355 libsmokenepomuk3
6356 libsmokephonon3
6357 libsmokeplasma3
6358 libsmokeqtcore4-3
6359 libsmokeqtdbus4-3
6360 libsmokeqtgui4-3
6361 libsmokeqtnetwork4-3
6362 libsmokeqtopengl4-3
6363 libsmokeqtscript4-3
6364 libsmokeqtsql4-3
6365 libsmokeqtsvg4-3
6366 libsmokeqttest4-3
6367 libsmokeqtuitools4-3
6368 libsmokeqtwebkit4-3
6369 libsmokeqtxml4-3
6370 libsmokesolid3
6371 libsmokesoprano3
6372 libtaskmanager4a
6373 libtidy-0.99-0
6374 libweather-ion4a
6375 libxklavier16
6376 libxxf86misc1
6377 okteta
6378 oxygencursors
6379 plasma-dataengines-addons
6380 plasma-scriptengine-superkaramba
6381 plasma-widget-lancelot
6382 plasma-widgets-addons
6383 plasma-widgets-workspace
6384 polkit-kde-1
6385 ruby1.8
6386 systemsettings
6387 update-notifier-common
6388 &lt;/p&gt;&lt;/blockquote&gt;
6389
6390 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6391 aptitude a bit more similar, but there are still quite a lott of
6392 differences. I have no idea what packages should be installed after
6393 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6394 </description>
6395 </item>
6396
6397 <item>
6398 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6399 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6400 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6401 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6402 <description>&lt;p&gt;Most of the computers in use by the
6403 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6404 are virtual machines. And they have been Xen machines running on a
6405 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6406 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6407 bit harder that it could have been, because we set up the Xen virtual
6408 machines to get the virtual partitions from LVM, which as far as I
6409 know is not supported by KVM. So to migrate, we had to convert
6410 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6411
6412 &lt;p&gt;I found
6413 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6414 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6415 migration. It uses qemu-img from the qemu package to make the disk
6416 image, parted to partition it, losetup and kpartx to present the disk
6417 image partions as devices, and dd to copy the data. I NFS mounted the
6418 new servers storage area on the old server to do the migration.&lt;/p&gt;
6419
6420 &lt;pre&gt;
6421 #!/bin/sh
6422
6423 # Based on
6424 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6425
6426 set -e
6427 set -x
6428
6429 if [ -z &quot;$1&quot; ] ; then
6430 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6431 exit 1
6432 else
6433 host=&quot;$1&quot;
6434 fi
6435
6436 if [ ! -e /dev/vg_data/$host-disk ] ; then
6437 echo &quot;error: unable to find LVM volume for $host&quot;
6438 exit 1
6439 fi
6440
6441 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6442 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6443 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6444 totalsize=$(( ( $disksize + $swapsize ) ))
6445
6446 img=$host.img
6447 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6448 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6449
6450 parted $img mklabel msdos
6451 parted $img mkpart primary linux-swap 0 $disksize
6452 parted $img mkpart primary ext2 $disksize $totalsize
6453 parted $img set 1 boot on
6454
6455 modprobe dm-mod
6456 losetup /dev/loop0 $img
6457 kpartx -a /dev/loop0
6458
6459 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6460 fsck.ext3 -f /dev/mapper/loop0p1 || true
6461 mkswap /dev/mapper/loop0p2
6462
6463 kpartx -d /dev/loop0
6464 losetup -d /dev/loop0
6465 &lt;/pre&gt;
6466
6467 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6468 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6469
6470 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6471 the new disk image attached, installed grub-pc and linux-image-686 and
6472 set up grub to boot from the disk image. After this, the KVM machines
6473 seem to work just fine.&lt;/p&gt;
6474 </description>
6475 </item>
6476
6477 <item>
6478 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6479 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6480 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6481 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6482 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6483 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6484 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6485 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6486
6487 &lt;p&gt;I still do not know what a correct migration should look like, so I
6488 report any differences between apt and aptitude and hope someone else
6489 can see if anything should be changed.&lt;/p&gt;
6490
6491 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6492
6493 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6494
6495 &lt;blockquote&gt;&lt;p&gt;
6496 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6497 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6498 dmz-cursor-theme empathy empathy-common finger
6499 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6500 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6501 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6502 gnome-cards-data gnome-codec-install gnome-core
6503 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6504 gnome-search-tool gnome-session-canberra gnome-spell
6505 gnome-system-log gnome-themes-extras gnome-themes-more
6506 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6507 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6508 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6509 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6510 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6511 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6512 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6513 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6514 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6515 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6516 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6517 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6518 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6519 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6520 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6521 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6522 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6523 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6524 libmono-security2.0-cil libmono-sharpzip2.84-cil
6525 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6526 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6527 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6528 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6529 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6530 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6531 libxalan2-java libxerces2-java media-player-info mesa-utils
6532 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6533 nautilus-sendto-empathy openoffice.org-writer2latex
6534 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6535 python-aptdaemon python-aptdaemon-gtk python-axiom
6536 python-beautifulsoup python-bugbuddy python-clientform
6537 python-coherence python-configobj python-crypto python-cupshelpers
6538 python-cupsutils python-eggtrayicon python-elementtree
6539 python-epsilon python-evolution python-feedparser python-gdata
6540 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6541 python-gtksourceview2 python-httplib2 python-louie python-mako
6542 python-markupsafe python-mechanize python-nevow python-notify
6543 python-opengl python-openssl python-pam python-pkg-resources
6544 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6545 python-tagpy python-twisted-bin python-twisted-conch
6546 python-twisted-core python-twisted-web python-utidylib python-webkit
6547 python-xdg python-zope.interface remmina remmina-plugin-data
6548 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6549 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6550 software-center svgalibg1 system-config-printer-udev
6551 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6552 totem totem-coherence totem-mozilla totem-plugins
6553 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6554 zip
6555 &lt;/p&gt;&lt;/blockquote&gt;
6556
6557 Installed using apt-get, removed with aptitude
6558
6559 &lt;blockquote&gt;&lt;p&gt;
6560 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6561 epiphany-extensions epiphany-gecko evolution-exchange
6562 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6563 gedit-common gnome-app-install gnome-games gnome-games-data
6564 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6565 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6566 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6567 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6568 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6569 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6570 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6571 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6572 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6573 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6574 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6575 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6576 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6577 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6578 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6579 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6580 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6581 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6582 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6583 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6584 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6585 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6586 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6587 sound-juicer swfdec-gnome system-config-printer totem-common
6588 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6589 &lt;/p&gt;&lt;/blockquote&gt;
6590
6591 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6592
6593 &lt;blockquote&gt;&lt;p&gt;
6594 gstreamer0.10-gnomevfs
6595 &lt;/p&gt;&lt;/blockquote&gt;
6596
6597 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6598
6599 &lt;blockquote&gt;&lt;p&gt;
6600 [nothing]
6601 &lt;/p&gt;&lt;/blockquote&gt;
6602
6603 &lt;p&gt;This is for KDE:&lt;/p&gt;
6604
6605 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6606
6607 &lt;blockquote&gt;&lt;p&gt;
6608 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6609 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6610 ghostscript-x git gnome-audio gnugo granatier gs-common
6611 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6612 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6613 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6614 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6615 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6616 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6617 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6618 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6619 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6620 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6621 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6622 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6623 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6624 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6625 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6626 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6627 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6628 libkrossui4 libmailtools-perl libmime-tools-perl
6629 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6630 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6631 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6632 lirc luatex marble networkstatus noatun-plugins
6633 openoffice.org-writer2latex palapeli palapeli-data parley
6634 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6635 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6636 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6637 ttf-sazanami-gothic
6638 &lt;/p&gt;&lt;/blockquote&gt;
6639
6640 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6641
6642 &lt;blockquote&gt;&lt;p&gt;
6643 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6644 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6645 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6646 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6647 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6648 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6649 kitchensync kiten kjumpingcube klatin klettres klickety klines
6650 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6651 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6652 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6653 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6654 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6655 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6656 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6657 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6658 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6659 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6660 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6661 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6662 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6663 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6664 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6665 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6666 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6667 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6668 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6669 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6670 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6671 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6672 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6673 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6674 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6675 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6676 &lt;/p&gt;&lt;/blockquote&gt;
6677
6678 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6679
6680 &lt;blockquote&gt;&lt;p&gt;
6681 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6682 kdeartwork kdebase kdebase-apps kdebase-workspace
6683 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6684 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6685 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6686 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6687 xscreensaver-screensaver-bsod
6688 &lt;/p&gt;&lt;/blockquote&gt;
6689
6690 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6691
6692 &lt;blockquote&gt;&lt;p&gt;
6693 kdebase-bin konq-plugins konqueror
6694 &lt;/p&gt;&lt;/blockquote&gt;
6695 </description>
6696 </item>
6697
6698 <item>
6699 <title>Gnash buildbot slave and Debian kfreebsd</title>
6700 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6701 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6702 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6703 <description>&lt;p&gt;Answering
6704 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6705 call from the Gnash project&lt;/a&gt; for
6706 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6707 current source, I have set up a virtual KVM machine on the Debian
6708 Edu/Skolelinux virtualization host to test the git source on
6709 Debian/Squeeze. I hope this can help the developers in getting new
6710 releases out more often.&lt;/p&gt;
6711
6712 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6713 I have considered setting up a &lt;a
6714 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6715 machine as well. I have also considered using the kfreebsd
6716 architecture in Debian as a file server in NUUG to get access to the 5
6717 TB zfs volume we currently use to store DV video. Because of this, I
6718 finally got around to do a test installation of Debian/Squeeze with
6719 kfreebsd. Installation went fairly smooth, thought I noticed some
6720 visual glitches in the cdebconf dialogs (black cursor left on the
6721 screen at random locations). Have not gotten very far with the
6722 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6723 fatal problem. Have to spend some more time on it to see if it is
6724 useful as a file server for NUUG. Will try to find time to set up a
6725 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6726 </description>
6727 </item>
6728
6729 <item>
6730 <title>Debian in 3D</title>
6731 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6732 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6733 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6734 <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;
6735
6736 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6737 3D linked in from
6738 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6739 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6740 </description>
6741 </item>
6742
6743 <item>
6744 <title>Software updates 2010-10-24</title>
6745 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6746 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6747 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6748 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6749
6750 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6751 raise money for the project is going well. The lower limit of 10
6752 signers was reached in 24 hours, and so far 13 people have signed it.
6753 More signers and more funding is most welcome, and I am really curious
6754 how far we can get before the time limit of December 24 is reached.
6755 :)&lt;/p&gt;
6756
6757 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6758 about what appear to be a great code coverage tool capable of
6759 generating code coverage stats without any changes to the source code.
6760 It is called
6761 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6762 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6763 It is missing in Debian, but the git source built just fine in Squeeze
6764 after I installed libelf-dev, libdwarf-dev, pkg-config and
6765 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6766 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6767
6768 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6769 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6770 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6771 alpha test release of the Squeeze based Debian Edu /
6772 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6773 release. Give it a try if you need a complete linux solution for your
6774 school, including central infrastructure server, workstations, thin
6775 client servers and diskless workstations. A nice touch added
6776 yesterday is RDP support on the thin client servers, for windows
6777 clients to get a Linux desktop on request.&lt;/p&gt;
6778 </description>
6779 </item>
6780
6781 <item>
6782 <title>Some notes on Flash in Debian and Debian Edu</title>
6783 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6784 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6785 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6786 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6787 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6788 second most popular used package that is missing in Debian. The sixth
6789 most popular is flashplayer-mozilla. This is a clear indication that
6790 working flash is important for Debian users. Around 10 percent of the
6791 users submitting data to popcon.debian.org have this package
6792 installed.&lt;/p&gt;
6793
6794 &lt;p&gt;In the report written by Lars Risan in August 2008
6795&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
6796 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6797 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6798 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6799 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6800 web sites require Flash to work, and lacking working Flash support in
6801 the web browser and the problems with installing it was perceived as a
6802 good reason to stay with Windows.&lt;/p&gt;
6803
6804 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6805 said to be the retarded cousin that did not really understand
6806 everything you told him but could work fairly well. This was a
6807 comment regarding the problems Linux have with proprietary formats and
6808 non-standard web pages, and is sad because it exposes a fairly common
6809 understanding of whose fault it is if web pages that only work in for
6810 example Internet Explorer 6 fail to work on Firefox, and funny because
6811 it explain very well how annoying it is for users when Linux
6812 distributions do not work with the documents they receive or the web
6813 pages they want to visit.&lt;/p&gt;
6814
6815 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6816 and Debian Edu to have a well working Flash implementation in the
6817 distribution, to get at least popular sites as Youtube and Google
6818 Video to working out of the box. For Squeeze, Debian have the chance
6819 to include the latest version of Gnash that will make this happen, as
6820 the new release 0.8.8 was published a few weeks ago and is resting in
6821 unstable. The new version work with more sites that version 0.8.7.
6822 The Gnash maintainers have asked for a freeze exception, but the
6823 release team have not had time to reply to it yet. I hope they agree
6824 with me that Flash is important for the Debian desktop users, and thus
6825 accept the new package into Squeeze.&lt;/p&gt;
6826 </description>
6827 </item>
6828
6829 <item>
6830 <title>Circular package dependencies harms apt recovery</title>
6831 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6833 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6834 <description>&lt;p&gt;I discovered this while doing
6835 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6836 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6837 in Debian still got circular dependencies, and it is often claimed
6838 that apt and aptitude should be able to handle this just fine, but
6839 some times these dependency loops causes apt to fail.&lt;/p&gt;
6840
6841 &lt;p&gt;An example is from todays
6842 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6843 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6844 causes perl-modules to fail to upgrade. The cause is simple. If a
6845 package fail to unpack, then only part of packages with the circular
6846 dependency might end up being unpacked when unpacking aborts, and the
6847 ones already unpacked will fail to configure in the recovery phase
6848 because its dependencies are unavailable.&lt;/p&gt;
6849
6850 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6851
6852 &lt;blockquote&gt;&lt;pre&gt;
6853 dpkg: dependency problems prevent configuration of perl-modules:
6854 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6855 Version of perl on system is 5.10.0-19lenny2.
6856 dpkg: error processing perl-modules (--configure):
6857 dependency problems - leaving unconfigured
6858 &lt;/pre&gt;&lt;/blockquote&gt;
6859
6860 &lt;p&gt;The perl/perl-modules circular dependency is already
6861 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6862 hopefully be solved as soon as possible, but it is not the only one,
6863 and each one of these loops in the dependency tree can cause similar
6864 failures. Of course, they only occur when there are bugs in other
6865 packages causing the unpacking to fail, but it is rather nasty when
6866 the failure of one package causes the problem to become worse because
6867 of dependency loops.&lt;/p&gt;
6868
6869 &lt;p&gt;Thanks to
6870 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6871 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6872 dependencies
6873 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6874 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6875
6876 &lt;p&gt;Todays testing also exposed a bug in
6877 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6878 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6879 apt-get and aptitude, the latter possibly caused by some circular
6880 dependency. Reported both to BTS to try to get someone to look at
6881 it.&lt;/p&gt;
6882 </description>
6883 </item>
6884
6885 <item>
6886 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6887 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6888 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6889 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6890 <description>&lt;p&gt;This is a
6891 &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;
6892 on my
6893 &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
6894 work&lt;/a&gt; on
6895 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6896 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6897
6898 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6899 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6900 and dhcp3-server-ldap in Debian use the LDAP server. The two
6901 implementations are quite different in how they use LDAP.&lt;/p&gt;
6902
6903 To get this information, I started slapd with debugging enabled and
6904 dumped the debug output to a file to get the LDAP searches performed
6905 on a Debian Edu main-server. Here is a summary.
6906
6907 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6908
6909 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6910 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6911 the web.
6912
6913 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6914 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6915 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6916 reverse entries are in two different subtrees in LDAP with a structure
6917 based on the DNS names, as in tjener.intern and
6918 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6919
6920 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6921 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6922 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6923 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6924 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6925 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6926 forward entries, it is looking for attributes named dnsttl, arecord,
6927 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6928 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6929 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6930 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6931 spfrecord and modifytimestamp. For reverse entries it is looking for
6932 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6933 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6934 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6935 ldapsearch commands could look like this:&lt;/p&gt;
6936
6937 &lt;blockquote&gt;&lt;pre&gt;
6938 ldapsearch -h ldap \
6939 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6940 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6941 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6942 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6943 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6944 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6945
6946 ldapsearch -h ldap \
6947 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6948 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6949 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6950 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6951 srvrecord naptrrecord modifytimestamp
6952 &lt;/pre&gt;&lt;/blockquote&gt;
6953
6954 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6955 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6956 example LDAP objects used there. In addition to these objects, the
6957 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6958 also exist.&lt;/p&gt;
6959
6960 &lt;blockquote&gt;&lt;pre&gt;
6961 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6962 objectclass: top
6963 objectclass: dnsdomain
6964 objectclass: domainrelatedobject
6965 dc: tjener
6966 arecord: 10.0.2.2
6967 associateddomain: tjener.intern
6968
6969 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6970 objectclass: top
6971 objectclass: dnsdomain2
6972 objectclass: domainrelatedobject
6973 dc: 2
6974 ptrrecord: tjener.intern
6975 associateddomain: 2.2.0.10.in-addr.arpa
6976 &lt;/pre&gt;&lt;/blockquote&gt;
6977
6978 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6979 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6980 same base as in the tree mode for a object with filter
6981 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6982 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6983 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6984 naptrrecord and modifytimestamp. For reverse entires it also do a
6985 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6986 and the requested attributes are associateddomain, dnsttl and
6987 modifytimestamp. In short, in strict mode the objects with ptrrecord
6988 go away, and the arecord attribute in the forward object is used
6989 instead.&lt;/p&gt;
6990
6991 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6992 like this:&lt;/p&gt;
6993
6994 &lt;blockquote&gt;&lt;pre&gt;
6995 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6996 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6997 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6998 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6999 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7000 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7001
7002 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7003 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
7004 &lt;/pre&gt;&lt;/blockquote&gt;
7005
7006 &lt;p&gt;In addition to the forward and reverse searches , there is also a
7007 search for SOA records, which behave similar to the forward and
7008 reverse lookups.&lt;/p&gt;
7009
7010 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
7011 specify any objectclass names, and instead look for the attributes it
7012 need to generate a DNS reply. This make it able to work with any
7013 objectclass that provide the needed attributes.&lt;/p&gt;
7014
7015 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
7016 dnsdomain2 schemas. The latter is used for reverse entries like
7017 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
7018
7019 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
7020 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7021 attributes) and domainrelatedobject (for associatedDomain). The use
7022 of structural object classes make it impossible to combine these
7023 classes with the object classes used by DHCP.&lt;/p&gt;
7024
7025 &lt;p&gt;There are other schemas that could be used too, for example the
7026 dnszone structural object class used by Gosa and bind-sdb for the DNS
7027 attributes combined with the domainrelatedobject object class, but in
7028 this case some unused attributes would have to be included as well
7029 (zonename and relativedomainname).&lt;/p&gt;
7030
7031 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
7032 mode and not use any of the existing objectclasses (dnsdomain,
7033 dnsdomain2 and dnszone) when one want to combine the DNS information
7034 with DHCP information, and instead create a auxiliary object class
7035 defined something like this (using the attributes defined for
7036 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
7037
7038 &lt;blockquote&gt;&lt;pre&gt;
7039 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
7040 SUP top
7041 AUXILIARY
7042 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7043 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7044 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7045 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7046 A6Record $ DNAMERecord
7047 ))
7048 &lt;/pre&gt;&lt;/blockquote&gt;
7049
7050 &lt;p&gt;This will allow any object to become a DNS entry when combined with
7051 the domainrelatedobject object class, and allow any entity to include
7052 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
7053 developers asking for their view on this schema and if they are
7054 interested in providing such schema with PowerDNS, and I hope my
7055 message will be accepted into their mailing list soon.&lt;/p&gt;
7056
7057 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
7058
7059 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
7060 the object attributes, and then uses the attributes it want. This
7061 make it harder to figure out exactly what attributes are used, but
7062 thanks to the working example in Debian Edu I can at least get an idea
7063 what is needed without having to read the source code.&lt;/p&gt;
7064
7065 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
7066 search filter to use to locate the correct dhcpServer entity is
7067 stored. These are the relevant entries from
7068 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
7069
7070 &lt;blockquote&gt;&lt;pre&gt;
7071 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
7072 ldap-dhcp-server-cn &quot;dhcp&quot;;
7073 &lt;/pre&gt;&lt;/blockquote&gt;
7074
7075 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
7076 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
7077 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
7078 search result is this entry:&lt;/p&gt;
7079
7080 &lt;blockquote&gt;&lt;pre&gt;
7081 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7082 cn: dhcp
7083 objectClass: top
7084 objectClass: dhcpServer
7085 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7086 &lt;/pre&gt;&lt;/blockquote&gt;
7087
7088 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
7089 subtree with DHCP configuration. The DHCP configuration subtree base
7090 is located using a base scope search with base &quot;cn=DHCP
7091 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
7092 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
7093 The search result is this entry:&lt;/p&gt;
7094
7095 &lt;blockquote&gt;&lt;pre&gt;
7096 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7097 cn: DHCP Config
7098 objectClass: top
7099 objectClass: dhcpService
7100 objectClass: dhcpOptions
7101 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7102 dhcpStatements: ddns-update-style none
7103 dhcpStatements: authoritative
7104 dhcpOption: smtp-server code 69 = array of ip-address
7105 dhcpOption: www-server code 72 = array of ip-address
7106 dhcpOption: wpad-url code 252 = text
7107 &lt;/pre&gt;&lt;/blockquote&gt;
7108
7109 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
7110 all the DHCP configuration is loaded, it is ready to receive requests.
7111 The subtree in Debian Edu contain objects with object classes
7112 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7113 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7114 and information about netmasks, dynamic range etc. Leaving out the
7115 details here because it is not relevant for the focus of my
7116 investigation, which is to see if it is possible to merge dns and dhcp
7117 related computer objects.&lt;/p&gt;
7118
7119 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
7120 of the client (00:00:00:00:00:00 in this example), using a subtree
7121 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
7122 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7123 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
7124 like:&lt;/p&gt;
7125
7126 &lt;blockquote&gt;&lt;pre&gt;
7127 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7128 cn: hostname
7129 objectClass: top
7130 objectClass: dhcpHost
7131 dhcpHWAddress: ethernet 00:00:00:00:00:00
7132 dhcpStatements: fixed-address hostname
7133 &lt;/pre&gt;&lt;/blockquote&gt;
7134
7135 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
7136 The object classes need to have fixed names, and the configuration
7137 need to be stored in a fairly specific LDAP structure. On the
7138 positive side, the invidiual dhcpHost entires can be anywhere without
7139 the DN pointed to by the dhcpServer entries. The latter should make
7140 it possible to group all host entries in a subtree next to the
7141 configuration entries, and this subtree can also be shared with the
7142 DNS server if the schema proposed above is combined with the dhcpHost
7143 structural object class.
7144
7145 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
7146
7147 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
7148 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
7149 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
7150 allowing DNS objects to be stored anywhere under the base cn specified
7151 in the configuration.&lt;/p&gt;
7152
7153 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
7154 regarding which LDAP schemas to use and which LDAP structure to use.
7155 I guess one could implement ones own schema, as long as the
7156 objectclasses and attributes have the names used, but this do not
7157 really help when the DHCP subtree need to have a fairly fixed
7158 structure.&lt;/p&gt;
7159
7160 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
7161 this might work for Debian Edu:&lt;/p&gt;
7162
7163 &lt;blockquote&gt;&lt;pre&gt;
7164 ou=services
7165 cn=machine-info (dhcpService) - dhcpServiceDN points here
7166 cn=dhcp (dhcpServer)
7167 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7168 cn=10.0.2.0 (dhcpSubnet)
7169 cn=group1 (dhcpGroup/dhcpOptions)
7170 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7171 cn=192.168.0.0 (dhcpSubnet)
7172 cn=group1 (dhcpGroup/dhcpOptions)
7173 ou=machines - PowerDNS base points here
7174 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7175 &lt;/pre&gt;&lt;/blockquote&gt;
7176
7177 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
7178 entries to be in the dhcpGroup subtrees, the entries can be stored
7179 there instead of a common machines subtree, and the PowerDNS base
7180 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
7181
7182 &lt;p&gt;The combined object under the machines subtree would look something
7183 like this:&lt;/p&gt;
7184
7185 &lt;blockquote&gt;&lt;pre&gt;
7186 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7187 dc: hostname
7188 objectClass: top
7189 objectClass: dhcpHost
7190 objectclass: domainrelatedobject
7191 objectclass: dnsDomainAux
7192 associateddomain: hostname.intern
7193 arecord: 10.11.12.13
7194 dhcpHWAddress: ethernet 00:00:00:00:00:00
7195 dhcpStatements: fixed-address hostname.intern
7196 &lt;/pre&gt;&lt;/blockquote&gt;
7197
7198 &lt;/p&gt;One could even add the LTSP configuration associated with a given
7199 machine, as long as the required attributes are available in a
7200 auxiliary object class.&lt;/p&gt;
7201 </description>
7202 </item>
7203
7204 <item>
7205 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
7206 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
7207 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
7208 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
7209 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
7210 DHCP services in Debian Edu to use the same LDAP objects for a given
7211 computer, to avoid the possibility of having a inconsistent state for
7212 a computer in LDAP (as in DHCP but no DNS entry or the other way
7213 around) and make it easier to add computers to LDAP.&lt;/p&gt;
7214
7215 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
7216 information finally found a solution that seem to work.&lt;/p&gt;
7217
7218 &lt;p&gt;The old setup required three LDAP objects for a given computer.
7219 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7220 we switch powerdns to use its strict LDAP method (ldap-method=strict
7221 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7222 merged into one while making it impossible to transfer the reverse map
7223 to a slave DNS server.&lt;/p&gt;
7224
7225 &lt;p&gt;If we also replace the object class used to get the DNS related
7226 attributes to one allowing these attributes to be combined with the
7227 dhcphost object class, we can merge the DNS and DHCP entries into one.
7228 I&#39;ve written such object class in the dnsdomainaux.schema file (need
7229 proper OIDs, but that is a minor issue), and tested the setup. It
7230 seem to work.&lt;/p&gt;
7231
7232 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
7233 for both DNS and DHCP, and even the LTSP configuration I suggested in
7234 an earlier email. The combined LDAP object will look something like
7235 this:&lt;/p&gt;
7236
7237 &lt;blockquote&gt;&lt;pre&gt;
7238 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7239 cn: hostname
7240 objectClass: dhcphost
7241 objectclass: domainrelatedobject
7242 objectclass: dnsdomainaux
7243 associateddomain: hostname.intern
7244 arecord: 10.11.12.13
7245 dhcphwaddress: ethernet 00:00:00:00:00:00
7246 dhcpstatements: fixed-address hostname
7247 ldapconfigsound: Y
7248 &lt;/pre&gt;&lt;/blockquote&gt;
7249
7250 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
7251 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7252 before asking DNS to resolve the fixed-adddress. LTSP will use
7253 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
7254
7255 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
7256 dhcphost in a different location, to allow us to put the objects
7257 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7258 that. If I can&#39;t figure out a way to do that, we can still get rid of
7259 the hosts subtree and move all its content into the DHCP Config tree
7260 (which probably should be renamed to be more related to the new
7261 content. I suspect cn=dnsdhcp,ou=services or something like that
7262 might be a good place to put it.&lt;/p&gt;
7263
7264 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7265 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7266 </description>
7267 </item>
7268
7269 <item>
7270 <title>Idea for storing LTSP configuration in LDAP</title>
7271 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7272 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7273 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7274 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7275 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7276 clients, and that this can be used to fetch configuration from LDAP if
7277 Debian Edu choose to store configuration there.&lt;/p&gt;
7278
7279 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7280 to get configuration from LDAP. The idea is to look up the MAC
7281 address of the client in LDAP, and look for attributes on the form
7282 ltspconfigsetting=value, and use this to export SETTING=value to the
7283 LTSP clients.&lt;/p&gt;
7284
7285 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7286 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7287 allowing us to store all information about a computer in one place.&lt;/p&gt;
7288
7289 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7290 this approach. A real LDAP schema for the ltspClientAux objectclass
7291 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7292
7293 &lt;blockquote&gt;&lt;pre&gt;
7294 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7295 #
7296 # Fetch LTSP client settings from LDAP based on MAC address
7297 #
7298 # Uses ethernet address as stored in the dhcpHost objectclass using
7299 # the dhcpHWAddress attribute or ethernet address stored in the
7300 # ieee802Device objectclass with the macAddress attribute.
7301 #
7302 # This module is written to be schema agnostic, and only depend on the
7303 # existence of attribute names.
7304 #
7305 # The LTSP configuration variables are saved directly using a
7306 # ltspConfig prefix and uppercasing the rest of the attribute name.
7307 # To set the SERVER variable, set the ltspConfigServer attribute.
7308 #
7309 # Some LDAP schema should be created with all the relevant
7310 # configuration settings. Something like this should work:
7311 #
7312 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7313 # SUP top
7314 # AUXILIARY
7315 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7316
7317 LDAPSERVER=$(debian-edu-ldapserver)
7318 if [ &quot;$LDAPSERVER&quot; ] ; then
7319 LDAPBASE=$(debian-edu-ldapserver -b)
7320 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7321 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7322 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7323 grep &#39;^ltspConfig&#39; | while read attr value ; do
7324 # Remove prefix and convert to upper case
7325 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7326 # bass value on to clients
7327 eval &quot;$attr=$value; export $attr&quot;
7328 done
7329 done
7330 fi
7331 &lt;/pre&gt;&lt;/blockquote&gt;
7332
7333 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7334 the while block might end up in a subshell causing the variables set
7335 there to not show up in ltsp-config, but if that is the case I am sure
7336 the code can be restructured to make sure the variables are passed on.
7337 I expect that can be solved with some testing. :)&lt;/p&gt;
7338
7339 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7340 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7341
7342 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7343 configuration in LDAP that was created around year 2000 by
7344 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7345 Xperience, Inc., 2000&lt;/a&gt;. I found its
7346 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7347 personal home page over at redhat.com.&lt;/p&gt;
7348 </description>
7349 </item>
7350
7351 <item>
7352 <title>jXplorer, a very nice LDAP GUI</title>
7353 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7354 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7355 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7356 <description>&lt;p&gt;Since
7357 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7358 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7359 LDAP GUI that is even better than luma. The java application
7360 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7361 moving LDAP objects and subtrees using drag-and-drop, and can
7362 authenticate using Kerberos. I have only tested the Kerberos
7363 authentication, but do not have a LDAP setup allowing me to rewrite
7364 LDAP with my test user yet. It is
7365 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7366 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7367 have with it is how it handle errors. If something go wrong, its
7368 non-intuitive behaviour require me to go through some query work list
7369 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7370 </description>
7371 </item>
7372
7373 <item>
7374 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7375 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7376 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7377 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7378 <description>&lt;p&gt;Here is a short update on my &lt;a
7379 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7380 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7381 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7382 not reporting the status for KDE, because the upgrade crashes when
7383 aptitude try because of missing conflicts
7384 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7385 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7386
7387 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7388 complete list of the installed packages. Based on this I see these
7389 differences when I did a test run today. As usual, I do not really
7390 know what the correct set of packages would be, but thought it best to
7391 publish the difference.&lt;/p&gt;
7392
7393 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7394
7395 &lt;blockquote&gt;&lt;p&gt;
7396 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7397 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7398 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7399 libgtksourceview-common libpt-1.10.10-plugins-alsa
7400 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7401 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7402 python-4suite-xml python-eggtrayicon python-gtkhtml2
7403 python-gtkmozembed svgalibg1 xserver-xephyr zip
7404 &lt;/p&gt;&lt;/blockquote&gt;
7405
7406 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7407
7408 &lt;blockquote&gt;&lt;p&gt;
7409 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7410 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7411 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7412 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7413 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7414 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7415 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7416 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7417 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7418 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7419 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7420 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7421 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7422 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7423 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7424 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7425 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7426 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7427 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7428 mysql-common swfdec-gnome totem-gstreamer wodim
7429 &lt;/p&gt;&lt;/blockquote&gt;
7430
7431 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7432
7433 &lt;blockquote&gt;&lt;p&gt;
7434 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7435 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7436 xserver-xorg-input-all xserver-xorg-input-evdev
7437 xserver-xorg-input-kbd xserver-xorg-input-mouse
7438 xserver-xorg-input-synaptics xserver-xorg-video-all
7439 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7440 xserver-xorg-video-chips xserver-xorg-video-cirrus
7441 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7442 xserver-xorg-video-glint xserver-xorg-video-i128
7443 xserver-xorg-video-i740 xserver-xorg-video-mach64
7444 xserver-xorg-video-mga xserver-xorg-video-neomagic
7445 xserver-xorg-video-nouveau xserver-xorg-video-nv
7446 xserver-xorg-video-r128 xserver-xorg-video-radeon
7447 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7448 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7449 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7450 xserver-xorg-video-sis xserver-xorg-video-sisusb
7451 xserver-xorg-video-tdfx xserver-xorg-video-tga
7452 xserver-xorg-video-trident xserver-xorg-video-tseng
7453 xserver-xorg-video-vesa xserver-xorg-video-vmware
7454 xserver-xorg-video-voodoo
7455 &lt;/p&gt;&lt;/blockquote&gt;
7456
7457 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7458
7459 &lt;blockquote&gt;&lt;p&gt;
7460 deskbar-applet xserver-xorg xserver-xorg-core
7461 xserver-xorg-input-wacom xserver-xorg-video-intel
7462 xserver-xorg-video-openchrome
7463 &lt;/p&gt;&lt;/blockquote&gt;
7464
7465 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7466 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7467 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7468 No idea when it hits Squeeze, but when it does I hope it will reduce
7469 the difference somewhat.
7470 </description>
7471 </item>
7472
7473 <item>
7474 <title>LUMA, a very nice LDAP GUI</title>
7475 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7476 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7477 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7478 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7479 directory in Debian Edu, and in the process I started to miss a GUI
7480 tool to browse the LDAP tree. The only one I was able to find in
7481 Debian/Squeeze and Lenny is
7482 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7483 be a great tool to get a overview of the current LDAP directory
7484 populated by default in Skolelinux. Thanks to it, I have been able to
7485 find empty and obsolete subtrees, misplaced objects and duplicate
7486 objects. It will be installed by default in Debian/Squeeze. If you
7487 are working with LDAP, give it a go. :)&lt;/p&gt;
7488
7489 &lt;p&gt;I did notice one problem with it I have not had time to report to
7490 the BTS yet. There is no .desktop file in the package, so the tool do
7491 not show up in the Gnome and KDE menus, but only deep down in in the
7492 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7493 released.&lt;/p&gt;
7494
7495 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7496 like to move objects and remove subtrees directly in the GUI, but have
7497 not found a way to do that with LUMA yet. So in the mean time, I use
7498 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7499
7500 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7501 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7502
7503 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7504 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7505 useful GUI alternative. It seem like a good tool, but is unmaintained
7506 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7507 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7508 </description>
7509 </item>
7510
7511 <item>
7512 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7513 <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>
7514 <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>
7515 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7516 <description>&lt;p&gt;A while back, I
7517 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7518 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7519 for storing DNS and DHCP information in LDAP to combine the two sets
7520 of information into one LDAP object representing a computer.&lt;/p&gt;
7521
7522 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7523 the dhcpHost object class auxiliary, to allow it to be combined with
7524 the dNSDomain object class, and thus forming one object for one
7525 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7526
7527 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7528 without also changing the assigned number for the object class, and I
7529 do not know enough about LDAP schema design to do that properly for
7530 Debian Edu.&lt;/p&gt;
7531
7532 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7533 the
7534 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7535 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7536 available today from IETF.&lt;/p&gt;
7537
7538 &lt;pre&gt;
7539 --- dhcp.schema (revision 65192)
7540 +++ dhcp.schema (working copy)
7541 @@ -376,7 +376,7 @@
7542 objectclass ( 2.16.840.1.113719.1.203.6.6
7543 NAME &#39;dhcpHost&#39;
7544 DESC &#39;This represents information about a particular client&#39;
7545 - SUP top
7546 + SUP top AUXILIARY
7547 MUST cn
7548 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7549 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7550 &lt;/pre&gt;
7551
7552 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7553 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7554 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7555
7556 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7557 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7558 </description>
7559 </item>
7560
7561 <item>
7562 <title>Calling tasksel like the installer, while still getting useful output</title>
7563 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7564 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7565 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7566 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7567 installs packages during the normal debian-installer run. Until now,
7568 I have ended up letting tasksel do the work, with the annoying problem
7569 of not getting any feedback at all when something fails (like a
7570 conffile question from dpkg or a download that fails), using code like
7571 this:
7572
7573 &lt;blockquote&gt;&lt;pre&gt;
7574 export DEBIAN_FRONTEND=noninteractive
7575 tasksel --new-install
7576 &lt;/pre&gt;&lt;/blockquote&gt;
7577
7578 This would invoke tasksel, let its automatic task selection pick the
7579 tasks to install, and continue to install the requested tasks without
7580 any output what so ever.
7581
7582 Recently I revisited this problem while working on the automatic
7583 package upgrade testing, because tasksel would some times hang without
7584 any useful feedback, and I want to see what is going on when it
7585 happen. Then it occured to me, I can parse the output from tasksel
7586 when asked to run in test mode, and use that aptitude command line
7587 printed by tasksel then to simulate the tasksel run. I ended up using
7588 code like this:
7589
7590 &lt;blockquote&gt;&lt;pre&gt;
7591 export DEBIAN_FRONTEND=noninteractive
7592 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7593 $cmd
7594 &lt;/pre&gt;&lt;/blockquote&gt;
7595
7596 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7597 --without-recommends -o APT::Install-Recommends=no -y install
7598 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7599 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7600 laptop task and all packages with priority standard , required and
7601 important, just like tasksel would have done it during
7602 installation.&lt;/p&gt;
7603
7604 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7605 install packages without using debconf-apt-progress, for use cases
7606 like this.&lt;/p&gt;
7607 </description>
7608 </item>
7609
7610 <item>
7611 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7612 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7614 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7615 <description>&lt;p&gt;My
7616 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7617 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7618 finally made the upgrade logs available from
7619 &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;.
7620 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7621 apt and aptitude, and found their differences interesting. This time
7622 I will only focus on their removal plans.&lt;/p&gt;
7623
7624 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7625 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7626 surprising part is that it want to remove xorg and all
7627 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7628 sure why. When asking aptitude to do the same, it want to remove 129
7629 packages, but most of them are library packages I suspect are no
7630 longer needed. Both of them want to remove bluetooth packages, which
7631 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7632
7633 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7634 which seem like a bad idea and xorg the same way as with Gnome. Asking
7635 aptitude for the same, it wants to remove 192 packages, none which are
7636 too surprising.&lt;/p&gt;
7637
7638 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7639 and avoided, and perhaps others as well. Here are the complete list
7640 of planned removals. The complete logs is available from the URL
7641 above. Note if you want to repeat these tests, that the upgrade test
7642 for kde+apt-get hung in the tasksel setup because of dpkg asking
7643 conffile questions. No idea why. I worked around it by using
7644 &#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
7645 continue.&lt;/p&gt;
7646
7647 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7648 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7649 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7650 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7651 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7652 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7653 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7654 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7655 xserver-xorg-input-kbd xserver-xorg-input-mouse
7656 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7657 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7658 xserver-xorg-video-ati xserver-xorg-video-chips
7659 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7660 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7661 xserver-xorg-video-glint xserver-xorg-video-i128
7662 xserver-xorg-video-i740 xserver-xorg-video-imstt
7663 xserver-xorg-video-intel xserver-xorg-video-mach64
7664 xserver-xorg-video-mga xserver-xorg-video-neomagic
7665 xserver-xorg-video-nsc xserver-xorg-video-nv
7666 xserver-xorg-video-openchrome xserver-xorg-video-r128
7667 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7668 xserver-xorg-video-rendition xserver-xorg-video-s3
7669 xserver-xorg-video-s3virge xserver-xorg-video-savage
7670 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7671 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7672 xserver-xorg-video-tga xserver-xorg-video-trident
7673 xserver-xorg-video-tseng xserver-xorg-video-v4l
7674 xserver-xorg-video-vesa xserver-xorg-video-vga
7675 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7676 xulrunner-1.9-gnome-support&lt;/p&gt;
7677
7678 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7679
7680 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7681 djvulibre-desktop finger gnome-app-install gnome-mount
7682 gnome-network-admin gnome-spell gnome-vfs-obexftp
7683 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7684 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7685 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7686 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7687 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7688 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7689 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7690 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7691 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7692 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7693 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7694 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7695 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7696 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7697 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7698 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7699 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7700 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7701 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7702 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7703 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7704 openoffice.org-writer2latex openssl-blacklist p7zip
7705 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7706 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7707 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7708 swfdec-mozilla totem-gstreamer update-manager wodim
7709 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7710 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7711 zip&lt;/p&gt;
7712
7713 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7714
7715 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7716 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7717 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7718 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7719 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7720 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7721 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7722 xserver-xorg-input-kbd xserver-xorg-input-mouse
7723 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7724 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7725 xserver-xorg-video-ati xserver-xorg-video-chips
7726 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7727 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7728 xserver-xorg-video-glint xserver-xorg-video-i128
7729 xserver-xorg-video-i740 xserver-xorg-video-imstt
7730 xserver-xorg-video-intel xserver-xorg-video-mach64
7731 xserver-xorg-video-mga xserver-xorg-video-neomagic
7732 xserver-xorg-video-nsc xserver-xorg-video-nv
7733 xserver-xorg-video-openchrome xserver-xorg-video-r128
7734 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7735 xserver-xorg-video-rendition xserver-xorg-video-s3
7736 xserver-xorg-video-s3virge xserver-xorg-video-savage
7737 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7738 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7739 xserver-xorg-video-tga xserver-xorg-video-trident
7740 xserver-xorg-video-tseng xserver-xorg-video-v4l
7741 xserver-xorg-video-vesa xserver-xorg-video-vga
7742 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7743
7744 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7745 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7746 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7747 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7748 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7749 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7750 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7751 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7752 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7753 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7754 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7755 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7756 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7757 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7758 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7759 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7760 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7761 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7762 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7763 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7764 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7765 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7766 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7767 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7768 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7769 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7770 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7771 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7772 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7773 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7774 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7775 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7776 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7777 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7778 texlive-common texlive-doc-base texlive-fonts-recommended
7779 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7780 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7781 xulrunner-1.9&lt;/p&gt;
7782
7783 </description>
7784 </item>
7785
7786 <item>
7787 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7788 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7789 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7790 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7791 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7792 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7793 have been discovered and reported in the process
7794 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7795 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7796 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7797 kdebase-workspace-data), and to get a more regular testing going on, I
7798 am working on a script to automate the test.&lt;/p&gt;
7799
7800 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7801 Gnome or KDE desktop installation inside the chroot before upgrading
7802 it. To ensure no services are started in the chroot, a policy-rc.d
7803 script is inserted. To make sure tasksel believe it is to install a
7804 desktop on a laptop, the tasksel tests are replaced in the chroot
7805 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7806
7807 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7808 currently always fail because udev refuses to upgrade with the kernel
7809 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7810 is created. The bug report
7811 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7812 this problem do not trigger in a chroot, but I touch the file anyway
7813 to make sure the upgrade go well. Testing on virtual and real
7814 hardware have failed me because of udev so far, and creating this file
7815 do the trick in such settings anyway. This is a
7816 &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
7817 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7818 maintainer because he lack the resources to rewrite udev to keep
7819 working with old kernels or something like that. I really wish the
7820 udev upstream would keep udev backwards compatible, to avoid such
7821 upgrade problem, but given that they fail to do so, I guess
7822 documenting the way out of this mess is the best option we got for
7823 Debian Squeeze.&lt;/p&gt;
7824
7825 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7826 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7827 trick:&lt;/p&gt;
7828
7829 &lt;blockquote&gt;&lt;pre&gt;
7830 #!/bin/sh
7831 set -ex
7832
7833 if [ &quot;$1&quot; ] ; then
7834 desktop=$1
7835 else
7836 desktop=gnome
7837 fi
7838
7839 from=lenny
7840 to=squeeze
7841
7842 exec &amp;lt; /dev/null
7843 unset LANG
7844 mirror=http://ftp.skolelinux.org/debian
7845 tmpdir=chroot-$from-upgrade-$to-$desktop
7846 fuser -mv .
7847 debootstrap $from $tmpdir $mirror
7848 chroot $tmpdir aptitude update
7849 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7850 #!/bin/sh
7851 exit 101
7852 EOF
7853 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7854 exit_cleanup() {
7855 umount $tmpdir/proc
7856 }
7857 mount -t proc proc $tmpdir/proc
7858 # Make sure proc is unmounted also on failure
7859 trap exit_cleanup EXIT INT
7860
7861 chroot $tmpdir aptitude -y install debconf-utils
7862
7863 # Make sure tasksel autoselection trigger. It need the test scripts
7864 # to return the correct answers.
7865 echo tasksel tasksel/desktop multiselect $desktop | \
7866 chroot $tmpdir debconf-set-selections
7867
7868 # Include the desktop and laptop task
7869 for test in desktop laptop ; do
7870 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7871 #!/bin/sh
7872 exit 2
7873 EOF
7874 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7875 done
7876
7877 DEBIAN_FRONTEND=noninteractive
7878 DEBIAN_PRIORITY=critical
7879 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7880 chroot $tmpdir tasksel --new-install
7881
7882 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7883 chroot $tmpdir aptitude update
7884 touch $tmpdir/etc/udev/kernel-upgrade
7885 chroot $tmpdir aptitude -y dist-upgrade
7886 fuser -mv
7887 &lt;/pre&gt;&lt;/blockquote&gt;
7888
7889 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7890 with aptitude, but I have not had time to look at how they behave
7891 differently so far. I hope to get a cron job running to do the test
7892 regularly and post the result on the web. The Gnome upgrade currently
7893 work, while the KDE upgrade fail because of the bug in
7894 kdebase-workspace-data&lt;/p&gt;
7895
7896 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7897 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7898 post, so I will refrain from trying. I can report that for Gnome,
7899 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7900 remove and 1 not upgraded and 1024MB need to be downloaded while for
7901 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7902 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7903
7904 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7905 is able to migrate to dependency based boot sequencing and parallel
7906 booting without a hitch. Was unsure if there were still bugs with
7907 packages failing to clean up their obsolete init.d script during
7908 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7909 packages.&lt;/p&gt;
7910 </description>
7911 </item>
7912
7913 <item>
7914 <title>Upstart or sysvinit - as init.d scripts see it</title>
7915 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7916 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7917 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7918 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7919 scripts to migrate (some of) their operations to upstart job while
7920 keeping the init.d for hurd and kfreebsd. The packages with such
7921 needs will need a way to get their init.d scripts to behave
7922 differently when used with sysvinit and with upstart. Because of
7923 this, I had a look at the environment variables set when a init.d
7924 script is running under upstart, and when it is not.&lt;/p&gt;
7925
7926 &lt;p&gt;With upstart, I notice these environment variables are set when a
7927 script is started from rcS.d/ (ignoring some irrelevant ones like
7928 COLUMNS):&lt;/p&gt;
7929
7930 &lt;blockquote&gt;&lt;pre&gt;
7931 DEFAULT_RUNLEVEL=2
7932 previous=N
7933 PREVLEVEL=
7934 RUNLEVEL=
7935 runlevel=S
7936 UPSTART_EVENTS=startup
7937 UPSTART_INSTANCE=
7938 UPSTART_JOB=rc-sysinit
7939 &lt;/pre&gt;&lt;/blockquote&gt;
7940
7941 &lt;p&gt;With sysvinit, these environment variables are set for the same
7942 script.&lt;/p&gt;
7943
7944 &lt;blockquote&gt;&lt;pre&gt;
7945 INIT_VERSION=sysvinit-2.88
7946 previous=N
7947 PREVLEVEL=N
7948 RUNLEVEL=S
7949 runlevel=S
7950 &lt;/pre&gt;&lt;/blockquote&gt;
7951
7952 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7953 sysvinit are not set by upstart. Not sure if it is intentional or not
7954 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7955
7956 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7957 looking for the UPSTART_JOB environment variable seem to be a good
7958 choice.&lt;/p&gt;
7959 </description>
7960 </item>
7961
7962 <item>
7963 <title>A manual for standards wars...</title>
7964 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7965 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7966 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7967 <description>&lt;p&gt;Via the
7968 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7969 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7970 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7971 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7972 following the standards wars of today.&lt;/p&gt;
7973 </description>
7974 </item>
7975
7976 <item>
7977 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7978 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7979 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7980 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7981 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7982 to get a list of the machine types in use thanks to the DMI
7983 information extracted from each machine. The script to do so is
7984 included in the sitesummary package, and here is example output from
7985 the Skolelinux build servers:&lt;/p&gt;
7986
7987 &lt;blockquote&gt;&lt;pre&gt;
7988 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7989 vendor count
7990 Dell Computer Corporation 1
7991 PowerEdge 1750 1
7992 IBM 1
7993 eserver xSeries 345 -[8670M1X]- 1
7994 Intel 2
7995 [no-dmi-info] 3
7996 maintainer:~#
7997 &lt;/pre&gt;&lt;/blockquote&gt;
7998
7999 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
8000 provided in each machine. Here there are Intel machines without model
8001 information listed with Intel as vendor and no model, and virtual Xen
8002 machines listed as [no-dmi-info]. One can add -l as a command line
8003 option to list the individual machines.&lt;/p&gt;
8004
8005 &lt;p&gt;A larger list is
8006 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
8007 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
8008 provide the basic sitesummary report publicly. In their report there
8009 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
8010 their machines, and as sitesummary is available in both distributions,
8011 it is trivial to get all of them to report to the same central
8012 collector.&lt;/p&gt;
8013 </description>
8014 </item>
8015
8016 <item>
8017 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
8018 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
8019 <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>
8020 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
8021 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
8022 start at boot when an NVidia video card is used is handled. The
8023 problem seem to be that the nvidia X.org driver uses a long time to
8024 initialize, and this duration is longer than kdm is configured to
8025 wait.&lt;/p&gt;
8026
8027 &lt;p&gt;I came across two bugs related to this issue,
8028 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
8029 against initscripts and passed on to nvidia-glx when it became obvious
8030 that the nvidia drivers were involved, and
8031 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
8032 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
8033
8034 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
8035 problem nvidia video card owners experience and make sure the Debian
8036 distribution work out of the box for these users. The nvidia driver
8037 maintainers expect kdm to be set up to wait longer, while kdm expect
8038 the nvidia driver maintainers to fix the driver to start faster, and
8039 while they wait for each other I guess the users end up switching to a
8040 distribution that work for them. I have no idea what the solution is,
8041 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
8042
8043 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
8044 </description>
8045 </item>
8046
8047 <item>
8048 <title>Parallellized boot seem to hold up well in Debian/testing</title>
8049 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
8050 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
8051 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
8052 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
8053 The feature seem to hold up pretty well, but three fairly serious
8054 issues are known and should be solved:
8055
8056 &lt;p&gt;&lt;ul&gt;
8057
8058 &lt;li&gt;The wicd package seen to
8059 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
8060 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
8061 parallel booting is enabled. No idea why, but the wicd maintainer
8062 seem to be on the case.&lt;/li&gt;
8063
8064 &lt;li&gt;The nvidia X driver seem to
8065 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
8066 triggered more easily when parallel booting is in effect. The
8067 maintainer is on the case.&lt;/li&gt;
8068
8069 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
8070 sequencing (the shutdown is broken) when old file-rc users
8071 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
8072 sysv-rc. One way to solve it would be for file-rc to create
8073 /etc/init.d/.legacy-bootordering, and another is to try to make
8074 sysv-rc more robust. Will investigate some more and probably upload a
8075 workaround in sysv-rc to help those trying to move from file-rc to
8076 sysv-rc get a working shutdown.&lt;/li&gt;
8077
8078 &lt;/ul&gt;&lt;/p&gt;
8079
8080 &lt;p&gt;All in all not many surprising issues, and all of them seem
8081 solvable before Squeeze is released. In addition to these there are
8082 some packages with bugs in their dependencies and run level settings,
8083 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
8084
8085 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8086 the BTS, please usertag the report to get it to show up at
8087 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8088 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8089
8090 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
8091 </description>
8092 </item>
8093
8094 <item>
8095 <title>More flexible firmware handling in debian-installer</title>
8096 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
8097 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
8098 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
8099 <description>&lt;p&gt;After a long break from debian-installer development, I finally
8100 found time today to return to the project. Having to spend less time
8101 working dependency based boot in debian, as it is almost complete now,
8102 definitely helped freeing some time.&lt;/p&gt;
8103
8104 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
8105 include some firmware packages on the Debian Edu CDs, those needed to
8106 get disk and network controllers working. Without having these
8107 firmware packages available during installation, it is impossible to
8108 install Debian Edu on the given machine, and because our target group
8109 are non-technical people, asking them to provide firmware packages on
8110 an external medium is a support pain. Initially, I expected it to be
8111 enough to include the firmware packages on the CD to get
8112 debian-installer to find and use them. This proved to be wrong.
8113 Next, I hoped it was enough to symlink the relevant firmware packages
8114 to some useful location on the CD (tried /cdrom/ and
8115 /cdrom/firmware/). This also proved to not work, and at this point I
8116 found time to look at the debian-installer code to figure out what was
8117 going to work.&lt;/p&gt;
8118
8119 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
8120 look revealed that it would only look for firmware packages outside
8121 the installation media, so the CD was never checked for firmware
8122 packages. It would only check USB sticks, floppies and other
8123 &quot;external&quot; media devices. Today I changed it to also look in the
8124 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8125 solve the problem I ran into with Debian edu. I also changed it to
8126 look in /firmware/, to make sure the installer also find firmware
8127 provided in the initrd when booting the installer via PXE, to allow us
8128 to provide the same feature in the PXE setup included in Debian
8129 Edu.&lt;/p&gt;
8130
8131 &lt;p&gt;To make sure firmware deb packages with a license questions are not
8132 activated without asking if the license is accepted, I extended
8133 hw-detect to look for preinst scripts in the firmware packages, and
8134 run these before activating the firmware during installation. The
8135 license question is asked using debconf in the preinst, so this should
8136 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
8137
8138 &lt;p&gt;If you want to discuss the details of these features, please
8139 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
8140 </description>
8141 </item>
8142
8143 <item>
8144 <title>Parallellized boot is now the default in Debian/unstable</title>
8145 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
8146 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
8147 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
8148 <description>&lt;p&gt;Since this evening, parallel booting is the default in
8149 Debian/unstable for machines using dependency based boot sequencing.
8150 Apparently the testing of concurrent booting has been wider than
8151 expected, if I am to believe the
8152 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8153 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
8154 with the feature this weekend, to give us some time to detect any
8155 remaining problems before Squeeze is frozen. If serious problems are
8156 detected, it is simple to change the default back to sequential boot.
8157 The upload of the new sysvinit package also activate a new upstream
8158 version.&lt;/p&gt;
8159
8160 More information about
8161 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8162 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
8163 currently possible to disable parallel booting when one run into
8164 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
8165
8166 &lt;blockquote&gt;&lt;pre&gt;
8167 CONCURRENCY=none
8168 &lt;/pre&gt;&lt;/blockquote&gt;
8169
8170 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8171 the BTS, please usertag the report to get it to show up at
8172 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8173 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8174 </description>
8175 </item>
8176
8177 <item>
8178 <title>Sitesummary tip: Listing MAC address of all clients</title>
8179 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
8180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
8181 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
8182 <description>&lt;p&gt;In the recent Debian Edu versions, the
8183 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
8184 system&lt;/a&gt; is used to keep track of the machines in the school
8185 network. Each machine will automatically report its status to the
8186 central server after boot and once per night. The network setup is
8187 also reported, and using this information it is possible to get the
8188 MAC address of all network interfaces in the machines. This is useful
8189 to update the DHCP configuration.&lt;/p&gt;
8190
8191 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
8192 ist all MAC addresses of all machines reporting to sitesummary. Run
8193 this on the collector host:&lt;/p&gt;
8194
8195 &lt;blockquote&gt;&lt;pre&gt;
8196 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
8197 &lt;/pre&gt;&lt;/blockquote&gt;
8198
8199 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
8200 line per machine and with space between the MAC addresses.&lt;/p&gt;
8201
8202 &lt;p&gt;To allow system administrators easier job at adding static DHCP
8203 addresses for hosts, it would be possible to extend this to fetch
8204 machine information from sitesummary and update the DHCP and DNS
8205 tables in LDAP using this information. Such tool is unfortunately not
8206 written yet.&lt;/p&gt;
8207 </description>
8208 </item>
8209
8210 <item>
8211 <title>systemd, an interesting alternative to upstart</title>
8212 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
8213 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
8214 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
8215 <description>&lt;p&gt;The last few days a new boot system called
8216 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
8217 has been
8218 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
8219
8220 to the free software world. I have not yet had time to play around
8221 with it, but it seem to be a very interesting alternative to
8222 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
8223 a good alternative for Debian when we are able to switch to an event
8224 based boot system. Tollef is
8225 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
8226 systemd into Debian, and I look forward to seeing how well it work. I
8227 like the fact that systemd handles init.d scripts with dependency
8228 information natively, allowing them to run in parallel where upstart
8229 at the moment do not.&lt;/p&gt;
8230
8231 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
8232 platform support. It only work on recent Linux kernels, and also need
8233 some new kernel features enabled to function properly. This means
8234 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8235 system. Not sure how that will be handled if systemd proves to be the
8236 way forward.&lt;/p&gt;
8237
8238 &lt;p&gt;In the mean time, based on the
8239 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8240 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
8241 decided to enable full parallel booting as the default in Debian as
8242 soon as possible (probably this weekend or early next week), to see if
8243 there are any remaining serious bugs in the init.d dependencies. A
8244 new version of the sysvinit package implementing this change is
8245 already in experimental. If all go well, Squeeze will be released
8246 with parallel booting enabled by default.&lt;/p&gt;
8247 </description>
8248 </item>
8249
8250 <item>
8251 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
8252 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
8253 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
8254 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
8255 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
8256 complete, so complete that it is actually possible to run all the
8257 init.d scripts in parallell based on these dependencies. If you want
8258 to test your Squeeze system, make sure
8259 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8260 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8261 /etc/default/rcS:&lt;/p&gt;
8262
8263 &lt;blockquote&gt;&lt;pre&gt;
8264 CONCURRENCY=makefile
8265 &lt;/pre&gt;&lt;/blockquote&gt;
8266
8267 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8268 scripts in parallel using the dependency information stored in
8269 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8270 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8271 to try to start the kdm and gdm scripts as early as possible, and will
8272 start the facilities required by kdm or gdm as early as possible to
8273 make this happen.&lt;/p&gt;
8274
8275 &lt;p&gt;Give it a try, and see if you like the result. If some services
8276 fail to start properly, it is most likely because they have incomplete
8277 init.d script dependencies in their startup script (or some of their
8278 dependent scripts have incomplete dependencies). Report bugs and get
8279 the package maintainers to fix it. :)&lt;/p&gt;
8280
8281 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8282 manage to get the init.d script dependencies complete and correct. I
8283 expect we will get there in Squeeze+1, if we get manage to test and
8284 fix the remaining issues.&lt;/p&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>Debian has switched to dependency based boot sequencing</title>
8295 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8297 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8298 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8299 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8300 have been migrated to using dependency based boot sequencing. This
8301 conclude work me and others have been doing for the last three days.
8302 It feels great to see this finally part of the default Debian
8303 installation. Now we just need to weed out the last few problems that
8304 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8305
8306 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8307 fixing the more fundamental problem of handing the event based
8308 non-predictable kernel in the early boot.&lt;/p&gt;
8309 </description>
8310 </item>
8311
8312 <item>
8313 <title>Taking over sysvinit development</title>
8314 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8315 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8316 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8317 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8318 the existing sysvinit upstream developer, I decided a few weeks ago to
8319 take over the package and become the new upstream. The number of
8320 patches to track for the Debian package was becoming a burden, and the
8321 lack of synchronization between the distribution made it hard to keep
8322 the package up to date.&lt;/p&gt;
8323
8324 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8325 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8326 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8327 and Fedora), based on the patches currently in use in these
8328 distributions. We Debian maintainers plan to move to this tarball as
8329 the new upstream as soon as we find time to do the merge. Since the
8330 new tarball was created, we agreed with Werner at SuSe to make a new
8331 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8332 development there. The project is registered and currently waiting
8333 for approval by the Savannah administrators, and as soon as it is
8334 approved, we will import the old versions from svn and continue
8335 working on the future release.&lt;/p&gt;
8336
8337 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8338 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8339 </description>
8340 </item>
8341
8342 <item>
8343 <title>Debian boots quicker and quicker</title>
8344 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8346 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8347 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8348 people involved in the boot system on Debian and Ubuntu, to see if we
8349 could find more ways to speed up the boot system. This was an Ubuntu
8350 funded
8351 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8352 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8353 of boot systems, and ways to handle the increasing number of boot
8354 issues introduced by the Linux kernel becoming more and more
8355 asynchronous and event base. The Ubuntu approach using udev and
8356 upstart might be a good way forward. Time will show.&lt;/p&gt;
8357
8358 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8359 process in Debian. All of these should be applied to get a quick
8360 boot:&lt;/p&gt;
8361
8362 &lt;ul&gt;
8363
8364 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8365
8366 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8367 clock is in UTC.&lt;/li&gt;
8368
8369 &lt;li&gt;Install and activate the insserv package to enable
8370 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8371 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8372
8373 &lt;/ul&gt;
8374
8375 These points are based on the Google summer of code work done by
8376 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8377 Villegas&lt;/a&gt;.
8378
8379 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8380 unstable yesterday. When we tested it, we were able to cut 6 seconds
8381 from the boot sequence. It depend on very correct dependency
8382 declaration in all init.d scripts, so I expect us to find edge cases
8383 where the dependences in some scripts are slightly wrong when we start
8384 using this.&lt;/p&gt;
8385
8386 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8387 introduced by Raphael Geissert today, one that could affect the
8388 startup speed as well. Instead of starting some scripts concurrently
8389 from rcS.d/ and another set of scripts from rc2.d/, it would be
8390 possible to run a of them in the same process. A quick way to test
8391 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8392 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8393 </description>
8394 </item>
8395
8396 <item>
8397 <title>BSAs påstander om piratkopiering møter motstand</title>
8398 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8399 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8400 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8401 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8402 programvareselskapene som Microsoft og Apple, publisert en rapport der
8403 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8404 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8405 dager siden kom
8406 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8407 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8408 dagene. Et spesielt interessant kommentar fra Sverige,
8409 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8410 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8411
8412 &lt;blockquote&gt;
8413 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8414 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8415 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8416 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8417 &lt;/blockquote&gt;
8418
8419 &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
8420 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8421 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8422 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8423 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8424
8425 &lt;p&gt;Fant lenkene via &lt;a
8426 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8427 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8428 </description>
8429 </item>
8430
8431 <item>
8432 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8433 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8434 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8435 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8436 <description>&lt;p&gt;Kom over
8437 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8438 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8439 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8440 jobber til daglig. En rask opptelling forteller meg at vi har 490
8441 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8442 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8443 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8444 </description>
8445 </item>
8446
8447 <item>
8448 <title>Kryptert harddisk - naturligvis</title>
8449 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8451 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8452 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8453 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8454 når en tar tap av arbeidstid, fortrolige dokumenter,
8455 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8456 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8457 til at jeg har kryptert harddisken på både kontormaskinen og min
8458 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8459 komme på avveie, den første informasjon relatert til jobben min ved
8460 Universitetet i Oslo, og den andre relatert til blant annet
8461 foreningsarbeide. Kryptering av diskene gjør at det er lite
8462 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8463 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8464 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8465 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8466 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8467 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8468 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8469 det er gjort slik jeg gjør det er minimale, og gevinstene er
8470 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8471 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8472
8473 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8474 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8475 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8476 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8477 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8478 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8479 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8480 betydelige.&lt;/p&gt;
8481 </description>
8482 </item>
8483
8484 <item>
8485 <title>Two projects that have improved the quality of free software a lot</title>
8486 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8487 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8488 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8489 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8490 quality of free software, and I wanted to mention both in case someone
8491 do not yet know them.&lt;/p&gt;
8492
8493 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8494 tool to detect and expose errors in the memory handling of programs.
8495 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8496 and it will report any problems on stdout. It is even better if the
8497 program include debug information. With debug information, it is able
8498 to report the source file name and line number where the problem
8499 occurs. It can report things like &#39;reading past memory block in file
8500 X line N, the memory block was allocated in file Y, line M&#39;, and
8501 &#39;using uninitialised value in control logic&#39;. This tool has made it
8502 trivial to investigate reproducible crash bugs in programs, and have
8503 reduced the number of this kind of bugs in free software a lot.
8504
8505 &lt;p&gt;The second one is
8506 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8507 a source code checker. It is able to process the source of a program
8508 and find problems in the logic without running the program. It
8509 started out as the Stanford Checker and became well known when it was
8510 used to find bugs in the Linux kernel. It is now a commercial tool
8511 and the company behind it is running
8512 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8513 free software community, where a lot of free software projects get
8514 their source checked for free. Several thousand defects have been
8515 found and fixed so far. It can find errors like &#39;lock L taken in file
8516 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8517 Y lines O to P can never be executed&#39;. The projects included in the
8518 community service project have managed to get rid of a lot of
8519 reliability problems thanks to Coverity.&lt;/p&gt;
8520
8521 &lt;p&gt;I believe tools like this, that are able to automatically find
8522 errors in the source, are vital to improve the quality of software and
8523 make sure we can get rid of the crashing and failing software we are
8524 surrounded by today.&lt;/p&gt;
8525 </description>
8526 </item>
8527
8528 <item>
8529 <title>No patch is not better than a useless patch</title>
8530 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8531 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8532 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8533 <description>&lt;p&gt;Julien Blache
8534 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8535 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8536 patch allow one to discuss a concrete and proposed solution, and also
8537 prove that the issue at hand is important enough for someone to spent
8538 time on fixing it. No patch do not provide any of these positive
8539 properties.&lt;/p&gt;
8540 </description>
8541 </item>
8542
8543 <item>
8544 <title>Standardize on protocols and formats, not vendors and applications</title>
8545 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8546 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8547 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8548 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8549 very good one to form a long lived computer infrastructure. It is the
8550 simple one, lost by many in todays computer industry: Standardize on
8551 open network protocols and open exchange/storage formats, not applications.
8552 Applications come and go, while protocols and files tend to stay, and
8553 thus one want to make it easy to change application and vendor, while
8554 avoiding conversion costs and locking users to a specific platform or
8555 application.&lt;/p&gt;
8556
8557 &lt;p&gt;This approach make it possible to replace the client applications
8558 independently of the server applications. One can even allow users to
8559 use several different applications as long as they handle the selected
8560 protocol and format. In the normal case, only one client application
8561 is recommended and users only get help if they choose to use this
8562 application, but those that want to deviate from the easy path are not
8563 blocked from doing so.&lt;/p&gt;
8564
8565 &lt;p&gt;It also allow us to replace the server side without forcing the
8566 users to replace their applications, and thus allow us to select the
8567 best server implementation at any moment, when scale and resouce
8568 requirements change.&lt;/p&gt;
8569
8570 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8571 open formats, but I would never recommend standardizing on a single
8572 application that do not use open network protocol or open formats.&lt;/p&gt;
8573 </description>
8574 </item>
8575
8576 <item>
8577 <title>Returning from Skolelinux developer gathering</title>
8578 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8579 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8580 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8581 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8582 Edu/Skolelinux development gathering. I got a bit done tuning the
8583 desktop, and looked into the dynamic service location protocol
8584 implementation avahi. It look like it could be useful for us. Almost
8585 30 people participated, and I believe it was a great environment to
8586 get to know the Skolelinux system. Walter Bender, involved in the
8587 development of the Sugar educational platform, presented his stuff and
8588 also helped me improve my OLPC installation. He also showed me that
8589 his Turtle Art application can be used in standalone mode, and we
8590 agreed that I would help getting it packaged for Debian. As a
8591 standalone application it would be great for Debian Edu. We also
8592 tried to get the video conferencing working with two OLPCs, but that
8593 proved to be too hard for us. The application seem to need more work
8594 before it is ready for me. I look forward to getting home and relax
8595 now. :)&lt;/p&gt;
8596 </description>
8597 </item>
8598
8599 <item>
8600 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8601 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8602 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8603 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8604 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8605 optimal. There is RFC 2307 documenting one way to store NIS maps in
8606 LDAP, and a modified version of this normally called RFC 2307bis, with
8607 some modifications to be compatible with Active Directory. The RFC
8608 specification handle the content of a lot of system databases, but do
8609 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8610
8611 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8612 we would like to store information about users, SMB clients/hosts,
8613 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8614 and LTSP configuration in LDAP. These objects have a lot in common,
8615 but with the current LDAP schemas it is not possible to have one
8616 object per entity. For example, one need to have at least three LDAP
8617 objects for a given computer, one with the SMB related stuff, one with
8618 DNS information and another with DHCP information. The schemas
8619 provided for DNS and DHCP are impossible to combine into one LDAP
8620 object. In addition, it is impossible to implement quick queries for
8621 netgroup membership, because of the way NIS triples are implemented.
8622 It just do not scale. I believe it is time for a few RFC
8623 specifications to cleam up this mess.&lt;/p&gt;
8624
8625 &lt;p&gt;I would like to have one LDAP object representing each computer in
8626 the network, and this object can then keep the SMB (ie host key), DHCP
8627 (mac address/name) and DNS (name/IP address) settings in one place.
8628 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8629
8630 &lt;p&gt;I would also like to have a quick way to map from a user or
8631 computer and to the net group this user or computer is a member.&lt;/p&gt;
8632
8633 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8634 in this regard, and the unix side need to catch up. Time to start a
8635 new IETF work group?&lt;/p&gt;
8636 </description>
8637 </item>
8638
8639 <item>
8640 <title>Endelig er Debian Lenny gitt ut</title>
8641 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8642 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8643 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8644 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8645 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8646 Et langt steg videre for Debian-prosjektet, og en rekke nye
8647 programpakker blir nå tilgjengelig for de av oss som bruker den
8648 stabile utgaven av Debian. Neste steg er nå å få
8649 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8650 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8651 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8652 slippes løs på skolene. Takk til alle debian-utviklerne som har
8653 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8654 bootsekvens tilgjengelig i stabil utgave, vha pakken
8655 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8656 </description>
8657 </item>
8658
8659 <item>
8660 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8661 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8662 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8663 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8664 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8665 Oslo. Most of Saturday was used for the general assemly for the
8666 member organization, but the rest of the weekend I used to tune the
8667 LTSP installation. LTSP now work out of the box on the 10-network.
8668 Acer Aspire One proved to be a very nice thin client, with both
8669 screen, mouse and keybard in a small box. Was working on getting the
8670 diskless workstation setup configured out of the box, but did not
8671 finish it before the weekend was up.&lt;/p&gt;
8672
8673 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8674 the Brazilian group, so that will have to wait for the next
8675 development gathering. Would love to have the Debian Edu installer
8676 automatically detect and configure a multiseat setup when it find one
8677 of these cards.&lt;/p&gt;
8678 </description>
8679 </item>
8680
8681 <item>
8682 <title>The sorry state of multimedia browser plugins in Debian</title>
8683 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8685 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8686 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8687 plugins available in Debian Lenny, to see which one we should use by
8688 default in Debian Edu. We need an embedded video playing plugin with
8689 control buttons to pause or stop the video, and capable of streaming
8690 all the multimedia content available on the web. The test results and
8691 notes are available on
8692 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8693 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8694 fill this need. My personal video player favorite, VLC, has a really
8695 bad plugin which fail on a lot of the test pages. A lot of the MIME
8696 types I would expect to work with any free software player (like
8697 video/ogg), just do not work. And simple formats like the
8698 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8699 totem and vlc plugins. I hope the situation will improve soon. No
8700 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8701
8702 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8703 be the only one fitting our needs. :/&lt;/p&gt;
8704 </description>
8705 </item>
8706
8707 </channel>
8708 </rss>