]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
24edf62a7d7b2e68ca2c11aaff82d8532e6fd031
[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>My own self balancing Lego Segway</title>
11 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
13 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
14 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
15 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
16 present. It had been on my wishlist for a while, because I wanted to
17 build a Segway like balancing lego robot. I had already built
18 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
19 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
20 NXT kit as the balance sensor, but it was not working very well. It
21 could balance for a while, but was very sensitive to the light
22 condition in the room and the reflective properties of the surface and
23 would fall over after a short while. I wanted something more robust,
24 and had
25 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
26 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
27 wishlist for some years before it suddenly showed up as a gift from my
28 loved ones. :)&lt;/p&gt;
29
30 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
31 since then. But that changed some days ago, when I was searching for
32 lego segway information and came across a recipe from HiTechnic for
33 building
34 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
35 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
36 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
37 code&lt;/a&gt; was included, so it was just a question of putting it all
38 together. And thanks to the great work of many Debian developers, the
39 compiler needed to build the source for the NXT is already included in
40 Debian, so I was read to go in less than an hour. The resulting robot
41 do not look very impressive in its simplicity:&lt;/p&gt;
42
43 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-robot.jpeg&quot;&gt;&lt;/p&gt;
44
45 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
46 design from HiTechnic, I had to comment out the last task
47 (taskControl). I simply placed /* and */ around it get the program
48 working without that sensor present. Now it balances just fine until
49 the battery status run low:&lt;/p&gt;
50
51 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
52 &lt;source src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-balancing.ogv&quot; type=&quot;video/ogg&quot;&gt;
53 &lt;/video&gt;&lt;/p&gt;
54
55 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
56 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
57
58 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
59 they need to work with LEGO in Debian and all our derivative
60 distributions like Ubuntu, check out
61 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
62 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
63 RCX and NXT controller (no EV3), and would like to make sure the
64 Debian tools needed to program the systems I own work as they
65 should.&lt;/p&gt;
66 </description>
67 </item>
68
69 <item>
70 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
71 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
72 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
73 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
74 <description>&lt;p&gt;In July
75 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html&quot;&gt;I
76 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
77 the ability to receive SMS messages (aka without a cell phone). It is
78 time to share some experiences and provide an updated setup.&lt;/p&gt;
79
80 &lt;p&gt;The Signal app have worked fine for several months now, and I use
81 it regularly to chat with my loved ones. I had a major snag at the
82 end of my summer vacation, when the the app completely forgot my
83 setup, identity and keys. The reason behind this major mess was
84 running out of disk space. To avoid that ever happening again I have
85 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
86 roll back to an earlier version if the files are wiped by mistake. I
87 had to use it once after introducing the git backup. When rolling
88 back to an earlier version, one need to use the &#39;reset session&#39; option
89 in Signal to get going, and notify the people you talk with about the
90 problem. I assume there is some sequence number tracking in the
91 protocol to detect rollback attacks. The git repository is rather big
92 (674 MiB so far), but I have not tried to figure out if some of the
93 content can be added to a .gitignore file due to lack of spare
94 time.&lt;/p&gt;
95
96 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
97 make it impossible to send messages using Signal. I could still
98 receive them, but had to patch the code with a new timestamp to send.
99 I believe the timeout is added by the developers to force people to
100 upgrade to the latest version of the app, even when there is no
101 protocol changes, to reduce the version skew among the user base and
102 thus try to keep the number of support requests down.&lt;/p&gt;
103
104 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
105 making the old patch fail to apply cleanly. Below is an updated
106 patch, including the shell wrapper I use to start Signal. The
107 original version required a new user to locate the JavaScript console
108 and call a function from there. I got help from a friend with more
109 JavaScript knowledge than me to modify the code to provide a GUI
110 button instead. This mean that to get started you just need to run
111 the wrapper and click the &#39;Register without mobile phone&#39; to get going
112 now. I&#39;ve also modified the timeout code to always set it to 90 days
113 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
114
115 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
116
117 &lt;ol&gt;
118
119 &lt;li&gt;First, install required packages to get the source code and the
120 browser you need. Signal only work with Chrome/Chromium, as far as I
121 know, so you need to install it.
122
123 &lt;pre&gt;
124 apt install git tor chromium
125 git clone https://github.com/WhisperSystems/Signal-Desktop.git
126 &lt;/pre&gt;&lt;/li&gt;
127
128 &lt;li&gt;Modify the source code using command listed in the the patch
129 block below.&lt;/li&gt;
130
131 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
132 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
133
134 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
135 number you can receive calls to the next minute, receive the
136 verification code and enter it into the form field and press
137 &#39;Register&#39;. Note, the phone number you use will be user Signal
138 username, ie the way others can find you on Signal.&lt;/li&gt;
139
140 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
141 not show up in the contact list until you restart Signal, and there is
142 no way to assign names to Contacts. There is also no way to create or
143 update chat groups. I suspect this is because the web app do not have
144 a associated contact database.&lt;/li&gt;
145
146 &lt;/ol&gt;
147
148 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
149 main author moxie0 reject federation and accept dependencies to major
150 corporations like Google (part of the code is fetched from Google) and
151 Amazon (the central coordination point is owned by Amazon). See for
152 example
153 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
154 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
155 view on these issues. But the network effect is strong in this case,
156 and several of the people I want to communicate with already use
157 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
158 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
159 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
160 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
161 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
162 working on Debian Stable.&lt;/p&gt;
163
164 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
165 working. It switch to the production servers, disable to timeout,
166 make registration easier and add the shell wrapper:&lt;/p&gt;
167
168 &lt;pre&gt;
169 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
170 diff --git a/js/background.js b/js/background.js
171 index 24b4c1d..579345f 100644
172 --- a/js/background.js
173 +++ b/js/background.js
174 @@ -33,9 +33,9 @@
175 });
176 });
177
178 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
179 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
180 var SERVER_PORTS = [80, 4433, 8443];
181 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
182 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
183 var messageReceiver;
184 window.getSocketStatus = function() {
185 if (messageReceiver) {
186 diff --git a/js/expire.js b/js/expire.js
187 index 639aeae..beb91c3 100644
188 --- a/js/expire.js
189 +++ b/js/expire.js
190 @@ -1,6 +1,6 @@
191 ;(function() {
192 &#39;use strict&#39;;
193 - var BUILD_EXPIRATION = 0;
194 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
195
196 window.extension = window.extension || {};
197
198 diff --git a/js/views/install_view.js b/js/views/install_view.js
199 index 7816f4f..1d6233b 100644
200 --- a/js/views/install_view.js
201 +++ b/js/views/install_view.js
202 @@ -38,7 +38,8 @@
203 return {
204 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
205 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
206 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
207 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
208 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
209 };
210 },
211 clearQR: function() {
212 diff --git a/options.html b/options.html
213 index dc0f28e..8d709f6 100644
214 --- a/options.html
215 +++ b/options.html
216 @@ -14,7 +14,10 @@
217 &amp;lt;div class=&#39;nav&#39;&gt;
218 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
219 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
220 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
221 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
222 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
223 +
224 + &amp;lt;/div&gt;
225 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
226 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
227 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
228 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
229 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
230 @@ -0,0 +1,12 @@
231 +#!/bin/sh
232 +set -e
233 +cd $(dirname $0)
234 +mkdir -p userdata
235 +userdata=&quot;`pwd`/userdata&quot;
236 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
237 + (cd $userdata &amp;&amp; git init)
238 +fi
239 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
240 +exec chromium \
241 + --proxy-server=&quot;socks://localhost:9050&quot; \
242 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
243 EOF
244 chmod a+rx run-signal-app
245 &lt;/pre&gt;
246
247 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
248 activities, please send Bitcoin donations to my address
249 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
250 </description>
251 </item>
252
253 <item>
254 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
255 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
256 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
257 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
258 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
259 system&lt;/a&gt; provide a practical and easy way to figure out which
260 packages support the hardware in a given machine. The command line
261 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
262 convenient way to list and install packages relevant for the current
263 hardware during system installation, both user space packages and
264 firmware packages. The GUI background daemon on the other hand provide
265 a pop-up proposing to install packages when a new dongle is inserted
266 while using the computer. For example, if you plug in a smart card
267 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
268 that package isn&#39;t already installed, and if you plug in a USB video
269 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
270 cheese is currently missing. This already work just fine.&lt;/p&gt;
271
272 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
273 package names. When I started no such database existed in Debian, so
274 I made my own data set and included it with the isenkram package and
275 made isenkram fetch the latest version of this database from git using
276 http. This way the isenkram users would get updated package proposals
277 as soon as I learned more about hardware related packages.&lt;/p&gt;
278
279 &lt;p&gt;The hardware is identified using modalias strings. The modalias
280 design is from the Linux kernel where most hardware descriptors are
281 made available as a strings that can be matched using filename style
282 globbing. It handle USB, PCI, DMI and a lot of other hardware related
283 identifiers.&lt;/p&gt;
284
285 &lt;p&gt;The downside to the Isenkram specific database is that there is no
286 information about relevant distribution / Debian version, making
287 isenkram propose obsolete packages too. But along came AppStream, a
288 cross distribution mechanism to store and collect metadata about
289 software packages. When I heard about the proposal, I contacted the
290 people involved and suggested to add a hardware matching rule using
291 modalias strings in the specification, to be able to use AppStream for
292 mapping hardware to packages. This idea was accepted and AppStream is
293 now a great way for a package to announce the hardware it support in a
294 distribution neutral way. I wrote
295 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html&quot;&gt;a
296 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
297 December. If you have a hardware related package in Debian, please
298 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
299
300 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
301 RCX or NXT unit, announce this support using AppStream. The effect is
302 that when you insert such LEGO robot controller into your Debian
303 machine, Isenkram will propose to install the packages needed to get
304 it working. The intention is that this should allow the local user to
305 start programming his robot controller right away without having to
306 guess what packages to use or which permissions to fix.&lt;/p&gt;
307
308 &lt;p&gt;But when I sat down with my son the other day to program our NXT
309 unit using his Debian Stretch computer, I discovered something
310 annoying. The local console user (ie my son) did not get access to
311 the USB device for programming the unit. This used to work, but no
312 longer in Jessie and Stretch. After some investigation and asking
313 around on #debian-devel, I discovered that this was because udev had
314 changed the mechanism used to grant access to local devices. The
315 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
316 no longer applied, because LDAP users no longer was added to the
317 plugdev group during login. Michael Biebl told me that this method
318 was obsolete and the new method used ACLs instead. This was good
319 news, as the plugdev mechanism is a mess when using a remote user
320 directory like LDAP. Using ACLs would make sure a user lost device
321 access when she logged out, even if the user left behind a background
322 process which would retain the plugdev membership with the ConsoleKit
323 setup. Armed with this knowledge I moved on to fix the access problem
324 for the LEGO Mindstorms related packages.&lt;/p&gt;
325
326 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
327 applied directly for a device, or is applied in
328 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
329 LEGO Mindstorms udev rules did not have a class, I decided to add the
330 tag directly in the udev rules files included in the packages. Here
331 is one example. For the nqc C compiler for the RCX, the
332 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
333
334 &lt;p&gt;&lt;pre&gt;
335 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
336 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
337 &lt;/pre&gt;&lt;/p&gt;
338
339 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
340 packages using plugdev in their /lib/udev/rules.d/ files should be
341 changed to use this tag (either directly or indirectly via
342 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
343 to detect this?&lt;/p&gt;
344
345 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
346 It is unclear to me if the uaccess tag is an internal implementation
347 detail like the udev-acl tag used by
348 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
349 indirect method is the preferred way. Michael
350 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
351 documentation from the systemd project&lt;/a&gt; and I hope it will make
352 this clearer. For now I use the generic classes when they exist and
353 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
354 directly if no such class exist.&lt;/p&gt;
355
356 &lt;p&gt;To learn more about the isenkram system, please check out
357 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
358 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
359
360 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
361 please join us on our IRC channel
362 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
363 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
364 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
365 list is not yet created, but we are working on it. :)&lt;/p&gt;
366
367 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
368 activities, please send Bitcoin donations to my address
369 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
370 </description>
371 </item>
372
373 <item>
374 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
375 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
376 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
377 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
378 <description>&lt;p&gt;In April we
379 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html&quot;&gt;started
380 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
381 how to set up and administrate a Debian system. Today I am happy to
382 report that the first draft is now publicly available. You can find
383 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
384 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
385 eight chapters have a first draft translation, and we are working on
386 proofreading the content. If you want to help out, please start
387 contributing using
388 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
389 hosted weblate project page&lt;/a&gt;, and get in touch using
390 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
391 translators mailing list&lt;/a&gt;. Please also check out
392 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
393 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
394 and update weblate if you find errors.&lt;/p&gt;
395
396 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
397 electronic form.&lt;/p&gt;
398 </description>
399 </item>
400
401 <item>
402 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
403 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
404 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
405 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
406 <description>&lt;p&gt;This summer, I read a great article
407 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
408 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
409 how to profile multi-threaded programs. It presented a system for
410 profiling software by running experiences in the running program,
411 testing how run time performance is affected by &quot;speeding up&quot; parts of
412 the code to various degrees compared to a normal run. It does this by
413 slowing down parallel threads while the &quot;faster up&quot; code is running
414 and measure how this affect processing time. The processing time is
415 measured using probes inserted into the code, either using progress
416 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
417 can also measure unmodified code by measuring complete the program
418 runtime and running the program several times instead.&lt;/p&gt;
419
420 &lt;p&gt;The project and presentation was so inspiring that I would like to
421 get the system into Debian. I
422 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
423 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
424 system ready for Debian by sending patches. The build process need to
425 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
426 to include the JavaScript web page used to visualize the collected
427 profiling information included in the source package.
428 But I expect that should work out fairly soon.&lt;/p&gt;
429
430 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
431 on a binary with debug symbols available, start the program like this:
432
433 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
434 coz run --- program-to-run
435 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
436
437 &lt;p&gt;This will create a text file profile.coz with the instrumentation
438 information. To show what part of the code affect the performance
439 most, use a web browser and either point it to
440 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
441 or use the copy from git (in the gh-pages branch). Check out this web
442 site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like. To make the
443 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
444 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
445 code, rebuild and run the profiler. This allow coz to do more
446 targeted experiments.&lt;/p&gt;
447
448 &lt;p&gt;A video published by ACM
449 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
450 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
451 from the 25th Symposium on Operating Systems Principles available
452 titled
453 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
454 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
455
456 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
457 for Coz is available from github. It will only build with clang
458 because it uses a
459 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
460 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
461 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
462 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
463
464 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
465 of software in Debian. I would very much like some help with the
466 packaging effort, as I lack the in depth knowledge on how to package
467 C++ libraries.&lt;/p&gt;
468 </description>
469 </item>
470
471 <item>
472 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
473 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
475 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
476 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
477 to be a slight challenge. Here is the recipe if I ever need to do it
478 again. It all started by me wanting to try the recipe to set up
479 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
480 hardened Android installation&lt;/a&gt; from the Tor project blog on a
481 device I had access to. It is a old mobile phone with a broken
482 microphone The initial idea had been to just
483 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
484 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
485 until a few days ago.&lt;/p&gt;
486
487 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
488 loader (press volume down and power at the same time), (2) select
489 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
490 machine, (4) request the device identifier token by running &#39;fastboot
491 oem get_identifier_token&#39;, (5) request the device unlocking key using
492 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
493 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
494
495 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
496 or newer, and the device I was working on had 2.00.0027. This
497 apparently can be easily fixed by downloading a Windows program and
498 running it on your Windows machine, if you accept the terms Microsoft
499 require you to accept to use Windows - which I do not. So I had to
500 come up with a different approach. I got a lot of help from AndyCap
501 on #nuug, and would not have been able to get this working without
502 him.&lt;/p&gt;
503
504 &lt;p&gt;First I needed to extract the hboot firmware from
505 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
506 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
507 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
508 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
509 recognise the file format, but unruu worked and extracted rom.zip,
510 containing the new hboot firmware and a text file describing which
511 devices it would work for.&lt;/p&gt;
512
513 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
514 followed some instructions
515 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
516 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
517 machine with Debian testing:&lt;/p&gt;
518
519 &lt;p&gt;&lt;pre&gt;
520 adb reboot-bootloader
521 fastboot oem rebootRUU
522 fastboot flash zip rom.zip
523 fastboot flash zip rom.zip
524 fastboot reboot
525 &lt;/pre&gt;&lt;/p&gt;
526
527 &lt;p&gt;The flash command apparently need to be done twice to take effect,
528 as the first is just preparations and the second one do the flashing.
529 The adb command is just to get to the boot loader menu, so turning the
530 device on while holding volume down and the power button should work
531 too.&lt;/p&gt;
532
533 &lt;p&gt;With the new hboot version in place I could start following the
534 instructions on the HTC developer web site. I got the device token
535 like this:&lt;/p&gt;
536
537 &lt;p&gt;&lt;pre&gt;
538 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
539 &lt;/pre&gt;
540
541 &lt;p&gt;And once I got the unlock code via email, I could use it like
542 this:&lt;/p&gt;
543
544 &lt;p&gt;&lt;pre&gt;
545 fastboot flash unlocktoken Unlock_code.bin
546 &lt;/pre&gt;&lt;/p&gt;
547
548 &lt;p&gt;And with that final step in place, the phone was unlocked and I
549 could start stuffing the software of my own choosing into the device.
550 So far I only inserted a replacement recovery image to wipe the phone
551 before I start. We will see what happen next. Perhaps I should
552 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
553 </description>
554 </item>
555
556 <item>
557 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
558 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</link>
559 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</guid>
560 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
561 <description>&lt;p&gt;For a while now, I have wanted to test
562 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
563 said to provide end to end encrypted communication and several of my
564 friends and family are already using it. As I by choice do not own a
565 mobile phone, this proved to be harder than expected. And I wanted to
566 have the source of the client and know that it was the code used on my
567 machine. But yesterday I managed to get it working. I used the
568 Github source, compared it to the source in
569 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
570 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
571 patches to use the production Signal servers, started the app and
572 asked for the hidden &quot;register without a smart phone&quot; form. Here is
573 the recipe how I did it.&lt;/p&gt;
574
575 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
576
577 &lt;pre&gt;
578 git clone https://github.com/WhisperSystems/Signal-Desktop.git
579 &lt;/pre&gt;
580
581 &lt;p&gt;Next, I patched the source to use the production servers, to be
582 able to talk to other Signal users:&lt;/p&gt;
583
584 &lt;pre&gt;
585 cat &amp;lt;&amp;lt;EOF | patch -p0
586 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
587 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
588 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
589 @@ -47,8 +47,8 @@
590 });
591 });
592
593 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
594 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
595 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
596 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
597 var messageReceiver;
598 window.getSocketStatus = function() {
599 if (messageReceiver) {
600 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
601 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
602 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
603 @@ -1,6 +1,6 @@
604 ;(function() {
605 &#39;use strict&#39;;
606 - var BUILD_EXPIRATION = 0;
607 + var BUILD_EXPIRATION = 1474492690000;
608
609 window.extension = window.extension || {};
610
611 EOF
612 &lt;/pre&gt;
613
614 &lt;p&gt;The first part is changing the servers, and the second is updating
615 an expiration timestamp. This timestamp need to be updated regularly.
616 It is set 90 days in the future by the build process (Gruntfile.js).
617 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
618
619 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
620 script to launch Signal in Chromium.&lt;/p&gt;
621
622 &lt;pre&gt;
623 #!/bin/sh
624 cd $(dirname $0)
625 mkdir -p userdata
626 exec chromium \
627 --proxy-server=&quot;socks://localhost:9050&quot; \
628 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
629 &lt;/pre&gt;
630
631 &lt;p&gt; The script start the app and configure Chromium to use the Tor
632 SOCKS5 proxy to make sure those controlling the Signal servers (today
633 Amazon and Whisper Systems) as well as those listening on the lines
634 will have a harder time location my laptop based on the Signal
635 connections if they use source IP address.&lt;/p&gt;
636
637 &lt;p&gt;When the script starts, one need to follow the instructions under
638 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
639 repository. I right clicked on the Signal window to get up the
640 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
641 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
642 registration form. Then I entered by land line phone number and
643 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
644 repeated the verification code three times. After entering the number
645 into the verification code field in the form, I could start using
646 Signal from my laptop.
647
648 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
649 whom and thus who know who to those controlling the central server,
650 but such leakage is hard to avoid with a centrally controlled server
651 setup. It is something to keep in mind when using Signal - the
652 content of your chats are harder to intercept, but the meta data
653 exposing your contact network is available to people you do not know.
654 So better than many options, but not great. And sadly the usage is
655 connected to my land line, thus allowing those controlling the server
656 to associate it to my home and person. I would prefer it if only
657 those I knew could tell who I was on Signal. There are options
658 avoiding such information leakage, but most of my friends are not
659 using them, so I am stuck with Signal for now.&lt;/p&gt;
660 </description>
661 </item>
662
663 <item>
664 <title>The new &quot;best&quot; multimedia player in Debian?</title>
665 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
666 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
667 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
668 <description>&lt;p&gt;When I set out a few weeks ago to figure out
669 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
670 multimedia player in Debian claimed to support most file formats /
671 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
672 the various players claimed support for. The range was from 55 to 130
673 MIME types. I suspect most media formats are supported by all
674 players, but this is not really reflected in the MimeTypes values in
675 their desktop files. There are probably also some bogus MIME types
676 listed, but it is hard to identify which one this is.&lt;/p&gt;
677
678 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
679 the players suggesting to add more MIME types to their desktop files,
680 and decided to spend some time myself improving the situation for my
681 favorite media player VLC. The fixes for VLC entered Debian unstable
682 yesterday. The complete list of MIME types can be seen on the
683 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
684 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
685
686 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
687 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
688 kmplayer. I am sure some of the other players desktop files support
689 several of the formats currently listed as working only with vlc,
690 toten and parole.&lt;/p&gt;
691
692 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
693 supported by all the tested multimedia players in Debian in their
694 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
695 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
696 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
697 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
698 it sad that video/ogg and video/webm is not supported by all the media
699 players in Debian. As far as I can tell, all of them can handle both
700 formats.&lt;/p&gt;
701 </description>
702 </item>
703
704 <item>
705 <title>A program should be able to open its own files on Linux</title>
706 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
707 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
708 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
709 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
710 decided to test its presentation tool when making the slides for a
711 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
712 wrote the first draft of the slides, saved the result and went to bed
713 the day before I would give the talk. The next day I took a plane to
714 the location where the meeting should take place, and on the plane I
715 started up koffice again to polish the talk a bit, only to discover
716 that kpresenter refused to load its own data file. I cursed a bit and
717 started making the slides again from memory, to have something to
718 present when I arrived. I tested that the saved files could be
719 loaded, and the day seemed to be rescued. I continued to polish the
720 slides until I suddenly discovered that the saved file could no longer
721 be loaded into kpresenter. In the end I had to rewrite the slides
722 three times, condensing the content until the talk became shorter and
723 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
724 kpresenter wrote inline images in a way itself could not understand.
725 Eventually that bug was fixed and kpresenter ended up being a great
726 program to make slides. The point I&#39;m trying to make is that we
727 expect a program to be able to load its own data files, and it is
728 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
729
730 &lt;p&gt;Did you ever experience a program failing to load its own data
731 files from the desktop file browser? It is not a uncommon problem. A
732 while back I discovered that the screencast recorder
733 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
734 browser would refuse to open. No video player claimed to understand
735 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
736 returning the application/ogg MIME type, which no video player I had
737 installed listed as a MIME type they would understand. I asked for
738 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
739 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
740 several video players to add video/ogg to their desktop files, to give
741 the file browser an idea what to do about Ogg Theora files. After a
742 while, the desktop file browsers in Debian started to handle the
743 output from gtk-recordmydesktop properly.&lt;/p&gt;
744
745 &lt;p&gt;But history repeats itself. A few days ago I tested the music
746 system Rosegarden again, and I discovered that the KDE and xfce file
747 browsers did not know what to do with the Rosegarden project files
748 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
749 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
750 included in the next upload. To increase the chance of me remembering
751 how to fix the problem next time some program fail to load its files
752 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
753
754 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
755 There are two sources for the MIME type of a given file. The output from
756 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
757 shared MIME type registry (under /usr/share/mime/). The file MIME
758 type is mapped to programs supporting the MIME type, and this
759 information is collected from
760 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
761 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
762 one desktop file claiming support for the MIME type of the file, it is
763 activated when asking to open a given file. If there are more, one
764 can normally select which one to use by right-clicking on the file and
765 selecting the wanted one using &#39;Open with&#39; or similar. In general
766 this work well. But it depend on each program picking a good MIME
767 type (preferably
768 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
769 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
770 registry recognizing the file and the desktop file to list the MIME
771 type in its list of supported MIME types.&lt;/p&gt;
772
773 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
774 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
775 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
776
777 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
778 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
779 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
780 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
781 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
782 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
783 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
784 &amp;lt;/mime-type&amp;gt;
785 &amp;lt;/mime-info&amp;gt;
786 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
787
788 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
789 (it is a gzipped XML file). Note, it is much better to use an
790 official MIME type registered with IANA than it is to make up ones own
791 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
792
793 &lt;p&gt;The desktop file of the rosegarden program failed to list
794 audio/x-rosegarden in its list of supported MIME types, causing the
795 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
796
797 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
798 % grep Mime /usr/share/applications/rosegarden.desktop
799 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
800 X-KDE-NativeMimeType=audio/x-rosegarden-composition
801 %
802 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
803
804 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
805 MimeType= line.&lt;/p&gt;
806
807 &lt;p&gt;If you run into a file which fail to open the correct program when
808 selected from the file browser, please check out the output from
809 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
810 MIME type is registered somewhere under /usr/share/mime/ and check
811 that some desktop file under /usr/share/applications/ is claiming
812 support for this MIME type. If not, please report a bug to have it
813 fixed. :)&lt;/p&gt;
814 </description>
815 </item>
816
817 <item>
818 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
819 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
820 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
821 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
822 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
823 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
824 related packages. The idea is to have a database of mappings between
825 hardware and packages, and pop up a dialog suggesting for the user to
826 install the packages to use a given hardware dongle. Some use cases
827 are when you insert a Yubikey, it proposes to install the software
828 needed to control it; when you insert a braille reader list it
829 proposes to install the packages needed to send text to the reader;
830 and when you insert a ColorHug screen calibrator it suggests to
831 install the driver for it. The system work well, and even have a few
832 command line tools to install firmware packages and packages for the
833 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
834
835 &lt;p&gt;The system was initially written using aptdaemon, because I found
836 good documentation and example code on how to use it. But aptdaemon
837 is going away and is generally being replaced by
838 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
839 so Isenkram needed a rewrite. And today, thanks to the great patch
840 from my college Sunil Mohan Adapa in the FreedomBox project, the
841 rewrite finally took place. I&#39;ve just uploaded a new version of
842 Isenkram into Debian Unstable with the patch included, and the default
843 for the background daemon is now to use PackageKit. To check it out,
844 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
845 and see if it is recognised.&lt;/p&gt;
846
847 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
848 the machine it is running on, you can check out the isenkram-lookup
849 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
850
851 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
852 % isenkram-lookup
853 bluez
854 cheese
855 fprintd
856 fprintd-demo
857 gkrellm-thinkbat
858 hdapsd
859 libpam-fprintd
860 pidgin-blinklight
861 thinkfan
862 tleds
863 tp-smapi-dkms
864 tp-smapi-source
865 tpb
866 %p
867 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
868
869 &lt;p&gt;The hardware mappings come from several places. The preferred way
870 is for packages to announce their hardware support using
871 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
872 cross distribution appstream system&lt;/a&gt;.
873 See
874 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
875 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
876 </description>
877 </item>
878
879 <item>
880 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
881 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
882 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
883 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
884 <description>&lt;p&gt;Yesterday I updated the
885 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
886 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
887 enterprising users. There were some nice user and visible changes.
888 First of all, both desktop menu entries now work. A design flaw in
889 one of the script made the history graph fail to show up (its PNG was
890 dumped in ~/.xsession-errors) if no controlling TTY was available.
891 The script worked when called from the command line, but not when
892 called from the desktop menu. I changed this to look for a DISPLAY
893 variable or a TTY before deciding where to draw the graph, and now the
894 graph window pop up as expected.&lt;/p&gt;
895
896 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
897 graphs (the one showing the last few hours). New is also the user of
898 colours showing charging in blue and discharge in red. The percentages
899 of this graph is relative to last full charge, not battery design
900 capacity.&lt;/p&gt;
901
902 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-rate.png&quot;/&gt;&lt;/p&gt;
903
904 &lt;p&gt;The other graph show the entire history of the collected battery
905 statistics, comparing it to the design capacity of the battery to
906 visualise how the battery life time get shorter over time. The red
907 line in this graph is what the previous graph considers 100 percent:
908
909 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-history.png&quot;/&gt;&lt;/p&gt;
910
911 &lt;p&gt;In this graph you can see that I only charge the battery to 80
912 percent of last full capacity, and how the capacity of the battery is
913 shrinking. :(&lt;/p&gt;
914
915 &lt;p&gt;The last new feature is in the collector, which now will handle
916 more hardware models. On some hardware, Linux power supply
917 information is stored in /sys/class/power_supply/ACAD/, while the
918 collector previously only looked in /sys/class/power_supply/AC/. Now
919 both are checked to figure if there is power connected to the
920 machine.&lt;/p&gt;
921
922 &lt;p&gt;If you are interested in how your laptop battery is doing, please
923 check out the
924 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
925 in Debian unstable, or rebuild it on Jessie to get it working on
926 Debian stable. :) The upstream source is available from &lt;a
927 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
928 Patches are very welcome.&lt;/p&gt;
929
930 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
931 activities, please send Bitcoin donations to my address
932 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
933 </description>
934 </item>
935
936 <item>
937 <title>Debian now with ZFS on Linux included</title>
938 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
939 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
940 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
941 <description>&lt;p&gt;Today, after many years of hard work from many people,
942 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
943 Debian. The package status can be seen on
944 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
945 for zfs-linux&lt;/a&gt;. and
946 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
947 team status page&lt;/a&gt;. If you want to help out, please join us.
948 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
949 source code&lt;/a&gt; is available via git on Alioth. It would also be
950 great if you could help out with
951 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
952 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
953 </description>
954 </item>
955
956 <item>
957 <title>What is the best multimedia player in Debian?</title>
958 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
959 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
960 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
961 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
962 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
963
964 &lt;p&gt;A few years ago, I had a look at the media support for Browser
965 plugins in Debian, to get an idea which plugins to include in Debian
966 Edu. I created a script to extract the set of supported MIME types
967 for each plugin, and used this to find out which multimedia browser
968 plugin supported most file formats / media types.
969 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
970 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
971 not been updated for a while. But browser plugins are less relevant
972 these days, so I thought it was time to look at standalone
973 players.&lt;/p&gt;
974
975 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
976 player when I wanted to play videos from the Norwegian National
977 Broadcasting Company, and decided to investigate why. The cause is a
978 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
979 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
980 of MIME types announced in the desktop file and the browser plugin,
981 only to discover that there is quite a large difference between the
982 two for VLC. This discovery made me dig up the script I used to
983 compare browser plugins, and adjust it to compare desktop files
984 instead, to try to figure out which multimedia player in Debian
985 support most file formats.&lt;/p&gt;
986
987 &lt;p&gt;The result can be seen on the Debian Wiki, as
988 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
989 table listing all MIME types supported by one of the packages included
990 in the table&lt;/a&gt;, with the package supporting most MIME types being
991 listed first in the table.&lt;/p&gt;
992
993 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
994 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
995 kmplayer. Time for the other players to update their announced MIME
996 support?&lt;/p&gt;
997 </description>
998 </item>
999
1000 <item>
1001 <title>The Pyra - handheld computer with Debian preinstalled</title>
1002 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
1003 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
1004 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
1005 <description>A friend of mine made me aware of
1006 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
1007 handheld computer which will be delivered with Debian preinstalled. I
1008 would love to get one of those for my birthday. :)&lt;/p&gt;
1009
1010 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1011 plugs and many others connectors, and include a full keyboard and a 5&quot;
1012 LCD touch screen. The 6000mAh battery is claimed to provide a whole
1013 day of battery life time, but I have not seen any independent tests
1014 confirming this. The vendor is still collecting preorders, and the
1015 last I heard last night was that 22 more orders were needed before
1016 production started.&lt;/p&gt;
1017
1018 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
1019 Debian. Please let me know if you know of any others. Is it the
1020 first computer being sold with Debian preinstalled?&lt;/p&gt;
1021 </description>
1022 </item>
1023
1024 <item>
1025 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
1026 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
1027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
1028 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
1029 <description>&lt;p&gt;During this weekends
1030 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
1031 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
1032 to make sure there are good books about Debian available in Norwegian
1033 Bokmål, and got in touch with the people behind the
1034 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
1035 project&lt;/a&gt; to get started. If you want to help out, please start
1036 contributing using
1037 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1038 hosted weblate project page&lt;/a&gt;, and get in touch using
1039 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1040 translators mailing list&lt;/a&gt;. Please also check out
1041 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1042 contributors&lt;/a&gt;.&lt;/p&gt;
1043
1044 &lt;p&gt;The book is already available on paper in English, French and
1045 Japanese, and our goal is to get it available on paper in Norwegian
1046 Bokmål too. In addition to the paper edition, there are also EPUB and
1047 Mobi versions available. And there are incomplete translations
1048 available for many more languages.&lt;/p&gt;
1049 </description>
1050 </item>
1051
1052 <item>
1053 <title>One in two hundred Debian users using ZFS on Linux?</title>
1054 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
1055 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
1056 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
1057 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
1058 packages in Debian, and was quite surprised with what I found. I use
1059 ZFS myself at home, but did not really expect many others to do so.
1060 But I might be wrong.&lt;/p&gt;
1061
1062 &lt;p&gt;According to
1063 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
1064 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
1065 0.53% of the population, with the package installed. As far as I know
1066 the only use of the spl-linux package is as a support library for ZFS
1067 on Linux, so I use it here as proxy for measuring the number of ZFS
1068 installation on Linux in Debian. In the kFreeBSD variant of Debian
1069 the ZFS feature is already available, and there
1070 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
1071 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
1072 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
1073
1074 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
1075 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
1076 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
1077 cleared, the package is still not in Debian. The package is again in
1078 the NEW queue. Several uploads have been rejected so far because the
1079 debian/copyright file was incomplete or wrong, but there is no reason
1080 to give up. The current status can be seen on
1081 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1082 team status page&lt;/a&gt;, and
1083 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
1084 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
1085
1086 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
1087 my home server can function in the future using only official Debian
1088 packages, and the current blocker is to get the debian/copyright file
1089 accepted by the FTP masters in Debian, I decided a while back to try
1090 to help out the team. This was the background for my blog post about
1091 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
1092 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
1093 used the techniques I explored there to try to find any errors in the
1094 copyright file. It is not very easy to check every one of the around
1095 2000 files in the source package, but I hope we this time got it
1096 right. If you want to help out, check out the git source and try to
1097 find missing entries in the debian/copyright file.&lt;/p&gt;
1098 </description>
1099 </item>
1100
1101 <item>
1102 <title>Full battery stats collector is now available in Debian</title>
1103 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
1104 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
1105 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
1106 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
1107 extended collector that will collect the complete battery history for
1108 later processing and graphing. The original collector store the
1109 battery level as percentage of last full level, while the new
1110 collector also record battery vendor, model, serial number, design
1111 full level, last full level and current battery level. This make it
1112 possible to predict the lifetime of the battery as well as visualise
1113 the energy flow when the battery is charging or discharging.&lt;/p&gt;
1114
1115 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
1116 in the version 0.5.1 package in unstable. Get the new battery level graph
1117 and lifetime prediction by running:
1118
1119 &lt;p&gt;&lt;pre&gt;
1120 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1121 &lt;/pre&gt;&lt;/p&gt;
1122
1123 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
1124
1125 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
1126 entry yet):&lt;/p&gt;
1127
1128 &lt;p&gt;&lt;pre&gt;
1129 /usr/share/battery-stats/battery-stats-graph-flow
1130 &lt;/pre&gt;&lt;/p&gt;
1131
1132 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
1133 when there are few data points. The graphs look a bit better with a
1134 few years of data.&lt;/p&gt;
1135
1136 &lt;p&gt;A while back one important feature I use in the battery stats
1137 collector broke in Debian. The scripts in
1138 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
1139 suspect it happened when Jessie started using systemd, but I do not
1140 know. The issue is reported as
1141 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
1142 pm-utils. I managed to work around it by adding an udev rule to call
1143 the collector script every time the power connector is connected and
1144 disconnected. With this fix in place it was finally time to make a
1145 new release of the package, and get it into Debian.&lt;/p&gt;
1146
1147 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1148 check out the
1149 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1150 in Debian unstable, or rebuild it on Jessie to get it working on
1151 Debian stable. :) The upstream source is available from
1152 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1153 As always, patches are very welcome.&lt;/p&gt;
1154 </description>
1155 </item>
1156
1157 <item>
1158 <title>Making battery measurements a little easier in Debian</title>
1159 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
1160 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
1161 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
1162 <description>&lt;p&gt;Back in September, I blogged about
1163 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
1164 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
1165 how it showed the decay and death of this battery (now replaced). I
1166 created a simple deb package to handle the collection and graphing,
1167 but did not want to upload it to Debian as there were already
1168 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
1169 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
1170 a point of uploading a competing package when battery-stats could be
1171 fixed instead. I reported a few bugs about its non-function, and
1172 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
1173
1174 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
1175 hands. The end result is that I am now the new upstream developer of
1176 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
1177 battery-stats in Debian, and the package in Debian unstable is finally
1178 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
1179 information provided by the Linux kernel. If you install the
1180 battery-stats package from unstable now, you will be able to get a
1181 graph of the current battery fill level, to get some idea about the
1182 status of the battery. The source package build and work just fine in
1183 Debian testing and stable (and probably oldstable too, but I have not
1184 tested). The default graph you get for that system look like this:&lt;/p&gt;
1185
1186 &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;
1187
1188 &lt;p&gt;My plans for the future is to merge my old scripts into the
1189 battery-stats package, as my old scripts collected a lot more details
1190 about the battery. The scripts are merged into the upstream
1191 battery-stats git repository already, but I am not convinced they work
1192 yet, as I changed a lot of paths along the way. Will have to test a
1193 bit more before I make a new release.&lt;/p&gt;
1194
1195 &lt;p&gt;I will also consider changing the file format slightly, as I
1196 suspect the way I combine several values into one field might make it
1197 impossible to know the type of the value when using it for processing
1198 and graphing.&lt;/p&gt;
1199
1200 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
1201 battery, check out the battery-stats package in
1202 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
1203 on
1204 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1205 I would love some help to improve the system further.&lt;/p&gt;
1206 </description>
1207 </item>
1208
1209 <item>
1210 <title>Creating, updating and checking debian/copyright semi-automatically</title>
1211 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
1212 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
1213 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
1214 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
1215 details. And one of the details is the content of the
1216 debian/copyright file, which should list all relevant licenses used by
1217 the code in the package in question, preferably in
1218 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
1219 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
1220
1221 &lt;p&gt;For large packages with lots of contributors it is hard to write
1222 and update this file manually, and if you get some detail wrong, the
1223 package is normally rejected by the ftpmasters. So getting it right
1224 the first time around get the package into Debian faster, and save
1225 both you and the ftpmasters some work.. Today, while trying to figure
1226 out what was wrong with
1227 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
1228 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
1229 figuring out the options for doing this job automatically, or at least
1230 semi-automatically.&lt;/p&gt;
1231
1232 &lt;p&gt;Lucikly, there are at least two tools available for generating the
1233 file based on the code in the source package,
1234 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
1235 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
1236 not sure which one of them came first, but both seem to be able to
1237 create a sensible draft file. As far as I can tell, none of them can
1238 be trusted to get the result just right, so the content need to be
1239 polished a bit before the file is OK to upload. I found the debmake
1240 option in
1241 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
1242 blog posts from 2014&lt;/a&gt;.
1243
1244 &lt;p&gt;To generate using debmake, use the -cc option:
1245
1246 &lt;p&gt;&lt;pre&gt;
1247 debmake -cc &gt; debian/copyright
1248 &lt;/pre&gt;&lt;/p&gt;
1249
1250 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
1251 this might not be the best option.&lt;/p&gt;
1252
1253 &lt;p&gt;The cme option is based on a config parsing library, and I found
1254 this approach in
1255 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
1256 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
1257 dpkg-copyright&#39; option:
1258
1259 &lt;p&gt;&lt;pre&gt;
1260 cme update dpkg-copyright
1261 &lt;/pre&gt;&lt;/p&gt;
1262
1263 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
1264 handle UTF-8 names better than debmake.&lt;/p&gt;
1265
1266 &lt;p&gt;When the copyright file is created, I would also like some help to
1267 check if the file is correct. For this I found two good options,
1268 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
1269 to focus on license types and file matching, and is able to detect
1270 ineffective blocks in the copyright file. The latter reports missing
1271 copyright holders and years, but was confused by inconsistent license
1272 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
1273 fix all issues reported by them before uploading. But I do not know
1274 if the tools and the ftpmasters agree on what is important to fix in a
1275 copyright file, so the package might still be rejected.&lt;/p&gt;
1276
1277 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
1278 will read through the source and try to find all copyright statements.
1279 It is not comparing the result to the content of debian/copyright, but
1280 can be useful when verifying the content of the copyright file.&lt;/p&gt;
1281
1282 &lt;p&gt;Are you aware of better tools in Debian to create and update
1283 debian/copyright file. Please let me know, or blog about it on
1284 planet.debian.org.&lt;/p&gt;
1285
1286 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1287 activities, please send Bitcoin donations to my address
1288 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1289
1290 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
1291 on how to use licensecheck and cdbs to create a draft copyright file
1292
1293 &lt;p&gt;&lt;pre&gt;
1294 licensecheck --copyright -r `find * -type f` | \
1295 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
1296 &lt;/pre&gt;&lt;/p&gt;
1297
1298 &lt;p&gt;He mentioned that he normally check the generated file into the
1299 version control system to make it easier to discover license and
1300 copyright changes in the upstream source. I will try to do the same
1301 with my packages in the future.&lt;/p&gt;
1302
1303 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
1304 against using -quiet for new users, so I removed it from the proposed
1305 command line.&lt;/p&gt;
1306 </description>
1307 </item>
1308
1309 <item>
1310 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
1311 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
1312 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
1313 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
1314 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
1315 is taking shape in Debian, and one provided feature is a very
1316 convenient way to tell you which package to install to make a given
1317 firmware file available when the kernel is looking for it. This can
1318 be done using apt-file too, but that is for someone else to blog
1319 about. :)&lt;/p&gt;
1320
1321 &lt;p&gt;Here is a small recipe to find the package with a given firmware
1322 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
1323 picked from the set of firmware announced using appstream in Debian
1324 unstable. In general you would be looking for the firmware requested
1325 by the kernel during kernel module loading. To find the package
1326 providing the example file, do like this:&lt;/p&gt;
1327
1328 &lt;blockquote&gt;&lt;pre&gt;
1329 % apt install appstream
1330 [...]
1331 % apt update
1332 [...]
1333 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
1334 awk &#39;/Package:/ {print $2}&#39;
1335 firmware-qlogic
1336 %
1337 &lt;/pre&gt;&lt;/blockquote&gt;
1338
1339 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
1340 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
1341 a way appstream can use.&lt;/p&gt;
1342
1343 &lt;p&gt;This same approach can be used to find any package supporting a
1344 given MIME type. This is very useful when you get a file you do not
1345 know how to handle. First find the mime type using &lt;tt&gt;file
1346 --mime-type&lt;/tt&gt;, and next look up the package providing support for
1347 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1348 and you can find all packages handling this type like this:&lt;/p&gt;
1349
1350 &lt;blockquote&gt;&lt;pre&gt;
1351 % apt install appstream
1352 [...]
1353 % apt update
1354 [...]
1355 % appstreamcli what-provides mimetype image/svg+xml | \
1356 awk &#39;/Package:/ {print $2}&#39;
1357 bkchem
1358 phototonic
1359 inkscape
1360 shutter
1361 tetzle
1362 geeqie
1363 xia
1364 pinta
1365 gthumb
1366 karbon
1367 comix
1368 mirage
1369 viewnior
1370 postr
1371 ristretto
1372 kolourpaint4
1373 eog
1374 eom
1375 gimagereader
1376 midori
1377 %
1378 &lt;/pre&gt;&lt;/blockquote&gt;
1379
1380 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
1381 packages providing appstream metadata.&lt;/p&gt;
1382 </description>
1383 </item>
1384
1385 <item>
1386 <title>Creepy, visualise geotagged social media information - nice free software</title>
1387 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
1388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
1389 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
1390 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
1391 with the computerised radio beacon known as a mobile phone their
1392 position is tracked by the phone company and often stored for a long
1393 time (like every time a SMS is received or sent). And if their
1394 computerised radio beacon is capable of running programs (often called
1395 mobile apps) downloaded from the Internet, these programs are often
1396 also capable of tracking their location (if the app requested access
1397 during installation). And when these programs send out information to
1398 central collection points, the location is often included, unless
1399 extra care is taken to not send the location. The provided
1400 information is used by several entities, for good and bad (what is
1401 good and bad, depend on your point of view). What is certain, is that
1402 the private sphere and the right to free movement is challenged and
1403 perhaps even eradicated for those announcing their location this way,
1404 when they share their whereabouts with private and public
1405 entities.&lt;/p&gt;
1406
1407 &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;
1408
1409 &lt;p&gt;The phone company logs provide a register of locations to check out
1410 when one want to figure out what the tracked person was doing. It is
1411 unavailable for most of us, but provided to selected government
1412 officials, company staff, those illegally buying information from
1413 unfaithful servants and crackers stealing the information. But the
1414 public information can be collected and analysed, and a free software
1415 tool to do so is called
1416 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
1417 discovered it when I read
1418 &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
1419 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
1420 November 2014, and decided to check if it was available in Debian.
1421 The python program was in Debian, but
1422 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
1423 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
1424 uploaded a new version which did not work quite right, but did not
1425 have time to fix it then. This Christmas I decided to finally try to
1426 get Creepy operational in Debian. Now a fixed version is available in
1427 Debian unstable and testing, and almost all Debian specific patches
1428 are now included
1429 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
1430
1431 &lt;p&gt;The Creepy program visualises geolocation information fetched from
1432 Twitter, Instagram, Flickr and Google+, and allow one to get a
1433 complete picture of every social media message posted recently in a
1434 given area, or track the movement of a given individual across all
1435 these services. Earlier it was possible to use the search API of at
1436 least some of these services without identifying oneself, but these
1437 days it is impossible. This mean that to use Creepy, you need to
1438 configure it to log in as yourself on these services, and provide
1439 information to them about your search interests. This should be taken
1440 into account when using Creepy, as it will also share information
1441 about yourself with the services.&lt;/p&gt;
1442
1443 &lt;p&gt;The picture above show the twitter messages sent from (or at least
1444 geotagged with a position from) the city centre of Oslo, the capital
1445 of Norway. One useful way to use Creepy is to first look at
1446 information tagged with an area of interest, and next look at all the
1447 information provided by one or more individuals who was in the area.
1448 I tested it by checking out which celebrity provide their location in
1449 twitter messages by checkout out who sent twitter messages near a
1450 Norwegian TV station, and next could track their position over time,
1451 making it possible to locate their home and work place, among other
1452 things. A similar technique have been
1453 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
1454 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
1455 tool to discover lying governments, and a useful tool to help people
1456 understand the value of the private information they provide to the
1457 public.&lt;/p&gt;
1458
1459 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
1460 it depend on several python modules currently missing in Jessie (at
1461 least python-instagram, python-flickrapi and
1462 python-requests-toolbelt).&lt;/p&gt;
1463
1464 &lt;p&gt;(I have uploaded
1465 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
1466 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
1467 Creepy program in Debian.)&lt;/p&gt;
1468 </description>
1469 </item>
1470
1471 <item>
1472 <title>Always download Debian packages using Tor - the simple recipe</title>
1473 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
1474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
1475 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
1476 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
1477 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
1478 that those listening on the Internet lines would have good reason to
1479 believe a computer have a given security hole&lt;/a&gt; if it download a
1480 security fix from a Debian mirror. This is a good reason to always
1481 use encrypted connections to the Debian mirror, to make sure those
1482 listening do not know which IP address to attack. In August, Richard
1483 Hartmann observed that encryption was not enough, when it was possible
1484 to interfere download size to security patches or the fact that
1485 download took place shortly after a security fix was released, and
1486 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
1487 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
1488 was not the first to propose this, as the
1489 &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;
1490 package by Tim Retout already existed to make it easy to convince apt
1491 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
1492 aware of that package when I read the blog post from Richard.&lt;/p&gt;
1493
1494 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
1495 sysadmins, and he set up a Tor hidden service on one of the central
1496 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1497 it possible to download packages directly between two tor nodes,
1498 making sure the network traffic always were encrypted.&lt;/p&gt;
1499
1500 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
1501 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
1502 urls with tor+http and tor+https, and using the hidden service instead
1503 of the official Debian mirror site. I recommend installing
1504 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
1505 done in /etc/.&lt;/p&gt;
1506
1507 &lt;blockquote&gt;&lt;pre&gt;
1508 apt install apt-transport-tor
1509 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
1510 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
1511 &lt;/pre&gt;&lt;/blockquote&gt;
1512
1513 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
1514 the sed commands for these too. The sed command is assuming your are
1515 using the ftp.debian.org Debian mirror. Adjust the command (or just
1516 edit the file manually) to match your mirror.&lt;/p&gt;
1517
1518 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
1519 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
1520 system, and do not work with these tor+http URLs. For
1521 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
1522 which need a recent apt version currently only in unstable. So if you
1523 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
1524
1525 &lt;p&gt;Another advantage from this change is that your machine will start
1526 using Tor regularly and at fairly random intervals (every time you
1527 update the package lists or upgrade or install a new package), thus
1528 masking other Tor traffic done from the same machine. Using Tor will
1529 become normal for the machine in question.&lt;/p&gt;
1530
1531 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
1532 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
1533 enabled. It would be great if it was the default on any Debian
1534 system.&lt;/p&gt;
1535 </description>
1536 </item>
1537
1538 <item>
1539 <title>OpenALPR, find car license plates in video streams - nice free software</title>
1540 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
1541 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
1542 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
1543 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
1544 call the car license plate numbers in those days. I would write the
1545 numbers down in my little book and compare notes with the other kids
1546 to see how many region codes we had seen and if we had seen some
1547 exotic or special region codes and numbers. It was a fun game to pass
1548 time, as we kids have plenty of it.&lt;/p&gt;
1549
1550 &lt;p&gt;A few days I came across
1551 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
1552 project&lt;/a&gt;, a free software project to automatically discover and
1553 report license plates in images and video streams, and provide the
1554 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
1555 such system for a while now, because I believe it is a bad idea that the
1556 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
1557 number plate recognition&lt;/a&gt; tool only is available in the hands of
1558 the powerful, and want it to be available also for the powerless to
1559 even the score when it comes to surveillance and sousveillance. I
1560 discovered the developer
1561 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
1562 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
1563 help him get it into shape to get the package uploaded into the Debian
1564 archive.&lt;/p&gt;
1565
1566 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
1567 it into Debian, where it currently
1568 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
1569 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
1570
1571 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
1572 for the common folks, ie those not running a large government
1573 surveillance system? Well, I plan to put it in a computer on my bike
1574 and in my car, tracking the cars nearby and allowing me to be notified
1575 when number plates on my watch list are discovered. Another use case
1576 was suggested by a friend of mine, who wanted to set it up at his home
1577 to open the car port automatically when it discovered the plate on his
1578 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1579 capable of placing his license plate number of a piece of cardboard to
1580 open his car port, men replied that it was always unlocked anyway. I
1581 guess for such use case it make sense. I am sure there are other use
1582 cases too, for those with imagination and a vision.&lt;/p&gt;
1583
1584 &lt;p&gt;If you want to build your own version of the Debian package, check
1585 out the upstream git source and symlink ./distros/debian to ./debian/
1586 before running &quot;debuild&quot; to build the source. Or wait a bit until the
1587 package show up in unstable.&lt;/p&gt;
1588 </description>
1589 </item>
1590
1591 <item>
1592 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
1593 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
1594 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
1595 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
1596 <description>&lt;p&gt;Around three years ago, I created
1597 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
1598 system&lt;/a&gt; to get a more practical solution in Debian for handing
1599 hardware related packages. A GUI system in the isenkram package will
1600 present a pop-up dialog when some hardware dongle supported by
1601 relevant packages in Debian is inserted into the machine. The same
1602 lookup mechanism to detect packages is available as command line
1603 tools in the isenkram-cli package. In addition to mapping hardware,
1604 it will also map kernel firmware files to packages and make it easy to
1605 install needed firmware packages automatically. The key for this
1606 system to work is a good way to map hardware to packages, in other
1607 words, allow packages to announce what hardware they will work
1608 with.&lt;/p&gt;
1609
1610 &lt;p&gt;I started by providing data files in the isenkram source, and
1611 adding code to download the latest version of these data files at run
1612 time, to ensure every user had the most up to date mapping available.
1613 I also added support for storing the mapping in the Packages file in
1614 the apt repositories, but did not push this approach because while I
1615 was trying to figure out how to best store hardware/package mappings,
1616 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1617 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
1618 add the hardware mapping into that data set to be able to use
1619 appstream as a data source, and this was accepted at least for the
1620 Debian version of appstream.&lt;/p&gt;
1621
1622 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
1623 and today I uploaded a new version 0.20 of isenkram adding support for
1624 appstream as a data source for mapping hardware to packages. The only
1625 package so far using appstream to announce its hardware support is my
1626 pymissile package. I got help from Matthias Klumpp with figuring out
1627 how do add the required
1628 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
1629 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
1630 this content:&lt;/p&gt;
1631
1632 &lt;blockquote&gt;&lt;pre&gt;
1633 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1634 &amp;lt;component&amp;gt;
1635 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
1636 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
1637 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
1638 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
1639 &amp;lt;description&amp;gt;
1640 &amp;lt;p&amp;gt;
1641 Pymissile provides a curses interface to control an original
1642 Marks and Spencer / Striker USB Missile Launcher, as well as a
1643 motion control script to allow a webcamera to control the
1644 launcher.
1645 &amp;lt;/p&amp;gt;
1646 &amp;lt;/description&amp;gt;
1647 &amp;lt;provides&amp;gt;
1648 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
1649 &amp;lt;/provides&amp;gt;
1650 &amp;lt;/component&amp;gt;
1651 &lt;/pre&gt;&lt;/blockquote&gt;
1652
1653 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
1654 which is a glob style match rule for hardware specific strings
1655 (modalias strings) provided by the Linux kernel. In this case, it
1656 will map to all USB devices with vendor code 1130 and product code
1657 0202.&lt;/p&gt;
1658
1659 &lt;p&gt;Note, it is important that the license of all the metadata files
1660 are compatible to have permissions to aggregate them into archive wide
1661 appstream files. Matthias suggested to use MIT or BSD licenses for
1662 these files. A challenge is figuring out a good id for the data, as
1663 it is supposed to be globally unique and shared across distributions
1664 (in other words, best to coordinate with upstream what to use). But
1665 it can be changed later or, so we went with the package name as
1666 upstream for this project is dormant.&lt;/p&gt;
1667
1668 &lt;p&gt;To get the metadata file installed in the correct location for the
1669 mirror update scripts to pick it up and include its content the
1670 appstream data source, the file must be installed in the binary
1671 package under /usr/share/appdata/. I did this by adding the following
1672 line to debian/pymissile.install:&lt;/p&gt;
1673
1674 &lt;blockquote&gt;&lt;pre&gt;
1675 debian/pymissile.metainfo.xml usr/share/appdata
1676 &lt;/pre&gt;&lt;/blockquote&gt;
1677
1678 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
1679 all packages useful on the current computer automatically, and the GUI
1680 pop-up handler will propose to install the package not already
1681 installed if a hardware dongle is inserted into the machine in
1682 question.&lt;/p&gt;
1683
1684 &lt;p&gt;Details of the modalias field in appstream is available from the
1685 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
1686
1687 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
1688 try running this command on the command line:&lt;/p&gt;
1689
1690 &lt;blockquote&gt;&lt;pre&gt;
1691 cat $(find /sys/devices/|grep modalias)
1692 &lt;/pre&gt;&lt;/blockquote&gt;
1693
1694 &lt;p&gt;To learn more about the isenkram system, please check out
1695 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
1696 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
1697 </description>
1698 </item>
1699
1700 <item>
1701 <title>The GNU General Public License is not magic pixie dust</title>
1702 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
1703 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
1704 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
1705 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
1706 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
1707 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
1708 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
1709 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
1710
1711 &lt;blockquote&gt;
1712
1713 &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;
1714
1715 &lt;blockquote&gt;
1716 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
1717
1718 The first step is to choose a
1719 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
1720 code.&lt;br/&gt;
1721
1722 The next step is, when someone fails to follow that copyleft license,
1723 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
1724
1725 and its a simple fact of our modern society that such type of
1726 work&lt;br/&gt;
1727
1728 is incredibly expensive to do and incredibly difficult to do.
1729 &lt;/blockquote&gt;
1730
1731 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
1732 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
1733 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
1734 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
1735
1736 &lt;p&gt;As the Debian Website
1737 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
1738 &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;
1739 imply, public domain and permissively licensed software can lead to
1740 the production of more proprietary software as people discover useful
1741 software, extend it and or incorporate it into their hardware or
1742 software products. Copyleft licenses such as the GNU GPL were created
1743 to close off this avenue to the production of proprietary software but
1744 such licenses are not enough. With the ongoing adoption of Free
1745 Software by individuals and groups, inevitably the community&#39;s
1746 expectations of license compliance are violated, usually out of
1747 ignorance of the way Free Software works, but not always. As Karen
1748 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
1749 Freedom&quot;&gt;FaiF&lt;/a&gt;
1750 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
1751 copyleft is nothing if no-one is willing and able to stand up in court
1752 to protect it. The reality of today&#39;s world is that legal
1753 representation is expensive, difficult and time consuming. With
1754 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
1755 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
1756 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
1757 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
1758 of the Linux project, Debian and other groups against GPL violations.
1759 In March the SFC supported a
1760 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
1761 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
1762 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
1763 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
1764 kernel. Since then two of their sponsors pulled corporate funding and
1765 conferences
1766 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
1767 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
1768 less on corporate funding and more on the broad community of
1769 individuals who support Free Software and copyleft. So the SFC has
1770 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
1771 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
1772 a community of folks who stand up for copyleft and the GPL by
1773 supporting their work on promoting and supporting copyleft and Free
1774 Software.&lt;/p&gt;
1775
1776 &lt;p&gt;If you support Free Software,
1777 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
1778 what the SFC do, agree with their
1779 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
1780 principles&lt;/a&gt;, are happy about their
1781 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
1782 work on a project that is an SFC
1783 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
1784 just want to stand up for copyleft, please join
1785 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
1786 Allan Webber&lt;/a&gt;,
1787 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
1788 Smith&lt;/a&gt;,
1789 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
1790 Bacon&lt;/a&gt;, myself and
1791 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
1792 becoming a
1793 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
1794 next week your donation will be
1795 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
1796 by an anonymous donor. Please also consider asking your employer to
1797 match your donation or become a sponsor of SFC. Don&#39;t forget to
1798 spread the word about your support for SFC via email, your blog and or
1799 social media accounts.&lt;/p&gt;
1800
1801 &lt;/blockquote&gt;
1802
1803 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
1804 of Software Freedom Conservancy myself. Perhaps you should be a
1805 supporter too?&lt;/p&gt;
1806 </description>
1807 </item>
1808
1809 <item>
1810 <title>PGP key transition statement for key EE4E02F9</title>
1811 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
1812 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
1813 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
1814 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
1815 set it up properly. I wanted to generate it offline and have it
1816 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
1817 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
1818 time to sit down with an offline machine almost took forever. But
1819 finally I&#39;ve been able to complete the process, and have now moved
1820 from my old GPG key to a new GPG key. See
1821 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
1822 full transition statement, signed with both my old and new key&lt;/a&gt; for
1823 the details. This is my new key:&lt;/p&gt;
1824
1825 &lt;pre&gt;
1826 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]
1827 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
1828 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
1829 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
1830 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
1831 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
1832 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
1833 &lt;/pre&gt;
1834
1835 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
1836 my old key.&lt;/p&gt;
1837
1838 &lt;p&gt;If you signed my old key
1839 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
1840 I&#39;d very much appreciate a signature on my new key, details and
1841 instructions in the transition statement. I m happy to reciprocate if
1842 you have a similarly signed transition statement to present.&lt;/p&gt;
1843 </description>
1844 </item>
1845
1846 <item>
1847 <title>The life and death of a laptop battery</title>
1848 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
1849 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
1850 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
1851 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
1852 But this do not last. The last few laptops gave me a feeling that
1853 within a year, the life time is just a fraction of what it used to be,
1854 and it slowly become painful to use the laptop without power connected
1855 all the time. Because of this, when I got a new Thinkpad X230 laptop
1856 about two years ago, I decided to monitor its battery state to have
1857 more hard facts when the battery started to fail.&lt;/p&gt;
1858
1859 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
1860
1861 &lt;p&gt;First I tried to find a sensible Debian package to record the
1862 battery status, assuming that this must be a problem already handled
1863 by someone else. I found
1864 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
1865 which collects statistics from the battery, but it was completely
1866 broken. I sent a few suggestions to the maintainer, but decided to
1867 write my own collector as a shell script while I waited for feedback
1868 from him. Via
1869 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
1870 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
1871 discovered
1872 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
1873 available in Debian.&lt;/p&gt;
1874
1875 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
1876 battery stats ever since. Now my
1877 /var/log/hjemmenett-battery-status.log file contain around 115,000
1878 measurements, from the time the battery was working great until now,
1879 when it is unable to charge above 7% of original capacity. My
1880 collector shell script is quite simple and look like this:&lt;/p&gt;
1881
1882 &lt;pre&gt;
1883 #!/bin/sh
1884 # Inspired by
1885 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
1886 # See also
1887 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
1888 logfile=/var/log/hjemmenett-battery-status.log
1889
1890 files=&quot;manufacturer model_name technology serial_number \
1891 energy_full energy_full_design energy_now cycle_count status&quot;
1892
1893 if [ ! -e &quot;$logfile&quot; ] ; then
1894 (
1895 printf &quot;timestamp,&quot;
1896 for f in $files; do
1897 printf &quot;%s,&quot; $f
1898 done
1899 echo
1900 ) &gt; &quot;$logfile&quot;
1901 fi
1902
1903 log_battery() {
1904 # Print complete message in one echo call, to avoid race condition
1905 # when several log processes run in parallel.
1906 msg=$(printf &quot;%s,&quot; $(date +%s); \
1907 for f in $files; do \
1908 printf &quot;%s,&quot; $(cat $f); \
1909 done)
1910 echo &quot;$msg&quot;
1911 }
1912
1913 cd /sys/class/power_supply
1914
1915 for bat in BAT*; do
1916 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
1917 done
1918 &lt;/pre&gt;
1919
1920 &lt;p&gt;The script is called when the power management system detect a
1921 change in the power status (power plug in or out), and when going into
1922 and out of hibernation and suspend. In addition, it collect a value
1923 every 10 minutes. This make it possible for me know when the battery
1924 is discharging, charging and how the maximum charge change over time.
1925 The code for the Debian package
1926 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
1927 available on github&lt;/a&gt;.&lt;/p&gt;
1928
1929 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
1930
1931 &lt;pre&gt;
1932 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1933 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
1934 [...]
1935 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
1936 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
1937 &lt;/pre&gt;
1938
1939 &lt;p&gt;I wrote a small script to create a graph of the charge development
1940 over time. This graph depicted above show the slow death of my laptop
1941 battery.&lt;/p&gt;
1942
1943 &lt;p&gt;But why is this happening? Why are my laptop batteries always
1944 dying in a year or two, while the batteries of space probes and
1945 satellites keep working year after year. If we are to believe
1946 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
1947 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
1948 chance, and the fix is to not charge the Lithium-ion batteries to 100%
1949 all the time, but to stay below 90% of full charge most of the time.
1950 I&#39;ve been told that the Tesla electric cars
1951 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
1952 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
1953 100% when preparing for a longer trip (not that I would want a car
1954 like Tesla where rights to privacy is abandoned, but that is another
1955 story), which I guess is the option we should have for laptops on
1956 Linux too.&lt;/p&gt;
1957
1958 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
1959 stop charging at 80%, unless requested to charge to 100% once in
1960 preparation for a longer trip? I found
1961 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
1962 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1963 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
1964 load).&lt;/p&gt;
1965
1966 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
1967 at the start. I also wonder why the &quot;full capacity&quot; increases some
1968 times, and if it is possible to repeat the process to get the battery
1969 back to design capacity. And I wonder if the discharge and charge
1970 speed change over time, or if this stay the same. I did not yet try
1971 to write a tool to calculate the derivative values of the battery
1972 level, but suspect some interesting insights might be learned from
1973 those.&lt;/p&gt;
1974
1975 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
1976 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1977 packages instead of the tp-smapi-dkms package I had tried to use
1978 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
1979 and stop. I&#39;ve done so now, but expect my existing battery is toast
1980 and need to be replaced. The proposal is unfortunately Thinkpad
1981 specific.&lt;/p&gt;
1982 </description>
1983 </item>
1984
1985 <item>
1986 <title>New laptop - some more clues and ideas based on feedback</title>
1987 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
1988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
1989 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
1990 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
1991 need for a new laptop, and provided very useful feedback. I wish to
1992 thank every one of these. Several pointed me to the possibility of
1993 fixing my X230, and I am already in the process of getting Lenovo to
1994 do so thanks to the on site, next day support contract covering the
1995 machine. But the battery is almost useless (I expect to replace it
1996 with a non-official battery) and I do not expect the machine to live
1997 for many more years, so it is time to plan its replacement. If I did
1998 not have a support contract, it was suggested to find replacement parts
1999 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
2000 might present a language barrier as I do not understand French.&lt;/p&gt;
2001
2002 &lt;p&gt;One tip I got was to use the
2003 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
2004 compare laptop models. It seem to have more models available than
2005 prisjakt.no. Another tip I got from someone I know have similar
2006 keyboard preferences was that the HP EliteBook 840 keyboard is not
2007 very good, and this matches my experience with earlier EliteBook
2008 keyboards I tested. Because of this, I will not consider it any further.
2009
2010 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
2011 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2012 (which is missing from the X240), and is working fairly well with
2013 Debian Sid/Unstable according to
2014 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
2015 got on the keyboard quality are not consistent. Some say the keyboard
2016 is good, others say it is ok, while others say it is not very good.
2017 Those with experience from X41 and and X60 agree that the X250
2018 keyboard is not as good as those trusty old laptops, and suggest I
2019 keep and fix my X230 instead of upgrading, or get a used X230 to
2020 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
2021 activity and battery status, which is very convenient on my X230. I&#39;m
2022 also told that the CPU fan is running very often, making it a bit
2023 noisy. In any case, the X250 do not work out of the box with Debian
2024 Stable/Jessie, one of my requirements.&lt;/p&gt;
2025
2026 &lt;p&gt;I have also gotten a few vendor proposals, one was
2027 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
2028 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
2029 The latter look very attractive to me.&lt;/p&gt;
2030
2031 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
2032 as I keep looking for a replacement.&lt;/p&gt;
2033
2034 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
2035 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
2036 different
2037 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
2038 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
2039 </description>
2040 </item>
2041
2042 <item>
2043 <title>Time to find a new laptop, as the old one is broken after only two years</title>
2044 <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>
2045 <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>
2046 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
2047 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
2048 replacement soon. The left 5 cm of the screen on my Thinkpad X230
2049 started flickering yesterday, and I suspect the cause is a broken
2050 cable, as changing the angle of the screen some times get rid of the
2051 flickering.&lt;/p&gt;
2052
2053 &lt;p&gt;My requirements have not really changed since I bought it, and is
2054 still as
2055 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
2056 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
2057 good help from
2058 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
2059 where I could select at least a few of the requirements (mouse pin,
2060 wifi, weight) and go through the rest manually. Three button mouse
2061 and a good keyboard is not available as an option, and all the three
2062 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
2063 G2) lack three mouse buttons). It is also unclear to me how good the
2064 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2065 the keyboard, even if the quality and robustness in the X series have
2066 deteriorated since X41.&lt;/p&gt;
2067
2068 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
2069 seem sensible to me? Are there better services around to search the
2070 set of available laptops for features? Please send me an email if you
2071 have suggestions.&lt;/p&gt;
2072
2073 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
2074 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
2075 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
2076 </description>
2077 </item>
2078
2079 <item>
2080 <title>How to stay with sysvinit in Debian Jessie</title>
2081 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
2082 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
2083 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
2084 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
2085 sysvinit as its boot system by default. But how can one keep using
2086 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2087 courtesy of
2088 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
2089 Schubert&lt;/a&gt; and
2090 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
2091 McVittie&lt;/a&gt;.
2092
2093 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
2094 keep sysvinit as your boot system, create a file
2095 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
2096 you upgrade:&lt;/p&gt;
2097
2098 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2099 Package: systemd-sysv
2100 Pin: release o=Debian
2101 Pin-Priority: -1
2102 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2103
2104 &lt;p&gt;This file content will tell apt and aptitude to not consider
2105 installing systemd-sysv as part of any installation and upgrade
2106 solution when resolving dependencies, and thus tell it to avoid
2107 systemd as a default boot system. The end result should be that the
2108 upgraded system keep using sysvinit.&lt;/p&gt;
2109
2110 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
2111 get sysvinit installed by default (debootstrap used by
2112 debian-installer have no option for this), but one can tell the
2113 installer to switch to sysvinit before the first boot. Either by
2114 using a kernel argument to the installer, or by adding a line to the
2115 preseed file used. First, the kernel command line argument:
2116
2117 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2118 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
2119 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2120
2121 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
2122
2123 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2124 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2125 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2126
2127 &lt;p&gt;One can of course also do this after the first boot by installing
2128 the sysvinit-core package.&lt;/p&gt;
2129
2130 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
2131 sysvinit boot sequence in Debian have several hardware specific bugs
2132 on Linux caused by the fact that it is unpredictable when hardware
2133 devices show up during boot. But on the other hand, the new default
2134 boot system still have a few rough edges I hope will be fixed before
2135 Jessie is released.&lt;/p&gt;
2136
2137 &lt;p&gt;Update 2014-11-26: Inspired by
2138 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
2139 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
2140 line.&lt;/p&gt;
2141 </description>
2142 </item>
2143
2144 <item>
2145 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
2146 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
2147 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
2148 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
2149 <description>&lt;p&gt;The right to communicate with your friends and family in private,
2150 without anyone snooping, is a right every citicen have in a liberal
2151 democracy. But this right is under serious attack these days.&lt;/p&gt;
2152
2153 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
2154 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2155 the whisleblower Snowden) more expensive for Internet email,
2156 is to deliver all email using SMTP via Tor. Such SMTP option would be
2157 a nice addition to the FreedomBox project if we could send email
2158 between FreedomBox machines without leaking metadata about the emails
2159 to the people peeking on the wire. I
2160 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
2161 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
2162 lot of useful feedback and suggestions. It also became obvious to me
2163 that this was not a novel idea, as the same idea was tested and
2164 documented by Johannes Berg as early as 2006, and both
2165 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
2166 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
2167 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
2168
2169 &lt;p&gt;To implement such system one need to set up a Tor hidden service
2170 providing the SMTP protocol on port 25, and use email addresses
2171 looking like username@hidden-service-name.onion. With such addresses
2172 the connections to port 25 on hidden-service-name.onion using Tor will
2173 go to the correct SMTP server. To do this, one need to configure the
2174 Tor daemon to provide the hidden service and the mail server to accept
2175 emails for this .onion domain. To learn more about Exim configuration
2176 in Debian and test the design provided by Johannes Berg in his FAQ, I
2177 set out yesterday to create a Debian package for making it trivial to
2178 set up such SMTP over Tor service based on Debian. Getting it to work
2179 were fairly easy, and
2180 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
2181 source code for the Debian package&lt;/a&gt; is available from github. I
2182 plan to move it into Debian if further testing prove this to be a
2183 useful approach.&lt;/p&gt;
2184
2185 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
2186 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
2187 get rid of exim4). Install tor, clone the git repository mentioned
2188 above, build the deb and install it on the machine. Next, run
2189 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
2190 the instructions to get the service up and running. Restart tor and
2191 exim when it is done, and test mail delivery using swaks like
2192 this:&lt;/p&gt;
2193
2194 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2195 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2196 --to fbx@dutlqrrmjhtfa3vp.onion
2197 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2198
2199 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
2200 address with your own address to test your server. :)&lt;/p&gt;
2201
2202 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
2203 easier and more automatic. Especially the tor setup need more work.
2204 Also, the package include a tor-smtp tool written in C, but its task
2205 should probably be rewritten in some script language to make the deb
2206 architecture independent. It would probably also make the code easier
2207 to review. The tor-smtp tool currently need to listen on a socket for
2208 exim to talk to it and is started using xinetd. It would be better if
2209 no daemon and no socket is needed. I suspect it is possible to get
2210 exim to run a command line tool for delivery instead of talking to a
2211 socket, and hope to figure out how in a future version of this
2212 system.&lt;/p&gt;
2213
2214 &lt;p&gt;Until I wipe my test machine, I can be reached using the
2215 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
2216 SMTorP. :)&lt;/p&gt;
2217 </description>
2218 </item>
2219
2220 <item>
2221 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
2222 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
2223 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
2224 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
2225 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
2226 alioth.debian.org, you know the web interface is fairly slow to
2227 operate. First you visit one web page, enter the moderation password
2228 and get a new page shown with a list of all the messages to moderate
2229 and various options for each email address. This take a while for
2230 every list you moderate, and you need to do it regularly to do a good
2231 job as a list moderator. But there is a quick alternative,
2232 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
2233 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
2234 to moderate in a fraction of a second. Here is a test run on two
2235 lists I recently took over:&lt;/p&gt;
2236
2237 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2238 % time listadmin xiph
2239 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2240 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2241
2242 real 0m1.709s
2243 user 0m0.232s
2244 sys 0m0.012s
2245 %
2246 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2247
2248 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
2249 there are no message in the moderation queue. Every morning I
2250 currently moderate 68 mailman lists, and it normally take around two
2251 minutes. When I took over the two pkg-xiph lists above a few days
2252 ago, there were 400 emails waiting in the moderator queue. It took me
2253 less than 15 minutes to process them all using the listadmin
2254 program.&lt;/p&gt;
2255
2256 &lt;p&gt;If you install
2257 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
2258 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
2259 with content like this, the moderation task is a breeze:&lt;/p&gt;
2260
2261 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2262 username username@example.org
2263 spamlevel 23
2264 default discard
2265 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
2266
2267 password secret
2268 adminurl https://{domain}/mailman/admindb/{list}
2269 mailman-list@lists.example.com
2270
2271 password hidden
2272 other-list@otherserver.example.org
2273 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2274
2275 &lt;p&gt;There are other options to set as well. Check the manual page to
2276 learn the details.&lt;/p&gt;
2277
2278 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
2279 the SSL certificate is self signed or not properly signed by a
2280 generally accepted signing authority, you can set a environment
2281 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
2282
2283 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2284 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
2285 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2286
2287 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
2288 can provide an argument to the listadmin script like I do in the
2289 initial screen dump (the xiph argument). Using an argument, only
2290 lists matching the argument string will be processed. This make it
2291 quick to accept messages if you notice the moderation request in your
2292 email.&lt;/p&gt;
2293
2294 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
2295 mailing lists, as I simply do not have time to spend on that if the
2296 process was any slower. The listadmin program have saved me hours of
2297 time I could spend elsewhere over the years. It truly is nice free
2298 software.&lt;/p&gt;
2299
2300 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2301 activities, please send Bitcoin donations to my address
2302 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2303
2304 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
2305 configuration example. Also, I&#39;ve been told that the
2306 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
2307 sure why.&lt;/p&gt;
2308 </description>
2309 </item>
2310
2311 <item>
2312 <title>Debian Jessie, PXE and automatic firmware installation</title>
2313 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
2314 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
2315 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
2316 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
2317 problem that the WiFi card require some firmware to work properly.
2318 And it has been a pain to fix this using preseeding in Debian.
2319 Normally something more is needed. But thanks to
2320 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
2321 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
2322 to do this using simple preseeding.&lt;/p&gt;
2323
2324 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
2325 firmware for the hardware found in the machine (actually, requested by
2326 the kernel modules for the hardware). (It can also install user space
2327 programs supporting the hardware detected, but that is not the focus
2328 of this story.)&lt;/p&gt;
2329
2330 &lt;p&gt;To get this working in the default installation, two preeseding
2331 values are needed. First, the isenkram-cli package must be installed
2332 into the target chroot (aka the hard drive) before tasksel is executed
2333 in the pkgsel step of the debian-installer system. This is done by
2334 preseeding the base-installer/includes debconf value to include the
2335 isenkram-cli package. The package name is next passed to debootstrap
2336 for installation. With the isenkram-cli package in place, tasksel
2337 will automatically use the isenkram tasks to detect hardware specific
2338 packages for the machine being installed and install them, because
2339 isenkram-cli contain tasksel tasks.&lt;/p&gt;
2340
2341 &lt;p&gt;Second, one need to enable the non-free APT repository, because
2342 most firmware unfortunately is non-free. This is done by preseeding
2343 the apt-mirror-setup step. This is unfortunate, but for a lot of
2344 hardware it is the only option in Debian.&lt;/p&gt;
2345
2346 &lt;p&gt;The end result is two lines needed in your preseeding file to get
2347 firmware installed automatically by the installer:&lt;/p&gt;
2348
2349 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2350 base-installer base-installer/includes string isenkram-cli
2351 apt-mirror-setup apt-setup/non-free boolean true
2352 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2353
2354 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
2355 both firmware and user space packages when using this method. It also
2356 do not work well, so use version 0.15 or later. Installing both
2357 firmware and user space packages might give you a bit more than you
2358 want, so I decided to split the tasksel task in two, one for firmware
2359 and one for user space programs. The firmware task is enabled by
2360 default, while the one for user space programs is not. This split is
2361 implemented in the package currently in unstable.&lt;/p&gt;
2362
2363 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
2364 this recipe work for you. :)&lt;/p&gt;
2365
2366 &lt;p&gt;So, I bet you are wondering, how can this work. First and
2367 foremost, it work because tasksel is modular, and driven by whatever
2368 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2369 isenkram-cli package place two files for tasksel to find. First there
2370 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
2371
2372 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2373 Task: isenkram-packages
2374 Section: hardware
2375 Description: Hardware specific packages (autodetected by isenkram)
2376 Based on the detected hardware various hardware specific packages are
2377 proposed.
2378 Test-new-install: show show
2379 Relevance: 8
2380 Packages: for-current-hardware
2381
2382 Task: isenkram-firmware
2383 Section: hardware
2384 Description: Hardware specific firmware packages (autodetected by isenkram)
2385 Based on the detected hardware various hardware specific firmware
2386 packages are proposed.
2387 Test-new-install: mark show
2388 Relevance: 8
2389 Packages: for-current-hardware-firmware
2390 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2391
2392 &lt;p&gt;The key parts are Test-new-install which indicate how the task
2393 should be handled and the Packages line referencing to a script in
2394 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2395 list of packages to install. The for-current-hardware-firmware script
2396 look like this to list relevant firmware for the machine:
2397
2398 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2399 #!/bin/sh
2400 #
2401 PATH=/usr/sbin:$PATH
2402 export PATH
2403 isenkram-autoinstall-firmware -l
2404 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2405
2406 &lt;p&gt;With those two pieces in place, the firmware is installed by
2407 tasksel during the normal d-i run. :)&lt;/p&gt;
2408
2409 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
2410 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
2411 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
2412 install.&lt;/p&gt;
2413
2414 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
2415 pilots in testing this feature, as isenkram is used there now to
2416 install firmware, replacing the earlier scripts.&lt;/p&gt;
2417 </description>
2418 </item>
2419
2420 <item>
2421 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
2422 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
2423 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
2424 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
2425 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
2426 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2427 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
2428 on a screen normally showing the bread types and prizes:&lt;/p&gt;
2429
2430 &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;
2431
2432 &lt;p&gt;If it had booted as it was supposed to, I would never had known
2433 about this hidden Linux installation. It is interesting what
2434 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
2435 </description>
2436 </item>
2437
2438 <item>
2439 <title>New lsdvd release version 0.17 is ready</title>
2440 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
2441 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
2442 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
2443 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
2444 got a new set of developers a few weeks ago, after the original
2445 developer decided to step down and pass the project to fresh blood.
2446 This project is now maintained by Petter Reinholdtsen and Steve
2447 Dibb.&lt;/p&gt;
2448
2449 &lt;p&gt;I just wrapped up
2450 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
2451 new lsdvd release&lt;/a&gt;, available in git or from
2452 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
2453 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
2454 0.17.&lt;/p&gt;
2455
2456 &lt;ul&gt;
2457
2458 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
2459 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
2460 non-existant, to work around additional copy protection&lt;/li&gt;
2461 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
2462 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
2463 &lt;li&gt;Fix include orders&lt;/li&gt;
2464 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
2465 &lt;li&gt;Fix the chapter count&lt;/li&gt;
2466 &lt;li&gt;Make sure the array size and the array limit used when initialising
2467 the palette size is the same.&lt;/li&gt;
2468 &lt;li&gt;Fix array printing.&lt;/li&gt;
2469 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
2470 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
2471 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
2472 with more GCC compiler warnings.&lt;/li&gt;
2473
2474 &lt;/ul&gt;
2475
2476 &lt;p&gt;This change bring together patches for lsdvd in use in various
2477 Linux and Unix distributions, as well as patches submitted to the
2478 project the last nine years. Please check it out. :)&lt;/p&gt;
2479 </description>
2480 </item>
2481
2482 <item>
2483 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
2484 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
2485 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
2486 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
2487 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
2488 project&lt;/a&gt; provide a Linux solution for schools, including a
2489 powerful desktop with education software, a central server providing
2490 web pages, user database, user home directories, central login and PXE
2491 boot of both clients without disk and the installation to install Debian
2492 Edu on machines with disk (and a few other services perhaps to small
2493 to mention here). We in the Debian Edu team are currently working on
2494 the Jessie based version, trying to get everything in shape before the
2495 freeze, to avoid having to maintain our own package repository in the
2496 future. The
2497 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
2498 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
2499 work left. Some fatal problems block testing, breaking the installer,
2500 but it is possible to work around these to get anyway. Here is a
2501 recipe on how to get the installation limping along.&lt;/p&gt;
2502
2503 &lt;p&gt;First, download the test ISO via
2504 &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;,
2505 &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;
2506 or rsync (use
2507 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
2508 The ISO build was broken on Tuesday, so we do not get a new ISO every
2509 12 hours or so, but thankfully the ISO we already got we are able to
2510 install with some tweaking.&lt;/p&gt;
2511
2512 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
2513 (use Alt-Ctrl-F2), run&lt;/p&gt;
2514
2515 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2516 nano /usr/bin/edu-eatmydata-install
2517 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2518
2519 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
2520 optimization. Return to the installation, select the profile you want
2521 and continue. Without this change, exim4-config will fail to install
2522 due to a known bug in eatmydata.&lt;/p&gt;
2523
2524 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
2525 this do not work, figure out what your correct value would be. All my
2526 test machines need /dev/sda, so I have no advice if it do not fit
2527 your need.&lt;/p&gt;
2528
2529 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
2530 root after the initial boot from hard drive, and install the
2531 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2532 or mate. If you want several desktop options, install more than one
2533 metapackage. Once this is done, reboot and you should have a working
2534 graphical login screen. This workaround should no longer be needed
2535 once the education-tasks package version 1.801 enter testing in two
2536 days.&lt;/p&gt;
2537
2538 &lt;p&gt;I believe the ISO build will start working on two days when the new
2539 tasksel package enter testing and Steve McIntyre get a chance to
2540 update the debian-cd git repository. The eatmydata, grub and desktop
2541 issues are already fixed in unstable and testing, and should show up
2542 on the ISO as soon as the ISO build start working again. Well the
2543 eatmydata optimization is really just disabled. The proper fix
2544 require an upload by the eatmydata maintainer applying the patch
2545 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
2546 The rest have proper fixes in unstable.&lt;/p&gt;
2547
2548 &lt;p&gt;I hope this get you going with the installation testing, as we are
2549 quickly running out of time trying to get our Jessie based
2550 installation ready before the distribution freeze in a month.&lt;/p&gt;
2551 </description>
2552 </item>
2553
2554 <item>
2555 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
2556 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
2557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
2558 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
2559 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
2560 to handle my fairly large DVD collection. It is a nice command line
2561 tool to get details about a DVD, like title, tracks, track length,
2562 etc, in XML, Perl or human readable format. But lsdvd have not seen
2563 any new development since 2006 and had a few irritating bugs affecting
2564 its use with some DVDs. Upstream seemed to be dead, and in January I
2565 sent a small probe asking for a version control repository for the
2566 project, without any reply. But I use it regularly and would like to
2567 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
2568 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
2569 the project admin, and after getting a reply from him explaining that
2570 he was no longer interested in the project, I asked if I could take
2571 over. And yesterday, I became project admin.&lt;/p&gt;
2572
2573 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
2574 maintainer interested in joining forces to maintain the upstream
2575 project, and I hope we can get a new release out fairly quickly,
2576 collecting the patches spread around on the internet into on place.
2577 I&#39;ve added the relevant Debian patches to the freshly created git
2578 repository, and expect the Gentoo patches to make it too. If you got
2579 a DVD collection and care about command line tools, check out
2580 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
2581 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
2582 list&lt;/a&gt;. :)&lt;/p&gt;
2583 </description>
2584 </item>
2585
2586 <item>
2587 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
2588 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
2589 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
2590 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
2591 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
2592 a lot quicker. When we install more than 2000 packages in
2593 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
2594 tasksel in the installer, unpacking the binary packages take forever.
2595 A part of the slow I/O issue was discussed in
2596 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
2597 much file system sync-ing done by dpkg, which is the package
2598 responsible for unpacking the binary packages. Other parts (like code
2599 executed by postinst scripts) might also sync to disk during
2600 installation. All this sync-ing to disk do not really make sense to
2601 me. If the machine crash half-way through, I start over, I do not try
2602 to salvage the half installed system. So the failure sync-ing is
2603 supposed to protect against, hardware or system crash, is not really
2604 relevant while the installer is running.&lt;/p&gt;
2605
2606 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
2607 system sync()-ing in a fairly non-intrusive way, without the need to
2608 change the code in several packages. The idea is not new, but I have
2609 not heard anyone propose the approach using dpkg-divert before. It
2610 depend on the small and clever package
2611 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
2612 uses LD_PRELOAD to replace the system functions for syncing data to
2613 disk with functions doing nothing, thus allowing programs to live
2614 dangerous while speeding up disk I/O significantly. Instead of
2615 modifying the implementation of dpkg, apt and tasksel (which are the
2616 packages responsible for selecting, fetching and installing packages),
2617 it occurred to me that we could just divert the programs away, replace
2618 them with a simple shell wrapper calling
2619 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
2620 Two days ago I decided to test the idea, and wrapped up a simple
2621 implementation for the Debian Edu udeb.&lt;/p&gt;
2622
2623 &lt;p&gt;The effect was stunning. In my first test it reduced the running
2624 time of the pkgsel step (installing tasks) from 64 to less than 44
2625 minutes (20 minutes shaved off the installation) on an old Dell
2626 Latitude D505 machine. I am not quite sure what the optimised time
2627 would have been, as I messed up the testing a bit, causing the debconf
2628 priority to get low enough for two questions to pop up during
2629 installation. As soon as I saw the questions I moved the installation
2630 along, but do not know how long the question were holding up the
2631 installation. I did some more measurements using Debian Edu Jessie,
2632 and got these results. The time measured is the time stamp in
2633 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
2634 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
2635 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2636 timing thus do not depend on how quickly the user handle the tasksel
2637 dialog.&lt;/p&gt;
2638
2639 &lt;p&gt;&lt;table&gt;
2640
2641 &lt;tr&gt;
2642 &lt;th&gt;Machine/setup&lt;/th&gt;
2643 &lt;th&gt;Original tasksel&lt;/th&gt;
2644 &lt;th&gt;Optimised tasksel&lt;/th&gt;
2645 &lt;th&gt;Reduction&lt;/th&gt;
2646 &lt;/tr&gt;
2647
2648 &lt;tr&gt;
2649 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
2650 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
2651 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
2652 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
2653 &lt;/tr&gt;
2654
2655 &lt;tr&gt;
2656 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
2657 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
2658 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
2659 &lt;td&gt;23 min 40%&lt;/td&gt;
2660 &lt;/tr&gt;
2661
2662 &lt;tr&gt;
2663 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
2664 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
2665 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
2666 &lt;td&gt;11 min 50%&lt;/td&gt;
2667 &lt;/tr&gt;
2668
2669 &lt;tr&gt;
2670 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
2671 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
2672 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
2673 &lt;td&gt;2 min 33%&lt;/td&gt;
2674 &lt;/tr&gt;
2675
2676 &lt;tr&gt;
2677 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
2678 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
2679 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
2680 &lt;td&gt;4 min 21%&lt;/td&gt;
2681 &lt;/tr&gt;
2682
2683 &lt;/table&gt;&lt;/p&gt;
2684
2685 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
2686 time is spent downloading packages. The connection to the Internet
2687 was 100Mbit/s during testing, so downloading should not be a
2688 significant factor in the measurement. Download typically took a few
2689 seconds to a few minutes, depending on the amount of packages being
2690 installed.&lt;/p&gt;
2691
2692 &lt;p&gt;The speedup is implemented by using two hooks in
2693 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
2694 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
2695 finish-install.d hook to remove the divert at the end of the
2696 installation. I picked the pre-pkgsel.d hook instead of the
2697 post-base-installer.d hook because I test using an ISO without the
2698 eatmydata package included, and the post-base-installer.d hook in
2699 Debian Edu can only operate on packages included in the ISO. The
2700 negative effect of this is that I am unable to activate this
2701 optimization for the kernel installation step in d-i. If the code is
2702 moved to the post-base-installer.d hook, the speedup would be larger
2703 for the entire installation.&lt;/p&gt;
2704
2705 &lt;p&gt;I&#39;ve implemented this in the
2706 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
2707 git repository, and plan to provide the optimization as part of the
2708 Debian Edu installation. If you want to test this yourself, you can
2709 create two files in the installer (or in an udeb). One shell script
2710 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
2711
2712 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2713 #!/bin/sh
2714 set -e
2715 . /usr/share/debconf/confmodule
2716 info() {
2717 logger -t my-pkgsel &quot;info: $*&quot;
2718 }
2719 error() {
2720 logger -t my-pkgsel &quot;error: $*&quot;
2721 }
2722 override_install() {
2723 apt-install eatmydata || true
2724 if [ -x /target/usr/bin/eatmydata ] ; then
2725 for bin in dpkg apt-get aptitude tasksel ; do
2726 file=/usr/bin/$bin
2727 # Test that the file exist and have not been diverted already.
2728 if [ -f /target$file ] ; then
2729 info &quot;diverting $file using eatmydata&quot;
2730 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
2731 &gt; /target$file.edu
2732 chmod 755 /target$file.edu
2733 in-target dpkg-divert --package debian-edu-config \
2734 --rename --quiet --add $file
2735 ln -sf ./$bin.edu /target$file
2736 else
2737 error &quot;unable to divert $file, as it is missing.&quot;
2738 fi
2739 done
2740 else
2741 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
2742 fi
2743 }
2744
2745 override_install
2746 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2747
2748 &lt;p&gt;To clean up, another shell script should go into
2749 /usr/lib/finish-install.d/ with code like this:
2750
2751 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2752 #! /bin/sh -e
2753 . /usr/share/debconf/confmodule
2754 error() {
2755 logger -t my-finish-install &quot;error: $@&quot;
2756 }
2757 remove_install_override() {
2758 for bin in dpkg apt-get aptitude tasksel ; do
2759 file=/usr/bin/$bin
2760 if [ -x /target$file.edu ] ; then
2761 rm /target$file
2762 in-target dpkg-divert --package debian-edu-config \
2763 --rename --quiet --remove $file
2764 rm /target$file.edu
2765 else
2766 error &quot;Missing divert for $file.&quot;
2767 fi
2768 done
2769 sync # Flush file buffers before continuing
2770 }
2771
2772 remove_install_override
2773 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2774
2775 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
2776 edu-eatmydata-install and call it from the pre-pkgsel.d and
2777 finish-install.d scripts.&lt;/p&gt;
2778
2779 &lt;p&gt;By now you might ask if this change should get into the normal
2780 Debian installer too? I suspect it should, but am not sure the
2781 current debian-installer coordinators find it useful enough. It also
2782 depend on the side effects of the change. I&#39;m not aware of any, but I
2783 guess we will see if the change is safe after some more testing.
2784 Perhaps there is some package in Debian depending on sync() and
2785 fsync() having effect? Perhaps it should go into its own udeb, to
2786 allow those of us wanting to enable it to do so without affecting
2787 everyone.&lt;/p&gt;
2788
2789 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
2790 will break installation of all programs using gnutls because of
2791 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
2792 eatmydata package in Debian will solve it.&lt;/p&gt;
2793
2794 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
2795 the optimization work again. And I have discovered that the
2796 dpkg-divert trick is not really needed and implemented a slightly
2797 simpler approach as part of the debian-edu-install package. See
2798 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
2799
2800 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
2801 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
2802 triggering on i386 made it into testing, and broke this installation
2803 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
2804 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
2805 </description>
2806 </item>
2807
2808 <item>
2809 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
2810 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
2811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
2812 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
2813 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
2814 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
2815 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
2816 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
2817 learn that there is a large set of publicly available key servers to
2818 use when looking for peoples public key. So far I have used
2819 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2820 were misbehaving, but those days are ended. The servers I have used
2821 up until yesterday have been slow and some times unavailable. I hope
2822 those problems are gone now.&lt;/p&gt;
2823
2824 &lt;p&gt;Behind the round robin DNS entry of the
2825 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
2826 there is a pool of more than 100 keyservers which are checked every
2827 day to ensure they are well connected and up to date. It must be
2828 better than what I have used so far. :)&lt;/p&gt;
2829
2830 &lt;p&gt;Yesterdays speaker told me that the service is the default
2831 keyserver provided by the default configuration in GnuPG, but this do
2832 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
2833
2834 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
2835 line:&lt;/p&gt;
2836
2837 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2838 keyserver pool.sks-keyservers.net
2839 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2840
2841 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
2842 entries in DNS. Just for fun, I did just that at work, so now every
2843 user of GnuPG at the University of Oslo should find a OpenGPG
2844 keyserver automatically should their need it:&lt;/p&gt;
2845
2846 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2847 % host -t srv _pgpkey-http._tcp.uio.no
2848 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
2849 %
2850 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2851
2852 &lt;p&gt;Now if only
2853 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
2854 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
2855 very happy. It can look up a given key or search for a user ID, but I
2856 normally do not want that, but to find a trust path from my key to
2857 another key. Given a user ID or key ID, I would like to find (and
2858 download) the keys representing a signature path from my key to the
2859 key in question, to be able to get a trust path between the two keys.
2860 This is as far as I can tell not possible today. Perhaps something
2861 for a future version of the protocol?&lt;/p&gt;
2862 </description>
2863 </item>
2864
2865 <item>
2866 <title>From English wiki to translated PDF and epub via Docbook</title>
2867 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
2868 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
2869 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
2870 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
2871 project&lt;/a&gt; provide an instruction manual for teachers, system
2872 administrators and other users that contain useful tips for setting up
2873 and maintaining a Debian Edu installation. This text is about how the
2874 text processing of this manual is handled in the project.&lt;/p&gt;
2875
2876 &lt;p&gt;One goal of the project is to provide information in the native
2877 language of its users, and for this we need to handle translations.
2878 But we also want to make sure each language contain the same
2879 information, so for this we need a good way to keep the translations
2880 in sync. And we want it to be easy for our users to improve the
2881 documentation, avoiding the need to learn special formats or tools to
2882 contribute, and the obvious way to do this is to make it possible to
2883 edit the documentation using a web browser. We also want it to be
2884 easy for translators to keep the translation up to date, and give them
2885 help in figuring out what need to be translated. Here is the list of
2886 tools and the process we have found trying to reach all these
2887 goals.&lt;/p&gt;
2888
2889 &lt;p&gt;We maintain the authoritative source of our manual in the
2890 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
2891 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
2892 front page with references to the different chapters, several pages
2893 for each chapter, and finally one &quot;collection page&quot; gluing all the
2894 chapters together into one large web page (aka
2895 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
2896 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
2897 processing and translations. Thanks to the fact that the
2898 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
2899 wiki.debian.org support exporting pages in
2900 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
2901 the list of pages to export using the raw version of the AllInOne
2902 page, loop over each of them to generate a Docbook XML version of the
2903 manual. This process also download images and transform image
2904 references to use the locally downloaded images. The generated
2905 Docbook XML files are slightly broken, so some post-processing is done
2906 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
2907 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2908 a handfull of images. The XML file can now be used to generate PDF, HTML
2909 and epub versions of the English manual. This is the basic step of
2910 our process, making PDF (using dblatex), HTML (using xsltproc) and
2911 epub (using dbtoepub) version from Docbook XML, and the resulting files
2912 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
2913
2914 &lt;p&gt;But English documentation is not enough for us. We want translated
2915 documentation too, and we want to make it easy for translators to
2916 track the English original. For this we use the
2917 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
2918 which allow us to transform the English Docbook XML file into a
2919 translation file (a .pot file), usable with the normal gettext based
2920 translation tools used by those translating free software. The pot
2921 file is used to create and maintain translation files (several .po
2922 files), which the translations update with the native language
2923 translations of all titles, paragraphs and blocks of text in the
2924 original. The next step is combining the original English Docbook XML
2925 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2926 create a translated Docbook XML file (in this case
2927 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2928 translated, if the translation is not complete) Docbook XML file can
2929 then be used like the original to create a PDF, HTML and epub version
2930 of the documentation.&lt;/p&gt;
2931
2932 &lt;p&gt;The translators use different tools to edit the .po files. We
2933 recommend using
2934 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
2935 while some use emacs and vi, others can use web based editors like
2936 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
2937 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
2938 is where the .po file end up, in our git repository. Updated
2939 translations can either be committed directly to git, or submitted as
2940 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
2941 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
2942
2943 &lt;p&gt;One challenge is images, which both might need to be translated (if
2944 they show translated user applications), and are needed in different
2945 formats when creating PDF and HTML versions (epub is a HTML version in
2946 this regard). For this we transform the original PNG images to the
2947 needed density and format during build, and have a way to provide
2948 translated images by storing translated versions in
2949 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2950 package maintainers know more.&lt;/p&gt;
2951
2952 &lt;p&gt;If you wonder what the result look like, we provide
2953 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
2954 of the documentation packages on the web&lt;/a&gt;. See for example the
2955 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
2956 PDF version&lt;/a&gt; or the
2957 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
2958 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
2959 but perhaps it will be done in the future.&lt;/p&gt;
2960
2961 &lt;p&gt;To learn more, check out
2962 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
2963 debian-edu-doc package&lt;/a&gt;,
2964 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
2965 manual on the wiki&lt;/a&gt; and
2966 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
2967 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
2968 </description>
2969 </item>
2970
2971 <item>
2972 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
2973 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
2974 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
2975 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
2976 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
2977 related packages relevant for the computer installed automatically.
2978 So I implemented one, using
2979 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
2980 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
2981 run tasksel as user root. You should be presented with a new option,
2982 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
2983 select it, tasksel will install the packages isenkram claim is fit for
2984 the current hardware, hot pluggable or not.&lt;p&gt;
2985
2986 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
2987 description, and the other is the script used to extract the list of
2988 packages to install. The first part is in
2989 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
2990 this:&lt;/p&gt;
2991
2992 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2993 Task: isenkram
2994 Section: hardware
2995 Description: Hardware specific packages (autodetected by isenkram)
2996 Based on the detected hardware various hardware specific packages are
2997 proposed.
2998 Test-new-install: mark show
2999 Relevance: 8
3000 Packages: for-current-hardware
3001 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3002
3003 &lt;p&gt;The second part is in
3004 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
3005 this:&lt;/p&gt;
3006
3007 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3008 #!/bin/sh
3009 #
3010 (
3011 isenkram-lookup
3012 isenkram-autoinstall-firmware -l
3013 ) | sort -u
3014 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3015
3016 &lt;p&gt;All in all, a very short and simple implementation making it
3017 trivial to install the hardware dependent package we all may want to
3018 have installed on our machines. I&#39;ve not been able to find a way to
3019 get tasksel to tell you exactly which packages it plan to install
3020 before doing the installation. So if you are curious or careful,
3021 check the output from the isenkram-* command line tools first.&lt;/p&gt;
3022
3023 &lt;p&gt;The information about which packages are handling which hardware is
3024 fetched either from the isenkram package itself in
3025 /usr/share/isenkram/, from git.debian.org or from the APT package
3026 database (using the Modaliases header). The APT package database
3027 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3028 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
3029 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
3030 the python-apt code (bug
3031 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
3032 workaround I was able to get rid of the file descriptor leak and
3033 reduce the memory leak from ~30 MiB per hardware detection down to
3034 around 2 MiB per hardware detection. It should make the desktop
3035 daemon a lot more useful. The fix is in version 0.7 uploaded to
3036 unstable today.&lt;/p&gt;
3037
3038 &lt;p&gt;I believe the current way of mapping hardware to packages in
3039 Isenkram is is a good draft, but in the future I expect isenkram to
3040 use the AppStream data source for this. A proposal for getting proper
3041 AppStream support into Debian is floating around as
3042 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
3043 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
3044 project&lt;/a&gt; will take place this summer to improve the situation. I
3045 look forward to seeing the result, and welcome patches for isenkram to
3046 start using the information when it is ready.&lt;/p&gt;
3047
3048 &lt;p&gt;If you want your package to map to some specific hardware, either
3049 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
3050 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
3051 package&lt;/a&gt; or submit a bug report with the details to the isenkram
3052 package. See also
3053 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
3054 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
3055 the information will be migrated to AppStream eventually, but for the
3056 moment I got no better place to store it.&lt;/p&gt;
3057 </description>
3058 </item>
3059
3060 <item>
3061 <title>FreedomBox milestone - all packages now in Debian Sid</title>
3062 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
3063 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
3064 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
3065 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3066 project&lt;/a&gt; is working on providing the software and hardware to make
3067 it easy for non-technical people to host their data and communication
3068 at home, and being able to communicate with their friends and family
3069 encrypted and away from prying eyes. It is still going strong, and
3070 today a major mile stone was reached.&lt;/p&gt;
3071
3072 &lt;p&gt;Today, the last of the packages currently used by the project to
3073 created the system images were accepted into Debian Unstable. It was
3074 the freedombox-setup package, which is used to configure the images
3075 during build and on the first boot. Now all one need to get going is
3076 the build code from the freedom-maker git repository and packages from
3077 Debian. And once the freedombox-setup package enter testing, we can
3078 build everything directly from Debian. :)&lt;/p&gt;
3079
3080 &lt;p&gt;Some key packages used by Freedombox are
3081 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
3082 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
3083 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
3084 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
3085 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
3086 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
3087 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
3088 are plans to integrate more packages into the setup. User
3089 documentation is maintained on the Debian wiki. Please
3090 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
3091 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
3092
3093 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
3094 setup, run this on a Debian machine using a user with sudo rights to
3095 become root:&lt;/p&gt;
3096
3097 &lt;p&gt;&lt;pre&gt;
3098 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3099 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3100 u-boot-tools
3101 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3102 freedom-maker
3103 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3104 &lt;/pre&gt;&lt;/p&gt;
3105
3106 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3107 devices. See the README in the freedom-maker git repo for more
3108 details on the build. If you do not want all three images, trim the
3109 make line. Note that the virtualbox-image target is not really
3110 virtualbox specific. It create a x86 image usable in kvm, qemu,
3111 vmware and any other x86 virtual machine environment. You might need
3112 the version of vmdebootstrap in Jessie to get the build working, as it
3113 include fixes for a race condition with kpartx.&lt;/p&gt;
3114
3115 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3116 method, boot a Debian Wheezy ISO and use this boot argument to load
3117 the preseed values:&lt;/p&gt;
3118
3119 &lt;p&gt;&lt;pre&gt;
3120 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;
3121 &lt;/pre&gt;&lt;/p&gt;
3122
3123 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
3124 it still work.&lt;/p&gt;
3125
3126 &lt;p&gt;If you wonder how to help, one task you could look at is using
3127 systemd as the boot system. It will become the default for Linux in
3128 Jessie, so we need to make sure it is usable on the Freedombox. I did
3129 a simple test a few weeks ago, and noticed dnsmasq failed to start
3130 during boot when using systemd. I suspect there are other problems
3131 too. :) To detect problems, there is a test suite included, which can
3132 be run from the plinth web interface.&lt;/p&gt;
3133
3134 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3135 us get the new release published. :) Please join us on
3136 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3137 irc.debian.org)&lt;/a&gt; and
3138 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3139 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3140 </description>
3141 </item>
3142
3143 <item>
3144 <title>S3QL, a locally mounted cloud file system - nice free software</title>
3145 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
3146 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
3147 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
3148 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
3149 solution for use at home. My requirements are simple, it must be
3150 cheap and locally encrypted (in other words, I keep the encryption
3151 keys, the storage provider do not have access to my private files).
3152 One idea me and my friends had many years ago, before the cloud
3153 storage providers showed up, was to use Google mail as storage,
3154 writing a Linux block device storing blocks as emails in the mail
3155 service provided by Google, and thus get heaps of free space. On top
3156 of this one can add encryption, RAID and volume management to have
3157 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3158 I never found time to implement such system. But the last few weeks I
3159 have looked at a system called
3160 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
3161 mounted network backed file system with the features I need.&lt;/p&gt;
3162
3163 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
3164 handling several different storage providers, any with Amazon S3,
3165 Google Drive or OpenStack API. There are heaps of such storage
3166 providers. S3QL can also use a local directory as storage, which
3167 combined with sshfs allow for file storage on any ssh server. S3QL
3168 include support for encryption, compression, de-duplication, snapshots
3169 and immutable file systems, allowing me to mount the remote storage as
3170 a local mount point, look at and use the files as if they were local,
3171 while the content is stored in the cloud as well. This allow me to
3172 have a backup that should survive fire. The file system can not be
3173 shared between several machines at the same time, as only one can
3174 mount it at the time, but any machine with the encryption key and
3175 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
3176
3177 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
3178 package is included already. So to get started, run &lt;tt&gt;apt-get
3179 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
3180 Greenqloud, after reading their nice recipe on
3181 &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
3182 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
3183 in Iceland more than those in USA when it come to keeping my personal
3184 data safe and private, and thus would rather spend money on a company
3185 in Iceland. Another nice recipe is available from the article
3186 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
3187 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
3188 Admin magazine. When the provider is picked, figure out how to get
3189 the API key needed to connect to the storage API. With Greencloud,
3190 the key did not show up until I had added payment details to my
3191 account.&lt;/p&gt;
3192
3193 &lt;p&gt;Armed with the API access details, it is time to create the file
3194 system. First, create a new bucket in the cloud. This bucket is the
3195 file system storage area. I picked a bucket name reflecting the
3196 machine that was going to store data there, but any name will do.
3197 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
3198 the API login and password, and a locally created password. Store it
3199 all in ~root/.s3ql/authinfo2 like this:
3200
3201 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3202 [s3c]
3203 storage-url: s3c://s.greenqloud.com:443/bucket-name
3204 backend-login: API-login
3205 backend-password: API-password
3206 fs-passphrase: local-password
3207 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3208
3209 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
3210 but any sensible way to create a fairly random password should do it.
3211 Armed with these details, it is now time to run mkfs, entering the API
3212 details and password to create it:&lt;/p&gt;
3213
3214 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3215 # mkdir -m 700 /var/lib/s3ql-cache
3216 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3217 --ssl s3c://s.greenqloud.com:443/bucket-name
3218 Enter backend login:
3219 Enter backend password:
3220 Before using S3QL, make sure to read the user&#39;s guide, especially
3221 the &#39;Important Rules to Avoid Loosing Data&#39; section.
3222 Enter encryption password:
3223 Confirm encryption password:
3224 Generating random encryption key...
3225 Creating metadata tables...
3226 Dumping metadata...
3227 ..objects..
3228 ..blocks..
3229 ..inodes..
3230 ..inode_blocks..
3231 ..symlink_targets..
3232 ..names..
3233 ..contents..
3234 ..ext_attributes..
3235 Compressing and uploading metadata...
3236 Wrote 0.00 MB of compressed metadata.
3237 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3238
3239 &lt;p&gt;The next step is mounting the file system to make the storage available.
3240
3241 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3242 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3243 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3244 Using 4 upload threads.
3245 Downloading and decompressing metadata...
3246 Reading metadata...
3247 ..objects..
3248 ..blocks..
3249 ..inodes..
3250 ..inode_blocks..
3251 ..symlink_targets..
3252 ..names..
3253 ..contents..
3254 ..ext_attributes..
3255 Mounting filesystem...
3256 # df -h /s3ql
3257 Filesystem Size Used Avail Use% Mounted on
3258 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
3259 #
3260 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3261
3262 &lt;p&gt;The file system is now ready for use. I use rsync to store my
3263 backups in it, and as the metadata used by rsync is downloaded at
3264 mount time, no network traffic (and storage cost) is triggered by
3265 running rsync. To unmount, one should not use the normal umount
3266 command, as this will not flush the cache to the cloud storage, but
3267 instead running the umount.s3ql command like this:
3268
3269 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3270 # umount.s3ql /s3ql
3271 #
3272 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3273
3274 &lt;p&gt;There is a fsck command available to check the file system and
3275 correct any problems detected. This can be used if the local server
3276 crashes while the file system is mounted, to reset the &quot;already
3277 mounted&quot; flag. This is what it look like when processing a working
3278 file system:&lt;/p&gt;
3279
3280 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3281 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
3282 Using cached metadata.
3283 File system seems clean, checking anyway.
3284 Checking DB integrity...
3285 Creating temporary extra indices...
3286 Checking lost+found...
3287 Checking cached objects...
3288 Checking names (refcounts)...
3289 Checking contents (names)...
3290 Checking contents (inodes)...
3291 Checking contents (parent inodes)...
3292 Checking objects (reference counts)...
3293 Checking objects (backend)...
3294 ..processed 5000 objects so far..
3295 ..processed 10000 objects so far..
3296 ..processed 15000 objects so far..
3297 Checking objects (sizes)...
3298 Checking blocks (referenced objects)...
3299 Checking blocks (refcounts)...
3300 Checking inode-block mapping (blocks)...
3301 Checking inode-block mapping (inodes)...
3302 Checking inodes (refcounts)...
3303 Checking inodes (sizes)...
3304 Checking extended attributes (names)...
3305 Checking extended attributes (inodes)...
3306 Checking symlinks (inodes)...
3307 Checking directory reachability...
3308 Checking unix conventions...
3309 Checking referential integrity...
3310 Dropping temporary indices...
3311 Backing up old metadata...
3312 Dumping metadata...
3313 ..objects..
3314 ..blocks..
3315 ..inodes..
3316 ..inode_blocks..
3317 ..symlink_targets..
3318 ..names..
3319 ..contents..
3320 ..ext_attributes..
3321 Compressing and uploading metadata...
3322 Wrote 0.89 MB of compressed metadata.
3323 #
3324 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3325
3326 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
3327 quick, about the same speed as local file access. Uploading large
3328 amount of data is to me limited by the bandwidth out of and into my
3329 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
3330 which is very close to my upload speed, and downloading the same
3331 Debian installation ISO gave me 610 kiB/s, close to my download speed.
3332 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
3333 network, not the file system code. I do not know what a good cache
3334 size would be, but suspect that the cache should e larger than your
3335 working set.&lt;/p&gt;
3336
3337 &lt;p&gt;I mentioned that only one machine can mount the file system at the
3338 time. If another machine try, it is told that the file system is
3339 busy:&lt;/p&gt;
3340
3341 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3342 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3343 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3344 Using 8 upload threads.
3345 Backend reports that fs is still mounted elsewhere, aborting.
3346 #
3347 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3348
3349 &lt;p&gt;The file content is uploaded when the cache is full, while the
3350 metadata is uploaded once every 24 hour by default. To ensure the
3351 file system content is flushed to the cloud, one can either umount the
3352 file system, or ask S3QL to flush the cache and metadata using
3353 s3qlctrl:
3354
3355 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3356 # s3qlctrl upload-meta /s3ql
3357 # s3qlctrl flushcache /s3ql
3358 #
3359 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3360
3361 &lt;p&gt;If you are curious about how much space your data uses in the
3362 cloud, and how much compression and deduplication cut down on the
3363 storage usage, you can use s3qlstat on the mounted file system to get
3364 a report:&lt;/p&gt;
3365
3366 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3367 # s3qlstat /s3ql
3368 Directory entries: 9141
3369 Inodes: 9143
3370 Data blocks: 8851
3371 Total data size: 22049.38 MB
3372 After de-duplication: 21955.46 MB (99.57% of total)
3373 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
3374 Database size: 2.39 MB (uncompressed)
3375 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3376 #
3377 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3378
3379 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
3380 storage. I did not try to locate them all, but am aware of at least
3381 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
3382 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
3383 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
3384 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
3385 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
3386 accept payment in Bitcoin. Pick one that suit your need. Some of
3387 them provide several GiB of free storage, but the prize models are
3388 quite different and you will have to figure out what suits you
3389 best.&lt;/p&gt;
3390
3391 &lt;p&gt;While researching this blog post, I had a look at research papers
3392 and posters discussing the S3QL file system. There are several, which
3393 told me that the file system is getting a critical check by the
3394 science community and increased my confidence in using it. One nice
3395 poster is titled
3396 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
3397 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3398 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
3399 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3400 and Pamela Smith. Please have a look.&lt;/p&gt;
3401
3402 &lt;p&gt;Given my problems with different file systems earlier, I decided to
3403 check out the mounted S3QL file system to see if it would be usable as
3404 a home directory (in other word, that it provided POSIX semantics when
3405 it come to locking and umask handling etc). Running
3406 &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
3407 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
3408 no error was found. So the file system can be used for home
3409 directories, if one chooses to do so.&lt;/p&gt;
3410
3411 &lt;p&gt;If you do not want a locally file system, and want something that
3412 work without the Linux fuse file system, I would like to mention the
3413 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
3414 provide locally encrypted backup using a command line client. It have
3415 a nicer access control system, where one can split out read and write
3416 access, allowing some systems to write to the backup and others to
3417 only read from it.&lt;/p&gt;
3418
3419 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3420 activities, please send Bitcoin donations to my address
3421 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3422 </description>
3423 </item>
3424
3425 <item>
3426 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
3427 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
3428 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
3429 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
3430 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3431 project&lt;/a&gt; is working on providing the software and hardware for
3432 making it easy for non-technical people to host their data and
3433 communication at home, and being able to communicate with their
3434 friends and family encrypted and away from prying eyes. It has been
3435 going on for a while, and is slowly progressing towards a new test
3436 release (0.2).&lt;/p&gt;
3437
3438 &lt;p&gt;And what day could be better than the Pi day to announce that the
3439 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
3440 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3441 system), and can also be installed using a Debian installer preseed
3442 file. The Debian based Freedombox is now based on Debian Jessie,
3443 where most of the needed packages used are already present. Only one,
3444 the freedombox-setup package, is missing. To try to build your own
3445 boot image to test the current status, fetch the freedom-maker scripts
3446 and build using
3447 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
3448 with a user with sudo access to become root:
3449
3450 &lt;pre&gt;
3451 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3452 freedom-maker
3453 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3454 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3455 u-boot-tools
3456 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3457 &lt;/pre&gt;
3458
3459 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3460 devices. See the README for more details on the build. If you do not
3461 want all three images, trim the make line. But note that thanks to &lt;a
3462 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
3463 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
3464 kpartx call.&lt;/p&gt;
3465
3466 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3467 method, boot a Debian Wheezy ISO and use this boot argument to load
3468 the preseed values:&lt;/p&gt;
3469
3470 &lt;pre&gt;
3471 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;
3472 &lt;/pre&gt;
3473
3474 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
3475 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
3476 currently hang while setting up APT sources. Killing the
3477 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
3478 installation will get the installation going. This affect all
3479 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
3480
3481 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3482 us get the new release published. :) Please join us on
3483 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3484 irc.debian.org)&lt;/a&gt; and
3485 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3486 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3487 </description>
3488 </item>
3489
3490 <item>
3491 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
3492 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
3493 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
3494 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
3495 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
3496 innetgr tools, because I needed them in
3497 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
3498 ng-utils, and it has served me well. I placed the project under the
3499 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
3500 repository. But many years ago, the CVS repository was dropped (lost,
3501 not migrated to new hardware, not sure), and the project have lacked a
3502 proper home since then.&lt;/p&gt;
3503
3504 &lt;p&gt;Last summer, I had a look at the package and made a new release
3505 fixing a irritating crash bug, but was unable to store the changes in
3506 a proper source control system. I applied for a project on
3507 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
3508 to follow up on it. Until today. :)&lt;/p&gt;
3509
3510 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
3511 now have a new home, and a git repository with the highlight of the
3512 history of the project. I published all release tarballs and imported
3513 them into the git repository. As the project is really stable and not
3514 expected to gain new features any time soon, I decided to make a new
3515 release and call it 1.0. Visit the new project home on
3516 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
3517 if you want to check it out. The new version is also uploaded into
3518 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
3519 </description>
3520 </item>
3521
3522 <item>
3523 <title>Testing sysvinit from experimental in Debian Hurd</title>
3524 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
3525 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
3526 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
3527 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
3528 their changes into sysvinit, to allow them to use the normal sysvinit
3529 boot system instead of their old one. This follow up on the
3530 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
3531 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
3532 get Debian on Hurd working more like Debian on Linux. To get started,
3533 I downloaded a prebuilt hard disk image from
3534 &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;,
3535 and started it using virt-manager.&lt;/p&gt;
3536
3537 &lt;p&gt;The first think I had to do after logging in (root without any
3538 password) was to get the network operational. I followed
3539 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
3540 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
3541 commands as root to get the machine to accept a IP address from the
3542 kvm internal DHCP server:&lt;/p&gt;
3543
3544 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3545 settrans -fgap /dev/netdde /hurd/netdde
3546 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
3547 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
3548 dhclient /dev/eth0
3549 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3550
3551 &lt;p&gt;After this, the machine had internet connectivity, and I could
3552 upgrade it and install the sysvinit packages from experimental and
3553 enable it as the default boot system in Hurd.&lt;/p&gt;
3554
3555 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
3556 running on the machine it for ssh login to work a password need to be
3557 set. Also, note that a bug somewhere in openssh on Hurd block
3558 compression from working. Remember to turn that off on the client
3559 side.&lt;/p&gt;
3560
3561 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
3562 stuff:&lt;/p&gt;
3563
3564 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3565 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
3566 deb http://http.debian.net/debian/ experimental main
3567 EOF
3568 apt-get update
3569 apt-get dist-upgrade
3570 apt-get install -t experimental initscripts sysv-rc sysvinit \
3571 sysvinit-core sysvinit-utils
3572 update-alternatives --config runsystem
3573 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3574
3575 &lt;p&gt;To reboot after switching boot system, you have to use
3576 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
3577 yet a sysvinit process able to receive the signals from the normal
3578 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
3579 upgrading every package and rebooting, the network come up with DHCP
3580 after boot as it should, and the settrans/pkill hack mentioned at the
3581 start is no longer needed. But for some strange reason, there are no
3582 longer any login prompt in the virtual console, so I logged in using
3583 ssh instead.
3584
3585 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
3586 fail some times. No idea what the cause is, but hope the Hurd porters
3587 figure it out. At least Justus said on IRC (#debian-hurd on
3588 irc.debian.org) that they are aware of the problem. A way to reduce
3589 the impact is to upgrade to the Hurd packages built by Justus by
3590 adding this repository to the machine:&lt;/p&gt;
3591
3592 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3593 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
3594 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3595 EOF
3596 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3597
3598 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
3599 http://ftp.debian-ports.org/debian, because some of the packages in
3600 unstable do not yet include the required patches that are lingering in
3601 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
3602
3603 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3604 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
3605 i emacs - GNU Emacs editor (metapackage)
3606 i gdb - GNU Debugger
3607 i hurd-recommended - Miscellaneous translators
3608 i isc-dhcp-client - ISC DHCP client
3609 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3610 i libc-bin - Embedded GNU C Library: Binaries
3611 i libc-dev-bin - Embedded GNU C Library: Development binaries
3612 i libc0.3 - Embedded GNU C Library: Shared libraries
3613 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3614 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3615 i multiarch-support - Transitional package to ensure multiarch compatibilit
3616 i A x11-common - X Window System (X.Org) infrastructure
3617 i xorg - X.Org X Window System
3618 i A xserver-xorg - X.Org X server
3619 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3620 #
3621 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3622
3623 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
3624 X.org did not work out of the box and I never took the time to follow
3625 the porters instructions to fix it. This time I was interested in the
3626 command line stuff.&lt;p&gt;
3627 </description>
3628 </item>
3629
3630 <item>
3631 <title>New chrpath release 0.16</title>
3632 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
3633 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
3634 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
3635 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
3636 find problems in C, C++ and Java code using static source code
3637 analysis. It can detect a lot of different problems, and is very
3638 useful to find memory and locking bugs in the error handling part of
3639 the source. The company behind it provide
3640 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
3641 a community service&lt;/a&gt;, and many hundred free software projects are
3642 already checked. A few days ago I decided to have a closer look at
3643 the Coverity system, and discovered that the
3644 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
3645 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
3646 projects I am involved with was already registered. But these are
3647 fairly big, and I would also like to have a small and easy project to
3648 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
3649 checking of the chrpath project&lt;/a&gt;. It was
3650 added to the checker and discovered seven potential defects. Six of
3651 these were real, mostly resource &quot;leak&quot; when the program detected an
3652 error. Nothing serious, as the resources would be released a fraction
3653 of a second later when the program exited because of the error, but it
3654 is nice to do it right in case the source of the program some time in
3655 the future end up in a library. Having fixed all defects and added
3656 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
3657 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
3658 publish a new release. These are the release notes:&lt;/p&gt;
3659
3660 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
3661
3662 &lt;ul&gt;
3663
3664 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
3665 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
3666 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
3667
3668 &lt;/ul&gt;
3669
3670 &lt;p&gt;You can
3671 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
3672 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
3673 project if something is wrong with the new release. The test suite
3674 did not discover any old errors, so if you find a new one, please also
3675 include a test suite check.&lt;/p&gt;
3676 </description>
3677 </item>
3678
3679 <item>
3680 <title>New chrpath release 0.15</title>
3681 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
3682 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
3683 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
3684 <description>&lt;p&gt;After many years break from the package and a vain hope that
3685 development would be continued by someone else, I finally pulled my
3686 acts together this morning and wrapped up a new release of chrpath,
3687 the command line tool to modify the rpath and runpath of already
3688 compiled ELF programs. The update was triggered by the persistence of
3689 Isha Vishnoi at IBM, which needed a new config.guess file to get
3690 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
3691 is working on. I checked the
3692 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
3693 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
3694 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
3695 packages for interesting patches (failed to find the source from
3696 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3697 These are the release notes:&lt;/p&gt;
3698
3699 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
3700
3701 &lt;ul&gt;
3702
3703 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
3704 with newer architectures. Thanks to isha vishnoi for the heads
3705 up.&lt;/li&gt;
3706
3707 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
3708
3709 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3710 Matthias Klose.&lt;/li&gt;
3711
3712 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
3713 Petr Machata found in Fedora.&lt;/li&gt;
3714
3715 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
3716 .dynamic is a NULL terminated string. Based on patch found in
3717 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
3718
3719 &lt;/ul&gt;
3720
3721 &lt;p&gt;You can
3722 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
3723 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
3724 project if something is wrong with the new release. The test suite
3725 did not discover any old errors, so if you find a new one, please also
3726 include a testsuite check.&lt;/p&gt;
3727 </description>
3728 </item>
3729
3730 <item>
3731 <title>Debian init.d boot script example for rsyslog</title>
3732 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
3733 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
3734 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
3735 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
3736 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
3737 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
3738 init.d scripts at all. Here is an example init.d script, ie a rewrite
3739 of /etc/init.d/rsyslog:&lt;/p&gt;
3740
3741 &lt;p&gt;&lt;pre&gt;
3742 #!/lib/init/init-d-script
3743 ### BEGIN INIT INFO
3744 # Provides: rsyslog
3745 # Required-Start: $remote_fs $time
3746 # Required-Stop: umountnfs $time
3747 # X-Stop-After: sendsigs
3748 # Default-Start: 2 3 4 5
3749 # Default-Stop: 0 1 6
3750 # Short-Description: enhanced syslogd
3751 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3752 # It is quite compatible to stock sysklogd and can be
3753 # used as a drop-in replacement.
3754 ### END INIT INFO
3755 DESC=&quot;enhanced syslogd&quot;
3756 DAEMON=/usr/sbin/rsyslogd
3757 &lt;/pre&gt;&lt;/p&gt;
3758
3759 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
3760 script was 137 lines, and the above is just 15 lines, most of it meta
3761 info/comments.&lt;/p&gt;
3762
3763 &lt;p&gt;How to do this, you ask? Well, one create a new script
3764 /lib/init/init-d-script looking something like this:
3765
3766 &lt;p&gt;&lt;pre&gt;
3767 #!/bin/sh
3768
3769 # Define LSB log_* functions.
3770 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
3771 # and status_of_proc is working.
3772 . /lib/lsb/init-functions
3773
3774 #
3775 # Function that starts the daemon/service
3776
3777 #
3778 do_start()
3779 {
3780 # Return
3781 # 0 if daemon has been started
3782 # 1 if daemon was already running
3783 # 2 if daemon could not be started
3784 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
3785 || return 1
3786 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3787 $DAEMON_ARGS \
3788 || return 2
3789 # Add code here, if necessary, that waits for the process to be ready
3790 # to handle requests from services started subsequently which depend
3791 # on this one. As a last resort, sleep for some time.
3792 }
3793
3794 #
3795 # Function that stops the daemon/service
3796 #
3797 do_stop()
3798 {
3799 # Return
3800 # 0 if daemon has been stopped
3801 # 1 if daemon was already stopped
3802 # 2 if daemon could not be stopped
3803 # other if a failure occurred
3804 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
3805 RETVAL=&quot;$?&quot;
3806 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
3807 # Wait for children to finish too if this is a daemon that forks
3808 # and if the daemon is only ever run from this initscript.
3809 # If the above conditions are not satisfied then add some other code
3810 # that waits for the process to drop all resources that could be
3811 # needed by services started subsequently. A last resort is to
3812 # sleep for some time.
3813 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
3814 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
3815 # Many daemons don&#39;t delete their pidfiles when they exit.
3816 rm -f $PIDFILE
3817 return &quot;$RETVAL&quot;
3818 }
3819
3820 #
3821 # Function that sends a SIGHUP to the daemon/service
3822 #
3823 do_reload() {
3824 #
3825 # If the daemon can reload its configuration without
3826 # restarting (for example, when it is sent a SIGHUP),
3827 # then implement that here.
3828 #
3829 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
3830 return 0
3831 }
3832
3833 SCRIPTNAME=$1
3834 scriptbasename=&quot;$(basename $1)&quot;
3835 echo &quot;SN: $scriptbasename&quot;
3836 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
3837 script=&quot;$1&quot;
3838 shift
3839 . $script
3840 else
3841 exit 0
3842 fi
3843
3844 NAME=$(basename $DAEMON)
3845 PIDFILE=/var/run/$NAME.pid
3846
3847 # Exit if the package is not installed
3848 #[ -x &quot;$DAEMON&quot; ] || exit 0
3849
3850 # Read configuration variable file if it is present
3851 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
3852
3853 # Load the VERBOSE setting and other rcS variables
3854 . /lib/init/vars.sh
3855
3856 case &quot;$1&quot; in
3857 start)
3858 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
3859 do_start
3860 case &quot;$?&quot; in
3861 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
3862 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
3863 esac
3864 ;;
3865 stop)
3866 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
3867 do_stop
3868 case &quot;$?&quot; in
3869 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
3870 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
3871 esac
3872 ;;
3873 status)
3874 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
3875 ;;
3876 #reload|force-reload)
3877 #
3878 # If do_reload() is not implemented then leave this commented out
3879 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
3880 #
3881 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
3882 #do_reload
3883 #log_end_msg $?
3884 #;;
3885 restart|force-reload)
3886 #
3887 # If the &quot;reload&quot; option is implemented then remove the
3888 # &#39;force-reload&#39; alias
3889 #
3890 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
3891 do_stop
3892 case &quot;$?&quot; in
3893 0|1)
3894 do_start
3895 case &quot;$?&quot; in
3896 0) log_end_msg 0 ;;
3897 1) log_end_msg 1 ;; # Old process is still running
3898 *) log_end_msg 1 ;; # Failed to start
3899 esac
3900 ;;
3901 *)
3902 # Failed to stop
3903 log_end_msg 1
3904 ;;
3905 esac
3906 ;;
3907 *)
3908 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
3909 exit 3
3910 ;;
3911 esac
3912
3913 :
3914 &lt;/pre&gt;&lt;/p&gt;
3915
3916 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
3917 lot. I did not really polish the approach, so it might not always
3918 work out of the box, but you get the idea. I did not try very hard to
3919 optimize it nor make it more robust either.&lt;/p&gt;
3920
3921 &lt;p&gt;A better argument for switching init system in Debian than reducing
3922 the size of init scripts (which is a good thing to do anyway), is to
3923 get boot system that is able to handle the kernel events sensibly and
3924 robustly, and do not depend on the boot to run sequentially. The boot
3925 and the kernel have not behaved sequentially in years.&lt;/p&gt;
3926 </description>
3927 </item>
3928
3929 <item>
3930 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
3931 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
3932 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
3933 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
3934 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
3935 remote display access is the preferred solution with oVirt and RedHat
3936 Enterprise Virtualization, and I was sad to discover the other day
3937 that the browser plugin needed to use these systems seamlessly was
3938 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
3939 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
3940 2013-04-01, so I decided to wrap up a package based on the great work
3941 from Cajus Pollmeier and put it in a collab-maint maintained git
3942 repository to get a package I could use. I would very much like
3943 others to help me maintain the package (or just take over, I do not
3944 mind), but as no-one had volunteered so far, I just uploaded it to
3945 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
3946
3947 &lt;p&gt;The source is now available from
3948 &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;
3949 </description>
3950 </item>
3951
3952 <item>
3953 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
3954 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
3955 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
3956 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
3957 <description>&lt;p&gt;The
3958 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
3959 program is a a very nice system to create virtual machine images. It
3960 create a image file, add a partition table, mount it and run
3961 debootstrap in the mounted directory to create a Debian system on a
3962 stick. Yesterday, I decided to try to teach it how to make images for
3963 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
3964 of a plan to simplify the build system for
3965 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
3966 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
3967 the virtualbox images, but its current build system made multistrap
3968 based system for Dreamplug images, and it is lacking support for
3969 Raspberry Pi.&lt;/p&gt;
3970
3971 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
3972 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3973 code and adjusted it to be able to build armel images on my amd64
3974 Debian laptop. I ended up giving vmdebootstrap five new options,
3975 allowing me to replicate the image creation process I use to make
3976 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
3977 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
3978 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
3979 call debootstrap with --foreign and to copy the handler into the
3980 generated chroot before running the second stage. This allow
3981 vmdebootstrap to create armel images on an amd64 host. Next I added
3982 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
3983 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
3984 given file system type, allowing me to create an image with a vfat
3985 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
3986 variant&lt;/tt&gt; option to allow me to create smaller images without the
3987 Debian base system packages installed. Finally, I added an option
3988 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
3989 as a boot loader. It is not needed on the Raspberry Pi and probably
3990 most other non-x86 architectures. The changes were accepted by the
3991 upstream author of vmdebootstrap yesterday and today, and is now
3992 available from
3993 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
3994 upstream project page&lt;/a&gt;.&lt;/p&gt;
3995
3996 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
3997 create a small script (the customize script) to add the non-free
3998 binary blob needed to boot the Raspberry Pi and the APT source
3999 list:&lt;/p&gt;
4000
4001 &lt;p&gt;&lt;pre&gt;
4002 #!/bin/sh
4003 set -e # Exit on first error
4004 rootdir=&quot;$1&quot;
4005 cd &quot;$rootdir&quot;
4006 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
4007 deb http://http.debian.net/debian/ jessie main contrib non-free
4008 EOF
4009 # Install non-free binary blob needed to boot Raspberry Pi. This
4010 # install a kernel somewhere too.
4011 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4012 -O $rootdir/usr/bin/rpi-update
4013 chmod a+x $rootdir/usr/bin/rpi-update
4014 mkdir -p $rootdir/lib/modules
4015 touch $rootdir/boot/start.elf
4016 chroot $rootdir rpi-update
4017 &lt;/pre&gt;&lt;/p&gt;
4018
4019 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
4020 to build the image:&lt;/p&gt;
4021
4022 &lt;pre&gt;
4023 sudo ./vmdebootstrap \
4024 --variant minbase \
4025 --arch armel \
4026 --distribution jessie \
4027 --mirror http://http.debian.net/debian \
4028 --image test.img \
4029 --size 600M \
4030 --bootsize 64M \
4031 --boottype vfat \
4032 --log-level debug \
4033 --verbose \
4034 --no-kernel \
4035 --no-extlinux \
4036 --root-password raspberry \
4037 --hostname raspberrypi \
4038 --foreign /usr/bin/qemu-arm-static \
4039 --customize `pwd`/customize \
4040 --package netbase \
4041 --package git-core \
4042 --package binutils \
4043 --package ca-certificates \
4044 --package wget \
4045 --package kmod
4046 &lt;/pre&gt;&lt;/p&gt;
4047
4048 &lt;p&gt;The list of packages being installed are the ones needed by
4049 rpi-update to make the image bootable on the Raspberry Pi, with the
4050 exception of netbase, which is needed by debootstrap to find
4051 /etc/hosts with the minbase variant. I really wish there was a way to
4052 set up an Raspberry Pi using only packages in the Debian archive, but
4053 that is not possible as far as I know, because it boots from the GPU
4054 using a non-free binary blob.&lt;/p&gt;
4055
4056 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
4057 probably a few others installed. I have not checked the complete
4058 build dependency list.&lt;/p&gt;
4059
4060 &lt;p&gt;The resulting image will not use the hardware floating point unit
4061 on the Raspberry PI, because the armel architecture in Debian is not
4062 optimized for that use. So the images created will be a bit slower
4063 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
4064 </description>
4065 </item>
4066
4067 <item>
4068 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
4069 <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>
4070 <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>
4071 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
4072 <description>&lt;p&gt;The last few days I came across a few good causes that should get
4073 wider attention. I recommend signing and donating to each one of
4074 these. :)&lt;/p&gt;
4075
4076 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
4077 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
4078 Women program which is a Google Summer of Code like initiative to get
4079 more women involved in free software. One debian sponsor has offered
4080 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
4081 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
4082 hope you will to. :)&lt;/p&gt;
4083
4084 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
4085 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
4086 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
4087 take place these days, and their need to fund the work. I&#39;ve already
4088 donated. Are you next?&lt;/p&gt;
4089
4090 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
4091 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4092 statement under the heading
4093 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
4094 Access&lt;/a&gt; for those of us asking for more focus on open access in the
4095 Norwegian government. So far 499 signatures. I hope you will sign it
4096 too.&lt;/p&gt;
4097 </description>
4098 </item>
4099
4100 <item>
4101 <title>Videos about the Freedombox project - for inspiration and learning</title>
4102 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
4103 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
4104 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
4105 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
4106 project&lt;/a&gt; have been going on for a while, and have presented the
4107 vision, ideas and solution several places. Here is a little
4108 collection of videos of talks and presentation of the project.&lt;/p&gt;
4109
4110 &lt;ul&gt;
4111
4112 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
4113 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
4114
4115 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
4116 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4117
4118 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
4119 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4120 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
4121 (Youtube)&lt;/li&gt;
4122
4123 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
4124 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
4125
4126 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
4127 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4128
4129 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
4130 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4131 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
4132
4133 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
4134 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
4135 (Youtube)&lt;/li&gt;
4136
4137 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
4138 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
4139
4140 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
4141 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
4142
4143 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
4144 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4145 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
4146
4147 &lt;/ul&gt;
4148
4149 &lt;p&gt;A larger list is available from
4150 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
4151 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
4152
4153 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
4154 Jessie is coming along quite well, and soon both Owncloud and using
4155 Tor should be available for testers of the Freedombox solution. :) In
4156 a few weeks I hope everything needed to test it is included in Debian.
4157 The withsqlite package is already in Debian, and the plinth package is
4158 pending in NEW. The third and vital part of that puzzle is the
4159 metapackage/setup framework, which is still pending an upload. Join
4160 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
4161 (#freedombox on irc.debian.org)&lt;/a&gt; and
4162 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4163 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4164 </description>
4165 </item>
4166
4167 <item>
4168 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
4169 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
4170 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
4171 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
4172 <description>&lt;p&gt;I was introduced to the
4173 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
4174 in 2010, when Eben Moglen presented his vision about serving the need
4175 of non-technical people to keep their personal information private and
4176 within the legal protection of their own homes. The idea is to give
4177 people back the power over their network and machines, and return
4178 Internet back to its intended peer-to-peer architecture. Instead of
4179 depending on a central service, the Freedombox will give everyone
4180 control over their own basic infrastructure.&lt;/p&gt;
4181
4182 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
4183 taken priority. But this summers nasty news about the misuse of trust
4184 and privilege exercised by the &quot;western&quot; intelligence gathering
4185 communities increased my eagerness to contribute to a point where I
4186 actually started working on the project a while back.&lt;/p&gt;
4187
4188 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
4189 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
4190 create a simple and cheap Debian based appliance that anyone can hook
4191 up in their home and get access to secure and private services and
4192 communication. The initial deployment platform have been the
4193 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
4194 which is a piece of hardware I do not own. So to be able to test what
4195 the current Freedombox setup look like, I had to come up with a way to install
4196 it on some hardware I do have access to. I have rewritten the
4197 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
4198 image build framework to use .deb packages instead of only copying
4199 setup into the boot images, and thanks to this rewrite I am able to
4200 set up any machine supported by Debian Wheezy as a Freedombox, using
4201 the previously mentioned deb (and a few support debs for packages
4202 missing in Debian).&lt;/p&gt;
4203
4204 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
4205 scripts
4206 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
4207 and a administrative web interface
4208 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
4209 withsqlite), as well as a privacy enhancing proxy based on
4210 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
4211 (freedombox-privoxy). There is also a web/javascript based XMPP
4212 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
4213 trying (unsuccessfully so far) to talk to the XMPP server
4214 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
4215 web interface is pluggable, and the goal is to use it to enable OpenID
4216 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4217 this is really working yet, see
4218 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
4219 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
4220 on github at the moment. The HTTP proxy is operational out of the
4221 box, and the admin web interface can be used to add/remove plinth
4222 users. I&#39;ve not been able to do anything else with it so far, but
4223 know there are several branches spread around github and other places
4224 with lots of half baked features.&lt;/p&gt;
4225
4226 &lt;p&gt;Anyway, if you want to have a look at the current state, the
4227 following recipes should work to give you a test machine to poke
4228 at.&lt;/p&gt;
4229
4230 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
4231
4232 &lt;ol&gt;
4233
4234 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
4235 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
4236 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
4237 to the Debian installer:&lt;p&gt;
4238 &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;
4239
4240 &lt;li&gt;Answer the few language/region/password questions and pick disk to
4241 install on.&lt;/li&gt;
4242
4243 &lt;li&gt;When the installation is finished and the machine have rebooted a
4244 few times, your Freedombox is ready for testing.&lt;/li&gt;
4245
4246 &lt;/ol&gt;
4247
4248 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
4249
4250 &lt;ol&gt;
4251
4252 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
4253 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
4254 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
4255 &lt;pre&gt;
4256 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
4257 &lt;/pre&gt;&lt;/li&gt;
4258 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
4259 &lt;pre&gt;
4260 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4261 apt-key add -
4262 apt-get update
4263 apt-get install freedombox-setup
4264 /usr/lib/freedombox/setup
4265 &lt;/pre&gt;&lt;/li&gt;
4266 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
4267
4268 &lt;/ol&gt;
4269
4270 &lt;p&gt;You can test it on other architectures too, but because the
4271 freedombox-privoxy package is binary, it will only work as intended on
4272 the architectures where I have had time to build the binary and put it
4273 in my APT repository. But do not let this stop you. It is only a
4274 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
4275
4276 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
4277 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
4278 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
4279 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
4280
4281 &lt;p&gt;Please let me know if this works for you, or if you have any
4282 problems. We gather on the IRC channel
4283 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
4284 irc.debian.org and the
4285 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
4286 mailing list&lt;/a&gt;.&lt;/p&gt;
4287
4288 &lt;p&gt;Once you get your freedombox operational, you can visit
4289 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
4290 welcome screen (dead end - do not be surprised if you are unable to
4291 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
4292 to look at the rest of plinth. The default user is &#39;admin&#39; and the
4293 default password is &#39;secret&#39;.&lt;/p&gt;
4294 </description>
4295 </item>
4296
4297 <item>
4298 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
4299 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
4300 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
4301 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
4302 <description>&lt;p&gt;Earlier, I reported about
4303 &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
4304 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
4305 told by IBM that the original disk should be thrown away. And as
4306 there no longer was a problem if I bricked the firmware, I decided
4307 today to try to install Intel firmware to replace the Lenovo firmware
4308 currently on the disk.&lt;/p&gt;
4309
4310 &lt;p&gt;I searched the Intel site for firmware, and found
4311 &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;
4312 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4313 according to the site should contain the latest firmware for SSD
4314 disks. I inserted the broken disk in one of my spare laptops and
4315 booted the ISO from a USB stick. The disk was recognized, but the
4316 program claimed the newest firmware already were installed and refused
4317 to insert any Intel firmware. So no change, and the disk is still
4318 unable to handle write load. :( I guess the only way to get them
4319 working would be if Lenovo releases new firmware. No idea how likely
4320 that is. Anyway, just blogging about this test for completeness. I
4321 got a working Samsung disk, and see no point in spending more time on
4322 the broken disks.&lt;/p&gt;
4323 </description>
4324 </item>
4325
4326 <item>
4327 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
4328 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
4329 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
4330 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
4331 <description>&lt;p&gt;Today I switched to
4332 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
4333 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
4334 my new Thinkpad X230, which was delivered with an
4335 &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
4336 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
4337 sustained writes. My hardware supplier have been very forthcoming in
4338 trying to find a solution, and after first trying with another
4339 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
4340 disk instead to fix it once and for all. The Samsung disk survived
4341 the installation of Debian with encrypted disks (filling the disk with
4342 random data during installation killed the first two), and I thus
4343 decided to trust it with my data. I have installed it as a Debian Edu
4344 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4345 server at home using Kerberos and LDAP, and will use it as my work
4346 station from now on.&lt;/p&gt;
4347
4348 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
4349 Debian Wheezy default installation need to be tuned a bit to increase
4350 performance and increase life time of the disk. The Linux kernel and
4351 user space applications do not yet adjust automatically to such
4352 environment. To make it easier for my self, I created a draft Debian
4353 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
4354 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
4355 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
4356 is set up to adjust the setup of the machine by just installing the
4357 package. If there is any non-SSD disk in the machine, the package
4358 will refuse to install, as I did not try to write any logic to sort
4359 file systems in SSD and non-SSD file systems.&lt;/p&gt;
4360
4361 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
4362 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4363 where I set up the machine with one large encrypted partition (in
4364 addition to /boot), put LVM on top of this and set up partitions on
4365 top of this again. See the README file in the package source for the
4366 references I used to pick the settings. At the moment these
4367 parameters are tuned:&lt;/p&gt;
4368
4369 &lt;ul&gt;
4370
4371 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
4372 (adding discard to /etc/crypttab)&lt;/li&gt;
4373
4374 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
4375 this case a cryptsetup partition) by changing issue_discards from
4376 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
4377
4378 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
4379 systems.&lt;/li&gt;
4380
4381 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
4382 /etc/fstab.&lt;/li&gt;
4383
4384 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
4385
4386 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
4387 cron.daily).&lt;/li&gt;
4388
4389 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
4390 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
4391
4392 &lt;/ul&gt;
4393
4394 &lt;p&gt;During installation, I cancelled the part where the installer fill
4395 the disk with random data, as this would kill the SSD performance for
4396 little gain. My goal with the encrypted file system is to ensure
4397 those stealing my laptop end up with a brick and not a working
4398 computer. I have no hope in keeping the really resourceful people
4399 from getting the data on the disk (see
4400 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
4401 Thus I concluded that adding the discard option to crypttab is the
4402 right thing to do.&lt;/p&gt;
4403
4404 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
4405 it for SSD, but others recommended deadline and a benchmark I found
4406 indicated that deadline might be better for interactive use.&lt;/p&gt;
4407
4408 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
4409 and ext4, but read that it would give a performance hit ever time a
4410 file is removed, and thought it best to that that slowdown once a day
4411 instead of during my work.&lt;/p&gt;
4412
4413 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4414 this is already done by Debian Edu.&lt;/p&gt;
4415
4416 &lt;p&gt;I have not yet started on the user space tuning. I expect
4417 iceweasel need some tuning, and perhaps other applications too, but
4418 have not yet had time to investigate those parts.&lt;/p&gt;
4419
4420 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
4421 there.&lt;/p&gt;
4422
4423 &lt;p&gt;As for the answer to the question in the title of this blog post,
4424 as far as I know, the only solution I know about is to replace the
4425 disk. It might be possible to flash it with Intel firmware instead of
4426 the Lenovo firmware. But I have not tried and did not want to do so
4427 without approval from Lenovo as I wanted to keep the warranty on the
4428 disk until a solution was found and they wanted the broken disks
4429 back.&lt;/p&gt;
4430 </description>
4431 </item>
4432
4433 <item>
4434 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
4435 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
4436 <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>
4437 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
4438 <description>&lt;p&gt;A few days ago, I wrote about
4439 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
4440 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
4441 was dying during installation because it is unable to cope with
4442 sustained write. My supplier is in contact with
4443 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
4444 replacement disk to try to fix the problem. They decided to send an
4445 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
4446
4447 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
4448 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4449 same firmware version as the original. This time my hope raised
4450 slightly as the installation progressed, as the original disk used to
4451 die after 4-7% of the disk was written to, while this time it kept
4452 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
4453 died again and I was back on square one. I still do not have a new
4454 laptop with a disk I can trust. I can not live with a disk that might
4455 lock up when I download a new
4456 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
4457 other large files. I look forward to hearing from my supplier with
4458 the next proposal from Lenovo.&lt;/p&gt;
4459
4460 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
4461 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4462 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
4463 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
4464 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
4465 P/N 45N8295, P0C38732.&lt;/p&gt;
4466
4467 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
4468 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
4469 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
4470 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
4471 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
4472 P/N 45N8295, P0C38732.&lt;/p&gt;
4473
4474 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
4475 SA, date and WNPP values. Mentioning all the details here in case
4476 someone is able to use the information to find a way to identify the
4477 failing disk among working ones (if any such working disk actually
4478 exist).&lt;/p&gt;
4479 </description>
4480 </item>
4481
4482 <item>
4483 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
4484 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
4485 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
4486 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
4487 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
4488 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4489 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
4490 member assosiation NUUG&lt;/a&gt; and
4491 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
4492 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
4493 Bitraf&lt;/a&gt;.&lt;/p&gt;
4494
4495 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
4496 welcome, and there is no fee to participate. There is on the other
4497 hand limited space, and only room for 30 people. Please put your name
4498 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
4499 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
4500 </description>
4501 </item>
4502
4503 <item>
4504 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
4505 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
4506 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
4507 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
4508 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
4509 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
4510 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
4511 time to spend on it, and it took a while to find a model I believe
4512 will do the job, but two days ago the replacement finally arrived. I
4513 ended up picking a
4514 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
4515 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4516 a roaming workstation, and it seemed to work flawlessly. But my
4517 second installation with encrypted disk was not as successful. More
4518 on that below.&lt;/p&gt;
4519
4520 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4521 important requirements (robust and with a good keyboard) are never
4522 listed in the feature list. But I did get good help from the search
4523 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4524 allowed me to limit the list of interesting laptops based on my other
4525 requirements. A bit surprising that SSD disk are not disks according
4526 to that search interface, so I had to drop specifying the number of
4527 disks from my search parameters. I also asked around among friends to
4528 get their impression on keyboards and robustness.&lt;/p&gt;
4529
4530 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
4531 X41. I am not quite convinced about the keyboard, as it is
4532 significantly wider than my old keyboard, and I have to stretch my
4533 hand a lot more to reach the edges. But the key response is fairly
4534 good and the individual key shape is fairly easy to handle, so I hope
4535 I will get used to it. My old X40 was starting to fail, and I really
4536 needed a new laptop now. :)&lt;/p&gt;
4537
4538 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
4539 visit to the BIOS during boot it disable it.&lt;/p&gt;
4540
4541 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
4542 lock up during load. And this happen when installing Debian Wheezy
4543 with encrypted disk, while the disk is being filled with random data.
4544 I also tested to install Ubuntu Raring, and it happen there too if I
4545 reenable the code to fill the disk with random data (it is disabled by
4546 default in Ubuntu). And the bug with is already known. It was
4547 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
4548 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
4549 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4550 kernel developers as
4551 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
4552 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
4553 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4554 Lenovo forums, both for
4555 &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
4556 2012-11-10&lt;/a&gt; and for
4557 &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
4558 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
4559 reports state that the disk lock up during use if many writes are done
4560 on the disk, so it is much no use to work around the installation
4561 problem and end up with a computer that can lock up at any moment.
4562 There is even a
4563 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
4564 available&lt;/a&gt; that will lock up the hard drive after running a few
4565 minutes by writing to a file.&lt;/p&gt;
4566
4567 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
4568 contacting PCHELP Norway (request 01D1FDP) which handle support
4569 requests for Lenovo, his first suggestion was to upgrade the disk
4570 firmware. Unfortunately there is no newer firmware available from
4571 Lenovo, as my disk already have the most recent one (version LF1i). I
4572 hope to hear more from him today and hope the problem can be
4573 fixed. :)&lt;/p&gt;
4574 </description>
4575 </item>
4576
4577 <item>
4578 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
4579 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
4580 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
4581 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
4582 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
4583 trusty old Thinkpad X41. Unfortunately I did not have much time to
4584 spend on it, but today the replacement finally arrived. I ended up
4585 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
4586 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
4587 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4588 this, it is installing what I hope will be a more final installation,
4589 with a encrypted hard drive to ensure any dope head stealing it end up
4590 with an expencive door stop.&lt;/p&gt;
4591
4592 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4593 important requirements (robust and with a good keyboard) are never
4594 listed in the feature list. But I did get good help from the search
4595 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4596 allowed me to limit the list of interesting laptops based on my other
4597 requirements. A bit surprising that SSD disk are not disks, so I had
4598 to drop number of disks from my search parameters.&lt;/p&gt;
4599
4600 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
4601 wider than my old keyboard, and I have to stretch my hand a lot more
4602 to reach the edges. But the key response is fairly good and the
4603 individual key shape is fairly easy to handle, so I hope I will get
4604 used to it. My old X40 was starting to fail, and I really needed a
4605 new laptop now. :)&lt;/p&gt;
4606
4607 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
4608 </description>
4609 </item>
4610
4611 <item>
4612 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
4613 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
4614 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
4615 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
4616 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
4617 perfectly capable of, and I have to do it manually to get things
4618 working. One such task is to find out what firmware packages are
4619 needed to get the hardware on my computer working. Most often this
4620 affect the wifi card, but some times it even affect the RAID
4621 controller or the ethernet card. Today I pushed version 0.4 of the
4622 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
4623 including a new script isenkram-autoinstall-firmware handling the
4624 process of asking all the loaded kernel modules what firmware files
4625 they want, find debian packages providing these files and install the
4626 debian packages. Here is a test run on my laptop:&lt;/p&gt;
4627
4628 &lt;p&gt;&lt;pre&gt;
4629 # isenkram-autoinstall-firmware
4630 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4631 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4632 info: locating packages with the requested firmware files
4633 info: Updating APT sources after adding non-free APT source
4634 info: trying to install firmware-ipw2x00
4635 firmware-ipw2x00
4636 firmware-ipw2x00
4637 Preconfiguring packages ...
4638 Selecting previously deselected package firmware-ipw2x00.
4639 (Reading database ... 259727 files and directories currently installed.)
4640 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4641 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
4642 #
4643 &lt;/pre&gt;&lt;/p&gt;
4644
4645 &lt;p&gt;When all the requested firmware is present, a simple message is
4646 printed instead:&lt;/p&gt;
4647
4648 &lt;p&gt;&lt;pre&gt;
4649 # isenkram-autoinstall-firmware
4650 info: did not find any firmware files requested by loaded kernel modules. exiting
4651 #
4652 &lt;/pre&gt;&lt;/p&gt;
4653
4654 &lt;p&gt;It could use some polish, but it is already working well and saving
4655 me some time when setting up new machines. :)&lt;/p&gt;
4656
4657 &lt;p&gt;So, how does it work? It look at the set of currently loaded
4658 kernel modules, and look up each one of them using modinfo, to find
4659 the firmware files listed in the module meta-information. Next, it
4660 download the Contents file from a nearby APT mirror, and search for
4661 the firmware files in this file to locate the package with the
4662 requested firmware file. If the package is in the non-free section, a
4663 non-free APT source is added and the package is installed using
4664 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
4665 machine.&lt;/p&gt;
4666
4667 &lt;p&gt;I hope someone find time to implement a more polished version of
4668 this script as part of the hw-detect debian-installer module, to
4669 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
4670 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
4671 firmware during a PXE install when the packages already are available
4672 from the nearby Debian mirror.&lt;/p&gt;
4673 </description>
4674 </item>
4675
4676 <item>
4677 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
4678 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
4679 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
4680 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
4681 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4682 the screen just turn black when Linux boot, either during installation
4683 or on first boot from the hard disk. I&#39;ve seen it once in a while the
4684 last few years, but only recently understood the cause. I&#39;ve seen it
4685 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4686 The reason seem to be in the wiring of some laptops. The system to
4687 control the screen background light is inverted, so when Linux try to
4688 turn the brightness fully on, it end up turning it off instead. I do
4689 not know which Linux drivers are affected, but this post is about the
4690 i915 driver used by the
4691 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
4692 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
4693
4694 &lt;p&gt;The problem can be worked around two ways. Either by adding
4695 i915.invert_brightness=1 as a kernel option, or by adding a file in
4696 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
4697 option when it load the i915 kernel module. On Debian and Ubuntu, it
4698 can be done by running these commands as root:&lt;/p&gt;
4699
4700 &lt;pre&gt;
4701 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
4702 update-initramfs -u -k all
4703 &lt;/pre&gt;
4704
4705 &lt;p&gt;Since March 2012 there is
4706 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
4707 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
4708 hardware have this problem, and get the driver to invert the
4709 brightness setting automatically. To use it, one need to add a row in
4710 &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
4711 intel_quirks array&lt;/a&gt; in the driver source
4712 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
4713 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
4714 number (vendor number 8086 is assumed) and subdevice vendor and device
4715 number.&lt;/p&gt;
4716
4717 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
4718 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
4719
4720 &lt;p&gt;&lt;pre&gt;
4721 00:02.0 VGA compatible controller [0300]: Intel Corporation \
4722 3rd Gen Core processor Graphics Controller [8086:0156] \
4723 (rev 09) (prog-if 00 [VGA controller])
4724 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
4725 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4726 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4727 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
4728 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
4729 Latency: 0
4730 Interrupt: pin A routed to IRQ 42
4731 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
4732 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
4733 Region 4: I/O ports at 4000 [size=64]
4734 Expansion ROM at &lt;unassigned&gt; [disabled]
4735 Capabilities: &lt;access denied&gt;
4736 Kernel driver in use: i915
4737 &lt;/pre&gt;&lt;/p&gt;
4738
4739 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
4740
4741 &lt;p&gt;&lt;pre&gt;
4742 struct intel_quirk intel_quirks[] = {
4743 ...
4744 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4745 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
4746 ...
4747 }
4748 &lt;/pre&gt;&lt;/p&gt;
4749
4750 &lt;p&gt;According to the kernel module instructions (as seen using
4751 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
4752 invert_brightness flag should be sent to the
4753 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
4754 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
4755 developers. But my email about the laptop sent 2013-06-03 have not
4756 yet shown up in
4757 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
4758 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
4759 emails from non-subscribers. Because of this, I sent my patch also to
4760 the Debian bug tracking system instead as
4761 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
4762 sure the patch is not lost.&lt;/p&gt;
4763
4764 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
4765 with this problem working properly with Linux. If you use Gnome, your
4766 worries should be over at this point. But if you use KDE, there is
4767 something in KDE ignoring the invert_brightness setting and turning on
4768 the screen during login. I&#39;ve reported it to Debian as
4769 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
4770 have no idea yet how to figure out exactly what subsystem is doing
4771 this. Perhaps you can help? Perhaps you know what the Gnome
4772 developers did to handle this, and this can give a clue to the KDE
4773 developers? Or you know where in KDE the screen brightness is changed
4774 during login? If so, please update the BTS report (or get in touch if
4775 you do not know how to update BTS).&lt;/p&gt;
4776
4777 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
4778 acpi_backlight=vendor, to disable ACPI backlight support completely,
4779 as the ACPI information on the machine is trash and it is better to
4780 leave it to the intel video driver to control the screen
4781 backlight.&lt;/p&gt;
4782 </description>
4783 </item>
4784
4785 <item>
4786 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
4787 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
4788 <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>
4789 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
4790 <description>&lt;p&gt;Two days ago, I asked
4791 &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
4792 I could install Linux on a Packard Bell EasyNote LV computer
4793 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
4794 with the obstacles put in the way of Linux users on a laptop with UEFI
4795 and Windows 8.&lt;/p&gt;
4796
4797 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
4798 secure booting or fast boot. I suspect fast boot was the problem,
4799 causing the firmware to boot directly from HD without considering any
4800 key presses and alternative devices, but do not know UEFI settings
4801 enough to tell.&lt;/p&gt;
4802
4803 &lt;p&gt;There is no way to install Linux on the machine in question without
4804 opening the box and disconnecting the hard drive! This is as far as I
4805 can tell, the only way to get access to the firmware setup menu
4806 without accepting the Windows 8 license agreement. I am told (and
4807 found description on how to) that it is possible to configure the
4808 firmware setup once booted into Windows 8. But as I believe the terms
4809 of that agreement are completely unacceptable, accepting the license
4810 was never an alternative. I do not enter agreements I do not intend
4811 to follow.&lt;/p&gt;
4812
4813 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
4814 waste many hours on this, but luckily there was a way to get it to
4815 work. But I would not recommend it to anyone planning to run Linux on
4816 it, and I have become sceptical to Windows 8 certified laptops. Is
4817 this the way Linux will be forced out of the market place, by making
4818 it close to impossible for &quot;normal&quot; users to install Linux without
4819 accepting the Microsoft Windows license terms? Or at least not
4820 without risking to loose the warranty?&lt;/p&gt;
4821
4822 &lt;p&gt;I&#39;ve updated the
4823 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
4824 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
4825 do not have to struggle as much as I did to get Linux into the
4826 machine.&lt;/p&gt;
4827
4828 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4829 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
4830 </description>
4831 </item>
4832
4833 <item>
4834 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
4835 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
4836 <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>
4837 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
4838 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
4839 new laptops for my parents and a few others. I bought Packard Bell
4840 Easynote LV to run Kubuntu on and use as their home computer. But I
4841 am completely unable to figure out how to install Linux on it. The
4842 computer is preinstalled with Windows 8, and I suspect it uses UEFI
4843 instead of a BIOS to boot.&lt;/p&gt;
4844
4845 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
4846 to get it to boot the Linux installer from my USB stick. I have yet
4847 to try the DVD install, and still hope it will work. when I turn on
4848 the computer, there is no information on what buttons to press to get
4849 the normal boot menu. I expect to get some boot menu to select PXE or
4850 USB stick booting. When booting, it first ask for the language to
4851 use, then for some regional settings, and finally if I will accept the
4852 Windows 8 terms of use. As these terms are completely unacceptable to
4853 me, I have no other choice but to turn off the computer and try again
4854 to get it to boot the Linux installer.&lt;/p&gt;
4855
4856 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
4857 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
4858 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
4859 installed on this machine, please get in touch or update that wiki
4860 page. If I can&#39;t find a way to install Linux, I will have to return
4861 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
4862
4863 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
4864 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
4865 on new Laptops?&lt;/p&gt;
4866 </description>
4867 </item>
4868
4869 <item>
4870 <title>How to transform a Debian based system to a Debian Edu installation</title>
4871 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
4872 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
4873 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
4874 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
4875 an operating system based on Debian intended for use in schools. It
4876 contain a turn-key solution for the computer network provided to
4877 pupils in the primary schools. It provide both the central server,
4878 network boot servers and desktop environments with heaps of
4879 educational software. The project was founded almost 12 years ago,
4880 2001-07-02. If you want to support the project, which is in need for
4881 cash to fund developer gatherings and other project related activity,
4882 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
4883 donate some money&lt;/a&gt;.
4884
4885 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
4886 lists and elsewhere, is the question on how to transform a Debian or
4887 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
4888 hard, and last week I wrote a script to replicate the steps done by
4889 the Debian Edu installer.&lt;/p&gt;
4890
4891 &lt;p&gt;The script,
4892 &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;
4893 in the debian-edu-config package, will go through these six steps and
4894 transform an existing Debian Wheezy or Ubuntu (untested) installation
4895 into a Debian Edu Workstation:&lt;/p&gt;
4896
4897 &lt;ol&gt;
4898
4899 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
4900 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
4901 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
4902 our configuration.&lt;/li&gt;
4903 &lt;li&gt;Preseed debconf database with profile setup in
4904 /etc/debian-edu/config, and run tasksel to install packages
4905 according to the profile specified in the config above,
4906 overriding some of the Debian automation machinery.&lt;/li&gt;
4907 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
4908 that could not be done using preseeding.&lt;/li&gt;
4909 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
4910
4911 &lt;/ol&gt;
4912
4913 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
4914 replicated like this. Disk partitioning and LVM setup, for example.
4915 So this script just assume there is enough disk space to install all
4916 the needed packages.&lt;/p&gt;
4917
4918 &lt;p&gt;The script was created to help a Debian Edu student working on
4919 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
4920 Debian Edu client, and using it he can take the existing
4921 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
4922 transform it into a fully functioning Debian Edu Workstation (or
4923 Roaming Workstation, or whatever :).&lt;/p&gt;
4924
4925 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
4926 If a LXDE based Roaming workstation is wanted instead, modify the
4927 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
4928
4929 &lt;p&gt;&lt;pre&gt;
4930 PROFILE=&quot;Roaming-Workstation&quot;
4931 DESKTOP=&quot;lxde&quot;
4932 &lt;/pre&gt;&lt;/p&gt;
4933
4934 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
4935 the cloud, by starting with a virtual Debian installation at some
4936 virtual hosting service and setting up all the services on first
4937 boot.&lt;/p&gt;
4938 </description>
4939 </item>
4940
4941 <item>
4942 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
4943 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
4944 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
4945 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
4946 <description>&lt;P&gt;In January,
4947 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
4948 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
4949 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
4950 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
4951 marvellous construction system from Denmark. We also created
4952 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
4953 a place to take notes and write down our plans and hopes. And several
4954 people showed up to help. I was very happy to see the effect of my
4955 call. Since the small start, we have a debtags tag
4956 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
4957 tag for LEGO related packages, and now count 10 packages related to
4958 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
4959
4960 &lt;p&gt;&lt;table&gt;
4961 &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;
4962 &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;
4963 &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;
4964 &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;
4965 &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;
4966 &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;
4967 &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;
4968 &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;
4969 &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;
4970 &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;
4971 &lt;/table&gt;&lt;/p&gt;
4972
4973 &lt;p&gt;Some of these are available in Wheezy, and all but one are
4974 currently available in Jessie/testing. leocad is so far only
4975 available in experimental.&lt;/p&gt;
4976
4977 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
4978 adding the rest of the great free software tools available on Linux
4979 for LEGO designers.&lt;/p&gt;
4980 </description>
4981 </item>
4982
4983 <item>
4984 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
4985 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
4986 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
4987 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
4988 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
4989 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
4990 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
4991 Debian release, and I expect to move my machines at home over to it fairly
4992 soon.&lt;/p&gt;
4993
4994 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
4995 in particular make me very happy to see included. The
4996 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
4997 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
4998 included for the first time. Alongside similar programs like
4999 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
5000 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
5001 it allow for visual programming where syntax errors can not happen,
5002 and a friendly programming environment for learning to control the
5003 computer. Scratch will also be included in the next release of Debian
5004 Edu.&lt;/a&gt;
5005
5006 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
5007 Edu/Skolelinux release too. The
5008 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
5009 alpha release&lt;/a&gt; went out last week, and the next should soon
5010 follow.&lt;p&gt;
5011 </description>
5012 </item>
5013
5014 <item>
5015 <title>Isenkram 0.2 finally in the Debian archive</title>
5016 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
5017 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
5018 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
5019 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
5020 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
5021 for many months. I uploaded it to the Debian experimental suite
5022 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
5023
5024 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
5025 install to work with a pluggable hardware device. The suggestion pop
5026 up when the device is plugged in. For example if a Lego Mindstorm NXT
5027 is inserted, it will suggest to install the program needed to program
5028 the NXT controller. Give it a go, and report bugs and suggestions to
5029 BTS. :)&lt;/p&gt;
5030 </description>
5031 </item>
5032
5033 <item>
5034 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
5035 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
5036 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
5037 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
5038 <description>&lt;p&gt;My
5039 &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
5040 bitcoin related blog post&lt;/a&gt; mentioned that the new
5041 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
5042 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5043 2013-01-19, and have been available in unstable since then. It was
5044 automatically copied to Ubuntu, and is available in their Raring
5045 version too.&lt;/p&gt;
5046
5047 &lt;p&gt;But there is a strange problem with the build that block this new
5048 version from being available on the i386 and kfreebsd-i386
5049 architectures. For some strange reason, the autobuilders in Debian
5050 for these architectures fail to run the test suite on these
5051 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
5052 We are so far unable to reproduce it when building it manually, and
5053 no-one have been able to propose a fix. If you got an idea what is
5054 failing, please let us know via the BTS.&lt;/p&gt;
5055
5056 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
5057 I often run low on disk space, is the fact that the client will exit
5058 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
5059 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
5060 it. :)&lt;/p&gt;
5061
5062 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5063 activities, please send Bitcoin donations to my address
5064 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5065 </description>
5066 </item>
5067
5068 <item>
5069 <title>Welcome to the world, Isenkram!</title>
5070 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
5071 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
5072 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
5073 <description>&lt;p&gt;Yesterday, I
5074 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
5075 for testers&lt;/a&gt; for my prototype for making Debian better at handling
5076 pluggable hardware devices, which I
5077 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
5078 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
5079 up, and caused me to really want to to open up the development to more
5080 people. But before I did this, I want to come up with a sensible name
5081 for this project. Today I finally decided on a new name, and I have
5082 renamed the project from hw-support-handler to this new name. In the
5083 process, I moved the source to git and made it available as a
5084 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
5085 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
5086 To fetch and build the latest version of the source, use&lt;/p&gt;
5087
5088 &lt;pre&gt;
5089 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5090 cd isenkram &amp;&amp; git-buildpackage -us -uc
5091 &lt;/pre&gt;
5092
5093 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
5094 want to hack on the source or improve the package, please go ahead.
5095 But please talk to me first on IRC or via email before you do major
5096 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
5097
5098 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
5099 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5100 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
5101 the German word eisenkram, for those that are familiar with that
5102 word.&lt;/p&gt;
5103
5104 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
5105 instructions, to avoid confusing people with an error from the signing
5106 process.&lt;/p&gt;
5107
5108 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
5109 clone argument to avoid the need for authentication.&lt;/p&gt;
5110 </description>
5111 </item>
5112
5113 <item>
5114 <title>First prototype ready making hardware easier to use in Debian</title>
5115 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
5116 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
5117 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
5118 <description>&lt;p&gt;Early this month I set out to try to
5119 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
5120 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
5121 prototype is working, and it is ready for a larger audience. To test
5122 it, fetch the
5123 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
5124 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
5125 package. You might have to log out and in again activate the
5126 autostart script.&lt;/p&gt;
5127
5128 &lt;p&gt;The design is simple:&lt;/p&gt;
5129
5130 &lt;ul&gt;
5131
5132 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
5133 hw-support-handlerd to start when the user log in.&lt;/li&gt;
5134
5135 &lt;li&gt;This program listen for kernel events about new hardware (directly
5136 from the kernel like udev does), not using HAL dbus events as I
5137 initially did.&lt;/li&gt;
5138
5139 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
5140 the APT database, a database
5141 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
5142 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
5143
5144 &lt;li&gt;If a package is mapped to the hardware in question, the package
5145 isn&#39;t installed yet and this is the first time the hardware was
5146 plugged in, show a desktop notification suggesting to install the
5147 package or packages.&lt;/li&gt;
5148
5149 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
5150 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
5151
5152 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
5153 package while showing progress information in a window.&lt;/li&gt;
5154
5155 &lt;/ul&gt;
5156
5157 &lt;p&gt;I still need to come up with a better name for the system. Here
5158 are some screen shots showing the prototype in action. First the
5159 notification, then the password request, and finally the request to
5160 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
5161
5162 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
5163 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
5164 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
5165 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
5166 &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;
5167
5168 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
5169 is already useful. The database of hardware to package mappings also
5170 need more work. It is currently compatible with the Ubuntu way of
5171 storing such information in the package control file, but could be
5172 changed to use other formats instead or in addition to the current
5173 method. I&#39;ve dropped the use of discover for this mapping, as the
5174 modalias approach is more flexible and easier to use on Linux as long
5175 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
5176
5177 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
5178 here is the command required to check out and build the source: Use
5179 &#39;&lt;tt&gt;svn checkout
5180 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5181 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
5182 devscripts package.&lt;/p&gt;
5183
5184 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
5185 renamed to Isenkram and the source moved from the Debian Edu
5186 subversion repository to a Debian collab-maint git repository. See
5187 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
5188 instructions&lt;/a&gt; for details.&lt;/p&gt;
5189 </description>
5190 </item>
5191
5192 <item>
5193 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
5194 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
5195 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
5196 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
5197 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
5198 suddenly in bed. With a quiet whimper, it went completely quiet and
5199 black. The power button was no longer able to turn it on. It was a
5200 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5201 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5202 Compaq I had before that. Now I need to find a replacement. To keep
5203 going during Christmas, I moved the one year old SSD disk to my old
5204 X40 where it fitted (only one I had left that could use it), but it is
5205 not a durable solution.
5206
5207 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
5208 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
5209
5210 &lt;ul&gt;
5211
5212 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
5213 than A4).&lt;/li&gt;
5214 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
5215 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
5216 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
5217 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
5218 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
5219 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
5220 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
5221 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
5222 size).&lt;/li&gt;
5223 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
5224 X.org packages.&lt;/li&gt;
5225 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
5226 the time).
5227
5228 &lt;/ul&gt;
5229
5230 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
5231 list. The reason is simply that the specifications on laptops the
5232 last 10-15 years have been sufficient for my needs, and I have to look
5233 at other features to choose my laptop. But are there still made as
5234 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5235 robust, and Thinkpads seem to be heading in the wrong direction since
5236 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
5237 still be useful.&lt;/p&gt;
5238
5239 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
5240 external keyboard? I&#39;ll have to check the
5241 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
5242 well-supported laptops, or perhaps just buy one preinstalled from one
5243 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
5244 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
5245 </description>
5246 </item>
5247
5248 <item>
5249 <title>How to find a browser plugin supporting a given MIME type</title>
5250 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
5251 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
5252 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
5253 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
5254 install to get support for a given MIME type. Thanks to
5255 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
5256 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
5257 Unfortunately, not very many packages provide the needed meta
5258 information, Anyway, here is a small script to look up all browser
5259 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
5260
5261 &lt;pre&gt;
5262 #!/usr/bin/python
5263 import sys
5264 import apt
5265 def pkgs_handling_mimetype(mimetype):
5266 cache = apt.Cache()
5267 cache.open(None)
5268 thepkgs = []
5269 for pkg in cache:
5270 version = pkg.candidate
5271 if version is None:
5272 version = pkg.installed
5273 if version is None:
5274 continue
5275 record = version.record
5276 if not record.has_key(&#39;Npp-MimeType&#39;):
5277 continue
5278 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
5279 for t in mime_types:
5280 t = t.rstrip().strip()
5281 if t == mimetype:
5282 thepkgs.append(pkg.name)
5283 return thepkgs
5284 mimetype = &quot;audio/ogg&quot;
5285 if 1 &lt; len(sys.argv):
5286 mimetype = sys.argv[1]
5287 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
5288 for pkg in pkgs_handling_mimetype(mimetype):
5289 print &quot; %s&quot; %pkg
5290 &lt;/pre&gt;
5291
5292 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
5293
5294 &lt;pre&gt;
5295 % ./apt-find-browserplug-for-mimetype
5296 Browser plugin packages supporting audio/ogg:
5297 gecko-mediaplayer
5298 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5299 Browser plugin packages supporting application/x-shockwave-flash:
5300 browser-plugin-gnash
5301 %
5302 &lt;/pre&gt;
5303
5304 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
5305 itself to query for plugins and propose to install the needed
5306 packages. It would be great if Debian supported such feature too. Is
5307 anyone working on adding it?&lt;/p&gt;
5308
5309 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
5310 request for icweasel support for this feature is
5311 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
5312 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
5313 of manpower and wish for a different design is the reason thus feature
5314 is not yet in iceweasel from Debian.&lt;/p&gt;
5315 </description>
5316 </item>
5317
5318 <item>
5319 <title>What is the most supported MIME type in Debian?</title>
5320 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
5321 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
5322 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
5323 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
5324 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
5325 proposal to make it possible for a Desktop application to propose to
5326 the user some package to install to gain support for a given MIME
5327 type, font, library etc. that is currently missing. With such
5328 mechanism in place, it would be possible for the desktop to
5329 automatically propose and install leocad if some LDraw file is
5330 downloaded by the browser.&lt;/p&gt;
5331
5332 &lt;p&gt;To get some idea about the current content of the archive, I decided
5333 to write a simple program to extract all .desktop files from the
5334 Debian archive and look up the claimed MIME support there. The result
5335 can be found on the
5336 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
5337 site&lt;/a&gt;. Using the collected information, it become possible to
5338 answer the question in the title. Here are the 20 most supported MIME
5339 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5340 The complete list is available from the link above.&lt;/p&gt;
5341
5342 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
5343
5344 &lt;pre&gt;
5345 count MIME type
5346 ----- -----------------------
5347 32 text/plain
5348 30 audio/mpeg
5349 29 image/png
5350 28 image/jpeg
5351 27 application/ogg
5352 26 audio/x-mp3
5353 25 image/tiff
5354 25 image/gif
5355 22 image/bmp
5356 22 audio/x-wav
5357 20 audio/x-flac
5358 19 audio/x-mpegurl
5359 18 video/x-ms-asf
5360 18 audio/x-musepack
5361 18 audio/x-mpeg
5362 18 application/x-ogg
5363 17 video/mpeg
5364 17 audio/x-scpls
5365 17 audio/ogg
5366 16 video/x-ms-wmv
5367 &lt;/pre&gt;
5368
5369 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
5370
5371 &lt;pre&gt;
5372 count MIME type
5373 ----- -----------------------
5374 33 text/plain
5375 32 image/png
5376 32 image/jpeg
5377 29 audio/mpeg
5378 27 image/gif
5379 26 image/tiff
5380 26 application/ogg
5381 25 audio/x-mp3
5382 22 image/bmp
5383 21 audio/x-wav
5384 19 audio/x-mpegurl
5385 19 audio/x-mpeg
5386 18 video/mpeg
5387 18 audio/x-scpls
5388 18 audio/x-flac
5389 18 application/x-ogg
5390 17 video/x-ms-asf
5391 17 text/html
5392 17 audio/x-musepack
5393 16 image/x-xbitmap
5394 &lt;/pre&gt;
5395
5396 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
5397
5398 &lt;pre&gt;
5399 count MIME type
5400 ----- -----------------------
5401 31 text/plain
5402 31 image/png
5403 31 image/jpeg
5404 29 audio/mpeg
5405 28 application/ogg
5406 27 image/gif
5407 26 image/tiff
5408 26 audio/x-mp3
5409 23 audio/x-wav
5410 22 image/bmp
5411 21 audio/x-flac
5412 20 audio/x-mpegurl
5413 19 audio/x-mpeg
5414 18 video/x-ms-asf
5415 18 video/mpeg
5416 18 audio/x-scpls
5417 18 application/x-ogg
5418 17 audio/x-musepack
5419 16 video/x-ms-wmv
5420 16 video/x-msvideo
5421 &lt;/pre&gt;
5422
5423 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
5424 information mentioned in DEP-11. I have not yet had time to look at
5425 it, but hope the PackageKit people in Debian are on top of these
5426 issues.&lt;/p&gt;
5427
5428 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
5429 discovering a typo in my script.&lt;/p&gt;
5430 </description>
5431 </item>
5432
5433 <item>
5434 <title>Using modalias info to find packages handling my hardware</title>
5435 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
5436 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
5437 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
5438 <description>&lt;p&gt;Yesterday, I wrote about the
5439 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
5440 values provided by the Linux kernel&lt;/a&gt; following my hope for
5441 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
5442 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
5443 modalias values attached to package names can be used to map packages
5444 to hardware. This allow the system to look up and suggest relevant
5445 packages when I plug in some new hardware into my machine, and replace
5446 discover and discover-data as the database used to map hardware to
5447 packages.&lt;/p&gt;
5448
5449 &lt;p&gt;I create a modaliases file with entries like the following,
5450 containing package name, kernel module name (if relevant, otherwise
5451 the package name) and globs matching the relevant hardware
5452 modalias.&lt;/p&gt;
5453
5454 &lt;p&gt;&lt;blockquote&gt;
5455 Package: package-name
5456 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
5457 &lt;/blockquote&gt;&lt;/p&gt;
5458
5459 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
5460 for a given modalias value using this file.&lt;/p&gt;
5461
5462 &lt;p&gt;An entry like this would suggest the video and picture application
5463 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
5464
5465 &lt;p&gt;&lt;blockquote&gt;
5466 Package: cheese
5467 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
5468 &lt;/blockquote&gt;&lt;/p&gt;
5469
5470 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
5471 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
5472
5473 &lt;p&gt;&lt;blockquote&gt;
5474 Package: pcmciautils
5475 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5476 &lt;/blockquote&gt;&lt;/p&gt;
5477
5478 &lt;p&gt;An entry like this would suggest the package colorhug-client when
5479 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
5480
5481 &lt;p&gt;&lt;blockquote&gt;
5482 Package: colorhug-client
5483 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
5484 &lt;/blockquote&gt;&lt;/p&gt;
5485
5486 &lt;p&gt;I believe the format is compatible with the format of the Packages
5487 file in the Debian archive. Ubuntu already uses their Packages file
5488 to store their mappings from packages to hardware.&lt;/p&gt;
5489
5490 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
5491 announce the hardware it support in a way my prototype understand.
5492 This allow those publishing packages in an APT source outside the
5493 Debian archive as well as those backporting packages to make sure the
5494 hardware mapping are included in the package meta information. I&#39;ve
5495 tested such header in the pymissile package, and its modalias mapping
5496 is working as it should with my prototype. It even made it to Ubuntu
5497 Raring.&lt;/p&gt;
5498
5499 &lt;p&gt;To test if it was possible to look up supported hardware using only
5500 the shell tools available in the Debian installer, I wrote a shell
5501 implementation of the lookup code. The idea is to create files for
5502 each modalias and let the shell do the matching. Please check out and
5503 try the
5504 &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;
5505 shell script. It run without any extra dependencies and fetch the
5506 hardware mappings from the Debian archive and the subversion
5507 repository where I currently work on my prototype.&lt;/p&gt;
5508
5509 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
5510 install yubikey-personalization:&lt;/p&gt;
5511
5512 &lt;p&gt;&lt;blockquote&gt;
5513 % ./hw-support-lookup
5514 &lt;br&gt;yubikey-personalization
5515 &lt;br&gt;%
5516 &lt;/blockquote&gt;&lt;/p&gt;
5517
5518 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5519 propose to install the pcmciautils package:&lt;/p&gt;
5520
5521 &lt;p&gt;&lt;blockquote&gt;
5522 % ./hw-support-lookup
5523 &lt;br&gt;pcmciautils
5524 &lt;br&gt;%
5525 &lt;/blockquote&gt;&lt;/p&gt;
5526
5527 &lt;p&gt;If you know of any hardware-package mapping that should be added to
5528 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
5529 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
5530
5531 &lt;p&gt;It could be possible to generate several of the mappings between
5532 packages and hardware. One source would be to look at packages with
5533 kernel modules, ie packages with *.ko files in /lib/modules/, and
5534 extract their modalias information. Another would be to look at
5535 packages with udev rules, ie packages with files in
5536 /lib/udev/rules.d/, and extract their vendor/model information to
5537 generate a modalias matching rule. I have not tested any of these to
5538 see if it work.&lt;/p&gt;
5539
5540 &lt;p&gt;If you want to help implementing a system to let us propose what
5541 packages to install when new hardware is plugged into a Debian
5542 machine, please send me an email or talk to me on
5543 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
5544 </description>
5545 </item>
5546
5547 <item>
5548 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
5549 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
5550 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
5551 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
5552 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
5553 information, to find the packages that support a given piece of
5554 hardware, I refreshed my memory regarding modalias values, and decided
5555 to document the details. Here are my findings so far, also available
5556 in
5557 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
5558 Debian Edu subversion repository&lt;/a&gt;:
5559
5560 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
5561
5562 &lt;p&gt;This document try to explain what the different types of modalias
5563 values stands for. It is in part based on information from
5564 &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;,
5565 &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;,
5566 &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
5567 &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;.
5568
5569 &lt;p&gt;The modalias entries for a given Linux machine can be found using
5570 this shell script:&lt;/p&gt;
5571
5572 &lt;pre&gt;
5573 find /sys -name modalias -print0 | xargs -0 cat | sort -u
5574 &lt;/pre&gt;
5575
5576 &lt;p&gt;The supported modalias globs for a given kernel module can be found
5577 using modinfo:&lt;/p&gt;
5578
5579 &lt;pre&gt;
5580 % /sbin/modinfo psmouse | grep alias:
5581 alias: serio:ty05pr*id*ex*
5582 alias: serio:ty01pr*id*ex*
5583 %
5584 &lt;/pre&gt;
5585
5586 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
5587
5588 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
5589 Bridge memory controller:&lt;/p&gt;
5590
5591 &lt;p&gt;&lt;blockquote&gt;
5592 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5593 &lt;/blockquote&gt;&lt;/p&gt;
5594
5595 &lt;p&gt;This represent these values:&lt;/p&gt;
5596
5597 &lt;pre&gt;
5598 v 00008086 (vendor)
5599 d 00002770 (device)
5600 sv 00001028 (subvendor)
5601 sd 000001AD (subdevice)
5602 bc 06 (bus class)
5603 sc 00 (bus subclass)
5604 i 00 (interface)
5605 &lt;/pre&gt;
5606
5607 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
5608 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
5609 0600. The 0600 class is a host bridge. Other useful bus values are
5610 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
5611
5612 &lt;p&gt;Not sure how to figure out the interface value, nor what it
5613 means.&lt;/p&gt;
5614
5615 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
5616
5617 &lt;p&gt;Some typical USB entries can look like this. This is an internal
5618 USB hub in a laptop:&lt;/p&gt;
5619
5620 &lt;p&gt;&lt;blockquote&gt;
5621 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5622 &lt;/blockquote&gt;&lt;/p&gt;
5623
5624 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
5625
5626 &lt;pre&gt;
5627 v 1D6B (device vendor)
5628 p 0001 (device product)
5629 d 0206 (bcddevice)
5630 dc 09 (device class)
5631 dsc 00 (device subclass)
5632 dp 00 (device protocol)
5633 ic 09 (interface class)
5634 isc 00 (interface subclass)
5635 ip 00 (interface protocol)
5636 &lt;/pre&gt;
5637
5638 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
5639 class is in the interface class section. For a simple USB web camera,
5640 these alias entries show up:&lt;/p&gt;
5641
5642 &lt;p&gt;&lt;blockquote&gt;
5643 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5644 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5645 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5646 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5647 &lt;/blockquote&gt;&lt;/p&gt;
5648
5649 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
5650 camera), 0101 is audio control device and 0102 is audio streaming (aka
5651 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
5652
5653 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
5654
5655 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
5656 receiver in a Thinkpad X40:&lt;/p&gt;
5657
5658 &lt;p&gt;&lt;blockquote&gt;
5659 acpi:IBM0071:PNP0511:
5660 &lt;/blockquote&gt;&lt;/p&gt;
5661
5662 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
5663
5664 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
5665
5666 &lt;p&gt;The DMI table contain lots of information about the computer case
5667 and model. This is an entry for a IBM Thinkpad X40, fetched from
5668 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
5669
5670 &lt;p&gt;&lt;blockquote&gt;
5671 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5672 &lt;/blockquote&gt;&lt;/p&gt;
5673
5674 &lt;p&gt;The values present are&lt;/p&gt;
5675
5676 &lt;pre&gt;
5677 bvn IBM (BIOS vendor)
5678 bvr 1UETB6WW(1.66) (BIOS version)
5679 bd 06/15/2005 (BIOS date)
5680 svn IBM (system vendor)
5681 pn 2371H4G (product name)
5682 pvr ThinkPadX40 (product version)
5683 rvn IBM (board vendor)
5684 rn 2371H4G (board name)
5685 rvr NotAvailable (board version)
5686 cvn IBM (chassis vendor)
5687 ct 10 (chassis type)
5688 cvr NotAvailable (chassis version)
5689 &lt;/pre&gt;
5690
5691 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
5692 found in the dmidecode source:&lt;/p&gt;
5693
5694 &lt;pre&gt;
5695 3 Desktop
5696 4 Low Profile Desktop
5697 5 Pizza Box
5698 6 Mini Tower
5699 7 Tower
5700 8 Portable
5701 9 Laptop
5702 10 Notebook
5703 11 Hand Held
5704 12 Docking Station
5705 13 All In One
5706 14 Sub Notebook
5707 15 Space-saving
5708 16 Lunch Box
5709 17 Main Server Chassis
5710 18 Expansion Chassis
5711 19 Sub Chassis
5712 20 Bus Expansion Chassis
5713 21 Peripheral Chassis
5714 22 RAID Chassis
5715 23 Rack Mount Chassis
5716 24 Sealed-case PC
5717 25 Multi-system
5718 26 CompactPCI
5719 27 AdvancedTCA
5720 28 Blade
5721 29 Blade Enclosing
5722 &lt;/pre&gt;
5723
5724 &lt;p&gt;The chassis type values are not always accurately set in the DMI
5725 table. For example my home server is a tower, but the DMI modalias
5726 claim it is a desktop.&lt;/p&gt;
5727
5728 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
5729
5730 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
5731 test machine:&lt;/p&gt;
5732
5733 &lt;p&gt;&lt;blockquote&gt;
5734 serio:ty01pr00id00ex00
5735 &lt;/blockquote&gt;&lt;/p&gt;
5736
5737 &lt;p&gt;The values present are&lt;/p&gt;
5738
5739 &lt;pre&gt;
5740 ty 01 (type)
5741 pr 00 (prototype)
5742 id 00 (id)
5743 ex 00 (extra)
5744 &lt;/pre&gt;
5745
5746 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
5747 the valid values are.&lt;/p&gt;
5748
5749 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
5750
5751 &lt;p&gt;There are heaps of other modalias subtypes according to
5752 file2alias.c. There is the rest of the list from that source: amba,
5753 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5754 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5755 vmbus, x86cpu and zorro. I did not spend time documenting all of
5756 these, as they do not seem relevant for my intended use with mapping
5757 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
5758
5759 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
5760
5761 &lt;p&gt;To check which kernel modules provide support for a given modalias,
5762 one can use the following shell script:&lt;/p&gt;
5763
5764 &lt;pre&gt;
5765 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
5766 echo &quot;$id&quot; ; \
5767 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
5768 done
5769 &lt;/pre&gt;
5770
5771 &lt;p&gt;The output can look like this (only the first few entries as the
5772 list is very long on my test machine):&lt;/p&gt;
5773
5774 &lt;pre&gt;
5775 acpi:ACPI0003:
5776 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
5777 acpi:device:
5778 FATAL: Module acpi:device: not found.
5779 acpi:IBM0068:
5780 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
5781 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
5782 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
5783 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5784 acpi:IBM0071:PNP0511:
5785 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
5786 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
5787 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
5788 [...]
5789 &lt;/pre&gt;
5790
5791 &lt;p&gt;If you want to help implementing a system to let us propose what
5792 packages to install when new hardware is plugged into a Debian
5793 machine, please send me an email or talk to me on
5794 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
5795
5796 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
5797 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
5798 in /sys/ with space in them.&lt;/p&gt;
5799 </description>
5800 </item>
5801
5802 <item>
5803 <title>Moved the pymissile Debian packaging to collab-maint</title>
5804 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
5805 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
5806 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
5807 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
5808 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5809 Launcher and updated the Debian package
5810 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
5811 sure udev will fix the device permissions when it is plugged in. I
5812 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
5813 hopefully make the package be proposed by jockey in Ubuntu when a user
5814 plug in his rocket launcher. In the process I moved the source to a
5815 git repository under collab-maint, to make it easier for any DD to
5816 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
5817 is not very active, but the software still work for me even after five
5818 years of relative silence. The new git repository is not listed in
5819 the uploaded package yet, because I want to test the other changes a
5820 bit more before I upload the new version. If you want to check out
5821 the new version with a .desktop file included, visit the
5822 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
5823 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
5824 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
5825 </description>
5826 </item>
5827
5828 <item>
5829 <title>Lets make hardware dongles easier to use in Debian</title>
5830 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
5831 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
5832 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
5833 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
5834 general, is that there is a great package management system with the
5835 ability to automatically install software packages by downloading them
5836 from the distribution mirrors, but no way to get it to automatically
5837 install the packages I need to use the hardware I plug into my
5838 machine. Even if the package to use it is easily available from the
5839 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5840 suggest to automatically install the python-nxt, nbc and t2n packages
5841 I need to talk to it. When I plug in a Yubikey, it could propose the
5842 yubikey-personalization package. The information required to do this
5843 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
5844
5845 &lt;p&gt;Some years ago, I proposed to
5846 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
5847 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
5848 simple:
5849
5850 &lt;ul&gt;
5851
5852 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
5853 starting when a user log in.&lt;/li&gt;
5854
5855 &lt;li&gt;Set this program up to listen for kernel events emitted when new
5856 hardware is inserted into the computer.&lt;/li&gt;
5857
5858 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
5859 database mapping to packages, and take note of any non-installed
5860 packages.&lt;/li&gt;
5861
5862 &lt;li&gt;Show a message to the user proposing to install the discovered
5863 package, and make it easy to install it.&lt;/li&gt;
5864
5865 &lt;/ul&gt;
5866
5867 &lt;p&gt;I am not sure what the best way to implement this is, but my
5868 initial idea was to use dbus events to discover new hardware, the
5869 discover database to find packages and
5870 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
5871 packages.&lt;/p&gt;
5872
5873 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
5874 draft package is now checked into
5875 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
5876 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
5877 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
5878 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5879 the relevant packages in Debian, and uploaded a new version
5880 2.2013.01.09 to unstable. I also discovered that the current
5881 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
5882 package in Debian no longer discovered any USB devices, because
5883 /proc/bus/usb/devices is no longer present. I ported it to use
5884 libusb as a fall back option to get it working. The fixed package
5885 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
5886 because of the freeze).&lt;/p&gt;
5887
5888 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
5889 desktop notification to show up (only once, the first time it is
5890 inserted):&lt;/p&gt;
5891
5892 &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;
5893
5894 &lt;p&gt;For this prototype to be really useful, some way to automatically
5895 install the proposed packages by pressing the &quot;Please install
5896 program(s)&quot; button should to be implemented.&lt;/p&gt;
5897
5898 &lt;p&gt;If this idea seem useful to you, and you want to help make it
5899 happen, please help me update the discover-data database with mappings
5900 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
5901 list the package you would like to have installed when a given
5902 hardware device is inserted into your computer, and report bugs using
5903 reportbug if it isn&#39;t. Or, if you know of a better way to provide
5904 such mapping, please let me know.&lt;/p&gt;
5905
5906 &lt;p&gt;This prototype need more work, and there are several questions that
5907 should be considered before it is ready for production use. Is dbus
5908 the correct way to detect new hardware? At the moment I look for HAL
5909 dbus events on the system bus, because that is the events I could see
5910 on my Debian Squeeze KDE desktop. Are there better events to use?
5911 How should the user be notified? Is the desktop notification
5912 mechanism the best option, or should the background daemon raise a
5913 popup instead? How should packages be installed? When should they
5914 not be installed?&lt;/p&gt;
5915
5916 &lt;p&gt;If you want to help getting such feature implemented in Debian,
5917 please send me an email. :)&lt;/p&gt;
5918 </description>
5919 </item>
5920
5921 <item>
5922 <title>New IRC channel for LEGO designers using Debian</title>
5923 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
5924 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
5925 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
5926 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
5927 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
5928 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
5929 discovered I had to build all the tools myself because none were
5930 already in Debian Squeeze. If Debian support for LEGO is something
5931 you care about, please join me on the IRC channel
5932 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
5933 irc.debian.org). There is a lot that could be done to improve the
5934 Debian support for LEGO designers. For example both CAD software
5935 and Mindstorm compilers are missing. :)&lt;/p&gt;
5936
5937 &lt;p&gt;Update 2012-01-03: A
5938 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
5939 including links to Lego related packages is now available.&lt;/p&gt;
5940 </description>
5941 </item>
5942
5943 <item>
5944 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
5945 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
5946 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
5947 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
5948 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
5949 year! I hope next year will prove to be a good year.&lt;/p&gt;
5950
5951 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
5952 decentralised &quot;currency&quot; that allow people to transfer bitcoins
5953 between each other with minimal overhead, is a very interesting
5954 experiment. And as I wrote a few days ago, the bitcoin situation in
5955 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
5956 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
5957 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
5958 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
5959 for one of the ftpmasters to approve the new bitcoin-qt package
5960 name.&lt;/p&gt;
5961
5962 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
5963 team in Debian, you can easily test the package in Debian Squeeze
5964 using the following steps to get a set of working packages:&lt;/p&gt;
5965
5966 &lt;blockquote&gt;&lt;pre&gt;
5967 git clone git://git.debian.org/git/collab-maint/bitcoin
5968 cd bitcoin
5969 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5970 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5971 &lt;/pre&gt;&lt;/blockquote&gt;
5972
5973 &lt;p&gt;You might have to install some build dependencies as well. The
5974 list of commands should give you two packages, bitcoind and
5975 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5976 client will download the complete set of bitcoin &quot;blocks&quot;, which need
5977 around 5.6 GiB of data on my machine at the moment. Make sure your
5978 ~/.bitcoin/ directory have lots of spare room if you want to download
5979 all the blocks. The client will warn if the disk is getting full, so
5980 there is not really a problem if you got too little room, but you will
5981 not be able to get all the features out of the client.&lt;/p&gt;
5982
5983 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5984 activities, please send Bitcoin donations to my address
5985 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5986 </description>
5987 </item>
5988
5989 <item>
5990 <title>A word on bitcoin support in Debian</title>
5991 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
5992 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
5993 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
5994 <description>&lt;p&gt;It has been a while since I wrote about
5995 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
5996 peer-to-peer based crypto-currency, and the reason is simply that I
5997 have been busy elsewhere. But two days ago, I started looking at the
5998 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
5999 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
6000 is now maintained by a
6001 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
6002 people&lt;/a&gt;, and the grunt work had already been done by this team. We
6003 owe a huge thank you to all these team members. :)
6004 But I was sad to discover that the bitcoin client is missing in
6005 Wheezy. It is only available in Sid (and an outdated client from
6006 backports). The client had several RC bugs registered in BTS blocking
6007 it from entering testing. To try to help the team and improve the
6008 situation, I spent some time providing patches and triaging the bug
6009 reports. I also had a look at the bitcoin package available from Matt
6010 Corallo in a
6011 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
6012 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
6013 Debian package.&lt;/p&gt;
6014
6015 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
6016 IRC, I pushed several patches into the collab-maint git repository to
6017 improve the package. It now contains fixes for the RC issues (not from
6018 me, but fixed by Scott Howard), build rules for a Qt GUI client
6019 package, konqueror support for the bitcoin: URI and bash completion
6020 setup. As I work on Debian Squeeze, I also created
6021 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
6022 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
6023 it and try to integrate it into the git repository before uploading a
6024 new version to unstable.
6025
6026 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
6027 centralized control currently exercised in the monetary system. I
6028 find it completely unacceptable that the USA government is collecting
6029 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6030 that the major credit card companies can block legal money
6031 transactions to Wikileaks. But for bitcoin to succeed, more people
6032 need to use bitcoins, and more people need to accept bitcoins when
6033 they sell products and services. Improving the bitcoin support in
6034 Debian is a small step in the right direction, but not enough.
6035 Unfortunately the user experience when browsing the web and wanting to
6036 pay with bitcoin is still not very good. The bitcoin: URI is a step
6037 in the right direction, but need to work in most or every browser in
6038 use. Also the bitcoin-qt client is too heavy to fire up to do a
6039 quick transaction. I believe there are other clients available, but
6040 have not tested them.&lt;/p&gt;
6041
6042 &lt;p&gt;My
6043 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
6044 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
6045 I received 20.15 BTC so far on the address I provided in my blog two
6046 years ago, as can be
6047 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
6048 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
6049 donation. The blockexplorer service demonstrates quite well that
6050 bitcoin is not quite anonymous and untracked. :) I wonder if the
6051 number of users have gone up since then. If you use bitcoin and want
6052 to show your support of my activity, please send Bitcoin donations to
6053 the same address as last time,
6054 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6055 </description>
6056 </item>
6057
6058 <item>
6059 <title>Git repository for song book for Computer Scientists</title>
6060 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
6061 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
6062 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
6063 <description>&lt;p&gt;As I
6064 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
6065 this summer&lt;/a&gt;, I have created a Computer Science song book a few
6066 years ago, and today I finally found time to create a public
6067 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
6068 repository for the project&lt;/a&gt;.&lt;/p&gt;
6069
6070 &lt;p&gt;If you want to help out, please clone the source and submit patches
6071 to the HTML version. To generate the PDF and PostScript version,
6072 please use prince XML, or let me know about a useful free software
6073 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
6074
6075 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
6076 PostScript formats at
6077 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
6078 Science Songbook&lt;/a&gt;.&lt;/p&gt;
6079 </description>
6080 </item>
6081
6082 <item>
6083 <title>Gratulerer med 19-årsdagen, Debian!</title>
6084 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
6085 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
6086 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
6087 <description>&lt;p&gt;I dag fyller
6088 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
6089 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
6090 si gratulerer med dagen, Debian!&lt;/p&gt;
6091 </description>
6092 </item>
6093
6094 <item>
6095 <title>Song book for Computer Scientists</title>
6096 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
6097 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
6098 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
6099 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
6100 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
6101 collecting computer related songs for use at parties. The original
6102 version was written in LaTeX, but a few years ago I got help from
6103 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6104 while keeping the ability to create a nice book in PDF format. I have
6105 not had time to maintain the book for a while now, and guess I should
6106 put it up on some public version control repository where others can
6107 help me extend and update the book. If anyone is volunteering to help
6108 me with this, send me an email. Also let me know if there are songs
6109 missing in my book.&lt;/p&gt;
6110
6111 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
6112 me today that I really should let all my readers share the joys of
6113 singing out load about programming, computers and computer networks.
6114 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
6115 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
6116 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
6117 Computer Science Songbook&lt;/a&gt;.
6118 </description>
6119 </item>
6120
6121 <item>
6122 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
6123 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
6124 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
6125 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
6126 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
6127 around 1000 at the moment. To be able to get help from the vendors
6128 when something go wrong, we want to keep the firmware on the servers
6129 up to date. If the firmware isn&#39;t the latest and greatest, the
6130 vendors typically refuse to start debugging any problems until the
6131 firmware is upgraded. So before every reboot, we want to upgrade the
6132 firmware, and we would really like everyone handling servers at the
6133 university to do this themselves when they plan to reboot a machine.
6134 For that to happen we at the unix server admin group need to provide
6135 the tools to do so.&lt;/p&gt;
6136
6137 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
6138 fetch and install the latest firmware for the servers we got. Most of
6139 our hardware are from Dell and HP, so I have focused on these servers
6140 so far. This blog post is about the Dell part.&lt;/P&gt;
6141
6142 &lt;p&gt;On the Dell FTP site I was lucky enough to find
6143 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
6144 with firmware information for all 11th generation servers, listing
6145 which firmware should be used on a given model and where on the FTP
6146 site I can find it. Using a simple perl XML parser I can then
6147 download the shell scripts Dell provides to do firmware upgrades from
6148 within Linux and reboot when all the firmware is primed and ready to
6149 be activated on the first reboot.&lt;/p&gt;
6150
6151 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
6152 Are there anyone working on similar tools for firmware upgrading all
6153 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
6154
6155 &lt;p&gt;&lt;pre&gt;
6156 #!/usr/bin/perl
6157 use strict;
6158 use warnings;
6159 use File::Temp qw(tempdir);
6160 BEGIN {
6161 # Install needed RHEL packages if missing
6162 my %rhelmodules = (
6163 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
6164 );
6165 for my $module (keys %rhelmodules) {
6166 eval &quot;use $module;&quot;;
6167 if ($@) {
6168 my $pkg = $rhelmodules{$module};
6169 system(&quot;yum install -y $pkg&quot;);
6170 eval &quot;use $module;&quot;;
6171 }
6172 }
6173 }
6174 my $errorsto = &#39;pere@hungry.com&#39;;
6175
6176 upgrade_dell();
6177
6178 exit 0;
6179
6180 sub run_firmware_script {
6181 my ($opts, $script) = @_;
6182 unless ($script) {
6183 print STDERR &quot;fail: missing script name\n&quot;;
6184 exit 1
6185 }
6186 print STDERR &quot;Running $script\n\n&quot;;
6187
6188 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
6189 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
6190 } else {
6191 print STDERR &quot;fail: firmware script returned error\n&quot;;
6192 }
6193 }
6194
6195 sub run_firmware_scripts {
6196 my ($opts, @dirs) = @_;
6197 # Run firmware packages
6198 for my $dir (@dirs) {
6199 print STDERR &quot;info: Running scripts in $dir\n&quot;;
6200 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
6201 while (my $s = readdir $dh) {
6202 next if $s =~ m/^\.\.?/;
6203 run_firmware_script($opts, &quot;$dir/$s&quot;);
6204 }
6205 closedir $dh;
6206 }
6207 }
6208
6209 sub download {
6210 my $url = shift;
6211 print STDERR &quot;info: Downloading $url\n&quot;;
6212 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
6213 }
6214
6215 sub upgrade_dell {
6216 my @dirs;
6217 my $product = `dmidecode -s system-product-name`;
6218 chomp $product;
6219
6220 if ($product =~ m/PowerEdge/) {
6221
6222 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6223 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
6224
6225 my $tmpdir = tempdir(
6226 CLEANUP =&gt; 1
6227 );
6228 chdir($tmpdir);
6229 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
6230 system(&#39;gunzip Catalog.xml.gz&#39;);
6231 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
6232 # -q is quiet, disabling interactivity and reducing console output
6233 my $fwopts = &quot;-q&quot;;
6234 if (@paths) {
6235 for my $url (@paths) {
6236 fetch_dell_fw($url);
6237 }
6238 run_firmware_scripts($fwopts, $tmpdir);
6239 } else {
6240 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6241 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6242 }
6243 chdir(&#39;/&#39;);
6244 } else {
6245 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6246 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6247 }
6248 }
6249
6250 sub fetch_dell_fw {
6251 my $path = shift;
6252 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
6253 download($url);
6254 }
6255
6256 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6257 # firmware packages to download from Dell. Only work for Linux
6258 # machines and 11th generation Dell servers.
6259 sub fetch_dell_fw_list {
6260 my $filename = shift;
6261
6262 my $product = `dmidecode -s system-product-name`;
6263 chomp $product;
6264 my ($mybrand, $mymodel) = split(/\s+/, $product);
6265
6266 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
6267
6268 my $xml = XMLin($filename);
6269 my @paths;
6270 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
6271 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
6272 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
6273 my $oscode;
6274 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
6275 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
6276 } else {
6277 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
6278 }
6279 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
6280 {
6281 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
6282 }
6283 }
6284 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
6285 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
6286
6287 # Drop application packages, only firmware and BIOS
6288 next if &#39;APAC&#39; eq $componenttype;
6289
6290 my $cpath = $component-&gt;{path};
6291 for my $path (@paths) {
6292 if ($cpath =~ m%/$path$%) {
6293 push(@paths, $cpath);
6294 }
6295 }
6296 }
6297 return @paths;
6298 }
6299 &lt;/pre&gt;
6300
6301 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
6302 it could work on other platforms with some tweaking. Anyone know a
6303 index like Catalog.xml is available from HP for HP servers? At the
6304 moment I maintain a similar list manually and it is quickly getting
6305 outdated.&lt;/p&gt;
6306 </description>
6307 </item>
6308
6309 <item>
6310 <title>How is booting into runlevel 1 different from single user boots?</title>
6311 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
6312 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
6313 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
6314 <description>&lt;p&gt;Wouter Verhelst have some
6315 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
6316 comments and opinions&lt;/a&gt; on my blog post on
6317 &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
6318 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
6319 &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
6320 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
6321 small piece of his comment now, and though it best to address the
6322 misunderstanding he bring forward:&lt;/p&gt;
6323
6324 &lt;p&gt;&lt;blockquote&gt;
6325 Currently, a system admin has four options: [...] boot to a
6326 single-user system (by adding &#39;single&#39; to the kernel command line;
6327 this runs rcS and rc1 scripts)
6328 &lt;/blockquote&gt;&lt;/p&gt;
6329
6330 &lt;p&gt;This make me believe Wouter believe booting into single user mode
6331 and booting into runlevel 1 is the same. I am not surprised he
6332 believe this, because it would make sense and is a quite sensible
6333 thing to believe. But because the boot in Debian is slightly broken,
6334 runlevel 1 do not work properly and it isn&#39;t the same as single user
6335 mode. I&#39;ll try to explain what is actually happing, but it is a bit
6336 hard to explain.&lt;/p&gt;
6337
6338 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
6339 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
6340 executed in single user mode is sulogin. Single user mode is a boot
6341 state &quot;between&quot; the runlevels, and when booting into single user mode,
6342 only the scripts in /etc/rcS.d/ are executed before the init process
6343 enters the single user state. When switching to runlevel 1, the state
6344 is in fact not ending in runlevel 1, but it passes through runlevel 1
6345 and end up in the single user mode (see /etc/rc1.d/S03single, which
6346 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
6347 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
6348 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6349 mode).&lt;/p&gt;
6350
6351 &lt;p&gt;This summary might make it clearer. When booting for the first
6352 time into single user mode, the following commands are executed:
6353 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
6354 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
6355 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
6356 trying to continue after visiting single user mode. Not all services
6357 are started again as they should, causing the machine to end up in an
6358 unpredicatble state. This is why Debian admins recommend rebooting
6359 after visiting single user mode.&lt;/p&gt;
6360
6361 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
6362 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
6363 to runlevel 1, the services started from /etc/rcS.d/ are not properly
6364 stopped when passing through the scripts in /etc/rc1.d/, and not
6365 started again when switching away from runlevel 1 to the runlevels
6366 2-5. I believe the problem is best fixed by moving all the scripts
6367 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
6368 functioning single user mode during boot.&lt;/p&gt;
6369
6370 &lt;p&gt;I have spent several years investigating the Debian boot system,
6371 and discovered this problem a few years ago. I suspect it originates
6372 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
6373 </description>
6374 </item>
6375
6376 <item>
6377 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
6378 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
6379 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
6380 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
6381 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
6382 are started from /etc/rcS.d/. In fact, there is a bite more of them
6383 than make sense, and this causes a few problems. What kind of
6384 problems, you might ask. There are at least two problems. The first
6385 is that it is not possible to recover a machine after switching to
6386 runlevel 1. One need to actually reboot to get the machine back to
6387 the expected state. The other is that single user boot will sometimes
6388 run into problems because some of the subsystems are activated before
6389 the root login is presented, causing problems when trying to recover a
6390 machine from a problem in that subsystem. A minor additional point is
6391 that moving more scripts out of rcS.d/ and into the other rc#.d/
6392 directories will increase the amount of scripts that can run in
6393 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
6394
6395 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
6396 scripts that _have_ to execute before the root login prompt is
6397 presented during a single user boot should go there. Everything else
6398 should go into the numeric runlevels. This means things like
6399 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6400 the numeric runlevels. Today in Debian, there are around 115 init.d
6401 scripts that are started from rcS.d/, and most of them should be moved
6402 out. Do your package have one of them? Please help us make single
6403 user and runlevel 1 better by moving it.&lt;/p&gt;
6404
6405 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
6406 etc. should still be started from rcS.d/, but there is for example no
6407 need to have the network enabled before the single user login prompt
6408 is presented.&lt;/p&gt;
6409
6410 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
6411 Debian systems working while scripts migrate and during upgrades, the
6412 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6413 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6414 and the next ones can only be moved when their dependencies have been
6415 moved first. This migration must be done sequentially while we ensure
6416 that the package system upgrade packages in the right order to keep
6417 the system state correct. This will require some coordination when it
6418 comes to network related packages, but most of the packages with
6419 scripts that should migrate do not have anything in rcS.d/ depending
6420 on them. Some packages have already been updated, like the sudo
6421 package, while others are still left to do. I wish I had time to work
6422 on this myself, but real live constrains make it unlikely that I will
6423 find time to push this forward.&lt;/p&gt;
6424 </description>
6425 </item>
6426
6427 <item>
6428 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
6429 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
6430 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
6431 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
6432 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
6433 mentioned the issues I believe should be improved in Debian for its
6434 desktop to be useful for more people. The use case for this is my
6435 parents, which are currently running Kubuntu which solve the
6436 issues.&lt;/p&gt;
6437
6438 &lt;p&gt;I suspect these four missing features are not very hard to
6439 implement. After all, they are present in Ubuntu, so if we wanted to
6440 do this in Debian we would have a source.&lt;/p&gt;
6441
6442 &lt;ol&gt;
6443
6444 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
6445 are new packages available for upgrades, a icon in the KDE status bar
6446 indicate this, and clicking on it will activate the simple upgrade
6447 tool to handle it. I have no problem guiding both of my parents
6448 through the process over the phone. If a kernel reboot is required,
6449 this too is indicated by the status bars and the upgrade tool. Last
6450 time I checked, nothing with the same features was working in KDE in
6451 Debian.&lt;/li&gt;
6452
6453 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
6454 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
6455 currently have a handler for, it will ask the user if the system
6456 should search for a package that would add support for this MIME type,
6457 and if the user say yes, the APT sources will be searched for packages
6458 advertising the MIME type in their control file (visible in the
6459 Packages file in the APT archive). If one or more packages are found,
6460 it is a simple click of the mouse to add support for the missing mime
6461 type. If the package require the user to accept some non-free
6462 license, this is explained to the user. The entire process make it
6463 more clear to the user why something do not work in the browser, and
6464 make the chances higher for the user to blame the web page authors and
6465 not the browser for any missing features.&lt;/li&gt;
6466
6467 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
6468 handlers.&lt;/strong&gt; When the media players encounter a format or codec
6469 it is not supporting, a dialog pop up asking the user if the system
6470 should search for a package that would add support for it. This
6471 happen with things like MP3, Windows Media or H.264. The selection
6472 and installation procedure is very similar to the Firefox browser
6473 plugin handling. This is as far as I know implemented using a
6474 gstreamer hook. The end result is that the user easily get access to
6475 the codecs that are present from the APT archives available, while
6476 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
6477
6478 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
6479 displaying a text/plain file in my Debian browser, it will propose to
6480 start emacs to show it. If I remember correctly, when doing the same
6481 in Kunbutu it show the file as a text file in the browser. At least I
6482 know Opera will show text files within the browser. I much prefer the
6483 latter behaviour.&lt;/li&gt;
6484
6485 &lt;/ol&gt;
6486
6487 &lt;p&gt;There are other nice features as well, like the simplified suite
6488 upgrader, but given that I am the one mostly doing the dist-upgrade,
6489 it do not matter much.&lt;/p&gt;
6490
6491 &lt;p&gt;I really hope we could get these features in place for the next
6492 Debian release. It would require the coordinated effort of several
6493 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
6494 </description>
6495 </item>
6496
6497 <item>
6498 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
6499 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
6500 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
6501 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
6502 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
6503 site is build on Debian/Squeeze, and this platform was chosen because
6504 I am most familiar with Debian (being a Debian Developer for around 10
6505 years) because it is the latest stable Debian release which should get
6506 security support for a few years.&lt;/p&gt;
6507
6508 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
6509 that are missing in Debian at the moment. It would be great if these
6510 modules were added to the Debian archive, allowing anyone to set up
6511 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
6512 in their own country using only Debian packages. The list of modules
6513 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
6514 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
6515 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6516 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6517 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6518 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6519 easier in the future.&lt;/p&gt;
6520
6521 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
6522 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
6523 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
6524 with the responsibility of tracking security problems, which I really
6525 do not have time for.&lt;/p&gt;
6526 </description>
6527 </item>
6528
6529 <item>
6530 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
6531 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
6532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
6533 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
6534 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
6535 posts have been in Norwegian the last few weeks, so here is a short
6536 update in English.&lt;/p&gt;
6537
6538 &lt;p&gt;The kids still keep me too busy to get much free software work
6539 done, but I did manage to organise a project to get a Norwegian port
6540 of the British service
6541 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
6542 and it has been running for a month now. The entire project has been
6543 organised by me and two others. Around Christmas we gathered sponsors
6544 to fund the development work. In January I drafted a contract with
6545 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
6546 and in February the development took place. Most of it involved
6547 converting the source to use GPS coordinates instead of British
6548 easting/northing, and the resulting code should be a lot easier to get
6549 running in any country by now. The Norwegian
6550 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
6551 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
6552 source and the source for administrative borders in Norway, and
6553 support for this had to be added/fixed.&lt;/p&gt;
6554
6555 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
6556 polishing the system before we announced it March 7th. The system is
6557 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
6558 problem reports in a few weeks. Soon we hope to announce the Android
6559 and iPhone versions making it even easier to report problems with the
6560 public infrastructure.&lt;/p&gt;
6561
6562 &lt;p&gt;Perhaps something to consider for those of you in countries without
6563 such service?&lt;/p&gt;
6564 </description>
6565 </item>
6566
6567 <item>
6568 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
6569 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
6570 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
6571 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
6572 <description>&lt;p&gt;The last few days I have looked at ways to track open security
6573 issues here at my work with the University of Oslo. My idea is that
6574 it should be possible to use the information about security issues
6575 available on the Internet, and check our locally
6576 maintained/distributed software against this information. It should
6577 allow us to verify that no known security issues are forgotten. The
6578 CVE database listing vulnerabilities seem like a great central point,
6579 and by using the package lists from Debian mapped to CVEs provided by
6580 the testing security team, I believed it should be possible to figure
6581 out which security holes were present in our free software
6582 collection.&lt;/p&gt;
6583
6584 &lt;p&gt;After reading up on the topic, it became obvious that the first
6585 building block is to be able to name software packages in a unique and
6586 consistent way across data sources. I considered several ways to do
6587 this, for example coming up with my own naming scheme like using URLs
6588 to project home pages or URLs to the Freshmeat entries, or using some
6589 existing naming scheme. And it seem like I am not the first one to
6590 come across this problem, as MITRE already proposed and implemented a
6591 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
6592 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
6593 software, hardware and other platform components. The CPE ids are
6594 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
6595 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
6596 issues for any CPE name. With this in place, all I need to do is to
6597 locate the CPE id for the software packages we use at the university.
6598 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
6599 NVD entry if a CVE for the package exist).&lt;/p&gt;
6600
6601 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
6602 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
6603 check out, one could look up
6604 &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
6605 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
6606 The most recent one is
6607 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
6608 and at the bottom of the NVD page for this vulnerability the complete
6609 list of affected versions is provided.&lt;/p&gt;
6610
6611 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
6612 for offline processing of issues. Using this dump, I&#39;ve written a
6613 small script taking a list of CPEs as input and list all CVEs
6614 affecting the packages represented by these CPEs. One give it CPEs
6615 with version numbers as specified above and get a list of open
6616 security issues out.&lt;/p&gt;
6617
6618 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
6619 information need to be high. For that to happen, I believe as many as
6620 possible need to use and contribute to the NVD database. I notice
6621 RHEL is providing
6622 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
6623 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
6624 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
6625
6626 &lt;p&gt;To get an idea about the quality for free software, I spent some
6627 time making it possible to compare the CVE database from Debian with
6628 the CVE database in NVD. The result look fairly good, but there are
6629 some inconsistencies in NVD (same software package having several
6630 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6631 Debian believe are affected by a CVE). Hope to find time to improve
6632 the quality of NVD, but that require being able to get in touch with
6633 someone maintaining it. So far my three emails with questions and
6634 corrections have not seen any reply, but I hope contact can be
6635 established soon.&lt;/p&gt;
6636
6637 &lt;p&gt;An interesting application for CPEs is cross platform package
6638 mapping. It would be useful to know which packages in for example
6639 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6640 this would be trivial if all linux distributions provided CPE entries
6641 for their packages.&lt;/p&gt;
6642 </description>
6643 </item>
6644
6645 <item>
6646 <title>Which module is loaded for a given PCI and USB device?</title>
6647 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
6648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
6649 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
6650 <description>&lt;p&gt;In the
6651 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
6652 package in Debian, there is a script to report useful information
6653 about the running hardware for use when people report missing
6654 information. One part of this script that I find very useful when
6655 debugging hardware problems, is the part mapping loaded kernel module
6656 to the PCI device it claims. It allow me to quickly see if the kernel
6657 module I expect is driving the hardware I am struggling with. To see
6658 the output, make sure discover-data is installed and run
6659 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
6660 one of my machines like this:&lt;/p&gt;
6661
6662 &lt;pre&gt;
6663 loaded modules:
6664 10de:03eb i2c_nforce2
6665 10de:03f1 ohci_hcd
6666 10de:03f2 ehci_hcd
6667 10de:03f0 snd_hda_intel
6668 10de:03ec pata_amd
6669 10de:03f6 sata_nv
6670 1022:1103 k8temp
6671 109e:036e bttv
6672 109e:0878 snd_bt87x
6673 11ab:4364 sky2
6674 &lt;/pre&gt;
6675
6676 &lt;p&gt;The code in question look like this, slightly modified for
6677 readability and to drop the output to file descriptor 3:&lt;/p&gt;
6678
6679 &lt;pre&gt;
6680 if [ -d /sys/bus/pci/devices/ ] ; then
6681 echo loaded pci modules:
6682 (
6683 cd /sys/bus/pci/devices/
6684 for address in * ; do
6685 if [ -d &quot;$address/driver/module&quot; ] ; then
6686 module=`cd $address/driver/module ; pwd -P | xargs basename`
6687 if grep -q &quot;^$module &quot; /proc/modules ; then
6688 address=$(echo $address |sed s/0000://)
6689 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
6690 echo &quot;$id $module&quot;
6691 fi
6692 fi
6693 done
6694 )
6695 echo
6696 fi
6697 &lt;/pre&gt;
6698
6699 &lt;p&gt;Similar code could be used to extract USB device module
6700 mappings:&lt;/p&gt;
6701
6702 &lt;pre&gt;
6703 if [ -d /sys/bus/usb/devices/ ] ; then
6704 echo loaded usb modules:
6705 (
6706 cd /sys/bus/usb/devices/
6707 for address in * ; do
6708 if [ -d &quot;$address/driver/module&quot; ] ; then
6709 module=`cd $address/driver/module ; pwd -P | xargs basename`
6710 if grep -q &quot;^$module &quot; /proc/modules ; then
6711 address=$(echo $address |sed s/0000://)
6712 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
6713 if [ &quot;$id&quot; ] ; then
6714 echo &quot;$id $module&quot;
6715 fi
6716 fi
6717 fi
6718 done
6719 )
6720 echo
6721 fi
6722 &lt;/pre&gt;
6723
6724 &lt;p&gt;This might perhaps be something to include in other tools as
6725 well.&lt;/p&gt;
6726 </description>
6727 </item>
6728
6729 <item>
6730 <title>How to test if a laptop is working with Linux</title>
6731 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
6732 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
6733 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
6734 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
6735 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
6736 batch of computers will work with Linux. Every year for the last few
6737 years the university have organised shared bid of a few thousand
6738 computers, and this year HP won the bid. Two different desktops and
6739 five different laptops are on the list this year. We in the UNIX
6740 group want to know which one of these computers work well with RHEL
6741 and Ubuntu, the two Linux distributions we currently handle at the
6742 university.&lt;/p&gt;
6743
6744 &lt;p&gt;My test method is simple, and I share it here to get feedback and
6745 perhaps inspire others to test hardware as well. To test, I PXE
6746 install the OS version of choice, and log in as my normal user and run
6747 a few applications and plug in selected pieces of hardware. When
6748 something fail, I make a note about this in the test matrix and move
6749 on. If I have some spare time I try to report the bug to the OS
6750 vendor, but as I only have the machines for a short time, I rarely
6751 have the time to do this for all the problems I find.&lt;/p&gt;
6752
6753 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
6754 I perform on a new model.&lt;/p&gt;
6755
6756 &lt;ul&gt;
6757
6758 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
6759 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6760 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
6761
6762 &lt;li&gt;Is X.org working? If the graphical login screen show up after
6763 installation, X.org is working.&lt;/li&gt;
6764
6765 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
6766 package mesa-utils on Ubuntu) and writing down the frames per second
6767 reported by the program.&lt;/li&gt;
6768
6769 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
6770 logging in, and if I can hear this the test is successful. If there
6771 are several audio exits on the machine, I try them all and check if
6772 the Gnome/KDE audio mixer can control where to send the sound. I
6773 normally test this by playing
6774 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
6775 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
6776
6777 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
6778 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
6779
6780 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
6781 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
6782
6783 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
6784 picture from the v4l device show up.&lt;/li&gt;
6785
6786 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6787 any bluetooth devices are discovered. In my office, I normally see a
6788 few.&lt;/li&gt;
6789
6790 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
6791 memory modules lying around, and stick them in and see if Gnome/KDE
6792 notice this.&lt;/li&gt;
6793
6794 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
6795 special button work, and if the laptop continue to work after
6796 resume.&lt;/li&gt;
6797
6798 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
6799 adjusting background light, switching on/off external video output,
6800 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6801 laptop to laptop, so I just write down which are working and which are
6802 not.&lt;/li&gt;
6803
6804 &lt;li&gt;Some laptops have smart card readers, finger print readers,
6805 acceleration sensors etc. I rarely test these, as I do not know how
6806 to quickly test if they are working or not, so I only document their
6807 existence.&lt;/li&gt;
6808
6809 &lt;/ul&gt;
6810
6811 &lt;p&gt;By now I suspect you are really curious what the test results are
6812 for the HP machines I am testing. I&#39;m not done yet, so I will report
6813 the test results later. For now I can report that HP 8100 Elite work
6814 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
6815 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
6816 can see, I have most machines left to test. One interesting
6817 observation is that Ubuntu Lucid has almost twice the frame rate than
6818 RHEL6 with glxgears. No idea why.&lt;/p&gt;
6819 </description>
6820 </item>
6821
6822 <item>
6823 <title>Some thoughts on BitCoins</title>
6824 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
6825 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
6826 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
6827 <description>&lt;p&gt;As I continue to explore
6828 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
6829 what properties the system have, and how it will be affected by laws
6830 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
6831
6832 &lt;p&gt;One interesting thing to note is that since the transactions are
6833 verified using a peer to peer network, all details about a transaction
6834 is known to everyone. This means that if a BitCoin address has been
6835 published like I did with mine in my initial post about BitCoin, it is
6836 possible for everyone to see how many BitCoins have been transfered to
6837 that address. There is even a web service to look at the details for
6838 all transactions. There I can see that my address
6839 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
6840 have received 16.06 Bitcoin, the
6841 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
6842 address of Simon Phipps have received 181.97 BitCoin and the address
6843 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
6844 of EFF have received 2447.38 BitCoins so far. Thank you to each and
6845 every one of you that donated bitcoins to support my activity. The
6846 fact that anyone can see how much money was transfered to a given
6847 address make it more obvious why the BitCoin community recommend to
6848 generate and hand out a new address for each transaction. I&#39;m told
6849 there is no way to track which addresses belong to a given person or
6850 organisation without the person or organisation revealing it
6851 themselves, as Simon, EFF and I have done.&lt;/p&gt;
6852
6853 &lt;p&gt;In Norway, and in most other countries, there are laws and
6854 regulations limiting how much money one can transfer across the border
6855 without declaring it. There are money laundering, tax and accounting
6856 laws and regulations I would expect to apply to the use of BitCoin.
6857 If the Skolelinux foundation
6858 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
6859 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
6860 normal bank transfers like EFF is doing, how should this be accounted?
6861 Given that it is impossible to know if money can cross the border or
6862 not, should everything or nothing be declared? What exchange rate
6863 should be used when calculating taxes? Would receivers have to pay
6864 income tax if the foundation were to pay Skolelinux contributors in
6865 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
6866
6867 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
6868 accepted by a lot of users. It must be possible to get easy access to
6869 the currency (as a wage or using currency exchanges), and it must be
6870 easy to spend it. At the moment BitCoin seem fairly easy to get
6871 access to, but there are very few places to spend it. I am not really
6872 a regular user of any of the vendor types currently accepting BitCoin,
6873 so I wonder when my kind of shop would start accepting BitCoins. I
6874 would like to buy electronics, travels and subway tickets, not herbs
6875 and books. :) The currency is young, and this will improve over time
6876 if it become popular, but I suspect regular banks will start to lobby
6877 to get BitCoin declared illegal if it become popular. I&#39;m sure they
6878 will claim it is helping fund terrorism and money laundering (which
6879 probably would be true, as is any currency in existence), but I
6880 believe the problems should be solved elsewhere and not by blaming
6881 currencies.&lt;/p&gt;
6882
6883 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
6884 CPU intensive process that depend on a bit of luck as well (as one is
6885 competing against all the other miners currently spending CPU cycles
6886 to see which one get the next lump of cash). The &quot;winner&quot; get 50
6887 BitCoin when this happen. Yesterday I came across the obvious way to
6888 join forces to increase ones changes of getting at least some coins,
6889 by coordinating the work on mining BitCoins across several machines
6890 and people, and sharing the result if one is lucky and get the 50
6891 BitCoins. Check out
6892 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
6893 if this sounds interesting. I have not had time to try to set up a
6894 machine to participate there yet, but have seen that running on ones
6895 own for a few days have not yield any BitCoins througth mining
6896 yet.&lt;/p&gt;
6897
6898 &lt;p&gt;Update 2010-12-15: Found an &lt;a
6899 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
6900 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
6901 it was interesting to read. The arguments presented seem to be
6902 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
6903 </description>
6904 </item>
6905
6906 <item>
6907 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
6908 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
6909 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
6910 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
6911 <description>&lt;p&gt;With this weeks lawless
6912 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
6913 attacks&lt;/a&gt; on Wikileak and
6914 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
6915 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
6916 not be trusted to handle money transactions.
6917 A blog post from
6918 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
6919 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
6920 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
6921 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
6922 some help from my friend to get it all running, and he even handed me
6923 some bitcoins to get started. I even donated a few bitcoins to Simon
6924 for helping me remember BitCoin.&lt;/p&gt;
6925
6926 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
6927 crypto-currency, decentralised and handled using peer-to-peer
6928 networks. It allows anonymous transactions and prohibits central
6929 control over the transactions, making it impossible for governments
6930 and companies alike to block donations and other transactions. The
6931 source is free software, and while the key dependency wxWidgets 2.9
6932 for the graphical user interface is missing in Debian, the command
6933 line client builds just fine. Hopefully Jonas
6934 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
6935 Debian&lt;/a&gt; soon.&lt;/p&gt;
6936
6937 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
6938 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
6939 bitcoins&lt;/a&gt; when selling services and goods, and there are even
6940 currency &quot;stock&quot; markets where the exchange rate is decided. There
6941 are not many users so far, but the concept seems promising. If you
6942 want to get started and lack a friend with any bitcoins to spare,
6943 you can even get
6944 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
6945 bitcoin at the time of writing). Use
6946 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
6947 on the current exchange rates.&lt;/p&gt;
6948
6949 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
6950 machines. If you want to support my activity, please send Bitcoin
6951 donations to the address
6952 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
6953 </description>
6954 </item>
6955
6956 <item>
6957 <title>Why isn&#39;t Debian Edu using VLC?</title>
6958 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
6959 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
6960 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
6961 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
6962 presented, and the winner among the multimedia player were VLC.
6963 Personally, I like VLC, and it is my player of choice when I first try
6964 to play a video file or stream. Only if VLC fail will I drag out
6965 gmplayer to see if it can do better. The reason is mostly the failure
6966 model and trust. When VLC fail, it normally pop up a error message
6967 reporting the problem. When mplayer fail, it normally segfault or
6968 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
6969
6970 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
6971 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6972 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
6973 plugin to play web videos seamlessly, and the VLC browser plugin is
6974 not very good. For example, it lack in-line control buttons, so there
6975 is no way for the user to pause the video. Also, when I
6976 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
6977 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
6978 failed on several video pages where mplayer based plugins worked. If
6979 the browser plugin for VLC was as good as the gecko-mediaplayer
6980 package (which uses mplayer), we would switch.&lt;/P&gt;
6981
6982 &lt;p&gt;While VLC is a good player, its user interface is slightly
6983 annoying. The most annoying feature is its inconsistent use of
6984 keyboard shortcuts. When the player is in full screen mode, its
6985 shortcuts are different from when it is playing the video in a window.
6986 For example, space only work as pause when in full screen mode. I
6987 wish it had consisten shortcuts and that space also would work when in
6988 window mode. Another nice shortcut in gmplayer is [enter] to restart
6989 the current video. It is very nice when playing short videos from the
6990 web and want to restart it when new people arrive to have a look at
6991 what is going on.&lt;/p&gt;
6992 </description>
6993 </item>
6994
6995 <item>
6996 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
6997 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
6998 <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>
6999 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
7000 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
7001 upgrade testing of the
7002 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7003 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
7004 This seem like a very good idea, so I adjusted by test scripts and
7005 can now present the updated result from today:&lt;/p&gt;
7006
7007 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7008
7009 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7010
7011 &lt;blockquote&gt;&lt;p&gt;
7012 apache2.2-bin
7013 aptdaemon
7014 baobab
7015 binfmt-support
7016 browser-plugin-gnash
7017 cheese-common
7018 cli-common
7019 cups-pk-helper
7020 dmz-cursor-theme
7021 empathy
7022 empathy-common
7023 freedesktop-sound-theme
7024 freeglut3
7025 gconf-defaults-service
7026 gdm-themes
7027 gedit-plugins
7028 geoclue
7029 geoclue-hostip
7030 geoclue-localnet
7031 geoclue-manual
7032 geoclue-yahoo
7033 gnash
7034 gnash-common
7035 gnome
7036 gnome-backgrounds
7037 gnome-cards-data
7038 gnome-codec-install
7039 gnome-core
7040 gnome-desktop-environment
7041 gnome-disk-utility
7042 gnome-screenshot
7043 gnome-search-tool
7044 gnome-session-canberra
7045 gnome-system-log
7046 gnome-themes-extras
7047 gnome-themes-more
7048 gnome-user-share
7049 gstreamer0.10-fluendo-mp3
7050 gstreamer0.10-tools
7051 gtk2-engines
7052 gtk2-engines-pixbuf
7053 gtk2-engines-smooth
7054 hamster-applet
7055 libapache2-mod-dnssd
7056 libapr1
7057 libaprutil1
7058 libaprutil1-dbd-sqlite3
7059 libaprutil1-ldap
7060 libart2.0-cil
7061 libboost-date-time1.42.0
7062 libboost-python1.42.0
7063 libboost-thread1.42.0
7064 libchamplain-0.4-0
7065 libchamplain-gtk-0.4-0
7066 libcheese-gtk18
7067 libclutter-gtk-0.10-0
7068 libcryptui0
7069 libdiscid0
7070 libelf1
7071 libepc-1.0-2
7072 libepc-common
7073 libepc-ui-1.0-2
7074 libfreerdp-plugins-standard
7075 libfreerdp0
7076 libgconf2.0-cil
7077 libgdata-common
7078 libgdata7
7079 libgdu-gtk0
7080 libgee2
7081 libgeoclue0
7082 libgexiv2-0
7083 libgif4
7084 libglade2.0-cil
7085 libglib2.0-cil
7086 libgmime2.4-cil
7087 libgnome-vfs2.0-cil
7088 libgnome2.24-cil
7089 libgnomepanel2.24-cil
7090 libgpod-common
7091 libgpod4
7092 libgtk2.0-cil
7093 libgtkglext1
7094 libgtksourceview2.0-common
7095 libmono-addins-gui0.2-cil
7096 libmono-addins0.2-cil
7097 libmono-cairo2.0-cil
7098 libmono-corlib2.0-cil
7099 libmono-i18n-west2.0-cil
7100 libmono-posix2.0-cil
7101 libmono-security2.0-cil
7102 libmono-sharpzip2.84-cil
7103 libmono-system2.0-cil
7104 libmtp8
7105 libmusicbrainz3-6
7106 libndesk-dbus-glib1.0-cil
7107 libndesk-dbus1.0-cil
7108 libopal3.6.8
7109 libpolkit-gtk-1-0
7110 libpt2.6.7
7111 libpython2.6
7112 librpm1
7113 librpmio1
7114 libsdl1.2debian
7115 libsrtp0
7116 libssh-4
7117 libtelepathy-farsight0
7118 libtelepathy-glib0
7119 libtidy-0.99-0
7120 media-player-info
7121 mesa-utils
7122 mono-2.0-gac
7123 mono-gac
7124 mono-runtime
7125 nautilus-sendto
7126 nautilus-sendto-empathy
7127 p7zip-full
7128 pkg-config
7129 python-aptdaemon
7130 python-aptdaemon-gtk
7131 python-axiom
7132 python-beautifulsoup
7133 python-bugbuddy
7134 python-clientform
7135 python-coherence
7136 python-configobj
7137 python-crypto
7138 python-cupshelpers
7139 python-elementtree
7140 python-epsilon
7141 python-evolution
7142 python-feedparser
7143 python-gdata
7144 python-gdbm
7145 python-gst0.10
7146 python-gtkglext1
7147 python-gtksourceview2
7148 python-httplib2
7149 python-louie
7150 python-mako
7151 python-markupsafe
7152 python-mechanize
7153 python-nevow
7154 python-notify
7155 python-opengl
7156 python-openssl
7157 python-pam
7158 python-pkg-resources
7159 python-pyasn1
7160 python-pysqlite2
7161 python-rdflib
7162 python-serial
7163 python-tagpy
7164 python-twisted-bin
7165 python-twisted-conch
7166 python-twisted-core
7167 python-twisted-web
7168 python-utidylib
7169 python-webkit
7170 python-xdg
7171 python-zope.interface
7172 remmina
7173 remmina-plugin-data
7174 remmina-plugin-rdp
7175 remmina-plugin-vnc
7176 rhythmbox-plugin-cdrecorder
7177 rhythmbox-plugins
7178 rpm-common
7179 rpm2cpio
7180 seahorse-plugins
7181 shotwell
7182 software-center
7183 system-config-printer-udev
7184 telepathy-gabble
7185 telepathy-mission-control-5
7186 telepathy-salut
7187 tomboy
7188 totem
7189 totem-coherence
7190 totem-mozilla
7191 totem-plugins
7192 transmission-common
7193 xdg-user-dirs
7194 xdg-user-dirs-gtk
7195 xserver-xephyr
7196 &lt;/p&gt;&lt;/blockquote&gt;
7197
7198 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7199
7200 &lt;blockquote&gt;&lt;p&gt;
7201 cheese
7202 ekiga
7203 eog
7204 epiphany-extensions
7205 evolution-exchange
7206 fast-user-switch-applet
7207 file-roller
7208 gcalctool
7209 gconf-editor
7210 gdm
7211 gedit
7212 gedit-common
7213 gnome-games
7214 gnome-games-data
7215 gnome-nettool
7216 gnome-system-tools
7217 gnome-themes
7218 gnuchess
7219 gucharmap
7220 guile-1.8-libs
7221 libavahi-ui0
7222 libdmx1
7223 libgalago3
7224 libgtk-vnc-1.0-0
7225 libgtksourceview2.0-0
7226 liblircclient0
7227 libsdl1.2debian-alsa
7228 libspeexdsp1
7229 libsvga1
7230 rhythmbox
7231 seahorse
7232 sound-juicer
7233 system-config-printer
7234 totem-common
7235 transmission-gtk
7236 vinagre
7237 vino
7238 &lt;/p&gt;&lt;/blockquote&gt;
7239
7240 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7241
7242 &lt;blockquote&gt;&lt;p&gt;
7243 gstreamer0.10-gnomevfs
7244 &lt;/p&gt;&lt;/blockquote&gt;
7245
7246 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7247
7248 &lt;blockquote&gt;&lt;p&gt;
7249 [nothing]
7250 &lt;/p&gt;&lt;/blockquote&gt;
7251
7252 &lt;p&gt;This is for KDE:&lt;/p&gt;
7253
7254 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7255
7256 &lt;blockquote&gt;&lt;p&gt;
7257 ksmserver
7258 &lt;/p&gt;&lt;/blockquote&gt;
7259
7260 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7261
7262 &lt;blockquote&gt;&lt;p&gt;
7263 kwin
7264 network-manager-kde
7265 &lt;/p&gt;&lt;/blockquote&gt;
7266
7267 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7268
7269 &lt;blockquote&gt;&lt;p&gt;
7270 arts
7271 dolphin
7272 freespacenotifier
7273 google-gadgets-gst
7274 google-gadgets-xul
7275 kappfinder
7276 kcalc
7277 kcharselect
7278 kde-core
7279 kde-plasma-desktop
7280 kde-standard
7281 kde-window-manager
7282 kdeartwork
7283 kdeartwork-emoticons
7284 kdeartwork-style
7285 kdeartwork-theme-icon
7286 kdebase
7287 kdebase-apps
7288 kdebase-workspace
7289 kdebase-workspace-bin
7290 kdebase-workspace-data
7291 kdeeject
7292 kdelibs
7293 kdeplasma-addons
7294 kdeutils
7295 kdewallpapers
7296 kdf
7297 kfloppy
7298 kgpg
7299 khelpcenter4
7300 kinfocenter
7301 konq-plugins-l10n
7302 konqueror-nsplugins
7303 kscreensaver
7304 kscreensaver-xsavers
7305 ktimer
7306 kwrite
7307 libgle3
7308 libkde4-ruby1.8
7309 libkonq5
7310 libkonq5-templates
7311 libnetpbm10
7312 libplasma-ruby
7313 libplasma-ruby1.8
7314 libqt4-ruby1.8
7315 marble-data
7316 marble-plugins
7317 netpbm
7318 nuvola-icon-theme
7319 plasma-dataengines-workspace
7320 plasma-desktop
7321 plasma-desktopthemes-artwork
7322 plasma-runners-addons
7323 plasma-scriptengine-googlegadgets
7324 plasma-scriptengine-python
7325 plasma-scriptengine-qedje
7326 plasma-scriptengine-ruby
7327 plasma-scriptengine-webkit
7328 plasma-scriptengines
7329 plasma-wallpapers-addons
7330 plasma-widget-folderview
7331 plasma-widget-networkmanagement
7332 ruby
7333 sweeper
7334 update-notifier-kde
7335 xscreensaver-data-extra
7336 xscreensaver-gl
7337 xscreensaver-gl-extra
7338 xscreensaver-screensaver-bsod
7339 &lt;/p&gt;&lt;/blockquote&gt;
7340
7341 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7342
7343 &lt;blockquote&gt;&lt;p&gt;
7344 ark
7345 google-gadgets-common
7346 google-gadgets-qt
7347 htdig
7348 kate
7349 kdebase-bin
7350 kdebase-data
7351 kdepasswd
7352 kfind
7353 klipper
7354 konq-plugins
7355 konqueror
7356 ksysguard
7357 ksysguardd
7358 libarchive1
7359 libcln6
7360 libeet1
7361 libeina-svn-06
7362 libggadget-1.0-0b
7363 libggadget-qt-1.0-0b
7364 libgps19
7365 libkdecorations4
7366 libkephal4
7367 libkonq4
7368 libkonqsidebarplugin4a
7369 libkscreensaver5
7370 libksgrd4
7371 libksignalplotter4
7372 libkunitconversion4
7373 libkwineffects1a
7374 libmarblewidget4
7375 libntrack-qt4-1
7376 libntrack0
7377 libplasma-geolocation-interface4
7378 libplasmaclock4a
7379 libplasmagenericshell4
7380 libprocesscore4a
7381 libprocessui4a
7382 libqalculate5
7383 libqedje0a
7384 libqtruby4shared2
7385 libqzion0a
7386 libruby1.8
7387 libscim8c2a
7388 libsmokekdecore4-3
7389 libsmokekdeui4-3
7390 libsmokekfile3
7391 libsmokekhtml3
7392 libsmokekio3
7393 libsmokeknewstuff2-3
7394 libsmokeknewstuff3-3
7395 libsmokekparts3
7396 libsmokektexteditor3
7397 libsmokekutils3
7398 libsmokenepomuk3
7399 libsmokephonon3
7400 libsmokeplasma3
7401 libsmokeqtcore4-3
7402 libsmokeqtdbus4-3
7403 libsmokeqtgui4-3
7404 libsmokeqtnetwork4-3
7405 libsmokeqtopengl4-3
7406 libsmokeqtscript4-3
7407 libsmokeqtsql4-3
7408 libsmokeqtsvg4-3
7409 libsmokeqttest4-3
7410 libsmokeqtuitools4-3
7411 libsmokeqtwebkit4-3
7412 libsmokeqtxml4-3
7413 libsmokesolid3
7414 libsmokesoprano3
7415 libtaskmanager4a
7416 libtidy-0.99-0
7417 libweather-ion4a
7418 libxklavier16
7419 libxxf86misc1
7420 okteta
7421 oxygencursors
7422 plasma-dataengines-addons
7423 plasma-scriptengine-superkaramba
7424 plasma-widget-lancelot
7425 plasma-widgets-addons
7426 plasma-widgets-workspace
7427 polkit-kde-1
7428 ruby1.8
7429 systemsettings
7430 update-notifier-common
7431 &lt;/p&gt;&lt;/blockquote&gt;
7432
7433 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
7434 aptitude a bit more similar, but there are still quite a lott of
7435 differences. I have no idea what packages should be installed after
7436 the upgrade, but hope those that do can have a look.&lt;/p&gt;
7437 </description>
7438 </item>
7439
7440 <item>
7441 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
7442 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
7443 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
7444 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
7445 <description>&lt;p&gt;Most of the computers in use by the
7446 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
7447 are virtual machines. And they have been Xen machines running on a
7448 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
7449 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
7450 bit harder that it could have been, because we set up the Xen virtual
7451 machines to get the virtual partitions from LVM, which as far as I
7452 know is not supported by KVM. So to migrate, we had to convert
7453 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
7454
7455 &lt;p&gt;I found
7456 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
7457 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
7458 migration. It uses qemu-img from the qemu package to make the disk
7459 image, parted to partition it, losetup and kpartx to present the disk
7460 image partions as devices, and dd to copy the data. I NFS mounted the
7461 new servers storage area on the old server to do the migration.&lt;/p&gt;
7462
7463 &lt;pre&gt;
7464 #!/bin/sh
7465
7466 # Based on
7467 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7468
7469 set -e
7470 set -x
7471
7472 if [ -z &quot;$1&quot; ] ; then
7473 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
7474 exit 1
7475 else
7476 host=&quot;$1&quot;
7477 fi
7478
7479 if [ ! -e /dev/vg_data/$host-disk ] ; then
7480 echo &quot;error: unable to find LVM volume for $host&quot;
7481 exit 1
7482 fi
7483
7484 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7485 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
7486 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
7487 totalsize=$(( ( $disksize + $swapsize ) ))
7488
7489 img=$host.img
7490 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
7491 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7492
7493 parted $img mklabel msdos
7494 parted $img mkpart primary linux-swap 0 $disksize
7495 parted $img mkpart primary ext2 $disksize $totalsize
7496 parted $img set 1 boot on
7497
7498 modprobe dm-mod
7499 losetup /dev/loop0 $img
7500 kpartx -a /dev/loop0
7501
7502 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
7503 fsck.ext3 -f /dev/mapper/loop0p1 || true
7504 mkswap /dev/mapper/loop0p2
7505
7506 kpartx -d /dev/loop0
7507 losetup -d /dev/loop0
7508 &lt;/pre&gt;
7509
7510 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
7511 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
7512
7513 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
7514 the new disk image attached, installed grub-pc and linux-image-686 and
7515 set up grub to boot from the disk image. After this, the KVM machines
7516 seem to work just fine.&lt;/p&gt;
7517 </description>
7518 </item>
7519
7520 <item>
7521 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
7522 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
7523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
7524 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
7525 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
7526 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7527 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
7528 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
7529
7530 &lt;p&gt;I still do not know what a correct migration should look like, so I
7531 report any differences between apt and aptitude and hope someone else
7532 can see if anything should be changed.&lt;/p&gt;
7533
7534 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7535
7536 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7537
7538 &lt;blockquote&gt;&lt;p&gt;
7539 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7540 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
7541 dmz-cursor-theme empathy empathy-common finger
7542 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7543 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7544 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7545 gnome-cards-data gnome-codec-install gnome-core
7546 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7547 gnome-search-tool gnome-session-canberra gnome-spell
7548 gnome-system-log gnome-themes-extras gnome-themes-more
7549 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7550 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7551 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7552 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7553 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
7554 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
7555 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
7556 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
7557 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
7558 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7559 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
7560 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7561 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7562 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7563 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7564 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7565 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7566 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7567 libmono-security2.0-cil libmono-sharpzip2.84-cil
7568 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
7569 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
7570 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
7571 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
7572 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
7573 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
7574 libxalan2-java libxerces2-java media-player-info mesa-utils
7575 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
7576 nautilus-sendto-empathy openoffice.org-writer2latex
7577 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
7578 python-aptdaemon python-aptdaemon-gtk python-axiom
7579 python-beautifulsoup python-bugbuddy python-clientform
7580 python-coherence python-configobj python-crypto python-cupshelpers
7581 python-cupsutils python-eggtrayicon python-elementtree
7582 python-epsilon python-evolution python-feedparser python-gdata
7583 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7584 python-gtksourceview2 python-httplib2 python-louie python-mako
7585 python-markupsafe python-mechanize python-nevow python-notify
7586 python-opengl python-openssl python-pam python-pkg-resources
7587 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7588 python-tagpy python-twisted-bin python-twisted-conch
7589 python-twisted-core python-twisted-web python-utidylib python-webkit
7590 python-xdg python-zope.interface remmina remmina-plugin-data
7591 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7592 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7593 software-center svgalibg1 system-config-printer-udev
7594 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
7595 totem totem-coherence totem-mozilla totem-plugins
7596 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7597 zip
7598 &lt;/p&gt;&lt;/blockquote&gt;
7599
7600 Installed using apt-get, removed with aptitude
7601
7602 &lt;blockquote&gt;&lt;p&gt;
7603 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7604 epiphany-extensions epiphany-gecko evolution-exchange
7605 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7606 gedit-common gnome-app-install gnome-games gnome-games-data
7607 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7608 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7609 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7610 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
7611 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
7612 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
7613 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
7614 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7615 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7616 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7617 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
7618 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
7619 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7620 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7621 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7622 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7623 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
7624 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
7625 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
7626 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
7627 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
7628 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7629 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7630 sound-juicer swfdec-gnome system-config-printer totem-common
7631 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7632 &lt;/p&gt;&lt;/blockquote&gt;
7633
7634 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7635
7636 &lt;blockquote&gt;&lt;p&gt;
7637 gstreamer0.10-gnomevfs
7638 &lt;/p&gt;&lt;/blockquote&gt;
7639
7640 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7641
7642 &lt;blockquote&gt;&lt;p&gt;
7643 [nothing]
7644 &lt;/p&gt;&lt;/blockquote&gt;
7645
7646 &lt;p&gt;This is for KDE:&lt;/p&gt;
7647
7648 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7649
7650 &lt;blockquote&gt;&lt;p&gt;
7651 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
7652 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7653 ghostscript-x git gnome-audio gnugo granatier gs-common
7654 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7655 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7656 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7657 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7658 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7659 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7660 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7661 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7662 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7663 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7664 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7665 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
7666 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7667 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7668 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7669 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7670 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7671 libkrossui4 libmailtools-perl libmime-tools-perl
7672 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7673 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7674 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7675 lirc luatex marble networkstatus noatun-plugins
7676 openoffice.org-writer2latex palapeli palapeli-data parley
7677 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7678 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7679 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7680 ttf-sazanami-gothic
7681 &lt;/p&gt;&lt;/blockquote&gt;
7682
7683 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7684
7685 &lt;blockquote&gt;&lt;p&gt;
7686 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7687 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7688 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7689 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7690 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7691 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7692 kitchensync kiten kjumpingcube klatin klettres klickety klines
7693 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7694 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7695 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7696 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7697 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7698 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7699 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7700 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7701 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7702 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
7703 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
7704 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7705 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
7706 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
7707 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7708 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7709 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7710 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7711 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7712 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7713 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
7714 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
7715 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7716 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7717 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7718 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7719 &lt;/p&gt;&lt;/blockquote&gt;
7720
7721 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7722
7723 &lt;blockquote&gt;&lt;p&gt;
7724 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7725 kdeartwork kdebase kdebase-apps kdebase-workspace
7726 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7727 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7728 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7729 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7730 xscreensaver-screensaver-bsod
7731 &lt;/p&gt;&lt;/blockquote&gt;
7732
7733 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7734
7735 &lt;blockquote&gt;&lt;p&gt;
7736 kdebase-bin konq-plugins konqueror
7737 &lt;/p&gt;&lt;/blockquote&gt;
7738 </description>
7739 </item>
7740
7741 <item>
7742 <title>Gnash buildbot slave and Debian kfreebsd</title>
7743 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
7744 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
7745 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
7746 <description>&lt;p&gt;Answering
7747 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
7748 call from the Gnash project&lt;/a&gt; for
7749 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
7750 current source, I have set up a virtual KVM machine on the Debian
7751 Edu/Skolelinux virtualization host to test the git source on
7752 Debian/Squeeze. I hope this can help the developers in getting new
7753 releases out more often.&lt;/p&gt;
7754
7755 &lt;p&gt;As the developers want less main-stream build platforms tested to,
7756 I have considered setting up a &lt;a
7757 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
7758 machine as well. I have also considered using the kfreebsd
7759 architecture in Debian as a file server in NUUG to get access to the 5
7760 TB zfs volume we currently use to store DV video. Because of this, I
7761 finally got around to do a test installation of Debian/Squeeze with
7762 kfreebsd. Installation went fairly smooth, thought I noticed some
7763 visual glitches in the cdebconf dialogs (black cursor left on the
7764 screen at random locations). Have not gotten very far with the
7765 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7766 fatal problem. Have to spend some more time on it to see if it is
7767 useful as a file server for NUUG. Will try to find time to set up a
7768 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
7769 </description>
7770 </item>
7771
7772 <item>
7773 <title>Debian in 3D</title>
7774 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
7775 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
7776 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
7777 <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;
7778
7779 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
7780 3D linked in from
7781 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
7782 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
7783 </description>
7784 </item>
7785
7786 <item>
7787 <title>Software updates 2010-10-24</title>
7788 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
7789 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
7790 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
7791 <description>&lt;p&gt;Some updates.&lt;/p&gt;
7792
7793 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
7794 raise money for the project is going well. The lower limit of 10
7795 signers was reached in 24 hours, and so far 13 people have signed it.
7796 More signers and more funding is most welcome, and I am really curious
7797 how far we can get before the time limit of December 24 is reached.
7798 :)&lt;/p&gt;
7799
7800 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
7801 about what appear to be a great code coverage tool capable of
7802 generating code coverage stats without any changes to the source code.
7803 It is called
7804 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
7805 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
7806 It is missing in Debian, but the git source built just fine in Squeeze
7807 after I installed libelf-dev, libdwarf-dev, pkg-config and
7808 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7809 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
7810
7811 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
7812 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
7813 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
7814 alpha test release of the Squeeze based Debian Edu /
7815 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
7816 release. Give it a try if you need a complete linux solution for your
7817 school, including central infrastructure server, workstations, thin
7818 client servers and diskless workstations. A nice touch added
7819 yesterday is RDP support on the thin client servers, for windows
7820 clients to get a Linux desktop on request.&lt;/p&gt;
7821 </description>
7822 </item>
7823
7824 <item>
7825 <title>Some notes on Flash in Debian and Debian Edu</title>
7826 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
7827 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
7828 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
7829 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
7830 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
7831 second most popular used package that is missing in Debian. The sixth
7832 most popular is flashplayer-mozilla. This is a clear indication that
7833 working flash is important for Debian users. Around 10 percent of the
7834 users submitting data to popcon.debian.org have this package
7835 installed.&lt;/p&gt;
7836
7837 &lt;p&gt;In the report written by Lars Risan in August 2008
7838&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
7839 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7840 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
7841 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
7842 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
7843 web sites require Flash to work, and lacking working Flash support in
7844 the web browser and the problems with installing it was perceived as a
7845 good reason to stay with Windows.&lt;/p&gt;
7846
7847 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
7848 said to be the retarded cousin that did not really understand
7849 everything you told him but could work fairly well. This was a
7850 comment regarding the problems Linux have with proprietary formats and
7851 non-standard web pages, and is sad because it exposes a fairly common
7852 understanding of whose fault it is if web pages that only work in for
7853 example Internet Explorer 6 fail to work on Firefox, and funny because
7854 it explain very well how annoying it is for users when Linux
7855 distributions do not work with the documents they receive or the web
7856 pages they want to visit.&lt;/p&gt;
7857
7858 &lt;p&gt;This is part of the reason why I believe it is important for Debian
7859 and Debian Edu to have a well working Flash implementation in the
7860 distribution, to get at least popular sites as Youtube and Google
7861 Video to working out of the box. For Squeeze, Debian have the chance
7862 to include the latest version of Gnash that will make this happen, as
7863 the new release 0.8.8 was published a few weeks ago and is resting in
7864 unstable. The new version work with more sites that version 0.8.7.
7865 The Gnash maintainers have asked for a freeze exception, but the
7866 release team have not had time to reply to it yet. I hope they agree
7867 with me that Flash is important for the Debian desktop users, and thus
7868 accept the new package into Squeeze.&lt;/p&gt;
7869 </description>
7870 </item>
7871
7872 <item>
7873 <title>Circular package dependencies harms apt recovery</title>
7874 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
7875 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
7876 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
7877 <description>&lt;p&gt;I discovered this while doing
7878 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
7879 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
7880 in Debian still got circular dependencies, and it is often claimed
7881 that apt and aptitude should be able to handle this just fine, but
7882 some times these dependency loops causes apt to fail.&lt;/p&gt;
7883
7884 &lt;p&gt;An example is from todays
7885 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
7886 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
7887 causes perl-modules to fail to upgrade. The cause is simple. If a
7888 package fail to unpack, then only part of packages with the circular
7889 dependency might end up being unpacked when unpacking aborts, and the
7890 ones already unpacked will fail to configure in the recovery phase
7891 because its dependencies are unavailable.&lt;/p&gt;
7892
7893 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
7894
7895 &lt;blockquote&gt;&lt;pre&gt;
7896 dpkg: dependency problems prevent configuration of perl-modules:
7897 perl-modules depends on perl (&gt;= 5.10.1-1); however:
7898 Version of perl on system is 5.10.0-19lenny2.
7899 dpkg: error processing perl-modules (--configure):
7900 dependency problems - leaving unconfigured
7901 &lt;/pre&gt;&lt;/blockquote&gt;
7902
7903 &lt;p&gt;The perl/perl-modules circular dependency is already
7904 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
7905 hopefully be solved as soon as possible, but it is not the only one,
7906 and each one of these loops in the dependency tree can cause similar
7907 failures. Of course, they only occur when there are bugs in other
7908 packages causing the unpacking to fail, but it is rather nasty when
7909 the failure of one package causes the problem to become worse because
7910 of dependency loops.&lt;/p&gt;
7911
7912 &lt;p&gt;Thanks to
7913 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
7914 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
7915 dependencies
7916 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
7917 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
7918
7919 &lt;p&gt;Todays testing also exposed a bug in
7920 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
7921 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
7922 apt-get and aptitude, the latter possibly caused by some circular
7923 dependency. Reported both to BTS to try to get someone to look at
7924 it.&lt;/p&gt;
7925 </description>
7926 </item>
7927
7928 <item>
7929 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
7930 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
7931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
7932 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
7933 <description>&lt;p&gt;This is a
7934 &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;
7935 on my
7936 &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
7937 work&lt;/a&gt; on
7938 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
7939 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
7940
7941 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
7942 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7943 and dhcp3-server-ldap in Debian use the LDAP server. The two
7944 implementations are quite different in how they use LDAP.&lt;/p&gt;
7945
7946 To get this information, I started slapd with debugging enabled and
7947 dumped the debug output to a file to get the LDAP searches performed
7948 on a Debian Edu main-server. Here is a summary.
7949
7950 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
7951
7952 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
7953 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
7954 the web.
7955
7956 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
7957 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
7958 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
7959 reverse entries are in two different subtrees in LDAP with a structure
7960 based on the DNS names, as in tjener.intern and
7961 2.2.0.10.in-addr.arpa.&lt;/p&gt;
7962
7963 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
7964 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
7965 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
7966 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
7967 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
7968 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
7969 forward entries, it is looking for attributes named dnsttl, arecord,
7970 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7971 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7972 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7973 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7974 spfrecord and modifytimestamp. For reverse entries it is looking for
7975 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7976 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7977 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7978 ldapsearch commands could look like this:&lt;/p&gt;
7979
7980 &lt;blockquote&gt;&lt;pre&gt;
7981 ldapsearch -h ldap \
7982 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7983 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
7984 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7985 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7986 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7987 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7988
7989 ldapsearch -h ldap \
7990 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7991 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
7992 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7993 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7994 srvrecord naptrrecord modifytimestamp
7995 &lt;/pre&gt;&lt;/blockquote&gt;
7996
7997 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
7998 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7999 example LDAP objects used there. In addition to these objects, the
8000 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8001 also exist.&lt;/p&gt;
8002
8003 &lt;blockquote&gt;&lt;pre&gt;
8004 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8005 objectclass: top
8006 objectclass: dnsdomain
8007 objectclass: domainrelatedobject
8008 dc: tjener
8009 arecord: 10.0.2.2
8010 associateddomain: tjener.intern
8011
8012 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8013 objectclass: top
8014 objectclass: dnsdomain2
8015 objectclass: domainrelatedobject
8016 dc: 2
8017 ptrrecord: tjener.intern
8018 associateddomain: 2.2.0.10.in-addr.arpa
8019 &lt;/pre&gt;&lt;/blockquote&gt;
8020
8021 &lt;p&gt;In strict mode, the server behaves differently. When looking for
8022 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
8023 same base as in the tree mode for a object with filter
8024 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
8025 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8026 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8027 naptrrecord and modifytimestamp. For reverse entires it also do a
8028 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
8029 and the requested attributes are associateddomain, dnsttl and
8030 modifytimestamp. In short, in strict mode the objects with ptrrecord
8031 go away, and the arecord attribute in the forward object is used
8032 instead.&lt;/p&gt;
8033
8034 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
8035 like this:&lt;/p&gt;
8036
8037 &lt;blockquote&gt;&lt;pre&gt;
8038 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8039 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8040 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8041 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8042 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8043 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8044
8045 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8046 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
8047 &lt;/pre&gt;&lt;/blockquote&gt;
8048
8049 &lt;p&gt;In addition to the forward and reverse searches , there is also a
8050 search for SOA records, which behave similar to the forward and
8051 reverse lookups.&lt;/p&gt;
8052
8053 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
8054 specify any objectclass names, and instead look for the attributes it
8055 need to generate a DNS reply. This make it able to work with any
8056 objectclass that provide the needed attributes.&lt;/p&gt;
8057
8058 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
8059 dnsdomain2 schemas. The latter is used for reverse entries like
8060 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
8061
8062 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
8063 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8064 attributes) and domainrelatedobject (for associatedDomain). The use
8065 of structural object classes make it impossible to combine these
8066 classes with the object classes used by DHCP.&lt;/p&gt;
8067
8068 &lt;p&gt;There are other schemas that could be used too, for example the
8069 dnszone structural object class used by Gosa and bind-sdb for the DNS
8070 attributes combined with the domainrelatedobject object class, but in
8071 this case some unused attributes would have to be included as well
8072 (zonename and relativedomainname).&lt;/p&gt;
8073
8074 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
8075 mode and not use any of the existing objectclasses (dnsdomain,
8076 dnsdomain2 and dnszone) when one want to combine the DNS information
8077 with DHCP information, and instead create a auxiliary object class
8078 defined something like this (using the attributes defined for
8079 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
8080
8081 &lt;blockquote&gt;&lt;pre&gt;
8082 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
8083 SUP top
8084 AUXILIARY
8085 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8086 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8087 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8088 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8089 A6Record $ DNAMERecord
8090 ))
8091 &lt;/pre&gt;&lt;/blockquote&gt;
8092
8093 &lt;p&gt;This will allow any object to become a DNS entry when combined with
8094 the domainrelatedobject object class, and allow any entity to include
8095 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
8096 developers asking for their view on this schema and if they are
8097 interested in providing such schema with PowerDNS, and I hope my
8098 message will be accepted into their mailing list soon.&lt;/p&gt;
8099
8100 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
8101
8102 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
8103 the object attributes, and then uses the attributes it want. This
8104 make it harder to figure out exactly what attributes are used, but
8105 thanks to the working example in Debian Edu I can at least get an idea
8106 what is needed without having to read the source code.&lt;/p&gt;
8107
8108 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
8109 search filter to use to locate the correct dhcpServer entity is
8110 stored. These are the relevant entries from
8111 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
8112
8113 &lt;blockquote&gt;&lt;pre&gt;
8114 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
8115 ldap-dhcp-server-cn &quot;dhcp&quot;;
8116 &lt;/pre&gt;&lt;/blockquote&gt;
8117
8118 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
8119 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
8120 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
8121 search result is this entry:&lt;/p&gt;
8122
8123 &lt;blockquote&gt;&lt;pre&gt;
8124 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8125 cn: dhcp
8126 objectClass: top
8127 objectClass: dhcpServer
8128 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8129 &lt;/pre&gt;&lt;/blockquote&gt;
8130
8131 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
8132 subtree with DHCP configuration. The DHCP configuration subtree base
8133 is located using a base scope search with base &quot;cn=DHCP
8134 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
8135 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
8136 The search result is this entry:&lt;/p&gt;
8137
8138 &lt;blockquote&gt;&lt;pre&gt;
8139 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8140 cn: DHCP Config
8141 objectClass: top
8142 objectClass: dhcpService
8143 objectClass: dhcpOptions
8144 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8145 dhcpStatements: ddns-update-style none
8146 dhcpStatements: authoritative
8147 dhcpOption: smtp-server code 69 = array of ip-address
8148 dhcpOption: www-server code 72 = array of ip-address
8149 dhcpOption: wpad-url code 252 = text
8150 &lt;/pre&gt;&lt;/blockquote&gt;
8151
8152 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
8153 all the DHCP configuration is loaded, it is ready to receive requests.
8154 The subtree in Debian Edu contain objects with object classes
8155 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8156 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8157 and information about netmasks, dynamic range etc. Leaving out the
8158 details here because it is not relevant for the focus of my
8159 investigation, which is to see if it is possible to merge dns and dhcp
8160 related computer objects.&lt;/p&gt;
8161
8162 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
8163 of the client (00:00:00:00:00:00 in this example), using a subtree
8164 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
8165 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8166 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
8167 like:&lt;/p&gt;
8168
8169 &lt;blockquote&gt;&lt;pre&gt;
8170 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8171 cn: hostname
8172 objectClass: top
8173 objectClass: dhcpHost
8174 dhcpHWAddress: ethernet 00:00:00:00:00:00
8175 dhcpStatements: fixed-address hostname
8176 &lt;/pre&gt;&lt;/blockquote&gt;
8177
8178 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
8179 The object classes need to have fixed names, and the configuration
8180 need to be stored in a fairly specific LDAP structure. On the
8181 positive side, the invidiual dhcpHost entires can be anywhere without
8182 the DN pointed to by the dhcpServer entries. The latter should make
8183 it possible to group all host entries in a subtree next to the
8184 configuration entries, and this subtree can also be shared with the
8185 DNS server if the schema proposed above is combined with the dhcpHost
8186 structural object class.
8187
8188 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
8189
8190 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
8191 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
8192 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
8193 allowing DNS objects to be stored anywhere under the base cn specified
8194 in the configuration.&lt;/p&gt;
8195
8196 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
8197 regarding which LDAP schemas to use and which LDAP structure to use.
8198 I guess one could implement ones own schema, as long as the
8199 objectclasses and attributes have the names used, but this do not
8200 really help when the DHCP subtree need to have a fairly fixed
8201 structure.&lt;/p&gt;
8202
8203 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
8204 this might work for Debian Edu:&lt;/p&gt;
8205
8206 &lt;blockquote&gt;&lt;pre&gt;
8207 ou=services
8208 cn=machine-info (dhcpService) - dhcpServiceDN points here
8209 cn=dhcp (dhcpServer)
8210 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8211 cn=10.0.2.0 (dhcpSubnet)
8212 cn=group1 (dhcpGroup/dhcpOptions)
8213 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8214 cn=192.168.0.0 (dhcpSubnet)
8215 cn=group1 (dhcpGroup/dhcpOptions)
8216 ou=machines - PowerDNS base points here
8217 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8218 &lt;/pre&gt;&lt;/blockquote&gt;
8219
8220 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
8221 entries to be in the dhcpGroup subtrees, the entries can be stored
8222 there instead of a common machines subtree, and the PowerDNS base
8223 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
8224
8225 &lt;p&gt;The combined object under the machines subtree would look something
8226 like this:&lt;/p&gt;
8227
8228 &lt;blockquote&gt;&lt;pre&gt;
8229 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8230 dc: hostname
8231 objectClass: top
8232 objectClass: dhcpHost
8233 objectclass: domainrelatedobject
8234 objectclass: dnsDomainAux
8235 associateddomain: hostname.intern
8236 arecord: 10.11.12.13
8237 dhcpHWAddress: ethernet 00:00:00:00:00:00
8238 dhcpStatements: fixed-address hostname.intern
8239 &lt;/pre&gt;&lt;/blockquote&gt;
8240
8241 &lt;/p&gt;One could even add the LTSP configuration associated with a given
8242 machine, as long as the required attributes are available in a
8243 auxiliary object class.&lt;/p&gt;
8244 </description>
8245 </item>
8246
8247 <item>
8248 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
8249 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
8250 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
8251 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
8252 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
8253 DHCP services in Debian Edu to use the same LDAP objects for a given
8254 computer, to avoid the possibility of having a inconsistent state for
8255 a computer in LDAP (as in DHCP but no DNS entry or the other way
8256 around) and make it easier to add computers to LDAP.&lt;/p&gt;
8257
8258 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
8259 information finally found a solution that seem to work.&lt;/p&gt;
8260
8261 &lt;p&gt;The old setup required three LDAP objects for a given computer.
8262 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8263 we switch powerdns to use its strict LDAP method (ldap-method=strict
8264 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8265 merged into one while making it impossible to transfer the reverse map
8266 to a slave DNS server.&lt;/p&gt;
8267
8268 &lt;p&gt;If we also replace the object class used to get the DNS related
8269 attributes to one allowing these attributes to be combined with the
8270 dhcphost object class, we can merge the DNS and DHCP entries into one.
8271 I&#39;ve written such object class in the dnsdomainaux.schema file (need
8272 proper OIDs, but that is a minor issue), and tested the setup. It
8273 seem to work.&lt;/p&gt;
8274
8275 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
8276 for both DNS and DHCP, and even the LTSP configuration I suggested in
8277 an earlier email. The combined LDAP object will look something like
8278 this:&lt;/p&gt;
8279
8280 &lt;blockquote&gt;&lt;pre&gt;
8281 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8282 cn: hostname
8283 objectClass: dhcphost
8284 objectclass: domainrelatedobject
8285 objectclass: dnsdomainaux
8286 associateddomain: hostname.intern
8287 arecord: 10.11.12.13
8288 dhcphwaddress: ethernet 00:00:00:00:00:00
8289 dhcpstatements: fixed-address hostname
8290 ldapconfigsound: Y
8291 &lt;/pre&gt;&lt;/blockquote&gt;
8292
8293 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
8294 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8295 before asking DNS to resolve the fixed-adddress. LTSP will use
8296 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
8297
8298 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
8299 dhcphost in a different location, to allow us to put the objects
8300 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
8301 that. If I can&#39;t figure out a way to do that, we can still get rid of
8302 the hosts subtree and move all its content into the DHCP Config tree
8303 (which probably should be renamed to be more related to the new
8304 content. I suspect cn=dnsdhcp,ou=services or something like that
8305 might be a good place to put it.&lt;/p&gt;
8306
8307 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8308 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8309 </description>
8310 </item>
8311
8312 <item>
8313 <title>Idea for storing LTSP configuration in LDAP</title>
8314 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
8315 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
8316 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
8317 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
8318 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8319 clients, and that this can be used to fetch configuration from LDAP if
8320 Debian Edu choose to store configuration there.&lt;/p&gt;
8321
8322 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
8323 to get configuration from LDAP. The idea is to look up the MAC
8324 address of the client in LDAP, and look for attributes on the form
8325 ltspconfigsetting=value, and use this to export SETTING=value to the
8326 LTSP clients.&lt;/p&gt;
8327
8328 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
8329 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
8330 allowing us to store all information about a computer in one place.&lt;/p&gt;
8331
8332 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
8333 this approach. A real LDAP schema for the ltspClientAux objectclass
8334 need to be written. Comments, suggestions, etc?&lt;/p&gt;
8335
8336 &lt;blockquote&gt;&lt;pre&gt;
8337 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8338 #
8339 # Fetch LTSP client settings from LDAP based on MAC address
8340 #
8341 # Uses ethernet address as stored in the dhcpHost objectclass using
8342 # the dhcpHWAddress attribute or ethernet address stored in the
8343 # ieee802Device objectclass with the macAddress attribute.
8344 #
8345 # This module is written to be schema agnostic, and only depend on the
8346 # existence of attribute names.
8347 #
8348 # The LTSP configuration variables are saved directly using a
8349 # ltspConfig prefix and uppercasing the rest of the attribute name.
8350 # To set the SERVER variable, set the ltspConfigServer attribute.
8351 #
8352 # Some LDAP schema should be created with all the relevant
8353 # configuration settings. Something like this should work:
8354 #
8355 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
8356 # SUP top
8357 # AUXILIARY
8358 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8359
8360 LDAPSERVER=$(debian-edu-ldapserver)
8361 if [ &quot;$LDAPSERVER&quot; ] ; then
8362 LDAPBASE=$(debian-edu-ldapserver -b)
8363 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
8364 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
8365 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
8366 grep &#39;^ltspConfig&#39; | while read attr value ; do
8367 # Remove prefix and convert to upper case
8368 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
8369 # bass value on to clients
8370 eval &quot;$attr=$value; export $attr&quot;
8371 done
8372 done
8373 fi
8374 &lt;/pre&gt;&lt;/blockquote&gt;
8375
8376 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
8377 the while block might end up in a subshell causing the variables set
8378 there to not show up in ltsp-config, but if that is the case I am sure
8379 the code can be restructured to make sure the variables are passed on.
8380 I expect that can be solved with some testing. :)&lt;/p&gt;
8381
8382 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8383 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8384
8385 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
8386 configuration in LDAP that was created around year 2000 by
8387 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
8388 Xperience, Inc., 2000&lt;/a&gt;. I found its
8389 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
8390 personal home page over at redhat.com.&lt;/p&gt;
8391 </description>
8392 </item>
8393
8394 <item>
8395 <title>jXplorer, a very nice LDAP GUI</title>
8396 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
8397 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
8398 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
8399 <description>&lt;p&gt;Since
8400 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
8401 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
8402 LDAP GUI that is even better than luma. The java application
8403 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
8404 moving LDAP objects and subtrees using drag-and-drop, and can
8405 authenticate using Kerberos. I have only tested the Kerberos
8406 authentication, but do not have a LDAP setup allowing me to rewrite
8407 LDAP with my test user yet. It is
8408 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
8409 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
8410 have with it is how it handle errors. If something go wrong, its
8411 non-intuitive behaviour require me to go through some query work list
8412 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
8413 </description>
8414 </item>
8415
8416 <item>
8417 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
8418 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
8419 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
8420 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
8421 <description>&lt;p&gt;Here is a short update on my &lt;a
8422 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
8423 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
8424 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
8425 not reporting the status for KDE, because the upgrade crashes when
8426 aptitude try because of missing conflicts
8427 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
8428 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
8429
8430 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
8431 complete list of the installed packages. Based on this I see these
8432 differences when I did a test run today. As usual, I do not really
8433 know what the correct set of packages would be, but thought it best to
8434 publish the difference.&lt;/p&gt;
8435
8436 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8437
8438 &lt;blockquote&gt;&lt;p&gt;
8439 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
8440 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
8441 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8442 libgtksourceview-common libpt-1.10.10-plugins-alsa
8443 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8444 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8445 python-4suite-xml python-eggtrayicon python-gtkhtml2
8446 python-gtkmozembed svgalibg1 xserver-xephyr zip
8447 &lt;/p&gt;&lt;/blockquote&gt;
8448
8449 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8450
8451 &lt;blockquote&gt;&lt;p&gt;
8452 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8453 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8454 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
8455 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
8456 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
8457 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
8458 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8459 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8460 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8461 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
8462 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
8463 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
8464 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8465 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
8466 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8467 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
8468 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
8469 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8470 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8471 mysql-common swfdec-gnome totem-gstreamer wodim
8472 &lt;/p&gt;&lt;/blockquote&gt;
8473
8474 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8475
8476 &lt;blockquote&gt;&lt;p&gt;
8477 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8478 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8479 xserver-xorg-input-all xserver-xorg-input-evdev
8480 xserver-xorg-input-kbd xserver-xorg-input-mouse
8481 xserver-xorg-input-synaptics xserver-xorg-video-all
8482 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8483 xserver-xorg-video-chips xserver-xorg-video-cirrus
8484 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8485 xserver-xorg-video-glint xserver-xorg-video-i128
8486 xserver-xorg-video-i740 xserver-xorg-video-mach64
8487 xserver-xorg-video-mga xserver-xorg-video-neomagic
8488 xserver-xorg-video-nouveau xserver-xorg-video-nv
8489 xserver-xorg-video-r128 xserver-xorg-video-radeon
8490 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8491 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8492 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8493 xserver-xorg-video-sis xserver-xorg-video-sisusb
8494 xserver-xorg-video-tdfx xserver-xorg-video-tga
8495 xserver-xorg-video-trident xserver-xorg-video-tseng
8496 xserver-xorg-video-vesa xserver-xorg-video-vmware
8497 xserver-xorg-video-voodoo
8498 &lt;/p&gt;&lt;/blockquote&gt;
8499
8500 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8501
8502 &lt;blockquote&gt;&lt;p&gt;
8503 deskbar-applet xserver-xorg xserver-xorg-core
8504 xserver-xorg-input-wacom xserver-xorg-video-intel
8505 xserver-xorg-video-openchrome
8506 &lt;/p&gt;&lt;/blockquote&gt;
8507
8508 &lt;p&gt;I was told on IRC that the xorg-xserver package was
8509 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
8510 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
8511 No idea when it hits Squeeze, but when it does I hope it will reduce
8512 the difference somewhat.
8513 </description>
8514 </item>
8515
8516 <item>
8517 <title>LUMA, a very nice LDAP GUI</title>
8518 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
8519 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
8520 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
8521 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
8522 directory in Debian Edu, and in the process I started to miss a GUI
8523 tool to browse the LDAP tree. The only one I was able to find in
8524 Debian/Squeeze and Lenny is
8525 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
8526 be a great tool to get a overview of the current LDAP directory
8527 populated by default in Skolelinux. Thanks to it, I have been able to
8528 find empty and obsolete subtrees, misplaced objects and duplicate
8529 objects. It will be installed by default in Debian/Squeeze. If you
8530 are working with LDAP, give it a go. :)&lt;/p&gt;
8531
8532 &lt;p&gt;I did notice one problem with it I have not had time to report to
8533 the BTS yet. There is no .desktop file in the package, so the tool do
8534 not show up in the Gnome and KDE menus, but only deep down in in the
8535 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8536 released.&lt;/p&gt;
8537
8538 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
8539 like to move objects and remove subtrees directly in the GUI, but have
8540 not found a way to do that with LUMA yet. So in the mean time, I use
8541 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
8542
8543 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
8544 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8545
8546 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
8547 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
8548 useful GUI alternative. It seem like a good tool, but is unmaintained
8549 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8550 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
8551 </description>
8552 </item>
8553
8554 <item>
8555 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
8556 <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>
8557 <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>
8558 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
8559 <description>&lt;p&gt;A while back, I
8560 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
8561 about the fact&lt;/a&gt; that it is not possible with the provided schemas
8562 for storing DNS and DHCP information in LDAP to combine the two sets
8563 of information into one LDAP object representing a computer.&lt;/p&gt;
8564
8565 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
8566 the dhcpHost object class auxiliary, to allow it to be combined with
8567 the dNSDomain object class, and thus forming one object for one
8568 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
8569
8570 &lt;p&gt;If I understand this correctly, it is not safe to do this change
8571 without also changing the assigned number for the object class, and I
8572 do not know enough about LDAP schema design to do that properly for
8573 Debian Edu.&lt;/p&gt;
8574
8575 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
8576 the
8577 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
8578 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
8579 available today from IETF.&lt;/p&gt;
8580
8581 &lt;pre&gt;
8582 --- dhcp.schema (revision 65192)
8583 +++ dhcp.schema (working copy)
8584 @@ -376,7 +376,7 @@
8585 objectclass ( 2.16.840.1.113719.1.203.6.6
8586 NAME &#39;dhcpHost&#39;
8587 DESC &#39;This represents information about a particular client&#39;
8588 - SUP top
8589 + SUP top AUXILIARY
8590 MUST cn
8591 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8592 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
8593 &lt;/pre&gt;
8594
8595 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
8596 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8597 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
8598
8599 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8600 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8601 </description>
8602 </item>
8603
8604 <item>
8605 <title>Calling tasksel like the installer, while still getting useful output</title>
8606 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
8607 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
8608 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
8609 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
8610 installs packages during the normal debian-installer run. Until now,
8611 I have ended up letting tasksel do the work, with the annoying problem
8612 of not getting any feedback at all when something fails (like a
8613 conffile question from dpkg or a download that fails), using code like
8614 this:
8615
8616 &lt;blockquote&gt;&lt;pre&gt;
8617 export DEBIAN_FRONTEND=noninteractive
8618 tasksel --new-install
8619 &lt;/pre&gt;&lt;/blockquote&gt;
8620
8621 This would invoke tasksel, let its automatic task selection pick the
8622 tasks to install, and continue to install the requested tasks without
8623 any output what so ever.
8624
8625 Recently I revisited this problem while working on the automatic
8626 package upgrade testing, because tasksel would some times hang without
8627 any useful feedback, and I want to see what is going on when it
8628 happen. Then it occured to me, I can parse the output from tasksel
8629 when asked to run in test mode, and use that aptitude command line
8630 printed by tasksel then to simulate the tasksel run. I ended up using
8631 code like this:
8632
8633 &lt;blockquote&gt;&lt;pre&gt;
8634 export DEBIAN_FRONTEND=noninteractive
8635 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
8636 $cmd
8637 &lt;/pre&gt;&lt;/blockquote&gt;
8638
8639 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
8640 --without-recommends -o APT::Install-Recommends=no -y install
8641 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8642 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
8643 laptop task and all packages with priority standard , required and
8644 important, just like tasksel would have done it during
8645 installation.&lt;/p&gt;
8646
8647 &lt;p&gt;A better approach is probably to extend tasksel to be able to
8648 install packages without using debconf-apt-progress, for use cases
8649 like this.&lt;/p&gt;
8650 </description>
8651 </item>
8652
8653 <item>
8654 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
8655 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
8656 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
8657 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
8658 <description>&lt;p&gt;My
8659 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
8660 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
8661 finally made the upgrade logs available from
8662 &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;.
8663 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8664 apt and aptitude, and found their differences interesting. This time
8665 I will only focus on their removal plans.&lt;/p&gt;
8666
8667 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
8668 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
8669 surprising part is that it want to remove xorg and all
8670 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8671 sure why. When asking aptitude to do the same, it want to remove 129
8672 packages, but most of them are library packages I suspect are no
8673 longer needed. Both of them want to remove bluetooth packages, which
8674 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
8675
8676 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
8677 which seem like a bad idea and xorg the same way as with Gnome. Asking
8678 aptitude for the same, it wants to remove 192 packages, none which are
8679 too surprising.&lt;/p&gt;
8680
8681 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
8682 and avoided, and perhaps others as well. Here are the complete list
8683 of planned removals. The complete logs is available from the URL
8684 above. Note if you want to repeat these tests, that the upgrade test
8685 for kde+apt-get hung in the tasksel setup because of dpkg asking
8686 conffile questions. No idea why. I worked around it by using
8687 &#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
8688 continue.&lt;/p&gt;
8689
8690 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
8691 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
8692 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8693 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
8694 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8695 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8696 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8697 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8698 xserver-xorg-input-kbd xserver-xorg-input-mouse
8699 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8700 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8701 xserver-xorg-video-ati xserver-xorg-video-chips
8702 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8703 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8704 xserver-xorg-video-glint xserver-xorg-video-i128
8705 xserver-xorg-video-i740 xserver-xorg-video-imstt
8706 xserver-xorg-video-intel xserver-xorg-video-mach64
8707 xserver-xorg-video-mga xserver-xorg-video-neomagic
8708 xserver-xorg-video-nsc xserver-xorg-video-nv
8709 xserver-xorg-video-openchrome xserver-xorg-video-r128
8710 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8711 xserver-xorg-video-rendition xserver-xorg-video-s3
8712 xserver-xorg-video-s3virge xserver-xorg-video-savage
8713 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8714 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8715 xserver-xorg-video-tga xserver-xorg-video-trident
8716 xserver-xorg-video-tseng xserver-xorg-video-v4l
8717 xserver-xorg-video-vesa xserver-xorg-video-vga
8718 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
8719 xulrunner-1.9-gnome-support&lt;/p&gt;
8720
8721 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
8722
8723 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
8724 djvulibre-desktop finger gnome-app-install gnome-mount
8725 gnome-network-admin gnome-spell gnome-vfs-obexftp
8726 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8727 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8728 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8729 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
8730 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
8731 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
8732 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
8733 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
8734 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
8735 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
8736 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
8737 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
8738 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8739 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
8740 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
8741 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
8742 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
8743 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
8744 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8745 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8746 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8747 openoffice.org-writer2latex openssl-blacklist p7zip
8748 python-4suite-xml python-eggtrayicon python-gnome2-desktop
8749 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8750 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8751 swfdec-mozilla totem-gstreamer update-manager wodim
8752 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8753 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8754 zip&lt;/p&gt;
8755
8756 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
8757
8758 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8759 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8760 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8761 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8762 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8763 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8764 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8765 xserver-xorg-input-kbd xserver-xorg-input-mouse
8766 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8767 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8768 xserver-xorg-video-ati xserver-xorg-video-chips
8769 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8770 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8771 xserver-xorg-video-glint xserver-xorg-video-i128
8772 xserver-xorg-video-i740 xserver-xorg-video-imstt
8773 xserver-xorg-video-intel xserver-xorg-video-mach64
8774 xserver-xorg-video-mga xserver-xorg-video-neomagic
8775 xserver-xorg-video-nsc xserver-xorg-video-nv
8776 xserver-xorg-video-openchrome xserver-xorg-video-r128
8777 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8778 xserver-xorg-video-rendition xserver-xorg-video-s3
8779 xserver-xorg-video-s3virge xserver-xorg-video-savage
8780 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8781 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8782 xserver-xorg-video-tga xserver-xorg-video-trident
8783 xserver-xorg-video-tseng xserver-xorg-video-v4l
8784 xserver-xorg-video-vesa xserver-xorg-video-vga
8785 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
8786
8787 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
8788 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
8789 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8790 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8791 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8792 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8793 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8794 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8795 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8796 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8797 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8798 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8799 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8800 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8801 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8802 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8803 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8804 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8805 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8806 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
8807 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8808 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8809 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
8810 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8811 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8812 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8813 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8814 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8815 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
8816 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
8817 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8818 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8819 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8820 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8821 texlive-common texlive-doc-base texlive-fonts-recommended
8822 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8823 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8824 xulrunner-1.9&lt;/p&gt;
8825
8826 </description>
8827 </item>
8828
8829 <item>
8830 <title>Automatic upgrade testing from Lenny to Squeeze</title>
8831 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
8832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
8833 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
8834 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
8835 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8836 have been discovered and reported in the process
8837 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
8838 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
8839 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
8840 kdebase-workspace-data), and to get a more regular testing going on, I
8841 am working on a script to automate the test.&lt;/p&gt;
8842
8843 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
8844 Gnome or KDE desktop installation inside the chroot before upgrading
8845 it. To ensure no services are started in the chroot, a policy-rc.d
8846 script is inserted. To make sure tasksel believe it is to install a
8847 desktop on a laptop, the tasksel tests are replaced in the chroot
8848 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
8849
8850 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8851 currently always fail because udev refuses to upgrade with the kernel
8852 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8853 is created. The bug report
8854 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
8855 this problem do not trigger in a chroot, but I touch the file anyway
8856 to make sure the upgrade go well. Testing on virtual and real
8857 hardware have failed me because of udev so far, and creating this file
8858 do the trick in such settings anyway. This is a
8859 &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
8860 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
8861 maintainer because he lack the resources to rewrite udev to keep
8862 working with old kernels or something like that. I really wish the
8863 udev upstream would keep udev backwards compatible, to avoid such
8864 upgrade problem, but given that they fail to do so, I guess
8865 documenting the way out of this mess is the best option we got for
8866 Debian Squeeze.&lt;/p&gt;
8867
8868 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
8869 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
8870 trick:&lt;/p&gt;
8871
8872 &lt;blockquote&gt;&lt;pre&gt;
8873 #!/bin/sh
8874 set -ex
8875
8876 if [ &quot;$1&quot; ] ; then
8877 desktop=$1
8878 else
8879 desktop=gnome
8880 fi
8881
8882 from=lenny
8883 to=squeeze
8884
8885 exec &amp;lt; /dev/null
8886 unset LANG
8887 mirror=http://ftp.skolelinux.org/debian
8888 tmpdir=chroot-$from-upgrade-$to-$desktop
8889 fuser -mv .
8890 debootstrap $from $tmpdir $mirror
8891 chroot $tmpdir aptitude update
8892 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
8893 #!/bin/sh
8894 exit 101
8895 EOF
8896 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8897 exit_cleanup() {
8898 umount $tmpdir/proc
8899 }
8900 mount -t proc proc $tmpdir/proc
8901 # Make sure proc is unmounted also on failure
8902 trap exit_cleanup EXIT INT
8903
8904 chroot $tmpdir aptitude -y install debconf-utils
8905
8906 # Make sure tasksel autoselection trigger. It need the test scripts
8907 # to return the correct answers.
8908 echo tasksel tasksel/desktop multiselect $desktop | \
8909 chroot $tmpdir debconf-set-selections
8910
8911 # Include the desktop and laptop task
8912 for test in desktop laptop ; do
8913 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
8914 #!/bin/sh
8915 exit 2
8916 EOF
8917 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8918 done
8919
8920 DEBIAN_FRONTEND=noninteractive
8921 DEBIAN_PRIORITY=critical
8922 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8923 chroot $tmpdir tasksel --new-install
8924
8925 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
8926 chroot $tmpdir aptitude update
8927 touch $tmpdir/etc/udev/kernel-upgrade
8928 chroot $tmpdir aptitude -y dist-upgrade
8929 fuser -mv
8930 &lt;/pre&gt;&lt;/blockquote&gt;
8931
8932 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
8933 with aptitude, but I have not had time to look at how they behave
8934 differently so far. I hope to get a cron job running to do the test
8935 regularly and post the result on the web. The Gnome upgrade currently
8936 work, while the KDE upgrade fail because of the bug in
8937 kdebase-workspace-data&lt;/p&gt;
8938
8939 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
8940 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
8941 post, so I will refrain from trying. I can report that for Gnome,
8942 aptitude report 760 packages upgraded, 448 newly installed, 129 to
8943 remove and 1 not upgraded and 1024MB need to be downloaded while for
8944 KDE the same numbers are 702 packages upgraded, 507 newly installed,
8945 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
8946
8947 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
8948 is able to migrate to dependency based boot sequencing and parallel
8949 booting without a hitch. Was unsure if there were still bugs with
8950 packages failing to clean up their obsolete init.d script during
8951 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8952 packages.&lt;/p&gt;
8953 </description>
8954 </item>
8955
8956 <item>
8957 <title>Upstart or sysvinit - as init.d scripts see it</title>
8958 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
8959 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
8960 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
8961 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
8962 scripts to migrate (some of) their operations to upstart job while
8963 keeping the init.d for hurd and kfreebsd. The packages with such
8964 needs will need a way to get their init.d scripts to behave
8965 differently when used with sysvinit and with upstart. Because of
8966 this, I had a look at the environment variables set when a init.d
8967 script is running under upstart, and when it is not.&lt;/p&gt;
8968
8969 &lt;p&gt;With upstart, I notice these environment variables are set when a
8970 script is started from rcS.d/ (ignoring some irrelevant ones like
8971 COLUMNS):&lt;/p&gt;
8972
8973 &lt;blockquote&gt;&lt;pre&gt;
8974 DEFAULT_RUNLEVEL=2
8975 previous=N
8976 PREVLEVEL=
8977 RUNLEVEL=
8978 runlevel=S
8979 UPSTART_EVENTS=startup
8980 UPSTART_INSTANCE=
8981 UPSTART_JOB=rc-sysinit
8982 &lt;/pre&gt;&lt;/blockquote&gt;
8983
8984 &lt;p&gt;With sysvinit, these environment variables are set for the same
8985 script.&lt;/p&gt;
8986
8987 &lt;blockquote&gt;&lt;pre&gt;
8988 INIT_VERSION=sysvinit-2.88
8989 previous=N
8990 PREVLEVEL=N
8991 RUNLEVEL=S
8992 runlevel=S
8993 &lt;/pre&gt;&lt;/blockquote&gt;
8994
8995 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
8996 sysvinit are not set by upstart. Not sure if it is intentional or not
8997 to not be compatible with sysvinit in this regard.&lt;/p&gt;
8998
8999 &lt;p&gt;For scripts needing to behave differently when upstart is used,
9000 looking for the UPSTART_JOB environment variable seem to be a good
9001 choice.&lt;/p&gt;
9002 </description>
9003 </item>
9004
9005 <item>
9006 <title>A manual for standards wars...</title>
9007 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
9008 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
9009 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
9010 <description>&lt;p&gt;Via the
9011 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
9012 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
9013 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
9014 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
9015 following the standards wars of today.&lt;/p&gt;
9016 </description>
9017 </item>
9018
9019 <item>
9020 <title>Sitesummary tip: Listing computer hardware models used at site</title>
9021 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
9022 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
9023 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
9024 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
9025 to get a list of the machine types in use thanks to the DMI
9026 information extracted from each machine. The script to do so is
9027 included in the sitesummary package, and here is example output from
9028 the Skolelinux build servers:&lt;/p&gt;
9029
9030 &lt;blockquote&gt;&lt;pre&gt;
9031 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9032 vendor count
9033 Dell Computer Corporation 1
9034 PowerEdge 1750 1
9035 IBM 1
9036 eserver xSeries 345 -[8670M1X]- 1
9037 Intel 2
9038 [no-dmi-info] 3
9039 maintainer:~#
9040 &lt;/pre&gt;&lt;/blockquote&gt;
9041
9042 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
9043 provided in each machine. Here there are Intel machines without model
9044 information listed with Intel as vendor and no model, and virtual Xen
9045 machines listed as [no-dmi-info]. One can add -l as a command line
9046 option to list the individual machines.&lt;/p&gt;
9047
9048 &lt;p&gt;A larger list is
9049 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
9050 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
9051 provide the basic sitesummary report publicly. In their report there
9052 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
9053 their machines, and as sitesummary is available in both distributions,
9054 it is trivial to get all of them to report to the same central
9055 collector.&lt;/p&gt;
9056 </description>
9057 </item>
9058
9059 <item>
9060 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
9061 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
9062 <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>
9063 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
9064 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
9065 start at boot when an NVidia video card is used is handled. The
9066 problem seem to be that the nvidia X.org driver uses a long time to
9067 initialize, and this duration is longer than kdm is configured to
9068 wait.&lt;/p&gt;
9069
9070 &lt;p&gt;I came across two bugs related to this issue,
9071 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
9072 against initscripts and passed on to nvidia-glx when it became obvious
9073 that the nvidia drivers were involved, and
9074 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
9075 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
9076
9077 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
9078 problem nvidia video card owners experience and make sure the Debian
9079 distribution work out of the box for these users. The nvidia driver
9080 maintainers expect kdm to be set up to wait longer, while kdm expect
9081 the nvidia driver maintainers to fix the driver to start faster, and
9082 while they wait for each other I guess the users end up switching to a
9083 distribution that work for them. I have no idea what the solution is,
9084 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
9085
9086 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
9087 </description>
9088 </item>
9089
9090 <item>
9091 <title>Parallellized boot seem to hold up well in Debian/testing</title>
9092 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
9093 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
9094 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
9095 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
9096 The feature seem to hold up pretty well, but three fairly serious
9097 issues are known and should be solved:
9098
9099 &lt;p&gt;&lt;ul&gt;
9100
9101 &lt;li&gt;The wicd package seen to
9102 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
9103 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
9104 parallel booting is enabled. No idea why, but the wicd maintainer
9105 seem to be on the case.&lt;/li&gt;
9106
9107 &lt;li&gt;The nvidia X driver seem to
9108 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
9109 triggered more easily when parallel booting is in effect. The
9110 maintainer is on the case.&lt;/li&gt;
9111
9112 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
9113 sequencing (the shutdown is broken) when old file-rc users
9114 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
9115 sysv-rc. One way to solve it would be for file-rc to create
9116 /etc/init.d/.legacy-bootordering, and another is to try to make
9117 sysv-rc more robust. Will investigate some more and probably upload a
9118 workaround in sysv-rc to help those trying to move from file-rc to
9119 sysv-rc get a working shutdown.&lt;/li&gt;
9120
9121 &lt;/ul&gt;&lt;/p&gt;
9122
9123 &lt;p&gt;All in all not many surprising issues, and all of them seem
9124 solvable before Squeeze is released. In addition to these there are
9125 some packages with bugs in their dependencies and run level settings,
9126 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
9127
9128 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9129 the BTS, please usertag the report to get it to show up at
9130 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9131 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9132
9133 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
9134 </description>
9135 </item>
9136
9137 <item>
9138 <title>More flexible firmware handling in debian-installer</title>
9139 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
9140 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
9141 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
9142 <description>&lt;p&gt;After a long break from debian-installer development, I finally
9143 found time today to return to the project. Having to spend less time
9144 working dependency based boot in debian, as it is almost complete now,
9145 definitely helped freeing some time.&lt;/p&gt;
9146
9147 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
9148 include some firmware packages on the Debian Edu CDs, those needed to
9149 get disk and network controllers working. Without having these
9150 firmware packages available during installation, it is impossible to
9151 install Debian Edu on the given machine, and because our target group
9152 are non-technical people, asking them to provide firmware packages on
9153 an external medium is a support pain. Initially, I expected it to be
9154 enough to include the firmware packages on the CD to get
9155 debian-installer to find and use them. This proved to be wrong.
9156 Next, I hoped it was enough to symlink the relevant firmware packages
9157 to some useful location on the CD (tried /cdrom/ and
9158 /cdrom/firmware/). This also proved to not work, and at this point I
9159 found time to look at the debian-installer code to figure out what was
9160 going to work.&lt;/p&gt;
9161
9162 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
9163 look revealed that it would only look for firmware packages outside
9164 the installation media, so the CD was never checked for firmware
9165 packages. It would only check USB sticks, floppies and other
9166 &quot;external&quot; media devices. Today I changed it to also look in the
9167 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9168 solve the problem I ran into with Debian edu. I also changed it to
9169 look in /firmware/, to make sure the installer also find firmware
9170 provided in the initrd when booting the installer via PXE, to allow us
9171 to provide the same feature in the PXE setup included in Debian
9172 Edu.&lt;/p&gt;
9173
9174 &lt;p&gt;To make sure firmware deb packages with a license questions are not
9175 activated without asking if the license is accepted, I extended
9176 hw-detect to look for preinst scripts in the firmware packages, and
9177 run these before activating the firmware during installation. The
9178 license question is asked using debconf in the preinst, so this should
9179 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
9180
9181 &lt;p&gt;If you want to discuss the details of these features, please
9182 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
9183 </description>
9184 </item>
9185
9186 <item>
9187 <title>Parallellized boot is now the default in Debian/unstable</title>
9188 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
9189 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
9190 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
9191 <description>&lt;p&gt;Since this evening, parallel booting is the default in
9192 Debian/unstable for machines using dependency based boot sequencing.
9193 Apparently the testing of concurrent booting has been wider than
9194 expected, if I am to believe the
9195 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9196 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
9197 with the feature this weekend, to give us some time to detect any
9198 remaining problems before Squeeze is frozen. If serious problems are
9199 detected, it is simple to change the default back to sequential boot.
9200 The upload of the new sysvinit package also activate a new upstream
9201 version.&lt;/p&gt;
9202
9203 More information about
9204 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9205 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
9206 currently possible to disable parallel booting when one run into
9207 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
9208
9209 &lt;blockquote&gt;&lt;pre&gt;
9210 CONCURRENCY=none
9211 &lt;/pre&gt;&lt;/blockquote&gt;
9212
9213 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9214 the BTS, please usertag the report to get it to show up at
9215 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9216 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9217 </description>
9218 </item>
9219
9220 <item>
9221 <title>Sitesummary tip: Listing MAC address of all clients</title>
9222 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
9223 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
9224 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
9225 <description>&lt;p&gt;In the recent Debian Edu versions, the
9226 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
9227 system&lt;/a&gt; is used to keep track of the machines in the school
9228 network. Each machine will automatically report its status to the
9229 central server after boot and once per night. The network setup is
9230 also reported, and using this information it is possible to get the
9231 MAC address of all network interfaces in the machines. This is useful
9232 to update the DHCP configuration.&lt;/p&gt;
9233
9234 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
9235 ist all MAC addresses of all machines reporting to sitesummary. Run
9236 this on the collector host:&lt;/p&gt;
9237
9238 &lt;blockquote&gt;&lt;pre&gt;
9239 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
9240 &lt;/pre&gt;&lt;/blockquote&gt;
9241
9242 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
9243 line per machine and with space between the MAC addresses.&lt;/p&gt;
9244
9245 &lt;p&gt;To allow system administrators easier job at adding static DHCP
9246 addresses for hosts, it would be possible to extend this to fetch
9247 machine information from sitesummary and update the DHCP and DNS
9248 tables in LDAP using this information. Such tool is unfortunately not
9249 written yet.&lt;/p&gt;
9250 </description>
9251 </item>
9252
9253 <item>
9254 <title>systemd, an interesting alternative to upstart</title>
9255 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
9256 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
9257 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
9258 <description>&lt;p&gt;The last few days a new boot system called
9259 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
9260 has been
9261 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
9262
9263 to the free software world. I have not yet had time to play around
9264 with it, but it seem to be a very interesting alternative to
9265 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
9266 a good alternative for Debian when we are able to switch to an event
9267 based boot system. Tollef is
9268 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
9269 systemd into Debian, and I look forward to seeing how well it work. I
9270 like the fact that systemd handles init.d scripts with dependency
9271 information natively, allowing them to run in parallel where upstart
9272 at the moment do not.&lt;/p&gt;
9273
9274 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
9275 platform support. It only work on recent Linux kernels, and also need
9276 some new kernel features enabled to function properly. This means
9277 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9278 system. Not sure how that will be handled if systemd proves to be the
9279 way forward.&lt;/p&gt;
9280
9281 &lt;p&gt;In the mean time, based on the
9282 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9283 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
9284 decided to enable full parallel booting as the default in Debian as
9285 soon as possible (probably this weekend or early next week), to see if
9286 there are any remaining serious bugs in the init.d dependencies. A
9287 new version of the sysvinit package implementing this change is
9288 already in experimental. If all go well, Squeeze will be released
9289 with parallel booting enabled by default.&lt;/p&gt;
9290 </description>
9291 </item>
9292
9293 <item>
9294 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
9295 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
9296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
9297 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
9298 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
9299 complete, so complete that it is actually possible to run all the
9300 init.d scripts in parallell based on these dependencies. If you want
9301 to test your Squeeze system, make sure
9302 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9303 based boot sequencing&lt;/a&gt; is enabled, and add this line to
9304 /etc/default/rcS:&lt;/p&gt;
9305
9306 &lt;blockquote&gt;&lt;pre&gt;
9307 CONCURRENCY=makefile
9308 &lt;/pre&gt;&lt;/blockquote&gt;
9309
9310 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
9311 scripts in parallel using the dependency information stored in
9312 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9313 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9314 to try to start the kdm and gdm scripts as early as possible, and will
9315 start the facilities required by kdm or gdm as early as possible to
9316 make this happen.&lt;/p&gt;
9317
9318 &lt;p&gt;Give it a try, and see if you like the result. If some services
9319 fail to start properly, it is most likely because they have incomplete
9320 init.d script dependencies in their startup script (or some of their
9321 dependent scripts have incomplete dependencies). Report bugs and get
9322 the package maintainers to fix it. :)&lt;/p&gt;
9323
9324 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
9325 manage to get the init.d script dependencies complete and correct. I
9326 expect we will get there in Squeeze+1, if we get manage to test and
9327 fix the remaining issues.&lt;/p&gt;
9328
9329 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9330 the BTS, please usertag the report to get it to show up at
9331 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9332 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9333 </description>
9334 </item>
9335
9336 <item>
9337 <title>Debian has switched to dependency based boot sequencing</title>
9338 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
9339 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
9340 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
9341 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
9342 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
9343 have been migrated to using dependency based boot sequencing. This
9344 conclude work me and others have been doing for the last three days.
9345 It feels great to see this finally part of the default Debian
9346 installation. Now we just need to weed out the last few problems that
9347 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
9348
9349 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
9350 fixing the more fundamental problem of handing the event based
9351 non-predictable kernel in the early boot.&lt;/p&gt;
9352 </description>
9353 </item>
9354
9355 <item>
9356 <title>Taking over sysvinit development</title>
9357 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
9358 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
9359 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
9360 <description>&lt;p&gt;After several years of frustration with the lack of activity from
9361 the existing sysvinit upstream developer, I decided a few weeks ago to
9362 take over the package and become the new upstream. The number of
9363 patches to track for the Debian package was becoming a burden, and the
9364 lack of synchronization between the distribution made it hard to keep
9365 the package up to date.&lt;/p&gt;
9366
9367 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9368 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
9369 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
9370 and Fedora), based on the patches currently in use in these
9371 distributions. We Debian maintainers plan to move to this tarball as
9372 the new upstream as soon as we find time to do the merge. Since the
9373 new tarball was created, we agreed with Werner at SuSe to make a new
9374 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
9375 development there. The project is registered and currently waiting
9376 for approval by the Savannah administrators, and as soon as it is
9377 approved, we will import the old versions from svn and continue
9378 working on the future release.&lt;/p&gt;
9379
9380 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
9381 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
9382 </description>
9383 </item>
9384
9385 <item>
9386 <title>Debian boots quicker and quicker</title>
9387 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
9388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
9389 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
9390 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
9391 people involved in the boot system on Debian and Ubuntu, to see if we
9392 could find more ways to speed up the boot system. This was an Ubuntu
9393 funded
9394 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
9395 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
9396 of boot systems, and ways to handle the increasing number of boot
9397 issues introduced by the Linux kernel becoming more and more
9398 asynchronous and event base. The Ubuntu approach using udev and
9399 upstart might be a good way forward. Time will show.&lt;/p&gt;
9400
9401 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
9402 process in Debian. All of these should be applied to get a quick
9403 boot:&lt;/p&gt;
9404
9405 &lt;ul&gt;
9406
9407 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
9408
9409 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
9410 clock is in UTC.&lt;/li&gt;
9411
9412 &lt;li&gt;Install and activate the insserv package to enable
9413 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9414 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
9415
9416 &lt;/ul&gt;
9417
9418 These points are based on the Google summer of code work done by
9419 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
9420 Villegas&lt;/a&gt;.
9421
9422 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
9423 unstable yesterday. When we tested it, we were able to cut 6 seconds
9424 from the boot sequence. It depend on very correct dependency
9425 declaration in all init.d scripts, so I expect us to find edge cases
9426 where the dependences in some scripts are slightly wrong when we start
9427 using this.&lt;/p&gt;
9428
9429 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9430 introduced by Raphael Geissert today, one that could affect the
9431 startup speed as well. Instead of starting some scripts concurrently
9432 from rcS.d/ and another set of scripts from rc2.d/, it would be
9433 possible to run a of them in the same process. A quick way to test
9434 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
9435 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
9436 </description>
9437 </item>
9438
9439 <item>
9440 <title>BSAs påstander om piratkopiering møter motstand</title>
9441 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
9442 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
9443 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
9444 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
9445 programvareselskapene som Microsoft og Apple, publisert en rapport der
9446 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9447 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9448 dager siden kom
9449 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
9450 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
9451 dagene. Et spesielt interessant kommentar fra Sverige,
9452 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
9453 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
9454
9455 &lt;blockquote&gt;
9456 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
9457 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9458 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
9459 exakta&quot;, säger BSAs Sverigechef John Hugosson.
9460 &lt;/blockquote&gt;
9461
9462 &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
9463 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
9464 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
9465 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
9466 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
9467
9468 &lt;p&gt;Fant lenkene via &lt;a
9469 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
9470 på Slashdot&lt;/a&gt;.&lt;/p&gt;
9471 </description>
9472 </item>
9473
9474 <item>
9475 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
9476 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
9477 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
9478 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
9479 <description>&lt;p&gt;Kom over
9480 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
9481 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9482 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9483 jobber til daglig. En rask opptelling forteller meg at vi har 490
9484 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
9485 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
9486 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
9487 </description>
9488 </item>
9489
9490 <item>
9491 <title>Kryptert harddisk - naturligvis</title>
9492 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
9493 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
9494 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
9495 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
9496 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
9497 når en tar tap av arbeidstid, fortrolige dokumenter,
9498 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9499 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9500 til at jeg har kryptert harddisken på både kontormaskinen og min
9501 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9502 komme på avveie, den første informasjon relatert til jobben min ved
9503 Universitetet i Oslo, og den andre relatert til blant annet
9504 foreningsarbeide. Kryptering av diskene gjør at det er lite
9505 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9506 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9507 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9508 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9509 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9510 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9511 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9512 det er gjort slik jeg gjør det er minimale, og gevinstene er
9513 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9514 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
9515
9516 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9517 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9518 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9519 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9520 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9521 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9522 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9523 betydelige.&lt;/p&gt;
9524 </description>
9525 </item>
9526
9527 <item>
9528 <title>Two projects that have improved the quality of free software a lot</title>
9529 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
9530 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
9531 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
9532 <description>&lt;p&gt;There are two software projects that have had huge influence on the
9533 quality of free software, and I wanted to mention both in case someone
9534 do not yet know them.&lt;/p&gt;
9535
9536 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
9537 tool to detect and expose errors in the memory handling of programs.
9538 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
9539 and it will report any problems on stdout. It is even better if the
9540 program include debug information. With debug information, it is able
9541 to report the source file name and line number where the problem
9542 occurs. It can report things like &#39;reading past memory block in file
9543 X line N, the memory block was allocated in file Y, line M&#39;, and
9544 &#39;using uninitialised value in control logic&#39;. This tool has made it
9545 trivial to investigate reproducible crash bugs in programs, and have
9546 reduced the number of this kind of bugs in free software a lot.
9547
9548 &lt;p&gt;The second one is
9549 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
9550 a source code checker. It is able to process the source of a program
9551 and find problems in the logic without running the program. It
9552 started out as the Stanford Checker and became well known when it was
9553 used to find bugs in the Linux kernel. It is now a commercial tool
9554 and the company behind it is running
9555 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
9556 free software community, where a lot of free software projects get
9557 their source checked for free. Several thousand defects have been
9558 found and fixed so far. It can find errors like &#39;lock L taken in file
9559 X line N is never released if exiting in line M&#39;, or &#39;the code in file
9560 Y lines O to P can never be executed&#39;. The projects included in the
9561 community service project have managed to get rid of a lot of
9562 reliability problems thanks to Coverity.&lt;/p&gt;
9563
9564 &lt;p&gt;I believe tools like this, that are able to automatically find
9565 errors in the source, are vital to improve the quality of software and
9566 make sure we can get rid of the crashing and failing software we are
9567 surrounded by today.&lt;/p&gt;
9568 </description>
9569 </item>
9570
9571 <item>
9572 <title>No patch is not better than a useless patch</title>
9573 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
9574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
9575 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
9576 <description>&lt;p&gt;Julien Blache
9577 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
9578 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
9579 patch allow one to discuss a concrete and proposed solution, and also
9580 prove that the issue at hand is important enough for someone to spent
9581 time on fixing it. No patch do not provide any of these positive
9582 properties.&lt;/p&gt;
9583 </description>
9584 </item>
9585
9586 <item>
9587 <title>Standardize on protocols and formats, not vendors and applications</title>
9588 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
9589 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
9590 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
9591 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
9592 very good one to form a long lived computer infrastructure. It is the
9593 simple one, lost by many in todays computer industry: Standardize on
9594 open network protocols and open exchange/storage formats, not applications.
9595 Applications come and go, while protocols and files tend to stay, and
9596 thus one want to make it easy to change application and vendor, while
9597 avoiding conversion costs and locking users to a specific platform or
9598 application.&lt;/p&gt;
9599
9600 &lt;p&gt;This approach make it possible to replace the client applications
9601 independently of the server applications. One can even allow users to
9602 use several different applications as long as they handle the selected
9603 protocol and format. In the normal case, only one client application
9604 is recommended and users only get help if they choose to use this
9605 application, but those that want to deviate from the easy path are not
9606 blocked from doing so.&lt;/p&gt;
9607
9608 &lt;p&gt;It also allow us to replace the server side without forcing the
9609 users to replace their applications, and thus allow us to select the
9610 best server implementation at any moment, when scale and resouce
9611 requirements change.&lt;/p&gt;
9612
9613 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
9614 open formats, but I would never recommend standardizing on a single
9615 application that do not use open network protocol or open formats.&lt;/p&gt;
9616 </description>
9617 </item>
9618
9619 <item>
9620 <title>Returning from Skolelinux developer gathering</title>
9621 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
9622 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
9623 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
9624 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
9625 Edu/Skolelinux development gathering. I got a bit done tuning the
9626 desktop, and looked into the dynamic service location protocol
9627 implementation avahi. It look like it could be useful for us. Almost
9628 30 people participated, and I believe it was a great environment to
9629 get to know the Skolelinux system. Walter Bender, involved in the
9630 development of the Sugar educational platform, presented his stuff and
9631 also helped me improve my OLPC installation. He also showed me that
9632 his Turtle Art application can be used in standalone mode, and we
9633 agreed that I would help getting it packaged for Debian. As a
9634 standalone application it would be great for Debian Edu. We also
9635 tried to get the video conferencing working with two OLPCs, but that
9636 proved to be too hard for us. The application seem to need more work
9637 before it is ready for me. I look forward to getting home and relax
9638 now. :)&lt;/p&gt;
9639 </description>
9640 </item>
9641
9642 <item>
9643 <title>Time for new LDAP schemas replacing RFC 2307?</title>
9644 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
9645 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
9646 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
9647 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
9648 optimal. There is RFC 2307 documenting one way to store NIS maps in
9649 LDAP, and a modified version of this normally called RFC 2307bis, with
9650 some modifications to be compatible with Active Directory. The RFC
9651 specification handle the content of a lot of system databases, but do
9652 not handle DNS zones and DHCP configuration.&lt;/p&gt;
9653
9654 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
9655 we would like to store information about users, SMB clients/hosts,
9656 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9657 and LTSP configuration in LDAP. These objects have a lot in common,
9658 but with the current LDAP schemas it is not possible to have one
9659 object per entity. For example, one need to have at least three LDAP
9660 objects for a given computer, one with the SMB related stuff, one with
9661 DNS information and another with DHCP information. The schemas
9662 provided for DNS and DHCP are impossible to combine into one LDAP
9663 object. In addition, it is impossible to implement quick queries for
9664 netgroup membership, because of the way NIS triples are implemented.
9665 It just do not scale. I believe it is time for a few RFC
9666 specifications to cleam up this mess.&lt;/p&gt;
9667
9668 &lt;p&gt;I would like to have one LDAP object representing each computer in
9669 the network, and this object can then keep the SMB (ie host key), DHCP
9670 (mac address/name) and DNS (name/IP address) settings in one place.
9671 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
9672
9673 &lt;p&gt;I would also like to have a quick way to map from a user or
9674 computer and to the net group this user or computer is a member.&lt;/p&gt;
9675
9676 &lt;p&gt;Active Directory have done a better job than unix heads like myself
9677 in this regard, and the unix side need to catch up. Time to start a
9678 new IETF work group?&lt;/p&gt;
9679 </description>
9680 </item>
9681
9682 <item>
9683 <title>Endelig er Debian Lenny gitt ut</title>
9684 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
9685 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
9686 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
9687 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
9688 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
9689 Et langt steg videre for Debian-prosjektet, og en rekke nye
9690 programpakker blir nå tilgjengelig for de av oss som bruker den
9691 stabile utgaven av Debian. Neste steg er nå å få
9692 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
9693 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
9694 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9695 slippes løs på skolene. Takk til alle debian-utviklerne som har
9696 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9697 bootsekvens tilgjengelig i stabil utgave, vha pakken
9698 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
9699 </description>
9700 </item>
9701
9702 <item>
9703 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
9704 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
9705 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
9706 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
9707 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
9708 Oslo. Most of Saturday was used for the general assemly for the
9709 member organization, but the rest of the weekend I used to tune the
9710 LTSP installation. LTSP now work out of the box on the 10-network.
9711 Acer Aspire One proved to be a very nice thin client, with both
9712 screen, mouse and keybard in a small box. Was working on getting the
9713 diskless workstation setup configured out of the box, but did not
9714 finish it before the weekend was up.&lt;/p&gt;
9715
9716 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
9717 the Brazilian group, so that will have to wait for the next
9718 development gathering. Would love to have the Debian Edu installer
9719 automatically detect and configure a multiseat setup when it find one
9720 of these cards.&lt;/p&gt;
9721 </description>
9722 </item>
9723
9724 <item>
9725 <title>The sorry state of multimedia browser plugins in Debian</title>
9726 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
9727 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
9728 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
9729 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
9730 plugins available in Debian Lenny, to see which one we should use by
9731 default in Debian Edu. We need an embedded video playing plugin with
9732 control buttons to pause or stop the video, and capable of streaming
9733 all the multimedia content available on the web. The test results and
9734 notes are available on
9735 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
9736 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
9737 fill this need. My personal video player favorite, VLC, has a really
9738 bad plugin which fail on a lot of the test pages. A lot of the MIME
9739 types I would expect to work with any free software player (like
9740 video/ogg), just do not work. And simple formats like the
9741 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
9742 totem and vlc plugins. I hope the situation will improve soon. No
9743 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
9744
9745 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
9746 be the only one fitting our needs. :/&lt;/p&gt;
9747 </description>
9748 </item>
9749
9750 </channel>
9751 </rss>