]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
dcb2fd3a7fdbb3e807c2eb47cd9d1f610cfbf28e
[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
90 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
91 on how to use licensecheck and cdbs to create a draft copyright file
92
93 &lt;p&gt;&lt;pre&gt;
94 licensecheck --copyright -r `find * -type f` | \
95 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
96 &lt;/pre&gt;&lt;/p&gt;
97
98 &lt;p&gt;He mentioned that he normally check the generated file into the
99 version control system to make it easier to discover license and
100 copyright changes in the upstream source. I will try to do the same
101 with my packages in the future.&lt;/p&gt;
102 </description>
103 </item>
104
105 <item>
106 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
107 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
109 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
110 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
111 is taking shape in Debian, and one provided feature is a very
112 convenient way to tell you which package to install to make a given
113 firmware file available when the kernel is looking for it. This can
114 be done using apt-file too, but that is for someone else to blog
115 about. :)&lt;/p&gt;
116
117 &lt;p&gt;Here is a small recipe to find the package with a given firmware
118 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
119 picked from the set of firmware announced using appstream in Debian
120 unstable. In general you would be looking for the firmware requested
121 by the kernel during kernel module loading. To find the package
122 providing the example file, do like this:&lt;/p&gt;
123
124 &lt;blockquote&gt;&lt;pre&gt;
125 % apt install appstream
126 [...]
127 % apt update
128 [...]
129 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
130 awk &#39;/Package:/ {print $2}&#39;
131 firmware-qlogic
132 %
133 &lt;/pre&gt;&lt;/blockquote&gt;
134
135 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
136 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
137 a way appstream can use.&lt;/p&gt;
138
139 &lt;p&gt;This same approach can be used to find any package supporting a
140 given MIME type. This is very useful when you get a file you do not
141 know how to handle. First find the mime type using &lt;tt&gt;file
142 --mime-type&lt;/tt&gt;, and next look up the package providing support for
143 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
144 and you can find all packages handling this type like this:&lt;/p&gt;
145
146 &lt;blockquote&gt;&lt;pre&gt;
147 % apt install appstream
148 [...]
149 % apt update
150 [...]
151 % appstreamcli what-provides mimetype image/svg+xml | \
152 awk &#39;/Package:/ {print $2}&#39;
153 bkchem
154 phototonic
155 inkscape
156 shutter
157 tetzle
158 geeqie
159 xia
160 pinta
161 gthumb
162 karbon
163 comix
164 mirage
165 viewnior
166 postr
167 ristretto
168 kolourpaint4
169 eog
170 eom
171 gimagereader
172 midori
173 %
174 &lt;/pre&gt;&lt;/blockquote&gt;
175
176 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
177 packages providing appstream metadata.&lt;/p&gt;
178 </description>
179 </item>
180
181 <item>
182 <title>Creepy, visualise geotagged social media information - nice free software</title>
183 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
185 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
186 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
187 with the computerised radio beacon known as a mobile phone their
188 position is tracked by the phone company and often stored for a long
189 time (like every time a SMS is received or sent). And if their
190 computerised radio beacon is capable of running programs (often called
191 mobile apps) downloaded from the Internet, these programs are often
192 also capable of tracking their location (if the app requested access
193 during installation). And when these programs send out information to
194 central collection points, the location is often included, unless
195 extra care is taken to not send the location. The provided
196 information is used by several entities, for good and bad (what is
197 good and bad, depend on your point of view). What is certain, is that
198 the private sphere and the right to free movement is challenged and
199 perhaps even eradicated for those announcing their location this way,
200 when they share their whereabouts with private and public
201 entities.&lt;/p&gt;
202
203 &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;
204
205 &lt;p&gt;The phone company logs provide a register of locations to check out
206 when one want to figure out what the tracked person was doing. It is
207 unavailable for most of us, but provided to selected government
208 officials, company staff, those illegally buying information from
209 unfaithful servants and crackers stealing the information. But the
210 public information can be collected and analysed, and a free software
211 tool to do so is called
212 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
213 discovered it when I read
214 &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
215 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
216 November 2014, and decided to check if it was available in Debian.
217 The python program was in Debian, but
218 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
219 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
220 uploaded a new version which did not work quite right, but did not
221 have time to fix it then. This Christmas I decided to finally try to
222 get Creepy operational in Debian. Now a fixed version is available in
223 Debian unstable and testing, and almost all Debian specific patches
224 are now included
225 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
226
227 &lt;p&gt;The Creepy program visualises geolocation information fetched from
228 Twitter, Instagram, Flickr and Google+, and allow one to get a
229 complete picture of every social media message posted recently in a
230 given area, or track the movement of a given individual across all
231 these services. Earlier it was possible to use the search API of at
232 least some of these services without identifying oneself, but these
233 days it is impossible. This mean that to use Creepy, you need to
234 configure it to log in as yourself on these services, and provide
235 information to them about your search interests. This should be taken
236 into account when using Creepy, as it will also share information
237 about yourself with the services.&lt;/p&gt;
238
239 &lt;p&gt;The picture above show the twitter messages sent from (or at least
240 geotagged with a position from) the city centre of Oslo, the capital
241 of Norway. One useful way to use Creepy is to first look at
242 information tagged with an area of interest, and next look at all the
243 information provided by one or more individuals who was in the area.
244 I tested it by checking out which celebrity provide their location in
245 twitter messages by checkout out who sent twitter messages near a
246 Norwegian TV station, and next could track their position over time,
247 making it possible to locate their home and work place, among other
248 things. A similar technique have been
249 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
250 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
251 tool to discover lying governments, and a useful tool to help people
252 understand the value of the private information they provide to the
253 public.&lt;/p&gt;
254
255 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
256 it depend on several python modules currently missing in Jessie (at
257 least python-instagram, python-flickrapi and
258 python-requests-toolbelt).&lt;/p&gt;
259
260 &lt;p&gt;(I have uploaded
261 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
262 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
263 Creepy program in Debian.)&lt;/p&gt;
264 </description>
265 </item>
266
267 <item>
268 <title>Always download Debian packages using Tor - the simple recipe</title>
269 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
271 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
272 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
273 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
274 that those listening on the Internet lines would have good reason to
275 believe a computer have a given security hole&lt;/a&gt; if it download a
276 security fix from a Debian mirror. This is a good reason to always
277 use encrypted connections to the Debian mirror, to make sure those
278 listening do not know which IP address to attack. In August, Richard
279 Hartmann observed that encryption was not enough, when it was possible
280 to interfere download size to security patches or the fact that
281 download took place shortly after a security fix was released, and
282 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
283 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
284 was not the first to propose this, as the
285 &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;
286 package by Tim Retout already existed to make it easy to convince apt
287 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
288 aware of that package when I read the blog post from Richard.&lt;/p&gt;
289
290 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
291 sysadmins, and he set up a Tor hidden service on one of the central
292 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
293 it possible to download packages directly between two tor nodes,
294 making sure the network traffic always were encrypted.&lt;/p&gt;
295
296 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
297 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
298 urls with tor+http and tor+https, and using the hidden service instead
299 of the official Debian mirror site. I recommend installing
300 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
301 done in /etc/.&lt;/p&gt;
302
303 &lt;blockquote&gt;&lt;pre&gt;
304 apt install apt-transport-tor
305 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
306 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
307 &lt;/pre&gt;&lt;/blockquote&gt;
308
309 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
310 the sed commands for these too. The sed command is assuming your are
311 using the ftp.debian.org Debian mirror. Adjust the command (or just
312 edit the file manually) to match your mirror.&lt;/p&gt;
313
314 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
315 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
316 system, and do not work with these tor+http URLs. For
317 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
318 which need a recent apt version currently only in unstable. So if you
319 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
320
321 &lt;p&gt;Another advantage from this change is that your machine will start
322 using Tor regularly and at fairly random intervals (every time you
323 update the package lists or upgrade or install a new package), thus
324 masking other Tor traffic done from the same machine. Using Tor will
325 become normal for the machine in question.&lt;/p&gt;
326
327 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
328 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
329 enabled. It would be great if it was the default on any Debian
330 system.&lt;/p&gt;
331 </description>
332 </item>
333
334 <item>
335 <title>OpenALPR, find car license plates in video streams - nice free software</title>
336 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
337 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
338 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
339 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
340 call the car license plate numbers in those days. I would write the
341 numbers down in my little book and compare notes with the other kids
342 to see how many region codes we had seen and if we had seen some
343 exotic or special region codes and numbers. It was a fun game to pass
344 time, as we kids have plenty of it.&lt;/p&gt;
345
346 &lt;p&gt;A few days I came across
347 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
348 project&lt;/a&gt;, a free software project to automatically discover and
349 report license plates in images and video streams, and provide the
350 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
351 such system for a while now, because I believe it is a bad idea that the
352 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
353 number plate recognition&lt;/a&gt; tool only is available in the hands of
354 the powerful, and want it to be available also for the powerless to
355 even the score when it comes to surveillance and sousveillance. I
356 discovered the developer
357 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
358 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
359 help him get it into shape to get the package uploaded into the Debian
360 archive.&lt;/p&gt;
361
362 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
363 it into Debian, where it currently
364 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
365 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
366
367 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
368 for the common folks, ie those not running a large government
369 surveillance system? Well, I plan to put it in a computer on my bike
370 and in my car, tracking the cars nearby and allowing me to be notified
371 when number plates on my watch list are discovered. Another use case
372 was suggested by a friend of mine, who wanted to set it up at his home
373 to open the car port automatically when it discovered the plate on his
374 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
375 capable of placing his license plate number of a piece of cardboard to
376 open his car port, men replied that it was always unlocked anyway. I
377 guess for such use case it make sense. I am sure there are other use
378 cases too, for those with imagination and a vision.&lt;/p&gt;
379
380 &lt;p&gt;If you want to build your own version of the Debian package, check
381 out the upstream git source and symlink ./distros/debian to ./debian/
382 before running &quot;debuild&quot; to build the source. Or wait a bit until the
383 package show up in unstable.&lt;/p&gt;
384 </description>
385 </item>
386
387 <item>
388 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
389 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
390 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
391 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
392 <description>&lt;p&gt;Around three years ago, I created
393 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
394 system&lt;/a&gt; to get a more practical solution in Debian for handing
395 hardware related packages. A GUI system in the isenkram package will
396 present a pop-up dialog when some hardware dongle supported by
397 relevant packages in Debian is inserted into the machine. The same
398 lookup mechanism to detect packages is available as command line
399 tools in the isenkram-cli package. In addition to mapping hardware,
400 it will also map kernel firmware files to packages and make it easy to
401 install needed firmware packages automatically. The key for this
402 system to work is a good way to map hardware to packages, in other
403 words, allow packages to announce what hardware they will work
404 with.&lt;/p&gt;
405
406 &lt;p&gt;I started by providing data files in the isenkram source, and
407 adding code to download the latest version of these data files at run
408 time, to ensure every user had the most up to date mapping available.
409 I also added support for storing the mapping in the Packages file in
410 the apt repositories, but did not push this approach because while I
411 was trying to figure out how to best store hardware/package mappings,
412 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
413 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
414 add the hardware mapping into that data set to be able to use
415 appstream as a data source, and this was accepted at least for the
416 Debian version of appstream.&lt;/p&gt;
417
418 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
419 and today I uploaded a new version 0.20 of isenkram adding support for
420 appstream as a data source for mapping hardware to packages. The only
421 package so far using appstream to announce its hardware support is my
422 pymissile package. I got help from Matthias Klumpp with figuring out
423 how do add the required
424 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
425 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
426 this content:&lt;/p&gt;
427
428 &lt;blockquote&gt;&lt;pre&gt;
429 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
430 &amp;lt;component&amp;gt;
431 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
432 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
433 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
434 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
435 &amp;lt;description&amp;gt;
436 &amp;lt;p&amp;gt;
437 Pymissile provides a curses interface to control an original
438 Marks and Spencer / Striker USB Missile Launcher, as well as a
439 motion control script to allow a webcamera to control the
440 launcher.
441 &amp;lt;/p&amp;gt;
442 &amp;lt;/description&amp;gt;
443 &amp;lt;provides&amp;gt;
444 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
445 &amp;lt;/provides&amp;gt;
446 &amp;lt;/component&amp;gt;
447 &lt;/pre&gt;&lt;/blockquote&gt;
448
449 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
450 which is a glob style match rule for hardware specific strings
451 (modalias strings) provided by the Linux kernel. In this case, it
452 will map to all USB devices with vendor code 1130 and product code
453 0202.&lt;/p&gt;
454
455 &lt;p&gt;Note, it is important that the license of all the metadata files
456 are compatible to have permissions to aggregate them into archive wide
457 appstream files. Matthias suggested to use MIT or BSD licenses for
458 these files. A challenge is figuring out a good id for the data, as
459 it is supposed to be globally unique and shared across distributions
460 (in other words, best to coordinate with upstream what to use). But
461 it can be changed later or, so we went with the package name as
462 upstream for this project is dormant.&lt;/p&gt;
463
464 &lt;p&gt;To get the metadata file installed in the correct location for the
465 mirror update scripts to pick it up and include its content the
466 appstream data source, the file must be installed in the binary
467 package under /usr/share/appdata/. I did this by adding the following
468 line to debian/pymissile.install:&lt;/p&gt;
469
470 &lt;blockquote&gt;&lt;pre&gt;
471 debian/pymissile.metainfo.xml usr/share/appdata
472 &lt;/pre&gt;&lt;/blockquote&gt;
473
474 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
475 all packages useful on the current computer automatically, and the GUI
476 pop-up handler will propose to install the package not already
477 installed if a hardware dongle is inserted into the machine in
478 question.&lt;/p&gt;
479
480 &lt;p&gt;Details of the modalias field in appstream is available from the
481 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
482
483 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
484 try running this command on the command line:&lt;/p&gt;
485
486 &lt;blockquote&gt;&lt;pre&gt;
487 cat $(find /sys/devices/|grep modalias)
488 &lt;/pre&gt;&lt;/blockquote&gt;
489
490 &lt;p&gt;To learn more about the isenkram system, please check out
491 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
492 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
493 </description>
494 </item>
495
496 <item>
497 <title>The GNU General Public License is not magic pixie dust</title>
498 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
499 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
500 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
501 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
502 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
503 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
504 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
505 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
506
507 &lt;blockquote&gt;
508
509 &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;
510
511 &lt;blockquote&gt;
512 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
513
514 The first step is to choose a
515 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
516 code.&lt;br/&gt;
517
518 The next step is, when someone fails to follow that copyleft license,
519 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
520
521 and its a simple fact of our modern society that such type of
522 work&lt;br/&gt;
523
524 is incredibly expensive to do and incredibly difficult to do.
525 &lt;/blockquote&gt;
526
527 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
528 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
529 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
530 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
531
532 &lt;p&gt;As the Debian Website
533 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
534 &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;
535 imply, public domain and permissively licensed software can lead to
536 the production of more proprietary software as people discover useful
537 software, extend it and or incorporate it into their hardware or
538 software products. Copyleft licenses such as the GNU GPL were created
539 to close off this avenue to the production of proprietary software but
540 such licenses are not enough. With the ongoing adoption of Free
541 Software by individuals and groups, inevitably the community&#39;s
542 expectations of license compliance are violated, usually out of
543 ignorance of the way Free Software works, but not always. As Karen
544 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
545 Freedom&quot;&gt;FaiF&lt;/a&gt;
546 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
547 copyleft is nothing if no-one is willing and able to stand up in court
548 to protect it. The reality of today&#39;s world is that legal
549 representation is expensive, difficult and time consuming. With
550 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
551 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
552 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
553 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
554 of the Linux project, Debian and other groups against GPL violations.
555 In March the SFC supported a
556 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
557 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
558 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
559 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
560 kernel. Since then two of their sponsors pulled corporate funding and
561 conferences
562 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
563 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
564 less on corporate funding and more on the broad community of
565 individuals who support Free Software and copyleft. So the SFC has
566 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
567 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
568 a community of folks who stand up for copyleft and the GPL by
569 supporting their work on promoting and supporting copyleft and Free
570 Software.&lt;/p&gt;
571
572 &lt;p&gt;If you support Free Software,
573 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
574 what the SFC do, agree with their
575 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
576 principles&lt;/a&gt;, are happy about their
577 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
578 work on a project that is an SFC
579 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
580 just want to stand up for copyleft, please join
581 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
582 Allan Webber&lt;/a&gt;,
583 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
584 Smith&lt;/a&gt;,
585 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
586 Bacon&lt;/a&gt;, myself and
587 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
588 becoming a
589 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
590 next week your donation will be
591 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
592 by an anonymous donor. Please also consider asking your employer to
593 match your donation or become a sponsor of SFC. Don&#39;t forget to
594 spread the word about your support for SFC via email, your blog and or
595 social media accounts.&lt;/p&gt;
596
597 &lt;/blockquote&gt;
598
599 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
600 of Software Freedom Conservancy myself. Perhaps you should be a
601 supporter too?&lt;/p&gt;
602 </description>
603 </item>
604
605 <item>
606 <title>PGP key transition statement for key EE4E02F9</title>
607 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
608 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
609 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
610 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
611 set it up properly. I wanted to generate it offline and have it
612 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
613 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
614 time to sit down with an offline machine almost took forever. But
615 finally I&#39;ve been able to complete the process, and have now moved
616 from my old GPG key to a new GPG key. See
617 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
618 full transition statement, signed with both my old and new key&lt;/a&gt; for
619 the details. This is my new key:&lt;/p&gt;
620
621 &lt;pre&gt;
622 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]
623 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
624 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
625 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
626 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
627 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
628 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
629 &lt;/pre&gt;
630
631 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
632 my old key.&lt;/p&gt;
633
634 &lt;p&gt;If you signed my old key
635 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
636 I&#39;d very much appreciate a signature on my new key, details and
637 instructions in the transition statement. I m happy to reciprocate if
638 you have a similarly signed transition statement to present.&lt;/p&gt;
639 </description>
640 </item>
641
642 <item>
643 <title>The life and death of a laptop battery</title>
644 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
645 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
646 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
647 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
648 But this do not last. The last few laptops gave me a feeling that
649 within a year, the life time is just a fraction of what it used to be,
650 and it slowly become painful to use the laptop without power connected
651 all the time. Because of this, when I got a new Thinkpad X230 laptop
652 about two years ago, I decided to monitor its battery state to have
653 more hard facts when the battery started to fail.&lt;/p&gt;
654
655 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
656
657 &lt;p&gt;First I tried to find a sensible Debian package to record the
658 battery status, assuming that this must be a problem already handled
659 by someone else. I found
660 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
661 which collects statistics from the battery, but it was completely
662 broken. I sent a few suggestions to the maintainer, but decided to
663 write my own collector as a shell script while I waited for feedback
664 from him. Via
665 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
666 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
667 discovered
668 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
669 available in Debian.&lt;/p&gt;
670
671 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
672 battery stats ever since. Now my
673 /var/log/hjemmenett-battery-status.log file contain around 115,000
674 measurements, from the time the battery was working great until now,
675 when it is unable to charge above 7% of original capacity. My
676 collector shell script is quite simple and look like this:&lt;/p&gt;
677
678 &lt;pre&gt;
679 #!/bin/sh
680 # Inspired by
681 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
682 # See also
683 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
684 logfile=/var/log/hjemmenett-battery-status.log
685
686 files=&quot;manufacturer model_name technology serial_number \
687 energy_full energy_full_design energy_now cycle_count status&quot;
688
689 if [ ! -e &quot;$logfile&quot; ] ; then
690 (
691 printf &quot;timestamp,&quot;
692 for f in $files; do
693 printf &quot;%s,&quot; $f
694 done
695 echo
696 ) &gt; &quot;$logfile&quot;
697 fi
698
699 log_battery() {
700 # Print complete message in one echo call, to avoid race condition
701 # when several log processes run in parallel.
702 msg=$(printf &quot;%s,&quot; $(date +%s); \
703 for f in $files; do \
704 printf &quot;%s,&quot; $(cat $f); \
705 done)
706 echo &quot;$msg&quot;
707 }
708
709 cd /sys/class/power_supply
710
711 for bat in BAT*; do
712 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
713 done
714 &lt;/pre&gt;
715
716 &lt;p&gt;The script is called when the power management system detect a
717 change in the power status (power plug in or out), and when going into
718 and out of hibernation and suspend. In addition, it collect a value
719 every 10 minutes. This make it possible for me know when the battery
720 is discharging, charging and how the maximum charge change over time.
721 The code for the Debian package
722 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
723 available on github&lt;/a&gt;.&lt;/p&gt;
724
725 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
726
727 &lt;pre&gt;
728 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
729 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
730 [...]
731 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
732 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
733 &lt;/pre&gt;
734
735 &lt;p&gt;I wrote a small script to create a graph of the charge development
736 over time. This graph depicted above show the slow death of my laptop
737 battery.&lt;/p&gt;
738
739 &lt;p&gt;But why is this happening? Why are my laptop batteries always
740 dying in a year or two, while the batteries of space probes and
741 satellites keep working year after year. If we are to believe
742 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
743 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
744 chance, and the fix is to not charge the Lithium-ion batteries to 100%
745 all the time, but to stay below 90% of full charge most of the time.
746 I&#39;ve been told that the Tesla electric cars
747 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
748 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
749 100% when preparing for a longer trip (not that I would want a car
750 like Tesla where rights to privacy is abandoned, but that is another
751 story), which I guess is the option we should have for laptops on
752 Linux too.&lt;/p&gt;
753
754 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
755 stop charging at 80%, unless requested to charge to 100% once in
756 preparation for a longer trip? I found
757 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
758 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
759 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
760 load).&lt;/p&gt;
761
762 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
763 at the start. I also wonder why the &quot;full capacity&quot; increases some
764 times, and if it is possible to repeat the process to get the battery
765 back to design capacity. And I wonder if the discharge and charge
766 speed change over time, or if this stay the same. I did not yet try
767 to write a tool to calculate the derivative values of the battery
768 level, but suspect some interesting insights might be learned from
769 those.&lt;/p&gt;
770
771 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
772 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
773 packages instead of the tp-smapi-dkms package I had tried to use
774 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
775 and stop. I&#39;ve done so now, but expect my existing battery is toast
776 and need to be replaced. The proposal is unfortunately Thinkpad
777 specific.&lt;/p&gt;
778 </description>
779 </item>
780
781 <item>
782 <title>New laptop - some more clues and ideas based on feedback</title>
783 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
784 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
785 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
786 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
787 need for a new laptop, and provided very useful feedback. I wish to
788 thank every one of these. Several pointed me to the possibility of
789 fixing my X230, and I am already in the process of getting Lenovo to
790 do so thanks to the on site, next day support contract covering the
791 machine. But the battery is almost useless (I expect to replace it
792 with a non-official battery) and I do not expect the machine to live
793 for many more years, so it is time to plan its replacement. If I did
794 not have a support contract, it was suggested to find replacement parts
795 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
796 might present a language barrier as I do not understand French.&lt;/p&gt;
797
798 &lt;p&gt;One tip I got was to use the
799 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
800 compare laptop models. It seem to have more models available than
801 prisjakt.no. Another tip I got from someone I know have similar
802 keyboard preferences was that the HP EliteBook 840 keyboard is not
803 very good, and this matches my experience with earlier EliteBook
804 keyboards I tested. Because of this, I will not consider it any further.
805
806 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
807 newest Thinkpad X model. The keyboard reintroduces mouse buttons
808 (which is missing from the X240), and is working fairly well with
809 Debian Sid/Unstable according to
810 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
811 got on the keyboard quality are not consistent. Some say the keyboard
812 is good, others say it is ok, while others say it is not very good.
813 Those with experience from X41 and and X60 agree that the X250
814 keyboard is not as good as those trusty old laptops, and suggest I
815 keep and fix my X230 instead of upgrading, or get a used X230 to
816 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
817 activity and battery status, which is very convenient on my X230. I&#39;m
818 also told that the CPU fan is running very often, making it a bit
819 noisy. In any case, the X250 do not work out of the box with Debian
820 Stable/Jessie, one of my requirements.&lt;/p&gt;
821
822 &lt;p&gt;I have also gotten a few vendor proposals, one was
823 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
824 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
825 The latter look very attractive to me.&lt;/p&gt;
826
827 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
828 as I keep looking for a replacement.&lt;/p&gt;
829
830 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
831 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
832 different
833 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
834 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
835 </description>
836 </item>
837
838 <item>
839 <title>Time to find a new laptop, as the old one is broken after only two years</title>
840 <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>
841 <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>
842 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
843 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
844 replacement soon. The left 5 cm of the screen on my Thinkpad X230
845 started flickering yesterday, and I suspect the cause is a broken
846 cable, as changing the angle of the screen some times get rid of the
847 flickering.&lt;/p&gt;
848
849 &lt;p&gt;My requirements have not really changed since I bought it, and is
850 still as
851 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
852 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
853 good help from
854 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
855 where I could select at least a few of the requirements (mouse pin,
856 wifi, weight) and go through the rest manually. Three button mouse
857 and a good keyboard is not available as an option, and all the three
858 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
859 G2) lack three mouse buttons). It is also unclear to me how good the
860 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
861 the keyboard, even if the quality and robustness in the X series have
862 deteriorated since X41.&lt;/p&gt;
863
864 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
865 seem sensible to me? Are there better services around to search the
866 set of available laptops for features? Please send me an email if you
867 have suggestions.&lt;/p&gt;
868
869 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
870 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
871 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
872 </description>
873 </item>
874
875 <item>
876 <title>How to stay with sysvinit in Debian Jessie</title>
877 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
878 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
879 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
880 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
881 sysvinit as its boot system by default. But how can one keep using
882 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
883 courtesy of
884 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
885 Schubert&lt;/a&gt; and
886 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
887 McVittie&lt;/a&gt;.
888
889 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
890 keep sysvinit as your boot system, create a file
891 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
892 you upgrade:&lt;/p&gt;
893
894 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
895 Package: systemd-sysv
896 Pin: release o=Debian
897 Pin-Priority: -1
898 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
899
900 &lt;p&gt;This file content will tell apt and aptitude to not consider
901 installing systemd-sysv as part of any installation and upgrade
902 solution when resolving dependencies, and thus tell it to avoid
903 systemd as a default boot system. The end result should be that the
904 upgraded system keep using sysvinit.&lt;/p&gt;
905
906 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
907 get sysvinit installed by default (debootstrap used by
908 debian-installer have no option for this), but one can tell the
909 installer to switch to sysvinit before the first boot. Either by
910 using a kernel argument to the installer, or by adding a line to the
911 preseed file used. First, the kernel command line argument:
912
913 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
914 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
915 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
916
917 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
918
919 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
920 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
921 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
922
923 &lt;p&gt;One can of course also do this after the first boot by installing
924 the sysvinit-core package.&lt;/p&gt;
925
926 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
927 sysvinit boot sequence in Debian have several hardware specific bugs
928 on Linux caused by the fact that it is unpredictable when hardware
929 devices show up during boot. But on the other hand, the new default
930 boot system still have a few rough edges I hope will be fixed before
931 Jessie is released.&lt;/p&gt;
932
933 &lt;p&gt;Update 2014-11-26: Inspired by
934 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
935 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
936 line.&lt;/p&gt;
937 </description>
938 </item>
939
940 <item>
941 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
942 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
943 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
944 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
945 <description>&lt;p&gt;The right to communicate with your friends and family in private,
946 without anyone snooping, is a right every citicen have in a liberal
947 democracy. But this right is under serious attack these days.&lt;/p&gt;
948
949 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
950 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
951 the whisleblower Snowden) more expensive for Internet email,
952 is to deliver all email using SMTP via Tor. Such SMTP option would be
953 a nice addition to the FreedomBox project if we could send email
954 between FreedomBox machines without leaking metadata about the emails
955 to the people peeking on the wire. I
956 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
957 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
958 lot of useful feedback and suggestions. It also became obvious to me
959 that this was not a novel idea, as the same idea was tested and
960 documented by Johannes Berg as early as 2006, and both
961 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
962 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
963 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
964
965 &lt;p&gt;To implement such system one need to set up a Tor hidden service
966 providing the SMTP protocol on port 25, and use email addresses
967 looking like username@hidden-service-name.onion. With such addresses
968 the connections to port 25 on hidden-service-name.onion using Tor will
969 go to the correct SMTP server. To do this, one need to configure the
970 Tor daemon to provide the hidden service and the mail server to accept
971 emails for this .onion domain. To learn more about Exim configuration
972 in Debian and test the design provided by Johannes Berg in his FAQ, I
973 set out yesterday to create a Debian package for making it trivial to
974 set up such SMTP over Tor service based on Debian. Getting it to work
975 were fairly easy, and
976 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
977 source code for the Debian package&lt;/a&gt; is available from github. I
978 plan to move it into Debian if further testing prove this to be a
979 useful approach.&lt;/p&gt;
980
981 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
982 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
983 get rid of exim4). Install tor, clone the git repository mentioned
984 above, build the deb and install it on the machine. Next, run
985 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
986 the instructions to get the service up and running. Restart tor and
987 exim when it is done, and test mail delivery using swaks like
988 this:&lt;/p&gt;
989
990 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
991 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
992 --to fbx@dutlqrrmjhtfa3vp.onion
993 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
994
995 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
996 address with your own address to test your server. :)&lt;/p&gt;
997
998 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
999 easier and more automatic. Especially the tor setup need more work.
1000 Also, the package include a tor-smtp tool written in C, but its task
1001 should probably be rewritten in some script language to make the deb
1002 architecture independent. It would probably also make the code easier
1003 to review. The tor-smtp tool currently need to listen on a socket for
1004 exim to talk to it and is started using xinetd. It would be better if
1005 no daemon and no socket is needed. I suspect it is possible to get
1006 exim to run a command line tool for delivery instead of talking to a
1007 socket, and hope to figure out how in a future version of this
1008 system.&lt;/p&gt;
1009
1010 &lt;p&gt;Until I wipe my test machine, I can be reached using the
1011 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
1012 SMTorP. :)&lt;/p&gt;
1013 </description>
1014 </item>
1015
1016 <item>
1017 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
1018 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
1019 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
1020 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
1021 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
1022 alioth.debian.org, you know the web interface is fairly slow to
1023 operate. First you visit one web page, enter the moderation password
1024 and get a new page shown with a list of all the messages to moderate
1025 and various options for each email address. This take a while for
1026 every list you moderate, and you need to do it regularly to do a good
1027 job as a list moderator. But there is a quick alternative,
1028 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
1029 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
1030 to moderate in a fraction of a second. Here is a test run on two
1031 lists I recently took over:&lt;/p&gt;
1032
1033 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1034 % time listadmin xiph
1035 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1036 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1037
1038 real 0m1.709s
1039 user 0m0.232s
1040 sys 0m0.012s
1041 %
1042 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1043
1044 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
1045 there are no message in the moderation queue. Every morning I
1046 currently moderate 68 mailman lists, and it normally take around two
1047 minutes. When I took over the two pkg-xiph lists above a few days
1048 ago, there were 400 emails waiting in the moderator queue. It took me
1049 less than 15 minutes to process them all using the listadmin
1050 program.&lt;/p&gt;
1051
1052 &lt;p&gt;If you install
1053 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
1054 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
1055 with content like this, the moderation task is a breeze:&lt;/p&gt;
1056
1057 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1058 username username@example.org
1059 spamlevel 23
1060 default discard
1061 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
1062
1063 password secret
1064 adminurl https://{domain}/mailman/admindb/{list}
1065 mailman-list@lists.example.com
1066
1067 password hidden
1068 other-list@otherserver.example.org
1069 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1070
1071 &lt;p&gt;There are other options to set as well. Check the manual page to
1072 learn the details.&lt;/p&gt;
1073
1074 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
1075 the SSL certificate is self signed or not properly signed by a
1076 generally accepted signing authority, you can set a environment
1077 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
1078
1079 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1080 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
1081 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1082
1083 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
1084 can provide an argument to the listadmin script like I do in the
1085 initial screen dump (the xiph argument). Using an argument, only
1086 lists matching the argument string will be processed. This make it
1087 quick to accept messages if you notice the moderation request in your
1088 email.&lt;/p&gt;
1089
1090 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
1091 mailing lists, as I simply do not have time to spend on that if the
1092 process was any slower. The listadmin program have saved me hours of
1093 time I could spend elsewhere over the years. It truly is nice free
1094 software.&lt;/p&gt;
1095
1096 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1097 activities, please send Bitcoin donations to my address
1098 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1099
1100 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1101 configuration example. Also, I&#39;ve been told that the
1102 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1103 sure why.&lt;/p&gt;
1104 </description>
1105 </item>
1106
1107 <item>
1108 <title>Debian Jessie, PXE and automatic firmware installation</title>
1109 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1110 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1111 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1112 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1113 problem that the WiFi card require some firmware to work properly.
1114 And it has been a pain to fix this using preseeding in Debian.
1115 Normally something more is needed. But thanks to
1116 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1117 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1118 to do this using simple preseeding.&lt;/p&gt;
1119
1120 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1121 firmware for the hardware found in the machine (actually, requested by
1122 the kernel modules for the hardware). (It can also install user space
1123 programs supporting the hardware detected, but that is not the focus
1124 of this story.)&lt;/p&gt;
1125
1126 &lt;p&gt;To get this working in the default installation, two preeseding
1127 values are needed. First, the isenkram-cli package must be installed
1128 into the target chroot (aka the hard drive) before tasksel is executed
1129 in the pkgsel step of the debian-installer system. This is done by
1130 preseeding the base-installer/includes debconf value to include the
1131 isenkram-cli package. The package name is next passed to debootstrap
1132 for installation. With the isenkram-cli package in place, tasksel
1133 will automatically use the isenkram tasks to detect hardware specific
1134 packages for the machine being installed and install them, because
1135 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1136
1137 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1138 most firmware unfortunately is non-free. This is done by preseeding
1139 the apt-mirror-setup step. This is unfortunate, but for a lot of
1140 hardware it is the only option in Debian.&lt;/p&gt;
1141
1142 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1143 firmware installed automatically by the installer:&lt;/p&gt;
1144
1145 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1146 base-installer base-installer/includes string isenkram-cli
1147 apt-mirror-setup apt-setup/non-free boolean true
1148 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1149
1150 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1151 both firmware and user space packages when using this method. It also
1152 do not work well, so use version 0.15 or later. Installing both
1153 firmware and user space packages might give you a bit more than you
1154 want, so I decided to split the tasksel task in two, one for firmware
1155 and one for user space programs. The firmware task is enabled by
1156 default, while the one for user space programs is not. This split is
1157 implemented in the package currently in unstable.&lt;/p&gt;
1158
1159 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1160 this recipe work for you. :)&lt;/p&gt;
1161
1162 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1163 foremost, it work because tasksel is modular, and driven by whatever
1164 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1165 isenkram-cli package place two files for tasksel to find. First there
1166 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1167
1168 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1169 Task: isenkram-packages
1170 Section: hardware
1171 Description: Hardware specific packages (autodetected by isenkram)
1172 Based on the detected hardware various hardware specific packages are
1173 proposed.
1174 Test-new-install: show show
1175 Relevance: 8
1176 Packages: for-current-hardware
1177
1178 Task: isenkram-firmware
1179 Section: hardware
1180 Description: Hardware specific firmware packages (autodetected by isenkram)
1181 Based on the detected hardware various hardware specific firmware
1182 packages are proposed.
1183 Test-new-install: mark show
1184 Relevance: 8
1185 Packages: for-current-hardware-firmware
1186 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1187
1188 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1189 should be handled and the Packages line referencing to a script in
1190 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1191 list of packages to install. The for-current-hardware-firmware script
1192 look like this to list relevant firmware for the machine:
1193
1194 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1195 #!/bin/sh
1196 #
1197 PATH=/usr/sbin:$PATH
1198 export PATH
1199 isenkram-autoinstall-firmware -l
1200 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1201
1202 &lt;p&gt;With those two pieces in place, the firmware is installed by
1203 tasksel during the normal d-i run. :)&lt;/p&gt;
1204
1205 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1206 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1207 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1208 install.&lt;/p&gt;
1209
1210 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1211 pilots in testing this feature, as isenkram is used there now to
1212 install firmware, replacing the earlier scripts.&lt;/p&gt;
1213 </description>
1214 </item>
1215
1216 <item>
1217 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1218 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1219 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1220 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1221 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1222 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1223 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1224 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1225
1226 &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;
1227
1228 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1229 about this hidden Linux installation. It is interesting what
1230 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1231 </description>
1232 </item>
1233
1234 <item>
1235 <title>New lsdvd release version 0.17 is ready</title>
1236 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1237 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1238 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1239 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1240 got a new set of developers a few weeks ago, after the original
1241 developer decided to step down and pass the project to fresh blood.
1242 This project is now maintained by Petter Reinholdtsen and Steve
1243 Dibb.&lt;/p&gt;
1244
1245 &lt;p&gt;I just wrapped up
1246 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1247 new lsdvd release&lt;/a&gt;, available in git or from
1248 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1249 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1250 0.17.&lt;/p&gt;
1251
1252 &lt;ul&gt;
1253
1254 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1255 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1256 non-existant, to work around additional copy protection&lt;/li&gt;
1257 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1258 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1259 &lt;li&gt;Fix include orders&lt;/li&gt;
1260 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1261 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1262 &lt;li&gt;Make sure the array size and the array limit used when initialising
1263 the palette size is the same.&lt;/li&gt;
1264 &lt;li&gt;Fix array printing.&lt;/li&gt;
1265 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1266 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1267 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1268 with more GCC compiler warnings.&lt;/li&gt;
1269
1270 &lt;/ul&gt;
1271
1272 &lt;p&gt;This change bring together patches for lsdvd in use in various
1273 Linux and Unix distributions, as well as patches submitted to the
1274 project the last nine years. Please check it out. :)&lt;/p&gt;
1275 </description>
1276 </item>
1277
1278 <item>
1279 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1280 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1281 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1282 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1283 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1284 project&lt;/a&gt; provide a Linux solution for schools, including a
1285 powerful desktop with education software, a central server providing
1286 web pages, user database, user home directories, central login and PXE
1287 boot of both clients without disk and the installation to install Debian
1288 Edu on machines with disk (and a few other services perhaps to small
1289 to mention here). We in the Debian Edu team are currently working on
1290 the Jessie based version, trying to get everything in shape before the
1291 freeze, to avoid having to maintain our own package repository in the
1292 future. The
1293 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1294 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1295 work left. Some fatal problems block testing, breaking the installer,
1296 but it is possible to work around these to get anyway. Here is a
1297 recipe on how to get the installation limping along.&lt;/p&gt;
1298
1299 &lt;p&gt;First, download the test ISO via
1300 &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;,
1301 &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;
1302 or rsync (use
1303 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1304 The ISO build was broken on Tuesday, so we do not get a new ISO every
1305 12 hours or so, but thankfully the ISO we already got we are able to
1306 install with some tweaking.&lt;/p&gt;
1307
1308 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1309 (use Alt-Ctrl-F2), run&lt;/p&gt;
1310
1311 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1312 nano /usr/bin/edu-eatmydata-install
1313 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1314
1315 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1316 optimization. Return to the installation, select the profile you want
1317 and continue. Without this change, exim4-config will fail to install
1318 due to a known bug in eatmydata.&lt;/p&gt;
1319
1320 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1321 this do not work, figure out what your correct value would be. All my
1322 test machines need /dev/sda, so I have no advice if it do not fit
1323 your need.&lt;/p&gt;
1324
1325 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1326 root after the initial boot from hard drive, and install the
1327 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1328 or mate. If you want several desktop options, install more than one
1329 metapackage. Once this is done, reboot and you should have a working
1330 graphical login screen. This workaround should no longer be needed
1331 once the education-tasks package version 1.801 enter testing in two
1332 days.&lt;/p&gt;
1333
1334 &lt;p&gt;I believe the ISO build will start working on two days when the new
1335 tasksel package enter testing and Steve McIntyre get a chance to
1336 update the debian-cd git repository. The eatmydata, grub and desktop
1337 issues are already fixed in unstable and testing, and should show up
1338 on the ISO as soon as the ISO build start working again. Well the
1339 eatmydata optimization is really just disabled. The proper fix
1340 require an upload by the eatmydata maintainer applying the patch
1341 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1342 The rest have proper fixes in unstable.&lt;/p&gt;
1343
1344 &lt;p&gt;I hope this get you going with the installation testing, as we are
1345 quickly running out of time trying to get our Jessie based
1346 installation ready before the distribution freeze in a month.&lt;/p&gt;
1347 </description>
1348 </item>
1349
1350 <item>
1351 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1352 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1354 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1355 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1356 to handle my fairly large DVD collection. It is a nice command line
1357 tool to get details about a DVD, like title, tracks, track length,
1358 etc, in XML, Perl or human readable format. But lsdvd have not seen
1359 any new development since 2006 and had a few irritating bugs affecting
1360 its use with some DVDs. Upstream seemed to be dead, and in January I
1361 sent a small probe asking for a version control repository for the
1362 project, without any reply. But I use it regularly and would like to
1363 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1364 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1365 the project admin, and after getting a reply from him explaining that
1366 he was no longer interested in the project, I asked if I could take
1367 over. And yesterday, I became project admin.&lt;/p&gt;
1368
1369 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1370 maintainer interested in joining forces to maintain the upstream
1371 project, and I hope we can get a new release out fairly quickly,
1372 collecting the patches spread around on the internet into on place.
1373 I&#39;ve added the relevant Debian patches to the freshly created git
1374 repository, and expect the Gentoo patches to make it too. If you got
1375 a DVD collection and care about command line tools, check out
1376 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1377 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1378 list&lt;/a&gt;. :)&lt;/p&gt;
1379 </description>
1380 </item>
1381
1382 <item>
1383 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1384 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1386 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1387 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1388 a lot quicker. When we install more than 2000 packages in
1389 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1390 tasksel in the installer, unpacking the binary packages take forever.
1391 A part of the slow I/O issue was discussed in
1392 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1393 much file system sync-ing done by dpkg, which is the package
1394 responsible for unpacking the binary packages. Other parts (like code
1395 executed by postinst scripts) might also sync to disk during
1396 installation. All this sync-ing to disk do not really make sense to
1397 me. If the machine crash half-way through, I start over, I do not try
1398 to salvage the half installed system. So the failure sync-ing is
1399 supposed to protect against, hardware or system crash, is not really
1400 relevant while the installer is running.&lt;/p&gt;
1401
1402 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1403 system sync()-ing in a fairly non-intrusive way, without the need to
1404 change the code in several packages. The idea is not new, but I have
1405 not heard anyone propose the approach using dpkg-divert before. It
1406 depend on the small and clever package
1407 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1408 uses LD_PRELOAD to replace the system functions for syncing data to
1409 disk with functions doing nothing, thus allowing programs to live
1410 dangerous while speeding up disk I/O significantly. Instead of
1411 modifying the implementation of dpkg, apt and tasksel (which are the
1412 packages responsible for selecting, fetching and installing packages),
1413 it occurred to me that we could just divert the programs away, replace
1414 them with a simple shell wrapper calling
1415 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1416 Two days ago I decided to test the idea, and wrapped up a simple
1417 implementation for the Debian Edu udeb.&lt;/p&gt;
1418
1419 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1420 time of the pkgsel step (installing tasks) from 64 to less than 44
1421 minutes (20 minutes shaved off the installation) on an old Dell
1422 Latitude D505 machine. I am not quite sure what the optimised time
1423 would have been, as I messed up the testing a bit, causing the debconf
1424 priority to get low enough for two questions to pop up during
1425 installation. As soon as I saw the questions I moved the installation
1426 along, but do not know how long the question were holding up the
1427 installation. I did some more measurements using Debian Edu Jessie,
1428 and got these results. The time measured is the time stamp in
1429 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1430 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1431 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1432 timing thus do not depend on how quickly the user handle the tasksel
1433 dialog.&lt;/p&gt;
1434
1435 &lt;p&gt;&lt;table&gt;
1436
1437 &lt;tr&gt;
1438 &lt;th&gt;Machine/setup&lt;/th&gt;
1439 &lt;th&gt;Original tasksel&lt;/th&gt;
1440 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1441 &lt;th&gt;Reduction&lt;/th&gt;
1442 &lt;/tr&gt;
1443
1444 &lt;tr&gt;
1445 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1446 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1447 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1448 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1449 &lt;/tr&gt;
1450
1451 &lt;tr&gt;
1452 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1453 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1454 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1455 &lt;td&gt;23 min 40%&lt;/td&gt;
1456 &lt;/tr&gt;
1457
1458 &lt;tr&gt;
1459 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1460 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1461 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1462 &lt;td&gt;11 min 50%&lt;/td&gt;
1463 &lt;/tr&gt;
1464
1465 &lt;tr&gt;
1466 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1467 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1468 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1469 &lt;td&gt;2 min 33%&lt;/td&gt;
1470 &lt;/tr&gt;
1471
1472 &lt;tr&gt;
1473 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1474 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1475 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1476 &lt;td&gt;4 min 21%&lt;/td&gt;
1477 &lt;/tr&gt;
1478
1479 &lt;/table&gt;&lt;/p&gt;
1480
1481 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1482 time is spent downloading packages. The connection to the Internet
1483 was 100Mbit/s during testing, so downloading should not be a
1484 significant factor in the measurement. Download typically took a few
1485 seconds to a few minutes, depending on the amount of packages being
1486 installed.&lt;/p&gt;
1487
1488 &lt;p&gt;The speedup is implemented by using two hooks in
1489 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1490 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1491 finish-install.d hook to remove the divert at the end of the
1492 installation. I picked the pre-pkgsel.d hook instead of the
1493 post-base-installer.d hook because I test using an ISO without the
1494 eatmydata package included, and the post-base-installer.d hook in
1495 Debian Edu can only operate on packages included in the ISO. The
1496 negative effect of this is that I am unable to activate this
1497 optimization for the kernel installation step in d-i. If the code is
1498 moved to the post-base-installer.d hook, the speedup would be larger
1499 for the entire installation.&lt;/p&gt;
1500
1501 &lt;p&gt;I&#39;ve implemented this in the
1502 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1503 git repository, and plan to provide the optimization as part of the
1504 Debian Edu installation. If you want to test this yourself, you can
1505 create two files in the installer (or in an udeb). One shell script
1506 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1507
1508 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1509 #!/bin/sh
1510 set -e
1511 . /usr/share/debconf/confmodule
1512 info() {
1513 logger -t my-pkgsel &quot;info: $*&quot;
1514 }
1515 error() {
1516 logger -t my-pkgsel &quot;error: $*&quot;
1517 }
1518 override_install() {
1519 apt-install eatmydata || true
1520 if [ -x /target/usr/bin/eatmydata ] ; then
1521 for bin in dpkg apt-get aptitude tasksel ; do
1522 file=/usr/bin/$bin
1523 # Test that the file exist and have not been diverted already.
1524 if [ -f /target$file ] ; then
1525 info &quot;diverting $file using eatmydata&quot;
1526 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1527 &gt; /target$file.edu
1528 chmod 755 /target$file.edu
1529 in-target dpkg-divert --package debian-edu-config \
1530 --rename --quiet --add $file
1531 ln -sf ./$bin.edu /target$file
1532 else
1533 error &quot;unable to divert $file, as it is missing.&quot;
1534 fi
1535 done
1536 else
1537 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1538 fi
1539 }
1540
1541 override_install
1542 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1543
1544 &lt;p&gt;To clean up, another shell script should go into
1545 /usr/lib/finish-install.d/ with code like this:
1546
1547 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1548 #! /bin/sh -e
1549 . /usr/share/debconf/confmodule
1550 error() {
1551 logger -t my-finish-install &quot;error: $@&quot;
1552 }
1553 remove_install_override() {
1554 for bin in dpkg apt-get aptitude tasksel ; do
1555 file=/usr/bin/$bin
1556 if [ -x /target$file.edu ] ; then
1557 rm /target$file
1558 in-target dpkg-divert --package debian-edu-config \
1559 --rename --quiet --remove $file
1560 rm /target$file.edu
1561 else
1562 error &quot;Missing divert for $file.&quot;
1563 fi
1564 done
1565 sync # Flush file buffers before continuing
1566 }
1567
1568 remove_install_override
1569 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1570
1571 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1572 edu-eatmydata-install and call it from the pre-pkgsel.d and
1573 finish-install.d scripts.&lt;/p&gt;
1574
1575 &lt;p&gt;By now you might ask if this change should get into the normal
1576 Debian installer too? I suspect it should, but am not sure the
1577 current debian-installer coordinators find it useful enough. It also
1578 depend on the side effects of the change. I&#39;m not aware of any, but I
1579 guess we will see if the change is safe after some more testing.
1580 Perhaps there is some package in Debian depending on sync() and
1581 fsync() having effect? Perhaps it should go into its own udeb, to
1582 allow those of us wanting to enable it to do so without affecting
1583 everyone.&lt;/p&gt;
1584
1585 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1586 will break installation of all programs using gnutls because of
1587 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1588 eatmydata package in Debian will solve it.&lt;/p&gt;
1589
1590 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1591 the optimization work again. And I have discovered that the
1592 dpkg-divert trick is not really needed and implemented a slightly
1593 simpler approach as part of the debian-edu-install package. See
1594 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1595
1596 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1597 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1598 triggering on i386 made it into testing, and broke this installation
1599 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1600 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1601 </description>
1602 </item>
1603
1604 <item>
1605 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1606 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1607 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1608 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1609 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1610 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1611 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1612 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1613 learn that there is a large set of publicly available key servers to
1614 use when looking for peoples public key. So far I have used
1615 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1616 were misbehaving, but those days are ended. The servers I have used
1617 up until yesterday have been slow and some times unavailable. I hope
1618 those problems are gone now.&lt;/p&gt;
1619
1620 &lt;p&gt;Behind the round robin DNS entry of the
1621 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1622 there is a pool of more than 100 keyservers which are checked every
1623 day to ensure they are well connected and up to date. It must be
1624 better than what I have used so far. :)&lt;/p&gt;
1625
1626 &lt;p&gt;Yesterdays speaker told me that the service is the default
1627 keyserver provided by the default configuration in GnuPG, but this do
1628 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1629
1630 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1631 line:&lt;/p&gt;
1632
1633 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1634 keyserver pool.sks-keyservers.net
1635 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1636
1637 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1638 entries in DNS. Just for fun, I did just that at work, so now every
1639 user of GnuPG at the University of Oslo should find a OpenGPG
1640 keyserver automatically should their need it:&lt;/p&gt;
1641
1642 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1643 % host -t srv _pgpkey-http._tcp.uio.no
1644 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1645 %
1646 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1647
1648 &lt;p&gt;Now if only
1649 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1650 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1651 very happy. It can look up a given key or search for a user ID, but I
1652 normally do not want that, but to find a trust path from my key to
1653 another key. Given a user ID or key ID, I would like to find (and
1654 download) the keys representing a signature path from my key to the
1655 key in question, to be able to get a trust path between the two keys.
1656 This is as far as I can tell not possible today. Perhaps something
1657 for a future version of the protocol?&lt;/p&gt;
1658 </description>
1659 </item>
1660
1661 <item>
1662 <title>From English wiki to translated PDF and epub via Docbook</title>
1663 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1664 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1665 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1666 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1667 project&lt;/a&gt; provide an instruction manual for teachers, system
1668 administrators and other users that contain useful tips for setting up
1669 and maintaining a Debian Edu installation. This text is about how the
1670 text processing of this manual is handled in the project.&lt;/p&gt;
1671
1672 &lt;p&gt;One goal of the project is to provide information in the native
1673 language of its users, and for this we need to handle translations.
1674 But we also want to make sure each language contain the same
1675 information, so for this we need a good way to keep the translations
1676 in sync. And we want it to be easy for our users to improve the
1677 documentation, avoiding the need to learn special formats or tools to
1678 contribute, and the obvious way to do this is to make it possible to
1679 edit the documentation using a web browser. We also want it to be
1680 easy for translators to keep the translation up to date, and give them
1681 help in figuring out what need to be translated. Here is the list of
1682 tools and the process we have found trying to reach all these
1683 goals.&lt;/p&gt;
1684
1685 &lt;p&gt;We maintain the authoritative source of our manual in the
1686 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1687 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1688 front page with references to the different chapters, several pages
1689 for each chapter, and finally one &quot;collection page&quot; gluing all the
1690 chapters together into one large web page (aka
1691 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1692 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1693 processing and translations. Thanks to the fact that the
1694 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1695 wiki.debian.org support exporting pages in
1696 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1697 the list of pages to export using the raw version of the AllInOne
1698 page, loop over each of them to generate a Docbook XML version of the
1699 manual. This process also download images and transform image
1700 references to use the locally downloaded images. The generated
1701 Docbook XML files are slightly broken, so some post-processing is done
1702 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1703 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1704 a handfull of images. The XML file can now be used to generate PDF, HTML
1705 and epub versions of the English manual. This is the basic step of
1706 our process, making PDF (using dblatex), HTML (using xsltproc) and
1707 epub (using dbtoepub) version from Docbook XML, and the resulting files
1708 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1709
1710 &lt;p&gt;But English documentation is not enough for us. We want translated
1711 documentation too, and we want to make it easy for translators to
1712 track the English original. For this we use the
1713 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1714 which allow us to transform the English Docbook XML file into a
1715 translation file (a .pot file), usable with the normal gettext based
1716 translation tools used by those translating free software. The pot
1717 file is used to create and maintain translation files (several .po
1718 files), which the translations update with the native language
1719 translations of all titles, paragraphs and blocks of text in the
1720 original. The next step is combining the original English Docbook XML
1721 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1722 create a translated Docbook XML file (in this case
1723 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1724 translated, if the translation is not complete) Docbook XML file can
1725 then be used like the original to create a PDF, HTML and epub version
1726 of the documentation.&lt;/p&gt;
1727
1728 &lt;p&gt;The translators use different tools to edit the .po files. We
1729 recommend using
1730 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1731 while some use emacs and vi, others can use web based editors like
1732 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1733 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1734 is where the .po file end up, in our git repository. Updated
1735 translations can either be committed directly to git, or submitted as
1736 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1737 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1738
1739 &lt;p&gt;One challenge is images, which both might need to be translated (if
1740 they show translated user applications), and are needed in different
1741 formats when creating PDF and HTML versions (epub is a HTML version in
1742 this regard). For this we transform the original PNG images to the
1743 needed density and format during build, and have a way to provide
1744 translated images by storing translated versions in
1745 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1746 package maintainers know more.&lt;/p&gt;
1747
1748 &lt;p&gt;If you wonder what the result look like, we provide
1749 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1750 of the documentation packages on the web&lt;/a&gt;. See for example the
1751 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1752 PDF version&lt;/a&gt; or the
1753 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1754 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1755 but perhaps it will be done in the future.&lt;/p&gt;
1756
1757 &lt;p&gt;To learn more, check out
1758 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1759 debian-edu-doc package&lt;/a&gt;,
1760 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1761 manual on the wiki&lt;/a&gt; and
1762 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1763 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1764 </description>
1765 </item>
1766
1767 <item>
1768 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1769 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1770 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1771 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1772 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1773 related packages relevant for the computer installed automatically.
1774 So I implemented one, using
1775 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1776 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1777 run tasksel as user root. You should be presented with a new option,
1778 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1779 select it, tasksel will install the packages isenkram claim is fit for
1780 the current hardware, hot pluggable or not.&lt;p&gt;
1781
1782 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1783 description, and the other is the script used to extract the list of
1784 packages to install. The first part is in
1785 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1786 this:&lt;/p&gt;
1787
1788 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1789 Task: isenkram
1790 Section: hardware
1791 Description: Hardware specific packages (autodetected by isenkram)
1792 Based on the detected hardware various hardware specific packages are
1793 proposed.
1794 Test-new-install: mark show
1795 Relevance: 8
1796 Packages: for-current-hardware
1797 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1798
1799 &lt;p&gt;The second part is in
1800 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1801 this:&lt;/p&gt;
1802
1803 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1804 #!/bin/sh
1805 #
1806 (
1807 isenkram-lookup
1808 isenkram-autoinstall-firmware -l
1809 ) | sort -u
1810 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1811
1812 &lt;p&gt;All in all, a very short and simple implementation making it
1813 trivial to install the hardware dependent package we all may want to
1814 have installed on our machines. I&#39;ve not been able to find a way to
1815 get tasksel to tell you exactly which packages it plan to install
1816 before doing the installation. So if you are curious or careful,
1817 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1818
1819 &lt;p&gt;The information about which packages are handling which hardware is
1820 fetched either from the isenkram package itself in
1821 /usr/share/isenkram/, from git.debian.org or from the APT package
1822 database (using the Modaliases header). The APT package database
1823 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1824 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1825 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1826 the python-apt code (bug
1827 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1828 workaround I was able to get rid of the file descriptor leak and
1829 reduce the memory leak from ~30 MiB per hardware detection down to
1830 around 2 MiB per hardware detection. It should make the desktop
1831 daemon a lot more useful. The fix is in version 0.7 uploaded to
1832 unstable today.&lt;/p&gt;
1833
1834 &lt;p&gt;I believe the current way of mapping hardware to packages in
1835 Isenkram is is a good draft, but in the future I expect isenkram to
1836 use the AppStream data source for this. A proposal for getting proper
1837 AppStream support into Debian is floating around as
1838 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1839 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1840 project&lt;/a&gt; will take place this summer to improve the situation. I
1841 look forward to seeing the result, and welcome patches for isenkram to
1842 start using the information when it is ready.&lt;/p&gt;
1843
1844 &lt;p&gt;If you want your package to map to some specific hardware, either
1845 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1846 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1847 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1848 package. See also
1849 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1850 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1851 the information will be migrated to AppStream eventually, but for the
1852 moment I got no better place to store it.&lt;/p&gt;
1853 </description>
1854 </item>
1855
1856 <item>
1857 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1858 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1859 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1860 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1861 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1862 project&lt;/a&gt; is working on providing the software and hardware to make
1863 it easy for non-technical people to host their data and communication
1864 at home, and being able to communicate with their friends and family
1865 encrypted and away from prying eyes. It is still going strong, and
1866 today a major mile stone was reached.&lt;/p&gt;
1867
1868 &lt;p&gt;Today, the last of the packages currently used by the project to
1869 created the system images were accepted into Debian Unstable. It was
1870 the freedombox-setup package, which is used to configure the images
1871 during build and on the first boot. Now all one need to get going is
1872 the build code from the freedom-maker git repository and packages from
1873 Debian. And once the freedombox-setup package enter testing, we can
1874 build everything directly from Debian. :)&lt;/p&gt;
1875
1876 &lt;p&gt;Some key packages used by Freedombox are
1877 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1878 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1879 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1880 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1881 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1882 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1883 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1884 are plans to integrate more packages into the setup. User
1885 documentation is maintained on the Debian wiki. Please
1886 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1887 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1888
1889 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1890 setup, run this on a Debian machine using a user with sudo rights to
1891 become root:&lt;/p&gt;
1892
1893 &lt;p&gt;&lt;pre&gt;
1894 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1895 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1896 u-boot-tools
1897 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1898 freedom-maker
1899 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1900 &lt;/pre&gt;&lt;/p&gt;
1901
1902 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1903 devices. See the README in the freedom-maker git repo for more
1904 details on the build. If you do not want all three images, trim the
1905 make line. Note that the virtualbox-image target is not really
1906 virtualbox specific. It create a x86 image usable in kvm, qemu,
1907 vmware and any other x86 virtual machine environment. You might need
1908 the version of vmdebootstrap in Jessie to get the build working, as it
1909 include fixes for a race condition with kpartx.&lt;/p&gt;
1910
1911 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1912 method, boot a Debian Wheezy ISO and use this boot argument to load
1913 the preseed values:&lt;/p&gt;
1914
1915 &lt;p&gt;&lt;pre&gt;
1916 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;
1917 &lt;/pre&gt;&lt;/p&gt;
1918
1919 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1920 it still work.&lt;/p&gt;
1921
1922 &lt;p&gt;If you wonder how to help, one task you could look at is using
1923 systemd as the boot system. It will become the default for Linux in
1924 Jessie, so we need to make sure it is usable on the Freedombox. I did
1925 a simple test a few weeks ago, and noticed dnsmasq failed to start
1926 during boot when using systemd. I suspect there are other problems
1927 too. :) To detect problems, there is a test suite included, which can
1928 be run from the plinth web interface.&lt;/p&gt;
1929
1930 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1931 us get the new release published. :) Please join us on
1932 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1933 irc.debian.org)&lt;/a&gt; and
1934 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1935 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1936 </description>
1937 </item>
1938
1939 <item>
1940 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1941 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1942 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1943 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1944 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1945 solution for use at home. My requirements are simple, it must be
1946 cheap and locally encrypted (in other words, I keep the encryption
1947 keys, the storage provider do not have access to my private files).
1948 One idea me and my friends had many years ago, before the cloud
1949 storage providers showed up, was to use Google mail as storage,
1950 writing a Linux block device storing blocks as emails in the mail
1951 service provided by Google, and thus get heaps of free space. On top
1952 of this one can add encryption, RAID and volume management to have
1953 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1954 I never found time to implement such system. But the last few weeks I
1955 have looked at a system called
1956 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1957 mounted network backed file system with the features I need.&lt;/p&gt;
1958
1959 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1960 handling several different storage providers, any with Amazon S3,
1961 Google Drive or OpenStack API. There are heaps of such storage
1962 providers. S3QL can also use a local directory as storage, which
1963 combined with sshfs allow for file storage on any ssh server. S3QL
1964 include support for encryption, compression, de-duplication, snapshots
1965 and immutable file systems, allowing me to mount the remote storage as
1966 a local mount point, look at and use the files as if they were local,
1967 while the content is stored in the cloud as well. This allow me to
1968 have a backup that should survive fire. The file system can not be
1969 shared between several machines at the same time, as only one can
1970 mount it at the time, but any machine with the encryption key and
1971 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1972
1973 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1974 package is included already. So to get started, run &lt;tt&gt;apt-get
1975 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1976 Greenqloud, after reading their nice recipe on
1977 &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
1978 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1979 in Iceland more than those in USA when it come to keeping my personal
1980 data safe and private, and thus would rather spend money on a company
1981 in Iceland. Another nice recipe is available from the article
1982 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1983 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1984 Admin magazine. When the provider is picked, figure out how to get
1985 the API key needed to connect to the storage API. With Greencloud,
1986 the key did not show up until I had added payment details to my
1987 account.&lt;/p&gt;
1988
1989 &lt;p&gt;Armed with the API access details, it is time to create the file
1990 system. First, create a new bucket in the cloud. This bucket is the
1991 file system storage area. I picked a bucket name reflecting the
1992 machine that was going to store data there, but any name will do.
1993 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1994 the API login and password, and a locally created password. Store it
1995 all in ~root/.s3ql/authinfo2 like this:
1996
1997 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1998 [s3c]
1999 storage-url: s3c://s.greenqloud.com:443/bucket-name
2000 backend-login: API-login
2001 backend-password: API-password
2002 fs-passphrase: local-password
2003 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2004
2005 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
2006 but any sensible way to create a fairly random password should do it.
2007 Armed with these details, it is now time to run mkfs, entering the API
2008 details and password to create it:&lt;/p&gt;
2009
2010 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2011 # mkdir -m 700 /var/lib/s3ql-cache
2012 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2013 --ssl s3c://s.greenqloud.com:443/bucket-name
2014 Enter backend login:
2015 Enter backend password:
2016 Before using S3QL, make sure to read the user&#39;s guide, especially
2017 the &#39;Important Rules to Avoid Loosing Data&#39; section.
2018 Enter encryption password:
2019 Confirm encryption password:
2020 Generating random encryption key...
2021 Creating metadata tables...
2022 Dumping metadata...
2023 ..objects..
2024 ..blocks..
2025 ..inodes..
2026 ..inode_blocks..
2027 ..symlink_targets..
2028 ..names..
2029 ..contents..
2030 ..ext_attributes..
2031 Compressing and uploading metadata...
2032 Wrote 0.00 MB of compressed metadata.
2033 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2034
2035 &lt;p&gt;The next step is mounting the file system to make the storage available.
2036
2037 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2038 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2039 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2040 Using 4 upload threads.
2041 Downloading and decompressing metadata...
2042 Reading metadata...
2043 ..objects..
2044 ..blocks..
2045 ..inodes..
2046 ..inode_blocks..
2047 ..symlink_targets..
2048 ..names..
2049 ..contents..
2050 ..ext_attributes..
2051 Mounting filesystem...
2052 # df -h /s3ql
2053 Filesystem Size Used Avail Use% Mounted on
2054 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
2055 #
2056 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2057
2058 &lt;p&gt;The file system is now ready for use. I use rsync to store my
2059 backups in it, and as the metadata used by rsync is downloaded at
2060 mount time, no network traffic (and storage cost) is triggered by
2061 running rsync. To unmount, one should not use the normal umount
2062 command, as this will not flush the cache to the cloud storage, but
2063 instead running the umount.s3ql command like this:
2064
2065 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2066 # umount.s3ql /s3ql
2067 #
2068 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2069
2070 &lt;p&gt;There is a fsck command available to check the file system and
2071 correct any problems detected. This can be used if the local server
2072 crashes while the file system is mounted, to reset the &quot;already
2073 mounted&quot; flag. This is what it look like when processing a working
2074 file system:&lt;/p&gt;
2075
2076 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2077 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
2078 Using cached metadata.
2079 File system seems clean, checking anyway.
2080 Checking DB integrity...
2081 Creating temporary extra indices...
2082 Checking lost+found...
2083 Checking cached objects...
2084 Checking names (refcounts)...
2085 Checking contents (names)...
2086 Checking contents (inodes)...
2087 Checking contents (parent inodes)...
2088 Checking objects (reference counts)...
2089 Checking objects (backend)...
2090 ..processed 5000 objects so far..
2091 ..processed 10000 objects so far..
2092 ..processed 15000 objects so far..
2093 Checking objects (sizes)...
2094 Checking blocks (referenced objects)...
2095 Checking blocks (refcounts)...
2096 Checking inode-block mapping (blocks)...
2097 Checking inode-block mapping (inodes)...
2098 Checking inodes (refcounts)...
2099 Checking inodes (sizes)...
2100 Checking extended attributes (names)...
2101 Checking extended attributes (inodes)...
2102 Checking symlinks (inodes)...
2103 Checking directory reachability...
2104 Checking unix conventions...
2105 Checking referential integrity...
2106 Dropping temporary indices...
2107 Backing up old metadata...
2108 Dumping metadata...
2109 ..objects..
2110 ..blocks..
2111 ..inodes..
2112 ..inode_blocks..
2113 ..symlink_targets..
2114 ..names..
2115 ..contents..
2116 ..ext_attributes..
2117 Compressing and uploading metadata...
2118 Wrote 0.89 MB of compressed metadata.
2119 #
2120 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2121
2122 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2123 quick, about the same speed as local file access. Uploading large
2124 amount of data is to me limited by the bandwidth out of and into my
2125 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2126 which is very close to my upload speed, and downloading the same
2127 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2128 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2129 network, not the file system code. I do not know what a good cache
2130 size would be, but suspect that the cache should e larger than your
2131 working set.&lt;/p&gt;
2132
2133 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2134 time. If another machine try, it is told that the file system is
2135 busy:&lt;/p&gt;
2136
2137 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2138 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2139 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2140 Using 8 upload threads.
2141 Backend reports that fs is still mounted elsewhere, aborting.
2142 #
2143 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2144
2145 &lt;p&gt;The file content is uploaded when the cache is full, while the
2146 metadata is uploaded once every 24 hour by default. To ensure the
2147 file system content is flushed to the cloud, one can either umount the
2148 file system, or ask S3QL to flush the cache and metadata using
2149 s3qlctrl:
2150
2151 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2152 # s3qlctrl upload-meta /s3ql
2153 # s3qlctrl flushcache /s3ql
2154 #
2155 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2156
2157 &lt;p&gt;If you are curious about how much space your data uses in the
2158 cloud, and how much compression and deduplication cut down on the
2159 storage usage, you can use s3qlstat on the mounted file system to get
2160 a report:&lt;/p&gt;
2161
2162 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2163 # s3qlstat /s3ql
2164 Directory entries: 9141
2165 Inodes: 9143
2166 Data blocks: 8851
2167 Total data size: 22049.38 MB
2168 After de-duplication: 21955.46 MB (99.57% of total)
2169 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2170 Database size: 2.39 MB (uncompressed)
2171 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2172 #
2173 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2174
2175 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2176 storage. I did not try to locate them all, but am aware of at least
2177 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2178 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2179 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2180 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2181 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2182 accept payment in Bitcoin. Pick one that suit your need. Some of
2183 them provide several GiB of free storage, but the prize models are
2184 quite different and you will have to figure out what suits you
2185 best.&lt;/p&gt;
2186
2187 &lt;p&gt;While researching this blog post, I had a look at research papers
2188 and posters discussing the S3QL file system. There are several, which
2189 told me that the file system is getting a critical check by the
2190 science community and increased my confidence in using it. One nice
2191 poster is titled
2192 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2193 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2194 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2195 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2196 and Pamela Smith. Please have a look.&lt;/p&gt;
2197
2198 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2199 check out the mounted S3QL file system to see if it would be usable as
2200 a home directory (in other word, that it provided POSIX semantics when
2201 it come to locking and umask handling etc). Running
2202 &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
2203 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2204 no error was found. So the file system can be used for home
2205 directories, if one chooses to do so.&lt;/p&gt;
2206
2207 &lt;p&gt;If you do not want a locally file system, and want something that
2208 work without the Linux fuse file system, I would like to mention the
2209 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2210 provide locally encrypted backup using a command line client. It have
2211 a nicer access control system, where one can split out read and write
2212 access, allowing some systems to write to the backup and others to
2213 only read from it.&lt;/p&gt;
2214
2215 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2216 activities, please send Bitcoin donations to my address
2217 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2218 </description>
2219 </item>
2220
2221 <item>
2222 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2223 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2224 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2225 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2226 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2227 project&lt;/a&gt; is working on providing the software and hardware for
2228 making it easy for non-technical people to host their data and
2229 communication at home, and being able to communicate with their
2230 friends and family encrypted and away from prying eyes. It has been
2231 going on for a while, and is slowly progressing towards a new test
2232 release (0.2).&lt;/p&gt;
2233
2234 &lt;p&gt;And what day could be better than the Pi day to announce that the
2235 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2236 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2237 system), and can also be installed using a Debian installer preseed
2238 file. The Debian based Freedombox is now based on Debian Jessie,
2239 where most of the needed packages used are already present. Only one,
2240 the freedombox-setup package, is missing. To try to build your own
2241 boot image to test the current status, fetch the freedom-maker scripts
2242 and build using
2243 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2244 with a user with sudo access to become root:
2245
2246 &lt;pre&gt;
2247 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2248 freedom-maker
2249 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2250 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2251 u-boot-tools
2252 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2253 &lt;/pre&gt;
2254
2255 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2256 devices. See the README for more details on the build. If you do not
2257 want all three images, trim the make line. But note that thanks to &lt;a
2258 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2259 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2260 kpartx call.&lt;/p&gt;
2261
2262 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2263 method, boot a Debian Wheezy ISO and use this boot argument to load
2264 the preseed values:&lt;/p&gt;
2265
2266 &lt;pre&gt;
2267 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;
2268 &lt;/pre&gt;
2269
2270 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2271 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2272 currently hang while setting up APT sources. Killing the
2273 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2274 installation will get the installation going. This affect all
2275 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2276
2277 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2278 us get the new release published. :) Please join us on
2279 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2280 irc.debian.org)&lt;/a&gt; and
2281 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2282 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2283 </description>
2284 </item>
2285
2286 <item>
2287 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2288 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2289 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2290 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2291 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2292 innetgr tools, because I needed them in
2293 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2294 ng-utils, and it has served me well. I placed the project under the
2295 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2296 repository. But many years ago, the CVS repository was dropped (lost,
2297 not migrated to new hardware, not sure), and the project have lacked a
2298 proper home since then.&lt;/p&gt;
2299
2300 &lt;p&gt;Last summer, I had a look at the package and made a new release
2301 fixing a irritating crash bug, but was unable to store the changes in
2302 a proper source control system. I applied for a project on
2303 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2304 to follow up on it. Until today. :)&lt;/p&gt;
2305
2306 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2307 now have a new home, and a git repository with the highlight of the
2308 history of the project. I published all release tarballs and imported
2309 them into the git repository. As the project is really stable and not
2310 expected to gain new features any time soon, I decided to make a new
2311 release and call it 1.0. Visit the new project home on
2312 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2313 if you want to check it out. The new version is also uploaded into
2314 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2315 </description>
2316 </item>
2317
2318 <item>
2319 <title>Testing sysvinit from experimental in Debian Hurd</title>
2320 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2321 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2322 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2323 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2324 their changes into sysvinit, to allow them to use the normal sysvinit
2325 boot system instead of their old one. This follow up on the
2326 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2327 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2328 get Debian on Hurd working more like Debian on Linux. To get started,
2329 I downloaded a prebuilt hard disk image from
2330 &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;,
2331 and started it using virt-manager.&lt;/p&gt;
2332
2333 &lt;p&gt;The first think I had to do after logging in (root without any
2334 password) was to get the network operational. I followed
2335 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2336 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2337 commands as root to get the machine to accept a IP address from the
2338 kvm internal DHCP server:&lt;/p&gt;
2339
2340 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2341 settrans -fgap /dev/netdde /hurd/netdde
2342 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2343 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2344 dhclient /dev/eth0
2345 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2346
2347 &lt;p&gt;After this, the machine had internet connectivity, and I could
2348 upgrade it and install the sysvinit packages from experimental and
2349 enable it as the default boot system in Hurd.&lt;/p&gt;
2350
2351 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2352 running on the machine it for ssh login to work a password need to be
2353 set. Also, note that a bug somewhere in openssh on Hurd block
2354 compression from working. Remember to turn that off on the client
2355 side.&lt;/p&gt;
2356
2357 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2358 stuff:&lt;/p&gt;
2359
2360 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2361 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2362 deb http://http.debian.net/debian/ experimental main
2363 EOF
2364 apt-get update
2365 apt-get dist-upgrade
2366 apt-get install -t experimental initscripts sysv-rc sysvinit \
2367 sysvinit-core sysvinit-utils
2368 update-alternatives --config runsystem
2369 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2370
2371 &lt;p&gt;To reboot after switching boot system, you have to use
2372 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2373 yet a sysvinit process able to receive the signals from the normal
2374 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2375 upgrading every package and rebooting, the network come up with DHCP
2376 after boot as it should, and the settrans/pkill hack mentioned at the
2377 start is no longer needed. But for some strange reason, there are no
2378 longer any login prompt in the virtual console, so I logged in using
2379 ssh instead.
2380
2381 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2382 fail some times. No idea what the cause is, but hope the Hurd porters
2383 figure it out. At least Justus said on IRC (#debian-hurd on
2384 irc.debian.org) that they are aware of the problem. A way to reduce
2385 the impact is to upgrade to the Hurd packages built by Justus by
2386 adding this repository to the machine:&lt;/p&gt;
2387
2388 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2389 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2390 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2391 EOF
2392 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2393
2394 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2395 http://ftp.debian-ports.org/debian, because some of the packages in
2396 unstable do not yet include the required patches that are lingering in
2397 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2398
2399 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2400 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2401 i emacs - GNU Emacs editor (metapackage)
2402 i gdb - GNU Debugger
2403 i hurd-recommended - Miscellaneous translators
2404 i isc-dhcp-client - ISC DHCP client
2405 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2406 i libc-bin - Embedded GNU C Library: Binaries
2407 i libc-dev-bin - Embedded GNU C Library: Development binaries
2408 i libc0.3 - Embedded GNU C Library: Shared libraries
2409 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2410 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2411 i multiarch-support - Transitional package to ensure multiarch compatibilit
2412 i A x11-common - X Window System (X.Org) infrastructure
2413 i xorg - X.Org X Window System
2414 i A xserver-xorg - X.Org X server
2415 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2416 #
2417 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2418
2419 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2420 X.org did not work out of the box and I never took the time to follow
2421 the porters instructions to fix it. This time I was interested in the
2422 command line stuff.&lt;p&gt;
2423 </description>
2424 </item>
2425
2426 <item>
2427 <title>New chrpath release 0.16</title>
2428 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2429 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2430 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2431 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2432 find problems in C, C++ and Java code using static source code
2433 analysis. It can detect a lot of different problems, and is very
2434 useful to find memory and locking bugs in the error handling part of
2435 the source. The company behind it provide
2436 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2437 a community service&lt;/a&gt;, and many hundred free software projects are
2438 already checked. A few days ago I decided to have a closer look at
2439 the Coverity system, and discovered that the
2440 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2441 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2442 projects I am involved with was already registered. But these are
2443 fairly big, and I would also like to have a small and easy project to
2444 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2445 checking of the chrpath project&lt;/a&gt;. It was
2446 added to the checker and discovered seven potential defects. Six of
2447 these were real, mostly resource &quot;leak&quot; when the program detected an
2448 error. Nothing serious, as the resources would be released a fraction
2449 of a second later when the program exited because of the error, but it
2450 is nice to do it right in case the source of the program some time in
2451 the future end up in a library. Having fixed all defects and added
2452 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2453 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2454 publish a new release. These are the release notes:&lt;/p&gt;
2455
2456 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2457
2458 &lt;ul&gt;
2459
2460 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2461 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2462 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2463
2464 &lt;/ul&gt;
2465
2466 &lt;p&gt;You can
2467 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2468 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2469 project if something is wrong with the new release. The test suite
2470 did not discover any old errors, so if you find a new one, please also
2471 include a test suite check.&lt;/p&gt;
2472 </description>
2473 </item>
2474
2475 <item>
2476 <title>New chrpath release 0.15</title>
2477 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2478 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2479 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2480 <description>&lt;p&gt;After many years break from the package and a vain hope that
2481 development would be continued by someone else, I finally pulled my
2482 acts together this morning and wrapped up a new release of chrpath,
2483 the command line tool to modify the rpath and runpath of already
2484 compiled ELF programs. The update was triggered by the persistence of
2485 Isha Vishnoi at IBM, which needed a new config.guess file to get
2486 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2487 is working on. I checked the
2488 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2489 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2490 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2491 packages for interesting patches (failed to find the source from
2492 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2493 These are the release notes:&lt;/p&gt;
2494
2495 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2496
2497 &lt;ul&gt;
2498
2499 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2500 with newer architectures. Thanks to isha vishnoi for the heads
2501 up.&lt;/li&gt;
2502
2503 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2504
2505 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2506 Matthias Klose.&lt;/li&gt;
2507
2508 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2509 Petr Machata found in Fedora.&lt;/li&gt;
2510
2511 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2512 .dynamic is a NULL terminated string. Based on patch found in
2513 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2514
2515 &lt;/ul&gt;
2516
2517 &lt;p&gt;You can
2518 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2519 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2520 project if something is wrong with the new release. The test suite
2521 did not discover any old errors, so if you find a new one, please also
2522 include a testsuite check.&lt;/p&gt;
2523 </description>
2524 </item>
2525
2526 <item>
2527 <title>Debian init.d boot script example for rsyslog</title>
2528 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2530 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2531 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2532 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2533 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2534 init.d scripts at all. Here is an example init.d script, ie a rewrite
2535 of /etc/init.d/rsyslog:&lt;/p&gt;
2536
2537 &lt;p&gt;&lt;pre&gt;
2538 #!/lib/init/init-d-script
2539 ### BEGIN INIT INFO
2540 # Provides: rsyslog
2541 # Required-Start: $remote_fs $time
2542 # Required-Stop: umountnfs $time
2543 # X-Stop-After: sendsigs
2544 # Default-Start: 2 3 4 5
2545 # Default-Stop: 0 1 6
2546 # Short-Description: enhanced syslogd
2547 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2548 # It is quite compatible to stock sysklogd and can be
2549 # used as a drop-in replacement.
2550 ### END INIT INFO
2551 DESC=&quot;enhanced syslogd&quot;
2552 DAEMON=/usr/sbin/rsyslogd
2553 &lt;/pre&gt;&lt;/p&gt;
2554
2555 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2556 script was 137 lines, and the above is just 15 lines, most of it meta
2557 info/comments.&lt;/p&gt;
2558
2559 &lt;p&gt;How to do this, you ask? Well, one create a new script
2560 /lib/init/init-d-script looking something like this:
2561
2562 &lt;p&gt;&lt;pre&gt;
2563 #!/bin/sh
2564
2565 # Define LSB log_* functions.
2566 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2567 # and status_of_proc is working.
2568 . /lib/lsb/init-functions
2569
2570 #
2571 # Function that starts the daemon/service
2572
2573 #
2574 do_start()
2575 {
2576 # Return
2577 # 0 if daemon has been started
2578 # 1 if daemon was already running
2579 # 2 if daemon could not be started
2580 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2581 || return 1
2582 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2583 $DAEMON_ARGS \
2584 || return 2
2585 # Add code here, if necessary, that waits for the process to be ready
2586 # to handle requests from services started subsequently which depend
2587 # on this one. As a last resort, sleep for some time.
2588 }
2589
2590 #
2591 # Function that stops the daemon/service
2592 #
2593 do_stop()
2594 {
2595 # Return
2596 # 0 if daemon has been stopped
2597 # 1 if daemon was already stopped
2598 # 2 if daemon could not be stopped
2599 # other if a failure occurred
2600 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2601 RETVAL=&quot;$?&quot;
2602 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2603 # Wait for children to finish too if this is a daemon that forks
2604 # and if the daemon is only ever run from this initscript.
2605 # If the above conditions are not satisfied then add some other code
2606 # that waits for the process to drop all resources that could be
2607 # needed by services started subsequently. A last resort is to
2608 # sleep for some time.
2609 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2610 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2611 # Many daemons don&#39;t delete their pidfiles when they exit.
2612 rm -f $PIDFILE
2613 return &quot;$RETVAL&quot;
2614 }
2615
2616 #
2617 # Function that sends a SIGHUP to the daemon/service
2618 #
2619 do_reload() {
2620 #
2621 # If the daemon can reload its configuration without
2622 # restarting (for example, when it is sent a SIGHUP),
2623 # then implement that here.
2624 #
2625 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2626 return 0
2627 }
2628
2629 SCRIPTNAME=$1
2630 scriptbasename=&quot;$(basename $1)&quot;
2631 echo &quot;SN: $scriptbasename&quot;
2632 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2633 script=&quot;$1&quot;
2634 shift
2635 . $script
2636 else
2637 exit 0
2638 fi
2639
2640 NAME=$(basename $DAEMON)
2641 PIDFILE=/var/run/$NAME.pid
2642
2643 # Exit if the package is not installed
2644 #[ -x &quot;$DAEMON&quot; ] || exit 0
2645
2646 # Read configuration variable file if it is present
2647 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2648
2649 # Load the VERBOSE setting and other rcS variables
2650 . /lib/init/vars.sh
2651
2652 case &quot;$1&quot; in
2653 start)
2654 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2655 do_start
2656 case &quot;$?&quot; in
2657 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2658 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2659 esac
2660 ;;
2661 stop)
2662 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2663 do_stop
2664 case &quot;$?&quot; in
2665 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2666 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2667 esac
2668 ;;
2669 status)
2670 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2671 ;;
2672 #reload|force-reload)
2673 #
2674 # If do_reload() is not implemented then leave this commented out
2675 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2676 #
2677 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2678 #do_reload
2679 #log_end_msg $?
2680 #;;
2681 restart|force-reload)
2682 #
2683 # If the &quot;reload&quot; option is implemented then remove the
2684 # &#39;force-reload&#39; alias
2685 #
2686 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2687 do_stop
2688 case &quot;$?&quot; in
2689 0|1)
2690 do_start
2691 case &quot;$?&quot; in
2692 0) log_end_msg 0 ;;
2693 1) log_end_msg 1 ;; # Old process is still running
2694 *) log_end_msg 1 ;; # Failed to start
2695 esac
2696 ;;
2697 *)
2698 # Failed to stop
2699 log_end_msg 1
2700 ;;
2701 esac
2702 ;;
2703 *)
2704 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2705 exit 3
2706 ;;
2707 esac
2708
2709 :
2710 &lt;/pre&gt;&lt;/p&gt;
2711
2712 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2713 lot. I did not really polish the approach, so it might not always
2714 work out of the box, but you get the idea. I did not try very hard to
2715 optimize it nor make it more robust either.&lt;/p&gt;
2716
2717 &lt;p&gt;A better argument for switching init system in Debian than reducing
2718 the size of init scripts (which is a good thing to do anyway), is to
2719 get boot system that is able to handle the kernel events sensibly and
2720 robustly, and do not depend on the boot to run sequentially. The boot
2721 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2722 </description>
2723 </item>
2724
2725 <item>
2726 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2727 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2728 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2729 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2730 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2731 remote display access is the preferred solution with oVirt and RedHat
2732 Enterprise Virtualization, and I was sad to discover the other day
2733 that the browser plugin needed to use these systems seamlessly was
2734 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2735 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2736 2013-04-01, so I decided to wrap up a package based on the great work
2737 from Cajus Pollmeier and put it in a collab-maint maintained git
2738 repository to get a package I could use. I would very much like
2739 others to help me maintain the package (or just take over, I do not
2740 mind), but as no-one had volunteered so far, I just uploaded it to
2741 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2742
2743 &lt;p&gt;The source is now available from
2744 &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;
2745 </description>
2746 </item>
2747
2748 <item>
2749 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2750 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2751 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2752 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2753 <description>&lt;p&gt;The
2754 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2755 program is a a very nice system to create virtual machine images. It
2756 create a image file, add a partition table, mount it and run
2757 debootstrap in the mounted directory to create a Debian system on a
2758 stick. Yesterday, I decided to try to teach it how to make images for
2759 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2760 of a plan to simplify the build system for
2761 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2762 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2763 the virtualbox images, but its current build system made multistrap
2764 based system for Dreamplug images, and it is lacking support for
2765 Raspberry Pi.&lt;/p&gt;
2766
2767 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2768 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2769 code and adjusted it to be able to build armel images on my amd64
2770 Debian laptop. I ended up giving vmdebootstrap five new options,
2771 allowing me to replicate the image creation process I use to make
2772 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2773 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2774 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2775 call debootstrap with --foreign and to copy the handler into the
2776 generated chroot before running the second stage. This allow
2777 vmdebootstrap to create armel images on an amd64 host. Next I added
2778 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2779 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2780 given file system type, allowing me to create an image with a vfat
2781 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2782 variant&lt;/tt&gt; option to allow me to create smaller images without the
2783 Debian base system packages installed. Finally, I added an option
2784 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2785 as a boot loader. It is not needed on the Raspberry Pi and probably
2786 most other non-x86 architectures. The changes were accepted by the
2787 upstream author of vmdebootstrap yesterday and today, and is now
2788 available from
2789 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2790 upstream project page&lt;/a&gt;.&lt;/p&gt;
2791
2792 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2793 create a small script (the customize script) to add the non-free
2794 binary blob needed to boot the Raspberry Pi and the APT source
2795 list:&lt;/p&gt;
2796
2797 &lt;p&gt;&lt;pre&gt;
2798 #!/bin/sh
2799 set -e # Exit on first error
2800 rootdir=&quot;$1&quot;
2801 cd &quot;$rootdir&quot;
2802 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2803 deb http://http.debian.net/debian/ jessie main contrib non-free
2804 EOF
2805 # Install non-free binary blob needed to boot Raspberry Pi. This
2806 # install a kernel somewhere too.
2807 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2808 -O $rootdir/usr/bin/rpi-update
2809 chmod a+x $rootdir/usr/bin/rpi-update
2810 mkdir -p $rootdir/lib/modules
2811 touch $rootdir/boot/start.elf
2812 chroot $rootdir rpi-update
2813 &lt;/pre&gt;&lt;/p&gt;
2814
2815 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2816 to build the image:&lt;/p&gt;
2817
2818 &lt;pre&gt;
2819 sudo ./vmdebootstrap \
2820 --variant minbase \
2821 --arch armel \
2822 --distribution jessie \
2823 --mirror http://http.debian.net/debian \
2824 --image test.img \
2825 --size 600M \
2826 --bootsize 64M \
2827 --boottype vfat \
2828 --log-level debug \
2829 --verbose \
2830 --no-kernel \
2831 --no-extlinux \
2832 --root-password raspberry \
2833 --hostname raspberrypi \
2834 --foreign /usr/bin/qemu-arm-static \
2835 --customize `pwd`/customize \
2836 --package netbase \
2837 --package git-core \
2838 --package binutils \
2839 --package ca-certificates \
2840 --package wget \
2841 --package kmod
2842 &lt;/pre&gt;&lt;/p&gt;
2843
2844 &lt;p&gt;The list of packages being installed are the ones needed by
2845 rpi-update to make the image bootable on the Raspberry Pi, with the
2846 exception of netbase, which is needed by debootstrap to find
2847 /etc/hosts with the minbase variant. I really wish there was a way to
2848 set up an Raspberry Pi using only packages in the Debian archive, but
2849 that is not possible as far as I know, because it boots from the GPU
2850 using a non-free binary blob.&lt;/p&gt;
2851
2852 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2853 probably a few others installed. I have not checked the complete
2854 build dependency list.&lt;/p&gt;
2855
2856 &lt;p&gt;The resulting image will not use the hardware floating point unit
2857 on the Raspberry PI, because the armel architecture in Debian is not
2858 optimized for that use. So the images created will be a bit slower
2859 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2860 </description>
2861 </item>
2862
2863 <item>
2864 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2865 <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>
2866 <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>
2867 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2868 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2869 wider attention. I recommend signing and donating to each one of
2870 these. :)&lt;/p&gt;
2871
2872 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2873 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2874 Women program which is a Google Summer of Code like initiative to get
2875 more women involved in free software. One debian sponsor has offered
2876 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2877 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2878 hope you will to. :)&lt;/p&gt;
2879
2880 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2881 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2882 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2883 take place these days, and their need to fund the work. I&#39;ve already
2884 donated. Are you next?&lt;/p&gt;
2885
2886 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2887 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2888 statement under the heading
2889 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2890 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2891 Norwegian government. So far 499 signatures. I hope you will sign it
2892 too.&lt;/p&gt;
2893 </description>
2894 </item>
2895
2896 <item>
2897 <title>Videos about the Freedombox project - for inspiration and learning</title>
2898 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2900 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2901 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2902 project&lt;/a&gt; have been going on for a while, and have presented the
2903 vision, ideas and solution several places. Here is a little
2904 collection of videos of talks and presentation of the project.&lt;/p&gt;
2905
2906 &lt;ul&gt;
2907
2908 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2909 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2910
2911 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2912 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2913
2914 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2915 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2916 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2917 (Youtube)&lt;/li&gt;
2918
2919 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2920 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2921
2922 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2923 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2924
2925 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2926 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2927 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2928
2929 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2930 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2931 (Youtube)&lt;/li&gt;
2932
2933 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2934 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2935
2936 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2937 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2938
2939 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2940 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2941 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2942
2943 &lt;/ul&gt;
2944
2945 &lt;p&gt;A larger list is available from
2946 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2947 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2948
2949 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2950 Jessie is coming along quite well, and soon both Owncloud and using
2951 Tor should be available for testers of the Freedombox solution. :) In
2952 a few weeks I hope everything needed to test it is included in Debian.
2953 The withsqlite package is already in Debian, and the plinth package is
2954 pending in NEW. The third and vital part of that puzzle is the
2955 metapackage/setup framework, which is still pending an upload. Join
2956 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2957 (#freedombox on irc.debian.org)&lt;/a&gt; and
2958 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2959 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2960 </description>
2961 </item>
2962
2963 <item>
2964 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2965 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2966 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2967 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2968 <description>&lt;p&gt;I was introduced to the
2969 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2970 in 2010, when Eben Moglen presented his vision about serving the need
2971 of non-technical people to keep their personal information private and
2972 within the legal protection of their own homes. The idea is to give
2973 people back the power over their network and machines, and return
2974 Internet back to its intended peer-to-peer architecture. Instead of
2975 depending on a central service, the Freedombox will give everyone
2976 control over their own basic infrastructure.&lt;/p&gt;
2977
2978 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2979 taken priority. But this summers nasty news about the misuse of trust
2980 and privilege exercised by the &quot;western&quot; intelligence gathering
2981 communities increased my eagerness to contribute to a point where I
2982 actually started working on the project a while back.&lt;/p&gt;
2983
2984 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2985 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2986 create a simple and cheap Debian based appliance that anyone can hook
2987 up in their home and get access to secure and private services and
2988 communication. The initial deployment platform have been the
2989 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2990 which is a piece of hardware I do not own. So to be able to test what
2991 the current Freedombox setup look like, I had to come up with a way to install
2992 it on some hardware I do have access to. I have rewritten the
2993 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2994 image build framework to use .deb packages instead of only copying
2995 setup into the boot images, and thanks to this rewrite I am able to
2996 set up any machine supported by Debian Wheezy as a Freedombox, using
2997 the previously mentioned deb (and a few support debs for packages
2998 missing in Debian).&lt;/p&gt;
2999
3000 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
3001 scripts
3002 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
3003 and a administrative web interface
3004 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
3005 withsqlite), as well as a privacy enhancing proxy based on
3006 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
3007 (freedombox-privoxy). There is also a web/javascript based XMPP
3008 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
3009 trying (unsuccessfully so far) to talk to the XMPP server
3010 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
3011 web interface is pluggable, and the goal is to use it to enable OpenID
3012 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3013 this is really working yet, see
3014 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
3015 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
3016 on github at the moment. The HTTP proxy is operational out of the
3017 box, and the admin web interface can be used to add/remove plinth
3018 users. I&#39;ve not been able to do anything else with it so far, but
3019 know there are several branches spread around github and other places
3020 with lots of half baked features.&lt;/p&gt;
3021
3022 &lt;p&gt;Anyway, if you want to have a look at the current state, the
3023 following recipes should work to give you a test machine to poke
3024 at.&lt;/p&gt;
3025
3026 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
3027
3028 &lt;ol&gt;
3029
3030 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
3031 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
3032 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
3033 to the Debian installer:&lt;p&gt;
3034 &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;
3035
3036 &lt;li&gt;Answer the few language/region/password questions and pick disk to
3037 install on.&lt;/li&gt;
3038
3039 &lt;li&gt;When the installation is finished and the machine have rebooted a
3040 few times, your Freedombox is ready for testing.&lt;/li&gt;
3041
3042 &lt;/ol&gt;
3043
3044 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
3045
3046 &lt;ol&gt;
3047
3048 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
3049 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
3050 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
3051 &lt;pre&gt;
3052 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
3053 &lt;/pre&gt;&lt;/li&gt;
3054 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
3055 &lt;pre&gt;
3056 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3057 apt-key add -
3058 apt-get update
3059 apt-get install freedombox-setup
3060 /usr/lib/freedombox/setup
3061 &lt;/pre&gt;&lt;/li&gt;
3062 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
3063
3064 &lt;/ol&gt;
3065
3066 &lt;p&gt;You can test it on other architectures too, but because the
3067 freedombox-privoxy package is binary, it will only work as intended on
3068 the architectures where I have had time to build the binary and put it
3069 in my APT repository. But do not let this stop you. It is only a
3070 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
3071
3072 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
3073 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
3074 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
3075 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
3076
3077 &lt;p&gt;Please let me know if this works for you, or if you have any
3078 problems. We gather on the IRC channel
3079 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
3080 irc.debian.org and the
3081 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
3082 mailing list&lt;/a&gt;.&lt;/p&gt;
3083
3084 &lt;p&gt;Once you get your freedombox operational, you can visit
3085 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
3086 welcome screen (dead end - do not be surprised if you are unable to
3087 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
3088 to look at the rest of plinth. The default user is &#39;admin&#39; and the
3089 default password is &#39;secret&#39;.&lt;/p&gt;
3090 </description>
3091 </item>
3092
3093 <item>
3094 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
3095 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3096 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3097 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3098 <description>&lt;p&gt;Earlier, I reported about
3099 &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
3100 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3101 told by IBM that the original disk should be thrown away. And as
3102 there no longer was a problem if I bricked the firmware, I decided
3103 today to try to install Intel firmware to replace the Lenovo firmware
3104 currently on the disk.&lt;/p&gt;
3105
3106 &lt;p&gt;I searched the Intel site for firmware, and found
3107 &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;
3108 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3109 according to the site should contain the latest firmware for SSD
3110 disks. I inserted the broken disk in one of my spare laptops and
3111 booted the ISO from a USB stick. The disk was recognized, but the
3112 program claimed the newest firmware already were installed and refused
3113 to insert any Intel firmware. So no change, and the disk is still
3114 unable to handle write load. :( I guess the only way to get them
3115 working would be if Lenovo releases new firmware. No idea how likely
3116 that is. Anyway, just blogging about this test for completeness. I
3117 got a working Samsung disk, and see no point in spending more time on
3118 the broken disks.&lt;/p&gt;
3119 </description>
3120 </item>
3121
3122 <item>
3123 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3124 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3125 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3126 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3127 <description>&lt;p&gt;Today I switched to
3128 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3129 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3130 my new Thinkpad X230, which was delivered with an
3131 &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
3132 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3133 sustained writes. My hardware supplier have been very forthcoming in
3134 trying to find a solution, and after first trying with another
3135 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3136 disk instead to fix it once and for all. The Samsung disk survived
3137 the installation of Debian with encrypted disks (filling the disk with
3138 random data during installation killed the first two), and I thus
3139 decided to trust it with my data. I have installed it as a Debian Edu
3140 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3141 server at home using Kerberos and LDAP, and will use it as my work
3142 station from now on.&lt;/p&gt;
3143
3144 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3145 Debian Wheezy default installation need to be tuned a bit to increase
3146 performance and increase life time of the disk. The Linux kernel and
3147 user space applications do not yet adjust automatically to such
3148 environment. To make it easier for my self, I created a draft Debian
3149 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3150 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3151 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3152 is set up to adjust the setup of the machine by just installing the
3153 package. If there is any non-SSD disk in the machine, the package
3154 will refuse to install, as I did not try to write any logic to sort
3155 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3156
3157 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3158 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3159 where I set up the machine with one large encrypted partition (in
3160 addition to /boot), put LVM on top of this and set up partitions on
3161 top of this again. See the README file in the package source for the
3162 references I used to pick the settings. At the moment these
3163 parameters are tuned:&lt;/p&gt;
3164
3165 &lt;ul&gt;
3166
3167 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3168 (adding discard to /etc/crypttab)&lt;/li&gt;
3169
3170 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3171 this case a cryptsetup partition) by changing issue_discards from
3172 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3173
3174 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3175 systems.&lt;/li&gt;
3176
3177 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3178 /etc/fstab.&lt;/li&gt;
3179
3180 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3181
3182 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3183 cron.daily).&lt;/li&gt;
3184
3185 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3186 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3187
3188 &lt;/ul&gt;
3189
3190 &lt;p&gt;During installation, I cancelled the part where the installer fill
3191 the disk with random data, as this would kill the SSD performance for
3192 little gain. My goal with the encrypted file system is to ensure
3193 those stealing my laptop end up with a brick and not a working
3194 computer. I have no hope in keeping the really resourceful people
3195 from getting the data on the disk (see
3196 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3197 Thus I concluded that adding the discard option to crypttab is the
3198 right thing to do.&lt;/p&gt;
3199
3200 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3201 it for SSD, but others recommended deadline and a benchmark I found
3202 indicated that deadline might be better for interactive use.&lt;/p&gt;
3203
3204 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3205 and ext4, but read that it would give a performance hit ever time a
3206 file is removed, and thought it best to that that slowdown once a day
3207 instead of during my work.&lt;/p&gt;
3208
3209 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3210 this is already done by Debian Edu.&lt;/p&gt;
3211
3212 &lt;p&gt;I have not yet started on the user space tuning. I expect
3213 iceweasel need some tuning, and perhaps other applications too, but
3214 have not yet had time to investigate those parts.&lt;/p&gt;
3215
3216 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3217 there.&lt;/p&gt;
3218
3219 &lt;p&gt;As for the answer to the question in the title of this blog post,
3220 as far as I know, the only solution I know about is to replace the
3221 disk. It might be possible to flash it with Intel firmware instead of
3222 the Lenovo firmware. But I have not tried and did not want to do so
3223 without approval from Lenovo as I wanted to keep the warranty on the
3224 disk until a solution was found and they wanted the broken disks
3225 back.&lt;/p&gt;
3226 </description>
3227 </item>
3228
3229 <item>
3230 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3231 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3232 <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>
3233 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3234 <description>&lt;p&gt;A few days ago, I wrote about
3235 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3236 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3237 was dying during installation because it is unable to cope with
3238 sustained write. My supplier is in contact with
3239 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3240 replacement disk to try to fix the problem. They decided to send an
3241 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3242
3243 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3244 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3245 same firmware version as the original. This time my hope raised
3246 slightly as the installation progressed, as the original disk used to
3247 die after 4-7% of the disk was written to, while this time it kept
3248 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3249 died again and I was back on square one. I still do not have a new
3250 laptop with a disk I can trust. I can not live with a disk that might
3251 lock up when I download a new
3252 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3253 other large files. I look forward to hearing from my supplier with
3254 the next proposal from Lenovo.&lt;/p&gt;
3255
3256 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3257 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3258 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3259 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3260 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3261 P/N 45N8295, P0C38732.&lt;/p&gt;
3262
3263 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3264 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3265 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3266 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3267 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3268 P/N 45N8295, P0C38732.&lt;/p&gt;
3269
3270 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3271 SA, date and WNPP values. Mentioning all the details here in case
3272 someone is able to use the information to find a way to identify the
3273 failing disk among working ones (if any such working disk actually
3274 exist).&lt;/p&gt;
3275 </description>
3276 </item>
3277
3278 <item>
3279 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3280 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3281 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3282 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3283 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3284 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3285 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3286 member assosiation NUUG&lt;/a&gt; and
3287 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3288 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3289 Bitraf&lt;/a&gt;.&lt;/p&gt;
3290
3291 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3292 welcome, and there is no fee to participate. There is on the other
3293 hand limited space, and only room for 30 people. Please put your name
3294 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3295 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3296 </description>
3297 </item>
3298
3299 <item>
3300 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3301 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3302 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3303 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3304 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3305 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3306 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3307 time to spend on it, and it took a while to find a model I believe
3308 will do the job, but two days ago the replacement finally arrived. I
3309 ended up picking a
3310 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3311 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3312 a roaming workstation, and it seemed to work flawlessly. But my
3313 second installation with encrypted disk was not as successful. More
3314 on that below.&lt;/p&gt;
3315
3316 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3317 important requirements (robust and with a good keyboard) are never
3318 listed in the feature list. But I did get good help from the search
3319 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3320 allowed me to limit the list of interesting laptops based on my other
3321 requirements. A bit surprising that SSD disk are not disks according
3322 to that search interface, so I had to drop specifying the number of
3323 disks from my search parameters. I also asked around among friends to
3324 get their impression on keyboards and robustness.&lt;/p&gt;
3325
3326 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3327 X41. I am not quite convinced about the keyboard, as it is
3328 significantly wider than my old keyboard, and I have to stretch my
3329 hand a lot more to reach the edges. But the key response is fairly
3330 good and the individual key shape is fairly easy to handle, so I hope
3331 I will get used to it. My old X40 was starting to fail, and I really
3332 needed a new laptop now. :)&lt;/p&gt;
3333
3334 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3335 visit to the BIOS during boot it disable it.&lt;/p&gt;
3336
3337 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3338 lock up during load. And this happen when installing Debian Wheezy
3339 with encrypted disk, while the disk is being filled with random data.
3340 I also tested to install Ubuntu Raring, and it happen there too if I
3341 reenable the code to fill the disk with random data (it is disabled by
3342 default in Ubuntu). And the bug with is already known. It was
3343 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3344 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3345 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3346 kernel developers as
3347 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3348 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3349 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3350 Lenovo forums, both for
3351 &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
3352 2012-11-10&lt;/a&gt; and for
3353 &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
3354 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3355 reports state that the disk lock up during use if many writes are done
3356 on the disk, so it is much no use to work around the installation
3357 problem and end up with a computer that can lock up at any moment.
3358 There is even a
3359 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3360 available&lt;/a&gt; that will lock up the hard drive after running a few
3361 minutes by writing to a file.&lt;/p&gt;
3362
3363 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3364 contacting PCHELP Norway (request 01D1FDP) which handle support
3365 requests for Lenovo, his first suggestion was to upgrade the disk
3366 firmware. Unfortunately there is no newer firmware available from
3367 Lenovo, as my disk already have the most recent one (version LF1i). I
3368 hope to hear more from him today and hope the problem can be
3369 fixed. :)&lt;/p&gt;
3370 </description>
3371 </item>
3372
3373 <item>
3374 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3375 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3376 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3377 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3378 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3379 trusty old Thinkpad X41. Unfortunately I did not have much time to
3380 spend on it, but today the replacement finally arrived. I ended up
3381 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3382 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3383 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3384 this, it is installing what I hope will be a more final installation,
3385 with a encrypted hard drive to ensure any dope head stealing it end up
3386 with an expencive door stop.&lt;/p&gt;
3387
3388 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3389 important requirements (robust and with a good keyboard) are never
3390 listed in the feature list. But I did get good help from the search
3391 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3392 allowed me to limit the list of interesting laptops based on my other
3393 requirements. A bit surprising that SSD disk are not disks, so I had
3394 to drop number of disks from my search parameters.&lt;/p&gt;
3395
3396 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3397 wider than my old keyboard, and I have to stretch my hand a lot more
3398 to reach the edges. But the key response is fairly good and the
3399 individual key shape is fairly easy to handle, so I hope I will get
3400 used to it. My old X40 was starting to fail, and I really needed a
3401 new laptop now. :)&lt;/p&gt;
3402
3403 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3404 </description>
3405 </item>
3406
3407 <item>
3408 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3409 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3410 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3411 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3412 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3413 perfectly capable of, and I have to do it manually to get things
3414 working. One such task is to find out what firmware packages are
3415 needed to get the hardware on my computer working. Most often this
3416 affect the wifi card, but some times it even affect the RAID
3417 controller or the ethernet card. Today I pushed version 0.4 of the
3418 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3419 including a new script isenkram-autoinstall-firmware handling the
3420 process of asking all the loaded kernel modules what firmware files
3421 they want, find debian packages providing these files and install the
3422 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3423
3424 &lt;p&gt;&lt;pre&gt;
3425 # isenkram-autoinstall-firmware
3426 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3427 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3428 info: locating packages with the requested firmware files
3429 info: Updating APT sources after adding non-free APT source
3430 info: trying to install firmware-ipw2x00
3431 firmware-ipw2x00
3432 firmware-ipw2x00
3433 Preconfiguring packages ...
3434 Selecting previously deselected package firmware-ipw2x00.
3435 (Reading database ... 259727 files and directories currently installed.)
3436 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3437 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3438 #
3439 &lt;/pre&gt;&lt;/p&gt;
3440
3441 &lt;p&gt;When all the requested firmware is present, a simple message is
3442 printed instead:&lt;/p&gt;
3443
3444 &lt;p&gt;&lt;pre&gt;
3445 # isenkram-autoinstall-firmware
3446 info: did not find any firmware files requested by loaded kernel modules. exiting
3447 #
3448 &lt;/pre&gt;&lt;/p&gt;
3449
3450 &lt;p&gt;It could use some polish, but it is already working well and saving
3451 me some time when setting up new machines. :)&lt;/p&gt;
3452
3453 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3454 kernel modules, and look up each one of them using modinfo, to find
3455 the firmware files listed in the module meta-information. Next, it
3456 download the Contents file from a nearby APT mirror, and search for
3457 the firmware files in this file to locate the package with the
3458 requested firmware file. If the package is in the non-free section, a
3459 non-free APT source is added and the package is installed using
3460 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3461 machine.&lt;/p&gt;
3462
3463 &lt;p&gt;I hope someone find time to implement a more polished version of
3464 this script as part of the hw-detect debian-installer module, to
3465 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3466 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3467 firmware during a PXE install when the packages already are available
3468 from the nearby Debian mirror.&lt;/p&gt;
3469 </description>
3470 </item>
3471
3472 <item>
3473 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3474 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3475 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3476 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3477 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3478 the screen just turn black when Linux boot, either during installation
3479 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3480 last few years, but only recently understood the cause. I&#39;ve seen it
3481 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3482 The reason seem to be in the wiring of some laptops. The system to
3483 control the screen background light is inverted, so when Linux try to
3484 turn the brightness fully on, it end up turning it off instead. I do
3485 not know which Linux drivers are affected, but this post is about the
3486 i915 driver used by the
3487 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3488 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3489
3490 &lt;p&gt;The problem can be worked around two ways. Either by adding
3491 i915.invert_brightness=1 as a kernel option, or by adding a file in
3492 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3493 option when it load the i915 kernel module. On Debian and Ubuntu, it
3494 can be done by running these commands as root:&lt;/p&gt;
3495
3496 &lt;pre&gt;
3497 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3498 update-initramfs -u -k all
3499 &lt;/pre&gt;
3500
3501 &lt;p&gt;Since March 2012 there is
3502 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3503 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3504 hardware have this problem, and get the driver to invert the
3505 brightness setting automatically. To use it, one need to add a row in
3506 &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
3507 intel_quirks array&lt;/a&gt; in the driver source
3508 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3509 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3510 number (vendor number 8086 is assumed) and subdevice vendor and device
3511 number.&lt;/p&gt;
3512
3513 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3514 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3515
3516 &lt;p&gt;&lt;pre&gt;
3517 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3518 3rd Gen Core processor Graphics Controller [8086:0156] \
3519 (rev 09) (prog-if 00 [VGA controller])
3520 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3521 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3522 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3523 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3524 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3525 Latency: 0
3526 Interrupt: pin A routed to IRQ 42
3527 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3528 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3529 Region 4: I/O ports at 4000 [size=64]
3530 Expansion ROM at &lt;unassigned&gt; [disabled]
3531 Capabilities: &lt;access denied&gt;
3532 Kernel driver in use: i915
3533 &lt;/pre&gt;&lt;/p&gt;
3534
3535 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3536
3537 &lt;p&gt;&lt;pre&gt;
3538 struct intel_quirk intel_quirks[] = {
3539 ...
3540 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3541 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3542 ...
3543 }
3544 &lt;/pre&gt;&lt;/p&gt;
3545
3546 &lt;p&gt;According to the kernel module instructions (as seen using
3547 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3548 invert_brightness flag should be sent to the
3549 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3550 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3551 developers. But my email about the laptop sent 2013-06-03 have not
3552 yet shown up in
3553 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3554 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3555 emails from non-subscribers. Because of this, I sent my patch also to
3556 the Debian bug tracking system instead as
3557 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3558 sure the patch is not lost.&lt;/p&gt;
3559
3560 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3561 with this problem working properly with Linux. If you use Gnome, your
3562 worries should be over at this point. But if you use KDE, there is
3563 something in KDE ignoring the invert_brightness setting and turning on
3564 the screen during login. I&#39;ve reported it to Debian as
3565 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3566 have no idea yet how to figure out exactly what subsystem is doing
3567 this. Perhaps you can help? Perhaps you know what the Gnome
3568 developers did to handle this, and this can give a clue to the KDE
3569 developers? Or you know where in KDE the screen brightness is changed
3570 during login? If so, please update the BTS report (or get in touch if
3571 you do not know how to update BTS).&lt;/p&gt;
3572
3573 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3574 acpi_backlight=vendor, to disable ACPI backlight support completely,
3575 as the ACPI information on the machine is trash and it is better to
3576 leave it to the intel video driver to control the screen
3577 backlight.&lt;/p&gt;
3578 </description>
3579 </item>
3580
3581 <item>
3582 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3583 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3584 <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>
3585 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3586 <description>&lt;p&gt;Two days ago, I asked
3587 &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
3588 I could install Linux on a Packard Bell EasyNote LV computer
3589 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3590 with the obstacles put in the way of Linux users on a laptop with UEFI
3591 and Windows 8.&lt;/p&gt;
3592
3593 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3594 secure booting or fast boot. I suspect fast boot was the problem,
3595 causing the firmware to boot directly from HD without considering any
3596 key presses and alternative devices, but do not know UEFI settings
3597 enough to tell.&lt;/p&gt;
3598
3599 &lt;p&gt;There is no way to install Linux on the machine in question without
3600 opening the box and disconnecting the hard drive! This is as far as I
3601 can tell, the only way to get access to the firmware setup menu
3602 without accepting the Windows 8 license agreement. I am told (and
3603 found description on how to) that it is possible to configure the
3604 firmware setup once booted into Windows 8. But as I believe the terms
3605 of that agreement are completely unacceptable, accepting the license
3606 was never an alternative. I do not enter agreements I do not intend
3607 to follow.&lt;/p&gt;
3608
3609 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3610 waste many hours on this, but luckily there was a way to get it to
3611 work. But I would not recommend it to anyone planning to run Linux on
3612 it, and I have become sceptical to Windows 8 certified laptops. Is
3613 this the way Linux will be forced out of the market place, by making
3614 it close to impossible for &quot;normal&quot; users to install Linux without
3615 accepting the Microsoft Windows license terms? Or at least not
3616 without risking to loose the warranty?&lt;/p&gt;
3617
3618 &lt;p&gt;I&#39;ve updated the
3619 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3620 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3621 do not have to struggle as much as I did to get Linux into the
3622 machine.&lt;/p&gt;
3623
3624 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3625 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3626 </description>
3627 </item>
3628
3629 <item>
3630 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3631 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3632 <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>
3633 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3634 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3635 new laptops for my parents and a few others. I bought Packard Bell
3636 Easynote LV to run Kubuntu on and use as their home computer. But I
3637 am completely unable to figure out how to install Linux on it. The
3638 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3639 instead of a BIOS to boot.&lt;/p&gt;
3640
3641 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3642 to get it to boot the Linux installer from my USB stick. I have yet
3643 to try the DVD install, and still hope it will work. when I turn on
3644 the computer, there is no information on what buttons to press to get
3645 the normal boot menu. I expect to get some boot menu to select PXE or
3646 USB stick booting. When booting, it first ask for the language to
3647 use, then for some regional settings, and finally if I will accept the
3648 Windows 8 terms of use. As these terms are completely unacceptable to
3649 me, I have no other choice but to turn off the computer and try again
3650 to get it to boot the Linux installer.&lt;/p&gt;
3651
3652 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3653 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3654 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3655 installed on this machine, please get in touch or update that wiki
3656 page. If I can&#39;t find a way to install Linux, I will have to return
3657 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3658
3659 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3660 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3661 on new Laptops?&lt;/p&gt;
3662 </description>
3663 </item>
3664
3665 <item>
3666 <title>How to transform a Debian based system to a Debian Edu installation</title>
3667 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3668 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3669 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3670 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3671 an operating system based on Debian intended for use in schools. It
3672 contain a turn-key solution for the computer network provided to
3673 pupils in the primary schools. It provide both the central server,
3674 network boot servers and desktop environments with heaps of
3675 educational software. The project was founded almost 12 years ago,
3676 2001-07-02. If you want to support the project, which is in need for
3677 cash to fund developer gatherings and other project related activity,
3678 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3679 donate some money&lt;/a&gt;.
3680
3681 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3682 lists and elsewhere, is the question on how to transform a Debian or
3683 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3684 hard, and last week I wrote a script to replicate the steps done by
3685 the Debian Edu installer.&lt;/p&gt;
3686
3687 &lt;p&gt;The script,
3688 &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;
3689 in the debian-edu-config package, will go through these six steps and
3690 transform an existing Debian Wheezy or Ubuntu (untested) installation
3691 into a Debian Edu Workstation:&lt;/p&gt;
3692
3693 &lt;ol&gt;
3694
3695 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3696 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3697 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3698 our configuration.&lt;/li&gt;
3699 &lt;li&gt;Preseed debconf database with profile setup in
3700 /etc/debian-edu/config, and run tasksel to install packages
3701 according to the profile specified in the config above,
3702 overriding some of the Debian automation machinery.&lt;/li&gt;
3703 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3704 that could not be done using preseeding.&lt;/li&gt;
3705 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3706
3707 &lt;/ol&gt;
3708
3709 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3710 replicated like this. Disk partitioning and LVM setup, for example.
3711 So this script just assume there is enough disk space to install all
3712 the needed packages.&lt;/p&gt;
3713
3714 &lt;p&gt;The script was created to help a Debian Edu student working on
3715 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3716 Debian Edu client, and using it he can take the existing
3717 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3718 transform it into a fully functioning Debian Edu Workstation (or
3719 Roaming Workstation, or whatever :).&lt;/p&gt;
3720
3721 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3722 If a LXDE based Roaming workstation is wanted instead, modify the
3723 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3724
3725 &lt;p&gt;&lt;pre&gt;
3726 PROFILE=&quot;Roaming-Workstation&quot;
3727 DESKTOP=&quot;lxde&quot;
3728 &lt;/pre&gt;&lt;/p&gt;
3729
3730 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3731 the cloud, by starting with a virtual Debian installation at some
3732 virtual hosting service and setting up all the services on first
3733 boot.&lt;/p&gt;
3734 </description>
3735 </item>
3736
3737 <item>
3738 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3739 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3740 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3741 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3742 <description>&lt;P&gt;In January,
3743 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3744 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3745 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3746 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3747 marvellous construction system from Denmark. We also created
3748 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3749 a place to take notes and write down our plans and hopes. And several
3750 people showed up to help. I was very happy to see the effect of my
3751 call. Since the small start, we have a debtags tag
3752 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3753 tag for LEGO related packages, and now count 10 packages related to
3754 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3755
3756 &lt;p&gt;&lt;table&gt;
3757 &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;
3758 &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;
3759 &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;
3760 &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;
3761 &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;
3762 &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;
3763 &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;
3764 &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;
3765 &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;
3766 &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;
3767 &lt;/table&gt;&lt;/p&gt;
3768
3769 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3770 currently available in Jessie/testing. leocad is so far only
3771 available in experimental.&lt;/p&gt;
3772
3773 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3774 adding the rest of the great free software tools available on Linux
3775 for LEGO designers.&lt;/p&gt;
3776 </description>
3777 </item>
3778
3779 <item>
3780 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3781 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3782 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3783 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3784 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3785 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3786 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3787 Debian release, and I expect to move my machines at home over to it fairly
3788 soon.&lt;/p&gt;
3789
3790 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3791 in particular make me very happy to see included. The
3792 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3793 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3794 included for the first time. Alongside similar programs like
3795 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3796 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3797 it allow for visual programming where syntax errors can not happen,
3798 and a friendly programming environment for learning to control the
3799 computer. Scratch will also be included in the next release of Debian
3800 Edu.&lt;/a&gt;
3801
3802 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3803 Edu/Skolelinux release too. The
3804 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3805 alpha release&lt;/a&gt; went out last week, and the next should soon
3806 follow.&lt;p&gt;
3807 </description>
3808 </item>
3809
3810 <item>
3811 <title>Isenkram 0.2 finally in the Debian archive</title>
3812 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3813 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3814 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3815 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3816 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3817 for many months. I uploaded it to the Debian experimental suite
3818 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3819
3820 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3821 install to work with a pluggable hardware device. The suggestion pop
3822 up when the device is plugged in. For example if a Lego Mindstorm NXT
3823 is inserted, it will suggest to install the program needed to program
3824 the NXT controller. Give it a go, and report bugs and suggestions to
3825 BTS. :)&lt;/p&gt;
3826 </description>
3827 </item>
3828
3829 <item>
3830 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3831 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3833 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3834 <description>&lt;p&gt;My
3835 &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
3836 bitcoin related blog post&lt;/a&gt; mentioned that the new
3837 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3838 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3839 2013-01-19, and have been available in unstable since then. It was
3840 automatically copied to Ubuntu, and is available in their Raring
3841 version too.&lt;/p&gt;
3842
3843 &lt;p&gt;But there is a strange problem with the build that block this new
3844 version from being available on the i386 and kfreebsd-i386
3845 architectures. For some strange reason, the autobuilders in Debian
3846 for these architectures fail to run the test suite on these
3847 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3848 We are so far unable to reproduce it when building it manually, and
3849 no-one have been able to propose a fix. If you got an idea what is
3850 failing, please let us know via the BTS.&lt;/p&gt;
3851
3852 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3853 I often run low on disk space, is the fact that the client will exit
3854 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3855 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3856 it. :)&lt;/p&gt;
3857
3858 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3859 activities, please send Bitcoin donations to my address
3860 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3861 </description>
3862 </item>
3863
3864 <item>
3865 <title>Welcome to the world, Isenkram!</title>
3866 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3867 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3868 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3869 <description>&lt;p&gt;Yesterday, I
3870 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3871 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3872 pluggable hardware devices, which I
3873 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3874 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3875 up, and caused me to really want to to open up the development to more
3876 people. But before I did this, I want to come up with a sensible name
3877 for this project. Today I finally decided on a new name, and I have
3878 renamed the project from hw-support-handler to this new name. In the
3879 process, I moved the source to git and made it available as a
3880 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3881 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3882 To fetch and build the latest version of the source, use&lt;/p&gt;
3883
3884 &lt;pre&gt;
3885 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3886 cd isenkram &amp;&amp; git-buildpackage -us -uc
3887 &lt;/pre&gt;
3888
3889 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3890 want to hack on the source or improve the package, please go ahead.
3891 But please talk to me first on IRC or via email before you do major
3892 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3893
3894 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3895 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3896 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3897 the German word eisenkram, for those that are familiar with that
3898 word.&lt;/p&gt;
3899
3900 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3901 instructions, to avoid confusing people with an error from the signing
3902 process.&lt;/p&gt;
3903
3904 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3905 clone argument to avoid the need for authentication.&lt;/p&gt;
3906 </description>
3907 </item>
3908
3909 <item>
3910 <title>First prototype ready making hardware easier to use in Debian</title>
3911 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3912 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3913 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3914 <description>&lt;p&gt;Early this month I set out to try to
3915 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3916 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3917 prototype is working, and it is ready for a larger audience. To test
3918 it, fetch the
3919 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3920 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3921 package. You might have to log out and in again activate the
3922 autostart script.&lt;/p&gt;
3923
3924 &lt;p&gt;The design is simple:&lt;/p&gt;
3925
3926 &lt;ul&gt;
3927
3928 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3929 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3930
3931 &lt;li&gt;This program listen for kernel events about new hardware (directly
3932 from the kernel like udev does), not using HAL dbus events as I
3933 initially did.&lt;/li&gt;
3934
3935 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3936 the APT database, a database
3937 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3938 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3939
3940 &lt;li&gt;If a package is mapped to the hardware in question, the package
3941 isn&#39;t installed yet and this is the first time the hardware was
3942 plugged in, show a desktop notification suggesting to install the
3943 package or packages.&lt;/li&gt;
3944
3945 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3946 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3947
3948 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3949 package while showing progress information in a window.&lt;/li&gt;
3950
3951 &lt;/ul&gt;
3952
3953 &lt;p&gt;I still need to come up with a better name for the system. Here
3954 are some screen shots showing the prototype in action. First the
3955 notification, then the password request, and finally the request to
3956 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3957
3958 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3959 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3960 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3961 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3962 &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;
3963
3964 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3965 is already useful. The database of hardware to package mappings also
3966 need more work. It is currently compatible with the Ubuntu way of
3967 storing such information in the package control file, but could be
3968 changed to use other formats instead or in addition to the current
3969 method. I&#39;ve dropped the use of discover for this mapping, as the
3970 modalias approach is more flexible and easier to use on Linux as long
3971 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3972
3973 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3974 here is the command required to check out and build the source: Use
3975 &#39;&lt;tt&gt;svn checkout
3976 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3977 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3978 devscripts package.&lt;/p&gt;
3979
3980 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3981 renamed to Isenkram and the source moved from the Debian Edu
3982 subversion repository to a Debian collab-maint git repository. See
3983 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3984 instructions&lt;/a&gt; for details.&lt;/p&gt;
3985 </description>
3986 </item>
3987
3988 <item>
3989 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3990 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3991 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3992 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3993 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3994 suddenly in bed. With a quiet whimper, it went completely quiet and
3995 black. The power button was no longer able to turn it on. It was a
3996 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3997 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3998 Compaq I had before that. Now I need to find a replacement. To keep
3999 going during Christmas, I moved the one year old SSD disk to my old
4000 X40 where it fitted (only one I had left that could use it), but it is
4001 not a durable solution.
4002
4003 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
4004 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
4005
4006 &lt;ul&gt;
4007
4008 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
4009 than A4).&lt;/li&gt;
4010 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
4011 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
4012 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
4013 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
4014 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
4015 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
4016 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
4017 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
4018 size).&lt;/li&gt;
4019 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
4020 X.org packages.&lt;/li&gt;
4021 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
4022 the time).
4023
4024 &lt;/ul&gt;
4025
4026 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
4027 list. The reason is simply that the specifications on laptops the
4028 last 10-15 years have been sufficient for my needs, and I have to look
4029 at other features to choose my laptop. But are there still made as
4030 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4031 robust, and Thinkpads seem to be heading in the wrong direction since
4032 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
4033 still be useful.&lt;/p&gt;
4034
4035 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
4036 external keyboard? I&#39;ll have to check the
4037 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
4038 well-supported laptops, or perhaps just buy one preinstalled from one
4039 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
4040 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
4041 </description>
4042 </item>
4043
4044 <item>
4045 <title>How to find a browser plugin supporting a given MIME type</title>
4046 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
4047 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
4048 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
4049 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
4050 install to get support for a given MIME type. Thanks to
4051 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
4052 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
4053 Unfortunately, not very many packages provide the needed meta
4054 information, Anyway, here is a small script to look up all browser
4055 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
4056
4057 &lt;pre&gt;
4058 #!/usr/bin/python
4059 import sys
4060 import apt
4061 def pkgs_handling_mimetype(mimetype):
4062 cache = apt.Cache()
4063 cache.open(None)
4064 thepkgs = []
4065 for pkg in cache:
4066 version = pkg.candidate
4067 if version is None:
4068 version = pkg.installed
4069 if version is None:
4070 continue
4071 record = version.record
4072 if not record.has_key(&#39;Npp-MimeType&#39;):
4073 continue
4074 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
4075 for t in mime_types:
4076 t = t.rstrip().strip()
4077 if t == mimetype:
4078 thepkgs.append(pkg.name)
4079 return thepkgs
4080 mimetype = &quot;audio/ogg&quot;
4081 if 1 &lt; len(sys.argv):
4082 mimetype = sys.argv[1]
4083 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
4084 for pkg in pkgs_handling_mimetype(mimetype):
4085 print &quot; %s&quot; %pkg
4086 &lt;/pre&gt;
4087
4088 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
4089
4090 &lt;pre&gt;
4091 % ./apt-find-browserplug-for-mimetype
4092 Browser plugin packages supporting audio/ogg:
4093 gecko-mediaplayer
4094 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4095 Browser plugin packages supporting application/x-shockwave-flash:
4096 browser-plugin-gnash
4097 %
4098 &lt;/pre&gt;
4099
4100 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4101 itself to query for plugins and propose to install the needed
4102 packages. It would be great if Debian supported such feature too. Is
4103 anyone working on adding it?&lt;/p&gt;
4104
4105 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4106 request for icweasel support for this feature is
4107 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4108 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4109 of manpower and wish for a different design is the reason thus feature
4110 is not yet in iceweasel from Debian.&lt;/p&gt;
4111 </description>
4112 </item>
4113
4114 <item>
4115 <title>What is the most supported MIME type in Debian?</title>
4116 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4118 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4119 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4120 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4121 proposal to make it possible for a Desktop application to propose to
4122 the user some package to install to gain support for a given MIME
4123 type, font, library etc. that is currently missing. With such
4124 mechanism in place, it would be possible for the desktop to
4125 automatically propose and install leocad if some LDraw file is
4126 downloaded by the browser.&lt;/p&gt;
4127
4128 &lt;p&gt;To get some idea about the current content of the archive, I decided
4129 to write a simple program to extract all .desktop files from the
4130 Debian archive and look up the claimed MIME support there. The result
4131 can be found on the
4132 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4133 site&lt;/a&gt;. Using the collected information, it become possible to
4134 answer the question in the title. Here are the 20 most supported MIME
4135 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4136 The complete list is available from the link above.&lt;/p&gt;
4137
4138 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4139
4140 &lt;pre&gt;
4141 count MIME type
4142 ----- -----------------------
4143 32 text/plain
4144 30 audio/mpeg
4145 29 image/png
4146 28 image/jpeg
4147 27 application/ogg
4148 26 audio/x-mp3
4149 25 image/tiff
4150 25 image/gif
4151 22 image/bmp
4152 22 audio/x-wav
4153 20 audio/x-flac
4154 19 audio/x-mpegurl
4155 18 video/x-ms-asf
4156 18 audio/x-musepack
4157 18 audio/x-mpeg
4158 18 application/x-ogg
4159 17 video/mpeg
4160 17 audio/x-scpls
4161 17 audio/ogg
4162 16 video/x-ms-wmv
4163 &lt;/pre&gt;
4164
4165 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4166
4167 &lt;pre&gt;
4168 count MIME type
4169 ----- -----------------------
4170 33 text/plain
4171 32 image/png
4172 32 image/jpeg
4173 29 audio/mpeg
4174 27 image/gif
4175 26 image/tiff
4176 26 application/ogg
4177 25 audio/x-mp3
4178 22 image/bmp
4179 21 audio/x-wav
4180 19 audio/x-mpegurl
4181 19 audio/x-mpeg
4182 18 video/mpeg
4183 18 audio/x-scpls
4184 18 audio/x-flac
4185 18 application/x-ogg
4186 17 video/x-ms-asf
4187 17 text/html
4188 17 audio/x-musepack
4189 16 image/x-xbitmap
4190 &lt;/pre&gt;
4191
4192 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4193
4194 &lt;pre&gt;
4195 count MIME type
4196 ----- -----------------------
4197 31 text/plain
4198 31 image/png
4199 31 image/jpeg
4200 29 audio/mpeg
4201 28 application/ogg
4202 27 image/gif
4203 26 image/tiff
4204 26 audio/x-mp3
4205 23 audio/x-wav
4206 22 image/bmp
4207 21 audio/x-flac
4208 20 audio/x-mpegurl
4209 19 audio/x-mpeg
4210 18 video/x-ms-asf
4211 18 video/mpeg
4212 18 audio/x-scpls
4213 18 application/x-ogg
4214 17 audio/x-musepack
4215 16 video/x-ms-wmv
4216 16 video/x-msvideo
4217 &lt;/pre&gt;
4218
4219 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4220 information mentioned in DEP-11. I have not yet had time to look at
4221 it, but hope the PackageKit people in Debian are on top of these
4222 issues.&lt;/p&gt;
4223
4224 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4225 discovering a typo in my script.&lt;/p&gt;
4226 </description>
4227 </item>
4228
4229 <item>
4230 <title>Using modalias info to find packages handling my hardware</title>
4231 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4232 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4233 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4234 <description>&lt;p&gt;Yesterday, I wrote about the
4235 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4236 values provided by the Linux kernel&lt;/a&gt; following my hope for
4237 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4238 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4239 modalias values attached to package names can be used to map packages
4240 to hardware. This allow the system to look up and suggest relevant
4241 packages when I plug in some new hardware into my machine, and replace
4242 discover and discover-data as the database used to map hardware to
4243 packages.&lt;/p&gt;
4244
4245 &lt;p&gt;I create a modaliases file with entries like the following,
4246 containing package name, kernel module name (if relevant, otherwise
4247 the package name) and globs matching the relevant hardware
4248 modalias.&lt;/p&gt;
4249
4250 &lt;p&gt;&lt;blockquote&gt;
4251 Package: package-name
4252 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4253 &lt;/blockquote&gt;&lt;/p&gt;
4254
4255 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4256 for a given modalias value using this file.&lt;/p&gt;
4257
4258 &lt;p&gt;An entry like this would suggest the video and picture application
4259 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4260
4261 &lt;p&gt;&lt;blockquote&gt;
4262 Package: cheese
4263 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4264 &lt;/blockquote&gt;&lt;/p&gt;
4265
4266 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4267 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4268
4269 &lt;p&gt;&lt;blockquote&gt;
4270 Package: pcmciautils
4271 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4272 &lt;/blockquote&gt;&lt;/p&gt;
4273
4274 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4275 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4276
4277 &lt;p&gt;&lt;blockquote&gt;
4278 Package: colorhug-client
4279 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4280 &lt;/blockquote&gt;&lt;/p&gt;
4281
4282 &lt;p&gt;I believe the format is compatible with the format of the Packages
4283 file in the Debian archive. Ubuntu already uses their Packages file
4284 to store their mappings from packages to hardware.&lt;/p&gt;
4285
4286 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4287 announce the hardware it support in a way my prototype understand.
4288 This allow those publishing packages in an APT source outside the
4289 Debian archive as well as those backporting packages to make sure the
4290 hardware mapping are included in the package meta information. I&#39;ve
4291 tested such header in the pymissile package, and its modalias mapping
4292 is working as it should with my prototype. It even made it to Ubuntu
4293 Raring.&lt;/p&gt;
4294
4295 &lt;p&gt;To test if it was possible to look up supported hardware using only
4296 the shell tools available in the Debian installer, I wrote a shell
4297 implementation of the lookup code. The idea is to create files for
4298 each modalias and let the shell do the matching. Please check out and
4299 try the
4300 &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;
4301 shell script. It run without any extra dependencies and fetch the
4302 hardware mappings from the Debian archive and the subversion
4303 repository where I currently work on my prototype.&lt;/p&gt;
4304
4305 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4306 install yubikey-personalization:&lt;/p&gt;
4307
4308 &lt;p&gt;&lt;blockquote&gt;
4309 % ./hw-support-lookup
4310 &lt;br&gt;yubikey-personalization
4311 &lt;br&gt;%
4312 &lt;/blockquote&gt;&lt;/p&gt;
4313
4314 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4315 propose to install the pcmciautils package:&lt;/p&gt;
4316
4317 &lt;p&gt;&lt;blockquote&gt;
4318 % ./hw-support-lookup
4319 &lt;br&gt;pcmciautils
4320 &lt;br&gt;%
4321 &lt;/blockquote&gt;&lt;/p&gt;
4322
4323 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4324 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4325 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4326
4327 &lt;p&gt;It could be possible to generate several of the mappings between
4328 packages and hardware. One source would be to look at packages with
4329 kernel modules, ie packages with *.ko files in /lib/modules/, and
4330 extract their modalias information. Another would be to look at
4331 packages with udev rules, ie packages with files in
4332 /lib/udev/rules.d/, and extract their vendor/model information to
4333 generate a modalias matching rule. I have not tested any of these to
4334 see if it work.&lt;/p&gt;
4335
4336 &lt;p&gt;If you want to help implementing a system to let us propose what
4337 packages to install when new hardware is plugged into a Debian
4338 machine, please send me an email or talk to me on
4339 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4340 </description>
4341 </item>
4342
4343 <item>
4344 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4345 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4346 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4347 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4348 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4349 information, to find the packages that support a given piece of
4350 hardware, I refreshed my memory regarding modalias values, and decided
4351 to document the details. Here are my findings so far, also available
4352 in
4353 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4354 Debian Edu subversion repository&lt;/a&gt;:
4355
4356 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4357
4358 &lt;p&gt;This document try to explain what the different types of modalias
4359 values stands for. It is in part based on information from
4360 &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;,
4361 &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;,
4362 &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
4363 &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;.
4364
4365 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4366 this shell script:&lt;/p&gt;
4367
4368 &lt;pre&gt;
4369 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4370 &lt;/pre&gt;
4371
4372 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4373 using modinfo:&lt;/p&gt;
4374
4375 &lt;pre&gt;
4376 % /sbin/modinfo psmouse | grep alias:
4377 alias: serio:ty05pr*id*ex*
4378 alias: serio:ty01pr*id*ex*
4379 %
4380 &lt;/pre&gt;
4381
4382 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4383
4384 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4385 Bridge memory controller:&lt;/p&gt;
4386
4387 &lt;p&gt;&lt;blockquote&gt;
4388 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4389 &lt;/blockquote&gt;&lt;/p&gt;
4390
4391 &lt;p&gt;This represent these values:&lt;/p&gt;
4392
4393 &lt;pre&gt;
4394 v 00008086 (vendor)
4395 d 00002770 (device)
4396 sv 00001028 (subvendor)
4397 sd 000001AD (subdevice)
4398 bc 06 (bus class)
4399 sc 00 (bus subclass)
4400 i 00 (interface)
4401 &lt;/pre&gt;
4402
4403 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4404 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4405 0600. The 0600 class is a host bridge. Other useful bus values are
4406 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4407
4408 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4409 means.&lt;/p&gt;
4410
4411 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4412
4413 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4414 USB hub in a laptop:&lt;/p&gt;
4415
4416 &lt;p&gt;&lt;blockquote&gt;
4417 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4418 &lt;/blockquote&gt;&lt;/p&gt;
4419
4420 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4421
4422 &lt;pre&gt;
4423 v 1D6B (device vendor)
4424 p 0001 (device product)
4425 d 0206 (bcddevice)
4426 dc 09 (device class)
4427 dsc 00 (device subclass)
4428 dp 00 (device protocol)
4429 ic 09 (interface class)
4430 isc 00 (interface subclass)
4431 ip 00 (interface protocol)
4432 &lt;/pre&gt;
4433
4434 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4435 class is in the interface class section. For a simple USB web camera,
4436 these alias entries show up:&lt;/p&gt;
4437
4438 &lt;p&gt;&lt;blockquote&gt;
4439 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4440 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4441 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4442 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4443 &lt;/blockquote&gt;&lt;/p&gt;
4444
4445 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4446 camera), 0101 is audio control device and 0102 is audio streaming (aka
4447 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4448
4449 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4450
4451 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4452 receiver in a Thinkpad X40:&lt;/p&gt;
4453
4454 &lt;p&gt;&lt;blockquote&gt;
4455 acpi:IBM0071:PNP0511:
4456 &lt;/blockquote&gt;&lt;/p&gt;
4457
4458 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4459
4460 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4461
4462 &lt;p&gt;The DMI table contain lots of information about the computer case
4463 and model. This is an entry for a IBM Thinkpad X40, fetched from
4464 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4465
4466 &lt;p&gt;&lt;blockquote&gt;
4467 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4468 &lt;/blockquote&gt;&lt;/p&gt;
4469
4470 &lt;p&gt;The values present are&lt;/p&gt;
4471
4472 &lt;pre&gt;
4473 bvn IBM (BIOS vendor)
4474 bvr 1UETB6WW(1.66) (BIOS version)
4475 bd 06/15/2005 (BIOS date)
4476 svn IBM (system vendor)
4477 pn 2371H4G (product name)
4478 pvr ThinkPadX40 (product version)
4479 rvn IBM (board vendor)
4480 rn 2371H4G (board name)
4481 rvr NotAvailable (board version)
4482 cvn IBM (chassis vendor)
4483 ct 10 (chassis type)
4484 cvr NotAvailable (chassis version)
4485 &lt;/pre&gt;
4486
4487 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4488 found in the dmidecode source:&lt;/p&gt;
4489
4490 &lt;pre&gt;
4491 3 Desktop
4492 4 Low Profile Desktop
4493 5 Pizza Box
4494 6 Mini Tower
4495 7 Tower
4496 8 Portable
4497 9 Laptop
4498 10 Notebook
4499 11 Hand Held
4500 12 Docking Station
4501 13 All In One
4502 14 Sub Notebook
4503 15 Space-saving
4504 16 Lunch Box
4505 17 Main Server Chassis
4506 18 Expansion Chassis
4507 19 Sub Chassis
4508 20 Bus Expansion Chassis
4509 21 Peripheral Chassis
4510 22 RAID Chassis
4511 23 Rack Mount Chassis
4512 24 Sealed-case PC
4513 25 Multi-system
4514 26 CompactPCI
4515 27 AdvancedTCA
4516 28 Blade
4517 29 Blade Enclosing
4518 &lt;/pre&gt;
4519
4520 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4521 table. For example my home server is a tower, but the DMI modalias
4522 claim it is a desktop.&lt;/p&gt;
4523
4524 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4525
4526 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4527 test machine:&lt;/p&gt;
4528
4529 &lt;p&gt;&lt;blockquote&gt;
4530 serio:ty01pr00id00ex00
4531 &lt;/blockquote&gt;&lt;/p&gt;
4532
4533 &lt;p&gt;The values present are&lt;/p&gt;
4534
4535 &lt;pre&gt;
4536 ty 01 (type)
4537 pr 00 (prototype)
4538 id 00 (id)
4539 ex 00 (extra)
4540 &lt;/pre&gt;
4541
4542 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4543 the valid values are.&lt;/p&gt;
4544
4545 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4546
4547 &lt;p&gt;There are heaps of other modalias subtypes according to
4548 file2alias.c. There is the rest of the list from that source: amba,
4549 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4550 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4551 vmbus, x86cpu and zorro. I did not spend time documenting all of
4552 these, as they do not seem relevant for my intended use with mapping
4553 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4554
4555 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4556
4557 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4558 one can use the following shell script:&lt;/p&gt;
4559
4560 &lt;pre&gt;
4561 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4562 echo &quot;$id&quot; ; \
4563 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4564 done
4565 &lt;/pre&gt;
4566
4567 &lt;p&gt;The output can look like this (only the first few entries as the
4568 list is very long on my test machine):&lt;/p&gt;
4569
4570 &lt;pre&gt;
4571 acpi:ACPI0003:
4572 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4573 acpi:device:
4574 FATAL: Module acpi:device: not found.
4575 acpi:IBM0068:
4576 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4577 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4578 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4579 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4580 acpi:IBM0071:PNP0511:
4581 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4582 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4583 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4584 [...]
4585 &lt;/pre&gt;
4586
4587 &lt;p&gt;If you want to help implementing a system to let us propose what
4588 packages to install when new hardware is plugged into a Debian
4589 machine, please send me an email or talk to me on
4590 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4591
4592 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4593 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4594 in /sys/ with space in them.&lt;/p&gt;
4595 </description>
4596 </item>
4597
4598 <item>
4599 <title>Moved the pymissile Debian packaging to collab-maint</title>
4600 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4601 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4602 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4603 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4604 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4605 Launcher and updated the Debian package
4606 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4607 sure udev will fix the device permissions when it is plugged in. I
4608 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4609 hopefully make the package be proposed by jockey in Ubuntu when a user
4610 plug in his rocket launcher. In the process I moved the source to a
4611 git repository under collab-maint, to make it easier for any DD to
4612 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4613 is not very active, but the software still work for me even after five
4614 years of relative silence. The new git repository is not listed in
4615 the uploaded package yet, because I want to test the other changes a
4616 bit more before I upload the new version. If you want to check out
4617 the new version with a .desktop file included, visit the
4618 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4619 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4620 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4621 </description>
4622 </item>
4623
4624 <item>
4625 <title>Lets make hardware dongles easier to use in Debian</title>
4626 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4627 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4628 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4629 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4630 general, is that there is a great package management system with the
4631 ability to automatically install software packages by downloading them
4632 from the distribution mirrors, but no way to get it to automatically
4633 install the packages I need to use the hardware I plug into my
4634 machine. Even if the package to use it is easily available from the
4635 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4636 suggest to automatically install the python-nxt, nbc and t2n packages
4637 I need to talk to it. When I plug in a Yubikey, it could propose the
4638 yubikey-personalization package. The information required to do this
4639 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4640
4641 &lt;p&gt;Some years ago, I proposed to
4642 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4643 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4644 simple:
4645
4646 &lt;ul&gt;
4647
4648 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4649 starting when a user log in.&lt;/li&gt;
4650
4651 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4652 hardware is inserted into the computer.&lt;/li&gt;
4653
4654 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4655 database mapping to packages, and take note of any non-installed
4656 packages.&lt;/li&gt;
4657
4658 &lt;li&gt;Show a message to the user proposing to install the discovered
4659 package, and make it easy to install it.&lt;/li&gt;
4660
4661 &lt;/ul&gt;
4662
4663 &lt;p&gt;I am not sure what the best way to implement this is, but my
4664 initial idea was to use dbus events to discover new hardware, the
4665 discover database to find packages and
4666 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4667 packages.&lt;/p&gt;
4668
4669 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4670 draft package is now checked into
4671 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4672 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4673 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4674 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4675 the relevant packages in Debian, and uploaded a new version
4676 2.2013.01.09 to unstable. I also discovered that the current
4677 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4678 package in Debian no longer discovered any USB devices, because
4679 /proc/bus/usb/devices is no longer present. I ported it to use
4680 libusb as a fall back option to get it working. The fixed package
4681 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4682 because of the freeze).&lt;/p&gt;
4683
4684 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4685 desktop notification to show up (only once, the first time it is
4686 inserted):&lt;/p&gt;
4687
4688 &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;
4689
4690 &lt;p&gt;For this prototype to be really useful, some way to automatically
4691 install the proposed packages by pressing the &quot;Please install
4692 program(s)&quot; button should to be implemented.&lt;/p&gt;
4693
4694 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4695 happen, please help me update the discover-data database with mappings
4696 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4697 list the package you would like to have installed when a given
4698 hardware device is inserted into your computer, and report bugs using
4699 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4700 such mapping, please let me know.&lt;/p&gt;
4701
4702 &lt;p&gt;This prototype need more work, and there are several questions that
4703 should be considered before it is ready for production use. Is dbus
4704 the correct way to detect new hardware? At the moment I look for HAL
4705 dbus events on the system bus, because that is the events I could see
4706 on my Debian Squeeze KDE desktop. Are there better events to use?
4707 How should the user be notified? Is the desktop notification
4708 mechanism the best option, or should the background daemon raise a
4709 popup instead? How should packages be installed? When should they
4710 not be installed?&lt;/p&gt;
4711
4712 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4713 please send me an email. :)&lt;/p&gt;
4714 </description>
4715 </item>
4716
4717 <item>
4718 <title>New IRC channel for LEGO designers using Debian</title>
4719 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4720 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4721 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4722 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4723 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4724 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4725 discovered I had to build all the tools myself because none were
4726 already in Debian Squeeze. If Debian support for LEGO is something
4727 you care about, please join me on the IRC channel
4728 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4729 irc.debian.org). There is a lot that could be done to improve the
4730 Debian support for LEGO designers. For example both CAD software
4731 and Mindstorm compilers are missing. :)&lt;/p&gt;
4732
4733 &lt;p&gt;Update 2012-01-03: A
4734 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4735 including links to Lego related packages is now available.&lt;/p&gt;
4736 </description>
4737 </item>
4738
4739 <item>
4740 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4741 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4742 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4743 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4744 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4745 year! I hope next year will prove to be a good year.&lt;/p&gt;
4746
4747 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4748 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4749 between each other with minimal overhead, is a very interesting
4750 experiment. And as I wrote a few days ago, the bitcoin situation in
4751 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4752 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4753 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4754 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4755 for one of the ftpmasters to approve the new bitcoin-qt package
4756 name.&lt;/p&gt;
4757
4758 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4759 team in Debian, you can easily test the package in Debian Squeeze
4760 using the following steps to get a set of working packages:&lt;/p&gt;
4761
4762 &lt;blockquote&gt;&lt;pre&gt;
4763 git clone git://git.debian.org/git/collab-maint/bitcoin
4764 cd bitcoin
4765 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4766 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4767 &lt;/pre&gt;&lt;/blockquote&gt;
4768
4769 &lt;p&gt;You might have to install some build dependencies as well. The
4770 list of commands should give you two packages, bitcoind and
4771 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4772 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4773 around 5.6 GiB of data on my machine at the moment. Make sure your
4774 ~/.bitcoin/ directory have lots of spare room if you want to download
4775 all the blocks. The client will warn if the disk is getting full, so
4776 there is not really a problem if you got too little room, but you will
4777 not be able to get all the features out of the client.&lt;/p&gt;
4778
4779 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4780 activities, please send Bitcoin donations to my address
4781 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4782 </description>
4783 </item>
4784
4785 <item>
4786 <title>A word on bitcoin support in Debian</title>
4787 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4789 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4790 <description>&lt;p&gt;It has been a while since I wrote about
4791 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4792 peer-to-peer based crypto-currency, and the reason is simply that I
4793 have been busy elsewhere. But two days ago, I started looking at the
4794 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4795 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4796 is now maintained by a
4797 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4798 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4799 owe a huge thank you to all these team members. :)
4800 But I was sad to discover that the bitcoin client is missing in
4801 Wheezy. It is only available in Sid (and an outdated client from
4802 backports). The client had several RC bugs registered in BTS blocking
4803 it from entering testing. To try to help the team and improve the
4804 situation, I spent some time providing patches and triaging the bug
4805 reports. I also had a look at the bitcoin package available from Matt
4806 Corallo in a
4807 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4808 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4809 Debian package.&lt;/p&gt;
4810
4811 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4812 IRC, I pushed several patches into the collab-maint git repository to
4813 improve the package. It now contains fixes for the RC issues (not from
4814 me, but fixed by Scott Howard), build rules for a Qt GUI client
4815 package, konqueror support for the bitcoin: URI and bash completion
4816 setup. As I work on Debian Squeeze, I also created
4817 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4818 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4819 it and try to integrate it into the git repository before uploading a
4820 new version to unstable.
4821
4822 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4823 centralized control currently exercised in the monetary system. I
4824 find it completely unacceptable that the USA government is collecting
4825 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4826 that the major credit card companies can block legal money
4827 transactions to Wikileaks. But for bitcoin to succeed, more people
4828 need to use bitcoins, and more people need to accept bitcoins when
4829 they sell products and services. Improving the bitcoin support in
4830 Debian is a small step in the right direction, but not enough.
4831 Unfortunately the user experience when browsing the web and wanting to
4832 pay with bitcoin is still not very good. The bitcoin: URI is a step
4833 in the right direction, but need to work in most or every browser in
4834 use. Also the bitcoin-qt client is too heavy to fire up to do a
4835 quick transaction. I believe there are other clients available, but
4836 have not tested them.&lt;/p&gt;
4837
4838 &lt;p&gt;My
4839 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4840 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4841 I received 20.15 BTC so far on the address I provided in my blog two
4842 years ago, as can be
4843 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4844 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4845 donation. The blockexplorer service demonstrates quite well that
4846 bitcoin is not quite anonymous and untracked. :) I wonder if the
4847 number of users have gone up since then. If you use bitcoin and want
4848 to show your support of my activity, please send Bitcoin donations to
4849 the same address as last time,
4850 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4851 </description>
4852 </item>
4853
4854 <item>
4855 <title>Git repository for song book for Computer Scientists</title>
4856 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4857 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4858 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4859 <description>&lt;p&gt;As I
4860 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4861 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4862 years ago, and today I finally found time to create a public
4863 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4864 repository for the project&lt;/a&gt;.&lt;/p&gt;
4865
4866 &lt;p&gt;If you want to help out, please clone the source and submit patches
4867 to the HTML version. To generate the PDF and PostScript version,
4868 please use prince XML, or let me know about a useful free software
4869 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4870
4871 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4872 PostScript formats at
4873 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4874 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4875 </description>
4876 </item>
4877
4878 <item>
4879 <title>Gratulerer med 19-årsdagen, Debian!</title>
4880 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4882 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4883 <description>&lt;p&gt;I dag fyller
4884 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4885 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4886 si gratulerer med dagen, Debian!&lt;/p&gt;
4887 </description>
4888 </item>
4889
4890 <item>
4891 <title>Song book for Computer Scientists</title>
4892 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4893 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4894 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4895 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4896 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4897 collecting computer related songs for use at parties. The original
4898 version was written in LaTeX, but a few years ago I got help from
4899 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4900 while keeping the ability to create a nice book in PDF format. I have
4901 not had time to maintain the book for a while now, and guess I should
4902 put it up on some public version control repository where others can
4903 help me extend and update the book. If anyone is volunteering to help
4904 me with this, send me an email. Also let me know if there are songs
4905 missing in my book.&lt;/p&gt;
4906
4907 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4908 me today that I really should let all my readers share the joys of
4909 singing out load about programming, computers and computer networks.
4910 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4911 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4912 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4913 Computer Science Songbook&lt;/a&gt;.
4914 </description>
4915 </item>
4916
4917 <item>
4918 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4919 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4920 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4921 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4922 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4923 around 1000 at the moment. To be able to get help from the vendors
4924 when something go wrong, we want to keep the firmware on the servers
4925 up to date. If the firmware isn&#39;t the latest and greatest, the
4926 vendors typically refuse to start debugging any problems until the
4927 firmware is upgraded. So before every reboot, we want to upgrade the
4928 firmware, and we would really like everyone handling servers at the
4929 university to do this themselves when they plan to reboot a machine.
4930 For that to happen we at the unix server admin group need to provide
4931 the tools to do so.&lt;/p&gt;
4932
4933 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4934 fetch and install the latest firmware for the servers we got. Most of
4935 our hardware are from Dell and HP, so I have focused on these servers
4936 so far. This blog post is about the Dell part.&lt;/P&gt;
4937
4938 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4939 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4940 with firmware information for all 11th generation servers, listing
4941 which firmware should be used on a given model and where on the FTP
4942 site I can find it. Using a simple perl XML parser I can then
4943 download the shell scripts Dell provides to do firmware upgrades from
4944 within Linux and reboot when all the firmware is primed and ready to
4945 be activated on the first reboot.&lt;/p&gt;
4946
4947 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4948 Are there anyone working on similar tools for firmware upgrading all
4949 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4950
4951 &lt;p&gt;&lt;pre&gt;
4952 #!/usr/bin/perl
4953 use strict;
4954 use warnings;
4955 use File::Temp qw(tempdir);
4956 BEGIN {
4957 # Install needed RHEL packages if missing
4958 my %rhelmodules = (
4959 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4960 );
4961 for my $module (keys %rhelmodules) {
4962 eval &quot;use $module;&quot;;
4963 if ($@) {
4964 my $pkg = $rhelmodules{$module};
4965 system(&quot;yum install -y $pkg&quot;);
4966 eval &quot;use $module;&quot;;
4967 }
4968 }
4969 }
4970 my $errorsto = &#39;pere@hungry.com&#39;;
4971
4972 upgrade_dell();
4973
4974 exit 0;
4975
4976 sub run_firmware_script {
4977 my ($opts, $script) = @_;
4978 unless ($script) {
4979 print STDERR &quot;fail: missing script name\n&quot;;
4980 exit 1
4981 }
4982 print STDERR &quot;Running $script\n\n&quot;;
4983
4984 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4985 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4986 } else {
4987 print STDERR &quot;fail: firmware script returned error\n&quot;;
4988 }
4989 }
4990
4991 sub run_firmware_scripts {
4992 my ($opts, @dirs) = @_;
4993 # Run firmware packages
4994 for my $dir (@dirs) {
4995 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4996 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4997 while (my $s = readdir $dh) {
4998 next if $s =~ m/^\.\.?/;
4999 run_firmware_script($opts, &quot;$dir/$s&quot;);
5000 }
5001 closedir $dh;
5002 }
5003 }
5004
5005 sub download {
5006 my $url = shift;
5007 print STDERR &quot;info: Downloading $url\n&quot;;
5008 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
5009 }
5010
5011 sub upgrade_dell {
5012 my @dirs;
5013 my $product = `dmidecode -s system-product-name`;
5014 chomp $product;
5015
5016 if ($product =~ m/PowerEdge/) {
5017
5018 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5019 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
5020
5021 my $tmpdir = tempdir(
5022 CLEANUP =&gt; 1
5023 );
5024 chdir($tmpdir);
5025 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
5026 system(&#39;gunzip Catalog.xml.gz&#39;);
5027 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
5028 # -q is quiet, disabling interactivity and reducing console output
5029 my $fwopts = &quot;-q&quot;;
5030 if (@paths) {
5031 for my $url (@paths) {
5032 fetch_dell_fw($url);
5033 }
5034 run_firmware_scripts($fwopts, $tmpdir);
5035 } else {
5036 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5037 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5038 }
5039 chdir(&#39;/&#39;);
5040 } else {
5041 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5042 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5043 }
5044 }
5045
5046 sub fetch_dell_fw {
5047 my $path = shift;
5048 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
5049 download($url);
5050 }
5051
5052 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5053 # firmware packages to download from Dell. Only work for Linux
5054 # machines and 11th generation Dell servers.
5055 sub fetch_dell_fw_list {
5056 my $filename = shift;
5057
5058 my $product = `dmidecode -s system-product-name`;
5059 chomp $product;
5060 my ($mybrand, $mymodel) = split(/\s+/, $product);
5061
5062 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
5063
5064 my $xml = XMLin($filename);
5065 my @paths;
5066 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
5067 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
5068 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
5069 my $oscode;
5070 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
5071 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
5072 } else {
5073 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
5074 }
5075 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
5076 {
5077 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
5078 }
5079 }
5080 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
5081 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
5082
5083 # Drop application packages, only firmware and BIOS
5084 next if &#39;APAC&#39; eq $componenttype;
5085
5086 my $cpath = $component-&gt;{path};
5087 for my $path (@paths) {
5088 if ($cpath =~ m%/$path$%) {
5089 push(@paths, $cpath);
5090 }
5091 }
5092 }
5093 return @paths;
5094 }
5095 &lt;/pre&gt;
5096
5097 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5098 it could work on other platforms with some tweaking. Anyone know a
5099 index like Catalog.xml is available from HP for HP servers? At the
5100 moment I maintain a similar list manually and it is quickly getting
5101 outdated.&lt;/p&gt;
5102 </description>
5103 </item>
5104
5105 <item>
5106 <title>How is booting into runlevel 1 different from single user boots?</title>
5107 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5109 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5110 <description>&lt;p&gt;Wouter Verhelst have some
5111 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5112 comments and opinions&lt;/a&gt; on my blog post on
5113 &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
5114 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5115 &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
5116 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5117 small piece of his comment now, and though it best to address the
5118 misunderstanding he bring forward:&lt;/p&gt;
5119
5120 &lt;p&gt;&lt;blockquote&gt;
5121 Currently, a system admin has four options: [...] boot to a
5122 single-user system (by adding &#39;single&#39; to the kernel command line;
5123 this runs rcS and rc1 scripts)
5124 &lt;/blockquote&gt;&lt;/p&gt;
5125
5126 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5127 and booting into runlevel 1 is the same. I am not surprised he
5128 believe this, because it would make sense and is a quite sensible
5129 thing to believe. But because the boot in Debian is slightly broken,
5130 runlevel 1 do not work properly and it isn&#39;t the same as single user
5131 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5132 hard to explain.&lt;/p&gt;
5133
5134 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5135 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5136 executed in single user mode is sulogin. Single user mode is a boot
5137 state &quot;between&quot; the runlevels, and when booting into single user mode,
5138 only the scripts in /etc/rcS.d/ are executed before the init process
5139 enters the single user state. When switching to runlevel 1, the state
5140 is in fact not ending in runlevel 1, but it passes through runlevel 1
5141 and end up in the single user mode (see /etc/rc1.d/S03single, which
5142 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5143 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5144 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5145 mode).&lt;/p&gt;
5146
5147 &lt;p&gt;This summary might make it clearer. When booting for the first
5148 time into single user mode, the following commands are executed:
5149 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5150 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5151 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5152 trying to continue after visiting single user mode. Not all services
5153 are started again as they should, causing the machine to end up in an
5154 unpredicatble state. This is why Debian admins recommend rebooting
5155 after visiting single user mode.&lt;/p&gt;
5156
5157 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5158 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5159 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5160 stopped when passing through the scripts in /etc/rc1.d/, and not
5161 started again when switching away from runlevel 1 to the runlevels
5162 2-5. I believe the problem is best fixed by moving all the scripts
5163 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5164 functioning single user mode during boot.&lt;/p&gt;
5165
5166 &lt;p&gt;I have spent several years investigating the Debian boot system,
5167 and discovered this problem a few years ago. I suspect it originates
5168 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5169 </description>
5170 </item>
5171
5172 <item>
5173 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5174 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5175 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5176 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5177 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5178 are started from /etc/rcS.d/. In fact, there is a bite more of them
5179 than make sense, and this causes a few problems. What kind of
5180 problems, you might ask. There are at least two problems. The first
5181 is that it is not possible to recover a machine after switching to
5182 runlevel 1. One need to actually reboot to get the machine back to
5183 the expected state. The other is that single user boot will sometimes
5184 run into problems because some of the subsystems are activated before
5185 the root login is presented, causing problems when trying to recover a
5186 machine from a problem in that subsystem. A minor additional point is
5187 that moving more scripts out of rcS.d/ and into the other rc#.d/
5188 directories will increase the amount of scripts that can run in
5189 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5190
5191 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5192 scripts that _have_ to execute before the root login prompt is
5193 presented during a single user boot should go there. Everything else
5194 should go into the numeric runlevels. This means things like
5195 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5196 the numeric runlevels. Today in Debian, there are around 115 init.d
5197 scripts that are started from rcS.d/, and most of them should be moved
5198 out. Do your package have one of them? Please help us make single
5199 user and runlevel 1 better by moving it.&lt;/p&gt;
5200
5201 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5202 etc. should still be started from rcS.d/, but there is for example no
5203 need to have the network enabled before the single user login prompt
5204 is presented.&lt;/p&gt;
5205
5206 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5207 Debian systems working while scripts migrate and during upgrades, the
5208 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5209 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5210 and the next ones can only be moved when their dependencies have been
5211 moved first. This migration must be done sequentially while we ensure
5212 that the package system upgrade packages in the right order to keep
5213 the system state correct. This will require some coordination when it
5214 comes to network related packages, but most of the packages with
5215 scripts that should migrate do not have anything in rcS.d/ depending
5216 on them. Some packages have already been updated, like the sudo
5217 package, while others are still left to do. I wish I had time to work
5218 on this myself, but real live constrains make it unlikely that I will
5219 find time to push this forward.&lt;/p&gt;
5220 </description>
5221 </item>
5222
5223 <item>
5224 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5225 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5226 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5227 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5228 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5229 mentioned the issues I believe should be improved in Debian for its
5230 desktop to be useful for more people. The use case for this is my
5231 parents, which are currently running Kubuntu which solve the
5232 issues.&lt;/p&gt;
5233
5234 &lt;p&gt;I suspect these four missing features are not very hard to
5235 implement. After all, they are present in Ubuntu, so if we wanted to
5236 do this in Debian we would have a source.&lt;/p&gt;
5237
5238 &lt;ol&gt;
5239
5240 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5241 are new packages available for upgrades, a icon in the KDE status bar
5242 indicate this, and clicking on it will activate the simple upgrade
5243 tool to handle it. I have no problem guiding both of my parents
5244 through the process over the phone. If a kernel reboot is required,
5245 this too is indicated by the status bars and the upgrade tool. Last
5246 time I checked, nothing with the same features was working in KDE in
5247 Debian.&lt;/li&gt;
5248
5249 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5250 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5251 currently have a handler for, it will ask the user if the system
5252 should search for a package that would add support for this MIME type,
5253 and if the user say yes, the APT sources will be searched for packages
5254 advertising the MIME type in their control file (visible in the
5255 Packages file in the APT archive). If one or more packages are found,
5256 it is a simple click of the mouse to add support for the missing mime
5257 type. If the package require the user to accept some non-free
5258 license, this is explained to the user. The entire process make it
5259 more clear to the user why something do not work in the browser, and
5260 make the chances higher for the user to blame the web page authors and
5261 not the browser for any missing features.&lt;/li&gt;
5262
5263 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5264 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5265 it is not supporting, a dialog pop up asking the user if the system
5266 should search for a package that would add support for it. This
5267 happen with things like MP3, Windows Media or H.264. The selection
5268 and installation procedure is very similar to the Firefox browser
5269 plugin handling. This is as far as I know implemented using a
5270 gstreamer hook. The end result is that the user easily get access to
5271 the codecs that are present from the APT archives available, while
5272 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5273
5274 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5275 displaying a text/plain file in my Debian browser, it will propose to
5276 start emacs to show it. If I remember correctly, when doing the same
5277 in Kunbutu it show the file as a text file in the browser. At least I
5278 know Opera will show text files within the browser. I much prefer the
5279 latter behaviour.&lt;/li&gt;
5280
5281 &lt;/ol&gt;
5282
5283 &lt;p&gt;There are other nice features as well, like the simplified suite
5284 upgrader, but given that I am the one mostly doing the dist-upgrade,
5285 it do not matter much.&lt;/p&gt;
5286
5287 &lt;p&gt;I really hope we could get these features in place for the next
5288 Debian release. It would require the coordinated effort of several
5289 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5290 </description>
5291 </item>
5292
5293 <item>
5294 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5295 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5297 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5298 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5299 site is build on Debian/Squeeze, and this platform was chosen because
5300 I am most familiar with Debian (being a Debian Developer for around 10
5301 years) because it is the latest stable Debian release which should get
5302 security support for a few years.&lt;/p&gt;
5303
5304 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5305 that are missing in Debian at the moment. It would be great if these
5306 modules were added to the Debian archive, allowing anyone to set up
5307 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5308 in their own country using only Debian packages. The list of modules
5309 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5310 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5311 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5312 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5313 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5314 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5315 easier in the future.&lt;/p&gt;
5316
5317 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5318 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5319 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5320 with the responsibility of tracking security problems, which I really
5321 do not have time for.&lt;/p&gt;
5322 </description>
5323 </item>
5324
5325 <item>
5326 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5327 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5328 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5329 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5330 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5331 posts have been in Norwegian the last few weeks, so here is a short
5332 update in English.&lt;/p&gt;
5333
5334 &lt;p&gt;The kids still keep me too busy to get much free software work
5335 done, but I did manage to organise a project to get a Norwegian port
5336 of the British service
5337 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5338 and it has been running for a month now. The entire project has been
5339 organised by me and two others. Around Christmas we gathered sponsors
5340 to fund the development work. In January I drafted a contract with
5341 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5342 and in February the development took place. Most of it involved
5343 converting the source to use GPS coordinates instead of British
5344 easting/northing, and the resulting code should be a lot easier to get
5345 running in any country by now. The Norwegian
5346 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5347 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5348 source and the source for administrative borders in Norway, and
5349 support for this had to be added/fixed.&lt;/p&gt;
5350
5351 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5352 polishing the system before we announced it March 7th. The system is
5353 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5354 problem reports in a few weeks. Soon we hope to announce the Android
5355 and iPhone versions making it even easier to report problems with the
5356 public infrastructure.&lt;/p&gt;
5357
5358 &lt;p&gt;Perhaps something to consider for those of you in countries without
5359 such service?&lt;/p&gt;
5360 </description>
5361 </item>
5362
5363 <item>
5364 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5365 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5366 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5367 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5368 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5369 issues here at my work with the University of Oslo. My idea is that
5370 it should be possible to use the information about security issues
5371 available on the Internet, and check our locally
5372 maintained/distributed software against this information. It should
5373 allow us to verify that no known security issues are forgotten. The
5374 CVE database listing vulnerabilities seem like a great central point,
5375 and by using the package lists from Debian mapped to CVEs provided by
5376 the testing security team, I believed it should be possible to figure
5377 out which security holes were present in our free software
5378 collection.&lt;/p&gt;
5379
5380 &lt;p&gt;After reading up on the topic, it became obvious that the first
5381 building block is to be able to name software packages in a unique and
5382 consistent way across data sources. I considered several ways to do
5383 this, for example coming up with my own naming scheme like using URLs
5384 to project home pages or URLs to the Freshmeat entries, or using some
5385 existing naming scheme. And it seem like I am not the first one to
5386 come across this problem, as MITRE already proposed and implemented a
5387 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5388 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5389 software, hardware and other platform components. The CPE ids are
5390 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5391 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5392 issues for any CPE name. With this in place, all I need to do is to
5393 locate the CPE id for the software packages we use at the university.
5394 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5395 NVD entry if a CVE for the package exist).&lt;/p&gt;
5396
5397 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5398 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5399 check out, one could look up
5400 &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
5401 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5402 The most recent one is
5403 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5404 and at the bottom of the NVD page for this vulnerability the complete
5405 list of affected versions is provided.&lt;/p&gt;
5406
5407 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5408 for offline processing of issues. Using this dump, I&#39;ve written a
5409 small script taking a list of CPEs as input and list all CVEs
5410 affecting the packages represented by these CPEs. One give it CPEs
5411 with version numbers as specified above and get a list of open
5412 security issues out.&lt;/p&gt;
5413
5414 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5415 information need to be high. For that to happen, I believe as many as
5416 possible need to use and contribute to the NVD database. I notice
5417 RHEL is providing
5418 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5419 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5420 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5421
5422 &lt;p&gt;To get an idea about the quality for free software, I spent some
5423 time making it possible to compare the CVE database from Debian with
5424 the CVE database in NVD. The result look fairly good, but there are
5425 some inconsistencies in NVD (same software package having several
5426 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5427 Debian believe are affected by a CVE). Hope to find time to improve
5428 the quality of NVD, but that require being able to get in touch with
5429 someone maintaining it. So far my three emails with questions and
5430 corrections have not seen any reply, but I hope contact can be
5431 established soon.&lt;/p&gt;
5432
5433 &lt;p&gt;An interesting application for CPEs is cross platform package
5434 mapping. It would be useful to know which packages in for example
5435 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5436 this would be trivial if all linux distributions provided CPE entries
5437 for their packages.&lt;/p&gt;
5438 </description>
5439 </item>
5440
5441 <item>
5442 <title>Which module is loaded for a given PCI and USB device?</title>
5443 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5444 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5445 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5446 <description>&lt;p&gt;In the
5447 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5448 package in Debian, there is a script to report useful information
5449 about the running hardware for use when people report missing
5450 information. One part of this script that I find very useful when
5451 debugging hardware problems, is the part mapping loaded kernel module
5452 to the PCI device it claims. It allow me to quickly see if the kernel
5453 module I expect is driving the hardware I am struggling with. To see
5454 the output, make sure discover-data is installed and run
5455 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5456 one of my machines like this:&lt;/p&gt;
5457
5458 &lt;pre&gt;
5459 loaded modules:
5460 10de:03eb i2c_nforce2
5461 10de:03f1 ohci_hcd
5462 10de:03f2 ehci_hcd
5463 10de:03f0 snd_hda_intel
5464 10de:03ec pata_amd
5465 10de:03f6 sata_nv
5466 1022:1103 k8temp
5467 109e:036e bttv
5468 109e:0878 snd_bt87x
5469 11ab:4364 sky2
5470 &lt;/pre&gt;
5471
5472 &lt;p&gt;The code in question look like this, slightly modified for
5473 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5474
5475 &lt;pre&gt;
5476 if [ -d /sys/bus/pci/devices/ ] ; then
5477 echo loaded pci modules:
5478 (
5479 cd /sys/bus/pci/devices/
5480 for address in * ; do
5481 if [ -d &quot;$address/driver/module&quot; ] ; then
5482 module=`cd $address/driver/module ; pwd -P | xargs basename`
5483 if grep -q &quot;^$module &quot; /proc/modules ; then
5484 address=$(echo $address |sed s/0000://)
5485 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5486 echo &quot;$id $module&quot;
5487 fi
5488 fi
5489 done
5490 )
5491 echo
5492 fi
5493 &lt;/pre&gt;
5494
5495 &lt;p&gt;Similar code could be used to extract USB device module
5496 mappings:&lt;/p&gt;
5497
5498 &lt;pre&gt;
5499 if [ -d /sys/bus/usb/devices/ ] ; then
5500 echo loaded usb modules:
5501 (
5502 cd /sys/bus/usb/devices/
5503 for address in * ; do
5504 if [ -d &quot;$address/driver/module&quot; ] ; then
5505 module=`cd $address/driver/module ; pwd -P | xargs basename`
5506 if grep -q &quot;^$module &quot; /proc/modules ; then
5507 address=$(echo $address |sed s/0000://)
5508 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5509 if [ &quot;$id&quot; ] ; then
5510 echo &quot;$id $module&quot;
5511 fi
5512 fi
5513 fi
5514 done
5515 )
5516 echo
5517 fi
5518 &lt;/pre&gt;
5519
5520 &lt;p&gt;This might perhaps be something to include in other tools as
5521 well.&lt;/p&gt;
5522 </description>
5523 </item>
5524
5525 <item>
5526 <title>How to test if a laptop is working with Linux</title>
5527 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5528 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5529 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5530 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5531 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5532 batch of computers will work with Linux. Every year for the last few
5533 years the university have organised shared bid of a few thousand
5534 computers, and this year HP won the bid. Two different desktops and
5535 five different laptops are on the list this year. We in the UNIX
5536 group want to know which one of these computers work well with RHEL
5537 and Ubuntu, the two Linux distributions we currently handle at the
5538 university.&lt;/p&gt;
5539
5540 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5541 perhaps inspire others to test hardware as well. To test, I PXE
5542 install the OS version of choice, and log in as my normal user and run
5543 a few applications and plug in selected pieces of hardware. When
5544 something fail, I make a note about this in the test matrix and move
5545 on. If I have some spare time I try to report the bug to the OS
5546 vendor, but as I only have the machines for a short time, I rarely
5547 have the time to do this for all the problems I find.&lt;/p&gt;
5548
5549 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5550 I perform on a new model.&lt;/p&gt;
5551
5552 &lt;ul&gt;
5553
5554 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5555 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5556 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5557
5558 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5559 installation, X.org is working.&lt;/li&gt;
5560
5561 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5562 package mesa-utils on Ubuntu) and writing down the frames per second
5563 reported by the program.&lt;/li&gt;
5564
5565 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5566 logging in, and if I can hear this the test is successful. If there
5567 are several audio exits on the machine, I try them all and check if
5568 the Gnome/KDE audio mixer can control where to send the sound. I
5569 normally test this by playing
5570 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5571 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5572
5573 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5574 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5575
5576 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5577 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5578
5579 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5580 picture from the v4l device show up.&lt;/li&gt;
5581
5582 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5583 any bluetooth devices are discovered. In my office, I normally see a
5584 few.&lt;/li&gt;
5585
5586 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5587 memory modules lying around, and stick them in and see if Gnome/KDE
5588 notice this.&lt;/li&gt;
5589
5590 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5591 special button work, and if the laptop continue to work after
5592 resume.&lt;/li&gt;
5593
5594 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5595 adjusting background light, switching on/off external video output,
5596 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5597 laptop to laptop, so I just write down which are working and which are
5598 not.&lt;/li&gt;
5599
5600 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5601 acceleration sensors etc. I rarely test these, as I do not know how
5602 to quickly test if they are working or not, so I only document their
5603 existence.&lt;/li&gt;
5604
5605 &lt;/ul&gt;
5606
5607 &lt;p&gt;By now I suspect you are really curious what the test results are
5608 for the HP machines I am testing. I&#39;m not done yet, so I will report
5609 the test results later. For now I can report that HP 8100 Elite work
5610 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5611 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5612 can see, I have most machines left to test. One interesting
5613 observation is that Ubuntu Lucid has almost twice the frame rate than
5614 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5615 </description>
5616 </item>
5617
5618 <item>
5619 <title>Some thoughts on BitCoins</title>
5620 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5621 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5622 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5623 <description>&lt;p&gt;As I continue to explore
5624 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5625 what properties the system have, and how it will be affected by laws
5626 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5627
5628 &lt;p&gt;One interesting thing to note is that since the transactions are
5629 verified using a peer to peer network, all details about a transaction
5630 is known to everyone. This means that if a BitCoin address has been
5631 published like I did with mine in my initial post about BitCoin, it is
5632 possible for everyone to see how many BitCoins have been transfered to
5633 that address. There is even a web service to look at the details for
5634 all transactions. There I can see that my address
5635 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5636 have received 16.06 Bitcoin, the
5637 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5638 address of Simon Phipps have received 181.97 BitCoin and the address
5639 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5640 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5641 every one of you that donated bitcoins to support my activity. The
5642 fact that anyone can see how much money was transfered to a given
5643 address make it more obvious why the BitCoin community recommend to
5644 generate and hand out a new address for each transaction. I&#39;m told
5645 there is no way to track which addresses belong to a given person or
5646 organisation without the person or organisation revealing it
5647 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5648
5649 &lt;p&gt;In Norway, and in most other countries, there are laws and
5650 regulations limiting how much money one can transfer across the border
5651 without declaring it. There are money laundering, tax and accounting
5652 laws and regulations I would expect to apply to the use of BitCoin.
5653 If the Skolelinux foundation
5654 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5655 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5656 normal bank transfers like EFF is doing, how should this be accounted?
5657 Given that it is impossible to know if money can cross the border or
5658 not, should everything or nothing be declared? What exchange rate
5659 should be used when calculating taxes? Would receivers have to pay
5660 income tax if the foundation were to pay Skolelinux contributors in
5661 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5662
5663 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5664 accepted by a lot of users. It must be possible to get easy access to
5665 the currency (as a wage or using currency exchanges), and it must be
5666 easy to spend it. At the moment BitCoin seem fairly easy to get
5667 access to, but there are very few places to spend it. I am not really
5668 a regular user of any of the vendor types currently accepting BitCoin,
5669 so I wonder when my kind of shop would start accepting BitCoins. I
5670 would like to buy electronics, travels and subway tickets, not herbs
5671 and books. :) The currency is young, and this will improve over time
5672 if it become popular, but I suspect regular banks will start to lobby
5673 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5674 will claim it is helping fund terrorism and money laundering (which
5675 probably would be true, as is any currency in existence), but I
5676 believe the problems should be solved elsewhere and not by blaming
5677 currencies.&lt;/p&gt;
5678
5679 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5680 CPU intensive process that depend on a bit of luck as well (as one is
5681 competing against all the other miners currently spending CPU cycles
5682 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5683 BitCoin when this happen. Yesterday I came across the obvious way to
5684 join forces to increase ones changes of getting at least some coins,
5685 by coordinating the work on mining BitCoins across several machines
5686 and people, and sharing the result if one is lucky and get the 50
5687 BitCoins. Check out
5688 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5689 if this sounds interesting. I have not had time to try to set up a
5690 machine to participate there yet, but have seen that running on ones
5691 own for a few days have not yield any BitCoins througth mining
5692 yet.&lt;/p&gt;
5693
5694 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5695 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5696 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5697 it was interesting to read. The arguments presented seem to be
5698 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5699 </description>
5700 </item>
5701
5702 <item>
5703 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5704 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5705 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5706 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5707 <description>&lt;p&gt;With this weeks lawless
5708 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5709 attacks&lt;/a&gt; on Wikileak and
5710 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5711 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5712 not be trusted to handle money transactions.
5713 A blog post from
5714 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5715 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5716 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5717 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5718 some help from my friend to get it all running, and he even handed me
5719 some bitcoins to get started. I even donated a few bitcoins to Simon
5720 for helping me remember BitCoin.&lt;/p&gt;
5721
5722 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5723 crypto-currency, decentralised and handled using peer-to-peer
5724 networks. It allows anonymous transactions and prohibits central
5725 control over the transactions, making it impossible for governments
5726 and companies alike to block donations and other transactions. The
5727 source is free software, and while the key dependency wxWidgets 2.9
5728 for the graphical user interface is missing in Debian, the command
5729 line client builds just fine. Hopefully Jonas
5730 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5731 Debian&lt;/a&gt; soon.&lt;/p&gt;
5732
5733 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5734 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5735 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5736 currency &quot;stock&quot; markets where the exchange rate is decided. There
5737 are not many users so far, but the concept seems promising. If you
5738 want to get started and lack a friend with any bitcoins to spare,
5739 you can even get
5740 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5741 bitcoin at the time of writing). Use
5742 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5743 on the current exchange rates.&lt;/p&gt;
5744
5745 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5746 machines. If you want to support my activity, please send Bitcoin
5747 donations to the address
5748 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5749 </description>
5750 </item>
5751
5752 <item>
5753 <title>Why isn&#39;t Debian Edu using VLC?</title>
5754 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5755 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5756 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5757 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5758 presented, and the winner among the multimedia player were VLC.
5759 Personally, I like VLC, and it is my player of choice when I first try
5760 to play a video file or stream. Only if VLC fail will I drag out
5761 gmplayer to see if it can do better. The reason is mostly the failure
5762 model and trust. When VLC fail, it normally pop up a error message
5763 reporting the problem. When mplayer fail, it normally segfault or
5764 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5765
5766 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5767 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5768 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5769 plugin to play web videos seamlessly, and the VLC browser plugin is
5770 not very good. For example, it lack in-line control buttons, so there
5771 is no way for the user to pause the video. Also, when I
5772 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5773 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5774 failed on several video pages where mplayer based plugins worked. If
5775 the browser plugin for VLC was as good as the gecko-mediaplayer
5776 package (which uses mplayer), we would switch.&lt;/P&gt;
5777
5778 &lt;p&gt;While VLC is a good player, its user interface is slightly
5779 annoying. The most annoying feature is its inconsistent use of
5780 keyboard shortcuts. When the player is in full screen mode, its
5781 shortcuts are different from when it is playing the video in a window.
5782 For example, space only work as pause when in full screen mode. I
5783 wish it had consisten shortcuts and that space also would work when in
5784 window mode. Another nice shortcut in gmplayer is [enter] to restart
5785 the current video. It is very nice when playing short videos from the
5786 web and want to restart it when new people arrive to have a look at
5787 what is going on.&lt;/p&gt;
5788 </description>
5789 </item>
5790
5791 <item>
5792 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5793 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5794 <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>
5795 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5796 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5797 upgrade testing of the
5798 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5799 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5800 This seem like a very good idea, so I adjusted by test scripts and
5801 can now present the updated result from today:&lt;/p&gt;
5802
5803 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5804
5805 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5806
5807 &lt;blockquote&gt;&lt;p&gt;
5808 apache2.2-bin
5809 aptdaemon
5810 baobab
5811 binfmt-support
5812 browser-plugin-gnash
5813 cheese-common
5814 cli-common
5815 cups-pk-helper
5816 dmz-cursor-theme
5817 empathy
5818 empathy-common
5819 freedesktop-sound-theme
5820 freeglut3
5821 gconf-defaults-service
5822 gdm-themes
5823 gedit-plugins
5824 geoclue
5825 geoclue-hostip
5826 geoclue-localnet
5827 geoclue-manual
5828 geoclue-yahoo
5829 gnash
5830 gnash-common
5831 gnome
5832 gnome-backgrounds
5833 gnome-cards-data
5834 gnome-codec-install
5835 gnome-core
5836 gnome-desktop-environment
5837 gnome-disk-utility
5838 gnome-screenshot
5839 gnome-search-tool
5840 gnome-session-canberra
5841 gnome-system-log
5842 gnome-themes-extras
5843 gnome-themes-more
5844 gnome-user-share
5845 gstreamer0.10-fluendo-mp3
5846 gstreamer0.10-tools
5847 gtk2-engines
5848 gtk2-engines-pixbuf
5849 gtk2-engines-smooth
5850 hamster-applet
5851 libapache2-mod-dnssd
5852 libapr1
5853 libaprutil1
5854 libaprutil1-dbd-sqlite3
5855 libaprutil1-ldap
5856 libart2.0-cil
5857 libboost-date-time1.42.0
5858 libboost-python1.42.0
5859 libboost-thread1.42.0
5860 libchamplain-0.4-0
5861 libchamplain-gtk-0.4-0
5862 libcheese-gtk18
5863 libclutter-gtk-0.10-0
5864 libcryptui0
5865 libdiscid0
5866 libelf1
5867 libepc-1.0-2
5868 libepc-common
5869 libepc-ui-1.0-2
5870 libfreerdp-plugins-standard
5871 libfreerdp0
5872 libgconf2.0-cil
5873 libgdata-common
5874 libgdata7
5875 libgdu-gtk0
5876 libgee2
5877 libgeoclue0
5878 libgexiv2-0
5879 libgif4
5880 libglade2.0-cil
5881 libglib2.0-cil
5882 libgmime2.4-cil
5883 libgnome-vfs2.0-cil
5884 libgnome2.24-cil
5885 libgnomepanel2.24-cil
5886 libgpod-common
5887 libgpod4
5888 libgtk2.0-cil
5889 libgtkglext1
5890 libgtksourceview2.0-common
5891 libmono-addins-gui0.2-cil
5892 libmono-addins0.2-cil
5893 libmono-cairo2.0-cil
5894 libmono-corlib2.0-cil
5895 libmono-i18n-west2.0-cil
5896 libmono-posix2.0-cil
5897 libmono-security2.0-cil
5898 libmono-sharpzip2.84-cil
5899 libmono-system2.0-cil
5900 libmtp8
5901 libmusicbrainz3-6
5902 libndesk-dbus-glib1.0-cil
5903 libndesk-dbus1.0-cil
5904 libopal3.6.8
5905 libpolkit-gtk-1-0
5906 libpt2.6.7
5907 libpython2.6
5908 librpm1
5909 librpmio1
5910 libsdl1.2debian
5911 libsrtp0
5912 libssh-4
5913 libtelepathy-farsight0
5914 libtelepathy-glib0
5915 libtidy-0.99-0
5916 media-player-info
5917 mesa-utils
5918 mono-2.0-gac
5919 mono-gac
5920 mono-runtime
5921 nautilus-sendto
5922 nautilus-sendto-empathy
5923 p7zip-full
5924 pkg-config
5925 python-aptdaemon
5926 python-aptdaemon-gtk
5927 python-axiom
5928 python-beautifulsoup
5929 python-bugbuddy
5930 python-clientform
5931 python-coherence
5932 python-configobj
5933 python-crypto
5934 python-cupshelpers
5935 python-elementtree
5936 python-epsilon
5937 python-evolution
5938 python-feedparser
5939 python-gdata
5940 python-gdbm
5941 python-gst0.10
5942 python-gtkglext1
5943 python-gtksourceview2
5944 python-httplib2
5945 python-louie
5946 python-mako
5947 python-markupsafe
5948 python-mechanize
5949 python-nevow
5950 python-notify
5951 python-opengl
5952 python-openssl
5953 python-pam
5954 python-pkg-resources
5955 python-pyasn1
5956 python-pysqlite2
5957 python-rdflib
5958 python-serial
5959 python-tagpy
5960 python-twisted-bin
5961 python-twisted-conch
5962 python-twisted-core
5963 python-twisted-web
5964 python-utidylib
5965 python-webkit
5966 python-xdg
5967 python-zope.interface
5968 remmina
5969 remmina-plugin-data
5970 remmina-plugin-rdp
5971 remmina-plugin-vnc
5972 rhythmbox-plugin-cdrecorder
5973 rhythmbox-plugins
5974 rpm-common
5975 rpm2cpio
5976 seahorse-plugins
5977 shotwell
5978 software-center
5979 system-config-printer-udev
5980 telepathy-gabble
5981 telepathy-mission-control-5
5982 telepathy-salut
5983 tomboy
5984 totem
5985 totem-coherence
5986 totem-mozilla
5987 totem-plugins
5988 transmission-common
5989 xdg-user-dirs
5990 xdg-user-dirs-gtk
5991 xserver-xephyr
5992 &lt;/p&gt;&lt;/blockquote&gt;
5993
5994 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5995
5996 &lt;blockquote&gt;&lt;p&gt;
5997 cheese
5998 ekiga
5999 eog
6000 epiphany-extensions
6001 evolution-exchange
6002 fast-user-switch-applet
6003 file-roller
6004 gcalctool
6005 gconf-editor
6006 gdm
6007 gedit
6008 gedit-common
6009 gnome-games
6010 gnome-games-data
6011 gnome-nettool
6012 gnome-system-tools
6013 gnome-themes
6014 gnuchess
6015 gucharmap
6016 guile-1.8-libs
6017 libavahi-ui0
6018 libdmx1
6019 libgalago3
6020 libgtk-vnc-1.0-0
6021 libgtksourceview2.0-0
6022 liblircclient0
6023 libsdl1.2debian-alsa
6024 libspeexdsp1
6025 libsvga1
6026 rhythmbox
6027 seahorse
6028 sound-juicer
6029 system-config-printer
6030 totem-common
6031 transmission-gtk
6032 vinagre
6033 vino
6034 &lt;/p&gt;&lt;/blockquote&gt;
6035
6036 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6037
6038 &lt;blockquote&gt;&lt;p&gt;
6039 gstreamer0.10-gnomevfs
6040 &lt;/p&gt;&lt;/blockquote&gt;
6041
6042 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6043
6044 &lt;blockquote&gt;&lt;p&gt;
6045 [nothing]
6046 &lt;/p&gt;&lt;/blockquote&gt;
6047
6048 &lt;p&gt;This is for KDE:&lt;/p&gt;
6049
6050 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6051
6052 &lt;blockquote&gt;&lt;p&gt;
6053 ksmserver
6054 &lt;/p&gt;&lt;/blockquote&gt;
6055
6056 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6057
6058 &lt;blockquote&gt;&lt;p&gt;
6059 kwin
6060 network-manager-kde
6061 &lt;/p&gt;&lt;/blockquote&gt;
6062
6063 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6064
6065 &lt;blockquote&gt;&lt;p&gt;
6066 arts
6067 dolphin
6068 freespacenotifier
6069 google-gadgets-gst
6070 google-gadgets-xul
6071 kappfinder
6072 kcalc
6073 kcharselect
6074 kde-core
6075 kde-plasma-desktop
6076 kde-standard
6077 kde-window-manager
6078 kdeartwork
6079 kdeartwork-emoticons
6080 kdeartwork-style
6081 kdeartwork-theme-icon
6082 kdebase
6083 kdebase-apps
6084 kdebase-workspace
6085 kdebase-workspace-bin
6086 kdebase-workspace-data
6087 kdeeject
6088 kdelibs
6089 kdeplasma-addons
6090 kdeutils
6091 kdewallpapers
6092 kdf
6093 kfloppy
6094 kgpg
6095 khelpcenter4
6096 kinfocenter
6097 konq-plugins-l10n
6098 konqueror-nsplugins
6099 kscreensaver
6100 kscreensaver-xsavers
6101 ktimer
6102 kwrite
6103 libgle3
6104 libkde4-ruby1.8
6105 libkonq5
6106 libkonq5-templates
6107 libnetpbm10
6108 libplasma-ruby
6109 libplasma-ruby1.8
6110 libqt4-ruby1.8
6111 marble-data
6112 marble-plugins
6113 netpbm
6114 nuvola-icon-theme
6115 plasma-dataengines-workspace
6116 plasma-desktop
6117 plasma-desktopthemes-artwork
6118 plasma-runners-addons
6119 plasma-scriptengine-googlegadgets
6120 plasma-scriptengine-python
6121 plasma-scriptengine-qedje
6122 plasma-scriptengine-ruby
6123 plasma-scriptengine-webkit
6124 plasma-scriptengines
6125 plasma-wallpapers-addons
6126 plasma-widget-folderview
6127 plasma-widget-networkmanagement
6128 ruby
6129 sweeper
6130 update-notifier-kde
6131 xscreensaver-data-extra
6132 xscreensaver-gl
6133 xscreensaver-gl-extra
6134 xscreensaver-screensaver-bsod
6135 &lt;/p&gt;&lt;/blockquote&gt;
6136
6137 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6138
6139 &lt;blockquote&gt;&lt;p&gt;
6140 ark
6141 google-gadgets-common
6142 google-gadgets-qt
6143 htdig
6144 kate
6145 kdebase-bin
6146 kdebase-data
6147 kdepasswd
6148 kfind
6149 klipper
6150 konq-plugins
6151 konqueror
6152 ksysguard
6153 ksysguardd
6154 libarchive1
6155 libcln6
6156 libeet1
6157 libeina-svn-06
6158 libggadget-1.0-0b
6159 libggadget-qt-1.0-0b
6160 libgps19
6161 libkdecorations4
6162 libkephal4
6163 libkonq4
6164 libkonqsidebarplugin4a
6165 libkscreensaver5
6166 libksgrd4
6167 libksignalplotter4
6168 libkunitconversion4
6169 libkwineffects1a
6170 libmarblewidget4
6171 libntrack-qt4-1
6172 libntrack0
6173 libplasma-geolocation-interface4
6174 libplasmaclock4a
6175 libplasmagenericshell4
6176 libprocesscore4a
6177 libprocessui4a
6178 libqalculate5
6179 libqedje0a
6180 libqtruby4shared2
6181 libqzion0a
6182 libruby1.8
6183 libscim8c2a
6184 libsmokekdecore4-3
6185 libsmokekdeui4-3
6186 libsmokekfile3
6187 libsmokekhtml3
6188 libsmokekio3
6189 libsmokeknewstuff2-3
6190 libsmokeknewstuff3-3
6191 libsmokekparts3
6192 libsmokektexteditor3
6193 libsmokekutils3
6194 libsmokenepomuk3
6195 libsmokephonon3
6196 libsmokeplasma3
6197 libsmokeqtcore4-3
6198 libsmokeqtdbus4-3
6199 libsmokeqtgui4-3
6200 libsmokeqtnetwork4-3
6201 libsmokeqtopengl4-3
6202 libsmokeqtscript4-3
6203 libsmokeqtsql4-3
6204 libsmokeqtsvg4-3
6205 libsmokeqttest4-3
6206 libsmokeqtuitools4-3
6207 libsmokeqtwebkit4-3
6208 libsmokeqtxml4-3
6209 libsmokesolid3
6210 libsmokesoprano3
6211 libtaskmanager4a
6212 libtidy-0.99-0
6213 libweather-ion4a
6214 libxklavier16
6215 libxxf86misc1
6216 okteta
6217 oxygencursors
6218 plasma-dataengines-addons
6219 plasma-scriptengine-superkaramba
6220 plasma-widget-lancelot
6221 plasma-widgets-addons
6222 plasma-widgets-workspace
6223 polkit-kde-1
6224 ruby1.8
6225 systemsettings
6226 update-notifier-common
6227 &lt;/p&gt;&lt;/blockquote&gt;
6228
6229 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6230 aptitude a bit more similar, but there are still quite a lott of
6231 differences. I have no idea what packages should be installed after
6232 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6233 </description>
6234 </item>
6235
6236 <item>
6237 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6238 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6239 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6240 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6241 <description>&lt;p&gt;Most of the computers in use by the
6242 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6243 are virtual machines. And they have been Xen machines running on a
6244 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6245 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6246 bit harder that it could have been, because we set up the Xen virtual
6247 machines to get the virtual partitions from LVM, which as far as I
6248 know is not supported by KVM. So to migrate, we had to convert
6249 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6250
6251 &lt;p&gt;I found
6252 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6253 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6254 migration. It uses qemu-img from the qemu package to make the disk
6255 image, parted to partition it, losetup and kpartx to present the disk
6256 image partions as devices, and dd to copy the data. I NFS mounted the
6257 new servers storage area on the old server to do the migration.&lt;/p&gt;
6258
6259 &lt;pre&gt;
6260 #!/bin/sh
6261
6262 # Based on
6263 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6264
6265 set -e
6266 set -x
6267
6268 if [ -z &quot;$1&quot; ] ; then
6269 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6270 exit 1
6271 else
6272 host=&quot;$1&quot;
6273 fi
6274
6275 if [ ! -e /dev/vg_data/$host-disk ] ; then
6276 echo &quot;error: unable to find LVM volume for $host&quot;
6277 exit 1
6278 fi
6279
6280 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6281 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6282 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6283 totalsize=$(( ( $disksize + $swapsize ) ))
6284
6285 img=$host.img
6286 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6287 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6288
6289 parted $img mklabel msdos
6290 parted $img mkpart primary linux-swap 0 $disksize
6291 parted $img mkpart primary ext2 $disksize $totalsize
6292 parted $img set 1 boot on
6293
6294 modprobe dm-mod
6295 losetup /dev/loop0 $img
6296 kpartx -a /dev/loop0
6297
6298 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6299 fsck.ext3 -f /dev/mapper/loop0p1 || true
6300 mkswap /dev/mapper/loop0p2
6301
6302 kpartx -d /dev/loop0
6303 losetup -d /dev/loop0
6304 &lt;/pre&gt;
6305
6306 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6307 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6308
6309 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6310 the new disk image attached, installed grub-pc and linux-image-686 and
6311 set up grub to boot from the disk image. After this, the KVM machines
6312 seem to work just fine.&lt;/p&gt;
6313 </description>
6314 </item>
6315
6316 <item>
6317 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6318 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6319 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6320 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6321 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6322 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6323 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6324 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6325
6326 &lt;p&gt;I still do not know what a correct migration should look like, so I
6327 report any differences between apt and aptitude and hope someone else
6328 can see if anything should be changed.&lt;/p&gt;
6329
6330 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6331
6332 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6333
6334 &lt;blockquote&gt;&lt;p&gt;
6335 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6336 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6337 dmz-cursor-theme empathy empathy-common finger
6338 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6339 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6340 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6341 gnome-cards-data gnome-codec-install gnome-core
6342 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6343 gnome-search-tool gnome-session-canberra gnome-spell
6344 gnome-system-log gnome-themes-extras gnome-themes-more
6345 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6346 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6347 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6348 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6349 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6350 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6351 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6352 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6353 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6354 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6355 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6356 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6357 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6358 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6359 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6360 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6361 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6362 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6363 libmono-security2.0-cil libmono-sharpzip2.84-cil
6364 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6365 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6366 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6367 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6368 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6369 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6370 libxalan2-java libxerces2-java media-player-info mesa-utils
6371 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6372 nautilus-sendto-empathy openoffice.org-writer2latex
6373 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6374 python-aptdaemon python-aptdaemon-gtk python-axiom
6375 python-beautifulsoup python-bugbuddy python-clientform
6376 python-coherence python-configobj python-crypto python-cupshelpers
6377 python-cupsutils python-eggtrayicon python-elementtree
6378 python-epsilon python-evolution python-feedparser python-gdata
6379 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6380 python-gtksourceview2 python-httplib2 python-louie python-mako
6381 python-markupsafe python-mechanize python-nevow python-notify
6382 python-opengl python-openssl python-pam python-pkg-resources
6383 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6384 python-tagpy python-twisted-bin python-twisted-conch
6385 python-twisted-core python-twisted-web python-utidylib python-webkit
6386 python-xdg python-zope.interface remmina remmina-plugin-data
6387 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6388 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6389 software-center svgalibg1 system-config-printer-udev
6390 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6391 totem totem-coherence totem-mozilla totem-plugins
6392 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6393 zip
6394 &lt;/p&gt;&lt;/blockquote&gt;
6395
6396 Installed using apt-get, removed with aptitude
6397
6398 &lt;blockquote&gt;&lt;p&gt;
6399 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6400 epiphany-extensions epiphany-gecko evolution-exchange
6401 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6402 gedit-common gnome-app-install gnome-games gnome-games-data
6403 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6404 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6405 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6406 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6407 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6408 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6409 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6410 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6411 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6412 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6413 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6414 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6415 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6416 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6417 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6418 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6419 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6420 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6421 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6422 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6423 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6424 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6425 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6426 sound-juicer swfdec-gnome system-config-printer totem-common
6427 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6428 &lt;/p&gt;&lt;/blockquote&gt;
6429
6430 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6431
6432 &lt;blockquote&gt;&lt;p&gt;
6433 gstreamer0.10-gnomevfs
6434 &lt;/p&gt;&lt;/blockquote&gt;
6435
6436 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6437
6438 &lt;blockquote&gt;&lt;p&gt;
6439 [nothing]
6440 &lt;/p&gt;&lt;/blockquote&gt;
6441
6442 &lt;p&gt;This is for KDE:&lt;/p&gt;
6443
6444 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6445
6446 &lt;blockquote&gt;&lt;p&gt;
6447 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6448 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6449 ghostscript-x git gnome-audio gnugo granatier gs-common
6450 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6451 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6452 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6453 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6454 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6455 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6456 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6457 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6458 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6459 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6460 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6461 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6462 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6463 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6464 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6465 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6466 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6467 libkrossui4 libmailtools-perl libmime-tools-perl
6468 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6469 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6470 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6471 lirc luatex marble networkstatus noatun-plugins
6472 openoffice.org-writer2latex palapeli palapeli-data parley
6473 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6474 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6475 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6476 ttf-sazanami-gothic
6477 &lt;/p&gt;&lt;/blockquote&gt;
6478
6479 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6480
6481 &lt;blockquote&gt;&lt;p&gt;
6482 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6483 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6484 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6485 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6486 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6487 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6488 kitchensync kiten kjumpingcube klatin klettres klickety klines
6489 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6490 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6491 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6492 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6493 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6494 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6495 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6496 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6497 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6498 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6499 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6500 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6501 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6502 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6503 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6504 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6505 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6506 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6507 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6508 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6509 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6510 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6511 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6512 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6513 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6514 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6515 &lt;/p&gt;&lt;/blockquote&gt;
6516
6517 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6518
6519 &lt;blockquote&gt;&lt;p&gt;
6520 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6521 kdeartwork kdebase kdebase-apps kdebase-workspace
6522 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6523 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6524 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6525 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6526 xscreensaver-screensaver-bsod
6527 &lt;/p&gt;&lt;/blockquote&gt;
6528
6529 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6530
6531 &lt;blockquote&gt;&lt;p&gt;
6532 kdebase-bin konq-plugins konqueror
6533 &lt;/p&gt;&lt;/blockquote&gt;
6534 </description>
6535 </item>
6536
6537 <item>
6538 <title>Gnash buildbot slave and Debian kfreebsd</title>
6539 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6540 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6541 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6542 <description>&lt;p&gt;Answering
6543 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6544 call from the Gnash project&lt;/a&gt; for
6545 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6546 current source, I have set up a virtual KVM machine on the Debian
6547 Edu/Skolelinux virtualization host to test the git source on
6548 Debian/Squeeze. I hope this can help the developers in getting new
6549 releases out more often.&lt;/p&gt;
6550
6551 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6552 I have considered setting up a &lt;a
6553 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6554 machine as well. I have also considered using the kfreebsd
6555 architecture in Debian as a file server in NUUG to get access to the 5
6556 TB zfs volume we currently use to store DV video. Because of this, I
6557 finally got around to do a test installation of Debian/Squeeze with
6558 kfreebsd. Installation went fairly smooth, thought I noticed some
6559 visual glitches in the cdebconf dialogs (black cursor left on the
6560 screen at random locations). Have not gotten very far with the
6561 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6562 fatal problem. Have to spend some more time on it to see if it is
6563 useful as a file server for NUUG. Will try to find time to set up a
6564 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6565 </description>
6566 </item>
6567
6568 <item>
6569 <title>Debian in 3D</title>
6570 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6571 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6572 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6573 <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;
6574
6575 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6576 3D linked in from
6577 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6578 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6579 </description>
6580 </item>
6581
6582 <item>
6583 <title>Software updates 2010-10-24</title>
6584 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6585 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6586 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6587 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6588
6589 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6590 raise money for the project is going well. The lower limit of 10
6591 signers was reached in 24 hours, and so far 13 people have signed it.
6592 More signers and more funding is most welcome, and I am really curious
6593 how far we can get before the time limit of December 24 is reached.
6594 :)&lt;/p&gt;
6595
6596 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6597 about what appear to be a great code coverage tool capable of
6598 generating code coverage stats without any changes to the source code.
6599 It is called
6600 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6601 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6602 It is missing in Debian, but the git source built just fine in Squeeze
6603 after I installed libelf-dev, libdwarf-dev, pkg-config and
6604 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6605 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6606
6607 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6608 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6609 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6610 alpha test release of the Squeeze based Debian Edu /
6611 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6612 release. Give it a try if you need a complete linux solution for your
6613 school, including central infrastructure server, workstations, thin
6614 client servers and diskless workstations. A nice touch added
6615 yesterday is RDP support on the thin client servers, for windows
6616 clients to get a Linux desktop on request.&lt;/p&gt;
6617 </description>
6618 </item>
6619
6620 <item>
6621 <title>Some notes on Flash in Debian and Debian Edu</title>
6622 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6624 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6625 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6626 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6627 second most popular used package that is missing in Debian. The sixth
6628 most popular is flashplayer-mozilla. This is a clear indication that
6629 working flash is important for Debian users. Around 10 percent of the
6630 users submitting data to popcon.debian.org have this package
6631 installed.&lt;/p&gt;
6632
6633 &lt;p&gt;In the report written by Lars Risan in August 2008
6634&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
6635 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6636 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6637 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6638 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6639 web sites require Flash to work, and lacking working Flash support in
6640 the web browser and the problems with installing it was perceived as a
6641 good reason to stay with Windows.&lt;/p&gt;
6642
6643 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6644 said to be the retarded cousin that did not really understand
6645 everything you told him but could work fairly well. This was a
6646 comment regarding the problems Linux have with proprietary formats and
6647 non-standard web pages, and is sad because it exposes a fairly common
6648 understanding of whose fault it is if web pages that only work in for
6649 example Internet Explorer 6 fail to work on Firefox, and funny because
6650 it explain very well how annoying it is for users when Linux
6651 distributions do not work with the documents they receive or the web
6652 pages they want to visit.&lt;/p&gt;
6653
6654 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6655 and Debian Edu to have a well working Flash implementation in the
6656 distribution, to get at least popular sites as Youtube and Google
6657 Video to working out of the box. For Squeeze, Debian have the chance
6658 to include the latest version of Gnash that will make this happen, as
6659 the new release 0.8.8 was published a few weeks ago and is resting in
6660 unstable. The new version work with more sites that version 0.8.7.
6661 The Gnash maintainers have asked for a freeze exception, but the
6662 release team have not had time to reply to it yet. I hope they agree
6663 with me that Flash is important for the Debian desktop users, and thus
6664 accept the new package into Squeeze.&lt;/p&gt;
6665 </description>
6666 </item>
6667
6668 <item>
6669 <title>Circular package dependencies harms apt recovery</title>
6670 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6671 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6672 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6673 <description>&lt;p&gt;I discovered this while doing
6674 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6675 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6676 in Debian still got circular dependencies, and it is often claimed
6677 that apt and aptitude should be able to handle this just fine, but
6678 some times these dependency loops causes apt to fail.&lt;/p&gt;
6679
6680 &lt;p&gt;An example is from todays
6681 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6682 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6683 causes perl-modules to fail to upgrade. The cause is simple. If a
6684 package fail to unpack, then only part of packages with the circular
6685 dependency might end up being unpacked when unpacking aborts, and the
6686 ones already unpacked will fail to configure in the recovery phase
6687 because its dependencies are unavailable.&lt;/p&gt;
6688
6689 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6690
6691 &lt;blockquote&gt;&lt;pre&gt;
6692 dpkg: dependency problems prevent configuration of perl-modules:
6693 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6694 Version of perl on system is 5.10.0-19lenny2.
6695 dpkg: error processing perl-modules (--configure):
6696 dependency problems - leaving unconfigured
6697 &lt;/pre&gt;&lt;/blockquote&gt;
6698
6699 &lt;p&gt;The perl/perl-modules circular dependency is already
6700 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6701 hopefully be solved as soon as possible, but it is not the only one,
6702 and each one of these loops in the dependency tree can cause similar
6703 failures. Of course, they only occur when there are bugs in other
6704 packages causing the unpacking to fail, but it is rather nasty when
6705 the failure of one package causes the problem to become worse because
6706 of dependency loops.&lt;/p&gt;
6707
6708 &lt;p&gt;Thanks to
6709 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6710 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6711 dependencies
6712 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6713 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6714
6715 &lt;p&gt;Todays testing also exposed a bug in
6716 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6717 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6718 apt-get and aptitude, the latter possibly caused by some circular
6719 dependency. Reported both to BTS to try to get someone to look at
6720 it.&lt;/p&gt;
6721 </description>
6722 </item>
6723
6724 <item>
6725 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6726 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6727 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6728 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6729 <description>&lt;p&gt;This is a
6730 &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;
6731 on my
6732 &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
6733 work&lt;/a&gt; on
6734 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6735 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6736
6737 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6738 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6739 and dhcp3-server-ldap in Debian use the LDAP server. The two
6740 implementations are quite different in how they use LDAP.&lt;/p&gt;
6741
6742 To get this information, I started slapd with debugging enabled and
6743 dumped the debug output to a file to get the LDAP searches performed
6744 on a Debian Edu main-server. Here is a summary.
6745
6746 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6747
6748 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6749 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6750 the web.
6751
6752 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6753 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6754 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6755 reverse entries are in two different subtrees in LDAP with a structure
6756 based on the DNS names, as in tjener.intern and
6757 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6758
6759 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6760 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6761 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6762 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6763 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6764 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6765 forward entries, it is looking for attributes named dnsttl, arecord,
6766 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6767 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6768 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6769 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6770 spfrecord and modifytimestamp. For reverse entries it is looking for
6771 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6772 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6773 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6774 ldapsearch commands could look like this:&lt;/p&gt;
6775
6776 &lt;blockquote&gt;&lt;pre&gt;
6777 ldapsearch -h ldap \
6778 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6779 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6780 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6781 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6782 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6783 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6784
6785 ldapsearch -h ldap \
6786 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6787 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6788 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6789 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6790 srvrecord naptrrecord modifytimestamp
6791 &lt;/pre&gt;&lt;/blockquote&gt;
6792
6793 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6794 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6795 example LDAP objects used there. In addition to these objects, the
6796 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6797 also exist.&lt;/p&gt;
6798
6799 &lt;blockquote&gt;&lt;pre&gt;
6800 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6801 objectclass: top
6802 objectclass: dnsdomain
6803 objectclass: domainrelatedobject
6804 dc: tjener
6805 arecord: 10.0.2.2
6806 associateddomain: tjener.intern
6807
6808 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6809 objectclass: top
6810 objectclass: dnsdomain2
6811 objectclass: domainrelatedobject
6812 dc: 2
6813 ptrrecord: tjener.intern
6814 associateddomain: 2.2.0.10.in-addr.arpa
6815 &lt;/pre&gt;&lt;/blockquote&gt;
6816
6817 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6818 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6819 same base as in the tree mode for a object with filter
6820 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6821 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6822 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6823 naptrrecord and modifytimestamp. For reverse entires it also do a
6824 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6825 and the requested attributes are associateddomain, dnsttl and
6826 modifytimestamp. In short, in strict mode the objects with ptrrecord
6827 go away, and the arecord attribute in the forward object is used
6828 instead.&lt;/p&gt;
6829
6830 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6831 like this:&lt;/p&gt;
6832
6833 &lt;blockquote&gt;&lt;pre&gt;
6834 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6835 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6836 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6837 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6838 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6839 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6840
6841 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6842 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6843 &lt;/pre&gt;&lt;/blockquote&gt;
6844
6845 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6846 search for SOA records, which behave similar to the forward and
6847 reverse lookups.&lt;/p&gt;
6848
6849 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6850 specify any objectclass names, and instead look for the attributes it
6851 need to generate a DNS reply. This make it able to work with any
6852 objectclass that provide the needed attributes.&lt;/p&gt;
6853
6854 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6855 dnsdomain2 schemas. The latter is used for reverse entries like
6856 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6857
6858 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6859 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6860 attributes) and domainrelatedobject (for associatedDomain). The use
6861 of structural object classes make it impossible to combine these
6862 classes with the object classes used by DHCP.&lt;/p&gt;
6863
6864 &lt;p&gt;There are other schemas that could be used too, for example the
6865 dnszone structural object class used by Gosa and bind-sdb for the DNS
6866 attributes combined with the domainrelatedobject object class, but in
6867 this case some unused attributes would have to be included as well
6868 (zonename and relativedomainname).&lt;/p&gt;
6869
6870 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6871 mode and not use any of the existing objectclasses (dnsdomain,
6872 dnsdomain2 and dnszone) when one want to combine the DNS information
6873 with DHCP information, and instead create a auxiliary object class
6874 defined something like this (using the attributes defined for
6875 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6876
6877 &lt;blockquote&gt;&lt;pre&gt;
6878 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6879 SUP top
6880 AUXILIARY
6881 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6882 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6883 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6884 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6885 A6Record $ DNAMERecord
6886 ))
6887 &lt;/pre&gt;&lt;/blockquote&gt;
6888
6889 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6890 the domainrelatedobject object class, and allow any entity to include
6891 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6892 developers asking for their view on this schema and if they are
6893 interested in providing such schema with PowerDNS, and I hope my
6894 message will be accepted into their mailing list soon.&lt;/p&gt;
6895
6896 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6897
6898 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6899 the object attributes, and then uses the attributes it want. This
6900 make it harder to figure out exactly what attributes are used, but
6901 thanks to the working example in Debian Edu I can at least get an idea
6902 what is needed without having to read the source code.&lt;/p&gt;
6903
6904 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6905 search filter to use to locate the correct dhcpServer entity is
6906 stored. These are the relevant entries from
6907 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6908
6909 &lt;blockquote&gt;&lt;pre&gt;
6910 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6911 ldap-dhcp-server-cn &quot;dhcp&quot;;
6912 &lt;/pre&gt;&lt;/blockquote&gt;
6913
6914 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6915 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6916 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6917 search result is this entry:&lt;/p&gt;
6918
6919 &lt;blockquote&gt;&lt;pre&gt;
6920 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6921 cn: dhcp
6922 objectClass: top
6923 objectClass: dhcpServer
6924 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6925 &lt;/pre&gt;&lt;/blockquote&gt;
6926
6927 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6928 subtree with DHCP configuration. The DHCP configuration subtree base
6929 is located using a base scope search with base &quot;cn=DHCP
6930 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6931 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6932 The search result is this entry:&lt;/p&gt;
6933
6934 &lt;blockquote&gt;&lt;pre&gt;
6935 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6936 cn: DHCP Config
6937 objectClass: top
6938 objectClass: dhcpService
6939 objectClass: dhcpOptions
6940 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6941 dhcpStatements: ddns-update-style none
6942 dhcpStatements: authoritative
6943 dhcpOption: smtp-server code 69 = array of ip-address
6944 dhcpOption: www-server code 72 = array of ip-address
6945 dhcpOption: wpad-url code 252 = text
6946 &lt;/pre&gt;&lt;/blockquote&gt;
6947
6948 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6949 all the DHCP configuration is loaded, it is ready to receive requests.
6950 The subtree in Debian Edu contain objects with object classes
6951 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6952 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6953 and information about netmasks, dynamic range etc. Leaving out the
6954 details here because it is not relevant for the focus of my
6955 investigation, which is to see if it is possible to merge dns and dhcp
6956 related computer objects.&lt;/p&gt;
6957
6958 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6959 of the client (00:00:00:00:00:00 in this example), using a subtree
6960 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6961 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6962 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6963 like:&lt;/p&gt;
6964
6965 &lt;blockquote&gt;&lt;pre&gt;
6966 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6967 cn: hostname
6968 objectClass: top
6969 objectClass: dhcpHost
6970 dhcpHWAddress: ethernet 00:00:00:00:00:00
6971 dhcpStatements: fixed-address hostname
6972 &lt;/pre&gt;&lt;/blockquote&gt;
6973
6974 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6975 The object classes need to have fixed names, and the configuration
6976 need to be stored in a fairly specific LDAP structure. On the
6977 positive side, the invidiual dhcpHost entires can be anywhere without
6978 the DN pointed to by the dhcpServer entries. The latter should make
6979 it possible to group all host entries in a subtree next to the
6980 configuration entries, and this subtree can also be shared with the
6981 DNS server if the schema proposed above is combined with the dhcpHost
6982 structural object class.
6983
6984 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6985
6986 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6987 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6988 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6989 allowing DNS objects to be stored anywhere under the base cn specified
6990 in the configuration.&lt;/p&gt;
6991
6992 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6993 regarding which LDAP schemas to use and which LDAP structure to use.
6994 I guess one could implement ones own schema, as long as the
6995 objectclasses and attributes have the names used, but this do not
6996 really help when the DHCP subtree need to have a fairly fixed
6997 structure.&lt;/p&gt;
6998
6999 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
7000 this might work for Debian Edu:&lt;/p&gt;
7001
7002 &lt;blockquote&gt;&lt;pre&gt;
7003 ou=services
7004 cn=machine-info (dhcpService) - dhcpServiceDN points here
7005 cn=dhcp (dhcpServer)
7006 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7007 cn=10.0.2.0 (dhcpSubnet)
7008 cn=group1 (dhcpGroup/dhcpOptions)
7009 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7010 cn=192.168.0.0 (dhcpSubnet)
7011 cn=group1 (dhcpGroup/dhcpOptions)
7012 ou=machines - PowerDNS base points here
7013 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7014 &lt;/pre&gt;&lt;/blockquote&gt;
7015
7016 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
7017 entries to be in the dhcpGroup subtrees, the entries can be stored
7018 there instead of a common machines subtree, and the PowerDNS base
7019 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
7020
7021 &lt;p&gt;The combined object under the machines subtree would look something
7022 like this:&lt;/p&gt;
7023
7024 &lt;blockquote&gt;&lt;pre&gt;
7025 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7026 dc: hostname
7027 objectClass: top
7028 objectClass: dhcpHost
7029 objectclass: domainrelatedobject
7030 objectclass: dnsDomainAux
7031 associateddomain: hostname.intern
7032 arecord: 10.11.12.13
7033 dhcpHWAddress: ethernet 00:00:00:00:00:00
7034 dhcpStatements: fixed-address hostname.intern
7035 &lt;/pre&gt;&lt;/blockquote&gt;
7036
7037 &lt;/p&gt;One could even add the LTSP configuration associated with a given
7038 machine, as long as the required attributes are available in a
7039 auxiliary object class.&lt;/p&gt;
7040 </description>
7041 </item>
7042
7043 <item>
7044 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
7045 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
7046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
7047 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
7048 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
7049 DHCP services in Debian Edu to use the same LDAP objects for a given
7050 computer, to avoid the possibility of having a inconsistent state for
7051 a computer in LDAP (as in DHCP but no DNS entry or the other way
7052 around) and make it easier to add computers to LDAP.&lt;/p&gt;
7053
7054 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
7055 information finally found a solution that seem to work.&lt;/p&gt;
7056
7057 &lt;p&gt;The old setup required three LDAP objects for a given computer.
7058 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7059 we switch powerdns to use its strict LDAP method (ldap-method=strict
7060 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7061 merged into one while making it impossible to transfer the reverse map
7062 to a slave DNS server.&lt;/p&gt;
7063
7064 &lt;p&gt;If we also replace the object class used to get the DNS related
7065 attributes to one allowing these attributes to be combined with the
7066 dhcphost object class, we can merge the DNS and DHCP entries into one.
7067 I&#39;ve written such object class in the dnsdomainaux.schema file (need
7068 proper OIDs, but that is a minor issue), and tested the setup. It
7069 seem to work.&lt;/p&gt;
7070
7071 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
7072 for both DNS and DHCP, and even the LTSP configuration I suggested in
7073 an earlier email. The combined LDAP object will look something like
7074 this:&lt;/p&gt;
7075
7076 &lt;blockquote&gt;&lt;pre&gt;
7077 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7078 cn: hostname
7079 objectClass: dhcphost
7080 objectclass: domainrelatedobject
7081 objectclass: dnsdomainaux
7082 associateddomain: hostname.intern
7083 arecord: 10.11.12.13
7084 dhcphwaddress: ethernet 00:00:00:00:00:00
7085 dhcpstatements: fixed-address hostname
7086 ldapconfigsound: Y
7087 &lt;/pre&gt;&lt;/blockquote&gt;
7088
7089 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
7090 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7091 before asking DNS to resolve the fixed-adddress. LTSP will use
7092 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
7093
7094 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
7095 dhcphost in a different location, to allow us to put the objects
7096 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7097 that. If I can&#39;t figure out a way to do that, we can still get rid of
7098 the hosts subtree and move all its content into the DHCP Config tree
7099 (which probably should be renamed to be more related to the new
7100 content. I suspect cn=dnsdhcp,ou=services or something like that
7101 might be a good place to put it.&lt;/p&gt;
7102
7103 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7104 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7105 </description>
7106 </item>
7107
7108 <item>
7109 <title>Idea for storing LTSP configuration in LDAP</title>
7110 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7111 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7112 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7113 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7114 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7115 clients, and that this can be used to fetch configuration from LDAP if
7116 Debian Edu choose to store configuration there.&lt;/p&gt;
7117
7118 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7119 to get configuration from LDAP. The idea is to look up the MAC
7120 address of the client in LDAP, and look for attributes on the form
7121 ltspconfigsetting=value, and use this to export SETTING=value to the
7122 LTSP clients.&lt;/p&gt;
7123
7124 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7125 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7126 allowing us to store all information about a computer in one place.&lt;/p&gt;
7127
7128 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7129 this approach. A real LDAP schema for the ltspClientAux objectclass
7130 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7131
7132 &lt;blockquote&gt;&lt;pre&gt;
7133 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7134 #
7135 # Fetch LTSP client settings from LDAP based on MAC address
7136 #
7137 # Uses ethernet address as stored in the dhcpHost objectclass using
7138 # the dhcpHWAddress attribute or ethernet address stored in the
7139 # ieee802Device objectclass with the macAddress attribute.
7140 #
7141 # This module is written to be schema agnostic, and only depend on the
7142 # existence of attribute names.
7143 #
7144 # The LTSP configuration variables are saved directly using a
7145 # ltspConfig prefix and uppercasing the rest of the attribute name.
7146 # To set the SERVER variable, set the ltspConfigServer attribute.
7147 #
7148 # Some LDAP schema should be created with all the relevant
7149 # configuration settings. Something like this should work:
7150 #
7151 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7152 # SUP top
7153 # AUXILIARY
7154 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7155
7156 LDAPSERVER=$(debian-edu-ldapserver)
7157 if [ &quot;$LDAPSERVER&quot; ] ; then
7158 LDAPBASE=$(debian-edu-ldapserver -b)
7159 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7160 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7161 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7162 grep &#39;^ltspConfig&#39; | while read attr value ; do
7163 # Remove prefix and convert to upper case
7164 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7165 # bass value on to clients
7166 eval &quot;$attr=$value; export $attr&quot;
7167 done
7168 done
7169 fi
7170 &lt;/pre&gt;&lt;/blockquote&gt;
7171
7172 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7173 the while block might end up in a subshell causing the variables set
7174 there to not show up in ltsp-config, but if that is the case I am sure
7175 the code can be restructured to make sure the variables are passed on.
7176 I expect that can be solved with some testing. :)&lt;/p&gt;
7177
7178 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7179 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7180
7181 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7182 configuration in LDAP that was created around year 2000 by
7183 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7184 Xperience, Inc., 2000&lt;/a&gt;. I found its
7185 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7186 personal home page over at redhat.com.&lt;/p&gt;
7187 </description>
7188 </item>
7189
7190 <item>
7191 <title>jXplorer, a very nice LDAP GUI</title>
7192 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7193 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7194 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7195 <description>&lt;p&gt;Since
7196 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7197 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7198 LDAP GUI that is even better than luma. The java application
7199 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7200 moving LDAP objects and subtrees using drag-and-drop, and can
7201 authenticate using Kerberos. I have only tested the Kerberos
7202 authentication, but do not have a LDAP setup allowing me to rewrite
7203 LDAP with my test user yet. It is
7204 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7205 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7206 have with it is how it handle errors. If something go wrong, its
7207 non-intuitive behaviour require me to go through some query work list
7208 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7209 </description>
7210 </item>
7211
7212 <item>
7213 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7214 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7215 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7216 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7217 <description>&lt;p&gt;Here is a short update on my &lt;a
7218 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7219 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7220 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7221 not reporting the status for KDE, because the upgrade crashes when
7222 aptitude try because of missing conflicts
7223 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7224 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7225
7226 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7227 complete list of the installed packages. Based on this I see these
7228 differences when I did a test run today. As usual, I do not really
7229 know what the correct set of packages would be, but thought it best to
7230 publish the difference.&lt;/p&gt;
7231
7232 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7233
7234 &lt;blockquote&gt;&lt;p&gt;
7235 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7236 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7237 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7238 libgtksourceview-common libpt-1.10.10-plugins-alsa
7239 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7240 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7241 python-4suite-xml python-eggtrayicon python-gtkhtml2
7242 python-gtkmozembed svgalibg1 xserver-xephyr zip
7243 &lt;/p&gt;&lt;/blockquote&gt;
7244
7245 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7246
7247 &lt;blockquote&gt;&lt;p&gt;
7248 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7249 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7250 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7251 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7252 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7253 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7254 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7255 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7256 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7257 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7258 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7259 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7260 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7261 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7262 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7263 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7264 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7265 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7266 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7267 mysql-common swfdec-gnome totem-gstreamer wodim
7268 &lt;/p&gt;&lt;/blockquote&gt;
7269
7270 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7271
7272 &lt;blockquote&gt;&lt;p&gt;
7273 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7274 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7275 xserver-xorg-input-all xserver-xorg-input-evdev
7276 xserver-xorg-input-kbd xserver-xorg-input-mouse
7277 xserver-xorg-input-synaptics xserver-xorg-video-all
7278 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7279 xserver-xorg-video-chips xserver-xorg-video-cirrus
7280 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7281 xserver-xorg-video-glint xserver-xorg-video-i128
7282 xserver-xorg-video-i740 xserver-xorg-video-mach64
7283 xserver-xorg-video-mga xserver-xorg-video-neomagic
7284 xserver-xorg-video-nouveau xserver-xorg-video-nv
7285 xserver-xorg-video-r128 xserver-xorg-video-radeon
7286 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7287 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7288 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7289 xserver-xorg-video-sis xserver-xorg-video-sisusb
7290 xserver-xorg-video-tdfx xserver-xorg-video-tga
7291 xserver-xorg-video-trident xserver-xorg-video-tseng
7292 xserver-xorg-video-vesa xserver-xorg-video-vmware
7293 xserver-xorg-video-voodoo
7294 &lt;/p&gt;&lt;/blockquote&gt;
7295
7296 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7297
7298 &lt;blockquote&gt;&lt;p&gt;
7299 deskbar-applet xserver-xorg xserver-xorg-core
7300 xserver-xorg-input-wacom xserver-xorg-video-intel
7301 xserver-xorg-video-openchrome
7302 &lt;/p&gt;&lt;/blockquote&gt;
7303
7304 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7305 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7306 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7307 No idea when it hits Squeeze, but when it does I hope it will reduce
7308 the difference somewhat.
7309 </description>
7310 </item>
7311
7312 <item>
7313 <title>LUMA, a very nice LDAP GUI</title>
7314 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7315 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7316 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7317 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7318 directory in Debian Edu, and in the process I started to miss a GUI
7319 tool to browse the LDAP tree. The only one I was able to find in
7320 Debian/Squeeze and Lenny is
7321 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7322 be a great tool to get a overview of the current LDAP directory
7323 populated by default in Skolelinux. Thanks to it, I have been able to
7324 find empty and obsolete subtrees, misplaced objects and duplicate
7325 objects. It will be installed by default in Debian/Squeeze. If you
7326 are working with LDAP, give it a go. :)&lt;/p&gt;
7327
7328 &lt;p&gt;I did notice one problem with it I have not had time to report to
7329 the BTS yet. There is no .desktop file in the package, so the tool do
7330 not show up in the Gnome and KDE menus, but only deep down in in the
7331 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7332 released.&lt;/p&gt;
7333
7334 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7335 like to move objects and remove subtrees directly in the GUI, but have
7336 not found a way to do that with LUMA yet. So in the mean time, I use
7337 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7338
7339 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7340 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7341
7342 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7343 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7344 useful GUI alternative. It seem like a good tool, but is unmaintained
7345 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7346 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7347 </description>
7348 </item>
7349
7350 <item>
7351 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7352 <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>
7353 <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>
7354 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7355 <description>&lt;p&gt;A while back, I
7356 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7357 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7358 for storing DNS and DHCP information in LDAP to combine the two sets
7359 of information into one LDAP object representing a computer.&lt;/p&gt;
7360
7361 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7362 the dhcpHost object class auxiliary, to allow it to be combined with
7363 the dNSDomain object class, and thus forming one object for one
7364 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7365
7366 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7367 without also changing the assigned number for the object class, and I
7368 do not know enough about LDAP schema design to do that properly for
7369 Debian Edu.&lt;/p&gt;
7370
7371 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7372 the
7373 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7374 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7375 available today from IETF.&lt;/p&gt;
7376
7377 &lt;pre&gt;
7378 --- dhcp.schema (revision 65192)
7379 +++ dhcp.schema (working copy)
7380 @@ -376,7 +376,7 @@
7381 objectclass ( 2.16.840.1.113719.1.203.6.6
7382 NAME &#39;dhcpHost&#39;
7383 DESC &#39;This represents information about a particular client&#39;
7384 - SUP top
7385 + SUP top AUXILIARY
7386 MUST cn
7387 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7388 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7389 &lt;/pre&gt;
7390
7391 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7392 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7393 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7394
7395 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7396 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7397 </description>
7398 </item>
7399
7400 <item>
7401 <title>Calling tasksel like the installer, while still getting useful output</title>
7402 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7403 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7404 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7405 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7406 installs packages during the normal debian-installer run. Until now,
7407 I have ended up letting tasksel do the work, with the annoying problem
7408 of not getting any feedback at all when something fails (like a
7409 conffile question from dpkg or a download that fails), using code like
7410 this:
7411
7412 &lt;blockquote&gt;&lt;pre&gt;
7413 export DEBIAN_FRONTEND=noninteractive
7414 tasksel --new-install
7415 &lt;/pre&gt;&lt;/blockquote&gt;
7416
7417 This would invoke tasksel, let its automatic task selection pick the
7418 tasks to install, and continue to install the requested tasks without
7419 any output what so ever.
7420
7421 Recently I revisited this problem while working on the automatic
7422 package upgrade testing, because tasksel would some times hang without
7423 any useful feedback, and I want to see what is going on when it
7424 happen. Then it occured to me, I can parse the output from tasksel
7425 when asked to run in test mode, and use that aptitude command line
7426 printed by tasksel then to simulate the tasksel run. I ended up using
7427 code like this:
7428
7429 &lt;blockquote&gt;&lt;pre&gt;
7430 export DEBIAN_FRONTEND=noninteractive
7431 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7432 $cmd
7433 &lt;/pre&gt;&lt;/blockquote&gt;
7434
7435 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7436 --without-recommends -o APT::Install-Recommends=no -y install
7437 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7438 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7439 laptop task and all packages with priority standard , required and
7440 important, just like tasksel would have done it during
7441 installation.&lt;/p&gt;
7442
7443 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7444 install packages without using debconf-apt-progress, for use cases
7445 like this.&lt;/p&gt;
7446 </description>
7447 </item>
7448
7449 <item>
7450 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7451 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7452 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7453 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7454 <description>&lt;p&gt;My
7455 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7456 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7457 finally made the upgrade logs available from
7458 &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;.
7459 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7460 apt and aptitude, and found their differences interesting. This time
7461 I will only focus on their removal plans.&lt;/p&gt;
7462
7463 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7464 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7465 surprising part is that it want to remove xorg and all
7466 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7467 sure why. When asking aptitude to do the same, it want to remove 129
7468 packages, but most of them are library packages I suspect are no
7469 longer needed. Both of them want to remove bluetooth packages, which
7470 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7471
7472 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7473 which seem like a bad idea and xorg the same way as with Gnome. Asking
7474 aptitude for the same, it wants to remove 192 packages, none which are
7475 too surprising.&lt;/p&gt;
7476
7477 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7478 and avoided, and perhaps others as well. Here are the complete list
7479 of planned removals. The complete logs is available from the URL
7480 above. Note if you want to repeat these tests, that the upgrade test
7481 for kde+apt-get hung in the tasksel setup because of dpkg asking
7482 conffile questions. No idea why. I worked around it by using
7483 &#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
7484 continue.&lt;/p&gt;
7485
7486 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7487 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7488 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7489 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7490 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7491 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7492 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7493 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7494 xserver-xorg-input-kbd xserver-xorg-input-mouse
7495 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7496 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7497 xserver-xorg-video-ati xserver-xorg-video-chips
7498 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7499 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7500 xserver-xorg-video-glint xserver-xorg-video-i128
7501 xserver-xorg-video-i740 xserver-xorg-video-imstt
7502 xserver-xorg-video-intel xserver-xorg-video-mach64
7503 xserver-xorg-video-mga xserver-xorg-video-neomagic
7504 xserver-xorg-video-nsc xserver-xorg-video-nv
7505 xserver-xorg-video-openchrome xserver-xorg-video-r128
7506 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7507 xserver-xorg-video-rendition xserver-xorg-video-s3
7508 xserver-xorg-video-s3virge xserver-xorg-video-savage
7509 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7510 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7511 xserver-xorg-video-tga xserver-xorg-video-trident
7512 xserver-xorg-video-tseng xserver-xorg-video-v4l
7513 xserver-xorg-video-vesa xserver-xorg-video-vga
7514 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7515 xulrunner-1.9-gnome-support&lt;/p&gt;
7516
7517 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7518
7519 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7520 djvulibre-desktop finger gnome-app-install gnome-mount
7521 gnome-network-admin gnome-spell gnome-vfs-obexftp
7522 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7523 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7524 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7525 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7526 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7527 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7528 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7529 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7530 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7531 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7532 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7533 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7534 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7535 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7536 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7537 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7538 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7539 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7540 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7541 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7542 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7543 openoffice.org-writer2latex openssl-blacklist p7zip
7544 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7545 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7546 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7547 swfdec-mozilla totem-gstreamer update-manager wodim
7548 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7549 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7550 zip&lt;/p&gt;
7551
7552 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7553
7554 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7555 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7556 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7557 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7558 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7559 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7560 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7561 xserver-xorg-input-kbd xserver-xorg-input-mouse
7562 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7563 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7564 xserver-xorg-video-ati xserver-xorg-video-chips
7565 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7566 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7567 xserver-xorg-video-glint xserver-xorg-video-i128
7568 xserver-xorg-video-i740 xserver-xorg-video-imstt
7569 xserver-xorg-video-intel xserver-xorg-video-mach64
7570 xserver-xorg-video-mga xserver-xorg-video-neomagic
7571 xserver-xorg-video-nsc xserver-xorg-video-nv
7572 xserver-xorg-video-openchrome xserver-xorg-video-r128
7573 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7574 xserver-xorg-video-rendition xserver-xorg-video-s3
7575 xserver-xorg-video-s3virge xserver-xorg-video-savage
7576 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7577 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7578 xserver-xorg-video-tga xserver-xorg-video-trident
7579 xserver-xorg-video-tseng xserver-xorg-video-v4l
7580 xserver-xorg-video-vesa xserver-xorg-video-vga
7581 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7582
7583 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7584 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7585 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7586 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7587 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7588 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7589 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7590 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7591 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7592 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7593 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7594 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7595 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7596 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7597 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7598 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7599 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7600 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7601 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7602 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7603 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7604 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7605 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7606 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7607 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7608 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7609 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7610 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7611 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7612 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7613 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7614 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7615 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7616 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7617 texlive-common texlive-doc-base texlive-fonts-recommended
7618 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7619 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7620 xulrunner-1.9&lt;/p&gt;
7621
7622 </description>
7623 </item>
7624
7625 <item>
7626 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7627 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7628 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7629 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7630 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7631 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7632 have been discovered and reported in the process
7633 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7634 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7635 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7636 kdebase-workspace-data), and to get a more regular testing going on, I
7637 am working on a script to automate the test.&lt;/p&gt;
7638
7639 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7640 Gnome or KDE desktop installation inside the chroot before upgrading
7641 it. To ensure no services are started in the chroot, a policy-rc.d
7642 script is inserted. To make sure tasksel believe it is to install a
7643 desktop on a laptop, the tasksel tests are replaced in the chroot
7644 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7645
7646 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7647 currently always fail because udev refuses to upgrade with the kernel
7648 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7649 is created. The bug report
7650 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7651 this problem do not trigger in a chroot, but I touch the file anyway
7652 to make sure the upgrade go well. Testing on virtual and real
7653 hardware have failed me because of udev so far, and creating this file
7654 do the trick in such settings anyway. This is a
7655 &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
7656 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7657 maintainer because he lack the resources to rewrite udev to keep
7658 working with old kernels or something like that. I really wish the
7659 udev upstream would keep udev backwards compatible, to avoid such
7660 upgrade problem, but given that they fail to do so, I guess
7661 documenting the way out of this mess is the best option we got for
7662 Debian Squeeze.&lt;/p&gt;
7663
7664 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7665 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7666 trick:&lt;/p&gt;
7667
7668 &lt;blockquote&gt;&lt;pre&gt;
7669 #!/bin/sh
7670 set -ex
7671
7672 if [ &quot;$1&quot; ] ; then
7673 desktop=$1
7674 else
7675 desktop=gnome
7676 fi
7677
7678 from=lenny
7679 to=squeeze
7680
7681 exec &amp;lt; /dev/null
7682 unset LANG
7683 mirror=http://ftp.skolelinux.org/debian
7684 tmpdir=chroot-$from-upgrade-$to-$desktop
7685 fuser -mv .
7686 debootstrap $from $tmpdir $mirror
7687 chroot $tmpdir aptitude update
7688 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7689 #!/bin/sh
7690 exit 101
7691 EOF
7692 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7693 exit_cleanup() {
7694 umount $tmpdir/proc
7695 }
7696 mount -t proc proc $tmpdir/proc
7697 # Make sure proc is unmounted also on failure
7698 trap exit_cleanup EXIT INT
7699
7700 chroot $tmpdir aptitude -y install debconf-utils
7701
7702 # Make sure tasksel autoselection trigger. It need the test scripts
7703 # to return the correct answers.
7704 echo tasksel tasksel/desktop multiselect $desktop | \
7705 chroot $tmpdir debconf-set-selections
7706
7707 # Include the desktop and laptop task
7708 for test in desktop laptop ; do
7709 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7710 #!/bin/sh
7711 exit 2
7712 EOF
7713 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7714 done
7715
7716 DEBIAN_FRONTEND=noninteractive
7717 DEBIAN_PRIORITY=critical
7718 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7719 chroot $tmpdir tasksel --new-install
7720
7721 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7722 chroot $tmpdir aptitude update
7723 touch $tmpdir/etc/udev/kernel-upgrade
7724 chroot $tmpdir aptitude -y dist-upgrade
7725 fuser -mv
7726 &lt;/pre&gt;&lt;/blockquote&gt;
7727
7728 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7729 with aptitude, but I have not had time to look at how they behave
7730 differently so far. I hope to get a cron job running to do the test
7731 regularly and post the result on the web. The Gnome upgrade currently
7732 work, while the KDE upgrade fail because of the bug in
7733 kdebase-workspace-data&lt;/p&gt;
7734
7735 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7736 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7737 post, so I will refrain from trying. I can report that for Gnome,
7738 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7739 remove and 1 not upgraded and 1024MB need to be downloaded while for
7740 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7741 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7742
7743 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7744 is able to migrate to dependency based boot sequencing and parallel
7745 booting without a hitch. Was unsure if there were still bugs with
7746 packages failing to clean up their obsolete init.d script during
7747 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7748 packages.&lt;/p&gt;
7749 </description>
7750 </item>
7751
7752 <item>
7753 <title>Upstart or sysvinit - as init.d scripts see it</title>
7754 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7755 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7756 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7757 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7758 scripts to migrate (some of) their operations to upstart job while
7759 keeping the init.d for hurd and kfreebsd. The packages with such
7760 needs will need a way to get their init.d scripts to behave
7761 differently when used with sysvinit and with upstart. Because of
7762 this, I had a look at the environment variables set when a init.d
7763 script is running under upstart, and when it is not.&lt;/p&gt;
7764
7765 &lt;p&gt;With upstart, I notice these environment variables are set when a
7766 script is started from rcS.d/ (ignoring some irrelevant ones like
7767 COLUMNS):&lt;/p&gt;
7768
7769 &lt;blockquote&gt;&lt;pre&gt;
7770 DEFAULT_RUNLEVEL=2
7771 previous=N
7772 PREVLEVEL=
7773 RUNLEVEL=
7774 runlevel=S
7775 UPSTART_EVENTS=startup
7776 UPSTART_INSTANCE=
7777 UPSTART_JOB=rc-sysinit
7778 &lt;/pre&gt;&lt;/blockquote&gt;
7779
7780 &lt;p&gt;With sysvinit, these environment variables are set for the same
7781 script.&lt;/p&gt;
7782
7783 &lt;blockquote&gt;&lt;pre&gt;
7784 INIT_VERSION=sysvinit-2.88
7785 previous=N
7786 PREVLEVEL=N
7787 RUNLEVEL=S
7788 runlevel=S
7789 &lt;/pre&gt;&lt;/blockquote&gt;
7790
7791 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7792 sysvinit are not set by upstart. Not sure if it is intentional or not
7793 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7794
7795 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7796 looking for the UPSTART_JOB environment variable seem to be a good
7797 choice.&lt;/p&gt;
7798 </description>
7799 </item>
7800
7801 <item>
7802 <title>A manual for standards wars...</title>
7803 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7804 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7805 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7806 <description>&lt;p&gt;Via the
7807 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7808 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7809 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7810 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7811 following the standards wars of today.&lt;/p&gt;
7812 </description>
7813 </item>
7814
7815 <item>
7816 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7817 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7818 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7819 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7820 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7821 to get a list of the machine types in use thanks to the DMI
7822 information extracted from each machine. The script to do so is
7823 included in the sitesummary package, and here is example output from
7824 the Skolelinux build servers:&lt;/p&gt;
7825
7826 &lt;blockquote&gt;&lt;pre&gt;
7827 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7828 vendor count
7829 Dell Computer Corporation 1
7830 PowerEdge 1750 1
7831 IBM 1
7832 eserver xSeries 345 -[8670M1X]- 1
7833 Intel 2
7834 [no-dmi-info] 3
7835 maintainer:~#
7836 &lt;/pre&gt;&lt;/blockquote&gt;
7837
7838 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7839 provided in each machine. Here there are Intel machines without model
7840 information listed with Intel as vendor and no model, and virtual Xen
7841 machines listed as [no-dmi-info]. One can add -l as a command line
7842 option to list the individual machines.&lt;/p&gt;
7843
7844 &lt;p&gt;A larger list is
7845 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7846 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7847 provide the basic sitesummary report publicly. In their report there
7848 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7849 their machines, and as sitesummary is available in both distributions,
7850 it is trivial to get all of them to report to the same central
7851 collector.&lt;/p&gt;
7852 </description>
7853 </item>
7854
7855 <item>
7856 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7857 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7858 <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>
7859 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7860 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7861 start at boot when an NVidia video card is used is handled. The
7862 problem seem to be that the nvidia X.org driver uses a long time to
7863 initialize, and this duration is longer than kdm is configured to
7864 wait.&lt;/p&gt;
7865
7866 &lt;p&gt;I came across two bugs related to this issue,
7867 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7868 against initscripts and passed on to nvidia-glx when it became obvious
7869 that the nvidia drivers were involved, and
7870 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7871 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7872
7873 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7874 problem nvidia video card owners experience and make sure the Debian
7875 distribution work out of the box for these users. The nvidia driver
7876 maintainers expect kdm to be set up to wait longer, while kdm expect
7877 the nvidia driver maintainers to fix the driver to start faster, and
7878 while they wait for each other I guess the users end up switching to a
7879 distribution that work for them. I have no idea what the solution is,
7880 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7881
7882 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7883 </description>
7884 </item>
7885
7886 <item>
7887 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7888 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7890 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7891 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7892 The feature seem to hold up pretty well, but three fairly serious
7893 issues are known and should be solved:
7894
7895 &lt;p&gt;&lt;ul&gt;
7896
7897 &lt;li&gt;The wicd package seen to
7898 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7899 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7900 parallel booting is enabled. No idea why, but the wicd maintainer
7901 seem to be on the case.&lt;/li&gt;
7902
7903 &lt;li&gt;The nvidia X driver seem to
7904 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7905 triggered more easily when parallel booting is in effect. The
7906 maintainer is on the case.&lt;/li&gt;
7907
7908 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7909 sequencing (the shutdown is broken) when old file-rc users
7910 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7911 sysv-rc. One way to solve it would be for file-rc to create
7912 /etc/init.d/.legacy-bootordering, and another is to try to make
7913 sysv-rc more robust. Will investigate some more and probably upload a
7914 workaround in sysv-rc to help those trying to move from file-rc to
7915 sysv-rc get a working shutdown.&lt;/li&gt;
7916
7917 &lt;/ul&gt;&lt;/p&gt;
7918
7919 &lt;p&gt;All in all not many surprising issues, and all of them seem
7920 solvable before Squeeze is released. In addition to these there are
7921 some packages with bugs in their dependencies and run level settings,
7922 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7923
7924 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7925 the BTS, please usertag the report to get it to show up at
7926 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7927 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7928
7929 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7930 </description>
7931 </item>
7932
7933 <item>
7934 <title>More flexible firmware handling in debian-installer</title>
7935 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7936 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7937 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7938 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7939 found time today to return to the project. Having to spend less time
7940 working dependency based boot in debian, as it is almost complete now,
7941 definitely helped freeing some time.&lt;/p&gt;
7942
7943 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7944 include some firmware packages on the Debian Edu CDs, those needed to
7945 get disk and network controllers working. Without having these
7946 firmware packages available during installation, it is impossible to
7947 install Debian Edu on the given machine, and because our target group
7948 are non-technical people, asking them to provide firmware packages on
7949 an external medium is a support pain. Initially, I expected it to be
7950 enough to include the firmware packages on the CD to get
7951 debian-installer to find and use them. This proved to be wrong.
7952 Next, I hoped it was enough to symlink the relevant firmware packages
7953 to some useful location on the CD (tried /cdrom/ and
7954 /cdrom/firmware/). This also proved to not work, and at this point I
7955 found time to look at the debian-installer code to figure out what was
7956 going to work.&lt;/p&gt;
7957
7958 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7959 look revealed that it would only look for firmware packages outside
7960 the installation media, so the CD was never checked for firmware
7961 packages. It would only check USB sticks, floppies and other
7962 &quot;external&quot; media devices. Today I changed it to also look in the
7963 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7964 solve the problem I ran into with Debian edu. I also changed it to
7965 look in /firmware/, to make sure the installer also find firmware
7966 provided in the initrd when booting the installer via PXE, to allow us
7967 to provide the same feature in the PXE setup included in Debian
7968 Edu.&lt;/p&gt;
7969
7970 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7971 activated without asking if the license is accepted, I extended
7972 hw-detect to look for preinst scripts in the firmware packages, and
7973 run these before activating the firmware during installation. The
7974 license question is asked using debconf in the preinst, so this should
7975 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7976
7977 &lt;p&gt;If you want to discuss the details of these features, please
7978 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7979 </description>
7980 </item>
7981
7982 <item>
7983 <title>Parallellized boot is now the default in Debian/unstable</title>
7984 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7985 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7986 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7987 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7988 Debian/unstable for machines using dependency based boot sequencing.
7989 Apparently the testing of concurrent booting has been wider than
7990 expected, if I am to believe the
7991 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7992 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7993 with the feature this weekend, to give us some time to detect any
7994 remaining problems before Squeeze is frozen. If serious problems are
7995 detected, it is simple to change the default back to sequential boot.
7996 The upload of the new sysvinit package also activate a new upstream
7997 version.&lt;/p&gt;
7998
7999 More information about
8000 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8001 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
8002 currently possible to disable parallel booting when one run into
8003 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
8004
8005 &lt;blockquote&gt;&lt;pre&gt;
8006 CONCURRENCY=none
8007 &lt;/pre&gt;&lt;/blockquote&gt;
8008
8009 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8010 the BTS, please usertag the report to get it to show up at
8011 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8012 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8013 </description>
8014 </item>
8015
8016 <item>
8017 <title>Sitesummary tip: Listing MAC address of all clients</title>
8018 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
8019 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
8020 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
8021 <description>&lt;p&gt;In the recent Debian Edu versions, the
8022 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
8023 system&lt;/a&gt; is used to keep track of the machines in the school
8024 network. Each machine will automatically report its status to the
8025 central server after boot and once per night. The network setup is
8026 also reported, and using this information it is possible to get the
8027 MAC address of all network interfaces in the machines. This is useful
8028 to update the DHCP configuration.&lt;/p&gt;
8029
8030 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
8031 ist all MAC addresses of all machines reporting to sitesummary. Run
8032 this on the collector host:&lt;/p&gt;
8033
8034 &lt;blockquote&gt;&lt;pre&gt;
8035 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
8036 &lt;/pre&gt;&lt;/blockquote&gt;
8037
8038 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
8039 line per machine and with space between the MAC addresses.&lt;/p&gt;
8040
8041 &lt;p&gt;To allow system administrators easier job at adding static DHCP
8042 addresses for hosts, it would be possible to extend this to fetch
8043 machine information from sitesummary and update the DHCP and DNS
8044 tables in LDAP using this information. Such tool is unfortunately not
8045 written yet.&lt;/p&gt;
8046 </description>
8047 </item>
8048
8049 <item>
8050 <title>systemd, an interesting alternative to upstart</title>
8051 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
8052 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
8053 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
8054 <description>&lt;p&gt;The last few days a new boot system called
8055 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
8056 has been
8057 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
8058
8059 to the free software world. I have not yet had time to play around
8060 with it, but it seem to be a very interesting alternative to
8061 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
8062 a good alternative for Debian when we are able to switch to an event
8063 based boot system. Tollef is
8064 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
8065 systemd into Debian, and I look forward to seeing how well it work. I
8066 like the fact that systemd handles init.d scripts with dependency
8067 information natively, allowing them to run in parallel where upstart
8068 at the moment do not.&lt;/p&gt;
8069
8070 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
8071 platform support. It only work on recent Linux kernels, and also need
8072 some new kernel features enabled to function properly. This means
8073 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8074 system. Not sure how that will be handled if systemd proves to be the
8075 way forward.&lt;/p&gt;
8076
8077 &lt;p&gt;In the mean time, based on the
8078 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8079 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
8080 decided to enable full parallel booting as the default in Debian as
8081 soon as possible (probably this weekend or early next week), to see if
8082 there are any remaining serious bugs in the init.d dependencies. A
8083 new version of the sysvinit package implementing this change is
8084 already in experimental. If all go well, Squeeze will be released
8085 with parallel booting enabled by default.&lt;/p&gt;
8086 </description>
8087 </item>
8088
8089 <item>
8090 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
8091 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
8092 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
8093 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
8094 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
8095 complete, so complete that it is actually possible to run all the
8096 init.d scripts in parallell based on these dependencies. If you want
8097 to test your Squeeze system, make sure
8098 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8099 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8100 /etc/default/rcS:&lt;/p&gt;
8101
8102 &lt;blockquote&gt;&lt;pre&gt;
8103 CONCURRENCY=makefile
8104 &lt;/pre&gt;&lt;/blockquote&gt;
8105
8106 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8107 scripts in parallel using the dependency information stored in
8108 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8109 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8110 to try to start the kdm and gdm scripts as early as possible, and will
8111 start the facilities required by kdm or gdm as early as possible to
8112 make this happen.&lt;/p&gt;
8113
8114 &lt;p&gt;Give it a try, and see if you like the result. If some services
8115 fail to start properly, it is most likely because they have incomplete
8116 init.d script dependencies in their startup script (or some of their
8117 dependent scripts have incomplete dependencies). Report bugs and get
8118 the package maintainers to fix it. :)&lt;/p&gt;
8119
8120 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8121 manage to get the init.d script dependencies complete and correct. I
8122 expect we will get there in Squeeze+1, if we get manage to test and
8123 fix the remaining issues.&lt;/p&gt;
8124
8125 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8126 the BTS, please usertag the report to get it to show up at
8127 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8128 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8129 </description>
8130 </item>
8131
8132 <item>
8133 <title>Debian has switched to dependency based boot sequencing</title>
8134 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8135 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8136 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8137 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8138 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8139 have been migrated to using dependency based boot sequencing. This
8140 conclude work me and others have been doing for the last three days.
8141 It feels great to see this finally part of the default Debian
8142 installation. Now we just need to weed out the last few problems that
8143 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8144
8145 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8146 fixing the more fundamental problem of handing the event based
8147 non-predictable kernel in the early boot.&lt;/p&gt;
8148 </description>
8149 </item>
8150
8151 <item>
8152 <title>Taking over sysvinit development</title>
8153 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8154 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8155 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8156 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8157 the existing sysvinit upstream developer, I decided a few weeks ago to
8158 take over the package and become the new upstream. The number of
8159 patches to track for the Debian package was becoming a burden, and the
8160 lack of synchronization between the distribution made it hard to keep
8161 the package up to date.&lt;/p&gt;
8162
8163 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8164 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8165 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8166 and Fedora), based on the patches currently in use in these
8167 distributions. We Debian maintainers plan to move to this tarball as
8168 the new upstream as soon as we find time to do the merge. Since the
8169 new tarball was created, we agreed with Werner at SuSe to make a new
8170 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8171 development there. The project is registered and currently waiting
8172 for approval by the Savannah administrators, and as soon as it is
8173 approved, we will import the old versions from svn and continue
8174 working on the future release.&lt;/p&gt;
8175
8176 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8177 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8178 </description>
8179 </item>
8180
8181 <item>
8182 <title>Debian boots quicker and quicker</title>
8183 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8185 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8186 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8187 people involved in the boot system on Debian and Ubuntu, to see if we
8188 could find more ways to speed up the boot system. This was an Ubuntu
8189 funded
8190 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8191 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8192 of boot systems, and ways to handle the increasing number of boot
8193 issues introduced by the Linux kernel becoming more and more
8194 asynchronous and event base. The Ubuntu approach using udev and
8195 upstart might be a good way forward. Time will show.&lt;/p&gt;
8196
8197 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8198 process in Debian. All of these should be applied to get a quick
8199 boot:&lt;/p&gt;
8200
8201 &lt;ul&gt;
8202
8203 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8204
8205 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8206 clock is in UTC.&lt;/li&gt;
8207
8208 &lt;li&gt;Install and activate the insserv package to enable
8209 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8210 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8211
8212 &lt;/ul&gt;
8213
8214 These points are based on the Google summer of code work done by
8215 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8216 Villegas&lt;/a&gt;.
8217
8218 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8219 unstable yesterday. When we tested it, we were able to cut 6 seconds
8220 from the boot sequence. It depend on very correct dependency
8221 declaration in all init.d scripts, so I expect us to find edge cases
8222 where the dependences in some scripts are slightly wrong when we start
8223 using this.&lt;/p&gt;
8224
8225 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8226 introduced by Raphael Geissert today, one that could affect the
8227 startup speed as well. Instead of starting some scripts concurrently
8228 from rcS.d/ and another set of scripts from rc2.d/, it would be
8229 possible to run a of them in the same process. A quick way to test
8230 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8231 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8232 </description>
8233 </item>
8234
8235 <item>
8236 <title>BSAs påstander om piratkopiering møter motstand</title>
8237 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8238 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8239 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8240 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8241 programvareselskapene som Microsoft og Apple, publisert en rapport der
8242 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8243 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8244 dager siden kom
8245 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8246 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8247 dagene. Et spesielt interessant kommentar fra Sverige,
8248 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8249 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8250
8251 &lt;blockquote&gt;
8252 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8253 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8254 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8255 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8256 &lt;/blockquote&gt;
8257
8258 &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
8259 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8260 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8261 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8262 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8263
8264 &lt;p&gt;Fant lenkene via &lt;a
8265 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8266 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8267 </description>
8268 </item>
8269
8270 <item>
8271 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8272 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8273 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8274 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8275 <description>&lt;p&gt;Kom over
8276 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8277 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8278 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8279 jobber til daglig. En rask opptelling forteller meg at vi har 490
8280 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8281 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8282 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8283 </description>
8284 </item>
8285
8286 <item>
8287 <title>Kryptert harddisk - naturligvis</title>
8288 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8289 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8290 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8291 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8292 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8293 når en tar tap av arbeidstid, fortrolige dokumenter,
8294 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8295 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8296 til at jeg har kryptert harddisken på både kontormaskinen og min
8297 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8298 komme på avveie, den første informasjon relatert til jobben min ved
8299 Universitetet i Oslo, og den andre relatert til blant annet
8300 foreningsarbeide. Kryptering av diskene gjør at det er lite
8301 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8302 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8303 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8304 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8305 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8306 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8307 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8308 det er gjort slik jeg gjør det er minimale, og gevinstene er
8309 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8310 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8311
8312 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8313 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8314 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8315 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8316 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8317 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8318 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8319 betydelige.&lt;/p&gt;
8320 </description>
8321 </item>
8322
8323 <item>
8324 <title>Two projects that have improved the quality of free software a lot</title>
8325 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8327 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8328 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8329 quality of free software, and I wanted to mention both in case someone
8330 do not yet know them.&lt;/p&gt;
8331
8332 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8333 tool to detect and expose errors in the memory handling of programs.
8334 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8335 and it will report any problems on stdout. It is even better if the
8336 program include debug information. With debug information, it is able
8337 to report the source file name and line number where the problem
8338 occurs. It can report things like &#39;reading past memory block in file
8339 X line N, the memory block was allocated in file Y, line M&#39;, and
8340 &#39;using uninitialised value in control logic&#39;. This tool has made it
8341 trivial to investigate reproducible crash bugs in programs, and have
8342 reduced the number of this kind of bugs in free software a lot.
8343
8344 &lt;p&gt;The second one is
8345 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8346 a source code checker. It is able to process the source of a program
8347 and find problems in the logic without running the program. It
8348 started out as the Stanford Checker and became well known when it was
8349 used to find bugs in the Linux kernel. It is now a commercial tool
8350 and the company behind it is running
8351 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8352 free software community, where a lot of free software projects get
8353 their source checked for free. Several thousand defects have been
8354 found and fixed so far. It can find errors like &#39;lock L taken in file
8355 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8356 Y lines O to P can never be executed&#39;. The projects included in the
8357 community service project have managed to get rid of a lot of
8358 reliability problems thanks to Coverity.&lt;/p&gt;
8359
8360 &lt;p&gt;I believe tools like this, that are able to automatically find
8361 errors in the source, are vital to improve the quality of software and
8362 make sure we can get rid of the crashing and failing software we are
8363 surrounded by today.&lt;/p&gt;
8364 </description>
8365 </item>
8366
8367 <item>
8368 <title>No patch is not better than a useless patch</title>
8369 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8370 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8371 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8372 <description>&lt;p&gt;Julien Blache
8373 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8374 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8375 patch allow one to discuss a concrete and proposed solution, and also
8376 prove that the issue at hand is important enough for someone to spent
8377 time on fixing it. No patch do not provide any of these positive
8378 properties.&lt;/p&gt;
8379 </description>
8380 </item>
8381
8382 <item>
8383 <title>Standardize on protocols and formats, not vendors and applications</title>
8384 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8386 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8387 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8388 very good one to form a long lived computer infrastructure. It is the
8389 simple one, lost by many in todays computer industry: Standardize on
8390 open network protocols and open exchange/storage formats, not applications.
8391 Applications come and go, while protocols and files tend to stay, and
8392 thus one want to make it easy to change application and vendor, while
8393 avoiding conversion costs and locking users to a specific platform or
8394 application.&lt;/p&gt;
8395
8396 &lt;p&gt;This approach make it possible to replace the client applications
8397 independently of the server applications. One can even allow users to
8398 use several different applications as long as they handle the selected
8399 protocol and format. In the normal case, only one client application
8400 is recommended and users only get help if they choose to use this
8401 application, but those that want to deviate from the easy path are not
8402 blocked from doing so.&lt;/p&gt;
8403
8404 &lt;p&gt;It also allow us to replace the server side without forcing the
8405 users to replace their applications, and thus allow us to select the
8406 best server implementation at any moment, when scale and resouce
8407 requirements change.&lt;/p&gt;
8408
8409 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8410 open formats, but I would never recommend standardizing on a single
8411 application that do not use open network protocol or open formats.&lt;/p&gt;
8412 </description>
8413 </item>
8414
8415 <item>
8416 <title>Returning from Skolelinux developer gathering</title>
8417 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8418 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8419 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8420 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8421 Edu/Skolelinux development gathering. I got a bit done tuning the
8422 desktop, and looked into the dynamic service location protocol
8423 implementation avahi. It look like it could be useful for us. Almost
8424 30 people participated, and I believe it was a great environment to
8425 get to know the Skolelinux system. Walter Bender, involved in the
8426 development of the Sugar educational platform, presented his stuff and
8427 also helped me improve my OLPC installation. He also showed me that
8428 his Turtle Art application can be used in standalone mode, and we
8429 agreed that I would help getting it packaged for Debian. As a
8430 standalone application it would be great for Debian Edu. We also
8431 tried to get the video conferencing working with two OLPCs, but that
8432 proved to be too hard for us. The application seem to need more work
8433 before it is ready for me. I look forward to getting home and relax
8434 now. :)&lt;/p&gt;
8435 </description>
8436 </item>
8437
8438 <item>
8439 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8440 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8441 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8442 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8443 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8444 optimal. There is RFC 2307 documenting one way to store NIS maps in
8445 LDAP, and a modified version of this normally called RFC 2307bis, with
8446 some modifications to be compatible with Active Directory. The RFC
8447 specification handle the content of a lot of system databases, but do
8448 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8449
8450 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8451 we would like to store information about users, SMB clients/hosts,
8452 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8453 and LTSP configuration in LDAP. These objects have a lot in common,
8454 but with the current LDAP schemas it is not possible to have one
8455 object per entity. For example, one need to have at least three LDAP
8456 objects for a given computer, one with the SMB related stuff, one with
8457 DNS information and another with DHCP information. The schemas
8458 provided for DNS and DHCP are impossible to combine into one LDAP
8459 object. In addition, it is impossible to implement quick queries for
8460 netgroup membership, because of the way NIS triples are implemented.
8461 It just do not scale. I believe it is time for a few RFC
8462 specifications to cleam up this mess.&lt;/p&gt;
8463
8464 &lt;p&gt;I would like to have one LDAP object representing each computer in
8465 the network, and this object can then keep the SMB (ie host key), DHCP
8466 (mac address/name) and DNS (name/IP address) settings in one place.
8467 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8468
8469 &lt;p&gt;I would also like to have a quick way to map from a user or
8470 computer and to the net group this user or computer is a member.&lt;/p&gt;
8471
8472 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8473 in this regard, and the unix side need to catch up. Time to start a
8474 new IETF work group?&lt;/p&gt;
8475 </description>
8476 </item>
8477
8478 <item>
8479 <title>Endelig er Debian Lenny gitt ut</title>
8480 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8481 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8482 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8483 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8484 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8485 Et langt steg videre for Debian-prosjektet, og en rekke nye
8486 programpakker blir nå tilgjengelig for de av oss som bruker den
8487 stabile utgaven av Debian. Neste steg er nå å få
8488 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8489 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8490 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8491 slippes løs på skolene. Takk til alle debian-utviklerne som har
8492 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8493 bootsekvens tilgjengelig i stabil utgave, vha pakken
8494 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8495 </description>
8496 </item>
8497
8498 <item>
8499 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8500 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8501 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8502 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8503 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8504 Oslo. Most of Saturday was used for the general assemly for the
8505 member organization, but the rest of the weekend I used to tune the
8506 LTSP installation. LTSP now work out of the box on the 10-network.
8507 Acer Aspire One proved to be a very nice thin client, with both
8508 screen, mouse and keybard in a small box. Was working on getting the
8509 diskless workstation setup configured out of the box, but did not
8510 finish it before the weekend was up.&lt;/p&gt;
8511
8512 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8513 the Brazilian group, so that will have to wait for the next
8514 development gathering. Would love to have the Debian Edu installer
8515 automatically detect and configure a multiseat setup when it find one
8516 of these cards.&lt;/p&gt;
8517 </description>
8518 </item>
8519
8520 <item>
8521 <title>The sorry state of multimedia browser plugins in Debian</title>
8522 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8524 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8525 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8526 plugins available in Debian Lenny, to see which one we should use by
8527 default in Debian Edu. We need an embedded video playing plugin with
8528 control buttons to pause or stop the video, and capable of streaming
8529 all the multimedia content available on the web. The test results and
8530 notes are available on
8531 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8532 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8533 fill this need. My personal video player favorite, VLC, has a really
8534 bad plugin which fail on a lot of the test pages. A lot of the MIME
8535 types I would expect to work with any free software player (like
8536 video/ogg), just do not work. And simple formats like the
8537 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8538 totem and vlc plugins. I hope the situation will improve soon. No
8539 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8540
8541 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8542 be the only one fitting our needs. :/&lt;/p&gt;
8543 </description>
8544 </item>
8545
8546 </channel>
8547 </rss>