]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
d15423eb58a201fa8c793d71c8e810175e0b39e3
[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>Making battery measurements a little easier in Debian</title>
11 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
13 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
14 <description>&lt;p&gt;Back in September, I blogged about
15 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
16 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
17 how it showed the decay and death of this battery (now replaced). I
18 created a simple deb package to handle the collection and graphing,
19 but did not want to upload it to Debian as there were already
20 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
21 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
22 a point of uploading a competing package when battery-stats could be
23 fixed instead. I reported a few bugs about its non-function, and
24 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
25
26 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
27 hands. The end result is that I am now the new upstream developer of
28 battery stats (&lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;available from github&lt;/a&gt;) and part of the team maintaining
29 battery-stats in Debian, and the package in Debian unstable is finally
30 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
31 information provided by the Linux kernel. If you install the
32 battery-stats package from unstable now, you will be able to get a
33 graph of the current battery fill level, to get some idea about the
34 status of the battery. The source package build and work just fine in
35 Debian testing and stable (and probably oldstable too, but I have not
36 tested). The default graph you get for that system look like this:&lt;/p&gt;
37
38 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png&quot; width=&quot;70%&quot; align=&quot;center&quot;&gt;&lt;/p&gt;
39
40 &lt;p&gt;My plans for the future is to merge my old scripts into the
41 battery-stats package, as my old scripts collected a lot more details
42 about the battery. The scripts are merged into the upstream
43 battery-stats git repository already, but I am not convinced they work
44 yet, as I changed a lot of paths along the way. Will have to test a
45 bit more before I make a new release.&lt;/p&gt;
46
47 &lt;p&gt;I will also consider changing the file format slightly, as I
48 suspect the way I combine several values into one field might make it
49 impossible to know the type of the value when using it for processing
50 and graphing.&lt;/p&gt;
51
52 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
53 battery, check out the battery-stats package in
54 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
55 on
56 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
57 I would love some help to improve the system further.&lt;/p&gt;
58 </description>
59 </item>
60
61 <item>
62 <title>Creating, updating and checking debian/copyright semi-automatically</title>
63 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
64 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
65 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
66 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
67 details. And one of the details is the content of the
68 debian/copyright file, which should list all relevant licenses used by
69 the code in the package in question, preferably in
70 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
71 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
72
73 &lt;p&gt;For large packages with lots of contributors it is hard to write
74 and update this file manually, and if you get some detail wrong, the
75 package is normally rejected by the ftpmasters. So getting it right
76 the first time around get the package into Debian faster, and save
77 both you and the ftpmasters some work.. Today, while trying to figure
78 out what was wrong with
79 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
80 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
81 figuring out the options for doing this job automatically, or at least
82 semi-automatically.&lt;/p&gt;
83
84 &lt;p&gt;Lucikly, there are at least two tools available for generating the
85 file based on the code in the source package,
86 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
87 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
88 not sure which one of them came first, but both seem to be able to
89 create a sensible draft file. As far as I can tell, none of them can
90 be trusted to get the result just right, so the content need to be
91 polished a bit before the file is OK to upload. I found the debmake
92 option in
93 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
94 blog posts from 2014&lt;/a&gt;.
95
96 &lt;p&gt;To generate using debmake, use the -cc option:
97
98 &lt;p&gt;&lt;pre&gt;
99 debmake -cc &gt; debian/copyright
100 &lt;/pre&gt;&lt;/p&gt;
101
102 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
103 this might not be the best option.&lt;/p&gt;
104
105 &lt;p&gt;The cme option is based on a config parsing library, and I found
106 this approach in
107 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
108 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
109 dpkg-copyright&#39; option:
110
111 &lt;p&gt;&lt;pre&gt;
112 cme update dpkg-copyright
113 &lt;/pre&gt;&lt;/p&gt;
114
115 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
116 handle UTF-8 names better than debmake.&lt;/p&gt;
117
118 &lt;p&gt;When the copyright file is created, I would also like some help to
119 check if the file is correct. For this I found two good options,
120 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
121 to focus on license types and file matching, and is able to detect
122 ineffective blocks in the copyright file. The latter reports missing
123 copyright holders and years, but was confused by inconsistent license
124 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
125 fix all issues reported by them before uploading. But I do not know
126 if the tools and the ftpmasters agree on what is important to fix in a
127 copyright file, so the package might still be rejected.&lt;/p&gt;
128
129 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
130 will read through the source and try to find all copyright statements.
131 It is not comparing the result to the content of debian/copyright, but
132 can be useful when verifying the content of the copyright file.&lt;/p&gt;
133
134 &lt;p&gt;Are you aware of better tools in Debian to create and update
135 debian/copyright file. Please let me know, or blog about it on
136 planet.debian.org.&lt;/p&gt;
137
138 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
139 activities, please send Bitcoin donations to my address
140 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
141
142 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
143 on how to use licensecheck and cdbs to create a draft copyright file
144
145 &lt;p&gt;&lt;pre&gt;
146 licensecheck --copyright -r `find * -type f` | \
147 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
148 &lt;/pre&gt;&lt;/p&gt;
149
150 &lt;p&gt;He mentioned that he normally check the generated file into the
151 version control system to make it easier to discover license and
152 copyright changes in the upstream source. I will try to do the same
153 with my packages in the future.&lt;/p&gt;
154
155 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
156 against using -quiet for new users, so I removed it from the proposed
157 command line.&lt;/p&gt;
158 </description>
159 </item>
160
161 <item>
162 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
163 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
164 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
165 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
166 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
167 is taking shape in Debian, and one provided feature is a very
168 convenient way to tell you which package to install to make a given
169 firmware file available when the kernel is looking for it. This can
170 be done using apt-file too, but that is for someone else to blog
171 about. :)&lt;/p&gt;
172
173 &lt;p&gt;Here is a small recipe to find the package with a given firmware
174 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
175 picked from the set of firmware announced using appstream in Debian
176 unstable. In general you would be looking for the firmware requested
177 by the kernel during kernel module loading. To find the package
178 providing the example file, do like this:&lt;/p&gt;
179
180 &lt;blockquote&gt;&lt;pre&gt;
181 % apt install appstream
182 [...]
183 % apt update
184 [...]
185 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
186 awk &#39;/Package:/ {print $2}&#39;
187 firmware-qlogic
188 %
189 &lt;/pre&gt;&lt;/blockquote&gt;
190
191 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
192 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
193 a way appstream can use.&lt;/p&gt;
194
195 &lt;p&gt;This same approach can be used to find any package supporting a
196 given MIME type. This is very useful when you get a file you do not
197 know how to handle. First find the mime type using &lt;tt&gt;file
198 --mime-type&lt;/tt&gt;, and next look up the package providing support for
199 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
200 and you can find all packages handling this type like this:&lt;/p&gt;
201
202 &lt;blockquote&gt;&lt;pre&gt;
203 % apt install appstream
204 [...]
205 % apt update
206 [...]
207 % appstreamcli what-provides mimetype image/svg+xml | \
208 awk &#39;/Package:/ {print $2}&#39;
209 bkchem
210 phototonic
211 inkscape
212 shutter
213 tetzle
214 geeqie
215 xia
216 pinta
217 gthumb
218 karbon
219 comix
220 mirage
221 viewnior
222 postr
223 ristretto
224 kolourpaint4
225 eog
226 eom
227 gimagereader
228 midori
229 %
230 &lt;/pre&gt;&lt;/blockquote&gt;
231
232 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
233 packages providing appstream metadata.&lt;/p&gt;
234 </description>
235 </item>
236
237 <item>
238 <title>Creepy, visualise geotagged social media information - nice free software</title>
239 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
241 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
242 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
243 with the computerised radio beacon known as a mobile phone their
244 position is tracked by the phone company and often stored for a long
245 time (like every time a SMS is received or sent). And if their
246 computerised radio beacon is capable of running programs (often called
247 mobile apps) downloaded from the Internet, these programs are often
248 also capable of tracking their location (if the app requested access
249 during installation). And when these programs send out information to
250 central collection points, the location is often included, unless
251 extra care is taken to not send the location. The provided
252 information is used by several entities, for good and bad (what is
253 good and bad, depend on your point of view). What is certain, is that
254 the private sphere and the right to free movement is challenged and
255 perhaps even eradicated for those announcing their location this way,
256 when they share their whereabouts with private and public
257 entities.&lt;/p&gt;
258
259 &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;
260
261 &lt;p&gt;The phone company logs provide a register of locations to check out
262 when one want to figure out what the tracked person was doing. It is
263 unavailable for most of us, but provided to selected government
264 officials, company staff, those illegally buying information from
265 unfaithful servants and crackers stealing the information. But the
266 public information can be collected and analysed, and a free software
267 tool to do so is called
268 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
269 discovered it when I read
270 &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
271 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
272 November 2014, and decided to check if it was available in Debian.
273 The python program was in Debian, but
274 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
275 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
276 uploaded a new version which did not work quite right, but did not
277 have time to fix it then. This Christmas I decided to finally try to
278 get Creepy operational in Debian. Now a fixed version is available in
279 Debian unstable and testing, and almost all Debian specific patches
280 are now included
281 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
282
283 &lt;p&gt;The Creepy program visualises geolocation information fetched from
284 Twitter, Instagram, Flickr and Google+, and allow one to get a
285 complete picture of every social media message posted recently in a
286 given area, or track the movement of a given individual across all
287 these services. Earlier it was possible to use the search API of at
288 least some of these services without identifying oneself, but these
289 days it is impossible. This mean that to use Creepy, you need to
290 configure it to log in as yourself on these services, and provide
291 information to them about your search interests. This should be taken
292 into account when using Creepy, as it will also share information
293 about yourself with the services.&lt;/p&gt;
294
295 &lt;p&gt;The picture above show the twitter messages sent from (or at least
296 geotagged with a position from) the city centre of Oslo, the capital
297 of Norway. One useful way to use Creepy is to first look at
298 information tagged with an area of interest, and next look at all the
299 information provided by one or more individuals who was in the area.
300 I tested it by checking out which celebrity provide their location in
301 twitter messages by checkout out who sent twitter messages near a
302 Norwegian TV station, and next could track their position over time,
303 making it possible to locate their home and work place, among other
304 things. A similar technique have been
305 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
306 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
307 tool to discover lying governments, and a useful tool to help people
308 understand the value of the private information they provide to the
309 public.&lt;/p&gt;
310
311 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
312 it depend on several python modules currently missing in Jessie (at
313 least python-instagram, python-flickrapi and
314 python-requests-toolbelt).&lt;/p&gt;
315
316 &lt;p&gt;(I have uploaded
317 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
318 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
319 Creepy program in Debian.)&lt;/p&gt;
320 </description>
321 </item>
322
323 <item>
324 <title>Always download Debian packages using Tor - the simple recipe</title>
325 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
327 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
328 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
329 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
330 that those listening on the Internet lines would have good reason to
331 believe a computer have a given security hole&lt;/a&gt; if it download a
332 security fix from a Debian mirror. This is a good reason to always
333 use encrypted connections to the Debian mirror, to make sure those
334 listening do not know which IP address to attack. In August, Richard
335 Hartmann observed that encryption was not enough, when it was possible
336 to interfere download size to security patches or the fact that
337 download took place shortly after a security fix was released, and
338 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
339 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
340 was not the first to propose this, as the
341 &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;
342 package by Tim Retout already existed to make it easy to convince apt
343 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
344 aware of that package when I read the blog post from Richard.&lt;/p&gt;
345
346 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
347 sysadmins, and he set up a Tor hidden service on one of the central
348 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
349 it possible to download packages directly between two tor nodes,
350 making sure the network traffic always were encrypted.&lt;/p&gt;
351
352 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
353 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
354 urls with tor+http and tor+https, and using the hidden service instead
355 of the official Debian mirror site. I recommend installing
356 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
357 done in /etc/.&lt;/p&gt;
358
359 &lt;blockquote&gt;&lt;pre&gt;
360 apt install apt-transport-tor
361 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
362 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
363 &lt;/pre&gt;&lt;/blockquote&gt;
364
365 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
366 the sed commands for these too. The sed command is assuming your are
367 using the ftp.debian.org Debian mirror. Adjust the command (or just
368 edit the file manually) to match your mirror.&lt;/p&gt;
369
370 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
371 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
372 system, and do not work with these tor+http URLs. For
373 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
374 which need a recent apt version currently only in unstable. So if you
375 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
376
377 &lt;p&gt;Another advantage from this change is that your machine will start
378 using Tor regularly and at fairly random intervals (every time you
379 update the package lists or upgrade or install a new package), thus
380 masking other Tor traffic done from the same machine. Using Tor will
381 become normal for the machine in question.&lt;/p&gt;
382
383 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
384 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
385 enabled. It would be great if it was the default on any Debian
386 system.&lt;/p&gt;
387 </description>
388 </item>
389
390 <item>
391 <title>OpenALPR, find car license plates in video streams - nice free software</title>
392 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
393 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
394 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
395 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
396 call the car license plate numbers in those days. I would write the
397 numbers down in my little book and compare notes with the other kids
398 to see how many region codes we had seen and if we had seen some
399 exotic or special region codes and numbers. It was a fun game to pass
400 time, as we kids have plenty of it.&lt;/p&gt;
401
402 &lt;p&gt;A few days I came across
403 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
404 project&lt;/a&gt;, a free software project to automatically discover and
405 report license plates in images and video streams, and provide the
406 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
407 such system for a while now, because I believe it is a bad idea that the
408 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
409 number plate recognition&lt;/a&gt; tool only is available in the hands of
410 the powerful, and want it to be available also for the powerless to
411 even the score when it comes to surveillance and sousveillance. I
412 discovered the developer
413 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
414 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
415 help him get it into shape to get the package uploaded into the Debian
416 archive.&lt;/p&gt;
417
418 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
419 it into Debian, where it currently
420 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
421 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
422
423 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
424 for the common folks, ie those not running a large government
425 surveillance system? Well, I plan to put it in a computer on my bike
426 and in my car, tracking the cars nearby and allowing me to be notified
427 when number plates on my watch list are discovered. Another use case
428 was suggested by a friend of mine, who wanted to set it up at his home
429 to open the car port automatically when it discovered the plate on his
430 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
431 capable of placing his license plate number of a piece of cardboard to
432 open his car port, men replied that it was always unlocked anyway. I
433 guess for such use case it make sense. I am sure there are other use
434 cases too, for those with imagination and a vision.&lt;/p&gt;
435
436 &lt;p&gt;If you want to build your own version of the Debian package, check
437 out the upstream git source and symlink ./distros/debian to ./debian/
438 before running &quot;debuild&quot; to build the source. Or wait a bit until the
439 package show up in unstable.&lt;/p&gt;
440 </description>
441 </item>
442
443 <item>
444 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
445 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
446 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
447 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
448 <description>&lt;p&gt;Around three years ago, I created
449 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
450 system&lt;/a&gt; to get a more practical solution in Debian for handing
451 hardware related packages. A GUI system in the isenkram package will
452 present a pop-up dialog when some hardware dongle supported by
453 relevant packages in Debian is inserted into the machine. The same
454 lookup mechanism to detect packages is available as command line
455 tools in the isenkram-cli package. In addition to mapping hardware,
456 it will also map kernel firmware files to packages and make it easy to
457 install needed firmware packages automatically. The key for this
458 system to work is a good way to map hardware to packages, in other
459 words, allow packages to announce what hardware they will work
460 with.&lt;/p&gt;
461
462 &lt;p&gt;I started by providing data files in the isenkram source, and
463 adding code to download the latest version of these data files at run
464 time, to ensure every user had the most up to date mapping available.
465 I also added support for storing the mapping in the Packages file in
466 the apt repositories, but did not push this approach because while I
467 was trying to figure out how to best store hardware/package mappings,
468 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
469 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
470 add the hardware mapping into that data set to be able to use
471 appstream as a data source, and this was accepted at least for the
472 Debian version of appstream.&lt;/p&gt;
473
474 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
475 and today I uploaded a new version 0.20 of isenkram adding support for
476 appstream as a data source for mapping hardware to packages. The only
477 package so far using appstream to announce its hardware support is my
478 pymissile package. I got help from Matthias Klumpp with figuring out
479 how do add the required
480 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
481 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
482 this content:&lt;/p&gt;
483
484 &lt;blockquote&gt;&lt;pre&gt;
485 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
486 &amp;lt;component&amp;gt;
487 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
488 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
489 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
490 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
491 &amp;lt;description&amp;gt;
492 &amp;lt;p&amp;gt;
493 Pymissile provides a curses interface to control an original
494 Marks and Spencer / Striker USB Missile Launcher, as well as a
495 motion control script to allow a webcamera to control the
496 launcher.
497 &amp;lt;/p&amp;gt;
498 &amp;lt;/description&amp;gt;
499 &amp;lt;provides&amp;gt;
500 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
501 &amp;lt;/provides&amp;gt;
502 &amp;lt;/component&amp;gt;
503 &lt;/pre&gt;&lt;/blockquote&gt;
504
505 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
506 which is a glob style match rule for hardware specific strings
507 (modalias strings) provided by the Linux kernel. In this case, it
508 will map to all USB devices with vendor code 1130 and product code
509 0202.&lt;/p&gt;
510
511 &lt;p&gt;Note, it is important that the license of all the metadata files
512 are compatible to have permissions to aggregate them into archive wide
513 appstream files. Matthias suggested to use MIT or BSD licenses for
514 these files. A challenge is figuring out a good id for the data, as
515 it is supposed to be globally unique and shared across distributions
516 (in other words, best to coordinate with upstream what to use). But
517 it can be changed later or, so we went with the package name as
518 upstream for this project is dormant.&lt;/p&gt;
519
520 &lt;p&gt;To get the metadata file installed in the correct location for the
521 mirror update scripts to pick it up and include its content the
522 appstream data source, the file must be installed in the binary
523 package under /usr/share/appdata/. I did this by adding the following
524 line to debian/pymissile.install:&lt;/p&gt;
525
526 &lt;blockquote&gt;&lt;pre&gt;
527 debian/pymissile.metainfo.xml usr/share/appdata
528 &lt;/pre&gt;&lt;/blockquote&gt;
529
530 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
531 all packages useful on the current computer automatically, and the GUI
532 pop-up handler will propose to install the package not already
533 installed if a hardware dongle is inserted into the machine in
534 question.&lt;/p&gt;
535
536 &lt;p&gt;Details of the modalias field in appstream is available from the
537 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
538
539 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
540 try running this command on the command line:&lt;/p&gt;
541
542 &lt;blockquote&gt;&lt;pre&gt;
543 cat $(find /sys/devices/|grep modalias)
544 &lt;/pre&gt;&lt;/blockquote&gt;
545
546 &lt;p&gt;To learn more about the isenkram system, please check out
547 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
548 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
549 </description>
550 </item>
551
552 <item>
553 <title>The GNU General Public License is not magic pixie dust</title>
554 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
555 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
556 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
557 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
558 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
559 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
560 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
561 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
562
563 &lt;blockquote&gt;
564
565 &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;
566
567 &lt;blockquote&gt;
568 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
569
570 The first step is to choose a
571 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
572 code.&lt;br/&gt;
573
574 The next step is, when someone fails to follow that copyleft license,
575 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
576
577 and its a simple fact of our modern society that such type of
578 work&lt;br/&gt;
579
580 is incredibly expensive to do and incredibly difficult to do.
581 &lt;/blockquote&gt;
582
583 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
584 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
585 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
586 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
587
588 &lt;p&gt;As the Debian Website
589 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
590 &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;
591 imply, public domain and permissively licensed software can lead to
592 the production of more proprietary software as people discover useful
593 software, extend it and or incorporate it into their hardware or
594 software products. Copyleft licenses such as the GNU GPL were created
595 to close off this avenue to the production of proprietary software but
596 such licenses are not enough. With the ongoing adoption of Free
597 Software by individuals and groups, inevitably the community&#39;s
598 expectations of license compliance are violated, usually out of
599 ignorance of the way Free Software works, but not always. As Karen
600 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
601 Freedom&quot;&gt;FaiF&lt;/a&gt;
602 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
603 copyleft is nothing if no-one is willing and able to stand up in court
604 to protect it. The reality of today&#39;s world is that legal
605 representation is expensive, difficult and time consuming. With
606 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
607 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
608 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
609 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
610 of the Linux project, Debian and other groups against GPL violations.
611 In March the SFC supported a
612 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
613 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
614 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
615 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
616 kernel. Since then two of their sponsors pulled corporate funding and
617 conferences
618 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
619 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
620 less on corporate funding and more on the broad community of
621 individuals who support Free Software and copyleft. So the SFC has
622 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
623 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
624 a community of folks who stand up for copyleft and the GPL by
625 supporting their work on promoting and supporting copyleft and Free
626 Software.&lt;/p&gt;
627
628 &lt;p&gt;If you support Free Software,
629 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
630 what the SFC do, agree with their
631 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
632 principles&lt;/a&gt;, are happy about their
633 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
634 work on a project that is an SFC
635 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
636 just want to stand up for copyleft, please join
637 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
638 Allan Webber&lt;/a&gt;,
639 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
640 Smith&lt;/a&gt;,
641 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
642 Bacon&lt;/a&gt;, myself and
643 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
644 becoming a
645 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
646 next week your donation will be
647 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
648 by an anonymous donor. Please also consider asking your employer to
649 match your donation or become a sponsor of SFC. Don&#39;t forget to
650 spread the word about your support for SFC via email, your blog and or
651 social media accounts.&lt;/p&gt;
652
653 &lt;/blockquote&gt;
654
655 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
656 of Software Freedom Conservancy myself. Perhaps you should be a
657 supporter too?&lt;/p&gt;
658 </description>
659 </item>
660
661 <item>
662 <title>PGP key transition statement for key EE4E02F9</title>
663 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
664 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
665 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
666 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
667 set it up properly. I wanted to generate it offline and have it
668 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
669 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
670 time to sit down with an offline machine almost took forever. But
671 finally I&#39;ve been able to complete the process, and have now moved
672 from my old GPG key to a new GPG key. See
673 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
674 full transition statement, signed with both my old and new key&lt;/a&gt; for
675 the details. This is my new key:&lt;/p&gt;
676
677 &lt;pre&gt;
678 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]
679 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
680 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
681 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
682 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
683 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
684 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
685 &lt;/pre&gt;
686
687 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
688 my old key.&lt;/p&gt;
689
690 &lt;p&gt;If you signed my old key
691 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
692 I&#39;d very much appreciate a signature on my new key, details and
693 instructions in the transition statement. I m happy to reciprocate if
694 you have a similarly signed transition statement to present.&lt;/p&gt;
695 </description>
696 </item>
697
698 <item>
699 <title>The life and death of a laptop battery</title>
700 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
701 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
702 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
703 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
704 But this do not last. The last few laptops gave me a feeling that
705 within a year, the life time is just a fraction of what it used to be,
706 and it slowly become painful to use the laptop without power connected
707 all the time. Because of this, when I got a new Thinkpad X230 laptop
708 about two years ago, I decided to monitor its battery state to have
709 more hard facts when the battery started to fail.&lt;/p&gt;
710
711 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
712
713 &lt;p&gt;First I tried to find a sensible Debian package to record the
714 battery status, assuming that this must be a problem already handled
715 by someone else. I found
716 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
717 which collects statistics from the battery, but it was completely
718 broken. I sent a few suggestions to the maintainer, but decided to
719 write my own collector as a shell script while I waited for feedback
720 from him. Via
721 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
722 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
723 discovered
724 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
725 available in Debian.&lt;/p&gt;
726
727 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
728 battery stats ever since. Now my
729 /var/log/hjemmenett-battery-status.log file contain around 115,000
730 measurements, from the time the battery was working great until now,
731 when it is unable to charge above 7% of original capacity. My
732 collector shell script is quite simple and look like this:&lt;/p&gt;
733
734 &lt;pre&gt;
735 #!/bin/sh
736 # Inspired by
737 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
738 # See also
739 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
740 logfile=/var/log/hjemmenett-battery-status.log
741
742 files=&quot;manufacturer model_name technology serial_number \
743 energy_full energy_full_design energy_now cycle_count status&quot;
744
745 if [ ! -e &quot;$logfile&quot; ] ; then
746 (
747 printf &quot;timestamp,&quot;
748 for f in $files; do
749 printf &quot;%s,&quot; $f
750 done
751 echo
752 ) &gt; &quot;$logfile&quot;
753 fi
754
755 log_battery() {
756 # Print complete message in one echo call, to avoid race condition
757 # when several log processes run in parallel.
758 msg=$(printf &quot;%s,&quot; $(date +%s); \
759 for f in $files; do \
760 printf &quot;%s,&quot; $(cat $f); \
761 done)
762 echo &quot;$msg&quot;
763 }
764
765 cd /sys/class/power_supply
766
767 for bat in BAT*; do
768 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
769 done
770 &lt;/pre&gt;
771
772 &lt;p&gt;The script is called when the power management system detect a
773 change in the power status (power plug in or out), and when going into
774 and out of hibernation and suspend. In addition, it collect a value
775 every 10 minutes. This make it possible for me know when the battery
776 is discharging, charging and how the maximum charge change over time.
777 The code for the Debian package
778 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
779 available on github&lt;/a&gt;.&lt;/p&gt;
780
781 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
782
783 &lt;pre&gt;
784 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
785 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
786 [...]
787 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
788 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
789 &lt;/pre&gt;
790
791 &lt;p&gt;I wrote a small script to create a graph of the charge development
792 over time. This graph depicted above show the slow death of my laptop
793 battery.&lt;/p&gt;
794
795 &lt;p&gt;But why is this happening? Why are my laptop batteries always
796 dying in a year or two, while the batteries of space probes and
797 satellites keep working year after year. If we are to believe
798 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
799 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
800 chance, and the fix is to not charge the Lithium-ion batteries to 100%
801 all the time, but to stay below 90% of full charge most of the time.
802 I&#39;ve been told that the Tesla electric cars
803 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
804 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
805 100% when preparing for a longer trip (not that I would want a car
806 like Tesla where rights to privacy is abandoned, but that is another
807 story), which I guess is the option we should have for laptops on
808 Linux too.&lt;/p&gt;
809
810 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
811 stop charging at 80%, unless requested to charge to 100% once in
812 preparation for a longer trip? I found
813 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
814 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
815 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
816 load).&lt;/p&gt;
817
818 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
819 at the start. I also wonder why the &quot;full capacity&quot; increases some
820 times, and if it is possible to repeat the process to get the battery
821 back to design capacity. And I wonder if the discharge and charge
822 speed change over time, or if this stay the same. I did not yet try
823 to write a tool to calculate the derivative values of the battery
824 level, but suspect some interesting insights might be learned from
825 those.&lt;/p&gt;
826
827 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
828 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
829 packages instead of the tp-smapi-dkms package I had tried to use
830 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
831 and stop. I&#39;ve done so now, but expect my existing battery is toast
832 and need to be replaced. The proposal is unfortunately Thinkpad
833 specific.&lt;/p&gt;
834 </description>
835 </item>
836
837 <item>
838 <title>New laptop - some more clues and ideas based on feedback</title>
839 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
840 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
841 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
842 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
843 need for a new laptop, and provided very useful feedback. I wish to
844 thank every one of these. Several pointed me to the possibility of
845 fixing my X230, and I am already in the process of getting Lenovo to
846 do so thanks to the on site, next day support contract covering the
847 machine. But the battery is almost useless (I expect to replace it
848 with a non-official battery) and I do not expect the machine to live
849 for many more years, so it is time to plan its replacement. If I did
850 not have a support contract, it was suggested to find replacement parts
851 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
852 might present a language barrier as I do not understand French.&lt;/p&gt;
853
854 &lt;p&gt;One tip I got was to use the
855 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
856 compare laptop models. It seem to have more models available than
857 prisjakt.no. Another tip I got from someone I know have similar
858 keyboard preferences was that the HP EliteBook 840 keyboard is not
859 very good, and this matches my experience with earlier EliteBook
860 keyboards I tested. Because of this, I will not consider it any further.
861
862 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
863 newest Thinkpad X model. The keyboard reintroduces mouse buttons
864 (which is missing from the X240), and is working fairly well with
865 Debian Sid/Unstable according to
866 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
867 got on the keyboard quality are not consistent. Some say the keyboard
868 is good, others say it is ok, while others say it is not very good.
869 Those with experience from X41 and and X60 agree that the X250
870 keyboard is not as good as those trusty old laptops, and suggest I
871 keep and fix my X230 instead of upgrading, or get a used X230 to
872 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
873 activity and battery status, which is very convenient on my X230. I&#39;m
874 also told that the CPU fan is running very often, making it a bit
875 noisy. In any case, the X250 do not work out of the box with Debian
876 Stable/Jessie, one of my requirements.&lt;/p&gt;
877
878 &lt;p&gt;I have also gotten a few vendor proposals, one was
879 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
880 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
881 The latter look very attractive to me.&lt;/p&gt;
882
883 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
884 as I keep looking for a replacement.&lt;/p&gt;
885
886 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
887 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
888 different
889 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
890 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
891 </description>
892 </item>
893
894 <item>
895 <title>Time to find a new laptop, as the old one is broken after only two years</title>
896 <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>
897 <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>
898 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
899 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
900 replacement soon. The left 5 cm of the screen on my Thinkpad X230
901 started flickering yesterday, and I suspect the cause is a broken
902 cable, as changing the angle of the screen some times get rid of the
903 flickering.&lt;/p&gt;
904
905 &lt;p&gt;My requirements have not really changed since I bought it, and is
906 still as
907 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
908 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
909 good help from
910 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
911 where I could select at least a few of the requirements (mouse pin,
912 wifi, weight) and go through the rest manually. Three button mouse
913 and a good keyboard is not available as an option, and all the three
914 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
915 G2) lack three mouse buttons). It is also unclear to me how good the
916 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
917 the keyboard, even if the quality and robustness in the X series have
918 deteriorated since X41.&lt;/p&gt;
919
920 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
921 seem sensible to me? Are there better services around to search the
922 set of available laptops for features? Please send me an email if you
923 have suggestions.&lt;/p&gt;
924
925 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
926 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
927 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
928 </description>
929 </item>
930
931 <item>
932 <title>How to stay with sysvinit in Debian Jessie</title>
933 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
934 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
935 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
936 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
937 sysvinit as its boot system by default. But how can one keep using
938 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
939 courtesy of
940 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
941 Schubert&lt;/a&gt; and
942 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
943 McVittie&lt;/a&gt;.
944
945 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
946 keep sysvinit as your boot system, create a file
947 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
948 you upgrade:&lt;/p&gt;
949
950 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
951 Package: systemd-sysv
952 Pin: release o=Debian
953 Pin-Priority: -1
954 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
955
956 &lt;p&gt;This file content will tell apt and aptitude to not consider
957 installing systemd-sysv as part of any installation and upgrade
958 solution when resolving dependencies, and thus tell it to avoid
959 systemd as a default boot system. The end result should be that the
960 upgraded system keep using sysvinit.&lt;/p&gt;
961
962 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
963 get sysvinit installed by default (debootstrap used by
964 debian-installer have no option for this), but one can tell the
965 installer to switch to sysvinit before the first boot. Either by
966 using a kernel argument to the installer, or by adding a line to the
967 preseed file used. First, the kernel command line argument:
968
969 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
970 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
971 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
972
973 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
974
975 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
976 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
977 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
978
979 &lt;p&gt;One can of course also do this after the first boot by installing
980 the sysvinit-core package.&lt;/p&gt;
981
982 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
983 sysvinit boot sequence in Debian have several hardware specific bugs
984 on Linux caused by the fact that it is unpredictable when hardware
985 devices show up during boot. But on the other hand, the new default
986 boot system still have a few rough edges I hope will be fixed before
987 Jessie is released.&lt;/p&gt;
988
989 &lt;p&gt;Update 2014-11-26: Inspired by
990 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
991 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
992 line.&lt;/p&gt;
993 </description>
994 </item>
995
996 <item>
997 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
998 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
999 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
1000 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
1001 <description>&lt;p&gt;The right to communicate with your friends and family in private,
1002 without anyone snooping, is a right every citicen have in a liberal
1003 democracy. But this right is under serious attack these days.&lt;/p&gt;
1004
1005 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
1006 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1007 the whisleblower Snowden) more expensive for Internet email,
1008 is to deliver all email using SMTP via Tor. Such SMTP option would be
1009 a nice addition to the FreedomBox project if we could send email
1010 between FreedomBox machines without leaking metadata about the emails
1011 to the people peeking on the wire. I
1012 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
1013 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
1014 lot of useful feedback and suggestions. It also became obvious to me
1015 that this was not a novel idea, as the same idea was tested and
1016 documented by Johannes Berg as early as 2006, and both
1017 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
1018 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
1019 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
1020
1021 &lt;p&gt;To implement such system one need to set up a Tor hidden service
1022 providing the SMTP protocol on port 25, and use email addresses
1023 looking like username@hidden-service-name.onion. With such addresses
1024 the connections to port 25 on hidden-service-name.onion using Tor will
1025 go to the correct SMTP server. To do this, one need to configure the
1026 Tor daemon to provide the hidden service and the mail server to accept
1027 emails for this .onion domain. To learn more about Exim configuration
1028 in Debian and test the design provided by Johannes Berg in his FAQ, I
1029 set out yesterday to create a Debian package for making it trivial to
1030 set up such SMTP over Tor service based on Debian. Getting it to work
1031 were fairly easy, and
1032 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
1033 source code for the Debian package&lt;/a&gt; is available from github. I
1034 plan to move it into Debian if further testing prove this to be a
1035 useful approach.&lt;/p&gt;
1036
1037 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
1038 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
1039 get rid of exim4). Install tor, clone the git repository mentioned
1040 above, build the deb and install it on the machine. Next, run
1041 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
1042 the instructions to get the service up and running. Restart tor and
1043 exim when it is done, and test mail delivery using swaks like
1044 this:&lt;/p&gt;
1045
1046 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1047 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1048 --to fbx@dutlqrrmjhtfa3vp.onion
1049 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1050
1051 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
1052 address with your own address to test your server. :)&lt;/p&gt;
1053
1054 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
1055 easier and more automatic. Especially the tor setup need more work.
1056 Also, the package include a tor-smtp tool written in C, but its task
1057 should probably be rewritten in some script language to make the deb
1058 architecture independent. It would probably also make the code easier
1059 to review. The tor-smtp tool currently need to listen on a socket for
1060 exim to talk to it and is started using xinetd. It would be better if
1061 no daemon and no socket is needed. I suspect it is possible to get
1062 exim to run a command line tool for delivery instead of talking to a
1063 socket, and hope to figure out how in a future version of this
1064 system.&lt;/p&gt;
1065
1066 &lt;p&gt;Until I wipe my test machine, I can be reached using the
1067 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
1068 SMTorP. :)&lt;/p&gt;
1069 </description>
1070 </item>
1071
1072 <item>
1073 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
1074 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
1075 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
1076 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
1077 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
1078 alioth.debian.org, you know the web interface is fairly slow to
1079 operate. First you visit one web page, enter the moderation password
1080 and get a new page shown with a list of all the messages to moderate
1081 and various options for each email address. This take a while for
1082 every list you moderate, and you need to do it regularly to do a good
1083 job as a list moderator. But there is a quick alternative,
1084 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
1085 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
1086 to moderate in a fraction of a second. Here is a test run on two
1087 lists I recently took over:&lt;/p&gt;
1088
1089 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1090 % time listadmin xiph
1091 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1092 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1093
1094 real 0m1.709s
1095 user 0m0.232s
1096 sys 0m0.012s
1097 %
1098 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1099
1100 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
1101 there are no message in the moderation queue. Every morning I
1102 currently moderate 68 mailman lists, and it normally take around two
1103 minutes. When I took over the two pkg-xiph lists above a few days
1104 ago, there were 400 emails waiting in the moderator queue. It took me
1105 less than 15 minutes to process them all using the listadmin
1106 program.&lt;/p&gt;
1107
1108 &lt;p&gt;If you install
1109 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
1110 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
1111 with content like this, the moderation task is a breeze:&lt;/p&gt;
1112
1113 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1114 username username@example.org
1115 spamlevel 23
1116 default discard
1117 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
1118
1119 password secret
1120 adminurl https://{domain}/mailman/admindb/{list}
1121 mailman-list@lists.example.com
1122
1123 password hidden
1124 other-list@otherserver.example.org
1125 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1126
1127 &lt;p&gt;There are other options to set as well. Check the manual page to
1128 learn the details.&lt;/p&gt;
1129
1130 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
1131 the SSL certificate is self signed or not properly signed by a
1132 generally accepted signing authority, you can set a environment
1133 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
1134
1135 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1136 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
1137 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1138
1139 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
1140 can provide an argument to the listadmin script like I do in the
1141 initial screen dump (the xiph argument). Using an argument, only
1142 lists matching the argument string will be processed. This make it
1143 quick to accept messages if you notice the moderation request in your
1144 email.&lt;/p&gt;
1145
1146 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
1147 mailing lists, as I simply do not have time to spend on that if the
1148 process was any slower. The listadmin program have saved me hours of
1149 time I could spend elsewhere over the years. It truly is nice free
1150 software.&lt;/p&gt;
1151
1152 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1153 activities, please send Bitcoin donations to my address
1154 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1155
1156 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1157 configuration example. Also, I&#39;ve been told that the
1158 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1159 sure why.&lt;/p&gt;
1160 </description>
1161 </item>
1162
1163 <item>
1164 <title>Debian Jessie, PXE and automatic firmware installation</title>
1165 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1166 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1167 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1168 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1169 problem that the WiFi card require some firmware to work properly.
1170 And it has been a pain to fix this using preseeding in Debian.
1171 Normally something more is needed. But thanks to
1172 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1173 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1174 to do this using simple preseeding.&lt;/p&gt;
1175
1176 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1177 firmware for the hardware found in the machine (actually, requested by
1178 the kernel modules for the hardware). (It can also install user space
1179 programs supporting the hardware detected, but that is not the focus
1180 of this story.)&lt;/p&gt;
1181
1182 &lt;p&gt;To get this working in the default installation, two preeseding
1183 values are needed. First, the isenkram-cli package must be installed
1184 into the target chroot (aka the hard drive) before tasksel is executed
1185 in the pkgsel step of the debian-installer system. This is done by
1186 preseeding the base-installer/includes debconf value to include the
1187 isenkram-cli package. The package name is next passed to debootstrap
1188 for installation. With the isenkram-cli package in place, tasksel
1189 will automatically use the isenkram tasks to detect hardware specific
1190 packages for the machine being installed and install them, because
1191 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1192
1193 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1194 most firmware unfortunately is non-free. This is done by preseeding
1195 the apt-mirror-setup step. This is unfortunate, but for a lot of
1196 hardware it is the only option in Debian.&lt;/p&gt;
1197
1198 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1199 firmware installed automatically by the installer:&lt;/p&gt;
1200
1201 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1202 base-installer base-installer/includes string isenkram-cli
1203 apt-mirror-setup apt-setup/non-free boolean true
1204 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1205
1206 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1207 both firmware and user space packages when using this method. It also
1208 do not work well, so use version 0.15 or later. Installing both
1209 firmware and user space packages might give you a bit more than you
1210 want, so I decided to split the tasksel task in two, one for firmware
1211 and one for user space programs. The firmware task is enabled by
1212 default, while the one for user space programs is not. This split is
1213 implemented in the package currently in unstable.&lt;/p&gt;
1214
1215 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1216 this recipe work for you. :)&lt;/p&gt;
1217
1218 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1219 foremost, it work because tasksel is modular, and driven by whatever
1220 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1221 isenkram-cli package place two files for tasksel to find. First there
1222 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1223
1224 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1225 Task: isenkram-packages
1226 Section: hardware
1227 Description: Hardware specific packages (autodetected by isenkram)
1228 Based on the detected hardware various hardware specific packages are
1229 proposed.
1230 Test-new-install: show show
1231 Relevance: 8
1232 Packages: for-current-hardware
1233
1234 Task: isenkram-firmware
1235 Section: hardware
1236 Description: Hardware specific firmware packages (autodetected by isenkram)
1237 Based on the detected hardware various hardware specific firmware
1238 packages are proposed.
1239 Test-new-install: mark show
1240 Relevance: 8
1241 Packages: for-current-hardware-firmware
1242 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1243
1244 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1245 should be handled and the Packages line referencing to a script in
1246 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1247 list of packages to install. The for-current-hardware-firmware script
1248 look like this to list relevant firmware for the machine:
1249
1250 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1251 #!/bin/sh
1252 #
1253 PATH=/usr/sbin:$PATH
1254 export PATH
1255 isenkram-autoinstall-firmware -l
1256 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1257
1258 &lt;p&gt;With those two pieces in place, the firmware is installed by
1259 tasksel during the normal d-i run. :)&lt;/p&gt;
1260
1261 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1262 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1263 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1264 install.&lt;/p&gt;
1265
1266 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1267 pilots in testing this feature, as isenkram is used there now to
1268 install firmware, replacing the earlier scripts.&lt;/p&gt;
1269 </description>
1270 </item>
1271
1272 <item>
1273 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1274 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1275 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1276 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1277 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1278 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1279 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1280 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1281
1282 &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;
1283
1284 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1285 about this hidden Linux installation. It is interesting what
1286 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1287 </description>
1288 </item>
1289
1290 <item>
1291 <title>New lsdvd release version 0.17 is ready</title>
1292 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1293 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1294 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1295 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1296 got a new set of developers a few weeks ago, after the original
1297 developer decided to step down and pass the project to fresh blood.
1298 This project is now maintained by Petter Reinholdtsen and Steve
1299 Dibb.&lt;/p&gt;
1300
1301 &lt;p&gt;I just wrapped up
1302 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1303 new lsdvd release&lt;/a&gt;, available in git or from
1304 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1305 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1306 0.17.&lt;/p&gt;
1307
1308 &lt;ul&gt;
1309
1310 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1311 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1312 non-existant, to work around additional copy protection&lt;/li&gt;
1313 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1314 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1315 &lt;li&gt;Fix include orders&lt;/li&gt;
1316 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1317 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1318 &lt;li&gt;Make sure the array size and the array limit used when initialising
1319 the palette size is the same.&lt;/li&gt;
1320 &lt;li&gt;Fix array printing.&lt;/li&gt;
1321 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1322 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1323 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1324 with more GCC compiler warnings.&lt;/li&gt;
1325
1326 &lt;/ul&gt;
1327
1328 &lt;p&gt;This change bring together patches for lsdvd in use in various
1329 Linux and Unix distributions, as well as patches submitted to the
1330 project the last nine years. Please check it out. :)&lt;/p&gt;
1331 </description>
1332 </item>
1333
1334 <item>
1335 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1336 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1337 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1338 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1339 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1340 project&lt;/a&gt; provide a Linux solution for schools, including a
1341 powerful desktop with education software, a central server providing
1342 web pages, user database, user home directories, central login and PXE
1343 boot of both clients without disk and the installation to install Debian
1344 Edu on machines with disk (and a few other services perhaps to small
1345 to mention here). We in the Debian Edu team are currently working on
1346 the Jessie based version, trying to get everything in shape before the
1347 freeze, to avoid having to maintain our own package repository in the
1348 future. The
1349 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1350 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1351 work left. Some fatal problems block testing, breaking the installer,
1352 but it is possible to work around these to get anyway. Here is a
1353 recipe on how to get the installation limping along.&lt;/p&gt;
1354
1355 &lt;p&gt;First, download the test ISO via
1356 &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;,
1357 &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;
1358 or rsync (use
1359 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1360 The ISO build was broken on Tuesday, so we do not get a new ISO every
1361 12 hours or so, but thankfully the ISO we already got we are able to
1362 install with some tweaking.&lt;/p&gt;
1363
1364 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1365 (use Alt-Ctrl-F2), run&lt;/p&gt;
1366
1367 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1368 nano /usr/bin/edu-eatmydata-install
1369 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1370
1371 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1372 optimization. Return to the installation, select the profile you want
1373 and continue. Without this change, exim4-config will fail to install
1374 due to a known bug in eatmydata.&lt;/p&gt;
1375
1376 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1377 this do not work, figure out what your correct value would be. All my
1378 test machines need /dev/sda, so I have no advice if it do not fit
1379 your need.&lt;/p&gt;
1380
1381 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1382 root after the initial boot from hard drive, and install the
1383 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1384 or mate. If you want several desktop options, install more than one
1385 metapackage. Once this is done, reboot and you should have a working
1386 graphical login screen. This workaround should no longer be needed
1387 once the education-tasks package version 1.801 enter testing in two
1388 days.&lt;/p&gt;
1389
1390 &lt;p&gt;I believe the ISO build will start working on two days when the new
1391 tasksel package enter testing and Steve McIntyre get a chance to
1392 update the debian-cd git repository. The eatmydata, grub and desktop
1393 issues are already fixed in unstable and testing, and should show up
1394 on the ISO as soon as the ISO build start working again. Well the
1395 eatmydata optimization is really just disabled. The proper fix
1396 require an upload by the eatmydata maintainer applying the patch
1397 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1398 The rest have proper fixes in unstable.&lt;/p&gt;
1399
1400 &lt;p&gt;I hope this get you going with the installation testing, as we are
1401 quickly running out of time trying to get our Jessie based
1402 installation ready before the distribution freeze in a month.&lt;/p&gt;
1403 </description>
1404 </item>
1405
1406 <item>
1407 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1408 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1409 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1410 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1411 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1412 to handle my fairly large DVD collection. It is a nice command line
1413 tool to get details about a DVD, like title, tracks, track length,
1414 etc, in XML, Perl or human readable format. But lsdvd have not seen
1415 any new development since 2006 and had a few irritating bugs affecting
1416 its use with some DVDs. Upstream seemed to be dead, and in January I
1417 sent a small probe asking for a version control repository for the
1418 project, without any reply. But I use it regularly and would like to
1419 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1420 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1421 the project admin, and after getting a reply from him explaining that
1422 he was no longer interested in the project, I asked if I could take
1423 over. And yesterday, I became project admin.&lt;/p&gt;
1424
1425 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1426 maintainer interested in joining forces to maintain the upstream
1427 project, and I hope we can get a new release out fairly quickly,
1428 collecting the patches spread around on the internet into on place.
1429 I&#39;ve added the relevant Debian patches to the freshly created git
1430 repository, and expect the Gentoo patches to make it too. If you got
1431 a DVD collection and care about command line tools, check out
1432 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1433 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1434 list&lt;/a&gt;. :)&lt;/p&gt;
1435 </description>
1436 </item>
1437
1438 <item>
1439 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1440 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1441 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1442 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1443 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1444 a lot quicker. When we install more than 2000 packages in
1445 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1446 tasksel in the installer, unpacking the binary packages take forever.
1447 A part of the slow I/O issue was discussed in
1448 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1449 much file system sync-ing done by dpkg, which is the package
1450 responsible for unpacking the binary packages. Other parts (like code
1451 executed by postinst scripts) might also sync to disk during
1452 installation. All this sync-ing to disk do not really make sense to
1453 me. If the machine crash half-way through, I start over, I do not try
1454 to salvage the half installed system. So the failure sync-ing is
1455 supposed to protect against, hardware or system crash, is not really
1456 relevant while the installer is running.&lt;/p&gt;
1457
1458 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1459 system sync()-ing in a fairly non-intrusive way, without the need to
1460 change the code in several packages. The idea is not new, but I have
1461 not heard anyone propose the approach using dpkg-divert before. It
1462 depend on the small and clever package
1463 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1464 uses LD_PRELOAD to replace the system functions for syncing data to
1465 disk with functions doing nothing, thus allowing programs to live
1466 dangerous while speeding up disk I/O significantly. Instead of
1467 modifying the implementation of dpkg, apt and tasksel (which are the
1468 packages responsible for selecting, fetching and installing packages),
1469 it occurred to me that we could just divert the programs away, replace
1470 them with a simple shell wrapper calling
1471 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1472 Two days ago I decided to test the idea, and wrapped up a simple
1473 implementation for the Debian Edu udeb.&lt;/p&gt;
1474
1475 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1476 time of the pkgsel step (installing tasks) from 64 to less than 44
1477 minutes (20 minutes shaved off the installation) on an old Dell
1478 Latitude D505 machine. I am not quite sure what the optimised time
1479 would have been, as I messed up the testing a bit, causing the debconf
1480 priority to get low enough for two questions to pop up during
1481 installation. As soon as I saw the questions I moved the installation
1482 along, but do not know how long the question were holding up the
1483 installation. I did some more measurements using Debian Edu Jessie,
1484 and got these results. The time measured is the time stamp in
1485 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1486 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1487 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1488 timing thus do not depend on how quickly the user handle the tasksel
1489 dialog.&lt;/p&gt;
1490
1491 &lt;p&gt;&lt;table&gt;
1492
1493 &lt;tr&gt;
1494 &lt;th&gt;Machine/setup&lt;/th&gt;
1495 &lt;th&gt;Original tasksel&lt;/th&gt;
1496 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1497 &lt;th&gt;Reduction&lt;/th&gt;
1498 &lt;/tr&gt;
1499
1500 &lt;tr&gt;
1501 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1502 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1503 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1504 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1505 &lt;/tr&gt;
1506
1507 &lt;tr&gt;
1508 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1509 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1510 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1511 &lt;td&gt;23 min 40%&lt;/td&gt;
1512 &lt;/tr&gt;
1513
1514 &lt;tr&gt;
1515 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1516 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1517 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1518 &lt;td&gt;11 min 50%&lt;/td&gt;
1519 &lt;/tr&gt;
1520
1521 &lt;tr&gt;
1522 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1523 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1524 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1525 &lt;td&gt;2 min 33%&lt;/td&gt;
1526 &lt;/tr&gt;
1527
1528 &lt;tr&gt;
1529 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1530 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1531 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1532 &lt;td&gt;4 min 21%&lt;/td&gt;
1533 &lt;/tr&gt;
1534
1535 &lt;/table&gt;&lt;/p&gt;
1536
1537 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1538 time is spent downloading packages. The connection to the Internet
1539 was 100Mbit/s during testing, so downloading should not be a
1540 significant factor in the measurement. Download typically took a few
1541 seconds to a few minutes, depending on the amount of packages being
1542 installed.&lt;/p&gt;
1543
1544 &lt;p&gt;The speedup is implemented by using two hooks in
1545 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1546 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1547 finish-install.d hook to remove the divert at the end of the
1548 installation. I picked the pre-pkgsel.d hook instead of the
1549 post-base-installer.d hook because I test using an ISO without the
1550 eatmydata package included, and the post-base-installer.d hook in
1551 Debian Edu can only operate on packages included in the ISO. The
1552 negative effect of this is that I am unable to activate this
1553 optimization for the kernel installation step in d-i. If the code is
1554 moved to the post-base-installer.d hook, the speedup would be larger
1555 for the entire installation.&lt;/p&gt;
1556
1557 &lt;p&gt;I&#39;ve implemented this in the
1558 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1559 git repository, and plan to provide the optimization as part of the
1560 Debian Edu installation. If you want to test this yourself, you can
1561 create two files in the installer (or in an udeb). One shell script
1562 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1563
1564 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1565 #!/bin/sh
1566 set -e
1567 . /usr/share/debconf/confmodule
1568 info() {
1569 logger -t my-pkgsel &quot;info: $*&quot;
1570 }
1571 error() {
1572 logger -t my-pkgsel &quot;error: $*&quot;
1573 }
1574 override_install() {
1575 apt-install eatmydata || true
1576 if [ -x /target/usr/bin/eatmydata ] ; then
1577 for bin in dpkg apt-get aptitude tasksel ; do
1578 file=/usr/bin/$bin
1579 # Test that the file exist and have not been diverted already.
1580 if [ -f /target$file ] ; then
1581 info &quot;diverting $file using eatmydata&quot;
1582 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1583 &gt; /target$file.edu
1584 chmod 755 /target$file.edu
1585 in-target dpkg-divert --package debian-edu-config \
1586 --rename --quiet --add $file
1587 ln -sf ./$bin.edu /target$file
1588 else
1589 error &quot;unable to divert $file, as it is missing.&quot;
1590 fi
1591 done
1592 else
1593 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1594 fi
1595 }
1596
1597 override_install
1598 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1599
1600 &lt;p&gt;To clean up, another shell script should go into
1601 /usr/lib/finish-install.d/ with code like this:
1602
1603 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1604 #! /bin/sh -e
1605 . /usr/share/debconf/confmodule
1606 error() {
1607 logger -t my-finish-install &quot;error: $@&quot;
1608 }
1609 remove_install_override() {
1610 for bin in dpkg apt-get aptitude tasksel ; do
1611 file=/usr/bin/$bin
1612 if [ -x /target$file.edu ] ; then
1613 rm /target$file
1614 in-target dpkg-divert --package debian-edu-config \
1615 --rename --quiet --remove $file
1616 rm /target$file.edu
1617 else
1618 error &quot;Missing divert for $file.&quot;
1619 fi
1620 done
1621 sync # Flush file buffers before continuing
1622 }
1623
1624 remove_install_override
1625 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1626
1627 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1628 edu-eatmydata-install and call it from the pre-pkgsel.d and
1629 finish-install.d scripts.&lt;/p&gt;
1630
1631 &lt;p&gt;By now you might ask if this change should get into the normal
1632 Debian installer too? I suspect it should, but am not sure the
1633 current debian-installer coordinators find it useful enough. It also
1634 depend on the side effects of the change. I&#39;m not aware of any, but I
1635 guess we will see if the change is safe after some more testing.
1636 Perhaps there is some package in Debian depending on sync() and
1637 fsync() having effect? Perhaps it should go into its own udeb, to
1638 allow those of us wanting to enable it to do so without affecting
1639 everyone.&lt;/p&gt;
1640
1641 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1642 will break installation of all programs using gnutls because of
1643 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1644 eatmydata package in Debian will solve it.&lt;/p&gt;
1645
1646 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1647 the optimization work again. And I have discovered that the
1648 dpkg-divert trick is not really needed and implemented a slightly
1649 simpler approach as part of the debian-edu-install package. See
1650 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1651
1652 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1653 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1654 triggering on i386 made it into testing, and broke this installation
1655 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1656 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1657 </description>
1658 </item>
1659
1660 <item>
1661 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1662 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1663 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1664 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1665 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1666 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1667 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1668 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1669 learn that there is a large set of publicly available key servers to
1670 use when looking for peoples public key. So far I have used
1671 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1672 were misbehaving, but those days are ended. The servers I have used
1673 up until yesterday have been slow and some times unavailable. I hope
1674 those problems are gone now.&lt;/p&gt;
1675
1676 &lt;p&gt;Behind the round robin DNS entry of the
1677 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1678 there is a pool of more than 100 keyservers which are checked every
1679 day to ensure they are well connected and up to date. It must be
1680 better than what I have used so far. :)&lt;/p&gt;
1681
1682 &lt;p&gt;Yesterdays speaker told me that the service is the default
1683 keyserver provided by the default configuration in GnuPG, but this do
1684 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1685
1686 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1687 line:&lt;/p&gt;
1688
1689 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1690 keyserver pool.sks-keyservers.net
1691 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1692
1693 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1694 entries in DNS. Just for fun, I did just that at work, so now every
1695 user of GnuPG at the University of Oslo should find a OpenGPG
1696 keyserver automatically should their need it:&lt;/p&gt;
1697
1698 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1699 % host -t srv _pgpkey-http._tcp.uio.no
1700 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1701 %
1702 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1703
1704 &lt;p&gt;Now if only
1705 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1706 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1707 very happy. It can look up a given key or search for a user ID, but I
1708 normally do not want that, but to find a trust path from my key to
1709 another key. Given a user ID or key ID, I would like to find (and
1710 download) the keys representing a signature path from my key to the
1711 key in question, to be able to get a trust path between the two keys.
1712 This is as far as I can tell not possible today. Perhaps something
1713 for a future version of the protocol?&lt;/p&gt;
1714 </description>
1715 </item>
1716
1717 <item>
1718 <title>From English wiki to translated PDF and epub via Docbook</title>
1719 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1720 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1721 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1722 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1723 project&lt;/a&gt; provide an instruction manual for teachers, system
1724 administrators and other users that contain useful tips for setting up
1725 and maintaining a Debian Edu installation. This text is about how the
1726 text processing of this manual is handled in the project.&lt;/p&gt;
1727
1728 &lt;p&gt;One goal of the project is to provide information in the native
1729 language of its users, and for this we need to handle translations.
1730 But we also want to make sure each language contain the same
1731 information, so for this we need a good way to keep the translations
1732 in sync. And we want it to be easy for our users to improve the
1733 documentation, avoiding the need to learn special formats or tools to
1734 contribute, and the obvious way to do this is to make it possible to
1735 edit the documentation using a web browser. We also want it to be
1736 easy for translators to keep the translation up to date, and give them
1737 help in figuring out what need to be translated. Here is the list of
1738 tools and the process we have found trying to reach all these
1739 goals.&lt;/p&gt;
1740
1741 &lt;p&gt;We maintain the authoritative source of our manual in the
1742 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1743 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1744 front page with references to the different chapters, several pages
1745 for each chapter, and finally one &quot;collection page&quot; gluing all the
1746 chapters together into one large web page (aka
1747 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1748 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1749 processing and translations. Thanks to the fact that the
1750 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1751 wiki.debian.org support exporting pages in
1752 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1753 the list of pages to export using the raw version of the AllInOne
1754 page, loop over each of them to generate a Docbook XML version of the
1755 manual. This process also download images and transform image
1756 references to use the locally downloaded images. The generated
1757 Docbook XML files are slightly broken, so some post-processing is done
1758 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1759 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1760 a handfull of images. The XML file can now be used to generate PDF, HTML
1761 and epub versions of the English manual. This is the basic step of
1762 our process, making PDF (using dblatex), HTML (using xsltproc) and
1763 epub (using dbtoepub) version from Docbook XML, and the resulting files
1764 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1765
1766 &lt;p&gt;But English documentation is not enough for us. We want translated
1767 documentation too, and we want to make it easy for translators to
1768 track the English original. For this we use the
1769 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1770 which allow us to transform the English Docbook XML file into a
1771 translation file (a .pot file), usable with the normal gettext based
1772 translation tools used by those translating free software. The pot
1773 file is used to create and maintain translation files (several .po
1774 files), which the translations update with the native language
1775 translations of all titles, paragraphs and blocks of text in the
1776 original. The next step is combining the original English Docbook XML
1777 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1778 create a translated Docbook XML file (in this case
1779 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1780 translated, if the translation is not complete) Docbook XML file can
1781 then be used like the original to create a PDF, HTML and epub version
1782 of the documentation.&lt;/p&gt;
1783
1784 &lt;p&gt;The translators use different tools to edit the .po files. We
1785 recommend using
1786 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1787 while some use emacs and vi, others can use web based editors like
1788 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1789 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1790 is where the .po file end up, in our git repository. Updated
1791 translations can either be committed directly to git, or submitted as
1792 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1793 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1794
1795 &lt;p&gt;One challenge is images, which both might need to be translated (if
1796 they show translated user applications), and are needed in different
1797 formats when creating PDF and HTML versions (epub is a HTML version in
1798 this regard). For this we transform the original PNG images to the
1799 needed density and format during build, and have a way to provide
1800 translated images by storing translated versions in
1801 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1802 package maintainers know more.&lt;/p&gt;
1803
1804 &lt;p&gt;If you wonder what the result look like, we provide
1805 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1806 of the documentation packages on the web&lt;/a&gt;. See for example the
1807 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1808 PDF version&lt;/a&gt; or the
1809 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1810 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1811 but perhaps it will be done in the future.&lt;/p&gt;
1812
1813 &lt;p&gt;To learn more, check out
1814 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1815 debian-edu-doc package&lt;/a&gt;,
1816 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1817 manual on the wiki&lt;/a&gt; and
1818 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1819 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1820 </description>
1821 </item>
1822
1823 <item>
1824 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1825 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1826 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1827 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1828 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1829 related packages relevant for the computer installed automatically.
1830 So I implemented one, using
1831 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1832 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1833 run tasksel as user root. You should be presented with a new option,
1834 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1835 select it, tasksel will install the packages isenkram claim is fit for
1836 the current hardware, hot pluggable or not.&lt;p&gt;
1837
1838 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1839 description, and the other is the script used to extract the list of
1840 packages to install. The first part is in
1841 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1842 this:&lt;/p&gt;
1843
1844 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1845 Task: isenkram
1846 Section: hardware
1847 Description: Hardware specific packages (autodetected by isenkram)
1848 Based on the detected hardware various hardware specific packages are
1849 proposed.
1850 Test-new-install: mark show
1851 Relevance: 8
1852 Packages: for-current-hardware
1853 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1854
1855 &lt;p&gt;The second part is in
1856 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1857 this:&lt;/p&gt;
1858
1859 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1860 #!/bin/sh
1861 #
1862 (
1863 isenkram-lookup
1864 isenkram-autoinstall-firmware -l
1865 ) | sort -u
1866 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1867
1868 &lt;p&gt;All in all, a very short and simple implementation making it
1869 trivial to install the hardware dependent package we all may want to
1870 have installed on our machines. I&#39;ve not been able to find a way to
1871 get tasksel to tell you exactly which packages it plan to install
1872 before doing the installation. So if you are curious or careful,
1873 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1874
1875 &lt;p&gt;The information about which packages are handling which hardware is
1876 fetched either from the isenkram package itself in
1877 /usr/share/isenkram/, from git.debian.org or from the APT package
1878 database (using the Modaliases header). The APT package database
1879 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1880 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1881 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1882 the python-apt code (bug
1883 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1884 workaround I was able to get rid of the file descriptor leak and
1885 reduce the memory leak from ~30 MiB per hardware detection down to
1886 around 2 MiB per hardware detection. It should make the desktop
1887 daemon a lot more useful. The fix is in version 0.7 uploaded to
1888 unstable today.&lt;/p&gt;
1889
1890 &lt;p&gt;I believe the current way of mapping hardware to packages in
1891 Isenkram is is a good draft, but in the future I expect isenkram to
1892 use the AppStream data source for this. A proposal for getting proper
1893 AppStream support into Debian is floating around as
1894 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1895 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1896 project&lt;/a&gt; will take place this summer to improve the situation. I
1897 look forward to seeing the result, and welcome patches for isenkram to
1898 start using the information when it is ready.&lt;/p&gt;
1899
1900 &lt;p&gt;If you want your package to map to some specific hardware, either
1901 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1902 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1903 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1904 package. See also
1905 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1906 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1907 the information will be migrated to AppStream eventually, but for the
1908 moment I got no better place to store it.&lt;/p&gt;
1909 </description>
1910 </item>
1911
1912 <item>
1913 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1914 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1915 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1916 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1917 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1918 project&lt;/a&gt; is working on providing the software and hardware to make
1919 it easy for non-technical people to host their data and communication
1920 at home, and being able to communicate with their friends and family
1921 encrypted and away from prying eyes. It is still going strong, and
1922 today a major mile stone was reached.&lt;/p&gt;
1923
1924 &lt;p&gt;Today, the last of the packages currently used by the project to
1925 created the system images were accepted into Debian Unstable. It was
1926 the freedombox-setup package, which is used to configure the images
1927 during build and on the first boot. Now all one need to get going is
1928 the build code from the freedom-maker git repository and packages from
1929 Debian. And once the freedombox-setup package enter testing, we can
1930 build everything directly from Debian. :)&lt;/p&gt;
1931
1932 &lt;p&gt;Some key packages used by Freedombox are
1933 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1934 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1935 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1936 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1937 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1938 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1939 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1940 are plans to integrate more packages into the setup. User
1941 documentation is maintained on the Debian wiki. Please
1942 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1943 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1944
1945 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1946 setup, run this on a Debian machine using a user with sudo rights to
1947 become root:&lt;/p&gt;
1948
1949 &lt;p&gt;&lt;pre&gt;
1950 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1951 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1952 u-boot-tools
1953 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1954 freedom-maker
1955 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1956 &lt;/pre&gt;&lt;/p&gt;
1957
1958 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1959 devices. See the README in the freedom-maker git repo for more
1960 details on the build. If you do not want all three images, trim the
1961 make line. Note that the virtualbox-image target is not really
1962 virtualbox specific. It create a x86 image usable in kvm, qemu,
1963 vmware and any other x86 virtual machine environment. You might need
1964 the version of vmdebootstrap in Jessie to get the build working, as it
1965 include fixes for a race condition with kpartx.&lt;/p&gt;
1966
1967 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1968 method, boot a Debian Wheezy ISO and use this boot argument to load
1969 the preseed values:&lt;/p&gt;
1970
1971 &lt;p&gt;&lt;pre&gt;
1972 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;
1973 &lt;/pre&gt;&lt;/p&gt;
1974
1975 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1976 it still work.&lt;/p&gt;
1977
1978 &lt;p&gt;If you wonder how to help, one task you could look at is using
1979 systemd as the boot system. It will become the default for Linux in
1980 Jessie, so we need to make sure it is usable on the Freedombox. I did
1981 a simple test a few weeks ago, and noticed dnsmasq failed to start
1982 during boot when using systemd. I suspect there are other problems
1983 too. :) To detect problems, there is a test suite included, which can
1984 be run from the plinth web interface.&lt;/p&gt;
1985
1986 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1987 us get the new release published. :) Please join us on
1988 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1989 irc.debian.org)&lt;/a&gt; and
1990 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1991 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1992 </description>
1993 </item>
1994
1995 <item>
1996 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1997 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1998 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1999 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
2000 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
2001 solution for use at home. My requirements are simple, it must be
2002 cheap and locally encrypted (in other words, I keep the encryption
2003 keys, the storage provider do not have access to my private files).
2004 One idea me and my friends had many years ago, before the cloud
2005 storage providers showed up, was to use Google mail as storage,
2006 writing a Linux block device storing blocks as emails in the mail
2007 service provided by Google, and thus get heaps of free space. On top
2008 of this one can add encryption, RAID and volume management to have
2009 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2010 I never found time to implement such system. But the last few weeks I
2011 have looked at a system called
2012 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
2013 mounted network backed file system with the features I need.&lt;/p&gt;
2014
2015 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
2016 handling several different storage providers, any with Amazon S3,
2017 Google Drive or OpenStack API. There are heaps of such storage
2018 providers. S3QL can also use a local directory as storage, which
2019 combined with sshfs allow for file storage on any ssh server. S3QL
2020 include support for encryption, compression, de-duplication, snapshots
2021 and immutable file systems, allowing me to mount the remote storage as
2022 a local mount point, look at and use the files as if they were local,
2023 while the content is stored in the cloud as well. This allow me to
2024 have a backup that should survive fire. The file system can not be
2025 shared between several machines at the same time, as only one can
2026 mount it at the time, but any machine with the encryption key and
2027 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
2028
2029 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
2030 package is included already. So to get started, run &lt;tt&gt;apt-get
2031 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
2032 Greenqloud, after reading their nice recipe on
2033 &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
2034 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
2035 in Iceland more than those in USA when it come to keeping my personal
2036 data safe and private, and thus would rather spend money on a company
2037 in Iceland. Another nice recipe is available from the article
2038 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
2039 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
2040 Admin magazine. When the provider is picked, figure out how to get
2041 the API key needed to connect to the storage API. With Greencloud,
2042 the key did not show up until I had added payment details to my
2043 account.&lt;/p&gt;
2044
2045 &lt;p&gt;Armed with the API access details, it is time to create the file
2046 system. First, create a new bucket in the cloud. This bucket is the
2047 file system storage area. I picked a bucket name reflecting the
2048 machine that was going to store data there, but any name will do.
2049 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
2050 the API login and password, and a locally created password. Store it
2051 all in ~root/.s3ql/authinfo2 like this:
2052
2053 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2054 [s3c]
2055 storage-url: s3c://s.greenqloud.com:443/bucket-name
2056 backend-login: API-login
2057 backend-password: API-password
2058 fs-passphrase: local-password
2059 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2060
2061 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
2062 but any sensible way to create a fairly random password should do it.
2063 Armed with these details, it is now time to run mkfs, entering the API
2064 details and password to create it:&lt;/p&gt;
2065
2066 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2067 # mkdir -m 700 /var/lib/s3ql-cache
2068 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2069 --ssl s3c://s.greenqloud.com:443/bucket-name
2070 Enter backend login:
2071 Enter backend password:
2072 Before using S3QL, make sure to read the user&#39;s guide, especially
2073 the &#39;Important Rules to Avoid Loosing Data&#39; section.
2074 Enter encryption password:
2075 Confirm encryption password:
2076 Generating random encryption key...
2077 Creating metadata tables...
2078 Dumping metadata...
2079 ..objects..
2080 ..blocks..
2081 ..inodes..
2082 ..inode_blocks..
2083 ..symlink_targets..
2084 ..names..
2085 ..contents..
2086 ..ext_attributes..
2087 Compressing and uploading metadata...
2088 Wrote 0.00 MB of compressed metadata.
2089 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2090
2091 &lt;p&gt;The next step is mounting the file system to make the storage available.
2092
2093 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2094 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2095 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2096 Using 4 upload threads.
2097 Downloading and decompressing metadata...
2098 Reading metadata...
2099 ..objects..
2100 ..blocks..
2101 ..inodes..
2102 ..inode_blocks..
2103 ..symlink_targets..
2104 ..names..
2105 ..contents..
2106 ..ext_attributes..
2107 Mounting filesystem...
2108 # df -h /s3ql
2109 Filesystem Size Used Avail Use% Mounted on
2110 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
2111 #
2112 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2113
2114 &lt;p&gt;The file system is now ready for use. I use rsync to store my
2115 backups in it, and as the metadata used by rsync is downloaded at
2116 mount time, no network traffic (and storage cost) is triggered by
2117 running rsync. To unmount, one should not use the normal umount
2118 command, as this will not flush the cache to the cloud storage, but
2119 instead running the umount.s3ql command like this:
2120
2121 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2122 # umount.s3ql /s3ql
2123 #
2124 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2125
2126 &lt;p&gt;There is a fsck command available to check the file system and
2127 correct any problems detected. This can be used if the local server
2128 crashes while the file system is mounted, to reset the &quot;already
2129 mounted&quot; flag. This is what it look like when processing a working
2130 file system:&lt;/p&gt;
2131
2132 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2133 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
2134 Using cached metadata.
2135 File system seems clean, checking anyway.
2136 Checking DB integrity...
2137 Creating temporary extra indices...
2138 Checking lost+found...
2139 Checking cached objects...
2140 Checking names (refcounts)...
2141 Checking contents (names)...
2142 Checking contents (inodes)...
2143 Checking contents (parent inodes)...
2144 Checking objects (reference counts)...
2145 Checking objects (backend)...
2146 ..processed 5000 objects so far..
2147 ..processed 10000 objects so far..
2148 ..processed 15000 objects so far..
2149 Checking objects (sizes)...
2150 Checking blocks (referenced objects)...
2151 Checking blocks (refcounts)...
2152 Checking inode-block mapping (blocks)...
2153 Checking inode-block mapping (inodes)...
2154 Checking inodes (refcounts)...
2155 Checking inodes (sizes)...
2156 Checking extended attributes (names)...
2157 Checking extended attributes (inodes)...
2158 Checking symlinks (inodes)...
2159 Checking directory reachability...
2160 Checking unix conventions...
2161 Checking referential integrity...
2162 Dropping temporary indices...
2163 Backing up old metadata...
2164 Dumping metadata...
2165 ..objects..
2166 ..blocks..
2167 ..inodes..
2168 ..inode_blocks..
2169 ..symlink_targets..
2170 ..names..
2171 ..contents..
2172 ..ext_attributes..
2173 Compressing and uploading metadata...
2174 Wrote 0.89 MB of compressed metadata.
2175 #
2176 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2177
2178 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2179 quick, about the same speed as local file access. Uploading large
2180 amount of data is to me limited by the bandwidth out of and into my
2181 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2182 which is very close to my upload speed, and downloading the same
2183 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2184 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2185 network, not the file system code. I do not know what a good cache
2186 size would be, but suspect that the cache should e larger than your
2187 working set.&lt;/p&gt;
2188
2189 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2190 time. If another machine try, it is told that the file system is
2191 busy:&lt;/p&gt;
2192
2193 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2194 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2195 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2196 Using 8 upload threads.
2197 Backend reports that fs is still mounted elsewhere, aborting.
2198 #
2199 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2200
2201 &lt;p&gt;The file content is uploaded when the cache is full, while the
2202 metadata is uploaded once every 24 hour by default. To ensure the
2203 file system content is flushed to the cloud, one can either umount the
2204 file system, or ask S3QL to flush the cache and metadata using
2205 s3qlctrl:
2206
2207 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2208 # s3qlctrl upload-meta /s3ql
2209 # s3qlctrl flushcache /s3ql
2210 #
2211 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2212
2213 &lt;p&gt;If you are curious about how much space your data uses in the
2214 cloud, and how much compression and deduplication cut down on the
2215 storage usage, you can use s3qlstat on the mounted file system to get
2216 a report:&lt;/p&gt;
2217
2218 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2219 # s3qlstat /s3ql
2220 Directory entries: 9141
2221 Inodes: 9143
2222 Data blocks: 8851
2223 Total data size: 22049.38 MB
2224 After de-duplication: 21955.46 MB (99.57% of total)
2225 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2226 Database size: 2.39 MB (uncompressed)
2227 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2228 #
2229 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2230
2231 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2232 storage. I did not try to locate them all, but am aware of at least
2233 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2234 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2235 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2236 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2237 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2238 accept payment in Bitcoin. Pick one that suit your need. Some of
2239 them provide several GiB of free storage, but the prize models are
2240 quite different and you will have to figure out what suits you
2241 best.&lt;/p&gt;
2242
2243 &lt;p&gt;While researching this blog post, I had a look at research papers
2244 and posters discussing the S3QL file system. There are several, which
2245 told me that the file system is getting a critical check by the
2246 science community and increased my confidence in using it. One nice
2247 poster is titled
2248 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2249 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2250 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2251 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2252 and Pamela Smith. Please have a look.&lt;/p&gt;
2253
2254 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2255 check out the mounted S3QL file system to see if it would be usable as
2256 a home directory (in other word, that it provided POSIX semantics when
2257 it come to locking and umask handling etc). Running
2258 &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
2259 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2260 no error was found. So the file system can be used for home
2261 directories, if one chooses to do so.&lt;/p&gt;
2262
2263 &lt;p&gt;If you do not want a locally file system, and want something that
2264 work without the Linux fuse file system, I would like to mention the
2265 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2266 provide locally encrypted backup using a command line client. It have
2267 a nicer access control system, where one can split out read and write
2268 access, allowing some systems to write to the backup and others to
2269 only read from it.&lt;/p&gt;
2270
2271 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2272 activities, please send Bitcoin donations to my address
2273 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2274 </description>
2275 </item>
2276
2277 <item>
2278 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2279 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2280 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2281 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2282 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2283 project&lt;/a&gt; is working on providing the software and hardware for
2284 making it easy for non-technical people to host their data and
2285 communication at home, and being able to communicate with their
2286 friends and family encrypted and away from prying eyes. It has been
2287 going on for a while, and is slowly progressing towards a new test
2288 release (0.2).&lt;/p&gt;
2289
2290 &lt;p&gt;And what day could be better than the Pi day to announce that the
2291 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2292 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2293 system), and can also be installed using a Debian installer preseed
2294 file. The Debian based Freedombox is now based on Debian Jessie,
2295 where most of the needed packages used are already present. Only one,
2296 the freedombox-setup package, is missing. To try to build your own
2297 boot image to test the current status, fetch the freedom-maker scripts
2298 and build using
2299 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2300 with a user with sudo access to become root:
2301
2302 &lt;pre&gt;
2303 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2304 freedom-maker
2305 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2306 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2307 u-boot-tools
2308 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2309 &lt;/pre&gt;
2310
2311 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2312 devices. See the README for more details on the build. If you do not
2313 want all three images, trim the make line. But note that thanks to &lt;a
2314 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2315 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2316 kpartx call.&lt;/p&gt;
2317
2318 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2319 method, boot a Debian Wheezy ISO and use this boot argument to load
2320 the preseed values:&lt;/p&gt;
2321
2322 &lt;pre&gt;
2323 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;
2324 &lt;/pre&gt;
2325
2326 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2327 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2328 currently hang while setting up APT sources. Killing the
2329 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2330 installation will get the installation going. This affect all
2331 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2332
2333 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2334 us get the new release published. :) Please join us on
2335 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2336 irc.debian.org)&lt;/a&gt; and
2337 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2338 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2339 </description>
2340 </item>
2341
2342 <item>
2343 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2344 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2346 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2347 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2348 innetgr tools, because I needed them in
2349 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2350 ng-utils, and it has served me well. I placed the project under the
2351 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2352 repository. But many years ago, the CVS repository was dropped (lost,
2353 not migrated to new hardware, not sure), and the project have lacked a
2354 proper home since then.&lt;/p&gt;
2355
2356 &lt;p&gt;Last summer, I had a look at the package and made a new release
2357 fixing a irritating crash bug, but was unable to store the changes in
2358 a proper source control system. I applied for a project on
2359 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2360 to follow up on it. Until today. :)&lt;/p&gt;
2361
2362 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2363 now have a new home, and a git repository with the highlight of the
2364 history of the project. I published all release tarballs and imported
2365 them into the git repository. As the project is really stable and not
2366 expected to gain new features any time soon, I decided to make a new
2367 release and call it 1.0. Visit the new project home on
2368 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2369 if you want to check it out. The new version is also uploaded into
2370 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2371 </description>
2372 </item>
2373
2374 <item>
2375 <title>Testing sysvinit from experimental in Debian Hurd</title>
2376 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2378 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2379 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2380 their changes into sysvinit, to allow them to use the normal sysvinit
2381 boot system instead of their old one. This follow up on the
2382 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2383 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2384 get Debian on Hurd working more like Debian on Linux. To get started,
2385 I downloaded a prebuilt hard disk image from
2386 &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;,
2387 and started it using virt-manager.&lt;/p&gt;
2388
2389 &lt;p&gt;The first think I had to do after logging in (root without any
2390 password) was to get the network operational. I followed
2391 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2392 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2393 commands as root to get the machine to accept a IP address from the
2394 kvm internal DHCP server:&lt;/p&gt;
2395
2396 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2397 settrans -fgap /dev/netdde /hurd/netdde
2398 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2399 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2400 dhclient /dev/eth0
2401 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2402
2403 &lt;p&gt;After this, the machine had internet connectivity, and I could
2404 upgrade it and install the sysvinit packages from experimental and
2405 enable it as the default boot system in Hurd.&lt;/p&gt;
2406
2407 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2408 running on the machine it for ssh login to work a password need to be
2409 set. Also, note that a bug somewhere in openssh on Hurd block
2410 compression from working. Remember to turn that off on the client
2411 side.&lt;/p&gt;
2412
2413 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2414 stuff:&lt;/p&gt;
2415
2416 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2417 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2418 deb http://http.debian.net/debian/ experimental main
2419 EOF
2420 apt-get update
2421 apt-get dist-upgrade
2422 apt-get install -t experimental initscripts sysv-rc sysvinit \
2423 sysvinit-core sysvinit-utils
2424 update-alternatives --config runsystem
2425 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2426
2427 &lt;p&gt;To reboot after switching boot system, you have to use
2428 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2429 yet a sysvinit process able to receive the signals from the normal
2430 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2431 upgrading every package and rebooting, the network come up with DHCP
2432 after boot as it should, and the settrans/pkill hack mentioned at the
2433 start is no longer needed. But for some strange reason, there are no
2434 longer any login prompt in the virtual console, so I logged in using
2435 ssh instead.
2436
2437 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2438 fail some times. No idea what the cause is, but hope the Hurd porters
2439 figure it out. At least Justus said on IRC (#debian-hurd on
2440 irc.debian.org) that they are aware of the problem. A way to reduce
2441 the impact is to upgrade to the Hurd packages built by Justus by
2442 adding this repository to the machine:&lt;/p&gt;
2443
2444 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2445 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2446 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2447 EOF
2448 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2449
2450 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2451 http://ftp.debian-ports.org/debian, because some of the packages in
2452 unstable do not yet include the required patches that are lingering in
2453 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2454
2455 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2456 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2457 i emacs - GNU Emacs editor (metapackage)
2458 i gdb - GNU Debugger
2459 i hurd-recommended - Miscellaneous translators
2460 i isc-dhcp-client - ISC DHCP client
2461 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2462 i libc-bin - Embedded GNU C Library: Binaries
2463 i libc-dev-bin - Embedded GNU C Library: Development binaries
2464 i libc0.3 - Embedded GNU C Library: Shared libraries
2465 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2466 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2467 i multiarch-support - Transitional package to ensure multiarch compatibilit
2468 i A x11-common - X Window System (X.Org) infrastructure
2469 i xorg - X.Org X Window System
2470 i A xserver-xorg - X.Org X server
2471 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2472 #
2473 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2474
2475 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2476 X.org did not work out of the box and I never took the time to follow
2477 the porters instructions to fix it. This time I was interested in the
2478 command line stuff.&lt;p&gt;
2479 </description>
2480 </item>
2481
2482 <item>
2483 <title>New chrpath release 0.16</title>
2484 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2485 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2486 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2487 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2488 find problems in C, C++ and Java code using static source code
2489 analysis. It can detect a lot of different problems, and is very
2490 useful to find memory and locking bugs in the error handling part of
2491 the source. The company behind it provide
2492 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2493 a community service&lt;/a&gt;, and many hundred free software projects are
2494 already checked. A few days ago I decided to have a closer look at
2495 the Coverity system, and discovered that the
2496 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2497 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2498 projects I am involved with was already registered. But these are
2499 fairly big, and I would also like to have a small and easy project to
2500 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2501 checking of the chrpath project&lt;/a&gt;. It was
2502 added to the checker and discovered seven potential defects. Six of
2503 these were real, mostly resource &quot;leak&quot; when the program detected an
2504 error. Nothing serious, as the resources would be released a fraction
2505 of a second later when the program exited because of the error, but it
2506 is nice to do it right in case the source of the program some time in
2507 the future end up in a library. Having fixed all defects and added
2508 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2509 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2510 publish a new release. These are the release notes:&lt;/p&gt;
2511
2512 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2513
2514 &lt;ul&gt;
2515
2516 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2517 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2518 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2519
2520 &lt;/ul&gt;
2521
2522 &lt;p&gt;You can
2523 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2524 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2525 project if something is wrong with the new release. The test suite
2526 did not discover any old errors, so if you find a new one, please also
2527 include a test suite check.&lt;/p&gt;
2528 </description>
2529 </item>
2530
2531 <item>
2532 <title>New chrpath release 0.15</title>
2533 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2534 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2535 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2536 <description>&lt;p&gt;After many years break from the package and a vain hope that
2537 development would be continued by someone else, I finally pulled my
2538 acts together this morning and wrapped up a new release of chrpath,
2539 the command line tool to modify the rpath and runpath of already
2540 compiled ELF programs. The update was triggered by the persistence of
2541 Isha Vishnoi at IBM, which needed a new config.guess file to get
2542 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2543 is working on. I checked the
2544 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2545 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2546 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2547 packages for interesting patches (failed to find the source from
2548 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2549 These are the release notes:&lt;/p&gt;
2550
2551 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2552
2553 &lt;ul&gt;
2554
2555 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2556 with newer architectures. Thanks to isha vishnoi for the heads
2557 up.&lt;/li&gt;
2558
2559 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2560
2561 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2562 Matthias Klose.&lt;/li&gt;
2563
2564 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2565 Petr Machata found in Fedora.&lt;/li&gt;
2566
2567 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2568 .dynamic is a NULL terminated string. Based on patch found in
2569 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2570
2571 &lt;/ul&gt;
2572
2573 &lt;p&gt;You can
2574 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2575 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2576 project if something is wrong with the new release. The test suite
2577 did not discover any old errors, so if you find a new one, please also
2578 include a testsuite check.&lt;/p&gt;
2579 </description>
2580 </item>
2581
2582 <item>
2583 <title>Debian init.d boot script example for rsyslog</title>
2584 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2585 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2586 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2587 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2588 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2589 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2590 init.d scripts at all. Here is an example init.d script, ie a rewrite
2591 of /etc/init.d/rsyslog:&lt;/p&gt;
2592
2593 &lt;p&gt;&lt;pre&gt;
2594 #!/lib/init/init-d-script
2595 ### BEGIN INIT INFO
2596 # Provides: rsyslog
2597 # Required-Start: $remote_fs $time
2598 # Required-Stop: umountnfs $time
2599 # X-Stop-After: sendsigs
2600 # Default-Start: 2 3 4 5
2601 # Default-Stop: 0 1 6
2602 # Short-Description: enhanced syslogd
2603 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2604 # It is quite compatible to stock sysklogd and can be
2605 # used as a drop-in replacement.
2606 ### END INIT INFO
2607 DESC=&quot;enhanced syslogd&quot;
2608 DAEMON=/usr/sbin/rsyslogd
2609 &lt;/pre&gt;&lt;/p&gt;
2610
2611 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2612 script was 137 lines, and the above is just 15 lines, most of it meta
2613 info/comments.&lt;/p&gt;
2614
2615 &lt;p&gt;How to do this, you ask? Well, one create a new script
2616 /lib/init/init-d-script looking something like this:
2617
2618 &lt;p&gt;&lt;pre&gt;
2619 #!/bin/sh
2620
2621 # Define LSB log_* functions.
2622 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2623 # and status_of_proc is working.
2624 . /lib/lsb/init-functions
2625
2626 #
2627 # Function that starts the daemon/service
2628
2629 #
2630 do_start()
2631 {
2632 # Return
2633 # 0 if daemon has been started
2634 # 1 if daemon was already running
2635 # 2 if daemon could not be started
2636 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2637 || return 1
2638 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2639 $DAEMON_ARGS \
2640 || return 2
2641 # Add code here, if necessary, that waits for the process to be ready
2642 # to handle requests from services started subsequently which depend
2643 # on this one. As a last resort, sleep for some time.
2644 }
2645
2646 #
2647 # Function that stops the daemon/service
2648 #
2649 do_stop()
2650 {
2651 # Return
2652 # 0 if daemon has been stopped
2653 # 1 if daemon was already stopped
2654 # 2 if daemon could not be stopped
2655 # other if a failure occurred
2656 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2657 RETVAL=&quot;$?&quot;
2658 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2659 # Wait for children to finish too if this is a daemon that forks
2660 # and if the daemon is only ever run from this initscript.
2661 # If the above conditions are not satisfied then add some other code
2662 # that waits for the process to drop all resources that could be
2663 # needed by services started subsequently. A last resort is to
2664 # sleep for some time.
2665 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2666 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2667 # Many daemons don&#39;t delete their pidfiles when they exit.
2668 rm -f $PIDFILE
2669 return &quot;$RETVAL&quot;
2670 }
2671
2672 #
2673 # Function that sends a SIGHUP to the daemon/service
2674 #
2675 do_reload() {
2676 #
2677 # If the daemon can reload its configuration without
2678 # restarting (for example, when it is sent a SIGHUP),
2679 # then implement that here.
2680 #
2681 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2682 return 0
2683 }
2684
2685 SCRIPTNAME=$1
2686 scriptbasename=&quot;$(basename $1)&quot;
2687 echo &quot;SN: $scriptbasename&quot;
2688 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2689 script=&quot;$1&quot;
2690 shift
2691 . $script
2692 else
2693 exit 0
2694 fi
2695
2696 NAME=$(basename $DAEMON)
2697 PIDFILE=/var/run/$NAME.pid
2698
2699 # Exit if the package is not installed
2700 #[ -x &quot;$DAEMON&quot; ] || exit 0
2701
2702 # Read configuration variable file if it is present
2703 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2704
2705 # Load the VERBOSE setting and other rcS variables
2706 . /lib/init/vars.sh
2707
2708 case &quot;$1&quot; in
2709 start)
2710 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2711 do_start
2712 case &quot;$?&quot; in
2713 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2714 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2715 esac
2716 ;;
2717 stop)
2718 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2719 do_stop
2720 case &quot;$?&quot; in
2721 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2722 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2723 esac
2724 ;;
2725 status)
2726 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2727 ;;
2728 #reload|force-reload)
2729 #
2730 # If do_reload() is not implemented then leave this commented out
2731 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2732 #
2733 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2734 #do_reload
2735 #log_end_msg $?
2736 #;;
2737 restart|force-reload)
2738 #
2739 # If the &quot;reload&quot; option is implemented then remove the
2740 # &#39;force-reload&#39; alias
2741 #
2742 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2743 do_stop
2744 case &quot;$?&quot; in
2745 0|1)
2746 do_start
2747 case &quot;$?&quot; in
2748 0) log_end_msg 0 ;;
2749 1) log_end_msg 1 ;; # Old process is still running
2750 *) log_end_msg 1 ;; # Failed to start
2751 esac
2752 ;;
2753 *)
2754 # Failed to stop
2755 log_end_msg 1
2756 ;;
2757 esac
2758 ;;
2759 *)
2760 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2761 exit 3
2762 ;;
2763 esac
2764
2765 :
2766 &lt;/pre&gt;&lt;/p&gt;
2767
2768 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2769 lot. I did not really polish the approach, so it might not always
2770 work out of the box, but you get the idea. I did not try very hard to
2771 optimize it nor make it more robust either.&lt;/p&gt;
2772
2773 &lt;p&gt;A better argument for switching init system in Debian than reducing
2774 the size of init scripts (which is a good thing to do anyway), is to
2775 get boot system that is able to handle the kernel events sensibly and
2776 robustly, and do not depend on the boot to run sequentially. The boot
2777 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2778 </description>
2779 </item>
2780
2781 <item>
2782 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2783 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2784 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2785 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2786 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2787 remote display access is the preferred solution with oVirt and RedHat
2788 Enterprise Virtualization, and I was sad to discover the other day
2789 that the browser plugin needed to use these systems seamlessly was
2790 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2791 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2792 2013-04-01, so I decided to wrap up a package based on the great work
2793 from Cajus Pollmeier and put it in a collab-maint maintained git
2794 repository to get a package I could use. I would very much like
2795 others to help me maintain the package (or just take over, I do not
2796 mind), but as no-one had volunteered so far, I just uploaded it to
2797 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2798
2799 &lt;p&gt;The source is now available from
2800 &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;
2801 </description>
2802 </item>
2803
2804 <item>
2805 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2806 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2807 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2808 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2809 <description>&lt;p&gt;The
2810 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2811 program is a a very nice system to create virtual machine images. It
2812 create a image file, add a partition table, mount it and run
2813 debootstrap in the mounted directory to create a Debian system on a
2814 stick. Yesterday, I decided to try to teach it how to make images for
2815 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2816 of a plan to simplify the build system for
2817 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2818 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2819 the virtualbox images, but its current build system made multistrap
2820 based system for Dreamplug images, and it is lacking support for
2821 Raspberry Pi.&lt;/p&gt;
2822
2823 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2824 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2825 code and adjusted it to be able to build armel images on my amd64
2826 Debian laptop. I ended up giving vmdebootstrap five new options,
2827 allowing me to replicate the image creation process I use to make
2828 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2829 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2830 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2831 call debootstrap with --foreign and to copy the handler into the
2832 generated chroot before running the second stage. This allow
2833 vmdebootstrap to create armel images on an amd64 host. Next I added
2834 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2835 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2836 given file system type, allowing me to create an image with a vfat
2837 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2838 variant&lt;/tt&gt; option to allow me to create smaller images without the
2839 Debian base system packages installed. Finally, I added an option
2840 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2841 as a boot loader. It is not needed on the Raspberry Pi and probably
2842 most other non-x86 architectures. The changes were accepted by the
2843 upstream author of vmdebootstrap yesterday and today, and is now
2844 available from
2845 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2846 upstream project page&lt;/a&gt;.&lt;/p&gt;
2847
2848 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2849 create a small script (the customize script) to add the non-free
2850 binary blob needed to boot the Raspberry Pi and the APT source
2851 list:&lt;/p&gt;
2852
2853 &lt;p&gt;&lt;pre&gt;
2854 #!/bin/sh
2855 set -e # Exit on first error
2856 rootdir=&quot;$1&quot;
2857 cd &quot;$rootdir&quot;
2858 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2859 deb http://http.debian.net/debian/ jessie main contrib non-free
2860 EOF
2861 # Install non-free binary blob needed to boot Raspberry Pi. This
2862 # install a kernel somewhere too.
2863 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2864 -O $rootdir/usr/bin/rpi-update
2865 chmod a+x $rootdir/usr/bin/rpi-update
2866 mkdir -p $rootdir/lib/modules
2867 touch $rootdir/boot/start.elf
2868 chroot $rootdir rpi-update
2869 &lt;/pre&gt;&lt;/p&gt;
2870
2871 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2872 to build the image:&lt;/p&gt;
2873
2874 &lt;pre&gt;
2875 sudo ./vmdebootstrap \
2876 --variant minbase \
2877 --arch armel \
2878 --distribution jessie \
2879 --mirror http://http.debian.net/debian \
2880 --image test.img \
2881 --size 600M \
2882 --bootsize 64M \
2883 --boottype vfat \
2884 --log-level debug \
2885 --verbose \
2886 --no-kernel \
2887 --no-extlinux \
2888 --root-password raspberry \
2889 --hostname raspberrypi \
2890 --foreign /usr/bin/qemu-arm-static \
2891 --customize `pwd`/customize \
2892 --package netbase \
2893 --package git-core \
2894 --package binutils \
2895 --package ca-certificates \
2896 --package wget \
2897 --package kmod
2898 &lt;/pre&gt;&lt;/p&gt;
2899
2900 &lt;p&gt;The list of packages being installed are the ones needed by
2901 rpi-update to make the image bootable on the Raspberry Pi, with the
2902 exception of netbase, which is needed by debootstrap to find
2903 /etc/hosts with the minbase variant. I really wish there was a way to
2904 set up an Raspberry Pi using only packages in the Debian archive, but
2905 that is not possible as far as I know, because it boots from the GPU
2906 using a non-free binary blob.&lt;/p&gt;
2907
2908 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2909 probably a few others installed. I have not checked the complete
2910 build dependency list.&lt;/p&gt;
2911
2912 &lt;p&gt;The resulting image will not use the hardware floating point unit
2913 on the Raspberry PI, because the armel architecture in Debian is not
2914 optimized for that use. So the images created will be a bit slower
2915 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2916 </description>
2917 </item>
2918
2919 <item>
2920 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2921 <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>
2922 <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>
2923 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2924 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2925 wider attention. I recommend signing and donating to each one of
2926 these. :)&lt;/p&gt;
2927
2928 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2929 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2930 Women program which is a Google Summer of Code like initiative to get
2931 more women involved in free software. One debian sponsor has offered
2932 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2933 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2934 hope you will to. :)&lt;/p&gt;
2935
2936 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2937 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2938 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2939 take place these days, and their need to fund the work. I&#39;ve already
2940 donated. Are you next?&lt;/p&gt;
2941
2942 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2943 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2944 statement under the heading
2945 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2946 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2947 Norwegian government. So far 499 signatures. I hope you will sign it
2948 too.&lt;/p&gt;
2949 </description>
2950 </item>
2951
2952 <item>
2953 <title>Videos about the Freedombox project - for inspiration and learning</title>
2954 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2955 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2956 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2957 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2958 project&lt;/a&gt; have been going on for a while, and have presented the
2959 vision, ideas and solution several places. Here is a little
2960 collection of videos of talks and presentation of the project.&lt;/p&gt;
2961
2962 &lt;ul&gt;
2963
2964 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2965 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2966
2967 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2968 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2969
2970 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2971 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2972 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2973 (Youtube)&lt;/li&gt;
2974
2975 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2976 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2977
2978 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2979 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2980
2981 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2982 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2983 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2984
2985 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2986 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2987 (Youtube)&lt;/li&gt;
2988
2989 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2990 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2991
2992 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2993 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2994
2995 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2996 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2997 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2998
2999 &lt;/ul&gt;
3000
3001 &lt;p&gt;A larger list is available from
3002 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
3003 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
3004
3005 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
3006 Jessie is coming along quite well, and soon both Owncloud and using
3007 Tor should be available for testers of the Freedombox solution. :) In
3008 a few weeks I hope everything needed to test it is included in Debian.
3009 The withsqlite package is already in Debian, and the plinth package is
3010 pending in NEW. The third and vital part of that puzzle is the
3011 metapackage/setup framework, which is still pending an upload. Join
3012 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
3013 (#freedombox on irc.debian.org)&lt;/a&gt; and
3014 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3015 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3016 </description>
3017 </item>
3018
3019 <item>
3020 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
3021 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
3022 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
3023 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
3024 <description>&lt;p&gt;I was introduced to the
3025 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
3026 in 2010, when Eben Moglen presented his vision about serving the need
3027 of non-technical people to keep their personal information private and
3028 within the legal protection of their own homes. The idea is to give
3029 people back the power over their network and machines, and return
3030 Internet back to its intended peer-to-peer architecture. Instead of
3031 depending on a central service, the Freedombox will give everyone
3032 control over their own basic infrastructure.&lt;/p&gt;
3033
3034 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
3035 taken priority. But this summers nasty news about the misuse of trust
3036 and privilege exercised by the &quot;western&quot; intelligence gathering
3037 communities increased my eagerness to contribute to a point where I
3038 actually started working on the project a while back.&lt;/p&gt;
3039
3040 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
3041 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
3042 create a simple and cheap Debian based appliance that anyone can hook
3043 up in their home and get access to secure and private services and
3044 communication. The initial deployment platform have been the
3045 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
3046 which is a piece of hardware I do not own. So to be able to test what
3047 the current Freedombox setup look like, I had to come up with a way to install
3048 it on some hardware I do have access to. I have rewritten the
3049 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
3050 image build framework to use .deb packages instead of only copying
3051 setup into the boot images, and thanks to this rewrite I am able to
3052 set up any machine supported by Debian Wheezy as a Freedombox, using
3053 the previously mentioned deb (and a few support debs for packages
3054 missing in Debian).&lt;/p&gt;
3055
3056 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
3057 scripts
3058 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
3059 and a administrative web interface
3060 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
3061 withsqlite), as well as a privacy enhancing proxy based on
3062 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
3063 (freedombox-privoxy). There is also a web/javascript based XMPP
3064 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
3065 trying (unsuccessfully so far) to talk to the XMPP server
3066 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
3067 web interface is pluggable, and the goal is to use it to enable OpenID
3068 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3069 this is really working yet, see
3070 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
3071 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
3072 on github at the moment. The HTTP proxy is operational out of the
3073 box, and the admin web interface can be used to add/remove plinth
3074 users. I&#39;ve not been able to do anything else with it so far, but
3075 know there are several branches spread around github and other places
3076 with lots of half baked features.&lt;/p&gt;
3077
3078 &lt;p&gt;Anyway, if you want to have a look at the current state, the
3079 following recipes should work to give you a test machine to poke
3080 at.&lt;/p&gt;
3081
3082 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
3083
3084 &lt;ol&gt;
3085
3086 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
3087 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
3088 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
3089 to the Debian installer:&lt;p&gt;
3090 &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;
3091
3092 &lt;li&gt;Answer the few language/region/password questions and pick disk to
3093 install on.&lt;/li&gt;
3094
3095 &lt;li&gt;When the installation is finished and the machine have rebooted a
3096 few times, your Freedombox is ready for testing.&lt;/li&gt;
3097
3098 &lt;/ol&gt;
3099
3100 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
3101
3102 &lt;ol&gt;
3103
3104 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
3105 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
3106 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
3107 &lt;pre&gt;
3108 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
3109 &lt;/pre&gt;&lt;/li&gt;
3110 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
3111 &lt;pre&gt;
3112 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3113 apt-key add -
3114 apt-get update
3115 apt-get install freedombox-setup
3116 /usr/lib/freedombox/setup
3117 &lt;/pre&gt;&lt;/li&gt;
3118 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
3119
3120 &lt;/ol&gt;
3121
3122 &lt;p&gt;You can test it on other architectures too, but because the
3123 freedombox-privoxy package is binary, it will only work as intended on
3124 the architectures where I have had time to build the binary and put it
3125 in my APT repository. But do not let this stop you. It is only a
3126 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
3127
3128 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
3129 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
3130 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
3131 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
3132
3133 &lt;p&gt;Please let me know if this works for you, or if you have any
3134 problems. We gather on the IRC channel
3135 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
3136 irc.debian.org and the
3137 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
3138 mailing list&lt;/a&gt;.&lt;/p&gt;
3139
3140 &lt;p&gt;Once you get your freedombox operational, you can visit
3141 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
3142 welcome screen (dead end - do not be surprised if you are unable to
3143 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
3144 to look at the rest of plinth. The default user is &#39;admin&#39; and the
3145 default password is &#39;secret&#39;.&lt;/p&gt;
3146 </description>
3147 </item>
3148
3149 <item>
3150 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
3151 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3152 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3153 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3154 <description>&lt;p&gt;Earlier, I reported about
3155 &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
3156 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3157 told by IBM that the original disk should be thrown away. And as
3158 there no longer was a problem if I bricked the firmware, I decided
3159 today to try to install Intel firmware to replace the Lenovo firmware
3160 currently on the disk.&lt;/p&gt;
3161
3162 &lt;p&gt;I searched the Intel site for firmware, and found
3163 &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;
3164 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3165 according to the site should contain the latest firmware for SSD
3166 disks. I inserted the broken disk in one of my spare laptops and
3167 booted the ISO from a USB stick. The disk was recognized, but the
3168 program claimed the newest firmware already were installed and refused
3169 to insert any Intel firmware. So no change, and the disk is still
3170 unable to handle write load. :( I guess the only way to get them
3171 working would be if Lenovo releases new firmware. No idea how likely
3172 that is. Anyway, just blogging about this test for completeness. I
3173 got a working Samsung disk, and see no point in spending more time on
3174 the broken disks.&lt;/p&gt;
3175 </description>
3176 </item>
3177
3178 <item>
3179 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3180 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3181 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3182 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3183 <description>&lt;p&gt;Today I switched to
3184 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3185 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3186 my new Thinkpad X230, which was delivered with an
3187 &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
3188 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3189 sustained writes. My hardware supplier have been very forthcoming in
3190 trying to find a solution, and after first trying with another
3191 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3192 disk instead to fix it once and for all. The Samsung disk survived
3193 the installation of Debian with encrypted disks (filling the disk with
3194 random data during installation killed the first two), and I thus
3195 decided to trust it with my data. I have installed it as a Debian Edu
3196 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3197 server at home using Kerberos and LDAP, and will use it as my work
3198 station from now on.&lt;/p&gt;
3199
3200 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3201 Debian Wheezy default installation need to be tuned a bit to increase
3202 performance and increase life time of the disk. The Linux kernel and
3203 user space applications do not yet adjust automatically to such
3204 environment. To make it easier for my self, I created a draft Debian
3205 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3206 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3207 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3208 is set up to adjust the setup of the machine by just installing the
3209 package. If there is any non-SSD disk in the machine, the package
3210 will refuse to install, as I did not try to write any logic to sort
3211 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3212
3213 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3214 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3215 where I set up the machine with one large encrypted partition (in
3216 addition to /boot), put LVM on top of this and set up partitions on
3217 top of this again. See the README file in the package source for the
3218 references I used to pick the settings. At the moment these
3219 parameters are tuned:&lt;/p&gt;
3220
3221 &lt;ul&gt;
3222
3223 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3224 (adding discard to /etc/crypttab)&lt;/li&gt;
3225
3226 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3227 this case a cryptsetup partition) by changing issue_discards from
3228 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3229
3230 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3231 systems.&lt;/li&gt;
3232
3233 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3234 /etc/fstab.&lt;/li&gt;
3235
3236 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3237
3238 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3239 cron.daily).&lt;/li&gt;
3240
3241 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3242 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3243
3244 &lt;/ul&gt;
3245
3246 &lt;p&gt;During installation, I cancelled the part where the installer fill
3247 the disk with random data, as this would kill the SSD performance for
3248 little gain. My goal with the encrypted file system is to ensure
3249 those stealing my laptop end up with a brick and not a working
3250 computer. I have no hope in keeping the really resourceful people
3251 from getting the data on the disk (see
3252 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3253 Thus I concluded that adding the discard option to crypttab is the
3254 right thing to do.&lt;/p&gt;
3255
3256 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3257 it for SSD, but others recommended deadline and a benchmark I found
3258 indicated that deadline might be better for interactive use.&lt;/p&gt;
3259
3260 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3261 and ext4, but read that it would give a performance hit ever time a
3262 file is removed, and thought it best to that that slowdown once a day
3263 instead of during my work.&lt;/p&gt;
3264
3265 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3266 this is already done by Debian Edu.&lt;/p&gt;
3267
3268 &lt;p&gt;I have not yet started on the user space tuning. I expect
3269 iceweasel need some tuning, and perhaps other applications too, but
3270 have not yet had time to investigate those parts.&lt;/p&gt;
3271
3272 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3273 there.&lt;/p&gt;
3274
3275 &lt;p&gt;As for the answer to the question in the title of this blog post,
3276 as far as I know, the only solution I know about is to replace the
3277 disk. It might be possible to flash it with Intel firmware instead of
3278 the Lenovo firmware. But I have not tried and did not want to do so
3279 without approval from Lenovo as I wanted to keep the warranty on the
3280 disk until a solution was found and they wanted the broken disks
3281 back.&lt;/p&gt;
3282 </description>
3283 </item>
3284
3285 <item>
3286 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3287 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3288 <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>
3289 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3290 <description>&lt;p&gt;A few days ago, I wrote about
3291 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3292 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3293 was dying during installation because it is unable to cope with
3294 sustained write. My supplier is in contact with
3295 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3296 replacement disk to try to fix the problem. They decided to send an
3297 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3298
3299 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3300 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3301 same firmware version as the original. This time my hope raised
3302 slightly as the installation progressed, as the original disk used to
3303 die after 4-7% of the disk was written to, while this time it kept
3304 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3305 died again and I was back on square one. I still do not have a new
3306 laptop with a disk I can trust. I can not live with a disk that might
3307 lock up when I download a new
3308 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3309 other large files. I look forward to hearing from my supplier with
3310 the next proposal from Lenovo.&lt;/p&gt;
3311
3312 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3313 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3314 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3315 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3316 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3317 P/N 45N8295, P0C38732.&lt;/p&gt;
3318
3319 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3320 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3321 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3322 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3323 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3324 P/N 45N8295, P0C38732.&lt;/p&gt;
3325
3326 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3327 SA, date and WNPP values. Mentioning all the details here in case
3328 someone is able to use the information to find a way to identify the
3329 failing disk among working ones (if any such working disk actually
3330 exist).&lt;/p&gt;
3331 </description>
3332 </item>
3333
3334 <item>
3335 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3336 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3337 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3338 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3339 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3340 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3341 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3342 member assosiation NUUG&lt;/a&gt; and
3343 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3344 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3345 Bitraf&lt;/a&gt;.&lt;/p&gt;
3346
3347 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3348 welcome, and there is no fee to participate. There is on the other
3349 hand limited space, and only room for 30 people. Please put your name
3350 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3351 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3352 </description>
3353 </item>
3354
3355 <item>
3356 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3357 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3358 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3359 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3360 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3361 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3362 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3363 time to spend on it, and it took a while to find a model I believe
3364 will do the job, but two days ago the replacement finally arrived. I
3365 ended up picking a
3366 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3367 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3368 a roaming workstation, and it seemed to work flawlessly. But my
3369 second installation with encrypted disk was not as successful. More
3370 on that below.&lt;/p&gt;
3371
3372 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3373 important requirements (robust and with a good keyboard) are never
3374 listed in the feature list. But I did get good help from the search
3375 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3376 allowed me to limit the list of interesting laptops based on my other
3377 requirements. A bit surprising that SSD disk are not disks according
3378 to that search interface, so I had to drop specifying the number of
3379 disks from my search parameters. I also asked around among friends to
3380 get their impression on keyboards and robustness.&lt;/p&gt;
3381
3382 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3383 X41. I am not quite convinced about the keyboard, as it is
3384 significantly wider than my old keyboard, and I have to stretch my
3385 hand a lot more to reach the edges. But the key response is fairly
3386 good and the individual key shape is fairly easy to handle, so I hope
3387 I will get used to it. My old X40 was starting to fail, and I really
3388 needed a new laptop now. :)&lt;/p&gt;
3389
3390 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3391 visit to the BIOS during boot it disable it.&lt;/p&gt;
3392
3393 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3394 lock up during load. And this happen when installing Debian Wheezy
3395 with encrypted disk, while the disk is being filled with random data.
3396 I also tested to install Ubuntu Raring, and it happen there too if I
3397 reenable the code to fill the disk with random data (it is disabled by
3398 default in Ubuntu). And the bug with is already known. It was
3399 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3400 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3401 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3402 kernel developers as
3403 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3404 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3405 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3406 Lenovo forums, both for
3407 &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
3408 2012-11-10&lt;/a&gt; and for
3409 &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
3410 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3411 reports state that the disk lock up during use if many writes are done
3412 on the disk, so it is much no use to work around the installation
3413 problem and end up with a computer that can lock up at any moment.
3414 There is even a
3415 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3416 available&lt;/a&gt; that will lock up the hard drive after running a few
3417 minutes by writing to a file.&lt;/p&gt;
3418
3419 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3420 contacting PCHELP Norway (request 01D1FDP) which handle support
3421 requests for Lenovo, his first suggestion was to upgrade the disk
3422 firmware. Unfortunately there is no newer firmware available from
3423 Lenovo, as my disk already have the most recent one (version LF1i). I
3424 hope to hear more from him today and hope the problem can be
3425 fixed. :)&lt;/p&gt;
3426 </description>
3427 </item>
3428
3429 <item>
3430 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3431 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3432 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3433 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3434 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3435 trusty old Thinkpad X41. Unfortunately I did not have much time to
3436 spend on it, but today the replacement finally arrived. I ended up
3437 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3438 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3439 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3440 this, it is installing what I hope will be a more final installation,
3441 with a encrypted hard drive to ensure any dope head stealing it end up
3442 with an expencive door stop.&lt;/p&gt;
3443
3444 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3445 important requirements (robust and with a good keyboard) are never
3446 listed in the feature list. But I did get good help from the search
3447 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3448 allowed me to limit the list of interesting laptops based on my other
3449 requirements. A bit surprising that SSD disk are not disks, so I had
3450 to drop number of disks from my search parameters.&lt;/p&gt;
3451
3452 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3453 wider than my old keyboard, and I have to stretch my hand a lot more
3454 to reach the edges. But the key response is fairly good and the
3455 individual key shape is fairly easy to handle, so I hope I will get
3456 used to it. My old X40 was starting to fail, and I really needed a
3457 new laptop now. :)&lt;/p&gt;
3458
3459 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3460 </description>
3461 </item>
3462
3463 <item>
3464 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3465 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3466 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3467 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3468 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3469 perfectly capable of, and I have to do it manually to get things
3470 working. One such task is to find out what firmware packages are
3471 needed to get the hardware on my computer working. Most often this
3472 affect the wifi card, but some times it even affect the RAID
3473 controller or the ethernet card. Today I pushed version 0.4 of the
3474 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3475 including a new script isenkram-autoinstall-firmware handling the
3476 process of asking all the loaded kernel modules what firmware files
3477 they want, find debian packages providing these files and install the
3478 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3479
3480 &lt;p&gt;&lt;pre&gt;
3481 # isenkram-autoinstall-firmware
3482 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3483 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3484 info: locating packages with the requested firmware files
3485 info: Updating APT sources after adding non-free APT source
3486 info: trying to install firmware-ipw2x00
3487 firmware-ipw2x00
3488 firmware-ipw2x00
3489 Preconfiguring packages ...
3490 Selecting previously deselected package firmware-ipw2x00.
3491 (Reading database ... 259727 files and directories currently installed.)
3492 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3493 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3494 #
3495 &lt;/pre&gt;&lt;/p&gt;
3496
3497 &lt;p&gt;When all the requested firmware is present, a simple message is
3498 printed instead:&lt;/p&gt;
3499
3500 &lt;p&gt;&lt;pre&gt;
3501 # isenkram-autoinstall-firmware
3502 info: did not find any firmware files requested by loaded kernel modules. exiting
3503 #
3504 &lt;/pre&gt;&lt;/p&gt;
3505
3506 &lt;p&gt;It could use some polish, but it is already working well and saving
3507 me some time when setting up new machines. :)&lt;/p&gt;
3508
3509 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3510 kernel modules, and look up each one of them using modinfo, to find
3511 the firmware files listed in the module meta-information. Next, it
3512 download the Contents file from a nearby APT mirror, and search for
3513 the firmware files in this file to locate the package with the
3514 requested firmware file. If the package is in the non-free section, a
3515 non-free APT source is added and the package is installed using
3516 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3517 machine.&lt;/p&gt;
3518
3519 &lt;p&gt;I hope someone find time to implement a more polished version of
3520 this script as part of the hw-detect debian-installer module, to
3521 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3522 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3523 firmware during a PXE install when the packages already are available
3524 from the nearby Debian mirror.&lt;/p&gt;
3525 </description>
3526 </item>
3527
3528 <item>
3529 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3530 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3531 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3532 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3533 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3534 the screen just turn black when Linux boot, either during installation
3535 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3536 last few years, but only recently understood the cause. I&#39;ve seen it
3537 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3538 The reason seem to be in the wiring of some laptops. The system to
3539 control the screen background light is inverted, so when Linux try to
3540 turn the brightness fully on, it end up turning it off instead. I do
3541 not know which Linux drivers are affected, but this post is about the
3542 i915 driver used by the
3543 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3544 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3545
3546 &lt;p&gt;The problem can be worked around two ways. Either by adding
3547 i915.invert_brightness=1 as a kernel option, or by adding a file in
3548 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3549 option when it load the i915 kernel module. On Debian and Ubuntu, it
3550 can be done by running these commands as root:&lt;/p&gt;
3551
3552 &lt;pre&gt;
3553 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3554 update-initramfs -u -k all
3555 &lt;/pre&gt;
3556
3557 &lt;p&gt;Since March 2012 there is
3558 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3559 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3560 hardware have this problem, and get the driver to invert the
3561 brightness setting automatically. To use it, one need to add a row in
3562 &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
3563 intel_quirks array&lt;/a&gt; in the driver source
3564 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3565 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3566 number (vendor number 8086 is assumed) and subdevice vendor and device
3567 number.&lt;/p&gt;
3568
3569 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3570 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3571
3572 &lt;p&gt;&lt;pre&gt;
3573 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3574 3rd Gen Core processor Graphics Controller [8086:0156] \
3575 (rev 09) (prog-if 00 [VGA controller])
3576 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3577 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3578 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3579 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3580 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3581 Latency: 0
3582 Interrupt: pin A routed to IRQ 42
3583 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3584 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3585 Region 4: I/O ports at 4000 [size=64]
3586 Expansion ROM at &lt;unassigned&gt; [disabled]
3587 Capabilities: &lt;access denied&gt;
3588 Kernel driver in use: i915
3589 &lt;/pre&gt;&lt;/p&gt;
3590
3591 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3592
3593 &lt;p&gt;&lt;pre&gt;
3594 struct intel_quirk intel_quirks[] = {
3595 ...
3596 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3597 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3598 ...
3599 }
3600 &lt;/pre&gt;&lt;/p&gt;
3601
3602 &lt;p&gt;According to the kernel module instructions (as seen using
3603 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3604 invert_brightness flag should be sent to the
3605 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3606 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3607 developers. But my email about the laptop sent 2013-06-03 have not
3608 yet shown up in
3609 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3610 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3611 emails from non-subscribers. Because of this, I sent my patch also to
3612 the Debian bug tracking system instead as
3613 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3614 sure the patch is not lost.&lt;/p&gt;
3615
3616 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3617 with this problem working properly with Linux. If you use Gnome, your
3618 worries should be over at this point. But if you use KDE, there is
3619 something in KDE ignoring the invert_brightness setting and turning on
3620 the screen during login. I&#39;ve reported it to Debian as
3621 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3622 have no idea yet how to figure out exactly what subsystem is doing
3623 this. Perhaps you can help? Perhaps you know what the Gnome
3624 developers did to handle this, and this can give a clue to the KDE
3625 developers? Or you know where in KDE the screen brightness is changed
3626 during login? If so, please update the BTS report (or get in touch if
3627 you do not know how to update BTS).&lt;/p&gt;
3628
3629 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3630 acpi_backlight=vendor, to disable ACPI backlight support completely,
3631 as the ACPI information on the machine is trash and it is better to
3632 leave it to the intel video driver to control the screen
3633 backlight.&lt;/p&gt;
3634 </description>
3635 </item>
3636
3637 <item>
3638 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3639 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3640 <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>
3641 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3642 <description>&lt;p&gt;Two days ago, I asked
3643 &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
3644 I could install Linux on a Packard Bell EasyNote LV computer
3645 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3646 with the obstacles put in the way of Linux users on a laptop with UEFI
3647 and Windows 8.&lt;/p&gt;
3648
3649 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3650 secure booting or fast boot. I suspect fast boot was the problem,
3651 causing the firmware to boot directly from HD without considering any
3652 key presses and alternative devices, but do not know UEFI settings
3653 enough to tell.&lt;/p&gt;
3654
3655 &lt;p&gt;There is no way to install Linux on the machine in question without
3656 opening the box and disconnecting the hard drive! This is as far as I
3657 can tell, the only way to get access to the firmware setup menu
3658 without accepting the Windows 8 license agreement. I am told (and
3659 found description on how to) that it is possible to configure the
3660 firmware setup once booted into Windows 8. But as I believe the terms
3661 of that agreement are completely unacceptable, accepting the license
3662 was never an alternative. I do not enter agreements I do not intend
3663 to follow.&lt;/p&gt;
3664
3665 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3666 waste many hours on this, but luckily there was a way to get it to
3667 work. But I would not recommend it to anyone planning to run Linux on
3668 it, and I have become sceptical to Windows 8 certified laptops. Is
3669 this the way Linux will be forced out of the market place, by making
3670 it close to impossible for &quot;normal&quot; users to install Linux without
3671 accepting the Microsoft Windows license terms? Or at least not
3672 without risking to loose the warranty?&lt;/p&gt;
3673
3674 &lt;p&gt;I&#39;ve updated the
3675 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3676 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3677 do not have to struggle as much as I did to get Linux into the
3678 machine.&lt;/p&gt;
3679
3680 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3681 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3682 </description>
3683 </item>
3684
3685 <item>
3686 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3687 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3688 <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>
3689 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3690 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3691 new laptops for my parents and a few others. I bought Packard Bell
3692 Easynote LV to run Kubuntu on and use as their home computer. But I
3693 am completely unable to figure out how to install Linux on it. The
3694 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3695 instead of a BIOS to boot.&lt;/p&gt;
3696
3697 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3698 to get it to boot the Linux installer from my USB stick. I have yet
3699 to try the DVD install, and still hope it will work. when I turn on
3700 the computer, there is no information on what buttons to press to get
3701 the normal boot menu. I expect to get some boot menu to select PXE or
3702 USB stick booting. When booting, it first ask for the language to
3703 use, then for some regional settings, and finally if I will accept the
3704 Windows 8 terms of use. As these terms are completely unacceptable to
3705 me, I have no other choice but to turn off the computer and try again
3706 to get it to boot the Linux installer.&lt;/p&gt;
3707
3708 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3709 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3710 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3711 installed on this machine, please get in touch or update that wiki
3712 page. If I can&#39;t find a way to install Linux, I will have to return
3713 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3714
3715 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3716 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3717 on new Laptops?&lt;/p&gt;
3718 </description>
3719 </item>
3720
3721 <item>
3722 <title>How to transform a Debian based system to a Debian Edu installation</title>
3723 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3724 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3725 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3726 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3727 an operating system based on Debian intended for use in schools. It
3728 contain a turn-key solution for the computer network provided to
3729 pupils in the primary schools. It provide both the central server,
3730 network boot servers and desktop environments with heaps of
3731 educational software. The project was founded almost 12 years ago,
3732 2001-07-02. If you want to support the project, which is in need for
3733 cash to fund developer gatherings and other project related activity,
3734 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3735 donate some money&lt;/a&gt;.
3736
3737 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3738 lists and elsewhere, is the question on how to transform a Debian or
3739 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3740 hard, and last week I wrote a script to replicate the steps done by
3741 the Debian Edu installer.&lt;/p&gt;
3742
3743 &lt;p&gt;The script,
3744 &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;
3745 in the debian-edu-config package, will go through these six steps and
3746 transform an existing Debian Wheezy or Ubuntu (untested) installation
3747 into a Debian Edu Workstation:&lt;/p&gt;
3748
3749 &lt;ol&gt;
3750
3751 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3752 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3753 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3754 our configuration.&lt;/li&gt;
3755 &lt;li&gt;Preseed debconf database with profile setup in
3756 /etc/debian-edu/config, and run tasksel to install packages
3757 according to the profile specified in the config above,
3758 overriding some of the Debian automation machinery.&lt;/li&gt;
3759 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3760 that could not be done using preseeding.&lt;/li&gt;
3761 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3762
3763 &lt;/ol&gt;
3764
3765 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3766 replicated like this. Disk partitioning and LVM setup, for example.
3767 So this script just assume there is enough disk space to install all
3768 the needed packages.&lt;/p&gt;
3769
3770 &lt;p&gt;The script was created to help a Debian Edu student working on
3771 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3772 Debian Edu client, and using it he can take the existing
3773 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3774 transform it into a fully functioning Debian Edu Workstation (or
3775 Roaming Workstation, or whatever :).&lt;/p&gt;
3776
3777 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3778 If a LXDE based Roaming workstation is wanted instead, modify the
3779 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3780
3781 &lt;p&gt;&lt;pre&gt;
3782 PROFILE=&quot;Roaming-Workstation&quot;
3783 DESKTOP=&quot;lxde&quot;
3784 &lt;/pre&gt;&lt;/p&gt;
3785
3786 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3787 the cloud, by starting with a virtual Debian installation at some
3788 virtual hosting service and setting up all the services on first
3789 boot.&lt;/p&gt;
3790 </description>
3791 </item>
3792
3793 <item>
3794 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3795 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3796 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3797 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3798 <description>&lt;P&gt;In January,
3799 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3800 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3801 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3802 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3803 marvellous construction system from Denmark. We also created
3804 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3805 a place to take notes and write down our plans and hopes. And several
3806 people showed up to help. I was very happy to see the effect of my
3807 call. Since the small start, we have a debtags tag
3808 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3809 tag for LEGO related packages, and now count 10 packages related to
3810 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3811
3812 &lt;p&gt;&lt;table&gt;
3813 &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;
3814 &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;
3815 &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;
3816 &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;
3817 &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;
3818 &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;
3819 &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;
3820 &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;
3821 &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;
3822 &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;
3823 &lt;/table&gt;&lt;/p&gt;
3824
3825 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3826 currently available in Jessie/testing. leocad is so far only
3827 available in experimental.&lt;/p&gt;
3828
3829 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3830 adding the rest of the great free software tools available on Linux
3831 for LEGO designers.&lt;/p&gt;
3832 </description>
3833 </item>
3834
3835 <item>
3836 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3837 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3838 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3839 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3840 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3841 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3842 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3843 Debian release, and I expect to move my machines at home over to it fairly
3844 soon.&lt;/p&gt;
3845
3846 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3847 in particular make me very happy to see included. The
3848 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3849 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3850 included for the first time. Alongside similar programs like
3851 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3852 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3853 it allow for visual programming where syntax errors can not happen,
3854 and a friendly programming environment for learning to control the
3855 computer. Scratch will also be included in the next release of Debian
3856 Edu.&lt;/a&gt;
3857
3858 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3859 Edu/Skolelinux release too. The
3860 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3861 alpha release&lt;/a&gt; went out last week, and the next should soon
3862 follow.&lt;p&gt;
3863 </description>
3864 </item>
3865
3866 <item>
3867 <title>Isenkram 0.2 finally in the Debian archive</title>
3868 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3869 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3870 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3871 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3872 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3873 for many months. I uploaded it to the Debian experimental suite
3874 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3875
3876 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3877 install to work with a pluggable hardware device. The suggestion pop
3878 up when the device is plugged in. For example if a Lego Mindstorm NXT
3879 is inserted, it will suggest to install the program needed to program
3880 the NXT controller. Give it a go, and report bugs and suggestions to
3881 BTS. :)&lt;/p&gt;
3882 </description>
3883 </item>
3884
3885 <item>
3886 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3887 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3888 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3889 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3890 <description>&lt;p&gt;My
3891 &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
3892 bitcoin related blog post&lt;/a&gt; mentioned that the new
3893 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3894 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3895 2013-01-19, and have been available in unstable since then. It was
3896 automatically copied to Ubuntu, and is available in their Raring
3897 version too.&lt;/p&gt;
3898
3899 &lt;p&gt;But there is a strange problem with the build that block this new
3900 version from being available on the i386 and kfreebsd-i386
3901 architectures. For some strange reason, the autobuilders in Debian
3902 for these architectures fail to run the test suite on these
3903 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3904 We are so far unable to reproduce it when building it manually, and
3905 no-one have been able to propose a fix. If you got an idea what is
3906 failing, please let us know via the BTS.&lt;/p&gt;
3907
3908 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3909 I often run low on disk space, is the fact that the client will exit
3910 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3911 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3912 it. :)&lt;/p&gt;
3913
3914 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3915 activities, please send Bitcoin donations to my address
3916 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3917 </description>
3918 </item>
3919
3920 <item>
3921 <title>Welcome to the world, Isenkram!</title>
3922 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3923 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3924 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3925 <description>&lt;p&gt;Yesterday, I
3926 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3927 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3928 pluggable hardware devices, which I
3929 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3930 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3931 up, and caused me to really want to to open up the development to more
3932 people. But before I did this, I want to come up with a sensible name
3933 for this project. Today I finally decided on a new name, and I have
3934 renamed the project from hw-support-handler to this new name. In the
3935 process, I moved the source to git and made it available as a
3936 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3937 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3938 To fetch and build the latest version of the source, use&lt;/p&gt;
3939
3940 &lt;pre&gt;
3941 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3942 cd isenkram &amp;&amp; git-buildpackage -us -uc
3943 &lt;/pre&gt;
3944
3945 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3946 want to hack on the source or improve the package, please go ahead.
3947 But please talk to me first on IRC or via email before you do major
3948 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3949
3950 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3951 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3952 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3953 the German word eisenkram, for those that are familiar with that
3954 word.&lt;/p&gt;
3955
3956 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3957 instructions, to avoid confusing people with an error from the signing
3958 process.&lt;/p&gt;
3959
3960 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3961 clone argument to avoid the need for authentication.&lt;/p&gt;
3962 </description>
3963 </item>
3964
3965 <item>
3966 <title>First prototype ready making hardware easier to use in Debian</title>
3967 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3969 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3970 <description>&lt;p&gt;Early this month I set out to try to
3971 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3972 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3973 prototype is working, and it is ready for a larger audience. To test
3974 it, fetch the
3975 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3976 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3977 package. You might have to log out and in again activate the
3978 autostart script.&lt;/p&gt;
3979
3980 &lt;p&gt;The design is simple:&lt;/p&gt;
3981
3982 &lt;ul&gt;
3983
3984 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3985 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3986
3987 &lt;li&gt;This program listen for kernel events about new hardware (directly
3988 from the kernel like udev does), not using HAL dbus events as I
3989 initially did.&lt;/li&gt;
3990
3991 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3992 the APT database, a database
3993 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3994 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3995
3996 &lt;li&gt;If a package is mapped to the hardware in question, the package
3997 isn&#39;t installed yet and this is the first time the hardware was
3998 plugged in, show a desktop notification suggesting to install the
3999 package or packages.&lt;/li&gt;
4000
4001 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
4002 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
4003
4004 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
4005 package while showing progress information in a window.&lt;/li&gt;
4006
4007 &lt;/ul&gt;
4008
4009 &lt;p&gt;I still need to come up with a better name for the system. Here
4010 are some screen shots showing the prototype in action. First the
4011 notification, then the password request, and finally the request to
4012 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
4013
4014 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
4015 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
4016 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
4017 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
4018 &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;
4019
4020 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
4021 is already useful. The database of hardware to package mappings also
4022 need more work. It is currently compatible with the Ubuntu way of
4023 storing such information in the package control file, but could be
4024 changed to use other formats instead or in addition to the current
4025 method. I&#39;ve dropped the use of discover for this mapping, as the
4026 modalias approach is more flexible and easier to use on Linux as long
4027 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
4028
4029 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
4030 here is the command required to check out and build the source: Use
4031 &#39;&lt;tt&gt;svn checkout
4032 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4033 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
4034 devscripts package.&lt;/p&gt;
4035
4036 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
4037 renamed to Isenkram and the source moved from the Debian Edu
4038 subversion repository to a Debian collab-maint git repository. See
4039 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
4040 instructions&lt;/a&gt; for details.&lt;/p&gt;
4041 </description>
4042 </item>
4043
4044 <item>
4045 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
4046 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
4047 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
4048 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
4049 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
4050 suddenly in bed. With a quiet whimper, it went completely quiet and
4051 black. The power button was no longer able to turn it on. It was a
4052 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4053 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4054 Compaq I had before that. Now I need to find a replacement. To keep
4055 going during Christmas, I moved the one year old SSD disk to my old
4056 X40 where it fitted (only one I had left that could use it), but it is
4057 not a durable solution.
4058
4059 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
4060 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
4061
4062 &lt;ul&gt;
4063
4064 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
4065 than A4).&lt;/li&gt;
4066 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
4067 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
4068 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
4069 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
4070 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
4071 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
4072 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
4073 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
4074 size).&lt;/li&gt;
4075 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
4076 X.org packages.&lt;/li&gt;
4077 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
4078 the time).
4079
4080 &lt;/ul&gt;
4081
4082 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
4083 list. The reason is simply that the specifications on laptops the
4084 last 10-15 years have been sufficient for my needs, and I have to look
4085 at other features to choose my laptop. But are there still made as
4086 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4087 robust, and Thinkpads seem to be heading in the wrong direction since
4088 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
4089 still be useful.&lt;/p&gt;
4090
4091 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
4092 external keyboard? I&#39;ll have to check the
4093 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
4094 well-supported laptops, or perhaps just buy one preinstalled from one
4095 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
4096 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
4097 </description>
4098 </item>
4099
4100 <item>
4101 <title>How to find a browser plugin supporting a given MIME type</title>
4102 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
4103 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
4104 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
4105 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
4106 install to get support for a given MIME type. Thanks to
4107 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
4108 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
4109 Unfortunately, not very many packages provide the needed meta
4110 information, Anyway, here is a small script to look up all browser
4111 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
4112
4113 &lt;pre&gt;
4114 #!/usr/bin/python
4115 import sys
4116 import apt
4117 def pkgs_handling_mimetype(mimetype):
4118 cache = apt.Cache()
4119 cache.open(None)
4120 thepkgs = []
4121 for pkg in cache:
4122 version = pkg.candidate
4123 if version is None:
4124 version = pkg.installed
4125 if version is None:
4126 continue
4127 record = version.record
4128 if not record.has_key(&#39;Npp-MimeType&#39;):
4129 continue
4130 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
4131 for t in mime_types:
4132 t = t.rstrip().strip()
4133 if t == mimetype:
4134 thepkgs.append(pkg.name)
4135 return thepkgs
4136 mimetype = &quot;audio/ogg&quot;
4137 if 1 &lt; len(sys.argv):
4138 mimetype = sys.argv[1]
4139 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
4140 for pkg in pkgs_handling_mimetype(mimetype):
4141 print &quot; %s&quot; %pkg
4142 &lt;/pre&gt;
4143
4144 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
4145
4146 &lt;pre&gt;
4147 % ./apt-find-browserplug-for-mimetype
4148 Browser plugin packages supporting audio/ogg:
4149 gecko-mediaplayer
4150 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4151 Browser plugin packages supporting application/x-shockwave-flash:
4152 browser-plugin-gnash
4153 %
4154 &lt;/pre&gt;
4155
4156 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4157 itself to query for plugins and propose to install the needed
4158 packages. It would be great if Debian supported such feature too. Is
4159 anyone working on adding it?&lt;/p&gt;
4160
4161 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4162 request for icweasel support for this feature is
4163 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4164 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4165 of manpower and wish for a different design is the reason thus feature
4166 is not yet in iceweasel from Debian.&lt;/p&gt;
4167 </description>
4168 </item>
4169
4170 <item>
4171 <title>What is the most supported MIME type in Debian?</title>
4172 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4173 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4174 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4175 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4176 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4177 proposal to make it possible for a Desktop application to propose to
4178 the user some package to install to gain support for a given MIME
4179 type, font, library etc. that is currently missing. With such
4180 mechanism in place, it would be possible for the desktop to
4181 automatically propose and install leocad if some LDraw file is
4182 downloaded by the browser.&lt;/p&gt;
4183
4184 &lt;p&gt;To get some idea about the current content of the archive, I decided
4185 to write a simple program to extract all .desktop files from the
4186 Debian archive and look up the claimed MIME support there. The result
4187 can be found on the
4188 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4189 site&lt;/a&gt;. Using the collected information, it become possible to
4190 answer the question in the title. Here are the 20 most supported MIME
4191 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4192 The complete list is available from the link above.&lt;/p&gt;
4193
4194 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4195
4196 &lt;pre&gt;
4197 count MIME type
4198 ----- -----------------------
4199 32 text/plain
4200 30 audio/mpeg
4201 29 image/png
4202 28 image/jpeg
4203 27 application/ogg
4204 26 audio/x-mp3
4205 25 image/tiff
4206 25 image/gif
4207 22 image/bmp
4208 22 audio/x-wav
4209 20 audio/x-flac
4210 19 audio/x-mpegurl
4211 18 video/x-ms-asf
4212 18 audio/x-musepack
4213 18 audio/x-mpeg
4214 18 application/x-ogg
4215 17 video/mpeg
4216 17 audio/x-scpls
4217 17 audio/ogg
4218 16 video/x-ms-wmv
4219 &lt;/pre&gt;
4220
4221 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4222
4223 &lt;pre&gt;
4224 count MIME type
4225 ----- -----------------------
4226 33 text/plain
4227 32 image/png
4228 32 image/jpeg
4229 29 audio/mpeg
4230 27 image/gif
4231 26 image/tiff
4232 26 application/ogg
4233 25 audio/x-mp3
4234 22 image/bmp
4235 21 audio/x-wav
4236 19 audio/x-mpegurl
4237 19 audio/x-mpeg
4238 18 video/mpeg
4239 18 audio/x-scpls
4240 18 audio/x-flac
4241 18 application/x-ogg
4242 17 video/x-ms-asf
4243 17 text/html
4244 17 audio/x-musepack
4245 16 image/x-xbitmap
4246 &lt;/pre&gt;
4247
4248 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4249
4250 &lt;pre&gt;
4251 count MIME type
4252 ----- -----------------------
4253 31 text/plain
4254 31 image/png
4255 31 image/jpeg
4256 29 audio/mpeg
4257 28 application/ogg
4258 27 image/gif
4259 26 image/tiff
4260 26 audio/x-mp3
4261 23 audio/x-wav
4262 22 image/bmp
4263 21 audio/x-flac
4264 20 audio/x-mpegurl
4265 19 audio/x-mpeg
4266 18 video/x-ms-asf
4267 18 video/mpeg
4268 18 audio/x-scpls
4269 18 application/x-ogg
4270 17 audio/x-musepack
4271 16 video/x-ms-wmv
4272 16 video/x-msvideo
4273 &lt;/pre&gt;
4274
4275 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4276 information mentioned in DEP-11. I have not yet had time to look at
4277 it, but hope the PackageKit people in Debian are on top of these
4278 issues.&lt;/p&gt;
4279
4280 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4281 discovering a typo in my script.&lt;/p&gt;
4282 </description>
4283 </item>
4284
4285 <item>
4286 <title>Using modalias info to find packages handling my hardware</title>
4287 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4288 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4289 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4290 <description>&lt;p&gt;Yesterday, I wrote about the
4291 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4292 values provided by the Linux kernel&lt;/a&gt; following my hope for
4293 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4294 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4295 modalias values attached to package names can be used to map packages
4296 to hardware. This allow the system to look up and suggest relevant
4297 packages when I plug in some new hardware into my machine, and replace
4298 discover and discover-data as the database used to map hardware to
4299 packages.&lt;/p&gt;
4300
4301 &lt;p&gt;I create a modaliases file with entries like the following,
4302 containing package name, kernel module name (if relevant, otherwise
4303 the package name) and globs matching the relevant hardware
4304 modalias.&lt;/p&gt;
4305
4306 &lt;p&gt;&lt;blockquote&gt;
4307 Package: package-name
4308 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4309 &lt;/blockquote&gt;&lt;/p&gt;
4310
4311 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4312 for a given modalias value using this file.&lt;/p&gt;
4313
4314 &lt;p&gt;An entry like this would suggest the video and picture application
4315 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4316
4317 &lt;p&gt;&lt;blockquote&gt;
4318 Package: cheese
4319 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4320 &lt;/blockquote&gt;&lt;/p&gt;
4321
4322 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4323 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4324
4325 &lt;p&gt;&lt;blockquote&gt;
4326 Package: pcmciautils
4327 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4328 &lt;/blockquote&gt;&lt;/p&gt;
4329
4330 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4331 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4332
4333 &lt;p&gt;&lt;blockquote&gt;
4334 Package: colorhug-client
4335 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4336 &lt;/blockquote&gt;&lt;/p&gt;
4337
4338 &lt;p&gt;I believe the format is compatible with the format of the Packages
4339 file in the Debian archive. Ubuntu already uses their Packages file
4340 to store their mappings from packages to hardware.&lt;/p&gt;
4341
4342 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4343 announce the hardware it support in a way my prototype understand.
4344 This allow those publishing packages in an APT source outside the
4345 Debian archive as well as those backporting packages to make sure the
4346 hardware mapping are included in the package meta information. I&#39;ve
4347 tested such header in the pymissile package, and its modalias mapping
4348 is working as it should with my prototype. It even made it to Ubuntu
4349 Raring.&lt;/p&gt;
4350
4351 &lt;p&gt;To test if it was possible to look up supported hardware using only
4352 the shell tools available in the Debian installer, I wrote a shell
4353 implementation of the lookup code. The idea is to create files for
4354 each modalias and let the shell do the matching. Please check out and
4355 try the
4356 &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;
4357 shell script. It run without any extra dependencies and fetch the
4358 hardware mappings from the Debian archive and the subversion
4359 repository where I currently work on my prototype.&lt;/p&gt;
4360
4361 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4362 install yubikey-personalization:&lt;/p&gt;
4363
4364 &lt;p&gt;&lt;blockquote&gt;
4365 % ./hw-support-lookup
4366 &lt;br&gt;yubikey-personalization
4367 &lt;br&gt;%
4368 &lt;/blockquote&gt;&lt;/p&gt;
4369
4370 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4371 propose to install the pcmciautils package:&lt;/p&gt;
4372
4373 &lt;p&gt;&lt;blockquote&gt;
4374 % ./hw-support-lookup
4375 &lt;br&gt;pcmciautils
4376 &lt;br&gt;%
4377 &lt;/blockquote&gt;&lt;/p&gt;
4378
4379 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4380 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4381 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4382
4383 &lt;p&gt;It could be possible to generate several of the mappings between
4384 packages and hardware. One source would be to look at packages with
4385 kernel modules, ie packages with *.ko files in /lib/modules/, and
4386 extract their modalias information. Another would be to look at
4387 packages with udev rules, ie packages with files in
4388 /lib/udev/rules.d/, and extract their vendor/model information to
4389 generate a modalias matching rule. I have not tested any of these to
4390 see if it work.&lt;/p&gt;
4391
4392 &lt;p&gt;If you want to help implementing a system to let us propose what
4393 packages to install when new hardware is plugged into a Debian
4394 machine, please send me an email or talk to me on
4395 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4396 </description>
4397 </item>
4398
4399 <item>
4400 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4401 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4403 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4404 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4405 information, to find the packages that support a given piece of
4406 hardware, I refreshed my memory regarding modalias values, and decided
4407 to document the details. Here are my findings so far, also available
4408 in
4409 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4410 Debian Edu subversion repository&lt;/a&gt;:
4411
4412 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4413
4414 &lt;p&gt;This document try to explain what the different types of modalias
4415 values stands for. It is in part based on information from
4416 &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;,
4417 &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;,
4418 &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
4419 &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;.
4420
4421 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4422 this shell script:&lt;/p&gt;
4423
4424 &lt;pre&gt;
4425 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4426 &lt;/pre&gt;
4427
4428 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4429 using modinfo:&lt;/p&gt;
4430
4431 &lt;pre&gt;
4432 % /sbin/modinfo psmouse | grep alias:
4433 alias: serio:ty05pr*id*ex*
4434 alias: serio:ty01pr*id*ex*
4435 %
4436 &lt;/pre&gt;
4437
4438 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4439
4440 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4441 Bridge memory controller:&lt;/p&gt;
4442
4443 &lt;p&gt;&lt;blockquote&gt;
4444 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4445 &lt;/blockquote&gt;&lt;/p&gt;
4446
4447 &lt;p&gt;This represent these values:&lt;/p&gt;
4448
4449 &lt;pre&gt;
4450 v 00008086 (vendor)
4451 d 00002770 (device)
4452 sv 00001028 (subvendor)
4453 sd 000001AD (subdevice)
4454 bc 06 (bus class)
4455 sc 00 (bus subclass)
4456 i 00 (interface)
4457 &lt;/pre&gt;
4458
4459 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4460 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4461 0600. The 0600 class is a host bridge. Other useful bus values are
4462 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4463
4464 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4465 means.&lt;/p&gt;
4466
4467 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4468
4469 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4470 USB hub in a laptop:&lt;/p&gt;
4471
4472 &lt;p&gt;&lt;blockquote&gt;
4473 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4474 &lt;/blockquote&gt;&lt;/p&gt;
4475
4476 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4477
4478 &lt;pre&gt;
4479 v 1D6B (device vendor)
4480 p 0001 (device product)
4481 d 0206 (bcddevice)
4482 dc 09 (device class)
4483 dsc 00 (device subclass)
4484 dp 00 (device protocol)
4485 ic 09 (interface class)
4486 isc 00 (interface subclass)
4487 ip 00 (interface protocol)
4488 &lt;/pre&gt;
4489
4490 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4491 class is in the interface class section. For a simple USB web camera,
4492 these alias entries show up:&lt;/p&gt;
4493
4494 &lt;p&gt;&lt;blockquote&gt;
4495 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4496 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4497 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4498 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4499 &lt;/blockquote&gt;&lt;/p&gt;
4500
4501 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4502 camera), 0101 is audio control device and 0102 is audio streaming (aka
4503 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4504
4505 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4506
4507 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4508 receiver in a Thinkpad X40:&lt;/p&gt;
4509
4510 &lt;p&gt;&lt;blockquote&gt;
4511 acpi:IBM0071:PNP0511:
4512 &lt;/blockquote&gt;&lt;/p&gt;
4513
4514 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4515
4516 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4517
4518 &lt;p&gt;The DMI table contain lots of information about the computer case
4519 and model. This is an entry for a IBM Thinkpad X40, fetched from
4520 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4521
4522 &lt;p&gt;&lt;blockquote&gt;
4523 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4524 &lt;/blockquote&gt;&lt;/p&gt;
4525
4526 &lt;p&gt;The values present are&lt;/p&gt;
4527
4528 &lt;pre&gt;
4529 bvn IBM (BIOS vendor)
4530 bvr 1UETB6WW(1.66) (BIOS version)
4531 bd 06/15/2005 (BIOS date)
4532 svn IBM (system vendor)
4533 pn 2371H4G (product name)
4534 pvr ThinkPadX40 (product version)
4535 rvn IBM (board vendor)
4536 rn 2371H4G (board name)
4537 rvr NotAvailable (board version)
4538 cvn IBM (chassis vendor)
4539 ct 10 (chassis type)
4540 cvr NotAvailable (chassis version)
4541 &lt;/pre&gt;
4542
4543 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4544 found in the dmidecode source:&lt;/p&gt;
4545
4546 &lt;pre&gt;
4547 3 Desktop
4548 4 Low Profile Desktop
4549 5 Pizza Box
4550 6 Mini Tower
4551 7 Tower
4552 8 Portable
4553 9 Laptop
4554 10 Notebook
4555 11 Hand Held
4556 12 Docking Station
4557 13 All In One
4558 14 Sub Notebook
4559 15 Space-saving
4560 16 Lunch Box
4561 17 Main Server Chassis
4562 18 Expansion Chassis
4563 19 Sub Chassis
4564 20 Bus Expansion Chassis
4565 21 Peripheral Chassis
4566 22 RAID Chassis
4567 23 Rack Mount Chassis
4568 24 Sealed-case PC
4569 25 Multi-system
4570 26 CompactPCI
4571 27 AdvancedTCA
4572 28 Blade
4573 29 Blade Enclosing
4574 &lt;/pre&gt;
4575
4576 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4577 table. For example my home server is a tower, but the DMI modalias
4578 claim it is a desktop.&lt;/p&gt;
4579
4580 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4581
4582 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4583 test machine:&lt;/p&gt;
4584
4585 &lt;p&gt;&lt;blockquote&gt;
4586 serio:ty01pr00id00ex00
4587 &lt;/blockquote&gt;&lt;/p&gt;
4588
4589 &lt;p&gt;The values present are&lt;/p&gt;
4590
4591 &lt;pre&gt;
4592 ty 01 (type)
4593 pr 00 (prototype)
4594 id 00 (id)
4595 ex 00 (extra)
4596 &lt;/pre&gt;
4597
4598 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4599 the valid values are.&lt;/p&gt;
4600
4601 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4602
4603 &lt;p&gt;There are heaps of other modalias subtypes according to
4604 file2alias.c. There is the rest of the list from that source: amba,
4605 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4606 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4607 vmbus, x86cpu and zorro. I did not spend time documenting all of
4608 these, as they do not seem relevant for my intended use with mapping
4609 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4610
4611 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4612
4613 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4614 one can use the following shell script:&lt;/p&gt;
4615
4616 &lt;pre&gt;
4617 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4618 echo &quot;$id&quot; ; \
4619 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4620 done
4621 &lt;/pre&gt;
4622
4623 &lt;p&gt;The output can look like this (only the first few entries as the
4624 list is very long on my test machine):&lt;/p&gt;
4625
4626 &lt;pre&gt;
4627 acpi:ACPI0003:
4628 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4629 acpi:device:
4630 FATAL: Module acpi:device: not found.
4631 acpi:IBM0068:
4632 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4633 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4634 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4635 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4636 acpi:IBM0071:PNP0511:
4637 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4638 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4639 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4640 [...]
4641 &lt;/pre&gt;
4642
4643 &lt;p&gt;If you want to help implementing a system to let us propose what
4644 packages to install when new hardware is plugged into a Debian
4645 machine, please send me an email or talk to me on
4646 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4647
4648 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4649 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4650 in /sys/ with space in them.&lt;/p&gt;
4651 </description>
4652 </item>
4653
4654 <item>
4655 <title>Moved the pymissile Debian packaging to collab-maint</title>
4656 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4657 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4658 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4659 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4660 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4661 Launcher and updated the Debian package
4662 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4663 sure udev will fix the device permissions when it is plugged in. I
4664 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4665 hopefully make the package be proposed by jockey in Ubuntu when a user
4666 plug in his rocket launcher. In the process I moved the source to a
4667 git repository under collab-maint, to make it easier for any DD to
4668 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4669 is not very active, but the software still work for me even after five
4670 years of relative silence. The new git repository is not listed in
4671 the uploaded package yet, because I want to test the other changes a
4672 bit more before I upload the new version. If you want to check out
4673 the new version with a .desktop file included, visit the
4674 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4675 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4676 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4677 </description>
4678 </item>
4679
4680 <item>
4681 <title>Lets make hardware dongles easier to use in Debian</title>
4682 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4683 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4684 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4685 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4686 general, is that there is a great package management system with the
4687 ability to automatically install software packages by downloading them
4688 from the distribution mirrors, but no way to get it to automatically
4689 install the packages I need to use the hardware I plug into my
4690 machine. Even if the package to use it is easily available from the
4691 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4692 suggest to automatically install the python-nxt, nbc and t2n packages
4693 I need to talk to it. When I plug in a Yubikey, it could propose the
4694 yubikey-personalization package. The information required to do this
4695 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4696
4697 &lt;p&gt;Some years ago, I proposed to
4698 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4699 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4700 simple:
4701
4702 &lt;ul&gt;
4703
4704 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4705 starting when a user log in.&lt;/li&gt;
4706
4707 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4708 hardware is inserted into the computer.&lt;/li&gt;
4709
4710 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4711 database mapping to packages, and take note of any non-installed
4712 packages.&lt;/li&gt;
4713
4714 &lt;li&gt;Show a message to the user proposing to install the discovered
4715 package, and make it easy to install it.&lt;/li&gt;
4716
4717 &lt;/ul&gt;
4718
4719 &lt;p&gt;I am not sure what the best way to implement this is, but my
4720 initial idea was to use dbus events to discover new hardware, the
4721 discover database to find packages and
4722 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4723 packages.&lt;/p&gt;
4724
4725 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4726 draft package is now checked into
4727 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4728 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4729 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4730 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4731 the relevant packages in Debian, and uploaded a new version
4732 2.2013.01.09 to unstable. I also discovered that the current
4733 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4734 package in Debian no longer discovered any USB devices, because
4735 /proc/bus/usb/devices is no longer present. I ported it to use
4736 libusb as a fall back option to get it working. The fixed package
4737 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4738 because of the freeze).&lt;/p&gt;
4739
4740 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4741 desktop notification to show up (only once, the first time it is
4742 inserted):&lt;/p&gt;
4743
4744 &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;
4745
4746 &lt;p&gt;For this prototype to be really useful, some way to automatically
4747 install the proposed packages by pressing the &quot;Please install
4748 program(s)&quot; button should to be implemented.&lt;/p&gt;
4749
4750 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4751 happen, please help me update the discover-data database with mappings
4752 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4753 list the package you would like to have installed when a given
4754 hardware device is inserted into your computer, and report bugs using
4755 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4756 such mapping, please let me know.&lt;/p&gt;
4757
4758 &lt;p&gt;This prototype need more work, and there are several questions that
4759 should be considered before it is ready for production use. Is dbus
4760 the correct way to detect new hardware? At the moment I look for HAL
4761 dbus events on the system bus, because that is the events I could see
4762 on my Debian Squeeze KDE desktop. Are there better events to use?
4763 How should the user be notified? Is the desktop notification
4764 mechanism the best option, or should the background daemon raise a
4765 popup instead? How should packages be installed? When should they
4766 not be installed?&lt;/p&gt;
4767
4768 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4769 please send me an email. :)&lt;/p&gt;
4770 </description>
4771 </item>
4772
4773 <item>
4774 <title>New IRC channel for LEGO designers using Debian</title>
4775 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4776 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4777 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4778 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4779 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4780 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4781 discovered I had to build all the tools myself because none were
4782 already in Debian Squeeze. If Debian support for LEGO is something
4783 you care about, please join me on the IRC channel
4784 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4785 irc.debian.org). There is a lot that could be done to improve the
4786 Debian support for LEGO designers. For example both CAD software
4787 and Mindstorm compilers are missing. :)&lt;/p&gt;
4788
4789 &lt;p&gt;Update 2012-01-03: A
4790 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4791 including links to Lego related packages is now available.&lt;/p&gt;
4792 </description>
4793 </item>
4794
4795 <item>
4796 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4797 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4798 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4799 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4800 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4801 year! I hope next year will prove to be a good year.&lt;/p&gt;
4802
4803 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4804 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4805 between each other with minimal overhead, is a very interesting
4806 experiment. And as I wrote a few days ago, the bitcoin situation in
4807 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4808 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4809 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4810 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4811 for one of the ftpmasters to approve the new bitcoin-qt package
4812 name.&lt;/p&gt;
4813
4814 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4815 team in Debian, you can easily test the package in Debian Squeeze
4816 using the following steps to get a set of working packages:&lt;/p&gt;
4817
4818 &lt;blockquote&gt;&lt;pre&gt;
4819 git clone git://git.debian.org/git/collab-maint/bitcoin
4820 cd bitcoin
4821 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4822 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4823 &lt;/pre&gt;&lt;/blockquote&gt;
4824
4825 &lt;p&gt;You might have to install some build dependencies as well. The
4826 list of commands should give you two packages, bitcoind and
4827 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4828 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4829 around 5.6 GiB of data on my machine at the moment. Make sure your
4830 ~/.bitcoin/ directory have lots of spare room if you want to download
4831 all the blocks. The client will warn if the disk is getting full, so
4832 there is not really a problem if you got too little room, but you will
4833 not be able to get all the features out of the client.&lt;/p&gt;
4834
4835 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4836 activities, please send Bitcoin donations to my address
4837 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4838 </description>
4839 </item>
4840
4841 <item>
4842 <title>A word on bitcoin support in Debian</title>
4843 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4844 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4845 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4846 <description>&lt;p&gt;It has been a while since I wrote about
4847 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4848 peer-to-peer based crypto-currency, and the reason is simply that I
4849 have been busy elsewhere. But two days ago, I started looking at the
4850 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4851 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4852 is now maintained by a
4853 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4854 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4855 owe a huge thank you to all these team members. :)
4856 But I was sad to discover that the bitcoin client is missing in
4857 Wheezy. It is only available in Sid (and an outdated client from
4858 backports). The client had several RC bugs registered in BTS blocking
4859 it from entering testing. To try to help the team and improve the
4860 situation, I spent some time providing patches and triaging the bug
4861 reports. I also had a look at the bitcoin package available from Matt
4862 Corallo in a
4863 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4864 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4865 Debian package.&lt;/p&gt;
4866
4867 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4868 IRC, I pushed several patches into the collab-maint git repository to
4869 improve the package. It now contains fixes for the RC issues (not from
4870 me, but fixed by Scott Howard), build rules for a Qt GUI client
4871 package, konqueror support for the bitcoin: URI and bash completion
4872 setup. As I work on Debian Squeeze, I also created
4873 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4874 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4875 it and try to integrate it into the git repository before uploading a
4876 new version to unstable.
4877
4878 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4879 centralized control currently exercised in the monetary system. I
4880 find it completely unacceptable that the USA government is collecting
4881 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4882 that the major credit card companies can block legal money
4883 transactions to Wikileaks. But for bitcoin to succeed, more people
4884 need to use bitcoins, and more people need to accept bitcoins when
4885 they sell products and services. Improving the bitcoin support in
4886 Debian is a small step in the right direction, but not enough.
4887 Unfortunately the user experience when browsing the web and wanting to
4888 pay with bitcoin is still not very good. The bitcoin: URI is a step
4889 in the right direction, but need to work in most or every browser in
4890 use. Also the bitcoin-qt client is too heavy to fire up to do a
4891 quick transaction. I believe there are other clients available, but
4892 have not tested them.&lt;/p&gt;
4893
4894 &lt;p&gt;My
4895 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4896 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4897 I received 20.15 BTC so far on the address I provided in my blog two
4898 years ago, as can be
4899 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4900 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4901 donation. The blockexplorer service demonstrates quite well that
4902 bitcoin is not quite anonymous and untracked. :) I wonder if the
4903 number of users have gone up since then. If you use bitcoin and want
4904 to show your support of my activity, please send Bitcoin donations to
4905 the same address as last time,
4906 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4907 </description>
4908 </item>
4909
4910 <item>
4911 <title>Git repository for song book for Computer Scientists</title>
4912 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4913 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4914 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4915 <description>&lt;p&gt;As I
4916 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4917 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4918 years ago, and today I finally found time to create a public
4919 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4920 repository for the project&lt;/a&gt;.&lt;/p&gt;
4921
4922 &lt;p&gt;If you want to help out, please clone the source and submit patches
4923 to the HTML version. To generate the PDF and PostScript version,
4924 please use prince XML, or let me know about a useful free software
4925 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4926
4927 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4928 PostScript formats at
4929 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4930 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4931 </description>
4932 </item>
4933
4934 <item>
4935 <title>Gratulerer med 19-årsdagen, Debian!</title>
4936 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4937 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4938 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4939 <description>&lt;p&gt;I dag fyller
4940 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4941 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4942 si gratulerer med dagen, Debian!&lt;/p&gt;
4943 </description>
4944 </item>
4945
4946 <item>
4947 <title>Song book for Computer Scientists</title>
4948 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4949 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4950 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4951 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4952 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4953 collecting computer related songs for use at parties. The original
4954 version was written in LaTeX, but a few years ago I got help from
4955 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4956 while keeping the ability to create a nice book in PDF format. I have
4957 not had time to maintain the book for a while now, and guess I should
4958 put it up on some public version control repository where others can
4959 help me extend and update the book. If anyone is volunteering to help
4960 me with this, send me an email. Also let me know if there are songs
4961 missing in my book.&lt;/p&gt;
4962
4963 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4964 me today that I really should let all my readers share the joys of
4965 singing out load about programming, computers and computer networks.
4966 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4967 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4968 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4969 Computer Science Songbook&lt;/a&gt;.
4970 </description>
4971 </item>
4972
4973 <item>
4974 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4975 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4976 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4977 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4978 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4979 around 1000 at the moment. To be able to get help from the vendors
4980 when something go wrong, we want to keep the firmware on the servers
4981 up to date. If the firmware isn&#39;t the latest and greatest, the
4982 vendors typically refuse to start debugging any problems until the
4983 firmware is upgraded. So before every reboot, we want to upgrade the
4984 firmware, and we would really like everyone handling servers at the
4985 university to do this themselves when they plan to reboot a machine.
4986 For that to happen we at the unix server admin group need to provide
4987 the tools to do so.&lt;/p&gt;
4988
4989 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4990 fetch and install the latest firmware for the servers we got. Most of
4991 our hardware are from Dell and HP, so I have focused on these servers
4992 so far. This blog post is about the Dell part.&lt;/P&gt;
4993
4994 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4995 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4996 with firmware information for all 11th generation servers, listing
4997 which firmware should be used on a given model and where on the FTP
4998 site I can find it. Using a simple perl XML parser I can then
4999 download the shell scripts Dell provides to do firmware upgrades from
5000 within Linux and reboot when all the firmware is primed and ready to
5001 be activated on the first reboot.&lt;/p&gt;
5002
5003 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
5004 Are there anyone working on similar tools for firmware upgrading all
5005 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
5006
5007 &lt;p&gt;&lt;pre&gt;
5008 #!/usr/bin/perl
5009 use strict;
5010 use warnings;
5011 use File::Temp qw(tempdir);
5012 BEGIN {
5013 # Install needed RHEL packages if missing
5014 my %rhelmodules = (
5015 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
5016 );
5017 for my $module (keys %rhelmodules) {
5018 eval &quot;use $module;&quot;;
5019 if ($@) {
5020 my $pkg = $rhelmodules{$module};
5021 system(&quot;yum install -y $pkg&quot;);
5022 eval &quot;use $module;&quot;;
5023 }
5024 }
5025 }
5026 my $errorsto = &#39;pere@hungry.com&#39;;
5027
5028 upgrade_dell();
5029
5030 exit 0;
5031
5032 sub run_firmware_script {
5033 my ($opts, $script) = @_;
5034 unless ($script) {
5035 print STDERR &quot;fail: missing script name\n&quot;;
5036 exit 1
5037 }
5038 print STDERR &quot;Running $script\n\n&quot;;
5039
5040 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
5041 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
5042 } else {
5043 print STDERR &quot;fail: firmware script returned error\n&quot;;
5044 }
5045 }
5046
5047 sub run_firmware_scripts {
5048 my ($opts, @dirs) = @_;
5049 # Run firmware packages
5050 for my $dir (@dirs) {
5051 print STDERR &quot;info: Running scripts in $dir\n&quot;;
5052 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
5053 while (my $s = readdir $dh) {
5054 next if $s =~ m/^\.\.?/;
5055 run_firmware_script($opts, &quot;$dir/$s&quot;);
5056 }
5057 closedir $dh;
5058 }
5059 }
5060
5061 sub download {
5062 my $url = shift;
5063 print STDERR &quot;info: Downloading $url\n&quot;;
5064 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
5065 }
5066
5067 sub upgrade_dell {
5068 my @dirs;
5069 my $product = `dmidecode -s system-product-name`;
5070 chomp $product;
5071
5072 if ($product =~ m/PowerEdge/) {
5073
5074 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5075 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
5076
5077 my $tmpdir = tempdir(
5078 CLEANUP =&gt; 1
5079 );
5080 chdir($tmpdir);
5081 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
5082 system(&#39;gunzip Catalog.xml.gz&#39;);
5083 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
5084 # -q is quiet, disabling interactivity and reducing console output
5085 my $fwopts = &quot;-q&quot;;
5086 if (@paths) {
5087 for my $url (@paths) {
5088 fetch_dell_fw($url);
5089 }
5090 run_firmware_scripts($fwopts, $tmpdir);
5091 } else {
5092 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5093 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5094 }
5095 chdir(&#39;/&#39;);
5096 } else {
5097 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5098 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5099 }
5100 }
5101
5102 sub fetch_dell_fw {
5103 my $path = shift;
5104 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
5105 download($url);
5106 }
5107
5108 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5109 # firmware packages to download from Dell. Only work for Linux
5110 # machines and 11th generation Dell servers.
5111 sub fetch_dell_fw_list {
5112 my $filename = shift;
5113
5114 my $product = `dmidecode -s system-product-name`;
5115 chomp $product;
5116 my ($mybrand, $mymodel) = split(/\s+/, $product);
5117
5118 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
5119
5120 my $xml = XMLin($filename);
5121 my @paths;
5122 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
5123 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
5124 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
5125 my $oscode;
5126 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
5127 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
5128 } else {
5129 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
5130 }
5131 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
5132 {
5133 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
5134 }
5135 }
5136 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
5137 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
5138
5139 # Drop application packages, only firmware and BIOS
5140 next if &#39;APAC&#39; eq $componenttype;
5141
5142 my $cpath = $component-&gt;{path};
5143 for my $path (@paths) {
5144 if ($cpath =~ m%/$path$%) {
5145 push(@paths, $cpath);
5146 }
5147 }
5148 }
5149 return @paths;
5150 }
5151 &lt;/pre&gt;
5152
5153 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5154 it could work on other platforms with some tweaking. Anyone know a
5155 index like Catalog.xml is available from HP for HP servers? At the
5156 moment I maintain a similar list manually and it is quickly getting
5157 outdated.&lt;/p&gt;
5158 </description>
5159 </item>
5160
5161 <item>
5162 <title>How is booting into runlevel 1 different from single user boots?</title>
5163 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5164 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5165 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5166 <description>&lt;p&gt;Wouter Verhelst have some
5167 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5168 comments and opinions&lt;/a&gt; on my blog post on
5169 &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
5170 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5171 &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
5172 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5173 small piece of his comment now, and though it best to address the
5174 misunderstanding he bring forward:&lt;/p&gt;
5175
5176 &lt;p&gt;&lt;blockquote&gt;
5177 Currently, a system admin has four options: [...] boot to a
5178 single-user system (by adding &#39;single&#39; to the kernel command line;
5179 this runs rcS and rc1 scripts)
5180 &lt;/blockquote&gt;&lt;/p&gt;
5181
5182 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5183 and booting into runlevel 1 is the same. I am not surprised he
5184 believe this, because it would make sense and is a quite sensible
5185 thing to believe. But because the boot in Debian is slightly broken,
5186 runlevel 1 do not work properly and it isn&#39;t the same as single user
5187 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5188 hard to explain.&lt;/p&gt;
5189
5190 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5191 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5192 executed in single user mode is sulogin. Single user mode is a boot
5193 state &quot;between&quot; the runlevels, and when booting into single user mode,
5194 only the scripts in /etc/rcS.d/ are executed before the init process
5195 enters the single user state. When switching to runlevel 1, the state
5196 is in fact not ending in runlevel 1, but it passes through runlevel 1
5197 and end up in the single user mode (see /etc/rc1.d/S03single, which
5198 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5199 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5200 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5201 mode).&lt;/p&gt;
5202
5203 &lt;p&gt;This summary might make it clearer. When booting for the first
5204 time into single user mode, the following commands are executed:
5205 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5206 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5207 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5208 trying to continue after visiting single user mode. Not all services
5209 are started again as they should, causing the machine to end up in an
5210 unpredicatble state. This is why Debian admins recommend rebooting
5211 after visiting single user mode.&lt;/p&gt;
5212
5213 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5214 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5215 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5216 stopped when passing through the scripts in /etc/rc1.d/, and not
5217 started again when switching away from runlevel 1 to the runlevels
5218 2-5. I believe the problem is best fixed by moving all the scripts
5219 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5220 functioning single user mode during boot.&lt;/p&gt;
5221
5222 &lt;p&gt;I have spent several years investigating the Debian boot system,
5223 and discovered this problem a few years ago. I suspect it originates
5224 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5225 </description>
5226 </item>
5227
5228 <item>
5229 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5230 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5231 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5232 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5233 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5234 are started from /etc/rcS.d/. In fact, there is a bite more of them
5235 than make sense, and this causes a few problems. What kind of
5236 problems, you might ask. There are at least two problems. The first
5237 is that it is not possible to recover a machine after switching to
5238 runlevel 1. One need to actually reboot to get the machine back to
5239 the expected state. The other is that single user boot will sometimes
5240 run into problems because some of the subsystems are activated before
5241 the root login is presented, causing problems when trying to recover a
5242 machine from a problem in that subsystem. A minor additional point is
5243 that moving more scripts out of rcS.d/ and into the other rc#.d/
5244 directories will increase the amount of scripts that can run in
5245 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5246
5247 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5248 scripts that _have_ to execute before the root login prompt is
5249 presented during a single user boot should go there. Everything else
5250 should go into the numeric runlevels. This means things like
5251 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5252 the numeric runlevels. Today in Debian, there are around 115 init.d
5253 scripts that are started from rcS.d/, and most of them should be moved
5254 out. Do your package have one of them? Please help us make single
5255 user and runlevel 1 better by moving it.&lt;/p&gt;
5256
5257 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5258 etc. should still be started from rcS.d/, but there is for example no
5259 need to have the network enabled before the single user login prompt
5260 is presented.&lt;/p&gt;
5261
5262 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5263 Debian systems working while scripts migrate and during upgrades, the
5264 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5265 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5266 and the next ones can only be moved when their dependencies have been
5267 moved first. This migration must be done sequentially while we ensure
5268 that the package system upgrade packages in the right order to keep
5269 the system state correct. This will require some coordination when it
5270 comes to network related packages, but most of the packages with
5271 scripts that should migrate do not have anything in rcS.d/ depending
5272 on them. Some packages have already been updated, like the sudo
5273 package, while others are still left to do. I wish I had time to work
5274 on this myself, but real live constrains make it unlikely that I will
5275 find time to push this forward.&lt;/p&gt;
5276 </description>
5277 </item>
5278
5279 <item>
5280 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5281 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5282 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5283 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5284 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5285 mentioned the issues I believe should be improved in Debian for its
5286 desktop to be useful for more people. The use case for this is my
5287 parents, which are currently running Kubuntu which solve the
5288 issues.&lt;/p&gt;
5289
5290 &lt;p&gt;I suspect these four missing features are not very hard to
5291 implement. After all, they are present in Ubuntu, so if we wanted to
5292 do this in Debian we would have a source.&lt;/p&gt;
5293
5294 &lt;ol&gt;
5295
5296 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5297 are new packages available for upgrades, a icon in the KDE status bar
5298 indicate this, and clicking on it will activate the simple upgrade
5299 tool to handle it. I have no problem guiding both of my parents
5300 through the process over the phone. If a kernel reboot is required,
5301 this too is indicated by the status bars and the upgrade tool. Last
5302 time I checked, nothing with the same features was working in KDE in
5303 Debian.&lt;/li&gt;
5304
5305 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5306 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5307 currently have a handler for, it will ask the user if the system
5308 should search for a package that would add support for this MIME type,
5309 and if the user say yes, the APT sources will be searched for packages
5310 advertising the MIME type in their control file (visible in the
5311 Packages file in the APT archive). If one or more packages are found,
5312 it is a simple click of the mouse to add support for the missing mime
5313 type. If the package require the user to accept some non-free
5314 license, this is explained to the user. The entire process make it
5315 more clear to the user why something do not work in the browser, and
5316 make the chances higher for the user to blame the web page authors and
5317 not the browser for any missing features.&lt;/li&gt;
5318
5319 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5320 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5321 it is not supporting, a dialog pop up asking the user if the system
5322 should search for a package that would add support for it. This
5323 happen with things like MP3, Windows Media or H.264. The selection
5324 and installation procedure is very similar to the Firefox browser
5325 plugin handling. This is as far as I know implemented using a
5326 gstreamer hook. The end result is that the user easily get access to
5327 the codecs that are present from the APT archives available, while
5328 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5329
5330 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5331 displaying a text/plain file in my Debian browser, it will propose to
5332 start emacs to show it. If I remember correctly, when doing the same
5333 in Kunbutu it show the file as a text file in the browser. At least I
5334 know Opera will show text files within the browser. I much prefer the
5335 latter behaviour.&lt;/li&gt;
5336
5337 &lt;/ol&gt;
5338
5339 &lt;p&gt;There are other nice features as well, like the simplified suite
5340 upgrader, but given that I am the one mostly doing the dist-upgrade,
5341 it do not matter much.&lt;/p&gt;
5342
5343 &lt;p&gt;I really hope we could get these features in place for the next
5344 Debian release. It would require the coordinated effort of several
5345 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5346 </description>
5347 </item>
5348
5349 <item>
5350 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5351 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5352 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5353 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5354 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5355 site is build on Debian/Squeeze, and this platform was chosen because
5356 I am most familiar with Debian (being a Debian Developer for around 10
5357 years) because it is the latest stable Debian release which should get
5358 security support for a few years.&lt;/p&gt;
5359
5360 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5361 that are missing in Debian at the moment. It would be great if these
5362 modules were added to the Debian archive, allowing anyone to set up
5363 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5364 in their own country using only Debian packages. The list of modules
5365 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5366 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5367 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5368 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5369 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5370 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5371 easier in the future.&lt;/p&gt;
5372
5373 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5374 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5375 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5376 with the responsibility of tracking security problems, which I really
5377 do not have time for.&lt;/p&gt;
5378 </description>
5379 </item>
5380
5381 <item>
5382 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5383 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5384 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5385 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5386 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5387 posts have been in Norwegian the last few weeks, so here is a short
5388 update in English.&lt;/p&gt;
5389
5390 &lt;p&gt;The kids still keep me too busy to get much free software work
5391 done, but I did manage to organise a project to get a Norwegian port
5392 of the British service
5393 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5394 and it has been running for a month now. The entire project has been
5395 organised by me and two others. Around Christmas we gathered sponsors
5396 to fund the development work. In January I drafted a contract with
5397 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5398 and in February the development took place. Most of it involved
5399 converting the source to use GPS coordinates instead of British
5400 easting/northing, and the resulting code should be a lot easier to get
5401 running in any country by now. The Norwegian
5402 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5403 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5404 source and the source for administrative borders in Norway, and
5405 support for this had to be added/fixed.&lt;/p&gt;
5406
5407 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5408 polishing the system before we announced it March 7th. The system is
5409 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5410 problem reports in a few weeks. Soon we hope to announce the Android
5411 and iPhone versions making it even easier to report problems with the
5412 public infrastructure.&lt;/p&gt;
5413
5414 &lt;p&gt;Perhaps something to consider for those of you in countries without
5415 such service?&lt;/p&gt;
5416 </description>
5417 </item>
5418
5419 <item>
5420 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5421 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5423 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5424 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5425 issues here at my work with the University of Oslo. My idea is that
5426 it should be possible to use the information about security issues
5427 available on the Internet, and check our locally
5428 maintained/distributed software against this information. It should
5429 allow us to verify that no known security issues are forgotten. The
5430 CVE database listing vulnerabilities seem like a great central point,
5431 and by using the package lists from Debian mapped to CVEs provided by
5432 the testing security team, I believed it should be possible to figure
5433 out which security holes were present in our free software
5434 collection.&lt;/p&gt;
5435
5436 &lt;p&gt;After reading up on the topic, it became obvious that the first
5437 building block is to be able to name software packages in a unique and
5438 consistent way across data sources. I considered several ways to do
5439 this, for example coming up with my own naming scheme like using URLs
5440 to project home pages or URLs to the Freshmeat entries, or using some
5441 existing naming scheme. And it seem like I am not the first one to
5442 come across this problem, as MITRE already proposed and implemented a
5443 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5444 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5445 software, hardware and other platform components. The CPE ids are
5446 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5447 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5448 issues for any CPE name. With this in place, all I need to do is to
5449 locate the CPE id for the software packages we use at the university.
5450 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5451 NVD entry if a CVE for the package exist).&lt;/p&gt;
5452
5453 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5454 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5455 check out, one could look up
5456 &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
5457 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5458 The most recent one is
5459 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5460 and at the bottom of the NVD page for this vulnerability the complete
5461 list of affected versions is provided.&lt;/p&gt;
5462
5463 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5464 for offline processing of issues. Using this dump, I&#39;ve written a
5465 small script taking a list of CPEs as input and list all CVEs
5466 affecting the packages represented by these CPEs. One give it CPEs
5467 with version numbers as specified above and get a list of open
5468 security issues out.&lt;/p&gt;
5469
5470 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5471 information need to be high. For that to happen, I believe as many as
5472 possible need to use and contribute to the NVD database. I notice
5473 RHEL is providing
5474 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5475 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5476 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5477
5478 &lt;p&gt;To get an idea about the quality for free software, I spent some
5479 time making it possible to compare the CVE database from Debian with
5480 the CVE database in NVD. The result look fairly good, but there are
5481 some inconsistencies in NVD (same software package having several
5482 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5483 Debian believe are affected by a CVE). Hope to find time to improve
5484 the quality of NVD, but that require being able to get in touch with
5485 someone maintaining it. So far my three emails with questions and
5486 corrections have not seen any reply, but I hope contact can be
5487 established soon.&lt;/p&gt;
5488
5489 &lt;p&gt;An interesting application for CPEs is cross platform package
5490 mapping. It would be useful to know which packages in for example
5491 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5492 this would be trivial if all linux distributions provided CPE entries
5493 for their packages.&lt;/p&gt;
5494 </description>
5495 </item>
5496
5497 <item>
5498 <title>Which module is loaded for a given PCI and USB device?</title>
5499 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5500 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5501 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5502 <description>&lt;p&gt;In the
5503 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5504 package in Debian, there is a script to report useful information
5505 about the running hardware for use when people report missing
5506 information. One part of this script that I find very useful when
5507 debugging hardware problems, is the part mapping loaded kernel module
5508 to the PCI device it claims. It allow me to quickly see if the kernel
5509 module I expect is driving the hardware I am struggling with. To see
5510 the output, make sure discover-data is installed and run
5511 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5512 one of my machines like this:&lt;/p&gt;
5513
5514 &lt;pre&gt;
5515 loaded modules:
5516 10de:03eb i2c_nforce2
5517 10de:03f1 ohci_hcd
5518 10de:03f2 ehci_hcd
5519 10de:03f0 snd_hda_intel
5520 10de:03ec pata_amd
5521 10de:03f6 sata_nv
5522 1022:1103 k8temp
5523 109e:036e bttv
5524 109e:0878 snd_bt87x
5525 11ab:4364 sky2
5526 &lt;/pre&gt;
5527
5528 &lt;p&gt;The code in question look like this, slightly modified for
5529 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5530
5531 &lt;pre&gt;
5532 if [ -d /sys/bus/pci/devices/ ] ; then
5533 echo loaded pci modules:
5534 (
5535 cd /sys/bus/pci/devices/
5536 for address in * ; do
5537 if [ -d &quot;$address/driver/module&quot; ] ; then
5538 module=`cd $address/driver/module ; pwd -P | xargs basename`
5539 if grep -q &quot;^$module &quot; /proc/modules ; then
5540 address=$(echo $address |sed s/0000://)
5541 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5542 echo &quot;$id $module&quot;
5543 fi
5544 fi
5545 done
5546 )
5547 echo
5548 fi
5549 &lt;/pre&gt;
5550
5551 &lt;p&gt;Similar code could be used to extract USB device module
5552 mappings:&lt;/p&gt;
5553
5554 &lt;pre&gt;
5555 if [ -d /sys/bus/usb/devices/ ] ; then
5556 echo loaded usb modules:
5557 (
5558 cd /sys/bus/usb/devices/
5559 for address in * ; do
5560 if [ -d &quot;$address/driver/module&quot; ] ; then
5561 module=`cd $address/driver/module ; pwd -P | xargs basename`
5562 if grep -q &quot;^$module &quot; /proc/modules ; then
5563 address=$(echo $address |sed s/0000://)
5564 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5565 if [ &quot;$id&quot; ] ; then
5566 echo &quot;$id $module&quot;
5567 fi
5568 fi
5569 fi
5570 done
5571 )
5572 echo
5573 fi
5574 &lt;/pre&gt;
5575
5576 &lt;p&gt;This might perhaps be something to include in other tools as
5577 well.&lt;/p&gt;
5578 </description>
5579 </item>
5580
5581 <item>
5582 <title>How to test if a laptop is working with Linux</title>
5583 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5584 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5585 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5586 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5587 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5588 batch of computers will work with Linux. Every year for the last few
5589 years the university have organised shared bid of a few thousand
5590 computers, and this year HP won the bid. Two different desktops and
5591 five different laptops are on the list this year. We in the UNIX
5592 group want to know which one of these computers work well with RHEL
5593 and Ubuntu, the two Linux distributions we currently handle at the
5594 university.&lt;/p&gt;
5595
5596 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5597 perhaps inspire others to test hardware as well. To test, I PXE
5598 install the OS version of choice, and log in as my normal user and run
5599 a few applications and plug in selected pieces of hardware. When
5600 something fail, I make a note about this in the test matrix and move
5601 on. If I have some spare time I try to report the bug to the OS
5602 vendor, but as I only have the machines for a short time, I rarely
5603 have the time to do this for all the problems I find.&lt;/p&gt;
5604
5605 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5606 I perform on a new model.&lt;/p&gt;
5607
5608 &lt;ul&gt;
5609
5610 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5611 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5612 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5613
5614 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5615 installation, X.org is working.&lt;/li&gt;
5616
5617 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5618 package mesa-utils on Ubuntu) and writing down the frames per second
5619 reported by the program.&lt;/li&gt;
5620
5621 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5622 logging in, and if I can hear this the test is successful. If there
5623 are several audio exits on the machine, I try them all and check if
5624 the Gnome/KDE audio mixer can control where to send the sound. I
5625 normally test this by playing
5626 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5627 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5628
5629 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5630 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5631
5632 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5633 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5634
5635 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5636 picture from the v4l device show up.&lt;/li&gt;
5637
5638 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5639 any bluetooth devices are discovered. In my office, I normally see a
5640 few.&lt;/li&gt;
5641
5642 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5643 memory modules lying around, and stick them in and see if Gnome/KDE
5644 notice this.&lt;/li&gt;
5645
5646 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5647 special button work, and if the laptop continue to work after
5648 resume.&lt;/li&gt;
5649
5650 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5651 adjusting background light, switching on/off external video output,
5652 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5653 laptop to laptop, so I just write down which are working and which are
5654 not.&lt;/li&gt;
5655
5656 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5657 acceleration sensors etc. I rarely test these, as I do not know how
5658 to quickly test if they are working or not, so I only document their
5659 existence.&lt;/li&gt;
5660
5661 &lt;/ul&gt;
5662
5663 &lt;p&gt;By now I suspect you are really curious what the test results are
5664 for the HP machines I am testing. I&#39;m not done yet, so I will report
5665 the test results later. For now I can report that HP 8100 Elite work
5666 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5667 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5668 can see, I have most machines left to test. One interesting
5669 observation is that Ubuntu Lucid has almost twice the frame rate than
5670 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5671 </description>
5672 </item>
5673
5674 <item>
5675 <title>Some thoughts on BitCoins</title>
5676 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5677 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5678 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5679 <description>&lt;p&gt;As I continue to explore
5680 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5681 what properties the system have, and how it will be affected by laws
5682 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5683
5684 &lt;p&gt;One interesting thing to note is that since the transactions are
5685 verified using a peer to peer network, all details about a transaction
5686 is known to everyone. This means that if a BitCoin address has been
5687 published like I did with mine in my initial post about BitCoin, it is
5688 possible for everyone to see how many BitCoins have been transfered to
5689 that address. There is even a web service to look at the details for
5690 all transactions. There I can see that my address
5691 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5692 have received 16.06 Bitcoin, the
5693 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5694 address of Simon Phipps have received 181.97 BitCoin and the address
5695 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5696 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5697 every one of you that donated bitcoins to support my activity. The
5698 fact that anyone can see how much money was transfered to a given
5699 address make it more obvious why the BitCoin community recommend to
5700 generate and hand out a new address for each transaction. I&#39;m told
5701 there is no way to track which addresses belong to a given person or
5702 organisation without the person or organisation revealing it
5703 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5704
5705 &lt;p&gt;In Norway, and in most other countries, there are laws and
5706 regulations limiting how much money one can transfer across the border
5707 without declaring it. There are money laundering, tax and accounting
5708 laws and regulations I would expect to apply to the use of BitCoin.
5709 If the Skolelinux foundation
5710 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5711 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5712 normal bank transfers like EFF is doing, how should this be accounted?
5713 Given that it is impossible to know if money can cross the border or
5714 not, should everything or nothing be declared? What exchange rate
5715 should be used when calculating taxes? Would receivers have to pay
5716 income tax if the foundation were to pay Skolelinux contributors in
5717 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5718
5719 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5720 accepted by a lot of users. It must be possible to get easy access to
5721 the currency (as a wage or using currency exchanges), and it must be
5722 easy to spend it. At the moment BitCoin seem fairly easy to get
5723 access to, but there are very few places to spend it. I am not really
5724 a regular user of any of the vendor types currently accepting BitCoin,
5725 so I wonder when my kind of shop would start accepting BitCoins. I
5726 would like to buy electronics, travels and subway tickets, not herbs
5727 and books. :) The currency is young, and this will improve over time
5728 if it become popular, but I suspect regular banks will start to lobby
5729 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5730 will claim it is helping fund terrorism and money laundering (which
5731 probably would be true, as is any currency in existence), but I
5732 believe the problems should be solved elsewhere and not by blaming
5733 currencies.&lt;/p&gt;
5734
5735 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5736 CPU intensive process that depend on a bit of luck as well (as one is
5737 competing against all the other miners currently spending CPU cycles
5738 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5739 BitCoin when this happen. Yesterday I came across the obvious way to
5740 join forces to increase ones changes of getting at least some coins,
5741 by coordinating the work on mining BitCoins across several machines
5742 and people, and sharing the result if one is lucky and get the 50
5743 BitCoins. Check out
5744 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5745 if this sounds interesting. I have not had time to try to set up a
5746 machine to participate there yet, but have seen that running on ones
5747 own for a few days have not yield any BitCoins througth mining
5748 yet.&lt;/p&gt;
5749
5750 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5751 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5752 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5753 it was interesting to read. The arguments presented seem to be
5754 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5755 </description>
5756 </item>
5757
5758 <item>
5759 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5760 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5761 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5762 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5763 <description>&lt;p&gt;With this weeks lawless
5764 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5765 attacks&lt;/a&gt; on Wikileak and
5766 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5767 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5768 not be trusted to handle money transactions.
5769 A blog post from
5770 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5771 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5772 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5773 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5774 some help from my friend to get it all running, and he even handed me
5775 some bitcoins to get started. I even donated a few bitcoins to Simon
5776 for helping me remember BitCoin.&lt;/p&gt;
5777
5778 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5779 crypto-currency, decentralised and handled using peer-to-peer
5780 networks. It allows anonymous transactions and prohibits central
5781 control over the transactions, making it impossible for governments
5782 and companies alike to block donations and other transactions. The
5783 source is free software, and while the key dependency wxWidgets 2.9
5784 for the graphical user interface is missing in Debian, the command
5785 line client builds just fine. Hopefully Jonas
5786 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5787 Debian&lt;/a&gt; soon.&lt;/p&gt;
5788
5789 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5790 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5791 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5792 currency &quot;stock&quot; markets where the exchange rate is decided. There
5793 are not many users so far, but the concept seems promising. If you
5794 want to get started and lack a friend with any bitcoins to spare,
5795 you can even get
5796 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5797 bitcoin at the time of writing). Use
5798 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5799 on the current exchange rates.&lt;/p&gt;
5800
5801 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5802 machines. If you want to support my activity, please send Bitcoin
5803 donations to the address
5804 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5805 </description>
5806 </item>
5807
5808 <item>
5809 <title>Why isn&#39;t Debian Edu using VLC?</title>
5810 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5812 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5813 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5814 presented, and the winner among the multimedia player were VLC.
5815 Personally, I like VLC, and it is my player of choice when I first try
5816 to play a video file or stream. Only if VLC fail will I drag out
5817 gmplayer to see if it can do better. The reason is mostly the failure
5818 model and trust. When VLC fail, it normally pop up a error message
5819 reporting the problem. When mplayer fail, it normally segfault or
5820 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5821
5822 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5823 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5824 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5825 plugin to play web videos seamlessly, and the VLC browser plugin is
5826 not very good. For example, it lack in-line control buttons, so there
5827 is no way for the user to pause the video. Also, when I
5828 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5829 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5830 failed on several video pages where mplayer based plugins worked. If
5831 the browser plugin for VLC was as good as the gecko-mediaplayer
5832 package (which uses mplayer), we would switch.&lt;/P&gt;
5833
5834 &lt;p&gt;While VLC is a good player, its user interface is slightly
5835 annoying. The most annoying feature is its inconsistent use of
5836 keyboard shortcuts. When the player is in full screen mode, its
5837 shortcuts are different from when it is playing the video in a window.
5838 For example, space only work as pause when in full screen mode. I
5839 wish it had consisten shortcuts and that space also would work when in
5840 window mode. Another nice shortcut in gmplayer is [enter] to restart
5841 the current video. It is very nice when playing short videos from the
5842 web and want to restart it when new people arrive to have a look at
5843 what is going on.&lt;/p&gt;
5844 </description>
5845 </item>
5846
5847 <item>
5848 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5849 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5850 <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>
5851 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5852 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5853 upgrade testing of the
5854 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5855 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5856 This seem like a very good idea, so I adjusted by test scripts and
5857 can now present the updated result from today:&lt;/p&gt;
5858
5859 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5860
5861 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5862
5863 &lt;blockquote&gt;&lt;p&gt;
5864 apache2.2-bin
5865 aptdaemon
5866 baobab
5867 binfmt-support
5868 browser-plugin-gnash
5869 cheese-common
5870 cli-common
5871 cups-pk-helper
5872 dmz-cursor-theme
5873 empathy
5874 empathy-common
5875 freedesktop-sound-theme
5876 freeglut3
5877 gconf-defaults-service
5878 gdm-themes
5879 gedit-plugins
5880 geoclue
5881 geoclue-hostip
5882 geoclue-localnet
5883 geoclue-manual
5884 geoclue-yahoo
5885 gnash
5886 gnash-common
5887 gnome
5888 gnome-backgrounds
5889 gnome-cards-data
5890 gnome-codec-install
5891 gnome-core
5892 gnome-desktop-environment
5893 gnome-disk-utility
5894 gnome-screenshot
5895 gnome-search-tool
5896 gnome-session-canberra
5897 gnome-system-log
5898 gnome-themes-extras
5899 gnome-themes-more
5900 gnome-user-share
5901 gstreamer0.10-fluendo-mp3
5902 gstreamer0.10-tools
5903 gtk2-engines
5904 gtk2-engines-pixbuf
5905 gtk2-engines-smooth
5906 hamster-applet
5907 libapache2-mod-dnssd
5908 libapr1
5909 libaprutil1
5910 libaprutil1-dbd-sqlite3
5911 libaprutil1-ldap
5912 libart2.0-cil
5913 libboost-date-time1.42.0
5914 libboost-python1.42.0
5915 libboost-thread1.42.0
5916 libchamplain-0.4-0
5917 libchamplain-gtk-0.4-0
5918 libcheese-gtk18
5919 libclutter-gtk-0.10-0
5920 libcryptui0
5921 libdiscid0
5922 libelf1
5923 libepc-1.0-2
5924 libepc-common
5925 libepc-ui-1.0-2
5926 libfreerdp-plugins-standard
5927 libfreerdp0
5928 libgconf2.0-cil
5929 libgdata-common
5930 libgdata7
5931 libgdu-gtk0
5932 libgee2
5933 libgeoclue0
5934 libgexiv2-0
5935 libgif4
5936 libglade2.0-cil
5937 libglib2.0-cil
5938 libgmime2.4-cil
5939 libgnome-vfs2.0-cil
5940 libgnome2.24-cil
5941 libgnomepanel2.24-cil
5942 libgpod-common
5943 libgpod4
5944 libgtk2.0-cil
5945 libgtkglext1
5946 libgtksourceview2.0-common
5947 libmono-addins-gui0.2-cil
5948 libmono-addins0.2-cil
5949 libmono-cairo2.0-cil
5950 libmono-corlib2.0-cil
5951 libmono-i18n-west2.0-cil
5952 libmono-posix2.0-cil
5953 libmono-security2.0-cil
5954 libmono-sharpzip2.84-cil
5955 libmono-system2.0-cil
5956 libmtp8
5957 libmusicbrainz3-6
5958 libndesk-dbus-glib1.0-cil
5959 libndesk-dbus1.0-cil
5960 libopal3.6.8
5961 libpolkit-gtk-1-0
5962 libpt2.6.7
5963 libpython2.6
5964 librpm1
5965 librpmio1
5966 libsdl1.2debian
5967 libsrtp0
5968 libssh-4
5969 libtelepathy-farsight0
5970 libtelepathy-glib0
5971 libtidy-0.99-0
5972 media-player-info
5973 mesa-utils
5974 mono-2.0-gac
5975 mono-gac
5976 mono-runtime
5977 nautilus-sendto
5978 nautilus-sendto-empathy
5979 p7zip-full
5980 pkg-config
5981 python-aptdaemon
5982 python-aptdaemon-gtk
5983 python-axiom
5984 python-beautifulsoup
5985 python-bugbuddy
5986 python-clientform
5987 python-coherence
5988 python-configobj
5989 python-crypto
5990 python-cupshelpers
5991 python-elementtree
5992 python-epsilon
5993 python-evolution
5994 python-feedparser
5995 python-gdata
5996 python-gdbm
5997 python-gst0.10
5998 python-gtkglext1
5999 python-gtksourceview2
6000 python-httplib2
6001 python-louie
6002 python-mako
6003 python-markupsafe
6004 python-mechanize
6005 python-nevow
6006 python-notify
6007 python-opengl
6008 python-openssl
6009 python-pam
6010 python-pkg-resources
6011 python-pyasn1
6012 python-pysqlite2
6013 python-rdflib
6014 python-serial
6015 python-tagpy
6016 python-twisted-bin
6017 python-twisted-conch
6018 python-twisted-core
6019 python-twisted-web
6020 python-utidylib
6021 python-webkit
6022 python-xdg
6023 python-zope.interface
6024 remmina
6025 remmina-plugin-data
6026 remmina-plugin-rdp
6027 remmina-plugin-vnc
6028 rhythmbox-plugin-cdrecorder
6029 rhythmbox-plugins
6030 rpm-common
6031 rpm2cpio
6032 seahorse-plugins
6033 shotwell
6034 software-center
6035 system-config-printer-udev
6036 telepathy-gabble
6037 telepathy-mission-control-5
6038 telepathy-salut
6039 tomboy
6040 totem
6041 totem-coherence
6042 totem-mozilla
6043 totem-plugins
6044 transmission-common
6045 xdg-user-dirs
6046 xdg-user-dirs-gtk
6047 xserver-xephyr
6048 &lt;/p&gt;&lt;/blockquote&gt;
6049
6050 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6051
6052 &lt;blockquote&gt;&lt;p&gt;
6053 cheese
6054 ekiga
6055 eog
6056 epiphany-extensions
6057 evolution-exchange
6058 fast-user-switch-applet
6059 file-roller
6060 gcalctool
6061 gconf-editor
6062 gdm
6063 gedit
6064 gedit-common
6065 gnome-games
6066 gnome-games-data
6067 gnome-nettool
6068 gnome-system-tools
6069 gnome-themes
6070 gnuchess
6071 gucharmap
6072 guile-1.8-libs
6073 libavahi-ui0
6074 libdmx1
6075 libgalago3
6076 libgtk-vnc-1.0-0
6077 libgtksourceview2.0-0
6078 liblircclient0
6079 libsdl1.2debian-alsa
6080 libspeexdsp1
6081 libsvga1
6082 rhythmbox
6083 seahorse
6084 sound-juicer
6085 system-config-printer
6086 totem-common
6087 transmission-gtk
6088 vinagre
6089 vino
6090 &lt;/p&gt;&lt;/blockquote&gt;
6091
6092 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6093
6094 &lt;blockquote&gt;&lt;p&gt;
6095 gstreamer0.10-gnomevfs
6096 &lt;/p&gt;&lt;/blockquote&gt;
6097
6098 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6099
6100 &lt;blockquote&gt;&lt;p&gt;
6101 [nothing]
6102 &lt;/p&gt;&lt;/blockquote&gt;
6103
6104 &lt;p&gt;This is for KDE:&lt;/p&gt;
6105
6106 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6107
6108 &lt;blockquote&gt;&lt;p&gt;
6109 ksmserver
6110 &lt;/p&gt;&lt;/blockquote&gt;
6111
6112 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6113
6114 &lt;blockquote&gt;&lt;p&gt;
6115 kwin
6116 network-manager-kde
6117 &lt;/p&gt;&lt;/blockquote&gt;
6118
6119 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6120
6121 &lt;blockquote&gt;&lt;p&gt;
6122 arts
6123 dolphin
6124 freespacenotifier
6125 google-gadgets-gst
6126 google-gadgets-xul
6127 kappfinder
6128 kcalc
6129 kcharselect
6130 kde-core
6131 kde-plasma-desktop
6132 kde-standard
6133 kde-window-manager
6134 kdeartwork
6135 kdeartwork-emoticons
6136 kdeartwork-style
6137 kdeartwork-theme-icon
6138 kdebase
6139 kdebase-apps
6140 kdebase-workspace
6141 kdebase-workspace-bin
6142 kdebase-workspace-data
6143 kdeeject
6144 kdelibs
6145 kdeplasma-addons
6146 kdeutils
6147 kdewallpapers
6148 kdf
6149 kfloppy
6150 kgpg
6151 khelpcenter4
6152 kinfocenter
6153 konq-plugins-l10n
6154 konqueror-nsplugins
6155 kscreensaver
6156 kscreensaver-xsavers
6157 ktimer
6158 kwrite
6159 libgle3
6160 libkde4-ruby1.8
6161 libkonq5
6162 libkonq5-templates
6163 libnetpbm10
6164 libplasma-ruby
6165 libplasma-ruby1.8
6166 libqt4-ruby1.8
6167 marble-data
6168 marble-plugins
6169 netpbm
6170 nuvola-icon-theme
6171 plasma-dataengines-workspace
6172 plasma-desktop
6173 plasma-desktopthemes-artwork
6174 plasma-runners-addons
6175 plasma-scriptengine-googlegadgets
6176 plasma-scriptengine-python
6177 plasma-scriptengine-qedje
6178 plasma-scriptengine-ruby
6179 plasma-scriptengine-webkit
6180 plasma-scriptengines
6181 plasma-wallpapers-addons
6182 plasma-widget-folderview
6183 plasma-widget-networkmanagement
6184 ruby
6185 sweeper
6186 update-notifier-kde
6187 xscreensaver-data-extra
6188 xscreensaver-gl
6189 xscreensaver-gl-extra
6190 xscreensaver-screensaver-bsod
6191 &lt;/p&gt;&lt;/blockquote&gt;
6192
6193 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6194
6195 &lt;blockquote&gt;&lt;p&gt;
6196 ark
6197 google-gadgets-common
6198 google-gadgets-qt
6199 htdig
6200 kate
6201 kdebase-bin
6202 kdebase-data
6203 kdepasswd
6204 kfind
6205 klipper
6206 konq-plugins
6207 konqueror
6208 ksysguard
6209 ksysguardd
6210 libarchive1
6211 libcln6
6212 libeet1
6213 libeina-svn-06
6214 libggadget-1.0-0b
6215 libggadget-qt-1.0-0b
6216 libgps19
6217 libkdecorations4
6218 libkephal4
6219 libkonq4
6220 libkonqsidebarplugin4a
6221 libkscreensaver5
6222 libksgrd4
6223 libksignalplotter4
6224 libkunitconversion4
6225 libkwineffects1a
6226 libmarblewidget4
6227 libntrack-qt4-1
6228 libntrack0
6229 libplasma-geolocation-interface4
6230 libplasmaclock4a
6231 libplasmagenericshell4
6232 libprocesscore4a
6233 libprocessui4a
6234 libqalculate5
6235 libqedje0a
6236 libqtruby4shared2
6237 libqzion0a
6238 libruby1.8
6239 libscim8c2a
6240 libsmokekdecore4-3
6241 libsmokekdeui4-3
6242 libsmokekfile3
6243 libsmokekhtml3
6244 libsmokekio3
6245 libsmokeknewstuff2-3
6246 libsmokeknewstuff3-3
6247 libsmokekparts3
6248 libsmokektexteditor3
6249 libsmokekutils3
6250 libsmokenepomuk3
6251 libsmokephonon3
6252 libsmokeplasma3
6253 libsmokeqtcore4-3
6254 libsmokeqtdbus4-3
6255 libsmokeqtgui4-3
6256 libsmokeqtnetwork4-3
6257 libsmokeqtopengl4-3
6258 libsmokeqtscript4-3
6259 libsmokeqtsql4-3
6260 libsmokeqtsvg4-3
6261 libsmokeqttest4-3
6262 libsmokeqtuitools4-3
6263 libsmokeqtwebkit4-3
6264 libsmokeqtxml4-3
6265 libsmokesolid3
6266 libsmokesoprano3
6267 libtaskmanager4a
6268 libtidy-0.99-0
6269 libweather-ion4a
6270 libxklavier16
6271 libxxf86misc1
6272 okteta
6273 oxygencursors
6274 plasma-dataengines-addons
6275 plasma-scriptengine-superkaramba
6276 plasma-widget-lancelot
6277 plasma-widgets-addons
6278 plasma-widgets-workspace
6279 polkit-kde-1
6280 ruby1.8
6281 systemsettings
6282 update-notifier-common
6283 &lt;/p&gt;&lt;/blockquote&gt;
6284
6285 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6286 aptitude a bit more similar, but there are still quite a lott of
6287 differences. I have no idea what packages should be installed after
6288 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6289 </description>
6290 </item>
6291
6292 <item>
6293 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6294 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6295 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6296 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6297 <description>&lt;p&gt;Most of the computers in use by the
6298 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6299 are virtual machines. And they have been Xen machines running on a
6300 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6301 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6302 bit harder that it could have been, because we set up the Xen virtual
6303 machines to get the virtual partitions from LVM, which as far as I
6304 know is not supported by KVM. So to migrate, we had to convert
6305 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6306
6307 &lt;p&gt;I found
6308 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6309 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6310 migration. It uses qemu-img from the qemu package to make the disk
6311 image, parted to partition it, losetup and kpartx to present the disk
6312 image partions as devices, and dd to copy the data. I NFS mounted the
6313 new servers storage area on the old server to do the migration.&lt;/p&gt;
6314
6315 &lt;pre&gt;
6316 #!/bin/sh
6317
6318 # Based on
6319 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6320
6321 set -e
6322 set -x
6323
6324 if [ -z &quot;$1&quot; ] ; then
6325 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6326 exit 1
6327 else
6328 host=&quot;$1&quot;
6329 fi
6330
6331 if [ ! -e /dev/vg_data/$host-disk ] ; then
6332 echo &quot;error: unable to find LVM volume for $host&quot;
6333 exit 1
6334 fi
6335
6336 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6337 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6338 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6339 totalsize=$(( ( $disksize + $swapsize ) ))
6340
6341 img=$host.img
6342 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6343 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6344
6345 parted $img mklabel msdos
6346 parted $img mkpart primary linux-swap 0 $disksize
6347 parted $img mkpart primary ext2 $disksize $totalsize
6348 parted $img set 1 boot on
6349
6350 modprobe dm-mod
6351 losetup /dev/loop0 $img
6352 kpartx -a /dev/loop0
6353
6354 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6355 fsck.ext3 -f /dev/mapper/loop0p1 || true
6356 mkswap /dev/mapper/loop0p2
6357
6358 kpartx -d /dev/loop0
6359 losetup -d /dev/loop0
6360 &lt;/pre&gt;
6361
6362 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6363 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6364
6365 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6366 the new disk image attached, installed grub-pc and linux-image-686 and
6367 set up grub to boot from the disk image. After this, the KVM machines
6368 seem to work just fine.&lt;/p&gt;
6369 </description>
6370 </item>
6371
6372 <item>
6373 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6374 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6375 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6376 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6377 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6378 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6379 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6380 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6381
6382 &lt;p&gt;I still do not know what a correct migration should look like, so I
6383 report any differences between apt and aptitude and hope someone else
6384 can see if anything should be changed.&lt;/p&gt;
6385
6386 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6387
6388 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6389
6390 &lt;blockquote&gt;&lt;p&gt;
6391 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6392 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6393 dmz-cursor-theme empathy empathy-common finger
6394 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6395 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6396 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6397 gnome-cards-data gnome-codec-install gnome-core
6398 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6399 gnome-search-tool gnome-session-canberra gnome-spell
6400 gnome-system-log gnome-themes-extras gnome-themes-more
6401 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6402 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6403 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6404 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6405 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6406 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6407 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6408 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6409 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6410 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6411 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6412 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6413 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6414 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6415 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6416 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6417 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6418 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6419 libmono-security2.0-cil libmono-sharpzip2.84-cil
6420 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6421 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6422 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6423 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6424 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6425 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6426 libxalan2-java libxerces2-java media-player-info mesa-utils
6427 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6428 nautilus-sendto-empathy openoffice.org-writer2latex
6429 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6430 python-aptdaemon python-aptdaemon-gtk python-axiom
6431 python-beautifulsoup python-bugbuddy python-clientform
6432 python-coherence python-configobj python-crypto python-cupshelpers
6433 python-cupsutils python-eggtrayicon python-elementtree
6434 python-epsilon python-evolution python-feedparser python-gdata
6435 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6436 python-gtksourceview2 python-httplib2 python-louie python-mako
6437 python-markupsafe python-mechanize python-nevow python-notify
6438 python-opengl python-openssl python-pam python-pkg-resources
6439 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6440 python-tagpy python-twisted-bin python-twisted-conch
6441 python-twisted-core python-twisted-web python-utidylib python-webkit
6442 python-xdg python-zope.interface remmina remmina-plugin-data
6443 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6444 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6445 software-center svgalibg1 system-config-printer-udev
6446 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6447 totem totem-coherence totem-mozilla totem-plugins
6448 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6449 zip
6450 &lt;/p&gt;&lt;/blockquote&gt;
6451
6452 Installed using apt-get, removed with aptitude
6453
6454 &lt;blockquote&gt;&lt;p&gt;
6455 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6456 epiphany-extensions epiphany-gecko evolution-exchange
6457 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6458 gedit-common gnome-app-install gnome-games gnome-games-data
6459 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6460 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6461 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6462 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6463 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6464 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6465 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6466 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6467 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6468 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6469 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6470 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6471 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6472 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6473 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6474 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6475 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6476 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6477 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6478 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6479 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6480 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6481 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6482 sound-juicer swfdec-gnome system-config-printer totem-common
6483 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6484 &lt;/p&gt;&lt;/blockquote&gt;
6485
6486 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6487
6488 &lt;blockquote&gt;&lt;p&gt;
6489 gstreamer0.10-gnomevfs
6490 &lt;/p&gt;&lt;/blockquote&gt;
6491
6492 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6493
6494 &lt;blockquote&gt;&lt;p&gt;
6495 [nothing]
6496 &lt;/p&gt;&lt;/blockquote&gt;
6497
6498 &lt;p&gt;This is for KDE:&lt;/p&gt;
6499
6500 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6501
6502 &lt;blockquote&gt;&lt;p&gt;
6503 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6504 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6505 ghostscript-x git gnome-audio gnugo granatier gs-common
6506 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6507 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6508 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6509 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6510 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6511 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6512 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6513 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6514 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6515 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6516 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6517 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6518 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6519 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6520 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6521 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6522 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6523 libkrossui4 libmailtools-perl libmime-tools-perl
6524 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6525 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6526 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6527 lirc luatex marble networkstatus noatun-plugins
6528 openoffice.org-writer2latex palapeli palapeli-data parley
6529 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6530 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6531 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6532 ttf-sazanami-gothic
6533 &lt;/p&gt;&lt;/blockquote&gt;
6534
6535 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6536
6537 &lt;blockquote&gt;&lt;p&gt;
6538 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6539 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6540 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6541 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6542 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6543 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6544 kitchensync kiten kjumpingcube klatin klettres klickety klines
6545 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6546 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6547 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6548 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6549 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6550 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6551 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6552 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6553 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6554 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6555 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6556 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6557 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6558 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6559 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6560 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6561 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6562 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6563 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6564 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6565 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6566 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6567 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6568 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6569 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6570 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6571 &lt;/p&gt;&lt;/blockquote&gt;
6572
6573 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6574
6575 &lt;blockquote&gt;&lt;p&gt;
6576 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6577 kdeartwork kdebase kdebase-apps kdebase-workspace
6578 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6579 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6580 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6581 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6582 xscreensaver-screensaver-bsod
6583 &lt;/p&gt;&lt;/blockquote&gt;
6584
6585 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6586
6587 &lt;blockquote&gt;&lt;p&gt;
6588 kdebase-bin konq-plugins konqueror
6589 &lt;/p&gt;&lt;/blockquote&gt;
6590 </description>
6591 </item>
6592
6593 <item>
6594 <title>Gnash buildbot slave and Debian kfreebsd</title>
6595 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6596 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6597 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6598 <description>&lt;p&gt;Answering
6599 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6600 call from the Gnash project&lt;/a&gt; for
6601 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6602 current source, I have set up a virtual KVM machine on the Debian
6603 Edu/Skolelinux virtualization host to test the git source on
6604 Debian/Squeeze. I hope this can help the developers in getting new
6605 releases out more often.&lt;/p&gt;
6606
6607 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6608 I have considered setting up a &lt;a
6609 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6610 machine as well. I have also considered using the kfreebsd
6611 architecture in Debian as a file server in NUUG to get access to the 5
6612 TB zfs volume we currently use to store DV video. Because of this, I
6613 finally got around to do a test installation of Debian/Squeeze with
6614 kfreebsd. Installation went fairly smooth, thought I noticed some
6615 visual glitches in the cdebconf dialogs (black cursor left on the
6616 screen at random locations). Have not gotten very far with the
6617 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6618 fatal problem. Have to spend some more time on it to see if it is
6619 useful as a file server for NUUG. Will try to find time to set up a
6620 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6621 </description>
6622 </item>
6623
6624 <item>
6625 <title>Debian in 3D</title>
6626 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6627 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6628 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6629 <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;
6630
6631 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6632 3D linked in from
6633 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6634 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6635 </description>
6636 </item>
6637
6638 <item>
6639 <title>Software updates 2010-10-24</title>
6640 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6641 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6642 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6643 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6644
6645 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6646 raise money for the project is going well. The lower limit of 10
6647 signers was reached in 24 hours, and so far 13 people have signed it.
6648 More signers and more funding is most welcome, and I am really curious
6649 how far we can get before the time limit of December 24 is reached.
6650 :)&lt;/p&gt;
6651
6652 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6653 about what appear to be a great code coverage tool capable of
6654 generating code coverage stats without any changes to the source code.
6655 It is called
6656 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6657 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6658 It is missing in Debian, but the git source built just fine in Squeeze
6659 after I installed libelf-dev, libdwarf-dev, pkg-config and
6660 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6661 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6662
6663 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6664 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6665 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6666 alpha test release of the Squeeze based Debian Edu /
6667 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6668 release. Give it a try if you need a complete linux solution for your
6669 school, including central infrastructure server, workstations, thin
6670 client servers and diskless workstations. A nice touch added
6671 yesterday is RDP support on the thin client servers, for windows
6672 clients to get a Linux desktop on request.&lt;/p&gt;
6673 </description>
6674 </item>
6675
6676 <item>
6677 <title>Some notes on Flash in Debian and Debian Edu</title>
6678 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6679 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6680 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6681 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6682 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6683 second most popular used package that is missing in Debian. The sixth
6684 most popular is flashplayer-mozilla. This is a clear indication that
6685 working flash is important for Debian users. Around 10 percent of the
6686 users submitting data to popcon.debian.org have this package
6687 installed.&lt;/p&gt;
6688
6689 &lt;p&gt;In the report written by Lars Risan in August 2008
6690&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
6691 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6692 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6693 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6694 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6695 web sites require Flash to work, and lacking working Flash support in
6696 the web browser and the problems with installing it was perceived as a
6697 good reason to stay with Windows.&lt;/p&gt;
6698
6699 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6700 said to be the retarded cousin that did not really understand
6701 everything you told him but could work fairly well. This was a
6702 comment regarding the problems Linux have with proprietary formats and
6703 non-standard web pages, and is sad because it exposes a fairly common
6704 understanding of whose fault it is if web pages that only work in for
6705 example Internet Explorer 6 fail to work on Firefox, and funny because
6706 it explain very well how annoying it is for users when Linux
6707 distributions do not work with the documents they receive or the web
6708 pages they want to visit.&lt;/p&gt;
6709
6710 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6711 and Debian Edu to have a well working Flash implementation in the
6712 distribution, to get at least popular sites as Youtube and Google
6713 Video to working out of the box. For Squeeze, Debian have the chance
6714 to include the latest version of Gnash that will make this happen, as
6715 the new release 0.8.8 was published a few weeks ago and is resting in
6716 unstable. The new version work with more sites that version 0.8.7.
6717 The Gnash maintainers have asked for a freeze exception, but the
6718 release team have not had time to reply to it yet. I hope they agree
6719 with me that Flash is important for the Debian desktop users, and thus
6720 accept the new package into Squeeze.&lt;/p&gt;
6721 </description>
6722 </item>
6723
6724 <item>
6725 <title>Circular package dependencies harms apt recovery</title>
6726 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6727 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6728 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6729 <description>&lt;p&gt;I discovered this while doing
6730 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6731 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6732 in Debian still got circular dependencies, and it is often claimed
6733 that apt and aptitude should be able to handle this just fine, but
6734 some times these dependency loops causes apt to fail.&lt;/p&gt;
6735
6736 &lt;p&gt;An example is from todays
6737 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6738 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6739 causes perl-modules to fail to upgrade. The cause is simple. If a
6740 package fail to unpack, then only part of packages with the circular
6741 dependency might end up being unpacked when unpacking aborts, and the
6742 ones already unpacked will fail to configure in the recovery phase
6743 because its dependencies are unavailable.&lt;/p&gt;
6744
6745 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6746
6747 &lt;blockquote&gt;&lt;pre&gt;
6748 dpkg: dependency problems prevent configuration of perl-modules:
6749 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6750 Version of perl on system is 5.10.0-19lenny2.
6751 dpkg: error processing perl-modules (--configure):
6752 dependency problems - leaving unconfigured
6753 &lt;/pre&gt;&lt;/blockquote&gt;
6754
6755 &lt;p&gt;The perl/perl-modules circular dependency is already
6756 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6757 hopefully be solved as soon as possible, but it is not the only one,
6758 and each one of these loops in the dependency tree can cause similar
6759 failures. Of course, they only occur when there are bugs in other
6760 packages causing the unpacking to fail, but it is rather nasty when
6761 the failure of one package causes the problem to become worse because
6762 of dependency loops.&lt;/p&gt;
6763
6764 &lt;p&gt;Thanks to
6765 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6766 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6767 dependencies
6768 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6769 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6770
6771 &lt;p&gt;Todays testing also exposed a bug in
6772 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6773 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6774 apt-get and aptitude, the latter possibly caused by some circular
6775 dependency. Reported both to BTS to try to get someone to look at
6776 it.&lt;/p&gt;
6777 </description>
6778 </item>
6779
6780 <item>
6781 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6782 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6783 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6784 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6785 <description>&lt;p&gt;This is a
6786 &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;
6787 on my
6788 &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
6789 work&lt;/a&gt; on
6790 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6791 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6792
6793 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6794 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6795 and dhcp3-server-ldap in Debian use the LDAP server. The two
6796 implementations are quite different in how they use LDAP.&lt;/p&gt;
6797
6798 To get this information, I started slapd with debugging enabled and
6799 dumped the debug output to a file to get the LDAP searches performed
6800 on a Debian Edu main-server. Here is a summary.
6801
6802 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6803
6804 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6805 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6806 the web.
6807
6808 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6809 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6810 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6811 reverse entries are in two different subtrees in LDAP with a structure
6812 based on the DNS names, as in tjener.intern and
6813 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6814
6815 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6816 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6817 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6818 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6819 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6820 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6821 forward entries, it is looking for attributes named dnsttl, arecord,
6822 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6823 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6824 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6825 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6826 spfrecord and modifytimestamp. For reverse entries it is looking for
6827 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6828 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6829 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6830 ldapsearch commands could look like this:&lt;/p&gt;
6831
6832 &lt;blockquote&gt;&lt;pre&gt;
6833 ldapsearch -h ldap \
6834 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6835 -s base -x &#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 \
6842 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6843 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6844 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6845 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6846 srvrecord naptrrecord modifytimestamp
6847 &lt;/pre&gt;&lt;/blockquote&gt;
6848
6849 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6850 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6851 example LDAP objects used there. In addition to these objects, the
6852 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6853 also exist.&lt;/p&gt;
6854
6855 &lt;blockquote&gt;&lt;pre&gt;
6856 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6857 objectclass: top
6858 objectclass: dnsdomain
6859 objectclass: domainrelatedobject
6860 dc: tjener
6861 arecord: 10.0.2.2
6862 associateddomain: tjener.intern
6863
6864 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6865 objectclass: top
6866 objectclass: dnsdomain2
6867 objectclass: domainrelatedobject
6868 dc: 2
6869 ptrrecord: tjener.intern
6870 associateddomain: 2.2.0.10.in-addr.arpa
6871 &lt;/pre&gt;&lt;/blockquote&gt;
6872
6873 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6874 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6875 same base as in the tree mode for a object with filter
6876 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6877 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6878 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6879 naptrrecord and modifytimestamp. For reverse entires it also do a
6880 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6881 and the requested attributes are associateddomain, dnsttl and
6882 modifytimestamp. In short, in strict mode the objects with ptrrecord
6883 go away, and the arecord attribute in the forward object is used
6884 instead.&lt;/p&gt;
6885
6886 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6887 like this:&lt;/p&gt;
6888
6889 &lt;blockquote&gt;&lt;pre&gt;
6890 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6891 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6892 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6893 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6894 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6895 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6896
6897 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6898 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6899 &lt;/pre&gt;&lt;/blockquote&gt;
6900
6901 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6902 search for SOA records, which behave similar to the forward and
6903 reverse lookups.&lt;/p&gt;
6904
6905 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6906 specify any objectclass names, and instead look for the attributes it
6907 need to generate a DNS reply. This make it able to work with any
6908 objectclass that provide the needed attributes.&lt;/p&gt;
6909
6910 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6911 dnsdomain2 schemas. The latter is used for reverse entries like
6912 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6913
6914 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6915 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6916 attributes) and domainrelatedobject (for associatedDomain). The use
6917 of structural object classes make it impossible to combine these
6918 classes with the object classes used by DHCP.&lt;/p&gt;
6919
6920 &lt;p&gt;There are other schemas that could be used too, for example the
6921 dnszone structural object class used by Gosa and bind-sdb for the DNS
6922 attributes combined with the domainrelatedobject object class, but in
6923 this case some unused attributes would have to be included as well
6924 (zonename and relativedomainname).&lt;/p&gt;
6925
6926 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6927 mode and not use any of the existing objectclasses (dnsdomain,
6928 dnsdomain2 and dnszone) when one want to combine the DNS information
6929 with DHCP information, and instead create a auxiliary object class
6930 defined something like this (using the attributes defined for
6931 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6932
6933 &lt;blockquote&gt;&lt;pre&gt;
6934 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6935 SUP top
6936 AUXILIARY
6937 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6938 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6939 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6940 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6941 A6Record $ DNAMERecord
6942 ))
6943 &lt;/pre&gt;&lt;/blockquote&gt;
6944
6945 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6946 the domainrelatedobject object class, and allow any entity to include
6947 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6948 developers asking for their view on this schema and if they are
6949 interested in providing such schema with PowerDNS, and I hope my
6950 message will be accepted into their mailing list soon.&lt;/p&gt;
6951
6952 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6953
6954 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6955 the object attributes, and then uses the attributes it want. This
6956 make it harder to figure out exactly what attributes are used, but
6957 thanks to the working example in Debian Edu I can at least get an idea
6958 what is needed without having to read the source code.&lt;/p&gt;
6959
6960 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6961 search filter to use to locate the correct dhcpServer entity is
6962 stored. These are the relevant entries from
6963 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6964
6965 &lt;blockquote&gt;&lt;pre&gt;
6966 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6967 ldap-dhcp-server-cn &quot;dhcp&quot;;
6968 &lt;/pre&gt;&lt;/blockquote&gt;
6969
6970 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6971 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6972 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6973 search result is this entry:&lt;/p&gt;
6974
6975 &lt;blockquote&gt;&lt;pre&gt;
6976 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6977 cn: dhcp
6978 objectClass: top
6979 objectClass: dhcpServer
6980 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6981 &lt;/pre&gt;&lt;/blockquote&gt;
6982
6983 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6984 subtree with DHCP configuration. The DHCP configuration subtree base
6985 is located using a base scope search with base &quot;cn=DHCP
6986 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6987 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6988 The search result is this entry:&lt;/p&gt;
6989
6990 &lt;blockquote&gt;&lt;pre&gt;
6991 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6992 cn: DHCP Config
6993 objectClass: top
6994 objectClass: dhcpService
6995 objectClass: dhcpOptions
6996 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6997 dhcpStatements: ddns-update-style none
6998 dhcpStatements: authoritative
6999 dhcpOption: smtp-server code 69 = array of ip-address
7000 dhcpOption: www-server code 72 = array of ip-address
7001 dhcpOption: wpad-url code 252 = text
7002 &lt;/pre&gt;&lt;/blockquote&gt;
7003
7004 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
7005 all the DHCP configuration is loaded, it is ready to receive requests.
7006 The subtree in Debian Edu contain objects with object classes
7007 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7008 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7009 and information about netmasks, dynamic range etc. Leaving out the
7010 details here because it is not relevant for the focus of my
7011 investigation, which is to see if it is possible to merge dns and dhcp
7012 related computer objects.&lt;/p&gt;
7013
7014 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
7015 of the client (00:00:00:00:00:00 in this example), using a subtree
7016 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
7017 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7018 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
7019 like:&lt;/p&gt;
7020
7021 &lt;blockquote&gt;&lt;pre&gt;
7022 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7023 cn: hostname
7024 objectClass: top
7025 objectClass: dhcpHost
7026 dhcpHWAddress: ethernet 00:00:00:00:00:00
7027 dhcpStatements: fixed-address hostname
7028 &lt;/pre&gt;&lt;/blockquote&gt;
7029
7030 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
7031 The object classes need to have fixed names, and the configuration
7032 need to be stored in a fairly specific LDAP structure. On the
7033 positive side, the invidiual dhcpHost entires can be anywhere without
7034 the DN pointed to by the dhcpServer entries. The latter should make
7035 it possible to group all host entries in a subtree next to the
7036 configuration entries, and this subtree can also be shared with the
7037 DNS server if the schema proposed above is combined with the dhcpHost
7038 structural object class.
7039
7040 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
7041
7042 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
7043 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
7044 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
7045 allowing DNS objects to be stored anywhere under the base cn specified
7046 in the configuration.&lt;/p&gt;
7047
7048 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
7049 regarding which LDAP schemas to use and which LDAP structure to use.
7050 I guess one could implement ones own schema, as long as the
7051 objectclasses and attributes have the names used, but this do not
7052 really help when the DHCP subtree need to have a fairly fixed
7053 structure.&lt;/p&gt;
7054
7055 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
7056 this might work for Debian Edu:&lt;/p&gt;
7057
7058 &lt;blockquote&gt;&lt;pre&gt;
7059 ou=services
7060 cn=machine-info (dhcpService) - dhcpServiceDN points here
7061 cn=dhcp (dhcpServer)
7062 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7063 cn=10.0.2.0 (dhcpSubnet)
7064 cn=group1 (dhcpGroup/dhcpOptions)
7065 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7066 cn=192.168.0.0 (dhcpSubnet)
7067 cn=group1 (dhcpGroup/dhcpOptions)
7068 ou=machines - PowerDNS base points here
7069 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7070 &lt;/pre&gt;&lt;/blockquote&gt;
7071
7072 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
7073 entries to be in the dhcpGroup subtrees, the entries can be stored
7074 there instead of a common machines subtree, and the PowerDNS base
7075 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
7076
7077 &lt;p&gt;The combined object under the machines subtree would look something
7078 like this:&lt;/p&gt;
7079
7080 &lt;blockquote&gt;&lt;pre&gt;
7081 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7082 dc: hostname
7083 objectClass: top
7084 objectClass: dhcpHost
7085 objectclass: domainrelatedobject
7086 objectclass: dnsDomainAux
7087 associateddomain: hostname.intern
7088 arecord: 10.11.12.13
7089 dhcpHWAddress: ethernet 00:00:00:00:00:00
7090 dhcpStatements: fixed-address hostname.intern
7091 &lt;/pre&gt;&lt;/blockquote&gt;
7092
7093 &lt;/p&gt;One could even add the LTSP configuration associated with a given
7094 machine, as long as the required attributes are available in a
7095 auxiliary object class.&lt;/p&gt;
7096 </description>
7097 </item>
7098
7099 <item>
7100 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
7101 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
7102 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
7103 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
7104 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
7105 DHCP services in Debian Edu to use the same LDAP objects for a given
7106 computer, to avoid the possibility of having a inconsistent state for
7107 a computer in LDAP (as in DHCP but no DNS entry or the other way
7108 around) and make it easier to add computers to LDAP.&lt;/p&gt;
7109
7110 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
7111 information finally found a solution that seem to work.&lt;/p&gt;
7112
7113 &lt;p&gt;The old setup required three LDAP objects for a given computer.
7114 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7115 we switch powerdns to use its strict LDAP method (ldap-method=strict
7116 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7117 merged into one while making it impossible to transfer the reverse map
7118 to a slave DNS server.&lt;/p&gt;
7119
7120 &lt;p&gt;If we also replace the object class used to get the DNS related
7121 attributes to one allowing these attributes to be combined with the
7122 dhcphost object class, we can merge the DNS and DHCP entries into one.
7123 I&#39;ve written such object class in the dnsdomainaux.schema file (need
7124 proper OIDs, but that is a minor issue), and tested the setup. It
7125 seem to work.&lt;/p&gt;
7126
7127 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
7128 for both DNS and DHCP, and even the LTSP configuration I suggested in
7129 an earlier email. The combined LDAP object will look something like
7130 this:&lt;/p&gt;
7131
7132 &lt;blockquote&gt;&lt;pre&gt;
7133 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7134 cn: hostname
7135 objectClass: dhcphost
7136 objectclass: domainrelatedobject
7137 objectclass: dnsdomainaux
7138 associateddomain: hostname.intern
7139 arecord: 10.11.12.13
7140 dhcphwaddress: ethernet 00:00:00:00:00:00
7141 dhcpstatements: fixed-address hostname
7142 ldapconfigsound: Y
7143 &lt;/pre&gt;&lt;/blockquote&gt;
7144
7145 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
7146 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7147 before asking DNS to resolve the fixed-adddress. LTSP will use
7148 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
7149
7150 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
7151 dhcphost in a different location, to allow us to put the objects
7152 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7153 that. If I can&#39;t figure out a way to do that, we can still get rid of
7154 the hosts subtree and move all its content into the DHCP Config tree
7155 (which probably should be renamed to be more related to the new
7156 content. I suspect cn=dnsdhcp,ou=services or something like that
7157 might be a good place to put it.&lt;/p&gt;
7158
7159 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7160 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7161 </description>
7162 </item>
7163
7164 <item>
7165 <title>Idea for storing LTSP configuration in LDAP</title>
7166 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7167 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7168 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7169 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7170 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7171 clients, and that this can be used to fetch configuration from LDAP if
7172 Debian Edu choose to store configuration there.&lt;/p&gt;
7173
7174 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7175 to get configuration from LDAP. The idea is to look up the MAC
7176 address of the client in LDAP, and look for attributes on the form
7177 ltspconfigsetting=value, and use this to export SETTING=value to the
7178 LTSP clients.&lt;/p&gt;
7179
7180 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7181 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7182 allowing us to store all information about a computer in one place.&lt;/p&gt;
7183
7184 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7185 this approach. A real LDAP schema for the ltspClientAux objectclass
7186 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7187
7188 &lt;blockquote&gt;&lt;pre&gt;
7189 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7190 #
7191 # Fetch LTSP client settings from LDAP based on MAC address
7192 #
7193 # Uses ethernet address as stored in the dhcpHost objectclass using
7194 # the dhcpHWAddress attribute or ethernet address stored in the
7195 # ieee802Device objectclass with the macAddress attribute.
7196 #
7197 # This module is written to be schema agnostic, and only depend on the
7198 # existence of attribute names.
7199 #
7200 # The LTSP configuration variables are saved directly using a
7201 # ltspConfig prefix and uppercasing the rest of the attribute name.
7202 # To set the SERVER variable, set the ltspConfigServer attribute.
7203 #
7204 # Some LDAP schema should be created with all the relevant
7205 # configuration settings. Something like this should work:
7206 #
7207 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7208 # SUP top
7209 # AUXILIARY
7210 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7211
7212 LDAPSERVER=$(debian-edu-ldapserver)
7213 if [ &quot;$LDAPSERVER&quot; ] ; then
7214 LDAPBASE=$(debian-edu-ldapserver -b)
7215 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7216 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7217 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7218 grep &#39;^ltspConfig&#39; | while read attr value ; do
7219 # Remove prefix and convert to upper case
7220 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7221 # bass value on to clients
7222 eval &quot;$attr=$value; export $attr&quot;
7223 done
7224 done
7225 fi
7226 &lt;/pre&gt;&lt;/blockquote&gt;
7227
7228 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7229 the while block might end up in a subshell causing the variables set
7230 there to not show up in ltsp-config, but if that is the case I am sure
7231 the code can be restructured to make sure the variables are passed on.
7232 I expect that can be solved with some testing. :)&lt;/p&gt;
7233
7234 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7235 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7236
7237 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7238 configuration in LDAP that was created around year 2000 by
7239 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7240 Xperience, Inc., 2000&lt;/a&gt;. I found its
7241 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7242 personal home page over at redhat.com.&lt;/p&gt;
7243 </description>
7244 </item>
7245
7246 <item>
7247 <title>jXplorer, a very nice LDAP GUI</title>
7248 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7249 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7250 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7251 <description>&lt;p&gt;Since
7252 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7253 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7254 LDAP GUI that is even better than luma. The java application
7255 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7256 moving LDAP objects and subtrees using drag-and-drop, and can
7257 authenticate using Kerberos. I have only tested the Kerberos
7258 authentication, but do not have a LDAP setup allowing me to rewrite
7259 LDAP with my test user yet. It is
7260 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7261 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7262 have with it is how it handle errors. If something go wrong, its
7263 non-intuitive behaviour require me to go through some query work list
7264 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7265 </description>
7266 </item>
7267
7268 <item>
7269 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7270 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7271 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7272 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7273 <description>&lt;p&gt;Here is a short update on my &lt;a
7274 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7275 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7276 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7277 not reporting the status for KDE, because the upgrade crashes when
7278 aptitude try because of missing conflicts
7279 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7280 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7281
7282 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7283 complete list of the installed packages. Based on this I see these
7284 differences when I did a test run today. As usual, I do not really
7285 know what the correct set of packages would be, but thought it best to
7286 publish the difference.&lt;/p&gt;
7287
7288 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7289
7290 &lt;blockquote&gt;&lt;p&gt;
7291 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7292 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7293 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7294 libgtksourceview-common libpt-1.10.10-plugins-alsa
7295 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7296 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7297 python-4suite-xml python-eggtrayicon python-gtkhtml2
7298 python-gtkmozembed svgalibg1 xserver-xephyr zip
7299 &lt;/p&gt;&lt;/blockquote&gt;
7300
7301 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7302
7303 &lt;blockquote&gt;&lt;p&gt;
7304 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7305 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7306 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7307 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7308 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7309 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7310 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7311 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7312 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7313 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7314 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7315 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7316 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7317 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7318 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7319 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7320 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7321 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7322 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7323 mysql-common swfdec-gnome totem-gstreamer wodim
7324 &lt;/p&gt;&lt;/blockquote&gt;
7325
7326 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7327
7328 &lt;blockquote&gt;&lt;p&gt;
7329 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7330 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7331 xserver-xorg-input-all xserver-xorg-input-evdev
7332 xserver-xorg-input-kbd xserver-xorg-input-mouse
7333 xserver-xorg-input-synaptics xserver-xorg-video-all
7334 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7335 xserver-xorg-video-chips xserver-xorg-video-cirrus
7336 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7337 xserver-xorg-video-glint xserver-xorg-video-i128
7338 xserver-xorg-video-i740 xserver-xorg-video-mach64
7339 xserver-xorg-video-mga xserver-xorg-video-neomagic
7340 xserver-xorg-video-nouveau xserver-xorg-video-nv
7341 xserver-xorg-video-r128 xserver-xorg-video-radeon
7342 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7343 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7344 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7345 xserver-xorg-video-sis xserver-xorg-video-sisusb
7346 xserver-xorg-video-tdfx xserver-xorg-video-tga
7347 xserver-xorg-video-trident xserver-xorg-video-tseng
7348 xserver-xorg-video-vesa xserver-xorg-video-vmware
7349 xserver-xorg-video-voodoo
7350 &lt;/p&gt;&lt;/blockquote&gt;
7351
7352 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7353
7354 &lt;blockquote&gt;&lt;p&gt;
7355 deskbar-applet xserver-xorg xserver-xorg-core
7356 xserver-xorg-input-wacom xserver-xorg-video-intel
7357 xserver-xorg-video-openchrome
7358 &lt;/p&gt;&lt;/blockquote&gt;
7359
7360 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7361 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7362 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7363 No idea when it hits Squeeze, but when it does I hope it will reduce
7364 the difference somewhat.
7365 </description>
7366 </item>
7367
7368 <item>
7369 <title>LUMA, a very nice LDAP GUI</title>
7370 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7371 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7372 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7373 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7374 directory in Debian Edu, and in the process I started to miss a GUI
7375 tool to browse the LDAP tree. The only one I was able to find in
7376 Debian/Squeeze and Lenny is
7377 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7378 be a great tool to get a overview of the current LDAP directory
7379 populated by default in Skolelinux. Thanks to it, I have been able to
7380 find empty and obsolete subtrees, misplaced objects and duplicate
7381 objects. It will be installed by default in Debian/Squeeze. If you
7382 are working with LDAP, give it a go. :)&lt;/p&gt;
7383
7384 &lt;p&gt;I did notice one problem with it I have not had time to report to
7385 the BTS yet. There is no .desktop file in the package, so the tool do
7386 not show up in the Gnome and KDE menus, but only deep down in in the
7387 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7388 released.&lt;/p&gt;
7389
7390 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7391 like to move objects and remove subtrees directly in the GUI, but have
7392 not found a way to do that with LUMA yet. So in the mean time, I use
7393 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7394
7395 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7396 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7397
7398 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7399 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7400 useful GUI alternative. It seem like a good tool, but is unmaintained
7401 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7402 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7403 </description>
7404 </item>
7405
7406 <item>
7407 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7408 <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>
7409 <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>
7410 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7411 <description>&lt;p&gt;A while back, I
7412 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7413 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7414 for storing DNS and DHCP information in LDAP to combine the two sets
7415 of information into one LDAP object representing a computer.&lt;/p&gt;
7416
7417 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7418 the dhcpHost object class auxiliary, to allow it to be combined with
7419 the dNSDomain object class, and thus forming one object for one
7420 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7421
7422 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7423 without also changing the assigned number for the object class, and I
7424 do not know enough about LDAP schema design to do that properly for
7425 Debian Edu.&lt;/p&gt;
7426
7427 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7428 the
7429 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7430 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7431 available today from IETF.&lt;/p&gt;
7432
7433 &lt;pre&gt;
7434 --- dhcp.schema (revision 65192)
7435 +++ dhcp.schema (working copy)
7436 @@ -376,7 +376,7 @@
7437 objectclass ( 2.16.840.1.113719.1.203.6.6
7438 NAME &#39;dhcpHost&#39;
7439 DESC &#39;This represents information about a particular client&#39;
7440 - SUP top
7441 + SUP top AUXILIARY
7442 MUST cn
7443 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7444 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7445 &lt;/pre&gt;
7446
7447 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7448 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7449 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7450
7451 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7452 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7453 </description>
7454 </item>
7455
7456 <item>
7457 <title>Calling tasksel like the installer, while still getting useful output</title>
7458 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7460 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7461 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7462 installs packages during the normal debian-installer run. Until now,
7463 I have ended up letting tasksel do the work, with the annoying problem
7464 of not getting any feedback at all when something fails (like a
7465 conffile question from dpkg or a download that fails), using code like
7466 this:
7467
7468 &lt;blockquote&gt;&lt;pre&gt;
7469 export DEBIAN_FRONTEND=noninteractive
7470 tasksel --new-install
7471 &lt;/pre&gt;&lt;/blockquote&gt;
7472
7473 This would invoke tasksel, let its automatic task selection pick the
7474 tasks to install, and continue to install the requested tasks without
7475 any output what so ever.
7476
7477 Recently I revisited this problem while working on the automatic
7478 package upgrade testing, because tasksel would some times hang without
7479 any useful feedback, and I want to see what is going on when it
7480 happen. Then it occured to me, I can parse the output from tasksel
7481 when asked to run in test mode, and use that aptitude command line
7482 printed by tasksel then to simulate the tasksel run. I ended up using
7483 code like this:
7484
7485 &lt;blockquote&gt;&lt;pre&gt;
7486 export DEBIAN_FRONTEND=noninteractive
7487 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7488 $cmd
7489 &lt;/pre&gt;&lt;/blockquote&gt;
7490
7491 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7492 --without-recommends -o APT::Install-Recommends=no -y install
7493 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7494 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7495 laptop task and all packages with priority standard , required and
7496 important, just like tasksel would have done it during
7497 installation.&lt;/p&gt;
7498
7499 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7500 install packages without using debconf-apt-progress, for use cases
7501 like this.&lt;/p&gt;
7502 </description>
7503 </item>
7504
7505 <item>
7506 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7507 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7508 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7509 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7510 <description>&lt;p&gt;My
7511 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7512 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7513 finally made the upgrade logs available from
7514 &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;.
7515 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7516 apt and aptitude, and found their differences interesting. This time
7517 I will only focus on their removal plans.&lt;/p&gt;
7518
7519 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7520 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7521 surprising part is that it want to remove xorg and all
7522 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7523 sure why. When asking aptitude to do the same, it want to remove 129
7524 packages, but most of them are library packages I suspect are no
7525 longer needed. Both of them want to remove bluetooth packages, which
7526 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7527
7528 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7529 which seem like a bad idea and xorg the same way as with Gnome. Asking
7530 aptitude for the same, it wants to remove 192 packages, none which are
7531 too surprising.&lt;/p&gt;
7532
7533 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7534 and avoided, and perhaps others as well. Here are the complete list
7535 of planned removals. The complete logs is available from the URL
7536 above. Note if you want to repeat these tests, that the upgrade test
7537 for kde+apt-get hung in the tasksel setup because of dpkg asking
7538 conffile questions. No idea why. I worked around it by using
7539 &#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
7540 continue.&lt;/p&gt;
7541
7542 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7543 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7544 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7545 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7546 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7547 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7548 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7549 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7550 xserver-xorg-input-kbd xserver-xorg-input-mouse
7551 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7552 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7553 xserver-xorg-video-ati xserver-xorg-video-chips
7554 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7555 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7556 xserver-xorg-video-glint xserver-xorg-video-i128
7557 xserver-xorg-video-i740 xserver-xorg-video-imstt
7558 xserver-xorg-video-intel xserver-xorg-video-mach64
7559 xserver-xorg-video-mga xserver-xorg-video-neomagic
7560 xserver-xorg-video-nsc xserver-xorg-video-nv
7561 xserver-xorg-video-openchrome xserver-xorg-video-r128
7562 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7563 xserver-xorg-video-rendition xserver-xorg-video-s3
7564 xserver-xorg-video-s3virge xserver-xorg-video-savage
7565 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7566 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7567 xserver-xorg-video-tga xserver-xorg-video-trident
7568 xserver-xorg-video-tseng xserver-xorg-video-v4l
7569 xserver-xorg-video-vesa xserver-xorg-video-vga
7570 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7571 xulrunner-1.9-gnome-support&lt;/p&gt;
7572
7573 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7574
7575 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7576 djvulibre-desktop finger gnome-app-install gnome-mount
7577 gnome-network-admin gnome-spell gnome-vfs-obexftp
7578 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7579 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7580 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7581 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7582 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7583 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7584 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7585 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7586 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7587 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7588 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7589 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7590 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7591 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7592 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7593 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7594 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7595 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7596 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7597 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7598 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7599 openoffice.org-writer2latex openssl-blacklist p7zip
7600 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7601 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7602 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7603 swfdec-mozilla totem-gstreamer update-manager wodim
7604 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7605 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7606 zip&lt;/p&gt;
7607
7608 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7609
7610 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7611 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7612 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7613 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7614 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7615 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7616 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7617 xserver-xorg-input-kbd xserver-xorg-input-mouse
7618 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7619 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7620 xserver-xorg-video-ati xserver-xorg-video-chips
7621 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7622 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7623 xserver-xorg-video-glint xserver-xorg-video-i128
7624 xserver-xorg-video-i740 xserver-xorg-video-imstt
7625 xserver-xorg-video-intel xserver-xorg-video-mach64
7626 xserver-xorg-video-mga xserver-xorg-video-neomagic
7627 xserver-xorg-video-nsc xserver-xorg-video-nv
7628 xserver-xorg-video-openchrome xserver-xorg-video-r128
7629 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7630 xserver-xorg-video-rendition xserver-xorg-video-s3
7631 xserver-xorg-video-s3virge xserver-xorg-video-savage
7632 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7633 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7634 xserver-xorg-video-tga xserver-xorg-video-trident
7635 xserver-xorg-video-tseng xserver-xorg-video-v4l
7636 xserver-xorg-video-vesa xserver-xorg-video-vga
7637 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7638
7639 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7640 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7641 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7642 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7643 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7644 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7645 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7646 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7647 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7648 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7649 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7650 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7651 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7652 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7653 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7654 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7655 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7656 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7657 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7658 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7659 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7660 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7661 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7662 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7663 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7664 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7665 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7666 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7667 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7668 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7669 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7670 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7671 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7672 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7673 texlive-common texlive-doc-base texlive-fonts-recommended
7674 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7675 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7676 xulrunner-1.9&lt;/p&gt;
7677
7678 </description>
7679 </item>
7680
7681 <item>
7682 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7683 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7685 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7686 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7687 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7688 have been discovered and reported in the process
7689 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7690 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7691 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7692 kdebase-workspace-data), and to get a more regular testing going on, I
7693 am working on a script to automate the test.&lt;/p&gt;
7694
7695 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7696 Gnome or KDE desktop installation inside the chroot before upgrading
7697 it. To ensure no services are started in the chroot, a policy-rc.d
7698 script is inserted. To make sure tasksel believe it is to install a
7699 desktop on a laptop, the tasksel tests are replaced in the chroot
7700 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7701
7702 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7703 currently always fail because udev refuses to upgrade with the kernel
7704 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7705 is created. The bug report
7706 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7707 this problem do not trigger in a chroot, but I touch the file anyway
7708 to make sure the upgrade go well. Testing on virtual and real
7709 hardware have failed me because of udev so far, and creating this file
7710 do the trick in such settings anyway. This is a
7711 &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
7712 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7713 maintainer because he lack the resources to rewrite udev to keep
7714 working with old kernels or something like that. I really wish the
7715 udev upstream would keep udev backwards compatible, to avoid such
7716 upgrade problem, but given that they fail to do so, I guess
7717 documenting the way out of this mess is the best option we got for
7718 Debian Squeeze.&lt;/p&gt;
7719
7720 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7721 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7722 trick:&lt;/p&gt;
7723
7724 &lt;blockquote&gt;&lt;pre&gt;
7725 #!/bin/sh
7726 set -ex
7727
7728 if [ &quot;$1&quot; ] ; then
7729 desktop=$1
7730 else
7731 desktop=gnome
7732 fi
7733
7734 from=lenny
7735 to=squeeze
7736
7737 exec &amp;lt; /dev/null
7738 unset LANG
7739 mirror=http://ftp.skolelinux.org/debian
7740 tmpdir=chroot-$from-upgrade-$to-$desktop
7741 fuser -mv .
7742 debootstrap $from $tmpdir $mirror
7743 chroot $tmpdir aptitude update
7744 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7745 #!/bin/sh
7746 exit 101
7747 EOF
7748 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7749 exit_cleanup() {
7750 umount $tmpdir/proc
7751 }
7752 mount -t proc proc $tmpdir/proc
7753 # Make sure proc is unmounted also on failure
7754 trap exit_cleanup EXIT INT
7755
7756 chroot $tmpdir aptitude -y install debconf-utils
7757
7758 # Make sure tasksel autoselection trigger. It need the test scripts
7759 # to return the correct answers.
7760 echo tasksel tasksel/desktop multiselect $desktop | \
7761 chroot $tmpdir debconf-set-selections
7762
7763 # Include the desktop and laptop task
7764 for test in desktop laptop ; do
7765 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7766 #!/bin/sh
7767 exit 2
7768 EOF
7769 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7770 done
7771
7772 DEBIAN_FRONTEND=noninteractive
7773 DEBIAN_PRIORITY=critical
7774 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7775 chroot $tmpdir tasksel --new-install
7776
7777 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7778 chroot $tmpdir aptitude update
7779 touch $tmpdir/etc/udev/kernel-upgrade
7780 chroot $tmpdir aptitude -y dist-upgrade
7781 fuser -mv
7782 &lt;/pre&gt;&lt;/blockquote&gt;
7783
7784 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7785 with aptitude, but I have not had time to look at how they behave
7786 differently so far. I hope to get a cron job running to do the test
7787 regularly and post the result on the web. The Gnome upgrade currently
7788 work, while the KDE upgrade fail because of the bug in
7789 kdebase-workspace-data&lt;/p&gt;
7790
7791 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7792 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7793 post, so I will refrain from trying. I can report that for Gnome,
7794 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7795 remove and 1 not upgraded and 1024MB need to be downloaded while for
7796 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7797 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7798
7799 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7800 is able to migrate to dependency based boot sequencing and parallel
7801 booting without a hitch. Was unsure if there were still bugs with
7802 packages failing to clean up their obsolete init.d script during
7803 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7804 packages.&lt;/p&gt;
7805 </description>
7806 </item>
7807
7808 <item>
7809 <title>Upstart or sysvinit - as init.d scripts see it</title>
7810 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7812 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7813 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7814 scripts to migrate (some of) their operations to upstart job while
7815 keeping the init.d for hurd and kfreebsd. The packages with such
7816 needs will need a way to get their init.d scripts to behave
7817 differently when used with sysvinit and with upstart. Because of
7818 this, I had a look at the environment variables set when a init.d
7819 script is running under upstart, and when it is not.&lt;/p&gt;
7820
7821 &lt;p&gt;With upstart, I notice these environment variables are set when a
7822 script is started from rcS.d/ (ignoring some irrelevant ones like
7823 COLUMNS):&lt;/p&gt;
7824
7825 &lt;blockquote&gt;&lt;pre&gt;
7826 DEFAULT_RUNLEVEL=2
7827 previous=N
7828 PREVLEVEL=
7829 RUNLEVEL=
7830 runlevel=S
7831 UPSTART_EVENTS=startup
7832 UPSTART_INSTANCE=
7833 UPSTART_JOB=rc-sysinit
7834 &lt;/pre&gt;&lt;/blockquote&gt;
7835
7836 &lt;p&gt;With sysvinit, these environment variables are set for the same
7837 script.&lt;/p&gt;
7838
7839 &lt;blockquote&gt;&lt;pre&gt;
7840 INIT_VERSION=sysvinit-2.88
7841 previous=N
7842 PREVLEVEL=N
7843 RUNLEVEL=S
7844 runlevel=S
7845 &lt;/pre&gt;&lt;/blockquote&gt;
7846
7847 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7848 sysvinit are not set by upstart. Not sure if it is intentional or not
7849 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7850
7851 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7852 looking for the UPSTART_JOB environment variable seem to be a good
7853 choice.&lt;/p&gt;
7854 </description>
7855 </item>
7856
7857 <item>
7858 <title>A manual for standards wars...</title>
7859 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7860 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7861 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7862 <description>&lt;p&gt;Via the
7863 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7864 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7865 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7866 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7867 following the standards wars of today.&lt;/p&gt;
7868 </description>
7869 </item>
7870
7871 <item>
7872 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7873 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7874 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7875 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7876 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7877 to get a list of the machine types in use thanks to the DMI
7878 information extracted from each machine. The script to do so is
7879 included in the sitesummary package, and here is example output from
7880 the Skolelinux build servers:&lt;/p&gt;
7881
7882 &lt;blockquote&gt;&lt;pre&gt;
7883 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7884 vendor count
7885 Dell Computer Corporation 1
7886 PowerEdge 1750 1
7887 IBM 1
7888 eserver xSeries 345 -[8670M1X]- 1
7889 Intel 2
7890 [no-dmi-info] 3
7891 maintainer:~#
7892 &lt;/pre&gt;&lt;/blockquote&gt;
7893
7894 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7895 provided in each machine. Here there are Intel machines without model
7896 information listed with Intel as vendor and no model, and virtual Xen
7897 machines listed as [no-dmi-info]. One can add -l as a command line
7898 option to list the individual machines.&lt;/p&gt;
7899
7900 &lt;p&gt;A larger list is
7901 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7902 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7903 provide the basic sitesummary report publicly. In their report there
7904 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7905 their machines, and as sitesummary is available in both distributions,
7906 it is trivial to get all of them to report to the same central
7907 collector.&lt;/p&gt;
7908 </description>
7909 </item>
7910
7911 <item>
7912 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7913 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7914 <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>
7915 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7916 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7917 start at boot when an NVidia video card is used is handled. The
7918 problem seem to be that the nvidia X.org driver uses a long time to
7919 initialize, and this duration is longer than kdm is configured to
7920 wait.&lt;/p&gt;
7921
7922 &lt;p&gt;I came across two bugs related to this issue,
7923 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7924 against initscripts and passed on to nvidia-glx when it became obvious
7925 that the nvidia drivers were involved, and
7926 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7927 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7928
7929 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7930 problem nvidia video card owners experience and make sure the Debian
7931 distribution work out of the box for these users. The nvidia driver
7932 maintainers expect kdm to be set up to wait longer, while kdm expect
7933 the nvidia driver maintainers to fix the driver to start faster, and
7934 while they wait for each other I guess the users end up switching to a
7935 distribution that work for them. I have no idea what the solution is,
7936 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7937
7938 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7939 </description>
7940 </item>
7941
7942 <item>
7943 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7944 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7945 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7946 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7947 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7948 The feature seem to hold up pretty well, but three fairly serious
7949 issues are known and should be solved:
7950
7951 &lt;p&gt;&lt;ul&gt;
7952
7953 &lt;li&gt;The wicd package seen to
7954 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7955 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7956 parallel booting is enabled. No idea why, but the wicd maintainer
7957 seem to be on the case.&lt;/li&gt;
7958
7959 &lt;li&gt;The nvidia X driver seem to
7960 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7961 triggered more easily when parallel booting is in effect. The
7962 maintainer is on the case.&lt;/li&gt;
7963
7964 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7965 sequencing (the shutdown is broken) when old file-rc users
7966 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7967 sysv-rc. One way to solve it would be for file-rc to create
7968 /etc/init.d/.legacy-bootordering, and another is to try to make
7969 sysv-rc more robust. Will investigate some more and probably upload a
7970 workaround in sysv-rc to help those trying to move from file-rc to
7971 sysv-rc get a working shutdown.&lt;/li&gt;
7972
7973 &lt;/ul&gt;&lt;/p&gt;
7974
7975 &lt;p&gt;All in all not many surprising issues, and all of them seem
7976 solvable before Squeeze is released. In addition to these there are
7977 some packages with bugs in their dependencies and run level settings,
7978 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7979
7980 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7981 the BTS, please usertag the report to get it to show up at
7982 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7983 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7984
7985 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7986 </description>
7987 </item>
7988
7989 <item>
7990 <title>More flexible firmware handling in debian-installer</title>
7991 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7992 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7993 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7994 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7995 found time today to return to the project. Having to spend less time
7996 working dependency based boot in debian, as it is almost complete now,
7997 definitely helped freeing some time.&lt;/p&gt;
7998
7999 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
8000 include some firmware packages on the Debian Edu CDs, those needed to
8001 get disk and network controllers working. Without having these
8002 firmware packages available during installation, it is impossible to
8003 install Debian Edu on the given machine, and because our target group
8004 are non-technical people, asking them to provide firmware packages on
8005 an external medium is a support pain. Initially, I expected it to be
8006 enough to include the firmware packages on the CD to get
8007 debian-installer to find and use them. This proved to be wrong.
8008 Next, I hoped it was enough to symlink the relevant firmware packages
8009 to some useful location on the CD (tried /cdrom/ and
8010 /cdrom/firmware/). This also proved to not work, and at this point I
8011 found time to look at the debian-installer code to figure out what was
8012 going to work.&lt;/p&gt;
8013
8014 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
8015 look revealed that it would only look for firmware packages outside
8016 the installation media, so the CD was never checked for firmware
8017 packages. It would only check USB sticks, floppies and other
8018 &quot;external&quot; media devices. Today I changed it to also look in the
8019 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8020 solve the problem I ran into with Debian edu. I also changed it to
8021 look in /firmware/, to make sure the installer also find firmware
8022 provided in the initrd when booting the installer via PXE, to allow us
8023 to provide the same feature in the PXE setup included in Debian
8024 Edu.&lt;/p&gt;
8025
8026 &lt;p&gt;To make sure firmware deb packages with a license questions are not
8027 activated without asking if the license is accepted, I extended
8028 hw-detect to look for preinst scripts in the firmware packages, and
8029 run these before activating the firmware during installation. The
8030 license question is asked using debconf in the preinst, so this should
8031 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
8032
8033 &lt;p&gt;If you want to discuss the details of these features, please
8034 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
8035 </description>
8036 </item>
8037
8038 <item>
8039 <title>Parallellized boot is now the default in Debian/unstable</title>
8040 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
8041 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
8042 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
8043 <description>&lt;p&gt;Since this evening, parallel booting is the default in
8044 Debian/unstable for machines using dependency based boot sequencing.
8045 Apparently the testing of concurrent booting has been wider than
8046 expected, if I am to believe the
8047 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8048 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
8049 with the feature this weekend, to give us some time to detect any
8050 remaining problems before Squeeze is frozen. If serious problems are
8051 detected, it is simple to change the default back to sequential boot.
8052 The upload of the new sysvinit package also activate a new upstream
8053 version.&lt;/p&gt;
8054
8055 More information about
8056 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8057 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
8058 currently possible to disable parallel booting when one run into
8059 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
8060
8061 &lt;blockquote&gt;&lt;pre&gt;
8062 CONCURRENCY=none
8063 &lt;/pre&gt;&lt;/blockquote&gt;
8064
8065 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8066 the BTS, please usertag the report to get it to show up at
8067 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8068 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8069 </description>
8070 </item>
8071
8072 <item>
8073 <title>Sitesummary tip: Listing MAC address of all clients</title>
8074 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
8075 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
8076 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
8077 <description>&lt;p&gt;In the recent Debian Edu versions, the
8078 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
8079 system&lt;/a&gt; is used to keep track of the machines in the school
8080 network. Each machine will automatically report its status to the
8081 central server after boot and once per night. The network setup is
8082 also reported, and using this information it is possible to get the
8083 MAC address of all network interfaces in the machines. This is useful
8084 to update the DHCP configuration.&lt;/p&gt;
8085
8086 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
8087 ist all MAC addresses of all machines reporting to sitesummary. Run
8088 this on the collector host:&lt;/p&gt;
8089
8090 &lt;blockquote&gt;&lt;pre&gt;
8091 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
8092 &lt;/pre&gt;&lt;/blockquote&gt;
8093
8094 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
8095 line per machine and with space between the MAC addresses.&lt;/p&gt;
8096
8097 &lt;p&gt;To allow system administrators easier job at adding static DHCP
8098 addresses for hosts, it would be possible to extend this to fetch
8099 machine information from sitesummary and update the DHCP and DNS
8100 tables in LDAP using this information. Such tool is unfortunately not
8101 written yet.&lt;/p&gt;
8102 </description>
8103 </item>
8104
8105 <item>
8106 <title>systemd, an interesting alternative to upstart</title>
8107 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
8108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
8109 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
8110 <description>&lt;p&gt;The last few days a new boot system called
8111 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
8112 has been
8113 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
8114
8115 to the free software world. I have not yet had time to play around
8116 with it, but it seem to be a very interesting alternative to
8117 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
8118 a good alternative for Debian when we are able to switch to an event
8119 based boot system. Tollef is
8120 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
8121 systemd into Debian, and I look forward to seeing how well it work. I
8122 like the fact that systemd handles init.d scripts with dependency
8123 information natively, allowing them to run in parallel where upstart
8124 at the moment do not.&lt;/p&gt;
8125
8126 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
8127 platform support. It only work on recent Linux kernels, and also need
8128 some new kernel features enabled to function properly. This means
8129 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8130 system. Not sure how that will be handled if systemd proves to be the
8131 way forward.&lt;/p&gt;
8132
8133 &lt;p&gt;In the mean time, based on the
8134 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8135 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
8136 decided to enable full parallel booting as the default in Debian as
8137 soon as possible (probably this weekend or early next week), to see if
8138 there are any remaining serious bugs in the init.d dependencies. A
8139 new version of the sysvinit package implementing this change is
8140 already in experimental. If all go well, Squeeze will be released
8141 with parallel booting enabled by default.&lt;/p&gt;
8142 </description>
8143 </item>
8144
8145 <item>
8146 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
8147 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
8148 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
8149 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
8150 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
8151 complete, so complete that it is actually possible to run all the
8152 init.d scripts in parallell based on these dependencies. If you want
8153 to test your Squeeze system, make sure
8154 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8155 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8156 /etc/default/rcS:&lt;/p&gt;
8157
8158 &lt;blockquote&gt;&lt;pre&gt;
8159 CONCURRENCY=makefile
8160 &lt;/pre&gt;&lt;/blockquote&gt;
8161
8162 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8163 scripts in parallel using the dependency information stored in
8164 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8165 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8166 to try to start the kdm and gdm scripts as early as possible, and will
8167 start the facilities required by kdm or gdm as early as possible to
8168 make this happen.&lt;/p&gt;
8169
8170 &lt;p&gt;Give it a try, and see if you like the result. If some services
8171 fail to start properly, it is most likely because they have incomplete
8172 init.d script dependencies in their startup script (or some of their
8173 dependent scripts have incomplete dependencies). Report bugs and get
8174 the package maintainers to fix it. :)&lt;/p&gt;
8175
8176 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8177 manage to get the init.d script dependencies complete and correct. I
8178 expect we will get there in Squeeze+1, if we get manage to test and
8179 fix the remaining issues.&lt;/p&gt;
8180
8181 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8182 the BTS, please usertag the report to get it to show up at
8183 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8184 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8185 </description>
8186 </item>
8187
8188 <item>
8189 <title>Debian has switched to dependency based boot sequencing</title>
8190 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8192 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8193 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8194 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8195 have been migrated to using dependency based boot sequencing. This
8196 conclude work me and others have been doing for the last three days.
8197 It feels great to see this finally part of the default Debian
8198 installation. Now we just need to weed out the last few problems that
8199 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8200
8201 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8202 fixing the more fundamental problem of handing the event based
8203 non-predictable kernel in the early boot.&lt;/p&gt;
8204 </description>
8205 </item>
8206
8207 <item>
8208 <title>Taking over sysvinit development</title>
8209 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8210 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8211 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8212 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8213 the existing sysvinit upstream developer, I decided a few weeks ago to
8214 take over the package and become the new upstream. The number of
8215 patches to track for the Debian package was becoming a burden, and the
8216 lack of synchronization between the distribution made it hard to keep
8217 the package up to date.&lt;/p&gt;
8218
8219 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8220 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8221 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8222 and Fedora), based on the patches currently in use in these
8223 distributions. We Debian maintainers plan to move to this tarball as
8224 the new upstream as soon as we find time to do the merge. Since the
8225 new tarball was created, we agreed with Werner at SuSe to make a new
8226 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8227 development there. The project is registered and currently waiting
8228 for approval by the Savannah administrators, and as soon as it is
8229 approved, we will import the old versions from svn and continue
8230 working on the future release.&lt;/p&gt;
8231
8232 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8233 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8234 </description>
8235 </item>
8236
8237 <item>
8238 <title>Debian boots quicker and quicker</title>
8239 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8241 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8242 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8243 people involved in the boot system on Debian and Ubuntu, to see if we
8244 could find more ways to speed up the boot system. This was an Ubuntu
8245 funded
8246 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8247 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8248 of boot systems, and ways to handle the increasing number of boot
8249 issues introduced by the Linux kernel becoming more and more
8250 asynchronous and event base. The Ubuntu approach using udev and
8251 upstart might be a good way forward. Time will show.&lt;/p&gt;
8252
8253 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8254 process in Debian. All of these should be applied to get a quick
8255 boot:&lt;/p&gt;
8256
8257 &lt;ul&gt;
8258
8259 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8260
8261 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8262 clock is in UTC.&lt;/li&gt;
8263
8264 &lt;li&gt;Install and activate the insserv package to enable
8265 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8266 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8267
8268 &lt;/ul&gt;
8269
8270 These points are based on the Google summer of code work done by
8271 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8272 Villegas&lt;/a&gt;.
8273
8274 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8275 unstable yesterday. When we tested it, we were able to cut 6 seconds
8276 from the boot sequence. It depend on very correct dependency
8277 declaration in all init.d scripts, so I expect us to find edge cases
8278 where the dependences in some scripts are slightly wrong when we start
8279 using this.&lt;/p&gt;
8280
8281 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8282 introduced by Raphael Geissert today, one that could affect the
8283 startup speed as well. Instead of starting some scripts concurrently
8284 from rcS.d/ and another set of scripts from rc2.d/, it would be
8285 possible to run a of them in the same process. A quick way to test
8286 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8287 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8288 </description>
8289 </item>
8290
8291 <item>
8292 <title>BSAs påstander om piratkopiering møter motstand</title>
8293 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8294 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8295 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8296 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8297 programvareselskapene som Microsoft og Apple, publisert en rapport der
8298 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8299 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8300 dager siden kom
8301 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8302 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8303 dagene. Et spesielt interessant kommentar fra Sverige,
8304 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8305 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8306
8307 &lt;blockquote&gt;
8308 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8309 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8310 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8311 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8312 &lt;/blockquote&gt;
8313
8314 &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
8315 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8316 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8317 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8318 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8319
8320 &lt;p&gt;Fant lenkene via &lt;a
8321 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8322 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8323 </description>
8324 </item>
8325
8326 <item>
8327 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8328 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8329 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8330 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8331 <description>&lt;p&gt;Kom over
8332 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8333 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8334 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8335 jobber til daglig. En rask opptelling forteller meg at vi har 490
8336 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8337 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8338 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8339 </description>
8340 </item>
8341
8342 <item>
8343 <title>Kryptert harddisk - naturligvis</title>
8344 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8346 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8347 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8348 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8349 når en tar tap av arbeidstid, fortrolige dokumenter,
8350 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8351 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8352 til at jeg har kryptert harddisken på både kontormaskinen og min
8353 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8354 komme på avveie, den første informasjon relatert til jobben min ved
8355 Universitetet i Oslo, og den andre relatert til blant annet
8356 foreningsarbeide. Kryptering av diskene gjør at det er lite
8357 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8358 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8359 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8360 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8361 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8362 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8363 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8364 det er gjort slik jeg gjør det er minimale, og gevinstene er
8365 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8366 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8367
8368 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8369 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8370 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8371 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8372 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8373 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8374 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8375 betydelige.&lt;/p&gt;
8376 </description>
8377 </item>
8378
8379 <item>
8380 <title>Two projects that have improved the quality of free software a lot</title>
8381 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8382 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8383 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8384 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8385 quality of free software, and I wanted to mention both in case someone
8386 do not yet know them.&lt;/p&gt;
8387
8388 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8389 tool to detect and expose errors in the memory handling of programs.
8390 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8391 and it will report any problems on stdout. It is even better if the
8392 program include debug information. With debug information, it is able
8393 to report the source file name and line number where the problem
8394 occurs. It can report things like &#39;reading past memory block in file
8395 X line N, the memory block was allocated in file Y, line M&#39;, and
8396 &#39;using uninitialised value in control logic&#39;. This tool has made it
8397 trivial to investigate reproducible crash bugs in programs, and have
8398 reduced the number of this kind of bugs in free software a lot.
8399
8400 &lt;p&gt;The second one is
8401 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8402 a source code checker. It is able to process the source of a program
8403 and find problems in the logic without running the program. It
8404 started out as the Stanford Checker and became well known when it was
8405 used to find bugs in the Linux kernel. It is now a commercial tool
8406 and the company behind it is running
8407 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8408 free software community, where a lot of free software projects get
8409 their source checked for free. Several thousand defects have been
8410 found and fixed so far. It can find errors like &#39;lock L taken in file
8411 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8412 Y lines O to P can never be executed&#39;. The projects included in the
8413 community service project have managed to get rid of a lot of
8414 reliability problems thanks to Coverity.&lt;/p&gt;
8415
8416 &lt;p&gt;I believe tools like this, that are able to automatically find
8417 errors in the source, are vital to improve the quality of software and
8418 make sure we can get rid of the crashing and failing software we are
8419 surrounded by today.&lt;/p&gt;
8420 </description>
8421 </item>
8422
8423 <item>
8424 <title>No patch is not better than a useless patch</title>
8425 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8426 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8427 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8428 <description>&lt;p&gt;Julien Blache
8429 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8430 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8431 patch allow one to discuss a concrete and proposed solution, and also
8432 prove that the issue at hand is important enough for someone to spent
8433 time on fixing it. No patch do not provide any of these positive
8434 properties.&lt;/p&gt;
8435 </description>
8436 </item>
8437
8438 <item>
8439 <title>Standardize on protocols and formats, not vendors and applications</title>
8440 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8441 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8442 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8443 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8444 very good one to form a long lived computer infrastructure. It is the
8445 simple one, lost by many in todays computer industry: Standardize on
8446 open network protocols and open exchange/storage formats, not applications.
8447 Applications come and go, while protocols and files tend to stay, and
8448 thus one want to make it easy to change application and vendor, while
8449 avoiding conversion costs and locking users to a specific platform or
8450 application.&lt;/p&gt;
8451
8452 &lt;p&gt;This approach make it possible to replace the client applications
8453 independently of the server applications. One can even allow users to
8454 use several different applications as long as they handle the selected
8455 protocol and format. In the normal case, only one client application
8456 is recommended and users only get help if they choose to use this
8457 application, but those that want to deviate from the easy path are not
8458 blocked from doing so.&lt;/p&gt;
8459
8460 &lt;p&gt;It also allow us to replace the server side without forcing the
8461 users to replace their applications, and thus allow us to select the
8462 best server implementation at any moment, when scale and resouce
8463 requirements change.&lt;/p&gt;
8464
8465 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8466 open formats, but I would never recommend standardizing on a single
8467 application that do not use open network protocol or open formats.&lt;/p&gt;
8468 </description>
8469 </item>
8470
8471 <item>
8472 <title>Returning from Skolelinux developer gathering</title>
8473 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8475 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8476 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8477 Edu/Skolelinux development gathering. I got a bit done tuning the
8478 desktop, and looked into the dynamic service location protocol
8479 implementation avahi. It look like it could be useful for us. Almost
8480 30 people participated, and I believe it was a great environment to
8481 get to know the Skolelinux system. Walter Bender, involved in the
8482 development of the Sugar educational platform, presented his stuff and
8483 also helped me improve my OLPC installation. He also showed me that
8484 his Turtle Art application can be used in standalone mode, and we
8485 agreed that I would help getting it packaged for Debian. As a
8486 standalone application it would be great for Debian Edu. We also
8487 tried to get the video conferencing working with two OLPCs, but that
8488 proved to be too hard for us. The application seem to need more work
8489 before it is ready for me. I look forward to getting home and relax
8490 now. :)&lt;/p&gt;
8491 </description>
8492 </item>
8493
8494 <item>
8495 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8496 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8497 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8498 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8499 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8500 optimal. There is RFC 2307 documenting one way to store NIS maps in
8501 LDAP, and a modified version of this normally called RFC 2307bis, with
8502 some modifications to be compatible with Active Directory. The RFC
8503 specification handle the content of a lot of system databases, but do
8504 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8505
8506 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8507 we would like to store information about users, SMB clients/hosts,
8508 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8509 and LTSP configuration in LDAP. These objects have a lot in common,
8510 but with the current LDAP schemas it is not possible to have one
8511 object per entity. For example, one need to have at least three LDAP
8512 objects for a given computer, one with the SMB related stuff, one with
8513 DNS information and another with DHCP information. The schemas
8514 provided for DNS and DHCP are impossible to combine into one LDAP
8515 object. In addition, it is impossible to implement quick queries for
8516 netgroup membership, because of the way NIS triples are implemented.
8517 It just do not scale. I believe it is time for a few RFC
8518 specifications to cleam up this mess.&lt;/p&gt;
8519
8520 &lt;p&gt;I would like to have one LDAP object representing each computer in
8521 the network, and this object can then keep the SMB (ie host key), DHCP
8522 (mac address/name) and DNS (name/IP address) settings in one place.
8523 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8524
8525 &lt;p&gt;I would also like to have a quick way to map from a user or
8526 computer and to the net group this user or computer is a member.&lt;/p&gt;
8527
8528 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8529 in this regard, and the unix side need to catch up. Time to start a
8530 new IETF work group?&lt;/p&gt;
8531 </description>
8532 </item>
8533
8534 <item>
8535 <title>Endelig er Debian Lenny gitt ut</title>
8536 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8537 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8538 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8539 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8540 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8541 Et langt steg videre for Debian-prosjektet, og en rekke nye
8542 programpakker blir nå tilgjengelig for de av oss som bruker den
8543 stabile utgaven av Debian. Neste steg er nå å få
8544 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8545 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8546 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8547 slippes løs på skolene. Takk til alle debian-utviklerne som har
8548 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8549 bootsekvens tilgjengelig i stabil utgave, vha pakken
8550 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8551 </description>
8552 </item>
8553
8554 <item>
8555 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8556 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8558 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8559 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8560 Oslo. Most of Saturday was used for the general assemly for the
8561 member organization, but the rest of the weekend I used to tune the
8562 LTSP installation. LTSP now work out of the box on the 10-network.
8563 Acer Aspire One proved to be a very nice thin client, with both
8564 screen, mouse and keybard in a small box. Was working on getting the
8565 diskless workstation setup configured out of the box, but did not
8566 finish it before the weekend was up.&lt;/p&gt;
8567
8568 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8569 the Brazilian group, so that will have to wait for the next
8570 development gathering. Would love to have the Debian Edu installer
8571 automatically detect and configure a multiseat setup when it find one
8572 of these cards.&lt;/p&gt;
8573 </description>
8574 </item>
8575
8576 <item>
8577 <title>The sorry state of multimedia browser plugins in Debian</title>
8578 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8579 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8580 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8581 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8582 plugins available in Debian Lenny, to see which one we should use by
8583 default in Debian Edu. We need an embedded video playing plugin with
8584 control buttons to pause or stop the video, and capable of streaming
8585 all the multimedia content available on the web. The test results and
8586 notes are available on
8587 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8588 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8589 fill this need. My personal video player favorite, VLC, has a really
8590 bad plugin which fail on a lot of the test pages. A lot of the MIME
8591 types I would expect to work with any free software player (like
8592 video/ogg), just do not work. And simple formats like the
8593 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8594 totem and vlc plugins. I hope the situation will improve soon. No
8595 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8596
8597 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8598 be the only one fitting our needs. :/&lt;/p&gt;
8599 </description>
8600 </item>
8601
8602 </channel>
8603 </rss>