]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
759294f2fbfcbc312ff269924fa43d9e39b66eaa
[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>Coz profiler for multi-threaded software is now in Debian</title>
11 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
13 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
14 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
15 profiler able to run benchmarking experiments on the instrumented
16 multi-threaded program, finally
17 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
18 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
19 months since
20 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html&quot;&gt;I
21 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
22 it suitable for Debian. There are still issues with clang
23 compatibility, inline assembly only working x86 and minimized
24 JavaScript libraries.&lt;/p&gt;
25
26 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
27
28 &lt;p&gt;&lt;blockquote&gt;
29 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
30 &lt;/blockquote&gt;&lt;/p&gt;
31
32 &lt;p&gt;This will produce a profile.coz file in the current working
33 directory with the profiling information. This is then given to a
34 JavaScript application provided in the package and available from
35 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
36 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
37
38 &lt;p&gt;&lt;blockquote&gt;
39 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
40 &lt;/blockquote&gt;&lt;/p&gt;
41
42 &lt;p&gt;See the project home page and the
43 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
44 ;login: article on Coz&lt;/a&gt; for more information on how it is
45 working.&lt;/p&gt;
46 </description>
47 </item>
48
49 <item>
50 <title>My own self balancing Lego Segway</title>
51 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
52 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
53 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
54 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
55 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
56 present. It had been on my wishlist for a while, because I wanted to
57 build a Segway like balancing lego robot. I had already built
58 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
59 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
60 NXT kit as the balance sensor, but it was not working very well. It
61 could balance for a while, but was very sensitive to the light
62 condition in the room and the reflective properties of the surface and
63 would fall over after a short while. I wanted something more robust,
64 and had
65 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
66 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
67 wishlist for some years before it suddenly showed up as a gift from my
68 loved ones. :)&lt;/p&gt;
69
70 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
71 since then. But that changed some days ago, when I was searching for
72 lego segway information and came across a recipe from HiTechnic for
73 building
74 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
75 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
76 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
77 code&lt;/a&gt; was included, so it was just a question of putting it all
78 together. And thanks to the great work of many Debian developers, the
79 compiler needed to build the source for the NXT is already included in
80 Debian, so I was read to go in less than an hour. The resulting robot
81 do not look very impressive in its simplicity:&lt;/p&gt;
82
83 &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;
84
85 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
86 design from HiTechnic, I had to comment out the last task
87 (taskControl). I simply placed /* and */ around it get the program
88 working without that sensor present. Now it balances just fine until
89 the battery status run low:&lt;/p&gt;
90
91 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
92 &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;
93 &lt;/video&gt;&lt;/p&gt;
94
95 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
96 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
97
98 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
99 they need to work with LEGO in Debian and all our derivative
100 distributions like Ubuntu, check out
101 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
102 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
103 RCX and NXT controller (no EV3), and would like to make sure the
104 Debian tools needed to program the systems I own work as they
105 should.&lt;/p&gt;
106 </description>
107 </item>
108
109 <item>
110 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
111 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
112 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
113 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
114 <description>&lt;p&gt;In July
115 &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
116 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
117 the ability to receive SMS messages (aka without a cell phone). It is
118 time to share some experiences and provide an updated setup.&lt;/p&gt;
119
120 &lt;p&gt;The Signal app have worked fine for several months now, and I use
121 it regularly to chat with my loved ones. I had a major snag at the
122 end of my summer vacation, when the the app completely forgot my
123 setup, identity and keys. The reason behind this major mess was
124 running out of disk space. To avoid that ever happening again I have
125 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
126 roll back to an earlier version if the files are wiped by mistake. I
127 had to use it once after introducing the git backup. When rolling
128 back to an earlier version, one need to use the &#39;reset session&#39; option
129 in Signal to get going, and notify the people you talk with about the
130 problem. I assume there is some sequence number tracking in the
131 protocol to detect rollback attacks. The git repository is rather big
132 (674 MiB so far), but I have not tried to figure out if some of the
133 content can be added to a .gitignore file due to lack of spare
134 time.&lt;/p&gt;
135
136 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
137 make it impossible to send messages using Signal. I could still
138 receive them, but had to patch the code with a new timestamp to send.
139 I believe the timeout is added by the developers to force people to
140 upgrade to the latest version of the app, even when there is no
141 protocol changes, to reduce the version skew among the user base and
142 thus try to keep the number of support requests down.&lt;/p&gt;
143
144 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
145 making the old patch fail to apply cleanly. Below is an updated
146 patch, including the shell wrapper I use to start Signal. The
147 original version required a new user to locate the JavaScript console
148 and call a function from there. I got help from a friend with more
149 JavaScript knowledge than me to modify the code to provide a GUI
150 button instead. This mean that to get started you just need to run
151 the wrapper and click the &#39;Register without mobile phone&#39; to get going
152 now. I&#39;ve also modified the timeout code to always set it to 90 days
153 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
154
155 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
156
157 &lt;ol&gt;
158
159 &lt;li&gt;First, install required packages to get the source code and the
160 browser you need. Signal only work with Chrome/Chromium, as far as I
161 know, so you need to install it.
162
163 &lt;pre&gt;
164 apt install git tor chromium
165 git clone https://github.com/WhisperSystems/Signal-Desktop.git
166 &lt;/pre&gt;&lt;/li&gt;
167
168 &lt;li&gt;Modify the source code using command listed in the the patch
169 block below.&lt;/li&gt;
170
171 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
172 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
173
174 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
175 number you can receive calls to the next minute, receive the
176 verification code and enter it into the form field and press
177 &#39;Register&#39;. Note, the phone number you use will be user Signal
178 username, ie the way others can find you on Signal.&lt;/li&gt;
179
180 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
181 not show up in the contact list until you restart Signal, and there is
182 no way to assign names to Contacts. There is also no way to create or
183 update chat groups. I suspect this is because the web app do not have
184 a associated contact database.&lt;/li&gt;
185
186 &lt;/ol&gt;
187
188 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
189 main author moxie0 reject federation and accept dependencies to major
190 corporations like Google (part of the code is fetched from Google) and
191 Amazon (the central coordination point is owned by Amazon). See for
192 example
193 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
194 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
195 view on these issues. But the network effect is strong in this case,
196 and several of the people I want to communicate with already use
197 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
198 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
199 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
200 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
201 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
202 working on Debian Stable.&lt;/p&gt;
203
204 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
205 working. It switch to the production servers, disable to timeout,
206 make registration easier and add the shell wrapper:&lt;/p&gt;
207
208 &lt;pre&gt;
209 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
210 diff --git a/js/background.js b/js/background.js
211 index 24b4c1d..579345f 100644
212 --- a/js/background.js
213 +++ b/js/background.js
214 @@ -33,9 +33,9 @@
215 });
216 });
217
218 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
219 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
220 var SERVER_PORTS = [80, 4433, 8443];
221 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
222 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
223 var messageReceiver;
224 window.getSocketStatus = function() {
225 if (messageReceiver) {
226 diff --git a/js/expire.js b/js/expire.js
227 index 639aeae..beb91c3 100644
228 --- a/js/expire.js
229 +++ b/js/expire.js
230 @@ -1,6 +1,6 @@
231 ;(function() {
232 &#39;use strict&#39;;
233 - var BUILD_EXPIRATION = 0;
234 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
235
236 window.extension = window.extension || {};
237
238 diff --git a/js/views/install_view.js b/js/views/install_view.js
239 index 7816f4f..1d6233b 100644
240 --- a/js/views/install_view.js
241 +++ b/js/views/install_view.js
242 @@ -38,7 +38,8 @@
243 return {
244 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
245 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
246 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
247 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
248 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
249 };
250 },
251 clearQR: function() {
252 diff --git a/options.html b/options.html
253 index dc0f28e..8d709f6 100644
254 --- a/options.html
255 +++ b/options.html
256 @@ -14,7 +14,10 @@
257 &amp;lt;div class=&#39;nav&#39;&gt;
258 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
259 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
260 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
261 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
262 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
263 +
264 + &amp;lt;/div&gt;
265 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
266 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
267 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
268 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
269 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
270 @@ -0,0 +1,12 @@
271 +#!/bin/sh
272 +set -e
273 +cd $(dirname $0)
274 +mkdir -p userdata
275 +userdata=&quot;`pwd`/userdata&quot;
276 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
277 + (cd $userdata &amp;&amp; git init)
278 +fi
279 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
280 +exec chromium \
281 + --proxy-server=&quot;socks://localhost:9050&quot; \
282 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
283 EOF
284 chmod a+rx run-signal-app
285 &lt;/pre&gt;
286
287 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
288 activities, please send Bitcoin donations to my address
289 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
290 </description>
291 </item>
292
293 <item>
294 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
295 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
297 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
298 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
299 system&lt;/a&gt; provide a practical and easy way to figure out which
300 packages support the hardware in a given machine. The command line
301 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
302 convenient way to list and install packages relevant for the current
303 hardware during system installation, both user space packages and
304 firmware packages. The GUI background daemon on the other hand provide
305 a pop-up proposing to install packages when a new dongle is inserted
306 while using the computer. For example, if you plug in a smart card
307 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
308 that package isn&#39;t already installed, and if you plug in a USB video
309 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
310 cheese is currently missing. This already work just fine.&lt;/p&gt;
311
312 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
313 package names. When I started no such database existed in Debian, so
314 I made my own data set and included it with the isenkram package and
315 made isenkram fetch the latest version of this database from git using
316 http. This way the isenkram users would get updated package proposals
317 as soon as I learned more about hardware related packages.&lt;/p&gt;
318
319 &lt;p&gt;The hardware is identified using modalias strings. The modalias
320 design is from the Linux kernel where most hardware descriptors are
321 made available as a strings that can be matched using filename style
322 globbing. It handle USB, PCI, DMI and a lot of other hardware related
323 identifiers.&lt;/p&gt;
324
325 &lt;p&gt;The downside to the Isenkram specific database is that there is no
326 information about relevant distribution / Debian version, making
327 isenkram propose obsolete packages too. But along came AppStream, a
328 cross distribution mechanism to store and collect metadata about
329 software packages. When I heard about the proposal, I contacted the
330 people involved and suggested to add a hardware matching rule using
331 modalias strings in the specification, to be able to use AppStream for
332 mapping hardware to packages. This idea was accepted and AppStream is
333 now a great way for a package to announce the hardware it support in a
334 distribution neutral way. I wrote
335 &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
336 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
337 December. If you have a hardware related package in Debian, please
338 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
339
340 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
341 RCX or NXT unit, announce this support using AppStream. The effect is
342 that when you insert such LEGO robot controller into your Debian
343 machine, Isenkram will propose to install the packages needed to get
344 it working. The intention is that this should allow the local user to
345 start programming his robot controller right away without having to
346 guess what packages to use or which permissions to fix.&lt;/p&gt;
347
348 &lt;p&gt;But when I sat down with my son the other day to program our NXT
349 unit using his Debian Stretch computer, I discovered something
350 annoying. The local console user (ie my son) did not get access to
351 the USB device for programming the unit. This used to work, but no
352 longer in Jessie and Stretch. After some investigation and asking
353 around on #debian-devel, I discovered that this was because udev had
354 changed the mechanism used to grant access to local devices. The
355 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
356 no longer applied, because LDAP users no longer was added to the
357 plugdev group during login. Michael Biebl told me that this method
358 was obsolete and the new method used ACLs instead. This was good
359 news, as the plugdev mechanism is a mess when using a remote user
360 directory like LDAP. Using ACLs would make sure a user lost device
361 access when she logged out, even if the user left behind a background
362 process which would retain the plugdev membership with the ConsoleKit
363 setup. Armed with this knowledge I moved on to fix the access problem
364 for the LEGO Mindstorms related packages.&lt;/p&gt;
365
366 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
367 applied directly for a device, or is applied in
368 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
369 LEGO Mindstorms udev rules did not have a class, I decided to add the
370 tag directly in the udev rules files included in the packages. Here
371 is one example. For the nqc C compiler for the RCX, the
372 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
373
374 &lt;p&gt;&lt;pre&gt;
375 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
376 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
377 &lt;/pre&gt;&lt;/p&gt;
378
379 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
380 packages using plugdev in their /lib/udev/rules.d/ files should be
381 changed to use this tag (either directly or indirectly via
382 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
383 to detect this?&lt;/p&gt;
384
385 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
386 It is unclear to me if the uaccess tag is an internal implementation
387 detail like the udev-acl tag used by
388 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
389 indirect method is the preferred way. Michael
390 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
391 documentation from the systemd project&lt;/a&gt; and I hope it will make
392 this clearer. For now I use the generic classes when they exist and
393 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
394 directly if no such class exist.&lt;/p&gt;
395
396 &lt;p&gt;To learn more about the isenkram system, please check out
397 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
398 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
399
400 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
401 please join us on our IRC channel
402 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
403 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
404 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
405 list is not yet created, but we are working on it. :)&lt;/p&gt;
406
407 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
408 activities, please send Bitcoin donations to my address
409 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
410 </description>
411 </item>
412
413 <item>
414 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
415 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
416 <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>
417 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
418 <description>&lt;p&gt;In April we
419 &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
420 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
421 how to set up and administrate a Debian system. Today I am happy to
422 report that the first draft is now publicly available. You can find
423 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
424 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
425 eight chapters have a first draft translation, and we are working on
426 proofreading the content. If you want to help out, please start
427 contributing using
428 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
429 hosted weblate project page&lt;/a&gt;, and get in touch using
430 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
431 translators mailing list&lt;/a&gt;. Please also check out
432 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
433 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
434 and update weblate if you find errors.&lt;/p&gt;
435
436 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
437 electronic form.&lt;/p&gt;
438 </description>
439 </item>
440
441 <item>
442 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
443 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
444 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
445 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
446 <description>&lt;p&gt;This summer, I read a great article
447 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
448 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
449 how to profile multi-threaded programs. It presented a system for
450 profiling software by running experiences in the running program,
451 testing how run time performance is affected by &quot;speeding up&quot; parts of
452 the code to various degrees compared to a normal run. It does this by
453 slowing down parallel threads while the &quot;faster up&quot; code is running
454 and measure how this affect processing time. The processing time is
455 measured using probes inserted into the code, either using progress
456 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
457 can also measure unmodified code by measuring complete the program
458 runtime and running the program several times instead.&lt;/p&gt;
459
460 &lt;p&gt;The project and presentation was so inspiring that I would like to
461 get the system into Debian. I
462 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
463 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
464 system ready for Debian by sending patches. The build process need to
465 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
466 to include the JavaScript web page used to visualize the collected
467 profiling information included in the source package.
468 But I expect that should work out fairly soon.&lt;/p&gt;
469
470 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
471 on a binary with debug symbols available, start the program like this:
472
473 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
474 coz run --- program-to-run
475 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
476
477 &lt;p&gt;This will create a text file profile.coz with the instrumentation
478 information. To show what part of the code affect the performance
479 most, use a web browser and either point it to
480 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
481 or use the copy from git (in the gh-pages branch). Check out this web
482 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
483 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
484 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
485 code, rebuild and run the profiler. This allow coz to do more
486 targeted experiments.&lt;/p&gt;
487
488 &lt;p&gt;A video published by ACM
489 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
490 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
491 from the 25th Symposium on Operating Systems Principles available
492 titled
493 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
494 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
495
496 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
497 for Coz is available from github. It will only build with clang
498 because it uses a
499 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
500 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
501 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
502 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
503
504 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
505 of software in Debian. I would very much like some help with the
506 packaging effort, as I lack the in depth knowledge on how to package
507 C++ libraries.&lt;/p&gt;
508 </description>
509 </item>
510
511 <item>
512 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
513 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
515 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
516 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
517 to be a slight challenge. Here is the recipe if I ever need to do it
518 again. It all started by me wanting to try the recipe to set up
519 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
520 hardened Android installation&lt;/a&gt; from the Tor project blog on a
521 device I had access to. It is a old mobile phone with a broken
522 microphone The initial idea had been to just
523 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
524 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
525 until a few days ago.&lt;/p&gt;
526
527 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
528 loader (press volume down and power at the same time), (2) select
529 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
530 machine, (4) request the device identifier token by running &#39;fastboot
531 oem get_identifier_token&#39;, (5) request the device unlocking key using
532 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
533 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
534
535 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
536 or newer, and the device I was working on had 2.00.0027. This
537 apparently can be easily fixed by downloading a Windows program and
538 running it on your Windows machine, if you accept the terms Microsoft
539 require you to accept to use Windows - which I do not. So I had to
540 come up with a different approach. I got a lot of help from AndyCap
541 on #nuug, and would not have been able to get this working without
542 him.&lt;/p&gt;
543
544 &lt;p&gt;First I needed to extract the hboot firmware from
545 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
546 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
547 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
548 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
549 recognise the file format, but unruu worked and extracted rom.zip,
550 containing the new hboot firmware and a text file describing which
551 devices it would work for.&lt;/p&gt;
552
553 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
554 followed some instructions
555 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
556 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
557 machine with Debian testing:&lt;/p&gt;
558
559 &lt;p&gt;&lt;pre&gt;
560 adb reboot-bootloader
561 fastboot oem rebootRUU
562 fastboot flash zip rom.zip
563 fastboot flash zip rom.zip
564 fastboot reboot
565 &lt;/pre&gt;&lt;/p&gt;
566
567 &lt;p&gt;The flash command apparently need to be done twice to take effect,
568 as the first is just preparations and the second one do the flashing.
569 The adb command is just to get to the boot loader menu, so turning the
570 device on while holding volume down and the power button should work
571 too.&lt;/p&gt;
572
573 &lt;p&gt;With the new hboot version in place I could start following the
574 instructions on the HTC developer web site. I got the device token
575 like this:&lt;/p&gt;
576
577 &lt;p&gt;&lt;pre&gt;
578 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
579 &lt;/pre&gt;
580
581 &lt;p&gt;And once I got the unlock code via email, I could use it like
582 this:&lt;/p&gt;
583
584 &lt;p&gt;&lt;pre&gt;
585 fastboot flash unlocktoken Unlock_code.bin
586 &lt;/pre&gt;&lt;/p&gt;
587
588 &lt;p&gt;And with that final step in place, the phone was unlocked and I
589 could start stuffing the software of my own choosing into the device.
590 So far I only inserted a replacement recovery image to wipe the phone
591 before I start. We will see what happen next. Perhaps I should
592 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
593 </description>
594 </item>
595
596 <item>
597 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
598 <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>
599 <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>
600 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
601 <description>&lt;p&gt;For a while now, I have wanted to test
602 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
603 said to provide end to end encrypted communication and several of my
604 friends and family are already using it. As I by choice do not own a
605 mobile phone, this proved to be harder than expected. And I wanted to
606 have the source of the client and know that it was the code used on my
607 machine. But yesterday I managed to get it working. I used the
608 Github source, compared it to the source in
609 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
610 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
611 patches to use the production Signal servers, started the app and
612 asked for the hidden &quot;register without a smart phone&quot; form. Here is
613 the recipe how I did it.&lt;/p&gt;
614
615 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
616
617 &lt;pre&gt;
618 git clone https://github.com/WhisperSystems/Signal-Desktop.git
619 &lt;/pre&gt;
620
621 &lt;p&gt;Next, I patched the source to use the production servers, to be
622 able to talk to other Signal users:&lt;/p&gt;
623
624 &lt;pre&gt;
625 cat &amp;lt;&amp;lt;EOF | patch -p0
626 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
627 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
628 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
629 @@ -47,8 +47,8 @@
630 });
631 });
632
633 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
634 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
635 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
636 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
637 var messageReceiver;
638 window.getSocketStatus = function() {
639 if (messageReceiver) {
640 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
641 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
642 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
643 @@ -1,6 +1,6 @@
644 ;(function() {
645 &#39;use strict&#39;;
646 - var BUILD_EXPIRATION = 0;
647 + var BUILD_EXPIRATION = 1474492690000;
648
649 window.extension = window.extension || {};
650
651 EOF
652 &lt;/pre&gt;
653
654 &lt;p&gt;The first part is changing the servers, and the second is updating
655 an expiration timestamp. This timestamp need to be updated regularly.
656 It is set 90 days in the future by the build process (Gruntfile.js).
657 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
658
659 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
660 script to launch Signal in Chromium.&lt;/p&gt;
661
662 &lt;pre&gt;
663 #!/bin/sh
664 cd $(dirname $0)
665 mkdir -p userdata
666 exec chromium \
667 --proxy-server=&quot;socks://localhost:9050&quot; \
668 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
669 &lt;/pre&gt;
670
671 &lt;p&gt; The script start the app and configure Chromium to use the Tor
672 SOCKS5 proxy to make sure those controlling the Signal servers (today
673 Amazon and Whisper Systems) as well as those listening on the lines
674 will have a harder time location my laptop based on the Signal
675 connections if they use source IP address.&lt;/p&gt;
676
677 &lt;p&gt;When the script starts, one need to follow the instructions under
678 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
679 repository. I right clicked on the Signal window to get up the
680 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
681 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
682 registration form. Then I entered by land line phone number and
683 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
684 repeated the verification code three times. After entering the number
685 into the verification code field in the form, I could start using
686 Signal from my laptop.
687
688 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
689 whom and thus who know who to those controlling the central server,
690 but such leakage is hard to avoid with a centrally controlled server
691 setup. It is something to keep in mind when using Signal - the
692 content of your chats are harder to intercept, but the meta data
693 exposing your contact network is available to people you do not know.
694 So better than many options, but not great. And sadly the usage is
695 connected to my land line, thus allowing those controlling the server
696 to associate it to my home and person. I would prefer it if only
697 those I knew could tell who I was on Signal. There are options
698 avoiding such information leakage, but most of my friends are not
699 using them, so I am stuck with Signal for now.&lt;/p&gt;
700 </description>
701 </item>
702
703 <item>
704 <title>The new &quot;best&quot; multimedia player in Debian?</title>
705 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
707 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
708 <description>&lt;p&gt;When I set out a few weeks ago to figure out
709 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
710 multimedia player in Debian claimed to support most file formats /
711 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
712 the various players claimed support for. The range was from 55 to 130
713 MIME types. I suspect most media formats are supported by all
714 players, but this is not really reflected in the MimeTypes values in
715 their desktop files. There are probably also some bogus MIME types
716 listed, but it is hard to identify which one this is.&lt;/p&gt;
717
718 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
719 the players suggesting to add more MIME types to their desktop files,
720 and decided to spend some time myself improving the situation for my
721 favorite media player VLC. The fixes for VLC entered Debian unstable
722 yesterday. The complete list of MIME types can be seen on the
723 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
724 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
725
726 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
727 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
728 kmplayer. I am sure some of the other players desktop files support
729 several of the formats currently listed as working only with vlc,
730 toten and parole.&lt;/p&gt;
731
732 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
733 supported by all the tested multimedia players in Debian in their
734 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
735 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
736 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
737 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
738 it sad that video/ogg and video/webm is not supported by all the media
739 players in Debian. As far as I can tell, all of them can handle both
740 formats.&lt;/p&gt;
741 </description>
742 </item>
743
744 <item>
745 <title>A program should be able to open its own files on Linux</title>
746 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
747 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
748 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
749 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
750 decided to test its presentation tool when making the slides for a
751 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
752 wrote the first draft of the slides, saved the result and went to bed
753 the day before I would give the talk. The next day I took a plane to
754 the location where the meeting should take place, and on the plane I
755 started up koffice again to polish the talk a bit, only to discover
756 that kpresenter refused to load its own data file. I cursed a bit and
757 started making the slides again from memory, to have something to
758 present when I arrived. I tested that the saved files could be
759 loaded, and the day seemed to be rescued. I continued to polish the
760 slides until I suddenly discovered that the saved file could no longer
761 be loaded into kpresenter. In the end I had to rewrite the slides
762 three times, condensing the content until the talk became shorter and
763 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
764 kpresenter wrote inline images in a way itself could not understand.
765 Eventually that bug was fixed and kpresenter ended up being a great
766 program to make slides. The point I&#39;m trying to make is that we
767 expect a program to be able to load its own data files, and it is
768 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
769
770 &lt;p&gt;Did you ever experience a program failing to load its own data
771 files from the desktop file browser? It is not a uncommon problem. A
772 while back I discovered that the screencast recorder
773 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
774 browser would refuse to open. No video player claimed to understand
775 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
776 returning the application/ogg MIME type, which no video player I had
777 installed listed as a MIME type they would understand. I asked for
778 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
779 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
780 several video players to add video/ogg to their desktop files, to give
781 the file browser an idea what to do about Ogg Theora files. After a
782 while, the desktop file browsers in Debian started to handle the
783 output from gtk-recordmydesktop properly.&lt;/p&gt;
784
785 &lt;p&gt;But history repeats itself. A few days ago I tested the music
786 system Rosegarden again, and I discovered that the KDE and xfce file
787 browsers did not know what to do with the Rosegarden project files
788 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
789 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
790 included in the next upload. To increase the chance of me remembering
791 how to fix the problem next time some program fail to load its files
792 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
793
794 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
795 There are two sources for the MIME type of a given file. The output from
796 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
797 shared MIME type registry (under /usr/share/mime/). The file MIME
798 type is mapped to programs supporting the MIME type, and this
799 information is collected from
800 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
801 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
802 one desktop file claiming support for the MIME type of the file, it is
803 activated when asking to open a given file. If there are more, one
804 can normally select which one to use by right-clicking on the file and
805 selecting the wanted one using &#39;Open with&#39; or similar. In general
806 this work well. But it depend on each program picking a good MIME
807 type (preferably
808 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
809 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
810 registry recognizing the file and the desktop file to list the MIME
811 type in its list of supported MIME types.&lt;/p&gt;
812
813 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
814 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
815 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
816
817 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
818 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
819 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
820 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
821 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
822 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
823 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
824 &amp;lt;/mime-type&amp;gt;
825 &amp;lt;/mime-info&amp;gt;
826 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
827
828 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
829 (it is a gzipped XML file). Note, it is much better to use an
830 official MIME type registered with IANA than it is to make up ones own
831 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
832
833 &lt;p&gt;The desktop file of the rosegarden program failed to list
834 audio/x-rosegarden in its list of supported MIME types, causing the
835 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
836
837 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
838 % grep Mime /usr/share/applications/rosegarden.desktop
839 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
840 X-KDE-NativeMimeType=audio/x-rosegarden-composition
841 %
842 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
843
844 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
845 MimeType= line.&lt;/p&gt;
846
847 &lt;p&gt;If you run into a file which fail to open the correct program when
848 selected from the file browser, please check out the output from
849 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
850 MIME type is registered somewhere under /usr/share/mime/ and check
851 that some desktop file under /usr/share/applications/ is claiming
852 support for this MIME type. If not, please report a bug to have it
853 fixed. :)&lt;/p&gt;
854 </description>
855 </item>
856
857 <item>
858 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
859 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
860 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
861 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
862 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
863 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
864 related packages. The idea is to have a database of mappings between
865 hardware and packages, and pop up a dialog suggesting for the user to
866 install the packages to use a given hardware dongle. Some use cases
867 are when you insert a Yubikey, it proposes to install the software
868 needed to control it; when you insert a braille reader list it
869 proposes to install the packages needed to send text to the reader;
870 and when you insert a ColorHug screen calibrator it suggests to
871 install the driver for it. The system work well, and even have a few
872 command line tools to install firmware packages and packages for the
873 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
874
875 &lt;p&gt;The system was initially written using aptdaemon, because I found
876 good documentation and example code on how to use it. But aptdaemon
877 is going away and is generally being replaced by
878 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
879 so Isenkram needed a rewrite. And today, thanks to the great patch
880 from my college Sunil Mohan Adapa in the FreedomBox project, the
881 rewrite finally took place. I&#39;ve just uploaded a new version of
882 Isenkram into Debian Unstable with the patch included, and the default
883 for the background daemon is now to use PackageKit. To check it out,
884 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
885 and see if it is recognised.&lt;/p&gt;
886
887 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
888 the machine it is running on, you can check out the isenkram-lookup
889 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
890
891 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
892 % isenkram-lookup
893 bluez
894 cheese
895 fprintd
896 fprintd-demo
897 gkrellm-thinkbat
898 hdapsd
899 libpam-fprintd
900 pidgin-blinklight
901 thinkfan
902 tleds
903 tp-smapi-dkms
904 tp-smapi-source
905 tpb
906 %p
907 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
908
909 &lt;p&gt;The hardware mappings come from several places. The preferred way
910 is for packages to announce their hardware support using
911 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
912 cross distribution appstream system&lt;/a&gt;.
913 See
914 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
915 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
916 </description>
917 </item>
918
919 <item>
920 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
921 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
922 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
923 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
924 <description>&lt;p&gt;Yesterday I updated the
925 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
926 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
927 enterprising users. There were some nice user and visible changes.
928 First of all, both desktop menu entries now work. A design flaw in
929 one of the script made the history graph fail to show up (its PNG was
930 dumped in ~/.xsession-errors) if no controlling TTY was available.
931 The script worked when called from the command line, but not when
932 called from the desktop menu. I changed this to look for a DISPLAY
933 variable or a TTY before deciding where to draw the graph, and now the
934 graph window pop up as expected.&lt;/p&gt;
935
936 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
937 graphs (the one showing the last few hours). New is also the user of
938 colours showing charging in blue and discharge in red. The percentages
939 of this graph is relative to last full charge, not battery design
940 capacity.&lt;/p&gt;
941
942 &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;
943
944 &lt;p&gt;The other graph show the entire history of the collected battery
945 statistics, comparing it to the design capacity of the battery to
946 visualise how the battery life time get shorter over time. The red
947 line in this graph is what the previous graph considers 100 percent:
948
949 &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;
950
951 &lt;p&gt;In this graph you can see that I only charge the battery to 80
952 percent of last full capacity, and how the capacity of the battery is
953 shrinking. :(&lt;/p&gt;
954
955 &lt;p&gt;The last new feature is in the collector, which now will handle
956 more hardware models. On some hardware, Linux power supply
957 information is stored in /sys/class/power_supply/ACAD/, while the
958 collector previously only looked in /sys/class/power_supply/AC/. Now
959 both are checked to figure if there is power connected to the
960 machine.&lt;/p&gt;
961
962 &lt;p&gt;If you are interested in how your laptop battery is doing, please
963 check out the
964 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
965 in Debian unstable, or rebuild it on Jessie to get it working on
966 Debian stable. :) The upstream source is available from &lt;a
967 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
968 Patches are very welcome.&lt;/p&gt;
969
970 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
971 activities, please send Bitcoin donations to my address
972 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
973 </description>
974 </item>
975
976 <item>
977 <title>Debian now with ZFS on Linux included</title>
978 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
979 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
980 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
981 <description>&lt;p&gt;Today, after many years of hard work from many people,
982 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
983 Debian. The package status can be seen on
984 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
985 for zfs-linux&lt;/a&gt;. and
986 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
987 team status page&lt;/a&gt;. If you want to help out, please join us.
988 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
989 source code&lt;/a&gt; is available via git on Alioth. It would also be
990 great if you could help out with
991 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
992 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
993 </description>
994 </item>
995
996 <item>
997 <title>What is the best multimedia player in Debian?</title>
998 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
999 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
1000 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
1001 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
1002 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
1003
1004 &lt;p&gt;A few years ago, I had a look at the media support for Browser
1005 plugins in Debian, to get an idea which plugins to include in Debian
1006 Edu. I created a script to extract the set of supported MIME types
1007 for each plugin, and used this to find out which multimedia browser
1008 plugin supported most file formats / media types.
1009 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
1010 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
1011 not been updated for a while. But browser plugins are less relevant
1012 these days, so I thought it was time to look at standalone
1013 players.&lt;/p&gt;
1014
1015 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
1016 player when I wanted to play videos from the Norwegian National
1017 Broadcasting Company, and decided to investigate why. The cause is a
1018 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
1019 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
1020 of MIME types announced in the desktop file and the browser plugin,
1021 only to discover that there is quite a large difference between the
1022 two for VLC. This discovery made me dig up the script I used to
1023 compare browser plugins, and adjust it to compare desktop files
1024 instead, to try to figure out which multimedia player in Debian
1025 support most file formats.&lt;/p&gt;
1026
1027 &lt;p&gt;The result can be seen on the Debian Wiki, as
1028 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
1029 table listing all MIME types supported by one of the packages included
1030 in the table&lt;/a&gt;, with the package supporting most MIME types being
1031 listed first in the table.&lt;/p&gt;
1032
1033 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
1034 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1035 kmplayer. Time for the other players to update their announced MIME
1036 support?&lt;/p&gt;
1037 </description>
1038 </item>
1039
1040 <item>
1041 <title>The Pyra - handheld computer with Debian preinstalled</title>
1042 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
1043 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
1044 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
1045 <description>A friend of mine made me aware of
1046 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
1047 handheld computer which will be delivered with Debian preinstalled. I
1048 would love to get one of those for my birthday. :)&lt;/p&gt;
1049
1050 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1051 plugs and many others connectors, and include a full keyboard and a 5&quot;
1052 LCD touch screen. The 6000mAh battery is claimed to provide a whole
1053 day of battery life time, but I have not seen any independent tests
1054 confirming this. The vendor is still collecting preorders, and the
1055 last I heard last night was that 22 more orders were needed before
1056 production started.&lt;/p&gt;
1057
1058 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
1059 Debian. Please let me know if you know of any others. Is it the
1060 first computer being sold with Debian preinstalled?&lt;/p&gt;
1061 </description>
1062 </item>
1063
1064 <item>
1065 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
1066 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
1067 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
1068 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
1069 <description>&lt;p&gt;During this weekends
1070 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
1071 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
1072 to make sure there are good books about Debian available in Norwegian
1073 Bokmål, and got in touch with the people behind the
1074 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
1075 project&lt;/a&gt; to get started. If you want to help out, please start
1076 contributing using
1077 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1078 hosted weblate project page&lt;/a&gt;, and get in touch using
1079 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1080 translators mailing list&lt;/a&gt;. Please also check out
1081 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1082 contributors&lt;/a&gt;.&lt;/p&gt;
1083
1084 &lt;p&gt;The book is already available on paper in English, French and
1085 Japanese, and our goal is to get it available on paper in Norwegian
1086 Bokmål too. In addition to the paper edition, there are also EPUB and
1087 Mobi versions available. And there are incomplete translations
1088 available for many more languages.&lt;/p&gt;
1089 </description>
1090 </item>
1091
1092 <item>
1093 <title>One in two hundred Debian users using ZFS on Linux?</title>
1094 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
1095 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
1096 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
1097 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
1098 packages in Debian, and was quite surprised with what I found. I use
1099 ZFS myself at home, but did not really expect many others to do so.
1100 But I might be wrong.&lt;/p&gt;
1101
1102 &lt;p&gt;According to
1103 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
1104 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
1105 0.53% of the population, with the package installed. As far as I know
1106 the only use of the spl-linux package is as a support library for ZFS
1107 on Linux, so I use it here as proxy for measuring the number of ZFS
1108 installation on Linux in Debian. In the kFreeBSD variant of Debian
1109 the ZFS feature is already available, and there
1110 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
1111 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
1112 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
1113
1114 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
1115 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
1116 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
1117 cleared, the package is still not in Debian. The package is again in
1118 the NEW queue. Several uploads have been rejected so far because the
1119 debian/copyright file was incomplete or wrong, but there is no reason
1120 to give up. The current status can be seen on
1121 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1122 team status page&lt;/a&gt;, and
1123 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
1124 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
1125
1126 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
1127 my home server can function in the future using only official Debian
1128 packages, and the current blocker is to get the debian/copyright file
1129 accepted by the FTP masters in Debian, I decided a while back to try
1130 to help out the team. This was the background for my blog post about
1131 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
1132 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
1133 used the techniques I explored there to try to find any errors in the
1134 copyright file. It is not very easy to check every one of the around
1135 2000 files in the source package, but I hope we this time got it
1136 right. If you want to help out, check out the git source and try to
1137 find missing entries in the debian/copyright file.&lt;/p&gt;
1138 </description>
1139 </item>
1140
1141 <item>
1142 <title>Full battery stats collector is now available in Debian</title>
1143 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
1144 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
1145 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
1146 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
1147 extended collector that will collect the complete battery history for
1148 later processing and graphing. The original collector store the
1149 battery level as percentage of last full level, while the new
1150 collector also record battery vendor, model, serial number, design
1151 full level, last full level and current battery level. This make it
1152 possible to predict the lifetime of the battery as well as visualise
1153 the energy flow when the battery is charging or discharging.&lt;/p&gt;
1154
1155 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
1156 in the version 0.5.1 package in unstable. Get the new battery level graph
1157 and lifetime prediction by running:
1158
1159 &lt;p&gt;&lt;pre&gt;
1160 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1161 &lt;/pre&gt;&lt;/p&gt;
1162
1163 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
1164
1165 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
1166 entry yet):&lt;/p&gt;
1167
1168 &lt;p&gt;&lt;pre&gt;
1169 /usr/share/battery-stats/battery-stats-graph-flow
1170 &lt;/pre&gt;&lt;/p&gt;
1171
1172 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
1173 when there are few data points. The graphs look a bit better with a
1174 few years of data.&lt;/p&gt;
1175
1176 &lt;p&gt;A while back one important feature I use in the battery stats
1177 collector broke in Debian. The scripts in
1178 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
1179 suspect it happened when Jessie started using systemd, but I do not
1180 know. The issue is reported as
1181 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
1182 pm-utils. I managed to work around it by adding an udev rule to call
1183 the collector script every time the power connector is connected and
1184 disconnected. With this fix in place it was finally time to make a
1185 new release of the package, and get it into Debian.&lt;/p&gt;
1186
1187 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1188 check out the
1189 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1190 in Debian unstable, or rebuild it on Jessie to get it working on
1191 Debian stable. :) The upstream source is available from
1192 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1193 As always, patches are very welcome.&lt;/p&gt;
1194 </description>
1195 </item>
1196
1197 <item>
1198 <title>Making battery measurements a little easier in Debian</title>
1199 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
1200 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
1201 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
1202 <description>&lt;p&gt;Back in September, I blogged about
1203 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
1204 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
1205 how it showed the decay and death of this battery (now replaced). I
1206 created a simple deb package to handle the collection and graphing,
1207 but did not want to upload it to Debian as there were already
1208 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
1209 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
1210 a point of uploading a competing package when battery-stats could be
1211 fixed instead. I reported a few bugs about its non-function, and
1212 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
1213
1214 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
1215 hands. The end result is that I am now the new upstream developer of
1216 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
1217 battery-stats in Debian, and the package in Debian unstable is finally
1218 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
1219 information provided by the Linux kernel. If you install the
1220 battery-stats package from unstable now, you will be able to get a
1221 graph of the current battery fill level, to get some idea about the
1222 status of the battery. The source package build and work just fine in
1223 Debian testing and stable (and probably oldstable too, but I have not
1224 tested). The default graph you get for that system look like this:&lt;/p&gt;
1225
1226 &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;
1227
1228 &lt;p&gt;My plans for the future is to merge my old scripts into the
1229 battery-stats package, as my old scripts collected a lot more details
1230 about the battery. The scripts are merged into the upstream
1231 battery-stats git repository already, but I am not convinced they work
1232 yet, as I changed a lot of paths along the way. Will have to test a
1233 bit more before I make a new release.&lt;/p&gt;
1234
1235 &lt;p&gt;I will also consider changing the file format slightly, as I
1236 suspect the way I combine several values into one field might make it
1237 impossible to know the type of the value when using it for processing
1238 and graphing.&lt;/p&gt;
1239
1240 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
1241 battery, check out the battery-stats package in
1242 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
1243 on
1244 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1245 I would love some help to improve the system further.&lt;/p&gt;
1246 </description>
1247 </item>
1248
1249 <item>
1250 <title>Creating, updating and checking debian/copyright semi-automatically</title>
1251 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
1252 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
1253 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
1254 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
1255 details. And one of the details is the content of the
1256 debian/copyright file, which should list all relevant licenses used by
1257 the code in the package in question, preferably in
1258 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
1259 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
1260
1261 &lt;p&gt;For large packages with lots of contributors it is hard to write
1262 and update this file manually, and if you get some detail wrong, the
1263 package is normally rejected by the ftpmasters. So getting it right
1264 the first time around get the package into Debian faster, and save
1265 both you and the ftpmasters some work.. Today, while trying to figure
1266 out what was wrong with
1267 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
1268 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
1269 figuring out the options for doing this job automatically, or at least
1270 semi-automatically.&lt;/p&gt;
1271
1272 &lt;p&gt;Lucikly, there are at least two tools available for generating the
1273 file based on the code in the source package,
1274 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
1275 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
1276 not sure which one of them came first, but both seem to be able to
1277 create a sensible draft file. As far as I can tell, none of them can
1278 be trusted to get the result just right, so the content need to be
1279 polished a bit before the file is OK to upload. I found the debmake
1280 option in
1281 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
1282 blog posts from 2014&lt;/a&gt;.
1283
1284 &lt;p&gt;To generate using debmake, use the -cc option:
1285
1286 &lt;p&gt;&lt;pre&gt;
1287 debmake -cc &gt; debian/copyright
1288 &lt;/pre&gt;&lt;/p&gt;
1289
1290 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
1291 this might not be the best option.&lt;/p&gt;
1292
1293 &lt;p&gt;The cme option is based on a config parsing library, and I found
1294 this approach in
1295 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
1296 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
1297 dpkg-copyright&#39; option:
1298
1299 &lt;p&gt;&lt;pre&gt;
1300 cme update dpkg-copyright
1301 &lt;/pre&gt;&lt;/p&gt;
1302
1303 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
1304 handle UTF-8 names better than debmake.&lt;/p&gt;
1305
1306 &lt;p&gt;When the copyright file is created, I would also like some help to
1307 check if the file is correct. For this I found two good options,
1308 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
1309 to focus on license types and file matching, and is able to detect
1310 ineffective blocks in the copyright file. The latter reports missing
1311 copyright holders and years, but was confused by inconsistent license
1312 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
1313 fix all issues reported by them before uploading. But I do not know
1314 if the tools and the ftpmasters agree on what is important to fix in a
1315 copyright file, so the package might still be rejected.&lt;/p&gt;
1316
1317 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
1318 will read through the source and try to find all copyright statements.
1319 It is not comparing the result to the content of debian/copyright, but
1320 can be useful when verifying the content of the copyright file.&lt;/p&gt;
1321
1322 &lt;p&gt;Are you aware of better tools in Debian to create and update
1323 debian/copyright file. Please let me know, or blog about it on
1324 planet.debian.org.&lt;/p&gt;
1325
1326 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1327 activities, please send Bitcoin donations to my address
1328 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1329
1330 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
1331 on how to use licensecheck and cdbs to create a draft copyright file
1332
1333 &lt;p&gt;&lt;pre&gt;
1334 licensecheck --copyright -r `find * -type f` | \
1335 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
1336 &lt;/pre&gt;&lt;/p&gt;
1337
1338 &lt;p&gt;He mentioned that he normally check the generated file into the
1339 version control system to make it easier to discover license and
1340 copyright changes in the upstream source. I will try to do the same
1341 with my packages in the future.&lt;/p&gt;
1342
1343 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
1344 against using -quiet for new users, so I removed it from the proposed
1345 command line.&lt;/p&gt;
1346 </description>
1347 </item>
1348
1349 <item>
1350 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
1351 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
1352 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
1353 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
1354 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
1355 is taking shape in Debian, and one provided feature is a very
1356 convenient way to tell you which package to install to make a given
1357 firmware file available when the kernel is looking for it. This can
1358 be done using apt-file too, but that is for someone else to blog
1359 about. :)&lt;/p&gt;
1360
1361 &lt;p&gt;Here is a small recipe to find the package with a given firmware
1362 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
1363 picked from the set of firmware announced using appstream in Debian
1364 unstable. In general you would be looking for the firmware requested
1365 by the kernel during kernel module loading. To find the package
1366 providing the example file, do like this:&lt;/p&gt;
1367
1368 &lt;blockquote&gt;&lt;pre&gt;
1369 % apt install appstream
1370 [...]
1371 % apt update
1372 [...]
1373 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
1374 awk &#39;/Package:/ {print $2}&#39;
1375 firmware-qlogic
1376 %
1377 &lt;/pre&gt;&lt;/blockquote&gt;
1378
1379 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
1380 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
1381 a way appstream can use.&lt;/p&gt;
1382
1383 &lt;p&gt;This same approach can be used to find any package supporting a
1384 given MIME type. This is very useful when you get a file you do not
1385 know how to handle. First find the mime type using &lt;tt&gt;file
1386 --mime-type&lt;/tt&gt;, and next look up the package providing support for
1387 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1388 and you can find all packages handling this type like this:&lt;/p&gt;
1389
1390 &lt;blockquote&gt;&lt;pre&gt;
1391 % apt install appstream
1392 [...]
1393 % apt update
1394 [...]
1395 % appstreamcli what-provides mimetype image/svg+xml | \
1396 awk &#39;/Package:/ {print $2}&#39;
1397 bkchem
1398 phototonic
1399 inkscape
1400 shutter
1401 tetzle
1402 geeqie
1403 xia
1404 pinta
1405 gthumb
1406 karbon
1407 comix
1408 mirage
1409 viewnior
1410 postr
1411 ristretto
1412 kolourpaint4
1413 eog
1414 eom
1415 gimagereader
1416 midori
1417 %
1418 &lt;/pre&gt;&lt;/blockquote&gt;
1419
1420 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
1421 packages providing appstream metadata.&lt;/p&gt;
1422 </description>
1423 </item>
1424
1425 <item>
1426 <title>Creepy, visualise geotagged social media information - nice free software</title>
1427 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
1428 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
1429 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
1430 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
1431 with the computerised radio beacon known as a mobile phone their
1432 position is tracked by the phone company and often stored for a long
1433 time (like every time a SMS is received or sent). And if their
1434 computerised radio beacon is capable of running programs (often called
1435 mobile apps) downloaded from the Internet, these programs are often
1436 also capable of tracking their location (if the app requested access
1437 during installation). And when these programs send out information to
1438 central collection points, the location is often included, unless
1439 extra care is taken to not send the location. The provided
1440 information is used by several entities, for good and bad (what is
1441 good and bad, depend on your point of view). What is certain, is that
1442 the private sphere and the right to free movement is challenged and
1443 perhaps even eradicated for those announcing their location this way,
1444 when they share their whereabouts with private and public
1445 entities.&lt;/p&gt;
1446
1447 &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;
1448
1449 &lt;p&gt;The phone company logs provide a register of locations to check out
1450 when one want to figure out what the tracked person was doing. It is
1451 unavailable for most of us, but provided to selected government
1452 officials, company staff, those illegally buying information from
1453 unfaithful servants and crackers stealing the information. But the
1454 public information can be collected and analysed, and a free software
1455 tool to do so is called
1456 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
1457 discovered it when I read
1458 &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
1459 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
1460 November 2014, and decided to check if it was available in Debian.
1461 The python program was in Debian, but
1462 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
1463 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
1464 uploaded a new version which did not work quite right, but did not
1465 have time to fix it then. This Christmas I decided to finally try to
1466 get Creepy operational in Debian. Now a fixed version is available in
1467 Debian unstable and testing, and almost all Debian specific patches
1468 are now included
1469 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
1470
1471 &lt;p&gt;The Creepy program visualises geolocation information fetched from
1472 Twitter, Instagram, Flickr and Google+, and allow one to get a
1473 complete picture of every social media message posted recently in a
1474 given area, or track the movement of a given individual across all
1475 these services. Earlier it was possible to use the search API of at
1476 least some of these services without identifying oneself, but these
1477 days it is impossible. This mean that to use Creepy, you need to
1478 configure it to log in as yourself on these services, and provide
1479 information to them about your search interests. This should be taken
1480 into account when using Creepy, as it will also share information
1481 about yourself with the services.&lt;/p&gt;
1482
1483 &lt;p&gt;The picture above show the twitter messages sent from (or at least
1484 geotagged with a position from) the city centre of Oslo, the capital
1485 of Norway. One useful way to use Creepy is to first look at
1486 information tagged with an area of interest, and next look at all the
1487 information provided by one or more individuals who was in the area.
1488 I tested it by checking out which celebrity provide their location in
1489 twitter messages by checkout out who sent twitter messages near a
1490 Norwegian TV station, and next could track their position over time,
1491 making it possible to locate their home and work place, among other
1492 things. A similar technique have been
1493 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
1494 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
1495 tool to discover lying governments, and a useful tool to help people
1496 understand the value of the private information they provide to the
1497 public.&lt;/p&gt;
1498
1499 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
1500 it depend on several python modules currently missing in Jessie (at
1501 least python-instagram, python-flickrapi and
1502 python-requests-toolbelt).&lt;/p&gt;
1503
1504 &lt;p&gt;(I have uploaded
1505 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
1506 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
1507 Creepy program in Debian.)&lt;/p&gt;
1508 </description>
1509 </item>
1510
1511 <item>
1512 <title>Always download Debian packages using Tor - the simple recipe</title>
1513 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
1514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
1515 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
1516 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
1517 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
1518 that those listening on the Internet lines would have good reason to
1519 believe a computer have a given security hole&lt;/a&gt; if it download a
1520 security fix from a Debian mirror. This is a good reason to always
1521 use encrypted connections to the Debian mirror, to make sure those
1522 listening do not know which IP address to attack. In August, Richard
1523 Hartmann observed that encryption was not enough, when it was possible
1524 to interfere download size to security patches or the fact that
1525 download took place shortly after a security fix was released, and
1526 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
1527 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
1528 was not the first to propose this, as the
1529 &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;
1530 package by Tim Retout already existed to make it easy to convince apt
1531 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
1532 aware of that package when I read the blog post from Richard.&lt;/p&gt;
1533
1534 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
1535 sysadmins, and he set up a Tor hidden service on one of the central
1536 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1537 it possible to download packages directly between two tor nodes,
1538 making sure the network traffic always were encrypted.&lt;/p&gt;
1539
1540 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
1541 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
1542 urls with tor+http and tor+https, and using the hidden service instead
1543 of the official Debian mirror site. I recommend installing
1544 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
1545 done in /etc/.&lt;/p&gt;
1546
1547 &lt;blockquote&gt;&lt;pre&gt;
1548 apt install apt-transport-tor
1549 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
1550 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
1551 &lt;/pre&gt;&lt;/blockquote&gt;
1552
1553 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
1554 the sed commands for these too. The sed command is assuming your are
1555 using the ftp.debian.org Debian mirror. Adjust the command (or just
1556 edit the file manually) to match your mirror.&lt;/p&gt;
1557
1558 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
1559 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
1560 system, and do not work with these tor+http URLs. For
1561 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
1562 which need a recent apt version currently only in unstable. So if you
1563 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
1564
1565 &lt;p&gt;Another advantage from this change is that your machine will start
1566 using Tor regularly and at fairly random intervals (every time you
1567 update the package lists or upgrade or install a new package), thus
1568 masking other Tor traffic done from the same machine. Using Tor will
1569 become normal for the machine in question.&lt;/p&gt;
1570
1571 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
1572 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
1573 enabled. It would be great if it was the default on any Debian
1574 system.&lt;/p&gt;
1575 </description>
1576 </item>
1577
1578 <item>
1579 <title>OpenALPR, find car license plates in video streams - nice free software</title>
1580 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
1581 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
1582 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
1583 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
1584 call the car license plate numbers in those days. I would write the
1585 numbers down in my little book and compare notes with the other kids
1586 to see how many region codes we had seen and if we had seen some
1587 exotic or special region codes and numbers. It was a fun game to pass
1588 time, as we kids have plenty of it.&lt;/p&gt;
1589
1590 &lt;p&gt;A few days I came across
1591 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
1592 project&lt;/a&gt;, a free software project to automatically discover and
1593 report license plates in images and video streams, and provide the
1594 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
1595 such system for a while now, because I believe it is a bad idea that the
1596 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
1597 number plate recognition&lt;/a&gt; tool only is available in the hands of
1598 the powerful, and want it to be available also for the powerless to
1599 even the score when it comes to surveillance and sousveillance. I
1600 discovered the developer
1601 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
1602 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
1603 help him get it into shape to get the package uploaded into the Debian
1604 archive.&lt;/p&gt;
1605
1606 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
1607 it into Debian, where it currently
1608 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
1609 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
1610
1611 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
1612 for the common folks, ie those not running a large government
1613 surveillance system? Well, I plan to put it in a computer on my bike
1614 and in my car, tracking the cars nearby and allowing me to be notified
1615 when number plates on my watch list are discovered. Another use case
1616 was suggested by a friend of mine, who wanted to set it up at his home
1617 to open the car port automatically when it discovered the plate on his
1618 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1619 capable of placing his license plate number of a piece of cardboard to
1620 open his car port, men replied that it was always unlocked anyway. I
1621 guess for such use case it make sense. I am sure there are other use
1622 cases too, for those with imagination and a vision.&lt;/p&gt;
1623
1624 &lt;p&gt;If you want to build your own version of the Debian package, check
1625 out the upstream git source and symlink ./distros/debian to ./debian/
1626 before running &quot;debuild&quot; to build the source. Or wait a bit until the
1627 package show up in unstable.&lt;/p&gt;
1628 </description>
1629 </item>
1630
1631 <item>
1632 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
1633 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
1634 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
1635 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
1636 <description>&lt;p&gt;Around three years ago, I created
1637 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
1638 system&lt;/a&gt; to get a more practical solution in Debian for handing
1639 hardware related packages. A GUI system in the isenkram package will
1640 present a pop-up dialog when some hardware dongle supported by
1641 relevant packages in Debian is inserted into the machine. The same
1642 lookup mechanism to detect packages is available as command line
1643 tools in the isenkram-cli package. In addition to mapping hardware,
1644 it will also map kernel firmware files to packages and make it easy to
1645 install needed firmware packages automatically. The key for this
1646 system to work is a good way to map hardware to packages, in other
1647 words, allow packages to announce what hardware they will work
1648 with.&lt;/p&gt;
1649
1650 &lt;p&gt;I started by providing data files in the isenkram source, and
1651 adding code to download the latest version of these data files at run
1652 time, to ensure every user had the most up to date mapping available.
1653 I also added support for storing the mapping in the Packages file in
1654 the apt repositories, but did not push this approach because while I
1655 was trying to figure out how to best store hardware/package mappings,
1656 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1657 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
1658 add the hardware mapping into that data set to be able to use
1659 appstream as a data source, and this was accepted at least for the
1660 Debian version of appstream.&lt;/p&gt;
1661
1662 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
1663 and today I uploaded a new version 0.20 of isenkram adding support for
1664 appstream as a data source for mapping hardware to packages. The only
1665 package so far using appstream to announce its hardware support is my
1666 pymissile package. I got help from Matthias Klumpp with figuring out
1667 how do add the required
1668 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
1669 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
1670 this content:&lt;/p&gt;
1671
1672 &lt;blockquote&gt;&lt;pre&gt;
1673 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1674 &amp;lt;component&amp;gt;
1675 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
1676 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
1677 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
1678 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
1679 &amp;lt;description&amp;gt;
1680 &amp;lt;p&amp;gt;
1681 Pymissile provides a curses interface to control an original
1682 Marks and Spencer / Striker USB Missile Launcher, as well as a
1683 motion control script to allow a webcamera to control the
1684 launcher.
1685 &amp;lt;/p&amp;gt;
1686 &amp;lt;/description&amp;gt;
1687 &amp;lt;provides&amp;gt;
1688 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
1689 &amp;lt;/provides&amp;gt;
1690 &amp;lt;/component&amp;gt;
1691 &lt;/pre&gt;&lt;/blockquote&gt;
1692
1693 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
1694 which is a glob style match rule for hardware specific strings
1695 (modalias strings) provided by the Linux kernel. In this case, it
1696 will map to all USB devices with vendor code 1130 and product code
1697 0202.&lt;/p&gt;
1698
1699 &lt;p&gt;Note, it is important that the license of all the metadata files
1700 are compatible to have permissions to aggregate them into archive wide
1701 appstream files. Matthias suggested to use MIT or BSD licenses for
1702 these files. A challenge is figuring out a good id for the data, as
1703 it is supposed to be globally unique and shared across distributions
1704 (in other words, best to coordinate with upstream what to use). But
1705 it can be changed later or, so we went with the package name as
1706 upstream for this project is dormant.&lt;/p&gt;
1707
1708 &lt;p&gt;To get the metadata file installed in the correct location for the
1709 mirror update scripts to pick it up and include its content the
1710 appstream data source, the file must be installed in the binary
1711 package under /usr/share/appdata/. I did this by adding the following
1712 line to debian/pymissile.install:&lt;/p&gt;
1713
1714 &lt;blockquote&gt;&lt;pre&gt;
1715 debian/pymissile.metainfo.xml usr/share/appdata
1716 &lt;/pre&gt;&lt;/blockquote&gt;
1717
1718 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
1719 all packages useful on the current computer automatically, and the GUI
1720 pop-up handler will propose to install the package not already
1721 installed if a hardware dongle is inserted into the machine in
1722 question.&lt;/p&gt;
1723
1724 &lt;p&gt;Details of the modalias field in appstream is available from the
1725 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
1726
1727 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
1728 try running this command on the command line:&lt;/p&gt;
1729
1730 &lt;blockquote&gt;&lt;pre&gt;
1731 cat $(find /sys/devices/|grep modalias)
1732 &lt;/pre&gt;&lt;/blockquote&gt;
1733
1734 &lt;p&gt;To learn more about the isenkram system, please check out
1735 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
1736 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
1737 </description>
1738 </item>
1739
1740 <item>
1741 <title>The GNU General Public License is not magic pixie dust</title>
1742 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
1743 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
1744 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
1745 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
1746 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
1747 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
1748 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
1749 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
1750
1751 &lt;blockquote&gt;
1752
1753 &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;
1754
1755 &lt;blockquote&gt;
1756 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
1757
1758 The first step is to choose a
1759 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
1760 code.&lt;br/&gt;
1761
1762 The next step is, when someone fails to follow that copyleft license,
1763 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
1764
1765 and its a simple fact of our modern society that such type of
1766 work&lt;br/&gt;
1767
1768 is incredibly expensive to do and incredibly difficult to do.
1769 &lt;/blockquote&gt;
1770
1771 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
1772 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
1773 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
1774 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
1775
1776 &lt;p&gt;As the Debian Website
1777 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
1778 &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;
1779 imply, public domain and permissively licensed software can lead to
1780 the production of more proprietary software as people discover useful
1781 software, extend it and or incorporate it into their hardware or
1782 software products. Copyleft licenses such as the GNU GPL were created
1783 to close off this avenue to the production of proprietary software but
1784 such licenses are not enough. With the ongoing adoption of Free
1785 Software by individuals and groups, inevitably the community&#39;s
1786 expectations of license compliance are violated, usually out of
1787 ignorance of the way Free Software works, but not always. As Karen
1788 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
1789 Freedom&quot;&gt;FaiF&lt;/a&gt;
1790 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
1791 copyleft is nothing if no-one is willing and able to stand up in court
1792 to protect it. The reality of today&#39;s world is that legal
1793 representation is expensive, difficult and time consuming. With
1794 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
1795 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
1796 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
1797 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
1798 of the Linux project, Debian and other groups against GPL violations.
1799 In March the SFC supported a
1800 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
1801 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
1802 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
1803 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
1804 kernel. Since then two of their sponsors pulled corporate funding and
1805 conferences
1806 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
1807 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
1808 less on corporate funding and more on the broad community of
1809 individuals who support Free Software and copyleft. So the SFC has
1810 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
1811 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
1812 a community of folks who stand up for copyleft and the GPL by
1813 supporting their work on promoting and supporting copyleft and Free
1814 Software.&lt;/p&gt;
1815
1816 &lt;p&gt;If you support Free Software,
1817 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
1818 what the SFC do, agree with their
1819 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
1820 principles&lt;/a&gt;, are happy about their
1821 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
1822 work on a project that is an SFC
1823 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
1824 just want to stand up for copyleft, please join
1825 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
1826 Allan Webber&lt;/a&gt;,
1827 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
1828 Smith&lt;/a&gt;,
1829 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
1830 Bacon&lt;/a&gt;, myself and
1831 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
1832 becoming a
1833 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
1834 next week your donation will be
1835 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
1836 by an anonymous donor. Please also consider asking your employer to
1837 match your donation or become a sponsor of SFC. Don&#39;t forget to
1838 spread the word about your support for SFC via email, your blog and or
1839 social media accounts.&lt;/p&gt;
1840
1841 &lt;/blockquote&gt;
1842
1843 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
1844 of Software Freedom Conservancy myself. Perhaps you should be a
1845 supporter too?&lt;/p&gt;
1846 </description>
1847 </item>
1848
1849 <item>
1850 <title>PGP key transition statement for key EE4E02F9</title>
1851 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
1852 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
1853 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
1854 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
1855 set it up properly. I wanted to generate it offline and have it
1856 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
1857 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
1858 time to sit down with an offline machine almost took forever. But
1859 finally I&#39;ve been able to complete the process, and have now moved
1860 from my old GPG key to a new GPG key. See
1861 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
1862 full transition statement, signed with both my old and new key&lt;/a&gt; for
1863 the details. This is my new key:&lt;/p&gt;
1864
1865 &lt;pre&gt;
1866 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]
1867 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
1868 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
1869 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
1870 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
1871 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
1872 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
1873 &lt;/pre&gt;
1874
1875 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
1876 my old key.&lt;/p&gt;
1877
1878 &lt;p&gt;If you signed my old key
1879 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
1880 I&#39;d very much appreciate a signature on my new key, details and
1881 instructions in the transition statement. I m happy to reciprocate if
1882 you have a similarly signed transition statement to present.&lt;/p&gt;
1883 </description>
1884 </item>
1885
1886 <item>
1887 <title>The life and death of a laptop battery</title>
1888 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
1889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
1890 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
1891 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
1892 But this do not last. The last few laptops gave me a feeling that
1893 within a year, the life time is just a fraction of what it used to be,
1894 and it slowly become painful to use the laptop without power connected
1895 all the time. Because of this, when I got a new Thinkpad X230 laptop
1896 about two years ago, I decided to monitor its battery state to have
1897 more hard facts when the battery started to fail.&lt;/p&gt;
1898
1899 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
1900
1901 &lt;p&gt;First I tried to find a sensible Debian package to record the
1902 battery status, assuming that this must be a problem already handled
1903 by someone else. I found
1904 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
1905 which collects statistics from the battery, but it was completely
1906 broken. I sent a few suggestions to the maintainer, but decided to
1907 write my own collector as a shell script while I waited for feedback
1908 from him. Via
1909 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
1910 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
1911 discovered
1912 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
1913 available in Debian.&lt;/p&gt;
1914
1915 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
1916 battery stats ever since. Now my
1917 /var/log/hjemmenett-battery-status.log file contain around 115,000
1918 measurements, from the time the battery was working great until now,
1919 when it is unable to charge above 7% of original capacity. My
1920 collector shell script is quite simple and look like this:&lt;/p&gt;
1921
1922 &lt;pre&gt;
1923 #!/bin/sh
1924 # Inspired by
1925 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
1926 # See also
1927 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
1928 logfile=/var/log/hjemmenett-battery-status.log
1929
1930 files=&quot;manufacturer model_name technology serial_number \
1931 energy_full energy_full_design energy_now cycle_count status&quot;
1932
1933 if [ ! -e &quot;$logfile&quot; ] ; then
1934 (
1935 printf &quot;timestamp,&quot;
1936 for f in $files; do
1937 printf &quot;%s,&quot; $f
1938 done
1939 echo
1940 ) &gt; &quot;$logfile&quot;
1941 fi
1942
1943 log_battery() {
1944 # Print complete message in one echo call, to avoid race condition
1945 # when several log processes run in parallel.
1946 msg=$(printf &quot;%s,&quot; $(date +%s); \
1947 for f in $files; do \
1948 printf &quot;%s,&quot; $(cat $f); \
1949 done)
1950 echo &quot;$msg&quot;
1951 }
1952
1953 cd /sys/class/power_supply
1954
1955 for bat in BAT*; do
1956 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
1957 done
1958 &lt;/pre&gt;
1959
1960 &lt;p&gt;The script is called when the power management system detect a
1961 change in the power status (power plug in or out), and when going into
1962 and out of hibernation and suspend. In addition, it collect a value
1963 every 10 minutes. This make it possible for me know when the battery
1964 is discharging, charging and how the maximum charge change over time.
1965 The code for the Debian package
1966 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
1967 available on github&lt;/a&gt;.&lt;/p&gt;
1968
1969 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
1970
1971 &lt;pre&gt;
1972 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1973 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
1974 [...]
1975 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
1976 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
1977 &lt;/pre&gt;
1978
1979 &lt;p&gt;I wrote a small script to create a graph of the charge development
1980 over time. This graph depicted above show the slow death of my laptop
1981 battery.&lt;/p&gt;
1982
1983 &lt;p&gt;But why is this happening? Why are my laptop batteries always
1984 dying in a year or two, while the batteries of space probes and
1985 satellites keep working year after year. If we are to believe
1986 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
1987 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
1988 chance, and the fix is to not charge the Lithium-ion batteries to 100%
1989 all the time, but to stay below 90% of full charge most of the time.
1990 I&#39;ve been told that the Tesla electric cars
1991 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
1992 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
1993 100% when preparing for a longer trip (not that I would want a car
1994 like Tesla where rights to privacy is abandoned, but that is another
1995 story), which I guess is the option we should have for laptops on
1996 Linux too.&lt;/p&gt;
1997
1998 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
1999 stop charging at 80%, unless requested to charge to 100% once in
2000 preparation for a longer trip? I found
2001 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
2002 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2003 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
2004 load).&lt;/p&gt;
2005
2006 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
2007 at the start. I also wonder why the &quot;full capacity&quot; increases some
2008 times, and if it is possible to repeat the process to get the battery
2009 back to design capacity. And I wonder if the discharge and charge
2010 speed change over time, or if this stay the same. I did not yet try
2011 to write a tool to calculate the derivative values of the battery
2012 level, but suspect some interesting insights might be learned from
2013 those.&lt;/p&gt;
2014
2015 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
2016 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2017 packages instead of the tp-smapi-dkms package I had tried to use
2018 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
2019 and stop. I&#39;ve done so now, but expect my existing battery is toast
2020 and need to be replaced. The proposal is unfortunately Thinkpad
2021 specific.&lt;/p&gt;
2022 </description>
2023 </item>
2024
2025 <item>
2026 <title>New laptop - some more clues and ideas based on feedback</title>
2027 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
2028 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
2029 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
2030 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
2031 need for a new laptop, and provided very useful feedback. I wish to
2032 thank every one of these. Several pointed me to the possibility of
2033 fixing my X230, and I am already in the process of getting Lenovo to
2034 do so thanks to the on site, next day support contract covering the
2035 machine. But the battery is almost useless (I expect to replace it
2036 with a non-official battery) and I do not expect the machine to live
2037 for many more years, so it is time to plan its replacement. If I did
2038 not have a support contract, it was suggested to find replacement parts
2039 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
2040 might present a language barrier as I do not understand French.&lt;/p&gt;
2041
2042 &lt;p&gt;One tip I got was to use the
2043 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
2044 compare laptop models. It seem to have more models available than
2045 prisjakt.no. Another tip I got from someone I know have similar
2046 keyboard preferences was that the HP EliteBook 840 keyboard is not
2047 very good, and this matches my experience with earlier EliteBook
2048 keyboards I tested. Because of this, I will not consider it any further.
2049
2050 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
2051 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2052 (which is missing from the X240), and is working fairly well with
2053 Debian Sid/Unstable according to
2054 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
2055 got on the keyboard quality are not consistent. Some say the keyboard
2056 is good, others say it is ok, while others say it is not very good.
2057 Those with experience from X41 and and X60 agree that the X250
2058 keyboard is not as good as those trusty old laptops, and suggest I
2059 keep and fix my X230 instead of upgrading, or get a used X230 to
2060 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
2061 activity and battery status, which is very convenient on my X230. I&#39;m
2062 also told that the CPU fan is running very often, making it a bit
2063 noisy. In any case, the X250 do not work out of the box with Debian
2064 Stable/Jessie, one of my requirements.&lt;/p&gt;
2065
2066 &lt;p&gt;I have also gotten a few vendor proposals, one was
2067 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
2068 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
2069 The latter look very attractive to me.&lt;/p&gt;
2070
2071 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
2072 as I keep looking for a replacement.&lt;/p&gt;
2073
2074 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
2075 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
2076 different
2077 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
2078 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
2079 </description>
2080 </item>
2081
2082 <item>
2083 <title>Time to find a new laptop, as the old one is broken after only two years</title>
2084 <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>
2085 <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>
2086 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
2087 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
2088 replacement soon. The left 5 cm of the screen on my Thinkpad X230
2089 started flickering yesterday, and I suspect the cause is a broken
2090 cable, as changing the angle of the screen some times get rid of the
2091 flickering.&lt;/p&gt;
2092
2093 &lt;p&gt;My requirements have not really changed since I bought it, and is
2094 still as
2095 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
2096 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
2097 good help from
2098 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
2099 where I could select at least a few of the requirements (mouse pin,
2100 wifi, weight) and go through the rest manually. Three button mouse
2101 and a good keyboard is not available as an option, and all the three
2102 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
2103 G2) lack three mouse buttons). It is also unclear to me how good the
2104 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2105 the keyboard, even if the quality and robustness in the X series have
2106 deteriorated since X41.&lt;/p&gt;
2107
2108 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
2109 seem sensible to me? Are there better services around to search the
2110 set of available laptops for features? Please send me an email if you
2111 have suggestions.&lt;/p&gt;
2112
2113 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
2114 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
2115 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
2116 </description>
2117 </item>
2118
2119 <item>
2120 <title>How to stay with sysvinit in Debian Jessie</title>
2121 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
2122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
2123 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
2124 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
2125 sysvinit as its boot system by default. But how can one keep using
2126 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2127 courtesy of
2128 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
2129 Schubert&lt;/a&gt; and
2130 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
2131 McVittie&lt;/a&gt;.
2132
2133 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
2134 keep sysvinit as your boot system, create a file
2135 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
2136 you upgrade:&lt;/p&gt;
2137
2138 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2139 Package: systemd-sysv
2140 Pin: release o=Debian
2141 Pin-Priority: -1
2142 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2143
2144 &lt;p&gt;This file content will tell apt and aptitude to not consider
2145 installing systemd-sysv as part of any installation and upgrade
2146 solution when resolving dependencies, and thus tell it to avoid
2147 systemd as a default boot system. The end result should be that the
2148 upgraded system keep using sysvinit.&lt;/p&gt;
2149
2150 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
2151 get sysvinit installed by default (debootstrap used by
2152 debian-installer have no option for this), but one can tell the
2153 installer to switch to sysvinit before the first boot. Either by
2154 using a kernel argument to the installer, or by adding a line to the
2155 preseed file used. First, the kernel command line argument:
2156
2157 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2158 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
2159 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2160
2161 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
2162
2163 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2164 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2165 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2166
2167 &lt;p&gt;One can of course also do this after the first boot by installing
2168 the sysvinit-core package.&lt;/p&gt;
2169
2170 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
2171 sysvinit boot sequence in Debian have several hardware specific bugs
2172 on Linux caused by the fact that it is unpredictable when hardware
2173 devices show up during boot. But on the other hand, the new default
2174 boot system still have a few rough edges I hope will be fixed before
2175 Jessie is released.&lt;/p&gt;
2176
2177 &lt;p&gt;Update 2014-11-26: Inspired by
2178 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
2179 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
2180 line.&lt;/p&gt;
2181 </description>
2182 </item>
2183
2184 <item>
2185 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
2186 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
2187 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
2188 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
2189 <description>&lt;p&gt;The right to communicate with your friends and family in private,
2190 without anyone snooping, is a right every citicen have in a liberal
2191 democracy. But this right is under serious attack these days.&lt;/p&gt;
2192
2193 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
2194 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2195 the whisleblower Snowden) more expensive for Internet email,
2196 is to deliver all email using SMTP via Tor. Such SMTP option would be
2197 a nice addition to the FreedomBox project if we could send email
2198 between FreedomBox machines without leaking metadata about the emails
2199 to the people peeking on the wire. I
2200 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
2201 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
2202 lot of useful feedback and suggestions. It also became obvious to me
2203 that this was not a novel idea, as the same idea was tested and
2204 documented by Johannes Berg as early as 2006, and both
2205 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
2206 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
2207 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
2208
2209 &lt;p&gt;To implement such system one need to set up a Tor hidden service
2210 providing the SMTP protocol on port 25, and use email addresses
2211 looking like username@hidden-service-name.onion. With such addresses
2212 the connections to port 25 on hidden-service-name.onion using Tor will
2213 go to the correct SMTP server. To do this, one need to configure the
2214 Tor daemon to provide the hidden service and the mail server to accept
2215 emails for this .onion domain. To learn more about Exim configuration
2216 in Debian and test the design provided by Johannes Berg in his FAQ, I
2217 set out yesterday to create a Debian package for making it trivial to
2218 set up such SMTP over Tor service based on Debian. Getting it to work
2219 were fairly easy, and
2220 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
2221 source code for the Debian package&lt;/a&gt; is available from github. I
2222 plan to move it into Debian if further testing prove this to be a
2223 useful approach.&lt;/p&gt;
2224
2225 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
2226 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
2227 get rid of exim4). Install tor, clone the git repository mentioned
2228 above, build the deb and install it on the machine. Next, run
2229 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
2230 the instructions to get the service up and running. Restart tor and
2231 exim when it is done, and test mail delivery using swaks like
2232 this:&lt;/p&gt;
2233
2234 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2235 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2236 --to fbx@dutlqrrmjhtfa3vp.onion
2237 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2238
2239 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
2240 address with your own address to test your server. :)&lt;/p&gt;
2241
2242 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
2243 easier and more automatic. Especially the tor setup need more work.
2244 Also, the package include a tor-smtp tool written in C, but its task
2245 should probably be rewritten in some script language to make the deb
2246 architecture independent. It would probably also make the code easier
2247 to review. The tor-smtp tool currently need to listen on a socket for
2248 exim to talk to it and is started using xinetd. It would be better if
2249 no daemon and no socket is needed. I suspect it is possible to get
2250 exim to run a command line tool for delivery instead of talking to a
2251 socket, and hope to figure out how in a future version of this
2252 system.&lt;/p&gt;
2253
2254 &lt;p&gt;Until I wipe my test machine, I can be reached using the
2255 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
2256 SMTorP. :)&lt;/p&gt;
2257 </description>
2258 </item>
2259
2260 <item>
2261 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
2262 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
2263 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
2264 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
2265 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
2266 alioth.debian.org, you know the web interface is fairly slow to
2267 operate. First you visit one web page, enter the moderation password
2268 and get a new page shown with a list of all the messages to moderate
2269 and various options for each email address. This take a while for
2270 every list you moderate, and you need to do it regularly to do a good
2271 job as a list moderator. But there is a quick alternative,
2272 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
2273 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
2274 to moderate in a fraction of a second. Here is a test run on two
2275 lists I recently took over:&lt;/p&gt;
2276
2277 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2278 % time listadmin xiph
2279 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2280 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2281
2282 real 0m1.709s
2283 user 0m0.232s
2284 sys 0m0.012s
2285 %
2286 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2287
2288 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
2289 there are no message in the moderation queue. Every morning I
2290 currently moderate 68 mailman lists, and it normally take around two
2291 minutes. When I took over the two pkg-xiph lists above a few days
2292 ago, there were 400 emails waiting in the moderator queue. It took me
2293 less than 15 minutes to process them all using the listadmin
2294 program.&lt;/p&gt;
2295
2296 &lt;p&gt;If you install
2297 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
2298 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
2299 with content like this, the moderation task is a breeze:&lt;/p&gt;
2300
2301 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2302 username username@example.org
2303 spamlevel 23
2304 default discard
2305 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
2306
2307 password secret
2308 adminurl https://{domain}/mailman/admindb/{list}
2309 mailman-list@lists.example.com
2310
2311 password hidden
2312 other-list@otherserver.example.org
2313 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2314
2315 &lt;p&gt;There are other options to set as well. Check the manual page to
2316 learn the details.&lt;/p&gt;
2317
2318 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
2319 the SSL certificate is self signed or not properly signed by a
2320 generally accepted signing authority, you can set a environment
2321 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
2322
2323 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2324 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
2325 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2326
2327 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
2328 can provide an argument to the listadmin script like I do in the
2329 initial screen dump (the xiph argument). Using an argument, only
2330 lists matching the argument string will be processed. This make it
2331 quick to accept messages if you notice the moderation request in your
2332 email.&lt;/p&gt;
2333
2334 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
2335 mailing lists, as I simply do not have time to spend on that if the
2336 process was any slower. The listadmin program have saved me hours of
2337 time I could spend elsewhere over the years. It truly is nice free
2338 software.&lt;/p&gt;
2339
2340 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2341 activities, please send Bitcoin donations to my address
2342 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2343
2344 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
2345 configuration example. Also, I&#39;ve been told that the
2346 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
2347 sure why.&lt;/p&gt;
2348 </description>
2349 </item>
2350
2351 <item>
2352 <title>Debian Jessie, PXE and automatic firmware installation</title>
2353 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
2354 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
2355 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
2356 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
2357 problem that the WiFi card require some firmware to work properly.
2358 And it has been a pain to fix this using preseeding in Debian.
2359 Normally something more is needed. But thanks to
2360 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
2361 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
2362 to do this using simple preseeding.&lt;/p&gt;
2363
2364 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
2365 firmware for the hardware found in the machine (actually, requested by
2366 the kernel modules for the hardware). (It can also install user space
2367 programs supporting the hardware detected, but that is not the focus
2368 of this story.)&lt;/p&gt;
2369
2370 &lt;p&gt;To get this working in the default installation, two preeseding
2371 values are needed. First, the isenkram-cli package must be installed
2372 into the target chroot (aka the hard drive) before tasksel is executed
2373 in the pkgsel step of the debian-installer system. This is done by
2374 preseeding the base-installer/includes debconf value to include the
2375 isenkram-cli package. The package name is next passed to debootstrap
2376 for installation. With the isenkram-cli package in place, tasksel
2377 will automatically use the isenkram tasks to detect hardware specific
2378 packages for the machine being installed and install them, because
2379 isenkram-cli contain tasksel tasks.&lt;/p&gt;
2380
2381 &lt;p&gt;Second, one need to enable the non-free APT repository, because
2382 most firmware unfortunately is non-free. This is done by preseeding
2383 the apt-mirror-setup step. This is unfortunate, but for a lot of
2384 hardware it is the only option in Debian.&lt;/p&gt;
2385
2386 &lt;p&gt;The end result is two lines needed in your preseeding file to get
2387 firmware installed automatically by the installer:&lt;/p&gt;
2388
2389 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2390 base-installer base-installer/includes string isenkram-cli
2391 apt-mirror-setup apt-setup/non-free boolean true
2392 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2393
2394 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
2395 both firmware and user space packages when using this method. It also
2396 do not work well, so use version 0.15 or later. Installing both
2397 firmware and user space packages might give you a bit more than you
2398 want, so I decided to split the tasksel task in two, one for firmware
2399 and one for user space programs. The firmware task is enabled by
2400 default, while the one for user space programs is not. This split is
2401 implemented in the package currently in unstable.&lt;/p&gt;
2402
2403 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
2404 this recipe work for you. :)&lt;/p&gt;
2405
2406 &lt;p&gt;So, I bet you are wondering, how can this work. First and
2407 foremost, it work because tasksel is modular, and driven by whatever
2408 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2409 isenkram-cli package place two files for tasksel to find. First there
2410 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
2411
2412 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2413 Task: isenkram-packages
2414 Section: hardware
2415 Description: Hardware specific packages (autodetected by isenkram)
2416 Based on the detected hardware various hardware specific packages are
2417 proposed.
2418 Test-new-install: show show
2419 Relevance: 8
2420 Packages: for-current-hardware
2421
2422 Task: isenkram-firmware
2423 Section: hardware
2424 Description: Hardware specific firmware packages (autodetected by isenkram)
2425 Based on the detected hardware various hardware specific firmware
2426 packages are proposed.
2427 Test-new-install: mark show
2428 Relevance: 8
2429 Packages: for-current-hardware-firmware
2430 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2431
2432 &lt;p&gt;The key parts are Test-new-install which indicate how the task
2433 should be handled and the Packages line referencing to a script in
2434 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2435 list of packages to install. The for-current-hardware-firmware script
2436 look like this to list relevant firmware for the machine:
2437
2438 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2439 #!/bin/sh
2440 #
2441 PATH=/usr/sbin:$PATH
2442 export PATH
2443 isenkram-autoinstall-firmware -l
2444 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2445
2446 &lt;p&gt;With those two pieces in place, the firmware is installed by
2447 tasksel during the normal d-i run. :)&lt;/p&gt;
2448
2449 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
2450 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
2451 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
2452 install.&lt;/p&gt;
2453
2454 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
2455 pilots in testing this feature, as isenkram is used there now to
2456 install firmware, replacing the earlier scripts.&lt;/p&gt;
2457 </description>
2458 </item>
2459
2460 <item>
2461 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
2462 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
2463 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
2464 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
2465 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
2466 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2467 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
2468 on a screen normally showing the bread types and prizes:&lt;/p&gt;
2469
2470 &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;
2471
2472 &lt;p&gt;If it had booted as it was supposed to, I would never had known
2473 about this hidden Linux installation. It is interesting what
2474 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
2475 </description>
2476 </item>
2477
2478 <item>
2479 <title>New lsdvd release version 0.17 is ready</title>
2480 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
2481 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
2482 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
2483 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
2484 got a new set of developers a few weeks ago, after the original
2485 developer decided to step down and pass the project to fresh blood.
2486 This project is now maintained by Petter Reinholdtsen and Steve
2487 Dibb.&lt;/p&gt;
2488
2489 &lt;p&gt;I just wrapped up
2490 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
2491 new lsdvd release&lt;/a&gt;, available in git or from
2492 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
2493 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
2494 0.17.&lt;/p&gt;
2495
2496 &lt;ul&gt;
2497
2498 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
2499 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
2500 non-existant, to work around additional copy protection&lt;/li&gt;
2501 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
2502 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
2503 &lt;li&gt;Fix include orders&lt;/li&gt;
2504 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
2505 &lt;li&gt;Fix the chapter count&lt;/li&gt;
2506 &lt;li&gt;Make sure the array size and the array limit used when initialising
2507 the palette size is the same.&lt;/li&gt;
2508 &lt;li&gt;Fix array printing.&lt;/li&gt;
2509 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
2510 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
2511 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
2512 with more GCC compiler warnings.&lt;/li&gt;
2513
2514 &lt;/ul&gt;
2515
2516 &lt;p&gt;This change bring together patches for lsdvd in use in various
2517 Linux and Unix distributions, as well as patches submitted to the
2518 project the last nine years. Please check it out. :)&lt;/p&gt;
2519 </description>
2520 </item>
2521
2522 <item>
2523 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
2524 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
2525 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
2526 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
2527 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
2528 project&lt;/a&gt; provide a Linux solution for schools, including a
2529 powerful desktop with education software, a central server providing
2530 web pages, user database, user home directories, central login and PXE
2531 boot of both clients without disk and the installation to install Debian
2532 Edu on machines with disk (and a few other services perhaps to small
2533 to mention here). We in the Debian Edu team are currently working on
2534 the Jessie based version, trying to get everything in shape before the
2535 freeze, to avoid having to maintain our own package repository in the
2536 future. The
2537 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
2538 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
2539 work left. Some fatal problems block testing, breaking the installer,
2540 but it is possible to work around these to get anyway. Here is a
2541 recipe on how to get the installation limping along.&lt;/p&gt;
2542
2543 &lt;p&gt;First, download the test ISO via
2544 &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;,
2545 &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;
2546 or rsync (use
2547 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
2548 The ISO build was broken on Tuesday, so we do not get a new ISO every
2549 12 hours or so, but thankfully the ISO we already got we are able to
2550 install with some tweaking.&lt;/p&gt;
2551
2552 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
2553 (use Alt-Ctrl-F2), run&lt;/p&gt;
2554
2555 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2556 nano /usr/bin/edu-eatmydata-install
2557 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2558
2559 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
2560 optimization. Return to the installation, select the profile you want
2561 and continue. Without this change, exim4-config will fail to install
2562 due to a known bug in eatmydata.&lt;/p&gt;
2563
2564 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
2565 this do not work, figure out what your correct value would be. All my
2566 test machines need /dev/sda, so I have no advice if it do not fit
2567 your need.&lt;/p&gt;
2568
2569 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
2570 root after the initial boot from hard drive, and install the
2571 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2572 or mate. If you want several desktop options, install more than one
2573 metapackage. Once this is done, reboot and you should have a working
2574 graphical login screen. This workaround should no longer be needed
2575 once the education-tasks package version 1.801 enter testing in two
2576 days.&lt;/p&gt;
2577
2578 &lt;p&gt;I believe the ISO build will start working on two days when the new
2579 tasksel package enter testing and Steve McIntyre get a chance to
2580 update the debian-cd git repository. The eatmydata, grub and desktop
2581 issues are already fixed in unstable and testing, and should show up
2582 on the ISO as soon as the ISO build start working again. Well the
2583 eatmydata optimization is really just disabled. The proper fix
2584 require an upload by the eatmydata maintainer applying the patch
2585 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
2586 The rest have proper fixes in unstable.&lt;/p&gt;
2587
2588 &lt;p&gt;I hope this get you going with the installation testing, as we are
2589 quickly running out of time trying to get our Jessie based
2590 installation ready before the distribution freeze in a month.&lt;/p&gt;
2591 </description>
2592 </item>
2593
2594 <item>
2595 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
2596 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
2597 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
2598 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
2599 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
2600 to handle my fairly large DVD collection. It is a nice command line
2601 tool to get details about a DVD, like title, tracks, track length,
2602 etc, in XML, Perl or human readable format. But lsdvd have not seen
2603 any new development since 2006 and had a few irritating bugs affecting
2604 its use with some DVDs. Upstream seemed to be dead, and in January I
2605 sent a small probe asking for a version control repository for the
2606 project, without any reply. But I use it regularly and would like to
2607 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
2608 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
2609 the project admin, and after getting a reply from him explaining that
2610 he was no longer interested in the project, I asked if I could take
2611 over. And yesterday, I became project admin.&lt;/p&gt;
2612
2613 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
2614 maintainer interested in joining forces to maintain the upstream
2615 project, and I hope we can get a new release out fairly quickly,
2616 collecting the patches spread around on the internet into on place.
2617 I&#39;ve added the relevant Debian patches to the freshly created git
2618 repository, and expect the Gentoo patches to make it too. If you got
2619 a DVD collection and care about command line tools, check out
2620 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
2621 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
2622 list&lt;/a&gt;. :)&lt;/p&gt;
2623 </description>
2624 </item>
2625
2626 <item>
2627 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
2628 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
2629 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
2630 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
2631 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
2632 a lot quicker. When we install more than 2000 packages in
2633 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
2634 tasksel in the installer, unpacking the binary packages take forever.
2635 A part of the slow I/O issue was discussed in
2636 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
2637 much file system sync-ing done by dpkg, which is the package
2638 responsible for unpacking the binary packages. Other parts (like code
2639 executed by postinst scripts) might also sync to disk during
2640 installation. All this sync-ing to disk do not really make sense to
2641 me. If the machine crash half-way through, I start over, I do not try
2642 to salvage the half installed system. So the failure sync-ing is
2643 supposed to protect against, hardware or system crash, is not really
2644 relevant while the installer is running.&lt;/p&gt;
2645
2646 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
2647 system sync()-ing in a fairly non-intrusive way, without the need to
2648 change the code in several packages. The idea is not new, but I have
2649 not heard anyone propose the approach using dpkg-divert before. It
2650 depend on the small and clever package
2651 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
2652 uses LD_PRELOAD to replace the system functions for syncing data to
2653 disk with functions doing nothing, thus allowing programs to live
2654 dangerous while speeding up disk I/O significantly. Instead of
2655 modifying the implementation of dpkg, apt and tasksel (which are the
2656 packages responsible for selecting, fetching and installing packages),
2657 it occurred to me that we could just divert the programs away, replace
2658 them with a simple shell wrapper calling
2659 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
2660 Two days ago I decided to test the idea, and wrapped up a simple
2661 implementation for the Debian Edu udeb.&lt;/p&gt;
2662
2663 &lt;p&gt;The effect was stunning. In my first test it reduced the running
2664 time of the pkgsel step (installing tasks) from 64 to less than 44
2665 minutes (20 minutes shaved off the installation) on an old Dell
2666 Latitude D505 machine. I am not quite sure what the optimised time
2667 would have been, as I messed up the testing a bit, causing the debconf
2668 priority to get low enough for two questions to pop up during
2669 installation. As soon as I saw the questions I moved the installation
2670 along, but do not know how long the question were holding up the
2671 installation. I did some more measurements using Debian Edu Jessie,
2672 and got these results. The time measured is the time stamp in
2673 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
2674 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
2675 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2676 timing thus do not depend on how quickly the user handle the tasksel
2677 dialog.&lt;/p&gt;
2678
2679 &lt;p&gt;&lt;table&gt;
2680
2681 &lt;tr&gt;
2682 &lt;th&gt;Machine/setup&lt;/th&gt;
2683 &lt;th&gt;Original tasksel&lt;/th&gt;
2684 &lt;th&gt;Optimised tasksel&lt;/th&gt;
2685 &lt;th&gt;Reduction&lt;/th&gt;
2686 &lt;/tr&gt;
2687
2688 &lt;tr&gt;
2689 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
2690 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
2691 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
2692 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
2693 &lt;/tr&gt;
2694
2695 &lt;tr&gt;
2696 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
2697 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
2698 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
2699 &lt;td&gt;23 min 40%&lt;/td&gt;
2700 &lt;/tr&gt;
2701
2702 &lt;tr&gt;
2703 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
2704 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
2705 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
2706 &lt;td&gt;11 min 50%&lt;/td&gt;
2707 &lt;/tr&gt;
2708
2709 &lt;tr&gt;
2710 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
2711 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
2712 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
2713 &lt;td&gt;2 min 33%&lt;/td&gt;
2714 &lt;/tr&gt;
2715
2716 &lt;tr&gt;
2717 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
2718 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
2719 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
2720 &lt;td&gt;4 min 21%&lt;/td&gt;
2721 &lt;/tr&gt;
2722
2723 &lt;/table&gt;&lt;/p&gt;
2724
2725 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
2726 time is spent downloading packages. The connection to the Internet
2727 was 100Mbit/s during testing, so downloading should not be a
2728 significant factor in the measurement. Download typically took a few
2729 seconds to a few minutes, depending on the amount of packages being
2730 installed.&lt;/p&gt;
2731
2732 &lt;p&gt;The speedup is implemented by using two hooks in
2733 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
2734 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
2735 finish-install.d hook to remove the divert at the end of the
2736 installation. I picked the pre-pkgsel.d hook instead of the
2737 post-base-installer.d hook because I test using an ISO without the
2738 eatmydata package included, and the post-base-installer.d hook in
2739 Debian Edu can only operate on packages included in the ISO. The
2740 negative effect of this is that I am unable to activate this
2741 optimization for the kernel installation step in d-i. If the code is
2742 moved to the post-base-installer.d hook, the speedup would be larger
2743 for the entire installation.&lt;/p&gt;
2744
2745 &lt;p&gt;I&#39;ve implemented this in the
2746 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
2747 git repository, and plan to provide the optimization as part of the
2748 Debian Edu installation. If you want to test this yourself, you can
2749 create two files in the installer (or in an udeb). One shell script
2750 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
2751
2752 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2753 #!/bin/sh
2754 set -e
2755 . /usr/share/debconf/confmodule
2756 info() {
2757 logger -t my-pkgsel &quot;info: $*&quot;
2758 }
2759 error() {
2760 logger -t my-pkgsel &quot;error: $*&quot;
2761 }
2762 override_install() {
2763 apt-install eatmydata || true
2764 if [ -x /target/usr/bin/eatmydata ] ; then
2765 for bin in dpkg apt-get aptitude tasksel ; do
2766 file=/usr/bin/$bin
2767 # Test that the file exist and have not been diverted already.
2768 if [ -f /target$file ] ; then
2769 info &quot;diverting $file using eatmydata&quot;
2770 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
2771 &gt; /target$file.edu
2772 chmod 755 /target$file.edu
2773 in-target dpkg-divert --package debian-edu-config \
2774 --rename --quiet --add $file
2775 ln -sf ./$bin.edu /target$file
2776 else
2777 error &quot;unable to divert $file, as it is missing.&quot;
2778 fi
2779 done
2780 else
2781 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
2782 fi
2783 }
2784
2785 override_install
2786 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2787
2788 &lt;p&gt;To clean up, another shell script should go into
2789 /usr/lib/finish-install.d/ with code like this:
2790
2791 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2792 #! /bin/sh -e
2793 . /usr/share/debconf/confmodule
2794 error() {
2795 logger -t my-finish-install &quot;error: $@&quot;
2796 }
2797 remove_install_override() {
2798 for bin in dpkg apt-get aptitude tasksel ; do
2799 file=/usr/bin/$bin
2800 if [ -x /target$file.edu ] ; then
2801 rm /target$file
2802 in-target dpkg-divert --package debian-edu-config \
2803 --rename --quiet --remove $file
2804 rm /target$file.edu
2805 else
2806 error &quot;Missing divert for $file.&quot;
2807 fi
2808 done
2809 sync # Flush file buffers before continuing
2810 }
2811
2812 remove_install_override
2813 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2814
2815 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
2816 edu-eatmydata-install and call it from the pre-pkgsel.d and
2817 finish-install.d scripts.&lt;/p&gt;
2818
2819 &lt;p&gt;By now you might ask if this change should get into the normal
2820 Debian installer too? I suspect it should, but am not sure the
2821 current debian-installer coordinators find it useful enough. It also
2822 depend on the side effects of the change. I&#39;m not aware of any, but I
2823 guess we will see if the change is safe after some more testing.
2824 Perhaps there is some package in Debian depending on sync() and
2825 fsync() having effect? Perhaps it should go into its own udeb, to
2826 allow those of us wanting to enable it to do so without affecting
2827 everyone.&lt;/p&gt;
2828
2829 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
2830 will break installation of all programs using gnutls because of
2831 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
2832 eatmydata package in Debian will solve it.&lt;/p&gt;
2833
2834 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
2835 the optimization work again. And I have discovered that the
2836 dpkg-divert trick is not really needed and implemented a slightly
2837 simpler approach as part of the debian-edu-install package. See
2838 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
2839
2840 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
2841 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
2842 triggering on i386 made it into testing, and broke this installation
2843 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
2844 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
2845 </description>
2846 </item>
2847
2848 <item>
2849 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
2850 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
2851 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
2852 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
2853 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
2854 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
2855 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
2856 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
2857 learn that there is a large set of publicly available key servers to
2858 use when looking for peoples public key. So far I have used
2859 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2860 were misbehaving, but those days are ended. The servers I have used
2861 up until yesterday have been slow and some times unavailable. I hope
2862 those problems are gone now.&lt;/p&gt;
2863
2864 &lt;p&gt;Behind the round robin DNS entry of the
2865 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
2866 there is a pool of more than 100 keyservers which are checked every
2867 day to ensure they are well connected and up to date. It must be
2868 better than what I have used so far. :)&lt;/p&gt;
2869
2870 &lt;p&gt;Yesterdays speaker told me that the service is the default
2871 keyserver provided by the default configuration in GnuPG, but this do
2872 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
2873
2874 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
2875 line:&lt;/p&gt;
2876
2877 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2878 keyserver pool.sks-keyservers.net
2879 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2880
2881 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
2882 entries in DNS. Just for fun, I did just that at work, so now every
2883 user of GnuPG at the University of Oslo should find a OpenGPG
2884 keyserver automatically should their need it:&lt;/p&gt;
2885
2886 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2887 % host -t srv _pgpkey-http._tcp.uio.no
2888 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
2889 %
2890 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2891
2892 &lt;p&gt;Now if only
2893 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
2894 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
2895 very happy. It can look up a given key or search for a user ID, but I
2896 normally do not want that, but to find a trust path from my key to
2897 another key. Given a user ID or key ID, I would like to find (and
2898 download) the keys representing a signature path from my key to the
2899 key in question, to be able to get a trust path between the two keys.
2900 This is as far as I can tell not possible today. Perhaps something
2901 for a future version of the protocol?&lt;/p&gt;
2902 </description>
2903 </item>
2904
2905 <item>
2906 <title>From English wiki to translated PDF and epub via Docbook</title>
2907 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
2908 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
2909 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
2910 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
2911 project&lt;/a&gt; provide an instruction manual for teachers, system
2912 administrators and other users that contain useful tips for setting up
2913 and maintaining a Debian Edu installation. This text is about how the
2914 text processing of this manual is handled in the project.&lt;/p&gt;
2915
2916 &lt;p&gt;One goal of the project is to provide information in the native
2917 language of its users, and for this we need to handle translations.
2918 But we also want to make sure each language contain the same
2919 information, so for this we need a good way to keep the translations
2920 in sync. And we want it to be easy for our users to improve the
2921 documentation, avoiding the need to learn special formats or tools to
2922 contribute, and the obvious way to do this is to make it possible to
2923 edit the documentation using a web browser. We also want it to be
2924 easy for translators to keep the translation up to date, and give them
2925 help in figuring out what need to be translated. Here is the list of
2926 tools and the process we have found trying to reach all these
2927 goals.&lt;/p&gt;
2928
2929 &lt;p&gt;We maintain the authoritative source of our manual in the
2930 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
2931 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
2932 front page with references to the different chapters, several pages
2933 for each chapter, and finally one &quot;collection page&quot; gluing all the
2934 chapters together into one large web page (aka
2935 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
2936 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
2937 processing and translations. Thanks to the fact that the
2938 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
2939 wiki.debian.org support exporting pages in
2940 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
2941 the list of pages to export using the raw version of the AllInOne
2942 page, loop over each of them to generate a Docbook XML version of the
2943 manual. This process also download images and transform image
2944 references to use the locally downloaded images. The generated
2945 Docbook XML files are slightly broken, so some post-processing is done
2946 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
2947 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2948 a handfull of images. The XML file can now be used to generate PDF, HTML
2949 and epub versions of the English manual. This is the basic step of
2950 our process, making PDF (using dblatex), HTML (using xsltproc) and
2951 epub (using dbtoepub) version from Docbook XML, and the resulting files
2952 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
2953
2954 &lt;p&gt;But English documentation is not enough for us. We want translated
2955 documentation too, and we want to make it easy for translators to
2956 track the English original. For this we use the
2957 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
2958 which allow us to transform the English Docbook XML file into a
2959 translation file (a .pot file), usable with the normal gettext based
2960 translation tools used by those translating free software. The pot
2961 file is used to create and maintain translation files (several .po
2962 files), which the translations update with the native language
2963 translations of all titles, paragraphs and blocks of text in the
2964 original. The next step is combining the original English Docbook XML
2965 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2966 create a translated Docbook XML file (in this case
2967 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2968 translated, if the translation is not complete) Docbook XML file can
2969 then be used like the original to create a PDF, HTML and epub version
2970 of the documentation.&lt;/p&gt;
2971
2972 &lt;p&gt;The translators use different tools to edit the .po files. We
2973 recommend using
2974 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
2975 while some use emacs and vi, others can use web based editors like
2976 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
2977 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
2978 is where the .po file end up, in our git repository. Updated
2979 translations can either be committed directly to git, or submitted as
2980 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
2981 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
2982
2983 &lt;p&gt;One challenge is images, which both might need to be translated (if
2984 they show translated user applications), and are needed in different
2985 formats when creating PDF and HTML versions (epub is a HTML version in
2986 this regard). For this we transform the original PNG images to the
2987 needed density and format during build, and have a way to provide
2988 translated images by storing translated versions in
2989 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2990 package maintainers know more.&lt;/p&gt;
2991
2992 &lt;p&gt;If you wonder what the result look like, we provide
2993 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
2994 of the documentation packages on the web&lt;/a&gt;. See for example the
2995 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
2996 PDF version&lt;/a&gt; or the
2997 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
2998 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
2999 but perhaps it will be done in the future.&lt;/p&gt;
3000
3001 &lt;p&gt;To learn more, check out
3002 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
3003 debian-edu-doc package&lt;/a&gt;,
3004 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
3005 manual on the wiki&lt;/a&gt; and
3006 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
3007 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
3008 </description>
3009 </item>
3010
3011 <item>
3012 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
3013 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
3014 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
3015 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
3016 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
3017 related packages relevant for the computer installed automatically.
3018 So I implemented one, using
3019 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
3020 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
3021 run tasksel as user root. You should be presented with a new option,
3022 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
3023 select it, tasksel will install the packages isenkram claim is fit for
3024 the current hardware, hot pluggable or not.&lt;p&gt;
3025
3026 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
3027 description, and the other is the script used to extract the list of
3028 packages to install. The first part is in
3029 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
3030 this:&lt;/p&gt;
3031
3032 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3033 Task: isenkram
3034 Section: hardware
3035 Description: Hardware specific packages (autodetected by isenkram)
3036 Based on the detected hardware various hardware specific packages are
3037 proposed.
3038 Test-new-install: mark show
3039 Relevance: 8
3040 Packages: for-current-hardware
3041 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3042
3043 &lt;p&gt;The second part is in
3044 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
3045 this:&lt;/p&gt;
3046
3047 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3048 #!/bin/sh
3049 #
3050 (
3051 isenkram-lookup
3052 isenkram-autoinstall-firmware -l
3053 ) | sort -u
3054 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3055
3056 &lt;p&gt;All in all, a very short and simple implementation making it
3057 trivial to install the hardware dependent package we all may want to
3058 have installed on our machines. I&#39;ve not been able to find a way to
3059 get tasksel to tell you exactly which packages it plan to install
3060 before doing the installation. So if you are curious or careful,
3061 check the output from the isenkram-* command line tools first.&lt;/p&gt;
3062
3063 &lt;p&gt;The information about which packages are handling which hardware is
3064 fetched either from the isenkram package itself in
3065 /usr/share/isenkram/, from git.debian.org or from the APT package
3066 database (using the Modaliases header). The APT package database
3067 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3068 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
3069 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
3070 the python-apt code (bug
3071 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
3072 workaround I was able to get rid of the file descriptor leak and
3073 reduce the memory leak from ~30 MiB per hardware detection down to
3074 around 2 MiB per hardware detection. It should make the desktop
3075 daemon a lot more useful. The fix is in version 0.7 uploaded to
3076 unstable today.&lt;/p&gt;
3077
3078 &lt;p&gt;I believe the current way of mapping hardware to packages in
3079 Isenkram is is a good draft, but in the future I expect isenkram to
3080 use the AppStream data source for this. A proposal for getting proper
3081 AppStream support into Debian is floating around as
3082 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
3083 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
3084 project&lt;/a&gt; will take place this summer to improve the situation. I
3085 look forward to seeing the result, and welcome patches for isenkram to
3086 start using the information when it is ready.&lt;/p&gt;
3087
3088 &lt;p&gt;If you want your package to map to some specific hardware, either
3089 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
3090 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
3091 package&lt;/a&gt; or submit a bug report with the details to the isenkram
3092 package. See also
3093 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
3094 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
3095 the information will be migrated to AppStream eventually, but for the
3096 moment I got no better place to store it.&lt;/p&gt;
3097 </description>
3098 </item>
3099
3100 <item>
3101 <title>FreedomBox milestone - all packages now in Debian Sid</title>
3102 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
3103 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
3104 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
3105 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3106 project&lt;/a&gt; is working on providing the software and hardware to make
3107 it easy for non-technical people to host their data and communication
3108 at home, and being able to communicate with their friends and family
3109 encrypted and away from prying eyes. It is still going strong, and
3110 today a major mile stone was reached.&lt;/p&gt;
3111
3112 &lt;p&gt;Today, the last of the packages currently used by the project to
3113 created the system images were accepted into Debian Unstable. It was
3114 the freedombox-setup package, which is used to configure the images
3115 during build and on the first boot. Now all one need to get going is
3116 the build code from the freedom-maker git repository and packages from
3117 Debian. And once the freedombox-setup package enter testing, we can
3118 build everything directly from Debian. :)&lt;/p&gt;
3119
3120 &lt;p&gt;Some key packages used by Freedombox are
3121 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
3122 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
3123 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
3124 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
3125 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
3126 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
3127 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
3128 are plans to integrate more packages into the setup. User
3129 documentation is maintained on the Debian wiki. Please
3130 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
3131 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
3132
3133 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
3134 setup, run this on a Debian machine using a user with sudo rights to
3135 become root:&lt;/p&gt;
3136
3137 &lt;p&gt;&lt;pre&gt;
3138 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3139 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3140 u-boot-tools
3141 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3142 freedom-maker
3143 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3144 &lt;/pre&gt;&lt;/p&gt;
3145
3146 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3147 devices. See the README in the freedom-maker git repo for more
3148 details on the build. If you do not want all three images, trim the
3149 make line. Note that the virtualbox-image target is not really
3150 virtualbox specific. It create a x86 image usable in kvm, qemu,
3151 vmware and any other x86 virtual machine environment. You might need
3152 the version of vmdebootstrap in Jessie to get the build working, as it
3153 include fixes for a race condition with kpartx.&lt;/p&gt;
3154
3155 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3156 method, boot a Debian Wheezy ISO and use this boot argument to load
3157 the preseed values:&lt;/p&gt;
3158
3159 &lt;p&gt;&lt;pre&gt;
3160 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;
3161 &lt;/pre&gt;&lt;/p&gt;
3162
3163 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
3164 it still work.&lt;/p&gt;
3165
3166 &lt;p&gt;If you wonder how to help, one task you could look at is using
3167 systemd as the boot system. It will become the default for Linux in
3168 Jessie, so we need to make sure it is usable on the Freedombox. I did
3169 a simple test a few weeks ago, and noticed dnsmasq failed to start
3170 during boot when using systemd. I suspect there are other problems
3171 too. :) To detect problems, there is a test suite included, which can
3172 be run from the plinth web interface.&lt;/p&gt;
3173
3174 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3175 us get the new release published. :) Please join us on
3176 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3177 irc.debian.org)&lt;/a&gt; and
3178 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3179 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3180 </description>
3181 </item>
3182
3183 <item>
3184 <title>S3QL, a locally mounted cloud file system - nice free software</title>
3185 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
3186 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
3187 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
3188 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
3189 solution for use at home. My requirements are simple, it must be
3190 cheap and locally encrypted (in other words, I keep the encryption
3191 keys, the storage provider do not have access to my private files).
3192 One idea me and my friends had many years ago, before the cloud
3193 storage providers showed up, was to use Google mail as storage,
3194 writing a Linux block device storing blocks as emails in the mail
3195 service provided by Google, and thus get heaps of free space. On top
3196 of this one can add encryption, RAID and volume management to have
3197 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3198 I never found time to implement such system. But the last few weeks I
3199 have looked at a system called
3200 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
3201 mounted network backed file system with the features I need.&lt;/p&gt;
3202
3203 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
3204 handling several different storage providers, any with Amazon S3,
3205 Google Drive or OpenStack API. There are heaps of such storage
3206 providers. S3QL can also use a local directory as storage, which
3207 combined with sshfs allow for file storage on any ssh server. S3QL
3208 include support for encryption, compression, de-duplication, snapshots
3209 and immutable file systems, allowing me to mount the remote storage as
3210 a local mount point, look at and use the files as if they were local,
3211 while the content is stored in the cloud as well. This allow me to
3212 have a backup that should survive fire. The file system can not be
3213 shared between several machines at the same time, as only one can
3214 mount it at the time, but any machine with the encryption key and
3215 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
3216
3217 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
3218 package is included already. So to get started, run &lt;tt&gt;apt-get
3219 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
3220 Greenqloud, after reading their nice recipe on
3221 &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
3222 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
3223 in Iceland more than those in USA when it come to keeping my personal
3224 data safe and private, and thus would rather spend money on a company
3225 in Iceland. Another nice recipe is available from the article
3226 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
3227 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
3228 Admin magazine. When the provider is picked, figure out how to get
3229 the API key needed to connect to the storage API. With Greencloud,
3230 the key did not show up until I had added payment details to my
3231 account.&lt;/p&gt;
3232
3233 &lt;p&gt;Armed with the API access details, it is time to create the file
3234 system. First, create a new bucket in the cloud. This bucket is the
3235 file system storage area. I picked a bucket name reflecting the
3236 machine that was going to store data there, but any name will do.
3237 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
3238 the API login and password, and a locally created password. Store it
3239 all in ~root/.s3ql/authinfo2 like this:
3240
3241 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3242 [s3c]
3243 storage-url: s3c://s.greenqloud.com:443/bucket-name
3244 backend-login: API-login
3245 backend-password: API-password
3246 fs-passphrase: local-password
3247 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3248
3249 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
3250 but any sensible way to create a fairly random password should do it.
3251 Armed with these details, it is now time to run mkfs, entering the API
3252 details and password to create it:&lt;/p&gt;
3253
3254 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3255 # mkdir -m 700 /var/lib/s3ql-cache
3256 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3257 --ssl s3c://s.greenqloud.com:443/bucket-name
3258 Enter backend login:
3259 Enter backend password:
3260 Before using S3QL, make sure to read the user&#39;s guide, especially
3261 the &#39;Important Rules to Avoid Loosing Data&#39; section.
3262 Enter encryption password:
3263 Confirm encryption password:
3264 Generating random encryption key...
3265 Creating metadata tables...
3266 Dumping metadata...
3267 ..objects..
3268 ..blocks..
3269 ..inodes..
3270 ..inode_blocks..
3271 ..symlink_targets..
3272 ..names..
3273 ..contents..
3274 ..ext_attributes..
3275 Compressing and uploading metadata...
3276 Wrote 0.00 MB of compressed metadata.
3277 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3278
3279 &lt;p&gt;The next step is mounting the file system to make the storage available.
3280
3281 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3282 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3283 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3284 Using 4 upload threads.
3285 Downloading and decompressing metadata...
3286 Reading metadata...
3287 ..objects..
3288 ..blocks..
3289 ..inodes..
3290 ..inode_blocks..
3291 ..symlink_targets..
3292 ..names..
3293 ..contents..
3294 ..ext_attributes..
3295 Mounting filesystem...
3296 # df -h /s3ql
3297 Filesystem Size Used Avail Use% Mounted on
3298 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
3299 #
3300 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3301
3302 &lt;p&gt;The file system is now ready for use. I use rsync to store my
3303 backups in it, and as the metadata used by rsync is downloaded at
3304 mount time, no network traffic (and storage cost) is triggered by
3305 running rsync. To unmount, one should not use the normal umount
3306 command, as this will not flush the cache to the cloud storage, but
3307 instead running the umount.s3ql command like this:
3308
3309 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3310 # umount.s3ql /s3ql
3311 #
3312 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3313
3314 &lt;p&gt;There is a fsck command available to check the file system and
3315 correct any problems detected. This can be used if the local server
3316 crashes while the file system is mounted, to reset the &quot;already
3317 mounted&quot; flag. This is what it look like when processing a working
3318 file system:&lt;/p&gt;
3319
3320 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3321 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
3322 Using cached metadata.
3323 File system seems clean, checking anyway.
3324 Checking DB integrity...
3325 Creating temporary extra indices...
3326 Checking lost+found...
3327 Checking cached objects...
3328 Checking names (refcounts)...
3329 Checking contents (names)...
3330 Checking contents (inodes)...
3331 Checking contents (parent inodes)...
3332 Checking objects (reference counts)...
3333 Checking objects (backend)...
3334 ..processed 5000 objects so far..
3335 ..processed 10000 objects so far..
3336 ..processed 15000 objects so far..
3337 Checking objects (sizes)...
3338 Checking blocks (referenced objects)...
3339 Checking blocks (refcounts)...
3340 Checking inode-block mapping (blocks)...
3341 Checking inode-block mapping (inodes)...
3342 Checking inodes (refcounts)...
3343 Checking inodes (sizes)...
3344 Checking extended attributes (names)...
3345 Checking extended attributes (inodes)...
3346 Checking symlinks (inodes)...
3347 Checking directory reachability...
3348 Checking unix conventions...
3349 Checking referential integrity...
3350 Dropping temporary indices...
3351 Backing up old metadata...
3352 Dumping metadata...
3353 ..objects..
3354 ..blocks..
3355 ..inodes..
3356 ..inode_blocks..
3357 ..symlink_targets..
3358 ..names..
3359 ..contents..
3360 ..ext_attributes..
3361 Compressing and uploading metadata...
3362 Wrote 0.89 MB of compressed metadata.
3363 #
3364 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3365
3366 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
3367 quick, about the same speed as local file access. Uploading large
3368 amount of data is to me limited by the bandwidth out of and into my
3369 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
3370 which is very close to my upload speed, and downloading the same
3371 Debian installation ISO gave me 610 kiB/s, close to my download speed.
3372 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
3373 network, not the file system code. I do not know what a good cache
3374 size would be, but suspect that the cache should e larger than your
3375 working set.&lt;/p&gt;
3376
3377 &lt;p&gt;I mentioned that only one machine can mount the file system at the
3378 time. If another machine try, it is told that the file system is
3379 busy:&lt;/p&gt;
3380
3381 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3382 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3383 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3384 Using 8 upload threads.
3385 Backend reports that fs is still mounted elsewhere, aborting.
3386 #
3387 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3388
3389 &lt;p&gt;The file content is uploaded when the cache is full, while the
3390 metadata is uploaded once every 24 hour by default. To ensure the
3391 file system content is flushed to the cloud, one can either umount the
3392 file system, or ask S3QL to flush the cache and metadata using
3393 s3qlctrl:
3394
3395 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3396 # s3qlctrl upload-meta /s3ql
3397 # s3qlctrl flushcache /s3ql
3398 #
3399 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3400
3401 &lt;p&gt;If you are curious about how much space your data uses in the
3402 cloud, and how much compression and deduplication cut down on the
3403 storage usage, you can use s3qlstat on the mounted file system to get
3404 a report:&lt;/p&gt;
3405
3406 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3407 # s3qlstat /s3ql
3408 Directory entries: 9141
3409 Inodes: 9143
3410 Data blocks: 8851
3411 Total data size: 22049.38 MB
3412 After de-duplication: 21955.46 MB (99.57% of total)
3413 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
3414 Database size: 2.39 MB (uncompressed)
3415 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3416 #
3417 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3418
3419 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
3420 storage. I did not try to locate them all, but am aware of at least
3421 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
3422 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
3423 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
3424 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
3425 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
3426 accept payment in Bitcoin. Pick one that suit your need. Some of
3427 them provide several GiB of free storage, but the prize models are
3428 quite different and you will have to figure out what suits you
3429 best.&lt;/p&gt;
3430
3431 &lt;p&gt;While researching this blog post, I had a look at research papers
3432 and posters discussing the S3QL file system. There are several, which
3433 told me that the file system is getting a critical check by the
3434 science community and increased my confidence in using it. One nice
3435 poster is titled
3436 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
3437 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3438 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
3439 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3440 and Pamela Smith. Please have a look.&lt;/p&gt;
3441
3442 &lt;p&gt;Given my problems with different file systems earlier, I decided to
3443 check out the mounted S3QL file system to see if it would be usable as
3444 a home directory (in other word, that it provided POSIX semantics when
3445 it come to locking and umask handling etc). Running
3446 &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
3447 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
3448 no error was found. So the file system can be used for home
3449 directories, if one chooses to do so.&lt;/p&gt;
3450
3451 &lt;p&gt;If you do not want a locally file system, and want something that
3452 work without the Linux fuse file system, I would like to mention the
3453 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
3454 provide locally encrypted backup using a command line client. It have
3455 a nicer access control system, where one can split out read and write
3456 access, allowing some systems to write to the backup and others to
3457 only read from it.&lt;/p&gt;
3458
3459 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3460 activities, please send Bitcoin donations to my address
3461 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3462 </description>
3463 </item>
3464
3465 <item>
3466 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
3467 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
3468 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
3469 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
3470 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3471 project&lt;/a&gt; is working on providing the software and hardware for
3472 making it easy for non-technical people to host their data and
3473 communication at home, and being able to communicate with their
3474 friends and family encrypted and away from prying eyes. It has been
3475 going on for a while, and is slowly progressing towards a new test
3476 release (0.2).&lt;/p&gt;
3477
3478 &lt;p&gt;And what day could be better than the Pi day to announce that the
3479 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
3480 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3481 system), and can also be installed using a Debian installer preseed
3482 file. The Debian based Freedombox is now based on Debian Jessie,
3483 where most of the needed packages used are already present. Only one,
3484 the freedombox-setup package, is missing. To try to build your own
3485 boot image to test the current status, fetch the freedom-maker scripts
3486 and build using
3487 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
3488 with a user with sudo access to become root:
3489
3490 &lt;pre&gt;
3491 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3492 freedom-maker
3493 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3494 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3495 u-boot-tools
3496 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3497 &lt;/pre&gt;
3498
3499 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3500 devices. See the README for more details on the build. If you do not
3501 want all three images, trim the make line. But note that thanks to &lt;a
3502 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
3503 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
3504 kpartx call.&lt;/p&gt;
3505
3506 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3507 method, boot a Debian Wheezy ISO and use this boot argument to load
3508 the preseed values:&lt;/p&gt;
3509
3510 &lt;pre&gt;
3511 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;
3512 &lt;/pre&gt;
3513
3514 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
3515 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
3516 currently hang while setting up APT sources. Killing the
3517 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
3518 installation will get the installation going. This affect all
3519 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
3520
3521 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3522 us get the new release published. :) Please join us on
3523 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3524 irc.debian.org)&lt;/a&gt; and
3525 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3526 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3527 </description>
3528 </item>
3529
3530 <item>
3531 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
3532 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
3533 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
3534 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
3535 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
3536 innetgr tools, because I needed them in
3537 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
3538 ng-utils, and it has served me well. I placed the project under the
3539 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
3540 repository. But many years ago, the CVS repository was dropped (lost,
3541 not migrated to new hardware, not sure), and the project have lacked a
3542 proper home since then.&lt;/p&gt;
3543
3544 &lt;p&gt;Last summer, I had a look at the package and made a new release
3545 fixing a irritating crash bug, but was unable to store the changes in
3546 a proper source control system. I applied for a project on
3547 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
3548 to follow up on it. Until today. :)&lt;/p&gt;
3549
3550 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
3551 now have a new home, and a git repository with the highlight of the
3552 history of the project. I published all release tarballs and imported
3553 them into the git repository. As the project is really stable and not
3554 expected to gain new features any time soon, I decided to make a new
3555 release and call it 1.0. Visit the new project home on
3556 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
3557 if you want to check it out. The new version is also uploaded into
3558 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
3559 </description>
3560 </item>
3561
3562 <item>
3563 <title>Testing sysvinit from experimental in Debian Hurd</title>
3564 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
3565 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
3566 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
3567 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
3568 their changes into sysvinit, to allow them to use the normal sysvinit
3569 boot system instead of their old one. This follow up on the
3570 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
3571 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
3572 get Debian on Hurd working more like Debian on Linux. To get started,
3573 I downloaded a prebuilt hard disk image from
3574 &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;,
3575 and started it using virt-manager.&lt;/p&gt;
3576
3577 &lt;p&gt;The first think I had to do after logging in (root without any
3578 password) was to get the network operational. I followed
3579 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
3580 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
3581 commands as root to get the machine to accept a IP address from the
3582 kvm internal DHCP server:&lt;/p&gt;
3583
3584 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3585 settrans -fgap /dev/netdde /hurd/netdde
3586 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
3587 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
3588 dhclient /dev/eth0
3589 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3590
3591 &lt;p&gt;After this, the machine had internet connectivity, and I could
3592 upgrade it and install the sysvinit packages from experimental and
3593 enable it as the default boot system in Hurd.&lt;/p&gt;
3594
3595 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
3596 running on the machine it for ssh login to work a password need to be
3597 set. Also, note that a bug somewhere in openssh on Hurd block
3598 compression from working. Remember to turn that off on the client
3599 side.&lt;/p&gt;
3600
3601 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
3602 stuff:&lt;/p&gt;
3603
3604 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3605 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
3606 deb http://http.debian.net/debian/ experimental main
3607 EOF
3608 apt-get update
3609 apt-get dist-upgrade
3610 apt-get install -t experimental initscripts sysv-rc sysvinit \
3611 sysvinit-core sysvinit-utils
3612 update-alternatives --config runsystem
3613 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3614
3615 &lt;p&gt;To reboot after switching boot system, you have to use
3616 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
3617 yet a sysvinit process able to receive the signals from the normal
3618 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
3619 upgrading every package and rebooting, the network come up with DHCP
3620 after boot as it should, and the settrans/pkill hack mentioned at the
3621 start is no longer needed. But for some strange reason, there are no
3622 longer any login prompt in the virtual console, so I logged in using
3623 ssh instead.
3624
3625 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
3626 fail some times. No idea what the cause is, but hope the Hurd porters
3627 figure it out. At least Justus said on IRC (#debian-hurd on
3628 irc.debian.org) that they are aware of the problem. A way to reduce
3629 the impact is to upgrade to the Hurd packages built by Justus by
3630 adding this repository to the machine:&lt;/p&gt;
3631
3632 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3633 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
3634 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3635 EOF
3636 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3637
3638 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
3639 http://ftp.debian-ports.org/debian, because some of the packages in
3640 unstable do not yet include the required patches that are lingering in
3641 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
3642
3643 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3644 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
3645 i emacs - GNU Emacs editor (metapackage)
3646 i gdb - GNU Debugger
3647 i hurd-recommended - Miscellaneous translators
3648 i isc-dhcp-client - ISC DHCP client
3649 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3650 i libc-bin - Embedded GNU C Library: Binaries
3651 i libc-dev-bin - Embedded GNU C Library: Development binaries
3652 i libc0.3 - Embedded GNU C Library: Shared libraries
3653 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3654 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3655 i multiarch-support - Transitional package to ensure multiarch compatibilit
3656 i A x11-common - X Window System (X.Org) infrastructure
3657 i xorg - X.Org X Window System
3658 i A xserver-xorg - X.Org X server
3659 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3660 #
3661 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3662
3663 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
3664 X.org did not work out of the box and I never took the time to follow
3665 the porters instructions to fix it. This time I was interested in the
3666 command line stuff.&lt;p&gt;
3667 </description>
3668 </item>
3669
3670 <item>
3671 <title>New chrpath release 0.16</title>
3672 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
3673 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
3674 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
3675 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
3676 find problems in C, C++ and Java code using static source code
3677 analysis. It can detect a lot of different problems, and is very
3678 useful to find memory and locking bugs in the error handling part of
3679 the source. The company behind it provide
3680 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
3681 a community service&lt;/a&gt;, and many hundred free software projects are
3682 already checked. A few days ago I decided to have a closer look at
3683 the Coverity system, and discovered that the
3684 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
3685 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
3686 projects I am involved with was already registered. But these are
3687 fairly big, and I would also like to have a small and easy project to
3688 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
3689 checking of the chrpath project&lt;/a&gt;. It was
3690 added to the checker and discovered seven potential defects. Six of
3691 these were real, mostly resource &quot;leak&quot; when the program detected an
3692 error. Nothing serious, as the resources would be released a fraction
3693 of a second later when the program exited because of the error, but it
3694 is nice to do it right in case the source of the program some time in
3695 the future end up in a library. Having fixed all defects and added
3696 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
3697 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
3698 publish a new release. These are the release notes:&lt;/p&gt;
3699
3700 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
3701
3702 &lt;ul&gt;
3703
3704 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
3705 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
3706 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
3707
3708 &lt;/ul&gt;
3709
3710 &lt;p&gt;You can
3711 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
3712 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
3713 project if something is wrong with the new release. The test suite
3714 did not discover any old errors, so if you find a new one, please also
3715 include a test suite check.&lt;/p&gt;
3716 </description>
3717 </item>
3718
3719 <item>
3720 <title>New chrpath release 0.15</title>
3721 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
3722 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
3723 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
3724 <description>&lt;p&gt;After many years break from the package and a vain hope that
3725 development would be continued by someone else, I finally pulled my
3726 acts together this morning and wrapped up a new release of chrpath,
3727 the command line tool to modify the rpath and runpath of already
3728 compiled ELF programs. The update was triggered by the persistence of
3729 Isha Vishnoi at IBM, which needed a new config.guess file to get
3730 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
3731 is working on. I checked the
3732 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
3733 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
3734 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
3735 packages for interesting patches (failed to find the source from
3736 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3737 These are the release notes:&lt;/p&gt;
3738
3739 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
3740
3741 &lt;ul&gt;
3742
3743 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
3744 with newer architectures. Thanks to isha vishnoi for the heads
3745 up.&lt;/li&gt;
3746
3747 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
3748
3749 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3750 Matthias Klose.&lt;/li&gt;
3751
3752 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
3753 Petr Machata found in Fedora.&lt;/li&gt;
3754
3755 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
3756 .dynamic is a NULL terminated string. Based on patch found in
3757 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
3758
3759 &lt;/ul&gt;
3760
3761 &lt;p&gt;You can
3762 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
3763 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
3764 project if something is wrong with the new release. The test suite
3765 did not discover any old errors, so if you find a new one, please also
3766 include a testsuite check.&lt;/p&gt;
3767 </description>
3768 </item>
3769
3770 <item>
3771 <title>Debian init.d boot script example for rsyslog</title>
3772 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
3773 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
3774 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
3775 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
3776 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
3777 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
3778 init.d scripts at all. Here is an example init.d script, ie a rewrite
3779 of /etc/init.d/rsyslog:&lt;/p&gt;
3780
3781 &lt;p&gt;&lt;pre&gt;
3782 #!/lib/init/init-d-script
3783 ### BEGIN INIT INFO
3784 # Provides: rsyslog
3785 # Required-Start: $remote_fs $time
3786 # Required-Stop: umountnfs $time
3787 # X-Stop-After: sendsigs
3788 # Default-Start: 2 3 4 5
3789 # Default-Stop: 0 1 6
3790 # Short-Description: enhanced syslogd
3791 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3792 # It is quite compatible to stock sysklogd and can be
3793 # used as a drop-in replacement.
3794 ### END INIT INFO
3795 DESC=&quot;enhanced syslogd&quot;
3796 DAEMON=/usr/sbin/rsyslogd
3797 &lt;/pre&gt;&lt;/p&gt;
3798
3799 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
3800 script was 137 lines, and the above is just 15 lines, most of it meta
3801 info/comments.&lt;/p&gt;
3802
3803 &lt;p&gt;How to do this, you ask? Well, one create a new script
3804 /lib/init/init-d-script looking something like this:
3805
3806 &lt;p&gt;&lt;pre&gt;
3807 #!/bin/sh
3808
3809 # Define LSB log_* functions.
3810 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
3811 # and status_of_proc is working.
3812 . /lib/lsb/init-functions
3813
3814 #
3815 # Function that starts the daemon/service
3816
3817 #
3818 do_start()
3819 {
3820 # Return
3821 # 0 if daemon has been started
3822 # 1 if daemon was already running
3823 # 2 if daemon could not be started
3824 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
3825 || return 1
3826 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3827 $DAEMON_ARGS \
3828 || return 2
3829 # Add code here, if necessary, that waits for the process to be ready
3830 # to handle requests from services started subsequently which depend
3831 # on this one. As a last resort, sleep for some time.
3832 }
3833
3834 #
3835 # Function that stops the daemon/service
3836 #
3837 do_stop()
3838 {
3839 # Return
3840 # 0 if daemon has been stopped
3841 # 1 if daemon was already stopped
3842 # 2 if daemon could not be stopped
3843 # other if a failure occurred
3844 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
3845 RETVAL=&quot;$?&quot;
3846 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
3847 # Wait for children to finish too if this is a daemon that forks
3848 # and if the daemon is only ever run from this initscript.
3849 # If the above conditions are not satisfied then add some other code
3850 # that waits for the process to drop all resources that could be
3851 # needed by services started subsequently. A last resort is to
3852 # sleep for some time.
3853 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
3854 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
3855 # Many daemons don&#39;t delete their pidfiles when they exit.
3856 rm -f $PIDFILE
3857 return &quot;$RETVAL&quot;
3858 }
3859
3860 #
3861 # Function that sends a SIGHUP to the daemon/service
3862 #
3863 do_reload() {
3864 #
3865 # If the daemon can reload its configuration without
3866 # restarting (for example, when it is sent a SIGHUP),
3867 # then implement that here.
3868 #
3869 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
3870 return 0
3871 }
3872
3873 SCRIPTNAME=$1
3874 scriptbasename=&quot;$(basename $1)&quot;
3875 echo &quot;SN: $scriptbasename&quot;
3876 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
3877 script=&quot;$1&quot;
3878 shift
3879 . $script
3880 else
3881 exit 0
3882 fi
3883
3884 NAME=$(basename $DAEMON)
3885 PIDFILE=/var/run/$NAME.pid
3886
3887 # Exit if the package is not installed
3888 #[ -x &quot;$DAEMON&quot; ] || exit 0
3889
3890 # Read configuration variable file if it is present
3891 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
3892
3893 # Load the VERBOSE setting and other rcS variables
3894 . /lib/init/vars.sh
3895
3896 case &quot;$1&quot; in
3897 start)
3898 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
3899 do_start
3900 case &quot;$?&quot; in
3901 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
3902 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
3903 esac
3904 ;;
3905 stop)
3906 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
3907 do_stop
3908 case &quot;$?&quot; in
3909 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
3910 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
3911 esac
3912 ;;
3913 status)
3914 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
3915 ;;
3916 #reload|force-reload)
3917 #
3918 # If do_reload() is not implemented then leave this commented out
3919 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
3920 #
3921 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
3922 #do_reload
3923 #log_end_msg $?
3924 #;;
3925 restart|force-reload)
3926 #
3927 # If the &quot;reload&quot; option is implemented then remove the
3928 # &#39;force-reload&#39; alias
3929 #
3930 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
3931 do_stop
3932 case &quot;$?&quot; in
3933 0|1)
3934 do_start
3935 case &quot;$?&quot; in
3936 0) log_end_msg 0 ;;
3937 1) log_end_msg 1 ;; # Old process is still running
3938 *) log_end_msg 1 ;; # Failed to start
3939 esac
3940 ;;
3941 *)
3942 # Failed to stop
3943 log_end_msg 1
3944 ;;
3945 esac
3946 ;;
3947 *)
3948 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
3949 exit 3
3950 ;;
3951 esac
3952
3953 :
3954 &lt;/pre&gt;&lt;/p&gt;
3955
3956 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
3957 lot. I did not really polish the approach, so it might not always
3958 work out of the box, but you get the idea. I did not try very hard to
3959 optimize it nor make it more robust either.&lt;/p&gt;
3960
3961 &lt;p&gt;A better argument for switching init system in Debian than reducing
3962 the size of init scripts (which is a good thing to do anyway), is to
3963 get boot system that is able to handle the kernel events sensibly and
3964 robustly, and do not depend on the boot to run sequentially. The boot
3965 and the kernel have not behaved sequentially in years.&lt;/p&gt;
3966 </description>
3967 </item>
3968
3969 <item>
3970 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
3971 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
3972 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
3973 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
3974 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
3975 remote display access is the preferred solution with oVirt and RedHat
3976 Enterprise Virtualization, and I was sad to discover the other day
3977 that the browser plugin needed to use these systems seamlessly was
3978 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
3979 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
3980 2013-04-01, so I decided to wrap up a package based on the great work
3981 from Cajus Pollmeier and put it in a collab-maint maintained git
3982 repository to get a package I could use. I would very much like
3983 others to help me maintain the package (or just take over, I do not
3984 mind), but as no-one had volunteered so far, I just uploaded it to
3985 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
3986
3987 &lt;p&gt;The source is now available from
3988 &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;
3989 </description>
3990 </item>
3991
3992 <item>
3993 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
3994 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
3995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
3996 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
3997 <description>&lt;p&gt;The
3998 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
3999 program is a a very nice system to create virtual machine images. It
4000 create a image file, add a partition table, mount it and run
4001 debootstrap in the mounted directory to create a Debian system on a
4002 stick. Yesterday, I decided to try to teach it how to make images for
4003 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
4004 of a plan to simplify the build system for
4005 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
4006 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
4007 the virtualbox images, but its current build system made multistrap
4008 based system for Dreamplug images, and it is lacking support for
4009 Raspberry Pi.&lt;/p&gt;
4010
4011 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
4012 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4013 code and adjusted it to be able to build armel images on my amd64
4014 Debian laptop. I ended up giving vmdebootstrap five new options,
4015 allowing me to replicate the image creation process I use to make
4016 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
4017 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
4018 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
4019 call debootstrap with --foreign and to copy the handler into the
4020 generated chroot before running the second stage. This allow
4021 vmdebootstrap to create armel images on an amd64 host. Next I added
4022 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
4023 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
4024 given file system type, allowing me to create an image with a vfat
4025 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
4026 variant&lt;/tt&gt; option to allow me to create smaller images without the
4027 Debian base system packages installed. Finally, I added an option
4028 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
4029 as a boot loader. It is not needed on the Raspberry Pi and probably
4030 most other non-x86 architectures. The changes were accepted by the
4031 upstream author of vmdebootstrap yesterday and today, and is now
4032 available from
4033 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
4034 upstream project page&lt;/a&gt;.&lt;/p&gt;
4035
4036 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
4037 create a small script (the customize script) to add the non-free
4038 binary blob needed to boot the Raspberry Pi and the APT source
4039 list:&lt;/p&gt;
4040
4041 &lt;p&gt;&lt;pre&gt;
4042 #!/bin/sh
4043 set -e # Exit on first error
4044 rootdir=&quot;$1&quot;
4045 cd &quot;$rootdir&quot;
4046 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
4047 deb http://http.debian.net/debian/ jessie main contrib non-free
4048 EOF
4049 # Install non-free binary blob needed to boot Raspberry Pi. This
4050 # install a kernel somewhere too.
4051 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4052 -O $rootdir/usr/bin/rpi-update
4053 chmod a+x $rootdir/usr/bin/rpi-update
4054 mkdir -p $rootdir/lib/modules
4055 touch $rootdir/boot/start.elf
4056 chroot $rootdir rpi-update
4057 &lt;/pre&gt;&lt;/p&gt;
4058
4059 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
4060 to build the image:&lt;/p&gt;
4061
4062 &lt;pre&gt;
4063 sudo ./vmdebootstrap \
4064 --variant minbase \
4065 --arch armel \
4066 --distribution jessie \
4067 --mirror http://http.debian.net/debian \
4068 --image test.img \
4069 --size 600M \
4070 --bootsize 64M \
4071 --boottype vfat \
4072 --log-level debug \
4073 --verbose \
4074 --no-kernel \
4075 --no-extlinux \
4076 --root-password raspberry \
4077 --hostname raspberrypi \
4078 --foreign /usr/bin/qemu-arm-static \
4079 --customize `pwd`/customize \
4080 --package netbase \
4081 --package git-core \
4082 --package binutils \
4083 --package ca-certificates \
4084 --package wget \
4085 --package kmod
4086 &lt;/pre&gt;&lt;/p&gt;
4087
4088 &lt;p&gt;The list of packages being installed are the ones needed by
4089 rpi-update to make the image bootable on the Raspberry Pi, with the
4090 exception of netbase, which is needed by debootstrap to find
4091 /etc/hosts with the minbase variant. I really wish there was a way to
4092 set up an Raspberry Pi using only packages in the Debian archive, but
4093 that is not possible as far as I know, because it boots from the GPU
4094 using a non-free binary blob.&lt;/p&gt;
4095
4096 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
4097 probably a few others installed. I have not checked the complete
4098 build dependency list.&lt;/p&gt;
4099
4100 &lt;p&gt;The resulting image will not use the hardware floating point unit
4101 on the Raspberry PI, because the armel architecture in Debian is not
4102 optimized for that use. So the images created will be a bit slower
4103 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
4104 </description>
4105 </item>
4106
4107 <item>
4108 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
4109 <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>
4110 <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>
4111 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
4112 <description>&lt;p&gt;The last few days I came across a few good causes that should get
4113 wider attention. I recommend signing and donating to each one of
4114 these. :)&lt;/p&gt;
4115
4116 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
4117 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
4118 Women program which is a Google Summer of Code like initiative to get
4119 more women involved in free software. One debian sponsor has offered
4120 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
4121 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
4122 hope you will to. :)&lt;/p&gt;
4123
4124 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
4125 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
4126 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
4127 take place these days, and their need to fund the work. I&#39;ve already
4128 donated. Are you next?&lt;/p&gt;
4129
4130 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
4131 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4132 statement under the heading
4133 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
4134 Access&lt;/a&gt; for those of us asking for more focus on open access in the
4135 Norwegian government. So far 499 signatures. I hope you will sign it
4136 too.&lt;/p&gt;
4137 </description>
4138 </item>
4139
4140 <item>
4141 <title>Videos about the Freedombox project - for inspiration and learning</title>
4142 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
4143 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
4144 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
4145 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
4146 project&lt;/a&gt; have been going on for a while, and have presented the
4147 vision, ideas and solution several places. Here is a little
4148 collection of videos of talks and presentation of the project.&lt;/p&gt;
4149
4150 &lt;ul&gt;
4151
4152 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
4153 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
4154
4155 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
4156 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4157
4158 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
4159 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4160 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
4161 (Youtube)&lt;/li&gt;
4162
4163 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
4164 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
4165
4166 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
4167 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4168
4169 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
4170 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4171 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
4172
4173 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
4174 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
4175 (Youtube)&lt;/li&gt;
4176
4177 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
4178 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
4179
4180 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
4181 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
4182
4183 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
4184 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4185 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
4186
4187 &lt;/ul&gt;
4188
4189 &lt;p&gt;A larger list is available from
4190 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
4191 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
4192
4193 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
4194 Jessie is coming along quite well, and soon both Owncloud and using
4195 Tor should be available for testers of the Freedombox solution. :) In
4196 a few weeks I hope everything needed to test it is included in Debian.
4197 The withsqlite package is already in Debian, and the plinth package is
4198 pending in NEW. The third and vital part of that puzzle is the
4199 metapackage/setup framework, which is still pending an upload. Join
4200 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
4201 (#freedombox on irc.debian.org)&lt;/a&gt; and
4202 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4203 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4204 </description>
4205 </item>
4206
4207 <item>
4208 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
4209 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
4210 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
4211 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
4212 <description>&lt;p&gt;I was introduced to the
4213 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
4214 in 2010, when Eben Moglen presented his vision about serving the need
4215 of non-technical people to keep their personal information private and
4216 within the legal protection of their own homes. The idea is to give
4217 people back the power over their network and machines, and return
4218 Internet back to its intended peer-to-peer architecture. Instead of
4219 depending on a central service, the Freedombox will give everyone
4220 control over their own basic infrastructure.&lt;/p&gt;
4221
4222 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
4223 taken priority. But this summers nasty news about the misuse of trust
4224 and privilege exercised by the &quot;western&quot; intelligence gathering
4225 communities increased my eagerness to contribute to a point where I
4226 actually started working on the project a while back.&lt;/p&gt;
4227
4228 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
4229 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
4230 create a simple and cheap Debian based appliance that anyone can hook
4231 up in their home and get access to secure and private services and
4232 communication. The initial deployment platform have been the
4233 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
4234 which is a piece of hardware I do not own. So to be able to test what
4235 the current Freedombox setup look like, I had to come up with a way to install
4236 it on some hardware I do have access to. I have rewritten the
4237 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
4238 image build framework to use .deb packages instead of only copying
4239 setup into the boot images, and thanks to this rewrite I am able to
4240 set up any machine supported by Debian Wheezy as a Freedombox, using
4241 the previously mentioned deb (and a few support debs for packages
4242 missing in Debian).&lt;/p&gt;
4243
4244 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
4245 scripts
4246 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
4247 and a administrative web interface
4248 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
4249 withsqlite), as well as a privacy enhancing proxy based on
4250 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
4251 (freedombox-privoxy). There is also a web/javascript based XMPP
4252 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
4253 trying (unsuccessfully so far) to talk to the XMPP server
4254 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
4255 web interface is pluggable, and the goal is to use it to enable OpenID
4256 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4257 this is really working yet, see
4258 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
4259 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
4260 on github at the moment. The HTTP proxy is operational out of the
4261 box, and the admin web interface can be used to add/remove plinth
4262 users. I&#39;ve not been able to do anything else with it so far, but
4263 know there are several branches spread around github and other places
4264 with lots of half baked features.&lt;/p&gt;
4265
4266 &lt;p&gt;Anyway, if you want to have a look at the current state, the
4267 following recipes should work to give you a test machine to poke
4268 at.&lt;/p&gt;
4269
4270 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
4271
4272 &lt;ol&gt;
4273
4274 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
4275 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
4276 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
4277 to the Debian installer:&lt;p&gt;
4278 &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;
4279
4280 &lt;li&gt;Answer the few language/region/password questions and pick disk to
4281 install on.&lt;/li&gt;
4282
4283 &lt;li&gt;When the installation is finished and the machine have rebooted a
4284 few times, your Freedombox is ready for testing.&lt;/li&gt;
4285
4286 &lt;/ol&gt;
4287
4288 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
4289
4290 &lt;ol&gt;
4291
4292 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
4293 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
4294 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
4295 &lt;pre&gt;
4296 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
4297 &lt;/pre&gt;&lt;/li&gt;
4298 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
4299 &lt;pre&gt;
4300 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4301 apt-key add -
4302 apt-get update
4303 apt-get install freedombox-setup
4304 /usr/lib/freedombox/setup
4305 &lt;/pre&gt;&lt;/li&gt;
4306 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
4307
4308 &lt;/ol&gt;
4309
4310 &lt;p&gt;You can test it on other architectures too, but because the
4311 freedombox-privoxy package is binary, it will only work as intended on
4312 the architectures where I have had time to build the binary and put it
4313 in my APT repository. But do not let this stop you. It is only a
4314 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
4315
4316 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
4317 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
4318 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
4319 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
4320
4321 &lt;p&gt;Please let me know if this works for you, or if you have any
4322 problems. We gather on the IRC channel
4323 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
4324 irc.debian.org and the
4325 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
4326 mailing list&lt;/a&gt;.&lt;/p&gt;
4327
4328 &lt;p&gt;Once you get your freedombox operational, you can visit
4329 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
4330 welcome screen (dead end - do not be surprised if you are unable to
4331 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
4332 to look at the rest of plinth. The default user is &#39;admin&#39; and the
4333 default password is &#39;secret&#39;.&lt;/p&gt;
4334 </description>
4335 </item>
4336
4337 <item>
4338 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
4339 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
4340 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
4341 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
4342 <description>&lt;p&gt;Earlier, I reported about
4343 &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
4344 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
4345 told by IBM that the original disk should be thrown away. And as
4346 there no longer was a problem if I bricked the firmware, I decided
4347 today to try to install Intel firmware to replace the Lenovo firmware
4348 currently on the disk.&lt;/p&gt;
4349
4350 &lt;p&gt;I searched the Intel site for firmware, and found
4351 &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;
4352 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4353 according to the site should contain the latest firmware for SSD
4354 disks. I inserted the broken disk in one of my spare laptops and
4355 booted the ISO from a USB stick. The disk was recognized, but the
4356 program claimed the newest firmware already were installed and refused
4357 to insert any Intel firmware. So no change, and the disk is still
4358 unable to handle write load. :( I guess the only way to get them
4359 working would be if Lenovo releases new firmware. No idea how likely
4360 that is. Anyway, just blogging about this test for completeness. I
4361 got a working Samsung disk, and see no point in spending more time on
4362 the broken disks.&lt;/p&gt;
4363 </description>
4364 </item>
4365
4366 <item>
4367 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
4368 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
4369 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
4370 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
4371 <description>&lt;p&gt;Today I switched to
4372 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
4373 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
4374 my new Thinkpad X230, which was delivered with an
4375 &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
4376 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
4377 sustained writes. My hardware supplier have been very forthcoming in
4378 trying to find a solution, and after first trying with another
4379 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
4380 disk instead to fix it once and for all. The Samsung disk survived
4381 the installation of Debian with encrypted disks (filling the disk with
4382 random data during installation killed the first two), and I thus
4383 decided to trust it with my data. I have installed it as a Debian Edu
4384 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4385 server at home using Kerberos and LDAP, and will use it as my work
4386 station from now on.&lt;/p&gt;
4387
4388 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
4389 Debian Wheezy default installation need to be tuned a bit to increase
4390 performance and increase life time of the disk. The Linux kernel and
4391 user space applications do not yet adjust automatically to such
4392 environment. To make it easier for my self, I created a draft Debian
4393 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
4394 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
4395 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
4396 is set up to adjust the setup of the machine by just installing the
4397 package. If there is any non-SSD disk in the machine, the package
4398 will refuse to install, as I did not try to write any logic to sort
4399 file systems in SSD and non-SSD file systems.&lt;/p&gt;
4400
4401 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
4402 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4403 where I set up the machine with one large encrypted partition (in
4404 addition to /boot), put LVM on top of this and set up partitions on
4405 top of this again. See the README file in the package source for the
4406 references I used to pick the settings. At the moment these
4407 parameters are tuned:&lt;/p&gt;
4408
4409 &lt;ul&gt;
4410
4411 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
4412 (adding discard to /etc/crypttab)&lt;/li&gt;
4413
4414 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
4415 this case a cryptsetup partition) by changing issue_discards from
4416 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
4417
4418 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
4419 systems.&lt;/li&gt;
4420
4421 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
4422 /etc/fstab.&lt;/li&gt;
4423
4424 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
4425
4426 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
4427 cron.daily).&lt;/li&gt;
4428
4429 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
4430 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
4431
4432 &lt;/ul&gt;
4433
4434 &lt;p&gt;During installation, I cancelled the part where the installer fill
4435 the disk with random data, as this would kill the SSD performance for
4436 little gain. My goal with the encrypted file system is to ensure
4437 those stealing my laptop end up with a brick and not a working
4438 computer. I have no hope in keeping the really resourceful people
4439 from getting the data on the disk (see
4440 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
4441 Thus I concluded that adding the discard option to crypttab is the
4442 right thing to do.&lt;/p&gt;
4443
4444 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
4445 it for SSD, but others recommended deadline and a benchmark I found
4446 indicated that deadline might be better for interactive use.&lt;/p&gt;
4447
4448 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
4449 and ext4, but read that it would give a performance hit ever time a
4450 file is removed, and thought it best to that that slowdown once a day
4451 instead of during my work.&lt;/p&gt;
4452
4453 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4454 this is already done by Debian Edu.&lt;/p&gt;
4455
4456 &lt;p&gt;I have not yet started on the user space tuning. I expect
4457 iceweasel need some tuning, and perhaps other applications too, but
4458 have not yet had time to investigate those parts.&lt;/p&gt;
4459
4460 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
4461 there.&lt;/p&gt;
4462
4463 &lt;p&gt;As for the answer to the question in the title of this blog post,
4464 as far as I know, the only solution I know about is to replace the
4465 disk. It might be possible to flash it with Intel firmware instead of
4466 the Lenovo firmware. But I have not tried and did not want to do so
4467 without approval from Lenovo as I wanted to keep the warranty on the
4468 disk until a solution was found and they wanted the broken disks
4469 back.&lt;/p&gt;
4470 </description>
4471 </item>
4472
4473 <item>
4474 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
4475 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
4476 <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>
4477 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
4478 <description>&lt;p&gt;A few days ago, I wrote about
4479 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
4480 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
4481 was dying during installation because it is unable to cope with
4482 sustained write. My supplier is in contact with
4483 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
4484 replacement disk to try to fix the problem. They decided to send an
4485 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
4486
4487 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
4488 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4489 same firmware version as the original. This time my hope raised
4490 slightly as the installation progressed, as the original disk used to
4491 die after 4-7% of the disk was written to, while this time it kept
4492 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
4493 died again and I was back on square one. I still do not have a new
4494 laptop with a disk I can trust. I can not live with a disk that might
4495 lock up when I download a new
4496 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
4497 other large files. I look forward to hearing from my supplier with
4498 the next proposal from Lenovo.&lt;/p&gt;
4499
4500 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
4501 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4502 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
4503 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
4504 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
4505 P/N 45N8295, P0C38732.&lt;/p&gt;
4506
4507 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
4508 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
4509 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
4510 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
4511 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
4512 P/N 45N8295, P0C38732.&lt;/p&gt;
4513
4514 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
4515 SA, date and WNPP values. Mentioning all the details here in case
4516 someone is able to use the information to find a way to identify the
4517 failing disk among working ones (if any such working disk actually
4518 exist).&lt;/p&gt;
4519 </description>
4520 </item>
4521
4522 <item>
4523 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
4524 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
4525 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
4526 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
4527 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
4528 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4529 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
4530 member assosiation NUUG&lt;/a&gt; and
4531 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
4532 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
4533 Bitraf&lt;/a&gt;.&lt;/p&gt;
4534
4535 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
4536 welcome, and there is no fee to participate. There is on the other
4537 hand limited space, and only room for 30 people. Please put your name
4538 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
4539 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
4540 </description>
4541 </item>
4542
4543 <item>
4544 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
4545 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
4546 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
4547 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
4548 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
4549 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
4550 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
4551 time to spend on it, and it took a while to find a model I believe
4552 will do the job, but two days ago the replacement finally arrived. I
4553 ended up picking a
4554 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
4555 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4556 a roaming workstation, and it seemed to work flawlessly. But my
4557 second installation with encrypted disk was not as successful. More
4558 on that below.&lt;/p&gt;
4559
4560 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4561 important requirements (robust and with a good keyboard) are never
4562 listed in the feature list. But I did get good help from the search
4563 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4564 allowed me to limit the list of interesting laptops based on my other
4565 requirements. A bit surprising that SSD disk are not disks according
4566 to that search interface, so I had to drop specifying the number of
4567 disks from my search parameters. I also asked around among friends to
4568 get their impression on keyboards and robustness.&lt;/p&gt;
4569
4570 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
4571 X41. I am not quite convinced about the keyboard, as it is
4572 significantly wider than my old keyboard, and I have to stretch my
4573 hand a lot more to reach the edges. But the key response is fairly
4574 good and the individual key shape is fairly easy to handle, so I hope
4575 I will get used to it. My old X40 was starting to fail, and I really
4576 needed a new laptop now. :)&lt;/p&gt;
4577
4578 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
4579 visit to the BIOS during boot it disable it.&lt;/p&gt;
4580
4581 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
4582 lock up during load. And this happen when installing Debian Wheezy
4583 with encrypted disk, while the disk is being filled with random data.
4584 I also tested to install Ubuntu Raring, and it happen there too if I
4585 reenable the code to fill the disk with random data (it is disabled by
4586 default in Ubuntu). And the bug with is already known. It was
4587 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
4588 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
4589 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4590 kernel developers as
4591 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
4592 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
4593 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4594 Lenovo forums, both for
4595 &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
4596 2012-11-10&lt;/a&gt; and for
4597 &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
4598 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
4599 reports state that the disk lock up during use if many writes are done
4600 on the disk, so it is much no use to work around the installation
4601 problem and end up with a computer that can lock up at any moment.
4602 There is even a
4603 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
4604 available&lt;/a&gt; that will lock up the hard drive after running a few
4605 minutes by writing to a file.&lt;/p&gt;
4606
4607 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
4608 contacting PCHELP Norway (request 01D1FDP) which handle support
4609 requests for Lenovo, his first suggestion was to upgrade the disk
4610 firmware. Unfortunately there is no newer firmware available from
4611 Lenovo, as my disk already have the most recent one (version LF1i). I
4612 hope to hear more from him today and hope the problem can be
4613 fixed. :)&lt;/p&gt;
4614 </description>
4615 </item>
4616
4617 <item>
4618 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
4619 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
4620 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
4621 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
4622 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
4623 trusty old Thinkpad X41. Unfortunately I did not have much time to
4624 spend on it, but today the replacement finally arrived. I ended up
4625 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
4626 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
4627 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4628 this, it is installing what I hope will be a more final installation,
4629 with a encrypted hard drive to ensure any dope head stealing it end up
4630 with an expencive door stop.&lt;/p&gt;
4631
4632 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4633 important requirements (robust and with a good keyboard) are never
4634 listed in the feature list. But I did get good help from the search
4635 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4636 allowed me to limit the list of interesting laptops based on my other
4637 requirements. A bit surprising that SSD disk are not disks, so I had
4638 to drop number of disks from my search parameters.&lt;/p&gt;
4639
4640 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
4641 wider than my old keyboard, and I have to stretch my hand a lot more
4642 to reach the edges. But the key response is fairly good and the
4643 individual key shape is fairly easy to handle, so I hope I will get
4644 used to it. My old X40 was starting to fail, and I really needed a
4645 new laptop now. :)&lt;/p&gt;
4646
4647 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
4648 </description>
4649 </item>
4650
4651 <item>
4652 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
4653 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
4654 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
4655 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
4656 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
4657 perfectly capable of, and I have to do it manually to get things
4658 working. One such task is to find out what firmware packages are
4659 needed to get the hardware on my computer working. Most often this
4660 affect the wifi card, but some times it even affect the RAID
4661 controller or the ethernet card. Today I pushed version 0.4 of the
4662 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
4663 including a new script isenkram-autoinstall-firmware handling the
4664 process of asking all the loaded kernel modules what firmware files
4665 they want, find debian packages providing these files and install the
4666 debian packages. Here is a test run on my laptop:&lt;/p&gt;
4667
4668 &lt;p&gt;&lt;pre&gt;
4669 # isenkram-autoinstall-firmware
4670 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4671 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4672 info: locating packages with the requested firmware files
4673 info: Updating APT sources after adding non-free APT source
4674 info: trying to install firmware-ipw2x00
4675 firmware-ipw2x00
4676 firmware-ipw2x00
4677 Preconfiguring packages ...
4678 Selecting previously deselected package firmware-ipw2x00.
4679 (Reading database ... 259727 files and directories currently installed.)
4680 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4681 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
4682 #
4683 &lt;/pre&gt;&lt;/p&gt;
4684
4685 &lt;p&gt;When all the requested firmware is present, a simple message is
4686 printed instead:&lt;/p&gt;
4687
4688 &lt;p&gt;&lt;pre&gt;
4689 # isenkram-autoinstall-firmware
4690 info: did not find any firmware files requested by loaded kernel modules. exiting
4691 #
4692 &lt;/pre&gt;&lt;/p&gt;
4693
4694 &lt;p&gt;It could use some polish, but it is already working well and saving
4695 me some time when setting up new machines. :)&lt;/p&gt;
4696
4697 &lt;p&gt;So, how does it work? It look at the set of currently loaded
4698 kernel modules, and look up each one of them using modinfo, to find
4699 the firmware files listed in the module meta-information. Next, it
4700 download the Contents file from a nearby APT mirror, and search for
4701 the firmware files in this file to locate the package with the
4702 requested firmware file. If the package is in the non-free section, a
4703 non-free APT source is added and the package is installed using
4704 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
4705 machine.&lt;/p&gt;
4706
4707 &lt;p&gt;I hope someone find time to implement a more polished version of
4708 this script as part of the hw-detect debian-installer module, to
4709 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
4710 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
4711 firmware during a PXE install when the packages already are available
4712 from the nearby Debian mirror.&lt;/p&gt;
4713 </description>
4714 </item>
4715
4716 <item>
4717 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
4718 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
4719 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
4720 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
4721 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4722 the screen just turn black when Linux boot, either during installation
4723 or on first boot from the hard disk. I&#39;ve seen it once in a while the
4724 last few years, but only recently understood the cause. I&#39;ve seen it
4725 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4726 The reason seem to be in the wiring of some laptops. The system to
4727 control the screen background light is inverted, so when Linux try to
4728 turn the brightness fully on, it end up turning it off instead. I do
4729 not know which Linux drivers are affected, but this post is about the
4730 i915 driver used by the
4731 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
4732 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
4733
4734 &lt;p&gt;The problem can be worked around two ways. Either by adding
4735 i915.invert_brightness=1 as a kernel option, or by adding a file in
4736 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
4737 option when it load the i915 kernel module. On Debian and Ubuntu, it
4738 can be done by running these commands as root:&lt;/p&gt;
4739
4740 &lt;pre&gt;
4741 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
4742 update-initramfs -u -k all
4743 &lt;/pre&gt;
4744
4745 &lt;p&gt;Since March 2012 there is
4746 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
4747 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
4748 hardware have this problem, and get the driver to invert the
4749 brightness setting automatically. To use it, one need to add a row in
4750 &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
4751 intel_quirks array&lt;/a&gt; in the driver source
4752 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
4753 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
4754 number (vendor number 8086 is assumed) and subdevice vendor and device
4755 number.&lt;/p&gt;
4756
4757 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
4758 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
4759
4760 &lt;p&gt;&lt;pre&gt;
4761 00:02.0 VGA compatible controller [0300]: Intel Corporation \
4762 3rd Gen Core processor Graphics Controller [8086:0156] \
4763 (rev 09) (prog-if 00 [VGA controller])
4764 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
4765 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4766 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4767 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
4768 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
4769 Latency: 0
4770 Interrupt: pin A routed to IRQ 42
4771 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
4772 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
4773 Region 4: I/O ports at 4000 [size=64]
4774 Expansion ROM at &lt;unassigned&gt; [disabled]
4775 Capabilities: &lt;access denied&gt;
4776 Kernel driver in use: i915
4777 &lt;/pre&gt;&lt;/p&gt;
4778
4779 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
4780
4781 &lt;p&gt;&lt;pre&gt;
4782 struct intel_quirk intel_quirks[] = {
4783 ...
4784 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4785 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
4786 ...
4787 }
4788 &lt;/pre&gt;&lt;/p&gt;
4789
4790 &lt;p&gt;According to the kernel module instructions (as seen using
4791 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
4792 invert_brightness flag should be sent to the
4793 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
4794 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
4795 developers. But my email about the laptop sent 2013-06-03 have not
4796 yet shown up in
4797 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
4798 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
4799 emails from non-subscribers. Because of this, I sent my patch also to
4800 the Debian bug tracking system instead as
4801 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
4802 sure the patch is not lost.&lt;/p&gt;
4803
4804 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
4805 with this problem working properly with Linux. If you use Gnome, your
4806 worries should be over at this point. But if you use KDE, there is
4807 something in KDE ignoring the invert_brightness setting and turning on
4808 the screen during login. I&#39;ve reported it to Debian as
4809 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
4810 have no idea yet how to figure out exactly what subsystem is doing
4811 this. Perhaps you can help? Perhaps you know what the Gnome
4812 developers did to handle this, and this can give a clue to the KDE
4813 developers? Or you know where in KDE the screen brightness is changed
4814 during login? If so, please update the BTS report (or get in touch if
4815 you do not know how to update BTS).&lt;/p&gt;
4816
4817 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
4818 acpi_backlight=vendor, to disable ACPI backlight support completely,
4819 as the ACPI information on the machine is trash and it is better to
4820 leave it to the intel video driver to control the screen
4821 backlight.&lt;/p&gt;
4822 </description>
4823 </item>
4824
4825 <item>
4826 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
4827 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
4828 <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>
4829 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
4830 <description>&lt;p&gt;Two days ago, I asked
4831 &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
4832 I could install Linux on a Packard Bell EasyNote LV computer
4833 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
4834 with the obstacles put in the way of Linux users on a laptop with UEFI
4835 and Windows 8.&lt;/p&gt;
4836
4837 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
4838 secure booting or fast boot. I suspect fast boot was the problem,
4839 causing the firmware to boot directly from HD without considering any
4840 key presses and alternative devices, but do not know UEFI settings
4841 enough to tell.&lt;/p&gt;
4842
4843 &lt;p&gt;There is no way to install Linux on the machine in question without
4844 opening the box and disconnecting the hard drive! This is as far as I
4845 can tell, the only way to get access to the firmware setup menu
4846 without accepting the Windows 8 license agreement. I am told (and
4847 found description on how to) that it is possible to configure the
4848 firmware setup once booted into Windows 8. But as I believe the terms
4849 of that agreement are completely unacceptable, accepting the license
4850 was never an alternative. I do not enter agreements I do not intend
4851 to follow.&lt;/p&gt;
4852
4853 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
4854 waste many hours on this, but luckily there was a way to get it to
4855 work. But I would not recommend it to anyone planning to run Linux on
4856 it, and I have become sceptical to Windows 8 certified laptops. Is
4857 this the way Linux will be forced out of the market place, by making
4858 it close to impossible for &quot;normal&quot; users to install Linux without
4859 accepting the Microsoft Windows license terms? Or at least not
4860 without risking to loose the warranty?&lt;/p&gt;
4861
4862 &lt;p&gt;I&#39;ve updated the
4863 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
4864 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
4865 do not have to struggle as much as I did to get Linux into the
4866 machine.&lt;/p&gt;
4867
4868 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4869 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
4870 </description>
4871 </item>
4872
4873 <item>
4874 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
4875 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
4876 <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>
4877 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
4878 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
4879 new laptops for my parents and a few others. I bought Packard Bell
4880 Easynote LV to run Kubuntu on and use as their home computer. But I
4881 am completely unable to figure out how to install Linux on it. The
4882 computer is preinstalled with Windows 8, and I suspect it uses UEFI
4883 instead of a BIOS to boot.&lt;/p&gt;
4884
4885 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
4886 to get it to boot the Linux installer from my USB stick. I have yet
4887 to try the DVD install, and still hope it will work. when I turn on
4888 the computer, there is no information on what buttons to press to get
4889 the normal boot menu. I expect to get some boot menu to select PXE or
4890 USB stick booting. When booting, it first ask for the language to
4891 use, then for some regional settings, and finally if I will accept the
4892 Windows 8 terms of use. As these terms are completely unacceptable to
4893 me, I have no other choice but to turn off the computer and try again
4894 to get it to boot the Linux installer.&lt;/p&gt;
4895
4896 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
4897 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
4898 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
4899 installed on this machine, please get in touch or update that wiki
4900 page. If I can&#39;t find a way to install Linux, I will have to return
4901 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
4902
4903 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
4904 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
4905 on new Laptops?&lt;/p&gt;
4906 </description>
4907 </item>
4908
4909 <item>
4910 <title>How to transform a Debian based system to a Debian Edu installation</title>
4911 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
4912 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
4913 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
4914 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
4915 an operating system based on Debian intended for use in schools. It
4916 contain a turn-key solution for the computer network provided to
4917 pupils in the primary schools. It provide both the central server,
4918 network boot servers and desktop environments with heaps of
4919 educational software. The project was founded almost 12 years ago,
4920 2001-07-02. If you want to support the project, which is in need for
4921 cash to fund developer gatherings and other project related activity,
4922 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
4923 donate some money&lt;/a&gt;.
4924
4925 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
4926 lists and elsewhere, is the question on how to transform a Debian or
4927 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
4928 hard, and last week I wrote a script to replicate the steps done by
4929 the Debian Edu installer.&lt;/p&gt;
4930
4931 &lt;p&gt;The script,
4932 &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;
4933 in the debian-edu-config package, will go through these six steps and
4934 transform an existing Debian Wheezy or Ubuntu (untested) installation
4935 into a Debian Edu Workstation:&lt;/p&gt;
4936
4937 &lt;ol&gt;
4938
4939 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
4940 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
4941 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
4942 our configuration.&lt;/li&gt;
4943 &lt;li&gt;Preseed debconf database with profile setup in
4944 /etc/debian-edu/config, and run tasksel to install packages
4945 according to the profile specified in the config above,
4946 overriding some of the Debian automation machinery.&lt;/li&gt;
4947 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
4948 that could not be done using preseeding.&lt;/li&gt;
4949 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
4950
4951 &lt;/ol&gt;
4952
4953 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
4954 replicated like this. Disk partitioning and LVM setup, for example.
4955 So this script just assume there is enough disk space to install all
4956 the needed packages.&lt;/p&gt;
4957
4958 &lt;p&gt;The script was created to help a Debian Edu student working on
4959 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
4960 Debian Edu client, and using it he can take the existing
4961 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
4962 transform it into a fully functioning Debian Edu Workstation (or
4963 Roaming Workstation, or whatever :).&lt;/p&gt;
4964
4965 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
4966 If a LXDE based Roaming workstation is wanted instead, modify the
4967 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
4968
4969 &lt;p&gt;&lt;pre&gt;
4970 PROFILE=&quot;Roaming-Workstation&quot;
4971 DESKTOP=&quot;lxde&quot;
4972 &lt;/pre&gt;&lt;/p&gt;
4973
4974 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
4975 the cloud, by starting with a virtual Debian installation at some
4976 virtual hosting service and setting up all the services on first
4977 boot.&lt;/p&gt;
4978 </description>
4979 </item>
4980
4981 <item>
4982 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
4983 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
4984 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
4985 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
4986 <description>&lt;P&gt;In January,
4987 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
4988 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
4989 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
4990 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
4991 marvellous construction system from Denmark. We also created
4992 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
4993 a place to take notes and write down our plans and hopes. And several
4994 people showed up to help. I was very happy to see the effect of my
4995 call. Since the small start, we have a debtags tag
4996 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
4997 tag for LEGO related packages, and now count 10 packages related to
4998 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
4999
5000 &lt;p&gt;&lt;table&gt;
5001 &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;
5002 &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;
5003 &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;
5004 &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;
5005 &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;
5006 &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;
5007 &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;
5008 &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;
5009 &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;
5010 &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;
5011 &lt;/table&gt;&lt;/p&gt;
5012
5013 &lt;p&gt;Some of these are available in Wheezy, and all but one are
5014 currently available in Jessie/testing. leocad is so far only
5015 available in experimental.&lt;/p&gt;
5016
5017 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
5018 adding the rest of the great free software tools available on Linux
5019 for LEGO designers.&lt;/p&gt;
5020 </description>
5021 </item>
5022
5023 <item>
5024 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
5025 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
5026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
5027 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
5028 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
5029 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
5030 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
5031 Debian release, and I expect to move my machines at home over to it fairly
5032 soon.&lt;/p&gt;
5033
5034 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
5035 in particular make me very happy to see included. The
5036 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
5037 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
5038 included for the first time. Alongside similar programs like
5039 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
5040 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
5041 it allow for visual programming where syntax errors can not happen,
5042 and a friendly programming environment for learning to control the
5043 computer. Scratch will also be included in the next release of Debian
5044 Edu.&lt;/a&gt;
5045
5046 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
5047 Edu/Skolelinux release too. The
5048 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
5049 alpha release&lt;/a&gt; went out last week, and the next should soon
5050 follow.&lt;p&gt;
5051 </description>
5052 </item>
5053
5054 <item>
5055 <title>Isenkram 0.2 finally in the Debian archive</title>
5056 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
5057 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
5058 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
5059 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
5060 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
5061 for many months. I uploaded it to the Debian experimental suite
5062 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
5063
5064 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
5065 install to work with a pluggable hardware device. The suggestion pop
5066 up when the device is plugged in. For example if a Lego Mindstorm NXT
5067 is inserted, it will suggest to install the program needed to program
5068 the NXT controller. Give it a go, and report bugs and suggestions to
5069 BTS. :)&lt;/p&gt;
5070 </description>
5071 </item>
5072
5073 <item>
5074 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
5075 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
5076 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
5077 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
5078 <description>&lt;p&gt;My
5079 &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
5080 bitcoin related blog post&lt;/a&gt; mentioned that the new
5081 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
5082 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5083 2013-01-19, and have been available in unstable since then. It was
5084 automatically copied to Ubuntu, and is available in their Raring
5085 version too.&lt;/p&gt;
5086
5087 &lt;p&gt;But there is a strange problem with the build that block this new
5088 version from being available on the i386 and kfreebsd-i386
5089 architectures. For some strange reason, the autobuilders in Debian
5090 for these architectures fail to run the test suite on these
5091 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
5092 We are so far unable to reproduce it when building it manually, and
5093 no-one have been able to propose a fix. If you got an idea what is
5094 failing, please let us know via the BTS.&lt;/p&gt;
5095
5096 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
5097 I often run low on disk space, is the fact that the client will exit
5098 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
5099 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
5100 it. :)&lt;/p&gt;
5101
5102 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5103 activities, please send Bitcoin donations to my address
5104 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5105 </description>
5106 </item>
5107
5108 <item>
5109 <title>Welcome to the world, Isenkram!</title>
5110 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
5111 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
5112 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
5113 <description>&lt;p&gt;Yesterday, I
5114 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
5115 for testers&lt;/a&gt; for my prototype for making Debian better at handling
5116 pluggable hardware devices, which I
5117 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
5118 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
5119 up, and caused me to really want to to open up the development to more
5120 people. But before I did this, I want to come up with a sensible name
5121 for this project. Today I finally decided on a new name, and I have
5122 renamed the project from hw-support-handler to this new name. In the
5123 process, I moved the source to git and made it available as a
5124 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
5125 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
5126 To fetch and build the latest version of the source, use&lt;/p&gt;
5127
5128 &lt;pre&gt;
5129 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5130 cd isenkram &amp;&amp; git-buildpackage -us -uc
5131 &lt;/pre&gt;
5132
5133 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
5134 want to hack on the source or improve the package, please go ahead.
5135 But please talk to me first on IRC or via email before you do major
5136 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
5137
5138 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
5139 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5140 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
5141 the German word eisenkram, for those that are familiar with that
5142 word.&lt;/p&gt;
5143
5144 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
5145 instructions, to avoid confusing people with an error from the signing
5146 process.&lt;/p&gt;
5147
5148 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
5149 clone argument to avoid the need for authentication.&lt;/p&gt;
5150 </description>
5151 </item>
5152
5153 <item>
5154 <title>First prototype ready making hardware easier to use in Debian</title>
5155 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
5156 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
5157 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
5158 <description>&lt;p&gt;Early this month I set out to try to
5159 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
5160 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
5161 prototype is working, and it is ready for a larger audience. To test
5162 it, fetch the
5163 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
5164 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
5165 package. You might have to log out and in again activate the
5166 autostart script.&lt;/p&gt;
5167
5168 &lt;p&gt;The design is simple:&lt;/p&gt;
5169
5170 &lt;ul&gt;
5171
5172 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
5173 hw-support-handlerd to start when the user log in.&lt;/li&gt;
5174
5175 &lt;li&gt;This program listen for kernel events about new hardware (directly
5176 from the kernel like udev does), not using HAL dbus events as I
5177 initially did.&lt;/li&gt;
5178
5179 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
5180 the APT database, a database
5181 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
5182 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
5183
5184 &lt;li&gt;If a package is mapped to the hardware in question, the package
5185 isn&#39;t installed yet and this is the first time the hardware was
5186 plugged in, show a desktop notification suggesting to install the
5187 package or packages.&lt;/li&gt;
5188
5189 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
5190 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
5191
5192 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
5193 package while showing progress information in a window.&lt;/li&gt;
5194
5195 &lt;/ul&gt;
5196
5197 &lt;p&gt;I still need to come up with a better name for the system. Here
5198 are some screen shots showing the prototype in action. First the
5199 notification, then the password request, and finally the request to
5200 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
5201
5202 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
5203 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
5204 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
5205 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
5206 &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;
5207
5208 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
5209 is already useful. The database of hardware to package mappings also
5210 need more work. It is currently compatible with the Ubuntu way of
5211 storing such information in the package control file, but could be
5212 changed to use other formats instead or in addition to the current
5213 method. I&#39;ve dropped the use of discover for this mapping, as the
5214 modalias approach is more flexible and easier to use on Linux as long
5215 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
5216
5217 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
5218 here is the command required to check out and build the source: Use
5219 &#39;&lt;tt&gt;svn checkout
5220 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5221 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
5222 devscripts package.&lt;/p&gt;
5223
5224 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
5225 renamed to Isenkram and the source moved from the Debian Edu
5226 subversion repository to a Debian collab-maint git repository. See
5227 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
5228 instructions&lt;/a&gt; for details.&lt;/p&gt;
5229 </description>
5230 </item>
5231
5232 <item>
5233 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
5234 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
5235 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
5236 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
5237 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
5238 suddenly in bed. With a quiet whimper, it went completely quiet and
5239 black. The power button was no longer able to turn it on. It was a
5240 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5241 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5242 Compaq I had before that. Now I need to find a replacement. To keep
5243 going during Christmas, I moved the one year old SSD disk to my old
5244 X40 where it fitted (only one I had left that could use it), but it is
5245 not a durable solution.
5246
5247 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
5248 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
5249
5250 &lt;ul&gt;
5251
5252 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
5253 than A4).&lt;/li&gt;
5254 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
5255 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
5256 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
5257 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
5258 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
5259 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
5260 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
5261 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
5262 size).&lt;/li&gt;
5263 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
5264 X.org packages.&lt;/li&gt;
5265 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
5266 the time).
5267
5268 &lt;/ul&gt;
5269
5270 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
5271 list. The reason is simply that the specifications on laptops the
5272 last 10-15 years have been sufficient for my needs, and I have to look
5273 at other features to choose my laptop. But are there still made as
5274 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5275 robust, and Thinkpads seem to be heading in the wrong direction since
5276 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
5277 still be useful.&lt;/p&gt;
5278
5279 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
5280 external keyboard? I&#39;ll have to check the
5281 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
5282 well-supported laptops, or perhaps just buy one preinstalled from one
5283 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
5284 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
5285 </description>
5286 </item>
5287
5288 <item>
5289 <title>How to find a browser plugin supporting a given MIME type</title>
5290 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
5291 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
5292 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
5293 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
5294 install to get support for a given MIME type. Thanks to
5295 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
5296 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
5297 Unfortunately, not very many packages provide the needed meta
5298 information, Anyway, here is a small script to look up all browser
5299 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
5300
5301 &lt;pre&gt;
5302 #!/usr/bin/python
5303 import sys
5304 import apt
5305 def pkgs_handling_mimetype(mimetype):
5306 cache = apt.Cache()
5307 cache.open(None)
5308 thepkgs = []
5309 for pkg in cache:
5310 version = pkg.candidate
5311 if version is None:
5312 version = pkg.installed
5313 if version is None:
5314 continue
5315 record = version.record
5316 if not record.has_key(&#39;Npp-MimeType&#39;):
5317 continue
5318 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
5319 for t in mime_types:
5320 t = t.rstrip().strip()
5321 if t == mimetype:
5322 thepkgs.append(pkg.name)
5323 return thepkgs
5324 mimetype = &quot;audio/ogg&quot;
5325 if 1 &lt; len(sys.argv):
5326 mimetype = sys.argv[1]
5327 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
5328 for pkg in pkgs_handling_mimetype(mimetype):
5329 print &quot; %s&quot; %pkg
5330 &lt;/pre&gt;
5331
5332 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
5333
5334 &lt;pre&gt;
5335 % ./apt-find-browserplug-for-mimetype
5336 Browser plugin packages supporting audio/ogg:
5337 gecko-mediaplayer
5338 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5339 Browser plugin packages supporting application/x-shockwave-flash:
5340 browser-plugin-gnash
5341 %
5342 &lt;/pre&gt;
5343
5344 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
5345 itself to query for plugins and propose to install the needed
5346 packages. It would be great if Debian supported such feature too. Is
5347 anyone working on adding it?&lt;/p&gt;
5348
5349 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
5350 request for icweasel support for this feature is
5351 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
5352 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
5353 of manpower and wish for a different design is the reason thus feature
5354 is not yet in iceweasel from Debian.&lt;/p&gt;
5355 </description>
5356 </item>
5357
5358 <item>
5359 <title>What is the most supported MIME type in Debian?</title>
5360 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
5361 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
5362 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
5363 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
5364 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
5365 proposal to make it possible for a Desktop application to propose to
5366 the user some package to install to gain support for a given MIME
5367 type, font, library etc. that is currently missing. With such
5368 mechanism in place, it would be possible for the desktop to
5369 automatically propose and install leocad if some LDraw file is
5370 downloaded by the browser.&lt;/p&gt;
5371
5372 &lt;p&gt;To get some idea about the current content of the archive, I decided
5373 to write a simple program to extract all .desktop files from the
5374 Debian archive and look up the claimed MIME support there. The result
5375 can be found on the
5376 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
5377 site&lt;/a&gt;. Using the collected information, it become possible to
5378 answer the question in the title. Here are the 20 most supported MIME
5379 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5380 The complete list is available from the link above.&lt;/p&gt;
5381
5382 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
5383
5384 &lt;pre&gt;
5385 count MIME type
5386 ----- -----------------------
5387 32 text/plain
5388 30 audio/mpeg
5389 29 image/png
5390 28 image/jpeg
5391 27 application/ogg
5392 26 audio/x-mp3
5393 25 image/tiff
5394 25 image/gif
5395 22 image/bmp
5396 22 audio/x-wav
5397 20 audio/x-flac
5398 19 audio/x-mpegurl
5399 18 video/x-ms-asf
5400 18 audio/x-musepack
5401 18 audio/x-mpeg
5402 18 application/x-ogg
5403 17 video/mpeg
5404 17 audio/x-scpls
5405 17 audio/ogg
5406 16 video/x-ms-wmv
5407 &lt;/pre&gt;
5408
5409 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
5410
5411 &lt;pre&gt;
5412 count MIME type
5413 ----- -----------------------
5414 33 text/plain
5415 32 image/png
5416 32 image/jpeg
5417 29 audio/mpeg
5418 27 image/gif
5419 26 image/tiff
5420 26 application/ogg
5421 25 audio/x-mp3
5422 22 image/bmp
5423 21 audio/x-wav
5424 19 audio/x-mpegurl
5425 19 audio/x-mpeg
5426 18 video/mpeg
5427 18 audio/x-scpls
5428 18 audio/x-flac
5429 18 application/x-ogg
5430 17 video/x-ms-asf
5431 17 text/html
5432 17 audio/x-musepack
5433 16 image/x-xbitmap
5434 &lt;/pre&gt;
5435
5436 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
5437
5438 &lt;pre&gt;
5439 count MIME type
5440 ----- -----------------------
5441 31 text/plain
5442 31 image/png
5443 31 image/jpeg
5444 29 audio/mpeg
5445 28 application/ogg
5446 27 image/gif
5447 26 image/tiff
5448 26 audio/x-mp3
5449 23 audio/x-wav
5450 22 image/bmp
5451 21 audio/x-flac
5452 20 audio/x-mpegurl
5453 19 audio/x-mpeg
5454 18 video/x-ms-asf
5455 18 video/mpeg
5456 18 audio/x-scpls
5457 18 application/x-ogg
5458 17 audio/x-musepack
5459 16 video/x-ms-wmv
5460 16 video/x-msvideo
5461 &lt;/pre&gt;
5462
5463 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
5464 information mentioned in DEP-11. I have not yet had time to look at
5465 it, but hope the PackageKit people in Debian are on top of these
5466 issues.&lt;/p&gt;
5467
5468 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
5469 discovering a typo in my script.&lt;/p&gt;
5470 </description>
5471 </item>
5472
5473 <item>
5474 <title>Using modalias info to find packages handling my hardware</title>
5475 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
5476 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
5477 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
5478 <description>&lt;p&gt;Yesterday, I wrote about the
5479 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
5480 values provided by the Linux kernel&lt;/a&gt; following my hope for
5481 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
5482 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
5483 modalias values attached to package names can be used to map packages
5484 to hardware. This allow the system to look up and suggest relevant
5485 packages when I plug in some new hardware into my machine, and replace
5486 discover and discover-data as the database used to map hardware to
5487 packages.&lt;/p&gt;
5488
5489 &lt;p&gt;I create a modaliases file with entries like the following,
5490 containing package name, kernel module name (if relevant, otherwise
5491 the package name) and globs matching the relevant hardware
5492 modalias.&lt;/p&gt;
5493
5494 &lt;p&gt;&lt;blockquote&gt;
5495 Package: package-name
5496 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
5497 &lt;/blockquote&gt;&lt;/p&gt;
5498
5499 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
5500 for a given modalias value using this file.&lt;/p&gt;
5501
5502 &lt;p&gt;An entry like this would suggest the video and picture application
5503 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
5504
5505 &lt;p&gt;&lt;blockquote&gt;
5506 Package: cheese
5507 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
5508 &lt;/blockquote&gt;&lt;/p&gt;
5509
5510 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
5511 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
5512
5513 &lt;p&gt;&lt;blockquote&gt;
5514 Package: pcmciautils
5515 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5516 &lt;/blockquote&gt;&lt;/p&gt;
5517
5518 &lt;p&gt;An entry like this would suggest the package colorhug-client when
5519 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
5520
5521 &lt;p&gt;&lt;blockquote&gt;
5522 Package: colorhug-client
5523 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
5524 &lt;/blockquote&gt;&lt;/p&gt;
5525
5526 &lt;p&gt;I believe the format is compatible with the format of the Packages
5527 file in the Debian archive. Ubuntu already uses their Packages file
5528 to store their mappings from packages to hardware.&lt;/p&gt;
5529
5530 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
5531 announce the hardware it support in a way my prototype understand.
5532 This allow those publishing packages in an APT source outside the
5533 Debian archive as well as those backporting packages to make sure the
5534 hardware mapping are included in the package meta information. I&#39;ve
5535 tested such header in the pymissile package, and its modalias mapping
5536 is working as it should with my prototype. It even made it to Ubuntu
5537 Raring.&lt;/p&gt;
5538
5539 &lt;p&gt;To test if it was possible to look up supported hardware using only
5540 the shell tools available in the Debian installer, I wrote a shell
5541 implementation of the lookup code. The idea is to create files for
5542 each modalias and let the shell do the matching. Please check out and
5543 try the
5544 &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;
5545 shell script. It run without any extra dependencies and fetch the
5546 hardware mappings from the Debian archive and the subversion
5547 repository where I currently work on my prototype.&lt;/p&gt;
5548
5549 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
5550 install yubikey-personalization:&lt;/p&gt;
5551
5552 &lt;p&gt;&lt;blockquote&gt;
5553 % ./hw-support-lookup
5554 &lt;br&gt;yubikey-personalization
5555 &lt;br&gt;%
5556 &lt;/blockquote&gt;&lt;/p&gt;
5557
5558 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5559 propose to install the pcmciautils package:&lt;/p&gt;
5560
5561 &lt;p&gt;&lt;blockquote&gt;
5562 % ./hw-support-lookup
5563 &lt;br&gt;pcmciautils
5564 &lt;br&gt;%
5565 &lt;/blockquote&gt;&lt;/p&gt;
5566
5567 &lt;p&gt;If you know of any hardware-package mapping that should be added to
5568 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
5569 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
5570
5571 &lt;p&gt;It could be possible to generate several of the mappings between
5572 packages and hardware. One source would be to look at packages with
5573 kernel modules, ie packages with *.ko files in /lib/modules/, and
5574 extract their modalias information. Another would be to look at
5575 packages with udev rules, ie packages with files in
5576 /lib/udev/rules.d/, and extract their vendor/model information to
5577 generate a modalias matching rule. I have not tested any of these to
5578 see if it work.&lt;/p&gt;
5579
5580 &lt;p&gt;If you want to help implementing a system to let us propose what
5581 packages to install when new hardware is plugged into a Debian
5582 machine, please send me an email or talk to me on
5583 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
5584 </description>
5585 </item>
5586
5587 <item>
5588 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
5589 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
5590 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
5591 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
5592 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
5593 information, to find the packages that support a given piece of
5594 hardware, I refreshed my memory regarding modalias values, and decided
5595 to document the details. Here are my findings so far, also available
5596 in
5597 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
5598 Debian Edu subversion repository&lt;/a&gt;:
5599
5600 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
5601
5602 &lt;p&gt;This document try to explain what the different types of modalias
5603 values stands for. It is in part based on information from
5604 &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;,
5605 &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;,
5606 &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
5607 &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;.
5608
5609 &lt;p&gt;The modalias entries for a given Linux machine can be found using
5610 this shell script:&lt;/p&gt;
5611
5612 &lt;pre&gt;
5613 find /sys -name modalias -print0 | xargs -0 cat | sort -u
5614 &lt;/pre&gt;
5615
5616 &lt;p&gt;The supported modalias globs for a given kernel module can be found
5617 using modinfo:&lt;/p&gt;
5618
5619 &lt;pre&gt;
5620 % /sbin/modinfo psmouse | grep alias:
5621 alias: serio:ty05pr*id*ex*
5622 alias: serio:ty01pr*id*ex*
5623 %
5624 &lt;/pre&gt;
5625
5626 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
5627
5628 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
5629 Bridge memory controller:&lt;/p&gt;
5630
5631 &lt;p&gt;&lt;blockquote&gt;
5632 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5633 &lt;/blockquote&gt;&lt;/p&gt;
5634
5635 &lt;p&gt;This represent these values:&lt;/p&gt;
5636
5637 &lt;pre&gt;
5638 v 00008086 (vendor)
5639 d 00002770 (device)
5640 sv 00001028 (subvendor)
5641 sd 000001AD (subdevice)
5642 bc 06 (bus class)
5643 sc 00 (bus subclass)
5644 i 00 (interface)
5645 &lt;/pre&gt;
5646
5647 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
5648 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
5649 0600. The 0600 class is a host bridge. Other useful bus values are
5650 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
5651
5652 &lt;p&gt;Not sure how to figure out the interface value, nor what it
5653 means.&lt;/p&gt;
5654
5655 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
5656
5657 &lt;p&gt;Some typical USB entries can look like this. This is an internal
5658 USB hub in a laptop:&lt;/p&gt;
5659
5660 &lt;p&gt;&lt;blockquote&gt;
5661 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5662 &lt;/blockquote&gt;&lt;/p&gt;
5663
5664 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
5665
5666 &lt;pre&gt;
5667 v 1D6B (device vendor)
5668 p 0001 (device product)
5669 d 0206 (bcddevice)
5670 dc 09 (device class)
5671 dsc 00 (device subclass)
5672 dp 00 (device protocol)
5673 ic 09 (interface class)
5674 isc 00 (interface subclass)
5675 ip 00 (interface protocol)
5676 &lt;/pre&gt;
5677
5678 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
5679 class is in the interface class section. For a simple USB web camera,
5680 these alias entries show up:&lt;/p&gt;
5681
5682 &lt;p&gt;&lt;blockquote&gt;
5683 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5684 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5685 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5686 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5687 &lt;/blockquote&gt;&lt;/p&gt;
5688
5689 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
5690 camera), 0101 is audio control device and 0102 is audio streaming (aka
5691 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
5692
5693 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
5694
5695 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
5696 receiver in a Thinkpad X40:&lt;/p&gt;
5697
5698 &lt;p&gt;&lt;blockquote&gt;
5699 acpi:IBM0071:PNP0511:
5700 &lt;/blockquote&gt;&lt;/p&gt;
5701
5702 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
5703
5704 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
5705
5706 &lt;p&gt;The DMI table contain lots of information about the computer case
5707 and model. This is an entry for a IBM Thinkpad X40, fetched from
5708 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
5709
5710 &lt;p&gt;&lt;blockquote&gt;
5711 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5712 &lt;/blockquote&gt;&lt;/p&gt;
5713
5714 &lt;p&gt;The values present are&lt;/p&gt;
5715
5716 &lt;pre&gt;
5717 bvn IBM (BIOS vendor)
5718 bvr 1UETB6WW(1.66) (BIOS version)
5719 bd 06/15/2005 (BIOS date)
5720 svn IBM (system vendor)
5721 pn 2371H4G (product name)
5722 pvr ThinkPadX40 (product version)
5723 rvn IBM (board vendor)
5724 rn 2371H4G (board name)
5725 rvr NotAvailable (board version)
5726 cvn IBM (chassis vendor)
5727 ct 10 (chassis type)
5728 cvr NotAvailable (chassis version)
5729 &lt;/pre&gt;
5730
5731 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
5732 found in the dmidecode source:&lt;/p&gt;
5733
5734 &lt;pre&gt;
5735 3 Desktop
5736 4 Low Profile Desktop
5737 5 Pizza Box
5738 6 Mini Tower
5739 7 Tower
5740 8 Portable
5741 9 Laptop
5742 10 Notebook
5743 11 Hand Held
5744 12 Docking Station
5745 13 All In One
5746 14 Sub Notebook
5747 15 Space-saving
5748 16 Lunch Box
5749 17 Main Server Chassis
5750 18 Expansion Chassis
5751 19 Sub Chassis
5752 20 Bus Expansion Chassis
5753 21 Peripheral Chassis
5754 22 RAID Chassis
5755 23 Rack Mount Chassis
5756 24 Sealed-case PC
5757 25 Multi-system
5758 26 CompactPCI
5759 27 AdvancedTCA
5760 28 Blade
5761 29 Blade Enclosing
5762 &lt;/pre&gt;
5763
5764 &lt;p&gt;The chassis type values are not always accurately set in the DMI
5765 table. For example my home server is a tower, but the DMI modalias
5766 claim it is a desktop.&lt;/p&gt;
5767
5768 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
5769
5770 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
5771 test machine:&lt;/p&gt;
5772
5773 &lt;p&gt;&lt;blockquote&gt;
5774 serio:ty01pr00id00ex00
5775 &lt;/blockquote&gt;&lt;/p&gt;
5776
5777 &lt;p&gt;The values present are&lt;/p&gt;
5778
5779 &lt;pre&gt;
5780 ty 01 (type)
5781 pr 00 (prototype)
5782 id 00 (id)
5783 ex 00 (extra)
5784 &lt;/pre&gt;
5785
5786 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
5787 the valid values are.&lt;/p&gt;
5788
5789 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
5790
5791 &lt;p&gt;There are heaps of other modalias subtypes according to
5792 file2alias.c. There is the rest of the list from that source: amba,
5793 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5794 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5795 vmbus, x86cpu and zorro. I did not spend time documenting all of
5796 these, as they do not seem relevant for my intended use with mapping
5797 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
5798
5799 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
5800
5801 &lt;p&gt;To check which kernel modules provide support for a given modalias,
5802 one can use the following shell script:&lt;/p&gt;
5803
5804 &lt;pre&gt;
5805 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
5806 echo &quot;$id&quot; ; \
5807 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
5808 done
5809 &lt;/pre&gt;
5810
5811 &lt;p&gt;The output can look like this (only the first few entries as the
5812 list is very long on my test machine):&lt;/p&gt;
5813
5814 &lt;pre&gt;
5815 acpi:ACPI0003:
5816 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
5817 acpi:device:
5818 FATAL: Module acpi:device: not found.
5819 acpi:IBM0068:
5820 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
5821 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
5822 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
5823 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5824 acpi:IBM0071:PNP0511:
5825 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
5826 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
5827 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
5828 [...]
5829 &lt;/pre&gt;
5830
5831 &lt;p&gt;If you want to help implementing a system to let us propose what
5832 packages to install when new hardware is plugged into a Debian
5833 machine, please send me an email or talk to me on
5834 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
5835
5836 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
5837 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
5838 in /sys/ with space in them.&lt;/p&gt;
5839 </description>
5840 </item>
5841
5842 <item>
5843 <title>Moved the pymissile Debian packaging to collab-maint</title>
5844 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
5845 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
5846 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
5847 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
5848 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5849 Launcher and updated the Debian package
5850 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
5851 sure udev will fix the device permissions when it is plugged in. I
5852 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
5853 hopefully make the package be proposed by jockey in Ubuntu when a user
5854 plug in his rocket launcher. In the process I moved the source to a
5855 git repository under collab-maint, to make it easier for any DD to
5856 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
5857 is not very active, but the software still work for me even after five
5858 years of relative silence. The new git repository is not listed in
5859 the uploaded package yet, because I want to test the other changes a
5860 bit more before I upload the new version. If you want to check out
5861 the new version with a .desktop file included, visit the
5862 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
5863 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
5864 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
5865 </description>
5866 </item>
5867
5868 <item>
5869 <title>Lets make hardware dongles easier to use in Debian</title>
5870 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
5871 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
5872 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
5873 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
5874 general, is that there is a great package management system with the
5875 ability to automatically install software packages by downloading them
5876 from the distribution mirrors, but no way to get it to automatically
5877 install the packages I need to use the hardware I plug into my
5878 machine. Even if the package to use it is easily available from the
5879 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5880 suggest to automatically install the python-nxt, nbc and t2n packages
5881 I need to talk to it. When I plug in a Yubikey, it could propose the
5882 yubikey-personalization package. The information required to do this
5883 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
5884
5885 &lt;p&gt;Some years ago, I proposed to
5886 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
5887 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
5888 simple:
5889
5890 &lt;ul&gt;
5891
5892 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
5893 starting when a user log in.&lt;/li&gt;
5894
5895 &lt;li&gt;Set this program up to listen for kernel events emitted when new
5896 hardware is inserted into the computer.&lt;/li&gt;
5897
5898 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
5899 database mapping to packages, and take note of any non-installed
5900 packages.&lt;/li&gt;
5901
5902 &lt;li&gt;Show a message to the user proposing to install the discovered
5903 package, and make it easy to install it.&lt;/li&gt;
5904
5905 &lt;/ul&gt;
5906
5907 &lt;p&gt;I am not sure what the best way to implement this is, but my
5908 initial idea was to use dbus events to discover new hardware, the
5909 discover database to find packages and
5910 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
5911 packages.&lt;/p&gt;
5912
5913 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
5914 draft package is now checked into
5915 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
5916 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
5917 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
5918 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5919 the relevant packages in Debian, and uploaded a new version
5920 2.2013.01.09 to unstable. I also discovered that the current
5921 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
5922 package in Debian no longer discovered any USB devices, because
5923 /proc/bus/usb/devices is no longer present. I ported it to use
5924 libusb as a fall back option to get it working. The fixed package
5925 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
5926 because of the freeze).&lt;/p&gt;
5927
5928 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
5929 desktop notification to show up (only once, the first time it is
5930 inserted):&lt;/p&gt;
5931
5932 &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;
5933
5934 &lt;p&gt;For this prototype to be really useful, some way to automatically
5935 install the proposed packages by pressing the &quot;Please install
5936 program(s)&quot; button should to be implemented.&lt;/p&gt;
5937
5938 &lt;p&gt;If this idea seem useful to you, and you want to help make it
5939 happen, please help me update the discover-data database with mappings
5940 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
5941 list the package you would like to have installed when a given
5942 hardware device is inserted into your computer, and report bugs using
5943 reportbug if it isn&#39;t. Or, if you know of a better way to provide
5944 such mapping, please let me know.&lt;/p&gt;
5945
5946 &lt;p&gt;This prototype need more work, and there are several questions that
5947 should be considered before it is ready for production use. Is dbus
5948 the correct way to detect new hardware? At the moment I look for HAL
5949 dbus events on the system bus, because that is the events I could see
5950 on my Debian Squeeze KDE desktop. Are there better events to use?
5951 How should the user be notified? Is the desktop notification
5952 mechanism the best option, or should the background daemon raise a
5953 popup instead? How should packages be installed? When should they
5954 not be installed?&lt;/p&gt;
5955
5956 &lt;p&gt;If you want to help getting such feature implemented in Debian,
5957 please send me an email. :)&lt;/p&gt;
5958 </description>
5959 </item>
5960
5961 <item>
5962 <title>New IRC channel for LEGO designers using Debian</title>
5963 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
5964 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
5965 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
5966 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
5967 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
5968 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
5969 discovered I had to build all the tools myself because none were
5970 already in Debian Squeeze. If Debian support for LEGO is something
5971 you care about, please join me on the IRC channel
5972 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
5973 irc.debian.org). There is a lot that could be done to improve the
5974 Debian support for LEGO designers. For example both CAD software
5975 and Mindstorm compilers are missing. :)&lt;/p&gt;
5976
5977 &lt;p&gt;Update 2012-01-03: A
5978 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
5979 including links to Lego related packages is now available.&lt;/p&gt;
5980 </description>
5981 </item>
5982
5983 <item>
5984 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
5985 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
5986 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
5987 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
5988 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
5989 year! I hope next year will prove to be a good year.&lt;/p&gt;
5990
5991 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
5992 decentralised &quot;currency&quot; that allow people to transfer bitcoins
5993 between each other with minimal overhead, is a very interesting
5994 experiment. And as I wrote a few days ago, the bitcoin situation in
5995 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
5996 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
5997 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
5998 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
5999 for one of the ftpmasters to approve the new bitcoin-qt package
6000 name.&lt;/p&gt;
6001
6002 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
6003 team in Debian, you can easily test the package in Debian Squeeze
6004 using the following steps to get a set of working packages:&lt;/p&gt;
6005
6006 &lt;blockquote&gt;&lt;pre&gt;
6007 git clone git://git.debian.org/git/collab-maint/bitcoin
6008 cd bitcoin
6009 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6010 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6011 &lt;/pre&gt;&lt;/blockquote&gt;
6012
6013 &lt;p&gt;You might have to install some build dependencies as well. The
6014 list of commands should give you two packages, bitcoind and
6015 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6016 client will download the complete set of bitcoin &quot;blocks&quot;, which need
6017 around 5.6 GiB of data on my machine at the moment. Make sure your
6018 ~/.bitcoin/ directory have lots of spare room if you want to download
6019 all the blocks. The client will warn if the disk is getting full, so
6020 there is not really a problem if you got too little room, but you will
6021 not be able to get all the features out of the client.&lt;/p&gt;
6022
6023 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6024 activities, please send Bitcoin donations to my address
6025 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6026 </description>
6027 </item>
6028
6029 <item>
6030 <title>A word on bitcoin support in Debian</title>
6031 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
6032 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
6033 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
6034 <description>&lt;p&gt;It has been a while since I wrote about
6035 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
6036 peer-to-peer based crypto-currency, and the reason is simply that I
6037 have been busy elsewhere. But two days ago, I started looking at the
6038 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
6039 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
6040 is now maintained by a
6041 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
6042 people&lt;/a&gt;, and the grunt work had already been done by this team. We
6043 owe a huge thank you to all these team members. :)
6044 But I was sad to discover that the bitcoin client is missing in
6045 Wheezy. It is only available in Sid (and an outdated client from
6046 backports). The client had several RC bugs registered in BTS blocking
6047 it from entering testing. To try to help the team and improve the
6048 situation, I spent some time providing patches and triaging the bug
6049 reports. I also had a look at the bitcoin package available from Matt
6050 Corallo in a
6051 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
6052 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
6053 Debian package.&lt;/p&gt;
6054
6055 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
6056 IRC, I pushed several patches into the collab-maint git repository to
6057 improve the package. It now contains fixes for the RC issues (not from
6058 me, but fixed by Scott Howard), build rules for a Qt GUI client
6059 package, konqueror support for the bitcoin: URI and bash completion
6060 setup. As I work on Debian Squeeze, I also created
6061 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
6062 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
6063 it and try to integrate it into the git repository before uploading a
6064 new version to unstable.
6065
6066 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
6067 centralized control currently exercised in the monetary system. I
6068 find it completely unacceptable that the USA government is collecting
6069 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6070 that the major credit card companies can block legal money
6071 transactions to Wikileaks. But for bitcoin to succeed, more people
6072 need to use bitcoins, and more people need to accept bitcoins when
6073 they sell products and services. Improving the bitcoin support in
6074 Debian is a small step in the right direction, but not enough.
6075 Unfortunately the user experience when browsing the web and wanting to
6076 pay with bitcoin is still not very good. The bitcoin: URI is a step
6077 in the right direction, but need to work in most or every browser in
6078 use. Also the bitcoin-qt client is too heavy to fire up to do a
6079 quick transaction. I believe there are other clients available, but
6080 have not tested them.&lt;/p&gt;
6081
6082 &lt;p&gt;My
6083 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
6084 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
6085 I received 20.15 BTC so far on the address I provided in my blog two
6086 years ago, as can be
6087 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
6088 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
6089 donation. The blockexplorer service demonstrates quite well that
6090 bitcoin is not quite anonymous and untracked. :) I wonder if the
6091 number of users have gone up since then. If you use bitcoin and want
6092 to show your support of my activity, please send Bitcoin donations to
6093 the same address as last time,
6094 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6095 </description>
6096 </item>
6097
6098 <item>
6099 <title>Git repository for song book for Computer Scientists</title>
6100 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
6101 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
6102 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
6103 <description>&lt;p&gt;As I
6104 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
6105 this summer&lt;/a&gt;, I have created a Computer Science song book a few
6106 years ago, and today I finally found time to create a public
6107 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
6108 repository for the project&lt;/a&gt;.&lt;/p&gt;
6109
6110 &lt;p&gt;If you want to help out, please clone the source and submit patches
6111 to the HTML version. To generate the PDF and PostScript version,
6112 please use prince XML, or let me know about a useful free software
6113 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
6114
6115 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
6116 PostScript formats at
6117 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
6118 Science Songbook&lt;/a&gt;.&lt;/p&gt;
6119 </description>
6120 </item>
6121
6122 <item>
6123 <title>Gratulerer med 19-årsdagen, Debian!</title>
6124 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
6125 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
6126 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
6127 <description>&lt;p&gt;I dag fyller
6128 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
6129 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
6130 si gratulerer med dagen, Debian!&lt;/p&gt;
6131 </description>
6132 </item>
6133
6134 <item>
6135 <title>Song book for Computer Scientists</title>
6136 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
6137 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
6138 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
6139 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
6140 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
6141 collecting computer related songs for use at parties. The original
6142 version was written in LaTeX, but a few years ago I got help from
6143 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6144 while keeping the ability to create a nice book in PDF format. I have
6145 not had time to maintain the book for a while now, and guess I should
6146 put it up on some public version control repository where others can
6147 help me extend and update the book. If anyone is volunteering to help
6148 me with this, send me an email. Also let me know if there are songs
6149 missing in my book.&lt;/p&gt;
6150
6151 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
6152 me today that I really should let all my readers share the joys of
6153 singing out load about programming, computers and computer networks.
6154 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
6155 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
6156 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
6157 Computer Science Songbook&lt;/a&gt;.
6158 </description>
6159 </item>
6160
6161 <item>
6162 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
6163 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
6164 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
6165 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
6166 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
6167 around 1000 at the moment. To be able to get help from the vendors
6168 when something go wrong, we want to keep the firmware on the servers
6169 up to date. If the firmware isn&#39;t the latest and greatest, the
6170 vendors typically refuse to start debugging any problems until the
6171 firmware is upgraded. So before every reboot, we want to upgrade the
6172 firmware, and we would really like everyone handling servers at the
6173 university to do this themselves when they plan to reboot a machine.
6174 For that to happen we at the unix server admin group need to provide
6175 the tools to do so.&lt;/p&gt;
6176
6177 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
6178 fetch and install the latest firmware for the servers we got. Most of
6179 our hardware are from Dell and HP, so I have focused on these servers
6180 so far. This blog post is about the Dell part.&lt;/P&gt;
6181
6182 &lt;p&gt;On the Dell FTP site I was lucky enough to find
6183 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
6184 with firmware information for all 11th generation servers, listing
6185 which firmware should be used on a given model and where on the FTP
6186 site I can find it. Using a simple perl XML parser I can then
6187 download the shell scripts Dell provides to do firmware upgrades from
6188 within Linux and reboot when all the firmware is primed and ready to
6189 be activated on the first reboot.&lt;/p&gt;
6190
6191 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
6192 Are there anyone working on similar tools for firmware upgrading all
6193 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
6194
6195 &lt;p&gt;&lt;pre&gt;
6196 #!/usr/bin/perl
6197 use strict;
6198 use warnings;
6199 use File::Temp qw(tempdir);
6200 BEGIN {
6201 # Install needed RHEL packages if missing
6202 my %rhelmodules = (
6203 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
6204 );
6205 for my $module (keys %rhelmodules) {
6206 eval &quot;use $module;&quot;;
6207 if ($@) {
6208 my $pkg = $rhelmodules{$module};
6209 system(&quot;yum install -y $pkg&quot;);
6210 eval &quot;use $module;&quot;;
6211 }
6212 }
6213 }
6214 my $errorsto = &#39;pere@hungry.com&#39;;
6215
6216 upgrade_dell();
6217
6218 exit 0;
6219
6220 sub run_firmware_script {
6221 my ($opts, $script) = @_;
6222 unless ($script) {
6223 print STDERR &quot;fail: missing script name\n&quot;;
6224 exit 1
6225 }
6226 print STDERR &quot;Running $script\n\n&quot;;
6227
6228 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
6229 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
6230 } else {
6231 print STDERR &quot;fail: firmware script returned error\n&quot;;
6232 }
6233 }
6234
6235 sub run_firmware_scripts {
6236 my ($opts, @dirs) = @_;
6237 # Run firmware packages
6238 for my $dir (@dirs) {
6239 print STDERR &quot;info: Running scripts in $dir\n&quot;;
6240 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
6241 while (my $s = readdir $dh) {
6242 next if $s =~ m/^\.\.?/;
6243 run_firmware_script($opts, &quot;$dir/$s&quot;);
6244 }
6245 closedir $dh;
6246 }
6247 }
6248
6249 sub download {
6250 my $url = shift;
6251 print STDERR &quot;info: Downloading $url\n&quot;;
6252 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
6253 }
6254
6255 sub upgrade_dell {
6256 my @dirs;
6257 my $product = `dmidecode -s system-product-name`;
6258 chomp $product;
6259
6260 if ($product =~ m/PowerEdge/) {
6261
6262 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6263 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
6264
6265 my $tmpdir = tempdir(
6266 CLEANUP =&gt; 1
6267 );
6268 chdir($tmpdir);
6269 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
6270 system(&#39;gunzip Catalog.xml.gz&#39;);
6271 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
6272 # -q is quiet, disabling interactivity and reducing console output
6273 my $fwopts = &quot;-q&quot;;
6274 if (@paths) {
6275 for my $url (@paths) {
6276 fetch_dell_fw($url);
6277 }
6278 run_firmware_scripts($fwopts, $tmpdir);
6279 } else {
6280 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6281 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6282 }
6283 chdir(&#39;/&#39;);
6284 } else {
6285 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6286 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6287 }
6288 }
6289
6290 sub fetch_dell_fw {
6291 my $path = shift;
6292 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
6293 download($url);
6294 }
6295
6296 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6297 # firmware packages to download from Dell. Only work for Linux
6298 # machines and 11th generation Dell servers.
6299 sub fetch_dell_fw_list {
6300 my $filename = shift;
6301
6302 my $product = `dmidecode -s system-product-name`;
6303 chomp $product;
6304 my ($mybrand, $mymodel) = split(/\s+/, $product);
6305
6306 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
6307
6308 my $xml = XMLin($filename);
6309 my @paths;
6310 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
6311 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
6312 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
6313 my $oscode;
6314 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
6315 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
6316 } else {
6317 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
6318 }
6319 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
6320 {
6321 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
6322 }
6323 }
6324 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
6325 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
6326
6327 # Drop application packages, only firmware and BIOS
6328 next if &#39;APAC&#39; eq $componenttype;
6329
6330 my $cpath = $component-&gt;{path};
6331 for my $path (@paths) {
6332 if ($cpath =~ m%/$path$%) {
6333 push(@paths, $cpath);
6334 }
6335 }
6336 }
6337 return @paths;
6338 }
6339 &lt;/pre&gt;
6340
6341 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
6342 it could work on other platforms with some tweaking. Anyone know a
6343 index like Catalog.xml is available from HP for HP servers? At the
6344 moment I maintain a similar list manually and it is quickly getting
6345 outdated.&lt;/p&gt;
6346 </description>
6347 </item>
6348
6349 <item>
6350 <title>How is booting into runlevel 1 different from single user boots?</title>
6351 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
6352 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
6353 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
6354 <description>&lt;p&gt;Wouter Verhelst have some
6355 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
6356 comments and opinions&lt;/a&gt; on my blog post on
6357 &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
6358 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
6359 &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
6360 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
6361 small piece of his comment now, and though it best to address the
6362 misunderstanding he bring forward:&lt;/p&gt;
6363
6364 &lt;p&gt;&lt;blockquote&gt;
6365 Currently, a system admin has four options: [...] boot to a
6366 single-user system (by adding &#39;single&#39; to the kernel command line;
6367 this runs rcS and rc1 scripts)
6368 &lt;/blockquote&gt;&lt;/p&gt;
6369
6370 &lt;p&gt;This make me believe Wouter believe booting into single user mode
6371 and booting into runlevel 1 is the same. I am not surprised he
6372 believe this, because it would make sense and is a quite sensible
6373 thing to believe. But because the boot in Debian is slightly broken,
6374 runlevel 1 do not work properly and it isn&#39;t the same as single user
6375 mode. I&#39;ll try to explain what is actually happing, but it is a bit
6376 hard to explain.&lt;/p&gt;
6377
6378 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
6379 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
6380 executed in single user mode is sulogin. Single user mode is a boot
6381 state &quot;between&quot; the runlevels, and when booting into single user mode,
6382 only the scripts in /etc/rcS.d/ are executed before the init process
6383 enters the single user state. When switching to runlevel 1, the state
6384 is in fact not ending in runlevel 1, but it passes through runlevel 1
6385 and end up in the single user mode (see /etc/rc1.d/S03single, which
6386 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
6387 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
6388 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6389 mode).&lt;/p&gt;
6390
6391 &lt;p&gt;This summary might make it clearer. When booting for the first
6392 time into single user mode, the following commands are executed:
6393 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
6394 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
6395 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
6396 trying to continue after visiting single user mode. Not all services
6397 are started again as they should, causing the machine to end up in an
6398 unpredicatble state. This is why Debian admins recommend rebooting
6399 after visiting single user mode.&lt;/p&gt;
6400
6401 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
6402 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
6403 to runlevel 1, the services started from /etc/rcS.d/ are not properly
6404 stopped when passing through the scripts in /etc/rc1.d/, and not
6405 started again when switching away from runlevel 1 to the runlevels
6406 2-5. I believe the problem is best fixed by moving all the scripts
6407 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
6408 functioning single user mode during boot.&lt;/p&gt;
6409
6410 &lt;p&gt;I have spent several years investigating the Debian boot system,
6411 and discovered this problem a few years ago. I suspect it originates
6412 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
6413 </description>
6414 </item>
6415
6416 <item>
6417 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
6418 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
6419 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
6420 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
6421 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
6422 are started from /etc/rcS.d/. In fact, there is a bite more of them
6423 than make sense, and this causes a few problems. What kind of
6424 problems, you might ask. There are at least two problems. The first
6425 is that it is not possible to recover a machine after switching to
6426 runlevel 1. One need to actually reboot to get the machine back to
6427 the expected state. The other is that single user boot will sometimes
6428 run into problems because some of the subsystems are activated before
6429 the root login is presented, causing problems when trying to recover a
6430 machine from a problem in that subsystem. A minor additional point is
6431 that moving more scripts out of rcS.d/ and into the other rc#.d/
6432 directories will increase the amount of scripts that can run in
6433 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
6434
6435 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
6436 scripts that _have_ to execute before the root login prompt is
6437 presented during a single user boot should go there. Everything else
6438 should go into the numeric runlevels. This means things like
6439 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6440 the numeric runlevels. Today in Debian, there are around 115 init.d
6441 scripts that are started from rcS.d/, and most of them should be moved
6442 out. Do your package have one of them? Please help us make single
6443 user and runlevel 1 better by moving it.&lt;/p&gt;
6444
6445 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
6446 etc. should still be started from rcS.d/, but there is for example no
6447 need to have the network enabled before the single user login prompt
6448 is presented.&lt;/p&gt;
6449
6450 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
6451 Debian systems working while scripts migrate and during upgrades, the
6452 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6453 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6454 and the next ones can only be moved when their dependencies have been
6455 moved first. This migration must be done sequentially while we ensure
6456 that the package system upgrade packages in the right order to keep
6457 the system state correct. This will require some coordination when it
6458 comes to network related packages, but most of the packages with
6459 scripts that should migrate do not have anything in rcS.d/ depending
6460 on them. Some packages have already been updated, like the sudo
6461 package, while others are still left to do. I wish I had time to work
6462 on this myself, but real live constrains make it unlikely that I will
6463 find time to push this forward.&lt;/p&gt;
6464 </description>
6465 </item>
6466
6467 <item>
6468 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
6469 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
6470 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
6471 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
6472 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
6473 mentioned the issues I believe should be improved in Debian for its
6474 desktop to be useful for more people. The use case for this is my
6475 parents, which are currently running Kubuntu which solve the
6476 issues.&lt;/p&gt;
6477
6478 &lt;p&gt;I suspect these four missing features are not very hard to
6479 implement. After all, they are present in Ubuntu, so if we wanted to
6480 do this in Debian we would have a source.&lt;/p&gt;
6481
6482 &lt;ol&gt;
6483
6484 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
6485 are new packages available for upgrades, a icon in the KDE status bar
6486 indicate this, and clicking on it will activate the simple upgrade
6487 tool to handle it. I have no problem guiding both of my parents
6488 through the process over the phone. If a kernel reboot is required,
6489 this too is indicated by the status bars and the upgrade tool. Last
6490 time I checked, nothing with the same features was working in KDE in
6491 Debian.&lt;/li&gt;
6492
6493 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
6494 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
6495 currently have a handler for, it will ask the user if the system
6496 should search for a package that would add support for this MIME type,
6497 and if the user say yes, the APT sources will be searched for packages
6498 advertising the MIME type in their control file (visible in the
6499 Packages file in the APT archive). If one or more packages are found,
6500 it is a simple click of the mouse to add support for the missing mime
6501 type. If the package require the user to accept some non-free
6502 license, this is explained to the user. The entire process make it
6503 more clear to the user why something do not work in the browser, and
6504 make the chances higher for the user to blame the web page authors and
6505 not the browser for any missing features.&lt;/li&gt;
6506
6507 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
6508 handlers.&lt;/strong&gt; When the media players encounter a format or codec
6509 it is not supporting, a dialog pop up asking the user if the system
6510 should search for a package that would add support for it. This
6511 happen with things like MP3, Windows Media or H.264. The selection
6512 and installation procedure is very similar to the Firefox browser
6513 plugin handling. This is as far as I know implemented using a
6514 gstreamer hook. The end result is that the user easily get access to
6515 the codecs that are present from the APT archives available, while
6516 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
6517
6518 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
6519 displaying a text/plain file in my Debian browser, it will propose to
6520 start emacs to show it. If I remember correctly, when doing the same
6521 in Kunbutu it show the file as a text file in the browser. At least I
6522 know Opera will show text files within the browser. I much prefer the
6523 latter behaviour.&lt;/li&gt;
6524
6525 &lt;/ol&gt;
6526
6527 &lt;p&gt;There are other nice features as well, like the simplified suite
6528 upgrader, but given that I am the one mostly doing the dist-upgrade,
6529 it do not matter much.&lt;/p&gt;
6530
6531 &lt;p&gt;I really hope we could get these features in place for the next
6532 Debian release. It would require the coordinated effort of several
6533 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
6534 </description>
6535 </item>
6536
6537 <item>
6538 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
6539 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
6540 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
6541 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
6542 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
6543 site is build on Debian/Squeeze, and this platform was chosen because
6544 I am most familiar with Debian (being a Debian Developer for around 10
6545 years) because it is the latest stable Debian release which should get
6546 security support for a few years.&lt;/p&gt;
6547
6548 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
6549 that are missing in Debian at the moment. It would be great if these
6550 modules were added to the Debian archive, allowing anyone to set up
6551 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
6552 in their own country using only Debian packages. The list of modules
6553 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
6554 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
6555 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6556 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6557 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6558 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6559 easier in the future.&lt;/p&gt;
6560
6561 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
6562 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
6563 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
6564 with the responsibility of tracking security problems, which I really
6565 do not have time for.&lt;/p&gt;
6566 </description>
6567 </item>
6568
6569 <item>
6570 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
6571 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
6572 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
6573 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
6574 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
6575 posts have been in Norwegian the last few weeks, so here is a short
6576 update in English.&lt;/p&gt;
6577
6578 &lt;p&gt;The kids still keep me too busy to get much free software work
6579 done, but I did manage to organise a project to get a Norwegian port
6580 of the British service
6581 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
6582 and it has been running for a month now. The entire project has been
6583 organised by me and two others. Around Christmas we gathered sponsors
6584 to fund the development work. In January I drafted a contract with
6585 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
6586 and in February the development took place. Most of it involved
6587 converting the source to use GPS coordinates instead of British
6588 easting/northing, and the resulting code should be a lot easier to get
6589 running in any country by now. The Norwegian
6590 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
6591 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
6592 source and the source for administrative borders in Norway, and
6593 support for this had to be added/fixed.&lt;/p&gt;
6594
6595 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
6596 polishing the system before we announced it March 7th. The system is
6597 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
6598 problem reports in a few weeks. Soon we hope to announce the Android
6599 and iPhone versions making it even easier to report problems with the
6600 public infrastructure.&lt;/p&gt;
6601
6602 &lt;p&gt;Perhaps something to consider for those of you in countries without
6603 such service?&lt;/p&gt;
6604 </description>
6605 </item>
6606
6607 <item>
6608 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
6609 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
6610 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
6611 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
6612 <description>&lt;p&gt;The last few days I have looked at ways to track open security
6613 issues here at my work with the University of Oslo. My idea is that
6614 it should be possible to use the information about security issues
6615 available on the Internet, and check our locally
6616 maintained/distributed software against this information. It should
6617 allow us to verify that no known security issues are forgotten. The
6618 CVE database listing vulnerabilities seem like a great central point,
6619 and by using the package lists from Debian mapped to CVEs provided by
6620 the testing security team, I believed it should be possible to figure
6621 out which security holes were present in our free software
6622 collection.&lt;/p&gt;
6623
6624 &lt;p&gt;After reading up on the topic, it became obvious that the first
6625 building block is to be able to name software packages in a unique and
6626 consistent way across data sources. I considered several ways to do
6627 this, for example coming up with my own naming scheme like using URLs
6628 to project home pages or URLs to the Freshmeat entries, or using some
6629 existing naming scheme. And it seem like I am not the first one to
6630 come across this problem, as MITRE already proposed and implemented a
6631 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
6632 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
6633 software, hardware and other platform components. The CPE ids are
6634 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
6635 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
6636 issues for any CPE name. With this in place, all I need to do is to
6637 locate the CPE id for the software packages we use at the university.
6638 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
6639 NVD entry if a CVE for the package exist).&lt;/p&gt;
6640
6641 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
6642 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
6643 check out, one could look up
6644 &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
6645 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
6646 The most recent one is
6647 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
6648 and at the bottom of the NVD page for this vulnerability the complete
6649 list of affected versions is provided.&lt;/p&gt;
6650
6651 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
6652 for offline processing of issues. Using this dump, I&#39;ve written a
6653 small script taking a list of CPEs as input and list all CVEs
6654 affecting the packages represented by these CPEs. One give it CPEs
6655 with version numbers as specified above and get a list of open
6656 security issues out.&lt;/p&gt;
6657
6658 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
6659 information need to be high. For that to happen, I believe as many as
6660 possible need to use and contribute to the NVD database. I notice
6661 RHEL is providing
6662 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
6663 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
6664 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
6665
6666 &lt;p&gt;To get an idea about the quality for free software, I spent some
6667 time making it possible to compare the CVE database from Debian with
6668 the CVE database in NVD. The result look fairly good, but there are
6669 some inconsistencies in NVD (same software package having several
6670 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6671 Debian believe are affected by a CVE). Hope to find time to improve
6672 the quality of NVD, but that require being able to get in touch with
6673 someone maintaining it. So far my three emails with questions and
6674 corrections have not seen any reply, but I hope contact can be
6675 established soon.&lt;/p&gt;
6676
6677 &lt;p&gt;An interesting application for CPEs is cross platform package
6678 mapping. It would be useful to know which packages in for example
6679 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6680 this would be trivial if all linux distributions provided CPE entries
6681 for their packages.&lt;/p&gt;
6682 </description>
6683 </item>
6684
6685 <item>
6686 <title>Which module is loaded for a given PCI and USB device?</title>
6687 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
6688 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
6689 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
6690 <description>&lt;p&gt;In the
6691 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
6692 package in Debian, there is a script to report useful information
6693 about the running hardware for use when people report missing
6694 information. One part of this script that I find very useful when
6695 debugging hardware problems, is the part mapping loaded kernel module
6696 to the PCI device it claims. It allow me to quickly see if the kernel
6697 module I expect is driving the hardware I am struggling with. To see
6698 the output, make sure discover-data is installed and run
6699 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
6700 one of my machines like this:&lt;/p&gt;
6701
6702 &lt;pre&gt;
6703 loaded modules:
6704 10de:03eb i2c_nforce2
6705 10de:03f1 ohci_hcd
6706 10de:03f2 ehci_hcd
6707 10de:03f0 snd_hda_intel
6708 10de:03ec pata_amd
6709 10de:03f6 sata_nv
6710 1022:1103 k8temp
6711 109e:036e bttv
6712 109e:0878 snd_bt87x
6713 11ab:4364 sky2
6714 &lt;/pre&gt;
6715
6716 &lt;p&gt;The code in question look like this, slightly modified for
6717 readability and to drop the output to file descriptor 3:&lt;/p&gt;
6718
6719 &lt;pre&gt;
6720 if [ -d /sys/bus/pci/devices/ ] ; then
6721 echo loaded pci modules:
6722 (
6723 cd /sys/bus/pci/devices/
6724 for address in * ; do
6725 if [ -d &quot;$address/driver/module&quot; ] ; then
6726 module=`cd $address/driver/module ; pwd -P | xargs basename`
6727 if grep -q &quot;^$module &quot; /proc/modules ; then
6728 address=$(echo $address |sed s/0000://)
6729 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
6730 echo &quot;$id $module&quot;
6731 fi
6732 fi
6733 done
6734 )
6735 echo
6736 fi
6737 &lt;/pre&gt;
6738
6739 &lt;p&gt;Similar code could be used to extract USB device module
6740 mappings:&lt;/p&gt;
6741
6742 &lt;pre&gt;
6743 if [ -d /sys/bus/usb/devices/ ] ; then
6744 echo loaded usb modules:
6745 (
6746 cd /sys/bus/usb/devices/
6747 for address in * ; do
6748 if [ -d &quot;$address/driver/module&quot; ] ; then
6749 module=`cd $address/driver/module ; pwd -P | xargs basename`
6750 if grep -q &quot;^$module &quot; /proc/modules ; then
6751 address=$(echo $address |sed s/0000://)
6752 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
6753 if [ &quot;$id&quot; ] ; then
6754 echo &quot;$id $module&quot;
6755 fi
6756 fi
6757 fi
6758 done
6759 )
6760 echo
6761 fi
6762 &lt;/pre&gt;
6763
6764 &lt;p&gt;This might perhaps be something to include in other tools as
6765 well.&lt;/p&gt;
6766 </description>
6767 </item>
6768
6769 <item>
6770 <title>How to test if a laptop is working with Linux</title>
6771 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
6772 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
6773 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
6774 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
6775 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
6776 batch of computers will work with Linux. Every year for the last few
6777 years the university have organised shared bid of a few thousand
6778 computers, and this year HP won the bid. Two different desktops and
6779 five different laptops are on the list this year. We in the UNIX
6780 group want to know which one of these computers work well with RHEL
6781 and Ubuntu, the two Linux distributions we currently handle at the
6782 university.&lt;/p&gt;
6783
6784 &lt;p&gt;My test method is simple, and I share it here to get feedback and
6785 perhaps inspire others to test hardware as well. To test, I PXE
6786 install the OS version of choice, and log in as my normal user and run
6787 a few applications and plug in selected pieces of hardware. When
6788 something fail, I make a note about this in the test matrix and move
6789 on. If I have some spare time I try to report the bug to the OS
6790 vendor, but as I only have the machines for a short time, I rarely
6791 have the time to do this for all the problems I find.&lt;/p&gt;
6792
6793 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
6794 I perform on a new model.&lt;/p&gt;
6795
6796 &lt;ul&gt;
6797
6798 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
6799 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6800 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
6801
6802 &lt;li&gt;Is X.org working? If the graphical login screen show up after
6803 installation, X.org is working.&lt;/li&gt;
6804
6805 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
6806 package mesa-utils on Ubuntu) and writing down the frames per second
6807 reported by the program.&lt;/li&gt;
6808
6809 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
6810 logging in, and if I can hear this the test is successful. If there
6811 are several audio exits on the machine, I try them all and check if
6812 the Gnome/KDE audio mixer can control where to send the sound. I
6813 normally test this by playing
6814 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
6815 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
6816
6817 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
6818 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
6819
6820 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
6821 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
6822
6823 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
6824 picture from the v4l device show up.&lt;/li&gt;
6825
6826 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6827 any bluetooth devices are discovered. In my office, I normally see a
6828 few.&lt;/li&gt;
6829
6830 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
6831 memory modules lying around, and stick them in and see if Gnome/KDE
6832 notice this.&lt;/li&gt;
6833
6834 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
6835 special button work, and if the laptop continue to work after
6836 resume.&lt;/li&gt;
6837
6838 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
6839 adjusting background light, switching on/off external video output,
6840 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6841 laptop to laptop, so I just write down which are working and which are
6842 not.&lt;/li&gt;
6843
6844 &lt;li&gt;Some laptops have smart card readers, finger print readers,
6845 acceleration sensors etc. I rarely test these, as I do not know how
6846 to quickly test if they are working or not, so I only document their
6847 existence.&lt;/li&gt;
6848
6849 &lt;/ul&gt;
6850
6851 &lt;p&gt;By now I suspect you are really curious what the test results are
6852 for the HP machines I am testing. I&#39;m not done yet, so I will report
6853 the test results later. For now I can report that HP 8100 Elite work
6854 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
6855 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
6856 can see, I have most machines left to test. One interesting
6857 observation is that Ubuntu Lucid has almost twice the frame rate than
6858 RHEL6 with glxgears. No idea why.&lt;/p&gt;
6859 </description>
6860 </item>
6861
6862 <item>
6863 <title>Some thoughts on BitCoins</title>
6864 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
6865 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
6866 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
6867 <description>&lt;p&gt;As I continue to explore
6868 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
6869 what properties the system have, and how it will be affected by laws
6870 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
6871
6872 &lt;p&gt;One interesting thing to note is that since the transactions are
6873 verified using a peer to peer network, all details about a transaction
6874 is known to everyone. This means that if a BitCoin address has been
6875 published like I did with mine in my initial post about BitCoin, it is
6876 possible for everyone to see how many BitCoins have been transfered to
6877 that address. There is even a web service to look at the details for
6878 all transactions. There I can see that my address
6879 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
6880 have received 16.06 Bitcoin, the
6881 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
6882 address of Simon Phipps have received 181.97 BitCoin and the address
6883 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
6884 of EFF have received 2447.38 BitCoins so far. Thank you to each and
6885 every one of you that donated bitcoins to support my activity. The
6886 fact that anyone can see how much money was transfered to a given
6887 address make it more obvious why the BitCoin community recommend to
6888 generate and hand out a new address for each transaction. I&#39;m told
6889 there is no way to track which addresses belong to a given person or
6890 organisation without the person or organisation revealing it
6891 themselves, as Simon, EFF and I have done.&lt;/p&gt;
6892
6893 &lt;p&gt;In Norway, and in most other countries, there are laws and
6894 regulations limiting how much money one can transfer across the border
6895 without declaring it. There are money laundering, tax and accounting
6896 laws and regulations I would expect to apply to the use of BitCoin.
6897 If the Skolelinux foundation
6898 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
6899 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
6900 normal bank transfers like EFF is doing, how should this be accounted?
6901 Given that it is impossible to know if money can cross the border or
6902 not, should everything or nothing be declared? What exchange rate
6903 should be used when calculating taxes? Would receivers have to pay
6904 income tax if the foundation were to pay Skolelinux contributors in
6905 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
6906
6907 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
6908 accepted by a lot of users. It must be possible to get easy access to
6909 the currency (as a wage or using currency exchanges), and it must be
6910 easy to spend it. At the moment BitCoin seem fairly easy to get
6911 access to, but there are very few places to spend it. I am not really
6912 a regular user of any of the vendor types currently accepting BitCoin,
6913 so I wonder when my kind of shop would start accepting BitCoins. I
6914 would like to buy electronics, travels and subway tickets, not herbs
6915 and books. :) The currency is young, and this will improve over time
6916 if it become popular, but I suspect regular banks will start to lobby
6917 to get BitCoin declared illegal if it become popular. I&#39;m sure they
6918 will claim it is helping fund terrorism and money laundering (which
6919 probably would be true, as is any currency in existence), but I
6920 believe the problems should be solved elsewhere and not by blaming
6921 currencies.&lt;/p&gt;
6922
6923 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
6924 CPU intensive process that depend on a bit of luck as well (as one is
6925 competing against all the other miners currently spending CPU cycles
6926 to see which one get the next lump of cash). The &quot;winner&quot; get 50
6927 BitCoin when this happen. Yesterday I came across the obvious way to
6928 join forces to increase ones changes of getting at least some coins,
6929 by coordinating the work on mining BitCoins across several machines
6930 and people, and sharing the result if one is lucky and get the 50
6931 BitCoins. Check out
6932 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
6933 if this sounds interesting. I have not had time to try to set up a
6934 machine to participate there yet, but have seen that running on ones
6935 own for a few days have not yield any BitCoins througth mining
6936 yet.&lt;/p&gt;
6937
6938 &lt;p&gt;Update 2010-12-15: Found an &lt;a
6939 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
6940 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
6941 it was interesting to read. The arguments presented seem to be
6942 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
6943 </description>
6944 </item>
6945
6946 <item>
6947 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
6948 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
6949 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
6950 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
6951 <description>&lt;p&gt;With this weeks lawless
6952 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
6953 attacks&lt;/a&gt; on Wikileak and
6954 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
6955 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
6956 not be trusted to handle money transactions.
6957 A blog post from
6958 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
6959 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
6960 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
6961 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
6962 some help from my friend to get it all running, and he even handed me
6963 some bitcoins to get started. I even donated a few bitcoins to Simon
6964 for helping me remember BitCoin.&lt;/p&gt;
6965
6966 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
6967 crypto-currency, decentralised and handled using peer-to-peer
6968 networks. It allows anonymous transactions and prohibits central
6969 control over the transactions, making it impossible for governments
6970 and companies alike to block donations and other transactions. The
6971 source is free software, and while the key dependency wxWidgets 2.9
6972 for the graphical user interface is missing in Debian, the command
6973 line client builds just fine. Hopefully Jonas
6974 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
6975 Debian&lt;/a&gt; soon.&lt;/p&gt;
6976
6977 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
6978 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
6979 bitcoins&lt;/a&gt; when selling services and goods, and there are even
6980 currency &quot;stock&quot; markets where the exchange rate is decided. There
6981 are not many users so far, but the concept seems promising. If you
6982 want to get started and lack a friend with any bitcoins to spare,
6983 you can even get
6984 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
6985 bitcoin at the time of writing). Use
6986 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
6987 on the current exchange rates.&lt;/p&gt;
6988
6989 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
6990 machines. If you want to support my activity, please send Bitcoin
6991 donations to the address
6992 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
6993 </description>
6994 </item>
6995
6996 <item>
6997 <title>Why isn&#39;t Debian Edu using VLC?</title>
6998 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
6999 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
7000 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
7001 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
7002 presented, and the winner among the multimedia player were VLC.
7003 Personally, I like VLC, and it is my player of choice when I first try
7004 to play a video file or stream. Only if VLC fail will I drag out
7005 gmplayer to see if it can do better. The reason is mostly the failure
7006 model and trust. When VLC fail, it normally pop up a error message
7007 reporting the problem. When mplayer fail, it normally segfault or
7008 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
7009
7010 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
7011 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
7012 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
7013 plugin to play web videos seamlessly, and the VLC browser plugin is
7014 not very good. For example, it lack in-line control buttons, so there
7015 is no way for the user to pause the video. Also, when I
7016 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
7017 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
7018 failed on several video pages where mplayer based plugins worked. If
7019 the browser plugin for VLC was as good as the gecko-mediaplayer
7020 package (which uses mplayer), we would switch.&lt;/P&gt;
7021
7022 &lt;p&gt;While VLC is a good player, its user interface is slightly
7023 annoying. The most annoying feature is its inconsistent use of
7024 keyboard shortcuts. When the player is in full screen mode, its
7025 shortcuts are different from when it is playing the video in a window.
7026 For example, space only work as pause when in full screen mode. I
7027 wish it had consisten shortcuts and that space also would work when in
7028 window mode. Another nice shortcut in gmplayer is [enter] to restart
7029 the current video. It is very nice when playing short videos from the
7030 web and want to restart it when new people arrive to have a look at
7031 what is going on.&lt;/p&gt;
7032 </description>
7033 </item>
7034
7035 <item>
7036 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
7037 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
7038 <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>
7039 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
7040 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
7041 upgrade testing of the
7042 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7043 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
7044 This seem like a very good idea, so I adjusted by test scripts and
7045 can now present the updated result from today:&lt;/p&gt;
7046
7047 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7048
7049 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7050
7051 &lt;blockquote&gt;&lt;p&gt;
7052 apache2.2-bin
7053 aptdaemon
7054 baobab
7055 binfmt-support
7056 browser-plugin-gnash
7057 cheese-common
7058 cli-common
7059 cups-pk-helper
7060 dmz-cursor-theme
7061 empathy
7062 empathy-common
7063 freedesktop-sound-theme
7064 freeglut3
7065 gconf-defaults-service
7066 gdm-themes
7067 gedit-plugins
7068 geoclue
7069 geoclue-hostip
7070 geoclue-localnet
7071 geoclue-manual
7072 geoclue-yahoo
7073 gnash
7074 gnash-common
7075 gnome
7076 gnome-backgrounds
7077 gnome-cards-data
7078 gnome-codec-install
7079 gnome-core
7080 gnome-desktop-environment
7081 gnome-disk-utility
7082 gnome-screenshot
7083 gnome-search-tool
7084 gnome-session-canberra
7085 gnome-system-log
7086 gnome-themes-extras
7087 gnome-themes-more
7088 gnome-user-share
7089 gstreamer0.10-fluendo-mp3
7090 gstreamer0.10-tools
7091 gtk2-engines
7092 gtk2-engines-pixbuf
7093 gtk2-engines-smooth
7094 hamster-applet
7095 libapache2-mod-dnssd
7096 libapr1
7097 libaprutil1
7098 libaprutil1-dbd-sqlite3
7099 libaprutil1-ldap
7100 libart2.0-cil
7101 libboost-date-time1.42.0
7102 libboost-python1.42.0
7103 libboost-thread1.42.0
7104 libchamplain-0.4-0
7105 libchamplain-gtk-0.4-0
7106 libcheese-gtk18
7107 libclutter-gtk-0.10-0
7108 libcryptui0
7109 libdiscid0
7110 libelf1
7111 libepc-1.0-2
7112 libepc-common
7113 libepc-ui-1.0-2
7114 libfreerdp-plugins-standard
7115 libfreerdp0
7116 libgconf2.0-cil
7117 libgdata-common
7118 libgdata7
7119 libgdu-gtk0
7120 libgee2
7121 libgeoclue0
7122 libgexiv2-0
7123 libgif4
7124 libglade2.0-cil
7125 libglib2.0-cil
7126 libgmime2.4-cil
7127 libgnome-vfs2.0-cil
7128 libgnome2.24-cil
7129 libgnomepanel2.24-cil
7130 libgpod-common
7131 libgpod4
7132 libgtk2.0-cil
7133 libgtkglext1
7134 libgtksourceview2.0-common
7135 libmono-addins-gui0.2-cil
7136 libmono-addins0.2-cil
7137 libmono-cairo2.0-cil
7138 libmono-corlib2.0-cil
7139 libmono-i18n-west2.0-cil
7140 libmono-posix2.0-cil
7141 libmono-security2.0-cil
7142 libmono-sharpzip2.84-cil
7143 libmono-system2.0-cil
7144 libmtp8
7145 libmusicbrainz3-6
7146 libndesk-dbus-glib1.0-cil
7147 libndesk-dbus1.0-cil
7148 libopal3.6.8
7149 libpolkit-gtk-1-0
7150 libpt2.6.7
7151 libpython2.6
7152 librpm1
7153 librpmio1
7154 libsdl1.2debian
7155 libsrtp0
7156 libssh-4
7157 libtelepathy-farsight0
7158 libtelepathy-glib0
7159 libtidy-0.99-0
7160 media-player-info
7161 mesa-utils
7162 mono-2.0-gac
7163 mono-gac
7164 mono-runtime
7165 nautilus-sendto
7166 nautilus-sendto-empathy
7167 p7zip-full
7168 pkg-config
7169 python-aptdaemon
7170 python-aptdaemon-gtk
7171 python-axiom
7172 python-beautifulsoup
7173 python-bugbuddy
7174 python-clientform
7175 python-coherence
7176 python-configobj
7177 python-crypto
7178 python-cupshelpers
7179 python-elementtree
7180 python-epsilon
7181 python-evolution
7182 python-feedparser
7183 python-gdata
7184 python-gdbm
7185 python-gst0.10
7186 python-gtkglext1
7187 python-gtksourceview2
7188 python-httplib2
7189 python-louie
7190 python-mako
7191 python-markupsafe
7192 python-mechanize
7193 python-nevow
7194 python-notify
7195 python-opengl
7196 python-openssl
7197 python-pam
7198 python-pkg-resources
7199 python-pyasn1
7200 python-pysqlite2
7201 python-rdflib
7202 python-serial
7203 python-tagpy
7204 python-twisted-bin
7205 python-twisted-conch
7206 python-twisted-core
7207 python-twisted-web
7208 python-utidylib
7209 python-webkit
7210 python-xdg
7211 python-zope.interface
7212 remmina
7213 remmina-plugin-data
7214 remmina-plugin-rdp
7215 remmina-plugin-vnc
7216 rhythmbox-plugin-cdrecorder
7217 rhythmbox-plugins
7218 rpm-common
7219 rpm2cpio
7220 seahorse-plugins
7221 shotwell
7222 software-center
7223 system-config-printer-udev
7224 telepathy-gabble
7225 telepathy-mission-control-5
7226 telepathy-salut
7227 tomboy
7228 totem
7229 totem-coherence
7230 totem-mozilla
7231 totem-plugins
7232 transmission-common
7233 xdg-user-dirs
7234 xdg-user-dirs-gtk
7235 xserver-xephyr
7236 &lt;/p&gt;&lt;/blockquote&gt;
7237
7238 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7239
7240 &lt;blockquote&gt;&lt;p&gt;
7241 cheese
7242 ekiga
7243 eog
7244 epiphany-extensions
7245 evolution-exchange
7246 fast-user-switch-applet
7247 file-roller
7248 gcalctool
7249 gconf-editor
7250 gdm
7251 gedit
7252 gedit-common
7253 gnome-games
7254 gnome-games-data
7255 gnome-nettool
7256 gnome-system-tools
7257 gnome-themes
7258 gnuchess
7259 gucharmap
7260 guile-1.8-libs
7261 libavahi-ui0
7262 libdmx1
7263 libgalago3
7264 libgtk-vnc-1.0-0
7265 libgtksourceview2.0-0
7266 liblircclient0
7267 libsdl1.2debian-alsa
7268 libspeexdsp1
7269 libsvga1
7270 rhythmbox
7271 seahorse
7272 sound-juicer
7273 system-config-printer
7274 totem-common
7275 transmission-gtk
7276 vinagre
7277 vino
7278 &lt;/p&gt;&lt;/blockquote&gt;
7279
7280 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7281
7282 &lt;blockquote&gt;&lt;p&gt;
7283 gstreamer0.10-gnomevfs
7284 &lt;/p&gt;&lt;/blockquote&gt;
7285
7286 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7287
7288 &lt;blockquote&gt;&lt;p&gt;
7289 [nothing]
7290 &lt;/p&gt;&lt;/blockquote&gt;
7291
7292 &lt;p&gt;This is for KDE:&lt;/p&gt;
7293
7294 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7295
7296 &lt;blockquote&gt;&lt;p&gt;
7297 ksmserver
7298 &lt;/p&gt;&lt;/blockquote&gt;
7299
7300 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7301
7302 &lt;blockquote&gt;&lt;p&gt;
7303 kwin
7304 network-manager-kde
7305 &lt;/p&gt;&lt;/blockquote&gt;
7306
7307 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7308
7309 &lt;blockquote&gt;&lt;p&gt;
7310 arts
7311 dolphin
7312 freespacenotifier
7313 google-gadgets-gst
7314 google-gadgets-xul
7315 kappfinder
7316 kcalc
7317 kcharselect
7318 kde-core
7319 kde-plasma-desktop
7320 kde-standard
7321 kde-window-manager
7322 kdeartwork
7323 kdeartwork-emoticons
7324 kdeartwork-style
7325 kdeartwork-theme-icon
7326 kdebase
7327 kdebase-apps
7328 kdebase-workspace
7329 kdebase-workspace-bin
7330 kdebase-workspace-data
7331 kdeeject
7332 kdelibs
7333 kdeplasma-addons
7334 kdeutils
7335 kdewallpapers
7336 kdf
7337 kfloppy
7338 kgpg
7339 khelpcenter4
7340 kinfocenter
7341 konq-plugins-l10n
7342 konqueror-nsplugins
7343 kscreensaver
7344 kscreensaver-xsavers
7345 ktimer
7346 kwrite
7347 libgle3
7348 libkde4-ruby1.8
7349 libkonq5
7350 libkonq5-templates
7351 libnetpbm10
7352 libplasma-ruby
7353 libplasma-ruby1.8
7354 libqt4-ruby1.8
7355 marble-data
7356 marble-plugins
7357 netpbm
7358 nuvola-icon-theme
7359 plasma-dataengines-workspace
7360 plasma-desktop
7361 plasma-desktopthemes-artwork
7362 plasma-runners-addons
7363 plasma-scriptengine-googlegadgets
7364 plasma-scriptengine-python
7365 plasma-scriptengine-qedje
7366 plasma-scriptengine-ruby
7367 plasma-scriptengine-webkit
7368 plasma-scriptengines
7369 plasma-wallpapers-addons
7370 plasma-widget-folderview
7371 plasma-widget-networkmanagement
7372 ruby
7373 sweeper
7374 update-notifier-kde
7375 xscreensaver-data-extra
7376 xscreensaver-gl
7377 xscreensaver-gl-extra
7378 xscreensaver-screensaver-bsod
7379 &lt;/p&gt;&lt;/blockquote&gt;
7380
7381 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7382
7383 &lt;blockquote&gt;&lt;p&gt;
7384 ark
7385 google-gadgets-common
7386 google-gadgets-qt
7387 htdig
7388 kate
7389 kdebase-bin
7390 kdebase-data
7391 kdepasswd
7392 kfind
7393 klipper
7394 konq-plugins
7395 konqueror
7396 ksysguard
7397 ksysguardd
7398 libarchive1
7399 libcln6
7400 libeet1
7401 libeina-svn-06
7402 libggadget-1.0-0b
7403 libggadget-qt-1.0-0b
7404 libgps19
7405 libkdecorations4
7406 libkephal4
7407 libkonq4
7408 libkonqsidebarplugin4a
7409 libkscreensaver5
7410 libksgrd4
7411 libksignalplotter4
7412 libkunitconversion4
7413 libkwineffects1a
7414 libmarblewidget4
7415 libntrack-qt4-1
7416 libntrack0
7417 libplasma-geolocation-interface4
7418 libplasmaclock4a
7419 libplasmagenericshell4
7420 libprocesscore4a
7421 libprocessui4a
7422 libqalculate5
7423 libqedje0a
7424 libqtruby4shared2
7425 libqzion0a
7426 libruby1.8
7427 libscim8c2a
7428 libsmokekdecore4-3
7429 libsmokekdeui4-3
7430 libsmokekfile3
7431 libsmokekhtml3
7432 libsmokekio3
7433 libsmokeknewstuff2-3
7434 libsmokeknewstuff3-3
7435 libsmokekparts3
7436 libsmokektexteditor3
7437 libsmokekutils3
7438 libsmokenepomuk3
7439 libsmokephonon3
7440 libsmokeplasma3
7441 libsmokeqtcore4-3
7442 libsmokeqtdbus4-3
7443 libsmokeqtgui4-3
7444 libsmokeqtnetwork4-3
7445 libsmokeqtopengl4-3
7446 libsmokeqtscript4-3
7447 libsmokeqtsql4-3
7448 libsmokeqtsvg4-3
7449 libsmokeqttest4-3
7450 libsmokeqtuitools4-3
7451 libsmokeqtwebkit4-3
7452 libsmokeqtxml4-3
7453 libsmokesolid3
7454 libsmokesoprano3
7455 libtaskmanager4a
7456 libtidy-0.99-0
7457 libweather-ion4a
7458 libxklavier16
7459 libxxf86misc1
7460 okteta
7461 oxygencursors
7462 plasma-dataengines-addons
7463 plasma-scriptengine-superkaramba
7464 plasma-widget-lancelot
7465 plasma-widgets-addons
7466 plasma-widgets-workspace
7467 polkit-kde-1
7468 ruby1.8
7469 systemsettings
7470 update-notifier-common
7471 &lt;/p&gt;&lt;/blockquote&gt;
7472
7473 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
7474 aptitude a bit more similar, but there are still quite a lott of
7475 differences. I have no idea what packages should be installed after
7476 the upgrade, but hope those that do can have a look.&lt;/p&gt;
7477 </description>
7478 </item>
7479
7480 <item>
7481 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
7482 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
7483 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
7484 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
7485 <description>&lt;p&gt;Most of the computers in use by the
7486 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
7487 are virtual machines. And they have been Xen machines running on a
7488 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
7489 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
7490 bit harder that it could have been, because we set up the Xen virtual
7491 machines to get the virtual partitions from LVM, which as far as I
7492 know is not supported by KVM. So to migrate, we had to convert
7493 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
7494
7495 &lt;p&gt;I found
7496 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
7497 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
7498 migration. It uses qemu-img from the qemu package to make the disk
7499 image, parted to partition it, losetup and kpartx to present the disk
7500 image partions as devices, and dd to copy the data. I NFS mounted the
7501 new servers storage area on the old server to do the migration.&lt;/p&gt;
7502
7503 &lt;pre&gt;
7504 #!/bin/sh
7505
7506 # Based on
7507 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7508
7509 set -e
7510 set -x
7511
7512 if [ -z &quot;$1&quot; ] ; then
7513 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
7514 exit 1
7515 else
7516 host=&quot;$1&quot;
7517 fi
7518
7519 if [ ! -e /dev/vg_data/$host-disk ] ; then
7520 echo &quot;error: unable to find LVM volume for $host&quot;
7521 exit 1
7522 fi
7523
7524 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7525 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
7526 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
7527 totalsize=$(( ( $disksize + $swapsize ) ))
7528
7529 img=$host.img
7530 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
7531 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7532
7533 parted $img mklabel msdos
7534 parted $img mkpart primary linux-swap 0 $disksize
7535 parted $img mkpart primary ext2 $disksize $totalsize
7536 parted $img set 1 boot on
7537
7538 modprobe dm-mod
7539 losetup /dev/loop0 $img
7540 kpartx -a /dev/loop0
7541
7542 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
7543 fsck.ext3 -f /dev/mapper/loop0p1 || true
7544 mkswap /dev/mapper/loop0p2
7545
7546 kpartx -d /dev/loop0
7547 losetup -d /dev/loop0
7548 &lt;/pre&gt;
7549
7550 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
7551 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
7552
7553 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
7554 the new disk image attached, installed grub-pc and linux-image-686 and
7555 set up grub to boot from the disk image. After this, the KVM machines
7556 seem to work just fine.&lt;/p&gt;
7557 </description>
7558 </item>
7559
7560 <item>
7561 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
7562 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
7563 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
7564 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
7565 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
7566 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7567 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
7568 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
7569
7570 &lt;p&gt;I still do not know what a correct migration should look like, so I
7571 report any differences between apt and aptitude and hope someone else
7572 can see if anything should be changed.&lt;/p&gt;
7573
7574 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7575
7576 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7577
7578 &lt;blockquote&gt;&lt;p&gt;
7579 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7580 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
7581 dmz-cursor-theme empathy empathy-common finger
7582 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7583 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7584 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7585 gnome-cards-data gnome-codec-install gnome-core
7586 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7587 gnome-search-tool gnome-session-canberra gnome-spell
7588 gnome-system-log gnome-themes-extras gnome-themes-more
7589 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7590 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7591 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7592 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7593 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
7594 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
7595 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
7596 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
7597 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
7598 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7599 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
7600 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7601 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7602 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7603 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7604 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7605 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7606 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7607 libmono-security2.0-cil libmono-sharpzip2.84-cil
7608 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
7609 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
7610 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
7611 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
7612 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
7613 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
7614 libxalan2-java libxerces2-java media-player-info mesa-utils
7615 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
7616 nautilus-sendto-empathy openoffice.org-writer2latex
7617 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
7618 python-aptdaemon python-aptdaemon-gtk python-axiom
7619 python-beautifulsoup python-bugbuddy python-clientform
7620 python-coherence python-configobj python-crypto python-cupshelpers
7621 python-cupsutils python-eggtrayicon python-elementtree
7622 python-epsilon python-evolution python-feedparser python-gdata
7623 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7624 python-gtksourceview2 python-httplib2 python-louie python-mako
7625 python-markupsafe python-mechanize python-nevow python-notify
7626 python-opengl python-openssl python-pam python-pkg-resources
7627 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7628 python-tagpy python-twisted-bin python-twisted-conch
7629 python-twisted-core python-twisted-web python-utidylib python-webkit
7630 python-xdg python-zope.interface remmina remmina-plugin-data
7631 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7632 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7633 software-center svgalibg1 system-config-printer-udev
7634 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
7635 totem totem-coherence totem-mozilla totem-plugins
7636 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7637 zip
7638 &lt;/p&gt;&lt;/blockquote&gt;
7639
7640 Installed using apt-get, removed with aptitude
7641
7642 &lt;blockquote&gt;&lt;p&gt;
7643 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7644 epiphany-extensions epiphany-gecko evolution-exchange
7645 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7646 gedit-common gnome-app-install gnome-games gnome-games-data
7647 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7648 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7649 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7650 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
7651 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
7652 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
7653 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
7654 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7655 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7656 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7657 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
7658 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
7659 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7660 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7661 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7662 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7663 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
7664 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
7665 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
7666 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
7667 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
7668 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7669 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7670 sound-juicer swfdec-gnome system-config-printer totem-common
7671 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7672 &lt;/p&gt;&lt;/blockquote&gt;
7673
7674 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7675
7676 &lt;blockquote&gt;&lt;p&gt;
7677 gstreamer0.10-gnomevfs
7678 &lt;/p&gt;&lt;/blockquote&gt;
7679
7680 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7681
7682 &lt;blockquote&gt;&lt;p&gt;
7683 [nothing]
7684 &lt;/p&gt;&lt;/blockquote&gt;
7685
7686 &lt;p&gt;This is for KDE:&lt;/p&gt;
7687
7688 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7689
7690 &lt;blockquote&gt;&lt;p&gt;
7691 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
7692 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7693 ghostscript-x git gnome-audio gnugo granatier gs-common
7694 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7695 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7696 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7697 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7698 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7699 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7700 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7701 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7702 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7703 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7704 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7705 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
7706 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7707 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7708 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7709 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7710 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7711 libkrossui4 libmailtools-perl libmime-tools-perl
7712 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7713 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7714 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7715 lirc luatex marble networkstatus noatun-plugins
7716 openoffice.org-writer2latex palapeli palapeli-data parley
7717 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7718 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7719 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7720 ttf-sazanami-gothic
7721 &lt;/p&gt;&lt;/blockquote&gt;
7722
7723 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7724
7725 &lt;blockquote&gt;&lt;p&gt;
7726 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7727 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7728 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7729 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7730 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7731 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7732 kitchensync kiten kjumpingcube klatin klettres klickety klines
7733 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7734 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7735 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7736 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7737 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7738 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7739 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7740 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7741 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7742 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
7743 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
7744 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7745 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
7746 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
7747 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7748 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7749 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7750 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7751 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7752 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7753 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
7754 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
7755 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7756 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7757 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7758 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7759 &lt;/p&gt;&lt;/blockquote&gt;
7760
7761 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7762
7763 &lt;blockquote&gt;&lt;p&gt;
7764 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7765 kdeartwork kdebase kdebase-apps kdebase-workspace
7766 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7767 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7768 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7769 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7770 xscreensaver-screensaver-bsod
7771 &lt;/p&gt;&lt;/blockquote&gt;
7772
7773 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7774
7775 &lt;blockquote&gt;&lt;p&gt;
7776 kdebase-bin konq-plugins konqueror
7777 &lt;/p&gt;&lt;/blockquote&gt;
7778 </description>
7779 </item>
7780
7781 <item>
7782 <title>Gnash buildbot slave and Debian kfreebsd</title>
7783 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
7784 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
7785 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
7786 <description>&lt;p&gt;Answering
7787 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
7788 call from the Gnash project&lt;/a&gt; for
7789 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
7790 current source, I have set up a virtual KVM machine on the Debian
7791 Edu/Skolelinux virtualization host to test the git source on
7792 Debian/Squeeze. I hope this can help the developers in getting new
7793 releases out more often.&lt;/p&gt;
7794
7795 &lt;p&gt;As the developers want less main-stream build platforms tested to,
7796 I have considered setting up a &lt;a
7797 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
7798 machine as well. I have also considered using the kfreebsd
7799 architecture in Debian as a file server in NUUG to get access to the 5
7800 TB zfs volume we currently use to store DV video. Because of this, I
7801 finally got around to do a test installation of Debian/Squeeze with
7802 kfreebsd. Installation went fairly smooth, thought I noticed some
7803 visual glitches in the cdebconf dialogs (black cursor left on the
7804 screen at random locations). Have not gotten very far with the
7805 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7806 fatal problem. Have to spend some more time on it to see if it is
7807 useful as a file server for NUUG. Will try to find time to set up a
7808 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
7809 </description>
7810 </item>
7811
7812 <item>
7813 <title>Debian in 3D</title>
7814 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
7815 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
7816 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
7817 <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;
7818
7819 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
7820 3D linked in from
7821 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
7822 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
7823 </description>
7824 </item>
7825
7826 <item>
7827 <title>Software updates 2010-10-24</title>
7828 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
7829 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
7830 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
7831 <description>&lt;p&gt;Some updates.&lt;/p&gt;
7832
7833 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
7834 raise money for the project is going well. The lower limit of 10
7835 signers was reached in 24 hours, and so far 13 people have signed it.
7836 More signers and more funding is most welcome, and I am really curious
7837 how far we can get before the time limit of December 24 is reached.
7838 :)&lt;/p&gt;
7839
7840 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
7841 about what appear to be a great code coverage tool capable of
7842 generating code coverage stats without any changes to the source code.
7843 It is called
7844 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
7845 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
7846 It is missing in Debian, but the git source built just fine in Squeeze
7847 after I installed libelf-dev, libdwarf-dev, pkg-config and
7848 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7849 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
7850
7851 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
7852 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
7853 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
7854 alpha test release of the Squeeze based Debian Edu /
7855 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
7856 release. Give it a try if you need a complete linux solution for your
7857 school, including central infrastructure server, workstations, thin
7858 client servers and diskless workstations. A nice touch added
7859 yesterday is RDP support on the thin client servers, for windows
7860 clients to get a Linux desktop on request.&lt;/p&gt;
7861 </description>
7862 </item>
7863
7864 <item>
7865 <title>Some notes on Flash in Debian and Debian Edu</title>
7866 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
7867 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
7868 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
7869 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
7870 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
7871 second most popular used package that is missing in Debian. The sixth
7872 most popular is flashplayer-mozilla. This is a clear indication that
7873 working flash is important for Debian users. Around 10 percent of the
7874 users submitting data to popcon.debian.org have this package
7875 installed.&lt;/p&gt;
7876
7877 &lt;p&gt;In the report written by Lars Risan in August 2008
7878&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
7879 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7880 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
7881 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
7882 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
7883 web sites require Flash to work, and lacking working Flash support in
7884 the web browser and the problems with installing it was perceived as a
7885 good reason to stay with Windows.&lt;/p&gt;
7886
7887 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
7888 said to be the retarded cousin that did not really understand
7889 everything you told him but could work fairly well. This was a
7890 comment regarding the problems Linux have with proprietary formats and
7891 non-standard web pages, and is sad because it exposes a fairly common
7892 understanding of whose fault it is if web pages that only work in for
7893 example Internet Explorer 6 fail to work on Firefox, and funny because
7894 it explain very well how annoying it is for users when Linux
7895 distributions do not work with the documents they receive or the web
7896 pages they want to visit.&lt;/p&gt;
7897
7898 &lt;p&gt;This is part of the reason why I believe it is important for Debian
7899 and Debian Edu to have a well working Flash implementation in the
7900 distribution, to get at least popular sites as Youtube and Google
7901 Video to working out of the box. For Squeeze, Debian have the chance
7902 to include the latest version of Gnash that will make this happen, as
7903 the new release 0.8.8 was published a few weeks ago and is resting in
7904 unstable. The new version work with more sites that version 0.8.7.
7905 The Gnash maintainers have asked for a freeze exception, but the
7906 release team have not had time to reply to it yet. I hope they agree
7907 with me that Flash is important for the Debian desktop users, and thus
7908 accept the new package into Squeeze.&lt;/p&gt;
7909 </description>
7910 </item>
7911
7912 <item>
7913 <title>Circular package dependencies harms apt recovery</title>
7914 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
7915 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
7916 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
7917 <description>&lt;p&gt;I discovered this while doing
7918 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
7919 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
7920 in Debian still got circular dependencies, and it is often claimed
7921 that apt and aptitude should be able to handle this just fine, but
7922 some times these dependency loops causes apt to fail.&lt;/p&gt;
7923
7924 &lt;p&gt;An example is from todays
7925 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
7926 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
7927 causes perl-modules to fail to upgrade. The cause is simple. If a
7928 package fail to unpack, then only part of packages with the circular
7929 dependency might end up being unpacked when unpacking aborts, and the
7930 ones already unpacked will fail to configure in the recovery phase
7931 because its dependencies are unavailable.&lt;/p&gt;
7932
7933 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
7934
7935 &lt;blockquote&gt;&lt;pre&gt;
7936 dpkg: dependency problems prevent configuration of perl-modules:
7937 perl-modules depends on perl (&gt;= 5.10.1-1); however:
7938 Version of perl on system is 5.10.0-19lenny2.
7939 dpkg: error processing perl-modules (--configure):
7940 dependency problems - leaving unconfigured
7941 &lt;/pre&gt;&lt;/blockquote&gt;
7942
7943 &lt;p&gt;The perl/perl-modules circular dependency is already
7944 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
7945 hopefully be solved as soon as possible, but it is not the only one,
7946 and each one of these loops in the dependency tree can cause similar
7947 failures. Of course, they only occur when there are bugs in other
7948 packages causing the unpacking to fail, but it is rather nasty when
7949 the failure of one package causes the problem to become worse because
7950 of dependency loops.&lt;/p&gt;
7951
7952 &lt;p&gt;Thanks to
7953 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
7954 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
7955 dependencies
7956 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
7957 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
7958
7959 &lt;p&gt;Todays testing also exposed a bug in
7960 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
7961 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
7962 apt-get and aptitude, the latter possibly caused by some circular
7963 dependency. Reported both to BTS to try to get someone to look at
7964 it.&lt;/p&gt;
7965 </description>
7966 </item>
7967
7968 <item>
7969 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
7970 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
7971 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
7972 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
7973 <description>&lt;p&gt;This is a
7974 &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;
7975 on my
7976 &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
7977 work&lt;/a&gt; on
7978 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
7979 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
7980
7981 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
7982 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7983 and dhcp3-server-ldap in Debian use the LDAP server. The two
7984 implementations are quite different in how they use LDAP.&lt;/p&gt;
7985
7986 To get this information, I started slapd with debugging enabled and
7987 dumped the debug output to a file to get the LDAP searches performed
7988 on a Debian Edu main-server. Here is a summary.
7989
7990 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
7991
7992 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
7993 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
7994 the web.
7995
7996 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
7997 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
7998 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
7999 reverse entries are in two different subtrees in LDAP with a structure
8000 based on the DNS names, as in tjener.intern and
8001 2.2.0.10.in-addr.arpa.&lt;/p&gt;
8002
8003 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
8004 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
8005 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
8006 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
8007 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
8008 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
8009 forward entries, it is looking for attributes named dnsttl, arecord,
8010 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8011 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8012 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8013 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8014 spfrecord and modifytimestamp. For reverse entries it is looking for
8015 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8016 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8017 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8018 ldapsearch commands could look like this:&lt;/p&gt;
8019
8020 &lt;blockquote&gt;&lt;pre&gt;
8021 ldapsearch -h ldap \
8022 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8023 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8024 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8025 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8026 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8027 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8028
8029 ldapsearch -h ldap \
8030 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8031 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
8032 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8033 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8034 srvrecord naptrrecord modifytimestamp
8035 &lt;/pre&gt;&lt;/blockquote&gt;
8036
8037 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
8038 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8039 example LDAP objects used there. In addition to these objects, the
8040 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8041 also exist.&lt;/p&gt;
8042
8043 &lt;blockquote&gt;&lt;pre&gt;
8044 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8045 objectclass: top
8046 objectclass: dnsdomain
8047 objectclass: domainrelatedobject
8048 dc: tjener
8049 arecord: 10.0.2.2
8050 associateddomain: tjener.intern
8051
8052 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8053 objectclass: top
8054 objectclass: dnsdomain2
8055 objectclass: domainrelatedobject
8056 dc: 2
8057 ptrrecord: tjener.intern
8058 associateddomain: 2.2.0.10.in-addr.arpa
8059 &lt;/pre&gt;&lt;/blockquote&gt;
8060
8061 &lt;p&gt;In strict mode, the server behaves differently. When looking for
8062 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
8063 same base as in the tree mode for a object with filter
8064 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
8065 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8066 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8067 naptrrecord and modifytimestamp. For reverse entires it also do a
8068 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
8069 and the requested attributes are associateddomain, dnsttl and
8070 modifytimestamp. In short, in strict mode the objects with ptrrecord
8071 go away, and the arecord attribute in the forward object is used
8072 instead.&lt;/p&gt;
8073
8074 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
8075 like this:&lt;/p&gt;
8076
8077 &lt;blockquote&gt;&lt;pre&gt;
8078 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8079 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8080 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8081 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8082 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8083 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8084
8085 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8086 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
8087 &lt;/pre&gt;&lt;/blockquote&gt;
8088
8089 &lt;p&gt;In addition to the forward and reverse searches , there is also a
8090 search for SOA records, which behave similar to the forward and
8091 reverse lookups.&lt;/p&gt;
8092
8093 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
8094 specify any objectclass names, and instead look for the attributes it
8095 need to generate a DNS reply. This make it able to work with any
8096 objectclass that provide the needed attributes.&lt;/p&gt;
8097
8098 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
8099 dnsdomain2 schemas. The latter is used for reverse entries like
8100 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
8101
8102 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
8103 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8104 attributes) and domainrelatedobject (for associatedDomain). The use
8105 of structural object classes make it impossible to combine these
8106 classes with the object classes used by DHCP.&lt;/p&gt;
8107
8108 &lt;p&gt;There are other schemas that could be used too, for example the
8109 dnszone structural object class used by Gosa and bind-sdb for the DNS
8110 attributes combined with the domainrelatedobject object class, but in
8111 this case some unused attributes would have to be included as well
8112 (zonename and relativedomainname).&lt;/p&gt;
8113
8114 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
8115 mode and not use any of the existing objectclasses (dnsdomain,
8116 dnsdomain2 and dnszone) when one want to combine the DNS information
8117 with DHCP information, and instead create a auxiliary object class
8118 defined something like this (using the attributes defined for
8119 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
8120
8121 &lt;blockquote&gt;&lt;pre&gt;
8122 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
8123 SUP top
8124 AUXILIARY
8125 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8126 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8127 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8128 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8129 A6Record $ DNAMERecord
8130 ))
8131 &lt;/pre&gt;&lt;/blockquote&gt;
8132
8133 &lt;p&gt;This will allow any object to become a DNS entry when combined with
8134 the domainrelatedobject object class, and allow any entity to include
8135 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
8136 developers asking for their view on this schema and if they are
8137 interested in providing such schema with PowerDNS, and I hope my
8138 message will be accepted into their mailing list soon.&lt;/p&gt;
8139
8140 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
8141
8142 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
8143 the object attributes, and then uses the attributes it want. This
8144 make it harder to figure out exactly what attributes are used, but
8145 thanks to the working example in Debian Edu I can at least get an idea
8146 what is needed without having to read the source code.&lt;/p&gt;
8147
8148 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
8149 search filter to use to locate the correct dhcpServer entity is
8150 stored. These are the relevant entries from
8151 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
8152
8153 &lt;blockquote&gt;&lt;pre&gt;
8154 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
8155 ldap-dhcp-server-cn &quot;dhcp&quot;;
8156 &lt;/pre&gt;&lt;/blockquote&gt;
8157
8158 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
8159 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
8160 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
8161 search result is this entry:&lt;/p&gt;
8162
8163 &lt;blockquote&gt;&lt;pre&gt;
8164 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8165 cn: dhcp
8166 objectClass: top
8167 objectClass: dhcpServer
8168 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8169 &lt;/pre&gt;&lt;/blockquote&gt;
8170
8171 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
8172 subtree with DHCP configuration. The DHCP configuration subtree base
8173 is located using a base scope search with base &quot;cn=DHCP
8174 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
8175 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
8176 The search result is this entry:&lt;/p&gt;
8177
8178 &lt;blockquote&gt;&lt;pre&gt;
8179 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8180 cn: DHCP Config
8181 objectClass: top
8182 objectClass: dhcpService
8183 objectClass: dhcpOptions
8184 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8185 dhcpStatements: ddns-update-style none
8186 dhcpStatements: authoritative
8187 dhcpOption: smtp-server code 69 = array of ip-address
8188 dhcpOption: www-server code 72 = array of ip-address
8189 dhcpOption: wpad-url code 252 = text
8190 &lt;/pre&gt;&lt;/blockquote&gt;
8191
8192 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
8193 all the DHCP configuration is loaded, it is ready to receive requests.
8194 The subtree in Debian Edu contain objects with object classes
8195 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8196 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8197 and information about netmasks, dynamic range etc. Leaving out the
8198 details here because it is not relevant for the focus of my
8199 investigation, which is to see if it is possible to merge dns and dhcp
8200 related computer objects.&lt;/p&gt;
8201
8202 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
8203 of the client (00:00:00:00:00:00 in this example), using a subtree
8204 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
8205 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8206 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
8207 like:&lt;/p&gt;
8208
8209 &lt;blockquote&gt;&lt;pre&gt;
8210 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8211 cn: hostname
8212 objectClass: top
8213 objectClass: dhcpHost
8214 dhcpHWAddress: ethernet 00:00:00:00:00:00
8215 dhcpStatements: fixed-address hostname
8216 &lt;/pre&gt;&lt;/blockquote&gt;
8217
8218 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
8219 The object classes need to have fixed names, and the configuration
8220 need to be stored in a fairly specific LDAP structure. On the
8221 positive side, the invidiual dhcpHost entires can be anywhere without
8222 the DN pointed to by the dhcpServer entries. The latter should make
8223 it possible to group all host entries in a subtree next to the
8224 configuration entries, and this subtree can also be shared with the
8225 DNS server if the schema proposed above is combined with the dhcpHost
8226 structural object class.
8227
8228 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
8229
8230 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
8231 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
8232 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
8233 allowing DNS objects to be stored anywhere under the base cn specified
8234 in the configuration.&lt;/p&gt;
8235
8236 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
8237 regarding which LDAP schemas to use and which LDAP structure to use.
8238 I guess one could implement ones own schema, as long as the
8239 objectclasses and attributes have the names used, but this do not
8240 really help when the DHCP subtree need to have a fairly fixed
8241 structure.&lt;/p&gt;
8242
8243 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
8244 this might work for Debian Edu:&lt;/p&gt;
8245
8246 &lt;blockquote&gt;&lt;pre&gt;
8247 ou=services
8248 cn=machine-info (dhcpService) - dhcpServiceDN points here
8249 cn=dhcp (dhcpServer)
8250 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8251 cn=10.0.2.0 (dhcpSubnet)
8252 cn=group1 (dhcpGroup/dhcpOptions)
8253 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8254 cn=192.168.0.0 (dhcpSubnet)
8255 cn=group1 (dhcpGroup/dhcpOptions)
8256 ou=machines - PowerDNS base points here
8257 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8258 &lt;/pre&gt;&lt;/blockquote&gt;
8259
8260 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
8261 entries to be in the dhcpGroup subtrees, the entries can be stored
8262 there instead of a common machines subtree, and the PowerDNS base
8263 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
8264
8265 &lt;p&gt;The combined object under the machines subtree would look something
8266 like this:&lt;/p&gt;
8267
8268 &lt;blockquote&gt;&lt;pre&gt;
8269 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8270 dc: hostname
8271 objectClass: top
8272 objectClass: dhcpHost
8273 objectclass: domainrelatedobject
8274 objectclass: dnsDomainAux
8275 associateddomain: hostname.intern
8276 arecord: 10.11.12.13
8277 dhcpHWAddress: ethernet 00:00:00:00:00:00
8278 dhcpStatements: fixed-address hostname.intern
8279 &lt;/pre&gt;&lt;/blockquote&gt;
8280
8281 &lt;/p&gt;One could even add the LTSP configuration associated with a given
8282 machine, as long as the required attributes are available in a
8283 auxiliary object class.&lt;/p&gt;
8284 </description>
8285 </item>
8286
8287 <item>
8288 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
8289 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
8290 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
8291 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
8292 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
8293 DHCP services in Debian Edu to use the same LDAP objects for a given
8294 computer, to avoid the possibility of having a inconsistent state for
8295 a computer in LDAP (as in DHCP but no DNS entry or the other way
8296 around) and make it easier to add computers to LDAP.&lt;/p&gt;
8297
8298 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
8299 information finally found a solution that seem to work.&lt;/p&gt;
8300
8301 &lt;p&gt;The old setup required three LDAP objects for a given computer.
8302 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8303 we switch powerdns to use its strict LDAP method (ldap-method=strict
8304 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8305 merged into one while making it impossible to transfer the reverse map
8306 to a slave DNS server.&lt;/p&gt;
8307
8308 &lt;p&gt;If we also replace the object class used to get the DNS related
8309 attributes to one allowing these attributes to be combined with the
8310 dhcphost object class, we can merge the DNS and DHCP entries into one.
8311 I&#39;ve written such object class in the dnsdomainaux.schema file (need
8312 proper OIDs, but that is a minor issue), and tested the setup. It
8313 seem to work.&lt;/p&gt;
8314
8315 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
8316 for both DNS and DHCP, and even the LTSP configuration I suggested in
8317 an earlier email. The combined LDAP object will look something like
8318 this:&lt;/p&gt;
8319
8320 &lt;blockquote&gt;&lt;pre&gt;
8321 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8322 cn: hostname
8323 objectClass: dhcphost
8324 objectclass: domainrelatedobject
8325 objectclass: dnsdomainaux
8326 associateddomain: hostname.intern
8327 arecord: 10.11.12.13
8328 dhcphwaddress: ethernet 00:00:00:00:00:00
8329 dhcpstatements: fixed-address hostname
8330 ldapconfigsound: Y
8331 &lt;/pre&gt;&lt;/blockquote&gt;
8332
8333 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
8334 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8335 before asking DNS to resolve the fixed-adddress. LTSP will use
8336 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
8337
8338 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
8339 dhcphost in a different location, to allow us to put the objects
8340 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
8341 that. If I can&#39;t figure out a way to do that, we can still get rid of
8342 the hosts subtree and move all its content into the DHCP Config tree
8343 (which probably should be renamed to be more related to the new
8344 content. I suspect cn=dnsdhcp,ou=services or something like that
8345 might be a good place to put it.&lt;/p&gt;
8346
8347 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8348 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8349 </description>
8350 </item>
8351
8352 <item>
8353 <title>Idea for storing LTSP configuration in LDAP</title>
8354 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
8355 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
8356 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
8357 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
8358 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8359 clients, and that this can be used to fetch configuration from LDAP if
8360 Debian Edu choose to store configuration there.&lt;/p&gt;
8361
8362 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
8363 to get configuration from LDAP. The idea is to look up the MAC
8364 address of the client in LDAP, and look for attributes on the form
8365 ltspconfigsetting=value, and use this to export SETTING=value to the
8366 LTSP clients.&lt;/p&gt;
8367
8368 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
8369 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
8370 allowing us to store all information about a computer in one place.&lt;/p&gt;
8371
8372 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
8373 this approach. A real LDAP schema for the ltspClientAux objectclass
8374 need to be written. Comments, suggestions, etc?&lt;/p&gt;
8375
8376 &lt;blockquote&gt;&lt;pre&gt;
8377 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8378 #
8379 # Fetch LTSP client settings from LDAP based on MAC address
8380 #
8381 # Uses ethernet address as stored in the dhcpHost objectclass using
8382 # the dhcpHWAddress attribute or ethernet address stored in the
8383 # ieee802Device objectclass with the macAddress attribute.
8384 #
8385 # This module is written to be schema agnostic, and only depend on the
8386 # existence of attribute names.
8387 #
8388 # The LTSP configuration variables are saved directly using a
8389 # ltspConfig prefix and uppercasing the rest of the attribute name.
8390 # To set the SERVER variable, set the ltspConfigServer attribute.
8391 #
8392 # Some LDAP schema should be created with all the relevant
8393 # configuration settings. Something like this should work:
8394 #
8395 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
8396 # SUP top
8397 # AUXILIARY
8398 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8399
8400 LDAPSERVER=$(debian-edu-ldapserver)
8401 if [ &quot;$LDAPSERVER&quot; ] ; then
8402 LDAPBASE=$(debian-edu-ldapserver -b)
8403 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
8404 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
8405 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
8406 grep &#39;^ltspConfig&#39; | while read attr value ; do
8407 # Remove prefix and convert to upper case
8408 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
8409 # bass value on to clients
8410 eval &quot;$attr=$value; export $attr&quot;
8411 done
8412 done
8413 fi
8414 &lt;/pre&gt;&lt;/blockquote&gt;
8415
8416 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
8417 the while block might end up in a subshell causing the variables set
8418 there to not show up in ltsp-config, but if that is the case I am sure
8419 the code can be restructured to make sure the variables are passed on.
8420 I expect that can be solved with some testing. :)&lt;/p&gt;
8421
8422 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8423 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8424
8425 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
8426 configuration in LDAP that was created around year 2000 by
8427 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
8428 Xperience, Inc., 2000&lt;/a&gt;. I found its
8429 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
8430 personal home page over at redhat.com.&lt;/p&gt;
8431 </description>
8432 </item>
8433
8434 <item>
8435 <title>jXplorer, a very nice LDAP GUI</title>
8436 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
8437 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
8438 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
8439 <description>&lt;p&gt;Since
8440 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
8441 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
8442 LDAP GUI that is even better than luma. The java application
8443 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
8444 moving LDAP objects and subtrees using drag-and-drop, and can
8445 authenticate using Kerberos. I have only tested the Kerberos
8446 authentication, but do not have a LDAP setup allowing me to rewrite
8447 LDAP with my test user yet. It is
8448 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
8449 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
8450 have with it is how it handle errors. If something go wrong, its
8451 non-intuitive behaviour require me to go through some query work list
8452 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
8453 </description>
8454 </item>
8455
8456 <item>
8457 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
8458 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
8459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
8460 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
8461 <description>&lt;p&gt;Here is a short update on my &lt;a
8462 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
8463 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
8464 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
8465 not reporting the status for KDE, because the upgrade crashes when
8466 aptitude try because of missing conflicts
8467 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
8468 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
8469
8470 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
8471 complete list of the installed packages. Based on this I see these
8472 differences when I did a test run today. As usual, I do not really
8473 know what the correct set of packages would be, but thought it best to
8474 publish the difference.&lt;/p&gt;
8475
8476 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8477
8478 &lt;blockquote&gt;&lt;p&gt;
8479 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
8480 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
8481 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8482 libgtksourceview-common libpt-1.10.10-plugins-alsa
8483 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8484 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8485 python-4suite-xml python-eggtrayicon python-gtkhtml2
8486 python-gtkmozembed svgalibg1 xserver-xephyr zip
8487 &lt;/p&gt;&lt;/blockquote&gt;
8488
8489 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8490
8491 &lt;blockquote&gt;&lt;p&gt;
8492 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8493 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8494 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
8495 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
8496 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
8497 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
8498 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8499 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8500 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8501 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
8502 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
8503 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
8504 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8505 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
8506 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8507 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
8508 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
8509 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8510 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8511 mysql-common swfdec-gnome totem-gstreamer wodim
8512 &lt;/p&gt;&lt;/blockquote&gt;
8513
8514 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8515
8516 &lt;blockquote&gt;&lt;p&gt;
8517 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8518 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8519 xserver-xorg-input-all xserver-xorg-input-evdev
8520 xserver-xorg-input-kbd xserver-xorg-input-mouse
8521 xserver-xorg-input-synaptics xserver-xorg-video-all
8522 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8523 xserver-xorg-video-chips xserver-xorg-video-cirrus
8524 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8525 xserver-xorg-video-glint xserver-xorg-video-i128
8526 xserver-xorg-video-i740 xserver-xorg-video-mach64
8527 xserver-xorg-video-mga xserver-xorg-video-neomagic
8528 xserver-xorg-video-nouveau xserver-xorg-video-nv
8529 xserver-xorg-video-r128 xserver-xorg-video-radeon
8530 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8531 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8532 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8533 xserver-xorg-video-sis xserver-xorg-video-sisusb
8534 xserver-xorg-video-tdfx xserver-xorg-video-tga
8535 xserver-xorg-video-trident xserver-xorg-video-tseng
8536 xserver-xorg-video-vesa xserver-xorg-video-vmware
8537 xserver-xorg-video-voodoo
8538 &lt;/p&gt;&lt;/blockquote&gt;
8539
8540 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8541
8542 &lt;blockquote&gt;&lt;p&gt;
8543 deskbar-applet xserver-xorg xserver-xorg-core
8544 xserver-xorg-input-wacom xserver-xorg-video-intel
8545 xserver-xorg-video-openchrome
8546 &lt;/p&gt;&lt;/blockquote&gt;
8547
8548 &lt;p&gt;I was told on IRC that the xorg-xserver package was
8549 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
8550 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
8551 No idea when it hits Squeeze, but when it does I hope it will reduce
8552 the difference somewhat.
8553 </description>
8554 </item>
8555
8556 <item>
8557 <title>LUMA, a very nice LDAP GUI</title>
8558 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
8559 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
8560 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
8561 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
8562 directory in Debian Edu, and in the process I started to miss a GUI
8563 tool to browse the LDAP tree. The only one I was able to find in
8564 Debian/Squeeze and Lenny is
8565 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
8566 be a great tool to get a overview of the current LDAP directory
8567 populated by default in Skolelinux. Thanks to it, I have been able to
8568 find empty and obsolete subtrees, misplaced objects and duplicate
8569 objects. It will be installed by default in Debian/Squeeze. If you
8570 are working with LDAP, give it a go. :)&lt;/p&gt;
8571
8572 &lt;p&gt;I did notice one problem with it I have not had time to report to
8573 the BTS yet. There is no .desktop file in the package, so the tool do
8574 not show up in the Gnome and KDE menus, but only deep down in in the
8575 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8576 released.&lt;/p&gt;
8577
8578 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
8579 like to move objects and remove subtrees directly in the GUI, but have
8580 not found a way to do that with LUMA yet. So in the mean time, I use
8581 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
8582
8583 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
8584 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8585
8586 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
8587 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
8588 useful GUI alternative. It seem like a good tool, but is unmaintained
8589 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8590 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
8591 </description>
8592 </item>
8593
8594 <item>
8595 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
8596 <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>
8597 <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>
8598 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
8599 <description>&lt;p&gt;A while back, I
8600 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
8601 about the fact&lt;/a&gt; that it is not possible with the provided schemas
8602 for storing DNS and DHCP information in LDAP to combine the two sets
8603 of information into one LDAP object representing a computer.&lt;/p&gt;
8604
8605 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
8606 the dhcpHost object class auxiliary, to allow it to be combined with
8607 the dNSDomain object class, and thus forming one object for one
8608 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
8609
8610 &lt;p&gt;If I understand this correctly, it is not safe to do this change
8611 without also changing the assigned number for the object class, and I
8612 do not know enough about LDAP schema design to do that properly for
8613 Debian Edu.&lt;/p&gt;
8614
8615 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
8616 the
8617 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
8618 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
8619 available today from IETF.&lt;/p&gt;
8620
8621 &lt;pre&gt;
8622 --- dhcp.schema (revision 65192)
8623 +++ dhcp.schema (working copy)
8624 @@ -376,7 +376,7 @@
8625 objectclass ( 2.16.840.1.113719.1.203.6.6
8626 NAME &#39;dhcpHost&#39;
8627 DESC &#39;This represents information about a particular client&#39;
8628 - SUP top
8629 + SUP top AUXILIARY
8630 MUST cn
8631 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8632 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
8633 &lt;/pre&gt;
8634
8635 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
8636 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8637 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
8638
8639 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8640 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8641 </description>
8642 </item>
8643
8644 <item>
8645 <title>Calling tasksel like the installer, while still getting useful output</title>
8646 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
8647 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
8648 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
8649 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
8650 installs packages during the normal debian-installer run. Until now,
8651 I have ended up letting tasksel do the work, with the annoying problem
8652 of not getting any feedback at all when something fails (like a
8653 conffile question from dpkg or a download that fails), using code like
8654 this:
8655
8656 &lt;blockquote&gt;&lt;pre&gt;
8657 export DEBIAN_FRONTEND=noninteractive
8658 tasksel --new-install
8659 &lt;/pre&gt;&lt;/blockquote&gt;
8660
8661 This would invoke tasksel, let its automatic task selection pick the
8662 tasks to install, and continue to install the requested tasks without
8663 any output what so ever.
8664
8665 Recently I revisited this problem while working on the automatic
8666 package upgrade testing, because tasksel would some times hang without
8667 any useful feedback, and I want to see what is going on when it
8668 happen. Then it occured to me, I can parse the output from tasksel
8669 when asked to run in test mode, and use that aptitude command line
8670 printed by tasksel then to simulate the tasksel run. I ended up using
8671 code like this:
8672
8673 &lt;blockquote&gt;&lt;pre&gt;
8674 export DEBIAN_FRONTEND=noninteractive
8675 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
8676 $cmd
8677 &lt;/pre&gt;&lt;/blockquote&gt;
8678
8679 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
8680 --without-recommends -o APT::Install-Recommends=no -y install
8681 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8682 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
8683 laptop task and all packages with priority standard , required and
8684 important, just like tasksel would have done it during
8685 installation.&lt;/p&gt;
8686
8687 &lt;p&gt;A better approach is probably to extend tasksel to be able to
8688 install packages without using debconf-apt-progress, for use cases
8689 like this.&lt;/p&gt;
8690 </description>
8691 </item>
8692
8693 <item>
8694 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
8695 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
8696 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
8697 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
8698 <description>&lt;p&gt;My
8699 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
8700 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
8701 finally made the upgrade logs available from
8702 &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;.
8703 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8704 apt and aptitude, and found their differences interesting. This time
8705 I will only focus on their removal plans.&lt;/p&gt;
8706
8707 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
8708 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
8709 surprising part is that it want to remove xorg and all
8710 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8711 sure why. When asking aptitude to do the same, it want to remove 129
8712 packages, but most of them are library packages I suspect are no
8713 longer needed. Both of them want to remove bluetooth packages, which
8714 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
8715
8716 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
8717 which seem like a bad idea and xorg the same way as with Gnome. Asking
8718 aptitude for the same, it wants to remove 192 packages, none which are
8719 too surprising.&lt;/p&gt;
8720
8721 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
8722 and avoided, and perhaps others as well. Here are the complete list
8723 of planned removals. The complete logs is available from the URL
8724 above. Note if you want to repeat these tests, that the upgrade test
8725 for kde+apt-get hung in the tasksel setup because of dpkg asking
8726 conffile questions. No idea why. I worked around it by using
8727 &#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
8728 continue.&lt;/p&gt;
8729
8730 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
8731 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
8732 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8733 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
8734 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8735 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8736 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8737 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8738 xserver-xorg-input-kbd xserver-xorg-input-mouse
8739 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8740 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8741 xserver-xorg-video-ati xserver-xorg-video-chips
8742 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8743 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8744 xserver-xorg-video-glint xserver-xorg-video-i128
8745 xserver-xorg-video-i740 xserver-xorg-video-imstt
8746 xserver-xorg-video-intel xserver-xorg-video-mach64
8747 xserver-xorg-video-mga xserver-xorg-video-neomagic
8748 xserver-xorg-video-nsc xserver-xorg-video-nv
8749 xserver-xorg-video-openchrome xserver-xorg-video-r128
8750 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8751 xserver-xorg-video-rendition xserver-xorg-video-s3
8752 xserver-xorg-video-s3virge xserver-xorg-video-savage
8753 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8754 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8755 xserver-xorg-video-tga xserver-xorg-video-trident
8756 xserver-xorg-video-tseng xserver-xorg-video-v4l
8757 xserver-xorg-video-vesa xserver-xorg-video-vga
8758 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
8759 xulrunner-1.9-gnome-support&lt;/p&gt;
8760
8761 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
8762
8763 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
8764 djvulibre-desktop finger gnome-app-install gnome-mount
8765 gnome-network-admin gnome-spell gnome-vfs-obexftp
8766 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8767 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8768 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8769 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
8770 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
8771 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
8772 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
8773 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
8774 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
8775 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
8776 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
8777 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
8778 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8779 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
8780 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
8781 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
8782 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
8783 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
8784 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8785 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8786 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8787 openoffice.org-writer2latex openssl-blacklist p7zip
8788 python-4suite-xml python-eggtrayicon python-gnome2-desktop
8789 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8790 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8791 swfdec-mozilla totem-gstreamer update-manager wodim
8792 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8793 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8794 zip&lt;/p&gt;
8795
8796 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
8797
8798 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8799 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8800 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8801 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8802 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8803 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8804 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8805 xserver-xorg-input-kbd xserver-xorg-input-mouse
8806 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8807 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8808 xserver-xorg-video-ati xserver-xorg-video-chips
8809 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8810 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8811 xserver-xorg-video-glint xserver-xorg-video-i128
8812 xserver-xorg-video-i740 xserver-xorg-video-imstt
8813 xserver-xorg-video-intel xserver-xorg-video-mach64
8814 xserver-xorg-video-mga xserver-xorg-video-neomagic
8815 xserver-xorg-video-nsc xserver-xorg-video-nv
8816 xserver-xorg-video-openchrome xserver-xorg-video-r128
8817 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8818 xserver-xorg-video-rendition xserver-xorg-video-s3
8819 xserver-xorg-video-s3virge xserver-xorg-video-savage
8820 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8821 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8822 xserver-xorg-video-tga xserver-xorg-video-trident
8823 xserver-xorg-video-tseng xserver-xorg-video-v4l
8824 xserver-xorg-video-vesa xserver-xorg-video-vga
8825 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
8826
8827 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
8828 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
8829 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8830 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8831 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8832 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8833 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8834 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8835 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8836 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8837 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8838 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8839 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8840 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8841 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8842 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8843 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8844 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8845 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8846 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
8847 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8848 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8849 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
8850 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8851 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8852 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8853 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8854 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8855 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
8856 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
8857 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8858 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8859 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8860 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8861 texlive-common texlive-doc-base texlive-fonts-recommended
8862 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8863 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8864 xulrunner-1.9&lt;/p&gt;
8865
8866 </description>
8867 </item>
8868
8869 <item>
8870 <title>Automatic upgrade testing from Lenny to Squeeze</title>
8871 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
8872 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
8873 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
8874 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
8875 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8876 have been discovered and reported in the process
8877 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
8878 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
8879 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
8880 kdebase-workspace-data), and to get a more regular testing going on, I
8881 am working on a script to automate the test.&lt;/p&gt;
8882
8883 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
8884 Gnome or KDE desktop installation inside the chroot before upgrading
8885 it. To ensure no services are started in the chroot, a policy-rc.d
8886 script is inserted. To make sure tasksel believe it is to install a
8887 desktop on a laptop, the tasksel tests are replaced in the chroot
8888 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
8889
8890 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8891 currently always fail because udev refuses to upgrade with the kernel
8892 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8893 is created. The bug report
8894 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
8895 this problem do not trigger in a chroot, but I touch the file anyway
8896 to make sure the upgrade go well. Testing on virtual and real
8897 hardware have failed me because of udev so far, and creating this file
8898 do the trick in such settings anyway. This is a
8899 &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
8900 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
8901 maintainer because he lack the resources to rewrite udev to keep
8902 working with old kernels or something like that. I really wish the
8903 udev upstream would keep udev backwards compatible, to avoid such
8904 upgrade problem, but given that they fail to do so, I guess
8905 documenting the way out of this mess is the best option we got for
8906 Debian Squeeze.&lt;/p&gt;
8907
8908 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
8909 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
8910 trick:&lt;/p&gt;
8911
8912 &lt;blockquote&gt;&lt;pre&gt;
8913 #!/bin/sh
8914 set -ex
8915
8916 if [ &quot;$1&quot; ] ; then
8917 desktop=$1
8918 else
8919 desktop=gnome
8920 fi
8921
8922 from=lenny
8923 to=squeeze
8924
8925 exec &amp;lt; /dev/null
8926 unset LANG
8927 mirror=http://ftp.skolelinux.org/debian
8928 tmpdir=chroot-$from-upgrade-$to-$desktop
8929 fuser -mv .
8930 debootstrap $from $tmpdir $mirror
8931 chroot $tmpdir aptitude update
8932 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
8933 #!/bin/sh
8934 exit 101
8935 EOF
8936 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8937 exit_cleanup() {
8938 umount $tmpdir/proc
8939 }
8940 mount -t proc proc $tmpdir/proc
8941 # Make sure proc is unmounted also on failure
8942 trap exit_cleanup EXIT INT
8943
8944 chroot $tmpdir aptitude -y install debconf-utils
8945
8946 # Make sure tasksel autoselection trigger. It need the test scripts
8947 # to return the correct answers.
8948 echo tasksel tasksel/desktop multiselect $desktop | \
8949 chroot $tmpdir debconf-set-selections
8950
8951 # Include the desktop and laptop task
8952 for test in desktop laptop ; do
8953 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
8954 #!/bin/sh
8955 exit 2
8956 EOF
8957 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8958 done
8959
8960 DEBIAN_FRONTEND=noninteractive
8961 DEBIAN_PRIORITY=critical
8962 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8963 chroot $tmpdir tasksel --new-install
8964
8965 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
8966 chroot $tmpdir aptitude update
8967 touch $tmpdir/etc/udev/kernel-upgrade
8968 chroot $tmpdir aptitude -y dist-upgrade
8969 fuser -mv
8970 &lt;/pre&gt;&lt;/blockquote&gt;
8971
8972 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
8973 with aptitude, but I have not had time to look at how they behave
8974 differently so far. I hope to get a cron job running to do the test
8975 regularly and post the result on the web. The Gnome upgrade currently
8976 work, while the KDE upgrade fail because of the bug in
8977 kdebase-workspace-data&lt;/p&gt;
8978
8979 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
8980 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
8981 post, so I will refrain from trying. I can report that for Gnome,
8982 aptitude report 760 packages upgraded, 448 newly installed, 129 to
8983 remove and 1 not upgraded and 1024MB need to be downloaded while for
8984 KDE the same numbers are 702 packages upgraded, 507 newly installed,
8985 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
8986
8987 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
8988 is able to migrate to dependency based boot sequencing and parallel
8989 booting without a hitch. Was unsure if there were still bugs with
8990 packages failing to clean up their obsolete init.d script during
8991 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8992 packages.&lt;/p&gt;
8993 </description>
8994 </item>
8995
8996 <item>
8997 <title>Upstart or sysvinit - as init.d scripts see it</title>
8998 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
8999 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
9000 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
9001 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
9002 scripts to migrate (some of) their operations to upstart job while
9003 keeping the init.d for hurd and kfreebsd. The packages with such
9004 needs will need a way to get their init.d scripts to behave
9005 differently when used with sysvinit and with upstart. Because of
9006 this, I had a look at the environment variables set when a init.d
9007 script is running under upstart, and when it is not.&lt;/p&gt;
9008
9009 &lt;p&gt;With upstart, I notice these environment variables are set when a
9010 script is started from rcS.d/ (ignoring some irrelevant ones like
9011 COLUMNS):&lt;/p&gt;
9012
9013 &lt;blockquote&gt;&lt;pre&gt;
9014 DEFAULT_RUNLEVEL=2
9015 previous=N
9016 PREVLEVEL=
9017 RUNLEVEL=
9018 runlevel=S
9019 UPSTART_EVENTS=startup
9020 UPSTART_INSTANCE=
9021 UPSTART_JOB=rc-sysinit
9022 &lt;/pre&gt;&lt;/blockquote&gt;
9023
9024 &lt;p&gt;With sysvinit, these environment variables are set for the same
9025 script.&lt;/p&gt;
9026
9027 &lt;blockquote&gt;&lt;pre&gt;
9028 INIT_VERSION=sysvinit-2.88
9029 previous=N
9030 PREVLEVEL=N
9031 RUNLEVEL=S
9032 runlevel=S
9033 &lt;/pre&gt;&lt;/blockquote&gt;
9034
9035 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
9036 sysvinit are not set by upstart. Not sure if it is intentional or not
9037 to not be compatible with sysvinit in this regard.&lt;/p&gt;
9038
9039 &lt;p&gt;For scripts needing to behave differently when upstart is used,
9040 looking for the UPSTART_JOB environment variable seem to be a good
9041 choice.&lt;/p&gt;
9042 </description>
9043 </item>
9044
9045 <item>
9046 <title>A manual for standards wars...</title>
9047 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
9048 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
9049 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
9050 <description>&lt;p&gt;Via the
9051 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
9052 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
9053 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
9054 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
9055 following the standards wars of today.&lt;/p&gt;
9056 </description>
9057 </item>
9058
9059 <item>
9060 <title>Sitesummary tip: Listing computer hardware models used at site</title>
9061 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
9062 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
9063 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
9064 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
9065 to get a list of the machine types in use thanks to the DMI
9066 information extracted from each machine. The script to do so is
9067 included in the sitesummary package, and here is example output from
9068 the Skolelinux build servers:&lt;/p&gt;
9069
9070 &lt;blockquote&gt;&lt;pre&gt;
9071 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9072 vendor count
9073 Dell Computer Corporation 1
9074 PowerEdge 1750 1
9075 IBM 1
9076 eserver xSeries 345 -[8670M1X]- 1
9077 Intel 2
9078 [no-dmi-info] 3
9079 maintainer:~#
9080 &lt;/pre&gt;&lt;/blockquote&gt;
9081
9082 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
9083 provided in each machine. Here there are Intel machines without model
9084 information listed with Intel as vendor and no model, and virtual Xen
9085 machines listed as [no-dmi-info]. One can add -l as a command line
9086 option to list the individual machines.&lt;/p&gt;
9087
9088 &lt;p&gt;A larger list is
9089 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
9090 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
9091 provide the basic sitesummary report publicly. In their report there
9092 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
9093 their machines, and as sitesummary is available in both distributions,
9094 it is trivial to get all of them to report to the same central
9095 collector.&lt;/p&gt;
9096 </description>
9097 </item>
9098
9099 <item>
9100 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
9101 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
9102 <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>
9103 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
9104 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
9105 start at boot when an NVidia video card is used is handled. The
9106 problem seem to be that the nvidia X.org driver uses a long time to
9107 initialize, and this duration is longer than kdm is configured to
9108 wait.&lt;/p&gt;
9109
9110 &lt;p&gt;I came across two bugs related to this issue,
9111 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
9112 against initscripts and passed on to nvidia-glx when it became obvious
9113 that the nvidia drivers were involved, and
9114 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
9115 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
9116
9117 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
9118 problem nvidia video card owners experience and make sure the Debian
9119 distribution work out of the box for these users. The nvidia driver
9120 maintainers expect kdm to be set up to wait longer, while kdm expect
9121 the nvidia driver maintainers to fix the driver to start faster, and
9122 while they wait for each other I guess the users end up switching to a
9123 distribution that work for them. I have no idea what the solution is,
9124 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
9125
9126 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
9127 </description>
9128 </item>
9129
9130 <item>
9131 <title>Parallellized boot seem to hold up well in Debian/testing</title>
9132 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
9133 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
9134 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
9135 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
9136 The feature seem to hold up pretty well, but three fairly serious
9137 issues are known and should be solved:
9138
9139 &lt;p&gt;&lt;ul&gt;
9140
9141 &lt;li&gt;The wicd package seen to
9142 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
9143 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
9144 parallel booting is enabled. No idea why, but the wicd maintainer
9145 seem to be on the case.&lt;/li&gt;
9146
9147 &lt;li&gt;The nvidia X driver seem to
9148 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
9149 triggered more easily when parallel booting is in effect. The
9150 maintainer is on the case.&lt;/li&gt;
9151
9152 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
9153 sequencing (the shutdown is broken) when old file-rc users
9154 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
9155 sysv-rc. One way to solve it would be for file-rc to create
9156 /etc/init.d/.legacy-bootordering, and another is to try to make
9157 sysv-rc more robust. Will investigate some more and probably upload a
9158 workaround in sysv-rc to help those trying to move from file-rc to
9159 sysv-rc get a working shutdown.&lt;/li&gt;
9160
9161 &lt;/ul&gt;&lt;/p&gt;
9162
9163 &lt;p&gt;All in all not many surprising issues, and all of them seem
9164 solvable before Squeeze is released. In addition to these there are
9165 some packages with bugs in their dependencies and run level settings,
9166 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
9167
9168 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9169 the BTS, please usertag the report to get it to show up at
9170 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9171 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9172
9173 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
9174 </description>
9175 </item>
9176
9177 <item>
9178 <title>More flexible firmware handling in debian-installer</title>
9179 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
9180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
9181 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
9182 <description>&lt;p&gt;After a long break from debian-installer development, I finally
9183 found time today to return to the project. Having to spend less time
9184 working dependency based boot in debian, as it is almost complete now,
9185 definitely helped freeing some time.&lt;/p&gt;
9186
9187 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
9188 include some firmware packages on the Debian Edu CDs, those needed to
9189 get disk and network controllers working. Without having these
9190 firmware packages available during installation, it is impossible to
9191 install Debian Edu on the given machine, and because our target group
9192 are non-technical people, asking them to provide firmware packages on
9193 an external medium is a support pain. Initially, I expected it to be
9194 enough to include the firmware packages on the CD to get
9195 debian-installer to find and use them. This proved to be wrong.
9196 Next, I hoped it was enough to symlink the relevant firmware packages
9197 to some useful location on the CD (tried /cdrom/ and
9198 /cdrom/firmware/). This also proved to not work, and at this point I
9199 found time to look at the debian-installer code to figure out what was
9200 going to work.&lt;/p&gt;
9201
9202 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
9203 look revealed that it would only look for firmware packages outside
9204 the installation media, so the CD was never checked for firmware
9205 packages. It would only check USB sticks, floppies and other
9206 &quot;external&quot; media devices. Today I changed it to also look in the
9207 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9208 solve the problem I ran into with Debian edu. I also changed it to
9209 look in /firmware/, to make sure the installer also find firmware
9210 provided in the initrd when booting the installer via PXE, to allow us
9211 to provide the same feature in the PXE setup included in Debian
9212 Edu.&lt;/p&gt;
9213
9214 &lt;p&gt;To make sure firmware deb packages with a license questions are not
9215 activated without asking if the license is accepted, I extended
9216 hw-detect to look for preinst scripts in the firmware packages, and
9217 run these before activating the firmware during installation. The
9218 license question is asked using debconf in the preinst, so this should
9219 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
9220
9221 &lt;p&gt;If you want to discuss the details of these features, please
9222 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
9223 </description>
9224 </item>
9225
9226 <item>
9227 <title>Parallellized boot is now the default in Debian/unstable</title>
9228 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
9229 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
9230 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
9231 <description>&lt;p&gt;Since this evening, parallel booting is the default in
9232 Debian/unstable for machines using dependency based boot sequencing.
9233 Apparently the testing of concurrent booting has been wider than
9234 expected, if I am to believe the
9235 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9236 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
9237 with the feature this weekend, to give us some time to detect any
9238 remaining problems before Squeeze is frozen. If serious problems are
9239 detected, it is simple to change the default back to sequential boot.
9240 The upload of the new sysvinit package also activate a new upstream
9241 version.&lt;/p&gt;
9242
9243 More information about
9244 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9245 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
9246 currently possible to disable parallel booting when one run into
9247 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
9248
9249 &lt;blockquote&gt;&lt;pre&gt;
9250 CONCURRENCY=none
9251 &lt;/pre&gt;&lt;/blockquote&gt;
9252
9253 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9254 the BTS, please usertag the report to get it to show up at
9255 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9256 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9257 </description>
9258 </item>
9259
9260 <item>
9261 <title>Sitesummary tip: Listing MAC address of all clients</title>
9262 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
9263 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
9264 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
9265 <description>&lt;p&gt;In the recent Debian Edu versions, the
9266 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
9267 system&lt;/a&gt; is used to keep track of the machines in the school
9268 network. Each machine will automatically report its status to the
9269 central server after boot and once per night. The network setup is
9270 also reported, and using this information it is possible to get the
9271 MAC address of all network interfaces in the machines. This is useful
9272 to update the DHCP configuration.&lt;/p&gt;
9273
9274 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
9275 ist all MAC addresses of all machines reporting to sitesummary. Run
9276 this on the collector host:&lt;/p&gt;
9277
9278 &lt;blockquote&gt;&lt;pre&gt;
9279 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
9280 &lt;/pre&gt;&lt;/blockquote&gt;
9281
9282 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
9283 line per machine and with space between the MAC addresses.&lt;/p&gt;
9284
9285 &lt;p&gt;To allow system administrators easier job at adding static DHCP
9286 addresses for hosts, it would be possible to extend this to fetch
9287 machine information from sitesummary and update the DHCP and DNS
9288 tables in LDAP using this information. Such tool is unfortunately not
9289 written yet.&lt;/p&gt;
9290 </description>
9291 </item>
9292
9293 <item>
9294 <title>systemd, an interesting alternative to upstart</title>
9295 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
9296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
9297 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
9298 <description>&lt;p&gt;The last few days a new boot system called
9299 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
9300 has been
9301 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
9302
9303 to the free software world. I have not yet had time to play around
9304 with it, but it seem to be a very interesting alternative to
9305 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
9306 a good alternative for Debian when we are able to switch to an event
9307 based boot system. Tollef is
9308 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
9309 systemd into Debian, and I look forward to seeing how well it work. I
9310 like the fact that systemd handles init.d scripts with dependency
9311 information natively, allowing them to run in parallel where upstart
9312 at the moment do not.&lt;/p&gt;
9313
9314 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
9315 platform support. It only work on recent Linux kernels, and also need
9316 some new kernel features enabled to function properly. This means
9317 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9318 system. Not sure how that will be handled if systemd proves to be the
9319 way forward.&lt;/p&gt;
9320
9321 &lt;p&gt;In the mean time, based on the
9322 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9323 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
9324 decided to enable full parallel booting as the default in Debian as
9325 soon as possible (probably this weekend or early next week), to see if
9326 there are any remaining serious bugs in the init.d dependencies. A
9327 new version of the sysvinit package implementing this change is
9328 already in experimental. If all go well, Squeeze will be released
9329 with parallel booting enabled by default.&lt;/p&gt;
9330 </description>
9331 </item>
9332
9333 <item>
9334 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
9335 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
9336 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
9337 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
9338 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
9339 complete, so complete that it is actually possible to run all the
9340 init.d scripts in parallell based on these dependencies. If you want
9341 to test your Squeeze system, make sure
9342 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9343 based boot sequencing&lt;/a&gt; is enabled, and add this line to
9344 /etc/default/rcS:&lt;/p&gt;
9345
9346 &lt;blockquote&gt;&lt;pre&gt;
9347 CONCURRENCY=makefile
9348 &lt;/pre&gt;&lt;/blockquote&gt;
9349
9350 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
9351 scripts in parallel using the dependency information stored in
9352 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9353 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9354 to try to start the kdm and gdm scripts as early as possible, and will
9355 start the facilities required by kdm or gdm as early as possible to
9356 make this happen.&lt;/p&gt;
9357
9358 &lt;p&gt;Give it a try, and see if you like the result. If some services
9359 fail to start properly, it is most likely because they have incomplete
9360 init.d script dependencies in their startup script (or some of their
9361 dependent scripts have incomplete dependencies). Report bugs and get
9362 the package maintainers to fix it. :)&lt;/p&gt;
9363
9364 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
9365 manage to get the init.d script dependencies complete and correct. I
9366 expect we will get there in Squeeze+1, if we get manage to test and
9367 fix the remaining issues.&lt;/p&gt;
9368
9369 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9370 the BTS, please usertag the report to get it to show up at
9371 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9372 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9373 </description>
9374 </item>
9375
9376 <item>
9377 <title>Debian has switched to dependency based boot sequencing</title>
9378 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
9379 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
9380 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
9381 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
9382 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
9383 have been migrated to using dependency based boot sequencing. This
9384 conclude work me and others have been doing for the last three days.
9385 It feels great to see this finally part of the default Debian
9386 installation. Now we just need to weed out the last few problems that
9387 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
9388
9389 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
9390 fixing the more fundamental problem of handing the event based
9391 non-predictable kernel in the early boot.&lt;/p&gt;
9392 </description>
9393 </item>
9394
9395 <item>
9396 <title>Taking over sysvinit development</title>
9397 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
9398 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
9399 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
9400 <description>&lt;p&gt;After several years of frustration with the lack of activity from
9401 the existing sysvinit upstream developer, I decided a few weeks ago to
9402 take over the package and become the new upstream. The number of
9403 patches to track for the Debian package was becoming a burden, and the
9404 lack of synchronization between the distribution made it hard to keep
9405 the package up to date.&lt;/p&gt;
9406
9407 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9408 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
9409 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
9410 and Fedora), based on the patches currently in use in these
9411 distributions. We Debian maintainers plan to move to this tarball as
9412 the new upstream as soon as we find time to do the merge. Since the
9413 new tarball was created, we agreed with Werner at SuSe to make a new
9414 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
9415 development there. The project is registered and currently waiting
9416 for approval by the Savannah administrators, and as soon as it is
9417 approved, we will import the old versions from svn and continue
9418 working on the future release.&lt;/p&gt;
9419
9420 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
9421 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
9422 </description>
9423 </item>
9424
9425 <item>
9426 <title>Debian boots quicker and quicker</title>
9427 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
9428 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
9429 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
9430 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
9431 people involved in the boot system on Debian and Ubuntu, to see if we
9432 could find more ways to speed up the boot system. This was an Ubuntu
9433 funded
9434 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
9435 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
9436 of boot systems, and ways to handle the increasing number of boot
9437 issues introduced by the Linux kernel becoming more and more
9438 asynchronous and event base. The Ubuntu approach using udev and
9439 upstart might be a good way forward. Time will show.&lt;/p&gt;
9440
9441 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
9442 process in Debian. All of these should be applied to get a quick
9443 boot:&lt;/p&gt;
9444
9445 &lt;ul&gt;
9446
9447 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
9448
9449 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
9450 clock is in UTC.&lt;/li&gt;
9451
9452 &lt;li&gt;Install and activate the insserv package to enable
9453 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9454 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
9455
9456 &lt;/ul&gt;
9457
9458 These points are based on the Google summer of code work done by
9459 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
9460 Villegas&lt;/a&gt;.
9461
9462 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
9463 unstable yesterday. When we tested it, we were able to cut 6 seconds
9464 from the boot sequence. It depend on very correct dependency
9465 declaration in all init.d scripts, so I expect us to find edge cases
9466 where the dependences in some scripts are slightly wrong when we start
9467 using this.&lt;/p&gt;
9468
9469 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9470 introduced by Raphael Geissert today, one that could affect the
9471 startup speed as well. Instead of starting some scripts concurrently
9472 from rcS.d/ and another set of scripts from rc2.d/, it would be
9473 possible to run a of them in the same process. A quick way to test
9474 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
9475 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
9476 </description>
9477 </item>
9478
9479 <item>
9480 <title>BSAs påstander om piratkopiering møter motstand</title>
9481 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
9482 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
9483 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
9484 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
9485 programvareselskapene som Microsoft og Apple, publisert en rapport der
9486 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9487 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9488 dager siden kom
9489 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
9490 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
9491 dagene. Et spesielt interessant kommentar fra Sverige,
9492 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
9493 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
9494
9495 &lt;blockquote&gt;
9496 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
9497 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9498 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
9499 exakta&quot;, säger BSAs Sverigechef John Hugosson.
9500 &lt;/blockquote&gt;
9501
9502 &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
9503 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
9504 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
9505 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
9506 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
9507
9508 &lt;p&gt;Fant lenkene via &lt;a
9509 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
9510 på Slashdot&lt;/a&gt;.&lt;/p&gt;
9511 </description>
9512 </item>
9513
9514 <item>
9515 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
9516 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
9517 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
9518 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
9519 <description>&lt;p&gt;Kom over
9520 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
9521 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9522 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9523 jobber til daglig. En rask opptelling forteller meg at vi har 490
9524 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
9525 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
9526 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
9527 </description>
9528 </item>
9529
9530 <item>
9531 <title>Kryptert harddisk - naturligvis</title>
9532 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
9533 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
9534 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
9535 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
9536 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
9537 når en tar tap av arbeidstid, fortrolige dokumenter,
9538 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9539 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9540 til at jeg har kryptert harddisken på både kontormaskinen og min
9541 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9542 komme på avveie, den første informasjon relatert til jobben min ved
9543 Universitetet i Oslo, og den andre relatert til blant annet
9544 foreningsarbeide. Kryptering av diskene gjør at det er lite
9545 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9546 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9547 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9548 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9549 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9550 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9551 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9552 det er gjort slik jeg gjør det er minimale, og gevinstene er
9553 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9554 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
9555
9556 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9557 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9558 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9559 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9560 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9561 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9562 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9563 betydelige.&lt;/p&gt;
9564 </description>
9565 </item>
9566
9567 <item>
9568 <title>Two projects that have improved the quality of free software a lot</title>
9569 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
9570 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
9571 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
9572 <description>&lt;p&gt;There are two software projects that have had huge influence on the
9573 quality of free software, and I wanted to mention both in case someone
9574 do not yet know them.&lt;/p&gt;
9575
9576 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
9577 tool to detect and expose errors in the memory handling of programs.
9578 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
9579 and it will report any problems on stdout. It is even better if the
9580 program include debug information. With debug information, it is able
9581 to report the source file name and line number where the problem
9582 occurs. It can report things like &#39;reading past memory block in file
9583 X line N, the memory block was allocated in file Y, line M&#39;, and
9584 &#39;using uninitialised value in control logic&#39;. This tool has made it
9585 trivial to investigate reproducible crash bugs in programs, and have
9586 reduced the number of this kind of bugs in free software a lot.
9587
9588 &lt;p&gt;The second one is
9589 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
9590 a source code checker. It is able to process the source of a program
9591 and find problems in the logic without running the program. It
9592 started out as the Stanford Checker and became well known when it was
9593 used to find bugs in the Linux kernel. It is now a commercial tool
9594 and the company behind it is running
9595 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
9596 free software community, where a lot of free software projects get
9597 their source checked for free. Several thousand defects have been
9598 found and fixed so far. It can find errors like &#39;lock L taken in file
9599 X line N is never released if exiting in line M&#39;, or &#39;the code in file
9600 Y lines O to P can never be executed&#39;. The projects included in the
9601 community service project have managed to get rid of a lot of
9602 reliability problems thanks to Coverity.&lt;/p&gt;
9603
9604 &lt;p&gt;I believe tools like this, that are able to automatically find
9605 errors in the source, are vital to improve the quality of software and
9606 make sure we can get rid of the crashing and failing software we are
9607 surrounded by today.&lt;/p&gt;
9608 </description>
9609 </item>
9610
9611 <item>
9612 <title>No patch is not better than a useless patch</title>
9613 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
9614 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
9615 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
9616 <description>&lt;p&gt;Julien Blache
9617 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
9618 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
9619 patch allow one to discuss a concrete and proposed solution, and also
9620 prove that the issue at hand is important enough for someone to spent
9621 time on fixing it. No patch do not provide any of these positive
9622 properties.&lt;/p&gt;
9623 </description>
9624 </item>
9625
9626 <item>
9627 <title>Standardize on protocols and formats, not vendors and applications</title>
9628 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
9629 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
9630 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
9631 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
9632 very good one to form a long lived computer infrastructure. It is the
9633 simple one, lost by many in todays computer industry: Standardize on
9634 open network protocols and open exchange/storage formats, not applications.
9635 Applications come and go, while protocols and files tend to stay, and
9636 thus one want to make it easy to change application and vendor, while
9637 avoiding conversion costs and locking users to a specific platform or
9638 application.&lt;/p&gt;
9639
9640 &lt;p&gt;This approach make it possible to replace the client applications
9641 independently of the server applications. One can even allow users to
9642 use several different applications as long as they handle the selected
9643 protocol and format. In the normal case, only one client application
9644 is recommended and users only get help if they choose to use this
9645 application, but those that want to deviate from the easy path are not
9646 blocked from doing so.&lt;/p&gt;
9647
9648 &lt;p&gt;It also allow us to replace the server side without forcing the
9649 users to replace their applications, and thus allow us to select the
9650 best server implementation at any moment, when scale and resouce
9651 requirements change.&lt;/p&gt;
9652
9653 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
9654 open formats, but I would never recommend standardizing on a single
9655 application that do not use open network protocol or open formats.&lt;/p&gt;
9656 </description>
9657 </item>
9658
9659 <item>
9660 <title>Returning from Skolelinux developer gathering</title>
9661 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
9662 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
9663 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
9664 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
9665 Edu/Skolelinux development gathering. I got a bit done tuning the
9666 desktop, and looked into the dynamic service location protocol
9667 implementation avahi. It look like it could be useful for us. Almost
9668 30 people participated, and I believe it was a great environment to
9669 get to know the Skolelinux system. Walter Bender, involved in the
9670 development of the Sugar educational platform, presented his stuff and
9671 also helped me improve my OLPC installation. He also showed me that
9672 his Turtle Art application can be used in standalone mode, and we
9673 agreed that I would help getting it packaged for Debian. As a
9674 standalone application it would be great for Debian Edu. We also
9675 tried to get the video conferencing working with two OLPCs, but that
9676 proved to be too hard for us. The application seem to need more work
9677 before it is ready for me. I look forward to getting home and relax
9678 now. :)&lt;/p&gt;
9679 </description>
9680 </item>
9681
9682 <item>
9683 <title>Time for new LDAP schemas replacing RFC 2307?</title>
9684 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
9685 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
9686 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
9687 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
9688 optimal. There is RFC 2307 documenting one way to store NIS maps in
9689 LDAP, and a modified version of this normally called RFC 2307bis, with
9690 some modifications to be compatible with Active Directory. The RFC
9691 specification handle the content of a lot of system databases, but do
9692 not handle DNS zones and DHCP configuration.&lt;/p&gt;
9693
9694 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
9695 we would like to store information about users, SMB clients/hosts,
9696 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9697 and LTSP configuration in LDAP. These objects have a lot in common,
9698 but with the current LDAP schemas it is not possible to have one
9699 object per entity. For example, one need to have at least three LDAP
9700 objects for a given computer, one with the SMB related stuff, one with
9701 DNS information and another with DHCP information. The schemas
9702 provided for DNS and DHCP are impossible to combine into one LDAP
9703 object. In addition, it is impossible to implement quick queries for
9704 netgroup membership, because of the way NIS triples are implemented.
9705 It just do not scale. I believe it is time for a few RFC
9706 specifications to cleam up this mess.&lt;/p&gt;
9707
9708 &lt;p&gt;I would like to have one LDAP object representing each computer in
9709 the network, and this object can then keep the SMB (ie host key), DHCP
9710 (mac address/name) and DNS (name/IP address) settings in one place.
9711 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
9712
9713 &lt;p&gt;I would also like to have a quick way to map from a user or
9714 computer and to the net group this user or computer is a member.&lt;/p&gt;
9715
9716 &lt;p&gt;Active Directory have done a better job than unix heads like myself
9717 in this regard, and the unix side need to catch up. Time to start a
9718 new IETF work group?&lt;/p&gt;
9719 </description>
9720 </item>
9721
9722 <item>
9723 <title>Endelig er Debian Lenny gitt ut</title>
9724 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
9725 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
9726 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
9727 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
9728 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
9729 Et langt steg videre for Debian-prosjektet, og en rekke nye
9730 programpakker blir nå tilgjengelig for de av oss som bruker den
9731 stabile utgaven av Debian. Neste steg er nå å få
9732 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
9733 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
9734 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9735 slippes løs på skolene. Takk til alle debian-utviklerne som har
9736 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9737 bootsekvens tilgjengelig i stabil utgave, vha pakken
9738 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
9739 </description>
9740 </item>
9741
9742 <item>
9743 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
9744 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
9745 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
9746 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
9747 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
9748 Oslo. Most of Saturday was used for the general assemly for the
9749 member organization, but the rest of the weekend I used to tune the
9750 LTSP installation. LTSP now work out of the box on the 10-network.
9751 Acer Aspire One proved to be a very nice thin client, with both
9752 screen, mouse and keybard in a small box. Was working on getting the
9753 diskless workstation setup configured out of the box, but did not
9754 finish it before the weekend was up.&lt;/p&gt;
9755
9756 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
9757 the Brazilian group, so that will have to wait for the next
9758 development gathering. Would love to have the Debian Edu installer
9759 automatically detect and configure a multiseat setup when it find one
9760 of these cards.&lt;/p&gt;
9761 </description>
9762 </item>
9763
9764 <item>
9765 <title>The sorry state of multimedia browser plugins in Debian</title>
9766 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
9767 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
9768 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
9769 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
9770 plugins available in Debian Lenny, to see which one we should use by
9771 default in Debian Edu. We need an embedded video playing plugin with
9772 control buttons to pause or stop the video, and capable of streaming
9773 all the multimedia content available on the web. The test results and
9774 notes are available on
9775 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
9776 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
9777 fill this need. My personal video player favorite, VLC, has a really
9778 bad plugin which fail on a lot of the test pages. A lot of the MIME
9779 types I would expect to work with any free software player (like
9780 video/ogg), just do not work. And simple formats like the
9781 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
9782 totem and vlc plugins. I hope the situation will improve soon. No
9783 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
9784
9785 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
9786 be the only one fitting our needs. :/&lt;/p&gt;
9787 </description>
9788 </item>
9789
9790 </channel>
9791 </rss>