]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
fe0a7ad7d25b88ca8821cbd9a5b6d16e60fd11f1
[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>Creating, updating and checking debian/copyright semi-automatically</title>
11 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
13 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
14 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
15 details. And one of the details is the content of the
16 debian/copyright file, which should list all relevant licenses used by
17 the code in the package in question, preferably in
18 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
19 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
20
21 &lt;p&gt;For large packages with lots of contributors it is hard to write
22 and update this file manually, and if you get some detail wrong, the
23 package is normally rejected by the ftpmasters. So getting it right
24 the first time around get the package into Debian faster, and save
25 both you and the ftpmasters some work.. Today, while trying to figure
26 out what was wrong with
27 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
28 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
29 figuring out the options for doing this job automatically, or at least
30 semi-automatically.&lt;/p&gt;
31
32 &lt;p&gt;Lucikly, there are at least two tools available for generating the
33 file based on the code in the source package,
34 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
35 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
36 not sure which one of them came first, but both seem to be able to
37 create a sensible draft file. As far as I can tell, none of them can
38 be trusted to get the result just right, so the content need to be
39 polished a bit before the file is OK to upload. I found the debmake
40 option in
41 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
42 blog posts from 2014&lt;/a&gt;.
43
44 &lt;p&gt;To generate using debmake, use the -cc option:
45
46 &lt;p&gt;&lt;pre&gt;
47 debmake -cc &gt; debian/copyright
48 &lt;/pre&gt;&lt;/p&gt;
49
50 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
51 this might not be the best option.&lt;/p&gt;
52
53 &lt;p&gt;The cme option is based on a config parsing library, and I found
54 this approach in
55 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
56 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
57 dpkg-copyright&#39; option:
58
59 &lt;p&gt;&lt;pre&gt;
60 cme update dpkg-copyright -quiet
61 &lt;/pre&gt;&lt;/p&gt;
62
63 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
64 handle UTF-8 names better than debmake.&lt;/p&gt;
65
66 &lt;p&gt;When the copyright file is created, I would also like some help to
67 check if the file is correct. For this I found two good options,
68 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
69 to focus on license types and file matching, and is able to detect
70 ineffective blocks in the copyright file. The latter reports missing
71 copyright holders and years, but was confused by inconsistent license
72 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
73 fix all issues reported by them before uploading. But I do not know
74 if the tools and the ftpmasters agree on what is important to fix in a
75 copyright file, so the package might still be rejected.&lt;/p&gt;
76
77 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
78 will read through the source and try to find all copyright statements.
79 It is not comparing the result to the content of debian/copyright, but
80 can be useful when verifying the content of the copyright file.&lt;/p&gt;
81
82 &lt;p&gt;Are you aware of better tools in Debian to create and update
83 debian/copyright file. Please let me know, or blog about it on
84 planet.debian.org.&lt;/p&gt;
85
86 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
87 activities, please send Bitcoin donations to my address
88 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
89 </description>
90 </item>
91
92 <item>
93 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
94 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
95 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
96 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
97 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
98 is taking shape in Debian, and one provided feature is a very
99 convenient way to tell you which package to install to make a given
100 firmware file available when the kernel is looking for it. This can
101 be done using apt-file too, but that is for someone else to blog
102 about. :)&lt;/p&gt;
103
104 &lt;p&gt;Here is a small recipe to find the package with a given firmware
105 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
106 picked from the set of firmware announced using appstream in Debian
107 unstable. In general you would be looking for the firmware requested
108 by the kernel during kernel module loading. To find the package
109 providing the example file, do like this:&lt;/p&gt;
110
111 &lt;blockquote&gt;&lt;pre&gt;
112 % apt install appstream
113 [...]
114 % apt update
115 [...]
116 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
117 awk &#39;/Package:/ {print $2}&#39;
118 firmware-qlogic
119 %
120 &lt;/pre&gt;&lt;/blockquote&gt;
121
122 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
123 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
124 a way appstream can use.&lt;/p&gt;
125
126 &lt;p&gt;This same approach can be used to find any package supporting a
127 given MIME type. This is very useful when you get a file you do not
128 know how to handle. First find the mime type using &lt;tt&gt;file
129 --mime-type&lt;/tt&gt;, and next look up the package providing support for
130 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
131 and you can find all packages handling this type like this:&lt;/p&gt;
132
133 &lt;blockquote&gt;&lt;pre&gt;
134 % apt install appstream
135 [...]
136 % apt update
137 [...]
138 % appstreamcli what-provides mimetype image/svg+xml | \
139 awk &#39;/Package:/ {print $2}&#39;
140 bkchem
141 phototonic
142 inkscape
143 shutter
144 tetzle
145 geeqie
146 xia
147 pinta
148 gthumb
149 karbon
150 comix
151 mirage
152 viewnior
153 postr
154 ristretto
155 kolourpaint4
156 eog
157 eom
158 gimagereader
159 midori
160 %
161 &lt;/pre&gt;&lt;/blockquote&gt;
162
163 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
164 packages providing appstream metadata.&lt;/p&gt;
165 </description>
166 </item>
167
168 <item>
169 <title>Creepy, visualise geotagged social media information - nice free software</title>
170 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
171 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
172 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
173 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
174 with the computerised radio beacon known as a mobile phone their
175 position is tracked by the phone company and often stored for a long
176 time (like every time a SMS is received or sent). And if their
177 computerised radio beacon is capable of running programs (often called
178 mobile apps) downloaded from the Internet, these programs are often
179 also capable of tracking their location (if the app requested access
180 during installation). And when these programs send out information to
181 central collection points, the location is often included, unless
182 extra care is taken to not send the location. The provided
183 information is used by several entities, for good and bad (what is
184 good and bad, depend on your point of view). What is certain, is that
185 the private sphere and the right to free movement is challenged and
186 perhaps even eradicated for those announcing their location this way,
187 when they share their whereabouts with private and public
188 entities.&lt;/p&gt;
189
190 &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;
191
192 &lt;p&gt;The phone company logs provide a register of locations to check out
193 when one want to figure out what the tracked person was doing. It is
194 unavailable for most of us, but provided to selected government
195 officials, company staff, those illegally buying information from
196 unfaithful servants and crackers stealing the information. But the
197 public information can be collected and analysed, and a free software
198 tool to do so is called
199 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
200 discovered it when I read
201 &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
202 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
203 November 2014, and decided to check if it was available in Debian.
204 The python program was in Debian, but
205 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
206 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
207 uploaded a new version which did not work quite right, but did not
208 have time to fix it then. This Christmas I decided to finally try to
209 get Creepy operational in Debian. Now a fixed version is available in
210 Debian unstable and testing, and almost all Debian specific patches
211 are now included
212 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
213
214 &lt;p&gt;The Creepy program visualises geolocation information fetched from
215 Twitter, Instagram, Flickr and Google+, and allow one to get a
216 complete picture of every social media message posted recently in a
217 given area, or track the movement of a given individual across all
218 these services. Earlier it was possible to use the search API of at
219 least some of these services without identifying oneself, but these
220 days it is impossible. This mean that to use Creepy, you need to
221 configure it to log in as yourself on these services, and provide
222 information to them about your search interests. This should be taken
223 into account when using Creepy, as it will also share information
224 about yourself with the services.&lt;/p&gt;
225
226 &lt;p&gt;The picture above show the twitter messages sent from (or at least
227 geotagged with a position from) the city centre of Oslo, the capital
228 of Norway. One useful way to use Creepy is to first look at
229 information tagged with an area of interest, and next look at all the
230 information provided by one or more individuals who was in the area.
231 I tested it by checking out which celebrity provide their location in
232 twitter messages by checkout out who sent twitter messages near a
233 Norwegian TV station, and next could track their position over time,
234 making it possible to locate their home and work place, among other
235 things. A similar technique have been
236 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
237 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
238 tool to discover lying governments, and a useful tool to help people
239 understand the value of the private information they provide to the
240 public.&lt;/p&gt;
241
242 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
243 it depend on several python modules currently missing in Jessie (at
244 least python-instagram, python-flickrapi and
245 python-requests-toolbelt).&lt;/p&gt;
246
247 &lt;p&gt;(I have uploaded
248 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
249 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
250 Creepy program in Debian.)&lt;/p&gt;
251 </description>
252 </item>
253
254 <item>
255 <title>Always download Debian packages using Tor - the simple recipe</title>
256 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
257 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
258 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
259 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
260 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
261 that those listening on the Internet lines would have good reason to
262 believe a computer have a given security hole&lt;/a&gt; if it download a
263 security fix from a Debian mirror. This is a good reason to always
264 use encrypted connections to the Debian mirror, to make sure those
265 listening do not know which IP address to attack. In August, Richard
266 Hartmann observed that encryption was not enough, when it was possible
267 to interfere download size to security patches or the fact that
268 download took place shortly after a security fix was released, and
269 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
270 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
271 was not the first to propose this, as the
272 &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;
273 package by Tim Retout already existed to make it easy to convince apt
274 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
275 aware of that package when I read the blog post from Richard.&lt;/p&gt;
276
277 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
278 sysadmins, and he set up a Tor hidden service on one of the central
279 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
280 it possible to download packages directly between two tor nodes,
281 making sure the network traffic always were encrypted.&lt;/p&gt;
282
283 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
284 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
285 urls with tor+http and tor+https, and using the hidden service instead
286 of the official Debian mirror site. I recommend installing
287 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
288 done in /etc/.&lt;/p&gt;
289
290 &lt;blockquote&gt;&lt;pre&gt;
291 apt install apt-transport-tor
292 sed -i &#39;s% http://ftp.debian.org/%tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
293 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
294 &lt;/pre&gt;&lt;/blockquote&gt;
295
296 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
297 the sed commands for these too. The sed command is assuming your are
298 using the ftp.debian.org Debian mirror. Adjust the command (or just
299 edit the file manually) to match your mirror.&lt;/p&gt;
300
301 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
302 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
303 system, and do not work with these tor+http URLs. For
304 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
305 which need a recent apt version currently only in unstable. So if you
306 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
307
308 &lt;p&gt;Another advantage from this change is that your machine will start
309 using Tor regularly and at fairly random intervals (every time you
310 update the package lists or upgrade or install a new package), thus
311 masking other Tor traffic done from the same machine. Using Tor will
312 become normal for the machine in question.&lt;/p&gt;
313
314 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
315 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
316 enabled. It would be great if it was the default on any Debian
317 system.&lt;/p&gt;
318 </description>
319 </item>
320
321 <item>
322 <title>OpenALPR, find car license plates in video streams - nice free software</title>
323 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
324 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
325 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
326 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
327 call the car license plate numbers in those days. I would write the
328 numbers down in my little book and compare notes with the other kids
329 to see how many region codes we had seen and if we had seen some
330 exotic or special region codes and numbers. It was a fun game to pass
331 time, as we kids have plenty of it.&lt;/p&gt;
332
333 &lt;p&gt;A few days I came across
334 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
335 project&lt;/a&gt;, a free software project to automatically discover and
336 report license plates in images and video streams, and provide the
337 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
338 such system for a while now, because I believe it is a bad idea that the
339 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
340 number plate recognition&lt;/a&gt; tool only is available in the hands of
341 the powerful, and want it to be available also for the powerless to
342 even the score when it comes to surveillance and sousveillance. I
343 discovered the developer
344 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
345 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
346 help him get it into shape to get the package uploaded into the Debian
347 archive.&lt;/p&gt;
348
349 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
350 it into Debian, where it currently
351 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
352 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
353
354 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
355 for the common folks, ie those not running a large government
356 surveillance system? Well, I plan to put it in a computer on my bike
357 and in my car, tracking the cars nearby and allowing me to be notified
358 when number plates on my watch list are discovered. Another use case
359 was suggested by a friend of mine, who wanted to set it up at his home
360 to open the car port automatically when it discovered the plate on his
361 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
362 capable of placing his license plate number of a piece of cardboard to
363 open his car port, men replied that it was always unlocked anyway. I
364 guess for such use case it make sense. I am sure there are other use
365 cases too, for those with imagination and a vision.&lt;/p&gt;
366
367 &lt;p&gt;If you want to build your own version of the Debian package, check
368 out the upstream git source and symlink ./distros/debian to ./debian/
369 before running &quot;debuild&quot; to build the source. Or wait a bit until the
370 package show up in unstable.&lt;/p&gt;
371 </description>
372 </item>
373
374 <item>
375 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
376 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
378 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
379 <description>&lt;p&gt;Around three years ago, I created
380 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
381 system&lt;/a&gt; to get a more practical solution in Debian for handing
382 hardware related packages. A GUI system in the isenkram package will
383 present a pop-up dialog when some hardware dongle supported by
384 relevant packages in Debian is inserted into the machine. The same
385 lookup mechanism to detect packages is available as command line
386 tools in the isenkram-cli package. In addition to mapping hardware,
387 it will also map kernel firmware files to packages and make it easy to
388 install needed firmware packages automatically. The key for this
389 system to work is a good way to map hardware to packages, in other
390 words, allow packages to announce what hardware they will work
391 with.&lt;/p&gt;
392
393 &lt;p&gt;I started by providing data files in the isenkram source, and
394 adding code to download the latest version of these data files at run
395 time, to ensure every user had the most up to date mapping available.
396 I also added support for storing the mapping in the Packages file in
397 the apt repositories, but did not push this approach because while I
398 was trying to figure out how to best store hardware/package mappings,
399 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
400 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
401 add the hardware mapping into that data set to be able to use
402 appstream as a data source, and this was accepted at least for the
403 Debian version of appstream.&lt;/p&gt;
404
405 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
406 and today I uploaded a new version 0.20 of isenkram adding support for
407 appstream as a data source for mapping hardware to packages. The only
408 package so far using appstream to announce its hardware support is my
409 pymissile package. I got help from Matthias Klumpp with figuring out
410 how do add the required
411 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
412 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
413 this content:&lt;/p&gt;
414
415 &lt;blockquote&gt;&lt;pre&gt;
416 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
417 &amp;lt;component&amp;gt;
418 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
419 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
420 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
421 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
422 &amp;lt;description&amp;gt;
423 &amp;lt;p&amp;gt;
424 Pymissile provides a curses interface to control an original
425 Marks and Spencer / Striker USB Missile Launcher, as well as a
426 motion control script to allow a webcamera to control the
427 launcher.
428 &amp;lt;/p&amp;gt;
429 &amp;lt;/description&amp;gt;
430 &amp;lt;provides&amp;gt;
431 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
432 &amp;lt;/provides&amp;gt;
433 &amp;lt;/component&amp;gt;
434 &lt;/pre&gt;&lt;/blockquote&gt;
435
436 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
437 which is a glob style match rule for hardware specific strings
438 (modalias strings) provided by the Linux kernel. In this case, it
439 will map to all USB devices with vendor code 1130 and product code
440 0202.&lt;/p&gt;
441
442 &lt;p&gt;Note, it is important that the license of all the metadata files
443 are compatible to have permissions to aggregate them into archive wide
444 appstream files. Matthias suggested to use MIT or BSD licenses for
445 these files. A challenge is figuring out a good id for the data, as
446 it is supposed to be globally unique and shared across distributions
447 (in other words, best to coordinate with upstream what to use). But
448 it can be changed later or, so we went with the package name as
449 upstream for this project is dormant.&lt;/p&gt;
450
451 &lt;p&gt;To get the metadata file installed in the correct location for the
452 mirror update scripts to pick it up and include its content the
453 appstream data source, the file must be installed in the binary
454 package under /usr/share/appdata/. I did this by adding the following
455 line to debian/pymissile.install:&lt;/p&gt;
456
457 &lt;blockquote&gt;&lt;pre&gt;
458 debian/pymissile.metainfo.xml usr/share/appdata
459 &lt;/pre&gt;&lt;/blockquote&gt;
460
461 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
462 all packages useful on the current computer automatically, and the GUI
463 pop-up handler will propose to install the package not already
464 installed if a hardware dongle is inserted into the machine in
465 question.&lt;/p&gt;
466
467 &lt;p&gt;Details of the modalias field in appstream is available from the
468 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
469
470 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
471 try running this command on the command line:&lt;/p&gt;
472
473 &lt;blockquote&gt;&lt;pre&gt;
474 cat $(find /sys/devices/|grep modalias)
475 &lt;/pre&gt;&lt;/blockquote&gt;
476
477 &lt;p&gt;To learn more about the isenkram system, please check out
478 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
479 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
480 </description>
481 </item>
482
483 <item>
484 <title>The GNU General Public License is not magic pixie dust</title>
485 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
486 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
487 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
488 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
489 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
490 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
491 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
492 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
493
494 &lt;blockquote&gt;
495
496 &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;
497
498 &lt;blockquote&gt;
499 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
500
501 The first step is to choose a
502 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
503 code.&lt;br/&gt;
504
505 The next step is, when someone fails to follow that copyleft license,
506 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
507
508 and its a simple fact of our modern society that such type of
509 work&lt;br/&gt;
510
511 is incredibly expensive to do and incredibly difficult to do.
512 &lt;/blockquote&gt;
513
514 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
515 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
516 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
517 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
518
519 &lt;p&gt;As the Debian Website
520 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
521 &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;
522 imply, public domain and permissively licensed software can lead to
523 the production of more proprietary software as people discover useful
524 software, extend it and or incorporate it into their hardware or
525 software products. Copyleft licenses such as the GNU GPL were created
526 to close off this avenue to the production of proprietary software but
527 such licenses are not enough. With the ongoing adoption of Free
528 Software by individuals and groups, inevitably the community&#39;s
529 expectations of license compliance are violated, usually out of
530 ignorance of the way Free Software works, but not always. As Karen
531 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
532 Freedom&quot;&gt;FaiF&lt;/a&gt;
533 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
534 copyleft is nothing if no-one is willing and able to stand up in court
535 to protect it. The reality of today&#39;s world is that legal
536 representation is expensive, difficult and time consuming. With
537 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
538 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
539 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
540 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
541 of the Linux project, Debian and other groups against GPL violations.
542 In March the SFC supported a
543 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
544 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
545 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
546 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
547 kernel. Since then two of their sponsors pulled corporate funding and
548 conferences
549 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
550 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
551 less on corporate funding and more on the broad community of
552 individuals who support Free Software and copyleft. So the SFC has
553 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
554 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
555 a community of folks who stand up for copyleft and the GPL by
556 supporting their work on promoting and supporting copyleft and Free
557 Software.&lt;/p&gt;
558
559 &lt;p&gt;If you support Free Software,
560 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
561 what the SFC do, agree with their
562 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
563 principles&lt;/a&gt;, are happy about their
564 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
565 work on a project that is an SFC
566 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
567 just want to stand up for copyleft, please join
568 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
569 Allan Webber&lt;/a&gt;,
570 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
571 Smith&lt;/a&gt;,
572 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
573 Bacon&lt;/a&gt;, myself and
574 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
575 becoming a
576 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
577 next week your donation will be
578 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
579 by an anonymous donor. Please also consider asking your employer to
580 match your donation or become a sponsor of SFC. Don&#39;t forget to
581 spread the word about your support for SFC via email, your blog and or
582 social media accounts.&lt;/p&gt;
583
584 &lt;/blockquote&gt;
585
586 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
587 of Software Freedom Conservancy myself. Perhaps you should be a
588 supporter too?&lt;/p&gt;
589 </description>
590 </item>
591
592 <item>
593 <title>PGP key transition statement for key EE4E02F9</title>
594 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
595 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
596 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
597 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
598 set it up properly. I wanted to generate it offline and have it
599 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
600 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
601 time to sit down with an offline machine almost took forever. But
602 finally I&#39;ve been able to complete the process, and have now moved
603 from my old GPG key to a new GPG key. See
604 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
605 full transition statement, signed with both my old and new key&lt;/a&gt; for
606 the details. This is my new key:&lt;/p&gt;
607
608 &lt;pre&gt;
609 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]
610 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
611 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
612 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
613 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
614 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
615 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
616 &lt;/pre&gt;
617
618 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
619 my old key.&lt;/p&gt;
620
621 &lt;p&gt;If you signed my old key
622 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
623 I&#39;d very much appreciate a signature on my new key, details and
624 instructions in the transition statement. I m happy to reciprocate if
625 you have a similarly signed transition statement to present.&lt;/p&gt;
626 </description>
627 </item>
628
629 <item>
630 <title>The life and death of a laptop battery</title>
631 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
632 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
633 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
634 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
635 But this do not last. The last few laptops gave me a feeling that
636 within a year, the life time is just a fraction of what it used to be,
637 and it slowly become painful to use the laptop without power connected
638 all the time. Because of this, when I got a new Thinkpad X230 laptop
639 about two years ago, I decided to monitor its battery state to have
640 more hard facts when the battery started to fail.&lt;/p&gt;
641
642 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
643
644 &lt;p&gt;First I tried to find a sensible Debian package to record the
645 battery status, assuming that this must be a problem already handled
646 by someone else. I found
647 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
648 which collects statistics from the battery, but it was completely
649 broken. I sent a few suggestions to the maintainer, but decided to
650 write my own collector as a shell script while I waited for feedback
651 from him. Via
652 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
653 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
654 discovered
655 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
656 available in Debian.&lt;/p&gt;
657
658 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
659 battery stats ever since. Now my
660 /var/log/hjemmenett-battery-status.log file contain around 115,000
661 measurements, from the time the battery was working great until now,
662 when it is unable to charge above 7% of original capacity. My
663 collector shell script is quite simple and look like this:&lt;/p&gt;
664
665 &lt;pre&gt;
666 #!/bin/sh
667 # Inspired by
668 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
669 # See also
670 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
671 logfile=/var/log/hjemmenett-battery-status.log
672
673 files=&quot;manufacturer model_name technology serial_number \
674 energy_full energy_full_design energy_now cycle_count status&quot;
675
676 if [ ! -e &quot;$logfile&quot; ] ; then
677 (
678 printf &quot;timestamp,&quot;
679 for f in $files; do
680 printf &quot;%s,&quot; $f
681 done
682 echo
683 ) &gt; &quot;$logfile&quot;
684 fi
685
686 log_battery() {
687 # Print complete message in one echo call, to avoid race condition
688 # when several log processes run in parallel.
689 msg=$(printf &quot;%s,&quot; $(date +%s); \
690 for f in $files; do \
691 printf &quot;%s,&quot; $(cat $f); \
692 done)
693 echo &quot;$msg&quot;
694 }
695
696 cd /sys/class/power_supply
697
698 for bat in BAT*; do
699 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
700 done
701 &lt;/pre&gt;
702
703 &lt;p&gt;The script is called when the power management system detect a
704 change in the power status (power plug in or out), and when going into
705 and out of hibernation and suspend. In addition, it collect a value
706 every 10 minutes. This make it possible for me know when the battery
707 is discharging, charging and how the maximum charge change over time.
708 The code for the Debian package
709 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
710 available on github&lt;/a&gt;.&lt;/p&gt;
711
712 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
713
714 &lt;pre&gt;
715 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
716 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
717 [...]
718 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
719 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
720 &lt;/pre&gt;
721
722 &lt;p&gt;I wrote a small script to create a graph of the charge development
723 over time. This graph depicted above show the slow death of my laptop
724 battery.&lt;/p&gt;
725
726 &lt;p&gt;But why is this happening? Why are my laptop batteries always
727 dying in a year or two, while the batteries of space probes and
728 satellites keep working year after year. If we are to believe
729 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
730 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
731 chance, and the fix is to not charge the Lithium-ion batteries to 100%
732 all the time, but to stay below 90% of full charge most of the time.
733 I&#39;ve been told that the Tesla electric cars
734 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
735 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
736 100% when preparing for a longer trip (not that I would want a car
737 like Tesla where rights to privacy is abandoned, but that is another
738 story), which I guess is the option we should have for laptops on
739 Linux too.&lt;/p&gt;
740
741 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
742 stop charging at 80%, unless requested to charge to 100% once in
743 preparation for a longer trip? I found
744 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
745 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
746 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
747 load).&lt;/p&gt;
748
749 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
750 at the start. I also wonder why the &quot;full capacity&quot; increases some
751 times, and if it is possible to repeat the process to get the battery
752 back to design capacity. And I wonder if the discharge and charge
753 speed change over time, or if this stay the same. I did not yet try
754 to write a tool to calculate the derivative values of the battery
755 level, but suspect some interesting insights might be learned from
756 those.&lt;/p&gt;
757
758 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
759 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
760 packages instead of the tp-smapi-dkms package I had tried to use
761 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
762 and stop. I&#39;ve done so now, but expect my existing battery is toast
763 and need to be replaced. The proposal is unfortunately Thinkpad
764 specific.&lt;/p&gt;
765 </description>
766 </item>
767
768 <item>
769 <title>New laptop - some more clues and ideas based on feedback</title>
770 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
771 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
772 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
773 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
774 need for a new laptop, and provided very useful feedback. I wish to
775 thank every one of these. Several pointed me to the possibility of
776 fixing my X230, and I am already in the process of getting Lenovo to
777 do so thanks to the on site, next day support contract covering the
778 machine. But the battery is almost useless (I expect to replace it
779 with a non-official battery) and I do not expect the machine to live
780 for many more years, so it is time to plan its replacement. If I did
781 not have a support contract, it was suggested to find replacement parts
782 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
783 might present a language barrier as I do not understand French.&lt;/p&gt;
784
785 &lt;p&gt;One tip I got was to use the
786 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
787 compare laptop models. It seem to have more models available than
788 prisjakt.no. Another tip I got from someone I know have similar
789 keyboard preferences was that the HP EliteBook 840 keyboard is not
790 very good, and this matches my experience with earlier EliteBook
791 keyboards I tested. Because of this, I will not consider it any further.
792
793 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
794 newest Thinkpad X model. The keyboard reintroduces mouse buttons
795 (which is missing from the X240), and is working fairly well with
796 Debian Sid/Unstable according to
797 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
798 got on the keyboard quality are not consistent. Some say the keyboard
799 is good, others say it is ok, while others say it is not very good.
800 Those with experience from X41 and and X60 agree that the X250
801 keyboard is not as good as those trusty old laptops, and suggest I
802 keep and fix my X230 instead of upgrading, or get a used X230 to
803 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
804 activity and battery status, which is very convenient on my X230. I&#39;m
805 also told that the CPU fan is running very often, making it a bit
806 noisy. In any case, the X250 do not work out of the box with Debian
807 Stable/Jessie, one of my requirements.&lt;/p&gt;
808
809 &lt;p&gt;I have also gotten a few vendor proposals, one was
810 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
811 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
812 The latter look very attractive to me.&lt;/p&gt;
813
814 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
815 as I keep looking for a replacement.&lt;/p&gt;
816
817 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
818 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
819 different
820 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
821 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
822 </description>
823 </item>
824
825 <item>
826 <title>Time to find a new laptop, as the old one is broken after only two years</title>
827 <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>
828 <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>
829 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
830 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
831 replacement soon. The left 5 cm of the screen on my Thinkpad X230
832 started flickering yesterday, and I suspect the cause is a broken
833 cable, as changing the angle of the screen some times get rid of the
834 flickering.&lt;/p&gt;
835
836 &lt;p&gt;My requirements have not really changed since I bought it, and is
837 still as
838 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
839 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
840 good help from
841 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
842 where I could select at least a few of the requirements (mouse pin,
843 wifi, weight) and go through the rest manually. Three button mouse
844 and a good keyboard is not available as an option, and all the three
845 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
846 G2) lack three mouse buttons). It is also unclear to me how good the
847 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
848 the keyboard, even if the quality and robustness in the X series have
849 deteriorated since X41.&lt;/p&gt;
850
851 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
852 seem sensible to me? Are there better services around to search the
853 set of available laptops for features? Please send me an email if you
854 have suggestions.&lt;/p&gt;
855
856 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
857 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
858 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
859 </description>
860 </item>
861
862 <item>
863 <title>How to stay with sysvinit in Debian Jessie</title>
864 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
865 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
866 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
867 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
868 sysvinit as its boot system by default. But how can one keep using
869 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
870 courtesy of
871 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
872 Schubert&lt;/a&gt; and
873 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
874 McVittie&lt;/a&gt;.
875
876 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
877 keep sysvinit as your boot system, create a file
878 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
879 you upgrade:&lt;/p&gt;
880
881 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
882 Package: systemd-sysv
883 Pin: release o=Debian
884 Pin-Priority: -1
885 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
886
887 &lt;p&gt;This file content will tell apt and aptitude to not consider
888 installing systemd-sysv as part of any installation and upgrade
889 solution when resolving dependencies, and thus tell it to avoid
890 systemd as a default boot system. The end result should be that the
891 upgraded system keep using sysvinit.&lt;/p&gt;
892
893 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
894 get sysvinit installed by default (debootstrap used by
895 debian-installer have no option for this), but one can tell the
896 installer to switch to sysvinit before the first boot. Either by
897 using a kernel argument to the installer, or by adding a line to the
898 preseed file used. First, the kernel command line argument:
899
900 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
901 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
902 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
903
904 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
905
906 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
907 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
908 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
909
910 &lt;p&gt;One can of course also do this after the first boot by installing
911 the sysvinit-core package.&lt;/p&gt;
912
913 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
914 sysvinit boot sequence in Debian have several hardware specific bugs
915 on Linux caused by the fact that it is unpredictable when hardware
916 devices show up during boot. But on the other hand, the new default
917 boot system still have a few rough edges I hope will be fixed before
918 Jessie is released.&lt;/p&gt;
919
920 &lt;p&gt;Update 2014-11-26: Inspired by
921 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
922 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
923 line.&lt;/p&gt;
924 </description>
925 </item>
926
927 <item>
928 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
929 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
930 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
931 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
932 <description>&lt;p&gt;The right to communicate with your friends and family in private,
933 without anyone snooping, is a right every citicen have in a liberal
934 democracy. But this right is under serious attack these days.&lt;/p&gt;
935
936 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
937 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
938 the whisleblower Snowden) more expensive for Internet email,
939 is to deliver all email using SMTP via Tor. Such SMTP option would be
940 a nice addition to the FreedomBox project if we could send email
941 between FreedomBox machines without leaking metadata about the emails
942 to the people peeking on the wire. I
943 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
944 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
945 lot of useful feedback and suggestions. It also became obvious to me
946 that this was not a novel idea, as the same idea was tested and
947 documented by Johannes Berg as early as 2006, and both
948 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
949 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
950 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
951
952 &lt;p&gt;To implement such system one need to set up a Tor hidden service
953 providing the SMTP protocol on port 25, and use email addresses
954 looking like username@hidden-service-name.onion. With such addresses
955 the connections to port 25 on hidden-service-name.onion using Tor will
956 go to the correct SMTP server. To do this, one need to configure the
957 Tor daemon to provide the hidden service and the mail server to accept
958 emails for this .onion domain. To learn more about Exim configuration
959 in Debian and test the design provided by Johannes Berg in his FAQ, I
960 set out yesterday to create a Debian package for making it trivial to
961 set up such SMTP over Tor service based on Debian. Getting it to work
962 were fairly easy, and
963 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
964 source code for the Debian package&lt;/a&gt; is available from github. I
965 plan to move it into Debian if further testing prove this to be a
966 useful approach.&lt;/p&gt;
967
968 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
969 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
970 get rid of exim4). Install tor, clone the git repository mentioned
971 above, build the deb and install it on the machine. Next, run
972 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
973 the instructions to get the service up and running. Restart tor and
974 exim when it is done, and test mail delivery using swaks like
975 this:&lt;/p&gt;
976
977 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
978 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
979 --to fbx@dutlqrrmjhtfa3vp.onion
980 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
981
982 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
983 address with your own address to test your server. :)&lt;/p&gt;
984
985 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
986 easier and more automatic. Especially the tor setup need more work.
987 Also, the package include a tor-smtp tool written in C, but its task
988 should probably be rewritten in some script language to make the deb
989 architecture independent. It would probably also make the code easier
990 to review. The tor-smtp tool currently need to listen on a socket for
991 exim to talk to it and is started using xinetd. It would be better if
992 no daemon and no socket is needed. I suspect it is possible to get
993 exim to run a command line tool for delivery instead of talking to a
994 socket, and hope to figure out how in a future version of this
995 system.&lt;/p&gt;
996
997 &lt;p&gt;Until I wipe my test machine, I can be reached using the
998 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
999 SMTorP. :)&lt;/p&gt;
1000 </description>
1001 </item>
1002
1003 <item>
1004 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
1005 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
1006 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
1007 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
1008 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
1009 alioth.debian.org, you know the web interface is fairly slow to
1010 operate. First you visit one web page, enter the moderation password
1011 and get a new page shown with a list of all the messages to moderate
1012 and various options for each email address. This take a while for
1013 every list you moderate, and you need to do it regularly to do a good
1014 job as a list moderator. But there is a quick alternative,
1015 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
1016 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
1017 to moderate in a fraction of a second. Here is a test run on two
1018 lists I recently took over:&lt;/p&gt;
1019
1020 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1021 % time listadmin xiph
1022 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1023 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1024
1025 real 0m1.709s
1026 user 0m0.232s
1027 sys 0m0.012s
1028 %
1029 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1030
1031 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
1032 there are no message in the moderation queue. Every morning I
1033 currently moderate 68 mailman lists, and it normally take around two
1034 minutes. When I took over the two pkg-xiph lists above a few days
1035 ago, there were 400 emails waiting in the moderator queue. It took me
1036 less than 15 minutes to process them all using the listadmin
1037 program.&lt;/p&gt;
1038
1039 &lt;p&gt;If you install
1040 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
1041 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
1042 with content like this, the moderation task is a breeze:&lt;/p&gt;
1043
1044 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1045 username username@example.org
1046 spamlevel 23
1047 default discard
1048 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
1049
1050 password secret
1051 adminurl https://{domain}/mailman/admindb/{list}
1052 mailman-list@lists.example.com
1053
1054 password hidden
1055 other-list@otherserver.example.org
1056 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1057
1058 &lt;p&gt;There are other options to set as well. Check the manual page to
1059 learn the details.&lt;/p&gt;
1060
1061 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
1062 the SSL certificate is self signed or not properly signed by a
1063 generally accepted signing authority, you can set a environment
1064 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
1065
1066 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1067 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
1068 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1069
1070 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
1071 can provide an argument to the listadmin script like I do in the
1072 initial screen dump (the xiph argument). Using an argument, only
1073 lists matching the argument string will be processed. This make it
1074 quick to accept messages if you notice the moderation request in your
1075 email.&lt;/p&gt;
1076
1077 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
1078 mailing lists, as I simply do not have time to spend on that if the
1079 process was any slower. The listadmin program have saved me hours of
1080 time I could spend elsewhere over the years. It truly is nice free
1081 software.&lt;/p&gt;
1082
1083 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1084 activities, please send Bitcoin donations to my address
1085 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1086
1087 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1088 configuration example. Also, I&#39;ve been told that the
1089 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1090 sure why.&lt;/p&gt;
1091 </description>
1092 </item>
1093
1094 <item>
1095 <title>Debian Jessie, PXE and automatic firmware installation</title>
1096 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1097 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1098 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1099 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1100 problem that the WiFi card require some firmware to work properly.
1101 And it has been a pain to fix this using preseeding in Debian.
1102 Normally something more is needed. But thanks to
1103 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1104 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1105 to do this using simple preseeding.&lt;/p&gt;
1106
1107 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1108 firmware for the hardware found in the machine (actually, requested by
1109 the kernel modules for the hardware). (It can also install user space
1110 programs supporting the hardware detected, but that is not the focus
1111 of this story.)&lt;/p&gt;
1112
1113 &lt;p&gt;To get this working in the default installation, two preeseding
1114 values are needed. First, the isenkram-cli package must be installed
1115 into the target chroot (aka the hard drive) before tasksel is executed
1116 in the pkgsel step of the debian-installer system. This is done by
1117 preseeding the base-installer/includes debconf value to include the
1118 isenkram-cli package. The package name is next passed to debootstrap
1119 for installation. With the isenkram-cli package in place, tasksel
1120 will automatically use the isenkram tasks to detect hardware specific
1121 packages for the machine being installed and install them, because
1122 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1123
1124 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1125 most firmware unfortunately is non-free. This is done by preseeding
1126 the apt-mirror-setup step. This is unfortunate, but for a lot of
1127 hardware it is the only option in Debian.&lt;/p&gt;
1128
1129 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1130 firmware installed automatically by the installer:&lt;/p&gt;
1131
1132 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1133 base-installer base-installer/includes string isenkram-cli
1134 apt-mirror-setup apt-setup/non-free boolean true
1135 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1136
1137 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1138 both firmware and user space packages when using this method. It also
1139 do not work well, so use version 0.15 or later. Installing both
1140 firmware and user space packages might give you a bit more than you
1141 want, so I decided to split the tasksel task in two, one for firmware
1142 and one for user space programs. The firmware task is enabled by
1143 default, while the one for user space programs is not. This split is
1144 implemented in the package currently in unstable.&lt;/p&gt;
1145
1146 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1147 this recipe work for you. :)&lt;/p&gt;
1148
1149 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1150 foremost, it work because tasksel is modular, and driven by whatever
1151 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1152 isenkram-cli package place two files for tasksel to find. First there
1153 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1154
1155 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1156 Task: isenkram-packages
1157 Section: hardware
1158 Description: Hardware specific packages (autodetected by isenkram)
1159 Based on the detected hardware various hardware specific packages are
1160 proposed.
1161 Test-new-install: show show
1162 Relevance: 8
1163 Packages: for-current-hardware
1164
1165 Task: isenkram-firmware
1166 Section: hardware
1167 Description: Hardware specific firmware packages (autodetected by isenkram)
1168 Based on the detected hardware various hardware specific firmware
1169 packages are proposed.
1170 Test-new-install: mark show
1171 Relevance: 8
1172 Packages: for-current-hardware-firmware
1173 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1174
1175 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1176 should be handled and the Packages line referencing to a script in
1177 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1178 list of packages to install. The for-current-hardware-firmware script
1179 look like this to list relevant firmware for the machine:
1180
1181 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1182 #!/bin/sh
1183 #
1184 PATH=/usr/sbin:$PATH
1185 export PATH
1186 isenkram-autoinstall-firmware -l
1187 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1188
1189 &lt;p&gt;With those two pieces in place, the firmware is installed by
1190 tasksel during the normal d-i run. :)&lt;/p&gt;
1191
1192 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1193 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1194 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1195 install.&lt;/p&gt;
1196
1197 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1198 pilots in testing this feature, as isenkram is used there now to
1199 install firmware, replacing the earlier scripts.&lt;/p&gt;
1200 </description>
1201 </item>
1202
1203 <item>
1204 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1205 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1206 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1207 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1208 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1209 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1210 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1211 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1212
1213 &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;
1214
1215 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1216 about this hidden Linux installation. It is interesting what
1217 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1218 </description>
1219 </item>
1220
1221 <item>
1222 <title>New lsdvd release version 0.17 is ready</title>
1223 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1224 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1225 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1226 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1227 got a new set of developers a few weeks ago, after the original
1228 developer decided to step down and pass the project to fresh blood.
1229 This project is now maintained by Petter Reinholdtsen and Steve
1230 Dibb.&lt;/p&gt;
1231
1232 &lt;p&gt;I just wrapped up
1233 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1234 new lsdvd release&lt;/a&gt;, available in git or from
1235 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1236 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1237 0.17.&lt;/p&gt;
1238
1239 &lt;ul&gt;
1240
1241 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1242 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1243 non-existant, to work around additional copy protection&lt;/li&gt;
1244 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1245 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1246 &lt;li&gt;Fix include orders&lt;/li&gt;
1247 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1248 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1249 &lt;li&gt;Make sure the array size and the array limit used when initialising
1250 the palette size is the same.&lt;/li&gt;
1251 &lt;li&gt;Fix array printing.&lt;/li&gt;
1252 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1253 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1254 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1255 with more GCC compiler warnings.&lt;/li&gt;
1256
1257 &lt;/ul&gt;
1258
1259 &lt;p&gt;This change bring together patches for lsdvd in use in various
1260 Linux and Unix distributions, as well as patches submitted to the
1261 project the last nine years. Please check it out. :)&lt;/p&gt;
1262 </description>
1263 </item>
1264
1265 <item>
1266 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1267 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1268 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1269 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1270 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1271 project&lt;/a&gt; provide a Linux solution for schools, including a
1272 powerful desktop with education software, a central server providing
1273 web pages, user database, user home directories, central login and PXE
1274 boot of both clients without disk and the installation to install Debian
1275 Edu on machines with disk (and a few other services perhaps to small
1276 to mention here). We in the Debian Edu team are currently working on
1277 the Jessie based version, trying to get everything in shape before the
1278 freeze, to avoid having to maintain our own package repository in the
1279 future. The
1280 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1281 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1282 work left. Some fatal problems block testing, breaking the installer,
1283 but it is possible to work around these to get anyway. Here is a
1284 recipe on how to get the installation limping along.&lt;/p&gt;
1285
1286 &lt;p&gt;First, download the test ISO via
1287 &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;,
1288 &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;
1289 or rsync (use
1290 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1291 The ISO build was broken on Tuesday, so we do not get a new ISO every
1292 12 hours or so, but thankfully the ISO we already got we are able to
1293 install with some tweaking.&lt;/p&gt;
1294
1295 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1296 (use Alt-Ctrl-F2), run&lt;/p&gt;
1297
1298 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1299 nano /usr/bin/edu-eatmydata-install
1300 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1301
1302 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1303 optimization. Return to the installation, select the profile you want
1304 and continue. Without this change, exim4-config will fail to install
1305 due to a known bug in eatmydata.&lt;/p&gt;
1306
1307 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1308 this do not work, figure out what your correct value would be. All my
1309 test machines need /dev/sda, so I have no advice if it do not fit
1310 your need.&lt;/p&gt;
1311
1312 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1313 root after the initial boot from hard drive, and install the
1314 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1315 or mate. If you want several desktop options, install more than one
1316 metapackage. Once this is done, reboot and you should have a working
1317 graphical login screen. This workaround should no longer be needed
1318 once the education-tasks package version 1.801 enter testing in two
1319 days.&lt;/p&gt;
1320
1321 &lt;p&gt;I believe the ISO build will start working on two days when the new
1322 tasksel package enter testing and Steve McIntyre get a chance to
1323 update the debian-cd git repository. The eatmydata, grub and desktop
1324 issues are already fixed in unstable and testing, and should show up
1325 on the ISO as soon as the ISO build start working again. Well the
1326 eatmydata optimization is really just disabled. The proper fix
1327 require an upload by the eatmydata maintainer applying the patch
1328 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1329 The rest have proper fixes in unstable.&lt;/p&gt;
1330
1331 &lt;p&gt;I hope this get you going with the installation testing, as we are
1332 quickly running out of time trying to get our Jessie based
1333 installation ready before the distribution freeze in a month.&lt;/p&gt;
1334 </description>
1335 </item>
1336
1337 <item>
1338 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1339 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1340 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1341 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1342 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1343 to handle my fairly large DVD collection. It is a nice command line
1344 tool to get details about a DVD, like title, tracks, track length,
1345 etc, in XML, Perl or human readable format. But lsdvd have not seen
1346 any new development since 2006 and had a few irritating bugs affecting
1347 its use with some DVDs. Upstream seemed to be dead, and in January I
1348 sent a small probe asking for a version control repository for the
1349 project, without any reply. But I use it regularly and would like to
1350 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1351 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1352 the project admin, and after getting a reply from him explaining that
1353 he was no longer interested in the project, I asked if I could take
1354 over. And yesterday, I became project admin.&lt;/p&gt;
1355
1356 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1357 maintainer interested in joining forces to maintain the upstream
1358 project, and I hope we can get a new release out fairly quickly,
1359 collecting the patches spread around on the internet into on place.
1360 I&#39;ve added the relevant Debian patches to the freshly created git
1361 repository, and expect the Gentoo patches to make it too. If you got
1362 a DVD collection and care about command line tools, check out
1363 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1364 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1365 list&lt;/a&gt;. :)&lt;/p&gt;
1366 </description>
1367 </item>
1368
1369 <item>
1370 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1371 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1373 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1374 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1375 a lot quicker. When we install more than 2000 packages in
1376 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1377 tasksel in the installer, unpacking the binary packages take forever.
1378 A part of the slow I/O issue was discussed in
1379 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1380 much file system sync-ing done by dpkg, which is the package
1381 responsible for unpacking the binary packages. Other parts (like code
1382 executed by postinst scripts) might also sync to disk during
1383 installation. All this sync-ing to disk do not really make sense to
1384 me. If the machine crash half-way through, I start over, I do not try
1385 to salvage the half installed system. So the failure sync-ing is
1386 supposed to protect against, hardware or system crash, is not really
1387 relevant while the installer is running.&lt;/p&gt;
1388
1389 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1390 system sync()-ing in a fairly non-intrusive way, without the need to
1391 change the code in several packages. The idea is not new, but I have
1392 not heard anyone propose the approach using dpkg-divert before. It
1393 depend on the small and clever package
1394 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1395 uses LD_PRELOAD to replace the system functions for syncing data to
1396 disk with functions doing nothing, thus allowing programs to live
1397 dangerous while speeding up disk I/O significantly. Instead of
1398 modifying the implementation of dpkg, apt and tasksel (which are the
1399 packages responsible for selecting, fetching and installing packages),
1400 it occurred to me that we could just divert the programs away, replace
1401 them with a simple shell wrapper calling
1402 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1403 Two days ago I decided to test the idea, and wrapped up a simple
1404 implementation for the Debian Edu udeb.&lt;/p&gt;
1405
1406 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1407 time of the pkgsel step (installing tasks) from 64 to less than 44
1408 minutes (20 minutes shaved off the installation) on an old Dell
1409 Latitude D505 machine. I am not quite sure what the optimised time
1410 would have been, as I messed up the testing a bit, causing the debconf
1411 priority to get low enough for two questions to pop up during
1412 installation. As soon as I saw the questions I moved the installation
1413 along, but do not know how long the question were holding up the
1414 installation. I did some more measurements using Debian Edu Jessie,
1415 and got these results. The time measured is the time stamp in
1416 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1417 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1418 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1419 timing thus do not depend on how quickly the user handle the tasksel
1420 dialog.&lt;/p&gt;
1421
1422 &lt;p&gt;&lt;table&gt;
1423
1424 &lt;tr&gt;
1425 &lt;th&gt;Machine/setup&lt;/th&gt;
1426 &lt;th&gt;Original tasksel&lt;/th&gt;
1427 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1428 &lt;th&gt;Reduction&lt;/th&gt;
1429 &lt;/tr&gt;
1430
1431 &lt;tr&gt;
1432 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1433 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1434 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1435 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1436 &lt;/tr&gt;
1437
1438 &lt;tr&gt;
1439 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1440 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1441 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1442 &lt;td&gt;23 min 40%&lt;/td&gt;
1443 &lt;/tr&gt;
1444
1445 &lt;tr&gt;
1446 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1447 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1448 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1449 &lt;td&gt;11 min 50%&lt;/td&gt;
1450 &lt;/tr&gt;
1451
1452 &lt;tr&gt;
1453 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1454 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1455 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1456 &lt;td&gt;2 min 33%&lt;/td&gt;
1457 &lt;/tr&gt;
1458
1459 &lt;tr&gt;
1460 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1461 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1462 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1463 &lt;td&gt;4 min 21%&lt;/td&gt;
1464 &lt;/tr&gt;
1465
1466 &lt;/table&gt;&lt;/p&gt;
1467
1468 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1469 time is spent downloading packages. The connection to the Internet
1470 was 100Mbit/s during testing, so downloading should not be a
1471 significant factor in the measurement. Download typically took a few
1472 seconds to a few minutes, depending on the amount of packages being
1473 installed.&lt;/p&gt;
1474
1475 &lt;p&gt;The speedup is implemented by using two hooks in
1476 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1477 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1478 finish-install.d hook to remove the divert at the end of the
1479 installation. I picked the pre-pkgsel.d hook instead of the
1480 post-base-installer.d hook because I test using an ISO without the
1481 eatmydata package included, and the post-base-installer.d hook in
1482 Debian Edu can only operate on packages included in the ISO. The
1483 negative effect of this is that I am unable to activate this
1484 optimization for the kernel installation step in d-i. If the code is
1485 moved to the post-base-installer.d hook, the speedup would be larger
1486 for the entire installation.&lt;/p&gt;
1487
1488 &lt;p&gt;I&#39;ve implemented this in the
1489 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1490 git repository, and plan to provide the optimization as part of the
1491 Debian Edu installation. If you want to test this yourself, you can
1492 create two files in the installer (or in an udeb). One shell script
1493 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1494
1495 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1496 #!/bin/sh
1497 set -e
1498 . /usr/share/debconf/confmodule
1499 info() {
1500 logger -t my-pkgsel &quot;info: $*&quot;
1501 }
1502 error() {
1503 logger -t my-pkgsel &quot;error: $*&quot;
1504 }
1505 override_install() {
1506 apt-install eatmydata || true
1507 if [ -x /target/usr/bin/eatmydata ] ; then
1508 for bin in dpkg apt-get aptitude tasksel ; do
1509 file=/usr/bin/$bin
1510 # Test that the file exist and have not been diverted already.
1511 if [ -f /target$file ] ; then
1512 info &quot;diverting $file using eatmydata&quot;
1513 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1514 &gt; /target$file.edu
1515 chmod 755 /target$file.edu
1516 in-target dpkg-divert --package debian-edu-config \
1517 --rename --quiet --add $file
1518 ln -sf ./$bin.edu /target$file
1519 else
1520 error &quot;unable to divert $file, as it is missing.&quot;
1521 fi
1522 done
1523 else
1524 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1525 fi
1526 }
1527
1528 override_install
1529 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1530
1531 &lt;p&gt;To clean up, another shell script should go into
1532 /usr/lib/finish-install.d/ with code like this:
1533
1534 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1535 #! /bin/sh -e
1536 . /usr/share/debconf/confmodule
1537 error() {
1538 logger -t my-finish-install &quot;error: $@&quot;
1539 }
1540 remove_install_override() {
1541 for bin in dpkg apt-get aptitude tasksel ; do
1542 file=/usr/bin/$bin
1543 if [ -x /target$file.edu ] ; then
1544 rm /target$file
1545 in-target dpkg-divert --package debian-edu-config \
1546 --rename --quiet --remove $file
1547 rm /target$file.edu
1548 else
1549 error &quot;Missing divert for $file.&quot;
1550 fi
1551 done
1552 sync # Flush file buffers before continuing
1553 }
1554
1555 remove_install_override
1556 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1557
1558 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1559 edu-eatmydata-install and call it from the pre-pkgsel.d and
1560 finish-install.d scripts.&lt;/p&gt;
1561
1562 &lt;p&gt;By now you might ask if this change should get into the normal
1563 Debian installer too? I suspect it should, but am not sure the
1564 current debian-installer coordinators find it useful enough. It also
1565 depend on the side effects of the change. I&#39;m not aware of any, but I
1566 guess we will see if the change is safe after some more testing.
1567 Perhaps there is some package in Debian depending on sync() and
1568 fsync() having effect? Perhaps it should go into its own udeb, to
1569 allow those of us wanting to enable it to do so without affecting
1570 everyone.&lt;/p&gt;
1571
1572 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1573 will break installation of all programs using gnutls because of
1574 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1575 eatmydata package in Debian will solve it.&lt;/p&gt;
1576
1577 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1578 the optimization work again. And I have discovered that the
1579 dpkg-divert trick is not really needed and implemented a slightly
1580 simpler approach as part of the debian-edu-install package. See
1581 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1582
1583 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1584 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1585 triggering on i386 made it into testing, and broke this installation
1586 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1587 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1588 </description>
1589 </item>
1590
1591 <item>
1592 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1593 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1594 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1595 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1596 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1597 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1598 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1599 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1600 learn that there is a large set of publicly available key servers to
1601 use when looking for peoples public key. So far I have used
1602 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1603 were misbehaving, but those days are ended. The servers I have used
1604 up until yesterday have been slow and some times unavailable. I hope
1605 those problems are gone now.&lt;/p&gt;
1606
1607 &lt;p&gt;Behind the round robin DNS entry of the
1608 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1609 there is a pool of more than 100 keyservers which are checked every
1610 day to ensure they are well connected and up to date. It must be
1611 better than what I have used so far. :)&lt;/p&gt;
1612
1613 &lt;p&gt;Yesterdays speaker told me that the service is the default
1614 keyserver provided by the default configuration in GnuPG, but this do
1615 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1616
1617 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1618 line:&lt;/p&gt;
1619
1620 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1621 keyserver pool.sks-keyservers.net
1622 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1623
1624 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1625 entries in DNS. Just for fun, I did just that at work, so now every
1626 user of GnuPG at the University of Oslo should find a OpenGPG
1627 keyserver automatically should their need it:&lt;/p&gt;
1628
1629 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1630 % host -t srv _pgpkey-http._tcp.uio.no
1631 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1632 %
1633 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1634
1635 &lt;p&gt;Now if only
1636 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1637 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1638 very happy. It can look up a given key or search for a user ID, but I
1639 normally do not want that, but to find a trust path from my key to
1640 another key. Given a user ID or key ID, I would like to find (and
1641 download) the keys representing a signature path from my key to the
1642 key in question, to be able to get a trust path between the two keys.
1643 This is as far as I can tell not possible today. Perhaps something
1644 for a future version of the protocol?&lt;/p&gt;
1645 </description>
1646 </item>
1647
1648 <item>
1649 <title>From English wiki to translated PDF and epub via Docbook</title>
1650 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1651 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1652 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1653 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1654 project&lt;/a&gt; provide an instruction manual for teachers, system
1655 administrators and other users that contain useful tips for setting up
1656 and maintaining a Debian Edu installation. This text is about how the
1657 text processing of this manual is handled in the project.&lt;/p&gt;
1658
1659 &lt;p&gt;One goal of the project is to provide information in the native
1660 language of its users, and for this we need to handle translations.
1661 But we also want to make sure each language contain the same
1662 information, so for this we need a good way to keep the translations
1663 in sync. And we want it to be easy for our users to improve the
1664 documentation, avoiding the need to learn special formats or tools to
1665 contribute, and the obvious way to do this is to make it possible to
1666 edit the documentation using a web browser. We also want it to be
1667 easy for translators to keep the translation up to date, and give them
1668 help in figuring out what need to be translated. Here is the list of
1669 tools and the process we have found trying to reach all these
1670 goals.&lt;/p&gt;
1671
1672 &lt;p&gt;We maintain the authoritative source of our manual in the
1673 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1674 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1675 front page with references to the different chapters, several pages
1676 for each chapter, and finally one &quot;collection page&quot; gluing all the
1677 chapters together into one large web page (aka
1678 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1679 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1680 processing and translations. Thanks to the fact that the
1681 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1682 wiki.debian.org support exporting pages in
1683 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1684 the list of pages to export using the raw version of the AllInOne
1685 page, loop over each of them to generate a Docbook XML version of the
1686 manual. This process also download images and transform image
1687 references to use the locally downloaded images. The generated
1688 Docbook XML files are slightly broken, so some post-processing is done
1689 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1690 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1691 a handfull of images. The XML file can now be used to generate PDF, HTML
1692 and epub versions of the English manual. This is the basic step of
1693 our process, making PDF (using dblatex), HTML (using xsltproc) and
1694 epub (using dbtoepub) version from Docbook XML, and the resulting files
1695 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1696
1697 &lt;p&gt;But English documentation is not enough for us. We want translated
1698 documentation too, and we want to make it easy for translators to
1699 track the English original. For this we use the
1700 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1701 which allow us to transform the English Docbook XML file into a
1702 translation file (a .pot file), usable with the normal gettext based
1703 translation tools used by those translating free software. The pot
1704 file is used to create and maintain translation files (several .po
1705 files), which the translations update with the native language
1706 translations of all titles, paragraphs and blocks of text in the
1707 original. The next step is combining the original English Docbook XML
1708 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1709 create a translated Docbook XML file (in this case
1710 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1711 translated, if the translation is not complete) Docbook XML file can
1712 then be used like the original to create a PDF, HTML and epub version
1713 of the documentation.&lt;/p&gt;
1714
1715 &lt;p&gt;The translators use different tools to edit the .po files. We
1716 recommend using
1717 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1718 while some use emacs and vi, others can use web based editors like
1719 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1720 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1721 is where the .po file end up, in our git repository. Updated
1722 translations can either be committed directly to git, or submitted as
1723 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1724 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1725
1726 &lt;p&gt;One challenge is images, which both might need to be translated (if
1727 they show translated user applications), and are needed in different
1728 formats when creating PDF and HTML versions (epub is a HTML version in
1729 this regard). For this we transform the original PNG images to the
1730 needed density and format during build, and have a way to provide
1731 translated images by storing translated versions in
1732 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1733 package maintainers know more.&lt;/p&gt;
1734
1735 &lt;p&gt;If you wonder what the result look like, we provide
1736 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1737 of the documentation packages on the web&lt;/a&gt;. See for example the
1738 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1739 PDF version&lt;/a&gt; or the
1740 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1741 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1742 but perhaps it will be done in the future.&lt;/p&gt;
1743
1744 &lt;p&gt;To learn more, check out
1745 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1746 debian-edu-doc package&lt;/a&gt;,
1747 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1748 manual on the wiki&lt;/a&gt; and
1749 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1750 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1751 </description>
1752 </item>
1753
1754 <item>
1755 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1756 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1757 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1758 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1759 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1760 related packages relevant for the computer installed automatically.
1761 So I implemented one, using
1762 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1763 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1764 run tasksel as user root. You should be presented with a new option,
1765 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1766 select it, tasksel will install the packages isenkram claim is fit for
1767 the current hardware, hot pluggable or not.&lt;p&gt;
1768
1769 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1770 description, and the other is the script used to extract the list of
1771 packages to install. The first part is in
1772 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1773 this:&lt;/p&gt;
1774
1775 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1776 Task: isenkram
1777 Section: hardware
1778 Description: Hardware specific packages (autodetected by isenkram)
1779 Based on the detected hardware various hardware specific packages are
1780 proposed.
1781 Test-new-install: mark show
1782 Relevance: 8
1783 Packages: for-current-hardware
1784 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1785
1786 &lt;p&gt;The second part is in
1787 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1788 this:&lt;/p&gt;
1789
1790 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1791 #!/bin/sh
1792 #
1793 (
1794 isenkram-lookup
1795 isenkram-autoinstall-firmware -l
1796 ) | sort -u
1797 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1798
1799 &lt;p&gt;All in all, a very short and simple implementation making it
1800 trivial to install the hardware dependent package we all may want to
1801 have installed on our machines. I&#39;ve not been able to find a way to
1802 get tasksel to tell you exactly which packages it plan to install
1803 before doing the installation. So if you are curious or careful,
1804 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1805
1806 &lt;p&gt;The information about which packages are handling which hardware is
1807 fetched either from the isenkram package itself in
1808 /usr/share/isenkram/, from git.debian.org or from the APT package
1809 database (using the Modaliases header). The APT package database
1810 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1811 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1812 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1813 the python-apt code (bug
1814 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1815 workaround I was able to get rid of the file descriptor leak and
1816 reduce the memory leak from ~30 MiB per hardware detection down to
1817 around 2 MiB per hardware detection. It should make the desktop
1818 daemon a lot more useful. The fix is in version 0.7 uploaded to
1819 unstable today.&lt;/p&gt;
1820
1821 &lt;p&gt;I believe the current way of mapping hardware to packages in
1822 Isenkram is is a good draft, but in the future I expect isenkram to
1823 use the AppStream data source for this. A proposal for getting proper
1824 AppStream support into Debian is floating around as
1825 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1826 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1827 project&lt;/a&gt; will take place this summer to improve the situation. I
1828 look forward to seeing the result, and welcome patches for isenkram to
1829 start using the information when it is ready.&lt;/p&gt;
1830
1831 &lt;p&gt;If you want your package to map to some specific hardware, either
1832 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1833 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1834 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1835 package. See also
1836 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1837 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1838 the information will be migrated to AppStream eventually, but for the
1839 moment I got no better place to store it.&lt;/p&gt;
1840 </description>
1841 </item>
1842
1843 <item>
1844 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1845 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1846 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1847 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1848 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1849 project&lt;/a&gt; is working on providing the software and hardware to make
1850 it easy for non-technical people to host their data and communication
1851 at home, and being able to communicate with their friends and family
1852 encrypted and away from prying eyes. It is still going strong, and
1853 today a major mile stone was reached.&lt;/p&gt;
1854
1855 &lt;p&gt;Today, the last of the packages currently used by the project to
1856 created the system images were accepted into Debian Unstable. It was
1857 the freedombox-setup package, which is used to configure the images
1858 during build and on the first boot. Now all one need to get going is
1859 the build code from the freedom-maker git repository and packages from
1860 Debian. And once the freedombox-setup package enter testing, we can
1861 build everything directly from Debian. :)&lt;/p&gt;
1862
1863 &lt;p&gt;Some key packages used by Freedombox are
1864 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1865 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1866 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1867 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1868 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1869 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1870 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1871 are plans to integrate more packages into the setup. User
1872 documentation is maintained on the Debian wiki. Please
1873 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1874 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1875
1876 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1877 setup, run this on a Debian machine using a user with sudo rights to
1878 become root:&lt;/p&gt;
1879
1880 &lt;p&gt;&lt;pre&gt;
1881 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1882 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1883 u-boot-tools
1884 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1885 freedom-maker
1886 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1887 &lt;/pre&gt;&lt;/p&gt;
1888
1889 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1890 devices. See the README in the freedom-maker git repo for more
1891 details on the build. If you do not want all three images, trim the
1892 make line. Note that the virtualbox-image target is not really
1893 virtualbox specific. It create a x86 image usable in kvm, qemu,
1894 vmware and any other x86 virtual machine environment. You might need
1895 the version of vmdebootstrap in Jessie to get the build working, as it
1896 include fixes for a race condition with kpartx.&lt;/p&gt;
1897
1898 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1899 method, boot a Debian Wheezy ISO and use this boot argument to load
1900 the preseed values:&lt;/p&gt;
1901
1902 &lt;p&gt;&lt;pre&gt;
1903 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;
1904 &lt;/pre&gt;&lt;/p&gt;
1905
1906 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1907 it still work.&lt;/p&gt;
1908
1909 &lt;p&gt;If you wonder how to help, one task you could look at is using
1910 systemd as the boot system. It will become the default for Linux in
1911 Jessie, so we need to make sure it is usable on the Freedombox. I did
1912 a simple test a few weeks ago, and noticed dnsmasq failed to start
1913 during boot when using systemd. I suspect there are other problems
1914 too. :) To detect problems, there is a test suite included, which can
1915 be run from the plinth web interface.&lt;/p&gt;
1916
1917 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1918 us get the new release published. :) Please join us on
1919 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1920 irc.debian.org)&lt;/a&gt; and
1921 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1922 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1923 </description>
1924 </item>
1925
1926 <item>
1927 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1928 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1929 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1930 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1931 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1932 solution for use at home. My requirements are simple, it must be
1933 cheap and locally encrypted (in other words, I keep the encryption
1934 keys, the storage provider do not have access to my private files).
1935 One idea me and my friends had many years ago, before the cloud
1936 storage providers showed up, was to use Google mail as storage,
1937 writing a Linux block device storing blocks as emails in the mail
1938 service provided by Google, and thus get heaps of free space. On top
1939 of this one can add encryption, RAID and volume management to have
1940 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1941 I never found time to implement such system. But the last few weeks I
1942 have looked at a system called
1943 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1944 mounted network backed file system with the features I need.&lt;/p&gt;
1945
1946 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1947 handling several different storage providers, any with Amazon S3,
1948 Google Drive or OpenStack API. There are heaps of such storage
1949 providers. S3QL can also use a local directory as storage, which
1950 combined with sshfs allow for file storage on any ssh server. S3QL
1951 include support for encryption, compression, de-duplication, snapshots
1952 and immutable file systems, allowing me to mount the remote storage as
1953 a local mount point, look at and use the files as if they were local,
1954 while the content is stored in the cloud as well. This allow me to
1955 have a backup that should survive fire. The file system can not be
1956 shared between several machines at the same time, as only one can
1957 mount it at the time, but any machine with the encryption key and
1958 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1959
1960 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1961 package is included already. So to get started, run &lt;tt&gt;apt-get
1962 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1963 Greenqloud, after reading their nice recipe on
1964 &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
1965 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1966 in Iceland more than those in USA when it come to keeping my personal
1967 data safe and private, and thus would rather spend money on a company
1968 in Iceland. Another nice recipe is available from the article
1969 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1970 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1971 Admin magazine. When the provider is picked, figure out how to get
1972 the API key needed to connect to the storage API. With Greencloud,
1973 the key did not show up until I had added payment details to my
1974 account.&lt;/p&gt;
1975
1976 &lt;p&gt;Armed with the API access details, it is time to create the file
1977 system. First, create a new bucket in the cloud. This bucket is the
1978 file system storage area. I picked a bucket name reflecting the
1979 machine that was going to store data there, but any name will do.
1980 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1981 the API login and password, and a locally created password. Store it
1982 all in ~root/.s3ql/authinfo2 like this:
1983
1984 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1985 [s3c]
1986 storage-url: s3c://s.greenqloud.com:443/bucket-name
1987 backend-login: API-login
1988 backend-password: API-password
1989 fs-passphrase: local-password
1990 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1991
1992 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1993 but any sensible way to create a fairly random password should do it.
1994 Armed with these details, it is now time to run mkfs, entering the API
1995 details and password to create it:&lt;/p&gt;
1996
1997 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1998 # mkdir -m 700 /var/lib/s3ql-cache
1999 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2000 --ssl s3c://s.greenqloud.com:443/bucket-name
2001 Enter backend login:
2002 Enter backend password:
2003 Before using S3QL, make sure to read the user&#39;s guide, especially
2004 the &#39;Important Rules to Avoid Loosing Data&#39; section.
2005 Enter encryption password:
2006 Confirm encryption password:
2007 Generating random encryption key...
2008 Creating metadata tables...
2009 Dumping metadata...
2010 ..objects..
2011 ..blocks..
2012 ..inodes..
2013 ..inode_blocks..
2014 ..symlink_targets..
2015 ..names..
2016 ..contents..
2017 ..ext_attributes..
2018 Compressing and uploading metadata...
2019 Wrote 0.00 MB of compressed metadata.
2020 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2021
2022 &lt;p&gt;The next step is mounting the file system to make the storage available.
2023
2024 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2025 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2026 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2027 Using 4 upload threads.
2028 Downloading and decompressing metadata...
2029 Reading metadata...
2030 ..objects..
2031 ..blocks..
2032 ..inodes..
2033 ..inode_blocks..
2034 ..symlink_targets..
2035 ..names..
2036 ..contents..
2037 ..ext_attributes..
2038 Mounting filesystem...
2039 # df -h /s3ql
2040 Filesystem Size Used Avail Use% Mounted on
2041 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
2042 #
2043 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2044
2045 &lt;p&gt;The file system is now ready for use. I use rsync to store my
2046 backups in it, and as the metadata used by rsync is downloaded at
2047 mount time, no network traffic (and storage cost) is triggered by
2048 running rsync. To unmount, one should not use the normal umount
2049 command, as this will not flush the cache to the cloud storage, but
2050 instead running the umount.s3ql command like this:
2051
2052 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2053 # umount.s3ql /s3ql
2054 #
2055 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2056
2057 &lt;p&gt;There is a fsck command available to check the file system and
2058 correct any problems detected. This can be used if the local server
2059 crashes while the file system is mounted, to reset the &quot;already
2060 mounted&quot; flag. This is what it look like when processing a working
2061 file system:&lt;/p&gt;
2062
2063 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2064 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
2065 Using cached metadata.
2066 File system seems clean, checking anyway.
2067 Checking DB integrity...
2068 Creating temporary extra indices...
2069 Checking lost+found...
2070 Checking cached objects...
2071 Checking names (refcounts)...
2072 Checking contents (names)...
2073 Checking contents (inodes)...
2074 Checking contents (parent inodes)...
2075 Checking objects (reference counts)...
2076 Checking objects (backend)...
2077 ..processed 5000 objects so far..
2078 ..processed 10000 objects so far..
2079 ..processed 15000 objects so far..
2080 Checking objects (sizes)...
2081 Checking blocks (referenced objects)...
2082 Checking blocks (refcounts)...
2083 Checking inode-block mapping (blocks)...
2084 Checking inode-block mapping (inodes)...
2085 Checking inodes (refcounts)...
2086 Checking inodes (sizes)...
2087 Checking extended attributes (names)...
2088 Checking extended attributes (inodes)...
2089 Checking symlinks (inodes)...
2090 Checking directory reachability...
2091 Checking unix conventions...
2092 Checking referential integrity...
2093 Dropping temporary indices...
2094 Backing up old metadata...
2095 Dumping metadata...
2096 ..objects..
2097 ..blocks..
2098 ..inodes..
2099 ..inode_blocks..
2100 ..symlink_targets..
2101 ..names..
2102 ..contents..
2103 ..ext_attributes..
2104 Compressing and uploading metadata...
2105 Wrote 0.89 MB of compressed metadata.
2106 #
2107 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2108
2109 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2110 quick, about the same speed as local file access. Uploading large
2111 amount of data is to me limited by the bandwidth out of and into my
2112 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2113 which is very close to my upload speed, and downloading the same
2114 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2115 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2116 network, not the file system code. I do not know what a good cache
2117 size would be, but suspect that the cache should e larger than your
2118 working set.&lt;/p&gt;
2119
2120 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2121 time. If another machine try, it is told that the file system is
2122 busy:&lt;/p&gt;
2123
2124 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2125 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2126 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2127 Using 8 upload threads.
2128 Backend reports that fs is still mounted elsewhere, aborting.
2129 #
2130 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2131
2132 &lt;p&gt;The file content is uploaded when the cache is full, while the
2133 metadata is uploaded once every 24 hour by default. To ensure the
2134 file system content is flushed to the cloud, one can either umount the
2135 file system, or ask S3QL to flush the cache and metadata using
2136 s3qlctrl:
2137
2138 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2139 # s3qlctrl upload-meta /s3ql
2140 # s3qlctrl flushcache /s3ql
2141 #
2142 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2143
2144 &lt;p&gt;If you are curious about how much space your data uses in the
2145 cloud, and how much compression and deduplication cut down on the
2146 storage usage, you can use s3qlstat on the mounted file system to get
2147 a report:&lt;/p&gt;
2148
2149 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2150 # s3qlstat /s3ql
2151 Directory entries: 9141
2152 Inodes: 9143
2153 Data blocks: 8851
2154 Total data size: 22049.38 MB
2155 After de-duplication: 21955.46 MB (99.57% of total)
2156 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2157 Database size: 2.39 MB (uncompressed)
2158 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2159 #
2160 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2161
2162 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2163 storage. I did not try to locate them all, but am aware of at least
2164 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2165 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2166 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2167 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2168 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2169 accept payment in Bitcoin. Pick one that suit your need. Some of
2170 them provide several GiB of free storage, but the prize models are
2171 quite different and you will have to figure out what suits you
2172 best.&lt;/p&gt;
2173
2174 &lt;p&gt;While researching this blog post, I had a look at research papers
2175 and posters discussing the S3QL file system. There are several, which
2176 told me that the file system is getting a critical check by the
2177 science community and increased my confidence in using it. One nice
2178 poster is titled
2179 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2180 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2181 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2182 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2183 and Pamela Smith. Please have a look.&lt;/p&gt;
2184
2185 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2186 check out the mounted S3QL file system to see if it would be usable as
2187 a home directory (in other word, that it provided POSIX semantics when
2188 it come to locking and umask handling etc). Running
2189 &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
2190 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2191 no error was found. So the file system can be used for home
2192 directories, if one chooses to do so.&lt;/p&gt;
2193
2194 &lt;p&gt;If you do not want a locally file system, and want something that
2195 work without the Linux fuse file system, I would like to mention the
2196 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2197 provide locally encrypted backup using a command line client. It have
2198 a nicer access control system, where one can split out read and write
2199 access, allowing some systems to write to the backup and others to
2200 only read from it.&lt;/p&gt;
2201
2202 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2203 activities, please send Bitcoin donations to my address
2204 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2205 </description>
2206 </item>
2207
2208 <item>
2209 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2210 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2211 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2212 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2213 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2214 project&lt;/a&gt; is working on providing the software and hardware for
2215 making it easy for non-technical people to host their data and
2216 communication at home, and being able to communicate with their
2217 friends and family encrypted and away from prying eyes. It has been
2218 going on for a while, and is slowly progressing towards a new test
2219 release (0.2).&lt;/p&gt;
2220
2221 &lt;p&gt;And what day could be better than the Pi day to announce that the
2222 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2223 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2224 system), and can also be installed using a Debian installer preseed
2225 file. The Debian based Freedombox is now based on Debian Jessie,
2226 where most of the needed packages used are already present. Only one,
2227 the freedombox-setup package, is missing. To try to build your own
2228 boot image to test the current status, fetch the freedom-maker scripts
2229 and build using
2230 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2231 with a user with sudo access to become root:
2232
2233 &lt;pre&gt;
2234 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2235 freedom-maker
2236 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2237 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2238 u-boot-tools
2239 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2240 &lt;/pre&gt;
2241
2242 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2243 devices. See the README for more details on the build. If you do not
2244 want all three images, trim the make line. But note that thanks to &lt;a
2245 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2246 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2247 kpartx call.&lt;/p&gt;
2248
2249 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2250 method, boot a Debian Wheezy ISO and use this boot argument to load
2251 the preseed values:&lt;/p&gt;
2252
2253 &lt;pre&gt;
2254 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;
2255 &lt;/pre&gt;
2256
2257 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2258 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2259 currently hang while setting up APT sources. Killing the
2260 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2261 installation will get the installation going. This affect all
2262 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2263
2264 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2265 us get the new release published. :) Please join us on
2266 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2267 irc.debian.org)&lt;/a&gt; and
2268 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2269 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2270 </description>
2271 </item>
2272
2273 <item>
2274 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2275 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2276 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2277 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2278 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2279 innetgr tools, because I needed them in
2280 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2281 ng-utils, and it has served me well. I placed the project under the
2282 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2283 repository. But many years ago, the CVS repository was dropped (lost,
2284 not migrated to new hardware, not sure), and the project have lacked a
2285 proper home since then.&lt;/p&gt;
2286
2287 &lt;p&gt;Last summer, I had a look at the package and made a new release
2288 fixing a irritating crash bug, but was unable to store the changes in
2289 a proper source control system. I applied for a project on
2290 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2291 to follow up on it. Until today. :)&lt;/p&gt;
2292
2293 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2294 now have a new home, and a git repository with the highlight of the
2295 history of the project. I published all release tarballs and imported
2296 them into the git repository. As the project is really stable and not
2297 expected to gain new features any time soon, I decided to make a new
2298 release and call it 1.0. Visit the new project home on
2299 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2300 if you want to check it out. The new version is also uploaded into
2301 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2302 </description>
2303 </item>
2304
2305 <item>
2306 <title>Testing sysvinit from experimental in Debian Hurd</title>
2307 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2308 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2309 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2310 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2311 their changes into sysvinit, to allow them to use the normal sysvinit
2312 boot system instead of their old one. This follow up on the
2313 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2314 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2315 get Debian on Hurd working more like Debian on Linux. To get started,
2316 I downloaded a prebuilt hard disk image from
2317 &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;,
2318 and started it using virt-manager.&lt;/p&gt;
2319
2320 &lt;p&gt;The first think I had to do after logging in (root without any
2321 password) was to get the network operational. I followed
2322 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2323 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2324 commands as root to get the machine to accept a IP address from the
2325 kvm internal DHCP server:&lt;/p&gt;
2326
2327 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2328 settrans -fgap /dev/netdde /hurd/netdde
2329 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2330 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2331 dhclient /dev/eth0
2332 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2333
2334 &lt;p&gt;After this, the machine had internet connectivity, and I could
2335 upgrade it and install the sysvinit packages from experimental and
2336 enable it as the default boot system in Hurd.&lt;/p&gt;
2337
2338 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2339 running on the machine it for ssh login to work a password need to be
2340 set. Also, note that a bug somewhere in openssh on Hurd block
2341 compression from working. Remember to turn that off on the client
2342 side.&lt;/p&gt;
2343
2344 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2345 stuff:&lt;/p&gt;
2346
2347 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2348 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2349 deb http://http.debian.net/debian/ experimental main
2350 EOF
2351 apt-get update
2352 apt-get dist-upgrade
2353 apt-get install -t experimental initscripts sysv-rc sysvinit \
2354 sysvinit-core sysvinit-utils
2355 update-alternatives --config runsystem
2356 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2357
2358 &lt;p&gt;To reboot after switching boot system, you have to use
2359 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2360 yet a sysvinit process able to receive the signals from the normal
2361 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2362 upgrading every package and rebooting, the network come up with DHCP
2363 after boot as it should, and the settrans/pkill hack mentioned at the
2364 start is no longer needed. But for some strange reason, there are no
2365 longer any login prompt in the virtual console, so I logged in using
2366 ssh instead.
2367
2368 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2369 fail some times. No idea what the cause is, but hope the Hurd porters
2370 figure it out. At least Justus said on IRC (#debian-hurd on
2371 irc.debian.org) that they are aware of the problem. A way to reduce
2372 the impact is to upgrade to the Hurd packages built by Justus by
2373 adding this repository to the machine:&lt;/p&gt;
2374
2375 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2376 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2377 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2378 EOF
2379 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2380
2381 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2382 http://ftp.debian-ports.org/debian, because some of the packages in
2383 unstable do not yet include the required patches that are lingering in
2384 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2385
2386 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2387 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2388 i emacs - GNU Emacs editor (metapackage)
2389 i gdb - GNU Debugger
2390 i hurd-recommended - Miscellaneous translators
2391 i isc-dhcp-client - ISC DHCP client
2392 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2393 i libc-bin - Embedded GNU C Library: Binaries
2394 i libc-dev-bin - Embedded GNU C Library: Development binaries
2395 i libc0.3 - Embedded GNU C Library: Shared libraries
2396 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2397 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2398 i multiarch-support - Transitional package to ensure multiarch compatibilit
2399 i A x11-common - X Window System (X.Org) infrastructure
2400 i xorg - X.Org X Window System
2401 i A xserver-xorg - X.Org X server
2402 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2403 #
2404 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2405
2406 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2407 X.org did not work out of the box and I never took the time to follow
2408 the porters instructions to fix it. This time I was interested in the
2409 command line stuff.&lt;p&gt;
2410 </description>
2411 </item>
2412
2413 <item>
2414 <title>New chrpath release 0.16</title>
2415 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2416 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2417 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2418 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2419 find problems in C, C++ and Java code using static source code
2420 analysis. It can detect a lot of different problems, and is very
2421 useful to find memory and locking bugs in the error handling part of
2422 the source. The company behind it provide
2423 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2424 a community service&lt;/a&gt;, and many hundred free software projects are
2425 already checked. A few days ago I decided to have a closer look at
2426 the Coverity system, and discovered that the
2427 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2428 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2429 projects I am involved with was already registered. But these are
2430 fairly big, and I would also like to have a small and easy project to
2431 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2432 checking of the chrpath project&lt;/a&gt;. It was
2433 added to the checker and discovered seven potential defects. Six of
2434 these were real, mostly resource &quot;leak&quot; when the program detected an
2435 error. Nothing serious, as the resources would be released a fraction
2436 of a second later when the program exited because of the error, but it
2437 is nice to do it right in case the source of the program some time in
2438 the future end up in a library. Having fixed all defects and added
2439 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2440 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2441 publish a new release. These are the release notes:&lt;/p&gt;
2442
2443 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2444
2445 &lt;ul&gt;
2446
2447 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2448 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2449 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2450
2451 &lt;/ul&gt;
2452
2453 &lt;p&gt;You can
2454 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2455 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2456 project if something is wrong with the new release. The test suite
2457 did not discover any old errors, so if you find a new one, please also
2458 include a test suite check.&lt;/p&gt;
2459 </description>
2460 </item>
2461
2462 <item>
2463 <title>New chrpath release 0.15</title>
2464 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2465 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2466 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2467 <description>&lt;p&gt;After many years break from the package and a vain hope that
2468 development would be continued by someone else, I finally pulled my
2469 acts together this morning and wrapped up a new release of chrpath,
2470 the command line tool to modify the rpath and runpath of already
2471 compiled ELF programs. The update was triggered by the persistence of
2472 Isha Vishnoi at IBM, which needed a new config.guess file to get
2473 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2474 is working on. I checked the
2475 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2476 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2477 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2478 packages for interesting patches (failed to find the source from
2479 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2480 These are the release notes:&lt;/p&gt;
2481
2482 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2483
2484 &lt;ul&gt;
2485
2486 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2487 with newer architectures. Thanks to isha vishnoi for the heads
2488 up.&lt;/li&gt;
2489
2490 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2491
2492 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2493 Matthias Klose.&lt;/li&gt;
2494
2495 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2496 Petr Machata found in Fedora.&lt;/li&gt;
2497
2498 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2499 .dynamic is a NULL terminated string. Based on patch found in
2500 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2501
2502 &lt;/ul&gt;
2503
2504 &lt;p&gt;You can
2505 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2506 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2507 project if something is wrong with the new release. The test suite
2508 did not discover any old errors, so if you find a new one, please also
2509 include a testsuite check.&lt;/p&gt;
2510 </description>
2511 </item>
2512
2513 <item>
2514 <title>Debian init.d boot script example for rsyslog</title>
2515 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2516 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2517 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2518 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2519 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2520 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2521 init.d scripts at all. Here is an example init.d script, ie a rewrite
2522 of /etc/init.d/rsyslog:&lt;/p&gt;
2523
2524 &lt;p&gt;&lt;pre&gt;
2525 #!/lib/init/init-d-script
2526 ### BEGIN INIT INFO
2527 # Provides: rsyslog
2528 # Required-Start: $remote_fs $time
2529 # Required-Stop: umountnfs $time
2530 # X-Stop-After: sendsigs
2531 # Default-Start: 2 3 4 5
2532 # Default-Stop: 0 1 6
2533 # Short-Description: enhanced syslogd
2534 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2535 # It is quite compatible to stock sysklogd and can be
2536 # used as a drop-in replacement.
2537 ### END INIT INFO
2538 DESC=&quot;enhanced syslogd&quot;
2539 DAEMON=/usr/sbin/rsyslogd
2540 &lt;/pre&gt;&lt;/p&gt;
2541
2542 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2543 script was 137 lines, and the above is just 15 lines, most of it meta
2544 info/comments.&lt;/p&gt;
2545
2546 &lt;p&gt;How to do this, you ask? Well, one create a new script
2547 /lib/init/init-d-script looking something like this:
2548
2549 &lt;p&gt;&lt;pre&gt;
2550 #!/bin/sh
2551
2552 # Define LSB log_* functions.
2553 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2554 # and status_of_proc is working.
2555 . /lib/lsb/init-functions
2556
2557 #
2558 # Function that starts the daemon/service
2559
2560 #
2561 do_start()
2562 {
2563 # Return
2564 # 0 if daemon has been started
2565 # 1 if daemon was already running
2566 # 2 if daemon could not be started
2567 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2568 || return 1
2569 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2570 $DAEMON_ARGS \
2571 || return 2
2572 # Add code here, if necessary, that waits for the process to be ready
2573 # to handle requests from services started subsequently which depend
2574 # on this one. As a last resort, sleep for some time.
2575 }
2576
2577 #
2578 # Function that stops the daemon/service
2579 #
2580 do_stop()
2581 {
2582 # Return
2583 # 0 if daemon has been stopped
2584 # 1 if daemon was already stopped
2585 # 2 if daemon could not be stopped
2586 # other if a failure occurred
2587 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2588 RETVAL=&quot;$?&quot;
2589 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2590 # Wait for children to finish too if this is a daemon that forks
2591 # and if the daemon is only ever run from this initscript.
2592 # If the above conditions are not satisfied then add some other code
2593 # that waits for the process to drop all resources that could be
2594 # needed by services started subsequently. A last resort is to
2595 # sleep for some time.
2596 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2597 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2598 # Many daemons don&#39;t delete their pidfiles when they exit.
2599 rm -f $PIDFILE
2600 return &quot;$RETVAL&quot;
2601 }
2602
2603 #
2604 # Function that sends a SIGHUP to the daemon/service
2605 #
2606 do_reload() {
2607 #
2608 # If the daemon can reload its configuration without
2609 # restarting (for example, when it is sent a SIGHUP),
2610 # then implement that here.
2611 #
2612 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2613 return 0
2614 }
2615
2616 SCRIPTNAME=$1
2617 scriptbasename=&quot;$(basename $1)&quot;
2618 echo &quot;SN: $scriptbasename&quot;
2619 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2620 script=&quot;$1&quot;
2621 shift
2622 . $script
2623 else
2624 exit 0
2625 fi
2626
2627 NAME=$(basename $DAEMON)
2628 PIDFILE=/var/run/$NAME.pid
2629
2630 # Exit if the package is not installed
2631 #[ -x &quot;$DAEMON&quot; ] || exit 0
2632
2633 # Read configuration variable file if it is present
2634 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2635
2636 # Load the VERBOSE setting and other rcS variables
2637 . /lib/init/vars.sh
2638
2639 case &quot;$1&quot; in
2640 start)
2641 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2642 do_start
2643 case &quot;$?&quot; in
2644 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2645 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2646 esac
2647 ;;
2648 stop)
2649 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2650 do_stop
2651 case &quot;$?&quot; in
2652 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2653 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2654 esac
2655 ;;
2656 status)
2657 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2658 ;;
2659 #reload|force-reload)
2660 #
2661 # If do_reload() is not implemented then leave this commented out
2662 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2663 #
2664 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2665 #do_reload
2666 #log_end_msg $?
2667 #;;
2668 restart|force-reload)
2669 #
2670 # If the &quot;reload&quot; option is implemented then remove the
2671 # &#39;force-reload&#39; alias
2672 #
2673 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2674 do_stop
2675 case &quot;$?&quot; in
2676 0|1)
2677 do_start
2678 case &quot;$?&quot; in
2679 0) log_end_msg 0 ;;
2680 1) log_end_msg 1 ;; # Old process is still running
2681 *) log_end_msg 1 ;; # Failed to start
2682 esac
2683 ;;
2684 *)
2685 # Failed to stop
2686 log_end_msg 1
2687 ;;
2688 esac
2689 ;;
2690 *)
2691 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2692 exit 3
2693 ;;
2694 esac
2695
2696 :
2697 &lt;/pre&gt;&lt;/p&gt;
2698
2699 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2700 lot. I did not really polish the approach, so it might not always
2701 work out of the box, but you get the idea. I did not try very hard to
2702 optimize it nor make it more robust either.&lt;/p&gt;
2703
2704 &lt;p&gt;A better argument for switching init system in Debian than reducing
2705 the size of init scripts (which is a good thing to do anyway), is to
2706 get boot system that is able to handle the kernel events sensibly and
2707 robustly, and do not depend on the boot to run sequentially. The boot
2708 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2709 </description>
2710 </item>
2711
2712 <item>
2713 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2714 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2715 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2716 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2717 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2718 remote display access is the preferred solution with oVirt and RedHat
2719 Enterprise Virtualization, and I was sad to discover the other day
2720 that the browser plugin needed to use these systems seamlessly was
2721 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2722 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2723 2013-04-01, so I decided to wrap up a package based on the great work
2724 from Cajus Pollmeier and put it in a collab-maint maintained git
2725 repository to get a package I could use. I would very much like
2726 others to help me maintain the package (or just take over, I do not
2727 mind), but as no-one had volunteered so far, I just uploaded it to
2728 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2729
2730 &lt;p&gt;The source is now available from
2731 &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;
2732 </description>
2733 </item>
2734
2735 <item>
2736 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2737 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2738 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2739 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2740 <description>&lt;p&gt;The
2741 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2742 program is a a very nice system to create virtual machine images. It
2743 create a image file, add a partition table, mount it and run
2744 debootstrap in the mounted directory to create a Debian system on a
2745 stick. Yesterday, I decided to try to teach it how to make images for
2746 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2747 of a plan to simplify the build system for
2748 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2749 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2750 the virtualbox images, but its current build system made multistrap
2751 based system for Dreamplug images, and it is lacking support for
2752 Raspberry Pi.&lt;/p&gt;
2753
2754 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2755 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2756 code and adjusted it to be able to build armel images on my amd64
2757 Debian laptop. I ended up giving vmdebootstrap five new options,
2758 allowing me to replicate the image creation process I use to make
2759 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2760 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2761 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2762 call debootstrap with --foreign and to copy the handler into the
2763 generated chroot before running the second stage. This allow
2764 vmdebootstrap to create armel images on an amd64 host. Next I added
2765 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2766 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2767 given file system type, allowing me to create an image with a vfat
2768 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2769 variant&lt;/tt&gt; option to allow me to create smaller images without the
2770 Debian base system packages installed. Finally, I added an option
2771 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2772 as a boot loader. It is not needed on the Raspberry Pi and probably
2773 most other non-x86 architectures. The changes were accepted by the
2774 upstream author of vmdebootstrap yesterday and today, and is now
2775 available from
2776 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2777 upstream project page&lt;/a&gt;.&lt;/p&gt;
2778
2779 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2780 create a small script (the customize script) to add the non-free
2781 binary blob needed to boot the Raspberry Pi and the APT source
2782 list:&lt;/p&gt;
2783
2784 &lt;p&gt;&lt;pre&gt;
2785 #!/bin/sh
2786 set -e # Exit on first error
2787 rootdir=&quot;$1&quot;
2788 cd &quot;$rootdir&quot;
2789 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2790 deb http://http.debian.net/debian/ jessie main contrib non-free
2791 EOF
2792 # Install non-free binary blob needed to boot Raspberry Pi. This
2793 # install a kernel somewhere too.
2794 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2795 -O $rootdir/usr/bin/rpi-update
2796 chmod a+x $rootdir/usr/bin/rpi-update
2797 mkdir -p $rootdir/lib/modules
2798 touch $rootdir/boot/start.elf
2799 chroot $rootdir rpi-update
2800 &lt;/pre&gt;&lt;/p&gt;
2801
2802 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2803 to build the image:&lt;/p&gt;
2804
2805 &lt;pre&gt;
2806 sudo ./vmdebootstrap \
2807 --variant minbase \
2808 --arch armel \
2809 --distribution jessie \
2810 --mirror http://http.debian.net/debian \
2811 --image test.img \
2812 --size 600M \
2813 --bootsize 64M \
2814 --boottype vfat \
2815 --log-level debug \
2816 --verbose \
2817 --no-kernel \
2818 --no-extlinux \
2819 --root-password raspberry \
2820 --hostname raspberrypi \
2821 --foreign /usr/bin/qemu-arm-static \
2822 --customize `pwd`/customize \
2823 --package netbase \
2824 --package git-core \
2825 --package binutils \
2826 --package ca-certificates \
2827 --package wget \
2828 --package kmod
2829 &lt;/pre&gt;&lt;/p&gt;
2830
2831 &lt;p&gt;The list of packages being installed are the ones needed by
2832 rpi-update to make the image bootable on the Raspberry Pi, with the
2833 exception of netbase, which is needed by debootstrap to find
2834 /etc/hosts with the minbase variant. I really wish there was a way to
2835 set up an Raspberry Pi using only packages in the Debian archive, but
2836 that is not possible as far as I know, because it boots from the GPU
2837 using a non-free binary blob.&lt;/p&gt;
2838
2839 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2840 probably a few others installed. I have not checked the complete
2841 build dependency list.&lt;/p&gt;
2842
2843 &lt;p&gt;The resulting image will not use the hardware floating point unit
2844 on the Raspberry PI, because the armel architecture in Debian is not
2845 optimized for that use. So the images created will be a bit slower
2846 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2847 </description>
2848 </item>
2849
2850 <item>
2851 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2852 <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>
2853 <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>
2854 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2855 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2856 wider attention. I recommend signing and donating to each one of
2857 these. :)&lt;/p&gt;
2858
2859 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2860 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2861 Women program which is a Google Summer of Code like initiative to get
2862 more women involved in free software. One debian sponsor has offered
2863 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2864 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2865 hope you will to. :)&lt;/p&gt;
2866
2867 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2868 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2869 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2870 take place these days, and their need to fund the work. I&#39;ve already
2871 donated. Are you next?&lt;/p&gt;
2872
2873 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2874 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2875 statement under the heading
2876 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2877 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2878 Norwegian government. So far 499 signatures. I hope you will sign it
2879 too.&lt;/p&gt;
2880 </description>
2881 </item>
2882
2883 <item>
2884 <title>Videos about the Freedombox project - for inspiration and learning</title>
2885 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2886 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2887 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2888 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2889 project&lt;/a&gt; have been going on for a while, and have presented the
2890 vision, ideas and solution several places. Here is a little
2891 collection of videos of talks and presentation of the project.&lt;/p&gt;
2892
2893 &lt;ul&gt;
2894
2895 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2896 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2897
2898 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2899 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2900
2901 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2902 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2903 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2904 (Youtube)&lt;/li&gt;
2905
2906 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2907 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2908
2909 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2910 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2911
2912 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2913 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2914 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2915
2916 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2917 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2918 (Youtube)&lt;/li&gt;
2919
2920 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2921 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2922
2923 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2924 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2925
2926 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2927 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2928 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2929
2930 &lt;/ul&gt;
2931
2932 &lt;p&gt;A larger list is available from
2933 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2934 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2935
2936 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2937 Jessie is coming along quite well, and soon both Owncloud and using
2938 Tor should be available for testers of the Freedombox solution. :) In
2939 a few weeks I hope everything needed to test it is included in Debian.
2940 The withsqlite package is already in Debian, and the plinth package is
2941 pending in NEW. The third and vital part of that puzzle is the
2942 metapackage/setup framework, which is still pending an upload. Join
2943 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2944 (#freedombox on irc.debian.org)&lt;/a&gt; and
2945 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2946 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2947 </description>
2948 </item>
2949
2950 <item>
2951 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2952 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2953 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2954 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2955 <description>&lt;p&gt;I was introduced to the
2956 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2957 in 2010, when Eben Moglen presented his vision about serving the need
2958 of non-technical people to keep their personal information private and
2959 within the legal protection of their own homes. The idea is to give
2960 people back the power over their network and machines, and return
2961 Internet back to its intended peer-to-peer architecture. Instead of
2962 depending on a central service, the Freedombox will give everyone
2963 control over their own basic infrastructure.&lt;/p&gt;
2964
2965 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2966 taken priority. But this summers nasty news about the misuse of trust
2967 and privilege exercised by the &quot;western&quot; intelligence gathering
2968 communities increased my eagerness to contribute to a point where I
2969 actually started working on the project a while back.&lt;/p&gt;
2970
2971 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2972 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2973 create a simple and cheap Debian based appliance that anyone can hook
2974 up in their home and get access to secure and private services and
2975 communication. The initial deployment platform have been the
2976 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2977 which is a piece of hardware I do not own. So to be able to test what
2978 the current Freedombox setup look like, I had to come up with a way to install
2979 it on some hardware I do have access to. I have rewritten the
2980 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2981 image build framework to use .deb packages instead of only copying
2982 setup into the boot images, and thanks to this rewrite I am able to
2983 set up any machine supported by Debian Wheezy as a Freedombox, using
2984 the previously mentioned deb (and a few support debs for packages
2985 missing in Debian).&lt;/p&gt;
2986
2987 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2988 scripts
2989 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2990 and a administrative web interface
2991 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2992 withsqlite), as well as a privacy enhancing proxy based on
2993 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2994 (freedombox-privoxy). There is also a web/javascript based XMPP
2995 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2996 trying (unsuccessfully so far) to talk to the XMPP server
2997 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2998 web interface is pluggable, and the goal is to use it to enable OpenID
2999 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3000 this is really working yet, see
3001 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
3002 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
3003 on github at the moment. The HTTP proxy is operational out of the
3004 box, and the admin web interface can be used to add/remove plinth
3005 users. I&#39;ve not been able to do anything else with it so far, but
3006 know there are several branches spread around github and other places
3007 with lots of half baked features.&lt;/p&gt;
3008
3009 &lt;p&gt;Anyway, if you want to have a look at the current state, the
3010 following recipes should work to give you a test machine to poke
3011 at.&lt;/p&gt;
3012
3013 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
3014
3015 &lt;ol&gt;
3016
3017 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
3018 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
3019 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
3020 to the Debian installer:&lt;p&gt;
3021 &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;
3022
3023 &lt;li&gt;Answer the few language/region/password questions and pick disk to
3024 install on.&lt;/li&gt;
3025
3026 &lt;li&gt;When the installation is finished and the machine have rebooted a
3027 few times, your Freedombox is ready for testing.&lt;/li&gt;
3028
3029 &lt;/ol&gt;
3030
3031 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
3032
3033 &lt;ol&gt;
3034
3035 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
3036 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
3037 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
3038 &lt;pre&gt;
3039 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
3040 &lt;/pre&gt;&lt;/li&gt;
3041 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
3042 &lt;pre&gt;
3043 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3044 apt-key add -
3045 apt-get update
3046 apt-get install freedombox-setup
3047 /usr/lib/freedombox/setup
3048 &lt;/pre&gt;&lt;/li&gt;
3049 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
3050
3051 &lt;/ol&gt;
3052
3053 &lt;p&gt;You can test it on other architectures too, but because the
3054 freedombox-privoxy package is binary, it will only work as intended on
3055 the architectures where I have had time to build the binary and put it
3056 in my APT repository. But do not let this stop you. It is only a
3057 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
3058
3059 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
3060 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
3061 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
3062 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
3063
3064 &lt;p&gt;Please let me know if this works for you, or if you have any
3065 problems. We gather on the IRC channel
3066 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
3067 irc.debian.org and the
3068 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
3069 mailing list&lt;/a&gt;.&lt;/p&gt;
3070
3071 &lt;p&gt;Once you get your freedombox operational, you can visit
3072 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
3073 welcome screen (dead end - do not be surprised if you are unable to
3074 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
3075 to look at the rest of plinth. The default user is &#39;admin&#39; and the
3076 default password is &#39;secret&#39;.&lt;/p&gt;
3077 </description>
3078 </item>
3079
3080 <item>
3081 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
3082 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3083 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3084 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3085 <description>&lt;p&gt;Earlier, I reported about
3086 &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
3087 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3088 told by IBM that the original disk should be thrown away. And as
3089 there no longer was a problem if I bricked the firmware, I decided
3090 today to try to install Intel firmware to replace the Lenovo firmware
3091 currently on the disk.&lt;/p&gt;
3092
3093 &lt;p&gt;I searched the Intel site for firmware, and found
3094 &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;
3095 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3096 according to the site should contain the latest firmware for SSD
3097 disks. I inserted the broken disk in one of my spare laptops and
3098 booted the ISO from a USB stick. The disk was recognized, but the
3099 program claimed the newest firmware already were installed and refused
3100 to insert any Intel firmware. So no change, and the disk is still
3101 unable to handle write load. :( I guess the only way to get them
3102 working would be if Lenovo releases new firmware. No idea how likely
3103 that is. Anyway, just blogging about this test for completeness. I
3104 got a working Samsung disk, and see no point in spending more time on
3105 the broken disks.&lt;/p&gt;
3106 </description>
3107 </item>
3108
3109 <item>
3110 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3111 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3112 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3113 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3114 <description>&lt;p&gt;Today I switched to
3115 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3116 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3117 my new Thinkpad X230, which was delivered with an
3118 &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
3119 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3120 sustained writes. My hardware supplier have been very forthcoming in
3121 trying to find a solution, and after first trying with another
3122 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3123 disk instead to fix it once and for all. The Samsung disk survived
3124 the installation of Debian with encrypted disks (filling the disk with
3125 random data during installation killed the first two), and I thus
3126 decided to trust it with my data. I have installed it as a Debian Edu
3127 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3128 server at home using Kerberos and LDAP, and will use it as my work
3129 station from now on.&lt;/p&gt;
3130
3131 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3132 Debian Wheezy default installation need to be tuned a bit to increase
3133 performance and increase life time of the disk. The Linux kernel and
3134 user space applications do not yet adjust automatically to such
3135 environment. To make it easier for my self, I created a draft Debian
3136 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3137 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3138 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3139 is set up to adjust the setup of the machine by just installing the
3140 package. If there is any non-SSD disk in the machine, the package
3141 will refuse to install, as I did not try to write any logic to sort
3142 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3143
3144 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3145 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3146 where I set up the machine with one large encrypted partition (in
3147 addition to /boot), put LVM on top of this and set up partitions on
3148 top of this again. See the README file in the package source for the
3149 references I used to pick the settings. At the moment these
3150 parameters are tuned:&lt;/p&gt;
3151
3152 &lt;ul&gt;
3153
3154 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3155 (adding discard to /etc/crypttab)&lt;/li&gt;
3156
3157 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3158 this case a cryptsetup partition) by changing issue_discards from
3159 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3160
3161 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3162 systems.&lt;/li&gt;
3163
3164 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3165 /etc/fstab.&lt;/li&gt;
3166
3167 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3168
3169 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3170 cron.daily).&lt;/li&gt;
3171
3172 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3173 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3174
3175 &lt;/ul&gt;
3176
3177 &lt;p&gt;During installation, I cancelled the part where the installer fill
3178 the disk with random data, as this would kill the SSD performance for
3179 little gain. My goal with the encrypted file system is to ensure
3180 those stealing my laptop end up with a brick and not a working
3181 computer. I have no hope in keeping the really resourceful people
3182 from getting the data on the disk (see
3183 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3184 Thus I concluded that adding the discard option to crypttab is the
3185 right thing to do.&lt;/p&gt;
3186
3187 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3188 it for SSD, but others recommended deadline and a benchmark I found
3189 indicated that deadline might be better for interactive use.&lt;/p&gt;
3190
3191 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3192 and ext4, but read that it would give a performance hit ever time a
3193 file is removed, and thought it best to that that slowdown once a day
3194 instead of during my work.&lt;/p&gt;
3195
3196 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3197 this is already done by Debian Edu.&lt;/p&gt;
3198
3199 &lt;p&gt;I have not yet started on the user space tuning. I expect
3200 iceweasel need some tuning, and perhaps other applications too, but
3201 have not yet had time to investigate those parts.&lt;/p&gt;
3202
3203 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3204 there.&lt;/p&gt;
3205
3206 &lt;p&gt;As for the answer to the question in the title of this blog post,
3207 as far as I know, the only solution I know about is to replace the
3208 disk. It might be possible to flash it with Intel firmware instead of
3209 the Lenovo firmware. But I have not tried and did not want to do so
3210 without approval from Lenovo as I wanted to keep the warranty on the
3211 disk until a solution was found and they wanted the broken disks
3212 back.&lt;/p&gt;
3213 </description>
3214 </item>
3215
3216 <item>
3217 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3218 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3219 <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>
3220 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3221 <description>&lt;p&gt;A few days ago, I wrote about
3222 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3223 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3224 was dying during installation because it is unable to cope with
3225 sustained write. My supplier is in contact with
3226 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3227 replacement disk to try to fix the problem. They decided to send an
3228 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3229
3230 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3231 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3232 same firmware version as the original. This time my hope raised
3233 slightly as the installation progressed, as the original disk used to
3234 die after 4-7% of the disk was written to, while this time it kept
3235 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3236 died again and I was back on square one. I still do not have a new
3237 laptop with a disk I can trust. I can not live with a disk that might
3238 lock up when I download a new
3239 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3240 other large files. I look forward to hearing from my supplier with
3241 the next proposal from Lenovo.&lt;/p&gt;
3242
3243 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3244 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3245 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3246 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3247 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3248 P/N 45N8295, P0C38732.&lt;/p&gt;
3249
3250 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3251 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3252 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3253 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3254 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3255 P/N 45N8295, P0C38732.&lt;/p&gt;
3256
3257 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3258 SA, date and WNPP values. Mentioning all the details here in case
3259 someone is able to use the information to find a way to identify the
3260 failing disk among working ones (if any such working disk actually
3261 exist).&lt;/p&gt;
3262 </description>
3263 </item>
3264
3265 <item>
3266 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3267 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3268 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3269 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3270 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3271 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3272 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3273 member assosiation NUUG&lt;/a&gt; and
3274 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3275 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3276 Bitraf&lt;/a&gt;.&lt;/p&gt;
3277
3278 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3279 welcome, and there is no fee to participate. There is on the other
3280 hand limited space, and only room for 30 people. Please put your name
3281 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3282 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3283 </description>
3284 </item>
3285
3286 <item>
3287 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3288 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3289 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3290 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3291 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3292 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3293 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3294 time to spend on it, and it took a while to find a model I believe
3295 will do the job, but two days ago the replacement finally arrived. I
3296 ended up picking a
3297 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3298 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3299 a roaming workstation, and it seemed to work flawlessly. But my
3300 second installation with encrypted disk was not as successful. More
3301 on that below.&lt;/p&gt;
3302
3303 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3304 important requirements (robust and with a good keyboard) are never
3305 listed in the feature list. But I did get good help from the search
3306 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3307 allowed me to limit the list of interesting laptops based on my other
3308 requirements. A bit surprising that SSD disk are not disks according
3309 to that search interface, so I had to drop specifying the number of
3310 disks from my search parameters. I also asked around among friends to
3311 get their impression on keyboards and robustness.&lt;/p&gt;
3312
3313 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3314 X41. I am not quite convinced about the keyboard, as it is
3315 significantly wider than my old keyboard, and I have to stretch my
3316 hand a lot more to reach the edges. But the key response is fairly
3317 good and the individual key shape is fairly easy to handle, so I hope
3318 I will get used to it. My old X40 was starting to fail, and I really
3319 needed a new laptop now. :)&lt;/p&gt;
3320
3321 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3322 visit to the BIOS during boot it disable it.&lt;/p&gt;
3323
3324 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3325 lock up during load. And this happen when installing Debian Wheezy
3326 with encrypted disk, while the disk is being filled with random data.
3327 I also tested to install Ubuntu Raring, and it happen there too if I
3328 reenable the code to fill the disk with random data (it is disabled by
3329 default in Ubuntu). And the bug with is already known. It was
3330 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3331 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3332 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3333 kernel developers as
3334 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3335 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3336 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3337 Lenovo forums, both for
3338 &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
3339 2012-11-10&lt;/a&gt; and for
3340 &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
3341 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3342 reports state that the disk lock up during use if many writes are done
3343 on the disk, so it is much no use to work around the installation
3344 problem and end up with a computer that can lock up at any moment.
3345 There is even a
3346 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3347 available&lt;/a&gt; that will lock up the hard drive after running a few
3348 minutes by writing to a file.&lt;/p&gt;
3349
3350 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3351 contacting PCHELP Norway (request 01D1FDP) which handle support
3352 requests for Lenovo, his first suggestion was to upgrade the disk
3353 firmware. Unfortunately there is no newer firmware available from
3354 Lenovo, as my disk already have the most recent one (version LF1i). I
3355 hope to hear more from him today and hope the problem can be
3356 fixed. :)&lt;/p&gt;
3357 </description>
3358 </item>
3359
3360 <item>
3361 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3362 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3363 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3364 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3365 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3366 trusty old Thinkpad X41. Unfortunately I did not have much time to
3367 spend on it, but today the replacement finally arrived. I ended up
3368 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3369 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3370 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3371 this, it is installing what I hope will be a more final installation,
3372 with a encrypted hard drive to ensure any dope head stealing it end up
3373 with an expencive door stop.&lt;/p&gt;
3374
3375 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3376 important requirements (robust and with a good keyboard) are never
3377 listed in the feature list. But I did get good help from the search
3378 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3379 allowed me to limit the list of interesting laptops based on my other
3380 requirements. A bit surprising that SSD disk are not disks, so I had
3381 to drop number of disks from my search parameters.&lt;/p&gt;
3382
3383 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3384 wider than my old keyboard, and I have to stretch my hand a lot more
3385 to reach the edges. But the key response is fairly good and the
3386 individual key shape is fairly easy to handle, so I hope I will get
3387 used to it. My old X40 was starting to fail, and I really needed a
3388 new laptop now. :)&lt;/p&gt;
3389
3390 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3391 </description>
3392 </item>
3393
3394 <item>
3395 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3396 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3397 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3398 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3399 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3400 perfectly capable of, and I have to do it manually to get things
3401 working. One such task is to find out what firmware packages are
3402 needed to get the hardware on my computer working. Most often this
3403 affect the wifi card, but some times it even affect the RAID
3404 controller or the ethernet card. Today I pushed version 0.4 of the
3405 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3406 including a new script isenkram-autoinstall-firmware handling the
3407 process of asking all the loaded kernel modules what firmware files
3408 they want, find debian packages providing these files and install the
3409 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3410
3411 &lt;p&gt;&lt;pre&gt;
3412 # isenkram-autoinstall-firmware
3413 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3414 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3415 info: locating packages with the requested firmware files
3416 info: Updating APT sources after adding non-free APT source
3417 info: trying to install firmware-ipw2x00
3418 firmware-ipw2x00
3419 firmware-ipw2x00
3420 Preconfiguring packages ...
3421 Selecting previously deselected package firmware-ipw2x00.
3422 (Reading database ... 259727 files and directories currently installed.)
3423 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3424 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3425 #
3426 &lt;/pre&gt;&lt;/p&gt;
3427
3428 &lt;p&gt;When all the requested firmware is present, a simple message is
3429 printed instead:&lt;/p&gt;
3430
3431 &lt;p&gt;&lt;pre&gt;
3432 # isenkram-autoinstall-firmware
3433 info: did not find any firmware files requested by loaded kernel modules. exiting
3434 #
3435 &lt;/pre&gt;&lt;/p&gt;
3436
3437 &lt;p&gt;It could use some polish, but it is already working well and saving
3438 me some time when setting up new machines. :)&lt;/p&gt;
3439
3440 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3441 kernel modules, and look up each one of them using modinfo, to find
3442 the firmware files listed in the module meta-information. Next, it
3443 download the Contents file from a nearby APT mirror, and search for
3444 the firmware files in this file to locate the package with the
3445 requested firmware file. If the package is in the non-free section, a
3446 non-free APT source is added and the package is installed using
3447 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3448 machine.&lt;/p&gt;
3449
3450 &lt;p&gt;I hope someone find time to implement a more polished version of
3451 this script as part of the hw-detect debian-installer module, to
3452 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3453 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3454 firmware during a PXE install when the packages already are available
3455 from the nearby Debian mirror.&lt;/p&gt;
3456 </description>
3457 </item>
3458
3459 <item>
3460 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3461 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3462 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3463 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3464 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3465 the screen just turn black when Linux boot, either during installation
3466 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3467 last few years, but only recently understood the cause. I&#39;ve seen it
3468 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3469 The reason seem to be in the wiring of some laptops. The system to
3470 control the screen background light is inverted, so when Linux try to
3471 turn the brightness fully on, it end up turning it off instead. I do
3472 not know which Linux drivers are affected, but this post is about the
3473 i915 driver used by the
3474 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3475 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3476
3477 &lt;p&gt;The problem can be worked around two ways. Either by adding
3478 i915.invert_brightness=1 as a kernel option, or by adding a file in
3479 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3480 option when it load the i915 kernel module. On Debian and Ubuntu, it
3481 can be done by running these commands as root:&lt;/p&gt;
3482
3483 &lt;pre&gt;
3484 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3485 update-initramfs -u -k all
3486 &lt;/pre&gt;
3487
3488 &lt;p&gt;Since March 2012 there is
3489 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3490 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3491 hardware have this problem, and get the driver to invert the
3492 brightness setting automatically. To use it, one need to add a row in
3493 &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
3494 intel_quirks array&lt;/a&gt; in the driver source
3495 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3496 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3497 number (vendor number 8086 is assumed) and subdevice vendor and device
3498 number.&lt;/p&gt;
3499
3500 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3501 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3502
3503 &lt;p&gt;&lt;pre&gt;
3504 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3505 3rd Gen Core processor Graphics Controller [8086:0156] \
3506 (rev 09) (prog-if 00 [VGA controller])
3507 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3508 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3509 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3510 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3511 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3512 Latency: 0
3513 Interrupt: pin A routed to IRQ 42
3514 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3515 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3516 Region 4: I/O ports at 4000 [size=64]
3517 Expansion ROM at &lt;unassigned&gt; [disabled]
3518 Capabilities: &lt;access denied&gt;
3519 Kernel driver in use: i915
3520 &lt;/pre&gt;&lt;/p&gt;
3521
3522 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3523
3524 &lt;p&gt;&lt;pre&gt;
3525 struct intel_quirk intel_quirks[] = {
3526 ...
3527 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3528 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3529 ...
3530 }
3531 &lt;/pre&gt;&lt;/p&gt;
3532
3533 &lt;p&gt;According to the kernel module instructions (as seen using
3534 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3535 invert_brightness flag should be sent to the
3536 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3537 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3538 developers. But my email about the laptop sent 2013-06-03 have not
3539 yet shown up in
3540 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3541 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3542 emails from non-subscribers. Because of this, I sent my patch also to
3543 the Debian bug tracking system instead as
3544 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3545 sure the patch is not lost.&lt;/p&gt;
3546
3547 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3548 with this problem working properly with Linux. If you use Gnome, your
3549 worries should be over at this point. But if you use KDE, there is
3550 something in KDE ignoring the invert_brightness setting and turning on
3551 the screen during login. I&#39;ve reported it to Debian as
3552 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3553 have no idea yet how to figure out exactly what subsystem is doing
3554 this. Perhaps you can help? Perhaps you know what the Gnome
3555 developers did to handle this, and this can give a clue to the KDE
3556 developers? Or you know where in KDE the screen brightness is changed
3557 during login? If so, please update the BTS report (or get in touch if
3558 you do not know how to update BTS).&lt;/p&gt;
3559
3560 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3561 acpi_backlight=vendor, to disable ACPI backlight support completely,
3562 as the ACPI information on the machine is trash and it is better to
3563 leave it to the intel video driver to control the screen
3564 backlight.&lt;/p&gt;
3565 </description>
3566 </item>
3567
3568 <item>
3569 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3570 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3571 <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>
3572 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3573 <description>&lt;p&gt;Two days ago, I asked
3574 &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
3575 I could install Linux on a Packard Bell EasyNote LV computer
3576 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3577 with the obstacles put in the way of Linux users on a laptop with UEFI
3578 and Windows 8.&lt;/p&gt;
3579
3580 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3581 secure booting or fast boot. I suspect fast boot was the problem,
3582 causing the firmware to boot directly from HD without considering any
3583 key presses and alternative devices, but do not know UEFI settings
3584 enough to tell.&lt;/p&gt;
3585
3586 &lt;p&gt;There is no way to install Linux on the machine in question without
3587 opening the box and disconnecting the hard drive! This is as far as I
3588 can tell, the only way to get access to the firmware setup menu
3589 without accepting the Windows 8 license agreement. I am told (and
3590 found description on how to) that it is possible to configure the
3591 firmware setup once booted into Windows 8. But as I believe the terms
3592 of that agreement are completely unacceptable, accepting the license
3593 was never an alternative. I do not enter agreements I do not intend
3594 to follow.&lt;/p&gt;
3595
3596 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3597 waste many hours on this, but luckily there was a way to get it to
3598 work. But I would not recommend it to anyone planning to run Linux on
3599 it, and I have become sceptical to Windows 8 certified laptops. Is
3600 this the way Linux will be forced out of the market place, by making
3601 it close to impossible for &quot;normal&quot; users to install Linux without
3602 accepting the Microsoft Windows license terms? Or at least not
3603 without risking to loose the warranty?&lt;/p&gt;
3604
3605 &lt;p&gt;I&#39;ve updated the
3606 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3607 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3608 do not have to struggle as much as I did to get Linux into the
3609 machine.&lt;/p&gt;
3610
3611 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3612 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3613 </description>
3614 </item>
3615
3616 <item>
3617 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3618 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3619 <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>
3620 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3621 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3622 new laptops for my parents and a few others. I bought Packard Bell
3623 Easynote LV to run Kubuntu on and use as their home computer. But I
3624 am completely unable to figure out how to install Linux on it. The
3625 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3626 instead of a BIOS to boot.&lt;/p&gt;
3627
3628 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3629 to get it to boot the Linux installer from my USB stick. I have yet
3630 to try the DVD install, and still hope it will work. when I turn on
3631 the computer, there is no information on what buttons to press to get
3632 the normal boot menu. I expect to get some boot menu to select PXE or
3633 USB stick booting. When booting, it first ask for the language to
3634 use, then for some regional settings, and finally if I will accept the
3635 Windows 8 terms of use. As these terms are completely unacceptable to
3636 me, I have no other choice but to turn off the computer and try again
3637 to get it to boot the Linux installer.&lt;/p&gt;
3638
3639 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3640 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3641 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3642 installed on this machine, please get in touch or update that wiki
3643 page. If I can&#39;t find a way to install Linux, I will have to return
3644 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3645
3646 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3647 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3648 on new Laptops?&lt;/p&gt;
3649 </description>
3650 </item>
3651
3652 <item>
3653 <title>How to transform a Debian based system to a Debian Edu installation</title>
3654 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3655 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3656 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3657 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3658 an operating system based on Debian intended for use in schools. It
3659 contain a turn-key solution for the computer network provided to
3660 pupils in the primary schools. It provide both the central server,
3661 network boot servers and desktop environments with heaps of
3662 educational software. The project was founded almost 12 years ago,
3663 2001-07-02. If you want to support the project, which is in need for
3664 cash to fund developer gatherings and other project related activity,
3665 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3666 donate some money&lt;/a&gt;.
3667
3668 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3669 lists and elsewhere, is the question on how to transform a Debian or
3670 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3671 hard, and last week I wrote a script to replicate the steps done by
3672 the Debian Edu installer.&lt;/p&gt;
3673
3674 &lt;p&gt;The script,
3675 &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;
3676 in the debian-edu-config package, will go through these six steps and
3677 transform an existing Debian Wheezy or Ubuntu (untested) installation
3678 into a Debian Edu Workstation:&lt;/p&gt;
3679
3680 &lt;ol&gt;
3681
3682 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3683 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3684 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3685 our configuration.&lt;/li&gt;
3686 &lt;li&gt;Preseed debconf database with profile setup in
3687 /etc/debian-edu/config, and run tasksel to install packages
3688 according to the profile specified in the config above,
3689 overriding some of the Debian automation machinery.&lt;/li&gt;
3690 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3691 that could not be done using preseeding.&lt;/li&gt;
3692 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3693
3694 &lt;/ol&gt;
3695
3696 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3697 replicated like this. Disk partitioning and LVM setup, for example.
3698 So this script just assume there is enough disk space to install all
3699 the needed packages.&lt;/p&gt;
3700
3701 &lt;p&gt;The script was created to help a Debian Edu student working on
3702 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3703 Debian Edu client, and using it he can take the existing
3704 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3705 transform it into a fully functioning Debian Edu Workstation (or
3706 Roaming Workstation, or whatever :).&lt;/p&gt;
3707
3708 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3709 If a LXDE based Roaming workstation is wanted instead, modify the
3710 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3711
3712 &lt;p&gt;&lt;pre&gt;
3713 PROFILE=&quot;Roaming-Workstation&quot;
3714 DESKTOP=&quot;lxde&quot;
3715 &lt;/pre&gt;&lt;/p&gt;
3716
3717 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3718 the cloud, by starting with a virtual Debian installation at some
3719 virtual hosting service and setting up all the services on first
3720 boot.&lt;/p&gt;
3721 </description>
3722 </item>
3723
3724 <item>
3725 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3726 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3727 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3728 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3729 <description>&lt;P&gt;In January,
3730 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3731 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3732 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3733 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3734 marvellous construction system from Denmark. We also created
3735 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3736 a place to take notes and write down our plans and hopes. And several
3737 people showed up to help. I was very happy to see the effect of my
3738 call. Since the small start, we have a debtags tag
3739 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3740 tag for LEGO related packages, and now count 10 packages related to
3741 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3742
3743 &lt;p&gt;&lt;table&gt;
3744 &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;
3745 &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;
3746 &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;
3747 &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;
3748 &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;
3749 &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;
3750 &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;
3751 &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;
3752 &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;
3753 &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;
3754 &lt;/table&gt;&lt;/p&gt;
3755
3756 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3757 currently available in Jessie/testing. leocad is so far only
3758 available in experimental.&lt;/p&gt;
3759
3760 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3761 adding the rest of the great free software tools available on Linux
3762 for LEGO designers.&lt;/p&gt;
3763 </description>
3764 </item>
3765
3766 <item>
3767 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3768 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3770 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3771 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3772 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3773 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3774 Debian release, and I expect to move my machines at home over to it fairly
3775 soon.&lt;/p&gt;
3776
3777 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3778 in particular make me very happy to see included. The
3779 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3780 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3781 included for the first time. Alongside similar programs like
3782 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3783 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3784 it allow for visual programming where syntax errors can not happen,
3785 and a friendly programming environment for learning to control the
3786 computer. Scratch will also be included in the next release of Debian
3787 Edu.&lt;/a&gt;
3788
3789 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3790 Edu/Skolelinux release too. The
3791 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3792 alpha release&lt;/a&gt; went out last week, and the next should soon
3793 follow.&lt;p&gt;
3794 </description>
3795 </item>
3796
3797 <item>
3798 <title>Isenkram 0.2 finally in the Debian archive</title>
3799 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3800 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3801 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3802 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3803 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3804 for many months. I uploaded it to the Debian experimental suite
3805 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3806
3807 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3808 install to work with a pluggable hardware device. The suggestion pop
3809 up when the device is plugged in. For example if a Lego Mindstorm NXT
3810 is inserted, it will suggest to install the program needed to program
3811 the NXT controller. Give it a go, and report bugs and suggestions to
3812 BTS. :)&lt;/p&gt;
3813 </description>
3814 </item>
3815
3816 <item>
3817 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3818 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3819 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3820 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3821 <description>&lt;p&gt;My
3822 &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
3823 bitcoin related blog post&lt;/a&gt; mentioned that the new
3824 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3825 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3826 2013-01-19, and have been available in unstable since then. It was
3827 automatically copied to Ubuntu, and is available in their Raring
3828 version too.&lt;/p&gt;
3829
3830 &lt;p&gt;But there is a strange problem with the build that block this new
3831 version from being available on the i386 and kfreebsd-i386
3832 architectures. For some strange reason, the autobuilders in Debian
3833 for these architectures fail to run the test suite on these
3834 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3835 We are so far unable to reproduce it when building it manually, and
3836 no-one have been able to propose a fix. If you got an idea what is
3837 failing, please let us know via the BTS.&lt;/p&gt;
3838
3839 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3840 I often run low on disk space, is the fact that the client will exit
3841 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3842 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3843 it. :)&lt;/p&gt;
3844
3845 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3846 activities, please send Bitcoin donations to my address
3847 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3848 </description>
3849 </item>
3850
3851 <item>
3852 <title>Welcome to the world, Isenkram!</title>
3853 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3854 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3855 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3856 <description>&lt;p&gt;Yesterday, I
3857 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3858 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3859 pluggable hardware devices, which I
3860 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3861 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3862 up, and caused me to really want to to open up the development to more
3863 people. But before I did this, I want to come up with a sensible name
3864 for this project. Today I finally decided on a new name, and I have
3865 renamed the project from hw-support-handler to this new name. In the
3866 process, I moved the source to git and made it available as a
3867 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3868 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3869 To fetch and build the latest version of the source, use&lt;/p&gt;
3870
3871 &lt;pre&gt;
3872 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3873 cd isenkram &amp;&amp; git-buildpackage -us -uc
3874 &lt;/pre&gt;
3875
3876 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3877 want to hack on the source or improve the package, please go ahead.
3878 But please talk to me first on IRC or via email before you do major
3879 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3880
3881 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3882 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3883 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3884 the German word eisenkram, for those that are familiar with that
3885 word.&lt;/p&gt;
3886
3887 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3888 instructions, to avoid confusing people with an error from the signing
3889 process.&lt;/p&gt;
3890
3891 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3892 clone argument to avoid the need for authentication.&lt;/p&gt;
3893 </description>
3894 </item>
3895
3896 <item>
3897 <title>First prototype ready making hardware easier to use in Debian</title>
3898 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3900 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3901 <description>&lt;p&gt;Early this month I set out to try to
3902 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3903 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3904 prototype is working, and it is ready for a larger audience. To test
3905 it, fetch the
3906 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3907 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3908 package. You might have to log out and in again activate the
3909 autostart script.&lt;/p&gt;
3910
3911 &lt;p&gt;The design is simple:&lt;/p&gt;
3912
3913 &lt;ul&gt;
3914
3915 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3916 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3917
3918 &lt;li&gt;This program listen for kernel events about new hardware (directly
3919 from the kernel like udev does), not using HAL dbus events as I
3920 initially did.&lt;/li&gt;
3921
3922 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3923 the APT database, a database
3924 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3925 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3926
3927 &lt;li&gt;If a package is mapped to the hardware in question, the package
3928 isn&#39;t installed yet and this is the first time the hardware was
3929 plugged in, show a desktop notification suggesting to install the
3930 package or packages.&lt;/li&gt;
3931
3932 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3933 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3934
3935 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3936 package while showing progress information in a window.&lt;/li&gt;
3937
3938 &lt;/ul&gt;
3939
3940 &lt;p&gt;I still need to come up with a better name for the system. Here
3941 are some screen shots showing the prototype in action. First the
3942 notification, then the password request, and finally the request to
3943 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3944
3945 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3946 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3947 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3948 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3949 &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;
3950
3951 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3952 is already useful. The database of hardware to package mappings also
3953 need more work. It is currently compatible with the Ubuntu way of
3954 storing such information in the package control file, but could be
3955 changed to use other formats instead or in addition to the current
3956 method. I&#39;ve dropped the use of discover for this mapping, as the
3957 modalias approach is more flexible and easier to use on Linux as long
3958 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3959
3960 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3961 here is the command required to check out and build the source: Use
3962 &#39;&lt;tt&gt;svn checkout
3963 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3964 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3965 devscripts package.&lt;/p&gt;
3966
3967 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3968 renamed to Isenkram and the source moved from the Debian Edu
3969 subversion repository to a Debian collab-maint git repository. See
3970 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3971 instructions&lt;/a&gt; for details.&lt;/p&gt;
3972 </description>
3973 </item>
3974
3975 <item>
3976 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3977 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3978 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3979 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3980 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3981 suddenly in bed. With a quiet whimper, it went completely quiet and
3982 black. The power button was no longer able to turn it on. It was a
3983 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3984 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3985 Compaq I had before that. Now I need to find a replacement. To keep
3986 going during Christmas, I moved the one year old SSD disk to my old
3987 X40 where it fitted (only one I had left that could use it), but it is
3988 not a durable solution.
3989
3990 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3991 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3992
3993 &lt;ul&gt;
3994
3995 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3996 than A4).&lt;/li&gt;
3997 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3998 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3999 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
4000 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
4001 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
4002 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
4003 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
4004 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
4005 size).&lt;/li&gt;
4006 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
4007 X.org packages.&lt;/li&gt;
4008 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
4009 the time).
4010
4011 &lt;/ul&gt;
4012
4013 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
4014 list. The reason is simply that the specifications on laptops the
4015 last 10-15 years have been sufficient for my needs, and I have to look
4016 at other features to choose my laptop. But are there still made as
4017 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4018 robust, and Thinkpads seem to be heading in the wrong direction since
4019 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
4020 still be useful.&lt;/p&gt;
4021
4022 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
4023 external keyboard? I&#39;ll have to check the
4024 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
4025 well-supported laptops, or perhaps just buy one preinstalled from one
4026 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
4027 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
4028 </description>
4029 </item>
4030
4031 <item>
4032 <title>How to find a browser plugin supporting a given MIME type</title>
4033 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
4034 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
4035 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
4036 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
4037 install to get support for a given MIME type. Thanks to
4038 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
4039 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
4040 Unfortunately, not very many packages provide the needed meta
4041 information, Anyway, here is a small script to look up all browser
4042 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
4043
4044 &lt;pre&gt;
4045 #!/usr/bin/python
4046 import sys
4047 import apt
4048 def pkgs_handling_mimetype(mimetype):
4049 cache = apt.Cache()
4050 cache.open(None)
4051 thepkgs = []
4052 for pkg in cache:
4053 version = pkg.candidate
4054 if version is None:
4055 version = pkg.installed
4056 if version is None:
4057 continue
4058 record = version.record
4059 if not record.has_key(&#39;Npp-MimeType&#39;):
4060 continue
4061 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
4062 for t in mime_types:
4063 t = t.rstrip().strip()
4064 if t == mimetype:
4065 thepkgs.append(pkg.name)
4066 return thepkgs
4067 mimetype = &quot;audio/ogg&quot;
4068 if 1 &lt; len(sys.argv):
4069 mimetype = sys.argv[1]
4070 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
4071 for pkg in pkgs_handling_mimetype(mimetype):
4072 print &quot; %s&quot; %pkg
4073 &lt;/pre&gt;
4074
4075 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
4076
4077 &lt;pre&gt;
4078 % ./apt-find-browserplug-for-mimetype
4079 Browser plugin packages supporting audio/ogg:
4080 gecko-mediaplayer
4081 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4082 Browser plugin packages supporting application/x-shockwave-flash:
4083 browser-plugin-gnash
4084 %
4085 &lt;/pre&gt;
4086
4087 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4088 itself to query for plugins and propose to install the needed
4089 packages. It would be great if Debian supported such feature too. Is
4090 anyone working on adding it?&lt;/p&gt;
4091
4092 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4093 request for icweasel support for this feature is
4094 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4095 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4096 of manpower and wish for a different design is the reason thus feature
4097 is not yet in iceweasel from Debian.&lt;/p&gt;
4098 </description>
4099 </item>
4100
4101 <item>
4102 <title>What is the most supported MIME type in Debian?</title>
4103 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4104 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4105 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4106 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4107 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4108 proposal to make it possible for a Desktop application to propose to
4109 the user some package to install to gain support for a given MIME
4110 type, font, library etc. that is currently missing. With such
4111 mechanism in place, it would be possible for the desktop to
4112 automatically propose and install leocad if some LDraw file is
4113 downloaded by the browser.&lt;/p&gt;
4114
4115 &lt;p&gt;To get some idea about the current content of the archive, I decided
4116 to write a simple program to extract all .desktop files from the
4117 Debian archive and look up the claimed MIME support there. The result
4118 can be found on the
4119 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4120 site&lt;/a&gt;. Using the collected information, it become possible to
4121 answer the question in the title. Here are the 20 most supported MIME
4122 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4123 The complete list is available from the link above.&lt;/p&gt;
4124
4125 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4126
4127 &lt;pre&gt;
4128 count MIME type
4129 ----- -----------------------
4130 32 text/plain
4131 30 audio/mpeg
4132 29 image/png
4133 28 image/jpeg
4134 27 application/ogg
4135 26 audio/x-mp3
4136 25 image/tiff
4137 25 image/gif
4138 22 image/bmp
4139 22 audio/x-wav
4140 20 audio/x-flac
4141 19 audio/x-mpegurl
4142 18 video/x-ms-asf
4143 18 audio/x-musepack
4144 18 audio/x-mpeg
4145 18 application/x-ogg
4146 17 video/mpeg
4147 17 audio/x-scpls
4148 17 audio/ogg
4149 16 video/x-ms-wmv
4150 &lt;/pre&gt;
4151
4152 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4153
4154 &lt;pre&gt;
4155 count MIME type
4156 ----- -----------------------
4157 33 text/plain
4158 32 image/png
4159 32 image/jpeg
4160 29 audio/mpeg
4161 27 image/gif
4162 26 image/tiff
4163 26 application/ogg
4164 25 audio/x-mp3
4165 22 image/bmp
4166 21 audio/x-wav
4167 19 audio/x-mpegurl
4168 19 audio/x-mpeg
4169 18 video/mpeg
4170 18 audio/x-scpls
4171 18 audio/x-flac
4172 18 application/x-ogg
4173 17 video/x-ms-asf
4174 17 text/html
4175 17 audio/x-musepack
4176 16 image/x-xbitmap
4177 &lt;/pre&gt;
4178
4179 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4180
4181 &lt;pre&gt;
4182 count MIME type
4183 ----- -----------------------
4184 31 text/plain
4185 31 image/png
4186 31 image/jpeg
4187 29 audio/mpeg
4188 28 application/ogg
4189 27 image/gif
4190 26 image/tiff
4191 26 audio/x-mp3
4192 23 audio/x-wav
4193 22 image/bmp
4194 21 audio/x-flac
4195 20 audio/x-mpegurl
4196 19 audio/x-mpeg
4197 18 video/x-ms-asf
4198 18 video/mpeg
4199 18 audio/x-scpls
4200 18 application/x-ogg
4201 17 audio/x-musepack
4202 16 video/x-ms-wmv
4203 16 video/x-msvideo
4204 &lt;/pre&gt;
4205
4206 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4207 information mentioned in DEP-11. I have not yet had time to look at
4208 it, but hope the PackageKit people in Debian are on top of these
4209 issues.&lt;/p&gt;
4210
4211 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4212 discovering a typo in my script.&lt;/p&gt;
4213 </description>
4214 </item>
4215
4216 <item>
4217 <title>Using modalias info to find packages handling my hardware</title>
4218 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4219 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4220 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4221 <description>&lt;p&gt;Yesterday, I wrote about the
4222 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4223 values provided by the Linux kernel&lt;/a&gt; following my hope for
4224 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4225 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4226 modalias values attached to package names can be used to map packages
4227 to hardware. This allow the system to look up and suggest relevant
4228 packages when I plug in some new hardware into my machine, and replace
4229 discover and discover-data as the database used to map hardware to
4230 packages.&lt;/p&gt;
4231
4232 &lt;p&gt;I create a modaliases file with entries like the following,
4233 containing package name, kernel module name (if relevant, otherwise
4234 the package name) and globs matching the relevant hardware
4235 modalias.&lt;/p&gt;
4236
4237 &lt;p&gt;&lt;blockquote&gt;
4238 Package: package-name
4239 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4240 &lt;/blockquote&gt;&lt;/p&gt;
4241
4242 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4243 for a given modalias value using this file.&lt;/p&gt;
4244
4245 &lt;p&gt;An entry like this would suggest the video and picture application
4246 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4247
4248 &lt;p&gt;&lt;blockquote&gt;
4249 Package: cheese
4250 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4251 &lt;/blockquote&gt;&lt;/p&gt;
4252
4253 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4254 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4255
4256 &lt;p&gt;&lt;blockquote&gt;
4257 Package: pcmciautils
4258 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4259 &lt;/blockquote&gt;&lt;/p&gt;
4260
4261 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4262 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4263
4264 &lt;p&gt;&lt;blockquote&gt;
4265 Package: colorhug-client
4266 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4267 &lt;/blockquote&gt;&lt;/p&gt;
4268
4269 &lt;p&gt;I believe the format is compatible with the format of the Packages
4270 file in the Debian archive. Ubuntu already uses their Packages file
4271 to store their mappings from packages to hardware.&lt;/p&gt;
4272
4273 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4274 announce the hardware it support in a way my prototype understand.
4275 This allow those publishing packages in an APT source outside the
4276 Debian archive as well as those backporting packages to make sure the
4277 hardware mapping are included in the package meta information. I&#39;ve
4278 tested such header in the pymissile package, and its modalias mapping
4279 is working as it should with my prototype. It even made it to Ubuntu
4280 Raring.&lt;/p&gt;
4281
4282 &lt;p&gt;To test if it was possible to look up supported hardware using only
4283 the shell tools available in the Debian installer, I wrote a shell
4284 implementation of the lookup code. The idea is to create files for
4285 each modalias and let the shell do the matching. Please check out and
4286 try the
4287 &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;
4288 shell script. It run without any extra dependencies and fetch the
4289 hardware mappings from the Debian archive and the subversion
4290 repository where I currently work on my prototype.&lt;/p&gt;
4291
4292 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4293 install yubikey-personalization:&lt;/p&gt;
4294
4295 &lt;p&gt;&lt;blockquote&gt;
4296 % ./hw-support-lookup
4297 &lt;br&gt;yubikey-personalization
4298 &lt;br&gt;%
4299 &lt;/blockquote&gt;&lt;/p&gt;
4300
4301 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4302 propose to install the pcmciautils package:&lt;/p&gt;
4303
4304 &lt;p&gt;&lt;blockquote&gt;
4305 % ./hw-support-lookup
4306 &lt;br&gt;pcmciautils
4307 &lt;br&gt;%
4308 &lt;/blockquote&gt;&lt;/p&gt;
4309
4310 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4311 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4312 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4313
4314 &lt;p&gt;It could be possible to generate several of the mappings between
4315 packages and hardware. One source would be to look at packages with
4316 kernel modules, ie packages with *.ko files in /lib/modules/, and
4317 extract their modalias information. Another would be to look at
4318 packages with udev rules, ie packages with files in
4319 /lib/udev/rules.d/, and extract their vendor/model information to
4320 generate a modalias matching rule. I have not tested any of these to
4321 see if it work.&lt;/p&gt;
4322
4323 &lt;p&gt;If you want to help implementing a system to let us propose what
4324 packages to install when new hardware is plugged into a Debian
4325 machine, please send me an email or talk to me on
4326 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4327 </description>
4328 </item>
4329
4330 <item>
4331 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4332 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4333 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4334 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4335 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4336 information, to find the packages that support a given piece of
4337 hardware, I refreshed my memory regarding modalias values, and decided
4338 to document the details. Here are my findings so far, also available
4339 in
4340 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4341 Debian Edu subversion repository&lt;/a&gt;:
4342
4343 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4344
4345 &lt;p&gt;This document try to explain what the different types of modalias
4346 values stands for. It is in part based on information from
4347 &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;,
4348 &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;,
4349 &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
4350 &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;.
4351
4352 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4353 this shell script:&lt;/p&gt;
4354
4355 &lt;pre&gt;
4356 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4357 &lt;/pre&gt;
4358
4359 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4360 using modinfo:&lt;/p&gt;
4361
4362 &lt;pre&gt;
4363 % /sbin/modinfo psmouse | grep alias:
4364 alias: serio:ty05pr*id*ex*
4365 alias: serio:ty01pr*id*ex*
4366 %
4367 &lt;/pre&gt;
4368
4369 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4370
4371 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4372 Bridge memory controller:&lt;/p&gt;
4373
4374 &lt;p&gt;&lt;blockquote&gt;
4375 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4376 &lt;/blockquote&gt;&lt;/p&gt;
4377
4378 &lt;p&gt;This represent these values:&lt;/p&gt;
4379
4380 &lt;pre&gt;
4381 v 00008086 (vendor)
4382 d 00002770 (device)
4383 sv 00001028 (subvendor)
4384 sd 000001AD (subdevice)
4385 bc 06 (bus class)
4386 sc 00 (bus subclass)
4387 i 00 (interface)
4388 &lt;/pre&gt;
4389
4390 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4391 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4392 0600. The 0600 class is a host bridge. Other useful bus values are
4393 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4394
4395 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4396 means.&lt;/p&gt;
4397
4398 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4399
4400 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4401 USB hub in a laptop:&lt;/p&gt;
4402
4403 &lt;p&gt;&lt;blockquote&gt;
4404 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4405 &lt;/blockquote&gt;&lt;/p&gt;
4406
4407 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4408
4409 &lt;pre&gt;
4410 v 1D6B (device vendor)
4411 p 0001 (device product)
4412 d 0206 (bcddevice)
4413 dc 09 (device class)
4414 dsc 00 (device subclass)
4415 dp 00 (device protocol)
4416 ic 09 (interface class)
4417 isc 00 (interface subclass)
4418 ip 00 (interface protocol)
4419 &lt;/pre&gt;
4420
4421 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4422 class is in the interface class section. For a simple USB web camera,
4423 these alias entries show up:&lt;/p&gt;
4424
4425 &lt;p&gt;&lt;blockquote&gt;
4426 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4427 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4428 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4429 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4430 &lt;/blockquote&gt;&lt;/p&gt;
4431
4432 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4433 camera), 0101 is audio control device and 0102 is audio streaming (aka
4434 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4435
4436 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4437
4438 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4439 receiver in a Thinkpad X40:&lt;/p&gt;
4440
4441 &lt;p&gt;&lt;blockquote&gt;
4442 acpi:IBM0071:PNP0511:
4443 &lt;/blockquote&gt;&lt;/p&gt;
4444
4445 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4446
4447 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4448
4449 &lt;p&gt;The DMI table contain lots of information about the computer case
4450 and model. This is an entry for a IBM Thinkpad X40, fetched from
4451 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4452
4453 &lt;p&gt;&lt;blockquote&gt;
4454 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4455 &lt;/blockquote&gt;&lt;/p&gt;
4456
4457 &lt;p&gt;The values present are&lt;/p&gt;
4458
4459 &lt;pre&gt;
4460 bvn IBM (BIOS vendor)
4461 bvr 1UETB6WW(1.66) (BIOS version)
4462 bd 06/15/2005 (BIOS date)
4463 svn IBM (system vendor)
4464 pn 2371H4G (product name)
4465 pvr ThinkPadX40 (product version)
4466 rvn IBM (board vendor)
4467 rn 2371H4G (board name)
4468 rvr NotAvailable (board version)
4469 cvn IBM (chassis vendor)
4470 ct 10 (chassis type)
4471 cvr NotAvailable (chassis version)
4472 &lt;/pre&gt;
4473
4474 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4475 found in the dmidecode source:&lt;/p&gt;
4476
4477 &lt;pre&gt;
4478 3 Desktop
4479 4 Low Profile Desktop
4480 5 Pizza Box
4481 6 Mini Tower
4482 7 Tower
4483 8 Portable
4484 9 Laptop
4485 10 Notebook
4486 11 Hand Held
4487 12 Docking Station
4488 13 All In One
4489 14 Sub Notebook
4490 15 Space-saving
4491 16 Lunch Box
4492 17 Main Server Chassis
4493 18 Expansion Chassis
4494 19 Sub Chassis
4495 20 Bus Expansion Chassis
4496 21 Peripheral Chassis
4497 22 RAID Chassis
4498 23 Rack Mount Chassis
4499 24 Sealed-case PC
4500 25 Multi-system
4501 26 CompactPCI
4502 27 AdvancedTCA
4503 28 Blade
4504 29 Blade Enclosing
4505 &lt;/pre&gt;
4506
4507 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4508 table. For example my home server is a tower, but the DMI modalias
4509 claim it is a desktop.&lt;/p&gt;
4510
4511 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4512
4513 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4514 test machine:&lt;/p&gt;
4515
4516 &lt;p&gt;&lt;blockquote&gt;
4517 serio:ty01pr00id00ex00
4518 &lt;/blockquote&gt;&lt;/p&gt;
4519
4520 &lt;p&gt;The values present are&lt;/p&gt;
4521
4522 &lt;pre&gt;
4523 ty 01 (type)
4524 pr 00 (prototype)
4525 id 00 (id)
4526 ex 00 (extra)
4527 &lt;/pre&gt;
4528
4529 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4530 the valid values are.&lt;/p&gt;
4531
4532 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4533
4534 &lt;p&gt;There are heaps of other modalias subtypes according to
4535 file2alias.c. There is the rest of the list from that source: amba,
4536 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4537 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4538 vmbus, x86cpu and zorro. I did not spend time documenting all of
4539 these, as they do not seem relevant for my intended use with mapping
4540 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4541
4542 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4543
4544 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4545 one can use the following shell script:&lt;/p&gt;
4546
4547 &lt;pre&gt;
4548 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4549 echo &quot;$id&quot; ; \
4550 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4551 done
4552 &lt;/pre&gt;
4553
4554 &lt;p&gt;The output can look like this (only the first few entries as the
4555 list is very long on my test machine):&lt;/p&gt;
4556
4557 &lt;pre&gt;
4558 acpi:ACPI0003:
4559 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4560 acpi:device:
4561 FATAL: Module acpi:device: not found.
4562 acpi:IBM0068:
4563 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4564 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4565 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4566 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4567 acpi:IBM0071:PNP0511:
4568 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4569 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4570 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4571 [...]
4572 &lt;/pre&gt;
4573
4574 &lt;p&gt;If you want to help implementing a system to let us propose what
4575 packages to install when new hardware is plugged into a Debian
4576 machine, please send me an email or talk to me on
4577 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4578
4579 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4580 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4581 in /sys/ with space in them.&lt;/p&gt;
4582 </description>
4583 </item>
4584
4585 <item>
4586 <title>Moved the pymissile Debian packaging to collab-maint</title>
4587 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4588 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4589 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4590 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4591 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4592 Launcher and updated the Debian package
4593 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4594 sure udev will fix the device permissions when it is plugged in. I
4595 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4596 hopefully make the package be proposed by jockey in Ubuntu when a user
4597 plug in his rocket launcher. In the process I moved the source to a
4598 git repository under collab-maint, to make it easier for any DD to
4599 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4600 is not very active, but the software still work for me even after five
4601 years of relative silence. The new git repository is not listed in
4602 the uploaded package yet, because I want to test the other changes a
4603 bit more before I upload the new version. If you want to check out
4604 the new version with a .desktop file included, visit the
4605 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4606 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4607 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4608 </description>
4609 </item>
4610
4611 <item>
4612 <title>Lets make hardware dongles easier to use in Debian</title>
4613 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4614 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4615 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4616 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4617 general, is that there is a great package management system with the
4618 ability to automatically install software packages by downloading them
4619 from the distribution mirrors, but no way to get it to automatically
4620 install the packages I need to use the hardware I plug into my
4621 machine. Even if the package to use it is easily available from the
4622 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4623 suggest to automatically install the python-nxt, nbc and t2n packages
4624 I need to talk to it. When I plug in a Yubikey, it could propose the
4625 yubikey-personalization package. The information required to do this
4626 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4627
4628 &lt;p&gt;Some years ago, I proposed to
4629 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4630 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4631 simple:
4632
4633 &lt;ul&gt;
4634
4635 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4636 starting when a user log in.&lt;/li&gt;
4637
4638 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4639 hardware is inserted into the computer.&lt;/li&gt;
4640
4641 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4642 database mapping to packages, and take note of any non-installed
4643 packages.&lt;/li&gt;
4644
4645 &lt;li&gt;Show a message to the user proposing to install the discovered
4646 package, and make it easy to install it.&lt;/li&gt;
4647
4648 &lt;/ul&gt;
4649
4650 &lt;p&gt;I am not sure what the best way to implement this is, but my
4651 initial idea was to use dbus events to discover new hardware, the
4652 discover database to find packages and
4653 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4654 packages.&lt;/p&gt;
4655
4656 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4657 draft package is now checked into
4658 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4659 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4660 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4661 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4662 the relevant packages in Debian, and uploaded a new version
4663 2.2013.01.09 to unstable. I also discovered that the current
4664 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4665 package in Debian no longer discovered any USB devices, because
4666 /proc/bus/usb/devices is no longer present. I ported it to use
4667 libusb as a fall back option to get it working. The fixed package
4668 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4669 because of the freeze).&lt;/p&gt;
4670
4671 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4672 desktop notification to show up (only once, the first time it is
4673 inserted):&lt;/p&gt;
4674
4675 &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;
4676
4677 &lt;p&gt;For this prototype to be really useful, some way to automatically
4678 install the proposed packages by pressing the &quot;Please install
4679 program(s)&quot; button should to be implemented.&lt;/p&gt;
4680
4681 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4682 happen, please help me update the discover-data database with mappings
4683 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4684 list the package you would like to have installed when a given
4685 hardware device is inserted into your computer, and report bugs using
4686 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4687 such mapping, please let me know.&lt;/p&gt;
4688
4689 &lt;p&gt;This prototype need more work, and there are several questions that
4690 should be considered before it is ready for production use. Is dbus
4691 the correct way to detect new hardware? At the moment I look for HAL
4692 dbus events on the system bus, because that is the events I could see
4693 on my Debian Squeeze KDE desktop. Are there better events to use?
4694 How should the user be notified? Is the desktop notification
4695 mechanism the best option, or should the background daemon raise a
4696 popup instead? How should packages be installed? When should they
4697 not be installed?&lt;/p&gt;
4698
4699 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4700 please send me an email. :)&lt;/p&gt;
4701 </description>
4702 </item>
4703
4704 <item>
4705 <title>New IRC channel for LEGO designers using Debian</title>
4706 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4707 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4708 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4709 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4710 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4711 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4712 discovered I had to build all the tools myself because none were
4713 already in Debian Squeeze. If Debian support for LEGO is something
4714 you care about, please join me on the IRC channel
4715 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4716 irc.debian.org). There is a lot that could be done to improve the
4717 Debian support for LEGO designers. For example both CAD software
4718 and Mindstorm compilers are missing. :)&lt;/p&gt;
4719
4720 &lt;p&gt;Update 2012-01-03: A
4721 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4722 including links to Lego related packages is now available.&lt;/p&gt;
4723 </description>
4724 </item>
4725
4726 <item>
4727 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4728 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4730 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4731 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4732 year! I hope next year will prove to be a good year.&lt;/p&gt;
4733
4734 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4735 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4736 between each other with minimal overhead, is a very interesting
4737 experiment. And as I wrote a few days ago, the bitcoin situation in
4738 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4739 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4740 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4741 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4742 for one of the ftpmasters to approve the new bitcoin-qt package
4743 name.&lt;/p&gt;
4744
4745 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4746 team in Debian, you can easily test the package in Debian Squeeze
4747 using the following steps to get a set of working packages:&lt;/p&gt;
4748
4749 &lt;blockquote&gt;&lt;pre&gt;
4750 git clone git://git.debian.org/git/collab-maint/bitcoin
4751 cd bitcoin
4752 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4753 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4754 &lt;/pre&gt;&lt;/blockquote&gt;
4755
4756 &lt;p&gt;You might have to install some build dependencies as well. The
4757 list of commands should give you two packages, bitcoind and
4758 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4759 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4760 around 5.6 GiB of data on my machine at the moment. Make sure your
4761 ~/.bitcoin/ directory have lots of spare room if you want to download
4762 all the blocks. The client will warn if the disk is getting full, so
4763 there is not really a problem if you got too little room, but you will
4764 not be able to get all the features out of the client.&lt;/p&gt;
4765
4766 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4767 activities, please send Bitcoin donations to my address
4768 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4769 </description>
4770 </item>
4771
4772 <item>
4773 <title>A word on bitcoin support in Debian</title>
4774 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4775 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4776 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4777 <description>&lt;p&gt;It has been a while since I wrote about
4778 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4779 peer-to-peer based crypto-currency, and the reason is simply that I
4780 have been busy elsewhere. But two days ago, I started looking at the
4781 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4782 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4783 is now maintained by a
4784 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4785 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4786 owe a huge thank you to all these team members. :)
4787 But I was sad to discover that the bitcoin client is missing in
4788 Wheezy. It is only available in Sid (and an outdated client from
4789 backports). The client had several RC bugs registered in BTS blocking
4790 it from entering testing. To try to help the team and improve the
4791 situation, I spent some time providing patches and triaging the bug
4792 reports. I also had a look at the bitcoin package available from Matt
4793 Corallo in a
4794 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4795 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4796 Debian package.&lt;/p&gt;
4797
4798 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4799 IRC, I pushed several patches into the collab-maint git repository to
4800 improve the package. It now contains fixes for the RC issues (not from
4801 me, but fixed by Scott Howard), build rules for a Qt GUI client
4802 package, konqueror support for the bitcoin: URI and bash completion
4803 setup. As I work on Debian Squeeze, I also created
4804 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4805 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4806 it and try to integrate it into the git repository before uploading a
4807 new version to unstable.
4808
4809 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4810 centralized control currently exercised in the monetary system. I
4811 find it completely unacceptable that the USA government is collecting
4812 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4813 that the major credit card companies can block legal money
4814 transactions to Wikileaks. But for bitcoin to succeed, more people
4815 need to use bitcoins, and more people need to accept bitcoins when
4816 they sell products and services. Improving the bitcoin support in
4817 Debian is a small step in the right direction, but not enough.
4818 Unfortunately the user experience when browsing the web and wanting to
4819 pay with bitcoin is still not very good. The bitcoin: URI is a step
4820 in the right direction, but need to work in most or every browser in
4821 use. Also the bitcoin-qt client is too heavy to fire up to do a
4822 quick transaction. I believe there are other clients available, but
4823 have not tested them.&lt;/p&gt;
4824
4825 &lt;p&gt;My
4826 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4827 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4828 I received 20.15 BTC so far on the address I provided in my blog two
4829 years ago, as can be
4830 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4831 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4832 donation. The blockexplorer service demonstrates quite well that
4833 bitcoin is not quite anonymous and untracked. :) I wonder if the
4834 number of users have gone up since then. If you use bitcoin and want
4835 to show your support of my activity, please send Bitcoin donations to
4836 the same address as last time,
4837 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4838 </description>
4839 </item>
4840
4841 <item>
4842 <title>Git repository for song book for Computer Scientists</title>
4843 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4844 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4845 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4846 <description>&lt;p&gt;As I
4847 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4848 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4849 years ago, and today I finally found time to create a public
4850 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4851 repository for the project&lt;/a&gt;.&lt;/p&gt;
4852
4853 &lt;p&gt;If you want to help out, please clone the source and submit patches
4854 to the HTML version. To generate the PDF and PostScript version,
4855 please use prince XML, or let me know about a useful free software
4856 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4857
4858 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4859 PostScript formats at
4860 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4861 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4862 </description>
4863 </item>
4864
4865 <item>
4866 <title>Gratulerer med 19-årsdagen, Debian!</title>
4867 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4868 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4869 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4870 <description>&lt;p&gt;I dag fyller
4871 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4872 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4873 si gratulerer med dagen, Debian!&lt;/p&gt;
4874 </description>
4875 </item>
4876
4877 <item>
4878 <title>Song book for Computer Scientists</title>
4879 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4880 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4881 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4882 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4883 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4884 collecting computer related songs for use at parties. The original
4885 version was written in LaTeX, but a few years ago I got help from
4886 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4887 while keeping the ability to create a nice book in PDF format. I have
4888 not had time to maintain the book for a while now, and guess I should
4889 put it up on some public version control repository where others can
4890 help me extend and update the book. If anyone is volunteering to help
4891 me with this, send me an email. Also let me know if there are songs
4892 missing in my book.&lt;/p&gt;
4893
4894 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4895 me today that I really should let all my readers share the joys of
4896 singing out load about programming, computers and computer networks.
4897 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4898 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4899 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4900 Computer Science Songbook&lt;/a&gt;.
4901 </description>
4902 </item>
4903
4904 <item>
4905 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4906 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4907 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4908 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4909 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4910 around 1000 at the moment. To be able to get help from the vendors
4911 when something go wrong, we want to keep the firmware on the servers
4912 up to date. If the firmware isn&#39;t the latest and greatest, the
4913 vendors typically refuse to start debugging any problems until the
4914 firmware is upgraded. So before every reboot, we want to upgrade the
4915 firmware, and we would really like everyone handling servers at the
4916 university to do this themselves when they plan to reboot a machine.
4917 For that to happen we at the unix server admin group need to provide
4918 the tools to do so.&lt;/p&gt;
4919
4920 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4921 fetch and install the latest firmware for the servers we got. Most of
4922 our hardware are from Dell and HP, so I have focused on these servers
4923 so far. This blog post is about the Dell part.&lt;/P&gt;
4924
4925 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4926 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4927 with firmware information for all 11th generation servers, listing
4928 which firmware should be used on a given model and where on the FTP
4929 site I can find it. Using a simple perl XML parser I can then
4930 download the shell scripts Dell provides to do firmware upgrades from
4931 within Linux and reboot when all the firmware is primed and ready to
4932 be activated on the first reboot.&lt;/p&gt;
4933
4934 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4935 Are there anyone working on similar tools for firmware upgrading all
4936 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4937
4938 &lt;p&gt;&lt;pre&gt;
4939 #!/usr/bin/perl
4940 use strict;
4941 use warnings;
4942 use File::Temp qw(tempdir);
4943 BEGIN {
4944 # Install needed RHEL packages if missing
4945 my %rhelmodules = (
4946 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4947 );
4948 for my $module (keys %rhelmodules) {
4949 eval &quot;use $module;&quot;;
4950 if ($@) {
4951 my $pkg = $rhelmodules{$module};
4952 system(&quot;yum install -y $pkg&quot;);
4953 eval &quot;use $module;&quot;;
4954 }
4955 }
4956 }
4957 my $errorsto = &#39;pere@hungry.com&#39;;
4958
4959 upgrade_dell();
4960
4961 exit 0;
4962
4963 sub run_firmware_script {
4964 my ($opts, $script) = @_;
4965 unless ($script) {
4966 print STDERR &quot;fail: missing script name\n&quot;;
4967 exit 1
4968 }
4969 print STDERR &quot;Running $script\n\n&quot;;
4970
4971 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4972 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4973 } else {
4974 print STDERR &quot;fail: firmware script returned error\n&quot;;
4975 }
4976 }
4977
4978 sub run_firmware_scripts {
4979 my ($opts, @dirs) = @_;
4980 # Run firmware packages
4981 for my $dir (@dirs) {
4982 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4983 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4984 while (my $s = readdir $dh) {
4985 next if $s =~ m/^\.\.?/;
4986 run_firmware_script($opts, &quot;$dir/$s&quot;);
4987 }
4988 closedir $dh;
4989 }
4990 }
4991
4992 sub download {
4993 my $url = shift;
4994 print STDERR &quot;info: Downloading $url\n&quot;;
4995 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4996 }
4997
4998 sub upgrade_dell {
4999 my @dirs;
5000 my $product = `dmidecode -s system-product-name`;
5001 chomp $product;
5002
5003 if ($product =~ m/PowerEdge/) {
5004
5005 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5006 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
5007
5008 my $tmpdir = tempdir(
5009 CLEANUP =&gt; 1
5010 );
5011 chdir($tmpdir);
5012 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
5013 system(&#39;gunzip Catalog.xml.gz&#39;);
5014 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
5015 # -q is quiet, disabling interactivity and reducing console output
5016 my $fwopts = &quot;-q&quot;;
5017 if (@paths) {
5018 for my $url (@paths) {
5019 fetch_dell_fw($url);
5020 }
5021 run_firmware_scripts($fwopts, $tmpdir);
5022 } else {
5023 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5024 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5025 }
5026 chdir(&#39;/&#39;);
5027 } else {
5028 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5029 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5030 }
5031 }
5032
5033 sub fetch_dell_fw {
5034 my $path = shift;
5035 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
5036 download($url);
5037 }
5038
5039 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5040 # firmware packages to download from Dell. Only work for Linux
5041 # machines and 11th generation Dell servers.
5042 sub fetch_dell_fw_list {
5043 my $filename = shift;
5044
5045 my $product = `dmidecode -s system-product-name`;
5046 chomp $product;
5047 my ($mybrand, $mymodel) = split(/\s+/, $product);
5048
5049 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
5050
5051 my $xml = XMLin($filename);
5052 my @paths;
5053 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
5054 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
5055 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
5056 my $oscode;
5057 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
5058 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
5059 } else {
5060 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
5061 }
5062 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
5063 {
5064 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
5065 }
5066 }
5067 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
5068 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
5069
5070 # Drop application packages, only firmware and BIOS
5071 next if &#39;APAC&#39; eq $componenttype;
5072
5073 my $cpath = $component-&gt;{path};
5074 for my $path (@paths) {
5075 if ($cpath =~ m%/$path$%) {
5076 push(@paths, $cpath);
5077 }
5078 }
5079 }
5080 return @paths;
5081 }
5082 &lt;/pre&gt;
5083
5084 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5085 it could work on other platforms with some tweaking. Anyone know a
5086 index like Catalog.xml is available from HP for HP servers? At the
5087 moment I maintain a similar list manually and it is quickly getting
5088 outdated.&lt;/p&gt;
5089 </description>
5090 </item>
5091
5092 <item>
5093 <title>How is booting into runlevel 1 different from single user boots?</title>
5094 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5095 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5096 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5097 <description>&lt;p&gt;Wouter Verhelst have some
5098 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5099 comments and opinions&lt;/a&gt; on my blog post on
5100 &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
5101 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5102 &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
5103 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5104 small piece of his comment now, and though it best to address the
5105 misunderstanding he bring forward:&lt;/p&gt;
5106
5107 &lt;p&gt;&lt;blockquote&gt;
5108 Currently, a system admin has four options: [...] boot to a
5109 single-user system (by adding &#39;single&#39; to the kernel command line;
5110 this runs rcS and rc1 scripts)
5111 &lt;/blockquote&gt;&lt;/p&gt;
5112
5113 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5114 and booting into runlevel 1 is the same. I am not surprised he
5115 believe this, because it would make sense and is a quite sensible
5116 thing to believe. But because the boot in Debian is slightly broken,
5117 runlevel 1 do not work properly and it isn&#39;t the same as single user
5118 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5119 hard to explain.&lt;/p&gt;
5120
5121 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5122 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5123 executed in single user mode is sulogin. Single user mode is a boot
5124 state &quot;between&quot; the runlevels, and when booting into single user mode,
5125 only the scripts in /etc/rcS.d/ are executed before the init process
5126 enters the single user state. When switching to runlevel 1, the state
5127 is in fact not ending in runlevel 1, but it passes through runlevel 1
5128 and end up in the single user mode (see /etc/rc1.d/S03single, which
5129 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5130 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5131 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5132 mode).&lt;/p&gt;
5133
5134 &lt;p&gt;This summary might make it clearer. When booting for the first
5135 time into single user mode, the following commands are executed:
5136 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5137 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5138 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5139 trying to continue after visiting single user mode. Not all services
5140 are started again as they should, causing the machine to end up in an
5141 unpredicatble state. This is why Debian admins recommend rebooting
5142 after visiting single user mode.&lt;/p&gt;
5143
5144 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5145 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5146 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5147 stopped when passing through the scripts in /etc/rc1.d/, and not
5148 started again when switching away from runlevel 1 to the runlevels
5149 2-5. I believe the problem is best fixed by moving all the scripts
5150 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5151 functioning single user mode during boot.&lt;/p&gt;
5152
5153 &lt;p&gt;I have spent several years investigating the Debian boot system,
5154 and discovered this problem a few years ago. I suspect it originates
5155 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5156 </description>
5157 </item>
5158
5159 <item>
5160 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5161 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5162 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5163 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5164 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5165 are started from /etc/rcS.d/. In fact, there is a bite more of them
5166 than make sense, and this causes a few problems. What kind of
5167 problems, you might ask. There are at least two problems. The first
5168 is that it is not possible to recover a machine after switching to
5169 runlevel 1. One need to actually reboot to get the machine back to
5170 the expected state. The other is that single user boot will sometimes
5171 run into problems because some of the subsystems are activated before
5172 the root login is presented, causing problems when trying to recover a
5173 machine from a problem in that subsystem. A minor additional point is
5174 that moving more scripts out of rcS.d/ and into the other rc#.d/
5175 directories will increase the amount of scripts that can run in
5176 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5177
5178 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5179 scripts that _have_ to execute before the root login prompt is
5180 presented during a single user boot should go there. Everything else
5181 should go into the numeric runlevels. This means things like
5182 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5183 the numeric runlevels. Today in Debian, there are around 115 init.d
5184 scripts that are started from rcS.d/, and most of them should be moved
5185 out. Do your package have one of them? Please help us make single
5186 user and runlevel 1 better by moving it.&lt;/p&gt;
5187
5188 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5189 etc. should still be started from rcS.d/, but there is for example no
5190 need to have the network enabled before the single user login prompt
5191 is presented.&lt;/p&gt;
5192
5193 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5194 Debian systems working while scripts migrate and during upgrades, the
5195 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5196 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5197 and the next ones can only be moved when their dependencies have been
5198 moved first. This migration must be done sequentially while we ensure
5199 that the package system upgrade packages in the right order to keep
5200 the system state correct. This will require some coordination when it
5201 comes to network related packages, but most of the packages with
5202 scripts that should migrate do not have anything in rcS.d/ depending
5203 on them. Some packages have already been updated, like the sudo
5204 package, while others are still left to do. I wish I had time to work
5205 on this myself, but real live constrains make it unlikely that I will
5206 find time to push this forward.&lt;/p&gt;
5207 </description>
5208 </item>
5209
5210 <item>
5211 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5212 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5213 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5214 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5215 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5216 mentioned the issues I believe should be improved in Debian for its
5217 desktop to be useful for more people. The use case for this is my
5218 parents, which are currently running Kubuntu which solve the
5219 issues.&lt;/p&gt;
5220
5221 &lt;p&gt;I suspect these four missing features are not very hard to
5222 implement. After all, they are present in Ubuntu, so if we wanted to
5223 do this in Debian we would have a source.&lt;/p&gt;
5224
5225 &lt;ol&gt;
5226
5227 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5228 are new packages available for upgrades, a icon in the KDE status bar
5229 indicate this, and clicking on it will activate the simple upgrade
5230 tool to handle it. I have no problem guiding both of my parents
5231 through the process over the phone. If a kernel reboot is required,
5232 this too is indicated by the status bars and the upgrade tool. Last
5233 time I checked, nothing with the same features was working in KDE in
5234 Debian.&lt;/li&gt;
5235
5236 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5237 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5238 currently have a handler for, it will ask the user if the system
5239 should search for a package that would add support for this MIME type,
5240 and if the user say yes, the APT sources will be searched for packages
5241 advertising the MIME type in their control file (visible in the
5242 Packages file in the APT archive). If one or more packages are found,
5243 it is a simple click of the mouse to add support for the missing mime
5244 type. If the package require the user to accept some non-free
5245 license, this is explained to the user. The entire process make it
5246 more clear to the user why something do not work in the browser, and
5247 make the chances higher for the user to blame the web page authors and
5248 not the browser for any missing features.&lt;/li&gt;
5249
5250 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5251 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5252 it is not supporting, a dialog pop up asking the user if the system
5253 should search for a package that would add support for it. This
5254 happen with things like MP3, Windows Media or H.264. The selection
5255 and installation procedure is very similar to the Firefox browser
5256 plugin handling. This is as far as I know implemented using a
5257 gstreamer hook. The end result is that the user easily get access to
5258 the codecs that are present from the APT archives available, while
5259 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5260
5261 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5262 displaying a text/plain file in my Debian browser, it will propose to
5263 start emacs to show it. If I remember correctly, when doing the same
5264 in Kunbutu it show the file as a text file in the browser. At least I
5265 know Opera will show text files within the browser. I much prefer the
5266 latter behaviour.&lt;/li&gt;
5267
5268 &lt;/ol&gt;
5269
5270 &lt;p&gt;There are other nice features as well, like the simplified suite
5271 upgrader, but given that I am the one mostly doing the dist-upgrade,
5272 it do not matter much.&lt;/p&gt;
5273
5274 &lt;p&gt;I really hope we could get these features in place for the next
5275 Debian release. It would require the coordinated effort of several
5276 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5277 </description>
5278 </item>
5279
5280 <item>
5281 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5282 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5283 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5284 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5285 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5286 site is build on Debian/Squeeze, and this platform was chosen because
5287 I am most familiar with Debian (being a Debian Developer for around 10
5288 years) because it is the latest stable Debian release which should get
5289 security support for a few years.&lt;/p&gt;
5290
5291 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5292 that are missing in Debian at the moment. It would be great if these
5293 modules were added to the Debian archive, allowing anyone to set up
5294 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5295 in their own country using only Debian packages. The list of modules
5296 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5297 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5298 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5299 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5300 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5301 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5302 easier in the future.&lt;/p&gt;
5303
5304 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5305 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5306 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5307 with the responsibility of tracking security problems, which I really
5308 do not have time for.&lt;/p&gt;
5309 </description>
5310 </item>
5311
5312 <item>
5313 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5314 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5315 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5316 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5317 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5318 posts have been in Norwegian the last few weeks, so here is a short
5319 update in English.&lt;/p&gt;
5320
5321 &lt;p&gt;The kids still keep me too busy to get much free software work
5322 done, but I did manage to organise a project to get a Norwegian port
5323 of the British service
5324 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5325 and it has been running for a month now. The entire project has been
5326 organised by me and two others. Around Christmas we gathered sponsors
5327 to fund the development work. In January I drafted a contract with
5328 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5329 and in February the development took place. Most of it involved
5330 converting the source to use GPS coordinates instead of British
5331 easting/northing, and the resulting code should be a lot easier to get
5332 running in any country by now. The Norwegian
5333 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5334 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5335 source and the source for administrative borders in Norway, and
5336 support for this had to be added/fixed.&lt;/p&gt;
5337
5338 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5339 polishing the system before we announced it March 7th. The system is
5340 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5341 problem reports in a few weeks. Soon we hope to announce the Android
5342 and iPhone versions making it even easier to report problems with the
5343 public infrastructure.&lt;/p&gt;
5344
5345 &lt;p&gt;Perhaps something to consider for those of you in countries without
5346 such service?&lt;/p&gt;
5347 </description>
5348 </item>
5349
5350 <item>
5351 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5352 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5354 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5355 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5356 issues here at my work with the University of Oslo. My idea is that
5357 it should be possible to use the information about security issues
5358 available on the Internet, and check our locally
5359 maintained/distributed software against this information. It should
5360 allow us to verify that no known security issues are forgotten. The
5361 CVE database listing vulnerabilities seem like a great central point,
5362 and by using the package lists from Debian mapped to CVEs provided by
5363 the testing security team, I believed it should be possible to figure
5364 out which security holes were present in our free software
5365 collection.&lt;/p&gt;
5366
5367 &lt;p&gt;After reading up on the topic, it became obvious that the first
5368 building block is to be able to name software packages in a unique and
5369 consistent way across data sources. I considered several ways to do
5370 this, for example coming up with my own naming scheme like using URLs
5371 to project home pages or URLs to the Freshmeat entries, or using some
5372 existing naming scheme. And it seem like I am not the first one to
5373 come across this problem, as MITRE already proposed and implemented a
5374 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5375 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5376 software, hardware and other platform components. The CPE ids are
5377 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5378 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5379 issues for any CPE name. With this in place, all I need to do is to
5380 locate the CPE id for the software packages we use at the university.
5381 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5382 NVD entry if a CVE for the package exist).&lt;/p&gt;
5383
5384 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5385 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5386 check out, one could look up
5387 &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
5388 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5389 The most recent one is
5390 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5391 and at the bottom of the NVD page for this vulnerability the complete
5392 list of affected versions is provided.&lt;/p&gt;
5393
5394 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5395 for offline processing of issues. Using this dump, I&#39;ve written a
5396 small script taking a list of CPEs as input and list all CVEs
5397 affecting the packages represented by these CPEs. One give it CPEs
5398 with version numbers as specified above and get a list of open
5399 security issues out.&lt;/p&gt;
5400
5401 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5402 information need to be high. For that to happen, I believe as many as
5403 possible need to use and contribute to the NVD database. I notice
5404 RHEL is providing
5405 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5406 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5407 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5408
5409 &lt;p&gt;To get an idea about the quality for free software, I spent some
5410 time making it possible to compare the CVE database from Debian with
5411 the CVE database in NVD. The result look fairly good, but there are
5412 some inconsistencies in NVD (same software package having several
5413 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5414 Debian believe are affected by a CVE). Hope to find time to improve
5415 the quality of NVD, but that require being able to get in touch with
5416 someone maintaining it. So far my three emails with questions and
5417 corrections have not seen any reply, but I hope contact can be
5418 established soon.&lt;/p&gt;
5419
5420 &lt;p&gt;An interesting application for CPEs is cross platform package
5421 mapping. It would be useful to know which packages in for example
5422 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5423 this would be trivial if all linux distributions provided CPE entries
5424 for their packages.&lt;/p&gt;
5425 </description>
5426 </item>
5427
5428 <item>
5429 <title>Which module is loaded for a given PCI and USB device?</title>
5430 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5431 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5432 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5433 <description>&lt;p&gt;In the
5434 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5435 package in Debian, there is a script to report useful information
5436 about the running hardware for use when people report missing
5437 information. One part of this script that I find very useful when
5438 debugging hardware problems, is the part mapping loaded kernel module
5439 to the PCI device it claims. It allow me to quickly see if the kernel
5440 module I expect is driving the hardware I am struggling with. To see
5441 the output, make sure discover-data is installed and run
5442 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5443 one of my machines like this:&lt;/p&gt;
5444
5445 &lt;pre&gt;
5446 loaded modules:
5447 10de:03eb i2c_nforce2
5448 10de:03f1 ohci_hcd
5449 10de:03f2 ehci_hcd
5450 10de:03f0 snd_hda_intel
5451 10de:03ec pata_amd
5452 10de:03f6 sata_nv
5453 1022:1103 k8temp
5454 109e:036e bttv
5455 109e:0878 snd_bt87x
5456 11ab:4364 sky2
5457 &lt;/pre&gt;
5458
5459 &lt;p&gt;The code in question look like this, slightly modified for
5460 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5461
5462 &lt;pre&gt;
5463 if [ -d /sys/bus/pci/devices/ ] ; then
5464 echo loaded pci modules:
5465 (
5466 cd /sys/bus/pci/devices/
5467 for address in * ; do
5468 if [ -d &quot;$address/driver/module&quot; ] ; then
5469 module=`cd $address/driver/module ; pwd -P | xargs basename`
5470 if grep -q &quot;^$module &quot; /proc/modules ; then
5471 address=$(echo $address |sed s/0000://)
5472 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5473 echo &quot;$id $module&quot;
5474 fi
5475 fi
5476 done
5477 )
5478 echo
5479 fi
5480 &lt;/pre&gt;
5481
5482 &lt;p&gt;Similar code could be used to extract USB device module
5483 mappings:&lt;/p&gt;
5484
5485 &lt;pre&gt;
5486 if [ -d /sys/bus/usb/devices/ ] ; then
5487 echo loaded usb modules:
5488 (
5489 cd /sys/bus/usb/devices/
5490 for address in * ; do
5491 if [ -d &quot;$address/driver/module&quot; ] ; then
5492 module=`cd $address/driver/module ; pwd -P | xargs basename`
5493 if grep -q &quot;^$module &quot; /proc/modules ; then
5494 address=$(echo $address |sed s/0000://)
5495 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5496 if [ &quot;$id&quot; ] ; then
5497 echo &quot;$id $module&quot;
5498 fi
5499 fi
5500 fi
5501 done
5502 )
5503 echo
5504 fi
5505 &lt;/pre&gt;
5506
5507 &lt;p&gt;This might perhaps be something to include in other tools as
5508 well.&lt;/p&gt;
5509 </description>
5510 </item>
5511
5512 <item>
5513 <title>How to test if a laptop is working with Linux</title>
5514 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5516 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5517 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5518 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5519 batch of computers will work with Linux. Every year for the last few
5520 years the university have organised shared bid of a few thousand
5521 computers, and this year HP won the bid. Two different desktops and
5522 five different laptops are on the list this year. We in the UNIX
5523 group want to know which one of these computers work well with RHEL
5524 and Ubuntu, the two Linux distributions we currently handle at the
5525 university.&lt;/p&gt;
5526
5527 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5528 perhaps inspire others to test hardware as well. To test, I PXE
5529 install the OS version of choice, and log in as my normal user and run
5530 a few applications and plug in selected pieces of hardware. When
5531 something fail, I make a note about this in the test matrix and move
5532 on. If I have some spare time I try to report the bug to the OS
5533 vendor, but as I only have the machines for a short time, I rarely
5534 have the time to do this for all the problems I find.&lt;/p&gt;
5535
5536 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5537 I perform on a new model.&lt;/p&gt;
5538
5539 &lt;ul&gt;
5540
5541 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5542 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5543 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5544
5545 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5546 installation, X.org is working.&lt;/li&gt;
5547
5548 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5549 package mesa-utils on Ubuntu) and writing down the frames per second
5550 reported by the program.&lt;/li&gt;
5551
5552 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5553 logging in, and if I can hear this the test is successful. If there
5554 are several audio exits on the machine, I try them all and check if
5555 the Gnome/KDE audio mixer can control where to send the sound. I
5556 normally test this by playing
5557 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5558 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5559
5560 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5561 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5562
5563 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5564 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5565
5566 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5567 picture from the v4l device show up.&lt;/li&gt;
5568
5569 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5570 any bluetooth devices are discovered. In my office, I normally see a
5571 few.&lt;/li&gt;
5572
5573 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5574 memory modules lying around, and stick them in and see if Gnome/KDE
5575 notice this.&lt;/li&gt;
5576
5577 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5578 special button work, and if the laptop continue to work after
5579 resume.&lt;/li&gt;
5580
5581 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5582 adjusting background light, switching on/off external video output,
5583 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5584 laptop to laptop, so I just write down which are working and which are
5585 not.&lt;/li&gt;
5586
5587 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5588 acceleration sensors etc. I rarely test these, as I do not know how
5589 to quickly test if they are working or not, so I only document their
5590 existence.&lt;/li&gt;
5591
5592 &lt;/ul&gt;
5593
5594 &lt;p&gt;By now I suspect you are really curious what the test results are
5595 for the HP machines I am testing. I&#39;m not done yet, so I will report
5596 the test results later. For now I can report that HP 8100 Elite work
5597 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5598 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5599 can see, I have most machines left to test. One interesting
5600 observation is that Ubuntu Lucid has almost twice the frame rate than
5601 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5602 </description>
5603 </item>
5604
5605 <item>
5606 <title>Some thoughts on BitCoins</title>
5607 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5608 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5609 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5610 <description>&lt;p&gt;As I continue to explore
5611 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5612 what properties the system have, and how it will be affected by laws
5613 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5614
5615 &lt;p&gt;One interesting thing to note is that since the transactions are
5616 verified using a peer to peer network, all details about a transaction
5617 is known to everyone. This means that if a BitCoin address has been
5618 published like I did with mine in my initial post about BitCoin, it is
5619 possible for everyone to see how many BitCoins have been transfered to
5620 that address. There is even a web service to look at the details for
5621 all transactions. There I can see that my address
5622 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5623 have received 16.06 Bitcoin, the
5624 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5625 address of Simon Phipps have received 181.97 BitCoin and the address
5626 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5627 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5628 every one of you that donated bitcoins to support my activity. The
5629 fact that anyone can see how much money was transfered to a given
5630 address make it more obvious why the BitCoin community recommend to
5631 generate and hand out a new address for each transaction. I&#39;m told
5632 there is no way to track which addresses belong to a given person or
5633 organisation without the person or organisation revealing it
5634 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5635
5636 &lt;p&gt;In Norway, and in most other countries, there are laws and
5637 regulations limiting how much money one can transfer across the border
5638 without declaring it. There are money laundering, tax and accounting
5639 laws and regulations I would expect to apply to the use of BitCoin.
5640 If the Skolelinux foundation
5641 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5642 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5643 normal bank transfers like EFF is doing, how should this be accounted?
5644 Given that it is impossible to know if money can cross the border or
5645 not, should everything or nothing be declared? What exchange rate
5646 should be used when calculating taxes? Would receivers have to pay
5647 income tax if the foundation were to pay Skolelinux contributors in
5648 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5649
5650 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5651 accepted by a lot of users. It must be possible to get easy access to
5652 the currency (as a wage or using currency exchanges), and it must be
5653 easy to spend it. At the moment BitCoin seem fairly easy to get
5654 access to, but there are very few places to spend it. I am not really
5655 a regular user of any of the vendor types currently accepting BitCoin,
5656 so I wonder when my kind of shop would start accepting BitCoins. I
5657 would like to buy electronics, travels and subway tickets, not herbs
5658 and books. :) The currency is young, and this will improve over time
5659 if it become popular, but I suspect regular banks will start to lobby
5660 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5661 will claim it is helping fund terrorism and money laundering (which
5662 probably would be true, as is any currency in existence), but I
5663 believe the problems should be solved elsewhere and not by blaming
5664 currencies.&lt;/p&gt;
5665
5666 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5667 CPU intensive process that depend on a bit of luck as well (as one is
5668 competing against all the other miners currently spending CPU cycles
5669 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5670 BitCoin when this happen. Yesterday I came across the obvious way to
5671 join forces to increase ones changes of getting at least some coins,
5672 by coordinating the work on mining BitCoins across several machines
5673 and people, and sharing the result if one is lucky and get the 50
5674 BitCoins. Check out
5675 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5676 if this sounds interesting. I have not had time to try to set up a
5677 machine to participate there yet, but have seen that running on ones
5678 own for a few days have not yield any BitCoins througth mining
5679 yet.&lt;/p&gt;
5680
5681 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5682 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5683 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5684 it was interesting to read. The arguments presented seem to be
5685 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5686 </description>
5687 </item>
5688
5689 <item>
5690 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5691 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5692 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5693 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5694 <description>&lt;p&gt;With this weeks lawless
5695 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5696 attacks&lt;/a&gt; on Wikileak and
5697 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5698 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5699 not be trusted to handle money transactions.
5700 A blog post from
5701 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5702 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5703 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5704 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5705 some help from my friend to get it all running, and he even handed me
5706 some bitcoins to get started. I even donated a few bitcoins to Simon
5707 for helping me remember BitCoin.&lt;/p&gt;
5708
5709 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5710 crypto-currency, decentralised and handled using peer-to-peer
5711 networks. It allows anonymous transactions and prohibits central
5712 control over the transactions, making it impossible for governments
5713 and companies alike to block donations and other transactions. The
5714 source is free software, and while the key dependency wxWidgets 2.9
5715 for the graphical user interface is missing in Debian, the command
5716 line client builds just fine. Hopefully Jonas
5717 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5718 Debian&lt;/a&gt; soon.&lt;/p&gt;
5719
5720 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5721 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5722 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5723 currency &quot;stock&quot; markets where the exchange rate is decided. There
5724 are not many users so far, but the concept seems promising. If you
5725 want to get started and lack a friend with any bitcoins to spare,
5726 you can even get
5727 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5728 bitcoin at the time of writing). Use
5729 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5730 on the current exchange rates.&lt;/p&gt;
5731
5732 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5733 machines. If you want to support my activity, please send Bitcoin
5734 donations to the address
5735 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5736 </description>
5737 </item>
5738
5739 <item>
5740 <title>Why isn&#39;t Debian Edu using VLC?</title>
5741 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5742 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5743 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5744 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5745 presented, and the winner among the multimedia player were VLC.
5746 Personally, I like VLC, and it is my player of choice when I first try
5747 to play a video file or stream. Only if VLC fail will I drag out
5748 gmplayer to see if it can do better. The reason is mostly the failure
5749 model and trust. When VLC fail, it normally pop up a error message
5750 reporting the problem. When mplayer fail, it normally segfault or
5751 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5752
5753 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5754 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5755 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5756 plugin to play web videos seamlessly, and the VLC browser plugin is
5757 not very good. For example, it lack in-line control buttons, so there
5758 is no way for the user to pause the video. Also, when I
5759 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5760 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5761 failed on several video pages where mplayer based plugins worked. If
5762 the browser plugin for VLC was as good as the gecko-mediaplayer
5763 package (which uses mplayer), we would switch.&lt;/P&gt;
5764
5765 &lt;p&gt;While VLC is a good player, its user interface is slightly
5766 annoying. The most annoying feature is its inconsistent use of
5767 keyboard shortcuts. When the player is in full screen mode, its
5768 shortcuts are different from when it is playing the video in a window.
5769 For example, space only work as pause when in full screen mode. I
5770 wish it had consisten shortcuts and that space also would work when in
5771 window mode. Another nice shortcut in gmplayer is [enter] to restart
5772 the current video. It is very nice when playing short videos from the
5773 web and want to restart it when new people arrive to have a look at
5774 what is going on.&lt;/p&gt;
5775 </description>
5776 </item>
5777
5778 <item>
5779 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5780 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5781 <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>
5782 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5783 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5784 upgrade testing of the
5785 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5786 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5787 This seem like a very good idea, so I adjusted by test scripts and
5788 can now present the updated result from today:&lt;/p&gt;
5789
5790 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5791
5792 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5793
5794 &lt;blockquote&gt;&lt;p&gt;
5795 apache2.2-bin
5796 aptdaemon
5797 baobab
5798 binfmt-support
5799 browser-plugin-gnash
5800 cheese-common
5801 cli-common
5802 cups-pk-helper
5803 dmz-cursor-theme
5804 empathy
5805 empathy-common
5806 freedesktop-sound-theme
5807 freeglut3
5808 gconf-defaults-service
5809 gdm-themes
5810 gedit-plugins
5811 geoclue
5812 geoclue-hostip
5813 geoclue-localnet
5814 geoclue-manual
5815 geoclue-yahoo
5816 gnash
5817 gnash-common
5818 gnome
5819 gnome-backgrounds
5820 gnome-cards-data
5821 gnome-codec-install
5822 gnome-core
5823 gnome-desktop-environment
5824 gnome-disk-utility
5825 gnome-screenshot
5826 gnome-search-tool
5827 gnome-session-canberra
5828 gnome-system-log
5829 gnome-themes-extras
5830 gnome-themes-more
5831 gnome-user-share
5832 gstreamer0.10-fluendo-mp3
5833 gstreamer0.10-tools
5834 gtk2-engines
5835 gtk2-engines-pixbuf
5836 gtk2-engines-smooth
5837 hamster-applet
5838 libapache2-mod-dnssd
5839 libapr1
5840 libaprutil1
5841 libaprutil1-dbd-sqlite3
5842 libaprutil1-ldap
5843 libart2.0-cil
5844 libboost-date-time1.42.0
5845 libboost-python1.42.0
5846 libboost-thread1.42.0
5847 libchamplain-0.4-0
5848 libchamplain-gtk-0.4-0
5849 libcheese-gtk18
5850 libclutter-gtk-0.10-0
5851 libcryptui0
5852 libdiscid0
5853 libelf1
5854 libepc-1.0-2
5855 libepc-common
5856 libepc-ui-1.0-2
5857 libfreerdp-plugins-standard
5858 libfreerdp0
5859 libgconf2.0-cil
5860 libgdata-common
5861 libgdata7
5862 libgdu-gtk0
5863 libgee2
5864 libgeoclue0
5865 libgexiv2-0
5866 libgif4
5867 libglade2.0-cil
5868 libglib2.0-cil
5869 libgmime2.4-cil
5870 libgnome-vfs2.0-cil
5871 libgnome2.24-cil
5872 libgnomepanel2.24-cil
5873 libgpod-common
5874 libgpod4
5875 libgtk2.0-cil
5876 libgtkglext1
5877 libgtksourceview2.0-common
5878 libmono-addins-gui0.2-cil
5879 libmono-addins0.2-cil
5880 libmono-cairo2.0-cil
5881 libmono-corlib2.0-cil
5882 libmono-i18n-west2.0-cil
5883 libmono-posix2.0-cil
5884 libmono-security2.0-cil
5885 libmono-sharpzip2.84-cil
5886 libmono-system2.0-cil
5887 libmtp8
5888 libmusicbrainz3-6
5889 libndesk-dbus-glib1.0-cil
5890 libndesk-dbus1.0-cil
5891 libopal3.6.8
5892 libpolkit-gtk-1-0
5893 libpt2.6.7
5894 libpython2.6
5895 librpm1
5896 librpmio1
5897 libsdl1.2debian
5898 libsrtp0
5899 libssh-4
5900 libtelepathy-farsight0
5901 libtelepathy-glib0
5902 libtidy-0.99-0
5903 media-player-info
5904 mesa-utils
5905 mono-2.0-gac
5906 mono-gac
5907 mono-runtime
5908 nautilus-sendto
5909 nautilus-sendto-empathy
5910 p7zip-full
5911 pkg-config
5912 python-aptdaemon
5913 python-aptdaemon-gtk
5914 python-axiom
5915 python-beautifulsoup
5916 python-bugbuddy
5917 python-clientform
5918 python-coherence
5919 python-configobj
5920 python-crypto
5921 python-cupshelpers
5922 python-elementtree
5923 python-epsilon
5924 python-evolution
5925 python-feedparser
5926 python-gdata
5927 python-gdbm
5928 python-gst0.10
5929 python-gtkglext1
5930 python-gtksourceview2
5931 python-httplib2
5932 python-louie
5933 python-mako
5934 python-markupsafe
5935 python-mechanize
5936 python-nevow
5937 python-notify
5938 python-opengl
5939 python-openssl
5940 python-pam
5941 python-pkg-resources
5942 python-pyasn1
5943 python-pysqlite2
5944 python-rdflib
5945 python-serial
5946 python-tagpy
5947 python-twisted-bin
5948 python-twisted-conch
5949 python-twisted-core
5950 python-twisted-web
5951 python-utidylib
5952 python-webkit
5953 python-xdg
5954 python-zope.interface
5955 remmina
5956 remmina-plugin-data
5957 remmina-plugin-rdp
5958 remmina-plugin-vnc
5959 rhythmbox-plugin-cdrecorder
5960 rhythmbox-plugins
5961 rpm-common
5962 rpm2cpio
5963 seahorse-plugins
5964 shotwell
5965 software-center
5966 system-config-printer-udev
5967 telepathy-gabble
5968 telepathy-mission-control-5
5969 telepathy-salut
5970 tomboy
5971 totem
5972 totem-coherence
5973 totem-mozilla
5974 totem-plugins
5975 transmission-common
5976 xdg-user-dirs
5977 xdg-user-dirs-gtk
5978 xserver-xephyr
5979 &lt;/p&gt;&lt;/blockquote&gt;
5980
5981 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5982
5983 &lt;blockquote&gt;&lt;p&gt;
5984 cheese
5985 ekiga
5986 eog
5987 epiphany-extensions
5988 evolution-exchange
5989 fast-user-switch-applet
5990 file-roller
5991 gcalctool
5992 gconf-editor
5993 gdm
5994 gedit
5995 gedit-common
5996 gnome-games
5997 gnome-games-data
5998 gnome-nettool
5999 gnome-system-tools
6000 gnome-themes
6001 gnuchess
6002 gucharmap
6003 guile-1.8-libs
6004 libavahi-ui0
6005 libdmx1
6006 libgalago3
6007 libgtk-vnc-1.0-0
6008 libgtksourceview2.0-0
6009 liblircclient0
6010 libsdl1.2debian-alsa
6011 libspeexdsp1
6012 libsvga1
6013 rhythmbox
6014 seahorse
6015 sound-juicer
6016 system-config-printer
6017 totem-common
6018 transmission-gtk
6019 vinagre
6020 vino
6021 &lt;/p&gt;&lt;/blockquote&gt;
6022
6023 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6024
6025 &lt;blockquote&gt;&lt;p&gt;
6026 gstreamer0.10-gnomevfs
6027 &lt;/p&gt;&lt;/blockquote&gt;
6028
6029 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6030
6031 &lt;blockquote&gt;&lt;p&gt;
6032 [nothing]
6033 &lt;/p&gt;&lt;/blockquote&gt;
6034
6035 &lt;p&gt;This is for KDE:&lt;/p&gt;
6036
6037 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6038
6039 &lt;blockquote&gt;&lt;p&gt;
6040 ksmserver
6041 &lt;/p&gt;&lt;/blockquote&gt;
6042
6043 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6044
6045 &lt;blockquote&gt;&lt;p&gt;
6046 kwin
6047 network-manager-kde
6048 &lt;/p&gt;&lt;/blockquote&gt;
6049
6050 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6051
6052 &lt;blockquote&gt;&lt;p&gt;
6053 arts
6054 dolphin
6055 freespacenotifier
6056 google-gadgets-gst
6057 google-gadgets-xul
6058 kappfinder
6059 kcalc
6060 kcharselect
6061 kde-core
6062 kde-plasma-desktop
6063 kde-standard
6064 kde-window-manager
6065 kdeartwork
6066 kdeartwork-emoticons
6067 kdeartwork-style
6068 kdeartwork-theme-icon
6069 kdebase
6070 kdebase-apps
6071 kdebase-workspace
6072 kdebase-workspace-bin
6073 kdebase-workspace-data
6074 kdeeject
6075 kdelibs
6076 kdeplasma-addons
6077 kdeutils
6078 kdewallpapers
6079 kdf
6080 kfloppy
6081 kgpg
6082 khelpcenter4
6083 kinfocenter
6084 konq-plugins-l10n
6085 konqueror-nsplugins
6086 kscreensaver
6087 kscreensaver-xsavers
6088 ktimer
6089 kwrite
6090 libgle3
6091 libkde4-ruby1.8
6092 libkonq5
6093 libkonq5-templates
6094 libnetpbm10
6095 libplasma-ruby
6096 libplasma-ruby1.8
6097 libqt4-ruby1.8
6098 marble-data
6099 marble-plugins
6100 netpbm
6101 nuvola-icon-theme
6102 plasma-dataengines-workspace
6103 plasma-desktop
6104 plasma-desktopthemes-artwork
6105 plasma-runners-addons
6106 plasma-scriptengine-googlegadgets
6107 plasma-scriptengine-python
6108 plasma-scriptengine-qedje
6109 plasma-scriptengine-ruby
6110 plasma-scriptengine-webkit
6111 plasma-scriptengines
6112 plasma-wallpapers-addons
6113 plasma-widget-folderview
6114 plasma-widget-networkmanagement
6115 ruby
6116 sweeper
6117 update-notifier-kde
6118 xscreensaver-data-extra
6119 xscreensaver-gl
6120 xscreensaver-gl-extra
6121 xscreensaver-screensaver-bsod
6122 &lt;/p&gt;&lt;/blockquote&gt;
6123
6124 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6125
6126 &lt;blockquote&gt;&lt;p&gt;
6127 ark
6128 google-gadgets-common
6129 google-gadgets-qt
6130 htdig
6131 kate
6132 kdebase-bin
6133 kdebase-data
6134 kdepasswd
6135 kfind
6136 klipper
6137 konq-plugins
6138 konqueror
6139 ksysguard
6140 ksysguardd
6141 libarchive1
6142 libcln6
6143 libeet1
6144 libeina-svn-06
6145 libggadget-1.0-0b
6146 libggadget-qt-1.0-0b
6147 libgps19
6148 libkdecorations4
6149 libkephal4
6150 libkonq4
6151 libkonqsidebarplugin4a
6152 libkscreensaver5
6153 libksgrd4
6154 libksignalplotter4
6155 libkunitconversion4
6156 libkwineffects1a
6157 libmarblewidget4
6158 libntrack-qt4-1
6159 libntrack0
6160 libplasma-geolocation-interface4
6161 libplasmaclock4a
6162 libplasmagenericshell4
6163 libprocesscore4a
6164 libprocessui4a
6165 libqalculate5
6166 libqedje0a
6167 libqtruby4shared2
6168 libqzion0a
6169 libruby1.8
6170 libscim8c2a
6171 libsmokekdecore4-3
6172 libsmokekdeui4-3
6173 libsmokekfile3
6174 libsmokekhtml3
6175 libsmokekio3
6176 libsmokeknewstuff2-3
6177 libsmokeknewstuff3-3
6178 libsmokekparts3
6179 libsmokektexteditor3
6180 libsmokekutils3
6181 libsmokenepomuk3
6182 libsmokephonon3
6183 libsmokeplasma3
6184 libsmokeqtcore4-3
6185 libsmokeqtdbus4-3
6186 libsmokeqtgui4-3
6187 libsmokeqtnetwork4-3
6188 libsmokeqtopengl4-3
6189 libsmokeqtscript4-3
6190 libsmokeqtsql4-3
6191 libsmokeqtsvg4-3
6192 libsmokeqttest4-3
6193 libsmokeqtuitools4-3
6194 libsmokeqtwebkit4-3
6195 libsmokeqtxml4-3
6196 libsmokesolid3
6197 libsmokesoprano3
6198 libtaskmanager4a
6199 libtidy-0.99-0
6200 libweather-ion4a
6201 libxklavier16
6202 libxxf86misc1
6203 okteta
6204 oxygencursors
6205 plasma-dataengines-addons
6206 plasma-scriptengine-superkaramba
6207 plasma-widget-lancelot
6208 plasma-widgets-addons
6209 plasma-widgets-workspace
6210 polkit-kde-1
6211 ruby1.8
6212 systemsettings
6213 update-notifier-common
6214 &lt;/p&gt;&lt;/blockquote&gt;
6215
6216 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6217 aptitude a bit more similar, but there are still quite a lott of
6218 differences. I have no idea what packages should be installed after
6219 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6220 </description>
6221 </item>
6222
6223 <item>
6224 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6225 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6226 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6227 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6228 <description>&lt;p&gt;Most of the computers in use by the
6229 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6230 are virtual machines. And they have been Xen machines running on a
6231 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6232 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6233 bit harder that it could have been, because we set up the Xen virtual
6234 machines to get the virtual partitions from LVM, which as far as I
6235 know is not supported by KVM. So to migrate, we had to convert
6236 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6237
6238 &lt;p&gt;I found
6239 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6240 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6241 migration. It uses qemu-img from the qemu package to make the disk
6242 image, parted to partition it, losetup and kpartx to present the disk
6243 image partions as devices, and dd to copy the data. I NFS mounted the
6244 new servers storage area on the old server to do the migration.&lt;/p&gt;
6245
6246 &lt;pre&gt;
6247 #!/bin/sh
6248
6249 # Based on
6250 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6251
6252 set -e
6253 set -x
6254
6255 if [ -z &quot;$1&quot; ] ; then
6256 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6257 exit 1
6258 else
6259 host=&quot;$1&quot;
6260 fi
6261
6262 if [ ! -e /dev/vg_data/$host-disk ] ; then
6263 echo &quot;error: unable to find LVM volume for $host&quot;
6264 exit 1
6265 fi
6266
6267 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6268 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6269 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6270 totalsize=$(( ( $disksize + $swapsize ) ))
6271
6272 img=$host.img
6273 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6274 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6275
6276 parted $img mklabel msdos
6277 parted $img mkpart primary linux-swap 0 $disksize
6278 parted $img mkpart primary ext2 $disksize $totalsize
6279 parted $img set 1 boot on
6280
6281 modprobe dm-mod
6282 losetup /dev/loop0 $img
6283 kpartx -a /dev/loop0
6284
6285 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6286 fsck.ext3 -f /dev/mapper/loop0p1 || true
6287 mkswap /dev/mapper/loop0p2
6288
6289 kpartx -d /dev/loop0
6290 losetup -d /dev/loop0
6291 &lt;/pre&gt;
6292
6293 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6294 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6295
6296 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6297 the new disk image attached, installed grub-pc and linux-image-686 and
6298 set up grub to boot from the disk image. After this, the KVM machines
6299 seem to work just fine.&lt;/p&gt;
6300 </description>
6301 </item>
6302
6303 <item>
6304 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6305 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6306 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6307 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6308 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6309 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6310 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6311 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6312
6313 &lt;p&gt;I still do not know what a correct migration should look like, so I
6314 report any differences between apt and aptitude and hope someone else
6315 can see if anything should be changed.&lt;/p&gt;
6316
6317 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6318
6319 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6320
6321 &lt;blockquote&gt;&lt;p&gt;
6322 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6323 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6324 dmz-cursor-theme empathy empathy-common finger
6325 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6326 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6327 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6328 gnome-cards-data gnome-codec-install gnome-core
6329 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6330 gnome-search-tool gnome-session-canberra gnome-spell
6331 gnome-system-log gnome-themes-extras gnome-themes-more
6332 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6333 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6334 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6335 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6336 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6337 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6338 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6339 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6340 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6341 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6342 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6343 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6344 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6345 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6346 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6347 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6348 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6349 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6350 libmono-security2.0-cil libmono-sharpzip2.84-cil
6351 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6352 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6353 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6354 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6355 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6356 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6357 libxalan2-java libxerces2-java media-player-info mesa-utils
6358 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6359 nautilus-sendto-empathy openoffice.org-writer2latex
6360 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6361 python-aptdaemon python-aptdaemon-gtk python-axiom
6362 python-beautifulsoup python-bugbuddy python-clientform
6363 python-coherence python-configobj python-crypto python-cupshelpers
6364 python-cupsutils python-eggtrayicon python-elementtree
6365 python-epsilon python-evolution python-feedparser python-gdata
6366 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6367 python-gtksourceview2 python-httplib2 python-louie python-mako
6368 python-markupsafe python-mechanize python-nevow python-notify
6369 python-opengl python-openssl python-pam python-pkg-resources
6370 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6371 python-tagpy python-twisted-bin python-twisted-conch
6372 python-twisted-core python-twisted-web python-utidylib python-webkit
6373 python-xdg python-zope.interface remmina remmina-plugin-data
6374 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6375 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6376 software-center svgalibg1 system-config-printer-udev
6377 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6378 totem totem-coherence totem-mozilla totem-plugins
6379 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6380 zip
6381 &lt;/p&gt;&lt;/blockquote&gt;
6382
6383 Installed using apt-get, removed with aptitude
6384
6385 &lt;blockquote&gt;&lt;p&gt;
6386 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6387 epiphany-extensions epiphany-gecko evolution-exchange
6388 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6389 gedit-common gnome-app-install gnome-games gnome-games-data
6390 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6391 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6392 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6393 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6394 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6395 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6396 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6397 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6398 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6399 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6400 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6401 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6402 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6403 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6404 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6405 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6406 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6407 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6408 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6409 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6410 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6411 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6412 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6413 sound-juicer swfdec-gnome system-config-printer totem-common
6414 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6415 &lt;/p&gt;&lt;/blockquote&gt;
6416
6417 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6418
6419 &lt;blockquote&gt;&lt;p&gt;
6420 gstreamer0.10-gnomevfs
6421 &lt;/p&gt;&lt;/blockquote&gt;
6422
6423 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6424
6425 &lt;blockquote&gt;&lt;p&gt;
6426 [nothing]
6427 &lt;/p&gt;&lt;/blockquote&gt;
6428
6429 &lt;p&gt;This is for KDE:&lt;/p&gt;
6430
6431 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6432
6433 &lt;blockquote&gt;&lt;p&gt;
6434 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6435 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6436 ghostscript-x git gnome-audio gnugo granatier gs-common
6437 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6438 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6439 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6440 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6441 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6442 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6443 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6444 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6445 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6446 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6447 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6448 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6449 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6450 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6451 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6452 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6453 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6454 libkrossui4 libmailtools-perl libmime-tools-perl
6455 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6456 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6457 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6458 lirc luatex marble networkstatus noatun-plugins
6459 openoffice.org-writer2latex palapeli palapeli-data parley
6460 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6461 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6462 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6463 ttf-sazanami-gothic
6464 &lt;/p&gt;&lt;/blockquote&gt;
6465
6466 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6467
6468 &lt;blockquote&gt;&lt;p&gt;
6469 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6470 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6471 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6472 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6473 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6474 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6475 kitchensync kiten kjumpingcube klatin klettres klickety klines
6476 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6477 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6478 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6479 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6480 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6481 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6482 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6483 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6484 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6485 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6486 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6487 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6488 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6489 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6490 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6491 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6492 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6493 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6494 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6495 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6496 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6497 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6498 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6499 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6500 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6501 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6502 &lt;/p&gt;&lt;/blockquote&gt;
6503
6504 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6505
6506 &lt;blockquote&gt;&lt;p&gt;
6507 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6508 kdeartwork kdebase kdebase-apps kdebase-workspace
6509 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6510 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6511 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6512 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6513 xscreensaver-screensaver-bsod
6514 &lt;/p&gt;&lt;/blockquote&gt;
6515
6516 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6517
6518 &lt;blockquote&gt;&lt;p&gt;
6519 kdebase-bin konq-plugins konqueror
6520 &lt;/p&gt;&lt;/blockquote&gt;
6521 </description>
6522 </item>
6523
6524 <item>
6525 <title>Gnash buildbot slave and Debian kfreebsd</title>
6526 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6527 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6528 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6529 <description>&lt;p&gt;Answering
6530 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6531 call from the Gnash project&lt;/a&gt; for
6532 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6533 current source, I have set up a virtual KVM machine on the Debian
6534 Edu/Skolelinux virtualization host to test the git source on
6535 Debian/Squeeze. I hope this can help the developers in getting new
6536 releases out more often.&lt;/p&gt;
6537
6538 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6539 I have considered setting up a &lt;a
6540 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6541 machine as well. I have also considered using the kfreebsd
6542 architecture in Debian as a file server in NUUG to get access to the 5
6543 TB zfs volume we currently use to store DV video. Because of this, I
6544 finally got around to do a test installation of Debian/Squeeze with
6545 kfreebsd. Installation went fairly smooth, thought I noticed some
6546 visual glitches in the cdebconf dialogs (black cursor left on the
6547 screen at random locations). Have not gotten very far with the
6548 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6549 fatal problem. Have to spend some more time on it to see if it is
6550 useful as a file server for NUUG. Will try to find time to set up a
6551 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6552 </description>
6553 </item>
6554
6555 <item>
6556 <title>Debian in 3D</title>
6557 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6558 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6559 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6560 <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;
6561
6562 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6563 3D linked in from
6564 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6565 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6566 </description>
6567 </item>
6568
6569 <item>
6570 <title>Software updates 2010-10-24</title>
6571 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6572 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6573 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6574 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6575
6576 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6577 raise money for the project is going well. The lower limit of 10
6578 signers was reached in 24 hours, and so far 13 people have signed it.
6579 More signers and more funding is most welcome, and I am really curious
6580 how far we can get before the time limit of December 24 is reached.
6581 :)&lt;/p&gt;
6582
6583 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6584 about what appear to be a great code coverage tool capable of
6585 generating code coverage stats without any changes to the source code.
6586 It is called
6587 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6588 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6589 It is missing in Debian, but the git source built just fine in Squeeze
6590 after I installed libelf-dev, libdwarf-dev, pkg-config and
6591 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6592 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6593
6594 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6595 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6596 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6597 alpha test release of the Squeeze based Debian Edu /
6598 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6599 release. Give it a try if you need a complete linux solution for your
6600 school, including central infrastructure server, workstations, thin
6601 client servers and diskless workstations. A nice touch added
6602 yesterday is RDP support on the thin client servers, for windows
6603 clients to get a Linux desktop on request.&lt;/p&gt;
6604 </description>
6605 </item>
6606
6607 <item>
6608 <title>Some notes on Flash in Debian and Debian Edu</title>
6609 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6610 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6611 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6612 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6613 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6614 second most popular used package that is missing in Debian. The sixth
6615 most popular is flashplayer-mozilla. This is a clear indication that
6616 working flash is important for Debian users. Around 10 percent of the
6617 users submitting data to popcon.debian.org have this package
6618 installed.&lt;/p&gt;
6619
6620 &lt;p&gt;In the report written by Lars Risan in August 2008
6621&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
6622 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6623 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6624 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6625 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6626 web sites require Flash to work, and lacking working Flash support in
6627 the web browser and the problems with installing it was perceived as a
6628 good reason to stay with Windows.&lt;/p&gt;
6629
6630 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6631 said to be the retarded cousin that did not really understand
6632 everything you told him but could work fairly well. This was a
6633 comment regarding the problems Linux have with proprietary formats and
6634 non-standard web pages, and is sad because it exposes a fairly common
6635 understanding of whose fault it is if web pages that only work in for
6636 example Internet Explorer 6 fail to work on Firefox, and funny because
6637 it explain very well how annoying it is for users when Linux
6638 distributions do not work with the documents they receive or the web
6639 pages they want to visit.&lt;/p&gt;
6640
6641 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6642 and Debian Edu to have a well working Flash implementation in the
6643 distribution, to get at least popular sites as Youtube and Google
6644 Video to working out of the box. For Squeeze, Debian have the chance
6645 to include the latest version of Gnash that will make this happen, as
6646 the new release 0.8.8 was published a few weeks ago and is resting in
6647 unstable. The new version work with more sites that version 0.8.7.
6648 The Gnash maintainers have asked for a freeze exception, but the
6649 release team have not had time to reply to it yet. I hope they agree
6650 with me that Flash is important for the Debian desktop users, and thus
6651 accept the new package into Squeeze.&lt;/p&gt;
6652 </description>
6653 </item>
6654
6655 <item>
6656 <title>Circular package dependencies harms apt recovery</title>
6657 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6658 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6659 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6660 <description>&lt;p&gt;I discovered this while doing
6661 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6662 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6663 in Debian still got circular dependencies, and it is often claimed
6664 that apt and aptitude should be able to handle this just fine, but
6665 some times these dependency loops causes apt to fail.&lt;/p&gt;
6666
6667 &lt;p&gt;An example is from todays
6668 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6669 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6670 causes perl-modules to fail to upgrade. The cause is simple. If a
6671 package fail to unpack, then only part of packages with the circular
6672 dependency might end up being unpacked when unpacking aborts, and the
6673 ones already unpacked will fail to configure in the recovery phase
6674 because its dependencies are unavailable.&lt;/p&gt;
6675
6676 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6677
6678 &lt;blockquote&gt;&lt;pre&gt;
6679 dpkg: dependency problems prevent configuration of perl-modules:
6680 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6681 Version of perl on system is 5.10.0-19lenny2.
6682 dpkg: error processing perl-modules (--configure):
6683 dependency problems - leaving unconfigured
6684 &lt;/pre&gt;&lt;/blockquote&gt;
6685
6686 &lt;p&gt;The perl/perl-modules circular dependency is already
6687 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6688 hopefully be solved as soon as possible, but it is not the only one,
6689 and each one of these loops in the dependency tree can cause similar
6690 failures. Of course, they only occur when there are bugs in other
6691 packages causing the unpacking to fail, but it is rather nasty when
6692 the failure of one package causes the problem to become worse because
6693 of dependency loops.&lt;/p&gt;
6694
6695 &lt;p&gt;Thanks to
6696 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6697 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6698 dependencies
6699 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6700 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6701
6702 &lt;p&gt;Todays testing also exposed a bug in
6703 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6704 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6705 apt-get and aptitude, the latter possibly caused by some circular
6706 dependency. Reported both to BTS to try to get someone to look at
6707 it.&lt;/p&gt;
6708 </description>
6709 </item>
6710
6711 <item>
6712 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6713 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6714 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6715 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6716 <description>&lt;p&gt;This is a
6717 &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;
6718 on my
6719 &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
6720 work&lt;/a&gt; on
6721 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6722 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6723
6724 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6725 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6726 and dhcp3-server-ldap in Debian use the LDAP server. The two
6727 implementations are quite different in how they use LDAP.&lt;/p&gt;
6728
6729 To get this information, I started slapd with debugging enabled and
6730 dumped the debug output to a file to get the LDAP searches performed
6731 on a Debian Edu main-server. Here is a summary.
6732
6733 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6734
6735 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6736 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6737 the web.
6738
6739 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6740 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6741 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6742 reverse entries are in two different subtrees in LDAP with a structure
6743 based on the DNS names, as in tjener.intern and
6744 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6745
6746 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6747 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6748 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6749 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6750 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6751 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6752 forward entries, it is looking for attributes named dnsttl, arecord,
6753 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6754 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6755 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6756 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6757 spfrecord and modifytimestamp. For reverse entries it is looking for
6758 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6759 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6760 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6761 ldapsearch commands could look like this:&lt;/p&gt;
6762
6763 &lt;blockquote&gt;&lt;pre&gt;
6764 ldapsearch -h ldap \
6765 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6766 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6767 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6768 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6769 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6770 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6771
6772 ldapsearch -h ldap \
6773 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6774 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6775 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6776 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6777 srvrecord naptrrecord modifytimestamp
6778 &lt;/pre&gt;&lt;/blockquote&gt;
6779
6780 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6781 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6782 example LDAP objects used there. In addition to these objects, the
6783 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6784 also exist.&lt;/p&gt;
6785
6786 &lt;blockquote&gt;&lt;pre&gt;
6787 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6788 objectclass: top
6789 objectclass: dnsdomain
6790 objectclass: domainrelatedobject
6791 dc: tjener
6792 arecord: 10.0.2.2
6793 associateddomain: tjener.intern
6794
6795 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6796 objectclass: top
6797 objectclass: dnsdomain2
6798 objectclass: domainrelatedobject
6799 dc: 2
6800 ptrrecord: tjener.intern
6801 associateddomain: 2.2.0.10.in-addr.arpa
6802 &lt;/pre&gt;&lt;/blockquote&gt;
6803
6804 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6805 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6806 same base as in the tree mode for a object with filter
6807 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6808 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6809 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6810 naptrrecord and modifytimestamp. For reverse entires it also do a
6811 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6812 and the requested attributes are associateddomain, dnsttl and
6813 modifytimestamp. In short, in strict mode the objects with ptrrecord
6814 go away, and the arecord attribute in the forward object is used
6815 instead.&lt;/p&gt;
6816
6817 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6818 like this:&lt;/p&gt;
6819
6820 &lt;blockquote&gt;&lt;pre&gt;
6821 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6822 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6823 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6824 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6825 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6826 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6827
6828 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6829 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6830 &lt;/pre&gt;&lt;/blockquote&gt;
6831
6832 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6833 search for SOA records, which behave similar to the forward and
6834 reverse lookups.&lt;/p&gt;
6835
6836 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6837 specify any objectclass names, and instead look for the attributes it
6838 need to generate a DNS reply. This make it able to work with any
6839 objectclass that provide the needed attributes.&lt;/p&gt;
6840
6841 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6842 dnsdomain2 schemas. The latter is used for reverse entries like
6843 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6844
6845 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6846 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6847 attributes) and domainrelatedobject (for associatedDomain). The use
6848 of structural object classes make it impossible to combine these
6849 classes with the object classes used by DHCP.&lt;/p&gt;
6850
6851 &lt;p&gt;There are other schemas that could be used too, for example the
6852 dnszone structural object class used by Gosa and bind-sdb for the DNS
6853 attributes combined with the domainrelatedobject object class, but in
6854 this case some unused attributes would have to be included as well
6855 (zonename and relativedomainname).&lt;/p&gt;
6856
6857 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6858 mode and not use any of the existing objectclasses (dnsdomain,
6859 dnsdomain2 and dnszone) when one want to combine the DNS information
6860 with DHCP information, and instead create a auxiliary object class
6861 defined something like this (using the attributes defined for
6862 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6863
6864 &lt;blockquote&gt;&lt;pre&gt;
6865 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6866 SUP top
6867 AUXILIARY
6868 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6869 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6870 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6871 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6872 A6Record $ DNAMERecord
6873 ))
6874 &lt;/pre&gt;&lt;/blockquote&gt;
6875
6876 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6877 the domainrelatedobject object class, and allow any entity to include
6878 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6879 developers asking for their view on this schema and if they are
6880 interested in providing such schema with PowerDNS, and I hope my
6881 message will be accepted into their mailing list soon.&lt;/p&gt;
6882
6883 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6884
6885 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6886 the object attributes, and then uses the attributes it want. This
6887 make it harder to figure out exactly what attributes are used, but
6888 thanks to the working example in Debian Edu I can at least get an idea
6889 what is needed without having to read the source code.&lt;/p&gt;
6890
6891 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6892 search filter to use to locate the correct dhcpServer entity is
6893 stored. These are the relevant entries from
6894 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6895
6896 &lt;blockquote&gt;&lt;pre&gt;
6897 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6898 ldap-dhcp-server-cn &quot;dhcp&quot;;
6899 &lt;/pre&gt;&lt;/blockquote&gt;
6900
6901 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6902 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6903 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6904 search result is this entry:&lt;/p&gt;
6905
6906 &lt;blockquote&gt;&lt;pre&gt;
6907 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6908 cn: dhcp
6909 objectClass: top
6910 objectClass: dhcpServer
6911 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6912 &lt;/pre&gt;&lt;/blockquote&gt;
6913
6914 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6915 subtree with DHCP configuration. The DHCP configuration subtree base
6916 is located using a base scope search with base &quot;cn=DHCP
6917 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6918 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6919 The search result is this entry:&lt;/p&gt;
6920
6921 &lt;blockquote&gt;&lt;pre&gt;
6922 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6923 cn: DHCP Config
6924 objectClass: top
6925 objectClass: dhcpService
6926 objectClass: dhcpOptions
6927 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6928 dhcpStatements: ddns-update-style none
6929 dhcpStatements: authoritative
6930 dhcpOption: smtp-server code 69 = array of ip-address
6931 dhcpOption: www-server code 72 = array of ip-address
6932 dhcpOption: wpad-url code 252 = text
6933 &lt;/pre&gt;&lt;/blockquote&gt;
6934
6935 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6936 all the DHCP configuration is loaded, it is ready to receive requests.
6937 The subtree in Debian Edu contain objects with object classes
6938 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6939 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6940 and information about netmasks, dynamic range etc. Leaving out the
6941 details here because it is not relevant for the focus of my
6942 investigation, which is to see if it is possible to merge dns and dhcp
6943 related computer objects.&lt;/p&gt;
6944
6945 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6946 of the client (00:00:00:00:00:00 in this example), using a subtree
6947 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6948 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6949 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6950 like:&lt;/p&gt;
6951
6952 &lt;blockquote&gt;&lt;pre&gt;
6953 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6954 cn: hostname
6955 objectClass: top
6956 objectClass: dhcpHost
6957 dhcpHWAddress: ethernet 00:00:00:00:00:00
6958 dhcpStatements: fixed-address hostname
6959 &lt;/pre&gt;&lt;/blockquote&gt;
6960
6961 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6962 The object classes need to have fixed names, and the configuration
6963 need to be stored in a fairly specific LDAP structure. On the
6964 positive side, the invidiual dhcpHost entires can be anywhere without
6965 the DN pointed to by the dhcpServer entries. The latter should make
6966 it possible to group all host entries in a subtree next to the
6967 configuration entries, and this subtree can also be shared with the
6968 DNS server if the schema proposed above is combined with the dhcpHost
6969 structural object class.
6970
6971 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6972
6973 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6974 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6975 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6976 allowing DNS objects to be stored anywhere under the base cn specified
6977 in the configuration.&lt;/p&gt;
6978
6979 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6980 regarding which LDAP schemas to use and which LDAP structure to use.
6981 I guess one could implement ones own schema, as long as the
6982 objectclasses and attributes have the names used, but this do not
6983 really help when the DHCP subtree need to have a fairly fixed
6984 structure.&lt;/p&gt;
6985
6986 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6987 this might work for Debian Edu:&lt;/p&gt;
6988
6989 &lt;blockquote&gt;&lt;pre&gt;
6990 ou=services
6991 cn=machine-info (dhcpService) - dhcpServiceDN points here
6992 cn=dhcp (dhcpServer)
6993 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6994 cn=10.0.2.0 (dhcpSubnet)
6995 cn=group1 (dhcpGroup/dhcpOptions)
6996 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6997 cn=192.168.0.0 (dhcpSubnet)
6998 cn=group1 (dhcpGroup/dhcpOptions)
6999 ou=machines - PowerDNS base points here
7000 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7001 &lt;/pre&gt;&lt;/blockquote&gt;
7002
7003 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
7004 entries to be in the dhcpGroup subtrees, the entries can be stored
7005 there instead of a common machines subtree, and the PowerDNS base
7006 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
7007
7008 &lt;p&gt;The combined object under the machines subtree would look something
7009 like this:&lt;/p&gt;
7010
7011 &lt;blockquote&gt;&lt;pre&gt;
7012 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7013 dc: hostname
7014 objectClass: top
7015 objectClass: dhcpHost
7016 objectclass: domainrelatedobject
7017 objectclass: dnsDomainAux
7018 associateddomain: hostname.intern
7019 arecord: 10.11.12.13
7020 dhcpHWAddress: ethernet 00:00:00:00:00:00
7021 dhcpStatements: fixed-address hostname.intern
7022 &lt;/pre&gt;&lt;/blockquote&gt;
7023
7024 &lt;/p&gt;One could even add the LTSP configuration associated with a given
7025 machine, as long as the required attributes are available in a
7026 auxiliary object class.&lt;/p&gt;
7027 </description>
7028 </item>
7029
7030 <item>
7031 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
7032 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
7033 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
7034 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
7035 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
7036 DHCP services in Debian Edu to use the same LDAP objects for a given
7037 computer, to avoid the possibility of having a inconsistent state for
7038 a computer in LDAP (as in DHCP but no DNS entry or the other way
7039 around) and make it easier to add computers to LDAP.&lt;/p&gt;
7040
7041 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
7042 information finally found a solution that seem to work.&lt;/p&gt;
7043
7044 &lt;p&gt;The old setup required three LDAP objects for a given computer.
7045 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7046 we switch powerdns to use its strict LDAP method (ldap-method=strict
7047 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7048 merged into one while making it impossible to transfer the reverse map
7049 to a slave DNS server.&lt;/p&gt;
7050
7051 &lt;p&gt;If we also replace the object class used to get the DNS related
7052 attributes to one allowing these attributes to be combined with the
7053 dhcphost object class, we can merge the DNS and DHCP entries into one.
7054 I&#39;ve written such object class in the dnsdomainaux.schema file (need
7055 proper OIDs, but that is a minor issue), and tested the setup. It
7056 seem to work.&lt;/p&gt;
7057
7058 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
7059 for both DNS and DHCP, and even the LTSP configuration I suggested in
7060 an earlier email. The combined LDAP object will look something like
7061 this:&lt;/p&gt;
7062
7063 &lt;blockquote&gt;&lt;pre&gt;
7064 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7065 cn: hostname
7066 objectClass: dhcphost
7067 objectclass: domainrelatedobject
7068 objectclass: dnsdomainaux
7069 associateddomain: hostname.intern
7070 arecord: 10.11.12.13
7071 dhcphwaddress: ethernet 00:00:00:00:00:00
7072 dhcpstatements: fixed-address hostname
7073 ldapconfigsound: Y
7074 &lt;/pre&gt;&lt;/blockquote&gt;
7075
7076 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
7077 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7078 before asking DNS to resolve the fixed-adddress. LTSP will use
7079 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
7080
7081 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
7082 dhcphost in a different location, to allow us to put the objects
7083 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7084 that. If I can&#39;t figure out a way to do that, we can still get rid of
7085 the hosts subtree and move all its content into the DHCP Config tree
7086 (which probably should be renamed to be more related to the new
7087 content. I suspect cn=dnsdhcp,ou=services or something like that
7088 might be a good place to put it.&lt;/p&gt;
7089
7090 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7091 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7092 </description>
7093 </item>
7094
7095 <item>
7096 <title>Idea for storing LTSP configuration in LDAP</title>
7097 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7098 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7099 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7100 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7101 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7102 clients, and that this can be used to fetch configuration from LDAP if
7103 Debian Edu choose to store configuration there.&lt;/p&gt;
7104
7105 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7106 to get configuration from LDAP. The idea is to look up the MAC
7107 address of the client in LDAP, and look for attributes on the form
7108 ltspconfigsetting=value, and use this to export SETTING=value to the
7109 LTSP clients.&lt;/p&gt;
7110
7111 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7112 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7113 allowing us to store all information about a computer in one place.&lt;/p&gt;
7114
7115 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7116 this approach. A real LDAP schema for the ltspClientAux objectclass
7117 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7118
7119 &lt;blockquote&gt;&lt;pre&gt;
7120 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7121 #
7122 # Fetch LTSP client settings from LDAP based on MAC address
7123 #
7124 # Uses ethernet address as stored in the dhcpHost objectclass using
7125 # the dhcpHWAddress attribute or ethernet address stored in the
7126 # ieee802Device objectclass with the macAddress attribute.
7127 #
7128 # This module is written to be schema agnostic, and only depend on the
7129 # existence of attribute names.
7130 #
7131 # The LTSP configuration variables are saved directly using a
7132 # ltspConfig prefix and uppercasing the rest of the attribute name.
7133 # To set the SERVER variable, set the ltspConfigServer attribute.
7134 #
7135 # Some LDAP schema should be created with all the relevant
7136 # configuration settings. Something like this should work:
7137 #
7138 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7139 # SUP top
7140 # AUXILIARY
7141 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7142
7143 LDAPSERVER=$(debian-edu-ldapserver)
7144 if [ &quot;$LDAPSERVER&quot; ] ; then
7145 LDAPBASE=$(debian-edu-ldapserver -b)
7146 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7147 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7148 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7149 grep &#39;^ltspConfig&#39; | while read attr value ; do
7150 # Remove prefix and convert to upper case
7151 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7152 # bass value on to clients
7153 eval &quot;$attr=$value; export $attr&quot;
7154 done
7155 done
7156 fi
7157 &lt;/pre&gt;&lt;/blockquote&gt;
7158
7159 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7160 the while block might end up in a subshell causing the variables set
7161 there to not show up in ltsp-config, but if that is the case I am sure
7162 the code can be restructured to make sure the variables are passed on.
7163 I expect that can be solved with some testing. :)&lt;/p&gt;
7164
7165 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7166 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7167
7168 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7169 configuration in LDAP that was created around year 2000 by
7170 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7171 Xperience, Inc., 2000&lt;/a&gt;. I found its
7172 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7173 personal home page over at redhat.com.&lt;/p&gt;
7174 </description>
7175 </item>
7176
7177 <item>
7178 <title>jXplorer, a very nice LDAP GUI</title>
7179 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7181 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7182 <description>&lt;p&gt;Since
7183 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7184 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7185 LDAP GUI that is even better than luma. The java application
7186 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7187 moving LDAP objects and subtrees using drag-and-drop, and can
7188 authenticate using Kerberos. I have only tested the Kerberos
7189 authentication, but do not have a LDAP setup allowing me to rewrite
7190 LDAP with my test user yet. It is
7191 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7192 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7193 have with it is how it handle errors. If something go wrong, its
7194 non-intuitive behaviour require me to go through some query work list
7195 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7196 </description>
7197 </item>
7198
7199 <item>
7200 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7201 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7202 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7203 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7204 <description>&lt;p&gt;Here is a short update on my &lt;a
7205 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7206 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7207 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7208 not reporting the status for KDE, because the upgrade crashes when
7209 aptitude try because of missing conflicts
7210 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7211 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7212
7213 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7214 complete list of the installed packages. Based on this I see these
7215 differences when I did a test run today. As usual, I do not really
7216 know what the correct set of packages would be, but thought it best to
7217 publish the difference.&lt;/p&gt;
7218
7219 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7220
7221 &lt;blockquote&gt;&lt;p&gt;
7222 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7223 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7224 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7225 libgtksourceview-common libpt-1.10.10-plugins-alsa
7226 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7227 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7228 python-4suite-xml python-eggtrayicon python-gtkhtml2
7229 python-gtkmozembed svgalibg1 xserver-xephyr zip
7230 &lt;/p&gt;&lt;/blockquote&gt;
7231
7232 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7233
7234 &lt;blockquote&gt;&lt;p&gt;
7235 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7236 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7237 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7238 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7239 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7240 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7241 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7242 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7243 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7244 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7245 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7246 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7247 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7248 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7249 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7250 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7251 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7252 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7253 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7254 mysql-common swfdec-gnome totem-gstreamer wodim
7255 &lt;/p&gt;&lt;/blockquote&gt;
7256
7257 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7258
7259 &lt;blockquote&gt;&lt;p&gt;
7260 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7261 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7262 xserver-xorg-input-all xserver-xorg-input-evdev
7263 xserver-xorg-input-kbd xserver-xorg-input-mouse
7264 xserver-xorg-input-synaptics xserver-xorg-video-all
7265 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7266 xserver-xorg-video-chips xserver-xorg-video-cirrus
7267 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7268 xserver-xorg-video-glint xserver-xorg-video-i128
7269 xserver-xorg-video-i740 xserver-xorg-video-mach64
7270 xserver-xorg-video-mga xserver-xorg-video-neomagic
7271 xserver-xorg-video-nouveau xserver-xorg-video-nv
7272 xserver-xorg-video-r128 xserver-xorg-video-radeon
7273 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7274 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7275 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7276 xserver-xorg-video-sis xserver-xorg-video-sisusb
7277 xserver-xorg-video-tdfx xserver-xorg-video-tga
7278 xserver-xorg-video-trident xserver-xorg-video-tseng
7279 xserver-xorg-video-vesa xserver-xorg-video-vmware
7280 xserver-xorg-video-voodoo
7281 &lt;/p&gt;&lt;/blockquote&gt;
7282
7283 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7284
7285 &lt;blockquote&gt;&lt;p&gt;
7286 deskbar-applet xserver-xorg xserver-xorg-core
7287 xserver-xorg-input-wacom xserver-xorg-video-intel
7288 xserver-xorg-video-openchrome
7289 &lt;/p&gt;&lt;/blockquote&gt;
7290
7291 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7292 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7293 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7294 No idea when it hits Squeeze, but when it does I hope it will reduce
7295 the difference somewhat.
7296 </description>
7297 </item>
7298
7299 <item>
7300 <title>LUMA, a very nice LDAP GUI</title>
7301 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7302 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7303 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7304 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7305 directory in Debian Edu, and in the process I started to miss a GUI
7306 tool to browse the LDAP tree. The only one I was able to find in
7307 Debian/Squeeze and Lenny is
7308 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7309 be a great tool to get a overview of the current LDAP directory
7310 populated by default in Skolelinux. Thanks to it, I have been able to
7311 find empty and obsolete subtrees, misplaced objects and duplicate
7312 objects. It will be installed by default in Debian/Squeeze. If you
7313 are working with LDAP, give it a go. :)&lt;/p&gt;
7314
7315 &lt;p&gt;I did notice one problem with it I have not had time to report to
7316 the BTS yet. There is no .desktop file in the package, so the tool do
7317 not show up in the Gnome and KDE menus, but only deep down in in the
7318 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7319 released.&lt;/p&gt;
7320
7321 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7322 like to move objects and remove subtrees directly in the GUI, but have
7323 not found a way to do that with LUMA yet. So in the mean time, I use
7324 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7325
7326 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7327 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7328
7329 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7330 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7331 useful GUI alternative. It seem like a good tool, but is unmaintained
7332 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7333 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7334 </description>
7335 </item>
7336
7337 <item>
7338 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7339 <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>
7340 <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>
7341 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7342 <description>&lt;p&gt;A while back, I
7343 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7344 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7345 for storing DNS and DHCP information in LDAP to combine the two sets
7346 of information into one LDAP object representing a computer.&lt;/p&gt;
7347
7348 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7349 the dhcpHost object class auxiliary, to allow it to be combined with
7350 the dNSDomain object class, and thus forming one object for one
7351 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7352
7353 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7354 without also changing the assigned number for the object class, and I
7355 do not know enough about LDAP schema design to do that properly for
7356 Debian Edu.&lt;/p&gt;
7357
7358 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7359 the
7360 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7361 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7362 available today from IETF.&lt;/p&gt;
7363
7364 &lt;pre&gt;
7365 --- dhcp.schema (revision 65192)
7366 +++ dhcp.schema (working copy)
7367 @@ -376,7 +376,7 @@
7368 objectclass ( 2.16.840.1.113719.1.203.6.6
7369 NAME &#39;dhcpHost&#39;
7370 DESC &#39;This represents information about a particular client&#39;
7371 - SUP top
7372 + SUP top AUXILIARY
7373 MUST cn
7374 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7375 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7376 &lt;/pre&gt;
7377
7378 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7379 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7380 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7381
7382 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7383 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7384 </description>
7385 </item>
7386
7387 <item>
7388 <title>Calling tasksel like the installer, while still getting useful output</title>
7389 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7390 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7391 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7392 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7393 installs packages during the normal debian-installer run. Until now,
7394 I have ended up letting tasksel do the work, with the annoying problem
7395 of not getting any feedback at all when something fails (like a
7396 conffile question from dpkg or a download that fails), using code like
7397 this:
7398
7399 &lt;blockquote&gt;&lt;pre&gt;
7400 export DEBIAN_FRONTEND=noninteractive
7401 tasksel --new-install
7402 &lt;/pre&gt;&lt;/blockquote&gt;
7403
7404 This would invoke tasksel, let its automatic task selection pick the
7405 tasks to install, and continue to install the requested tasks without
7406 any output what so ever.
7407
7408 Recently I revisited this problem while working on the automatic
7409 package upgrade testing, because tasksel would some times hang without
7410 any useful feedback, and I want to see what is going on when it
7411 happen. Then it occured to me, I can parse the output from tasksel
7412 when asked to run in test mode, and use that aptitude command line
7413 printed by tasksel then to simulate the tasksel run. I ended up using
7414 code like this:
7415
7416 &lt;blockquote&gt;&lt;pre&gt;
7417 export DEBIAN_FRONTEND=noninteractive
7418 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7419 $cmd
7420 &lt;/pre&gt;&lt;/blockquote&gt;
7421
7422 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7423 --without-recommends -o APT::Install-Recommends=no -y install
7424 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7425 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7426 laptop task and all packages with priority standard , required and
7427 important, just like tasksel would have done it during
7428 installation.&lt;/p&gt;
7429
7430 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7431 install packages without using debconf-apt-progress, for use cases
7432 like this.&lt;/p&gt;
7433 </description>
7434 </item>
7435
7436 <item>
7437 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7438 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7439 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7440 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7441 <description>&lt;p&gt;My
7442 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7443 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7444 finally made the upgrade logs available from
7445 &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;.
7446 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7447 apt and aptitude, and found their differences interesting. This time
7448 I will only focus on their removal plans.&lt;/p&gt;
7449
7450 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7451 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7452 surprising part is that it want to remove xorg and all
7453 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7454 sure why. When asking aptitude to do the same, it want to remove 129
7455 packages, but most of them are library packages I suspect are no
7456 longer needed. Both of them want to remove bluetooth packages, which
7457 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7458
7459 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7460 which seem like a bad idea and xorg the same way as with Gnome. Asking
7461 aptitude for the same, it wants to remove 192 packages, none which are
7462 too surprising.&lt;/p&gt;
7463
7464 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7465 and avoided, and perhaps others as well. Here are the complete list
7466 of planned removals. The complete logs is available from the URL
7467 above. Note if you want to repeat these tests, that the upgrade test
7468 for kde+apt-get hung in the tasksel setup because of dpkg asking
7469 conffile questions. No idea why. I worked around it by using
7470 &#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
7471 continue.&lt;/p&gt;
7472
7473 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7474 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7475 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7476 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7477 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7478 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7479 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7480 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7481 xserver-xorg-input-kbd xserver-xorg-input-mouse
7482 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7483 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7484 xserver-xorg-video-ati xserver-xorg-video-chips
7485 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7486 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7487 xserver-xorg-video-glint xserver-xorg-video-i128
7488 xserver-xorg-video-i740 xserver-xorg-video-imstt
7489 xserver-xorg-video-intel xserver-xorg-video-mach64
7490 xserver-xorg-video-mga xserver-xorg-video-neomagic
7491 xserver-xorg-video-nsc xserver-xorg-video-nv
7492 xserver-xorg-video-openchrome xserver-xorg-video-r128
7493 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7494 xserver-xorg-video-rendition xserver-xorg-video-s3
7495 xserver-xorg-video-s3virge xserver-xorg-video-savage
7496 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7497 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7498 xserver-xorg-video-tga xserver-xorg-video-trident
7499 xserver-xorg-video-tseng xserver-xorg-video-v4l
7500 xserver-xorg-video-vesa xserver-xorg-video-vga
7501 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7502 xulrunner-1.9-gnome-support&lt;/p&gt;
7503
7504 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7505
7506 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7507 djvulibre-desktop finger gnome-app-install gnome-mount
7508 gnome-network-admin gnome-spell gnome-vfs-obexftp
7509 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7510 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7511 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7512 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7513 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7514 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7515 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7516 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7517 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7518 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7519 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7520 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7521 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7522 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7523 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7524 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7525 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7526 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7527 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7528 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7529 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7530 openoffice.org-writer2latex openssl-blacklist p7zip
7531 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7532 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7533 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7534 swfdec-mozilla totem-gstreamer update-manager wodim
7535 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7536 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7537 zip&lt;/p&gt;
7538
7539 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7540
7541 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7542 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7543 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7544 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7545 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7546 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7547 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7548 xserver-xorg-input-kbd xserver-xorg-input-mouse
7549 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7550 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7551 xserver-xorg-video-ati xserver-xorg-video-chips
7552 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7553 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7554 xserver-xorg-video-glint xserver-xorg-video-i128
7555 xserver-xorg-video-i740 xserver-xorg-video-imstt
7556 xserver-xorg-video-intel xserver-xorg-video-mach64
7557 xserver-xorg-video-mga xserver-xorg-video-neomagic
7558 xserver-xorg-video-nsc xserver-xorg-video-nv
7559 xserver-xorg-video-openchrome xserver-xorg-video-r128
7560 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7561 xserver-xorg-video-rendition xserver-xorg-video-s3
7562 xserver-xorg-video-s3virge xserver-xorg-video-savage
7563 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7564 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7565 xserver-xorg-video-tga xserver-xorg-video-trident
7566 xserver-xorg-video-tseng xserver-xorg-video-v4l
7567 xserver-xorg-video-vesa xserver-xorg-video-vga
7568 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7569
7570 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7571 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7572 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7573 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7574 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7575 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7576 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7577 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7578 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7579 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7580 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7581 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7582 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7583 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7584 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7585 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7586 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7587 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7588 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7589 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7590 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7591 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7592 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7593 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7594 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7595 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7596 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7597 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7598 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7599 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7600 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7601 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7602 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7603 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7604 texlive-common texlive-doc-base texlive-fonts-recommended
7605 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7606 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7607 xulrunner-1.9&lt;/p&gt;
7608
7609 </description>
7610 </item>
7611
7612 <item>
7613 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7614 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7615 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7616 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7617 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7618 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7619 have been discovered and reported in the process
7620 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7621 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7622 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7623 kdebase-workspace-data), and to get a more regular testing going on, I
7624 am working on a script to automate the test.&lt;/p&gt;
7625
7626 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7627 Gnome or KDE desktop installation inside the chroot before upgrading
7628 it. To ensure no services are started in the chroot, a policy-rc.d
7629 script is inserted. To make sure tasksel believe it is to install a
7630 desktop on a laptop, the tasksel tests are replaced in the chroot
7631 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7632
7633 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7634 currently always fail because udev refuses to upgrade with the kernel
7635 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7636 is created. The bug report
7637 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7638 this problem do not trigger in a chroot, but I touch the file anyway
7639 to make sure the upgrade go well. Testing on virtual and real
7640 hardware have failed me because of udev so far, and creating this file
7641 do the trick in such settings anyway. This is a
7642 &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
7643 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7644 maintainer because he lack the resources to rewrite udev to keep
7645 working with old kernels or something like that. I really wish the
7646 udev upstream would keep udev backwards compatible, to avoid such
7647 upgrade problem, but given that they fail to do so, I guess
7648 documenting the way out of this mess is the best option we got for
7649 Debian Squeeze.&lt;/p&gt;
7650
7651 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7652 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7653 trick:&lt;/p&gt;
7654
7655 &lt;blockquote&gt;&lt;pre&gt;
7656 #!/bin/sh
7657 set -ex
7658
7659 if [ &quot;$1&quot; ] ; then
7660 desktop=$1
7661 else
7662 desktop=gnome
7663 fi
7664
7665 from=lenny
7666 to=squeeze
7667
7668 exec &amp;lt; /dev/null
7669 unset LANG
7670 mirror=http://ftp.skolelinux.org/debian
7671 tmpdir=chroot-$from-upgrade-$to-$desktop
7672 fuser -mv .
7673 debootstrap $from $tmpdir $mirror
7674 chroot $tmpdir aptitude update
7675 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7676 #!/bin/sh
7677 exit 101
7678 EOF
7679 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7680 exit_cleanup() {
7681 umount $tmpdir/proc
7682 }
7683 mount -t proc proc $tmpdir/proc
7684 # Make sure proc is unmounted also on failure
7685 trap exit_cleanup EXIT INT
7686
7687 chroot $tmpdir aptitude -y install debconf-utils
7688
7689 # Make sure tasksel autoselection trigger. It need the test scripts
7690 # to return the correct answers.
7691 echo tasksel tasksel/desktop multiselect $desktop | \
7692 chroot $tmpdir debconf-set-selections
7693
7694 # Include the desktop and laptop task
7695 for test in desktop laptop ; do
7696 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7697 #!/bin/sh
7698 exit 2
7699 EOF
7700 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7701 done
7702
7703 DEBIAN_FRONTEND=noninteractive
7704 DEBIAN_PRIORITY=critical
7705 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7706 chroot $tmpdir tasksel --new-install
7707
7708 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7709 chroot $tmpdir aptitude update
7710 touch $tmpdir/etc/udev/kernel-upgrade
7711 chroot $tmpdir aptitude -y dist-upgrade
7712 fuser -mv
7713 &lt;/pre&gt;&lt;/blockquote&gt;
7714
7715 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7716 with aptitude, but I have not had time to look at how they behave
7717 differently so far. I hope to get a cron job running to do the test
7718 regularly and post the result on the web. The Gnome upgrade currently
7719 work, while the KDE upgrade fail because of the bug in
7720 kdebase-workspace-data&lt;/p&gt;
7721
7722 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7723 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7724 post, so I will refrain from trying. I can report that for Gnome,
7725 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7726 remove and 1 not upgraded and 1024MB need to be downloaded while for
7727 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7728 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7729
7730 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7731 is able to migrate to dependency based boot sequencing and parallel
7732 booting without a hitch. Was unsure if there were still bugs with
7733 packages failing to clean up their obsolete init.d script during
7734 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7735 packages.&lt;/p&gt;
7736 </description>
7737 </item>
7738
7739 <item>
7740 <title>Upstart or sysvinit - as init.d scripts see it</title>
7741 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7742 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7743 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7744 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7745 scripts to migrate (some of) their operations to upstart job while
7746 keeping the init.d for hurd and kfreebsd. The packages with such
7747 needs will need a way to get their init.d scripts to behave
7748 differently when used with sysvinit and with upstart. Because of
7749 this, I had a look at the environment variables set when a init.d
7750 script is running under upstart, and when it is not.&lt;/p&gt;
7751
7752 &lt;p&gt;With upstart, I notice these environment variables are set when a
7753 script is started from rcS.d/ (ignoring some irrelevant ones like
7754 COLUMNS):&lt;/p&gt;
7755
7756 &lt;blockquote&gt;&lt;pre&gt;
7757 DEFAULT_RUNLEVEL=2
7758 previous=N
7759 PREVLEVEL=
7760 RUNLEVEL=
7761 runlevel=S
7762 UPSTART_EVENTS=startup
7763 UPSTART_INSTANCE=
7764 UPSTART_JOB=rc-sysinit
7765 &lt;/pre&gt;&lt;/blockquote&gt;
7766
7767 &lt;p&gt;With sysvinit, these environment variables are set for the same
7768 script.&lt;/p&gt;
7769
7770 &lt;blockquote&gt;&lt;pre&gt;
7771 INIT_VERSION=sysvinit-2.88
7772 previous=N
7773 PREVLEVEL=N
7774 RUNLEVEL=S
7775 runlevel=S
7776 &lt;/pre&gt;&lt;/blockquote&gt;
7777
7778 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7779 sysvinit are not set by upstart. Not sure if it is intentional or not
7780 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7781
7782 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7783 looking for the UPSTART_JOB environment variable seem to be a good
7784 choice.&lt;/p&gt;
7785 </description>
7786 </item>
7787
7788 <item>
7789 <title>A manual for standards wars...</title>
7790 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7791 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7792 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7793 <description>&lt;p&gt;Via the
7794 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7795 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7796 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7797 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7798 following the standards wars of today.&lt;/p&gt;
7799 </description>
7800 </item>
7801
7802 <item>
7803 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7804 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7805 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7806 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7807 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7808 to get a list of the machine types in use thanks to the DMI
7809 information extracted from each machine. The script to do so is
7810 included in the sitesummary package, and here is example output from
7811 the Skolelinux build servers:&lt;/p&gt;
7812
7813 &lt;blockquote&gt;&lt;pre&gt;
7814 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7815 vendor count
7816 Dell Computer Corporation 1
7817 PowerEdge 1750 1
7818 IBM 1
7819 eserver xSeries 345 -[8670M1X]- 1
7820 Intel 2
7821 [no-dmi-info] 3
7822 maintainer:~#
7823 &lt;/pre&gt;&lt;/blockquote&gt;
7824
7825 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7826 provided in each machine. Here there are Intel machines without model
7827 information listed with Intel as vendor and no model, and virtual Xen
7828 machines listed as [no-dmi-info]. One can add -l as a command line
7829 option to list the individual machines.&lt;/p&gt;
7830
7831 &lt;p&gt;A larger list is
7832 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7833 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7834 provide the basic sitesummary report publicly. In their report there
7835 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7836 their machines, and as sitesummary is available in both distributions,
7837 it is trivial to get all of them to report to the same central
7838 collector.&lt;/p&gt;
7839 </description>
7840 </item>
7841
7842 <item>
7843 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7844 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7845 <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>
7846 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7847 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7848 start at boot when an NVidia video card is used is handled. The
7849 problem seem to be that the nvidia X.org driver uses a long time to
7850 initialize, and this duration is longer than kdm is configured to
7851 wait.&lt;/p&gt;
7852
7853 &lt;p&gt;I came across two bugs related to this issue,
7854 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7855 against initscripts and passed on to nvidia-glx when it became obvious
7856 that the nvidia drivers were involved, and
7857 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7858 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7859
7860 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7861 problem nvidia video card owners experience and make sure the Debian
7862 distribution work out of the box for these users. The nvidia driver
7863 maintainers expect kdm to be set up to wait longer, while kdm expect
7864 the nvidia driver maintainers to fix the driver to start faster, and
7865 while they wait for each other I guess the users end up switching to a
7866 distribution that work for them. I have no idea what the solution is,
7867 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7868
7869 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7870 </description>
7871 </item>
7872
7873 <item>
7874 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7875 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7876 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7877 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7878 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7879 The feature seem to hold up pretty well, but three fairly serious
7880 issues are known and should be solved:
7881
7882 &lt;p&gt;&lt;ul&gt;
7883
7884 &lt;li&gt;The wicd package seen to
7885 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7886 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7887 parallel booting is enabled. No idea why, but the wicd maintainer
7888 seem to be on the case.&lt;/li&gt;
7889
7890 &lt;li&gt;The nvidia X driver seem to
7891 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7892 triggered more easily when parallel booting is in effect. The
7893 maintainer is on the case.&lt;/li&gt;
7894
7895 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7896 sequencing (the shutdown is broken) when old file-rc users
7897 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7898 sysv-rc. One way to solve it would be for file-rc to create
7899 /etc/init.d/.legacy-bootordering, and another is to try to make
7900 sysv-rc more robust. Will investigate some more and probably upload a
7901 workaround in sysv-rc to help those trying to move from file-rc to
7902 sysv-rc get a working shutdown.&lt;/li&gt;
7903
7904 &lt;/ul&gt;&lt;/p&gt;
7905
7906 &lt;p&gt;All in all not many surprising issues, and all of them seem
7907 solvable before Squeeze is released. In addition to these there are
7908 some packages with bugs in their dependencies and run level settings,
7909 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7910
7911 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7912 the BTS, please usertag the report to get it to show up at
7913 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7914 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7915
7916 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7917 </description>
7918 </item>
7919
7920 <item>
7921 <title>More flexible firmware handling in debian-installer</title>
7922 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7923 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7924 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7925 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7926 found time today to return to the project. Having to spend less time
7927 working dependency based boot in debian, as it is almost complete now,
7928 definitely helped freeing some time.&lt;/p&gt;
7929
7930 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7931 include some firmware packages on the Debian Edu CDs, those needed to
7932 get disk and network controllers working. Without having these
7933 firmware packages available during installation, it is impossible to
7934 install Debian Edu on the given machine, and because our target group
7935 are non-technical people, asking them to provide firmware packages on
7936 an external medium is a support pain. Initially, I expected it to be
7937 enough to include the firmware packages on the CD to get
7938 debian-installer to find and use them. This proved to be wrong.
7939 Next, I hoped it was enough to symlink the relevant firmware packages
7940 to some useful location on the CD (tried /cdrom/ and
7941 /cdrom/firmware/). This also proved to not work, and at this point I
7942 found time to look at the debian-installer code to figure out what was
7943 going to work.&lt;/p&gt;
7944
7945 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7946 look revealed that it would only look for firmware packages outside
7947 the installation media, so the CD was never checked for firmware
7948 packages. It would only check USB sticks, floppies and other
7949 &quot;external&quot; media devices. Today I changed it to also look in the
7950 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7951 solve the problem I ran into with Debian edu. I also changed it to
7952 look in /firmware/, to make sure the installer also find firmware
7953 provided in the initrd when booting the installer via PXE, to allow us
7954 to provide the same feature in the PXE setup included in Debian
7955 Edu.&lt;/p&gt;
7956
7957 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7958 activated without asking if the license is accepted, I extended
7959 hw-detect to look for preinst scripts in the firmware packages, and
7960 run these before activating the firmware during installation. The
7961 license question is asked using debconf in the preinst, so this should
7962 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7963
7964 &lt;p&gt;If you want to discuss the details of these features, please
7965 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7966 </description>
7967 </item>
7968
7969 <item>
7970 <title>Parallellized boot is now the default in Debian/unstable</title>
7971 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7972 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7973 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7974 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7975 Debian/unstable for machines using dependency based boot sequencing.
7976 Apparently the testing of concurrent booting has been wider than
7977 expected, if I am to believe the
7978 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7979 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7980 with the feature this weekend, to give us some time to detect any
7981 remaining problems before Squeeze is frozen. If serious problems are
7982 detected, it is simple to change the default back to sequential boot.
7983 The upload of the new sysvinit package also activate a new upstream
7984 version.&lt;/p&gt;
7985
7986 More information about
7987 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7988 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7989 currently possible to disable parallel booting when one run into
7990 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7991
7992 &lt;blockquote&gt;&lt;pre&gt;
7993 CONCURRENCY=none
7994 &lt;/pre&gt;&lt;/blockquote&gt;
7995
7996 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7997 the BTS, please usertag the report to get it to show up at
7998 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7999 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8000 </description>
8001 </item>
8002
8003 <item>
8004 <title>Sitesummary tip: Listing MAC address of all clients</title>
8005 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
8006 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
8007 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
8008 <description>&lt;p&gt;In the recent Debian Edu versions, the
8009 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
8010 system&lt;/a&gt; is used to keep track of the machines in the school
8011 network. Each machine will automatically report its status to the
8012 central server after boot and once per night. The network setup is
8013 also reported, and using this information it is possible to get the
8014 MAC address of all network interfaces in the machines. This is useful
8015 to update the DHCP configuration.&lt;/p&gt;
8016
8017 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
8018 ist all MAC addresses of all machines reporting to sitesummary. Run
8019 this on the collector host:&lt;/p&gt;
8020
8021 &lt;blockquote&gt;&lt;pre&gt;
8022 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
8023 &lt;/pre&gt;&lt;/blockquote&gt;
8024
8025 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
8026 line per machine and with space between the MAC addresses.&lt;/p&gt;
8027
8028 &lt;p&gt;To allow system administrators easier job at adding static DHCP
8029 addresses for hosts, it would be possible to extend this to fetch
8030 machine information from sitesummary and update the DHCP and DNS
8031 tables in LDAP using this information. Such tool is unfortunately not
8032 written yet.&lt;/p&gt;
8033 </description>
8034 </item>
8035
8036 <item>
8037 <title>systemd, an interesting alternative to upstart</title>
8038 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
8039 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
8040 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
8041 <description>&lt;p&gt;The last few days a new boot system called
8042 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
8043 has been
8044 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
8045
8046 to the free software world. I have not yet had time to play around
8047 with it, but it seem to be a very interesting alternative to
8048 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
8049 a good alternative for Debian when we are able to switch to an event
8050 based boot system. Tollef is
8051 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
8052 systemd into Debian, and I look forward to seeing how well it work. I
8053 like the fact that systemd handles init.d scripts with dependency
8054 information natively, allowing them to run in parallel where upstart
8055 at the moment do not.&lt;/p&gt;
8056
8057 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
8058 platform support. It only work on recent Linux kernels, and also need
8059 some new kernel features enabled to function properly. This means
8060 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8061 system. Not sure how that will be handled if systemd proves to be the
8062 way forward.&lt;/p&gt;
8063
8064 &lt;p&gt;In the mean time, based on the
8065 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8066 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
8067 decided to enable full parallel booting as the default in Debian as
8068 soon as possible (probably this weekend or early next week), to see if
8069 there are any remaining serious bugs in the init.d dependencies. A
8070 new version of the sysvinit package implementing this change is
8071 already in experimental. If all go well, Squeeze will be released
8072 with parallel booting enabled by default.&lt;/p&gt;
8073 </description>
8074 </item>
8075
8076 <item>
8077 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
8078 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
8079 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
8080 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
8081 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
8082 complete, so complete that it is actually possible to run all the
8083 init.d scripts in parallell based on these dependencies. If you want
8084 to test your Squeeze system, make sure
8085 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8086 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8087 /etc/default/rcS:&lt;/p&gt;
8088
8089 &lt;blockquote&gt;&lt;pre&gt;
8090 CONCURRENCY=makefile
8091 &lt;/pre&gt;&lt;/blockquote&gt;
8092
8093 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8094 scripts in parallel using the dependency information stored in
8095 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8096 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8097 to try to start the kdm and gdm scripts as early as possible, and will
8098 start the facilities required by kdm or gdm as early as possible to
8099 make this happen.&lt;/p&gt;
8100
8101 &lt;p&gt;Give it a try, and see if you like the result. If some services
8102 fail to start properly, it is most likely because they have incomplete
8103 init.d script dependencies in their startup script (or some of their
8104 dependent scripts have incomplete dependencies). Report bugs and get
8105 the package maintainers to fix it. :)&lt;/p&gt;
8106
8107 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8108 manage to get the init.d script dependencies complete and correct. I
8109 expect we will get there in Squeeze+1, if we get manage to test and
8110 fix the remaining issues.&lt;/p&gt;
8111
8112 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8113 the BTS, please usertag the report to get it to show up at
8114 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8115 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8116 </description>
8117 </item>
8118
8119 <item>
8120 <title>Debian has switched to dependency based boot sequencing</title>
8121 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8123 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8124 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8125 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8126 have been migrated to using dependency based boot sequencing. This
8127 conclude work me and others have been doing for the last three days.
8128 It feels great to see this finally part of the default Debian
8129 installation. Now we just need to weed out the last few problems that
8130 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8131
8132 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8133 fixing the more fundamental problem of handing the event based
8134 non-predictable kernel in the early boot.&lt;/p&gt;
8135 </description>
8136 </item>
8137
8138 <item>
8139 <title>Taking over sysvinit development</title>
8140 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8141 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8142 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8143 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8144 the existing sysvinit upstream developer, I decided a few weeks ago to
8145 take over the package and become the new upstream. The number of
8146 patches to track for the Debian package was becoming a burden, and the
8147 lack of synchronization between the distribution made it hard to keep
8148 the package up to date.&lt;/p&gt;
8149
8150 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8151 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8152 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8153 and Fedora), based on the patches currently in use in these
8154 distributions. We Debian maintainers plan to move to this tarball as
8155 the new upstream as soon as we find time to do the merge. Since the
8156 new tarball was created, we agreed with Werner at SuSe to make a new
8157 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8158 development there. The project is registered and currently waiting
8159 for approval by the Savannah administrators, and as soon as it is
8160 approved, we will import the old versions from svn and continue
8161 working on the future release.&lt;/p&gt;
8162
8163 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8164 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8165 </description>
8166 </item>
8167
8168 <item>
8169 <title>Debian boots quicker and quicker</title>
8170 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8171 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8172 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8173 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8174 people involved in the boot system on Debian and Ubuntu, to see if we
8175 could find more ways to speed up the boot system. This was an Ubuntu
8176 funded
8177 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8178 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8179 of boot systems, and ways to handle the increasing number of boot
8180 issues introduced by the Linux kernel becoming more and more
8181 asynchronous and event base. The Ubuntu approach using udev and
8182 upstart might be a good way forward. Time will show.&lt;/p&gt;
8183
8184 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8185 process in Debian. All of these should be applied to get a quick
8186 boot:&lt;/p&gt;
8187
8188 &lt;ul&gt;
8189
8190 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8191
8192 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8193 clock is in UTC.&lt;/li&gt;
8194
8195 &lt;li&gt;Install and activate the insserv package to enable
8196 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8197 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8198
8199 &lt;/ul&gt;
8200
8201 These points are based on the Google summer of code work done by
8202 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8203 Villegas&lt;/a&gt;.
8204
8205 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8206 unstable yesterday. When we tested it, we were able to cut 6 seconds
8207 from the boot sequence. It depend on very correct dependency
8208 declaration in all init.d scripts, so I expect us to find edge cases
8209 where the dependences in some scripts are slightly wrong when we start
8210 using this.&lt;/p&gt;
8211
8212 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8213 introduced by Raphael Geissert today, one that could affect the
8214 startup speed as well. Instead of starting some scripts concurrently
8215 from rcS.d/ and another set of scripts from rc2.d/, it would be
8216 possible to run a of them in the same process. A quick way to test
8217 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8218 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8219 </description>
8220 </item>
8221
8222 <item>
8223 <title>BSAs påstander om piratkopiering møter motstand</title>
8224 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8225 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8226 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8227 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8228 programvareselskapene som Microsoft og Apple, publisert en rapport der
8229 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8230 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8231 dager siden kom
8232 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8233 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8234 dagene. Et spesielt interessant kommentar fra Sverige,
8235 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8236 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8237
8238 &lt;blockquote&gt;
8239 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8240 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8241 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8242 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8243 &lt;/blockquote&gt;
8244
8245 &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
8246 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8247 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8248 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8249 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8250
8251 &lt;p&gt;Fant lenkene via &lt;a
8252 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8253 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8254 </description>
8255 </item>
8256
8257 <item>
8258 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8259 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8260 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8261 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8262 <description>&lt;p&gt;Kom over
8263 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8264 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8265 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8266 jobber til daglig. En rask opptelling forteller meg at vi har 490
8267 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8268 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8269 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8270 </description>
8271 </item>
8272
8273 <item>
8274 <title>Kryptert harddisk - naturligvis</title>
8275 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8276 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8277 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8278 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8279 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8280 når en tar tap av arbeidstid, fortrolige dokumenter,
8281 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8282 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8283 til at jeg har kryptert harddisken på både kontormaskinen og min
8284 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8285 komme på avveie, den første informasjon relatert til jobben min ved
8286 Universitetet i Oslo, og den andre relatert til blant annet
8287 foreningsarbeide. Kryptering av diskene gjør at det er lite
8288 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8289 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8290 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8291 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8292 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8293 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8294 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8295 det er gjort slik jeg gjør det er minimale, og gevinstene er
8296 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8297 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8298
8299 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8300 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8301 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8302 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8303 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8304 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8305 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8306 betydelige.&lt;/p&gt;
8307 </description>
8308 </item>
8309
8310 <item>
8311 <title>Two projects that have improved the quality of free software a lot</title>
8312 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8313 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8314 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8315 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8316 quality of free software, and I wanted to mention both in case someone
8317 do not yet know them.&lt;/p&gt;
8318
8319 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8320 tool to detect and expose errors in the memory handling of programs.
8321 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8322 and it will report any problems on stdout. It is even better if the
8323 program include debug information. With debug information, it is able
8324 to report the source file name and line number where the problem
8325 occurs. It can report things like &#39;reading past memory block in file
8326 X line N, the memory block was allocated in file Y, line M&#39;, and
8327 &#39;using uninitialised value in control logic&#39;. This tool has made it
8328 trivial to investigate reproducible crash bugs in programs, and have
8329 reduced the number of this kind of bugs in free software a lot.
8330
8331 &lt;p&gt;The second one is
8332 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8333 a source code checker. It is able to process the source of a program
8334 and find problems in the logic without running the program. It
8335 started out as the Stanford Checker and became well known when it was
8336 used to find bugs in the Linux kernel. It is now a commercial tool
8337 and the company behind it is running
8338 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8339 free software community, where a lot of free software projects get
8340 their source checked for free. Several thousand defects have been
8341 found and fixed so far. It can find errors like &#39;lock L taken in file
8342 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8343 Y lines O to P can never be executed&#39;. The projects included in the
8344 community service project have managed to get rid of a lot of
8345 reliability problems thanks to Coverity.&lt;/p&gt;
8346
8347 &lt;p&gt;I believe tools like this, that are able to automatically find
8348 errors in the source, are vital to improve the quality of software and
8349 make sure we can get rid of the crashing and failing software we are
8350 surrounded by today.&lt;/p&gt;
8351 </description>
8352 </item>
8353
8354 <item>
8355 <title>No patch is not better than a useless patch</title>
8356 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8357 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8358 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8359 <description>&lt;p&gt;Julien Blache
8360 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8361 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8362 patch allow one to discuss a concrete and proposed solution, and also
8363 prove that the issue at hand is important enough for someone to spent
8364 time on fixing it. No patch do not provide any of these positive
8365 properties.&lt;/p&gt;
8366 </description>
8367 </item>
8368
8369 <item>
8370 <title>Standardize on protocols and formats, not vendors and applications</title>
8371 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8373 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8374 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8375 very good one to form a long lived computer infrastructure. It is the
8376 simple one, lost by many in todays computer industry: Standardize on
8377 open network protocols and open exchange/storage formats, not applications.
8378 Applications come and go, while protocols and files tend to stay, and
8379 thus one want to make it easy to change application and vendor, while
8380 avoiding conversion costs and locking users to a specific platform or
8381 application.&lt;/p&gt;
8382
8383 &lt;p&gt;This approach make it possible to replace the client applications
8384 independently of the server applications. One can even allow users to
8385 use several different applications as long as they handle the selected
8386 protocol and format. In the normal case, only one client application
8387 is recommended and users only get help if they choose to use this
8388 application, but those that want to deviate from the easy path are not
8389 blocked from doing so.&lt;/p&gt;
8390
8391 &lt;p&gt;It also allow us to replace the server side without forcing the
8392 users to replace their applications, and thus allow us to select the
8393 best server implementation at any moment, when scale and resouce
8394 requirements change.&lt;/p&gt;
8395
8396 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8397 open formats, but I would never recommend standardizing on a single
8398 application that do not use open network protocol or open formats.&lt;/p&gt;
8399 </description>
8400 </item>
8401
8402 <item>
8403 <title>Returning from Skolelinux developer gathering</title>
8404 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8405 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8406 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8407 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8408 Edu/Skolelinux development gathering. I got a bit done tuning the
8409 desktop, and looked into the dynamic service location protocol
8410 implementation avahi. It look like it could be useful for us. Almost
8411 30 people participated, and I believe it was a great environment to
8412 get to know the Skolelinux system. Walter Bender, involved in the
8413 development of the Sugar educational platform, presented his stuff and
8414 also helped me improve my OLPC installation. He also showed me that
8415 his Turtle Art application can be used in standalone mode, and we
8416 agreed that I would help getting it packaged for Debian. As a
8417 standalone application it would be great for Debian Edu. We also
8418 tried to get the video conferencing working with two OLPCs, but that
8419 proved to be too hard for us. The application seem to need more work
8420 before it is ready for me. I look forward to getting home and relax
8421 now. :)&lt;/p&gt;
8422 </description>
8423 </item>
8424
8425 <item>
8426 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8427 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8428 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8429 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8430 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8431 optimal. There is RFC 2307 documenting one way to store NIS maps in
8432 LDAP, and a modified version of this normally called RFC 2307bis, with
8433 some modifications to be compatible with Active Directory. The RFC
8434 specification handle the content of a lot of system databases, but do
8435 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8436
8437 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8438 we would like to store information about users, SMB clients/hosts,
8439 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8440 and LTSP configuration in LDAP. These objects have a lot in common,
8441 but with the current LDAP schemas it is not possible to have one
8442 object per entity. For example, one need to have at least three LDAP
8443 objects for a given computer, one with the SMB related stuff, one with
8444 DNS information and another with DHCP information. The schemas
8445 provided for DNS and DHCP are impossible to combine into one LDAP
8446 object. In addition, it is impossible to implement quick queries for
8447 netgroup membership, because of the way NIS triples are implemented.
8448 It just do not scale. I believe it is time for a few RFC
8449 specifications to cleam up this mess.&lt;/p&gt;
8450
8451 &lt;p&gt;I would like to have one LDAP object representing each computer in
8452 the network, and this object can then keep the SMB (ie host key), DHCP
8453 (mac address/name) and DNS (name/IP address) settings in one place.
8454 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8455
8456 &lt;p&gt;I would also like to have a quick way to map from a user or
8457 computer and to the net group this user or computer is a member.&lt;/p&gt;
8458
8459 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8460 in this regard, and the unix side need to catch up. Time to start a
8461 new IETF work group?&lt;/p&gt;
8462 </description>
8463 </item>
8464
8465 <item>
8466 <title>Endelig er Debian Lenny gitt ut</title>
8467 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8468 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8469 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8470 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8471 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8472 Et langt steg videre for Debian-prosjektet, og en rekke nye
8473 programpakker blir nå tilgjengelig for de av oss som bruker den
8474 stabile utgaven av Debian. Neste steg er nå å få
8475 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8476 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8477 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8478 slippes løs på skolene. Takk til alle debian-utviklerne som har
8479 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8480 bootsekvens tilgjengelig i stabil utgave, vha pakken
8481 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8482 </description>
8483 </item>
8484
8485 <item>
8486 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8487 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8488 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8489 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8490 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8491 Oslo. Most of Saturday was used for the general assemly for the
8492 member organization, but the rest of the weekend I used to tune the
8493 LTSP installation. LTSP now work out of the box on the 10-network.
8494 Acer Aspire One proved to be a very nice thin client, with both
8495 screen, mouse and keybard in a small box. Was working on getting the
8496 diskless workstation setup configured out of the box, but did not
8497 finish it before the weekend was up.&lt;/p&gt;
8498
8499 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8500 the Brazilian group, so that will have to wait for the next
8501 development gathering. Would love to have the Debian Edu installer
8502 automatically detect and configure a multiseat setup when it find one
8503 of these cards.&lt;/p&gt;
8504 </description>
8505 </item>
8506
8507 <item>
8508 <title>The sorry state of multimedia browser plugins in Debian</title>
8509 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8510 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8511 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8512 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8513 plugins available in Debian Lenny, to see which one we should use by
8514 default in Debian Edu. We need an embedded video playing plugin with
8515 control buttons to pause or stop the video, and capable of streaming
8516 all the multimedia content available on the web. The test results and
8517 notes are available on
8518 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8519 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8520 fill this need. My personal video player favorite, VLC, has a really
8521 bad plugin which fail on a lot of the test pages. A lot of the MIME
8522 types I would expect to work with any free software player (like
8523 video/ogg), just do not work. And simple formats like the
8524 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8525 totem and vlc plugins. I hope the situation will improve soon. No
8526 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8527
8528 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8529 be the only one fitting our needs. :/&lt;/p&gt;
8530 </description>
8531 </item>
8532
8533 </channel>
8534 </rss>