1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged debian
</title>
5 <description>Entries tagged debian
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
11 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
13 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
14 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
15 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
16 der det er krav om målføre. I tillegg til alle skoleoppgavene som
17 elever over det ganske land skal levere inn hvert år. Det mange ikke
18 vet er at selv om de kommersielle alternativene
19 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
20 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
21 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
22 utmerket fri programvarealternativ som kan. Oversetterverktøyet
23 Apertium har støtte for en rekke språkkombinasjoner, og takket være
24 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
25 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
26 nynorsk, og få den automatoversatt til det andre målføret. Resultatet
27 er ikke perfekt, men et svært godt utgangspunkt. Av og til er
28 resultatet så bra at det kan benyttes uten endringer. Jeg vet
29 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
30 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
31 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
32 teksten din i webskjemaet der.
34 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
35 teknologien kan du enten installere pakken
36 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
37 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
39 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
40 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
41 denne teksten som ble skrevet på bokmål over maskinoversatt til
46 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
47 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
48 det er krav om målføre. I tillegg til alle skuleoppgåvene som elevar
49 over det ganske land skal levera inn kvart år. Det mange ikkje veit
50 er at sjølv om dei kommersielle alternativa
51 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
52 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
53 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
54 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
55 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
56 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
57 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
58 nynorsk, og få den *automatoversatt til det andre målføret.
59 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
60 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
61 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
62 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
63 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
64 teksta di i *webskjemaet der.
66 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
67 teknologien kan du anten installera pakken
68 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
69 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
70 *api.*apertium.org. Sjå
71 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
72 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
73 for denne teksta som vart skreva på bokmål over *maskinoversatt til
79 <title>Coz profiler for multi-threaded software is now in Debian
</title>
80 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
81 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
82 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
83 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
84 profiler able to run benchmarking experiments on the instrumented
85 multi-threaded program, finally
86 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
87 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
89 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
90 blogged about the coz tool
</a
> in August working with upstream to make
91 it suitable for Debian. There are still issues with clang
92 compatibility, inline assembly only working x86 and minimized
93 JavaScript libraries.
</p
>
95 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
97 <p
><blockquote
>
98 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
99 </blockquote
></p
>
101 <p
>This will produce a profile.coz file in the current working
102 directory with the profiling information. This is then given to a
103 JavaScript application provided in the package and available from
104 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
105 To start the local copy, invoke it in a browser like this:
</p
>
107 <p
><blockquote
>
108 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
109 </blockquote
></p
>
111 <p
>See the project home page and the
112 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
113 ;login: article on Coz
</a
> for more information on how it is
119 <title>My own self balancing Lego Segway
</title>
120 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
122 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
123 <description><p
>A while back I received a Gyro sensor for the NXT
124 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
125 present. It had been on my wishlist for a while, because I wanted to
126 build a Segway like balancing lego robot. I had already built
127 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
128 robot
</a
> with the kids, using the light/color sensor included in the
129 NXT kit as the balance sensor, but it was not working very well. It
130 could balance for a while, but was very sensitive to the light
131 condition in the room and the reflective properties of the surface and
132 would fall over after a short while. I wanted something more robust,
134 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
135 gyro sensor from HiTechnic
</a
> I believed would solve it on my
136 wishlist for some years before it suddenly showed up as a gift from my
137 loved ones. :)
</p
>
139 <p
>Unfortunately I have not had time to sit down and play with it
140 since then. But that changed some days ago, when I was searching for
141 lego segway information and came across a recipe from HiTechnic for
143 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
144 HTWay
</a
>, a segway like balancing robot. Build instructions and
145 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
146 code
</a
> was included, so it was just a question of putting it all
147 together. And thanks to the great work of many Debian developers, the
148 compiler needed to build the source for the NXT is already included in
149 Debian, so I was read to go in less than an hour. The resulting robot
150 do not look very impressive in its simplicity:
</p
>
152 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
154 <p
>Because I lack the infrared sensor used to control the robot in the
155 design from HiTechnic, I had to comment out the last task
156 (taskControl). I simply placed /* and */ around it get the program
157 working without that sensor present. Now it balances just fine until
158 the battery status run low:
</p
>
160 <p align=
"center
"><video width=
"70%
" controls=
"true
">
161 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
162 </video
></p
>
164 <p
>Now we would like to teach it how to follow a line and take remote
165 control instructions using the included Bluetooth receiver in the NXT.
</p
>
167 <p
>If you, like me, love LEGO and want to make sure we find the tools
168 they need to work with LEGO in Debian and all our derivative
169 distributions like Ubuntu, check out
170 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
171 project page
</a
> and join the Debian LEGO team. Personally I own a
172 RCX and NXT controller (no EV3), and would like to make sure the
173 Debian tools needed to program the systems I own work as they
179 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
180 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
181 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
182 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
183 <description><p
>In July
184 <a href=
"http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
">I
185 wrote how to get the Signal Chrome/Chromium app working
</a
> without
186 the ability to receive SMS messages (aka without a cell phone). It is
187 time to share some experiences and provide an updated setup.
</p
>
189 <p
>The Signal app have worked fine for several months now, and I use
190 it regularly to chat with my loved ones. I had a major snag at the
191 end of my summer vacation, when the the app completely forgot my
192 setup, identity and keys. The reason behind this major mess was
193 running out of disk space. To avoid that ever happening again I have
194 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
195 roll back to an earlier version if the files are wiped by mistake. I
196 had to use it once after introducing the git backup. When rolling
197 back to an earlier version, one need to use the
'reset session
' option
198 in Signal to get going, and notify the people you talk with about the
199 problem. I assume there is some sequence number tracking in the
200 protocol to detect rollback attacks. The git repository is rather big
201 (
674 MiB so far), but I have not tried to figure out if some of the
202 content can be added to a .gitignore file due to lack of spare
205 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
206 make it impossible to send messages using Signal. I could still
207 receive them, but had to patch the code with a new timestamp to send.
208 I believe the timeout is added by the developers to force people to
209 upgrade to the latest version of the app, even when there is no
210 protocol changes, to reduce the version skew among the user base and
211 thus try to keep the number of support requests down.
</p
>
213 <p
>Since my original recipe, the Signal source code changed slightly,
214 making the old patch fail to apply cleanly. Below is an updated
215 patch, including the shell wrapper I use to start Signal. The
216 original version required a new user to locate the JavaScript console
217 and call a function from there. I got help from a friend with more
218 JavaScript knowledge than me to modify the code to provide a GUI
219 button instead. This mean that to get started you just need to run
220 the wrapper and click the
'Register without mobile phone
' to get going
221 now. I
've also modified the timeout code to always set it to
90 days
222 in the future, to avoid having to patch the code regularly.
</p
>
224 <p
>So, the updated recipe for Debian Jessie:
</p
>
228 <li
>First, install required packages to get the source code and the
229 browser you need. Signal only work with Chrome/Chromium, as far as I
230 know, so you need to install it.
233 apt install git tor chromium
234 git clone https://github.com/WhisperSystems/Signal-Desktop.git
235 </pre
></li
>
237 <li
>Modify the source code using command listed in the the patch
238 block below.
</li
>
240 <li
>Start Signal using the run-signal-app wrapper (for example using
241 <tt
>`pwd`/run-signal-app
</tt
>).
243 <li
>Click on the
'Register without mobile phone
', will in a phone
244 number you can receive calls to the next minute, receive the
245 verification code and enter it into the form field and press
246 'Register
'. Note, the phone number you use will be user Signal
247 username, ie the way others can find you on Signal.
</li
>
249 <li
>You can now use Signal to contact others. Note, new contacts do
250 not show up in the contact list until you restart Signal, and there is
251 no way to assign names to Contacts. There is also no way to create or
252 update chat groups. I suspect this is because the web app do not have
253 a associated contact database.
</li
>
257 <p
>I am still a bit uneasy about using Signal, because of the way its
258 main author moxie0 reject federation and accept dependencies to major
259 corporations like Google (part of the code is fetched from Google) and
260 Amazon (the central coordination point is owned by Amazon). See for
262 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
263 LibreSignal issue tracker
</a
> for a thread documenting the authors
264 view on these issues. But the network effect is strong in this case,
265 and several of the people I want to communicate with already use
266 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
267 once it
<a href=
"https://bugs.debian.org/
830265">work on my
268 laptop
</a
>? It already work on Windows and Android, and is included
269 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
270 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
271 working on Debian Stable.
</p
>
273 <p
>Anyway, this is the patch I apply to the Signal code to get it
274 working. It switch to the production servers, disable to timeout,
275 make registration easier and add the shell wrapper:
</p
>
278 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
279 diff --git a/js/background.js b/js/background.js
280 index
24b4c1d.
.579345f
100644
281 --- a/js/background.js
282 +++ b/js/background.js
287 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
288 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
289 var SERVER_PORTS = [
80,
4433,
8443];
290 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
291 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
293 window.getSocketStatus = function() {
294 if (messageReceiver) {
295 diff --git a/js/expire.js b/js/expire.js
296 index
639aeae..beb91c3
100644
301 'use strict
';
302 - var BUILD_EXPIRATION =
0;
303 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
305 window.extension = window.extension || {};
307 diff --git a/js/views/install_view.js b/js/views/install_view.js
308 index
7816f4f.
.1d6233b
100644
309 --- a/js/views/install_view.js
310 +++ b/js/views/install_view.js
313 'click .step1
': this.selectStep.bind(this,
1),
314 'click .step2
': this.selectStep.bind(this,
2),
315 -
'click .step3
': this.selectStep.bind(this,
3)
316 +
'click .step3
': this.selectStep.bind(this,
3),
317 +
'click .callreg
': function() { extension.install(
'standalone
') },
320 clearQR: function() {
321 diff --git a/options.html b/options.html
322 index dc0f28e.
.8d709f6
100644
326 &lt;div class=
'nav
'>
327 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
328 &lt;p
>{{ installTagline }}
&lt;/p
>
329 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
330 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
331 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
334 &lt;span class=
'dot step1 selected
'>&lt;/span
>
335 &lt;span class=
'dot step2
'>&lt;/span
>
336 &lt;span class=
'dot step3
'>&lt;/span
>
337 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
338 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
344 +userdata=
"`pwd`/userdata
"
345 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
346 + (cd $userdata
&& git init)
348 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
350 + --proxy-server=
"socks://localhost:
9050" \
351 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
353 chmod a+rx run-signal-app
356 <p
>As usual, if you use Bitcoin and want to show your support of my
357 activities, please send Bitcoin donations to my address
358 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
363 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
364 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
365 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
366 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
367 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
368 system
</a
> provide a practical and easy way to figure out which
369 packages support the hardware in a given machine. The command line
370 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
371 convenient way to list and install packages relevant for the current
372 hardware during system installation, both user space packages and
373 firmware packages. The GUI background daemon on the other hand provide
374 a pop-up proposing to install packages when a new dongle is inserted
375 while using the computer. For example, if you plug in a smart card
376 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
377 that package isn
't already installed, and if you plug in a USB video
378 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
379 cheese is currently missing. This already work just fine.
</p
>
381 <p
>But Isenkram depend on a database mapping from hardware IDs to
382 package names. When I started no such database existed in Debian, so
383 I made my own data set and included it with the isenkram package and
384 made isenkram fetch the latest version of this database from git using
385 http. This way the isenkram users would get updated package proposals
386 as soon as I learned more about hardware related packages.
</p
>
388 <p
>The hardware is identified using modalias strings. The modalias
389 design is from the Linux kernel where most hardware descriptors are
390 made available as a strings that can be matched using filename style
391 globbing. It handle USB, PCI, DMI and a lot of other hardware related
392 identifiers.
</p
>
394 <p
>The downside to the Isenkram specific database is that there is no
395 information about relevant distribution / Debian version, making
396 isenkram propose obsolete packages too. But along came AppStream, a
397 cross distribution mechanism to store and collect metadata about
398 software packages. When I heard about the proposal, I contacted the
399 people involved and suggested to add a hardware matching rule using
400 modalias strings in the specification, to be able to use AppStream for
401 mapping hardware to packages. This idea was accepted and AppStream is
402 now a great way for a package to announce the hardware it support in a
403 distribution neutral way. I wrote
404 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
405 recipe on how to add such meta-information
</a
> in a blog post last
406 December. If you have a hardware related package in Debian, please
407 announce the relevant hardware IDs using AppStream.
</p
>
409 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
410 RCX or NXT unit, announce this support using AppStream. The effect is
411 that when you insert such LEGO robot controller into your Debian
412 machine, Isenkram will propose to install the packages needed to get
413 it working. The intention is that this should allow the local user to
414 start programming his robot controller right away without having to
415 guess what packages to use or which permissions to fix.
</p
>
417 <p
>But when I sat down with my son the other day to program our NXT
418 unit using his Debian Stretch computer, I discovered something
419 annoying. The local console user (ie my son) did not get access to
420 the USB device for programming the unit. This used to work, but no
421 longer in Jessie and Stretch. After some investigation and asking
422 around on #debian-devel, I discovered that this was because udev had
423 changed the mechanism used to grant access to local devices. The
424 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
425 no longer applied, because LDAP users no longer was added to the
426 plugdev group during login. Michael Biebl told me that this method
427 was obsolete and the new method used ACLs instead. This was good
428 news, as the plugdev mechanism is a mess when using a remote user
429 directory like LDAP. Using ACLs would make sure a user lost device
430 access when she logged out, even if the user left behind a background
431 process which would retain the plugdev membership with the ConsoleKit
432 setup. Armed with this knowledge I moved on to fix the access problem
433 for the LEGO Mindstorms related packages.
</p
>
435 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
436 applied directly for a device, or is applied in
437 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
438 LEGO Mindstorms udev rules did not have a class, I decided to add the
439 tag directly in the udev rules files included in the packages. Here
440 is one example. For the nqc C compiler for the RCX, the
441 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
444 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
445 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
446 </pre
></p
>
448 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
449 packages using plugdev in their /lib/udev/rules.d/ files should be
450 changed to use this tag (either directly or indirectly via
451 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
452 to detect this?
</p
>
454 <p
>I
've been unable to find good documentation on the uaccess feature.
455 It is unclear to me if the uaccess tag is an internal implementation
456 detail like the udev-acl tag used by
457 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
458 indirect method is the preferred way. Michael
459 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
460 documentation from the systemd project
</a
> and I hope it will make
461 this clearer. For now I use the generic classes when they exist and
462 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
463 directly if no such class exist.
</p
>
465 <p
>To learn more about the isenkram system, please check out
466 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
467 blog posts tagged isenkram
</a
>.
</p
>
469 <p
>To help out making life for LEGO constructors in Debian easier,
470 please join us on our IRC channel
471 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
472 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
473 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
474 list is not yet created, but we are working on it. :)
</p
>
476 <p
>As usual, if you use Bitcoin and want to show your support of my
477 activities, please send Bitcoin donations to my address
478 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
483 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
484 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
485 <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>
486 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
487 <description><p
>In April we
488 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
489 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
490 how to set up and administrate a Debian system. Today I am happy to
491 report that the first draft is now publicly available. You can find
492 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
493 Administrator
's Handbook page
</a
> (under Other languages). The first
494 eight chapters have a first draft translation, and we are working on
495 proofreading the content. If you want to help out, please start
497 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
498 hosted weblate project page
</a
>, and get in touch using
499 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
500 translators mailing list
</a
>. Please also check out
501 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
502 contributors
</a
>. A good way to contribute is to proofread the text
503 and update weblate if you find errors.
</p
>
505 <p
>Our goal is still to make the Norwegian book available on paper as well as
506 electronic form.
</p
>
511 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
512 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
514 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
515 <description><p
>This summer, I read a great article
516 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
517 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
518 how to profile multi-threaded programs. It presented a system for
519 profiling software by running experiences in the running program,
520 testing how run time performance is affected by
"speeding up
" parts of
521 the code to various degrees compared to a normal run. It does this by
522 slowing down parallel threads while the
"faster up
" code is running
523 and measure how this affect processing time. The processing time is
524 measured using probes inserted into the code, either using progress
525 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
526 can also measure unmodified code by measuring complete the program
527 runtime and running the program several times instead.
</p
>
529 <p
>The project and presentation was so inspiring that I would like to
530 get the system into Debian. I
531 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
532 a WNPP request for it
</a
> and contacted upstream to try to make the
533 system ready for Debian by sending patches. The build process need to
534 be changed a bit to avoid running
'git clone
' to get dependencies, and
535 to include the JavaScript web page used to visualize the collected
536 profiling information included in the source package.
537 But I expect that should work out fairly soon.
</p
>
539 <p
>The way the system work is fairly simple. To run an coz experiment
540 on a binary with debug symbols available, start the program like this:
542 <p
><blockquote
><pre
>
543 coz run --- program-to-run
544 </pre
></blockquote
></p
>
546 <p
>This will create a text file profile.coz with the instrumentation
547 information. To show what part of the code affect the performance
548 most, use a web browser and either point it to
549 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
550 or use the copy from git (in the gh-pages branch). Check out this web
551 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
552 profiling more useful you include
&lt;coz.h
&gt; and insert the
553 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
554 code, rebuild and run the profiler. This allow coz to do more
555 targeted experiments.
</p
>
557 <p
>A video published by ACM
558 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
559 Coz profiler
</a
> is available from Youtube. There is also a paper
560 from the
25th Symposium on Operating Systems Principles available
562 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
563 finding code that counts with causal profiling
</a
>.
</p
>
565 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
566 for Coz is available from github. It will only build with clang
568 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
569 feature missing in GCC
</a
>, but I
've submitted
570 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
571 it
</a
> and hope it will be included in the upstream source soon.
</p
>
573 <p
>Please get in touch if you, like me, would like to see this piece
574 of software in Debian. I would very much like some help with the
575 packaging effort, as I lack the in depth knowledge on how to package
576 C++ libraries.
</p
>
581 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
582 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
583 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
584 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
585 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
586 to be a slight challenge. Here is the recipe if I ever need to do it
587 again. It all started by me wanting to try the recipe to set up
588 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
589 hardened Android installation
</a
> from the Tor project blog on a
590 device I had access to. It is a old mobile phone with a broken
591 microphone The initial idea had been to just
592 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
593 CyanogenMod on it
</a
>, but did not quite find time to start on it
594 until a few days ago.
</p
>
596 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
597 loader (press volume down and power at the same time), (
2) select
598 'fastboot
' before (
3) connecting the device via USB to a Linux
599 machine, (
4) request the device identifier token by running
'fastboot
600 oem get_identifier_token
', (
5) request the device unlocking key using
601 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
602 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
604 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
605 or newer, and the device I was working on had
2.00.0027. This
606 apparently can be easily fixed by downloading a Windows program and
607 running it on your Windows machine, if you accept the terms Microsoft
608 require you to accept to use Windows - which I do not. So I had to
609 come up with a different approach. I got a lot of help from AndyCap
610 on #nuug, and would not have been able to get this working without
613 <p
>First I needed to extract the hboot firmware from
614 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
615 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
616 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
617 project named unruu
</a
> using libunshield. The unshield tool did not
618 recognise the file format, but unruu worked and extracted rom.zip,
619 containing the new hboot firmware and a text file describing which
620 devices it would work for.
</p
>
622 <p
>Next, I needed to get the new firmware into the device. For this I
623 followed some instructions
624 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
625 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
626 machine with Debian testing:
</p
>
629 adb reboot-bootloader
630 fastboot oem rebootRUU
631 fastboot flash zip rom.zip
632 fastboot flash zip rom.zip
634 </pre
></p
>
636 <p
>The flash command apparently need to be done twice to take effect,
637 as the first is just preparations and the second one do the flashing.
638 The adb command is just to get to the boot loader menu, so turning the
639 device on while holding volume down and the power button should work
642 <p
>With the new hboot version in place I could start following the
643 instructions on the HTC developer web site. I got the device token
647 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
650 <p
>And once I got the unlock code via email, I could use it like
654 fastboot flash unlocktoken Unlock_code.bin
655 </pre
></p
>
657 <p
>And with that final step in place, the phone was unlocked and I
658 could start stuffing the software of my own choosing into the device.
659 So far I only inserted a replacement recovery image to wipe the phone
660 before I start. We will see what happen next. Perhaps I should
661 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
666 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
667 <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>
668 <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>
669 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
670 <description><p
>For a while now, I have wanted to test
671 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
672 said to provide end to end encrypted communication and several of my
673 friends and family are already using it. As I by choice do not own a
674 mobile phone, this proved to be harder than expected. And I wanted to
675 have the source of the client and know that it was the code used on my
676 machine. But yesterday I managed to get it working. I used the
677 Github source, compared it to the source in
678 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
679 Signal Chrome app
</a
> available from the Chrome web store, applied
680 patches to use the production Signal servers, started the app and
681 asked for the hidden
"register without a smart phone
" form. Here is
682 the recipe how I did it.
</p
>
684 <p
>First, I fetched the Signal desktop source from Github, using
687 git clone https://github.com/WhisperSystems/Signal-Desktop.git
690 <p
>Next, I patched the source to use the production servers, to be
691 able to talk to other Signal users:
</p
>
694 cat
&lt;
&lt;EOF | patch -p0
695 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
696 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
697 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
702 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
703 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
704 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
705 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
707 window.getSocketStatus = function() {
708 if (messageReceiver) {
709 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
710 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
711 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
714 'use strict
';
715 - var BUILD_EXPIRATION =
0;
716 + var BUILD_EXPIRATION =
1474492690000;
718 window.extension = window.extension || {};
723 <p
>The first part is changing the servers, and the second is updating
724 an expiration timestamp. This timestamp need to be updated regularly.
725 It is set
90 days in the future by the build process (Gruntfile.js).
726 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
728 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
729 script to launch Signal in Chromium.
</p
>
736 --proxy-server=
"socks://localhost:
9050" \
737 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
740 <p
> The script start the app and configure Chromium to use the Tor
741 SOCKS5 proxy to make sure those controlling the Signal servers (today
742 Amazon and Whisper Systems) as well as those listening on the lines
743 will have a harder time location my laptop based on the Signal
744 connections if they use source IP address.
</p
>
746 <p
>When the script starts, one need to follow the instructions under
747 "Standalone Registration
" in the CONTRIBUTING.md file in the git
748 repository. I right clicked on the Signal window to get up the
749 Chromium debugging tool, visited the
'Console
' tab and wrote
750 'extension.install(
"standalone
")
' on the console prompt to get the
751 registration form. Then I entered by land line phone number and
752 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
753 repeated the verification code three times. After entering the number
754 into the verification code field in the form, I could start using
755 Signal from my laptop.
757 <p
>As far as I can tell, The Signal app will leak who is talking to
758 whom and thus who know who to those controlling the central server,
759 but such leakage is hard to avoid with a centrally controlled server
760 setup. It is something to keep in mind when using Signal - the
761 content of your chats are harder to intercept, but the meta data
762 exposing your contact network is available to people you do not know.
763 So better than many options, but not great. And sadly the usage is
764 connected to my land line, thus allowing those controlling the server
765 to associate it to my home and person. I would prefer it if only
766 those I knew could tell who I was on Signal. There are options
767 avoiding such information leakage, but most of my friends are not
768 using them, so I am stuck with Signal for now.
</p
>
773 <title>The new
"best
" multimedia player in Debian?
</title>
774 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
775 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
776 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
777 <description><p
>When I set out a few weeks ago to figure out
778 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
779 multimedia player in Debian claimed to support most file formats /
780 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
781 the various players claimed support for. The range was from
55 to
130
782 MIME types. I suspect most media formats are supported by all
783 players, but this is not really reflected in the MimeTypes values in
784 their desktop files. There are probably also some bogus MIME types
785 listed, but it is hard to identify which one this is.
</p
>
787 <p
>Anyway, in the mean time I got in touch with upstream for some of
788 the players suggesting to add more MIME types to their desktop files,
789 and decided to spend some time myself improving the situation for my
790 favorite media player VLC. The fixes for VLC entered Debian unstable
791 yesterday. The complete list of MIME types can be seen on the
792 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
793 player MIME type support status
</a
> Debian wiki page.
</p
>
795 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
796 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
797 kmplayer. I am sure some of the other players desktop files support
798 several of the formats currently listed as working only with vlc,
799 toten and parole.
</p
>
801 <p
>A sad observation is that only
14 MIME types are listed as
802 supported by all the tested multimedia players in Debian in their
803 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
804 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
805 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
806 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
807 it sad that video/ogg and video/webm is not supported by all the media
808 players in Debian. As far as I can tell, all of them can handle both
814 <title>A program should be able to open its own files on Linux
</title>
815 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
816 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
817 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
818 <description><p
>Many years ago, when koffice was fresh and with few users, I
819 decided to test its presentation tool when making the slides for a
820 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
821 wrote the first draft of the slides, saved the result and went to bed
822 the day before I would give the talk. The next day I took a plane to
823 the location where the meeting should take place, and on the plane I
824 started up koffice again to polish the talk a bit, only to discover
825 that kpresenter refused to load its own data file. I cursed a bit and
826 started making the slides again from memory, to have something to
827 present when I arrived. I tested that the saved files could be
828 loaded, and the day seemed to be rescued. I continued to polish the
829 slides until I suddenly discovered that the saved file could no longer
830 be loaded into kpresenter. In the end I had to rewrite the slides
831 three times, condensing the content until the talk became shorter and
832 shorter. After the talk I was able to pinpoint the problem
&ndash;
833 kpresenter wrote inline images in a way itself could not understand.
834 Eventually that bug was fixed and kpresenter ended up being a great
835 program to make slides. The point I
'm trying to make is that we
836 expect a program to be able to load its own data files, and it is
837 embarrassing to its developers if it can
't.
</p
>
839 <p
>Did you ever experience a program failing to load its own data
840 files from the desktop file browser? It is not a uncommon problem. A
841 while back I discovered that the screencast recorder
842 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
843 browser would refuse to open. No video player claimed to understand
844 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
845 returning the application/ogg MIME type, which no video player I had
846 installed listed as a MIME type they would understand. I asked for
847 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
848 behavour
</a
> and use the MIME type video/ogg instead. I also asked
849 several video players to add video/ogg to their desktop files, to give
850 the file browser an idea what to do about Ogg Theora files. After a
851 while, the desktop file browsers in Debian started to handle the
852 output from gtk-recordmydesktop properly.
</p
>
854 <p
>But history repeats itself. A few days ago I tested the music
855 system Rosegarden again, and I discovered that the KDE and xfce file
856 browsers did not know what to do with the Rosegarden project files
857 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
858 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
859 included in the next upload. To increase the chance of me remembering
860 how to fix the problem next time some program fail to load its files
861 from the file browser, here are some notes on how to fix it.
</p
>
863 <p
>The file browsers in Debian in general operates on MIME types.
864 There are two sources for the MIME type of a given file. The output from
865 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
866 shared MIME type registry (under /usr/share/mime/). The file MIME
867 type is mapped to programs supporting the MIME type, and this
868 information is collected from
869 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
870 desktop files
</a
> available in /usr/share/applications/. If there is
871 one desktop file claiming support for the MIME type of the file, it is
872 activated when asking to open a given file. If there are more, one
873 can normally select which one to use by right-clicking on the file and
874 selecting the wanted one using
'Open with
' or similar. In general
875 this work well. But it depend on each program picking a good MIME
877 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
878 MIME type registered with IANA
</a
>), file and/or the shared MIME
879 registry recognizing the file and the desktop file to list the MIME
880 type in its list of supported MIME types.
</p
>
882 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
883 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
884 Shared MIME database
</a
> look like this:
</p
>
886 <p
><blockquote
><pre
>
887 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
888 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
889 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
890 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
891 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
892 &lt;glob pattern=
"*.rg
"/
&gt;
893 &lt;/mime-type
&gt;
894 &lt;/mime-info
&gt;
895 </pre
></blockquote
></p
>
897 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
898 (it is a gzipped XML file). Note, it is much better to use an
899 official MIME type registered with IANA than it is to make up ones own
900 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
902 <p
>The desktop file of the rosegarden program failed to list
903 audio/x-rosegarden in its list of supported MIME types, causing the
904 file browsers to have no idea what to do with *.rg files:
</p
>
906 <p
><blockquote
><pre
>
907 % grep Mime /usr/share/applications/rosegarden.desktop
908 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
909 X-KDE-NativeMimeType=audio/x-rosegarden-composition
911 </pre
></blockquote
></p
>
913 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
914 MimeType= line.
</p
>
916 <p
>If you run into a file which fail to open the correct program when
917 selected from the file browser, please check out the output from
918 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
919 MIME type is registered somewhere under /usr/share/mime/ and check
920 that some desktop file under /usr/share/applications/ is claiming
921 support for this MIME type. If not, please report a bug to have it
927 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
928 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
929 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
930 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
931 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
932 system
</a
> is a user-focused solution in Debian for handling hardware
933 related packages. The idea is to have a database of mappings between
934 hardware and packages, and pop up a dialog suggesting for the user to
935 install the packages to use a given hardware dongle. Some use cases
936 are when you insert a Yubikey, it proposes to install the software
937 needed to control it; when you insert a braille reader list it
938 proposes to install the packages needed to send text to the reader;
939 and when you insert a ColorHug screen calibrator it suggests to
940 install the driver for it. The system work well, and even have a few
941 command line tools to install firmware packages and packages for the
942 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
944 <p
>The system was initially written using aptdaemon, because I found
945 good documentation and example code on how to use it. But aptdaemon
946 is going away and is generally being replaced by
947 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
948 so Isenkram needed a rewrite. And today, thanks to the great patch
949 from my college Sunil Mohan Adapa in the FreedomBox project, the
950 rewrite finally took place. I
've just uploaded a new version of
951 Isenkram into Debian Unstable with the patch included, and the default
952 for the background daemon is now to use PackageKit. To check it out,
953 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
954 and see if it is recognised.
</p
>
956 <p
>If you want to know what kind of packages isenkram would propose for
957 the machine it is running on, you can check out the isenkram-lookup
958 program. This is what it look like on a Thinkpad X230:
</p
>
960 <p
><blockquote
><pre
>
976 </pre
></blockquote
></p
>
978 <p
>The hardware mappings come from several places. The preferred way
979 is for packages to announce their hardware support using
980 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
981 cross distribution appstream system
</a
>.
983 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
984 blog posts about isenkram
</a
> to learn how to do that.
</p
>
989 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
990 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
991 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
992 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
993 <description><p
>Yesterday I updated the
994 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
995 package in Debian
</a
> with a few patches sent to me by skilled and
996 enterprising users. There were some nice user and visible changes.
997 First of all, both desktop menu entries now work. A design flaw in
998 one of the script made the history graph fail to show up (its PNG was
999 dumped in ~/.xsession-errors) if no controlling TTY was available.
1000 The script worked when called from the command line, but not when
1001 called from the desktop menu. I changed this to look for a DISPLAY
1002 variable or a TTY before deciding where to draw the graph, and now the
1003 graph window pop up as expected.
</p
>
1005 <p
>The next new feature is a discharge rate estimator in one of the
1006 graphs (the one showing the last few hours). New is also the user of
1007 colours showing charging in blue and discharge in red. The percentages
1008 of this graph is relative to last full charge, not battery design
1011 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1013 <p
>The other graph show the entire history of the collected battery
1014 statistics, comparing it to the design capacity of the battery to
1015 visualise how the battery life time get shorter over time. The red
1016 line in this graph is what the previous graph considers
100 percent:
1018 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1020 <p
>In this graph you can see that I only charge the battery to
80
1021 percent of last full capacity, and how the capacity of the battery is
1022 shrinking. :(
</p
>
1024 <p
>The last new feature is in the collector, which now will handle
1025 more hardware models. On some hardware, Linux power supply
1026 information is stored in /sys/class/power_supply/ACAD/, while the
1027 collector previously only looked in /sys/class/power_supply/AC/. Now
1028 both are checked to figure if there is power connected to the
1031 <p
>If you are interested in how your laptop battery is doing, please
1033 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1034 in Debian unstable, or rebuild it on Jessie to get it working on
1035 Debian stable. :) The upstream source is available from
<a
1036 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1037 Patches are very welcome.
</p
>
1039 <p
>As usual, if you use Bitcoin and want to show your support of my
1040 activities, please send Bitcoin donations to my address
1041 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1046 <title>Debian now with ZFS on Linux included
</title>
1047 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1048 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1049 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1050 <description><p
>Today, after many years of hard work from many people,
1051 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1052 Debian. The package status can be seen on
1053 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1054 for zfs-linux
</a
>. and
1055 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1056 team status page
</a
>. If you want to help out, please join us.
1057 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1058 source code
</a
> is available via git on Alioth. It would also be
1059 great if you could help out with
1060 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1061 it is an important piece of the puzzle to get ZFS working.
</p
>
1066 <title>What is the best multimedia player in Debian?
</title>
1067 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1068 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1069 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1070 <description><p
><strong
>Where I set out to figure out which multimedia player in
1071 Debian claim support for most file formats.
</strong
></p
>
1073 <p
>A few years ago, I had a look at the media support for Browser
1074 plugins in Debian, to get an idea which plugins to include in Debian
1075 Edu. I created a script to extract the set of supported MIME types
1076 for each plugin, and used this to find out which multimedia browser
1077 plugin supported most file formats / media types.
1078 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1079 result
</a
> can still be seen on the Debian wiki, even though it have
1080 not been updated for a while. But browser plugins are less relevant
1081 these days, so I thought it was time to look at standalone
1084 <p
>A few days ago I was tired of VLC not being listed as a viable
1085 player when I wanted to play videos from the Norwegian National
1086 Broadcasting Company, and decided to investigate why. The cause is a
1087 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1088 desktop file
</a
>. In the process I wrote a script to compare the set
1089 of MIME types announced in the desktop file and the browser plugin,
1090 only to discover that there is quite a large difference between the
1091 two for VLC. This discovery made me dig up the script I used to
1092 compare browser plugins, and adjust it to compare desktop files
1093 instead, to try to figure out which multimedia player in Debian
1094 support most file formats.
</p
>
1096 <p
>The result can be seen on the Debian Wiki, as
1097 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1098 table listing all MIME types supported by one of the packages included
1099 in the table
</a
>, with the package supporting most MIME types being
1100 listed first in the table.
</p
>
1102 </p
>The best multimedia player in Debian? It is totem, followed by
1103 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1104 kmplayer. Time for the other players to update their announced MIME
1110 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1111 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1113 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1114 <description>A friend of mine made me aware of
1115 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1116 handheld computer which will be delivered with Debian preinstalled. I
1117 would love to get one of those for my birthday. :)
</p
>
1119 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1120 plugs and many others connectors, and include a full keyboard and a
5"
1121 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1122 day of battery life time, but I have not seen any independent tests
1123 confirming this. The vendor is still collecting preorders, and the
1124 last I heard last night was that
22 more orders were needed before
1125 production started.
</p
>
1127 <p
>As far as I know, this is the first handheld preinstalled with
1128 Debian. Please let me know if you know of any others. Is it the
1129 first computer being sold with Debian preinstalled?
</p
>
1134 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1135 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1137 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1138 <description><p
>During this weekends
1139 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1140 squashing party and developer gathering
</a
>, we decided to do our part
1141 to make sure there are good books about Debian available in Norwegian
1142 Bokmål, and got in touch with the people behind the
1143 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1144 project
</a
> to get started. If you want to help out, please start
1146 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1147 hosted weblate project page
</a
>, and get in touch using
1148 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1149 translators mailing list
</a
>. Please also check out
1150 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1151 contributors
</a
>.
</p
>
1153 <p
>The book is already available on paper in English, French and
1154 Japanese, and our goal is to get it available on paper in Norwegian
1155 Bokmål too. In addition to the paper edition, there are also EPUB and
1156 Mobi versions available. And there are incomplete translations
1157 available for many more languages.
</p
>
1162 <title>One in two hundred Debian users using ZFS on Linux?
</title>
1163 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
1164 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
1165 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
1166 <description><p
>Just for fun I had a look at the popcon number of ZFS related
1167 packages in Debian, and was quite surprised with what I found. I use
1168 ZFS myself at home, but did not really expect many others to do so.
1169 But I might be wrong.
</p
>
1171 <p
>According to
1172 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1173 results for spl-linux
</a
>, there are
1019 Debian installations, or
1174 0.53% of the population, with the package installed. As far as I know
1175 the only use of the spl-linux package is as a support library for ZFS
1176 on Linux, so I use it here as proxy for measuring the number of ZFS
1177 installation on Linux in Debian. In the kFreeBSD variant of Debian
1178 the ZFS feature is already available, and there
1179 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1180 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1181 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1183 <p
>But even though the Debian project leader Lucas Nussbaum
1184 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1185 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1186 cleared, the package is still not in Debian. The package is again in
1187 the NEW queue. Several uploads have been rejected so far because the
1188 debian/copyright file was incomplete or wrong, but there is no reason
1189 to give up. The current status can be seen on
1190 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1191 team status page
</a
>, and
1192 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1193 source code
</a
> is available on Alioth.
</p
>
1195 <p
>As I want ZFS to be included in next version of Debian to make sure
1196 my home server can function in the future using only official Debian
1197 packages, and the current blocker is to get the debian/copyright file
1198 accepted by the FTP masters in Debian, I decided a while back to try
1199 to help out the team. This was the background for my blog post about
1200 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1201 updating and checking debian/copyright semi-automatically
</a
>, and I
1202 used the techniques I explored there to try to find any errors in the
1203 copyright file. It is not very easy to check every one of the around
1204 2000 files in the source package, but I hope we this time got it
1205 right. If you want to help out, check out the git source and try to
1206 find missing entries in the debian/copyright file.
</p
>
1211 <title>Full battery stats collector is now available in Debian
</title>
1212 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1213 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1214 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1215 <description><p
>Since this morning, the battery-stats package in Debian include an
1216 extended collector that will collect the complete battery history for
1217 later processing and graphing. The original collector store the
1218 battery level as percentage of last full level, while the new
1219 collector also record battery vendor, model, serial number, design
1220 full level, last full level and current battery level. This make it
1221 possible to predict the lifetime of the battery as well as visualise
1222 the energy flow when the battery is charging or discharging.
</p
>
1224 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1225 in the version
0.5.1 package in unstable. Get the new battery level graph
1226 and lifetime prediction by running:
1228 <p
><pre
>
1229 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1230 </pre
></p
>
1232 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1234 <p
>The flow in/out of the battery can be seen by running (no menu
1235 entry yet):
</p
>
1237 <p
><pre
>
1238 /usr/share/battery-stats/battery-stats-graph-flow
1239 </pre
></p
>
1241 <p
>I
'm not quite happy with the way the data is visualised, at least
1242 when there are few data points. The graphs look a bit better with a
1243 few years of data.
</p
>
1245 <p
>A while back one important feature I use in the battery stats
1246 collector broke in Debian. The scripts in
1247 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1248 suspect it happened when Jessie started using systemd, but I do not
1249 know. The issue is reported as
1250 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
1251 pm-utils. I managed to work around it by adding an udev rule to call
1252 the collector script every time the power connector is connected and
1253 disconnected. With this fix in place it was finally time to make a
1254 new release of the package, and get it into Debian.
</p
>
1256 <p
>If you are interested in how your laptop battery is doing, please
1258 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1259 in Debian unstable, or rebuild it on Jessie to get it working on
1260 Debian stable. :) The upstream source is available from
1261 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1262 As always, patches are very welcome.
</p
>
1267 <title>Making battery measurements a little easier in Debian
</title>
1268 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
1269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
1270 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
1271 <description><p
>Back in September, I blogged about
1272 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
1273 system I wrote to collect statistics about my laptop battery
</a
>, and
1274 how it showed the decay and death of this battery (now replaced). I
1275 created a simple deb package to handle the collection and graphing,
1276 but did not want to upload it to Debian as there were already
1277 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
1278 package in Debian
</a
> that should do the same thing, and I did not see
1279 a point of uploading a competing package when battery-stats could be
1280 fixed instead. I reported a few bugs about its non-function, and
1281 hoped someone would step in and fix it. But no-one did.
</p
>
1283 <p
>I got tired of waiting a few days ago, and took matters in my own
1284 hands. The end result is that I am now the new upstream developer of
1285 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
1286 battery-stats in Debian, and the package in Debian unstable is finally
1287 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
1288 information provided by the Linux kernel. If you install the
1289 battery-stats package from unstable now, you will be able to get a
1290 graph of the current battery fill level, to get some idea about the
1291 status of the battery. The source package build and work just fine in
1292 Debian testing and stable (and probably oldstable too, but I have not
1293 tested). The default graph you get for that system look like this:
</p
>
1295 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
03-
15-battery-stats-graph-example.png
" width=
"70%
" align=
"center
"></p
>
1297 <p
>My plans for the future is to merge my old scripts into the
1298 battery-stats package, as my old scripts collected a lot more details
1299 about the battery. The scripts are merged into the upstream
1300 battery-stats git repository already, but I am not convinced they work
1301 yet, as I changed a lot of paths along the way. Will have to test a
1302 bit more before I make a new release.
</p
>
1304 <p
>I will also consider changing the file format slightly, as I
1305 suspect the way I combine several values into one field might make it
1306 impossible to know the type of the value when using it for processing
1307 and graphing.
</p
>
1309 <p
>If you would like I would like to keep an close eye on your laptop
1310 battery, check out the battery-stats package in
1311 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
1313 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1314 I would love some help to improve the system further.
</p
>
1319 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
1320 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
1321 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
1322 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
1323 <description><p
>Making packages for Debian requires quite a lot of attention to
1324 details. And one of the details is the content of the
1325 debian/copyright file, which should list all relevant licenses used by
1326 the code in the package in question, preferably in
1327 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
1328 readable DEP5 format
</a
>.
</p
>
1330 <p
>For large packages with lots of contributors it is hard to write
1331 and update this file manually, and if you get some detail wrong, the
1332 package is normally rejected by the ftpmasters. So getting it right
1333 the first time around get the package into Debian faster, and save
1334 both you and the ftpmasters some work.. Today, while trying to figure
1335 out what was wrong with
1336 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
1337 zfsonlinux copyright file
</a
>, I decided to spend some time on
1338 figuring out the options for doing this job automatically, or at least
1339 semi-automatically.
</p
>
1341 <p
>Lucikly, there are at least two tools available for generating the
1342 file based on the code in the source package,
1343 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
1344 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
1345 not sure which one of them came first, but both seem to be able to
1346 create a sensible draft file. As far as I can tell, none of them can
1347 be trusted to get the result just right, so the content need to be
1348 polished a bit before the file is OK to upload. I found the debmake
1350 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
1351 blog posts from
2014</a
>.
1353 <p
>To generate using debmake, use the -cc option:
1355 <p
><pre
>
1356 debmake -cc
> debian/copyright
1357 </pre
></p
>
1359 <p
>Note there are some problems with python and non-ASCII names, so
1360 this might not be the best option.
</p
>
1362 <p
>The cme option is based on a config parsing library, and I found
1364 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1365 blog post from
2015</a
>. To generate using cme, use the
'update
1366 dpkg-copyright
' option:
1368 <p
><pre
>
1369 cme update dpkg-copyright
1370 </pre
></p
>
1372 <p
>This will create or update debian/copyright. The cme tool seem to
1373 handle UTF-
8 names better than debmake.
</p
>
1375 <p
>When the copyright file is created, I would also like some help to
1376 check if the file is correct. For this I found two good options,
1377 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1378 to focus on license types and file matching, and is able to detect
1379 ineffective blocks in the copyright file. The latter reports missing
1380 copyright holders and years, but was confused by inconsistent license
1381 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1382 fix all issues reported by them before uploading. But I do not know
1383 if the tools and the ftpmasters agree on what is important to fix in a
1384 copyright file, so the package might still be rejected.
</p
>
1386 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1387 will read through the source and try to find all copyright statements.
1388 It is not comparing the result to the content of debian/copyright, but
1389 can be useful when verifying the content of the copyright file.
</p
>
1391 <p
>Are you aware of better tools in Debian to create and update
1392 debian/copyright file. Please let me know, or blog about it on
1393 planet.debian.org.
</p
>
1395 <p
>As usual, if you use Bitcoin and want to show your support of my
1396 activities, please send Bitcoin donations to my address
1397 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1399 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1400 on how to use licensecheck and cdbs to create a draft copyright file
1402 <p
><pre
>
1403 licensecheck --copyright -r `find * -type f` | \
1404 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1405 </pre
></p
>
1407 <p
>He mentioned that he normally check the generated file into the
1408 version control system to make it easier to discover license and
1409 copyright changes in the upstream source. I will try to do the same
1410 with my packages in the future.
</p
>
1412 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1413 against using -quiet for new users, so I removed it from the proposed
1414 command line.
</p
>
1419 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1420 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1421 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1422 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1423 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1424 is taking shape in Debian, and one provided feature is a very
1425 convenient way to tell you which package to install to make a given
1426 firmware file available when the kernel is looking for it. This can
1427 be done using apt-file too, but that is for someone else to blog
1430 <p
>Here is a small recipe to find the package with a given firmware
1431 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1432 picked from the set of firmware announced using appstream in Debian
1433 unstable. In general you would be looking for the firmware requested
1434 by the kernel during kernel module loading. To find the package
1435 providing the example file, do like this:
</p
>
1437 <blockquote
><pre
>
1438 % apt install appstream
1442 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1443 awk
'/Package:/ {print $
2}
'
1446 </pre
></blockquote
>
1448 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
1449 appstream wiki
</a
> page to learn how to embed the package metadata in
1450 a way appstream can use.
</p
>
1452 <p
>This same approach can be used to find any package supporting a
1453 given MIME type. This is very useful when you get a file you do not
1454 know how to handle. First find the mime type using
<tt
>file
1455 --mime-type
</tt
>, and next look up the package providing support for
1456 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1457 and you can find all packages handling this type like this:
</p
>
1459 <blockquote
><pre
>
1460 % apt install appstream
1464 % appstreamcli what-provides mimetype image/svg+xml | \
1465 awk
'/Package:/ {print $
2}
'
1487 </pre
></blockquote
>
1489 <p
>I believe the MIME types are fetched from the desktop file for
1490 packages providing appstream metadata.
</p
>
1495 <title>Creepy, visualise geotagged social media information - nice free software
</title>
1496 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
1497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
1498 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
1499 <description><p
>Most people seem not to realise that every time they walk around
1500 with the computerised radio beacon known as a mobile phone their
1501 position is tracked by the phone company and often stored for a long
1502 time (like every time a SMS is received or sent). And if their
1503 computerised radio beacon is capable of running programs (often called
1504 mobile apps) downloaded from the Internet, these programs are often
1505 also capable of tracking their location (if the app requested access
1506 during installation). And when these programs send out information to
1507 central collection points, the location is often included, unless
1508 extra care is taken to not send the location. The provided
1509 information is used by several entities, for good and bad (what is
1510 good and bad, depend on your point of view). What is certain, is that
1511 the private sphere and the right to free movement is challenged and
1512 perhaps even eradicated for those announcing their location this way,
1513 when they share their whereabouts with private and public
1516 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1518 <p
>The phone company logs provide a register of locations to check out
1519 when one want to figure out what the tracked person was doing. It is
1520 unavailable for most of us, but provided to selected government
1521 officials, company staff, those illegally buying information from
1522 unfaithful servants and crackers stealing the information. But the
1523 public information can be collected and analysed, and a free software
1524 tool to do so is called
1525 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1526 discovered it when I read
1527 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1528 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1529 November
2014, and decided to check if it was available in Debian.
1530 The python program was in Debian, but
1531 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1532 Debian
</a
> was completely broken and practically unmaintained. I
1533 uploaded a new version which did not work quite right, but did not
1534 have time to fix it then. This Christmas I decided to finally try to
1535 get Creepy operational in Debian. Now a fixed version is available in
1536 Debian unstable and testing, and almost all Debian specific patches
1538 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1540 <p
>The Creepy program visualises geolocation information fetched from
1541 Twitter, Instagram, Flickr and Google+, and allow one to get a
1542 complete picture of every social media message posted recently in a
1543 given area, or track the movement of a given individual across all
1544 these services. Earlier it was possible to use the search API of at
1545 least some of these services without identifying oneself, but these
1546 days it is impossible. This mean that to use Creepy, you need to
1547 configure it to log in as yourself on these services, and provide
1548 information to them about your search interests. This should be taken
1549 into account when using Creepy, as it will also share information
1550 about yourself with the services.
</p
>
1552 <p
>The picture above show the twitter messages sent from (or at least
1553 geotagged with a position from) the city centre of Oslo, the capital
1554 of Norway. One useful way to use Creepy is to first look at
1555 information tagged with an area of interest, and next look at all the
1556 information provided by one or more individuals who was in the area.
1557 I tested it by checking out which celebrity provide their location in
1558 twitter messages by checkout out who sent twitter messages near a
1559 Norwegian TV station, and next could track their position over time,
1560 making it possible to locate their home and work place, among other
1561 things. A similar technique have been
1562 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
1563 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
1564 tool to discover lying governments, and a useful tool to help people
1565 understand the value of the private information they provide to the
1568 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
1569 it depend on several python modules currently missing in Jessie (at
1570 least python-instagram, python-flickrapi and
1571 python-requests-toolbelt).
</p
>
1573 <p
>(I have uploaded
1574 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
1575 screenshots.debian.net
</a
> and licensed it under the same terms as the
1576 Creepy program in Debian.)
</p
>
1581 <title>Always download Debian packages using Tor - the simple recipe
</title>
1582 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
1583 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
1584 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
1585 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
1586 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
1587 that those listening on the Internet lines would have good reason to
1588 believe a computer have a given security hole
</a
> if it download a
1589 security fix from a Debian mirror. This is a good reason to always
1590 use encrypted connections to the Debian mirror, to make sure those
1591 listening do not know which IP address to attack. In August, Richard
1592 Hartmann observed that encryption was not enough, when it was possible
1593 to interfere download size to security patches or the fact that
1594 download took place shortly after a security fix was released, and
1595 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
1596 to always use Tor to download packages from the Debian mirror
</a
>. He
1597 was not the first to propose this, as the
1598 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
1599 package by Tim Retout already existed to make it easy to convince apt
1600 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
1601 aware of that package when I read the blog post from Richard.
</p
>
1603 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
1604 sysadmins, and he set up a Tor hidden service on one of the central
1605 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1606 it possible to download packages directly between two tor nodes,
1607 making sure the network traffic always were encrypted.
</p
>
1609 <p
>Here is a short recipe for enabling this on your machine, by
1610 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
1611 urls with tor+http and tor+https, and using the hidden service instead
1612 of the official Debian mirror site. I recommend installing
1613 <tt
>etckeeper
</tt
> before you start to have a history of the changes
1614 done in /etc/.
</p
>
1616 <blockquote
><pre
>
1617 apt install apt-transport-tor
1618 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
1619 sed -i
's% http% tor+http%
' /etc/apt/sources.list
1620 </pre
></blockquote
>
1622 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
1623 the sed commands for these too. The sed command is assuming your are
1624 using the ftp.debian.org Debian mirror. Adjust the command (or just
1625 edit the file manually) to match your mirror.
</p
>
1627 <p
>This work in Debian Jessie and later. Note that tools like
1628 <tt
>apt-file
</tt
> only recently started using the apt transport
1629 system, and do not work with these tor+http URLs. For
1630 <tt
>apt-file
</tt
> you need the version currently in experimental,
1631 which need a recent apt version currently only in unstable. So if you
1632 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
1634 <p
>Another advantage from this change is that your machine will start
1635 using Tor regularly and at fairly random intervals (every time you
1636 update the package lists or upgrade or install a new package), thus
1637 masking other Tor traffic done from the same machine. Using Tor will
1638 become normal for the machine in question.
</p
>
1640 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
1641 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
1642 enabled. It would be great if it was the default on any Debian
1648 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
1649 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
1650 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
1651 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
1652 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
1653 call the car license plate numbers in those days. I would write the
1654 numbers down in my little book and compare notes with the other kids
1655 to see how many region codes we had seen and if we had seen some
1656 exotic or special region codes and numbers. It was a fun game to pass
1657 time, as we kids have plenty of it.
</p
>
1659 <p
>A few days I came across
1660 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
1661 project
</a
>, a free software project to automatically discover and
1662 report license plates in images and video streams, and provide the
1663 "car numbers
" in a machine readable format. I
've been looking for
1664 such system for a while now, because I believe it is a bad idea that the
1665 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
1666 number plate recognition
</a
> tool only is available in the hands of
1667 the powerful, and want it to be available also for the powerless to
1668 even the score when it comes to surveillance and sousveillance. I
1669 discovered the developer
1670 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
1671 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
1672 help him get it into shape to get the package uploaded into the Debian
1675 <p
>Today we finally managed to get the package into shape and uploaded
1676 it into Debian, where it currently
1677 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
1678 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
1680 <p
>I guess you are wondering why on earth such tool would be useful
1681 for the common folks, ie those not running a large government
1682 surveillance system? Well, I plan to put it in a computer on my bike
1683 and in my car, tracking the cars nearby and allowing me to be notified
1684 when number plates on my watch list are discovered. Another use case
1685 was suggested by a friend of mine, who wanted to set it up at his home
1686 to open the car port automatically when it discovered the plate on his
1687 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1688 capable of placing his license plate number of a piece of cardboard to
1689 open his car port, men replied that it was always unlocked anyway. I
1690 guess for such use case it make sense. I am sure there are other use
1691 cases too, for those with imagination and a vision.
</p
>
1693 <p
>If you want to build your own version of the Debian package, check
1694 out the upstream git source and symlink ./distros/debian to ./debian/
1695 before running
"debuild
" to build the source. Or wait a bit until the
1696 package show up in unstable.
</p
>
1701 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
1702 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
1703 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
1704 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
1705 <description><p
>Around three years ago, I created
1706 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
1707 system
</a
> to get a more practical solution in Debian for handing
1708 hardware related packages. A GUI system in the isenkram package will
1709 present a pop-up dialog when some hardware dongle supported by
1710 relevant packages in Debian is inserted into the machine. The same
1711 lookup mechanism to detect packages is available as command line
1712 tools in the isenkram-cli package. In addition to mapping hardware,
1713 it will also map kernel firmware files to packages and make it easy to
1714 install needed firmware packages automatically. The key for this
1715 system to work is a good way to map hardware to packages, in other
1716 words, allow packages to announce what hardware they will work
1719 <p
>I started by providing data files in the isenkram source, and
1720 adding code to download the latest version of these data files at run
1721 time, to ensure every user had the most up to date mapping available.
1722 I also added support for storing the mapping in the Packages file in
1723 the apt repositories, but did not push this approach because while I
1724 was trying to figure out how to best store hardware/package mappings,
1725 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
1726 appstream system
</a
> was announced. I got in touch and suggested to
1727 add the hardware mapping into that data set to be able to use
1728 appstream as a data source, and this was accepted at least for the
1729 Debian version of appstream.
</p
>
1731 <p
>A few days ago using appstream in Debian for this became possible,
1732 and today I uploaded a new version
0.20 of isenkram adding support for
1733 appstream as a data source for mapping hardware to packages. The only
1734 package so far using appstream to announce its hardware support is my
1735 pymissile package. I got help from Matthias Klumpp with figuring out
1736 how do add the required
1737 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
1738 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
1739 this content:
</p
>
1741 <blockquote
><pre
>
1742 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1743 &lt;component
&gt;
1744 &lt;id
&gt;pymissile
&lt;/id
&gt;
1745 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
1746 &lt;name
&gt;pymissile
&lt;/name
&gt;
1747 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
1748 &lt;description
&gt;
1750 Pymissile provides a curses interface to control an original
1751 Marks and Spencer / Striker USB Missile Launcher, as well as a
1752 motion control script to allow a webcamera to control the
1755 &lt;/description
&gt;
1756 &lt;provides
&gt;
1757 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
1758 &lt;/provides
&gt;
1759 &lt;/component
&gt;
1760 </pre
></blockquote
>
1762 <p
>The key for isenkram is the component/provides/modalias value,
1763 which is a glob style match rule for hardware specific strings
1764 (modalias strings) provided by the Linux kernel. In this case, it
1765 will map to all USB devices with vendor code
1130 and product code
1768 <p
>Note, it is important that the license of all the metadata files
1769 are compatible to have permissions to aggregate them into archive wide
1770 appstream files. Matthias suggested to use MIT or BSD licenses for
1771 these files. A challenge is figuring out a good id for the data, as
1772 it is supposed to be globally unique and shared across distributions
1773 (in other words, best to coordinate with upstream what to use). But
1774 it can be changed later or, so we went with the package name as
1775 upstream for this project is dormant.
</p
>
1777 <p
>To get the metadata file installed in the correct location for the
1778 mirror update scripts to pick it up and include its content the
1779 appstream data source, the file must be installed in the binary
1780 package under /usr/share/appdata/. I did this by adding the following
1781 line to debian/pymissile.install:
</p
>
1783 <blockquote
><pre
>
1784 debian/pymissile.metainfo.xml usr/share/appdata
1785 </pre
></blockquote
>
1787 <p
>With that in place, the command line tool isenkram-lookup will list
1788 all packages useful on the current computer automatically, and the GUI
1789 pop-up handler will propose to install the package not already
1790 installed if a hardware dongle is inserted into the machine in
1793 <p
>Details of the modalias field in appstream is available from the
1794 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
1796 <p
>To locate the modalias values of all hardware present in a machine,
1797 try running this command on the command line:
</p
>
1799 <blockquote
><pre
>
1800 cat $(find /sys/devices/|grep modalias)
1801 </pre
></blockquote
>
1803 <p
>To learn more about the isenkram system, please check out
1804 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1805 blog posts tagged isenkram
</a
>.
</p
>
1810 <title>The GNU General Public License is not magic pixie dust
</title>
1811 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
1812 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
1813 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
1814 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
1815 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
1816 GPL is not magic pixie dust
</a
>" explain the importance of making sure
1817 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
1818 I quote the blog post from Paul in full here with his permission:
<p
>
1822 <p
><a href=
"https://sfconservancy.org/supporter/
"><img src=
"https://sfconservancy.org/img/supporter-badge.png
" width=
"194" height=
"90" alt=
"Become a Software Freedom Conservancy Supporter!
" align=
"right
" border=
"0" /
></a
></p
>
1825 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
1827 The first step is to choose a
1828 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
1831 The next step is, when someone fails to follow that copyleft license,
1832 <b
>it must be enforced
</b
><br/
>
1834 and its a simple fact of our modern society that such type of
1837 is incredibly expensive to do and incredibly difficult to do.
1840 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
1841 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
1842 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
1843 0x57</a
></small
></p
>
1845 <p
>As the Debian Website
1846 <a href=
"https://bugs.debian.org/
794116">used
</a
>
1847 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
1848 imply, public domain and permissively licensed software can lead to
1849 the production of more proprietary software as people discover useful
1850 software, extend it and or incorporate it into their hardware or
1851 software products. Copyleft licenses such as the GNU GPL were created
1852 to close off this avenue to the production of proprietary software but
1853 such licenses are not enough. With the ongoing adoption of Free
1854 Software by individuals and groups, inevitably the community
's
1855 expectations of license compliance are violated, usually out of
1856 ignorance of the way Free Software works, but not always. As Karen
1857 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
1858 Freedom
">FaiF
</a
>
1859 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
1860 copyleft is nothing if no-one is willing and able to stand up in court
1861 to protect it. The reality of today
's world is that legal
1862 representation is expensive, difficult and time consuming. With
1863 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
1864 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
1865 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
1866 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
1867 of the Linux project, Debian and other groups against GPL violations.
1868 In March the SFC supported a
1869 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
1870 by Christoph Hellwig
</a
> against VMware for refusing to
1871 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
1872 with the GPL
</a
> in relation to their use of parts of the Linux
1873 kernel. Since then two of their sponsors pulled corporate funding and
1875 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
1876 or cancelled their talks
</a
>. As a result they have decided to rely
1877 less on corporate funding and more on the broad community of
1878 individuals who support Free Software and copyleft. So the SFC has
1879 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
1880 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
1881 a community of folks who stand up for copyleft and the GPL by
1882 supporting their work on promoting and supporting copyleft and Free
1885 <p
>If you support Free Software,
1886 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
1887 what the SFC do, agree with their
1888 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
1889 principles
</a
>, are happy about their
1890 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
1891 work on a project that is an SFC
1892 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
1893 just want to stand up for copyleft, please join
1894 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
1895 Allan Webber
</a
>,
1896 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
1898 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
1899 Bacon
</a
>, myself and
1900 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
1902 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
1903 next week your donation will be
1904 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
1905 by an anonymous donor. Please also consider asking your employer to
1906 match your donation or become a sponsor of SFC. Don
't forget to
1907 spread the word about your support for SFC via email, your blog and or
1908 social media accounts.
</p
>
1912 <p
>I agree with Paul on this topic and just signed up as a Supporter
1913 of Software Freedom Conservancy myself. Perhaps you should be a
1914 supporter too?
</p
>
1919 <title>PGP key transition statement for key EE4E02F9
</title>
1920 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
1921 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
1922 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
1923 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
1924 set it up properly. I wanted to generate it offline and have it
1925 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
1926 smart card
</a
> for daily use, and learning how to do it and finding
1927 time to sit down with an offline machine almost took forever. But
1928 finally I
've been able to complete the process, and have now moved
1929 from my old GPG key to a new GPG key. See
1930 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
1931 full transition statement, signed with both my old and new key
</a
> for
1932 the details. This is my new key:
</p
>
1935 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
1936 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
1937 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
1938 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
1939 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
1940 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
1941 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
1944 <p
>The key can be downloaded from the OpenPGP key servers, signed by
1945 my old key.
</p
>
1947 <p
>If you signed my old key
1948 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
1949 I
'd very much appreciate a signature on my new key, details and
1950 instructions in the transition statement. I m happy to reciprocate if
1951 you have a similarly signed transition statement to present.
</p
>
1956 <title>The life and death of a laptop battery
</title>
1957 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
1958 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
1959 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
1960 <description><p
>When I get a new laptop, the battery life time at the start is OK.
1961 But this do not last. The last few laptops gave me a feeling that
1962 within a year, the life time is just a fraction of what it used to be,
1963 and it slowly become painful to use the laptop without power connected
1964 all the time. Because of this, when I got a new Thinkpad X230 laptop
1965 about two years ago, I decided to monitor its battery state to have
1966 more hard facts when the battery started to fail.
</p
>
1968 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
1970 <p
>First I tried to find a sensible Debian package to record the
1971 battery status, assuming that this must be a problem already handled
1972 by someone else. I found
1973 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
1974 which collects statistics from the battery, but it was completely
1975 broken. I sent a few suggestions to the maintainer, but decided to
1976 write my own collector as a shell script while I waited for feedback
1978 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
1979 blog post about the battery development on a MacBook Air
</a
> I also
1981 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
1982 available in Debian.
</p
>
1984 <p
>I started my collector
2013-
07-
15, and it has been collecting
1985 battery stats ever since. Now my
1986 /var/log/hjemmenett-battery-status.log file contain around
115,
000
1987 measurements, from the time the battery was working great until now,
1988 when it is unable to charge above
7% of original capacity. My
1989 collector shell script is quite simple and look like this:
</p
>
1994 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
1996 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
1997 logfile=/var/log/hjemmenett-battery-status.log
1999 files=
"manufacturer model_name technology serial_number \
2000 energy_full energy_full_design energy_now cycle_count status
"
2002 if [ ! -e
"$logfile
" ] ; then
2004 printf
"timestamp,
"
2006 printf
"%s,
" $f
2009 )
> "$logfile
"
2013 # Print complete message in one echo call, to avoid race condition
2014 # when several log processes run in parallel.
2015 msg=$(printf
"%s,
" $(date +%s); \
2016 for f in $files; do \
2017 printf
"%s,
" $(cat $f); \
2019 echo
"$msg
"
2022 cd /sys/class/power_supply
2025 (cd $bat
&& log_battery
>> "$logfile
")
2029 <p
>The script is called when the power management system detect a
2030 change in the power status (power plug in or out), and when going into
2031 and out of hibernation and suspend. In addition, it collect a value
2032 every
10 minutes. This make it possible for me know when the battery
2033 is discharging, charging and how the maximum charge change over time.
2034 The code for the Debian package
2035 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2036 available on github
</a
>.
</p
>
2038 <p
>The collected log file look like this:
</p
>
2041 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2042 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2044 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2045 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2048 <p
>I wrote a small script to create a graph of the charge development
2049 over time. This graph depicted above show the slow death of my laptop
2052 <p
>But why is this happening? Why are my laptop batteries always
2053 dying in a year or two, while the batteries of space probes and
2054 satellites keep working year after year. If we are to believe
2055 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2056 University
</a
>, the cause is me charging the battery whenever I have a
2057 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2058 all the time, but to stay below
90% of full charge most of the time.
2059 I
've been told that the Tesla electric cars
2060 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2061 the charge of their batteries to
80%
</a
>, with the option to charge to
2062 100% when preparing for a longer trip (not that I would want a car
2063 like Tesla where rights to privacy is abandoned, but that is another
2064 story), which I guess is the option we should have for laptops on
2065 Linux too.
</p
>
2067 <p
>Is there a good and generic way with Linux to tell the battery to
2068 stop charging at
80%, unless requested to charge to
100% once in
2069 preparation for a longer trip? I found
2070 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2071 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2072 80%
</a
>, but could not get it to work (kernel module refused to
2075 <p
>I wonder why the battery capacity was reported to be more than
100%
2076 at the start. I also wonder why the
"full capacity
" increases some
2077 times, and if it is possible to repeat the process to get the battery
2078 back to design capacity. And I wonder if the discharge and charge
2079 speed change over time, or if this stay the same. I did not yet try
2080 to write a tool to calculate the derivative values of the battery
2081 level, but suspect some interesting insights might be learned from
2084 <p
>Update
2015-
09-
24: I got a tip to install the packages
2085 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2086 packages instead of the tp-smapi-dkms package I had tried to use
2087 initially, and use
'tlp setcharge
40 80' to change when charging start
2088 and stop. I
've done so now, but expect my existing battery is toast
2089 and need to be replaced. The proposal is unfortunately Thinkpad
2095 <title>New laptop - some more clues and ideas based on feedback
</title>
2096 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2097 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2098 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2099 <description><p
>Several people contacted me after my previous blog post about my
2100 need for a new laptop, and provided very useful feedback. I wish to
2101 thank every one of these. Several pointed me to the possibility of
2102 fixing my X230, and I am already in the process of getting Lenovo to
2103 do so thanks to the on site, next day support contract covering the
2104 machine. But the battery is almost useless (I expect to replace it
2105 with a non-official battery) and I do not expect the machine to live
2106 for many more years, so it is time to plan its replacement. If I did
2107 not have a support contract, it was suggested to find replacement parts
2108 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2109 might present a language barrier as I do not understand French.
</p
>
2111 <p
>One tip I got was to use the
2112 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2113 compare laptop models. It seem to have more models available than
2114 prisjakt.no. Another tip I got from someone I know have similar
2115 keyboard preferences was that the HP EliteBook
840 keyboard is not
2116 very good, and this matches my experience with earlier EliteBook
2117 keyboards I tested. Because of this, I will not consider it any further.
2119 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2120 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2121 (which is missing from the X240), and is working fairly well with
2122 Debian Sid/Unstable according to
2123 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2124 got on the keyboard quality are not consistent. Some say the keyboard
2125 is good, others say it is ok, while others say it is not very good.
2126 Those with experience from X41 and and X60 agree that the X250
2127 keyboard is not as good as those trusty old laptops, and suggest I
2128 keep and fix my X230 instead of upgrading, or get a used X230 to
2129 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2130 activity and battery status, which is very convenient on my X230. I
'm
2131 also told that the CPU fan is running very often, making it a bit
2132 noisy. In any case, the X250 do not work out of the box with Debian
2133 Stable/Jessie, one of my requirements.
</p
>
2135 <p
>I have also gotten a few vendor proposals, one was
2136 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2137 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2138 The latter look very attractive to me.
</p
>
2140 <p
>Again, thank you all for the very useful feedback. It help a lot
2141 as I keep looking for a replacement.
</p
>
2143 <p
>Update
2015-
07-
06: I was recommended to check out the
2144 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2146 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2147 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2152 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2153 <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>
2154 <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>
2155 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2156 <description><p
>My primary work horse laptop is failing, and will need a
2157 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2158 started flickering yesterday, and I suspect the cause is a broken
2159 cable, as changing the angle of the screen some times get rid of the
2160 flickering.
</p
>
2162 <p
>My requirements have not really changed since I bought it, and is
2164 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
2165 described them in
2013</a
>. The last time I bought a laptop, I had
2167 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
2168 where I could select at least a few of the requirements (mouse pin,
2169 wifi, weight) and go through the rest manually. Three button mouse
2170 and a good keyboard is not available as an option, and all the three
2171 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2172 G2) lack three mouse buttons). It is also unclear to me how good the
2173 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2174 the keyboard, even if the quality and robustness in the X series have
2175 deteriorated since X41.
</p
>
2177 <p
>I wonder how I can find a sensible laptop when none of the options
2178 seem sensible to me? Are there better services around to search the
2179 set of available laptops for features? Please send me an email if you
2180 have suggestions.
</p
>
2182 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2183 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2184 of endorsed hardware
</a
>, which is useful background information.
</p
>
2189 <title>How to stay with sysvinit in Debian Jessie
</title>
2190 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2191 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2192 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2193 <description><p
>By now, it is well known that Debian Jessie will not be using
2194 sysvinit as its boot system by default. But how can one keep using
2195 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2197 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2198 Schubert
</a
> and
2199 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2202 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2203 keep sysvinit as your boot system, create a file
2204 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2205 you upgrade:
</p
>
2207 <p
><blockquote
><pre
>
2208 Package: systemd-sysv
2209 Pin: release o=Debian
2211 </pre
></blockquote
><p
>
2213 <p
>This file content will tell apt and aptitude to not consider
2214 installing systemd-sysv as part of any installation and upgrade
2215 solution when resolving dependencies, and thus tell it to avoid
2216 systemd as a default boot system. The end result should be that the
2217 upgraded system keep using sysvinit.
</p
>
2219 <p
>If you are installing Jessie for the first time, there is no way to
2220 get sysvinit installed by default (debootstrap used by
2221 debian-installer have no option for this), but one can tell the
2222 installer to switch to sysvinit before the first boot. Either by
2223 using a kernel argument to the installer, or by adding a line to the
2224 preseed file used. First, the kernel command line argument:
2226 <p
><blockquote
><pre
>
2227 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2228 </pre
></blockquote
><p
>
2230 <p
>Next, the line to use in a preseed file:
</p
>
2232 <p
><blockquote
><pre
>
2233 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2234 </pre
></blockquote
><p
>
2236 <p
>One can of course also do this after the first boot by installing
2237 the sysvinit-core package.
</p
>
2239 <p
>I recommend only using sysvinit if you really need it, as the
2240 sysvinit boot sequence in Debian have several hardware specific bugs
2241 on Linux caused by the fact that it is unpredictable when hardware
2242 devices show up during boot. But on the other hand, the new default
2243 boot system still have a few rough edges I hope will be fixed before
2244 Jessie is released.
</p
>
2246 <p
>Update
2014-
11-
26: Inspired by
2247 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2248 blog post by Torsten Glaser
</a
>, added --purge to the preseed
2254 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
2255 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
2256 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
2257 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
2258 <description><p
>The right to communicate with your friends and family in private,
2259 without anyone snooping, is a right every citicen have in a liberal
2260 democracy. But this right is under serious attack these days.
</p
>
2262 <p
>A while back it occurred to me that one way to make the dragnet
2263 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2264 the whisleblower Snowden) more expensive for Internet email,
2265 is to deliver all email using SMTP via Tor. Such SMTP option would be
2266 a nice addition to the FreedomBox project if we could send email
2267 between FreedomBox machines without leaking metadata about the emails
2268 to the people peeking on the wire. I
2269 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
2270 this on the FreedomBox project mailing list in October
</a
> and got a
2271 lot of useful feedback and suggestions. It also became obvious to me
2272 that this was not a novel idea, as the same idea was tested and
2273 documented by Johannes Berg as early as
2006, and both
2274 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
2275 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
2276 propose a similar method / protocol to pass emails between users.
</p
>
2278 <p
>To implement such system one need to set up a Tor hidden service
2279 providing the SMTP protocol on port
25, and use email addresses
2280 looking like username@hidden-service-name.onion. With such addresses
2281 the connections to port
25 on hidden-service-name.onion using Tor will
2282 go to the correct SMTP server. To do this, one need to configure the
2283 Tor daemon to provide the hidden service and the mail server to accept
2284 emails for this .onion domain. To learn more about Exim configuration
2285 in Debian and test the design provided by Johannes Berg in his FAQ, I
2286 set out yesterday to create a Debian package for making it trivial to
2287 set up such SMTP over Tor service based on Debian. Getting it to work
2288 were fairly easy, and
2289 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
2290 source code for the Debian package
</a
> is available from github. I
2291 plan to move it into Debian if further testing prove this to be a
2292 useful approach.
</p
>
2294 <p
>If you want to test this, set up a blank Debian machine without any
2295 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
2296 get rid of exim4). Install tor, clone the git repository mentioned
2297 above, build the deb and install it on the machine. Next, run
2298 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
2299 the instructions to get the service up and running. Restart tor and
2300 exim when it is done, and test mail delivery using swaks like
2303 <p
><blockquote
><pre
>
2304 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2305 --to fbx@dutlqrrmjhtfa3vp.onion
2306 </pre
></blockquote
></p
>
2308 <p
>This will test the SMTP delivery using tor. Replace the email
2309 address with your own address to test your server. :)
</p
>
2311 <p
>The setup procedure is still to complex, and I hope it can be made
2312 easier and more automatic. Especially the tor setup need more work.
2313 Also, the package include a tor-smtp tool written in C, but its task
2314 should probably be rewritten in some script language to make the deb
2315 architecture independent. It would probably also make the code easier
2316 to review. The tor-smtp tool currently need to listen on a socket for
2317 exim to talk to it and is started using xinetd. It would be better if
2318 no daemon and no socket is needed. I suspect it is possible to get
2319 exim to run a command line tool for delivery instead of talking to a
2320 socket, and hope to figure out how in a future version of this
2323 <p
>Until I wipe my test machine, I can be reached using the
2324 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
2325 SMTorP. :)
</p
>
2330 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
2331 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
2332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
2333 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
2334 <description><p
>If you ever had to moderate a mailman list, like the ones on
2335 alioth.debian.org, you know the web interface is fairly slow to
2336 operate. First you visit one web page, enter the moderation password
2337 and get a new page shown with a list of all the messages to moderate
2338 and various options for each email address. This take a while for
2339 every list you moderate, and you need to do it regularly to do a good
2340 job as a list moderator. But there is a quick alternative,
2341 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
2342 listadmin program
</a
>. It allow you to check lists for new messages
2343 to moderate in a fraction of a second. Here is a test run on two
2344 lists I recently took over:
</p
>
2346 <p
><blockquote
><pre
>
2347 % time listadmin xiph
2348 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2349 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2355 </pre
></blockquote
></p
>
2357 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2358 there are no message in the moderation queue. Every morning I
2359 currently moderate
68 mailman lists, and it normally take around two
2360 minutes. When I took over the two pkg-xiph lists above a few days
2361 ago, there were
400 emails waiting in the moderator queue. It took me
2362 less than
15 minutes to process them all using the listadmin
2365 <p
>If you install
2366 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2367 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2368 with content like this, the moderation task is a breeze:
</p
>
2370 <p
><blockquote
><pre
>
2371 username username@example.org
2374 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2377 adminurl https://{domain}/mailman/admindb/{list}
2378 mailman-list@lists.example.com
2381 other-list@otherserver.example.org
2382 </pre
></blockquote
></p
>
2384 <p
>There are other options to set as well. Check the manual page to
2385 learn the details.
</p
>
2387 <p
>If you are forced to moderate lists on a mailman installation where
2388 the SSL certificate is self signed or not properly signed by a
2389 generally accepted signing authority, you can set a environment
2390 variable when calling listadmin to disable SSL verification:
</p
>
2392 <p
><blockquote
><pre
>
2393 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2394 </pre
></blockquote
></p
>
2396 <p
>If you want to moderate a subset of the lists you take care of, you
2397 can provide an argument to the listadmin script like I do in the
2398 initial screen dump (the xiph argument). Using an argument, only
2399 lists matching the argument string will be processed. This make it
2400 quick to accept messages if you notice the moderation request in your
2403 <p
>Without the listadmin program, I would never be the moderator of
68
2404 mailing lists, as I simply do not have time to spend on that if the
2405 process was any slower. The listadmin program have saved me hours of
2406 time I could spend elsewhere over the years. It truly is nice free
2409 <p
>As usual, if you use Bitcoin and want to show your support of my
2410 activities, please send Bitcoin donations to my address
2411 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2413 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2414 configuration example. Also, I
've been told that the
2415 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2421 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2422 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2423 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2424 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2425 <description><p
>When PXE installing laptops with Debian, I often run into the
2426 problem that the WiFi card require some firmware to work properly.
2427 And it has been a pain to fix this using preseeding in Debian.
2428 Normally something more is needed. But thanks to
2429 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2430 package
</a
> and its recent tasksel extension, it has now become easy
2431 to do this using simple preseeding.
</p
>
2433 <p
>The isenkram-cli package provide tasksel tasks which will install
2434 firmware for the hardware found in the machine (actually, requested by
2435 the kernel modules for the hardware). (It can also install user space
2436 programs supporting the hardware detected, but that is not the focus
2437 of this story.)
</p
>
2439 <p
>To get this working in the default installation, two preeseding
2440 values are needed. First, the isenkram-cli package must be installed
2441 into the target chroot (aka the hard drive) before tasksel is executed
2442 in the pkgsel step of the debian-installer system. This is done by
2443 preseeding the base-installer/includes debconf value to include the
2444 isenkram-cli package. The package name is next passed to debootstrap
2445 for installation. With the isenkram-cli package in place, tasksel
2446 will automatically use the isenkram tasks to detect hardware specific
2447 packages for the machine being installed and install them, because
2448 isenkram-cli contain tasksel tasks.
</p
>
2450 <p
>Second, one need to enable the non-free APT repository, because
2451 most firmware unfortunately is non-free. This is done by preseeding
2452 the apt-mirror-setup step. This is unfortunate, but for a lot of
2453 hardware it is the only option in Debian.
</p
>
2455 <p
>The end result is two lines needed in your preseeding file to get
2456 firmware installed automatically by the installer:
</p
>
2458 <p
><blockquote
><pre
>
2459 base-installer base-installer/includes string isenkram-cli
2460 apt-mirror-setup apt-setup/non-free boolean true
2461 </pre
></blockquote
></p
>
2463 <p
>The current version of isenkram-cli in testing/jessie will install
2464 both firmware and user space packages when using this method. It also
2465 do not work well, so use version
0.15 or later. Installing both
2466 firmware and user space packages might give you a bit more than you
2467 want, so I decided to split the tasksel task in two, one for firmware
2468 and one for user space programs. The firmware task is enabled by
2469 default, while the one for user space programs is not. This split is
2470 implemented in the package currently in unstable.
</p
>
2472 <p
>If you decide to give this a go, please let me know (via email) how
2473 this recipe work for you. :)
</p
>
2475 <p
>So, I bet you are wondering, how can this work. First and
2476 foremost, it work because tasksel is modular, and driven by whatever
2477 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2478 isenkram-cli package place two files for tasksel to find. First there
2479 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2481 <p
><blockquote
><pre
>
2482 Task: isenkram-packages
2484 Description: Hardware specific packages (autodetected by isenkram)
2485 Based on the detected hardware various hardware specific packages are
2487 Test-new-install: show show
2489 Packages: for-current-hardware
2491 Task: isenkram-firmware
2493 Description: Hardware specific firmware packages (autodetected by isenkram)
2494 Based on the detected hardware various hardware specific firmware
2495 packages are proposed.
2496 Test-new-install: mark show
2498 Packages: for-current-hardware-firmware
2499 </pre
></blockquote
></p
>
2501 <p
>The key parts are Test-new-install which indicate how the task
2502 should be handled and the Packages line referencing to a script in
2503 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2504 list of packages to install. The for-current-hardware-firmware script
2505 look like this to list relevant firmware for the machine:
2507 <p
><blockquote
><pre
>
2510 PATH=/usr/sbin:$PATH
2512 isenkram-autoinstall-firmware -l
2513 </pre
></blockquote
></p
>
2515 <p
>With those two pieces in place, the firmware is installed by
2516 tasksel during the normal d-i run. :)
</p
>
2518 <p
>If you want to test what tasksel will install when isenkram-cli is
2519 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2520 --new-install
</tt
> to get the list of packages that tasksel would
2523 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2524 pilots in testing this feature, as isenkram is used there now to
2525 install firmware, replacing the earlier scripts.
</p
>
2530 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2531 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2532 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2533 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2534 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2535 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2536 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2537 on a screen normally showing the bread types and prizes:
</p
>
2539 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2541 <p
>If it had booted as it was supposed to, I would never had known
2542 about this hidden Linux installation. It is interesting what
2543 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
2548 <title>New lsdvd release version
0.17 is ready
</title>
2549 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
2550 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
2551 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
2552 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
2553 got a new set of developers a few weeks ago, after the original
2554 developer decided to step down and pass the project to fresh blood.
2555 This project is now maintained by Petter Reinholdtsen and Steve
2558 <p
>I just wrapped up
2559 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
2560 new lsdvd release
</a
>, available in git or from
2561 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
2562 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
2567 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
2568 <li
>Check for garbage in the program chains, which indicate that a track is
2569 non-existant, to work around additional copy protection
</li
>
2570 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
2571 <li
>Fix pallete display of first entry
</li
>
2572 <li
>Fix include orders
</li
>
2573 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
2574 <li
>Fix the chapter count
</li
>
2575 <li
>Make sure the array size and the array limit used when initialising
2576 the palette size is the same.
</li
>
2577 <li
>Fix array printing.
</li
>
2578 <li
>Correct subsecond calculations.
</li
>
2579 <li
>Add sector information to the output format.
</li
>
2580 <li
>Clean up code to be closer to ANSI C and compile without warnings
2581 with more GCC compiler warnings.
</li
>
2585 <p
>This change bring together patches for lsdvd in use in various
2586 Linux and Unix distributions, as well as patches submitted to the
2587 project the last nine years. Please check it out. :)
</p
>
2592 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
2593 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
2594 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
2595 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
2596 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2597 project
</a
> provide a Linux solution for schools, including a
2598 powerful desktop with education software, a central server providing
2599 web pages, user database, user home directories, central login and PXE
2600 boot of both clients without disk and the installation to install Debian
2601 Edu on machines with disk (and a few other services perhaps to small
2602 to mention here). We in the Debian Edu team are currently working on
2603 the Jessie based version, trying to get everything in shape before the
2604 freeze, to avoid having to maintain our own package repository in the
2606 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
2607 status
</a
> can be seen on the Debian wiki, and there is still heaps of
2608 work left. Some fatal problems block testing, breaking the installer,
2609 but it is possible to work around these to get anyway. Here is a
2610 recipe on how to get the installation limping along.
</p
>
2612 <p
>First, download the test ISO via
2613 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
2614 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
2616 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
2617 The ISO build was broken on Tuesday, so we do not get a new ISO every
2618 12 hours or so, but thankfully the ISO we already got we are able to
2619 install with some tweaking.
</p
>
2621 <p
>When you get to the Debian Edu profile question, go to tty2
2622 (use Alt-Ctrl-F2), run
</p
>
2624 <p
><blockquote
><pre
>
2625 nano /usr/bin/edu-eatmydata-install
2626 </pre
></blockquote
></p
>
2628 <p
>and add
'exit
0' as the second line, disabling the eatmydata
2629 optimization. Return to the installation, select the profile you want
2630 and continue. Without this change, exim4-config will fail to install
2631 due to a known bug in eatmydata.
</p
>
2633 <p
>When you get the grub question at the end, answer /dev/sda (or if
2634 this do not work, figure out what your correct value would be. All my
2635 test machines need /dev/sda, so I have no advice if it do not fit
2636 your need.
</p
>
2638 <p
>If you installed a profile including a graphical desktop, log in as
2639 root after the initial boot from hard drive, and install the
2640 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2641 or mate. If you want several desktop options, install more than one
2642 metapackage. Once this is done, reboot and you should have a working
2643 graphical login screen. This workaround should no longer be needed
2644 once the education-tasks package version
1.801 enter testing in two
2647 <p
>I believe the ISO build will start working on two days when the new
2648 tasksel package enter testing and Steve McIntyre get a chance to
2649 update the debian-cd git repository. The eatmydata, grub and desktop
2650 issues are already fixed in unstable and testing, and should show up
2651 on the ISO as soon as the ISO build start working again. Well the
2652 eatmydata optimization is really just disabled. The proper fix
2653 require an upload by the eatmydata maintainer applying the patch
2654 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
2655 The rest have proper fixes in unstable.
</p
>
2657 <p
>I hope this get you going with the installation testing, as we are
2658 quickly running out of time trying to get our Jessie based
2659 installation ready before the distribution freeze in a month.
</p
>
2664 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
2665 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
2666 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
2667 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
2668 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
2669 to handle my fairly large DVD collection. It is a nice command line
2670 tool to get details about a DVD, like title, tracks, track length,
2671 etc, in XML, Perl or human readable format. But lsdvd have not seen
2672 any new development since
2006 and had a few irritating bugs affecting
2673 its use with some DVDs. Upstream seemed to be dead, and in January I
2674 sent a small probe asking for a version control repository for the
2675 project, without any reply. But I use it regularly and would like to
2676 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
2677 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
2678 the project admin, and after getting a reply from him explaining that
2679 he was no longer interested in the project, I asked if I could take
2680 over. And yesterday, I became project admin.
</p
>
2682 <p
>I
've been in touch with a Gentoo developer and the Debian
2683 maintainer interested in joining forces to maintain the upstream
2684 project, and I hope we can get a new release out fairly quickly,
2685 collecting the patches spread around on the internet into on place.
2686 I
've added the relevant Debian patches to the freshly created git
2687 repository, and expect the Gentoo patches to make it too. If you got
2688 a DVD collection and care about command line tools, check out
2689 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
2690 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
2691 list
</a
>. :)
</p
>
2696 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
2697 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
2698 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
2699 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
2700 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
2701 a lot quicker. When we install more than
2000 packages in
2702 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
2703 tasksel in the installer, unpacking the binary packages take forever.
2704 A part of the slow I/O issue was discussed in
2705 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
2706 much file system sync-ing done by dpkg, which is the package
2707 responsible for unpacking the binary packages. Other parts (like code
2708 executed by postinst scripts) might also sync to disk during
2709 installation. All this sync-ing to disk do not really make sense to
2710 me. If the machine crash half-way through, I start over, I do not try
2711 to salvage the half installed system. So the failure sync-ing is
2712 supposed to protect against, hardware or system crash, is not really
2713 relevant while the installer is running.
</p
>
2715 <p
>A few days ago, I thought of a way to get rid of all the file
2716 system sync()-ing in a fairly non-intrusive way, without the need to
2717 change the code in several packages. The idea is not new, but I have
2718 not heard anyone propose the approach using dpkg-divert before. It
2719 depend on the small and clever package
2720 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
2721 uses LD_PRELOAD to replace the system functions for syncing data to
2722 disk with functions doing nothing, thus allowing programs to live
2723 dangerous while speeding up disk I/O significantly. Instead of
2724 modifying the implementation of dpkg, apt and tasksel (which are the
2725 packages responsible for selecting, fetching and installing packages),
2726 it occurred to me that we could just divert the programs away, replace
2727 them with a simple shell wrapper calling
2728 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
2729 Two days ago I decided to test the idea, and wrapped up a simple
2730 implementation for the Debian Edu udeb.
</p
>
2732 <p
>The effect was stunning. In my first test it reduced the running
2733 time of the pkgsel step (installing tasks) from
64 to less than
44
2734 minutes (
20 minutes shaved off the installation) on an old Dell
2735 Latitude D505 machine. I am not quite sure what the optimised time
2736 would have been, as I messed up the testing a bit, causing the debconf
2737 priority to get low enough for two questions to pop up during
2738 installation. As soon as I saw the questions I moved the installation
2739 along, but do not know how long the question were holding up the
2740 installation. I did some more measurements using Debian Edu Jessie,
2741 and got these results. The time measured is the time stamp in
2742 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
2743 "pkgsel: finishing up
" lines, if you want to do the same measurement
2744 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2745 timing thus do not depend on how quickly the user handle the tasksel
2748 <p
><table
>
2751 <th
>Machine/setup
</th
>
2752 <th
>Original tasksel
</th
>
2753 <th
>Optimised tasksel
</th
>
2754 <th
>Reduction
</th
>
2758 <td
>Latitude D505 Main+LTSP LXDE
</td
>
2759 <td
>64 min (
07:
46-
08:
50)
</td
>
2760 <td
><44 min (
11:
27-
12:
11)
</td
>
2761 <td
>>20 min
18%
</td
>
2765 <td
>Latitude D505 Roaming LXDE
</td
>
2766 <td
>57 min (
08:
48-
09:
45)
</td
>
2767 <td
>34 min (
07:
43-
08:
17)
</td
>
2768 <td
>23 min
40%
</td
>
2772 <td
>Latitude D505 Minimal
</td
>
2773 <td
>22 min (
10:
37-
10:
59)
</td
>
2774 <td
>11 min (
11:
16-
11:
27)
</td
>
2775 <td
>11 min
50%
</td
>
2779 <td
>Thinkpad X200 Minimal
</td
>
2780 <td
>6 min (
08:
19-
08:
25)
</td
>
2781 <td
>4 min (
08:
04-
08:
08)
</td
>
2782 <td
>2 min
33%
</td
>
2786 <td
>Thinkpad X200 Roaming KDE
</td
>
2787 <td
>19 min (
09:
21-
09:
40)
</td
>
2788 <td
>15 min (
10:
25-
10:
40)
</td
>
2789 <td
>4 min
21%
</td
>
2792 </table
></p
>
2794 <p
>The test is done using a netinst ISO on a USB stick, so some of the
2795 time is spent downloading packages. The connection to the Internet
2796 was
100Mbit/s during testing, so downloading should not be a
2797 significant factor in the measurement. Download typically took a few
2798 seconds to a few minutes, depending on the amount of packages being
2799 installed.
</p
>
2801 <p
>The speedup is implemented by using two hooks in
2802 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
2803 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
2804 finish-install.d hook to remove the divert at the end of the
2805 installation. I picked the pre-pkgsel.d hook instead of the
2806 post-base-installer.d hook because I test using an ISO without the
2807 eatmydata package included, and the post-base-installer.d hook in
2808 Debian Edu can only operate on packages included in the ISO. The
2809 negative effect of this is that I am unable to activate this
2810 optimization for the kernel installation step in d-i. If the code is
2811 moved to the post-base-installer.d hook, the speedup would be larger
2812 for the entire installation.
</p
>
2814 <p
>I
've implemented this in the
2815 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
2816 git repository, and plan to provide the optimization as part of the
2817 Debian Edu installation. If you want to test this yourself, you can
2818 create two files in the installer (or in an udeb). One shell script
2819 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
2821 <p
><blockquote
><pre
>
2824 . /usr/share/debconf/confmodule
2826 logger -t my-pkgsel
"info: $*
"
2829 logger -t my-pkgsel
"error: $*
"
2831 override_install() {
2832 apt-install eatmydata || true
2833 if [ -x /target/usr/bin/eatmydata ] ; then
2834 for bin in dpkg apt-get aptitude tasksel ; do
2836 # Test that the file exist and have not been diverted already.
2837 if [ -f /target$file ] ; then
2838 info
"diverting $file using eatmydata
"
2839 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
2840 > /target$file.edu
2841 chmod
755 /target$file.edu
2842 in-target dpkg-divert --package debian-edu-config \
2843 --rename --quiet --add $file
2844 ln -sf ./$bin.edu /target$file
2846 error
"unable to divert $file, as it is missing.
"
2850 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
2855 </pre
></blockquote
></p
>
2857 <p
>To clean up, another shell script should go into
2858 /usr/lib/finish-install.d/ with code like this:
2860 <p
><blockquote
><pre
>
2862 . /usr/share/debconf/confmodule
2864 logger -t my-finish-install
"error: $@
"
2866 remove_install_override() {
2867 for bin in dpkg apt-get aptitude tasksel ; do
2869 if [ -x /target$file.edu ] ; then
2871 in-target dpkg-divert --package debian-edu-config \
2872 --rename --quiet --remove $file
2875 error
"Missing divert for $file.
"
2878 sync # Flush file buffers before continuing
2881 remove_install_override
2882 </pre
></blockquote
></p
>
2884 <p
>In Debian Edu, I placed both code fragments in a separate script
2885 edu-eatmydata-install and call it from the pre-pkgsel.d and
2886 finish-install.d scripts.
</p
>
2888 <p
>By now you might ask if this change should get into the normal
2889 Debian installer too? I suspect it should, but am not sure the
2890 current debian-installer coordinators find it useful enough. It also
2891 depend on the side effects of the change. I
'm not aware of any, but I
2892 guess we will see if the change is safe after some more testing.
2893 Perhaps there is some package in Debian depending on sync() and
2894 fsync() having effect? Perhaps it should go into its own udeb, to
2895 allow those of us wanting to enable it to do so without affecting
2898 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
2899 will break installation of all programs using gnutls because of
2900 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
2901 eatmydata package in Debian will solve it.
</p
>
2903 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
2904 the optimization work again. And I have discovered that the
2905 dpkg-divert trick is not really needed and implemented a slightly
2906 simpler approach as part of the debian-edu-install package. See
2907 tools/edu-eatmydata-install in the source package.
</p
>
2909 <p
>Update
2014-
11-
11: Unfortunately, a new
2910 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
2911 triggering on i386 made it into testing, and broke this installation
2912 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
2913 request
768893</a
> is accepted, it should be working again.
</p
>
2918 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
2919 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
2920 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
2921 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
2922 <description><p
>Yesterday, I had the pleasure of attending a talk with the
2923 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
2924 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
2925 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
2926 learn that there is a large set of publicly available key servers to
2927 use when looking for peoples public key. So far I have used
2928 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2929 were misbehaving, but those days are ended. The servers I have used
2930 up until yesterday have been slow and some times unavailable. I hope
2931 those problems are gone now.
</p
>
2933 <p
>Behind the round robin DNS entry of the
2934 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
2935 there is a pool of more than
100 keyservers which are checked every
2936 day to ensure they are well connected and up to date. It must be
2937 better than what I have used so far. :)
</p
>
2939 <p
>Yesterdays speaker told me that the service is the default
2940 keyserver provided by the default configuration in GnuPG, but this do
2941 not seem to be used in Debian. Perhaps it should?
</p
>
2943 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
2946 <p
><blockquote
><pre
>
2947 keyserver pool.sks-keyservers.net
2948 </pre
></blockquote
></p
>
2950 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
2951 entries in DNS. Just for fun, I did just that at work, so now every
2952 user of GnuPG at the University of Oslo should find a OpenGPG
2953 keyserver automatically should their need it:
</p
>
2955 <p
><blockquote
><pre
>
2956 % host -t srv _pgpkey-http._tcp.uio.no
2957 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
2959 </pre
></blockquote
></p
>
2961 <p
>Now if only
2962 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
2963 HKP lookup protocol
</a
> supported finding signature paths, I would be
2964 very happy. It can look up a given key or search for a user ID, but I
2965 normally do not want that, but to find a trust path from my key to
2966 another key. Given a user ID or key ID, I would like to find (and
2967 download) the keys representing a signature path from my key to the
2968 key in question, to be able to get a trust path between the two keys.
2969 This is as far as I can tell not possible today. Perhaps something
2970 for a future version of the protocol?
</p
>
2975 <title>From English wiki to translated PDF and epub via Docbook
</title>
2976 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
2977 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
2978 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
2979 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2980 project
</a
> provide an instruction manual for teachers, system
2981 administrators and other users that contain useful tips for setting up
2982 and maintaining a Debian Edu installation. This text is about how the
2983 text processing of this manual is handled in the project.
</p
>
2985 <p
>One goal of the project is to provide information in the native
2986 language of its users, and for this we need to handle translations.
2987 But we also want to make sure each language contain the same
2988 information, so for this we need a good way to keep the translations
2989 in sync. And we want it to be easy for our users to improve the
2990 documentation, avoiding the need to learn special formats or tools to
2991 contribute, and the obvious way to do this is to make it possible to
2992 edit the documentation using a web browser. We also want it to be
2993 easy for translators to keep the translation up to date, and give them
2994 help in figuring out what need to be translated. Here is the list of
2995 tools and the process we have found trying to reach all these
2998 <p
>We maintain the authoritative source of our manual in the
2999 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3000 wiki
</a
>, as several wiki pages written in English. It consist of one
3001 front page with references to the different chapters, several pages
3002 for each chapter, and finally one
"collection page
" gluing all the
3003 chapters together into one large web page (aka
3004 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3005 AllInOne page
</a
>). The AllInOne page is the one used for further
3006 processing and translations. Thanks to the fact that the
3007 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3008 wiki.debian.org support exporting pages in
3009 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3010 the list of pages to export using the raw version of the AllInOne
3011 page, loop over each of them to generate a Docbook XML version of the
3012 manual. This process also download images and transform image
3013 references to use the locally downloaded images. The generated
3014 Docbook XML files are slightly broken, so some post-processing is done
3015 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3016 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3017 a handfull of images. The XML file can now be used to generate PDF, HTML
3018 and epub versions of the English manual. This is the basic step of
3019 our process, making PDF (using dblatex), HTML (using xsltproc) and
3020 epub (using dbtoepub) version from Docbook XML, and the resulting files
3021 are placed in the debian-edu-doc-en binary package.
</p
>
3023 <p
>But English documentation is not enough for us. We want translated
3024 documentation too, and we want to make it easy for translators to
3025 track the English original. For this we use the
3026 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3027 which allow us to transform the English Docbook XML file into a
3028 translation file (a .pot file), usable with the normal gettext based
3029 translation tools used by those translating free software. The pot
3030 file is used to create and maintain translation files (several .po
3031 files), which the translations update with the native language
3032 translations of all titles, paragraphs and blocks of text in the
3033 original. The next step is combining the original English Docbook XML
3034 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3035 create a translated Docbook XML file (in this case
3036 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3037 translated, if the translation is not complete) Docbook XML file can
3038 then be used like the original to create a PDF, HTML and epub version
3039 of the documentation.
</p
>
3041 <p
>The translators use different tools to edit the .po files. We
3043 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3044 while some use emacs and vi, others can use web based editors like
3045 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3046 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3047 is where the .po file end up, in our git repository. Updated
3048 translations can either be committed directly to git, or submitted as
3049 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3050 against the debian-edu-doc package
</a
>.
</p
>
3052 <p
>One challenge is images, which both might need to be translated (if
3053 they show translated user applications), and are needed in different
3054 formats when creating PDF and HTML versions (epub is a HTML version in
3055 this regard). For this we transform the original PNG images to the
3056 needed density and format during build, and have a way to provide
3057 translated images by storing translated versions in
3058 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3059 package maintainers know more.
</p
>
3061 <p
>If you wonder what the result look like, we provide
3062 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3063 of the documentation packages on the web
</a
>. See for example the
3064 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3065 PDF version
</a
> or the
3066 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3067 HTML version
</a
>. We do not yet build the epub version by default,
3068 but perhaps it will be done in the future.
</p
>
3070 <p
>To learn more, check out
3071 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3072 debian-edu-doc package
</a
>,
3073 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3074 manual on the wiki
</a
> and
3075 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3076 translation instructions
</a
> in the manual.
</p
>
3081 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3082 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3083 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3084 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3085 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3086 related packages relevant for the computer installed automatically.
3087 So I implemented one, using
3088 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3089 package
</a
>. To use it, install the tasksel and isenkram packages and
3090 run tasksel as user root. You should be presented with a new option,
3091 "Hardware specific packages (autodetected by isenkram)
". When you
3092 select it, tasksel will install the packages isenkram claim is fit for
3093 the current hardware, hot pluggable or not.
<p
>
3095 <p
>The implementation is in two files, one is the tasksel menu entry
3096 description, and the other is the script used to extract the list of
3097 packages to install. The first part is in
3098 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3101 <p
><blockquote
><pre
>
3104 Description: Hardware specific packages (autodetected by isenkram)
3105 Based on the detected hardware various hardware specific packages are
3107 Test-new-install: mark show
3109 Packages: for-current-hardware
3110 </pre
></blockquote
></p
>
3112 <p
>The second part is in
3113 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3116 <p
><blockquote
><pre
>
3121 isenkram-autoinstall-firmware -l
3123 </pre
></blockquote
></p
>
3125 <p
>All in all, a very short and simple implementation making it
3126 trivial to install the hardware dependent package we all may want to
3127 have installed on our machines. I
've not been able to find a way to
3128 get tasksel to tell you exactly which packages it plan to install
3129 before doing the installation. So if you are curious or careful,
3130 check the output from the isenkram-* command line tools first.
</p
>
3132 <p
>The information about which packages are handling which hardware is
3133 fetched either from the isenkram package itself in
3134 /usr/share/isenkram/, from git.debian.org or from the APT package
3135 database (using the Modaliases header). The APT package database
3136 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3137 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3138 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3139 the python-apt code (bug
3140 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3141 workaround I was able to get rid of the file descriptor leak and
3142 reduce the memory leak from ~
30 MiB per hardware detection down to
3143 around
2 MiB per hardware detection. It should make the desktop
3144 daemon a lot more useful. The fix is in version
0.7 uploaded to
3145 unstable today.
</p
>
3147 <p
>I believe the current way of mapping hardware to packages in
3148 Isenkram is is a good draft, but in the future I expect isenkram to
3149 use the AppStream data source for this. A proposal for getting proper
3150 AppStream support into Debian is floating around as
3151 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3152 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3153 project
</a
> will take place this summer to improve the situation. I
3154 look forward to seeing the result, and welcome patches for isenkram to
3155 start using the information when it is ready.
</p
>
3157 <p
>If you want your package to map to some specific hardware, either
3158 add a
"Xb-Modaliases
" header to your control file like I did in
3159 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
3160 package
</a
> or submit a bug report with the details to the isenkram
3162 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
3163 blog posts tagged isenkram
</a
> for details on the notation. I expect
3164 the information will be migrated to AppStream eventually, but for the
3165 moment I got no better place to store it.
</p
>
3170 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3171 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3172 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3173 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3174 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3175 project
</a
> is working on providing the software and hardware to make
3176 it easy for non-technical people to host their data and communication
3177 at home, and being able to communicate with their friends and family
3178 encrypted and away from prying eyes. It is still going strong, and
3179 today a major mile stone was reached.
</p
>
3181 <p
>Today, the last of the packages currently used by the project to
3182 created the system images were accepted into Debian Unstable. It was
3183 the freedombox-setup package, which is used to configure the images
3184 during build and on the first boot. Now all one need to get going is
3185 the build code from the freedom-maker git repository and packages from
3186 Debian. And once the freedombox-setup package enter testing, we can
3187 build everything directly from Debian. :)
</p
>
3189 <p
>Some key packages used by Freedombox are
3190 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3191 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3192 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3193 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3194 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3195 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3196 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3197 are plans to integrate more packages into the setup. User
3198 documentation is maintained on the Debian wiki. Please
3199 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3200 the manual
</a
> and help us improve it.
</p
>
3202 <p
>To test for yourself and create boot images with the FreedomBox
3203 setup, run this on a Debian machine using a user with sudo rights to
3204 become root:
</p
>
3206 <p
><pre
>
3207 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3208 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3210 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3212 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3213 </pre
></p
>
3215 <p
>Root access is needed to run debootstrap and mount loopback
3216 devices. See the README in the freedom-maker git repo for more
3217 details on the build. If you do not want all three images, trim the
3218 make line. Note that the virtualbox-image target is not really
3219 virtualbox specific. It create a x86 image usable in kvm, qemu,
3220 vmware and any other x86 virtual machine environment. You might need
3221 the version of vmdebootstrap in Jessie to get the build working, as it
3222 include fixes for a race condition with kpartx.
</p
>
3224 <p
>If you instead want to install using a Debian CD and the preseed
3225 method, boot a Debian Wheezy ISO and use this boot argument to load
3226 the preseed values:
</p
>
3228 <p
><pre
>
3229 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3230 </pre
></p
>
3232 <p
>I have not tested it myself the last few weeks, so I do not know if
3233 it still work.
</p
>
3235 <p
>If you wonder how to help, one task you could look at is using
3236 systemd as the boot system. It will become the default for Linux in
3237 Jessie, so we need to make sure it is usable on the Freedombox. I did
3238 a simple test a few weeks ago, and noticed dnsmasq failed to start
3239 during boot when using systemd. I suspect there are other problems
3240 too. :) To detect problems, there is a test suite included, which can
3241 be run from the plinth web interface.
</p
>
3243 <p
>Give it a go and let us know how it goes on the mailing list, and help
3244 us get the new release published. :) Please join us on
3245 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3246 irc.debian.org)
</a
> and
3247 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3248 mailing list
</a
> if you want to help make this vision come true.
</p
>
3253 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
3254 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
3255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
3256 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
3257 <description><p
>For a while now, I have been looking for a sensible offsite backup
3258 solution for use at home. My requirements are simple, it must be
3259 cheap and locally encrypted (in other words, I keep the encryption
3260 keys, the storage provider do not have access to my private files).
3261 One idea me and my friends had many years ago, before the cloud
3262 storage providers showed up, was to use Google mail as storage,
3263 writing a Linux block device storing blocks as emails in the mail
3264 service provided by Google, and thus get heaps of free space. On top
3265 of this one can add encryption, RAID and volume management to have
3266 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3267 I never found time to implement such system. But the last few weeks I
3268 have looked at a system called
3269 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
3270 mounted network backed file system with the features I need.
</p
>
3272 <p
>S3QL is a fuse file system with a local cache and cloud storage,
3273 handling several different storage providers, any with Amazon S3,
3274 Google Drive or OpenStack API. There are heaps of such storage
3275 providers. S3QL can also use a local directory as storage, which
3276 combined with sshfs allow for file storage on any ssh server. S3QL
3277 include support for encryption, compression, de-duplication, snapshots
3278 and immutable file systems, allowing me to mount the remote storage as
3279 a local mount point, look at and use the files as if they were local,
3280 while the content is stored in the cloud as well. This allow me to
3281 have a backup that should survive fire. The file system can not be
3282 shared between several machines at the same time, as only one can
3283 mount it at the time, but any machine with the encryption key and
3284 access to the storage service can mount it if it is unmounted.
</p
>
3286 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
3287 package is included already. So to get started, run
<tt
>apt-get
3288 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
3289 Greenqloud, after reading their nice recipe on
3290 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
3291 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
3292 in Iceland more than those in USA when it come to keeping my personal
3293 data safe and private, and thus would rather spend money on a company
3294 in Iceland. Another nice recipe is available from the article
3295 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
3296 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
3297 Admin magazine. When the provider is picked, figure out how to get
3298 the API key needed to connect to the storage API. With Greencloud,
3299 the key did not show up until I had added payment details to my
3302 <p
>Armed with the API access details, it is time to create the file
3303 system. First, create a new bucket in the cloud. This bucket is the
3304 file system storage area. I picked a bucket name reflecting the
3305 machine that was going to store data there, but any name will do.
3306 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
3307 the API login and password, and a locally created password. Store it
3308 all in ~root/.s3ql/authinfo2 like this:
3310 <p
><blockquote
><pre
>
3312 storage-url: s3c://s.greenqloud.com:
443/bucket-name
3313 backend-login: API-login
3314 backend-password: API-password
3315 fs-passphrase: local-password
3316 </pre
></blockquote
></p
>
3318 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
3319 but any sensible way to create a fairly random password should do it.
3320 Armed with these details, it is now time to run mkfs, entering the API
3321 details and password to create it:
</p
>
3323 <p
><blockquote
><pre
>
3324 # mkdir -m
700 /var/lib/s3ql-cache
3325 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3326 --ssl s3c://s.greenqloud.com:
443/bucket-name
3327 Enter backend login:
3328 Enter backend password:
3329 Before using S3QL, make sure to read the user
's guide, especially
3330 the
'Important Rules to Avoid Loosing Data
' section.
3331 Enter encryption password:
3332 Confirm encryption password:
3333 Generating random encryption key...
3334 Creating metadata tables...
3344 Compressing and uploading metadata...
3345 Wrote
0.00 MB of compressed metadata.
3346 #
</pre
></blockquote
></p
>
3348 <p
>The next step is mounting the file system to make the storage available.
3350 <p
><blockquote
><pre
>
3351 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3352 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3353 Using
4 upload threads.
3354 Downloading and decompressing metadata...
3364 Mounting filesystem...
3366 Filesystem Size Used Avail Use% Mounted on
3367 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3369 </pre
></blockquote
></p
>
3371 <p
>The file system is now ready for use. I use rsync to store my
3372 backups in it, and as the metadata used by rsync is downloaded at
3373 mount time, no network traffic (and storage cost) is triggered by
3374 running rsync. To unmount, one should not use the normal umount
3375 command, as this will not flush the cache to the cloud storage, but
3376 instead running the umount.s3ql command like this:
3378 <p
><blockquote
><pre
>
3381 </pre
></blockquote
></p
>
3383 <p
>There is a fsck command available to check the file system and
3384 correct any problems detected. This can be used if the local server
3385 crashes while the file system is mounted, to reset the
"already
3386 mounted
" flag. This is what it look like when processing a working
3387 file system:
</p
>
3389 <p
><blockquote
><pre
>
3390 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3391 Using cached metadata.
3392 File system seems clean, checking anyway.
3393 Checking DB integrity...
3394 Creating temporary extra indices...
3395 Checking lost+found...
3396 Checking cached objects...
3397 Checking names (refcounts)...
3398 Checking contents (names)...
3399 Checking contents (inodes)...
3400 Checking contents (parent inodes)...
3401 Checking objects (reference counts)...
3402 Checking objects (backend)...
3403 ..processed
5000 objects so far..
3404 ..processed
10000 objects so far..
3405 ..processed
15000 objects so far..
3406 Checking objects (sizes)...
3407 Checking blocks (referenced objects)...
3408 Checking blocks (refcounts)...
3409 Checking inode-block mapping (blocks)...
3410 Checking inode-block mapping (inodes)...
3411 Checking inodes (refcounts)...
3412 Checking inodes (sizes)...
3413 Checking extended attributes (names)...
3414 Checking extended attributes (inodes)...
3415 Checking symlinks (inodes)...
3416 Checking directory reachability...
3417 Checking unix conventions...
3418 Checking referential integrity...
3419 Dropping temporary indices...
3420 Backing up old metadata...
3430 Compressing and uploading metadata...
3431 Wrote
0.89 MB of compressed metadata.
3433 </pre
></blockquote
></p
>
3435 <p
>Thanks to the cache, working on files that fit in the cache is very
3436 quick, about the same speed as local file access. Uploading large
3437 amount of data is to me limited by the bandwidth out of and into my
3438 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3439 which is very close to my upload speed, and downloading the same
3440 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3441 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3442 network, not the file system code. I do not know what a good cache
3443 size would be, but suspect that the cache should e larger than your
3444 working set.
</p
>
3446 <p
>I mentioned that only one machine can mount the file system at the
3447 time. If another machine try, it is told that the file system is
3450 <p
><blockquote
><pre
>
3451 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3452 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3453 Using
8 upload threads.
3454 Backend reports that fs is still mounted elsewhere, aborting.
3456 </pre
></blockquote
></p
>
3458 <p
>The file content is uploaded when the cache is full, while the
3459 metadata is uploaded once every
24 hour by default. To ensure the
3460 file system content is flushed to the cloud, one can either umount the
3461 file system, or ask S3QL to flush the cache and metadata using
3464 <p
><blockquote
><pre
>
3465 # s3qlctrl upload-meta /s3ql
3466 # s3qlctrl flushcache /s3ql
3468 </pre
></blockquote
></p
>
3470 <p
>If you are curious about how much space your data uses in the
3471 cloud, and how much compression and deduplication cut down on the
3472 storage usage, you can use s3qlstat on the mounted file system to get
3475 <p
><blockquote
><pre
>
3477 Directory entries:
9141
3480 Total data size:
22049.38 MB
3481 After de-duplication:
21955.46 MB (
99.57% of total)
3482 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
3483 Database size:
2.39 MB (uncompressed)
3484 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3486 </pre
></blockquote
></p
>
3488 <p
>I mentioned earlier that there are several possible suppliers of
3489 storage. I did not try to locate them all, but am aware of at least
3490 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
3491 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
3492 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
3493 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
3494 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
3495 accept payment in Bitcoin. Pick one that suit your need. Some of
3496 them provide several GiB of free storage, but the prize models are
3497 quite different and you will have to figure out what suits you
3500 <p
>While researching this blog post, I had a look at research papers
3501 and posters discussing the S3QL file system. There are several, which
3502 told me that the file system is getting a critical check by the
3503 science community and increased my confidence in using it. One nice
3505 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3506 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3507 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3508 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3509 and Pamela Smith. Please have a look.
</p
>
3511 <p
>Given my problems with different file systems earlier, I decided to
3512 check out the mounted S3QL file system to see if it would be usable as
3513 a home directory (in other word, that it provided POSIX semantics when
3514 it come to locking and umask handling etc). Running
3515 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3516 test code to check file system semantics
</a
>, I was happy to discover that
3517 no error was found. So the file system can be used for home
3518 directories, if one chooses to do so.
</p
>
3520 <p
>If you do not want a locally file system, and want something that
3521 work without the Linux fuse file system, I would like to mention the
3522 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3523 provide locally encrypted backup using a command line client. It have
3524 a nicer access control system, where one can split out read and write
3525 access, allowing some systems to write to the backup and others to
3526 only read from it.
</p
>
3528 <p
>As usual, if you use Bitcoin and want to show your support of my
3529 activities, please send Bitcoin donations to my address
3530 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3535 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3536 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3537 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3538 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3539 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3540 project
</a
> is working on providing the software and hardware for
3541 making it easy for non-technical people to host their data and
3542 communication at home, and being able to communicate with their
3543 friends and family encrypted and away from prying eyes. It has been
3544 going on for a while, and is slowly progressing towards a new test
3545 release (
0.2).
</p
>
3547 <p
>And what day could be better than the Pi day to announce that the
3548 new version will provide
"hard drive
" / SD card / USB stick images for
3549 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3550 system), and can also be installed using a Debian installer preseed
3551 file. The Debian based Freedombox is now based on Debian Jessie,
3552 where most of the needed packages used are already present. Only one,
3553 the freedombox-setup package, is missing. To try to build your own
3554 boot image to test the current status, fetch the freedom-maker scripts
3556 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
3557 with a user with sudo access to become root:
3560 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3562 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3563 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3565 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3568 <p
>Root access is needed to run debootstrap and mount loopback
3569 devices. See the README for more details on the build. If you do not
3570 want all three images, trim the make line. But note that thanks to
<a
3571 href=
"https://bugs.debian.org/
741407">a race condition in
3572 vmdebootstrap
</a
>, the build might fail without the patch to the
3573 kpartx call.
</p
>
3575 <p
>If you instead want to install using a Debian CD and the preseed
3576 method, boot a Debian Wheezy ISO and use this boot argument to load
3577 the preseed values:
</p
>
3580 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3583 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
3584 recently introduced bug in apt in Jessie
</a
>, the installer will
3585 currently hang while setting up APT sources. Killing the
3586 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
3587 installation will get the installation going. This affect all
3588 installations in Jessie, and I expect it will be fixed soon.
</p
>
3590 <p
>Give it a go and let us know how it goes on the mailing list, and help
3591 us get the new release published. :) Please join us on
3592 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3593 irc.debian.org)
</a
> and
3594 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3595 mailing list
</a
> if you want to help make this vision come true.
</p
>
3600 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
3601 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
3602 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
3603 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
3604 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
3605 innetgr tools, because I needed them in
3606 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
3607 ng-utils, and it has served me well. I placed the project under the
3608 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
3609 repository. But many years ago, the CVS repository was dropped (lost,
3610 not migrated to new hardware, not sure), and the project have lacked a
3611 proper home since then.
</p
>
3613 <p
>Last summer, I had a look at the package and made a new release
3614 fixing a irritating crash bug, but was unable to store the changes in
3615 a proper source control system. I applied for a project on
3616 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
3617 to follow up on it. Until today. :)
</p
>
3619 <p
>After many hours of cleaning and migration, the ng-utils project
3620 now have a new home, and a git repository with the highlight of the
3621 history of the project. I published all release tarballs and imported
3622 them into the git repository. As the project is really stable and not
3623 expected to gain new features any time soon, I decided to make a new
3624 release and call it
1.0. Visit the new project home on
3625 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
3626 if you want to check it out. The new version is also uploaded into
3627 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
3632 <title>Testing sysvinit from experimental in Debian Hurd
</title>
3633 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
3634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
3635 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
3636 <description><p
>A few days ago I decided to try to help the Hurd people to get
3637 their changes into sysvinit, to allow them to use the normal sysvinit
3638 boot system instead of their old one. This follow up on the
3639 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
3640 Google Summer of Code work
</a
> done last summer by Justus Winter to
3641 get Debian on Hurd working more like Debian on Linux. To get started,
3642 I downloaded a prebuilt hard disk image from
3643 <a href=
"http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz
">http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz
</a
>,
3644 and started it using virt-manager.
</p
>
3646 <p
>The first think I had to do after logging in (root without any
3647 password) was to get the network operational. I followed
3648 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
3649 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
3650 commands as root to get the machine to accept a IP address from the
3651 kvm internal DHCP server:
</p
>
3653 <p
><blockquote
><pre
>
3654 settrans -fgap /dev/netdde /hurd/netdde
3655 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
3656 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
3658 </pre
></blockquote
></p
>
3660 <p
>After this, the machine had internet connectivity, and I could
3661 upgrade it and install the sysvinit packages from experimental and
3662 enable it as the default boot system in Hurd.
</p
>
3664 <p
>But before I did that, I set a password on the root user, as ssh is
3665 running on the machine it for ssh login to work a password need to be
3666 set. Also, note that a bug somewhere in openssh on Hurd block
3667 compression from working. Remember to turn that off on the client
3670 <p
>Run these commands as root to upgrade and test the new sysvinit
3673 <p
><blockquote
><pre
>
3674 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
3675 deb http://http.debian.net/debian/ experimental main
3678 apt-get dist-upgrade
3679 apt-get install -t experimental initscripts sysv-rc sysvinit \
3680 sysvinit-core sysvinit-utils
3681 update-alternatives --config runsystem
3682 </pre
></blockquote
></p
>
3684 <p
>To reboot after switching boot system, you have to use
3685 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
3686 yet a sysvinit process able to receive the signals from the normal
3687 'reboot
' command. After switching to sysvinit as the boot system,
3688 upgrading every package and rebooting, the network come up with DHCP
3689 after boot as it should, and the settrans/pkill hack mentioned at the
3690 start is no longer needed. But for some strange reason, there are no
3691 longer any login prompt in the virtual console, so I logged in using
3694 <p
>Note that there are some race conditions in Hurd making the boot
3695 fail some times. No idea what the cause is, but hope the Hurd porters
3696 figure it out. At least Justus said on IRC (#debian-hurd on
3697 irc.debian.org) that they are aware of the problem. A way to reduce
3698 the impact is to upgrade to the Hurd packages built by Justus by
3699 adding this repository to the machine:
</p
>
3701 <p
><blockquote
><pre
>
3702 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
3703 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3705 </pre
></blockquote
></p
>
3707 <p
>At the moment the prebuilt virtual machine get some packages from
3708 http://ftp.debian-ports.org/debian, because some of the packages in
3709 unstable do not yet include the required patches that are lingering in
3710 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
3712 <p
><blockquote
><pre
>
3713 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
3714 i emacs - GNU Emacs editor (metapackage)
3715 i gdb - GNU Debugger
3716 i hurd-recommended - Miscellaneous translators
3717 i isc-dhcp-client - ISC DHCP client
3718 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3719 i libc-bin - Embedded GNU C Library: Binaries
3720 i libc-dev-bin - Embedded GNU C Library: Development binaries
3721 i libc0.3 - Embedded GNU C Library: Shared libraries
3722 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3723 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3724 i multiarch-support - Transitional package to ensure multiarch compatibilit
3725 i A x11-common - X Window System (X.Org) infrastructure
3726 i xorg - X.Org X Window System
3727 i A xserver-xorg - X.Org X server
3728 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3730 </pre
></blockquote
></p
>
3732 <p
>All in all, testing hurd has been an interesting experience. :)
3733 X.org did not work out of the box and I never took the time to follow
3734 the porters instructions to fix it. This time I was interested in the
3735 command line stuff.
<p
>
3740 <title>New chrpath release
0.16</title>
3741 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
3742 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
3743 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
3744 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
3745 find problems in C, C++ and Java code using static source code
3746 analysis. It can detect a lot of different problems, and is very
3747 useful to find memory and locking bugs in the error handling part of
3748 the source. The company behind it provide
3749 <a href=
"https://scan.coverity.com/
">check of free software projects as
3750 a community service
</a
>, and many hundred free software projects are
3751 already checked. A few days ago I decided to have a closer look at
3752 the Coverity system, and discovered that the
3753 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
3754 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
3755 projects I am involved with was already registered. But these are
3756 fairly big, and I would also like to have a small and easy project to
3757 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
3758 checking of the chrpath project
</a
>. It was
3759 added to the checker and discovered seven potential defects. Six of
3760 these were real, mostly resource
"leak
" when the program detected an
3761 error. Nothing serious, as the resources would be released a fraction
3762 of a second later when the program exited because of the error, but it
3763 is nice to do it right in case the source of the program some time in
3764 the future end up in a library. Having fixed all defects and added
3765 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
3766 mailing list for the chrpath developers
</a
>, I decided it was time to
3767 publish a new release. These are the release notes:
</p
>
3769 <p
>New in
0.16 released
2014-
01-
14:
</p
>
3773 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
3774 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
3775 <li
>Mention new project mailing list in the documentation.
</li
>
3780 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3781 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
3782 project if something is wrong with the new release. The test suite
3783 did not discover any old errors, so if you find a new one, please also
3784 include a test suite check.
</p
>
3789 <title>New chrpath release
0.15</title>
3790 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
3791 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
3792 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
3793 <description><p
>After many years break from the package and a vain hope that
3794 development would be continued by someone else, I finally pulled my
3795 acts together this morning and wrapped up a new release of chrpath,
3796 the command line tool to modify the rpath and runpath of already
3797 compiled ELF programs. The update was triggered by the persistence of
3798 Isha Vishnoi at IBM, which needed a new config.guess file to get
3799 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
3800 is working on. I checked the
3801 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
3802 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
3803 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
3804 packages for interesting patches (failed to find the source from
3805 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3806 These are the release notes:
</p
>
3808 <p
>New in
0.15 released
2013-
11-
24:
</p
>
3812 <li
>Updated config.sub and config.guess from the GNU project to work
3813 with newer architectures. Thanks to isha vishnoi for the heads
3816 <li
>Updated README with current URLs.
</li
>
3818 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3819 Matthias Klose.
</li
>
3821 <li
>Added missing help for -k|--keepgoing option, using patch by
3822 Petr Machata found in Fedora.
</li
>
3824 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
3825 .dynamic is a NULL terminated string. Based on patch found in
3826 Fedora credited Axel Thimm and Christian Krause.
</li
>
3831 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3832 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
3833 project if something is wrong with the new release. The test suite
3834 did not discover any old errors, so if you find a new one, please also
3835 include a testsuite check.
</p
>
3840 <title>Debian init.d boot script example for rsyslog
</title>
3841 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
3842 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
3843 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
3844 <description><p
>If one of the points of switching to a new init system in Debian is
3845 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
3846 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
3847 init.d scripts at all. Here is an example init.d script, ie a rewrite
3848 of /etc/init.d/rsyslog:
</p
>
3850 <p
><pre
>
3851 #!/lib/init/init-d-script
3854 # Required-Start: $remote_fs $time
3855 # Required-Stop: umountnfs $time
3856 # X-Stop-After: sendsigs
3857 # Default-Start:
2 3 4 5
3858 # Default-Stop:
0 1 6
3859 # Short-Description: enhanced syslogd
3860 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3861 # It is quite compatible to stock sysklogd and can be
3862 # used as a drop-in replacement.
3864 DESC=
"enhanced syslogd
"
3865 DAEMON=/usr/sbin/rsyslogd
3866 </pre
></p
>
3868 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
3869 script was
137 lines, and the above is just
15 lines, most of it meta
3870 info/comments.
</p
>
3872 <p
>How to do this, you ask? Well, one create a new script
3873 /lib/init/init-d-script looking something like this:
3875 <p
><pre
>
3878 # Define LSB log_* functions.
3879 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
3880 # and status_of_proc is working.
3881 . /lib/lsb/init-functions
3884 # Function that starts the daemon/service
3890 #
0 if daemon has been started
3891 #
1 if daemon was already running
3892 #
2 if daemon could not be started
3893 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
3895 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3898 # Add code here, if necessary, that waits for the process to be ready
3899 # to handle requests from services started subsequently which depend
3900 # on this one. As a last resort, sleep for some time.
3904 # Function that stops the daemon/service
3909 #
0 if daemon has been stopped
3910 #
1 if daemon was already stopped
3911 #
2 if daemon could not be stopped
3912 # other if a failure occurred
3913 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
3914 RETVAL=
"$?
"
3915 [
"$RETVAL
" =
2 ]
&& return
2
3916 # Wait for children to finish too if this is a daemon that forks
3917 # and if the daemon is only ever run from this initscript.
3918 # If the above conditions are not satisfied then add some other code
3919 # that waits for the process to drop all resources that could be
3920 # needed by services started subsequently. A last resort is to
3921 # sleep for some time.
3922 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
3923 [
"$?
" =
2 ]
&& return
2
3924 # Many daemons don
't delete their pidfiles when they exit.
3926 return
"$RETVAL
"
3930 # Function that sends a SIGHUP to the daemon/service
3934 # If the daemon can reload its configuration without
3935 # restarting (for example, when it is sent a SIGHUP),
3936 # then implement that here.
3938 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
3943 scriptbasename=
"$(basename $
1)
"
3944 echo
"SN: $scriptbasename
"
3945 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
3946 script=
"$
1"
3953 NAME=$(basename $DAEMON)
3954 PIDFILE=/var/run/$NAME.pid
3956 # Exit if the package is not installed
3957 #[ -x
"$DAEMON
" ] || exit
0
3959 # Read configuration variable file if it is present
3960 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
3962 # Load the VERBOSE setting and other rcS variables
3965 case
"$
1" in
3967 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
3969 case
"$?
" in
3970 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3971 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3975 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
3977 case
"$?
" in
3978 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3979 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3983 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
3985 #reload|force-reload)
3987 # If do_reload() is not implemented then leave this commented out
3988 # and leave
'force-reload
' as an alias for
'restart
'.
3990 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
3994 restart|force-reload)
3996 # If the
"reload
" option is implemented then remove the
3997 #
'force-reload
' alias
3999 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4001 case
"$?
" in
4004 case
"$?
" in
4006 1) log_end_msg
1 ;; # Old process is still running
4007 *) log_end_msg
1 ;; # Failed to start
4017 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4023 </pre
></p
>
4025 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4026 lot. I did not really polish the approach, so it might not always
4027 work out of the box, but you get the idea. I did not try very hard to
4028 optimize it nor make it more robust either.
</p
>
4030 <p
>A better argument for switching init system in Debian than reducing
4031 the size of init scripts (which is a good thing to do anyway), is to
4032 get boot system that is able to handle the kernel events sensibly and
4033 robustly, and do not depend on the boot to run sequentially. The boot
4034 and the kernel have not behaved sequentially in years.
</p
>
4039 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4040 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4041 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4042 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4043 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4044 remote display access is the preferred solution with oVirt and RedHat
4045 Enterprise Virtualization, and I was sad to discover the other day
4046 that the browser plugin needed to use these systems seamlessly was
4047 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4048 for a package
</a
> was from
2012-
04-
10 with no progress since
4049 2013-
04-
01, so I decided to wrap up a package based on the great work
4050 from Cajus Pollmeier and put it in a collab-maint maintained git
4051 repository to get a package I could use. I would very much like
4052 others to help me maintain the package (or just take over, I do not
4053 mind), but as no-one had volunteered so far, I just uploaded it to
4054 NEW. I hope it will be available in Debian in a few days.
</p
>
4056 <p
>The source is now available from
4057 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
">http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
</a
>.
</p
>
4062 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4063 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4064 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4065 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4066 <description><p
>The
4067 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4068 program is a a very nice system to create virtual machine images. It
4069 create a image file, add a partition table, mount it and run
4070 debootstrap in the mounted directory to create a Debian system on a
4071 stick. Yesterday, I decided to try to teach it how to make images for
4072 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4073 of a plan to simplify the build system for
4074 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4075 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4076 the virtualbox images, but its current build system made multistrap
4077 based system for Dreamplug images, and it is lacking support for
4078 Raspberry Pi.
</p
>
4080 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4081 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4082 code and adjusted it to be able to build armel images on my amd64
4083 Debian laptop. I ended up giving vmdebootstrap five new options,
4084 allowing me to replicate the image creation process I use to make
4085 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4086 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4087 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4088 call debootstrap with --foreign and to copy the handler into the
4089 generated chroot before running the second stage. This allow
4090 vmdebootstrap to create armel images on an amd64 host. Next I added
4091 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4092 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4093 given file system type, allowing me to create an image with a vfat
4094 partition for the /boot/ stuff. I also added a
<tt
>--variant
4095 variant
</tt
> option to allow me to create smaller images without the
4096 Debian base system packages installed. Finally, I added an option
4097 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4098 as a boot loader. It is not needed on the Raspberry Pi and probably
4099 most other non-x86 architectures. The changes were accepted by the
4100 upstream author of vmdebootstrap yesterday and today, and is now
4102 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4103 upstream project page
</a
>.
</p
>
4105 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4106 create a small script (the customize script) to add the non-free
4107 binary blob needed to boot the Raspberry Pi and the APT source
4110 <p
><pre
>
4112 set -e # Exit on first error
4113 rootdir=
"$
1"
4114 cd
"$rootdir
"
4115 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4116 deb http://http.debian.net/debian/ jessie main contrib non-free
4118 # Install non-free binary blob needed to boot Raspberry Pi. This
4119 # install a kernel somewhere too.
4120 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4121 -O $rootdir/usr/bin/rpi-update
4122 chmod a+x $rootdir/usr/bin/rpi-update
4123 mkdir -p $rootdir/lib/modules
4124 touch $rootdir/boot/start.elf
4125 chroot $rootdir rpi-update
4126 </pre
></p
>
4128 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4129 to build the image:
</p
>
4132 sudo ./vmdebootstrap \
4135 --distribution jessie \
4136 --mirror http://http.debian.net/debian \
4145 --root-password raspberry \
4146 --hostname raspberrypi \
4147 --foreign /usr/bin/qemu-arm-static \
4148 --customize `pwd`/customize \
4150 --package git-core \
4151 --package binutils \
4152 --package ca-certificates \
4155 </pre
></p
>
4157 <p
>The list of packages being installed are the ones needed by
4158 rpi-update to make the image bootable on the Raspberry Pi, with the
4159 exception of netbase, which is needed by debootstrap to find
4160 /etc/hosts with the minbase variant. I really wish there was a way to
4161 set up an Raspberry Pi using only packages in the Debian archive, but
4162 that is not possible as far as I know, because it boots from the GPU
4163 using a non-free binary blob.
</p
>
4165 <p
>The build host need debootstrap, kpartx and qemu-user-static and
4166 probably a few others installed. I have not checked the complete
4167 build dependency list.
</p
>
4169 <p
>The resulting image will not use the hardware floating point unit
4170 on the Raspberry PI, because the armel architecture in Debian is not
4171 optimized for that use. So the images created will be a bit slower
4172 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4177 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4178 <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>
4179 <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>
4180 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4181 <description><p
>The last few days I came across a few good causes that should get
4182 wider attention. I recommend signing and donating to each one of
4185 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4186 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4187 Women program which is a Google Summer of Code like initiative to get
4188 more women involved in free software. One debian sponsor has offered
4189 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4190 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4191 hope you will to. :)
</p
>
4193 <p
>And the Electronic Frontier Foundation just announced plans to
4194 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4195 documentaries about the excessive spying
</a
> on every Internet user that
4196 take place these days, and their need to fund the work. I
've already
4197 donated. Are you next?
</p
>
4199 <p
>For my Norwegian audience, the organisation Studentenes og
4200 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4201 statement under the heading
4202 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4203 Access
</a
> for those of us asking for more focus on open access in the
4204 Norwegian government. So far
499 signatures. I hope you will sign it
4210 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4211 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4212 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4213 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4214 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4215 project
</a
> have been going on for a while, and have presented the
4216 vision, ideas and solution several places. Here is a little
4217 collection of videos of talks and presentation of the project.
</p
>
4221 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4222 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4224 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4225 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4227 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4228 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4229 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4230 (Youtube)
</li
>
4232 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4233 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4235 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4236 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4238 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4239 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4240 York City in
2012</a
> (Youtube)
</li
>
4242 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4243 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4244 (Youtube)
</li
>
4246 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4247 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4249 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
4250 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
4252 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
4253 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4254 2013</a
> (Youtube)
</li
>
4258 <p
>A larger list is available from
4259 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
4260 Freedombox Wiki
</a
>.
</p
>
4262 <p
>On other news, I am happy to report that Freedombox based on Debian
4263 Jessie is coming along quite well, and soon both Owncloud and using
4264 Tor should be available for testers of the Freedombox solution. :) In
4265 a few weeks I hope everything needed to test it is included in Debian.
4266 The withsqlite package is already in Debian, and the plinth package is
4267 pending in NEW. The third and vital part of that puzzle is the
4268 metapackage/setup framework, which is still pending an upload. Join
4269 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
4270 (#freedombox on irc.debian.org)
</a
> and
4271 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4272 mailing list
</a
> if you want to help make this vision come true.
</p
>
4277 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
4278 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
4279 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
4280 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
4281 <description><p
>I was introduced to the
4282 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
4283 in
2010, when Eben Moglen presented his vision about serving the need
4284 of non-technical people to keep their personal information private and
4285 within the legal protection of their own homes. The idea is to give
4286 people back the power over their network and machines, and return
4287 Internet back to its intended peer-to-peer architecture. Instead of
4288 depending on a central service, the Freedombox will give everyone
4289 control over their own basic infrastructure.
</p
>
4291 <p
>I
've intended to join the effort since then, but other tasks have
4292 taken priority. But this summers nasty news about the misuse of trust
4293 and privilege exercised by the
"western
" intelligence gathering
4294 communities increased my eagerness to contribute to a point where I
4295 actually started working on the project a while back.
</p
>
4297 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
4298 Debian initiative
</a
> based on the vision from Eben Moglen, is to
4299 create a simple and cheap Debian based appliance that anyone can hook
4300 up in their home and get access to secure and private services and
4301 communication. The initial deployment platform have been the
4302 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
4303 which is a piece of hardware I do not own. So to be able to test what
4304 the current Freedombox setup look like, I had to come up with a way to install
4305 it on some hardware I do have access to. I have rewritten the
4306 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
4307 image build framework to use .deb packages instead of only copying
4308 setup into the boot images, and thanks to this rewrite I am able to
4309 set up any machine supported by Debian Wheezy as a Freedombox, using
4310 the previously mentioned deb (and a few support debs for packages
4311 missing in Debian).
</p
>
4313 <p
>The current Freedombox setup consist of a set of bootstrapping
4315 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
4316 and a administrative web interface
4317 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
4318 withsqlite), as well as a privacy enhancing proxy based on
4319 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
4320 (freedombox-privoxy). There is also a web/javascript based XMPP
4321 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
4322 trying (unsuccessfully so far) to talk to the XMPP server
4323 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
4324 web interface is pluggable, and the goal is to use it to enable OpenID
4325 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4326 this is really working yet, see
4327 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
4328 project TODO
</a
> for links to GIT repositories. Most of the code is
4329 on github at the moment. The HTTP proxy is operational out of the
4330 box, and the admin web interface can be used to add/remove plinth
4331 users. I
've not been able to do anything else with it so far, but
4332 know there are several branches spread around github and other places
4333 with lots of half baked features.
</p
>
4335 <p
>Anyway, if you want to have a look at the current state, the
4336 following recipes should work to give you a test machine to poke
4339 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
4343 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
4344 <li
>Boot from it, either as CD or USB stick.
</li
>
4345 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
4346 to the Debian installer:
<p
>
4347 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
4349 <li
>Answer the few language/region/password questions and pick disk to
4350 install on.
</li
>
4352 <li
>When the installation is finished and the machine have rebooted a
4353 few times, your Freedombox is ready for testing.
</li
>
4357 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4361 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4362 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4363 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4365 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4366 </pre
></li
>
4367 <li
><p
>Run this as root:
</p
>
4369 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4372 apt-get install freedombox-setup
4373 /usr/lib/freedombox/setup
4374 </pre
></li
>
4375 <li
>Reboot into your freshly created Freedombox.
</li
>
4379 <p
>You can test it on other architectures too, but because the
4380 freedombox-privoxy package is binary, it will only work as intended on
4381 the architectures where I have had time to build the binary and put it
4382 in my APT repository. But do not let this stop you. It is only a
4383 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4385 <p
>Note that by default Freedombox is a DHCP server on the
4386 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4387 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4388 disable
</tt
>" as root.
</p
>
4390 <p
>Please let me know if this works for you, or if you have any
4391 problems. We gather on the IRC channel
4392 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4393 irc.debian.org and the
4394 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4395 mailing list
</a
>.
</p
>
4397 <p
>Once you get your freedombox operational, you can visit
4398 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4399 welcome screen (dead end - do not be surprised if you are unable to
4400 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4401 to look at the rest of plinth. The default user is
'admin
' and the
4402 default password is
'secret
'.
</p
>
4407 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4408 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4409 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4410 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4411 <description><p
>Earlier, I reported about
4412 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4413 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4414 told by IBM that the original disk should be thrown away. And as
4415 there no longer was a problem if I bricked the firmware, I decided
4416 today to try to install Intel firmware to replace the Lenovo firmware
4417 currently on the disk.
</p
>
4419 <p
>I searched the Intel site for firmware, and found
4420 <a href=
"https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y
&ProdId=
3472&DwnldID=
18363&ProductFamily=Solid-State+Drives+and+Caching
&ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive
&ProductProduct=Intel%c2%ae+SSD+
520+Series+(
180GB%
2c+
2.5in+SATA+
6Gb%
2fs%
2c+
25nm%
2c+MLC)
&lang=eng
">issdfut_2.0
.4.iso
</a
>
4421 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4422 according to the site should contain the latest firmware for SSD
4423 disks. I inserted the broken disk in one of my spare laptops and
4424 booted the ISO from a USB stick. The disk was recognized, but the
4425 program claimed the newest firmware already were installed and refused
4426 to insert any Intel firmware. So no change, and the disk is still
4427 unable to handle write load. :( I guess the only way to get them
4428 working would be if Lenovo releases new firmware. No idea how likely
4429 that is. Anyway, just blogging about this test for completeness. I
4430 got a working Samsung disk, and see no point in spending more time on
4431 the broken disks.
</p
>
4436 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4437 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4438 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4439 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4440 <description><p
>Today I switched to
4441 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4442 new laptop
</a
>. I
've previously written about the problems I had with
4443 my new Thinkpad X230, which was delivered with an
4444 <a href=
"http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
">180
4445 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4446 sustained writes. My hardware supplier have been very forthcoming in
4447 trying to find a solution, and after first trying with another
4448 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
4449 disk instead to fix it once and for all. The Samsung disk survived
4450 the installation of Debian with encrypted disks (filling the disk with
4451 random data during installation killed the first two), and I thus
4452 decided to trust it with my data. I have installed it as a Debian Edu
4453 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4454 server at home using Kerberos and LDAP, and will use it as my work
4455 station from now on.
</p
>
4457 <p
>As this is a solid state disk with no moving parts, I believe the
4458 Debian Wheezy default installation need to be tuned a bit to increase
4459 performance and increase life time of the disk. The Linux kernel and
4460 user space applications do not yet adjust automatically to such
4461 environment. To make it easier for my self, I created a draft Debian
4462 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
4463 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
4464 for the ssd-setup package
</a
> is available from collab-maint, and it
4465 is set up to adjust the setup of the machine by just installing the
4466 package. If there is any non-SSD disk in the machine, the package
4467 will refuse to install, as I did not try to write any logic to sort
4468 file systems in SSD and non-SSD file systems.
</p
>
4470 <p
>I consider the package a draft, as I am a bit unsure how to best
4471 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4472 where I set up the machine with one large encrypted partition (in
4473 addition to /boot), put LVM on top of this and set up partitions on
4474 top of this again. See the README file in the package source for the
4475 references I used to pick the settings. At the moment these
4476 parameters are tuned:
</p
>
4480 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4481 (adding discard to /etc/crypttab)
</li
>
4483 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
4484 this case a cryptsetup partition) by changing issue_discards from
4485 0 to
1 in /etc/lvm/lvm.conf.
</li
>
4487 <li
>Set relatime as a file system option for ext3 and ext4 file
4490 <li
>Tell swap to use TRIM commands by adding
'discard
' to
4491 /etc/fstab.
</li
>
4493 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
4495 <li
>Run fstrim on every ext3 and ext4 file system every night (from
4496 cron.daily).
</li
>
4498 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
4499 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4503 <p
>During installation, I cancelled the part where the installer fill
4504 the disk with random data, as this would kill the SSD performance for
4505 little gain. My goal with the encrypted file system is to ensure
4506 those stealing my laptop end up with a brick and not a working
4507 computer. I have no hope in keeping the really resourceful people
4508 from getting the data on the disk (see
4509 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4510 Thus I concluded that adding the discard option to crypttab is the
4511 right thing to do.
</p
>
4513 <p
>I considered using the noop I/O scheduler, as several recommended
4514 it for SSD, but others recommended deadline and a benchmark I found
4515 indicated that deadline might be better for interactive use.
</p
>
4517 <p
>I also considered using the
'discard
' file system option for ext3
4518 and ext4, but read that it would give a performance hit ever time a
4519 file is removed, and thought it best to that that slowdown once a day
4520 instead of during my work.
</p
>
4522 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4523 this is already done by Debian Edu.
</p
>
4525 <p
>I have not yet started on the user space tuning. I expect
4526 iceweasel need some tuning, and perhaps other applications too, but
4527 have not yet had time to investigate those parts.
</p
>
4529 <p
>The package should work on Ubuntu too, but I have not yet tested it
4532 <p
>As for the answer to the question in the title of this blog post,
4533 as far as I know, the only solution I know about is to replace the
4534 disk. It might be possible to flash it with Intel firmware instead of
4535 the Lenovo firmware. But I have not tried and did not want to do so
4536 without approval from Lenovo as I wanted to keep the warranty on the
4537 disk until a solution was found and they wanted the broken disks
4543 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4544 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4545 <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>
4546 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
4547 <description><p
>A few days ago, I wrote about
4548 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
4549 problems I experienced with my new X230 and its SSD disk
</a
>, which
4550 was dying during installation because it is unable to cope with
4551 sustained write. My supplier is in contact with
4552 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
4553 replacement disk to try to fix the problem. They decided to send an
4554 identical model, so my hopes for a permanent fix was slim.
</p
>
4556 <p
>Anyway, today I got the replacement disk and tried to install
4557 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4558 same firmware version as the original. This time my hope raised
4559 slightly as the installation progressed, as the original disk used to
4560 die after
4-
7% of the disk was written to, while this time it kept
4561 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
4562 died again and I was back on square one. I still do not have a new
4563 laptop with a disk I can trust. I can not live with a disk that might
4564 lock up when I download a new
4565 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
4566 other large files. I look forward to hearing from my supplier with
4567 the next proposal from Lenovo.
</p
>
4569 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
4570 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4571 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4572 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
4573 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4574 P/N
45N8295, P0C38732.
</p
>
4576 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
4577 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
4578 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4579 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
4580 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4581 P/N
45N8295, P0C38732.
</p
>
4583 <p
>The only difference is in the first number (serial number?), ISN,
4584 SA, date and WNPP values. Mentioning all the details here in case
4585 someone is able to use the information to find a way to identify the
4586 failing disk among working ones (if any such working disk actually
4592 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
4593 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
4594 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
4595 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
4596 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
4597 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4598 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
4599 member assosiation NUUG
</a
> and
4600 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
4601 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
4602 Bitraf
</a
>.
</p
>
4604 <p
>It starts
10:
00 and continue until late evening. Everyone is
4605 welcome, and there is no fee to participate. There is on the other
4606 hand limited space, and only room for
30 people. Please put your name
4607 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
4608 wiki page
</a
> if you plan to join us.
</p
>
4613 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
4614 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
4615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
4616 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
4617 <description><p
>Half a year ago, I reported that I had to find a
4618 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
4619 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
4620 time to spend on it, and it took a while to find a model I believe
4621 will do the job, but two days ago the replacement finally arrived. I
4623 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
4624 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4625 a roaming workstation, and it seemed to work flawlessly. But my
4626 second installation with encrypted disk was not as successful. More
4627 on that below.
</p
>
4629 <p
>I had a hard time trying to track down a good laptop, as my most
4630 important requirements (robust and with a good keyboard) are never
4631 listed in the feature list. But I did get good help from the search
4632 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4633 allowed me to limit the list of interesting laptops based on my other
4634 requirements. A bit surprising that SSD disk are not disks according
4635 to that search interface, so I had to drop specifying the number of
4636 disks from my search parameters. I also asked around among friends to
4637 get their impression on keyboards and robustness.
</p
>
4639 <p
>So the new laptop arrived, and it is quite a lot wider than the
4640 X41. I am not quite convinced about the keyboard, as it is
4641 significantly wider than my old keyboard, and I have to stretch my
4642 hand a lot more to reach the edges. But the key response is fairly
4643 good and the individual key shape is fairly easy to handle, so I hope
4644 I will get used to it. My old X40 was starting to fail, and I really
4645 needed a new laptop now. :)
</p
>
4647 <p
>Turning off the touch pad was simple. All it took was a quick
4648 visit to the BIOS during boot it disable it.
</p
>
4650 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
4651 lock up during load. And this happen when installing Debian Wheezy
4652 with encrypted disk, while the disk is being filled with random data.
4653 I also tested to install Ubuntu Raring, and it happen there too if I
4654 reenable the code to fill the disk with random data (it is disabled by
4655 default in Ubuntu). And the bug with is already known. It was
4656 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
4657 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
4658 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4659 kernel developers as
4660 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
4661 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
4662 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4663 Lenovo forums, both for
4664 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
4665 2012-
11-
10</a
> and for
4666 <a href=
"http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x230-SATA-errors-with-
180GB-Intel-
520-SSD-under-heavy-write-load/m-p/
1068147">X230
4667 03-
20-
2013</a
>. The problem do not only affect installation. The
4668 reports state that the disk lock up during use if many writes are done
4669 on the disk, so it is much no use to work around the installation
4670 problem and end up with a computer that can lock up at any moment.
4672 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
4673 available
</a
> that will lock up the hard drive after running a few
4674 minutes by writing to a file.
</p
>
4676 <p
>I
've contacted my supplier and asked how to handle this, and after
4677 contacting PCHELP Norway (request
01D1FDP) which handle support
4678 requests for Lenovo, his first suggestion was to upgrade the disk
4679 firmware. Unfortunately there is no newer firmware available from
4680 Lenovo, as my disk already have the most recent one (version LF1i). I
4681 hope to hear more from him today and hope the problem can be
4687 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
4688 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
4689 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
4690 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
4691 <description><p
>Half a year ago, I reported that I had to find a replacement for my
4692 trusty old Thinkpad X41. Unfortunately I did not have much time to
4693 spend on it, but today the replacement finally arrived. I ended up
4694 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
4695 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
4696 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4697 this, it is installing what I hope will be a more final installation,
4698 with a encrypted hard drive to ensure any dope head stealing it end up
4699 with an expencive door stop.
</p
>
4701 <p
>I had a hard time trying to track down a good laptop, as my most
4702 important requirements (robust and with a good keyboard) are never
4703 listed in the feature list. But I did get good help from the search
4704 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4705 allowed me to limit the list of interesting laptops based on my other
4706 requirements. A bit surprising that SSD disk are not disks, so I had
4707 to drop number of disks from my search parameters.
</p
>
4709 <p
>I am not quite convinced about the keyboard, as it is significantly
4710 wider than my old keyboard, and I have to stretch my hand a lot more
4711 to reach the edges. But the key response is fairly good and the
4712 individual key shape is fairly easy to handle, so I hope I will get
4713 used to it. My old X40 was starting to fail, and I really needed a
4714 new laptop now. :)
</p
>
4716 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
4721 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
4722 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
4723 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
4724 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
4725 <description><p
>It annoys me when the computer fail to do automatically what it is
4726 perfectly capable of, and I have to do it manually to get things
4727 working. One such task is to find out what firmware packages are
4728 needed to get the hardware on my computer working. Most often this
4729 affect the wifi card, but some times it even affect the RAID
4730 controller or the ethernet card. Today I pushed version
0.4 of the
4731 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
4732 including a new script isenkram-autoinstall-firmware handling the
4733 process of asking all the loaded kernel modules what firmware files
4734 they want, find debian packages providing these files and install the
4735 debian packages. Here is a test run on my laptop:
</p
>
4737 <p
><pre
>
4738 # isenkram-autoinstall-firmware
4739 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4740 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4741 info: locating packages with the requested firmware files
4742 info: Updating APT sources after adding non-free APT source
4743 info: trying to install firmware-ipw2x00
4746 Preconfiguring packages ...
4747 Selecting previously deselected package firmware-ipw2x00.
4748 (Reading database ...
259727 files and directories currently installed.)
4749 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4750 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
4752 </pre
></p
>
4754 <p
>When all the requested firmware is present, a simple message is
4755 printed instead:
</p
>
4757 <p
><pre
>
4758 # isenkram-autoinstall-firmware
4759 info: did not find any firmware files requested by loaded kernel modules. exiting
4761 </pre
></p
>
4763 <p
>It could use some polish, but it is already working well and saving
4764 me some time when setting up new machines. :)
</p
>
4766 <p
>So, how does it work? It look at the set of currently loaded
4767 kernel modules, and look up each one of them using modinfo, to find
4768 the firmware files listed in the module meta-information. Next, it
4769 download the Contents file from a nearby APT mirror, and search for
4770 the firmware files in this file to locate the package with the
4771 requested firmware file. If the package is in the non-free section, a
4772 non-free APT source is added and the package is installed using
4773 <tt
>apt-get install
</tt
>. The end result is a slightly better working
4776 <p
>I hope someone find time to implement a more polished version of
4777 this script as part of the hw-detect debian-installer module, to
4778 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
4779 #
655507</a
>. There really is no need to insert USB sticks with
4780 firmware during a PXE install when the packages already are available
4781 from the nearby Debian mirror.
</p
>
4786 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
4787 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
4788 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
4789 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
4790 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4791 the screen just turn black when Linux boot, either during installation
4792 or on first boot from the hard disk. I
've seen it once in a while the
4793 last few years, but only recently understood the cause. I
've seen it
4794 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4795 The reason seem to be in the wiring of some laptops. The system to
4796 control the screen background light is inverted, so when Linux try to
4797 turn the brightness fully on, it end up turning it off instead. I do
4798 not know which Linux drivers are affected, but this post is about the
4799 i915 driver used by the
4800 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4801 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
4803 <p
>The problem can be worked around two ways. Either by adding
4804 i915.invert_brightness=
1 as a kernel option, or by adding a file in
4805 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
4806 option when it load the i915 kernel module. On Debian and Ubuntu, it
4807 can be done by running these commands as root:
</p
>
4810 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
4811 update-initramfs -u -k all
4814 <p
>Since March
2012 there is
4815 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
4816 mechanism in the Linux kernel
</a
> to tell the i915 driver which
4817 hardware have this problem, and get the driver to invert the
4818 brightness setting automatically. To use it, one need to add a row in
4819 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
4820 intel_quirks array
</a
> in the driver source
4821 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
4822 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
4823 number (vendor number
8086 is assumed) and subdevice vendor and device
4826 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
4827 -vvnn
</tt
> for the video card in question:
</p
>
4829 <p
><pre
>
4830 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
4831 3rd Gen Core processor Graphics Controller [
8086:
0156] \
4832 (rev
09) (prog-if
00 [VGA controller])
4833 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
4834 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4835 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4836 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
4837 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
4839 Interrupt: pin A routed to IRQ
42
4840 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
4841 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
4842 Region
4: I/O ports at
4000 [size=
64]
4843 Expansion ROM at
<unassigned
> [disabled]
4844 Capabilities:
<access denied
>
4845 Kernel driver in use: i915
4846 </pre
></p
>
4848 <p
>The resulting intel_quirks entry would then look like this:
</p
>
4850 <p
><pre
>
4851 struct intel_quirk intel_quirks[] = {
4853 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4854 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
4857 </pre
></p
>
4859 <p
>According to the kernel module instructions (as seen using
4860 <tt
>modinfo i915
</tt
>), information about hardware needing the
4861 invert_brightness flag should be sent to the
4862 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
4863 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
4864 developers. But my email about the laptop sent
2013-
06-
03 have not
4866 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
4867 web archive for the mailing list
</a
>, so I suspect they do not accept
4868 emails from non-subscribers. Because of this, I sent my patch also to
4869 the Debian bug tracking system instead as
4870 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
4871 sure the patch is not lost.
</p
>
4873 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
4874 with this problem working properly with Linux. If you use Gnome, your
4875 worries should be over at this point. But if you use KDE, there is
4876 something in KDE ignoring the invert_brightness setting and turning on
4877 the screen during login. I
've reported it to Debian as
4878 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
4879 have no idea yet how to figure out exactly what subsystem is doing
4880 this. Perhaps you can help? Perhaps you know what the Gnome
4881 developers did to handle this, and this can give a clue to the KDE
4882 developers? Or you know where in KDE the screen brightness is changed
4883 during login? If so, please update the BTS report (or get in touch if
4884 you do not know how to update BTS).
</p
>
4886 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
4887 acpi_backlight=vendor, to disable ACPI backlight support completely,
4888 as the ACPI information on the machine is trash and it is better to
4889 leave it to the intel video driver to control the screen
4890 backlight.
</p
>
4895 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
4896 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
4897 <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>
4898 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
4899 <description><p
>Two days ago, I asked
4900 <a href=
"http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
">how
4901 I could install Linux on a Packard Bell EasyNote LV computer
4902 preinstalled with Windows
8</a
>. I found a solution, but am horrified
4903 with the obstacles put in the way of Linux users on a laptop with UEFI
4904 and Windows
8.
</p
>
4906 <p
>I never found out if the cause of my problems were the use of UEFI
4907 secure booting or fast boot. I suspect fast boot was the problem,
4908 causing the firmware to boot directly from HD without considering any
4909 key presses and alternative devices, but do not know UEFI settings
4910 enough to tell.
</p
>
4912 <p
>There is no way to install Linux on the machine in question without
4913 opening the box and disconnecting the hard drive! This is as far as I
4914 can tell, the only way to get access to the firmware setup menu
4915 without accepting the Windows
8 license agreement. I am told (and
4916 found description on how to) that it is possible to configure the
4917 firmware setup once booted into Windows
8. But as I believe the terms
4918 of that agreement are completely unacceptable, accepting the license
4919 was never an alternative. I do not enter agreements I do not intend
4920 to follow.
</p
>
4922 <p
>I feared I had to return the laptops and ask for a refund, and
4923 waste many hours on this, but luckily there was a way to get it to
4924 work. But I would not recommend it to anyone planning to run Linux on
4925 it, and I have become sceptical to Windows
8 certified laptops. Is
4926 this the way Linux will be forced out of the market place, by making
4927 it close to impossible for
"normal
" users to install Linux without
4928 accepting the Microsoft Windows license terms? Or at least not
4929 without risking to loose the warranty?
</p
>
4931 <p
>I
've updated the
4932 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
4933 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
4934 do not have to struggle as much as I did to get Linux into the
4937 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4938 Michael Tokarev and others for feedback and ideas.
</p
>
4943 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
4944 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
4945 <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>
4946 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
4947 <description><p
>I
've run into quite a problem the last few days. I bought three
4948 new laptops for my parents and a few others. I bought Packard Bell
4949 Easynote LV to run Kubuntu on and use as their home computer. But I
4950 am completely unable to figure out how to install Linux on it. The
4951 computer is preinstalled with Windows
8, and I suspect it uses UEFI
4952 instead of a BIOS to boot.
</p
>
4954 <p
>The problem is that I am unable to get it to PXE boot, and unable
4955 to get it to boot the Linux installer from my USB stick. I have yet
4956 to try the DVD install, and still hope it will work. when I turn on
4957 the computer, there is no information on what buttons to press to get
4958 the normal boot menu. I expect to get some boot menu to select PXE or
4959 USB stick booting. When booting, it first ask for the language to
4960 use, then for some regional settings, and finally if I will accept the
4961 Windows
8 terms of use. As these terms are completely unacceptable to
4962 me, I have no other choice but to turn off the computer and try again
4963 to get it to boot the Linux installer.
</p
>
4965 <p
>I have gathered my findings so far on a Linlap page about the
4966 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4967 EasyNote LV
</a
> model. If you have any idea how to get Linux
4968 installed on this machine, please get in touch or update that wiki
4969 page. If I can
't find a way to install Linux, I will have to return
4970 the laptop to the seller and find another machine for my parents.
</p
>
4972 <p
>I wonder, is this the way Linux will be forced out of the market
4973 using UEFI and
"secure boot
" by making it impossible to install Linux
4974 on new Laptops?
</p
>
4979 <title>How to transform a Debian based system to a Debian Edu installation
</title>
4980 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
4981 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
4982 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
4983 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
4984 an operating system based on Debian intended for use in schools. It
4985 contain a turn-key solution for the computer network provided to
4986 pupils in the primary schools. It provide both the central server,
4987 network boot servers and desktop environments with heaps of
4988 educational software. The project was founded almost
12 years ago,
4989 2001-
07-
02. If you want to support the project, which is in need for
4990 cash to fund developer gatherings and other project related activity,
4991 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
4992 donate some money
</a
>.
4994 <p
>A topic that come up again and again on the Debian Edu mailing
4995 lists and elsewhere, is the question on how to transform a Debian or
4996 Ubuntu installation into a Debian Edu installation. It isn
't very
4997 hard, and last week I wrote a script to replicate the steps done by
4998 the Debian Edu installer.
</p
>
5000 <p
>The script,
5001 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-config/share/debian-edu-config/tools/debian-edu-bless?view=markup
">debian-edu-bless
<a/
>
5002 in the debian-edu-config package, will go through these six steps and
5003 transform an existing Debian Wheezy or Ubuntu (untested) installation
5004 into a Debian Edu Workstation:
</p
>
5008 <li
>Add skolelinux related APT sources.
</li
>
5009 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5010 <li
>Install debian-edu-install to load preseeding values and pull in
5011 our configuration.
</li
>
5012 <li
>Preseed debconf database with profile setup in
5013 /etc/debian-edu/config, and run tasksel to install packages
5014 according to the profile specified in the config above,
5015 overriding some of the Debian automation machinery.
</li
>
5016 <li
>Run debian-edu-cfengine-D installation to configure everything
5017 that could not be done using preseeding.
</li
>
5018 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5022 <p
>There are some steps in the Debian Edu installation that can not be
5023 replicated like this. Disk partitioning and LVM setup, for example.
5024 So this script just assume there is enough disk space to install all
5025 the needed packages.
</p
>
5027 <p
>The script was created to help a Debian Edu student working on
5028 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5029 Debian Edu client, and using it he can take the existing
5030 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5031 transform it into a fully functioning Debian Edu Workstation (or
5032 Roaming Workstation, or whatever :).
</p
>
5034 <p
>The default setting in the script is to create a KDE Workstation.
5035 If a LXDE based Roaming workstation is wanted instead, modify the
5036 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5038 <p
><pre
>
5039 PROFILE=
"Roaming-Workstation
"
5040 DESKTOP=
"lxde
"
5041 </pre
></p
>
5043 <p
>The script could even become useful to set up Debian Edu servers in
5044 the cloud, by starting with a virtual Debian installation at some
5045 virtual hosting service and setting up all the services on first
5051 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5052 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5053 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5054 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5055 <description><P
>In January,
5056 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5057 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5058 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5059 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5060 marvellous construction system from Denmark. We also created
5061 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5062 a place to take notes and write down our plans and hopes. And several
5063 people showed up to help. I was very happy to see the effect of my
5064 call. Since the small start, we have a debtags tag
5065 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5066 tag for LEGO related packages, and now count
10 packages related to
5067 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5069 <p
><table
>
5070 <tr
><td
><a href=
"http://packages.qa.debian.org/brickos
">brickos
</a
></td
><td
>alternative OS for LEGO Mindstorms RCX. Supports development in C/C++
</td
></tr
>
5071 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5072 <tr
><td
><a href=
"http://packages.qa.debian.org/libnxt
">libnxt
</a
></td
><td
>utility library for talking to the LEGO Mindstorms NX
</td
></tr
>
5073 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5074 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5075 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5076 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt
">python-nxt
</a
></td
><td
>python driver/interface/wrapper for the Lego Mindstorms NXT robot
</td
></tr
>
5077 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt-filer
">python-nxt-filer
</a
></td
><td
>simple GUI to manage files on a LEGO Mindstorms NXT
</td
></tr
>
5078 <tr
><td
><a href=
"http://packages.qa.debian.org/scratch
">scratch
</a
></td
><td
>easy to use programming environment for ages
8 and up
</td
></tr
>
5079 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5080 </table
></p
>
5082 <p
>Some of these are available in Wheezy, and all but one are
5083 currently available in Jessie/testing. leocad is so far only
5084 available in experimental.
</p
>
5086 <p
>If you care about LEGO in Debian, please join us on IRC and help
5087 adding the rest of the great free software tools available on Linux
5088 for LEGO designers.
</p
>
5093 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5094 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5095 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5096 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5097 <description><p
>When I woke up this morning, I was very happy to see that the
5098 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5099 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5100 Debian release, and I expect to move my machines at home over to it fairly
5103 <p
>The new debian release contain heaps of new stuff, and one program
5104 in particular make me very happy to see included. The
5105 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5106 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5107 included for the first time. Alongside similar programs like
5108 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5109 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5110 it allow for visual programming where syntax errors can not happen,
5111 and a friendly programming environment for learning to control the
5112 computer. Scratch will also be included in the next release of Debian
5115 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5116 Edu/Skolelinux release too. The
5117 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5118 alpha release
</a
> went out last week, and the next should soon
5124 <title>Isenkram
0.2 finally in the Debian archive
</title>
5125 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5126 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5127 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5128 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5129 package
</a
> finally made it into the archive, after lingering in NEW
5130 for many months. I uploaded it to the Debian experimental suite
5131 2013-
01-
27, and today it was accepted into the archive.
</p
>
5133 <p
>Isenkram is a system for suggesting to users what packages to
5134 install to work with a pluggable hardware device. The suggestion pop
5135 up when the device is plugged in. For example if a Lego Mindstorm NXT
5136 is inserted, it will suggest to install the program needed to program
5137 the NXT controller. Give it a go, and report bugs and suggestions to
5143 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5144 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5145 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5146 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5147 <description><p
>My
5148 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5149 bitcoin related blog post
</a
> mentioned that the new
5150 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5151 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5152 2013-
01-
19, and have been available in unstable since then. It was
5153 automatically copied to Ubuntu, and is available in their Raring
5154 version too.
</p
>
5156 <p
>But there is a strange problem with the build that block this new
5157 version from being available on the i386 and kfreebsd-i386
5158 architectures. For some strange reason, the autobuilders in Debian
5159 for these architectures fail to run the test suite on these
5160 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
5161 We are so far unable to reproduce it when building it manually, and
5162 no-one have been able to propose a fix. If you got an idea what is
5163 failing, please let us know via the BTS.
</p
>
5165 <p
>One feature that is annoying me with of the bitcoin client, because
5166 I often run low on disk space, is the fact that the client will exit
5167 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
5168 #
696715</a
>). So make sure you have enough disk space when you run
5171 <p
>As usual, if you use bitcoin and want to show your support of my
5172 activities, please send Bitcoin donations to my address
5173 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5178 <title>Welcome to the world, Isenkram!
</title>
5179 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5180 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5181 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5182 <description><p
>Yesterday, I
5183 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5184 for testers
</a
> for my prototype for making Debian better at handling
5185 pluggable hardware devices, which I
5186 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5187 out to create
</a
> earlier this month. Several valuable testers showed
5188 up, and caused me to really want to to open up the development to more
5189 people. But before I did this, I want to come up with a sensible name
5190 for this project. Today I finally decided on a new name, and I have
5191 renamed the project from hw-support-handler to this new name. In the
5192 process, I moved the source to git and made it available as a
5193 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5194 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5195 To fetch and build the latest version of the source, use
</p
>
5198 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5199 cd isenkram
&& git-buildpackage -us -uc
5202 <p
>I have not yet adjusted all files to use the new name yet. If you
5203 want to hack on the source or improve the package, please go ahead.
5204 But please talk to me first on IRC or via email before you do major
5205 changes, to make sure we do not step on each others toes. :)
</p
>
5207 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5208 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5209 stuff, in other words. I
've been told it is the Norwegian variant of
5210 the German word eisenkram, for those that are familiar with that
5213 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5214 instructions, to avoid confusing people with an error from the signing
5217 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5218 clone argument to avoid the need for authentication.
</p
>
5223 <title>First prototype ready making hardware easier to use in Debian
</title>
5224 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5225 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5226 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5227 <description><p
>Early this month I set out to try to
5228 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5229 the Debian support for pluggable hardware devices
</a
>. Now my
5230 prototype is working, and it is ready for a larger audience. To test
5232 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5233 from the Debian Edu subversion repository
</a
>, build and install the
5234 package. You might have to log out and in again activate the
5235 autostart script.
</p
>
5237 <p
>The design is simple:
</p
>
5241 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5242 hw-support-handlerd to start when the user log in.
</li
>
5244 <li
>This program listen for kernel events about new hardware (directly
5245 from the kernel like udev does), not using HAL dbus events as I
5246 initially did.
</li
>
5248 <li
>When new hardware is inserted, look up the hardware modalias in
5249 the APT database, a database
5250 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
5251 via HTTP
</a
> and a database available as part of the package.
</li
>
5253 <li
>If a package is mapped to the hardware in question, the package
5254 isn
't installed yet and this is the first time the hardware was
5255 plugged in, show a desktop notification suggesting to install the
5256 package or packages.
</li
>
5258 <li
>If the user click on the
'install package now
' button, ask
5259 aptdaemon via the PackageKit API to install the requrired package.
</li
>
5261 <li
>aptdaemon ask for root password or sudo password, and install the
5262 package while showing progress information in a window.
</li
>
5266 <p
>I still need to come up with a better name for the system. Here
5267 are some screen shots showing the prototype in action. First the
5268 notification, then the password request, and finally the request to
5269 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
5271 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
5272 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
5273 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
5274 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
5275 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
5277 <p
>The prototype still need to be improved with longer timeouts, but
5278 is already useful. The database of hardware to package mappings also
5279 need more work. It is currently compatible with the Ubuntu way of
5280 storing such information in the package control file, but could be
5281 changed to use other formats instead or in addition to the current
5282 method. I
've dropped the use of discover for this mapping, as the
5283 modalias approach is more flexible and easier to use on Linux as long
5284 as the Linux kernel expose its modalias strings directly.
</p
>
5286 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
5287 here is the command required to check out and build the source: Use
5288 '<tt
>svn checkout
5289 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5290 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
5291 devscripts package.
</p
>
5293 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
5294 renamed to Isenkram and the source moved from the Debian Edu
5295 subversion repository to a Debian collab-maint git repository. See
5296 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
5297 instructions
</a
> for details.
</p
>
5302 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
5303 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
5304 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
5305 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
5306 <description><p
>This Christmas my trusty old laptop died. It died quietly and
5307 suddenly in bed. With a quiet whimper, it went completely quiet and
5308 black. The power button was no longer able to turn it on. It was a
5309 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5310 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5311 Compaq I had before that. Now I need to find a replacement. To keep
5312 going during Christmas, I moved the one year old SSD disk to my old
5313 X40 where it fitted (only one I had left that could use it), but it is
5314 not a durable solution.
5316 <p
>My laptop needs are fairly modest. This is my wishlist from when I
5317 got a new one more than
10 years ago. It still holds true.:)
</p
>
5321 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
5322 than A4).
</li
>
5323 <li
>Robust, it will be in my backpack every day.
</li
>
5324 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
5325 <li
>Long battery life time. Preferable a week.
</li
>
5326 <li
>Internal WIFI network card.
</li
>
5327 <li
>Internal Twisted Pair network card.
</li
>
5328 <li
>Some USB slots (
2-
3 is plenty)
</li
>
5329 <li
>Good keyboard - similar to the Thinkpad.
</li
>
5330 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
5332 <li
>Hardware supported by Debian Stable, ie the default kernel and
5333 X.org packages.
</li
>
5334 <li
>Quiet, preferably fan free (or at least not using the fan most of
5339 <p
>You will notice that there are no RAM and CPU requirements in the
5340 list. The reason is simply that the specifications on laptops the
5341 last
10-
15 years have been sufficient for my needs, and I have to look
5342 at other features to choose my laptop. But are there still made as
5343 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5344 robust, and Thinkpads seem to be heading in the wrong direction since
5345 Lenovo took over. But I
've been told that X220 and X1 Carbon might
5346 still be useful.
</p
>
5348 <p
>Perhaps I should rethink my needs, and look for a pad with an
5349 external keyboard? I
'll have to check the
5350 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
5351 well-supported laptops, or perhaps just buy one preinstalled from one
5352 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
5353 Pre-loaded site
</a
>.
</p
>
5358 <title>How to find a browser plugin supporting a given MIME type
</title>
5359 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5360 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5361 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5362 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5363 install to get support for a given MIME type. Thanks to
5364 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5365 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5366 Unfortunately, not very many packages provide the needed meta
5367 information, Anyway, here is a small script to look up all browser
5368 plugin packages announcing ther MIME support using this specification:
</p
>
5374 def pkgs_handling_mimetype(mimetype):
5379 version = pkg.candidate
5381 version = pkg.installed
5384 record = version.record
5385 if not record.has_key(
'Npp-MimeType
'):
5387 mime_types = record[
'Npp-MimeType
'].split(
',
')
5388 for t in mime_types:
5389 t = t.rstrip().strip()
5391 thepkgs.append(pkg.name)
5393 mimetype =
"audio/ogg
"
5394 if
1 < len(sys.argv):
5395 mimetype = sys.argv[
1]
5396 print
"Browser plugin packages supporting %s:
" % mimetype
5397 for pkg in pkgs_handling_mimetype(mimetype):
5398 print
" %s
" %pkg
5401 <p
>It can be used like this to look up a given MIME type:
</p
>
5404 % ./apt-find-browserplug-for-mimetype
5405 Browser plugin packages supporting audio/ogg:
5407 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5408 Browser plugin packages supporting application/x-shockwave-flash:
5409 browser-plugin-gnash
5413 <p
>In Ubuntu this mechanism is combined with support in the browser
5414 itself to query for plugins and propose to install the needed
5415 packages. It would be great if Debian supported such feature too. Is
5416 anyone working on adding it?
</p
>
5418 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5419 request for icweasel support for this feature is
5420 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5421 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5422 of manpower and wish for a different design is the reason thus feature
5423 is not yet in iceweasel from Debian.
</p
>
5428 <title>What is the most supported MIME type in Debian?
</title>
5429 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5430 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5431 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5432 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5433 proposal to add AppStream information to the Debian archive
</a
>, is a
5434 proposal to make it possible for a Desktop application to propose to
5435 the user some package to install to gain support for a given MIME
5436 type, font, library etc. that is currently missing. With such
5437 mechanism in place, it would be possible for the desktop to
5438 automatically propose and install leocad if some LDraw file is
5439 downloaded by the browser.
</p
>
5441 <p
>To get some idea about the current content of the archive, I decided
5442 to write a simple program to extract all .desktop files from the
5443 Debian archive and look up the claimed MIME support there. The result
5445 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5446 site
</a
>. Using the collected information, it become possible to
5447 answer the question in the title. Here are the
20 most supported MIME
5448 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5449 The complete list is available from the link above.
</p
>
5451 <p
><strong
>Debian Stable:
</strong
></p
>
5455 ----- -----------------------
5471 18 application/x-ogg
5478 <p
><strong
>Debian Testing:
</strong
></p
>
5482 ----- -----------------------
5498 18 application/x-ogg
5505 <p
><strong
>Debian Unstable:
</strong
></p
>
5509 ----- -----------------------
5526 18 application/x-ogg
5532 <p
>I am told that PackageKit can provide an API to access the kind of
5533 information mentioned in DEP-
11. I have not yet had time to look at
5534 it, but hope the PackageKit people in Debian are on top of these
5537 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5538 discovering a typo in my script.
</p
>
5543 <title>Using modalias info to find packages handling my hardware
</title>
5544 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5545 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5546 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
5547 <description><p
>Yesterday, I wrote about the
5548 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
5549 values provided by the Linux kernel
</a
> following my hope for
5550 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
5551 dongle support in Debian
</a
>. Using this knowledge, I have tested how
5552 modalias values attached to package names can be used to map packages
5553 to hardware. This allow the system to look up and suggest relevant
5554 packages when I plug in some new hardware into my machine, and replace
5555 discover and discover-data as the database used to map hardware to
5558 <p
>I create a modaliases file with entries like the following,
5559 containing package name, kernel module name (if relevant, otherwise
5560 the package name) and globs matching the relevant hardware
5563 <p
><blockquote
>
5564 Package: package-name
5565 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
5566 </blockquote
></p
>
5568 <p
>It is fairly trivial to write code to find the relevant packages
5569 for a given modalias value using this file.
</p
>
5571 <p
>An entry like this would suggest the video and picture application
5572 cheese for many USB web cameras (interface bus class
0E01):
</p
>
5574 <p
><blockquote
>
5576 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
5577 </blockquote
></p
>
5579 <p
>An entry like this would suggest the pcmciautils package when a
5580 CardBus bridge (bus class
0607) PCI device is present:
</p
>
5582 <p
><blockquote
>
5583 Package: pcmciautils
5584 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5585 </blockquote
></p
>
5587 <p
>An entry like this would suggest the package colorhug-client when
5588 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
5590 <p
><blockquote
>
5591 Package: colorhug-client
5592 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
5593 </blockquote
></p
>
5595 <p
>I believe the format is compatible with the format of the Packages
5596 file in the Debian archive. Ubuntu already uses their Packages file
5597 to store their mappings from packages to hardware.
</p
>
5599 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
5600 announce the hardware it support in a way my prototype understand.
5601 This allow those publishing packages in an APT source outside the
5602 Debian archive as well as those backporting packages to make sure the
5603 hardware mapping are included in the package meta information. I
've
5604 tested such header in the pymissile package, and its modalias mapping
5605 is working as it should with my prototype. It even made it to Ubuntu
5608 <p
>To test if it was possible to look up supported hardware using only
5609 the shell tools available in the Debian installer, I wrote a shell
5610 implementation of the lookup code. The idea is to create files for
5611 each modalias and let the shell do the matching. Please check out and
5613 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
5614 shell script. It run without any extra dependencies and fetch the
5615 hardware mappings from the Debian archive and the subversion
5616 repository where I currently work on my prototype.
</p
>
5618 <p
>When I use it on a machine with a yubikey inserted, it suggest to
5619 install yubikey-personalization:
</p
>
5621 <p
><blockquote
>
5622 % ./hw-support-lookup
5623 <br
>yubikey-personalization
5625 </blockquote
></p
>
5627 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5628 propose to install the pcmciautils package:
</p
>
5630 <p
><blockquote
>
5631 % ./hw-support-lookup
5632 <br
>pcmciautils
5634 </blockquote
></p
>
5636 <p
>If you know of any hardware-package mapping that should be added to
5637 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
5638 database
</a
>, please tell me about it.
</p
>
5640 <p
>It could be possible to generate several of the mappings between
5641 packages and hardware. One source would be to look at packages with
5642 kernel modules, ie packages with *.ko files in /lib/modules/, and
5643 extract their modalias information. Another would be to look at
5644 packages with udev rules, ie packages with files in
5645 /lib/udev/rules.d/, and extract their vendor/model information to
5646 generate a modalias matching rule. I have not tested any of these to
5647 see if it work.
</p
>
5649 <p
>If you want to help implementing a system to let us propose what
5650 packages to install when new hardware is plugged into a Debian
5651 machine, please send me an email or talk to me on
5652 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5657 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
5658 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
5659 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
5660 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
5661 <description><p
>While looking into how to look up Debian packages based on hardware
5662 information, to find the packages that support a given piece of
5663 hardware, I refreshed my memory regarding modalias values, and decided
5664 to document the details. Here are my findings so far, also available
5666 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5667 Debian Edu subversion repository
</a
>:
5669 <p
><strong
>Modalias decoded
</strong
></p
>
5671 <p
>This document try to explain what the different types of modalias
5672 values stands for. It is in part based on information from
5673 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
5674 &lt;URL:
<a href=
"http://unix.stackexchange.com/questions/
26132/how-to-assign-usb-driver-to-device
">http://unix.stackexchange.com/questions/
26132/how-to-assign-usb-driver-to-device
</a
> &gt;,
5675 &lt;URL:
<a href=
"http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c
">http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c
</a
> &gt; and
5676 &lt;URL:
<a href=
"http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode
&view=markup
">http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode
&view=markup
</a
> &gt;.
5678 <p
>The modalias entries for a given Linux machine can be found using
5679 this shell script:
</p
>
5682 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
5685 <p
>The supported modalias globs for a given kernel module can be found
5686 using modinfo:
</p
>
5689 % /sbin/modinfo psmouse | grep alias:
5690 alias: serio:ty05pr*id*ex*
5691 alias: serio:ty01pr*id*ex*
5695 <p
><strong
>PCI subtype
</strong
></p
>
5697 <p
>A typical PCI entry can look like this. This is an Intel Host
5698 Bridge memory controller:
</p
>
5700 <p
><blockquote
>
5701 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5702 </blockquote
></p
>
5704 <p
>This represent these values:
</p
>
5709 sv
00001028 (subvendor)
5710 sd
000001AD (subdevice)
5712 sc
00 (bus subclass)
5716 <p
>The vendor/device values are the same values outputted from
'lspci
5717 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
5718 0600. The
0600 class is a host bridge. Other useful bus values are
5719 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
5721 <p
>Not sure how to figure out the interface value, nor what it
5724 <p
><strong
>USB subtype
</strong
></p
>
5726 <p
>Some typical USB entries can look like this. This is an internal
5727 USB hub in a laptop:
</p
>
5729 <p
><blockquote
>
5730 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5731 </blockquote
></p
>
5733 <p
>Here is the values included in this alias:
</p
>
5736 v
1D6B (device vendor)
5737 p
0001 (device product)
5739 dc
09 (device class)
5740 dsc
00 (device subclass)
5741 dp
00 (device protocol)
5742 ic
09 (interface class)
5743 isc
00 (interface subclass)
5744 ip
00 (interface protocol)
5747 <p
>The
0900 device class/subclass means hub. Some times the relevant
5748 class is in the interface class section. For a simple USB web camera,
5749 these alias entries show up:
</p
>
5751 <p
><blockquote
>
5752 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5753 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5754 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5755 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5756 </blockquote
></p
>
5758 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
5759 camera),
0101 is audio control device and
0102 is audio streaming (aka
5760 microphone). Thus this is a camera with microphone included.
</p
>
5762 <p
><strong
>ACPI subtype
</strong
></p
>
5764 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
5765 receiver in a Thinkpad X40:
</p
>
5767 <p
><blockquote
>
5768 acpi:IBM0071:PNP0511:
5769 </blockquote
></p
>
5771 <p
>The values between the colons are IDs.
</p
>
5773 <p
><strong
>DMI subtype
</strong
></p
>
5775 <p
>The DMI table contain lots of information about the computer case
5776 and model. This is an entry for a IBM Thinkpad X40, fetched from
5777 /sys/devices/virtual/dmi/id/modalias:
</p
>
5779 <p
><blockquote
>
5780 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5781 </blockquote
></p
>
5783 <p
>The values present are
</p
>
5786 bvn IBM (BIOS vendor)
5787 bvr
1UETB
6WW(
1.66) (BIOS version)
5788 bd
06/
15/
2005 (BIOS date)
5789 svn IBM (system vendor)
5790 pn
2371H4G (product name)
5791 pvr ThinkPadX40 (product version)
5792 rvn IBM (board vendor)
5793 rn
2371H4G (board name)
5794 rvr NotAvailable (board version)
5795 cvn IBM (chassis vendor)
5796 ct
10 (chassis type)
5797 cvr NotAvailable (chassis version)
5800 <p
>The chassis type
10 is Notebook. Other interesting values can be
5801 found in the dmidecode source:
</p
>
5805 4 Low Profile Desktop
5818 17 Main Server Chassis
5819 18 Expansion Chassis
5821 20 Bus Expansion Chassis
5822 21 Peripheral Chassis
5824 23 Rack Mount Chassis
5833 <p
>The chassis type values are not always accurately set in the DMI
5834 table. For example my home server is a tower, but the DMI modalias
5835 claim it is a desktop.
</p
>
5837 <p
><strong
>SerIO subtype
</strong
></p
>
5839 <p
>This type is used for PS/
2 mouse plugs. One example is from my
5840 test machine:
</p
>
5842 <p
><blockquote
>
5843 serio:ty01pr00id00ex00
5844 </blockquote
></p
>
5846 <p
>The values present are
</p
>
5855 <p
>This type is supported by the psmouse driver. I am not sure what
5856 the valid values are.
</p
>
5858 <p
><strong
>Other subtypes
</strong
></p
>
5860 <p
>There are heaps of other modalias subtypes according to
5861 file2alias.c. There is the rest of the list from that source: amba,
5862 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5863 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5864 vmbus, x86cpu and zorro. I did not spend time documenting all of
5865 these, as they do not seem relevant for my intended use with mapping
5866 hardware to packages when new stuff is inserted during run time.
</p
>
5868 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
5870 <p
>To check which kernel modules provide support for a given modalias,
5871 one can use the following shell script:
</p
>
5874 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
5875 echo
"$id
" ; \
5876 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
5880 <p
>The output can look like this (only the first few entries as the
5881 list is very long on my test machine):
</p
>
5885 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
5887 FATAL: Module acpi:device: not found.
5889 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
5890 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
5891 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
5892 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5893 acpi:IBM0071:PNP0511:
5894 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
5895 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
5896 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
5900 <p
>If you want to help implementing a system to let us propose what
5901 packages to install when new hardware is plugged into a Debian
5902 machine, please send me an email or talk to me on
5903 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5905 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
5906 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
5907 in /sys/ with space in them.
</p
>
5912 <title>Moved the pymissile Debian packaging to collab-maint
</title>
5913 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
5914 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
5915 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
5916 <description><p
>As part of my investigation on how to improve the support in Debian
5917 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5918 Launcher and updated the Debian package
5919 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
5920 sure udev will fix the device permissions when it is plugged in. I
5921 also added a
"Modaliases
" header to test it in the Debian archive and
5922 hopefully make the package be proposed by jockey in Ubuntu when a user
5923 plug in his rocket launcher. In the process I moved the source to a
5924 git repository under collab-maint, to make it easier for any DD to
5925 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
5926 is not very active, but the software still work for me even after five
5927 years of relative silence. The new git repository is not listed in
5928 the uploaded package yet, because I want to test the other changes a
5929 bit more before I upload the new version. If you want to check out
5930 the new version with a .desktop file included, visit the
5931 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
5932 view
</a
> or use
"<tt
>git clone
5933 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
5938 <title>Lets make hardware dongles easier to use in Debian
</title>
5939 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
5940 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
5941 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
5942 <description><p
>One thing that annoys me with Debian and Linux distributions in
5943 general, is that there is a great package management system with the
5944 ability to automatically install software packages by downloading them
5945 from the distribution mirrors, but no way to get it to automatically
5946 install the packages I need to use the hardware I plug into my
5947 machine. Even if the package to use it is easily available from the
5948 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5949 suggest to automatically install the python-nxt, nbc and t2n packages
5950 I need to talk to it. When I plug in a Yubikey, it could propose the
5951 yubikey-personalization package. The information required to do this
5952 is available, but no-one have pulled all the pieces together.
</p
>
5954 <p
>Some years ago, I proposed to
5955 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
5956 the discover subsystem to implement this
</a
>. The idea is fairly
5961 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
5962 starting when a user log in.
</li
>
5964 <li
>Set this program up to listen for kernel events emitted when new
5965 hardware is inserted into the computer.
</li
>
5967 <li
>When new hardware is inserted, look up the hardware ID in a
5968 database mapping to packages, and take note of any non-installed
5969 packages.
</li
>
5971 <li
>Show a message to the user proposing to install the discovered
5972 package, and make it easy to install it.
</li
>
5976 <p
>I am not sure what the best way to implement this is, but my
5977 initial idea was to use dbus events to discover new hardware, the
5978 discover database to find packages and
5979 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
5982 <p
>Yesterday, I found time to try to implement this idea, and the
5983 draft package is now checked into
5984 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5985 Debian Edu subversion repository
</a
>. In the process, I updated the
5986 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
5987 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5988 the relevant packages in Debian, and uploaded a new version
5989 2.2013.01.09 to unstable. I also discovered that the current
5990 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
5991 package in Debian no longer discovered any USB devices, because
5992 /proc/bus/usb/devices is no longer present. I ported it to use
5993 libusb as a fall back option to get it working. The fixed package
5994 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
5995 because of the freeze).
</p
>
5997 <p
>With this prototype in place, I can insert my Yubikey, and get this
5998 desktop notification to show up (only once, the first time it is
5999 inserted):
</p
>
6001 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6003 <p
>For this prototype to be really useful, some way to automatically
6004 install the proposed packages by pressing the
"Please install
6005 program(s)
" button should to be implemented.
</p
>
6007 <p
>If this idea seem useful to you, and you want to help make it
6008 happen, please help me update the discover-data database with mappings
6009 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6010 list the package you would like to have installed when a given
6011 hardware device is inserted into your computer, and report bugs using
6012 reportbug if it isn
't. Or, if you know of a better way to provide
6013 such mapping, please let me know.
</p
>
6015 <p
>This prototype need more work, and there are several questions that
6016 should be considered before it is ready for production use. Is dbus
6017 the correct way to detect new hardware? At the moment I look for HAL
6018 dbus events on the system bus, because that is the events I could see
6019 on my Debian Squeeze KDE desktop. Are there better events to use?
6020 How should the user be notified? Is the desktop notification
6021 mechanism the best option, or should the background daemon raise a
6022 popup instead? How should packages be installed? When should they
6023 not be installed?
</p
>
6025 <p
>If you want to help getting such feature implemented in Debian,
6026 please send me an email. :)
</p
>
6031 <title>New IRC channel for LEGO designers using Debian
</title>
6032 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6033 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6034 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6035 <description><p
>During Christmas, I have worked a bit on the Debian support for
6036 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6037 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6038 discovered I had to build all the tools myself because none were
6039 already in Debian Squeeze. If Debian support for LEGO is something
6040 you care about, please join me on the IRC channel
6041 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6042 irc.debian.org). There is a lot that could be done to improve the
6043 Debian support for LEGO designers. For example both CAD software
6044 and Mindstorm compilers are missing. :)
</p
>
6046 <p
>Update
2012-
01-
03: A
6047 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6048 including links to Lego related packages is now available.
</p
>
6053 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6054 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6055 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6056 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6057 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6058 year! I hope next year will prove to be a good year.
</p
>
6060 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6061 decentralised
"currency
" that allow people to transfer bitcoins
6062 between each other with minimal overhead, is a very interesting
6063 experiment. And as I wrote a few days ago, the bitcoin situation in
6064 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6065 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6066 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6067 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6068 for one of the ftpmasters to approve the new bitcoin-qt package
6071 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6072 team in Debian, you can easily test the package in Debian Squeeze
6073 using the following steps to get a set of working packages:
</p
>
6075 <blockquote
><pre
>
6076 git clone git://git.debian.org/git/collab-maint/bitcoin
6078 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6079 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6080 </pre
></blockquote
>
6082 <p
>You might have to install some build dependencies as well. The
6083 list of commands should give you two packages, bitcoind and
6084 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6085 client will download the complete set of bitcoin
"blocks
", which need
6086 around
5.6 GiB of data on my machine at the moment. Make sure your
6087 ~/.bitcoin/ directory have lots of spare room if you want to download
6088 all the blocks. The client will warn if the disk is getting full, so
6089 there is not really a problem if you got too little room, but you will
6090 not be able to get all the features out of the client.
</p
>
6092 <p
>As usual, if you use bitcoin and want to show your support of my
6093 activities, please send Bitcoin donations to my address
6094 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6099 <title>A word on bitcoin support in Debian
</title>
6100 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6102 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6103 <description><p
>It has been a while since I wrote about
6104 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6105 peer-to-peer based crypto-currency, and the reason is simply that I
6106 have been busy elsewhere. But two days ago, I started looking at the
6107 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6108 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6109 is now maintained by a
6110 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6111 people
</a
>, and the grunt work had already been done by this team. We
6112 owe a huge thank you to all these team members. :)
6113 But I was sad to discover that the bitcoin client is missing in
6114 Wheezy. It is only available in Sid (and an outdated client from
6115 backports). The client had several RC bugs registered in BTS blocking
6116 it from entering testing. To try to help the team and improve the
6117 situation, I spent some time providing patches and triaging the bug
6118 reports. I also had a look at the bitcoin package available from Matt
6120 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6121 Ubuntu
</a
>, and moved the useful pieces from that version into the
6122 Debian package.
</p
>
6124 <p
>After checking with the main package maintainer Jonas Smedegaard on
6125 IRC, I pushed several patches into the collab-maint git repository to
6126 improve the package. It now contains fixes for the RC issues (not from
6127 me, but fixed by Scott Howard), build rules for a Qt GUI client
6128 package, konqueror support for the bitcoin: URI and bash completion
6129 setup. As I work on Debian Squeeze, I also created
6130 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6131 patch to backport
</a
> the latest version. Jonas is going to look at
6132 it and try to integrate it into the git repository before uploading a
6133 new version to unstable.
6135 <p
>I would very much like bitcoin to succeed, to get rid of the
6136 centralized control currently exercised in the monetary system. I
6137 find it completely unacceptable that the USA government is collecting
6138 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6139 that the major credit card companies can block legal money
6140 transactions to Wikileaks. But for bitcoin to succeed, more people
6141 need to use bitcoins, and more people need to accept bitcoins when
6142 they sell products and services. Improving the bitcoin support in
6143 Debian is a small step in the right direction, but not enough.
6144 Unfortunately the user experience when browsing the web and wanting to
6145 pay with bitcoin is still not very good. The bitcoin: URI is a step
6146 in the right direction, but need to work in most or every browser in
6147 use. Also the bitcoin-qt client is too heavy to fire up to do a
6148 quick transaction. I believe there are other clients available, but
6149 have not tested them.
</p
>
6152 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6153 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6154 I received
20.15 BTC so far on the address I provided in my blog two
6155 years ago, as can be
6156 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6157 on the blockexplorer service
</a
>. Thank you everyone for your
6158 donation. The blockexplorer service demonstrates quite well that
6159 bitcoin is not quite anonymous and untracked. :) I wonder if the
6160 number of users have gone up since then. If you use bitcoin and want
6161 to show your support of my activity, please send Bitcoin donations to
6162 the same address as last time,
6163 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6168 <title>Git repository for song book for Computer Scientists
</title>
6169 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6170 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6171 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6172 <description><p
>As I
6173 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6174 this summer
</a
>, I have created a Computer Science song book a few
6175 years ago, and today I finally found time to create a public
6176 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6177 repository for the project
</a
>.
</p
>
6179 <p
>If you want to help out, please clone the source and submit patches
6180 to the HTML version. To generate the PDF and PostScript version,
6181 please use prince XML, or let me know about a useful free software
6182 processor capable of creating a good looking PDF from the HTML.
</p
>
6184 <p
>Want to sing? You can still find the song book in HTML, PDF and
6185 PostScript formats at
6186 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6187 Science Songbook
</a
>.
</p
>
6192 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6193 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6194 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6195 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6196 <description><p
>I dag fyller
6197 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6198 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6199 si gratulerer med dagen, Debian!
</p
>
6204 <title>Song book for Computer Scientists
</title>
6205 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6207 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6208 <description><p
>Many years ago, while studying Computer Science at the
6209 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6210 collecting computer related songs for use at parties. The original
6211 version was written in LaTeX, but a few years ago I got help from
6212 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6213 while keeping the ability to create a nice book in PDF format. I have
6214 not had time to maintain the book for a while now, and guess I should
6215 put it up on some public version control repository where others can
6216 help me extend and update the book. If anyone is volunteering to help
6217 me with this, send me an email. Also let me know if there are songs
6218 missing in my book.
</p
>
6220 <p
>I have not mentioned the book on my blog so far, and it occured to
6221 me today that I really should let all my readers share the joys of
6222 singing out load about programming, computers and computer networks.
6223 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6224 12</a
> is about to start (and I am not going). Want to sing? Check
6225 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6226 Computer Science Songbook
</a
>.
6231 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6232 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6233 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6234 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6235 <description><p
>At work we have heaps of servers. I believe the total count is
6236 around
1000 at the moment. To be able to get help from the vendors
6237 when something go wrong, we want to keep the firmware on the servers
6238 up to date. If the firmware isn
't the latest and greatest, the
6239 vendors typically refuse to start debugging any problems until the
6240 firmware is upgraded. So before every reboot, we want to upgrade the
6241 firmware, and we would really like everyone handling servers at the
6242 university to do this themselves when they plan to reboot a machine.
6243 For that to happen we at the unix server admin group need to provide
6244 the tools to do so.
</p
>
6246 <p
>To make firmware upgrading easier, I am working on a script to
6247 fetch and install the latest firmware for the servers we got. Most of
6248 our hardware are from Dell and HP, so I have focused on these servers
6249 so far. This blog post is about the Dell part.
</P
>
6251 <p
>On the Dell FTP site I was lucky enough to find
6252 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
6253 with firmware information for all
11th generation servers, listing
6254 which firmware should be used on a given model and where on the FTP
6255 site I can find it. Using a simple perl XML parser I can then
6256 download the shell scripts Dell provides to do firmware upgrades from
6257 within Linux and reboot when all the firmware is primed and ready to
6258 be activated on the first reboot.
</p
>
6260 <p
>This is the Dell related fragment of the perl code I am working on.
6261 Are there anyone working on similar tools for firmware upgrading all
6262 servers at a site? Please get in touch and lets share resources.
</p
>
6264 <p
><pre
>
6268 use File::Temp qw(tempdir);
6270 # Install needed RHEL packages if missing
6272 'XML::Simple
' =
> 'perl-XML-Simple
',
6274 for my $module (keys %rhelmodules) {
6275 eval
"use $module;
";
6277 my $pkg = $rhelmodules{$module};
6278 system(
"yum install -y $pkg
");
6279 eval
"use $module;
";
6283 my $errorsto =
'pere@hungry.com
';
6289 sub run_firmware_script {
6290 my ($opts, $script) = @_;
6292 print STDERR
"fail: missing script name\n
";
6295 print STDERR
"Running $script\n\n
";
6297 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
6298 print STDERR
"success: firmware script ran succcessfully\n
";
6300 print STDERR
"fail: firmware script returned error\n
";
6304 sub run_firmware_scripts {
6305 my ($opts, @dirs) = @_;
6306 # Run firmware packages
6307 for my $dir (@dirs) {
6308 print STDERR
"info: Running scripts in $dir\n
";
6309 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
6310 while (my $s = readdir $dh) {
6311 next if $s =~ m/^\.\.?/;
6312 run_firmware_script($opts,
"$dir/$s
");
6320 print STDERR
"info: Downloading $url\n
";
6321 system(
"wget --quiet \
"$url\
"");
6326 my $product = `dmidecode -s system-product-name`;
6329 if ($product =~ m/PowerEdge/) {
6331 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6332 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
6334 my $tmpdir = tempdir(
6338 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
6339 system(
'gunzip Catalog.xml.gz
');
6340 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
6341 # -q is quiet, disabling interactivity and reducing console output
6342 my $fwopts =
"-q
";
6344 for my $url (@paths) {
6345 fetch_dell_fw($url);
6347 run_firmware_scripts($fwopts, $tmpdir);
6349 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6350 print STDERR
"error: Please report to $errorsto.\n
";
6354 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6355 print STDERR
"error: Please report to $errorsto.\n
";
6361 my $url =
"ftp://ftp.us.dell.com/$path
";
6365 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6366 # firmware packages to download from Dell. Only work for Linux
6367 # machines and
11th generation Dell servers.
6368 sub fetch_dell_fw_list {
6369 my $filename = shift;
6371 my $product = `dmidecode -s system-product-name`;
6373 my ($mybrand, $mymodel) = split(/\s+/, $product);
6375 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6377 my $xml = XMLin($filename);
6379 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6380 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6381 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6383 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6384 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6386 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6388 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6390 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6393 for my $component (@{$xml-
>{SoftwareComponent}}) {
6394 my $componenttype = $component-
>{ComponentType}-
>{value};
6396 # Drop application packages, only firmware and BIOS
6397 next if
'APAC
' eq $componenttype;
6399 my $cpath = $component-
>{path};
6400 for my $path (@paths) {
6401 if ($cpath =~ m%/$path$%) {
6402 push(@paths, $cpath);
6410 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6411 it could work on other platforms with some tweaking. Anyone know a
6412 index like Catalog.xml is available from HP for HP servers? At the
6413 moment I maintain a similar list manually and it is quickly getting
6419 <title>How is booting into runlevel
1 different from single user boots?
</title>
6420 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6421 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6422 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6423 <description><p
>Wouter Verhelst have some
6424 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6425 comments and opinions
</a
> on my blog post on
6426 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6427 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6428 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6429 default KDE desktop in Debian
</a
>. I only have time to address one
6430 small piece of his comment now, and though it best to address the
6431 misunderstanding he bring forward:
</p
>
6433 <p
><blockquote
>
6434 Currently, a system admin has four options: [...] boot to a
6435 single-user system (by adding
'single
' to the kernel command line;
6436 this runs rcS and rc1 scripts)
6437 </blockquote
></p
>
6439 <p
>This make me believe Wouter believe booting into single user mode
6440 and booting into runlevel
1 is the same. I am not surprised he
6441 believe this, because it would make sense and is a quite sensible
6442 thing to believe. But because the boot in Debian is slightly broken,
6443 runlevel
1 do not work properly and it isn
't the same as single user
6444 mode. I
'll try to explain what is actually happing, but it is a bit
6445 hard to explain.
</p
>
6447 <p
>Single user mode is defined like this in /etc/inittab:
6448 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
6449 executed in single user mode is sulogin. Single user mode is a boot
6450 state
"between
" the runlevels, and when booting into single user mode,
6451 only the scripts in /etc/rcS.d/ are executed before the init process
6452 enters the single user state. When switching to runlevel
1, the state
6453 is in fact not ending in runlevel
1, but it passes through runlevel
1
6454 and end up in the single user mode (see /etc/rc1.d/S03single, which
6455 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
6456 1. It is confusing that the
'S
' (single user) init mode is not the
6457 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6460 <p
>This summary might make it clearer. When booting for the first
6461 time into single user mode, the following commands are executed:
6462 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
6463 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
6464 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
6465 trying to continue after visiting single user mode. Not all services
6466 are started again as they should, causing the machine to end up in an
6467 unpredicatble state. This is why Debian admins recommend rebooting
6468 after visiting single user mode.
</p
>
6470 <p
>A similar problem with runlevel
1 is caused by the amount of
6471 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
6472 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6473 stopped when passing through the scripts in /etc/rc1.d/, and not
6474 started again when switching away from runlevel
1 to the runlevels
6475 2-
5. I believe the problem is best fixed by moving all the scripts
6476 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6477 functioning single user mode during boot.
</p
>
6479 <p
>I have spent several years investigating the Debian boot system,
6480 and discovered this problem a few years ago. I suspect it originates
6481 from when sysvinit was introduced into Debian, a long time ago.
</p
>
6486 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
6487 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
6488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
6489 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
6490 <description><p
>In the Debian boot system, several packages include scripts that
6491 are started from /etc/rcS.d/. In fact, there is a bite more of them
6492 than make sense, and this causes a few problems. What kind of
6493 problems, you might ask. There are at least two problems. The first
6494 is that it is not possible to recover a machine after switching to
6495 runlevel
1. One need to actually reboot to get the machine back to
6496 the expected state. The other is that single user boot will sometimes
6497 run into problems because some of the subsystems are activated before
6498 the root login is presented, causing problems when trying to recover a
6499 machine from a problem in that subsystem. A minor additional point is
6500 that moving more scripts out of rcS.d/ and into the other rc#.d/
6501 directories will increase the amount of scripts that can run in
6502 parallel during boot, and thus decrease the boot time.
</p
>
6504 <p
>So, which scripts should start from rcS.d/. In short, only the
6505 scripts that _have_ to execute before the root login prompt is
6506 presented during a single user boot should go there. Everything else
6507 should go into the numeric runlevels. This means things like
6508 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6509 the numeric runlevels. Today in Debian, there are around
115 init.d
6510 scripts that are started from rcS.d/, and most of them should be moved
6511 out. Do your package have one of them? Please help us make single
6512 user and runlevel
1 better by moving it.
</p
>
6514 <p
>Scripts setting up the screen, keyboard, system partitions
6515 etc. should still be started from rcS.d/, but there is for example no
6516 need to have the network enabled before the single user login prompt
6517 is presented.
</p
>
6519 <p
>As always, things are not so easy to fix as they sound. To keep
6520 Debian systems working while scripts migrate and during upgrades, the
6521 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6522 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6523 and the next ones can only be moved when their dependencies have been
6524 moved first. This migration must be done sequentially while we ensure
6525 that the package system upgrade packages in the right order to keep
6526 the system state correct. This will require some coordination when it
6527 comes to network related packages, but most of the packages with
6528 scripts that should migrate do not have anything in rcS.d/ depending
6529 on them. Some packages have already been updated, like the sudo
6530 package, while others are still left to do. I wish I had time to work
6531 on this myself, but real live constrains make it unlikely that I will
6532 find time to push this forward.
</p
>
6537 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6538 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6539 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6540 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6541 <description><p
>While at Debconf11, I have several times during discussions
6542 mentioned the issues I believe should be improved in Debian for its
6543 desktop to be useful for more people. The use case for this is my
6544 parents, which are currently running Kubuntu which solve the
6547 <p
>I suspect these four missing features are not very hard to
6548 implement. After all, they are present in Ubuntu, so if we wanted to
6549 do this in Debian we would have a source.
</p
>
6553 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
6554 are new packages available for upgrades, a icon in the KDE status bar
6555 indicate this, and clicking on it will activate the simple upgrade
6556 tool to handle it. I have no problem guiding both of my parents
6557 through the process over the phone. If a kernel reboot is required,
6558 this too is indicated by the status bars and the upgrade tool. Last
6559 time I checked, nothing with the same features was working in KDE in
6562 <li
><strong
>Simple handling of missing Firefox browser
6563 plugins.
</strong
> When the browser encounter a MIME type it do not
6564 currently have a handler for, it will ask the user if the system
6565 should search for a package that would add support for this MIME type,
6566 and if the user say yes, the APT sources will be searched for packages
6567 advertising the MIME type in their control file (visible in the
6568 Packages file in the APT archive). If one or more packages are found,
6569 it is a simple click of the mouse to add support for the missing mime
6570 type. If the package require the user to accept some non-free
6571 license, this is explained to the user. The entire process make it
6572 more clear to the user why something do not work in the browser, and
6573 make the chances higher for the user to blame the web page authors and
6574 not the browser for any missing features.
</li
>
6576 <li
><strong
>Simple handling of missing multimedia codec/format
6577 handlers.
</strong
> When the media players encounter a format or codec
6578 it is not supporting, a dialog pop up asking the user if the system
6579 should search for a package that would add support for it. This
6580 happen with things like MP3, Windows Media or H
.264. The selection
6581 and installation procedure is very similar to the Firefox browser
6582 plugin handling. This is as far as I know implemented using a
6583 gstreamer hook. The end result is that the user easily get access to
6584 the codecs that are present from the APT archives available, while
6585 explaining more on why a given format is unsupported by Ubuntu.
</li
>
6587 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
6588 displaying a text/plain file in my Debian browser, it will propose to
6589 start emacs to show it. If I remember correctly, when doing the same
6590 in Kunbutu it show the file as a text file in the browser. At least I
6591 know Opera will show text files within the browser. I much prefer the
6592 latter behaviour.
</li
>
6596 <p
>There are other nice features as well, like the simplified suite
6597 upgrader, but given that I am the one mostly doing the dist-upgrade,
6598 it do not matter much.
</p
>
6600 <p
>I really hope we could get these features in place for the next
6601 Debian release. It would require the coordinated effort of several
6602 maintainers, but would make the end user experience a lot better.
</p
>
6607 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
6608 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
6609 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
6610 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
6611 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
6612 site is build on Debian/Squeeze, and this platform was chosen because
6613 I am most familiar with Debian (being a Debian Developer for around
10
6614 years) because it is the latest stable Debian release which should get
6615 security support for a few years.
</p
>
6617 <p
>The web service is written in Perl, and depend on some perl modules
6618 that are missing in Debian at the moment. It would be great if these
6619 modules were added to the Debian archive, allowing anyone to set up
6620 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
6621 in their own country using only Debian packages. The list of modules
6622 missing in Debian/Squeeze isn
't very long, and I hope the perl group
6623 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
6624 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6625 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6626 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6627 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6628 easier in the future.
</p
>
6630 <p
>Thanks to the great tools in Debian, getting the missing modules
6631 installed on my server was a simple call to
'cpan2deb Module::Name
'
6632 and
'dpkg -i
' to install the resulting package. But this leave me
6633 with the responsibility of tracking security problems, which I really
6634 do not have time for.
</p
>
6639 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
6640 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
6641 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
6642 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
6643 <description><p
>Here is a small update for my English readers. Most of my blog
6644 posts have been in Norwegian the last few weeks, so here is a short
6645 update in English.
</p
>
6647 <p
>The kids still keep me too busy to get much free software work
6648 done, but I did manage to organise a project to get a Norwegian port
6649 of the British service
6650 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
6651 and it has been running for a month now. The entire project has been
6652 organised by me and two others. Around Christmas we gathered sponsors
6653 to fund the development work. In January I drafted a contract with
6654 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
6655 and in February the development took place. Most of it involved
6656 converting the source to use GPS coordinates instead of British
6657 easting/northing, and the resulting code should be a lot easier to get
6658 running in any country by now. The Norwegian
6659 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
6660 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
6661 source and the source for administrative borders in Norway, and
6662 support for this had to be added/fixed.
</p
>
6664 <p
>The Norwegian version went live March
3th, and we spent the weekend
6665 polishing the system before we announced it March
7th. The system is
6666 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
6667 problem reports in a few weeks. Soon we hope to announce the Android
6668 and iPhone versions making it even easier to report problems with the
6669 public infrastructure.
</p
>
6671 <p
>Perhaps something to consider for those of you in countries without
6672 such service?
</p
>
6677 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
6678 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
6679 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
6680 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
6681 <description><p
>The last few days I have looked at ways to track open security
6682 issues here at my work with the University of Oslo. My idea is that
6683 it should be possible to use the information about security issues
6684 available on the Internet, and check our locally
6685 maintained/distributed software against this information. It should
6686 allow us to verify that no known security issues are forgotten. The
6687 CVE database listing vulnerabilities seem like a great central point,
6688 and by using the package lists from Debian mapped to CVEs provided by
6689 the testing security team, I believed it should be possible to figure
6690 out which security holes were present in our free software
6691 collection.
</p
>
6693 <p
>After reading up on the topic, it became obvious that the first
6694 building block is to be able to name software packages in a unique and
6695 consistent way across data sources. I considered several ways to do
6696 this, for example coming up with my own naming scheme like using URLs
6697 to project home pages or URLs to the Freshmeat entries, or using some
6698 existing naming scheme. And it seem like I am not the first one to
6699 come across this problem, as MITRE already proposed and implemented a
6700 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
6701 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
6702 software, hardware and other platform components. The CPE ids are
6703 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
6704 Vulnerability Database
</a
>, allowing me to look up know security
6705 issues for any CPE name. With this in place, all I need to do is to
6706 locate the CPE id for the software packages we use at the university.
6707 This is fairly trivial (I google for
'cve cpe $package
' and check the
6708 NVD entry if a CVE for the package exist).
</p
>
6710 <p
>To give you an example. The GNU gzip source package have the CPE
6711 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
6712 check out, one could look up
6713 <a href=
"http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%
3A%
2Fa%
3Agnu%
3Agzip:
1.3.3">cpe:/a:gnu:gzip:
1.3.3
6714 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
6715 The most recent one is
6716 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
6717 and at the bottom of the NVD page for this vulnerability the complete
6718 list of affected versions is provided.
</p
>
6720 <p
>The NVD database of CVEs is also available as a XML dump, allowing
6721 for offline processing of issues. Using this dump, I
've written a
6722 small script taking a list of CPEs as input and list all CVEs
6723 affecting the packages represented by these CPEs. One give it CPEs
6724 with version numbers as specified above and get a list of open
6725 security issues out.
</p
>
6727 <p
>Of course for this approach to be useful, the quality of the NVD
6728 information need to be high. For that to happen, I believe as many as
6729 possible need to use and contribute to the NVD database. I notice
6731 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
6732 map from CVE to CPE
</a
>, indicating that they are using the CPE
6733 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
6735 <p
>To get an idea about the quality for free software, I spent some
6736 time making it possible to compare the CVE database from Debian with
6737 the CVE database in NVD. The result look fairly good, but there are
6738 some inconsistencies in NVD (same software package having several
6739 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6740 Debian believe are affected by a CVE). Hope to find time to improve
6741 the quality of NVD, but that require being able to get in touch with
6742 someone maintaining it. So far my three emails with questions and
6743 corrections have not seen any reply, but I hope contact can be
6744 established soon.
</p
>
6746 <p
>An interesting application for CPEs is cross platform package
6747 mapping. It would be useful to know which packages in for example
6748 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6749 this would be trivial if all linux distributions provided CPE entries
6750 for their packages.
</p
>
6755 <title>Which module is loaded for a given PCI and USB device?
</title>
6756 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
6757 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
6758 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
6759 <description><p
>In the
6760 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
6761 package in Debian, there is a script to report useful information
6762 about the running hardware for use when people report missing
6763 information. One part of this script that I find very useful when
6764 debugging hardware problems, is the part mapping loaded kernel module
6765 to the PCI device it claims. It allow me to quickly see if the kernel
6766 module I expect is driving the hardware I am struggling with. To see
6767 the output, make sure discover-data is installed and run
6768 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
6769 one of my machines like this:
</p
>
6773 10de:
03eb i2c_nforce2
6776 10de:
03f0 snd_hda_intel
6785 <p
>The code in question look like this, slightly modified for
6786 readability and to drop the output to file descriptor
3:
</p
>
6789 if [ -d /sys/bus/pci/devices/ ] ; then
6790 echo loaded pci modules:
6792 cd /sys/bus/pci/devices/
6793 for address in * ; do
6794 if [ -d
"$address/driver/module
" ] ; then
6795 module=`cd $address/driver/module ; pwd -P | xargs basename`
6796 if grep -q
"^$module
" /proc/modules ; then
6797 address=$(echo $address |sed s/
0000://)
6798 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
6799 echo
"$id $module
"
6808 <p
>Similar code could be used to extract USB device module
6812 if [ -d /sys/bus/usb/devices/ ] ; then
6813 echo loaded usb modules:
6815 cd /sys/bus/usb/devices/
6816 for address in * ; do
6817 if [ -d
"$address/driver/module
" ] ; then
6818 module=`cd $address/driver/module ; pwd -P | xargs basename`
6819 if grep -q
"^$module
" /proc/modules ; then
6820 address=$(echo $address |sed s/
0000://)
6821 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
6822 if [
"$id
" ] ; then
6823 echo
"$id $module
"
6833 <p
>This might perhaps be something to include in other tools as
6839 <title>How to test if a laptop is working with Linux
</title>
6840 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
6841 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
6842 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
6843 <description><p
>The last few days I have spent at work here at the
<a
6844 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
6845 batch of computers will work with Linux. Every year for the last few
6846 years the university have organised shared bid of a few thousand
6847 computers, and this year HP won the bid. Two different desktops and
6848 five different laptops are on the list this year. We in the UNIX
6849 group want to know which one of these computers work well with RHEL
6850 and Ubuntu, the two Linux distributions we currently handle at the
6851 university.
</p
>
6853 <p
>My test method is simple, and I share it here to get feedback and
6854 perhaps inspire others to test hardware as well. To test, I PXE
6855 install the OS version of choice, and log in as my normal user and run
6856 a few applications and plug in selected pieces of hardware. When
6857 something fail, I make a note about this in the test matrix and move
6858 on. If I have some spare time I try to report the bug to the OS
6859 vendor, but as I only have the machines for a short time, I rarely
6860 have the time to do this for all the problems I find.
</p
>
6862 <p
>Anyway, to get to the point of this post. Here is the simple tests
6863 I perform on a new model.
</p
>
6867 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
6868 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6869 RHEL5 and Debian Edu/Squeeze.
</li
>
6871 <li
>Is X.org working? If the graphical login screen show up after
6872 installation, X.org is working.
</li
>
6874 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
6875 package mesa-utils on Ubuntu) and writing down the frames per second
6876 reported by the program.
</li
>
6878 <li
>Is sound working? With Gnome and KDE, a sound is played when
6879 logging in, and if I can hear this the test is successful. If there
6880 are several audio exits on the machine, I try them all and check if
6881 the Gnome/KDE audio mixer can control where to send the sound. I
6882 normally test this by playing
6883 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
6884 video
</a
> in Firefox/Iceweasel.
</li
>
6886 <li
>Is the USB subsystem working? I test this by plugging in a USB
6887 memory stick and see if Gnome/KDE notices this.
</li
>
6889 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
6890 I have lying around, and see if Gnome/KDE notices this.
</li
>
6892 <li
>Is any built in camera working? Test using cheese, and see if a
6893 picture from the v4l device show up.
</li
>
6895 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6896 any bluetooth devices are discovered. In my office, I normally see a
6899 <li
>For laptops, is the SD or Compaq Flash reader working. I have
6900 memory modules lying around, and stick them in and see if Gnome/KDE
6901 notice this.
</li
>
6903 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
6904 special button work, and if the laptop continue to work after
6907 <li
>For laptops, is the extra buttons working, like audio level,
6908 adjusting background light, switching on/off external video output,
6909 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6910 laptop to laptop, so I just write down which are working and which are
6913 <li
>Some laptops have smart card readers, finger print readers,
6914 acceleration sensors etc. I rarely test these, as I do not know how
6915 to quickly test if they are working or not, so I only document their
6916 existence.
</li
>
6920 <p
>By now I suspect you are really curious what the test results are
6921 for the HP machines I am testing. I
'm not done yet, so I will report
6922 the test results later. For now I can report that HP
8100 Elite work
6923 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
6924 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
6925 can see, I have most machines left to test. One interesting
6926 observation is that Ubuntu Lucid has almost twice the frame rate than
6927 RHEL6 with glxgears. No idea why.
</p
>
6932 <title>Some thoughts on BitCoins
</title>
6933 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
6934 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
6935 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
6936 <description><p
>As I continue to explore
6937 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
6938 what properties the system have, and how it will be affected by laws
6939 and regulations here in Norway. Here are some random notes.
</p
>
6941 <p
>One interesting thing to note is that since the transactions are
6942 verified using a peer to peer network, all details about a transaction
6943 is known to everyone. This means that if a BitCoin address has been
6944 published like I did with mine in my initial post about BitCoin, it is
6945 possible for everyone to see how many BitCoins have been transfered to
6946 that address. There is even a web service to look at the details for
6947 all transactions. There I can see that my address
6948 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
6949 have received
16.06 Bitcoin, the
6950 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
6951 address of Simon Phipps have received
181.97 BitCoin and the address
6952 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
6953 of EFF have received
2447.38 BitCoins so far. Thank you to each and
6954 every one of you that donated bitcoins to support my activity. The
6955 fact that anyone can see how much money was transfered to a given
6956 address make it more obvious why the BitCoin community recommend to
6957 generate and hand out a new address for each transaction. I
'm told
6958 there is no way to track which addresses belong to a given person or
6959 organisation without the person or organisation revealing it
6960 themselves, as Simon, EFF and I have done.
</p
>
6962 <p
>In Norway, and in most other countries, there are laws and
6963 regulations limiting how much money one can transfer across the border
6964 without declaring it. There are money laundering, tax and accounting
6965 laws and regulations I would expect to apply to the use of BitCoin.
6966 If the Skolelinux foundation
6967 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
6968 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
6969 normal bank transfers like EFF is doing, how should this be accounted?
6970 Given that it is impossible to know if money can cross the border or
6971 not, should everything or nothing be declared? What exchange rate
6972 should be used when calculating taxes? Would receivers have to pay
6973 income tax if the foundation were to pay Skolelinux contributors in
6974 BitCoin? I have no idea, but it would be interesting to know.
</p
>
6976 <p
>For a currency to be useful and successful, it must be trusted and
6977 accepted by a lot of users. It must be possible to get easy access to
6978 the currency (as a wage or using currency exchanges), and it must be
6979 easy to spend it. At the moment BitCoin seem fairly easy to get
6980 access to, but there are very few places to spend it. I am not really
6981 a regular user of any of the vendor types currently accepting BitCoin,
6982 so I wonder when my kind of shop would start accepting BitCoins. I
6983 would like to buy electronics, travels and subway tickets, not herbs
6984 and books. :) The currency is young, and this will improve over time
6985 if it become popular, but I suspect regular banks will start to lobby
6986 to get BitCoin declared illegal if it become popular. I
'm sure they
6987 will claim it is helping fund terrorism and money laundering (which
6988 probably would be true, as is any currency in existence), but I
6989 believe the problems should be solved elsewhere and not by blaming
6990 currencies.
</p
>
6992 <p
>The process of creating new BitCoins is called mining, and it is
6993 CPU intensive process that depend on a bit of luck as well (as one is
6994 competing against all the other miners currently spending CPU cycles
6995 to see which one get the next lump of cash). The
"winner
" get
50
6996 BitCoin when this happen. Yesterday I came across the obvious way to
6997 join forces to increase ones changes of getting at least some coins,
6998 by coordinating the work on mining BitCoins across several machines
6999 and people, and sharing the result if one is lucky and get the
50
7001 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7002 if this sounds interesting. I have not had time to try to set up a
7003 machine to participate there yet, but have seen that running on ones
7004 own for a few days have not yield any BitCoins througth mining
7007 <p
>Update
2010-
12-
15: Found an
<a
7008 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7009 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7010 it was interesting to read. The arguments presented seem to be
7011 equally valid for gold, which was used as a currency for many years.
</p
>
7016 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7017 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7018 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7019 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7020 <description><p
>With this weeks lawless
7021 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7022 attacks
</a
> on Wikileak and
7023 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7024 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7025 not be trusted to handle money transactions.
7027 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7028 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7029 mine mentioned earlier. I decided to follow Simon
's example, and get
7030 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7031 some help from my friend to get it all running, and he even handed me
7032 some bitcoins to get started. I even donated a few bitcoins to Simon
7033 for helping me remember BitCoin.
</p
>
7035 <p
>So, what is bitcoins, you probably wonder? It is a digital
7036 crypto-currency, decentralised and handled using peer-to-peer
7037 networks. It allows anonymous transactions and prohibits central
7038 control over the transactions, making it impossible for governments
7039 and companies alike to block donations and other transactions. The
7040 source is free software, and while the key dependency wxWidgets
2.9
7041 for the graphical user interface is missing in Debian, the command
7042 line client builds just fine. Hopefully Jonas
7043 <a href=
"http://bugs.debian.org/
578157">will get the package into
7044 Debian
</a
> soon.
</p
>
7046 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7047 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7048 bitcoins
</a
> when selling services and goods, and there are even
7049 currency
"stock
" markets where the exchange rate is decided. There
7050 are not many users so far, but the concept seems promising. If you
7051 want to get started and lack a friend with any bitcoins to spare,
7053 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7054 bitcoin at the time of writing). Use
7055 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7056 on the current exchange rates.
</p
>
7058 <p
>As an experiment, I have decided to set up bitcoind on one of my
7059 machines. If you want to support my activity, please send Bitcoin
7060 donations to the address
7061 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7066 <title>Why isn
't Debian Edu using VLC?
</title>
7067 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7068 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7069 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7070 <description><p
>In the latest issue of Linux Journal, the readers choices were
7071 presented, and the winner among the multimedia player were VLC.
7072 Personally, I like VLC, and it is my player of choice when I first try
7073 to play a video file or stream. Only if VLC fail will I drag out
7074 gmplayer to see if it can do better. The reason is mostly the failure
7075 model and trust. When VLC fail, it normally pop up a error message
7076 reporting the problem. When mplayer fail, it normally segfault or
7077 just hangs. The latter failure mode drain my trust in the program.
<p
>
7079 <p
>But even if VLC is my player of choice, we have choosen to use
7080 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7081 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7082 plugin to play web videos seamlessly, and the VLC browser plugin is
7083 not very good. For example, it lack in-line control buttons, so there
7084 is no way for the user to pause the video. Also, when I
7085 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7086 tested the browser plugins
</a
> available in Debian, the VLC plugin
7087 failed on several video pages where mplayer based plugins worked. If
7088 the browser plugin for VLC was as good as the gecko-mediaplayer
7089 package (which uses mplayer), we would switch.
</P
>
7091 <p
>While VLC is a good player, its user interface is slightly
7092 annoying. The most annoying feature is its inconsistent use of
7093 keyboard shortcuts. When the player is in full screen mode, its
7094 shortcuts are different from when it is playing the video in a window.
7095 For example, space only work as pause when in full screen mode. I
7096 wish it had consisten shortcuts and that space also would work when in
7097 window mode. Another nice shortcut in gmplayer is [enter] to restart
7098 the current video. It is very nice when playing short videos from the
7099 web and want to restart it when new people arrive to have a look at
7100 what is going on.
</p
>
7105 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7106 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7107 <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>
7108 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7109 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7110 upgrade testing of the
7111 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7112 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7113 This seem like a very good idea, so I adjusted by test scripts and
7114 can now present the updated result from today:
</p
>
7116 <p
>This is for Gnome:
</p
>
7118 <p
>Installed using apt-get, missing with aptitude
</p
>
7120 <blockquote
><p
>
7125 browser-plugin-gnash
7132 freedesktop-sound-theme
7134 gconf-defaults-service
7149 gnome-desktop-environment
7153 gnome-session-canberra
7158 gstreamer0.10-fluendo-mp3
7164 libapache2-mod-dnssd
7167 libaprutil1-dbd-sqlite3
7170 libboost-date-time1.42
.0
7171 libboost-python1.42
.0
7172 libboost-thread1.42
.0
7174 libchamplain-gtk-
0.4-
0
7176 libclutter-gtk-
0.10-
0
7183 libfreerdp-plugins-standard
7198 libgnomepanel2.24-cil
7203 libgtksourceview2.0-common
7204 libmono-addins-gui0.2-cil
7205 libmono-addins0.2-cil
7206 libmono-cairo2.0-cil
7207 libmono-corlib2.0-cil
7208 libmono-i18n-west2.0-cil
7209 libmono-posix2.0-cil
7210 libmono-security2.0-cil
7211 libmono-sharpzip2.84-cil
7212 libmono-system2.0-cil
7215 libndesk-dbus-glib1.0-cil
7216 libndesk-dbus1.0-cil
7226 libtelepathy-farsight0
7235 nautilus-sendto-empathy
7239 python-aptdaemon-gtk
7241 python-beautifulsoup
7256 python-gtksourceview2
7267 python-pkg-resources
7274 python-twisted-conch
7280 python-zope.interface
7285 rhythmbox-plugin-cdrecorder
7292 system-config-printer-udev
7294 telepathy-mission-control-
5
7305 </p
></blockquote
>
7307 <p
>Installed using apt-get, removed with aptitude
</p
>
7309 <blockquote
><p
>
7315 fast-user-switch-applet
7334 libgtksourceview2.0-
0
7336 libsdl1.2debian-alsa
7342 system-config-printer
7347 </p
></blockquote
>
7349 <p
>Installed using aptitude, missing with apt-get
</p
>
7351 <blockquote
><p
>
7352 gstreamer0.10-gnomevfs
7353 </p
></blockquote
>
7355 <p
>Installed using aptitude, removed with apt-get
</p
>
7357 <blockquote
><p
>
7359 </p
></blockquote
>
7361 <p
>This is for KDE:
</p
>
7363 <p
>Installed using apt-get, missing with aptitude
</p
>
7365 <blockquote
><p
>
7367 </p
></blockquote
>
7369 <p
>Installed using apt-get, removed with aptitude
</p
>
7371 <blockquote
><p
>
7374 </p
></blockquote
>
7376 <p
>Installed using aptitude, missing with apt-get
</p
>
7378 <blockquote
><p
>
7392 kdeartwork-emoticons
7394 kdeartwork-theme-icon
7398 kdebase-workspace-bin
7399 kdebase-workspace-data
7413 kscreensaver-xsavers
7428 plasma-dataengines-workspace
7430 plasma-desktopthemes-artwork
7431 plasma-runners-addons
7432 plasma-scriptengine-googlegadgets
7433 plasma-scriptengine-python
7434 plasma-scriptengine-qedje
7435 plasma-scriptengine-ruby
7436 plasma-scriptengine-webkit
7437 plasma-scriptengines
7438 plasma-wallpapers-addons
7439 plasma-widget-folderview
7440 plasma-widget-networkmanagement
7444 xscreensaver-data-extra
7446 xscreensaver-gl-extra
7447 xscreensaver-screensaver-bsod
7448 </p
></blockquote
>
7450 <p
>Installed using aptitude, removed with apt-get
</p
>
7452 <blockquote
><p
>
7454 google-gadgets-common
7472 libggadget-qt-
1.0-
0b
7477 libkonqsidebarplugin4a
7486 libplasma-geolocation-interface4
7488 libplasmagenericshell4
7502 libsmokeknewstuff2-
3
7503 libsmokeknewstuff3-
3
7505 libsmokektexteditor3
7513 libsmokeqtnetwork4-
3
7519 libsmokeqtuitools4-
3
7531 plasma-dataengines-addons
7532 plasma-scriptengine-superkaramba
7533 plasma-widget-lancelot
7534 plasma-widgets-addons
7535 plasma-widgets-workspace
7539 update-notifier-common
7540 </p
></blockquote
>
7542 <p
>Running apt-get autoremove made the results using apt-get and
7543 aptitude a bit more similar, but there are still quite a lott of
7544 differences. I have no idea what packages should be installed after
7545 the upgrade, but hope those that do can have a look.
</p
>
7550 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
7551 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
7552 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
7553 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
7554 <description><p
>Most of the computers in use by the
7555 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
7556 are virtual machines. And they have been Xen machines running on a
7557 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
7558 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
7559 bit harder that it could have been, because we set up the Xen virtual
7560 machines to get the virtual partitions from LVM, which as far as I
7561 know is not supported by KVM. So to migrate, we had to convert
7562 several LVM logical volumes to partitions on a virtual disk file.
</p
>
7565 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
7566 nice recipe
</a
> to do this, and wrote the following script to do the
7567 migration. It uses qemu-img from the qemu package to make the disk
7568 image, parted to partition it, losetup and kpartx to present the disk
7569 image partions as devices, and dd to copy the data. I NFS mounted the
7570 new servers storage area on the old server to do the migration.
</p
>
7576 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7581 if [ -z
"$
1" ] ; then
7582 echo
"Usage: $
0 &lt;hostname
&gt;
"
7588 if [ ! -e /dev/vg_data/$host-disk ] ; then
7589 echo
"error: unable to find LVM volume for $host
"
7593 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7594 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7595 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7596 totalsize=$(( ( $disksize + $swapsize ) ))
7599 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
7600 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7602 parted $img mklabel msdos
7603 parted $img mkpart primary linux-swap
0 $disksize
7604 parted $img mkpart primary ext2 $disksize $totalsize
7605 parted $img set
1 boot on
7608 losetup /dev/loop0 $img
7609 kpartx -a /dev/loop0
7611 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
7612 fsck.ext3 -f /dev/mapper/loop0p1 || true
7613 mkswap /dev/mapper/loop0p2
7615 kpartx -d /dev/loop0
7616 losetup -d /dev/loop0
7619 <p
>The script is perhaps so simple that it is not copyrightable, but
7620 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
7622 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
7623 the new disk image attached, installed grub-pc and linux-image-
686 and
7624 set up grub to boot from the disk image. After this, the KVM machines
7625 seem to work just fine.
</p
>
7630 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
7631 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
7632 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
7633 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
7634 <description><p
>I
'm still running upgrade testing of the
7635 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7636 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
7637 status. Here is a short update based on a test I ran
20101118.
</p
>
7639 <p
>I still do not know what a correct migration should look like, so I
7640 report any differences between apt and aptitude and hope someone else
7641 can see if anything should be changed.
</p
>
7643 <p
>This is for Gnome:
</p
>
7645 <p
>Installed using apt-get, missing with aptitude
</p
>
7647 <blockquote
><p
>
7648 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7649 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
7650 dmz-cursor-theme empathy empathy-common finger
7651 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7652 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7653 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7654 gnome-cards-data gnome-codec-install gnome-core
7655 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7656 gnome-search-tool gnome-session-canberra gnome-spell
7657 gnome-system-log gnome-themes-extras gnome-themes-more
7658 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7659 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7660 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7661 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7662 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
7663 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
7664 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
7665 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
7666 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
7667 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7668 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
7669 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7670 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7671 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7672 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7673 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7674 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7675 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7676 libmono-security2.0-cil libmono-sharpzip2.84-cil
7677 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
7678 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
7679 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
7680 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
7681 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
7682 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
7683 libxalan2-java libxerces2-java media-player-info mesa-utils
7684 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
7685 nautilus-sendto-empathy openoffice.org-writer2latex
7686 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
7687 python-aptdaemon python-aptdaemon-gtk python-axiom
7688 python-beautifulsoup python-bugbuddy python-clientform
7689 python-coherence python-configobj python-crypto python-cupshelpers
7690 python-cupsutils python-eggtrayicon python-elementtree
7691 python-epsilon python-evolution python-feedparser python-gdata
7692 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7693 python-gtksourceview2 python-httplib2 python-louie python-mako
7694 python-markupsafe python-mechanize python-nevow python-notify
7695 python-opengl python-openssl python-pam python-pkg-resources
7696 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7697 python-tagpy python-twisted-bin python-twisted-conch
7698 python-twisted-core python-twisted-web python-utidylib python-webkit
7699 python-xdg python-zope.interface remmina remmina-plugin-data
7700 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7701 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7702 software-center svgalibg1 system-config-printer-udev
7703 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
7704 totem totem-coherence totem-mozilla totem-plugins
7705 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7707 </p
></blockquote
>
7709 Installed using apt-get, removed with aptitude
7711 <blockquote
><p
>
7712 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7713 epiphany-extensions epiphany-gecko evolution-exchange
7714 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7715 gedit-common gnome-app-install gnome-games gnome-games-data
7716 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7717 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7718 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7719 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
7720 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
7721 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
7722 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
7723 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7724 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7725 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7726 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
7727 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
7728 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7729 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7730 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7731 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7732 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
7733 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
7734 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
7735 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
7736 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
7737 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7738 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7739 sound-juicer swfdec-gnome system-config-printer totem-common
7740 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7741 </p
></blockquote
>
7743 <p
>Installed using aptitude, missing with apt-get
</p
>
7745 <blockquote
><p
>
7746 gstreamer0.10-gnomevfs
7747 </p
></blockquote
>
7749 <p
>Installed using aptitude, removed with apt-get
</p
>
7751 <blockquote
><p
>
7753 </p
></blockquote
>
7755 <p
>This is for KDE:
</p
>
7757 <p
>Installed using apt-get, missing with aptitude
</p
>
7759 <blockquote
><p
>
7760 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
7761 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7762 ghostscript-x git gnome-audio gnugo granatier gs-common
7763 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7764 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7765 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7766 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7767 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7768 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7769 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7770 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7771 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7772 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7773 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7774 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
7775 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7776 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7777 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7778 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7779 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7780 libkrossui4 libmailtools-perl libmime-tools-perl
7781 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7782 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7783 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7784 lirc luatex marble networkstatus noatun-plugins
7785 openoffice.org-writer2latex palapeli palapeli-data parley
7786 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7787 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7788 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7790 </p
></blockquote
>
7792 <p
>Installed using apt-get, removed with aptitude
</p
>
7794 <blockquote
><p
>
7795 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7796 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7797 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7798 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7799 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7800 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7801 kitchensync kiten kjumpingcube klatin klettres klickety klines
7802 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7803 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7804 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7805 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7806 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7807 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7808 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7809 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7810 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7811 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
7812 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
7813 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7814 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
7815 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
7816 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7817 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7818 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7819 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7820 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7821 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7822 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
7823 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
7824 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7825 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7826 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7827 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7828 </p
></blockquote
>
7830 <p
>Installed using aptitude, missing with apt-get
</p
>
7832 <blockquote
><p
>
7833 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7834 kdeartwork kdebase kdebase-apps kdebase-workspace
7835 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7836 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7837 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7838 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7839 xscreensaver-screensaver-bsod
7840 </p
></blockquote
>
7842 <p
>Installed using aptitude, removed with apt-get
</p
>
7844 <blockquote
><p
>
7845 kdebase-bin konq-plugins konqueror
7846 </p
></blockquote
>
7851 <title>Gnash buildbot slave and Debian kfreebsd
</title>
7852 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
7853 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
7854 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
7855 <description><p
>Answering
7856 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
7857 call from the Gnash project
</a
> for
7858 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
7859 current source, I have set up a virtual KVM machine on the Debian
7860 Edu/Skolelinux virtualization host to test the git source on
7861 Debian/Squeeze. I hope this can help the developers in getting new
7862 releases out more often.
</p
>
7864 <p
>As the developers want less main-stream build platforms tested to,
7865 I have considered setting up a
<a
7866 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
7867 machine as well. I have also considered using the kfreebsd
7868 architecture in Debian as a file server in NUUG to get access to the
5
7869 TB zfs volume we currently use to store DV video. Because of this, I
7870 finally got around to do a test installation of Debian/Squeeze with
7871 kfreebsd. Installation went fairly smooth, thought I noticed some
7872 visual glitches in the cdebconf dialogs (black cursor left on the
7873 screen at random locations). Have not gotten very far with the
7874 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7875 fatal problem. Have to spend some more time on it to see if it is
7876 useful as a file server for NUUG. Will try to find time to set up a
7877 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
7882 <title>Debian in
3D
</title>
7883 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
7884 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
7885 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
7886 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
7888 <p
>3D printing is just great. I just came across this Debian logo in
7890 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
7891 thingiverse blog
</a
>.
</p
>
7896 <title>Software updates
2010-
10-
24</title>
7897 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
7898 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
7899 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
7900 <description><p
>Some updates.
</p
>
7902 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
7903 raise money for the project is going well. The lower limit of
10
7904 signers was reached in
24 hours, and so far
13 people have signed it.
7905 More signers and more funding is most welcome, and I am really curious
7906 how far we can get before the time limit of December
24 is reached.
7909 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
7910 about what appear to be a great code coverage tool capable of
7911 generating code coverage stats without any changes to the source code.
7913 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
7914 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
7915 It is missing in Debian, but the git source built just fine in Squeeze
7916 after I installed libelf-dev, libdwarf-dev, pkg-config and
7917 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7918 solvable. I hope kcov make it into Debian soon.
</p
>
7920 <p
>Finally found time to wrap up the release notes for
<a
7921 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
7922 new alpha release of Debian Edu
</a
>, and just published the second
7923 alpha test release of the Squeeze based Debian Edu /
7924 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
7925 release. Give it a try if you need a complete linux solution for your
7926 school, including central infrastructure server, workstations, thin
7927 client servers and diskless workstations. A nice touch added
7928 yesterday is RDP support on the thin client servers, for windows
7929 clients to get a Linux desktop on request.
</p
>
7934 <title>Some notes on Flash in Debian and Debian Edu
</title>
7935 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
7936 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
7937 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
7938 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
7939 popularity-contest numbers
</a
>, the adobe-flashplugin package the
7940 second most popular used package that is missing in Debian. The sixth
7941 most popular is flashplayer-mozilla. This is a clear indication that
7942 working flash is important for Debian users. Around
10 percent of the
7943 users submitting data to popcon.debian.org have this package
7944 installed.
</p
>
7946 <p
>In the report written by Lars Risan in August
2008
7947 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
7948 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7949 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
7950 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
7951 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
7952 web sites require Flash to work, and lacking working Flash support in
7953 the web browser and the problems with installing it was perceived as a
7954 good reason to stay with Windows.
</p
>
7956 <p
>I once saw a funny and sad comment in a web forum, where Linux was
7957 said to be the retarded cousin that did not really understand
7958 everything you told him but could work fairly well. This was a
7959 comment regarding the problems Linux have with proprietary formats and
7960 non-standard web pages, and is sad because it exposes a fairly common
7961 understanding of whose fault it is if web pages that only work in for
7962 example Internet Explorer
6 fail to work on Firefox, and funny because
7963 it explain very well how annoying it is for users when Linux
7964 distributions do not work with the documents they receive or the web
7965 pages they want to visit.
</p
>
7967 <p
>This is part of the reason why I believe it is important for Debian
7968 and Debian Edu to have a well working Flash implementation in the
7969 distribution, to get at least popular sites as Youtube and Google
7970 Video to working out of the box. For Squeeze, Debian have the chance
7971 to include the latest version of Gnash that will make this happen, as
7972 the new release
0.8.8 was published a few weeks ago and is resting in
7973 unstable. The new version work with more sites that version
0.8.7.
7974 The Gnash maintainers have asked for a freeze exception, but the
7975 release team have not had time to reply to it yet. I hope they agree
7976 with me that Flash is important for the Debian desktop users, and thus
7977 accept the new package into Squeeze.
</p
>
7982 <title>Circular package dependencies harms apt recovery
</title>
7983 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
7984 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
7985 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
7986 <description><p
>I discovered this while doing
7987 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
7988 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
7989 in Debian still got circular dependencies, and it is often claimed
7990 that apt and aptitude should be able to handle this just fine, but
7991 some times these dependency loops causes apt to fail.
</p
>
7993 <p
>An example is from todays
7994 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
7995 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
7996 causes perl-modules to fail to upgrade. The cause is simple. If a
7997 package fail to unpack, then only part of packages with the circular
7998 dependency might end up being unpacked when unpacking aborts, and the
7999 ones already unpacked will fail to configure in the recovery phase
8000 because its dependencies are unavailable.
</p
>
8002 <p
>In this log, the problem manifest itself with this error:
</p
>
8004 <blockquote
><pre
>
8005 dpkg: dependency problems prevent configuration of perl-modules:
8006 perl-modules depends on perl (
>=
5.10.1-
1); however:
8007 Version of perl on system is
5.10.0-
19lenny
2.
8008 dpkg: error processing perl-modules (--configure):
8009 dependency problems - leaving unconfigured
8010 </pre
></blockquote
>
8012 <p
>The perl/perl-modules circular dependency is already
8013 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8014 hopefully be solved as soon as possible, but it is not the only one,
8015 and each one of these loops in the dependency tree can cause similar
8016 failures. Of course, they only occur when there are bugs in other
8017 packages causing the unpacking to fail, but it is rather nasty when
8018 the failure of one package causes the problem to become worse because
8019 of dependency loops.
</p
>
8022 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8023 tireless effort by Bill Allombert
</a
>, the number of circular
8025 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8026 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8028 <p
>Todays testing also exposed a bug in
8029 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8030 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8031 apt-get and aptitude, the latter possibly caused by some circular
8032 dependency. Reported both to BTS to try to get someone to look at
8038 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8039 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8040 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8041 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8042 <description><p
>This is a
8043 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8045 <a href=
"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
">previous
8047 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8048 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8050 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8051 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8052 and dhcp3-server-ldap in Debian use the LDAP server. The two
8053 implementations are quite different in how they use LDAP.
</p
>
8055 To get this information, I started slapd with debugging enabled and
8056 dumped the debug output to a file to get the LDAP searches performed
8057 on a Debian Edu main-server. Here is a summary.
8059 <p
><strong
>powerdns
</strong
></p
>
8061 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8062 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8065 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8066 One
"strict
" mode where the forward and reverse DNS lookups are done
8067 using the same LDAP objects, and a
"tree
" mode where the forward and
8068 reverse entries are in two different subtrees in LDAP with a structure
8069 based on the DNS names, as in tjener.intern and
8070 2.2.0.10.in-addr.arpa.
</p
>
8072 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8073 base, and uses a
"base
" scoped search for the DNS name by adding
8074 "dc=tjener,dc=intern,
" to the base with a filter for
8075 "(associateddomain=tjener.intern)
" for the forward entry and
8076 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8077 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8078 forward entries, it is looking for attributes named dnsttl, arecord,
8079 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8080 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8081 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8082 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8083 spfrecord and modifytimestamp. For reverse entries it is looking for
8084 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8085 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8086 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8087 ldapsearch commands could look like this:
</p
>
8089 <blockquote
><pre
>
8090 ldapsearch -h ldap \
8091 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8092 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8093 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8094 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8095 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8096 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8098 ldapsearch -h ldap \
8099 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8100 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8101 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8102 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8103 srvrecord naptrrecord modifytimestamp
8104 </pre
></blockquote
>
8106 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8107 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8108 example LDAP objects used there. In addition to these objects, the
8109 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8110 also exist.
</p
>
8112 <blockquote
><pre
>
8113 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8115 objectclass: dnsdomain
8116 objectclass: domainrelatedobject
8119 associateddomain: tjener.intern
8121 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8123 objectclass: dnsdomain2
8124 objectclass: domainrelatedobject
8126 ptrrecord: tjener.intern
8127 associateddomain:
2.2.0.10.in-addr.arpa
8128 </pre
></blockquote
>
8130 <p
>In strict mode, the server behaves differently. When looking for
8131 forward DNS entries, it is doing a
"subtree
" scoped search with the
8132 same base as in the tree mode for a object with filter
8133 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8134 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8135 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8136 naptrrecord and modifytimestamp. For reverse entires it also do a
8137 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8138 and the requested attributes are associateddomain, dnsttl and
8139 modifytimestamp. In short, in strict mode the objects with ptrrecord
8140 go away, and the arecord attribute in the forward object is used
8143 <p
>The forward and reverse searches can be simulated using ldapsearch
8144 like this:
</p
>
8146 <blockquote
><pre
>
8147 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8148 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8149 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8150 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8151 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8152 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8154 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8155 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8156 </pre
></blockquote
>
8158 <p
>In addition to the forward and reverse searches , there is also a
8159 search for SOA records, which behave similar to the forward and
8160 reverse lookups.
</p
>
8162 <p
>A thing to note with the PowerDNS behaviour is that it do not
8163 specify any objectclass names, and instead look for the attributes it
8164 need to generate a DNS reply. This make it able to work with any
8165 objectclass that provide the needed attributes.
</p
>
8167 <p
>The attributes are normally provided in the cosine (RFC
1274) and
8168 dnsdomain2 schemas. The latter is used for reverse entries like
8169 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8171 <p
>In Debian Edu, we have created DNS objects using the object classes
8172 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8173 attributes) and domainrelatedobject (for associatedDomain). The use
8174 of structural object classes make it impossible to combine these
8175 classes with the object classes used by DHCP.
</p
>
8177 <p
>There are other schemas that could be used too, for example the
8178 dnszone structural object class used by Gosa and bind-sdb for the DNS
8179 attributes combined with the domainrelatedobject object class, but in
8180 this case some unused attributes would have to be included as well
8181 (zonename and relativedomainname).
</p
>
8183 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8184 mode and not use any of the existing objectclasses (dnsdomain,
8185 dnsdomain2 and dnszone) when one want to combine the DNS information
8186 with DHCP information, and instead create a auxiliary object class
8187 defined something like this (using the attributes defined for
8188 dnsdomain and dnsdomain2 or dnszone):
</p
>
8190 <blockquote
><pre
>
8191 objectclass ( some-oid NAME
'dnsDomainAux
'
8194 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8195 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8196 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8197 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8198 A6Record $ DNAMERecord
8200 </pre
></blockquote
>
8202 <p
>This will allow any object to become a DNS entry when combined with
8203 the domainrelatedobject object class, and allow any entity to include
8204 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8205 developers asking for their view on this schema and if they are
8206 interested in providing such schema with PowerDNS, and I hope my
8207 message will be accepted into their mailing list soon.
</p
>
8209 <p
><strong
>ISC dhcp
</strong
></p
>
8211 <p
>The DHCP server searches for specific objectclass and requests all
8212 the object attributes, and then uses the attributes it want. This
8213 make it harder to figure out exactly what attributes are used, but
8214 thanks to the working example in Debian Edu I can at least get an idea
8215 what is needed without having to read the source code.
</p
>
8217 <p
>In the DHCP server configuration, the LDAP base to use and the
8218 search filter to use to locate the correct dhcpServer entity is
8219 stored. These are the relevant entries from
8220 /etc/dhcp3/dhcpd.conf:
</p
>
8222 <blockquote
><pre
>
8223 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8224 ldap-dhcp-server-cn
"dhcp
";
8225 </pre
></blockquote
>
8227 <p
>The DHCP server uses this information to nest all the DHCP
8228 configuration it need. The cn
"dhcp
" is located using the given LDAP
8229 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8230 search result is this entry:
</p
>
8232 <blockquote
><pre
>
8233 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8236 objectClass: dhcpServer
8237 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8238 </pre
></blockquote
>
8240 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8241 subtree with DHCP configuration. The DHCP configuration subtree base
8242 is located using a base scope search with base
"cn=DHCP
8243 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8244 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8245 The search result is this entry:
</p
>
8247 <blockquote
><pre
>
8248 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8251 objectClass: dhcpService
8252 objectClass: dhcpOptions
8253 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8254 dhcpStatements: ddns-update-style none
8255 dhcpStatements: authoritative
8256 dhcpOption: smtp-server code
69 = array of ip-address
8257 dhcpOption: www-server code
72 = array of ip-address
8258 dhcpOption: wpad-url code
252 = text
8259 </pre
></blockquote
>
8261 <p
>Next, the entire subtree is processed, one level at the time. When
8262 all the DHCP configuration is loaded, it is ready to receive requests.
8263 The subtree in Debian Edu contain objects with object classes
8264 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8265 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8266 and information about netmasks, dynamic range etc. Leaving out the
8267 details here because it is not relevant for the focus of my
8268 investigation, which is to see if it is possible to merge dns and dhcp
8269 related computer objects.
</p
>
8271 <p
>When a DHCP request come in, LDAP is searched for the MAC address
8272 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
8273 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
8274 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8275 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
8278 <blockquote
><pre
>
8279 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8282 objectClass: dhcpHost
8283 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8284 dhcpStatements: fixed-address hostname
8285 </pre
></blockquote
>
8287 <p
>There is less flexiblity in the way LDAP searches are done here.
8288 The object classes need to have fixed names, and the configuration
8289 need to be stored in a fairly specific LDAP structure. On the
8290 positive side, the invidiual dhcpHost entires can be anywhere without
8291 the DN pointed to by the dhcpServer entries. The latter should make
8292 it possible to group all host entries in a subtree next to the
8293 configuration entries, and this subtree can also be shared with the
8294 DNS server if the schema proposed above is combined with the dhcpHost
8295 structural object class.
8297 <p
><strong
>Conclusion
</strong
></p
>
8299 <p
>The PowerDNS implementation seem to be very flexible when it come
8300 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
8301 come to the the LDAP structure, the
"strict
" mode is very flexible,
8302 allowing DNS objects to be stored anywhere under the base cn specified
8303 in the configuration.
</p
>
8305 <p
>The DHCP implementation on the other hand is very inflexible, both
8306 regarding which LDAP schemas to use and which LDAP structure to use.
8307 I guess one could implement ones own schema, as long as the
8308 objectclasses and attributes have the names used, but this do not
8309 really help when the DHCP subtree need to have a fairly fixed
8310 structure.
</p
>
8312 <p
>Based on the observed behaviour, I suspect a LDAP structure like
8313 this might work for Debian Edu:
</p
>
8315 <blockquote
><pre
>
8317 cn=machine-info (dhcpService) - dhcpServiceDN points here
8318 cn=dhcp (dhcpServer)
8319 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8320 cn=
10.0.2.0 (dhcpSubnet)
8321 cn=group1 (dhcpGroup/dhcpOptions)
8322 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8323 cn=
192.168.0.0 (dhcpSubnet)
8324 cn=group1 (dhcpGroup/dhcpOptions)
8325 ou=machines - PowerDNS base points here
8326 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8327 </pre
></blockquote
>
8329 <P
>This is not tested yet. If the DHCP server require the dhcpHost
8330 entries to be in the dhcpGroup subtrees, the entries can be stored
8331 there instead of a common machines subtree, and the PowerDNS base
8332 would have to be moved one level up to the machine-info subtree.
</p
>
8334 <p
>The combined object under the machines subtree would look something
8335 like this:
</p
>
8337 <blockquote
><pre
>
8338 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8341 objectClass: dhcpHost
8342 objectclass: domainrelatedobject
8343 objectclass: dnsDomainAux
8344 associateddomain: hostname.intern
8345 arecord:
10.11.12.13
8346 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8347 dhcpStatements: fixed-address hostname.intern
8348 </pre
></blockquote
>
8350 </p
>One could even add the LTSP configuration associated with a given
8351 machine, as long as the required attributes are available in a
8352 auxiliary object class.
</p
>
8357 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8358 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8359 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8360 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8361 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8362 DHCP services in Debian Edu to use the same LDAP objects for a given
8363 computer, to avoid the possibility of having a inconsistent state for
8364 a computer in LDAP (as in DHCP but no DNS entry or the other way
8365 around) and make it easier to add computers to LDAP.
</p
>
8367 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8368 information finally found a solution that seem to work.
</p
>
8370 <p
>The old setup required three LDAP objects for a given computer.
8371 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8372 we switch powerdns to use its strict LDAP method (ldap-method=strict
8373 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8374 merged into one while making it impossible to transfer the reverse map
8375 to a slave DNS server.
</p
>
8377 <p
>If we also replace the object class used to get the DNS related
8378 attributes to one allowing these attributes to be combined with the
8379 dhcphost object class, we can merge the DNS and DHCP entries into one.
8380 I
've written such object class in the dnsdomainaux.schema file (need
8381 proper OIDs, but that is a minor issue), and tested the setup. It
8382 seem to work.
</p
>
8384 <p
>With this test setup in place, we can get away with one LDAP object
8385 for both DNS and DHCP, and even the LTSP configuration I suggested in
8386 an earlier email. The combined LDAP object will look something like
8389 <blockquote
><pre
>
8390 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8392 objectClass: dhcphost
8393 objectclass: domainrelatedobject
8394 objectclass: dnsdomainaux
8395 associateddomain: hostname.intern
8396 arecord:
10.11.12.13
8397 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8398 dhcpstatements: fixed-address hostname
8400 </pre
></blockquote
>
8402 <p
>The DNS server uses the associateddomain and arecord entries, while
8403 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8404 before asking DNS to resolve the fixed-adddress. LTSP will use
8405 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8407 <p
>I am not yet sure if I can get the DHCP server to look for its
8408 dhcphost in a different location, to allow us to put the objects
8409 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8410 that. If I can
't figure out a way to do that, we can still get rid of
8411 the hosts subtree and move all its content into the DHCP Config tree
8412 (which probably should be renamed to be more related to the new
8413 content. I suspect cn=dnsdhcp,ou=services or something like that
8414 might be a good place to put it.
</p
>
8416 <p
>If you want to help out with implementing this for Debian Edu,
8417 please contact us on debian-edu@lists.debian.org.
</p
>
8422 <title>Idea for storing LTSP configuration in LDAP
</title>
8423 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8424 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8425 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8426 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8427 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8428 clients, and that this can be used to fetch configuration from LDAP if
8429 Debian Edu choose to store configuration there.
</p
>
8431 <p
>Armed with this information, I got inspired and wrote a test module
8432 to get configuration from LDAP. The idea is to look up the MAC
8433 address of the client in LDAP, and look for attributes on the form
8434 ltspconfigsetting=value, and use this to export SETTING=value to the
8435 LTSP clients.
</p
>
8437 <p
>The goal is to be able to store the LTSP configuration attributes
8438 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8439 allowing us to store all information about a computer in one place.
</p
>
8441 <p
>This is a untested draft implementation, and I welcome feedback on
8442 this approach. A real LDAP schema for the ltspClientAux objectclass
8443 need to be written. Comments, suggestions, etc?
</p
>
8445 <blockquote
><pre
>
8446 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8448 # Fetch LTSP client settings from LDAP based on MAC address
8450 # Uses ethernet address as stored in the dhcpHost objectclass using
8451 # the dhcpHWAddress attribute or ethernet address stored in the
8452 # ieee802Device objectclass with the macAddress attribute.
8454 # This module is written to be schema agnostic, and only depend on the
8455 # existence of attribute names.
8457 # The LTSP configuration variables are saved directly using a
8458 # ltspConfig prefix and uppercasing the rest of the attribute name.
8459 # To set the SERVER variable, set the ltspConfigServer attribute.
8461 # Some LDAP schema should be created with all the relevant
8462 # configuration settings. Something like this should work:
8464 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
8467 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8469 LDAPSERVER=$(debian-edu-ldapserver)
8470 if [
"$LDAPSERVER
" ] ; then
8471 LDAPBASE=$(debian-edu-ldapserver -b)
8472 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8473 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8474 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8475 grep
'^ltspConfig
' | while read attr value ; do
8476 # Remove prefix and convert to upper case
8477 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8478 # bass value on to clients
8479 eval
"$attr=$value; export $attr
"
8483 </pre
></blockquote
>
8485 <p
>I
'm not sure this shell construction will work, because I suspect
8486 the while block might end up in a subshell causing the variables set
8487 there to not show up in ltsp-config, but if that is the case I am sure
8488 the code can be restructured to make sure the variables are passed on.
8489 I expect that can be solved with some testing. :)
</p
>
8491 <p
>If you want to help out with implementing this for Debian Edu,
8492 please contact us on debian-edu@lists.debian.org.
</p
>
8494 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
8495 configuration in LDAP that was created around year
2000 by
8496 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
8497 Xperience, Inc.,
2000</a
>. I found its
8498 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
8499 personal home page over at redhat.com.
</p
>
8504 <title>jXplorer, a very nice LDAP GUI
</title>
8505 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8506 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8507 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8508 <description><p
>Since
8509 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8510 last post
</a
> about available LDAP tools in Debian, I was told about a
8511 LDAP GUI that is even better than luma. The java application
8512 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8513 moving LDAP objects and subtrees using drag-and-drop, and can
8514 authenticate using Kerberos. I have only tested the Kerberos
8515 authentication, but do not have a LDAP setup allowing me to rewrite
8516 LDAP with my test user yet. It is
8517 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8518 Debian
</a
> testing and unstable at the moment. The only problem I
8519 have with it is how it handle errors. If something go wrong, its
8520 non-intuitive behaviour require me to go through some query work list
8521 and remove the failing query. Nothing big, but very annoying.
</p
>
8526 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8527 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8528 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8529 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8530 <description><p
>Here is a short update on my
<a
8531 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8532 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8533 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8534 not reporting the status for KDE, because the upgrade crashes when
8535 aptitude try because of missing conflicts
8536 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8537 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8539 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8540 complete list of the installed packages. Based on this I see these
8541 differences when I did a test run today. As usual, I do not really
8542 know what the correct set of packages would be, but thought it best to
8543 publish the difference.
</p
>
8545 <p
>Installed using apt-get, missing with aptitude
</p
>
8547 <blockquote
><p
>
8548 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
8549 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
8550 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8551 libgtksourceview-common libpt-
1.10.10-plugins-alsa
8552 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8553 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8554 python-
4suite-xml python-eggtrayicon python-gtkhtml2
8555 python-gtkmozembed svgalibg1 xserver-xephyr zip
8556 </p
></blockquote
>
8558 <p
>Installed using apt-get, removed with aptitude
</p
>
8560 <blockquote
><p
>
8561 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8562 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8563 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
8564 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
8565 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
8566 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
8567 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8568 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8569 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8570 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
8571 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
8572 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
8573 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8574 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
8575 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8576 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
8577 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
8578 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8579 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8580 mysql-common swfdec-gnome totem-gstreamer wodim
8581 </p
></blockquote
>
8583 <p
>Installed using aptitude, missing with apt-get
</p
>
8585 <blockquote
><p
>
8586 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8587 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8588 xserver-xorg-input-all xserver-xorg-input-evdev
8589 xserver-xorg-input-kbd xserver-xorg-input-mouse
8590 xserver-xorg-input-synaptics xserver-xorg-video-all
8591 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8592 xserver-xorg-video-chips xserver-xorg-video-cirrus
8593 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8594 xserver-xorg-video-glint xserver-xorg-video-i128
8595 xserver-xorg-video-i740 xserver-xorg-video-mach64
8596 xserver-xorg-video-mga xserver-xorg-video-neomagic
8597 xserver-xorg-video-nouveau xserver-xorg-video-nv
8598 xserver-xorg-video-r128 xserver-xorg-video-radeon
8599 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8600 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8601 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8602 xserver-xorg-video-sis xserver-xorg-video-sisusb
8603 xserver-xorg-video-tdfx xserver-xorg-video-tga
8604 xserver-xorg-video-trident xserver-xorg-video-tseng
8605 xserver-xorg-video-vesa xserver-xorg-video-vmware
8606 xserver-xorg-video-voodoo
8607 </p
></blockquote
>
8609 <p
>Installed using aptitude, removed with apt-get
</p
>
8611 <blockquote
><p
>
8612 deskbar-applet xserver-xorg xserver-xorg-core
8613 xserver-xorg-input-wacom xserver-xorg-video-intel
8614 xserver-xorg-video-openchrome
8615 </p
></blockquote
>
8617 <p
>I was told on IRC that the xorg-xserver package was
8618 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
8619 in git
</a
> today to try to get apt-get to not remove xorg completely.
8620 No idea when it hits Squeeze, but when it does I hope it will reduce
8621 the difference somewhat.
8626 <title>LUMA, a very nice LDAP GUI
</title>
8627 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
8628 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
8629 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
8630 <description><p
>The last few days I have been looking into the status of the LDAP
8631 directory in Debian Edu, and in the process I started to miss a GUI
8632 tool to browse the LDAP tree. The only one I was able to find in
8633 Debian/Squeeze and Lenny is
8634 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
8635 be a great tool to get a overview of the current LDAP directory
8636 populated by default in Skolelinux. Thanks to it, I have been able to
8637 find empty and obsolete subtrees, misplaced objects and duplicate
8638 objects. It will be installed by default in Debian/Squeeze. If you
8639 are working with LDAP, give it a go. :)
</p
>
8641 <p
>I did notice one problem with it I have not had time to report to
8642 the BTS yet. There is no .desktop file in the package, so the tool do
8643 not show up in the Gnome and KDE menus, but only deep down in in the
8644 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8647 <p
>I have not yet been able to get it to modify the tree yet. I would
8648 like to move objects and remove subtrees directly in the GUI, but have
8649 not found a way to do that with LUMA yet. So in the mean time, I use
8650 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
8652 <p
>If you have tips on other GUI tools for LDAP that might be useful
8653 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
8655 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
8656 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
8657 useful GUI alternative. It seem like a good tool, but is unmaintained
8658 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8659 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
8664 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
8665 <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>
8666 <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>
8667 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
8668 <description><p
>A while back, I
8669 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
8670 about the fact
</a
> that it is not possible with the provided schemas
8671 for storing DNS and DHCP information in LDAP to combine the two sets
8672 of information into one LDAP object representing a computer.
</p
>
8674 <p
>In the mean time, I discovered that a simple fix would be to make
8675 the dhcpHost object class auxiliary, to allow it to be combined with
8676 the dNSDomain object class, and thus forming one object for one
8677 computer when storing both DHCP and DNS information in LDAP.
</p
>
8679 <p
>If I understand this correctly, it is not safe to do this change
8680 without also changing the assigned number for the object class, and I
8681 do not know enough about LDAP schema design to do that properly for
8682 Debian Edu.
</p
>
8684 <p
>Anyway, for future reference, this is how I believe we could change
8686 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
8687 schema
</a
> to solve at least part of the problem with the LDAP schemas
8688 available today from IETF.
</p
>
8691 --- dhcp.schema (revision
65192)
8692 +++ dhcp.schema (working copy)
8694 objectclass (
2.16.840.1.113719.1.203.6.6
8695 NAME
'dhcpHost
'
8696 DESC
'This represents information about a particular client
'
8700 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8701 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
8704 <p
>I very much welcome clues on how to do this properly for Debian
8705 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8706 package, and should thus be free to rewrite it as we see fit.
</p
>
8708 <p
>If you want to help out with implementing this for Debian Edu,
8709 please contact us on debian-edu@lists.debian.org.
</p
>
8714 <title>Calling tasksel like the installer, while still getting useful output
</title>
8715 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
8716 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
8717 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
8718 <description><p
>A few times I have had the need to simulate the way tasksel
8719 installs packages during the normal debian-installer run. Until now,
8720 I have ended up letting tasksel do the work, with the annoying problem
8721 of not getting any feedback at all when something fails (like a
8722 conffile question from dpkg or a download that fails), using code like
8725 <blockquote
><pre
>
8726 export DEBIAN_FRONTEND=noninteractive
8727 tasksel --new-install
8728 </pre
></blockquote
>
8730 This would invoke tasksel, let its automatic task selection pick the
8731 tasks to install, and continue to install the requested tasks without
8732 any output what so ever.
8734 Recently I revisited this problem while working on the automatic
8735 package upgrade testing, because tasksel would some times hang without
8736 any useful feedback, and I want to see what is going on when it
8737 happen. Then it occured to me, I can parse the output from tasksel
8738 when asked to run in test mode, and use that aptitude command line
8739 printed by tasksel then to simulate the tasksel run. I ended up using
8742 <blockquote
><pre
>
8743 export DEBIAN_FRONTEND=noninteractive
8744 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
8746 </pre
></blockquote
>
8748 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
8749 --without-recommends -o APT::Install-Recommends=no -y install
8750 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8751 ~pimportant
</tt
>", which will install the gnome desktop task, the
8752 laptop task and all packages with priority standard , required and
8753 important, just like tasksel would have done it during
8754 installation.
</p
>
8756 <p
>A better approach is probably to extend tasksel to be able to
8757 install packages without using debconf-apt-progress, for use cases
8758 like this.
</p
>
8763 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
8764 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
8765 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
8766 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
8767 <description><p
>My
8768 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
8769 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
8770 finally made the upgrade logs available from
8771 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
8772 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8773 apt and aptitude, and found their differences interesting. This time
8774 I will only focus on their removal plans.
</p
>
8776 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
8777 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
8778 surprising part is that it want to remove xorg and all
8779 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8780 sure why. When asking aptitude to do the same, it want to remove
129
8781 packages, but most of them are library packages I suspect are no
8782 longer needed. Both of them want to remove bluetooth packages, which
8783 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
8785 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
8786 which seem like a bad idea and xorg the same way as with Gnome. Asking
8787 aptitude for the same, it wants to remove
192 packages, none which are
8788 too surprising.
</p
>
8790 <p
>I guess the removal of xorg during upgrades should be investigated
8791 and avoided, and perhaps others as well. Here are the complete list
8792 of planned removals. The complete logs is available from the URL
8793 above. Note if you want to repeat these tests, that the upgrade test
8794 for kde+apt-get hung in the tasksel setup because of dpkg asking
8795 conffile questions. No idea why. I worked around it by using
8796 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
8799 <p
><b
>apt-get gnome
72</b
>
8800 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
8801 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8802 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
8803 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8804 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8805 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8806 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8807 xserver-xorg-input-kbd xserver-xorg-input-mouse
8808 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8809 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8810 xserver-xorg-video-ati xserver-xorg-video-chips
8811 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8812 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8813 xserver-xorg-video-glint xserver-xorg-video-i128
8814 xserver-xorg-video-i740 xserver-xorg-video-imstt
8815 xserver-xorg-video-intel xserver-xorg-video-mach64
8816 xserver-xorg-video-mga xserver-xorg-video-neomagic
8817 xserver-xorg-video-nsc xserver-xorg-video-nv
8818 xserver-xorg-video-openchrome xserver-xorg-video-r128
8819 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8820 xserver-xorg-video-rendition xserver-xorg-video-s3
8821 xserver-xorg-video-s3virge xserver-xorg-video-savage
8822 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8823 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8824 xserver-xorg-video-tga xserver-xorg-video-trident
8825 xserver-xorg-video-tseng xserver-xorg-video-v4l
8826 xserver-xorg-video-vesa xserver-xorg-video-vga
8827 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
8828 xulrunner-
1.9-gnome-support
</p
>
8830 <p
><b
>aptitude gnome
129</b
>
8832 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
8833 djvulibre-desktop finger gnome-app-install gnome-mount
8834 gnome-network-admin gnome-spell gnome-vfs-obexftp
8835 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8836 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8837 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8838 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
8839 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
8840 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
8841 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
8842 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
8843 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
8844 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
8845 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
8846 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
8847 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8848 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
8849 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
8850 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
8851 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
8852 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
8853 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8854 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8855 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8856 openoffice.org-writer2latex openssl-blacklist p7zip
8857 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
8858 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8859 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8860 swfdec-mozilla totem-gstreamer update-manager wodim
8861 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8862 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8865 <p
><b
>apt-get kde
82</b
>
8867 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8868 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8869 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8870 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8871 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8872 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8873 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8874 xserver-xorg-input-kbd xserver-xorg-input-mouse
8875 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8876 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8877 xserver-xorg-video-ati xserver-xorg-video-chips
8878 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8879 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8880 xserver-xorg-video-glint xserver-xorg-video-i128
8881 xserver-xorg-video-i740 xserver-xorg-video-imstt
8882 xserver-xorg-video-intel xserver-xorg-video-mach64
8883 xserver-xorg-video-mga xserver-xorg-video-neomagic
8884 xserver-xorg-video-nsc xserver-xorg-video-nv
8885 xserver-xorg-video-openchrome xserver-xorg-video-r128
8886 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8887 xserver-xorg-video-rendition xserver-xorg-video-s3
8888 xserver-xorg-video-s3virge xserver-xorg-video-savage
8889 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8890 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8891 xserver-xorg-video-tga xserver-xorg-video-trident
8892 xserver-xorg-video-tseng xserver-xorg-video-v4l
8893 xserver-xorg-video-vesa xserver-xorg-video-vga
8894 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
8896 <p
><b
>aptitude kde
192</b
>
8897 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
8898 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8899 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8900 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8901 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8902 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8903 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8904 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8905 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8906 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8907 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8908 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8909 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8910 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8911 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8912 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8913 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8914 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8915 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
8916 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8917 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8918 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
8919 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8920 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8921 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8922 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8923 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8924 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
8925 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
8926 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8927 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8928 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8929 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8930 texlive-common texlive-doc-base texlive-fonts-recommended
8931 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8932 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8933 xulrunner-
1.9</p
>
8939 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
8940 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
8941 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
8942 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
8943 <description><p
>The last few days I have done some upgrade testing in Debian, to
8944 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8945 have been discovered and reported in the process
8946 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
8947 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
8948 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
8949 kdebase-workspace-data), and to get a more regular testing going on, I
8950 am working on a script to automate the test.
</p
>
8952 <p
>The idea is to create a Lenny chroot and use tasksel to install a
8953 Gnome or KDE desktop installation inside the chroot before upgrading
8954 it. To ensure no services are started in the chroot, a policy-rc.d
8955 script is inserted. To make sure tasksel believe it is to install a
8956 desktop on a laptop, the tasksel tests are replaced in the chroot
8957 (only acceptable because this is a throw-away chroot).
</p
>
8959 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8960 currently always fail because udev refuses to upgrade with the kernel
8961 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8962 is created. The bug report
8963 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
8964 this problem do not trigger in a chroot, but I touch the file anyway
8965 to make sure the upgrade go well. Testing on virtual and real
8966 hardware have failed me because of udev so far, and creating this file
8967 do the trick in such settings anyway. This is a
8968 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
8969 issue
</a
> and the current udev behaviour is intended by the udev
8970 maintainer because he lack the resources to rewrite udev to keep
8971 working with old kernels or something like that. I really wish the
8972 udev upstream would keep udev backwards compatible, to avoid such
8973 upgrade problem, but given that they fail to do so, I guess
8974 documenting the way out of this mess is the best option we got for
8975 Debian Squeeze.
</p
>
8977 <p
>Anyway, back to the task at hand, testing upgrades. This test
8978 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
8981 <blockquote
><pre
>
8985 if [
"$
1" ] ; then
8994 exec
&lt; /dev/null
8996 mirror=http://ftp.skolelinux.org/debian
8997 tmpdir=chroot-$from-upgrade-$to-$desktop
8999 debootstrap $from $tmpdir $mirror
9000 chroot $tmpdir aptitude update
9001 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9005 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9009 mount -t proc proc $tmpdir/proc
9010 # Make sure proc is unmounted also on failure
9011 trap exit_cleanup EXIT INT
9013 chroot $tmpdir aptitude -y install debconf-utils
9015 # Make sure tasksel autoselection trigger. It need the test scripts
9016 # to return the correct answers.
9017 echo tasksel tasksel/desktop multiselect $desktop | \
9018 chroot $tmpdir debconf-set-selections
9020 # Include the desktop and laptop task
9021 for test in desktop laptop ; do
9022 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9026 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9029 DEBIAN_FRONTEND=noninteractive
9030 DEBIAN_PRIORITY=critical
9031 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9032 chroot $tmpdir tasksel --new-install
9034 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9035 chroot $tmpdir aptitude update
9036 touch $tmpdir/etc/udev/kernel-upgrade
9037 chroot $tmpdir aptitude -y dist-upgrade
9039 </pre
></blockquote
>
9041 <p
>I suspect it would be useful to test upgrades with both apt-get and
9042 with aptitude, but I have not had time to look at how they behave
9043 differently so far. I hope to get a cron job running to do the test
9044 regularly and post the result on the web. The Gnome upgrade currently
9045 work, while the KDE upgrade fail because of the bug in
9046 kdebase-workspace-data
</p
>
9048 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9049 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9050 post, so I will refrain from trying. I can report that for Gnome,
9051 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9052 remove and
1 not upgraded and
1024MB need to be downloaded while for
9053 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9054 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9056 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9057 is able to migrate to dependency based boot sequencing and parallel
9058 booting without a hitch. Was unsure if there were still bugs with
9059 packages failing to clean up their obsolete init.d script during
9060 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9066 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9067 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9068 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9069 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9070 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9071 scripts to migrate (some of) their operations to upstart job while
9072 keeping the init.d for hurd and kfreebsd. The packages with such
9073 needs will need a way to get their init.d scripts to behave
9074 differently when used with sysvinit and with upstart. Because of
9075 this, I had a look at the environment variables set when a init.d
9076 script is running under upstart, and when it is not.
</p
>
9078 <p
>With upstart, I notice these environment variables are set when a
9079 script is started from rcS.d/ (ignoring some irrelevant ones like
9082 <blockquote
><pre
>
9088 UPSTART_EVENTS=startup
9090 UPSTART_JOB=rc-sysinit
9091 </pre
></blockquote
>
9093 <p
>With sysvinit, these environment variables are set for the same
9096 <blockquote
><pre
>
9097 INIT_VERSION=sysvinit-
2.88
9102 </pre
></blockquote
>
9104 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9105 sysvinit are not set by upstart. Not sure if it is intentional or not
9106 to not be compatible with sysvinit in this regard.
</p
>
9108 <p
>For scripts needing to behave differently when upstart is used,
9109 looking for the UPSTART_JOB environment variable seem to be a good
9115 <title>A manual for standards wars...
</title>
9116 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9117 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9118 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9119 <description><p
>Via the
9120 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9121 of Rob Weir
</a
> I came across the very interesting essay named
9122 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9123 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9124 following the standards wars of today.
</p
>
9129 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9130 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9131 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9132 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9133 <description><p
>When using sitesummary at a site to track machines, it is possible
9134 to get a list of the machine types in use thanks to the DMI
9135 information extracted from each machine. The script to do so is
9136 included in the sitesummary package, and here is example output from
9137 the Skolelinux build servers:
</p
>
9139 <blockquote
><pre
>
9140 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9142 Dell Computer Corporation
1
9145 eserver xSeries
345 -[
8670M1X]-
1
9149 </pre
></blockquote
>
9151 <p
>The quality of the report depend on the quality of the DMI tables
9152 provided in each machine. Here there are Intel machines without model
9153 information listed with Intel as vendor and no model, and virtual Xen
9154 machines listed as [no-dmi-info]. One can add -l as a command line
9155 option to list the individual machines.
</p
>
9157 <p
>A larger list is
9158 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
9159 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
9160 provide the basic sitesummary report publicly. In their report there
9161 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
9162 their machines, and as sitesummary is available in both distributions,
9163 it is trivial to get all of them to report to the same central
9164 collector.
</p
>
9169 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9170 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9171 <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>
9172 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9173 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9174 start at boot when an NVidia video card is used is handled. The
9175 problem seem to be that the nvidia X.org driver uses a long time to
9176 initialize, and this duration is longer than kdm is configured to
9179 <p
>I came across two bugs related to this issue,
9180 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9181 against initscripts and passed on to nvidia-glx when it became obvious
9182 that the nvidia drivers were involved, and
9183 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9184 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9186 <p
>To me, it seem that no-one is interested in actually solving the
9187 problem nvidia video card owners experience and make sure the Debian
9188 distribution work out of the box for these users. The nvidia driver
9189 maintainers expect kdm to be set up to wait longer, while kdm expect
9190 the nvidia driver maintainers to fix the driver to start faster, and
9191 while they wait for each other I guess the users end up switching to a
9192 distribution that work for them. I have no idea what the solution is,
9193 but I am pretty sure that waiting for each other is not it.
</p
>
9195 <p
>I wonder why we end up handling bugs this way.
</p
>
9200 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9201 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9202 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9203 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9204 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9205 The feature seem to hold up pretty well, but three fairly serious
9206 issues are known and should be solved:
9210 <li
>The wicd package seen to
9211 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9212 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9213 parallel booting is enabled. No idea why, but the wicd maintainer
9214 seem to be on the case.
</li
>
9216 <li
>The nvidia X driver seem to
9217 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9218 triggered more easily when parallel booting is in effect. The
9219 maintainer is on the case.
</li
>
9221 <li
>The sysv-rc package fail to properly enable dependency based boot
9222 sequencing (the shutdown is broken) when old file-rc users
9223 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9224 sysv-rc. One way to solve it would be for file-rc to create
9225 /etc/init.d/.legacy-bootordering, and another is to try to make
9226 sysv-rc more robust. Will investigate some more and probably upload a
9227 workaround in sysv-rc to help those trying to move from file-rc to
9228 sysv-rc get a working shutdown.
</li
>
9230 </ul
></p
>
9232 <p
>All in all not many surprising issues, and all of them seem
9233 solvable before Squeeze is released. In addition to these there are
9234 some packages with bugs in their dependencies and run level settings,
9235 which I expect will be fixed in a reasonable time span.
</p
>
9237 <p
>If you report any problems with dependencies in init.d scripts to
9238 the BTS, please usertag the report to get it to show up at
9239 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9240 list of usertagged bugs related to this
</a
>.
</p
>
9242 <p
>Update: Correct bug number to file-rc issue.
</p
>
9247 <title>More flexible firmware handling in debian-installer
</title>
9248 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9249 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
9250 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
9251 <description><p
>After a long break from debian-installer development, I finally
9252 found time today to return to the project. Having to spend less time
9253 working dependency based boot in debian, as it is almost complete now,
9254 definitely helped freeing some time.
</p
>
9256 <p
>A while back, I ran into a problem while working on Debian Edu. We
9257 include some firmware packages on the Debian Edu CDs, those needed to
9258 get disk and network controllers working. Without having these
9259 firmware packages available during installation, it is impossible to
9260 install Debian Edu on the given machine, and because our target group
9261 are non-technical people, asking them to provide firmware packages on
9262 an external medium is a support pain. Initially, I expected it to be
9263 enough to include the firmware packages on the CD to get
9264 debian-installer to find and use them. This proved to be wrong.
9265 Next, I hoped it was enough to symlink the relevant firmware packages
9266 to some useful location on the CD (tried /cdrom/ and
9267 /cdrom/firmware/). This also proved to not work, and at this point I
9268 found time to look at the debian-installer code to figure out what was
9269 going to work.
</p
>
9271 <p
>The firmware loading code is in the hw-detect package, and a closer
9272 look revealed that it would only look for firmware packages outside
9273 the installation media, so the CD was never checked for firmware
9274 packages. It would only check USB sticks, floppies and other
9275 "external
" media devices. Today I changed it to also look in the
9276 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9277 solve the problem I ran into with Debian edu. I also changed it to
9278 look in /firmware/, to make sure the installer also find firmware
9279 provided in the initrd when booting the installer via PXE, to allow us
9280 to provide the same feature in the PXE setup included in Debian
9283 <p
>To make sure firmware deb packages with a license questions are not
9284 activated without asking if the license is accepted, I extended
9285 hw-detect to look for preinst scripts in the firmware packages, and
9286 run these before activating the firmware during installation. The
9287 license question is asked using debconf in the preinst, so this should
9288 solve the issue for the firmware packages I have looked at so far.
</p
>
9290 <p
>If you want to discuss the details of these features, please
9291 contact us on debian-boot@lists.debian.org.
</p
>
9296 <title>Parallellized boot is now the default in Debian/unstable
</title>
9297 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
9298 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
9299 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
9300 <description><p
>Since this evening, parallel booting is the default in
9301 Debian/unstable for machines using dependency based boot sequencing.
9302 Apparently the testing of concurrent booting has been wider than
9303 expected, if I am to believe the
9304 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9305 on debian-devel@
</a
>, and I concluded a few days ago to move forward
9306 with the feature this weekend, to give us some time to detect any
9307 remaining problems before Squeeze is frozen. If serious problems are
9308 detected, it is simple to change the default back to sequential boot.
9309 The upload of the new sysvinit package also activate a new upstream
9312 More information about
9313 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9314 based boot sequencing
</a
> is available from the Debian wiki. It is
9315 currently possible to disable parallel booting when one run into
9316 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
9318 <blockquote
><pre
>
9320 </pre
></blockquote
>
9322 <p
>If you report any problems with dependencies in init.d scripts to
9323 the BTS, please usertag the report to get it to show up at
9324 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9325 list of usertagged bugs related to this
</a
>.
</p
>
9330 <title>Sitesummary tip: Listing MAC address of all clients
</title>
9331 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
9332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
9333 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
9334 <description><p
>In the recent Debian Edu versions, the
9335 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
9336 system
</a
> is used to keep track of the machines in the school
9337 network. Each machine will automatically report its status to the
9338 central server after boot and once per night. The network setup is
9339 also reported, and using this information it is possible to get the
9340 MAC address of all network interfaces in the machines. This is useful
9341 to update the DHCP configuration.
</p
>
9343 <p
>To give some idea how to use sitesummary, here is a one-liner to
9344 ist all MAC addresses of all machines reporting to sitesummary. Run
9345 this on the collector host:
</p
>
9347 <blockquote
><pre
>
9348 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
9349 </pre
></blockquote
>
9351 <p
>This will list all MAC addresses assosiated with all machine, one
9352 line per machine and with space between the MAC addresses.
</p
>
9354 <p
>To allow system administrators easier job at adding static DHCP
9355 addresses for hosts, it would be possible to extend this to fetch
9356 machine information from sitesummary and update the DHCP and DNS
9357 tables in LDAP using this information. Such tool is unfortunately not
9358 written yet.
</p
>
9363 <title>systemd, an interesting alternative to upstart
</title>
9364 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9365 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9366 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9367 <description><p
>The last few days a new boot system called
9368 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9370 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9372 to the free software world. I have not yet had time to play around
9373 with it, but it seem to be a very interesting alternative to
9374 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9375 a good alternative for Debian when we are able to switch to an event
9376 based boot system. Tollef is
9377 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9378 systemd into Debian, and I look forward to seeing how well it work. I
9379 like the fact that systemd handles init.d scripts with dependency
9380 information natively, allowing them to run in parallel where upstart
9381 at the moment do not.
</p
>
9383 <p
>Unfortunately do systemd have the same problem as upstart regarding
9384 platform support. It only work on recent Linux kernels, and also need
9385 some new kernel features enabled to function properly. This means
9386 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9387 system. Not sure how that will be handled if systemd proves to be the
9388 way forward.
</p
>
9390 <p
>In the mean time, based on the
9391 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9392 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9393 decided to enable full parallel booting as the default in Debian as
9394 soon as possible (probably this weekend or early next week), to see if
9395 there are any remaining serious bugs in the init.d dependencies. A
9396 new version of the sysvinit package implementing this change is
9397 already in experimental. If all go well, Squeeze will be released
9398 with parallel booting enabled by default.
</p
>
9403 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9404 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9405 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9406 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9407 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9408 complete, so complete that it is actually possible to run all the
9409 init.d scripts in parallell based on these dependencies. If you want
9410 to test your Squeeze system, make sure
9411 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9412 based boot sequencing
</a
> is enabled, and add this line to
9413 /etc/default/rcS:
</p
>
9415 <blockquote
><pre
>
9416 CONCURRENCY=makefile
9417 </pre
></blockquote
>
9419 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9420 scripts in parallel using the dependency information stored in
9421 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9422 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9423 to try to start the kdm and gdm scripts as early as possible, and will
9424 start the facilities required by kdm or gdm as early as possible to
9425 make this happen.
</p
>
9427 <p
>Give it a try, and see if you like the result. If some services
9428 fail to start properly, it is most likely because they have incomplete
9429 init.d script dependencies in their startup script (or some of their
9430 dependent scripts have incomplete dependencies). Report bugs and get
9431 the package maintainers to fix it. :)
</p
>
9433 <p
>Running scripts in parallel could be the default in Debian when we
9434 manage to get the init.d script dependencies complete and correct. I
9435 expect we will get there in Squeeze+
1, if we get manage to test and
9436 fix the remaining issues.
</p
>
9438 <p
>If you report any problems with dependencies in init.d scripts to
9439 the BTS, please usertag the report to get it to show up at
9440 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9441 list of usertagged bugs related to this
</a
>.
</p
>
9446 <title>Debian has switched to dependency based boot sequencing
</title>
9447 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
9448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
9449 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
9450 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
9451 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
9452 have been migrated to using dependency based boot sequencing. This
9453 conclude work me and others have been doing for the last three days.
9454 It feels great to see this finally part of the default Debian
9455 installation. Now we just need to weed out the last few problems that
9456 are bound to show up, to get everything ready for Squeeze.
</p
>
9458 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
9459 fixing the more fundamental problem of handing the event based
9460 non-predictable kernel in the early boot.
</p
>
9465 <title>Taking over sysvinit development
</title>
9466 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
9467 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
9468 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
9469 <description><p
>After several years of frustration with the lack of activity from
9470 the existing sysvinit upstream developer, I decided a few weeks ago to
9471 take over the package and become the new upstream. The number of
9472 patches to track for the Debian package was becoming a burden, and the
9473 lack of synchronization between the distribution made it hard to keep
9474 the package up to date.
</p
>
9476 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9477 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9478 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9479 and Fedora), based on the patches currently in use in these
9480 distributions. We Debian maintainers plan to move to this tarball as
9481 the new upstream as soon as we find time to do the merge. Since the
9482 new tarball was created, we agreed with Werner at SuSe to make a new
9483 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
9484 development there. The project is registered and currently waiting
9485 for approval by the Savannah administrators, and as soon as it is
9486 approved, we will import the old versions from svn and continue
9487 working on the future release.
</p
>
9489 <p
>It is a bit ironic that this is done now, when some of the involved
9490 distributions are moving to upstart as a syvinit replacement.
</p
>
9495 <title>Debian boots quicker and quicker
</title>
9496 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
9497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
9498 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
9499 <description><p
>I spent Monday and tuesday this week in London with a lot of the
9500 people involved in the boot system on Debian and Ubuntu, to see if we
9501 could find more ways to speed up the boot system. This was an Ubuntu
9503 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9504 gathering
</a
>. It was quite productive. We also discussed the future
9505 of boot systems, and ways to handle the increasing number of boot
9506 issues introduced by the Linux kernel becoming more and more
9507 asynchronous and event base. The Ubuntu approach using udev and
9508 upstart might be a good way forward. Time will show.
</p
>
9510 <p
>Anyway, there are a few ways at the moment to speed up the boot
9511 process in Debian. All of these should be applied to get a quick
9516 <li
>Use dash as /bin/sh.
</li
>
9518 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9519 clock is in UTC.
</li
>
9521 <li
>Install and activate the insserv package to enable
9522 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9523 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9527 These points are based on the Google summer of code work done by
9528 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9531 <p
>Support for makefile-style concurrency during boot was uploaded to
9532 unstable yesterday. When we tested it, we were able to cut
6 seconds
9533 from the boot sequence. It depend on very correct dependency
9534 declaration in all init.d scripts, so I expect us to find edge cases
9535 where the dependences in some scripts are slightly wrong when we start
9536 using this.
</p
>
9538 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9539 introduced by Raphael Geissert today, one that could affect the
9540 startup speed as well. Instead of starting some scripts concurrently
9541 from rcS.d/ and another set of scripts from rc2.d/, it would be
9542 possible to run a of them in the same process. A quick way to test
9543 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9544 insserv
'. Will need to test if that work. :)
</p
>
9549 <title>BSAs påstander om piratkopiering møter motstand
</title>
9550 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
9551 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
9552 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
9553 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
9554 programvareselskapene som Microsoft og Apple, publisert en rapport der
9555 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9556 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9558 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
9559 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
9560 dagene. Et spesielt interessant kommentar fra Sverige,
9561 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
9562 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
9565 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
9566 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9567 företag.
"Man bör nog kanske inte se de här siffrorna som helt
9568 exakta
", säger BSAs Sverigechef John Hugosson.
9571 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
9572 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
9573 piracy figures need a shot of reality
</a
> og
<a
9574 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
9575 Copyright Treaty Work?
</a
></p
>
9577 <p
>Fant lenkene via
<a
9578 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
9579 på Slashdot
</a
>.
</p
>
9584 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
9585 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
9586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
9587 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
9588 <description><p
>Kom over
9589 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
9590 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9591 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9592 jobber til daglig. En rask opptelling forteller meg at vi har
490
9593 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
9594 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
9595 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
9600 <title>Kryptert harddisk - naturligvis
</title>
9601 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
9602 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
9603 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
9604 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
9605 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
9606 når en tar tap av arbeidstid, fortrolige dokumenter,
9607 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9608 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9609 til at jeg har kryptert harddisken på både kontormaskinen og min
9610 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9611 komme på avveie, den første informasjon relatert til jobben min ved
9612 Universitetet i Oslo, og den andre relatert til blant annet
9613 foreningsarbeide. Kryptering av diskene gjør at det er lite
9614 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9615 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9616 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9617 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9618 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9619 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9620 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9621 det er gjort slik jeg gjør det er minimale, og gevinstene er
9622 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9623 maskinen reinstalleres og alt er tapt.
</p
>
9625 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9626 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9627 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9628 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9629 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9630 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9631 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9632 betydelige.
</p
>
9637 <title>Two projects that have improved the quality of free software a lot
</title>
9638 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
9639 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
9640 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
9641 <description><p
>There are two software projects that have had huge influence on the
9642 quality of free software, and I wanted to mention both in case someone
9643 do not yet know them.
</p
>
9645 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
9646 tool to detect and expose errors in the memory handling of programs.
9647 It is easy to use, all one need to do is to run
'valgrind program
',
9648 and it will report any problems on stdout. It is even better if the
9649 program include debug information. With debug information, it is able
9650 to report the source file name and line number where the problem
9651 occurs. It can report things like
'reading past memory block in file
9652 X line N, the memory block was allocated in file Y, line M
', and
9653 'using uninitialised value in control logic
'. This tool has made it
9654 trivial to investigate reproducible crash bugs in programs, and have
9655 reduced the number of this kind of bugs in free software a lot.
9657 <p
>The second one is
9658 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
9659 a source code checker. It is able to process the source of a program
9660 and find problems in the logic without running the program. It
9661 started out as the Stanford Checker and became well known when it was
9662 used to find bugs in the Linux kernel. It is now a commercial tool
9663 and the company behind it is running
9664 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
9665 free software community, where a lot of free software projects get
9666 their source checked for free. Several thousand defects have been
9667 found and fixed so far. It can find errors like
'lock L taken in file
9668 X line N is never released if exiting in line M
', or
'the code in file
9669 Y lines O to P can never be executed
'. The projects included in the
9670 community service project have managed to get rid of a lot of
9671 reliability problems thanks to Coverity.
</p
>
9673 <p
>I believe tools like this, that are able to automatically find
9674 errors in the source, are vital to improve the quality of software and
9675 make sure we can get rid of the crashing and failing software we are
9676 surrounded by today.
</p
>
9681 <title>No patch is not better than a useless patch
</title>
9682 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
9683 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
9684 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
9685 <description><p
>Julien Blache
9686 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
9687 patch is better than a useless patch
</a
>. I completely disagree, as a
9688 patch allow one to discuss a concrete and proposed solution, and also
9689 prove that the issue at hand is important enough for someone to spent
9690 time on fixing it. No patch do not provide any of these positive
9691 properties.
</p
>
9696 <title>Standardize on protocols and formats, not vendors and applications
</title>
9697 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
9698 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
9699 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
9700 <description><p
>Where I work at the University of Oslo, one decision stand out as a
9701 very good one to form a long lived computer infrastructure. It is the
9702 simple one, lost by many in todays computer industry: Standardize on
9703 open network protocols and open exchange/storage formats, not applications.
9704 Applications come and go, while protocols and files tend to stay, and
9705 thus one want to make it easy to change application and vendor, while
9706 avoiding conversion costs and locking users to a specific platform or
9707 application.
</p
>
9709 <p
>This approach make it possible to replace the client applications
9710 independently of the server applications. One can even allow users to
9711 use several different applications as long as they handle the selected
9712 protocol and format. In the normal case, only one client application
9713 is recommended and users only get help if they choose to use this
9714 application, but those that want to deviate from the easy path are not
9715 blocked from doing so.
</p
>
9717 <p
>It also allow us to replace the server side without forcing the
9718 users to replace their applications, and thus allow us to select the
9719 best server implementation at any moment, when scale and resouce
9720 requirements change.
</p
>
9722 <p
>I strongly recommend standardizing - on open network protocols and
9723 open formats, but I would never recommend standardizing on a single
9724 application that do not use open network protocol or open formats.
</p
>
9729 <title>Returning from Skolelinux developer gathering
</title>
9730 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
9731 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
9732 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
9733 <description><p
>I
'm sitting on the train going home from this weekends Debian
9734 Edu/Skolelinux development gathering. I got a bit done tuning the
9735 desktop, and looked into the dynamic service location protocol
9736 implementation avahi. It look like it could be useful for us. Almost
9737 30 people participated, and I believe it was a great environment to
9738 get to know the Skolelinux system. Walter Bender, involved in the
9739 development of the Sugar educational platform, presented his stuff and
9740 also helped me improve my OLPC installation. He also showed me that
9741 his Turtle Art application can be used in standalone mode, and we
9742 agreed that I would help getting it packaged for Debian. As a
9743 standalone application it would be great for Debian Edu. We also
9744 tried to get the video conferencing working with two OLPCs, but that
9745 proved to be too hard for us. The application seem to need more work
9746 before it is ready for me. I look forward to getting home and relax
9752 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
9753 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
9754 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
9755 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
9756 <description><p
>The state of standardized LDAP schemas on Linux is far from
9757 optimal. There is RFC
2307 documenting one way to store NIS maps in
9758 LDAP, and a modified version of this normally called RFC
2307bis, with
9759 some modifications to be compatible with Active Directory. The RFC
9760 specification handle the content of a lot of system databases, but do
9761 not handle DNS zones and DHCP configuration.
</p
>
9763 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
9764 we would like to store information about users, SMB clients/hosts,
9765 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9766 and LTSP configuration in LDAP. These objects have a lot in common,
9767 but with the current LDAP schemas it is not possible to have one
9768 object per entity. For example, one need to have at least three LDAP
9769 objects for a given computer, one with the SMB related stuff, one with
9770 DNS information and another with DHCP information. The schemas
9771 provided for DNS and DHCP are impossible to combine into one LDAP
9772 object. In addition, it is impossible to implement quick queries for
9773 netgroup membership, because of the way NIS triples are implemented.
9774 It just do not scale. I believe it is time for a few RFC
9775 specifications to cleam up this mess.
</p
>
9777 <p
>I would like to have one LDAP object representing each computer in
9778 the network, and this object can then keep the SMB (ie host key), DHCP
9779 (mac address/name) and DNS (name/IP address) settings in one place.
9780 It need to be efficently stored to make sure it scale well.
</p
>
9782 <p
>I would also like to have a quick way to map from a user or
9783 computer and to the net group this user or computer is a member.
</p
>
9785 <p
>Active Directory have done a better job than unix heads like myself
9786 in this regard, and the unix side need to catch up. Time to start a
9787 new IETF work group?
</p
>
9792 <title>Endelig er Debian Lenny gitt ut
</title>
9793 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
9794 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
9795 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
9796 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
9797 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
9798 Et langt steg videre for Debian-prosjektet, og en rekke nye
9799 programpakker blir nå tilgjengelig for de av oss som bruker den
9800 stabile utgaven av Debian. Neste steg er nå å få
9801 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
9802 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
9803 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9804 slippes løs på skolene. Takk til alle debian-utviklerne som har
9805 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9806 bootsekvens tilgjengelig i stabil utgave, vha pakken
9807 <tt
>insserv
</tt
>.
</p
>
9812 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
9813 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
9814 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
9815 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
9816 <description><p
>This weekend we had a small developer gathering for Debian Edu in
9817 Oslo. Most of Saturday was used for the general assemly for the
9818 member organization, but the rest of the weekend I used to tune the
9819 LTSP installation. LTSP now work out of the box on the
10-network.
9820 Acer Aspire One proved to be a very nice thin client, with both
9821 screen, mouse and keybard in a small box. Was working on getting the
9822 diskless workstation setup configured out of the box, but did not
9823 finish it before the weekend was up.
</p
>
9825 <p
>Did not find time to look at the
4 VGA cards in one box we got from
9826 the Brazilian group, so that will have to wait for the next
9827 development gathering. Would love to have the Debian Edu installer
9828 automatically detect and configure a multiseat setup when it find one
9829 of these cards.
</p
>
9834 <title>The sorry state of multimedia browser plugins in Debian
</title>
9835 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
9836 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
9837 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
9838 <description><p
>Recently I have spent some time evaluating the multimedia browser
9839 plugins available in Debian Lenny, to see which one we should use by
9840 default in Debian Edu. We need an embedded video playing plugin with
9841 control buttons to pause or stop the video, and capable of streaming
9842 all the multimedia content available on the web. The test results and
9843 notes are available on
9844 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
9845 Debian wiki
</a
>. I was surprised how few of the plugins are able to
9846 fill this need. My personal video player favorite, VLC, has a really
9847 bad plugin which fail on a lot of the test pages. A lot of the MIME
9848 types I would expect to work with any free software player (like
9849 video/ogg), just do not work. And simple formats like the
9850 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
9851 totem and vlc plugins. I hope the situation will improve soon. No
9852 wonder sites use the proprietary Adobe flash to play video.
</p
>
9854 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
9855 be the only one fitting our needs. :/
</p
>