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>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
11 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
13 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
14 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
15 system
</a
> provide a practical and easy way to figure out which
16 packages support the hardware in a given machine. The command line
17 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
18 convenient way to list and install packages relevant for the current
19 hardware during system installation, both user space packages and
20 firmware packages. The GUI background daemon on the other hand provide
21 a pop-up proposing to install packages when a new dongle is inserted
22 while using the computer. For example, if you plug in a smart card
23 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
24 that package isn
't already installed, and if you plug in a USB video
25 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
26 cheese is currently missing. This already work just fine.
</p
>
28 <p
>But Isenkram depend on a database mapping from hardware IDs to
29 package names. When I started no such database existed in Debian, so
30 I made my own data set and included it with the isenkram package and
31 made isenkram fetch the latest version of this database from git using
32 http. This way the isenkram users would get updated package proposals
33 as soon as I learned more about hardware related packages.
</p
>
35 <p
>The hardware is identified using modalias strings. The modalias
36 design is from the Linux kernel where most hardware descriptors are
37 made available as a strings that can be matched using filename style
38 globbing. It handle USB, PCI, DMI and a lot of other hardware related
39 identifiers.
</p
>
41 <p
>The downside to the Isenkram specific database is that there is no
42 information about relevant distribution / Debian version, making
43 isenkram propose obsolete packages too. But along came AppStream, a
44 cross distribution mechanism to store and collect metadata about
45 software packages. When I heard about the proposal, I contacted the
46 people involved and suggested to add a hardware matching rule using
47 modalias strings in the specification, to be able to use AppStream for
48 mapping hardware to packages. This idea was accepted and AppStream is
49 now a great way for a package to announce the hardware it support in a
50 distribution neutral way. I wrote
51 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
52 recipe on how to add such meta-information
</a
> in a blog post last
53 December. If you have a hardware related package in Debian, please
54 announce the relevant hardware IDs using AppStream.
</p
>
56 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
57 RCX or NXT unit, announce this support using AppStream. The effect is
58 that when you insert such LEGO robot controller into your Debian
59 machine, Isenkram will propose to install the packages needed to get
60 it working. The intention is that this should allow the local user to
61 start programming his robot controller right away without having to
62 guess what packages to use or which permissions to fix.
</p
>
64 <p
>But when I sat down with my son the other day to program our NXT
65 unit using his Debian Stretch computer, I discovered something
66 annoying. The local console user (ie my son) did not get access to
67 the USB device for programming the unit. This used to work, but no
68 longer in Jessie and Stretch. After some investigation and asking
69 around on #debian-devel, I discovered that this was because udev had
70 changed the mechanism used to grant access to local devices. The
71 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
72 no longer applied, because LDAP users no longer was added to the
73 plugdev group during login. Michael Biebl told me that this method
74 was obsolete and the new method used ACLs instead. This was good
75 news, as the plugdev mechanism is a mess when using a remote user
76 directory like LDAP. Using ACLs would make sure a user lost device
77 access when she logged out, even if the user left behind a background
78 process which would retain the plugdev membership with the ConsoleKit
79 setup. Armed with this knowledge I moved on to fix the access problem
80 for the LEGO Mindstorms related packages.
</p
>
82 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
83 applied directly for a device, or is applied in
84 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
85 LEGO Mindstorms udev rules did not have a class, I decided to add the
86 tag directly in the udev rules files included in the packages. Here
87 is one example. For the nqc C compiler for the RCX, the
88 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
91 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
92 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
93 </pre
></p
>
95 <p
>I suspect all packages using plugdev in their /lib/udev/rules.d/
96 files should be changed to use this tag (either directly or indirectly
97 via
<tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be
98 created to detect this?
</p
>
100 <p
>I
've been unable to find good documentation on the uaccess feature.
101 It is unclear to me if the uaccess tag is an internal implementation
102 detail like the udev-acl tag used by
103 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
104 indirect method is the preferred way. Michael
105 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
106 documentation from the systemd project
</a
> and I hope it will make
107 this clearer. For now I use the generic classes when they exist and
108 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
109 directly if no such class exist.
</p
>
111 <p
>To learn more about the isenkram system, please check out
112 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
113 blog posts tagged isenkram
</a
>.
</p
>
115 <p
>To help out making life for LEGO constructors in Debian easier,
116 please join us on our IRC channel
117 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
118 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
119 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
120 list is not yet created, but we are working on it. :)
</p
>
122 <p
>As usual, if you use Bitcoin and want to show your support of my
123 activities, please send Bitcoin donations to my address
124 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
129 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
130 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
131 <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>
132 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
133 <description><p
>In April we
134 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
135 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
136 how to set up and administrate a Debian system. Today I am happy to
137 report that the first draft is now publicly available. You can find
138 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
139 Administrator
's Handbook page
</a
> (under Other languages). The first
140 eight chapters have a first draft translation, and we are working on
141 proofreading the content. If you want to help out, please start
143 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
144 hosted weblate project page
</a
>, and get in touch using
145 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
146 translators mailing list
</a
>. Please also check out
147 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
148 contributors
</a
>. A good way to contribute is to proofread the text
149 and update weblate if you find errors.
</p
>
151 <p
>Our goal is still to make the Norwegian book available on paper as well as
152 electronic form.
</p
>
157 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
158 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
159 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
160 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
161 <description><p
>This summer, I read a great article
162 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
163 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
164 how to profile multi-threaded programs. It presented a system for
165 profiling software by running experiences in the running program,
166 testing how run time performance is affected by
"speeding up
" parts of
167 the code to various degrees compared to a normal run. It does this by
168 slowing down parallel threads while the
"faster up
" code is running
169 and measure how this affect processing time. The processing time is
170 measured using probes inserted into the code, either using progress
171 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
172 can also measure unmodified code by measuring complete the program
173 runtime and running the program several times instead.
</p
>
175 <p
>The project and presentation was so inspiring that I would like to
176 get the system into Debian. I
177 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
178 a WNPP request for it
</a
> and contacted upstream to try to make the
179 system ready for Debian by sending patches. The build process need to
180 be changed a bit to avoid running
'git clone
' to get dependencies, and
181 to include the JavaScript web page used to visualize the collected
182 profiling information included in the source package.
183 But I expect that should work out fairly soon.
</p
>
185 <p
>The way the system work is fairly simple. To run an coz experiment
186 on a binary with debug symbols available, start the program like this:
188 <p
><blockquote
><pre
>
189 coz run --- program-to-run
190 </pre
></blockquote
></p
>
192 <p
>This will create a text file profile.coz with the instrumentation
193 information. To show what part of the code affect the performance
194 most, use a web browser and either point it to
195 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
196 or use the copy from git (in the gh-pages branch). Check out this web
197 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
198 profiling more useful you include
&lt;coz.h
&gt; and insert the
199 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
200 code, rebuild and run the profiler. This allow coz to do more
201 targeted experiments.
</p
>
203 <p
>A video published by ACM
204 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
205 Coz profiler
</a
> is available from Youtube. There is also a paper
206 from the
25th Symposium on Operating Systems Principles available
208 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
209 finding code that counts with causal profiling
</a
>.
</p
>
211 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
212 for Coz is available from github. It will only build with clang
214 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
215 feature missing in GCC
</a
>, but I
've submitted
216 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
217 it
</a
> and hope it will be included in the upstream source soon.
</p
>
219 <p
>Please get in touch if you, like me, would like to see this piece
220 of software in Debian. I would very much like some help with the
221 packaging effort, as I lack the in depth knowledge on how to package
222 C++ libraries.
</p
>
227 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
228 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
229 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
230 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
231 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
232 to be a slight challenge. Here is the recipe if I ever need to do it
233 again. It all started by me wanting to try the recipe to set up
234 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
235 hardened Android installation
</a
> from the Tor project blog on a
236 device I had access to. It is a old mobile phone with a broken
237 microphone The initial idea had been to just
238 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
239 CyanogenMod on it
</a
>, but did not quite find time to start on it
240 until a few days ago.
</p
>
242 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
243 loader (press volume down and power at the same time), (
2) select
244 'fastboot
' before (
3) connecting the device via USB to a Linux
245 machine, (
4) request the device identifier token by running
'fastboot
246 oem get_identifier_token
', (
5) request the device unlocking key using
247 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
248 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
250 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
251 or newer, and the device I was working on had
2.00.0027. This
252 apparently can be easily fixed by downloading a Windows program and
253 running it on your Windows machine, if you accept the terms Microsoft
254 require you to accept to use Windows - which I do not. So I had to
255 come up with a different approach. I got a lot of help from AndyCap
256 on #nuug, and would not have been able to get this working without
259 <p
>First I needed to extract the hboot firmware from
260 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
261 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
262 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
263 project named unruu
</a
> using libunshield. The unshield tool did not
264 recognise the file format, but unruu worked and extracted rom.zip,
265 containing the new hboot firmware and a text file describing which
266 devices it would work for.
</p
>
268 <p
>Next, I needed to get the new firmware into the device. For this I
269 followed some instructions
270 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
271 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
272 machine with Debian testing:
</p
>
275 adb reboot-bootloader
276 fastboot oem rebootRUU
277 fastboot flash zip rom.zip
278 fastboot flash zip rom.zip
280 </pre
></p
>
282 <p
>The flash command apparently need to be done twice to take effect,
283 as the first is just preparations and the second one do the flashing.
284 The adb command is just to get to the boot loader menu, so turning the
285 device on while holding volume down and the power button should work
288 <p
>With the new hboot version in place I could start following the
289 instructions on the HTC developer web site. I got the device token
293 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
296 <p
>And once I got the unlock code via email, I could use it like
300 fastboot flash unlocktoken Unlock_code.bin
301 </pre
></p
>
303 <p
>And with that final step in place, the phone was unlocked and I
304 could start stuffing the software of my own choosing into the device.
305 So far I only inserted a replacement recovery image to wipe the phone
306 before I start. We will see what happen next. Perhaps I should
307 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
312 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
313 <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>
314 <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>
315 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
316 <description><p
>For a while now, I have wanted to test
317 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
318 said to provide end to end encrypted communication and several of my
319 friends and family are already using it. As I by choice do not own a
320 mobile phone, this proved to be harder than expected. And I wanted to
321 have the source of the client and know that it was the code used on my
322 machine. But yesterday I managed to get it working. I used the
323 Github source, compared it to the source in
324 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
325 Signal Chrome app
</a
> available from the Chrome web store, applied
326 patches to use the production Signal servers, started the app and
327 asked for the hidden
"register without a smart phone
" form. Here is
328 the recipe how I did it.
</p
>
330 <p
>First, I fetched the Signal desktop source from Github, using
333 git clone https://github.com/WhisperSystems/Signal-Desktop.git
336 <p
>Next, I patched the source to use the production servers, to be
337 able to talk to other Signal users:
</p
>
340 cat
&lt;
&lt;EOF | patch -p0
341 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
342 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
343 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
348 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
349 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
350 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
351 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
353 window.getSocketStatus = function() {
354 if (messageReceiver) {
355 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
356 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
357 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
360 'use strict
';
361 - var BUILD_EXPIRATION =
0;
362 + var BUILD_EXPIRATION =
1474492690000;
364 window.extension = window.extension || {};
369 <p
>The first part is changing the servers, and the second is updating
370 an expiration timestamp. This timestamp need to be updated regularly.
371 It is set
90 days in the future by the build process (Gruntfile.js).
372 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
374 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
375 script to launch Signal in Chromium.
</p
>
382 --proxy-server=
"socks://localhost:
9050" \
383 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
386 <p
> The script start the app and configure Chromium to use the Tor
387 SOCKS5 proxy to make sure those controlling the Signal servers (today
388 Amazon and Whisper Systems) as well as those listening on the lines
389 will have a harder time location my laptop based on the Signal
390 connections if they use source IP address.
</p
>
392 <p
>When the script starts, one need to follow the instructions under
393 "Standalone Registration
" in the CONTRIBUTING.md file in the git
394 repository. I right clicked on the Signal window to get up the
395 Chromium debugging tool, visited the
'Console
' tab and wrote
396 'extension.install(
"standalone
")
' on the console prompt to get the
397 registration form. Then I entered by land line phone number and
398 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
399 repeated the verification code three times. After entering the number
400 into the verification code field in the form, I could start using
401 Signal from my laptop.
403 <p
>As far as I can tell, The Signal app will leak who is talking to
404 whom and thus who know who to those controlling the central server,
405 but such leakage is hard to avoid with a centrally controlled server
406 setup. It is something to keep in mind when using Signal - the
407 content of your chats are harder to intercept, but the meta data
408 exposing your contact network is available to people you do not know.
409 So better than many options, but not great. And sadly the usage is
410 connected to my land line, thus allowing those controlling the server
411 to associate it to my home and person. I would prefer it if only
412 those I knew could tell who I was on Signal. There are options
413 avoiding such information leakage, but most of my friends are not
414 using them, so I am stuck with Signal for now.
</p
>
419 <title>The new
"best
" multimedia player in Debian?
</title>
420 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
421 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
422 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
423 <description><p
>When I set out a few weeks ago to figure out
424 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
425 multimedia player in Debian claimed to support most file formats /
426 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
427 the various players claimed support for. The range was from
55 to
130
428 MIME types. I suspect most media formats are supported by all
429 players, but this is not really reflected in the MimeTypes values in
430 their desktop files. There are probably also some bogus MIME types
431 listed, but it is hard to identify which one this is.
</p
>
433 <p
>Anyway, in the mean time I got in touch with upstream for some of
434 the players suggesting to add more MIME types to their desktop files,
435 and decided to spend some time myself improving the situation for my
436 favorite media player VLC. The fixes for VLC entered Debian unstable
437 yesterday. The complete list of MIME types can be seen on the
438 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
439 player MIME type support status
</a
> Debian wiki page.
</p
>
441 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
442 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
443 kmplayer. I am sure some of the other players desktop files support
444 several of the formats currently listed as working only with vlc,
445 toten and parole.
</p
>
447 <p
>A sad observation is that only
14 MIME types are listed as
448 supported by all the tested multimedia players in Debian in their
449 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
450 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
451 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
452 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
453 it sad that video/ogg and video/webm is not supported by all the media
454 players in Debian. As far as I can tell, all of them can handle both
460 <title>A program should be able to open its own files on Linux
</title>
461 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
462 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
463 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
464 <description><p
>Many years ago, when koffice was fresh and with few users, I
465 decided to test its presentation tool when making the slides for a
466 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
467 wrote the first draft of the slides, saved the result and went to bed
468 the day before I would give the talk. The next day I took a plane to
469 the location where the meeting should take place, and on the plane I
470 started up koffice again to polish the talk a bit, only to discover
471 that kpresenter refused to load its own data file. I cursed a bit and
472 started making the slides again from memory, to have something to
473 present when I arrived. I tested that the saved files could be
474 loaded, and the day seemed to be rescued. I continued to polish the
475 slides until I suddenly discovered that the saved file could no longer
476 be loaded into kpresenter. In the end I had to rewrite the slides
477 three times, condensing the content until the talk became shorter and
478 shorter. After the talk I was able to pinpoint the problem
&ndash;
479 kpresenter wrote inline images in a way itself could not understand.
480 Eventually that bug was fixed and kpresenter ended up being a great
481 program to make slides. The point I
'm trying to make is that we
482 expect a program to be able to load its own data files, and it is
483 embarrassing to its developers if it can
't.
</p
>
485 <p
>Did you ever experience a program failing to load its own data
486 files from the desktop file browser? It is not a uncommon problem. A
487 while back I discovered that the screencast recorder
488 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
489 browser would refuse to open. No video player claimed to understand
490 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
491 returning the application/ogg MIME type, which no video player I had
492 installed listed as a MIME type they would understand. I asked for
493 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
494 behavour
</a
> and use the MIME type video/ogg instead. I also asked
495 several video players to add video/ogg to their desktop files, to give
496 the file browser an idea what to do about Ogg Theora files. After a
497 while, the desktop file browsers in Debian started to handle the
498 output from gtk-recordmydesktop properly.
</p
>
500 <p
>But history repeats itself. A few days ago I tested the music
501 system Rosegarden again, and I discovered that the KDE and xfce file
502 browsers did not know what to do with the Rosegarden project files
503 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
504 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
505 included in the next upload. To increase the chance of me remembering
506 how to fix the problem next time some program fail to load its files
507 from the file browser, here are some notes on how to fix it.
</p
>
509 <p
>The file browsers in Debian in general operates on MIME types.
510 There are two sources for the MIME type of a given file. The output from
511 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
512 shared MIME type registry (under /usr/share/mime/). The file MIME
513 type is mapped to programs supporting the MIME type, and this
514 information is collected from
515 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
516 desktop files
</a
> available in /usr/share/applications/. If there is
517 one desktop file claiming support for the MIME type of the file, it is
518 activated when asking to open a given file. If there are more, one
519 can normally select which one to use by right-clicking on the file and
520 selecting the wanted one using
'Open with
' or similar. In general
521 this work well. But it depend on each program picking a good MIME
523 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
524 MIME type registered with IANA
</a
>), file and/or the shared MIME
525 registry recognizing the file and the desktop file to list the MIME
526 type in its list of supported MIME types.
</p
>
528 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
529 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
530 Shared MIME database
</a
> look like this:
</p
>
532 <p
><blockquote
><pre
>
533 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
534 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
535 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
536 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
537 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
538 &lt;glob pattern=
"*.rg
"/
&gt;
539 &lt;/mime-type
&gt;
540 &lt;/mime-info
&gt;
541 </pre
></blockquote
></p
>
543 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
544 (it is a gzipped XML file). Note, it is much better to use an
545 official MIME type registered with IANA than it is to make up ones own
546 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
548 <p
>The desktop file of the rosegarden program failed to list
549 audio/x-rosegarden in its list of supported MIME types, causing the
550 file browsers to have no idea what to do with *.rg files:
</p
>
552 <p
><blockquote
><pre
>
553 % grep Mime /usr/share/applications/rosegarden.desktop
554 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
555 X-KDE-NativeMimeType=audio/x-rosegarden-composition
557 </pre
></blockquote
></p
>
559 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
560 MimeType= line.
</p
>
562 <p
>If you run into a file which fail to open the correct program when
563 selected from the file browser, please check out the output from
564 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
565 MIME type is registered somewhere under /usr/share/mime/ and check
566 that some desktop file under /usr/share/applications/ is claiming
567 support for this MIME type. If not, please report a bug to have it
573 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
574 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
575 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
576 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
577 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
578 system
</a
> is a user-focused solution in Debian for handling hardware
579 related packages. The idea is to have a database of mappings between
580 hardware and packages, and pop up a dialog suggesting for the user to
581 install the packages to use a given hardware dongle. Some use cases
582 are when you insert a Yubikey, it proposes to install the software
583 needed to control it; when you insert a braille reader list it
584 proposes to install the packages needed to send text to the reader;
585 and when you insert a ColorHug screen calibrator it suggests to
586 install the driver for it. The system work well, and even have a few
587 command line tools to install firmware packages and packages for the
588 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
590 <p
>The system was initially written using aptdaemon, because I found
591 good documentation and example code on how to use it. But aptdaemon
592 is going away and is generally being replaced by
593 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
594 so Isenkram needed a rewrite. And today, thanks to the great patch
595 from my college Sunil Mohan Adapa in the FreedomBox project, the
596 rewrite finally took place. I
've just uploaded a new version of
597 Isenkram into Debian Unstable with the patch included, and the default
598 for the background daemon is now to use PackageKit. To check it out,
599 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
600 and see if it is recognised.
</p
>
602 <p
>If you want to know what kind of packages isenkram would propose for
603 the machine it is running on, you can check out the isenkram-lookup
604 program. This is what it look like on a Thinkpad X230:
</p
>
606 <p
><blockquote
><pre
>
622 </pre
></blockquote
></p
>
624 <p
>The hardware mappings come from several places. The preferred way
625 is for packages to announce their hardware support using
626 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
627 cross distribution appstream system
</a
>.
629 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
630 blog posts about isenkram
</a
> to learn how to do that.
</p
>
635 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
636 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
637 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
638 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
639 <description><p
>Yesterday I updated the
640 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
641 package in Debian
</a
> with a few patches sent to me by skilled and
642 enterprising users. There were some nice user and visible changes.
643 First of all, both desktop menu entries now work. A design flaw in
644 one of the script made the history graph fail to show up (its PNG was
645 dumped in ~/.xsession-errors) if no controlling TTY was available.
646 The script worked when called from the command line, but not when
647 called from the desktop menu. I changed this to look for a DISPLAY
648 variable or a TTY before deciding where to draw the graph, and now the
649 graph window pop up as expected.
</p
>
651 <p
>The next new feature is a discharge rate estimator in one of the
652 graphs (the one showing the last few hours). New is also the user of
653 colours showing charging in blue and discharge in red. The percentages
654 of this graph is relative to last full charge, not battery design
657 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
659 <p
>The other graph show the entire history of the collected battery
660 statistics, comparing it to the design capacity of the battery to
661 visualise how the battery life time get shorter over time. The red
662 line in this graph is what the previous graph considers
100 percent:
664 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
666 <p
>In this graph you can see that I only charge the battery to
80
667 percent of last full capacity, and how the capacity of the battery is
668 shrinking. :(
</p
>
670 <p
>The last new feature is in the collector, which now will handle
671 more hardware models. On some hardware, Linux power supply
672 information is stored in /sys/class/power_supply/ACAD/, while the
673 collector previously only looked in /sys/class/power_supply/AC/. Now
674 both are checked to figure if there is power connected to the
677 <p
>If you are interested in how your laptop battery is doing, please
679 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
680 in Debian unstable, or rebuild it on Jessie to get it working on
681 Debian stable. :) The upstream source is available from
<a
682 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
683 Patches are very welcome.
</p
>
685 <p
>As usual, if you use Bitcoin and want to show your support of my
686 activities, please send Bitcoin donations to my address
687 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
692 <title>Debian now with ZFS on Linux included
</title>
693 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
694 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
695 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
696 <description><p
>Today, after many years of hard work from many people,
697 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
698 Debian. The package status can be seen on
699 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
700 for zfs-linux
</a
>. and
701 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
702 team status page
</a
>. If you want to help out, please join us.
703 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
704 source code
</a
> is available via git on Alioth. It would also be
705 great if you could help out with
706 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
707 it is an important piece of the puzzle to get ZFS working.
</p
>
712 <title>What is the best multimedia player in Debian?
</title>
713 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
715 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
716 <description><p
><strong
>Where I set out to figure out which multimedia player in
717 Debian claim support for most file formats.
</strong
></p
>
719 <p
>A few years ago, I had a look at the media support for Browser
720 plugins in Debian, to get an idea which plugins to include in Debian
721 Edu. I created a script to extract the set of supported MIME types
722 for each plugin, and used this to find out which multimedia browser
723 plugin supported most file formats / media types.
724 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
725 result
</a
> can still be seen on the Debian wiki, even though it have
726 not been updated for a while. But browser plugins are less relevant
727 these days, so I thought it was time to look at standalone
730 <p
>A few days ago I was tired of VLC not being listed as a viable
731 player when I wanted to play videos from the Norwegian National
732 Broadcasting Company, and decided to investigate why. The cause is a
733 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
734 desktop file
</a
>. In the process I wrote a script to compare the set
735 of MIME types announced in the desktop file and the browser plugin,
736 only to discover that there is quite a large difference between the
737 two for VLC. This discovery made me dig up the script I used to
738 compare browser plugins, and adjust it to compare desktop files
739 instead, to try to figure out which multimedia player in Debian
740 support most file formats.
</p
>
742 <p
>The result can be seen on the Debian Wiki, as
743 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
744 table listing all MIME types supported by one of the packages included
745 in the table
</a
>, with the package supporting most MIME types being
746 listed first in the table.
</p
>
748 </p
>The best multimedia player in Debian? It is totem, followed by
749 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
750 kmplayer. Time for the other players to update their announced MIME
756 <title>The Pyra - handheld computer with Debian preinstalled
</title>
757 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
758 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
759 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
760 <description>A friend of mine made me aware of
761 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
762 handheld computer which will be delivered with Debian preinstalled. I
763 would love to get one of those for my birthday. :)
</p
>
765 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
766 plugs and many others connectors, and include a full keyboard and a
5"
767 LCD touch screen. The
6000mAh battery is claimed to provide a whole
768 day of battery life time, but I have not seen any independent tests
769 confirming this. The vendor is still collecting preorders, and the
770 last I heard last night was that
22 more orders were needed before
771 production started.
</p
>
773 <p
>As far as I know, this is the first handheld preinstalled with
774 Debian. Please let me know if you know of any others. Is it the
775 first computer being sold with Debian preinstalled?
</p
>
780 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
781 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
782 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
783 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
784 <description><p
>During this weekends
785 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
786 squashing party and developer gathering
</a
>, we decided to do our part
787 to make sure there are good books about Debian available in Norwegian
788 Bokmål, and got in touch with the people behind the
789 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
790 project
</a
> to get started. If you want to help out, please start
792 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
793 hosted weblate project page
</a
>, and get in touch using
794 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
795 translators mailing list
</a
>. Please also check out
796 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
797 contributors
</a
>.
</p
>
799 <p
>The book is already available on paper in English, French and
800 Japanese, and our goal is to get it available on paper in Norwegian
801 Bokmål too. In addition to the paper edition, there are also EPUB and
802 Mobi versions available. And there are incomplete translations
803 available for many more languages.
</p
>
808 <title>One in two hundred Debian users using ZFS on Linux?
</title>
809 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
810 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
811 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
812 <description><p
>Just for fun I had a look at the popcon number of ZFS related
813 packages in Debian, and was quite surprised with what I found. I use
814 ZFS myself at home, but did not really expect many others to do so.
815 But I might be wrong.
</p
>
817 <p
>According to
818 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
819 results for spl-linux
</a
>, there are
1019 Debian installations, or
820 0.53% of the population, with the package installed. As far as I know
821 the only use of the spl-linux package is as a support library for ZFS
822 on Linux, so I use it here as proxy for measuring the number of ZFS
823 installation on Linux in Debian. In the kFreeBSD variant of Debian
824 the ZFS feature is already available, and there
825 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
826 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
827 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
829 <p
>But even though the Debian project leader Lucas Nussbaum
830 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
831 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
832 cleared, the package is still not in Debian. The package is again in
833 the NEW queue. Several uploads have been rejected so far because the
834 debian/copyright file was incomplete or wrong, but there is no reason
835 to give up. The current status can be seen on
836 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
837 team status page
</a
>, and
838 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
839 source code
</a
> is available on Alioth.
</p
>
841 <p
>As I want ZFS to be included in next version of Debian to make sure
842 my home server can function in the future using only official Debian
843 packages, and the current blocker is to get the debian/copyright file
844 accepted by the FTP masters in Debian, I decided a while back to try
845 to help out the team. This was the background for my blog post about
846 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
847 updating and checking debian/copyright semi-automatically
</a
>, and I
848 used the techniques I explored there to try to find any errors in the
849 copyright file. It is not very easy to check every one of the around
850 2000 files in the source package, but I hope we this time got it
851 right. If you want to help out, check out the git source and try to
852 find missing entries in the debian/copyright file.
</p
>
857 <title>Full battery stats collector is now available in Debian
</title>
858 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
860 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
861 <description><p
>Since this morning, the battery-stats package in Debian include an
862 extended collector that will collect the complete battery history for
863 later processing and graphing. The original collector store the
864 battery level as percentage of last full level, while the new
865 collector also record battery vendor, model, serial number, design
866 full level, last full level and current battery level. This make it
867 possible to predict the lifetime of the battery as well as visualise
868 the energy flow when the battery is charging or discharging.
</p
>
870 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
871 in the version
0.5.1 package in unstable. Get the new battery level graph
872 and lifetime prediction by running:
875 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
876 </pre
></p
>
878 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
880 <p
>The flow in/out of the battery can be seen by running (no menu
881 entry yet):
</p
>
884 /usr/share/battery-stats/battery-stats-graph-flow
885 </pre
></p
>
887 <p
>I
'm not quite happy with the way the data is visualised, at least
888 when there are few data points. The graphs look a bit better with a
889 few years of data.
</p
>
891 <p
>A while back one important feature I use in the battery stats
892 collector broke in Debian. The scripts in
893 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
894 suspect it happened when Jessie started using systemd, but I do not
895 know. The issue is reported as
896 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
897 pm-utils. I managed to work around it by adding an udev rule to call
898 the collector script every time the power connector is connected and
899 disconnected. With this fix in place it was finally time to make a
900 new release of the package, and get it into Debian.
</p
>
902 <p
>If you are interested in how your laptop battery is doing, please
904 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
905 in Debian unstable, or rebuild it on Jessie to get it working on
906 Debian stable. :) The upstream source is available from
907 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
908 As always, patches are very welcome.
</p
>
913 <title>Making battery measurements a little easier in Debian
</title>
914 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
915 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
916 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
917 <description><p
>Back in September, I blogged about
918 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
919 system I wrote to collect statistics about my laptop battery
</a
>, and
920 how it showed the decay and death of this battery (now replaced). I
921 created a simple deb package to handle the collection and graphing,
922 but did not want to upload it to Debian as there were already
923 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
924 package in Debian
</a
> that should do the same thing, and I did not see
925 a point of uploading a competing package when battery-stats could be
926 fixed instead. I reported a few bugs about its non-function, and
927 hoped someone would step in and fix it. But no-one did.
</p
>
929 <p
>I got tired of waiting a few days ago, and took matters in my own
930 hands. The end result is that I am now the new upstream developer of
931 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
932 battery-stats in Debian, and the package in Debian unstable is finally
933 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
934 information provided by the Linux kernel. If you install the
935 battery-stats package from unstable now, you will be able to get a
936 graph of the current battery fill level, to get some idea about the
937 status of the battery. The source package build and work just fine in
938 Debian testing and stable (and probably oldstable too, but I have not
939 tested). The default graph you get for that system look like this:
</p
>
941 <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
>
943 <p
>My plans for the future is to merge my old scripts into the
944 battery-stats package, as my old scripts collected a lot more details
945 about the battery. The scripts are merged into the upstream
946 battery-stats git repository already, but I am not convinced they work
947 yet, as I changed a lot of paths along the way. Will have to test a
948 bit more before I make a new release.
</p
>
950 <p
>I will also consider changing the file format slightly, as I
951 suspect the way I combine several values into one field might make it
952 impossible to know the type of the value when using it for processing
953 and graphing.
</p
>
955 <p
>If you would like I would like to keep an close eye on your laptop
956 battery, check out the battery-stats package in
957 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
959 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
960 I would love some help to improve the system further.
</p
>
965 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
966 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
967 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
968 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
969 <description><p
>Making packages for Debian requires quite a lot of attention to
970 details. And one of the details is the content of the
971 debian/copyright file, which should list all relevant licenses used by
972 the code in the package in question, preferably in
973 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
974 readable DEP5 format
</a
>.
</p
>
976 <p
>For large packages with lots of contributors it is hard to write
977 and update this file manually, and if you get some detail wrong, the
978 package is normally rejected by the ftpmasters. So getting it right
979 the first time around get the package into Debian faster, and save
980 both you and the ftpmasters some work.. Today, while trying to figure
981 out what was wrong with
982 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
983 zfsonlinux copyright file
</a
>, I decided to spend some time on
984 figuring out the options for doing this job automatically, or at least
985 semi-automatically.
</p
>
987 <p
>Lucikly, there are at least two tools available for generating the
988 file based on the code in the source package,
989 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
990 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
991 not sure which one of them came first, but both seem to be able to
992 create a sensible draft file. As far as I can tell, none of them can
993 be trusted to get the result just right, so the content need to be
994 polished a bit before the file is OK to upload. I found the debmake
996 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
997 blog posts from
2014</a
>.
999 <p
>To generate using debmake, use the -cc option:
1001 <p
><pre
>
1002 debmake -cc
> debian/copyright
1003 </pre
></p
>
1005 <p
>Note there are some problems with python and non-ASCII names, so
1006 this might not be the best option.
</p
>
1008 <p
>The cme option is based on a config parsing library, and I found
1010 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1011 blog post from
2015</a
>. To generate using cme, use the
'update
1012 dpkg-copyright
' option:
1014 <p
><pre
>
1015 cme update dpkg-copyright
1016 </pre
></p
>
1018 <p
>This will create or update debian/copyright. The cme tool seem to
1019 handle UTF-
8 names better than debmake.
</p
>
1021 <p
>When the copyright file is created, I would also like some help to
1022 check if the file is correct. For this I found two good options,
1023 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1024 to focus on license types and file matching, and is able to detect
1025 ineffective blocks in the copyright file. The latter reports missing
1026 copyright holders and years, but was confused by inconsistent license
1027 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1028 fix all issues reported by them before uploading. But I do not know
1029 if the tools and the ftpmasters agree on what is important to fix in a
1030 copyright file, so the package might still be rejected.
</p
>
1032 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1033 will read through the source and try to find all copyright statements.
1034 It is not comparing the result to the content of debian/copyright, but
1035 can be useful when verifying the content of the copyright file.
</p
>
1037 <p
>Are you aware of better tools in Debian to create and update
1038 debian/copyright file. Please let me know, or blog about it on
1039 planet.debian.org.
</p
>
1041 <p
>As usual, if you use Bitcoin and want to show your support of my
1042 activities, please send Bitcoin donations to my address
1043 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1045 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1046 on how to use licensecheck and cdbs to create a draft copyright file
1048 <p
><pre
>
1049 licensecheck --copyright -r `find * -type f` | \
1050 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1051 </pre
></p
>
1053 <p
>He mentioned that he normally check the generated file into the
1054 version control system to make it easier to discover license and
1055 copyright changes in the upstream source. I will try to do the same
1056 with my packages in the future.
</p
>
1058 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1059 against using -quiet for new users, so I removed it from the proposed
1060 command line.
</p
>
1065 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1066 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1067 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1068 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1069 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1070 is taking shape in Debian, and one provided feature is a very
1071 convenient way to tell you which package to install to make a given
1072 firmware file available when the kernel is looking for it. This can
1073 be done using apt-file too, but that is for someone else to blog
1076 <p
>Here is a small recipe to find the package with a given firmware
1077 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1078 picked from the set of firmware announced using appstream in Debian
1079 unstable. In general you would be looking for the firmware requested
1080 by the kernel during kernel module loading. To find the package
1081 providing the example file, do like this:
</p
>
1083 <blockquote
><pre
>
1084 % apt install appstream
1088 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1089 awk
'/Package:/ {print $
2}
'
1092 </pre
></blockquote
>
1094 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
1095 appstream wiki
</a
> page to learn how to embed the package metadata in
1096 a way appstream can use.
</p
>
1098 <p
>This same approach can be used to find any package supporting a
1099 given MIME type. This is very useful when you get a file you do not
1100 know how to handle. First find the mime type using
<tt
>file
1101 --mime-type
</tt
>, and next look up the package providing support for
1102 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1103 and you can find all packages handling this type like this:
</p
>
1105 <blockquote
><pre
>
1106 % apt install appstream
1110 % appstreamcli what-provides mimetype image/svg+xml | \
1111 awk
'/Package:/ {print $
2}
'
1133 </pre
></blockquote
>
1135 <p
>I believe the MIME types are fetched from the desktop file for
1136 packages providing appstream metadata.
</p
>
1141 <title>Creepy, visualise geotagged social media information - nice free software
</title>
1142 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
1143 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
1144 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
1145 <description><p
>Most people seem not to realise that every time they walk around
1146 with the computerised radio beacon known as a mobile phone their
1147 position is tracked by the phone company and often stored for a long
1148 time (like every time a SMS is received or sent). And if their
1149 computerised radio beacon is capable of running programs (often called
1150 mobile apps) downloaded from the Internet, these programs are often
1151 also capable of tracking their location (if the app requested access
1152 during installation). And when these programs send out information to
1153 central collection points, the location is often included, unless
1154 extra care is taken to not send the location. The provided
1155 information is used by several entities, for good and bad (what is
1156 good and bad, depend on your point of view). What is certain, is that
1157 the private sphere and the right to free movement is challenged and
1158 perhaps even eradicated for those announcing their location this way,
1159 when they share their whereabouts with private and public
1162 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1164 <p
>The phone company logs provide a register of locations to check out
1165 when one want to figure out what the tracked person was doing. It is
1166 unavailable for most of us, but provided to selected government
1167 officials, company staff, those illegally buying information from
1168 unfaithful servants and crackers stealing the information. But the
1169 public information can be collected and analysed, and a free software
1170 tool to do so is called
1171 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1172 discovered it when I read
1173 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1174 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1175 November
2014, and decided to check if it was available in Debian.
1176 The python program was in Debian, but
1177 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1178 Debian
</a
> was completely broken and practically unmaintained. I
1179 uploaded a new version which did not work quite right, but did not
1180 have time to fix it then. This Christmas I decided to finally try to
1181 get Creepy operational in Debian. Now a fixed version is available in
1182 Debian unstable and testing, and almost all Debian specific patches
1184 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1186 <p
>The Creepy program visualises geolocation information fetched from
1187 Twitter, Instagram, Flickr and Google+, and allow one to get a
1188 complete picture of every social media message posted recently in a
1189 given area, or track the movement of a given individual across all
1190 these services. Earlier it was possible to use the search API of at
1191 least some of these services without identifying oneself, but these
1192 days it is impossible. This mean that to use Creepy, you need to
1193 configure it to log in as yourself on these services, and provide
1194 information to them about your search interests. This should be taken
1195 into account when using Creepy, as it will also share information
1196 about yourself with the services.
</p
>
1198 <p
>The picture above show the twitter messages sent from (or at least
1199 geotagged with a position from) the city centre of Oslo, the capital
1200 of Norway. One useful way to use Creepy is to first look at
1201 information tagged with an area of interest, and next look at all the
1202 information provided by one or more individuals who was in the area.
1203 I tested it by checking out which celebrity provide their location in
1204 twitter messages by checkout out who sent twitter messages near a
1205 Norwegian TV station, and next could track their position over time,
1206 making it possible to locate their home and work place, among other
1207 things. A similar technique have been
1208 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
1209 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
1210 tool to discover lying governments, and a useful tool to help people
1211 understand the value of the private information they provide to the
1214 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
1215 it depend on several python modules currently missing in Jessie (at
1216 least python-instagram, python-flickrapi and
1217 python-requests-toolbelt).
</p
>
1219 <p
>(I have uploaded
1220 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
1221 screenshots.debian.net
</a
> and licensed it under the same terms as the
1222 Creepy program in Debian.)
</p
>
1227 <title>Always download Debian packages using Tor - the simple recipe
</title>
1228 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
1229 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
1230 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
1231 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
1232 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
1233 that those listening on the Internet lines would have good reason to
1234 believe a computer have a given security hole
</a
> if it download a
1235 security fix from a Debian mirror. This is a good reason to always
1236 use encrypted connections to the Debian mirror, to make sure those
1237 listening do not know which IP address to attack. In August, Richard
1238 Hartmann observed that encryption was not enough, when it was possible
1239 to interfere download size to security patches or the fact that
1240 download took place shortly after a security fix was released, and
1241 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
1242 to always use Tor to download packages from the Debian mirror
</a
>. He
1243 was not the first to propose this, as the
1244 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
1245 package by Tim Retout already existed to make it easy to convince apt
1246 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
1247 aware of that package when I read the blog post from Richard.
</p
>
1249 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
1250 sysadmins, and he set up a Tor hidden service on one of the central
1251 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1252 it possible to download packages directly between two tor nodes,
1253 making sure the network traffic always were encrypted.
</p
>
1255 <p
>Here is a short recipe for enabling this on your machine, by
1256 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
1257 urls with tor+http and tor+https, and using the hidden service instead
1258 of the official Debian mirror site. I recommend installing
1259 <tt
>etckeeper
</tt
> before you start to have a history of the changes
1260 done in /etc/.
</p
>
1262 <blockquote
><pre
>
1263 apt install apt-transport-tor
1264 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
1265 sed -i
's% http% tor+http%
' /etc/apt/sources.list
1266 </pre
></blockquote
>
1268 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
1269 the sed commands for these too. The sed command is assuming your are
1270 using the ftp.debian.org Debian mirror. Adjust the command (or just
1271 edit the file manually) to match your mirror.
</p
>
1273 <p
>This work in Debian Jessie and later. Note that tools like
1274 <tt
>apt-file
</tt
> only recently started using the apt transport
1275 system, and do not work with these tor+http URLs. For
1276 <tt
>apt-file
</tt
> you need the version currently in experimental,
1277 which need a recent apt version currently only in unstable. So if you
1278 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
1280 <p
>Another advantage from this change is that your machine will start
1281 using Tor regularly and at fairly random intervals (every time you
1282 update the package lists or upgrade or install a new package), thus
1283 masking other Tor traffic done from the same machine. Using Tor will
1284 become normal for the machine in question.
</p
>
1286 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
1287 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
1288 enabled. It would be great if it was the default on any Debian
1294 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
1295 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
1296 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
1297 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
1298 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
1299 call the car license plate numbers in those days. I would write the
1300 numbers down in my little book and compare notes with the other kids
1301 to see how many region codes we had seen and if we had seen some
1302 exotic or special region codes and numbers. It was a fun game to pass
1303 time, as we kids have plenty of it.
</p
>
1305 <p
>A few days I came across
1306 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
1307 project
</a
>, a free software project to automatically discover and
1308 report license plates in images and video streams, and provide the
1309 "car numbers
" in a machine readable format. I
've been looking for
1310 such system for a while now, because I believe it is a bad idea that the
1311 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
1312 number plate recognition
</a
> tool only is available in the hands of
1313 the powerful, and want it to be available also for the powerless to
1314 even the score when it comes to surveillance and sousveillance. I
1315 discovered the developer
1316 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
1317 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
1318 help him get it into shape to get the package uploaded into the Debian
1321 <p
>Today we finally managed to get the package into shape and uploaded
1322 it into Debian, where it currently
1323 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
1324 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
1326 <p
>I guess you are wondering why on earth such tool would be useful
1327 for the common folks, ie those not running a large government
1328 surveillance system? Well, I plan to put it in a computer on my bike
1329 and in my car, tracking the cars nearby and allowing me to be notified
1330 when number plates on my watch list are discovered. Another use case
1331 was suggested by a friend of mine, who wanted to set it up at his home
1332 to open the car port automatically when it discovered the plate on his
1333 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1334 capable of placing his license plate number of a piece of cardboard to
1335 open his car port, men replied that it was always unlocked anyway. I
1336 guess for such use case it make sense. I am sure there are other use
1337 cases too, for those with imagination and a vision.
</p
>
1339 <p
>If you want to build your own version of the Debian package, check
1340 out the upstream git source and symlink ./distros/debian to ./debian/
1341 before running
"debuild
" to build the source. Or wait a bit until the
1342 package show up in unstable.
</p
>
1347 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
1348 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
1349 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
1350 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
1351 <description><p
>Around three years ago, I created
1352 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
1353 system
</a
> to get a more practical solution in Debian for handing
1354 hardware related packages. A GUI system in the isenkram package will
1355 present a pop-up dialog when some hardware dongle supported by
1356 relevant packages in Debian is inserted into the machine. The same
1357 lookup mechanism to detect packages is available as command line
1358 tools in the isenkram-cli package. In addition to mapping hardware,
1359 it will also map kernel firmware files to packages and make it easy to
1360 install needed firmware packages automatically. The key for this
1361 system to work is a good way to map hardware to packages, in other
1362 words, allow packages to announce what hardware they will work
1365 <p
>I started by providing data files in the isenkram source, and
1366 adding code to download the latest version of these data files at run
1367 time, to ensure every user had the most up to date mapping available.
1368 I also added support for storing the mapping in the Packages file in
1369 the apt repositories, but did not push this approach because while I
1370 was trying to figure out how to best store hardware/package mappings,
1371 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
1372 appstream system
</a
> was announced. I got in touch and suggested to
1373 add the hardware mapping into that data set to be able to use
1374 appstream as a data source, and this was accepted at least for the
1375 Debian version of appstream.
</p
>
1377 <p
>A few days ago using appstream in Debian for this became possible,
1378 and today I uploaded a new version
0.20 of isenkram adding support for
1379 appstream as a data source for mapping hardware to packages. The only
1380 package so far using appstream to announce its hardware support is my
1381 pymissile package. I got help from Matthias Klumpp with figuring out
1382 how do add the required
1383 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
1384 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
1385 this content:
</p
>
1387 <blockquote
><pre
>
1388 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1389 &lt;component
&gt;
1390 &lt;id
&gt;pymissile
&lt;/id
&gt;
1391 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
1392 &lt;name
&gt;pymissile
&lt;/name
&gt;
1393 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
1394 &lt;description
&gt;
1396 Pymissile provides a curses interface to control an original
1397 Marks and Spencer / Striker USB Missile Launcher, as well as a
1398 motion control script to allow a webcamera to control the
1401 &lt;/description
&gt;
1402 &lt;provides
&gt;
1403 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
1404 &lt;/provides
&gt;
1405 &lt;/component
&gt;
1406 </pre
></blockquote
>
1408 <p
>The key for isenkram is the component/provides/modalias value,
1409 which is a glob style match rule for hardware specific strings
1410 (modalias strings) provided by the Linux kernel. In this case, it
1411 will map to all USB devices with vendor code
1130 and product code
1414 <p
>Note, it is important that the license of all the metadata files
1415 are compatible to have permissions to aggregate them into archive wide
1416 appstream files. Matthias suggested to use MIT or BSD licenses for
1417 these files. A challenge is figuring out a good id for the data, as
1418 it is supposed to be globally unique and shared across distributions
1419 (in other words, best to coordinate with upstream what to use). But
1420 it can be changed later or, so we went with the package name as
1421 upstream for this project is dormant.
</p
>
1423 <p
>To get the metadata file installed in the correct location for the
1424 mirror update scripts to pick it up and include its content the
1425 appstream data source, the file must be installed in the binary
1426 package under /usr/share/appdata/. I did this by adding the following
1427 line to debian/pymissile.install:
</p
>
1429 <blockquote
><pre
>
1430 debian/pymissile.metainfo.xml usr/share/appdata
1431 </pre
></blockquote
>
1433 <p
>With that in place, the command line tool isenkram-lookup will list
1434 all packages useful on the current computer automatically, and the GUI
1435 pop-up handler will propose to install the package not already
1436 installed if a hardware dongle is inserted into the machine in
1439 <p
>Details of the modalias field in appstream is available from the
1440 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
1442 <p
>To locate the modalias values of all hardware present in a machine,
1443 try running this command on the command line:
</p
>
1445 <blockquote
><pre
>
1446 cat $(find /sys/devices/|grep modalias)
1447 </pre
></blockquote
>
1449 <p
>To learn more about the isenkram system, please check out
1450 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1451 blog posts tagged isenkram
</a
>.
</p
>
1456 <title>The GNU General Public License is not magic pixie dust
</title>
1457 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
1458 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
1459 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
1460 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
1461 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
1462 GPL is not magic pixie dust
</a
>" explain the importance of making sure
1463 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
1464 I quote the blog post from Paul in full here with his permission:
<p
>
1468 <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
>
1471 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
1473 The first step is to choose a
1474 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
1477 The next step is, when someone fails to follow that copyleft license,
1478 <b
>it must be enforced
</b
><br/
>
1480 and its a simple fact of our modern society that such type of
1483 is incredibly expensive to do and incredibly difficult to do.
1486 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
1487 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
1488 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
1489 0x57</a
></small
></p
>
1491 <p
>As the Debian Website
1492 <a href=
"https://bugs.debian.org/
794116">used
</a
>
1493 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
1494 imply, public domain and permissively licensed software can lead to
1495 the production of more proprietary software as people discover useful
1496 software, extend it and or incorporate it into their hardware or
1497 software products. Copyleft licenses such as the GNU GPL were created
1498 to close off this avenue to the production of proprietary software but
1499 such licenses are not enough. With the ongoing adoption of Free
1500 Software by individuals and groups, inevitably the community
's
1501 expectations of license compliance are violated, usually out of
1502 ignorance of the way Free Software works, but not always. As Karen
1503 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
1504 Freedom
">FaiF
</a
>
1505 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
1506 copyleft is nothing if no-one is willing and able to stand up in court
1507 to protect it. The reality of today
's world is that legal
1508 representation is expensive, difficult and time consuming. With
1509 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
1510 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
1511 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
1512 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
1513 of the Linux project, Debian and other groups against GPL violations.
1514 In March the SFC supported a
1515 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
1516 by Christoph Hellwig
</a
> against VMware for refusing to
1517 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
1518 with the GPL
</a
> in relation to their use of parts of the Linux
1519 kernel. Since then two of their sponsors pulled corporate funding and
1521 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
1522 or cancelled their talks
</a
>. As a result they have decided to rely
1523 less on corporate funding and more on the broad community of
1524 individuals who support Free Software and copyleft. So the SFC has
1525 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
1526 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
1527 a community of folks who stand up for copyleft and the GPL by
1528 supporting their work on promoting and supporting copyleft and Free
1531 <p
>If you support Free Software,
1532 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
1533 what the SFC do, agree with their
1534 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
1535 principles
</a
>, are happy about their
1536 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
1537 work on a project that is an SFC
1538 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
1539 just want to stand up for copyleft, please join
1540 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
1541 Allan Webber
</a
>,
1542 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
1544 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
1545 Bacon
</a
>, myself and
1546 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
1548 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
1549 next week your donation will be
1550 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
1551 by an anonymous donor. Please also consider asking your employer to
1552 match your donation or become a sponsor of SFC. Don
't forget to
1553 spread the word about your support for SFC via email, your blog and or
1554 social media accounts.
</p
>
1558 <p
>I agree with Paul on this topic and just signed up as a Supporter
1559 of Software Freedom Conservancy myself. Perhaps you should be a
1560 supporter too?
</p
>
1565 <title>PGP key transition statement for key EE4E02F9
</title>
1566 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
1567 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
1568 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
1569 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
1570 set it up properly. I wanted to generate it offline and have it
1571 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
1572 smart card
</a
> for daily use, and learning how to do it and finding
1573 time to sit down with an offline machine almost took forever. But
1574 finally I
've been able to complete the process, and have now moved
1575 from my old GPG key to a new GPG key. See
1576 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
1577 full transition statement, signed with both my old and new key
</a
> for
1578 the details. This is my new key:
</p
>
1581 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
1582 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
1583 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
1584 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
1585 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
1586 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
1587 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
1590 <p
>The key can be downloaded from the OpenPGP key servers, signed by
1591 my old key.
</p
>
1593 <p
>If you signed my old key
1594 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
1595 I
'd very much appreciate a signature on my new key, details and
1596 instructions in the transition statement. I m happy to reciprocate if
1597 you have a similarly signed transition statement to present.
</p
>
1602 <title>The life and death of a laptop battery
</title>
1603 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
1604 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
1605 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
1606 <description><p
>When I get a new laptop, the battery life time at the start is OK.
1607 But this do not last. The last few laptops gave me a feeling that
1608 within a year, the life time is just a fraction of what it used to be,
1609 and it slowly become painful to use the laptop without power connected
1610 all the time. Because of this, when I got a new Thinkpad X230 laptop
1611 about two years ago, I decided to monitor its battery state to have
1612 more hard facts when the battery started to fail.
</p
>
1614 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
1616 <p
>First I tried to find a sensible Debian package to record the
1617 battery status, assuming that this must be a problem already handled
1618 by someone else. I found
1619 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
1620 which collects statistics from the battery, but it was completely
1621 broken. I sent a few suggestions to the maintainer, but decided to
1622 write my own collector as a shell script while I waited for feedback
1624 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
1625 blog post about the battery development on a MacBook Air
</a
> I also
1627 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
1628 available in Debian.
</p
>
1630 <p
>I started my collector
2013-
07-
15, and it has been collecting
1631 battery stats ever since. Now my
1632 /var/log/hjemmenett-battery-status.log file contain around
115,
000
1633 measurements, from the time the battery was working great until now,
1634 when it is unable to charge above
7% of original capacity. My
1635 collector shell script is quite simple and look like this:
</p
>
1640 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
1642 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
1643 logfile=/var/log/hjemmenett-battery-status.log
1645 files=
"manufacturer model_name technology serial_number \
1646 energy_full energy_full_design energy_now cycle_count status
"
1648 if [ ! -e
"$logfile
" ] ; then
1650 printf
"timestamp,
"
1652 printf
"%s,
" $f
1655 )
> "$logfile
"
1659 # Print complete message in one echo call, to avoid race condition
1660 # when several log processes run in parallel.
1661 msg=$(printf
"%s,
" $(date +%s); \
1662 for f in $files; do \
1663 printf
"%s,
" $(cat $f); \
1665 echo
"$msg
"
1668 cd /sys/class/power_supply
1671 (cd $bat
&& log_battery
>> "$logfile
")
1675 <p
>The script is called when the power management system detect a
1676 change in the power status (power plug in or out), and when going into
1677 and out of hibernation and suspend. In addition, it collect a value
1678 every
10 minutes. This make it possible for me know when the battery
1679 is discharging, charging and how the maximum charge change over time.
1680 The code for the Debian package
1681 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
1682 available on github
</a
>.
</p
>
1684 <p
>The collected log file look like this:
</p
>
1687 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1688 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
1690 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1691 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1694 <p
>I wrote a small script to create a graph of the charge development
1695 over time. This graph depicted above show the slow death of my laptop
1698 <p
>But why is this happening? Why are my laptop batteries always
1699 dying in a year or two, while the batteries of space probes and
1700 satellites keep working year after year. If we are to believe
1701 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
1702 University
</a
>, the cause is me charging the battery whenever I have a
1703 chance, and the fix is to not charge the Lithium-ion batteries to
100%
1704 all the time, but to stay below
90% of full charge most of the time.
1705 I
've been told that the Tesla electric cars
1706 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
1707 the charge of their batteries to
80%
</a
>, with the option to charge to
1708 100% when preparing for a longer trip (not that I would want a car
1709 like Tesla where rights to privacy is abandoned, but that is another
1710 story), which I guess is the option we should have for laptops on
1711 Linux too.
</p
>
1713 <p
>Is there a good and generic way with Linux to tell the battery to
1714 stop charging at
80%, unless requested to charge to
100% once in
1715 preparation for a longer trip? I found
1716 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
1717 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1718 80%
</a
>, but could not get it to work (kernel module refused to
1721 <p
>I wonder why the battery capacity was reported to be more than
100%
1722 at the start. I also wonder why the
"full capacity
" increases some
1723 times, and if it is possible to repeat the process to get the battery
1724 back to design capacity. And I wonder if the discharge and charge
1725 speed change over time, or if this stay the same. I did not yet try
1726 to write a tool to calculate the derivative values of the battery
1727 level, but suspect some interesting insights might be learned from
1730 <p
>Update
2015-
09-
24: I got a tip to install the packages
1731 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1732 packages instead of the tp-smapi-dkms package I had tried to use
1733 initially, and use
'tlp setcharge
40 80' to change when charging start
1734 and stop. I
've done so now, but expect my existing battery is toast
1735 and need to be replaced. The proposal is unfortunately Thinkpad
1741 <title>New laptop - some more clues and ideas based on feedback
</title>
1742 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
1743 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
1744 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
1745 <description><p
>Several people contacted me after my previous blog post about my
1746 need for a new laptop, and provided very useful feedback. I wish to
1747 thank every one of these. Several pointed me to the possibility of
1748 fixing my X230, and I am already in the process of getting Lenovo to
1749 do so thanks to the on site, next day support contract covering the
1750 machine. But the battery is almost useless (I expect to replace it
1751 with a non-official battery) and I do not expect the machine to live
1752 for many more years, so it is time to plan its replacement. If I did
1753 not have a support contract, it was suggested to find replacement parts
1754 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
1755 might present a language barrier as I do not understand French.
</p
>
1757 <p
>One tip I got was to use the
1758 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
1759 compare laptop models. It seem to have more models available than
1760 prisjakt.no. Another tip I got from someone I know have similar
1761 keyboard preferences was that the HP EliteBook
840 keyboard is not
1762 very good, and this matches my experience with earlier EliteBook
1763 keyboards I tested. Because of this, I will not consider it any further.
1765 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
1766 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1767 (which is missing from the X240), and is working fairly well with
1768 Debian Sid/Unstable according to
1769 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
1770 got on the keyboard quality are not consistent. Some say the keyboard
1771 is good, others say it is ok, while others say it is not very good.
1772 Those with experience from X41 and and X60 agree that the X250
1773 keyboard is not as good as those trusty old laptops, and suggest I
1774 keep and fix my X230 instead of upgrading, or get a used X230 to
1775 replace it. I
'm also told that the X250 lack leds for caps lock, disk
1776 activity and battery status, which is very convenient on my X230. I
'm
1777 also told that the CPU fan is running very often, making it a bit
1778 noisy. In any case, the X250 do not work out of the box with Debian
1779 Stable/Jessie, one of my requirements.
</p
>
1781 <p
>I have also gotten a few vendor proposals, one was
1782 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
1783 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
1784 The latter look very attractive to me.
</p
>
1786 <p
>Again, thank you all for the very useful feedback. It help a lot
1787 as I keep looking for a replacement.
</p
>
1789 <p
>Update
2015-
07-
06: I was recommended to check out the
1790 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
1792 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
1793 thinkpad X models
</a
>, and provide one year warranty.
</p
>
1798 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
1799 <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>
1800 <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>
1801 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
1802 <description><p
>My primary work horse laptop is failing, and will need a
1803 replacement soon. The left
5 cm of the screen on my Thinkpad X230
1804 started flickering yesterday, and I suspect the cause is a broken
1805 cable, as changing the angle of the screen some times get rid of the
1806 flickering.
</p
>
1808 <p
>My requirements have not really changed since I bought it, and is
1810 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
1811 described them in
2013</a
>. The last time I bought a laptop, I had
1813 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
1814 where I could select at least a few of the requirements (mouse pin,
1815 wifi, weight) and go through the rest manually. Three button mouse
1816 and a good keyboard is not available as an option, and all the three
1817 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
1818 G2) lack three mouse buttons). It is also unclear to me how good the
1819 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1820 the keyboard, even if the quality and robustness in the X series have
1821 deteriorated since X41.
</p
>
1823 <p
>I wonder how I can find a sensible laptop when none of the options
1824 seem sensible to me? Are there better services around to search the
1825 set of available laptops for features? Please send me an email if you
1826 have suggestions.
</p
>
1828 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
1829 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
1830 of endorsed hardware
</a
>, which is useful background information.
</p
>
1835 <title>How to stay with sysvinit in Debian Jessie
</title>
1836 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
1837 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
1838 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
1839 <description><p
>By now, it is well known that Debian Jessie will not be using
1840 sysvinit as its boot system by default. But how can one keep using
1841 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1843 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
1844 Schubert
</a
> and
1845 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
1848 <p
>If you already are using Wheezy and want to upgrade to Jessie and
1849 keep sysvinit as your boot system, create a file
1850 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
1851 you upgrade:
</p
>
1853 <p
><blockquote
><pre
>
1854 Package: systemd-sysv
1855 Pin: release o=Debian
1857 </pre
></blockquote
><p
>
1859 <p
>This file content will tell apt and aptitude to not consider
1860 installing systemd-sysv as part of any installation and upgrade
1861 solution when resolving dependencies, and thus tell it to avoid
1862 systemd as a default boot system. The end result should be that the
1863 upgraded system keep using sysvinit.
</p
>
1865 <p
>If you are installing Jessie for the first time, there is no way to
1866 get sysvinit installed by default (debootstrap used by
1867 debian-installer have no option for this), but one can tell the
1868 installer to switch to sysvinit before the first boot. Either by
1869 using a kernel argument to the installer, or by adding a line to the
1870 preseed file used. First, the kernel command line argument:
1872 <p
><blockquote
><pre
>
1873 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
1874 </pre
></blockquote
><p
>
1876 <p
>Next, the line to use in a preseed file:
</p
>
1878 <p
><blockquote
><pre
>
1879 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1880 </pre
></blockquote
><p
>
1882 <p
>One can of course also do this after the first boot by installing
1883 the sysvinit-core package.
</p
>
1885 <p
>I recommend only using sysvinit if you really need it, as the
1886 sysvinit boot sequence in Debian have several hardware specific bugs
1887 on Linux caused by the fact that it is unpredictable when hardware
1888 devices show up during boot. But on the other hand, the new default
1889 boot system still have a few rough edges I hope will be fixed before
1890 Jessie is released.
</p
>
1892 <p
>Update
2014-
11-
26: Inspired by
1893 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
1894 blog post by Torsten Glaser
</a
>, added --purge to the preseed
1900 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
1901 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
1902 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
1903 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
1904 <description><p
>The right to communicate with your friends and family in private,
1905 without anyone snooping, is a right every citicen have in a liberal
1906 democracy. But this right is under serious attack these days.
</p
>
1908 <p
>A while back it occurred to me that one way to make the dragnet
1909 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1910 the whisleblower Snowden) more expensive for Internet email,
1911 is to deliver all email using SMTP via Tor. Such SMTP option would be
1912 a nice addition to the FreedomBox project if we could send email
1913 between FreedomBox machines without leaking metadata about the emails
1914 to the people peeking on the wire. I
1915 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
1916 this on the FreedomBox project mailing list in October
</a
> and got a
1917 lot of useful feedback and suggestions. It also became obvious to me
1918 that this was not a novel idea, as the same idea was tested and
1919 documented by Johannes Berg as early as
2006, and both
1920 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
1921 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
1922 propose a similar method / protocol to pass emails between users.
</p
>
1924 <p
>To implement such system one need to set up a Tor hidden service
1925 providing the SMTP protocol on port
25, and use email addresses
1926 looking like username@hidden-service-name.onion. With such addresses
1927 the connections to port
25 on hidden-service-name.onion using Tor will
1928 go to the correct SMTP server. To do this, one need to configure the
1929 Tor daemon to provide the hidden service and the mail server to accept
1930 emails for this .onion domain. To learn more about Exim configuration
1931 in Debian and test the design provided by Johannes Berg in his FAQ, I
1932 set out yesterday to create a Debian package for making it trivial to
1933 set up such SMTP over Tor service based on Debian. Getting it to work
1934 were fairly easy, and
1935 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
1936 source code for the Debian package
</a
> is available from github. I
1937 plan to move it into Debian if further testing prove this to be a
1938 useful approach.
</p
>
1940 <p
>If you want to test this, set up a blank Debian machine without any
1941 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
1942 get rid of exim4). Install tor, clone the git repository mentioned
1943 above, build the deb and install it on the machine. Next, run
1944 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
1945 the instructions to get the service up and running. Restart tor and
1946 exim when it is done, and test mail delivery using swaks like
1949 <p
><blockquote
><pre
>
1950 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1951 --to fbx@dutlqrrmjhtfa3vp.onion
1952 </pre
></blockquote
></p
>
1954 <p
>This will test the SMTP delivery using tor. Replace the email
1955 address with your own address to test your server. :)
</p
>
1957 <p
>The setup procedure is still to complex, and I hope it can be made
1958 easier and more automatic. Especially the tor setup need more work.
1959 Also, the package include a tor-smtp tool written in C, but its task
1960 should probably be rewritten in some script language to make the deb
1961 architecture independent. It would probably also make the code easier
1962 to review. The tor-smtp tool currently need to listen on a socket for
1963 exim to talk to it and is started using xinetd. It would be better if
1964 no daemon and no socket is needed. I suspect it is possible to get
1965 exim to run a command line tool for delivery instead of talking to a
1966 socket, and hope to figure out how in a future version of this
1969 <p
>Until I wipe my test machine, I can be reached using the
1970 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
1971 SMTorP. :)
</p
>
1976 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
1977 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
1978 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
1979 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
1980 <description><p
>If you ever had to moderate a mailman list, like the ones on
1981 alioth.debian.org, you know the web interface is fairly slow to
1982 operate. First you visit one web page, enter the moderation password
1983 and get a new page shown with a list of all the messages to moderate
1984 and various options for each email address. This take a while for
1985 every list you moderate, and you need to do it regularly to do a good
1986 job as a list moderator. But there is a quick alternative,
1987 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
1988 listadmin program
</a
>. It allow you to check lists for new messages
1989 to moderate in a fraction of a second. Here is a test run on two
1990 lists I recently took over:
</p
>
1992 <p
><blockquote
><pre
>
1993 % time listadmin xiph
1994 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1995 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2001 </pre
></blockquote
></p
>
2003 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2004 there are no message in the moderation queue. Every morning I
2005 currently moderate
68 mailman lists, and it normally take around two
2006 minutes. When I took over the two pkg-xiph lists above a few days
2007 ago, there were
400 emails waiting in the moderator queue. It took me
2008 less than
15 minutes to process them all using the listadmin
2011 <p
>If you install
2012 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2013 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2014 with content like this, the moderation task is a breeze:
</p
>
2016 <p
><blockquote
><pre
>
2017 username username@example.org
2020 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2023 adminurl https://{domain}/mailman/admindb/{list}
2024 mailman-list@lists.example.com
2027 other-list@otherserver.example.org
2028 </pre
></blockquote
></p
>
2030 <p
>There are other options to set as well. Check the manual page to
2031 learn the details.
</p
>
2033 <p
>If you are forced to moderate lists on a mailman installation where
2034 the SSL certificate is self signed or not properly signed by a
2035 generally accepted signing authority, you can set a environment
2036 variable when calling listadmin to disable SSL verification:
</p
>
2038 <p
><blockquote
><pre
>
2039 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2040 </pre
></blockquote
></p
>
2042 <p
>If you want to moderate a subset of the lists you take care of, you
2043 can provide an argument to the listadmin script like I do in the
2044 initial screen dump (the xiph argument). Using an argument, only
2045 lists matching the argument string will be processed. This make it
2046 quick to accept messages if you notice the moderation request in your
2049 <p
>Without the listadmin program, I would never be the moderator of
68
2050 mailing lists, as I simply do not have time to spend on that if the
2051 process was any slower. The listadmin program have saved me hours of
2052 time I could spend elsewhere over the years. It truly is nice free
2055 <p
>As usual, if you use Bitcoin and want to show your support of my
2056 activities, please send Bitcoin donations to my address
2057 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2059 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2060 configuration example. Also, I
've been told that the
2061 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2067 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2068 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2069 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2070 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2071 <description><p
>When PXE installing laptops with Debian, I often run into the
2072 problem that the WiFi card require some firmware to work properly.
2073 And it has been a pain to fix this using preseeding in Debian.
2074 Normally something more is needed. But thanks to
2075 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2076 package
</a
> and its recent tasksel extension, it has now become easy
2077 to do this using simple preseeding.
</p
>
2079 <p
>The isenkram-cli package provide tasksel tasks which will install
2080 firmware for the hardware found in the machine (actually, requested by
2081 the kernel modules for the hardware). (It can also install user space
2082 programs supporting the hardware detected, but that is not the focus
2083 of this story.)
</p
>
2085 <p
>To get this working in the default installation, two preeseding
2086 values are needed. First, the isenkram-cli package must be installed
2087 into the target chroot (aka the hard drive) before tasksel is executed
2088 in the pkgsel step of the debian-installer system. This is done by
2089 preseeding the base-installer/includes debconf value to include the
2090 isenkram-cli package. The package name is next passed to debootstrap
2091 for installation. With the isenkram-cli package in place, tasksel
2092 will automatically use the isenkram tasks to detect hardware specific
2093 packages for the machine being installed and install them, because
2094 isenkram-cli contain tasksel tasks.
</p
>
2096 <p
>Second, one need to enable the non-free APT repository, because
2097 most firmware unfortunately is non-free. This is done by preseeding
2098 the apt-mirror-setup step. This is unfortunate, but for a lot of
2099 hardware it is the only option in Debian.
</p
>
2101 <p
>The end result is two lines needed in your preseeding file to get
2102 firmware installed automatically by the installer:
</p
>
2104 <p
><blockquote
><pre
>
2105 base-installer base-installer/includes string isenkram-cli
2106 apt-mirror-setup apt-setup/non-free boolean true
2107 </pre
></blockquote
></p
>
2109 <p
>The current version of isenkram-cli in testing/jessie will install
2110 both firmware and user space packages when using this method. It also
2111 do not work well, so use version
0.15 or later. Installing both
2112 firmware and user space packages might give you a bit more than you
2113 want, so I decided to split the tasksel task in two, one for firmware
2114 and one for user space programs. The firmware task is enabled by
2115 default, while the one for user space programs is not. This split is
2116 implemented in the package currently in unstable.
</p
>
2118 <p
>If you decide to give this a go, please let me know (via email) how
2119 this recipe work for you. :)
</p
>
2121 <p
>So, I bet you are wondering, how can this work. First and
2122 foremost, it work because tasksel is modular, and driven by whatever
2123 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2124 isenkram-cli package place two files for tasksel to find. First there
2125 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2127 <p
><blockquote
><pre
>
2128 Task: isenkram-packages
2130 Description: Hardware specific packages (autodetected by isenkram)
2131 Based on the detected hardware various hardware specific packages are
2133 Test-new-install: show show
2135 Packages: for-current-hardware
2137 Task: isenkram-firmware
2139 Description: Hardware specific firmware packages (autodetected by isenkram)
2140 Based on the detected hardware various hardware specific firmware
2141 packages are proposed.
2142 Test-new-install: mark show
2144 Packages: for-current-hardware-firmware
2145 </pre
></blockquote
></p
>
2147 <p
>The key parts are Test-new-install which indicate how the task
2148 should be handled and the Packages line referencing to a script in
2149 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2150 list of packages to install. The for-current-hardware-firmware script
2151 look like this to list relevant firmware for the machine:
2153 <p
><blockquote
><pre
>
2156 PATH=/usr/sbin:$PATH
2158 isenkram-autoinstall-firmware -l
2159 </pre
></blockquote
></p
>
2161 <p
>With those two pieces in place, the firmware is installed by
2162 tasksel during the normal d-i run. :)
</p
>
2164 <p
>If you want to test what tasksel will install when isenkram-cli is
2165 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2166 --new-install
</tt
> to get the list of packages that tasksel would
2169 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2170 pilots in testing this feature, as isenkram is used there now to
2171 install firmware, replacing the earlier scripts.
</p
>
2176 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2177 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2179 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2180 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2181 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2182 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2183 on a screen normally showing the bread types and prizes:
</p
>
2185 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2187 <p
>If it had booted as it was supposed to, I would never had known
2188 about this hidden Linux installation. It is interesting what
2189 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
2194 <title>New lsdvd release version
0.17 is ready
</title>
2195 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
2196 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
2197 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
2198 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
2199 got a new set of developers a few weeks ago, after the original
2200 developer decided to step down and pass the project to fresh blood.
2201 This project is now maintained by Petter Reinholdtsen and Steve
2204 <p
>I just wrapped up
2205 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
2206 new lsdvd release
</a
>, available in git or from
2207 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
2208 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
2213 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
2214 <li
>Check for garbage in the program chains, which indicate that a track is
2215 non-existant, to work around additional copy protection
</li
>
2216 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
2217 <li
>Fix pallete display of first entry
</li
>
2218 <li
>Fix include orders
</li
>
2219 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
2220 <li
>Fix the chapter count
</li
>
2221 <li
>Make sure the array size and the array limit used when initialising
2222 the palette size is the same.
</li
>
2223 <li
>Fix array printing.
</li
>
2224 <li
>Correct subsecond calculations.
</li
>
2225 <li
>Add sector information to the output format.
</li
>
2226 <li
>Clean up code to be closer to ANSI C and compile without warnings
2227 with more GCC compiler warnings.
</li
>
2231 <p
>This change bring together patches for lsdvd in use in various
2232 Linux and Unix distributions, as well as patches submitted to the
2233 project the last nine years. Please check it out. :)
</p
>
2238 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
2239 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
2240 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
2241 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
2242 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2243 project
</a
> provide a Linux solution for schools, including a
2244 powerful desktop with education software, a central server providing
2245 web pages, user database, user home directories, central login and PXE
2246 boot of both clients without disk and the installation to install Debian
2247 Edu on machines with disk (and a few other services perhaps to small
2248 to mention here). We in the Debian Edu team are currently working on
2249 the Jessie based version, trying to get everything in shape before the
2250 freeze, to avoid having to maintain our own package repository in the
2252 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
2253 status
</a
> can be seen on the Debian wiki, and there is still heaps of
2254 work left. Some fatal problems block testing, breaking the installer,
2255 but it is possible to work around these to get anyway. Here is a
2256 recipe on how to get the installation limping along.
</p
>
2258 <p
>First, download the test ISO via
2259 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
2260 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
2262 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
2263 The ISO build was broken on Tuesday, so we do not get a new ISO every
2264 12 hours or so, but thankfully the ISO we already got we are able to
2265 install with some tweaking.
</p
>
2267 <p
>When you get to the Debian Edu profile question, go to tty2
2268 (use Alt-Ctrl-F2), run
</p
>
2270 <p
><blockquote
><pre
>
2271 nano /usr/bin/edu-eatmydata-install
2272 </pre
></blockquote
></p
>
2274 <p
>and add
'exit
0' as the second line, disabling the eatmydata
2275 optimization. Return to the installation, select the profile you want
2276 and continue. Without this change, exim4-config will fail to install
2277 due to a known bug in eatmydata.
</p
>
2279 <p
>When you get the grub question at the end, answer /dev/sda (or if
2280 this do not work, figure out what your correct value would be. All my
2281 test machines need /dev/sda, so I have no advice if it do not fit
2282 your need.
</p
>
2284 <p
>If you installed a profile including a graphical desktop, log in as
2285 root after the initial boot from hard drive, and install the
2286 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2287 or mate. If you want several desktop options, install more than one
2288 metapackage. Once this is done, reboot and you should have a working
2289 graphical login screen. This workaround should no longer be needed
2290 once the education-tasks package version
1.801 enter testing in two
2293 <p
>I believe the ISO build will start working on two days when the new
2294 tasksel package enter testing and Steve McIntyre get a chance to
2295 update the debian-cd git repository. The eatmydata, grub and desktop
2296 issues are already fixed in unstable and testing, and should show up
2297 on the ISO as soon as the ISO build start working again. Well the
2298 eatmydata optimization is really just disabled. The proper fix
2299 require an upload by the eatmydata maintainer applying the patch
2300 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
2301 The rest have proper fixes in unstable.
</p
>
2303 <p
>I hope this get you going with the installation testing, as we are
2304 quickly running out of time trying to get our Jessie based
2305 installation ready before the distribution freeze in a month.
</p
>
2310 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
2311 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
2312 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
2313 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
2314 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
2315 to handle my fairly large DVD collection. It is a nice command line
2316 tool to get details about a DVD, like title, tracks, track length,
2317 etc, in XML, Perl or human readable format. But lsdvd have not seen
2318 any new development since
2006 and had a few irritating bugs affecting
2319 its use with some DVDs. Upstream seemed to be dead, and in January I
2320 sent a small probe asking for a version control repository for the
2321 project, without any reply. But I use it regularly and would like to
2322 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
2323 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
2324 the project admin, and after getting a reply from him explaining that
2325 he was no longer interested in the project, I asked if I could take
2326 over. And yesterday, I became project admin.
</p
>
2328 <p
>I
've been in touch with a Gentoo developer and the Debian
2329 maintainer interested in joining forces to maintain the upstream
2330 project, and I hope we can get a new release out fairly quickly,
2331 collecting the patches spread around on the internet into on place.
2332 I
've added the relevant Debian patches to the freshly created git
2333 repository, and expect the Gentoo patches to make it too. If you got
2334 a DVD collection and care about command line tools, check out
2335 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
2336 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
2337 list
</a
>. :)
</p
>
2342 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
2343 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
2344 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
2345 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
2346 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
2347 a lot quicker. When we install more than
2000 packages in
2348 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
2349 tasksel in the installer, unpacking the binary packages take forever.
2350 A part of the slow I/O issue was discussed in
2351 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
2352 much file system sync-ing done by dpkg, which is the package
2353 responsible for unpacking the binary packages. Other parts (like code
2354 executed by postinst scripts) might also sync to disk during
2355 installation. All this sync-ing to disk do not really make sense to
2356 me. If the machine crash half-way through, I start over, I do not try
2357 to salvage the half installed system. So the failure sync-ing is
2358 supposed to protect against, hardware or system crash, is not really
2359 relevant while the installer is running.
</p
>
2361 <p
>A few days ago, I thought of a way to get rid of all the file
2362 system sync()-ing in a fairly non-intrusive way, without the need to
2363 change the code in several packages. The idea is not new, but I have
2364 not heard anyone propose the approach using dpkg-divert before. It
2365 depend on the small and clever package
2366 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
2367 uses LD_PRELOAD to replace the system functions for syncing data to
2368 disk with functions doing nothing, thus allowing programs to live
2369 dangerous while speeding up disk I/O significantly. Instead of
2370 modifying the implementation of dpkg, apt and tasksel (which are the
2371 packages responsible for selecting, fetching and installing packages),
2372 it occurred to me that we could just divert the programs away, replace
2373 them with a simple shell wrapper calling
2374 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
2375 Two days ago I decided to test the idea, and wrapped up a simple
2376 implementation for the Debian Edu udeb.
</p
>
2378 <p
>The effect was stunning. In my first test it reduced the running
2379 time of the pkgsel step (installing tasks) from
64 to less than
44
2380 minutes (
20 minutes shaved off the installation) on an old Dell
2381 Latitude D505 machine. I am not quite sure what the optimised time
2382 would have been, as I messed up the testing a bit, causing the debconf
2383 priority to get low enough for two questions to pop up during
2384 installation. As soon as I saw the questions I moved the installation
2385 along, but do not know how long the question were holding up the
2386 installation. I did some more measurements using Debian Edu Jessie,
2387 and got these results. The time measured is the time stamp in
2388 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
2389 "pkgsel: finishing up
" lines, if you want to do the same measurement
2390 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2391 timing thus do not depend on how quickly the user handle the tasksel
2394 <p
><table
>
2397 <th
>Machine/setup
</th
>
2398 <th
>Original tasksel
</th
>
2399 <th
>Optimised tasksel
</th
>
2400 <th
>Reduction
</th
>
2404 <td
>Latitude D505 Main+LTSP LXDE
</td
>
2405 <td
>64 min (
07:
46-
08:
50)
</td
>
2406 <td
><44 min (
11:
27-
12:
11)
</td
>
2407 <td
>>20 min
18%
</td
>
2411 <td
>Latitude D505 Roaming LXDE
</td
>
2412 <td
>57 min (
08:
48-
09:
45)
</td
>
2413 <td
>34 min (
07:
43-
08:
17)
</td
>
2414 <td
>23 min
40%
</td
>
2418 <td
>Latitude D505 Minimal
</td
>
2419 <td
>22 min (
10:
37-
10:
59)
</td
>
2420 <td
>11 min (
11:
16-
11:
27)
</td
>
2421 <td
>11 min
50%
</td
>
2425 <td
>Thinkpad X200 Minimal
</td
>
2426 <td
>6 min (
08:
19-
08:
25)
</td
>
2427 <td
>4 min (
08:
04-
08:
08)
</td
>
2428 <td
>2 min
33%
</td
>
2432 <td
>Thinkpad X200 Roaming KDE
</td
>
2433 <td
>19 min (
09:
21-
09:
40)
</td
>
2434 <td
>15 min (
10:
25-
10:
40)
</td
>
2435 <td
>4 min
21%
</td
>
2438 </table
></p
>
2440 <p
>The test is done using a netinst ISO on a USB stick, so some of the
2441 time is spent downloading packages. The connection to the Internet
2442 was
100Mbit/s during testing, so downloading should not be a
2443 significant factor in the measurement. Download typically took a few
2444 seconds to a few minutes, depending on the amount of packages being
2445 installed.
</p
>
2447 <p
>The speedup is implemented by using two hooks in
2448 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
2449 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
2450 finish-install.d hook to remove the divert at the end of the
2451 installation. I picked the pre-pkgsel.d hook instead of the
2452 post-base-installer.d hook because I test using an ISO without the
2453 eatmydata package included, and the post-base-installer.d hook in
2454 Debian Edu can only operate on packages included in the ISO. The
2455 negative effect of this is that I am unable to activate this
2456 optimization for the kernel installation step in d-i. If the code is
2457 moved to the post-base-installer.d hook, the speedup would be larger
2458 for the entire installation.
</p
>
2460 <p
>I
've implemented this in the
2461 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
2462 git repository, and plan to provide the optimization as part of the
2463 Debian Edu installation. If you want to test this yourself, you can
2464 create two files in the installer (or in an udeb). One shell script
2465 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
2467 <p
><blockquote
><pre
>
2470 . /usr/share/debconf/confmodule
2472 logger -t my-pkgsel
"info: $*
"
2475 logger -t my-pkgsel
"error: $*
"
2477 override_install() {
2478 apt-install eatmydata || true
2479 if [ -x /target/usr/bin/eatmydata ] ; then
2480 for bin in dpkg apt-get aptitude tasksel ; do
2482 # Test that the file exist and have not been diverted already.
2483 if [ -f /target$file ] ; then
2484 info
"diverting $file using eatmydata
"
2485 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
2486 > /target$file.edu
2487 chmod
755 /target$file.edu
2488 in-target dpkg-divert --package debian-edu-config \
2489 --rename --quiet --add $file
2490 ln -sf ./$bin.edu /target$file
2492 error
"unable to divert $file, as it is missing.
"
2496 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
2501 </pre
></blockquote
></p
>
2503 <p
>To clean up, another shell script should go into
2504 /usr/lib/finish-install.d/ with code like this:
2506 <p
><blockquote
><pre
>
2508 . /usr/share/debconf/confmodule
2510 logger -t my-finish-install
"error: $@
"
2512 remove_install_override() {
2513 for bin in dpkg apt-get aptitude tasksel ; do
2515 if [ -x /target$file.edu ] ; then
2517 in-target dpkg-divert --package debian-edu-config \
2518 --rename --quiet --remove $file
2521 error
"Missing divert for $file.
"
2524 sync # Flush file buffers before continuing
2527 remove_install_override
2528 </pre
></blockquote
></p
>
2530 <p
>In Debian Edu, I placed both code fragments in a separate script
2531 edu-eatmydata-install and call it from the pre-pkgsel.d and
2532 finish-install.d scripts.
</p
>
2534 <p
>By now you might ask if this change should get into the normal
2535 Debian installer too? I suspect it should, but am not sure the
2536 current debian-installer coordinators find it useful enough. It also
2537 depend on the side effects of the change. I
'm not aware of any, but I
2538 guess we will see if the change is safe after some more testing.
2539 Perhaps there is some package in Debian depending on sync() and
2540 fsync() having effect? Perhaps it should go into its own udeb, to
2541 allow those of us wanting to enable it to do so without affecting
2544 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
2545 will break installation of all programs using gnutls because of
2546 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
2547 eatmydata package in Debian will solve it.
</p
>
2549 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
2550 the optimization work again. And I have discovered that the
2551 dpkg-divert trick is not really needed and implemented a slightly
2552 simpler approach as part of the debian-edu-install package. See
2553 tools/edu-eatmydata-install in the source package.
</p
>
2555 <p
>Update
2014-
11-
11: Unfortunately, a new
2556 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
2557 triggering on i386 made it into testing, and broke this installation
2558 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
2559 request
768893</a
> is accepted, it should be working again.
</p
>
2564 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
2565 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
2566 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
2567 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
2568 <description><p
>Yesterday, I had the pleasure of attending a talk with the
2569 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
2570 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
2571 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
2572 learn that there is a large set of publicly available key servers to
2573 use when looking for peoples public key. So far I have used
2574 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2575 were misbehaving, but those days are ended. The servers I have used
2576 up until yesterday have been slow and some times unavailable. I hope
2577 those problems are gone now.
</p
>
2579 <p
>Behind the round robin DNS entry of the
2580 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
2581 there is a pool of more than
100 keyservers which are checked every
2582 day to ensure they are well connected and up to date. It must be
2583 better than what I have used so far. :)
</p
>
2585 <p
>Yesterdays speaker told me that the service is the default
2586 keyserver provided by the default configuration in GnuPG, but this do
2587 not seem to be used in Debian. Perhaps it should?
</p
>
2589 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
2592 <p
><blockquote
><pre
>
2593 keyserver pool.sks-keyservers.net
2594 </pre
></blockquote
></p
>
2596 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
2597 entries in DNS. Just for fun, I did just that at work, so now every
2598 user of GnuPG at the University of Oslo should find a OpenGPG
2599 keyserver automatically should their need it:
</p
>
2601 <p
><blockquote
><pre
>
2602 % host -t srv _pgpkey-http._tcp.uio.no
2603 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
2605 </pre
></blockquote
></p
>
2607 <p
>Now if only
2608 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
2609 HKP lookup protocol
</a
> supported finding signature paths, I would be
2610 very happy. It can look up a given key or search for a user ID, but I
2611 normally do not want that, but to find a trust path from my key to
2612 another key. Given a user ID or key ID, I would like to find (and
2613 download) the keys representing a signature path from my key to the
2614 key in question, to be able to get a trust path between the two keys.
2615 This is as far as I can tell not possible today. Perhaps something
2616 for a future version of the protocol?
</p
>
2621 <title>From English wiki to translated PDF and epub via Docbook
</title>
2622 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
2623 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
2624 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
2625 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2626 project
</a
> provide an instruction manual for teachers, system
2627 administrators and other users that contain useful tips for setting up
2628 and maintaining a Debian Edu installation. This text is about how the
2629 text processing of this manual is handled in the project.
</p
>
2631 <p
>One goal of the project is to provide information in the native
2632 language of its users, and for this we need to handle translations.
2633 But we also want to make sure each language contain the same
2634 information, so for this we need a good way to keep the translations
2635 in sync. And we want it to be easy for our users to improve the
2636 documentation, avoiding the need to learn special formats or tools to
2637 contribute, and the obvious way to do this is to make it possible to
2638 edit the documentation using a web browser. We also want it to be
2639 easy for translators to keep the translation up to date, and give them
2640 help in figuring out what need to be translated. Here is the list of
2641 tools and the process we have found trying to reach all these
2644 <p
>We maintain the authoritative source of our manual in the
2645 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
2646 wiki
</a
>, as several wiki pages written in English. It consist of one
2647 front page with references to the different chapters, several pages
2648 for each chapter, and finally one
"collection page
" gluing all the
2649 chapters together into one large web page (aka
2650 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
2651 AllInOne page
</a
>). The AllInOne page is the one used for further
2652 processing and translations. Thanks to the fact that the
2653 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
2654 wiki.debian.org support exporting pages in
2655 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
2656 the list of pages to export using the raw version of the AllInOne
2657 page, loop over each of them to generate a Docbook XML version of the
2658 manual. This process also download images and transform image
2659 references to use the locally downloaded images. The generated
2660 Docbook XML files are slightly broken, so some post-processing is done
2661 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
2662 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2663 a handfull of images. The XML file can now be used to generate PDF, HTML
2664 and epub versions of the English manual. This is the basic step of
2665 our process, making PDF (using dblatex), HTML (using xsltproc) and
2666 epub (using dbtoepub) version from Docbook XML, and the resulting files
2667 are placed in the debian-edu-doc-en binary package.
</p
>
2669 <p
>But English documentation is not enough for us. We want translated
2670 documentation too, and we want to make it easy for translators to
2671 track the English original. For this we use the
2672 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
2673 which allow us to transform the English Docbook XML file into a
2674 translation file (a .pot file), usable with the normal gettext based
2675 translation tools used by those translating free software. The pot
2676 file is used to create and maintain translation files (several .po
2677 files), which the translations update with the native language
2678 translations of all titles, paragraphs and blocks of text in the
2679 original. The next step is combining the original English Docbook XML
2680 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2681 create a translated Docbook XML file (in this case
2682 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2683 translated, if the translation is not complete) Docbook XML file can
2684 then be used like the original to create a PDF, HTML and epub version
2685 of the documentation.
</p
>
2687 <p
>The translators use different tools to edit the .po files. We
2689 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
2690 while some use emacs and vi, others can use web based editors like
2691 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
2692 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
2693 is where the .po file end up, in our git repository. Updated
2694 translations can either be committed directly to git, or submitted as
2695 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
2696 against the debian-edu-doc package
</a
>.
</p
>
2698 <p
>One challenge is images, which both might need to be translated (if
2699 they show translated user applications), and are needed in different
2700 formats when creating PDF and HTML versions (epub is a HTML version in
2701 this regard). For this we transform the original PNG images to the
2702 needed density and format during build, and have a way to provide
2703 translated images by storing translated versions in
2704 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2705 package maintainers know more.
</p
>
2707 <p
>If you wonder what the result look like, we provide
2708 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
2709 of the documentation packages on the web
</a
>. See for example the
2710 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
2711 PDF version
</a
> or the
2712 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
2713 HTML version
</a
>. We do not yet build the epub version by default,
2714 but perhaps it will be done in the future.
</p
>
2716 <p
>To learn more, check out
2717 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
2718 debian-edu-doc package
</a
>,
2719 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
2720 manual on the wiki
</a
> and
2721 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
2722 translation instructions
</a
> in the manual.
</p
>
2727 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
2728 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
2729 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
2730 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
2731 <description><p
>It would be nice if it was easier in Debian to get all the hardware
2732 related packages relevant for the computer installed automatically.
2733 So I implemented one, using
2734 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
2735 package
</a
>. To use it, install the tasksel and isenkram packages and
2736 run tasksel as user root. You should be presented with a new option,
2737 "Hardware specific packages (autodetected by isenkram)
". When you
2738 select it, tasksel will install the packages isenkram claim is fit for
2739 the current hardware, hot pluggable or not.
<p
>
2741 <p
>The implementation is in two files, one is the tasksel menu entry
2742 description, and the other is the script used to extract the list of
2743 packages to install. The first part is in
2744 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
2747 <p
><blockquote
><pre
>
2750 Description: Hardware specific packages (autodetected by isenkram)
2751 Based on the detected hardware various hardware specific packages are
2753 Test-new-install: mark show
2755 Packages: for-current-hardware
2756 </pre
></blockquote
></p
>
2758 <p
>The second part is in
2759 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
2762 <p
><blockquote
><pre
>
2767 isenkram-autoinstall-firmware -l
2769 </pre
></blockquote
></p
>
2771 <p
>All in all, a very short and simple implementation making it
2772 trivial to install the hardware dependent package we all may want to
2773 have installed on our machines. I
've not been able to find a way to
2774 get tasksel to tell you exactly which packages it plan to install
2775 before doing the installation. So if you are curious or careful,
2776 check the output from the isenkram-* command line tools first.
</p
>
2778 <p
>The information about which packages are handling which hardware is
2779 fetched either from the isenkram package itself in
2780 /usr/share/isenkram/, from git.debian.org or from the APT package
2781 database (using the Modaliases header). The APT package database
2782 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2783 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
2784 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
2785 the python-apt code (bug
2786 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
2787 workaround I was able to get rid of the file descriptor leak and
2788 reduce the memory leak from ~
30 MiB per hardware detection down to
2789 around
2 MiB per hardware detection. It should make the desktop
2790 daemon a lot more useful. The fix is in version
0.7 uploaded to
2791 unstable today.
</p
>
2793 <p
>I believe the current way of mapping hardware to packages in
2794 Isenkram is is a good draft, but in the future I expect isenkram to
2795 use the AppStream data source for this. A proposal for getting proper
2796 AppStream support into Debian is floating around as
2797 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
2798 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
2799 project
</a
> will take place this summer to improve the situation. I
2800 look forward to seeing the result, and welcome patches for isenkram to
2801 start using the information when it is ready.
</p
>
2803 <p
>If you want your package to map to some specific hardware, either
2804 add a
"Xb-Modaliases
" header to your control file like I did in
2805 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
2806 package
</a
> or submit a bug report with the details to the isenkram
2808 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
2809 blog posts tagged isenkram
</a
> for details on the notation. I expect
2810 the information will be migrated to AppStream eventually, but for the
2811 moment I got no better place to store it.
</p
>
2816 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
2817 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
2818 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
2819 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
2820 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2821 project
</a
> is working on providing the software and hardware to make
2822 it easy for non-technical people to host their data and communication
2823 at home, and being able to communicate with their friends and family
2824 encrypted and away from prying eyes. It is still going strong, and
2825 today a major mile stone was reached.
</p
>
2827 <p
>Today, the last of the packages currently used by the project to
2828 created the system images were accepted into Debian Unstable. It was
2829 the freedombox-setup package, which is used to configure the images
2830 during build and on the first boot. Now all one need to get going is
2831 the build code from the freedom-maker git repository and packages from
2832 Debian. And once the freedombox-setup package enter testing, we can
2833 build everything directly from Debian. :)
</p
>
2835 <p
>Some key packages used by Freedombox are
2836 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
2837 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
2838 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
2839 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
2840 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
2841 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
2842 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
2843 are plans to integrate more packages into the setup. User
2844 documentation is maintained on the Debian wiki. Please
2845 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
2846 the manual
</a
> and help us improve it.
</p
>
2848 <p
>To test for yourself and create boot images with the FreedomBox
2849 setup, run this on a Debian machine using a user with sudo rights to
2850 become root:
</p
>
2852 <p
><pre
>
2853 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2854 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2856 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2858 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2859 </pre
></p
>
2861 <p
>Root access is needed to run debootstrap and mount loopback
2862 devices. See the README in the freedom-maker git repo for more
2863 details on the build. If you do not want all three images, trim the
2864 make line. Note that the virtualbox-image target is not really
2865 virtualbox specific. It create a x86 image usable in kvm, qemu,
2866 vmware and any other x86 virtual machine environment. You might need
2867 the version of vmdebootstrap in Jessie to get the build working, as it
2868 include fixes for a race condition with kpartx.
</p
>
2870 <p
>If you instead want to install using a Debian CD and the preseed
2871 method, boot a Debian Wheezy ISO and use this boot argument to load
2872 the preseed values:
</p
>
2874 <p
><pre
>
2875 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2876 </pre
></p
>
2878 <p
>I have not tested it myself the last few weeks, so I do not know if
2879 it still work.
</p
>
2881 <p
>If you wonder how to help, one task you could look at is using
2882 systemd as the boot system. It will become the default for Linux in
2883 Jessie, so we need to make sure it is usable on the Freedombox. I did
2884 a simple test a few weeks ago, and noticed dnsmasq failed to start
2885 during boot when using systemd. I suspect there are other problems
2886 too. :) To detect problems, there is a test suite included, which can
2887 be run from the plinth web interface.
</p
>
2889 <p
>Give it a go and let us know how it goes on the mailing list, and help
2890 us get the new release published. :) Please join us on
2891 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2892 irc.debian.org)
</a
> and
2893 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2894 mailing list
</a
> if you want to help make this vision come true.
</p
>
2899 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
2900 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
2901 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
2902 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
2903 <description><p
>For a while now, I have been looking for a sensible offsite backup
2904 solution for use at home. My requirements are simple, it must be
2905 cheap and locally encrypted (in other words, I keep the encryption
2906 keys, the storage provider do not have access to my private files).
2907 One idea me and my friends had many years ago, before the cloud
2908 storage providers showed up, was to use Google mail as storage,
2909 writing a Linux block device storing blocks as emails in the mail
2910 service provided by Google, and thus get heaps of free space. On top
2911 of this one can add encryption, RAID and volume management to have
2912 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2913 I never found time to implement such system. But the last few weeks I
2914 have looked at a system called
2915 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
2916 mounted network backed file system with the features I need.
</p
>
2918 <p
>S3QL is a fuse file system with a local cache and cloud storage,
2919 handling several different storage providers, any with Amazon S3,
2920 Google Drive or OpenStack API. There are heaps of such storage
2921 providers. S3QL can also use a local directory as storage, which
2922 combined with sshfs allow for file storage on any ssh server. S3QL
2923 include support for encryption, compression, de-duplication, snapshots
2924 and immutable file systems, allowing me to mount the remote storage as
2925 a local mount point, look at and use the files as if they were local,
2926 while the content is stored in the cloud as well. This allow me to
2927 have a backup that should survive fire. The file system can not be
2928 shared between several machines at the same time, as only one can
2929 mount it at the time, but any machine with the encryption key and
2930 access to the storage service can mount it if it is unmounted.
</p
>
2932 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
2933 package is included already. So to get started, run
<tt
>apt-get
2934 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
2935 Greenqloud, after reading their nice recipe on
2936 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
2937 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
2938 in Iceland more than those in USA when it come to keeping my personal
2939 data safe and private, and thus would rather spend money on a company
2940 in Iceland. Another nice recipe is available from the article
2941 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
2942 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
2943 Admin magazine. When the provider is picked, figure out how to get
2944 the API key needed to connect to the storage API. With Greencloud,
2945 the key did not show up until I had added payment details to my
2948 <p
>Armed with the API access details, it is time to create the file
2949 system. First, create a new bucket in the cloud. This bucket is the
2950 file system storage area. I picked a bucket name reflecting the
2951 machine that was going to store data there, but any name will do.
2952 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
2953 the API login and password, and a locally created password. Store it
2954 all in ~root/.s3ql/authinfo2 like this:
2956 <p
><blockquote
><pre
>
2958 storage-url: s3c://s.greenqloud.com:
443/bucket-name
2959 backend-login: API-login
2960 backend-password: API-password
2961 fs-passphrase: local-password
2962 </pre
></blockquote
></p
>
2964 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
2965 but any sensible way to create a fairly random password should do it.
2966 Armed with these details, it is now time to run mkfs, entering the API
2967 details and password to create it:
</p
>
2969 <p
><blockquote
><pre
>
2970 # mkdir -m
700 /var/lib/s3ql-cache
2971 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2972 --ssl s3c://s.greenqloud.com:
443/bucket-name
2973 Enter backend login:
2974 Enter backend password:
2975 Before using S3QL, make sure to read the user
's guide, especially
2976 the
'Important Rules to Avoid Loosing Data
' section.
2977 Enter encryption password:
2978 Confirm encryption password:
2979 Generating random encryption key...
2980 Creating metadata tables...
2990 Compressing and uploading metadata...
2991 Wrote
0.00 MB of compressed metadata.
2992 #
</pre
></blockquote
></p
>
2994 <p
>The next step is mounting the file system to make the storage available.
2996 <p
><blockquote
><pre
>
2997 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2998 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2999 Using
4 upload threads.
3000 Downloading and decompressing metadata...
3010 Mounting filesystem...
3012 Filesystem Size Used Avail Use% Mounted on
3013 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3015 </pre
></blockquote
></p
>
3017 <p
>The file system is now ready for use. I use rsync to store my
3018 backups in it, and as the metadata used by rsync is downloaded at
3019 mount time, no network traffic (and storage cost) is triggered by
3020 running rsync. To unmount, one should not use the normal umount
3021 command, as this will not flush the cache to the cloud storage, but
3022 instead running the umount.s3ql command like this:
3024 <p
><blockquote
><pre
>
3027 </pre
></blockquote
></p
>
3029 <p
>There is a fsck command available to check the file system and
3030 correct any problems detected. This can be used if the local server
3031 crashes while the file system is mounted, to reset the
"already
3032 mounted
" flag. This is what it look like when processing a working
3033 file system:
</p
>
3035 <p
><blockquote
><pre
>
3036 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3037 Using cached metadata.
3038 File system seems clean, checking anyway.
3039 Checking DB integrity...
3040 Creating temporary extra indices...
3041 Checking lost+found...
3042 Checking cached objects...
3043 Checking names (refcounts)...
3044 Checking contents (names)...
3045 Checking contents (inodes)...
3046 Checking contents (parent inodes)...
3047 Checking objects (reference counts)...
3048 Checking objects (backend)...
3049 ..processed
5000 objects so far..
3050 ..processed
10000 objects so far..
3051 ..processed
15000 objects so far..
3052 Checking objects (sizes)...
3053 Checking blocks (referenced objects)...
3054 Checking blocks (refcounts)...
3055 Checking inode-block mapping (blocks)...
3056 Checking inode-block mapping (inodes)...
3057 Checking inodes (refcounts)...
3058 Checking inodes (sizes)...
3059 Checking extended attributes (names)...
3060 Checking extended attributes (inodes)...
3061 Checking symlinks (inodes)...
3062 Checking directory reachability...
3063 Checking unix conventions...
3064 Checking referential integrity...
3065 Dropping temporary indices...
3066 Backing up old metadata...
3076 Compressing and uploading metadata...
3077 Wrote
0.89 MB of compressed metadata.
3079 </pre
></blockquote
></p
>
3081 <p
>Thanks to the cache, working on files that fit in the cache is very
3082 quick, about the same speed as local file access. Uploading large
3083 amount of data is to me limited by the bandwidth out of and into my
3084 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3085 which is very close to my upload speed, and downloading the same
3086 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3087 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3088 network, not the file system code. I do not know what a good cache
3089 size would be, but suspect that the cache should e larger than your
3090 working set.
</p
>
3092 <p
>I mentioned that only one machine can mount the file system at the
3093 time. If another machine try, it is told that the file system is
3096 <p
><blockquote
><pre
>
3097 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3098 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3099 Using
8 upload threads.
3100 Backend reports that fs is still mounted elsewhere, aborting.
3102 </pre
></blockquote
></p
>
3104 <p
>The file content is uploaded when the cache is full, while the
3105 metadata is uploaded once every
24 hour by default. To ensure the
3106 file system content is flushed to the cloud, one can either umount the
3107 file system, or ask S3QL to flush the cache and metadata using
3110 <p
><blockquote
><pre
>
3111 # s3qlctrl upload-meta /s3ql
3112 # s3qlctrl flushcache /s3ql
3114 </pre
></blockquote
></p
>
3116 <p
>If you are curious about how much space your data uses in the
3117 cloud, and how much compression and deduplication cut down on the
3118 storage usage, you can use s3qlstat on the mounted file system to get
3121 <p
><blockquote
><pre
>
3123 Directory entries:
9141
3126 Total data size:
22049.38 MB
3127 After de-duplication:
21955.46 MB (
99.57% of total)
3128 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
3129 Database size:
2.39 MB (uncompressed)
3130 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3132 </pre
></blockquote
></p
>
3134 <p
>I mentioned earlier that there are several possible suppliers of
3135 storage. I did not try to locate them all, but am aware of at least
3136 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
3137 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
3138 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
3139 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
3140 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
3141 accept payment in Bitcoin. Pick one that suit your need. Some of
3142 them provide several GiB of free storage, but the prize models are
3143 quite different and you will have to figure out what suits you
3146 <p
>While researching this blog post, I had a look at research papers
3147 and posters discussing the S3QL file system. There are several, which
3148 told me that the file system is getting a critical check by the
3149 science community and increased my confidence in using it. One nice
3151 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3152 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3153 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3154 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3155 and Pamela Smith. Please have a look.
</p
>
3157 <p
>Given my problems with different file systems earlier, I decided to
3158 check out the mounted S3QL file system to see if it would be usable as
3159 a home directory (in other word, that it provided POSIX semantics when
3160 it come to locking and umask handling etc). Running
3161 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3162 test code to check file system semantics
</a
>, I was happy to discover that
3163 no error was found. So the file system can be used for home
3164 directories, if one chooses to do so.
</p
>
3166 <p
>If you do not want a locally file system, and want something that
3167 work without the Linux fuse file system, I would like to mention the
3168 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3169 provide locally encrypted backup using a command line client. It have
3170 a nicer access control system, where one can split out read and write
3171 access, allowing some systems to write to the backup and others to
3172 only read from it.
</p
>
3174 <p
>As usual, if you use Bitcoin and want to show your support of my
3175 activities, please send Bitcoin donations to my address
3176 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3181 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3182 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3183 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3184 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3185 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3186 project
</a
> is working on providing the software and hardware for
3187 making it easy for non-technical people to host their data and
3188 communication at home, and being able to communicate with their
3189 friends and family encrypted and away from prying eyes. It has been
3190 going on for a while, and is slowly progressing towards a new test
3191 release (
0.2).
</p
>
3193 <p
>And what day could be better than the Pi day to announce that the
3194 new version will provide
"hard drive
" / SD card / USB stick images for
3195 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3196 system), and can also be installed using a Debian installer preseed
3197 file. The Debian based Freedombox is now based on Debian Jessie,
3198 where most of the needed packages used are already present. Only one,
3199 the freedombox-setup package, is missing. To try to build your own
3200 boot image to test the current status, fetch the freedom-maker scripts
3202 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
3203 with a user with sudo access to become root:
3206 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3208 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3209 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3211 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3214 <p
>Root access is needed to run debootstrap and mount loopback
3215 devices. See the README for more details on the build. If you do not
3216 want all three images, trim the make line. But note that thanks to
<a
3217 href=
"https://bugs.debian.org/
741407">a race condition in
3218 vmdebootstrap
</a
>, the build might fail without the patch to the
3219 kpartx call.
</p
>
3221 <p
>If you instead want to install using a Debian CD and the preseed
3222 method, boot a Debian Wheezy ISO and use this boot argument to load
3223 the preseed values:
</p
>
3226 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3229 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
3230 recently introduced bug in apt in Jessie
</a
>, the installer will
3231 currently hang while setting up APT sources. Killing the
3232 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
3233 installation will get the installation going. This affect all
3234 installations in Jessie, and I expect it will be fixed soon.
</p
>
3236 <p
>Give it a go and let us know how it goes on the mailing list, and help
3237 us get the new release published. :) Please join us on
3238 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3239 irc.debian.org)
</a
> and
3240 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3241 mailing list
</a
> if you want to help make this vision come true.
</p
>
3246 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
3247 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
3248 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
3249 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
3250 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
3251 innetgr tools, because I needed them in
3252 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
3253 ng-utils, and it has served me well. I placed the project under the
3254 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
3255 repository. But many years ago, the CVS repository was dropped (lost,
3256 not migrated to new hardware, not sure), and the project have lacked a
3257 proper home since then.
</p
>
3259 <p
>Last summer, I had a look at the package and made a new release
3260 fixing a irritating crash bug, but was unable to store the changes in
3261 a proper source control system. I applied for a project on
3262 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
3263 to follow up on it. Until today. :)
</p
>
3265 <p
>After many hours of cleaning and migration, the ng-utils project
3266 now have a new home, and a git repository with the highlight of the
3267 history of the project. I published all release tarballs and imported
3268 them into the git repository. As the project is really stable and not
3269 expected to gain new features any time soon, I decided to make a new
3270 release and call it
1.0. Visit the new project home on
3271 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
3272 if you want to check it out. The new version is also uploaded into
3273 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
3278 <title>Testing sysvinit from experimental in Debian Hurd
</title>
3279 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
3280 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
3281 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
3282 <description><p
>A few days ago I decided to try to help the Hurd people to get
3283 their changes into sysvinit, to allow them to use the normal sysvinit
3284 boot system instead of their old one. This follow up on the
3285 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
3286 Google Summer of Code work
</a
> done last summer by Justus Winter to
3287 get Debian on Hurd working more like Debian on Linux. To get started,
3288 I downloaded a prebuilt hard disk image from
3289 <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
>,
3290 and started it using virt-manager.
</p
>
3292 <p
>The first think I had to do after logging in (root without any
3293 password) was to get the network operational. I followed
3294 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
3295 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
3296 commands as root to get the machine to accept a IP address from the
3297 kvm internal DHCP server:
</p
>
3299 <p
><blockquote
><pre
>
3300 settrans -fgap /dev/netdde /hurd/netdde
3301 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
3302 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
3304 </pre
></blockquote
></p
>
3306 <p
>After this, the machine had internet connectivity, and I could
3307 upgrade it and install the sysvinit packages from experimental and
3308 enable it as the default boot system in Hurd.
</p
>
3310 <p
>But before I did that, I set a password on the root user, as ssh is
3311 running on the machine it for ssh login to work a password need to be
3312 set. Also, note that a bug somewhere in openssh on Hurd block
3313 compression from working. Remember to turn that off on the client
3316 <p
>Run these commands as root to upgrade and test the new sysvinit
3319 <p
><blockquote
><pre
>
3320 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
3321 deb http://http.debian.net/debian/ experimental main
3324 apt-get dist-upgrade
3325 apt-get install -t experimental initscripts sysv-rc sysvinit \
3326 sysvinit-core sysvinit-utils
3327 update-alternatives --config runsystem
3328 </pre
></blockquote
></p
>
3330 <p
>To reboot after switching boot system, you have to use
3331 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
3332 yet a sysvinit process able to receive the signals from the normal
3333 'reboot
' command. After switching to sysvinit as the boot system,
3334 upgrading every package and rebooting, the network come up with DHCP
3335 after boot as it should, and the settrans/pkill hack mentioned at the
3336 start is no longer needed. But for some strange reason, there are no
3337 longer any login prompt in the virtual console, so I logged in using
3340 <p
>Note that there are some race conditions in Hurd making the boot
3341 fail some times. No idea what the cause is, but hope the Hurd porters
3342 figure it out. At least Justus said on IRC (#debian-hurd on
3343 irc.debian.org) that they are aware of the problem. A way to reduce
3344 the impact is to upgrade to the Hurd packages built by Justus by
3345 adding this repository to the machine:
</p
>
3347 <p
><blockquote
><pre
>
3348 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
3349 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3351 </pre
></blockquote
></p
>
3353 <p
>At the moment the prebuilt virtual machine get some packages from
3354 http://ftp.debian-ports.org/debian, because some of the packages in
3355 unstable do not yet include the required patches that are lingering in
3356 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
3358 <p
><blockquote
><pre
>
3359 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
3360 i emacs - GNU Emacs editor (metapackage)
3361 i gdb - GNU Debugger
3362 i hurd-recommended - Miscellaneous translators
3363 i isc-dhcp-client - ISC DHCP client
3364 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3365 i libc-bin - Embedded GNU C Library: Binaries
3366 i libc-dev-bin - Embedded GNU C Library: Development binaries
3367 i libc0.3 - Embedded GNU C Library: Shared libraries
3368 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3369 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3370 i multiarch-support - Transitional package to ensure multiarch compatibilit
3371 i A x11-common - X Window System (X.Org) infrastructure
3372 i xorg - X.Org X Window System
3373 i A xserver-xorg - X.Org X server
3374 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3376 </pre
></blockquote
></p
>
3378 <p
>All in all, testing hurd has been an interesting experience. :)
3379 X.org did not work out of the box and I never took the time to follow
3380 the porters instructions to fix it. This time I was interested in the
3381 command line stuff.
<p
>
3386 <title>New chrpath release
0.16</title>
3387 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
3388 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
3389 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
3390 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
3391 find problems in C, C++ and Java code using static source code
3392 analysis. It can detect a lot of different problems, and is very
3393 useful to find memory and locking bugs in the error handling part of
3394 the source. The company behind it provide
3395 <a href=
"https://scan.coverity.com/
">check of free software projects as
3396 a community service
</a
>, and many hundred free software projects are
3397 already checked. A few days ago I decided to have a closer look at
3398 the Coverity system, and discovered that the
3399 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
3400 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
3401 projects I am involved with was already registered. But these are
3402 fairly big, and I would also like to have a small and easy project to
3403 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
3404 checking of the chrpath project
</a
>. It was
3405 added to the checker and discovered seven potential defects. Six of
3406 these were real, mostly resource
"leak
" when the program detected an
3407 error. Nothing serious, as the resources would be released a fraction
3408 of a second later when the program exited because of the error, but it
3409 is nice to do it right in case the source of the program some time in
3410 the future end up in a library. Having fixed all defects and added
3411 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
3412 mailing list for the chrpath developers
</a
>, I decided it was time to
3413 publish a new release. These are the release notes:
</p
>
3415 <p
>New in
0.16 released
2014-
01-
14:
</p
>
3419 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
3420 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
3421 <li
>Mention new project mailing list in the documentation.
</li
>
3426 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3427 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
3428 project if something is wrong with the new release. The test suite
3429 did not discover any old errors, so if you find a new one, please also
3430 include a test suite check.
</p
>
3435 <title>New chrpath release
0.15</title>
3436 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
3437 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
3438 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
3439 <description><p
>After many years break from the package and a vain hope that
3440 development would be continued by someone else, I finally pulled my
3441 acts together this morning and wrapped up a new release of chrpath,
3442 the command line tool to modify the rpath and runpath of already
3443 compiled ELF programs. The update was triggered by the persistence of
3444 Isha Vishnoi at IBM, which needed a new config.guess file to get
3445 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
3446 is working on. I checked the
3447 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
3448 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
3449 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
3450 packages for interesting patches (failed to find the source from
3451 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3452 These are the release notes:
</p
>
3454 <p
>New in
0.15 released
2013-
11-
24:
</p
>
3458 <li
>Updated config.sub and config.guess from the GNU project to work
3459 with newer architectures. Thanks to isha vishnoi for the heads
3462 <li
>Updated README with current URLs.
</li
>
3464 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3465 Matthias Klose.
</li
>
3467 <li
>Added missing help for -k|--keepgoing option, using patch by
3468 Petr Machata found in Fedora.
</li
>
3470 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
3471 .dynamic is a NULL terminated string. Based on patch found in
3472 Fedora credited Axel Thimm and Christian Krause.
</li
>
3477 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3478 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
3479 project if something is wrong with the new release. The test suite
3480 did not discover any old errors, so if you find a new one, please also
3481 include a testsuite check.
</p
>
3486 <title>Debian init.d boot script example for rsyslog
</title>
3487 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
3488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
3489 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
3490 <description><p
>If one of the points of switching to a new init system in Debian is
3491 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
3492 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
3493 init.d scripts at all. Here is an example init.d script, ie a rewrite
3494 of /etc/init.d/rsyslog:
</p
>
3496 <p
><pre
>
3497 #!/lib/init/init-d-script
3500 # Required-Start: $remote_fs $time
3501 # Required-Stop: umountnfs $time
3502 # X-Stop-After: sendsigs
3503 # Default-Start:
2 3 4 5
3504 # Default-Stop:
0 1 6
3505 # Short-Description: enhanced syslogd
3506 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3507 # It is quite compatible to stock sysklogd and can be
3508 # used as a drop-in replacement.
3510 DESC=
"enhanced syslogd
"
3511 DAEMON=/usr/sbin/rsyslogd
3512 </pre
></p
>
3514 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
3515 script was
137 lines, and the above is just
15 lines, most of it meta
3516 info/comments.
</p
>
3518 <p
>How to do this, you ask? Well, one create a new script
3519 /lib/init/init-d-script looking something like this:
3521 <p
><pre
>
3524 # Define LSB log_* functions.
3525 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
3526 # and status_of_proc is working.
3527 . /lib/lsb/init-functions
3530 # Function that starts the daemon/service
3536 #
0 if daemon has been started
3537 #
1 if daemon was already running
3538 #
2 if daemon could not be started
3539 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
3541 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3544 # Add code here, if necessary, that waits for the process to be ready
3545 # to handle requests from services started subsequently which depend
3546 # on this one. As a last resort, sleep for some time.
3550 # Function that stops the daemon/service
3555 #
0 if daemon has been stopped
3556 #
1 if daemon was already stopped
3557 #
2 if daemon could not be stopped
3558 # other if a failure occurred
3559 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
3560 RETVAL=
"$?
"
3561 [
"$RETVAL
" =
2 ]
&& return
2
3562 # Wait for children to finish too if this is a daemon that forks
3563 # and if the daemon is only ever run from this initscript.
3564 # If the above conditions are not satisfied then add some other code
3565 # that waits for the process to drop all resources that could be
3566 # needed by services started subsequently. A last resort is to
3567 # sleep for some time.
3568 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
3569 [
"$?
" =
2 ]
&& return
2
3570 # Many daemons don
't delete their pidfiles when they exit.
3572 return
"$RETVAL
"
3576 # Function that sends a SIGHUP to the daemon/service
3580 # If the daemon can reload its configuration without
3581 # restarting (for example, when it is sent a SIGHUP),
3582 # then implement that here.
3584 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
3589 scriptbasename=
"$(basename $
1)
"
3590 echo
"SN: $scriptbasename
"
3591 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
3592 script=
"$
1"
3599 NAME=$(basename $DAEMON)
3600 PIDFILE=/var/run/$NAME.pid
3602 # Exit if the package is not installed
3603 #[ -x
"$DAEMON
" ] || exit
0
3605 # Read configuration variable file if it is present
3606 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
3608 # Load the VERBOSE setting and other rcS variables
3611 case
"$
1" in
3613 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
3615 case
"$?
" in
3616 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3617 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3621 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
3623 case
"$?
" in
3624 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3625 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3629 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
3631 #reload|force-reload)
3633 # If do_reload() is not implemented then leave this commented out
3634 # and leave
'force-reload
' as an alias for
'restart
'.
3636 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
3640 restart|force-reload)
3642 # If the
"reload
" option is implemented then remove the
3643 #
'force-reload
' alias
3645 log_daemon_msg
"Restarting $DESC
" "$NAME
"
3647 case
"$?
" in
3650 case
"$?
" in
3652 1) log_end_msg
1 ;; # Old process is still running
3653 *) log_end_msg
1 ;; # Failed to start
3663 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
3669 </pre
></p
>
3671 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
3672 lot. I did not really polish the approach, so it might not always
3673 work out of the box, but you get the idea. I did not try very hard to
3674 optimize it nor make it more robust either.
</p
>
3676 <p
>A better argument for switching init system in Debian than reducing
3677 the size of init scripts (which is a good thing to do anyway), is to
3678 get boot system that is able to handle the kernel events sensibly and
3679 robustly, and do not depend on the boot to run sequentially. The boot
3680 and the kernel have not behaved sequentially in years.
</p
>
3685 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
3686 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
3687 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
3688 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
3689 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
3690 remote display access is the preferred solution with oVirt and RedHat
3691 Enterprise Virtualization, and I was sad to discover the other day
3692 that the browser plugin needed to use these systems seamlessly was
3693 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
3694 for a package
</a
> was from
2012-
04-
10 with no progress since
3695 2013-
04-
01, so I decided to wrap up a package based on the great work
3696 from Cajus Pollmeier and put it in a collab-maint maintained git
3697 repository to get a package I could use. I would very much like
3698 others to help me maintain the package (or just take over, I do not
3699 mind), but as no-one had volunteered so far, I just uploaded it to
3700 NEW. I hope it will be available in Debian in a few days.
</p
>
3702 <p
>The source is now available from
3703 <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
>
3708 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
3709 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
3710 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
3711 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
3712 <description><p
>The
3713 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
3714 program is a a very nice system to create virtual machine images. It
3715 create a image file, add a partition table, mount it and run
3716 debootstrap in the mounted directory to create a Debian system on a
3717 stick. Yesterday, I decided to try to teach it how to make images for
3718 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
3719 of a plan to simplify the build system for
3720 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
3721 project
</a
>. The FreedomBox project already uses vmdebootstrap for
3722 the virtualbox images, but its current build system made multistrap
3723 based system for Dreamplug images, and it is lacking support for
3724 Raspberry Pi.
</p
>
3726 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
3727 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3728 code and adjusted it to be able to build armel images on my amd64
3729 Debian laptop. I ended up giving vmdebootstrap five new options,
3730 allowing me to replicate the image creation process I use to make
3731 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
3732 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
3733 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
3734 call debootstrap with --foreign and to copy the handler into the
3735 generated chroot before running the second stage. This allow
3736 vmdebootstrap to create armel images on an amd64 host. Next I added
3737 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
3738 fstype
</tt
> to teach it to create a separate /boot/ partition with the
3739 given file system type, allowing me to create an image with a vfat
3740 partition for the /boot/ stuff. I also added a
<tt
>--variant
3741 variant
</tt
> option to allow me to create smaller images without the
3742 Debian base system packages installed. Finally, I added an option
3743 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
3744 as a boot loader. It is not needed on the Raspberry Pi and probably
3745 most other non-x86 architectures. The changes were accepted by the
3746 upstream author of vmdebootstrap yesterday and today, and is now
3748 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
3749 upstream project page
</a
>.
</p
>
3751 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
3752 create a small script (the customize script) to add the non-free
3753 binary blob needed to boot the Raspberry Pi and the APT source
3756 <p
><pre
>
3758 set -e # Exit on first error
3759 rootdir=
"$
1"
3760 cd
"$rootdir
"
3761 cat
&lt;
&lt;EOF
> etc/apt/sources.list
3762 deb http://http.debian.net/debian/ jessie main contrib non-free
3764 # Install non-free binary blob needed to boot Raspberry Pi. This
3765 # install a kernel somewhere too.
3766 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3767 -O $rootdir/usr/bin/rpi-update
3768 chmod a+x $rootdir/usr/bin/rpi-update
3769 mkdir -p $rootdir/lib/modules
3770 touch $rootdir/boot/start.elf
3771 chroot $rootdir rpi-update
3772 </pre
></p
>
3774 <p
>Next, fetch the latest vmdebootstrap script and call it like this
3775 to build the image:
</p
>
3778 sudo ./vmdebootstrap \
3781 --distribution jessie \
3782 --mirror http://http.debian.net/debian \
3791 --root-password raspberry \
3792 --hostname raspberrypi \
3793 --foreign /usr/bin/qemu-arm-static \
3794 --customize `pwd`/customize \
3796 --package git-core \
3797 --package binutils \
3798 --package ca-certificates \
3801 </pre
></p
>
3803 <p
>The list of packages being installed are the ones needed by
3804 rpi-update to make the image bootable on the Raspberry Pi, with the
3805 exception of netbase, which is needed by debootstrap to find
3806 /etc/hosts with the minbase variant. I really wish there was a way to
3807 set up an Raspberry Pi using only packages in the Debian archive, but
3808 that is not possible as far as I know, because it boots from the GPU
3809 using a non-free binary blob.
</p
>
3811 <p
>The build host need debootstrap, kpartx and qemu-user-static and
3812 probably a few others installed. I have not checked the complete
3813 build dependency list.
</p
>
3815 <p
>The resulting image will not use the hardware floating point unit
3816 on the Raspberry PI, because the armel architecture in Debian is not
3817 optimized for that use. So the images created will be a bit slower
3818 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
3823 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
3824 <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>
3825 <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>
3826 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
3827 <description><p
>The last few days I came across a few good causes that should get
3828 wider attention. I recommend signing and donating to each one of
3831 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
3832 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
3833 Women program which is a Google Summer of Code like initiative to get
3834 more women involved in free software. One debian sponsor has offered
3835 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
3836 earmarked
</a
> for this initiative. I donated a few minutes ago, and
3837 hope you will to. :)
</p
>
3839 <p
>And the Electronic Frontier Foundation just announced plans to
3840 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
3841 documentaries about the excessive spying
</a
> on every Internet user that
3842 take place these days, and their need to fund the work. I
've already
3843 donated. Are you next?
</p
>
3845 <p
>For my Norwegian audience, the organisation Studentenes og
3846 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3847 statement under the heading
3848 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
3849 Access
</a
> for those of us asking for more focus on open access in the
3850 Norwegian government. So far
499 signatures. I hope you will sign it
3856 <title>Videos about the Freedombox project - for inspiration and learning
</title>
3857 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
3858 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
3859 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
3860 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
3861 project
</a
> have been going on for a while, and have presented the
3862 vision, ideas and solution several places. Here is a little
3863 collection of videos of talks and presentation of the project.
</p
>
3867 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
3868 2,
5 minute marketing film
</a
> (Youtube)
</li
>
3870 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
3871 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
3873 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
3874 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3875 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
3876 (Youtube)
</li
>
3878 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
3879 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
3881 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
3882 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
3884 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
3885 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3886 York City in
2012</a
> (Youtube)
</li
>
3888 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
3889 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
3890 (Youtube)
</li
>
3892 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
3893 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
3895 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
3896 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
3898 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
3899 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3900 2013</a
> (Youtube)
</li
>
3904 <p
>A larger list is available from
3905 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
3906 Freedombox Wiki
</a
>.
</p
>
3908 <p
>On other news, I am happy to report that Freedombox based on Debian
3909 Jessie is coming along quite well, and soon both Owncloud and using
3910 Tor should be available for testers of the Freedombox solution. :) In
3911 a few weeks I hope everything needed to test it is included in Debian.
3912 The withsqlite package is already in Debian, and the plinth package is
3913 pending in NEW. The third and vital part of that puzzle is the
3914 metapackage/setup framework, which is still pending an upload. Join
3915 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
3916 (#freedombox on irc.debian.org)
</a
> and
3917 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3918 mailing list
</a
> if you want to help make this vision come true.
</p
>
3923 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
3924 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
3925 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
3926 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
3927 <description><p
>I was introduced to the
3928 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
3929 in
2010, when Eben Moglen presented his vision about serving the need
3930 of non-technical people to keep their personal information private and
3931 within the legal protection of their own homes. The idea is to give
3932 people back the power over their network and machines, and return
3933 Internet back to its intended peer-to-peer architecture. Instead of
3934 depending on a central service, the Freedombox will give everyone
3935 control over their own basic infrastructure.
</p
>
3937 <p
>I
've intended to join the effort since then, but other tasks have
3938 taken priority. But this summers nasty news about the misuse of trust
3939 and privilege exercised by the
"western
" intelligence gathering
3940 communities increased my eagerness to contribute to a point where I
3941 actually started working on the project a while back.
</p
>
3943 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
3944 Debian initiative
</a
> based on the vision from Eben Moglen, is to
3945 create a simple and cheap Debian based appliance that anyone can hook
3946 up in their home and get access to secure and private services and
3947 communication. The initial deployment platform have been the
3948 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
3949 which is a piece of hardware I do not own. So to be able to test what
3950 the current Freedombox setup look like, I had to come up with a way to install
3951 it on some hardware I do have access to. I have rewritten the
3952 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
3953 image build framework to use .deb packages instead of only copying
3954 setup into the boot images, and thanks to this rewrite I am able to
3955 set up any machine supported by Debian Wheezy as a Freedombox, using
3956 the previously mentioned deb (and a few support debs for packages
3957 missing in Debian).
</p
>
3959 <p
>The current Freedombox setup consist of a set of bootstrapping
3961 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
3962 and a administrative web interface
3963 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
3964 withsqlite), as well as a privacy enhancing proxy based on
3965 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
3966 (freedombox-privoxy). There is also a web/javascript based XMPP
3967 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
3968 trying (unsuccessfully so far) to talk to the XMPP server
3969 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
3970 web interface is pluggable, and the goal is to use it to enable OpenID
3971 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3972 this is really working yet, see
3973 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
3974 project TODO
</a
> for links to GIT repositories. Most of the code is
3975 on github at the moment. The HTTP proxy is operational out of the
3976 box, and the admin web interface can be used to add/remove plinth
3977 users. I
've not been able to do anything else with it so far, but
3978 know there are several branches spread around github and other places
3979 with lots of half baked features.
</p
>
3981 <p
>Anyway, if you want to have a look at the current state, the
3982 following recipes should work to give you a test machine to poke
3985 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
3989 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
3990 <li
>Boot from it, either as CD or USB stick.
</li
>
3991 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
3992 to the Debian installer:
<p
>
3993 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
3995 <li
>Answer the few language/region/password questions and pick disk to
3996 install on.
</li
>
3998 <li
>When the installation is finished and the machine have rebooted a
3999 few times, your Freedombox is ready for testing.
</li
>
4003 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4007 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4008 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4009 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4011 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4012 </pre
></li
>
4013 <li
><p
>Run this as root:
</p
>
4015 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4018 apt-get install freedombox-setup
4019 /usr/lib/freedombox/setup
4020 </pre
></li
>
4021 <li
>Reboot into your freshly created Freedombox.
</li
>
4025 <p
>You can test it on other architectures too, but because the
4026 freedombox-privoxy package is binary, it will only work as intended on
4027 the architectures where I have had time to build the binary and put it
4028 in my APT repository. But do not let this stop you. It is only a
4029 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4031 <p
>Note that by default Freedombox is a DHCP server on the
4032 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4033 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4034 disable
</tt
>" as root.
</p
>
4036 <p
>Please let me know if this works for you, or if you have any
4037 problems. We gather on the IRC channel
4038 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4039 irc.debian.org and the
4040 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4041 mailing list
</a
>.
</p
>
4043 <p
>Once you get your freedombox operational, you can visit
4044 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4045 welcome screen (dead end - do not be surprised if you are unable to
4046 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4047 to look at the rest of plinth. The default user is
'admin
' and the
4048 default password is
'secret
'.
</p
>
4053 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4054 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4055 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4056 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4057 <description><p
>Earlier, I reported about
4058 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4059 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4060 told by IBM that the original disk should be thrown away. And as
4061 there no longer was a problem if I bricked the firmware, I decided
4062 today to try to install Intel firmware to replace the Lenovo firmware
4063 currently on the disk.
</p
>
4065 <p
>I searched the Intel site for firmware, and found
4066 <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
>
4067 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4068 according to the site should contain the latest firmware for SSD
4069 disks. I inserted the broken disk in one of my spare laptops and
4070 booted the ISO from a USB stick. The disk was recognized, but the
4071 program claimed the newest firmware already were installed and refused
4072 to insert any Intel firmware. So no change, and the disk is still
4073 unable to handle write load. :( I guess the only way to get them
4074 working would be if Lenovo releases new firmware. No idea how likely
4075 that is. Anyway, just blogging about this test for completeness. I
4076 got a working Samsung disk, and see no point in spending more time on
4077 the broken disks.
</p
>
4082 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4083 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4084 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4085 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4086 <description><p
>Today I switched to
4087 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4088 new laptop
</a
>. I
've previously written about the problems I had with
4089 my new Thinkpad X230, which was delivered with an
4090 <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
4091 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4092 sustained writes. My hardware supplier have been very forthcoming in
4093 trying to find a solution, and after first trying with another
4094 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
4095 disk instead to fix it once and for all. The Samsung disk survived
4096 the installation of Debian with encrypted disks (filling the disk with
4097 random data during installation killed the first two), and I thus
4098 decided to trust it with my data. I have installed it as a Debian Edu
4099 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4100 server at home using Kerberos and LDAP, and will use it as my work
4101 station from now on.
</p
>
4103 <p
>As this is a solid state disk with no moving parts, I believe the
4104 Debian Wheezy default installation need to be tuned a bit to increase
4105 performance and increase life time of the disk. The Linux kernel and
4106 user space applications do not yet adjust automatically to such
4107 environment. To make it easier for my self, I created a draft Debian
4108 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
4109 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
4110 for the ssd-setup package
</a
> is available from collab-maint, and it
4111 is set up to adjust the setup of the machine by just installing the
4112 package. If there is any non-SSD disk in the machine, the package
4113 will refuse to install, as I did not try to write any logic to sort
4114 file systems in SSD and non-SSD file systems.
</p
>
4116 <p
>I consider the package a draft, as I am a bit unsure how to best
4117 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4118 where I set up the machine with one large encrypted partition (in
4119 addition to /boot), put LVM on top of this and set up partitions on
4120 top of this again. See the README file in the package source for the
4121 references I used to pick the settings. At the moment these
4122 parameters are tuned:
</p
>
4126 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4127 (adding discard to /etc/crypttab)
</li
>
4129 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
4130 this case a cryptsetup partition) by changing issue_discards from
4131 0 to
1 in /etc/lvm/lvm.conf.
</li
>
4133 <li
>Set relatime as a file system option for ext3 and ext4 file
4136 <li
>Tell swap to use TRIM commands by adding
'discard
' to
4137 /etc/fstab.
</li
>
4139 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
4141 <li
>Run fstrim on every ext3 and ext4 file system every night (from
4142 cron.daily).
</li
>
4144 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
4145 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4149 <p
>During installation, I cancelled the part where the installer fill
4150 the disk with random data, as this would kill the SSD performance for
4151 little gain. My goal with the encrypted file system is to ensure
4152 those stealing my laptop end up with a brick and not a working
4153 computer. I have no hope in keeping the really resourceful people
4154 from getting the data on the disk (see
4155 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4156 Thus I concluded that adding the discard option to crypttab is the
4157 right thing to do.
</p
>
4159 <p
>I considered using the noop I/O scheduler, as several recommended
4160 it for SSD, but others recommended deadline and a benchmark I found
4161 indicated that deadline might be better for interactive use.
</p
>
4163 <p
>I also considered using the
'discard
' file system option for ext3
4164 and ext4, but read that it would give a performance hit ever time a
4165 file is removed, and thought it best to that that slowdown once a day
4166 instead of during my work.
</p
>
4168 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4169 this is already done by Debian Edu.
</p
>
4171 <p
>I have not yet started on the user space tuning. I expect
4172 iceweasel need some tuning, and perhaps other applications too, but
4173 have not yet had time to investigate those parts.
</p
>
4175 <p
>The package should work on Ubuntu too, but I have not yet tested it
4178 <p
>As for the answer to the question in the title of this blog post,
4179 as far as I know, the only solution I know about is to replace the
4180 disk. It might be possible to flash it with Intel firmware instead of
4181 the Lenovo firmware. But I have not tried and did not want to do so
4182 without approval from Lenovo as I wanted to keep the warranty on the
4183 disk until a solution was found and they wanted the broken disks
4189 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4190 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4191 <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>
4192 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
4193 <description><p
>A few days ago, I wrote about
4194 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
4195 problems I experienced with my new X230 and its SSD disk
</a
>, which
4196 was dying during installation because it is unable to cope with
4197 sustained write. My supplier is in contact with
4198 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
4199 replacement disk to try to fix the problem. They decided to send an
4200 identical model, so my hopes for a permanent fix was slim.
</p
>
4202 <p
>Anyway, today I got the replacement disk and tried to install
4203 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4204 same firmware version as the original. This time my hope raised
4205 slightly as the installation progressed, as the original disk used to
4206 die after
4-
7% of the disk was written to, while this time it kept
4207 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
4208 died again and I was back on square one. I still do not have a new
4209 laptop with a disk I can trust. I can not live with a disk that might
4210 lock up when I download a new
4211 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
4212 other large files. I look forward to hearing from my supplier with
4213 the next proposal from Lenovo.
</p
>
4215 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
4216 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4217 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4218 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
4219 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4220 P/N
45N8295, P0C38732.
</p
>
4222 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
4223 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
4224 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4225 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
4226 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4227 P/N
45N8295, P0C38732.
</p
>
4229 <p
>The only difference is in the first number (serial number?), ISN,
4230 SA, date and WNPP values. Mentioning all the details here in case
4231 someone is able to use the information to find a way to identify the
4232 failing disk among working ones (if any such working disk actually
4238 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
4239 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
4240 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
4241 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
4242 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
4243 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4244 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
4245 member assosiation NUUG
</a
> and
4246 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
4247 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
4248 Bitraf
</a
>.
</p
>
4250 <p
>It starts
10:
00 and continue until late evening. Everyone is
4251 welcome, and there is no fee to participate. There is on the other
4252 hand limited space, and only room for
30 people. Please put your name
4253 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
4254 wiki page
</a
> if you plan to join us.
</p
>
4259 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
4260 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
4261 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
4262 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
4263 <description><p
>Half a year ago, I reported that I had to find a
4264 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
4265 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
4266 time to spend on it, and it took a while to find a model I believe
4267 will do the job, but two days ago the replacement finally arrived. I
4269 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
4270 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4271 a roaming workstation, and it seemed to work flawlessly. But my
4272 second installation with encrypted disk was not as successful. More
4273 on that below.
</p
>
4275 <p
>I had a hard time trying to track down a good laptop, as my most
4276 important requirements (robust and with a good keyboard) are never
4277 listed in the feature list. But I did get good help from the search
4278 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4279 allowed me to limit the list of interesting laptops based on my other
4280 requirements. A bit surprising that SSD disk are not disks according
4281 to that search interface, so I had to drop specifying the number of
4282 disks from my search parameters. I also asked around among friends to
4283 get their impression on keyboards and robustness.
</p
>
4285 <p
>So the new laptop arrived, and it is quite a lot wider than the
4286 X41. I am not quite convinced about the keyboard, as it is
4287 significantly wider than my old keyboard, and I have to stretch my
4288 hand a lot more to reach the edges. But the key response is fairly
4289 good and the individual key shape is fairly easy to handle, so I hope
4290 I will get used to it. My old X40 was starting to fail, and I really
4291 needed a new laptop now. :)
</p
>
4293 <p
>Turning off the touch pad was simple. All it took was a quick
4294 visit to the BIOS during boot it disable it.
</p
>
4296 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
4297 lock up during load. And this happen when installing Debian Wheezy
4298 with encrypted disk, while the disk is being filled with random data.
4299 I also tested to install Ubuntu Raring, and it happen there too if I
4300 reenable the code to fill the disk with random data (it is disabled by
4301 default in Ubuntu). And the bug with is already known. It was
4302 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
4303 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
4304 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4305 kernel developers as
4306 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
4307 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
4308 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4309 Lenovo forums, both for
4310 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
4311 2012-
11-
10</a
> and for
4312 <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
4313 03-
20-
2013</a
>. The problem do not only affect installation. The
4314 reports state that the disk lock up during use if many writes are done
4315 on the disk, so it is much no use to work around the installation
4316 problem and end up with a computer that can lock up at any moment.
4318 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
4319 available
</a
> that will lock up the hard drive after running a few
4320 minutes by writing to a file.
</p
>
4322 <p
>I
've contacted my supplier and asked how to handle this, and after
4323 contacting PCHELP Norway (request
01D1FDP) which handle support
4324 requests for Lenovo, his first suggestion was to upgrade the disk
4325 firmware. Unfortunately there is no newer firmware available from
4326 Lenovo, as my disk already have the most recent one (version LF1i). I
4327 hope to hear more from him today and hope the problem can be
4333 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
4334 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
4335 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
4336 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
4337 <description><p
>Half a year ago, I reported that I had to find a replacement for my
4338 trusty old Thinkpad X41. Unfortunately I did not have much time to
4339 spend on it, but today the replacement finally arrived. I ended up
4340 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
4341 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
4342 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4343 this, it is installing what I hope will be a more final installation,
4344 with a encrypted hard drive to ensure any dope head stealing it end up
4345 with an expencive door stop.
</p
>
4347 <p
>I had a hard time trying to track down a good laptop, as my most
4348 important requirements (robust and with a good keyboard) are never
4349 listed in the feature list. But I did get good help from the search
4350 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4351 allowed me to limit the list of interesting laptops based on my other
4352 requirements. A bit surprising that SSD disk are not disks, so I had
4353 to drop number of disks from my search parameters.
</p
>
4355 <p
>I am not quite convinced about the keyboard, as it is significantly
4356 wider than my old keyboard, and I have to stretch my hand a lot more
4357 to reach the edges. But the key response is fairly good and the
4358 individual key shape is fairly easy to handle, so I hope I will get
4359 used to it. My old X40 was starting to fail, and I really needed a
4360 new laptop now. :)
</p
>
4362 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
4367 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
4368 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
4369 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
4370 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
4371 <description><p
>It annoys me when the computer fail to do automatically what it is
4372 perfectly capable of, and I have to do it manually to get things
4373 working. One such task is to find out what firmware packages are
4374 needed to get the hardware on my computer working. Most often this
4375 affect the wifi card, but some times it even affect the RAID
4376 controller or the ethernet card. Today I pushed version
0.4 of the
4377 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
4378 including a new script isenkram-autoinstall-firmware handling the
4379 process of asking all the loaded kernel modules what firmware files
4380 they want, find debian packages providing these files and install the
4381 debian packages. Here is a test run on my laptop:
</p
>
4383 <p
><pre
>
4384 # isenkram-autoinstall-firmware
4385 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4386 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4387 info: locating packages with the requested firmware files
4388 info: Updating APT sources after adding non-free APT source
4389 info: trying to install firmware-ipw2x00
4392 Preconfiguring packages ...
4393 Selecting previously deselected package firmware-ipw2x00.
4394 (Reading database ...
259727 files and directories currently installed.)
4395 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4396 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
4398 </pre
></p
>
4400 <p
>When all the requested firmware is present, a simple message is
4401 printed instead:
</p
>
4403 <p
><pre
>
4404 # isenkram-autoinstall-firmware
4405 info: did not find any firmware files requested by loaded kernel modules. exiting
4407 </pre
></p
>
4409 <p
>It could use some polish, but it is already working well and saving
4410 me some time when setting up new machines. :)
</p
>
4412 <p
>So, how does it work? It look at the set of currently loaded
4413 kernel modules, and look up each one of them using modinfo, to find
4414 the firmware files listed in the module meta-information. Next, it
4415 download the Contents file from a nearby APT mirror, and search for
4416 the firmware files in this file to locate the package with the
4417 requested firmware file. If the package is in the non-free section, a
4418 non-free APT source is added and the package is installed using
4419 <tt
>apt-get install
</tt
>. The end result is a slightly better working
4422 <p
>I hope someone find time to implement a more polished version of
4423 this script as part of the hw-detect debian-installer module, to
4424 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
4425 #
655507</a
>. There really is no need to insert USB sticks with
4426 firmware during a PXE install when the packages already are available
4427 from the nearby Debian mirror.
</p
>
4432 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
4433 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
4434 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
4435 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
4436 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4437 the screen just turn black when Linux boot, either during installation
4438 or on first boot from the hard disk. I
've seen it once in a while the
4439 last few years, but only recently understood the cause. I
've seen it
4440 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4441 The reason seem to be in the wiring of some laptops. The system to
4442 control the screen background light is inverted, so when Linux try to
4443 turn the brightness fully on, it end up turning it off instead. I do
4444 not know which Linux drivers are affected, but this post is about the
4445 i915 driver used by the
4446 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4447 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
4449 <p
>The problem can be worked around two ways. Either by adding
4450 i915.invert_brightness=
1 as a kernel option, or by adding a file in
4451 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
4452 option when it load the i915 kernel module. On Debian and Ubuntu, it
4453 can be done by running these commands as root:
</p
>
4456 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
4457 update-initramfs -u -k all
4460 <p
>Since March
2012 there is
4461 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
4462 mechanism in the Linux kernel
</a
> to tell the i915 driver which
4463 hardware have this problem, and get the driver to invert the
4464 brightness setting automatically. To use it, one need to add a row in
4465 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
4466 intel_quirks array
</a
> in the driver source
4467 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
4468 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
4469 number (vendor number
8086 is assumed) and subdevice vendor and device
4472 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
4473 -vvnn
</tt
> for the video card in question:
</p
>
4475 <p
><pre
>
4476 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
4477 3rd Gen Core processor Graphics Controller [
8086:
0156] \
4478 (rev
09) (prog-if
00 [VGA controller])
4479 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
4480 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4481 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4482 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
4483 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
4485 Interrupt: pin A routed to IRQ
42
4486 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
4487 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
4488 Region
4: I/O ports at
4000 [size=
64]
4489 Expansion ROM at
<unassigned
> [disabled]
4490 Capabilities:
<access denied
>
4491 Kernel driver in use: i915
4492 </pre
></p
>
4494 <p
>The resulting intel_quirks entry would then look like this:
</p
>
4496 <p
><pre
>
4497 struct intel_quirk intel_quirks[] = {
4499 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4500 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
4503 </pre
></p
>
4505 <p
>According to the kernel module instructions (as seen using
4506 <tt
>modinfo i915
</tt
>), information about hardware needing the
4507 invert_brightness flag should be sent to the
4508 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
4509 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
4510 developers. But my email about the laptop sent
2013-
06-
03 have not
4512 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
4513 web archive for the mailing list
</a
>, so I suspect they do not accept
4514 emails from non-subscribers. Because of this, I sent my patch also to
4515 the Debian bug tracking system instead as
4516 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
4517 sure the patch is not lost.
</p
>
4519 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
4520 with this problem working properly with Linux. If you use Gnome, your
4521 worries should be over at this point. But if you use KDE, there is
4522 something in KDE ignoring the invert_brightness setting and turning on
4523 the screen during login. I
've reported it to Debian as
4524 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
4525 have no idea yet how to figure out exactly what subsystem is doing
4526 this. Perhaps you can help? Perhaps you know what the Gnome
4527 developers did to handle this, and this can give a clue to the KDE
4528 developers? Or you know where in KDE the screen brightness is changed
4529 during login? If so, please update the BTS report (or get in touch if
4530 you do not know how to update BTS).
</p
>
4532 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
4533 acpi_backlight=vendor, to disable ACPI backlight support completely,
4534 as the ACPI information on the machine is trash and it is better to
4535 leave it to the intel video driver to control the screen
4536 backlight.
</p
>
4541 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
4542 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
4543 <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>
4544 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
4545 <description><p
>Two days ago, I asked
4546 <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
4547 I could install Linux on a Packard Bell EasyNote LV computer
4548 preinstalled with Windows
8</a
>. I found a solution, but am horrified
4549 with the obstacles put in the way of Linux users on a laptop with UEFI
4550 and Windows
8.
</p
>
4552 <p
>I never found out if the cause of my problems were the use of UEFI
4553 secure booting or fast boot. I suspect fast boot was the problem,
4554 causing the firmware to boot directly from HD without considering any
4555 key presses and alternative devices, but do not know UEFI settings
4556 enough to tell.
</p
>
4558 <p
>There is no way to install Linux on the machine in question without
4559 opening the box and disconnecting the hard drive! This is as far as I
4560 can tell, the only way to get access to the firmware setup menu
4561 without accepting the Windows
8 license agreement. I am told (and
4562 found description on how to) that it is possible to configure the
4563 firmware setup once booted into Windows
8. But as I believe the terms
4564 of that agreement are completely unacceptable, accepting the license
4565 was never an alternative. I do not enter agreements I do not intend
4566 to follow.
</p
>
4568 <p
>I feared I had to return the laptops and ask for a refund, and
4569 waste many hours on this, but luckily there was a way to get it to
4570 work. But I would not recommend it to anyone planning to run Linux on
4571 it, and I have become sceptical to Windows
8 certified laptops. Is
4572 this the way Linux will be forced out of the market place, by making
4573 it close to impossible for
"normal
" users to install Linux without
4574 accepting the Microsoft Windows license terms? Or at least not
4575 without risking to loose the warranty?
</p
>
4577 <p
>I
've updated the
4578 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
4579 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
4580 do not have to struggle as much as I did to get Linux into the
4583 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4584 Michael Tokarev and others for feedback and ideas.
</p
>
4589 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
4590 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
4591 <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>
4592 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
4593 <description><p
>I
've run into quite a problem the last few days. I bought three
4594 new laptops for my parents and a few others. I bought Packard Bell
4595 Easynote LV to run Kubuntu on and use as their home computer. But I
4596 am completely unable to figure out how to install Linux on it. The
4597 computer is preinstalled with Windows
8, and I suspect it uses UEFI
4598 instead of a BIOS to boot.
</p
>
4600 <p
>The problem is that I am unable to get it to PXE boot, and unable
4601 to get it to boot the Linux installer from my USB stick. I have yet
4602 to try the DVD install, and still hope it will work. when I turn on
4603 the computer, there is no information on what buttons to press to get
4604 the normal boot menu. I expect to get some boot menu to select PXE or
4605 USB stick booting. When booting, it first ask for the language to
4606 use, then for some regional settings, and finally if I will accept the
4607 Windows
8 terms of use. As these terms are completely unacceptable to
4608 me, I have no other choice but to turn off the computer and try again
4609 to get it to boot the Linux installer.
</p
>
4611 <p
>I have gathered my findings so far on a Linlap page about the
4612 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4613 EasyNote LV
</a
> model. If you have any idea how to get Linux
4614 installed on this machine, please get in touch or update that wiki
4615 page. If I can
't find a way to install Linux, I will have to return
4616 the laptop to the seller and find another machine for my parents.
</p
>
4618 <p
>I wonder, is this the way Linux will be forced out of the market
4619 using UEFI and
"secure boot
" by making it impossible to install Linux
4620 on new Laptops?
</p
>
4625 <title>How to transform a Debian based system to a Debian Edu installation
</title>
4626 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
4627 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
4628 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
4629 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
4630 an operating system based on Debian intended for use in schools. It
4631 contain a turn-key solution for the computer network provided to
4632 pupils in the primary schools. It provide both the central server,
4633 network boot servers and desktop environments with heaps of
4634 educational software. The project was founded almost
12 years ago,
4635 2001-
07-
02. If you want to support the project, which is in need for
4636 cash to fund developer gatherings and other project related activity,
4637 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
4638 donate some money
</a
>.
4640 <p
>A topic that come up again and again on the Debian Edu mailing
4641 lists and elsewhere, is the question on how to transform a Debian or
4642 Ubuntu installation into a Debian Edu installation. It isn
't very
4643 hard, and last week I wrote a script to replicate the steps done by
4644 the Debian Edu installer.
</p
>
4646 <p
>The script,
4647 <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/
>
4648 in the debian-edu-config package, will go through these six steps and
4649 transform an existing Debian Wheezy or Ubuntu (untested) installation
4650 into a Debian Edu Workstation:
</p
>
4654 <li
>Add skolelinux related APT sources.
</li
>
4655 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
4656 <li
>Install debian-edu-install to load preseeding values and pull in
4657 our configuration.
</li
>
4658 <li
>Preseed debconf database with profile setup in
4659 /etc/debian-edu/config, and run tasksel to install packages
4660 according to the profile specified in the config above,
4661 overriding some of the Debian automation machinery.
</li
>
4662 <li
>Run debian-edu-cfengine-D installation to configure everything
4663 that could not be done using preseeding.
</li
>
4664 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
4668 <p
>There are some steps in the Debian Edu installation that can not be
4669 replicated like this. Disk partitioning and LVM setup, for example.
4670 So this script just assume there is enough disk space to install all
4671 the needed packages.
</p
>
4673 <p
>The script was created to help a Debian Edu student working on
4674 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
4675 Debian Edu client, and using it he can take the existing
4676 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
4677 transform it into a fully functioning Debian Edu Workstation (or
4678 Roaming Workstation, or whatever :).
</p
>
4680 <p
>The default setting in the script is to create a KDE Workstation.
4681 If a LXDE based Roaming workstation is wanted instead, modify the
4682 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
4684 <p
><pre
>
4685 PROFILE=
"Roaming-Workstation
"
4686 DESKTOP=
"lxde
"
4687 </pre
></p
>
4689 <p
>The script could even become useful to set up Debian Edu servers in
4690 the cloud, by starting with a virtual Debian installation at some
4691 virtual hosting service and setting up all the services on first
4697 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
4698 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
4699 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
4700 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
4701 <description><P
>In January,
4702 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
4703 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
4704 channel #debian-lego
</a
>, for those of us in the Debian and Linux
4705 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
4706 marvellous construction system from Denmark. We also created
4707 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
4708 a place to take notes and write down our plans and hopes. And several
4709 people showed up to help. I was very happy to see the effect of my
4710 call. Since the small start, we have a debtags tag
4711 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
4712 tag for LEGO related packages, and now count
10 packages related to
4713 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
4715 <p
><table
>
4716 <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
>
4717 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
4718 <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
>
4719 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
4720 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
4721 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
4722 <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
>
4723 <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
>
4724 <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
>
4725 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
4726 </table
></p
>
4728 <p
>Some of these are available in Wheezy, and all but one are
4729 currently available in Jessie/testing. leocad is so far only
4730 available in experimental.
</p
>
4732 <p
>If you care about LEGO in Debian, please join us on IRC and help
4733 adding the rest of the great free software tools available on Linux
4734 for LEGO designers.
</p
>
4739 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
4740 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
4741 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
4742 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
4743 <description><p
>When I woke up this morning, I was very happy to see that the
4744 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
4745 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
4746 Debian release, and I expect to move my machines at home over to it fairly
4749 <p
>The new debian release contain heaps of new stuff, and one program
4750 in particular make me very happy to see included. The
4751 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
4752 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
4753 included for the first time. Alongside similar programs like
4754 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
4755 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
4756 it allow for visual programming where syntax errors can not happen,
4757 and a friendly programming environment for learning to control the
4758 computer. Scratch will also be included in the next release of Debian
4761 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
4762 Edu/Skolelinux release too. The
4763 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
4764 alpha release
</a
> went out last week, and the next should soon
4770 <title>Isenkram
0.2 finally in the Debian archive
</title>
4771 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
4772 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
4773 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
4774 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
4775 package
</a
> finally made it into the archive, after lingering in NEW
4776 for many months. I uploaded it to the Debian experimental suite
4777 2013-
01-
27, and today it was accepted into the archive.
</p
>
4779 <p
>Isenkram is a system for suggesting to users what packages to
4780 install to work with a pluggable hardware device. The suggestion pop
4781 up when the device is plugged in. For example if a Lego Mindstorm NXT
4782 is inserted, it will suggest to install the program needed to program
4783 the NXT controller. Give it a go, and report bugs and suggestions to
4789 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
4790 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
4791 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
4792 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
4793 <description><p
>My
4794 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
4795 bitcoin related blog post
</a
> mentioned that the new
4796 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
4797 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4798 2013-
01-
19, and have been available in unstable since then. It was
4799 automatically copied to Ubuntu, and is available in their Raring
4800 version too.
</p
>
4802 <p
>But there is a strange problem with the build that block this new
4803 version from being available on the i386 and kfreebsd-i386
4804 architectures. For some strange reason, the autobuilders in Debian
4805 for these architectures fail to run the test suite on these
4806 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
4807 We are so far unable to reproduce it when building it manually, and
4808 no-one have been able to propose a fix. If you got an idea what is
4809 failing, please let us know via the BTS.
</p
>
4811 <p
>One feature that is annoying me with of the bitcoin client, because
4812 I often run low on disk space, is the fact that the client will exit
4813 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
4814 #
696715</a
>). So make sure you have enough disk space when you run
4817 <p
>As usual, if you use bitcoin and want to show your support of my
4818 activities, please send Bitcoin donations to my address
4819 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4824 <title>Welcome to the world, Isenkram!
</title>
4825 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
4826 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
4827 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
4828 <description><p
>Yesterday, I
4829 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
4830 for testers
</a
> for my prototype for making Debian better at handling
4831 pluggable hardware devices, which I
4832 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
4833 out to create
</a
> earlier this month. Several valuable testers showed
4834 up, and caused me to really want to to open up the development to more
4835 people. But before I did this, I want to come up with a sensible name
4836 for this project. Today I finally decided on a new name, and I have
4837 renamed the project from hw-support-handler to this new name. In the
4838 process, I moved the source to git and made it available as a
4839 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
4840 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
4841 To fetch and build the latest version of the source, use
</p
>
4844 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4845 cd isenkram
&& git-buildpackage -us -uc
4848 <p
>I have not yet adjusted all files to use the new name yet. If you
4849 want to hack on the source or improve the package, please go ahead.
4850 But please talk to me first on IRC or via email before you do major
4851 changes, to make sure we do not step on each others toes. :)
</p
>
4853 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
4854 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4855 stuff, in other words. I
've been told it is the Norwegian variant of
4856 the German word eisenkram, for those that are familiar with that
4859 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
4860 instructions, to avoid confusing people with an error from the signing
4863 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
4864 clone argument to avoid the need for authentication.
</p
>
4869 <title>First prototype ready making hardware easier to use in Debian
</title>
4870 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
4871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
4872 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
4873 <description><p
>Early this month I set out to try to
4874 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
4875 the Debian support for pluggable hardware devices
</a
>. Now my
4876 prototype is working, and it is ready for a larger audience. To test
4878 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
4879 from the Debian Edu subversion repository
</a
>, build and install the
4880 package. You might have to log out and in again activate the
4881 autostart script.
</p
>
4883 <p
>The design is simple:
</p
>
4887 <li
>Add desktop entry in /usr/share/autostart/ causing a program
4888 hw-support-handlerd to start when the user log in.
</li
>
4890 <li
>This program listen for kernel events about new hardware (directly
4891 from the kernel like udev does), not using HAL dbus events as I
4892 initially did.
</li
>
4894 <li
>When new hardware is inserted, look up the hardware modalias in
4895 the APT database, a database
4896 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
4897 via HTTP
</a
> and a database available as part of the package.
</li
>
4899 <li
>If a package is mapped to the hardware in question, the package
4900 isn
't installed yet and this is the first time the hardware was
4901 plugged in, show a desktop notification suggesting to install the
4902 package or packages.
</li
>
4904 <li
>If the user click on the
'install package now
' button, ask
4905 aptdaemon via the PackageKit API to install the requrired package.
</li
>
4907 <li
>aptdaemon ask for root password or sudo password, and install the
4908 package while showing progress information in a window.
</li
>
4912 <p
>I still need to come up with a better name for the system. Here
4913 are some screen shots showing the prototype in action. First the
4914 notification, then the password request, and finally the request to
4915 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
4917 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
4918 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
4919 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
4920 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
4921 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
4923 <p
>The prototype still need to be improved with longer timeouts, but
4924 is already useful. The database of hardware to package mappings also
4925 need more work. It is currently compatible with the Ubuntu way of
4926 storing such information in the package control file, but could be
4927 changed to use other formats instead or in addition to the current
4928 method. I
've dropped the use of discover for this mapping, as the
4929 modalias approach is more flexible and easier to use on Linux as long
4930 as the Linux kernel expose its modalias strings directly.
</p
>
4932 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
4933 here is the command required to check out and build the source: Use
4934 '<tt
>svn checkout
4935 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4936 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
4937 devscripts package.
</p
>
4939 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
4940 renamed to Isenkram and the source moved from the Debian Edu
4941 subversion repository to a Debian collab-maint git repository. See
4942 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
4943 instructions
</a
> for details.
</p
>
4948 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
4949 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
4950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
4951 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
4952 <description><p
>This Christmas my trusty old laptop died. It died quietly and
4953 suddenly in bed. With a quiet whimper, it went completely quiet and
4954 black. The power button was no longer able to turn it on. It was a
4955 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4956 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4957 Compaq I had before that. Now I need to find a replacement. To keep
4958 going during Christmas, I moved the one year old SSD disk to my old
4959 X40 where it fitted (only one I had left that could use it), but it is
4960 not a durable solution.
4962 <p
>My laptop needs are fairly modest. This is my wishlist from when I
4963 got a new one more than
10 years ago. It still holds true.:)
</p
>
4967 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
4968 than A4).
</li
>
4969 <li
>Robust, it will be in my backpack every day.
</li
>
4970 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
4971 <li
>Long battery life time. Preferable a week.
</li
>
4972 <li
>Internal WIFI network card.
</li
>
4973 <li
>Internal Twisted Pair network card.
</li
>
4974 <li
>Some USB slots (
2-
3 is plenty)
</li
>
4975 <li
>Good keyboard - similar to the Thinkpad.
</li
>
4976 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
4978 <li
>Hardware supported by Debian Stable, ie the default kernel and
4979 X.org packages.
</li
>
4980 <li
>Quiet, preferably fan free (or at least not using the fan most of
4985 <p
>You will notice that there are no RAM and CPU requirements in the
4986 list. The reason is simply that the specifications on laptops the
4987 last
10-
15 years have been sufficient for my needs, and I have to look
4988 at other features to choose my laptop. But are there still made as
4989 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4990 robust, and Thinkpads seem to be heading in the wrong direction since
4991 Lenovo took over. But I
've been told that X220 and X1 Carbon might
4992 still be useful.
</p
>
4994 <p
>Perhaps I should rethink my needs, and look for a pad with an
4995 external keyboard? I
'll have to check the
4996 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
4997 well-supported laptops, or perhaps just buy one preinstalled from one
4998 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
4999 Pre-loaded site
</a
>.
</p
>
5004 <title>How to find a browser plugin supporting a given MIME type
</title>
5005 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5006 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5007 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5008 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5009 install to get support for a given MIME type. Thanks to
5010 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5011 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5012 Unfortunately, not very many packages provide the needed meta
5013 information, Anyway, here is a small script to look up all browser
5014 plugin packages announcing ther MIME support using this specification:
</p
>
5020 def pkgs_handling_mimetype(mimetype):
5025 version = pkg.candidate
5027 version = pkg.installed
5030 record = version.record
5031 if not record.has_key(
'Npp-MimeType
'):
5033 mime_types = record[
'Npp-MimeType
'].split(
',
')
5034 for t in mime_types:
5035 t = t.rstrip().strip()
5037 thepkgs.append(pkg.name)
5039 mimetype =
"audio/ogg
"
5040 if
1 < len(sys.argv):
5041 mimetype = sys.argv[
1]
5042 print
"Browser plugin packages supporting %s:
" % mimetype
5043 for pkg in pkgs_handling_mimetype(mimetype):
5044 print
" %s
" %pkg
5047 <p
>It can be used like this to look up a given MIME type:
</p
>
5050 % ./apt-find-browserplug-for-mimetype
5051 Browser plugin packages supporting audio/ogg:
5053 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5054 Browser plugin packages supporting application/x-shockwave-flash:
5055 browser-plugin-gnash
5059 <p
>In Ubuntu this mechanism is combined with support in the browser
5060 itself to query for plugins and propose to install the needed
5061 packages. It would be great if Debian supported such feature too. Is
5062 anyone working on adding it?
</p
>
5064 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5065 request for icweasel support for this feature is
5066 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5067 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5068 of manpower and wish for a different design is the reason thus feature
5069 is not yet in iceweasel from Debian.
</p
>
5074 <title>What is the most supported MIME type in Debian?
</title>
5075 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5076 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5077 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5078 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5079 proposal to add AppStream information to the Debian archive
</a
>, is a
5080 proposal to make it possible for a Desktop application to propose to
5081 the user some package to install to gain support for a given MIME
5082 type, font, library etc. that is currently missing. With such
5083 mechanism in place, it would be possible for the desktop to
5084 automatically propose and install leocad if some LDraw file is
5085 downloaded by the browser.
</p
>
5087 <p
>To get some idea about the current content of the archive, I decided
5088 to write a simple program to extract all .desktop files from the
5089 Debian archive and look up the claimed MIME support there. The result
5091 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5092 site
</a
>. Using the collected information, it become possible to
5093 answer the question in the title. Here are the
20 most supported MIME
5094 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5095 The complete list is available from the link above.
</p
>
5097 <p
><strong
>Debian Stable:
</strong
></p
>
5101 ----- -----------------------
5117 18 application/x-ogg
5124 <p
><strong
>Debian Testing:
</strong
></p
>
5128 ----- -----------------------
5144 18 application/x-ogg
5151 <p
><strong
>Debian Unstable:
</strong
></p
>
5155 ----- -----------------------
5172 18 application/x-ogg
5178 <p
>I am told that PackageKit can provide an API to access the kind of
5179 information mentioned in DEP-
11. I have not yet had time to look at
5180 it, but hope the PackageKit people in Debian are on top of these
5183 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5184 discovering a typo in my script.
</p
>
5189 <title>Using modalias info to find packages handling my hardware
</title>
5190 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5191 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5192 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
5193 <description><p
>Yesterday, I wrote about the
5194 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
5195 values provided by the Linux kernel
</a
> following my hope for
5196 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
5197 dongle support in Debian
</a
>. Using this knowledge, I have tested how
5198 modalias values attached to package names can be used to map packages
5199 to hardware. This allow the system to look up and suggest relevant
5200 packages when I plug in some new hardware into my machine, and replace
5201 discover and discover-data as the database used to map hardware to
5204 <p
>I create a modaliases file with entries like the following,
5205 containing package name, kernel module name (if relevant, otherwise
5206 the package name) and globs matching the relevant hardware
5209 <p
><blockquote
>
5210 Package: package-name
5211 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
5212 </blockquote
></p
>
5214 <p
>It is fairly trivial to write code to find the relevant packages
5215 for a given modalias value using this file.
</p
>
5217 <p
>An entry like this would suggest the video and picture application
5218 cheese for many USB web cameras (interface bus class
0E01):
</p
>
5220 <p
><blockquote
>
5222 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
5223 </blockquote
></p
>
5225 <p
>An entry like this would suggest the pcmciautils package when a
5226 CardBus bridge (bus class
0607) PCI device is present:
</p
>
5228 <p
><blockquote
>
5229 Package: pcmciautils
5230 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5231 </blockquote
></p
>
5233 <p
>An entry like this would suggest the package colorhug-client when
5234 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
5236 <p
><blockquote
>
5237 Package: colorhug-client
5238 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
5239 </blockquote
></p
>
5241 <p
>I believe the format is compatible with the format of the Packages
5242 file in the Debian archive. Ubuntu already uses their Packages file
5243 to store their mappings from packages to hardware.
</p
>
5245 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
5246 announce the hardware it support in a way my prototype understand.
5247 This allow those publishing packages in an APT source outside the
5248 Debian archive as well as those backporting packages to make sure the
5249 hardware mapping are included in the package meta information. I
've
5250 tested such header in the pymissile package, and its modalias mapping
5251 is working as it should with my prototype. It even made it to Ubuntu
5254 <p
>To test if it was possible to look up supported hardware using only
5255 the shell tools available in the Debian installer, I wrote a shell
5256 implementation of the lookup code. The idea is to create files for
5257 each modalias and let the shell do the matching. Please check out and
5259 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
5260 shell script. It run without any extra dependencies and fetch the
5261 hardware mappings from the Debian archive and the subversion
5262 repository where I currently work on my prototype.
</p
>
5264 <p
>When I use it on a machine with a yubikey inserted, it suggest to
5265 install yubikey-personalization:
</p
>
5267 <p
><blockquote
>
5268 % ./hw-support-lookup
5269 <br
>yubikey-personalization
5271 </blockquote
></p
>
5273 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5274 propose to install the pcmciautils package:
</p
>
5276 <p
><blockquote
>
5277 % ./hw-support-lookup
5278 <br
>pcmciautils
5280 </blockquote
></p
>
5282 <p
>If you know of any hardware-package mapping that should be added to
5283 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
5284 database
</a
>, please tell me about it.
</p
>
5286 <p
>It could be possible to generate several of the mappings between
5287 packages and hardware. One source would be to look at packages with
5288 kernel modules, ie packages with *.ko files in /lib/modules/, and
5289 extract their modalias information. Another would be to look at
5290 packages with udev rules, ie packages with files in
5291 /lib/udev/rules.d/, and extract their vendor/model information to
5292 generate a modalias matching rule. I have not tested any of these to
5293 see if it work.
</p
>
5295 <p
>If you want to help implementing a system to let us propose what
5296 packages to install when new hardware is plugged into a Debian
5297 machine, please send me an email or talk to me on
5298 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5303 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
5304 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
5305 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
5306 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
5307 <description><p
>While looking into how to look up Debian packages based on hardware
5308 information, to find the packages that support a given piece of
5309 hardware, I refreshed my memory regarding modalias values, and decided
5310 to document the details. Here are my findings so far, also available
5312 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5313 Debian Edu subversion repository
</a
>:
5315 <p
><strong
>Modalias decoded
</strong
></p
>
5317 <p
>This document try to explain what the different types of modalias
5318 values stands for. It is in part based on information from
5319 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
5320 &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;,
5321 &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
5322 &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;.
5324 <p
>The modalias entries for a given Linux machine can be found using
5325 this shell script:
</p
>
5328 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
5331 <p
>The supported modalias globs for a given kernel module can be found
5332 using modinfo:
</p
>
5335 % /sbin/modinfo psmouse | grep alias:
5336 alias: serio:ty05pr*id*ex*
5337 alias: serio:ty01pr*id*ex*
5341 <p
><strong
>PCI subtype
</strong
></p
>
5343 <p
>A typical PCI entry can look like this. This is an Intel Host
5344 Bridge memory controller:
</p
>
5346 <p
><blockquote
>
5347 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5348 </blockquote
></p
>
5350 <p
>This represent these values:
</p
>
5355 sv
00001028 (subvendor)
5356 sd
000001AD (subdevice)
5358 sc
00 (bus subclass)
5362 <p
>The vendor/device values are the same values outputted from
'lspci
5363 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
5364 0600. The
0600 class is a host bridge. Other useful bus values are
5365 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
5367 <p
>Not sure how to figure out the interface value, nor what it
5370 <p
><strong
>USB subtype
</strong
></p
>
5372 <p
>Some typical USB entries can look like this. This is an internal
5373 USB hub in a laptop:
</p
>
5375 <p
><blockquote
>
5376 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5377 </blockquote
></p
>
5379 <p
>Here is the values included in this alias:
</p
>
5382 v
1D6B (device vendor)
5383 p
0001 (device product)
5385 dc
09 (device class)
5386 dsc
00 (device subclass)
5387 dp
00 (device protocol)
5388 ic
09 (interface class)
5389 isc
00 (interface subclass)
5390 ip
00 (interface protocol)
5393 <p
>The
0900 device class/subclass means hub. Some times the relevant
5394 class is in the interface class section. For a simple USB web camera,
5395 these alias entries show up:
</p
>
5397 <p
><blockquote
>
5398 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5399 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5400 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5401 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5402 </blockquote
></p
>
5404 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
5405 camera),
0101 is audio control device and
0102 is audio streaming (aka
5406 microphone). Thus this is a camera with microphone included.
</p
>
5408 <p
><strong
>ACPI subtype
</strong
></p
>
5410 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
5411 receiver in a Thinkpad X40:
</p
>
5413 <p
><blockquote
>
5414 acpi:IBM0071:PNP0511:
5415 </blockquote
></p
>
5417 <p
>The values between the colons are IDs.
</p
>
5419 <p
><strong
>DMI subtype
</strong
></p
>
5421 <p
>The DMI table contain lots of information about the computer case
5422 and model. This is an entry for a IBM Thinkpad X40, fetched from
5423 /sys/devices/virtual/dmi/id/modalias:
</p
>
5425 <p
><blockquote
>
5426 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5427 </blockquote
></p
>
5429 <p
>The values present are
</p
>
5432 bvn IBM (BIOS vendor)
5433 bvr
1UETB
6WW(
1.66) (BIOS version)
5434 bd
06/
15/
2005 (BIOS date)
5435 svn IBM (system vendor)
5436 pn
2371H4G (product name)
5437 pvr ThinkPadX40 (product version)
5438 rvn IBM (board vendor)
5439 rn
2371H4G (board name)
5440 rvr NotAvailable (board version)
5441 cvn IBM (chassis vendor)
5442 ct
10 (chassis type)
5443 cvr NotAvailable (chassis version)
5446 <p
>The chassis type
10 is Notebook. Other interesting values can be
5447 found in the dmidecode source:
</p
>
5451 4 Low Profile Desktop
5464 17 Main Server Chassis
5465 18 Expansion Chassis
5467 20 Bus Expansion Chassis
5468 21 Peripheral Chassis
5470 23 Rack Mount Chassis
5479 <p
>The chassis type values are not always accurately set in the DMI
5480 table. For example my home server is a tower, but the DMI modalias
5481 claim it is a desktop.
</p
>
5483 <p
><strong
>SerIO subtype
</strong
></p
>
5485 <p
>This type is used for PS/
2 mouse plugs. One example is from my
5486 test machine:
</p
>
5488 <p
><blockquote
>
5489 serio:ty01pr00id00ex00
5490 </blockquote
></p
>
5492 <p
>The values present are
</p
>
5501 <p
>This type is supported by the psmouse driver. I am not sure what
5502 the valid values are.
</p
>
5504 <p
><strong
>Other subtypes
</strong
></p
>
5506 <p
>There are heaps of other modalias subtypes according to
5507 file2alias.c. There is the rest of the list from that source: amba,
5508 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5509 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5510 vmbus, x86cpu and zorro. I did not spend time documenting all of
5511 these, as they do not seem relevant for my intended use with mapping
5512 hardware to packages when new stuff is inserted during run time.
</p
>
5514 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
5516 <p
>To check which kernel modules provide support for a given modalias,
5517 one can use the following shell script:
</p
>
5520 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
5521 echo
"$id
" ; \
5522 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
5526 <p
>The output can look like this (only the first few entries as the
5527 list is very long on my test machine):
</p
>
5531 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
5533 FATAL: Module acpi:device: not found.
5535 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
5536 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
5537 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
5538 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5539 acpi:IBM0071:PNP0511:
5540 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
5541 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
5542 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
5546 <p
>If you want to help implementing a system to let us propose what
5547 packages to install when new hardware is plugged into a Debian
5548 machine, please send me an email or talk to me on
5549 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5551 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
5552 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
5553 in /sys/ with space in them.
</p
>
5558 <title>Moved the pymissile Debian packaging to collab-maint
</title>
5559 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
5560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
5561 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
5562 <description><p
>As part of my investigation on how to improve the support in Debian
5563 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5564 Launcher and updated the Debian package
5565 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
5566 sure udev will fix the device permissions when it is plugged in. I
5567 also added a
"Modaliases
" header to test it in the Debian archive and
5568 hopefully make the package be proposed by jockey in Ubuntu when a user
5569 plug in his rocket launcher. In the process I moved the source to a
5570 git repository under collab-maint, to make it easier for any DD to
5571 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
5572 is not very active, but the software still work for me even after five
5573 years of relative silence. The new git repository is not listed in
5574 the uploaded package yet, because I want to test the other changes a
5575 bit more before I upload the new version. If you want to check out
5576 the new version with a .desktop file included, visit the
5577 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
5578 view
</a
> or use
"<tt
>git clone
5579 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
5584 <title>Lets make hardware dongles easier to use in Debian
</title>
5585 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
5586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
5587 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
5588 <description><p
>One thing that annoys me with Debian and Linux distributions in
5589 general, is that there is a great package management system with the
5590 ability to automatically install software packages by downloading them
5591 from the distribution mirrors, but no way to get it to automatically
5592 install the packages I need to use the hardware I plug into my
5593 machine. Even if the package to use it is easily available from the
5594 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5595 suggest to automatically install the python-nxt, nbc and t2n packages
5596 I need to talk to it. When I plug in a Yubikey, it could propose the
5597 yubikey-personalization package. The information required to do this
5598 is available, but no-one have pulled all the pieces together.
</p
>
5600 <p
>Some years ago, I proposed to
5601 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
5602 the discover subsystem to implement this
</a
>. The idea is fairly
5607 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
5608 starting when a user log in.
</li
>
5610 <li
>Set this program up to listen for kernel events emitted when new
5611 hardware is inserted into the computer.
</li
>
5613 <li
>When new hardware is inserted, look up the hardware ID in a
5614 database mapping to packages, and take note of any non-installed
5615 packages.
</li
>
5617 <li
>Show a message to the user proposing to install the discovered
5618 package, and make it easy to install it.
</li
>
5622 <p
>I am not sure what the best way to implement this is, but my
5623 initial idea was to use dbus events to discover new hardware, the
5624 discover database to find packages and
5625 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
5628 <p
>Yesterday, I found time to try to implement this idea, and the
5629 draft package is now checked into
5630 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5631 Debian Edu subversion repository
</a
>. In the process, I updated the
5632 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
5633 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5634 the relevant packages in Debian, and uploaded a new version
5635 2.2013.01.09 to unstable. I also discovered that the current
5636 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
5637 package in Debian no longer discovered any USB devices, because
5638 /proc/bus/usb/devices is no longer present. I ported it to use
5639 libusb as a fall back option to get it working. The fixed package
5640 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
5641 because of the freeze).
</p
>
5643 <p
>With this prototype in place, I can insert my Yubikey, and get this
5644 desktop notification to show up (only once, the first time it is
5645 inserted):
</p
>
5647 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
5649 <p
>For this prototype to be really useful, some way to automatically
5650 install the proposed packages by pressing the
"Please install
5651 program(s)
" button should to be implemented.
</p
>
5653 <p
>If this idea seem useful to you, and you want to help make it
5654 happen, please help me update the discover-data database with mappings
5655 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
5656 list the package you would like to have installed when a given
5657 hardware device is inserted into your computer, and report bugs using
5658 reportbug if it isn
't. Or, if you know of a better way to provide
5659 such mapping, please let me know.
</p
>
5661 <p
>This prototype need more work, and there are several questions that
5662 should be considered before it is ready for production use. Is dbus
5663 the correct way to detect new hardware? At the moment I look for HAL
5664 dbus events on the system bus, because that is the events I could see
5665 on my Debian Squeeze KDE desktop. Are there better events to use?
5666 How should the user be notified? Is the desktop notification
5667 mechanism the best option, or should the background daemon raise a
5668 popup instead? How should packages be installed? When should they
5669 not be installed?
</p
>
5671 <p
>If you want to help getting such feature implemented in Debian,
5672 please send me an email. :)
</p
>
5677 <title>New IRC channel for LEGO designers using Debian
</title>
5678 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
5679 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
5680 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
5681 <description><p
>During Christmas, I have worked a bit on the Debian support for
5682 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
5683 NXT
</a
>. My son and I have played a bit with my NXT set, and I
5684 discovered I had to build all the tools myself because none were
5685 already in Debian Squeeze. If Debian support for LEGO is something
5686 you care about, please join me on the IRC channel
5687 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
5688 irc.debian.org). There is a lot that could be done to improve the
5689 Debian support for LEGO designers. For example both CAD software
5690 and Mindstorm compilers are missing. :)
</p
>
5692 <p
>Update
2012-
01-
03: A
5693 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
5694 including links to Lego related packages is now available.
</p
>
5699 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
5700 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
5701 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
5702 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
5703 <description><p
>Let me start by wishing you all marry Christmas and a happy new
5704 year! I hope next year will prove to be a good year.
</p
>
5706 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
5707 decentralised
"currency
" that allow people to transfer bitcoins
5708 between each other with minimal overhead, is a very interesting
5709 experiment. And as I wrote a few days ago, the bitcoin situation in
5710 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
5711 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
5712 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
5713 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
5714 for one of the ftpmasters to approve the new bitcoin-qt package
5717 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
5718 team in Debian, you can easily test the package in Debian Squeeze
5719 using the following steps to get a set of working packages:
</p
>
5721 <blockquote
><pre
>
5722 git clone git://git.debian.org/git/collab-maint/bitcoin
5724 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5725 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5726 </pre
></blockquote
>
5728 <p
>You might have to install some build dependencies as well. The
5729 list of commands should give you two packages, bitcoind and
5730 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5731 client will download the complete set of bitcoin
"blocks
", which need
5732 around
5.6 GiB of data on my machine at the moment. Make sure your
5733 ~/.bitcoin/ directory have lots of spare room if you want to download
5734 all the blocks. The client will warn if the disk is getting full, so
5735 there is not really a problem if you got too little room, but you will
5736 not be able to get all the features out of the client.
</p
>
5738 <p
>As usual, if you use bitcoin and want to show your support of my
5739 activities, please send Bitcoin donations to my address
5740 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5745 <title>A word on bitcoin support in Debian
</title>
5746 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
5747 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
5748 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
5749 <description><p
>It has been a while since I wrote about
5750 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
5751 peer-to-peer based crypto-currency, and the reason is simply that I
5752 have been busy elsewhere. But two days ago, I started looking at the
5753 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
5754 Debian
</a
> again to try to recover my old bitcoin wallet. The package
5755 is now maintained by a
5756 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
5757 people
</a
>, and the grunt work had already been done by this team. We
5758 owe a huge thank you to all these team members. :)
5759 But I was sad to discover that the bitcoin client is missing in
5760 Wheezy. It is only available in Sid (and an outdated client from
5761 backports). The client had several RC bugs registered in BTS blocking
5762 it from entering testing. To try to help the team and improve the
5763 situation, I spent some time providing patches and triaging the bug
5764 reports. I also had a look at the bitcoin package available from Matt
5766 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
5767 Ubuntu
</a
>, and moved the useful pieces from that version into the
5768 Debian package.
</p
>
5770 <p
>After checking with the main package maintainer Jonas Smedegaard on
5771 IRC, I pushed several patches into the collab-maint git repository to
5772 improve the package. It now contains fixes for the RC issues (not from
5773 me, but fixed by Scott Howard), build rules for a Qt GUI client
5774 package, konqueror support for the bitcoin: URI and bash completion
5775 setup. As I work on Debian Squeeze, I also created
5776 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
5777 patch to backport
</a
> the latest version. Jonas is going to look at
5778 it and try to integrate it into the git repository before uploading a
5779 new version to unstable.
5781 <p
>I would very much like bitcoin to succeed, to get rid of the
5782 centralized control currently exercised in the monetary system. I
5783 find it completely unacceptable that the USA government is collecting
5784 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5785 that the major credit card companies can block legal money
5786 transactions to Wikileaks. But for bitcoin to succeed, more people
5787 need to use bitcoins, and more people need to accept bitcoins when
5788 they sell products and services. Improving the bitcoin support in
5789 Debian is a small step in the right direction, but not enough.
5790 Unfortunately the user experience when browsing the web and wanting to
5791 pay with bitcoin is still not very good. The bitcoin: URI is a step
5792 in the right direction, but need to work in most or every browser in
5793 use. Also the bitcoin-qt client is too heavy to fire up to do a
5794 quick transaction. I believe there are other clients available, but
5795 have not tested them.
</p
>
5798 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
5799 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
5800 I received
20.15 BTC so far on the address I provided in my blog two
5801 years ago, as can be
5802 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
5803 on the blockexplorer service
</a
>. Thank you everyone for your
5804 donation. The blockexplorer service demonstrates quite well that
5805 bitcoin is not quite anonymous and untracked. :) I wonder if the
5806 number of users have gone up since then. If you use bitcoin and want
5807 to show your support of my activity, please send Bitcoin donations to
5808 the same address as last time,
5809 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5814 <title>Git repository for song book for Computer Scientists
</title>
5815 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
5816 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
5817 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
5818 <description><p
>As I
5819 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
5820 this summer
</a
>, I have created a Computer Science song book a few
5821 years ago, and today I finally found time to create a public
5822 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
5823 repository for the project
</a
>.
</p
>
5825 <p
>If you want to help out, please clone the source and submit patches
5826 to the HTML version. To generate the PDF and PostScript version,
5827 please use prince XML, or let me know about a useful free software
5828 processor capable of creating a good looking PDF from the HTML.
</p
>
5830 <p
>Want to sing? You can still find the song book in HTML, PDF and
5831 PostScript formats at
5832 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
5833 Science Songbook
</a
>.
</p
>
5838 <title>Gratulerer med
19-årsdagen, Debian!
</title>
5839 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
5840 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
5841 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
5842 <description><p
>I dag fyller
5843 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
5844 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
5845 si gratulerer med dagen, Debian!
</p
>
5850 <title>Song book for Computer Scientists
</title>
5851 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
5852 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
5853 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
5854 <description><p
>Many years ago, while studying Computer Science at the
5855 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
5856 collecting computer related songs for use at parties. The original
5857 version was written in LaTeX, but a few years ago I got help from
5858 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5859 while keeping the ability to create a nice book in PDF format. I have
5860 not had time to maintain the book for a while now, and guess I should
5861 put it up on some public version control repository where others can
5862 help me extend and update the book. If anyone is volunteering to help
5863 me with this, send me an email. Also let me know if there are songs
5864 missing in my book.
</p
>
5866 <p
>I have not mentioned the book on my blog so far, and it occured to
5867 me today that I really should let all my readers share the joys of
5868 singing out load about programming, computers and computer networks.
5869 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
5870 12</a
> is about to start (and I am not going). Want to sing? Check
5871 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
5872 Computer Science Songbook
</a
>.
5877 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
5878 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
5879 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
5880 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
5881 <description><p
>At work we have heaps of servers. I believe the total count is
5882 around
1000 at the moment. To be able to get help from the vendors
5883 when something go wrong, we want to keep the firmware on the servers
5884 up to date. If the firmware isn
't the latest and greatest, the
5885 vendors typically refuse to start debugging any problems until the
5886 firmware is upgraded. So before every reboot, we want to upgrade the
5887 firmware, and we would really like everyone handling servers at the
5888 university to do this themselves when they plan to reboot a machine.
5889 For that to happen we at the unix server admin group need to provide
5890 the tools to do so.
</p
>
5892 <p
>To make firmware upgrading easier, I am working on a script to
5893 fetch and install the latest firmware for the servers we got. Most of
5894 our hardware are from Dell and HP, so I have focused on these servers
5895 so far. This blog post is about the Dell part.
</P
>
5897 <p
>On the Dell FTP site I was lucky enough to find
5898 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
5899 with firmware information for all
11th generation servers, listing
5900 which firmware should be used on a given model and where on the FTP
5901 site I can find it. Using a simple perl XML parser I can then
5902 download the shell scripts Dell provides to do firmware upgrades from
5903 within Linux and reboot when all the firmware is primed and ready to
5904 be activated on the first reboot.
</p
>
5906 <p
>This is the Dell related fragment of the perl code I am working on.
5907 Are there anyone working on similar tools for firmware upgrading all
5908 servers at a site? Please get in touch and lets share resources.
</p
>
5910 <p
><pre
>
5914 use File::Temp qw(tempdir);
5916 # Install needed RHEL packages if missing
5918 'XML::Simple
' =
> 'perl-XML-Simple
',
5920 for my $module (keys %rhelmodules) {
5921 eval
"use $module;
";
5923 my $pkg = $rhelmodules{$module};
5924 system(
"yum install -y $pkg
");
5925 eval
"use $module;
";
5929 my $errorsto =
'pere@hungry.com
';
5935 sub run_firmware_script {
5936 my ($opts, $script) = @_;
5938 print STDERR
"fail: missing script name\n
";
5941 print STDERR
"Running $script\n\n
";
5943 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
5944 print STDERR
"success: firmware script ran succcessfully\n
";
5946 print STDERR
"fail: firmware script returned error\n
";
5950 sub run_firmware_scripts {
5951 my ($opts, @dirs) = @_;
5952 # Run firmware packages
5953 for my $dir (@dirs) {
5954 print STDERR
"info: Running scripts in $dir\n
";
5955 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
5956 while (my $s = readdir $dh) {
5957 next if $s =~ m/^\.\.?/;
5958 run_firmware_script($opts,
"$dir/$s
");
5966 print STDERR
"info: Downloading $url\n
";
5967 system(
"wget --quiet \
"$url\
"");
5972 my $product = `dmidecode -s system-product-name`;
5975 if ($product =~ m/PowerEdge/) {
5977 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5978 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
5980 my $tmpdir = tempdir(
5984 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
5985 system(
'gunzip Catalog.xml.gz
');
5986 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
5987 # -q is quiet, disabling interactivity and reducing console output
5988 my $fwopts =
"-q
";
5990 for my $url (@paths) {
5991 fetch_dell_fw($url);
5993 run_firmware_scripts($fwopts, $tmpdir);
5995 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5996 print STDERR
"error: Please report to $errorsto.\n
";
6000 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6001 print STDERR
"error: Please report to $errorsto.\n
";
6007 my $url =
"ftp://ftp.us.dell.com/$path
";
6011 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6012 # firmware packages to download from Dell. Only work for Linux
6013 # machines and
11th generation Dell servers.
6014 sub fetch_dell_fw_list {
6015 my $filename = shift;
6017 my $product = `dmidecode -s system-product-name`;
6019 my ($mybrand, $mymodel) = split(/\s+/, $product);
6021 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6023 my $xml = XMLin($filename);
6025 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6026 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6027 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6029 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6030 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6032 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6034 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6036 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6039 for my $component (@{$xml-
>{SoftwareComponent}}) {
6040 my $componenttype = $component-
>{ComponentType}-
>{value};
6042 # Drop application packages, only firmware and BIOS
6043 next if
'APAC
' eq $componenttype;
6045 my $cpath = $component-
>{path};
6046 for my $path (@paths) {
6047 if ($cpath =~ m%/$path$%) {
6048 push(@paths, $cpath);
6056 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6057 it could work on other platforms with some tweaking. Anyone know a
6058 index like Catalog.xml is available from HP for HP servers? At the
6059 moment I maintain a similar list manually and it is quickly getting
6065 <title>How is booting into runlevel
1 different from single user boots?
</title>
6066 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6067 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6068 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6069 <description><p
>Wouter Verhelst have some
6070 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6071 comments and opinions
</a
> on my blog post on
6072 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6073 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6074 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6075 default KDE desktop in Debian
</a
>. I only have time to address one
6076 small piece of his comment now, and though it best to address the
6077 misunderstanding he bring forward:
</p
>
6079 <p
><blockquote
>
6080 Currently, a system admin has four options: [...] boot to a
6081 single-user system (by adding
'single
' to the kernel command line;
6082 this runs rcS and rc1 scripts)
6083 </blockquote
></p
>
6085 <p
>This make me believe Wouter believe booting into single user mode
6086 and booting into runlevel
1 is the same. I am not surprised he
6087 believe this, because it would make sense and is a quite sensible
6088 thing to believe. But because the boot in Debian is slightly broken,
6089 runlevel
1 do not work properly and it isn
't the same as single user
6090 mode. I
'll try to explain what is actually happing, but it is a bit
6091 hard to explain.
</p
>
6093 <p
>Single user mode is defined like this in /etc/inittab:
6094 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
6095 executed in single user mode is sulogin. Single user mode is a boot
6096 state
"between
" the runlevels, and when booting into single user mode,
6097 only the scripts in /etc/rcS.d/ are executed before the init process
6098 enters the single user state. When switching to runlevel
1, the state
6099 is in fact not ending in runlevel
1, but it passes through runlevel
1
6100 and end up in the single user mode (see /etc/rc1.d/S03single, which
6101 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
6102 1. It is confusing that the
'S
' (single user) init mode is not the
6103 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6106 <p
>This summary might make it clearer. When booting for the first
6107 time into single user mode, the following commands are executed:
6108 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
6109 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
6110 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
6111 trying to continue after visiting single user mode. Not all services
6112 are started again as they should, causing the machine to end up in an
6113 unpredicatble state. This is why Debian admins recommend rebooting
6114 after visiting single user mode.
</p
>
6116 <p
>A similar problem with runlevel
1 is caused by the amount of
6117 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
6118 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6119 stopped when passing through the scripts in /etc/rc1.d/, and not
6120 started again when switching away from runlevel
1 to the runlevels
6121 2-
5. I believe the problem is best fixed by moving all the scripts
6122 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6123 functioning single user mode during boot.
</p
>
6125 <p
>I have spent several years investigating the Debian boot system,
6126 and discovered this problem a few years ago. I suspect it originates
6127 from when sysvinit was introduced into Debian, a long time ago.
</p
>
6132 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
6133 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
6134 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
6135 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
6136 <description><p
>In the Debian boot system, several packages include scripts that
6137 are started from /etc/rcS.d/. In fact, there is a bite more of them
6138 than make sense, and this causes a few problems. What kind of
6139 problems, you might ask. There are at least two problems. The first
6140 is that it is not possible to recover a machine after switching to
6141 runlevel
1. One need to actually reboot to get the machine back to
6142 the expected state. The other is that single user boot will sometimes
6143 run into problems because some of the subsystems are activated before
6144 the root login is presented, causing problems when trying to recover a
6145 machine from a problem in that subsystem. A minor additional point is
6146 that moving more scripts out of rcS.d/ and into the other rc#.d/
6147 directories will increase the amount of scripts that can run in
6148 parallel during boot, and thus decrease the boot time.
</p
>
6150 <p
>So, which scripts should start from rcS.d/. In short, only the
6151 scripts that _have_ to execute before the root login prompt is
6152 presented during a single user boot should go there. Everything else
6153 should go into the numeric runlevels. This means things like
6154 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6155 the numeric runlevels. Today in Debian, there are around
115 init.d
6156 scripts that are started from rcS.d/, and most of them should be moved
6157 out. Do your package have one of them? Please help us make single
6158 user and runlevel
1 better by moving it.
</p
>
6160 <p
>Scripts setting up the screen, keyboard, system partitions
6161 etc. should still be started from rcS.d/, but there is for example no
6162 need to have the network enabled before the single user login prompt
6163 is presented.
</p
>
6165 <p
>As always, things are not so easy to fix as they sound. To keep
6166 Debian systems working while scripts migrate and during upgrades, the
6167 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6168 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6169 and the next ones can only be moved when their dependencies have been
6170 moved first. This migration must be done sequentially while we ensure
6171 that the package system upgrade packages in the right order to keep
6172 the system state correct. This will require some coordination when it
6173 comes to network related packages, but most of the packages with
6174 scripts that should migrate do not have anything in rcS.d/ depending
6175 on them. Some packages have already been updated, like the sudo
6176 package, while others are still left to do. I wish I had time to work
6177 on this myself, but real live constrains make it unlikely that I will
6178 find time to push this forward.
</p
>
6183 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6184 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6185 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6186 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6187 <description><p
>While at Debconf11, I have several times during discussions
6188 mentioned the issues I believe should be improved in Debian for its
6189 desktop to be useful for more people. The use case for this is my
6190 parents, which are currently running Kubuntu which solve the
6193 <p
>I suspect these four missing features are not very hard to
6194 implement. After all, they are present in Ubuntu, so if we wanted to
6195 do this in Debian we would have a source.
</p
>
6199 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
6200 are new packages available for upgrades, a icon in the KDE status bar
6201 indicate this, and clicking on it will activate the simple upgrade
6202 tool to handle it. I have no problem guiding both of my parents
6203 through the process over the phone. If a kernel reboot is required,
6204 this too is indicated by the status bars and the upgrade tool. Last
6205 time I checked, nothing with the same features was working in KDE in
6208 <li
><strong
>Simple handling of missing Firefox browser
6209 plugins.
</strong
> When the browser encounter a MIME type it do not
6210 currently have a handler for, it will ask the user if the system
6211 should search for a package that would add support for this MIME type,
6212 and if the user say yes, the APT sources will be searched for packages
6213 advertising the MIME type in their control file (visible in the
6214 Packages file in the APT archive). If one or more packages are found,
6215 it is a simple click of the mouse to add support for the missing mime
6216 type. If the package require the user to accept some non-free
6217 license, this is explained to the user. The entire process make it
6218 more clear to the user why something do not work in the browser, and
6219 make the chances higher for the user to blame the web page authors and
6220 not the browser for any missing features.
</li
>
6222 <li
><strong
>Simple handling of missing multimedia codec/format
6223 handlers.
</strong
> When the media players encounter a format or codec
6224 it is not supporting, a dialog pop up asking the user if the system
6225 should search for a package that would add support for it. This
6226 happen with things like MP3, Windows Media or H
.264. The selection
6227 and installation procedure is very similar to the Firefox browser
6228 plugin handling. This is as far as I know implemented using a
6229 gstreamer hook. The end result is that the user easily get access to
6230 the codecs that are present from the APT archives available, while
6231 explaining more on why a given format is unsupported by Ubuntu.
</li
>
6233 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
6234 displaying a text/plain file in my Debian browser, it will propose to
6235 start emacs to show it. If I remember correctly, when doing the same
6236 in Kunbutu it show the file as a text file in the browser. At least I
6237 know Opera will show text files within the browser. I much prefer the
6238 latter behaviour.
</li
>
6242 <p
>There are other nice features as well, like the simplified suite
6243 upgrader, but given that I am the one mostly doing the dist-upgrade,
6244 it do not matter much.
</p
>
6246 <p
>I really hope we could get these features in place for the next
6247 Debian release. It would require the coordinated effort of several
6248 maintainers, but would make the end user experience a lot better.
</p
>
6253 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
6254 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
6255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
6256 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
6257 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
6258 site is build on Debian/Squeeze, and this platform was chosen because
6259 I am most familiar with Debian (being a Debian Developer for around
10
6260 years) because it is the latest stable Debian release which should get
6261 security support for a few years.
</p
>
6263 <p
>The web service is written in Perl, and depend on some perl modules
6264 that are missing in Debian at the moment. It would be great if these
6265 modules were added to the Debian archive, allowing anyone to set up
6266 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
6267 in their own country using only Debian packages. The list of modules
6268 missing in Debian/Squeeze isn
't very long, and I hope the perl group
6269 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
6270 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6271 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6272 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6273 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6274 easier in the future.
</p
>
6276 <p
>Thanks to the great tools in Debian, getting the missing modules
6277 installed on my server was a simple call to
'cpan2deb Module::Name
'
6278 and
'dpkg -i
' to install the resulting package. But this leave me
6279 with the responsibility of tracking security problems, which I really
6280 do not have time for.
</p
>
6285 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
6286 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
6287 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
6288 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
6289 <description><p
>Here is a small update for my English readers. Most of my blog
6290 posts have been in Norwegian the last few weeks, so here is a short
6291 update in English.
</p
>
6293 <p
>The kids still keep me too busy to get much free software work
6294 done, but I did manage to organise a project to get a Norwegian port
6295 of the British service
6296 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
6297 and it has been running for a month now. The entire project has been
6298 organised by me and two others. Around Christmas we gathered sponsors
6299 to fund the development work. In January I drafted a contract with
6300 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
6301 and in February the development took place. Most of it involved
6302 converting the source to use GPS coordinates instead of British
6303 easting/northing, and the resulting code should be a lot easier to get
6304 running in any country by now. The Norwegian
6305 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
6306 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
6307 source and the source for administrative borders in Norway, and
6308 support for this had to be added/fixed.
</p
>
6310 <p
>The Norwegian version went live March
3th, and we spent the weekend
6311 polishing the system before we announced it March
7th. The system is
6312 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
6313 problem reports in a few weeks. Soon we hope to announce the Android
6314 and iPhone versions making it even easier to report problems with the
6315 public infrastructure.
</p
>
6317 <p
>Perhaps something to consider for those of you in countries without
6318 such service?
</p
>
6323 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
6324 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
6325 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
6326 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
6327 <description><p
>The last few days I have looked at ways to track open security
6328 issues here at my work with the University of Oslo. My idea is that
6329 it should be possible to use the information about security issues
6330 available on the Internet, and check our locally
6331 maintained/distributed software against this information. It should
6332 allow us to verify that no known security issues are forgotten. The
6333 CVE database listing vulnerabilities seem like a great central point,
6334 and by using the package lists from Debian mapped to CVEs provided by
6335 the testing security team, I believed it should be possible to figure
6336 out which security holes were present in our free software
6337 collection.
</p
>
6339 <p
>After reading up on the topic, it became obvious that the first
6340 building block is to be able to name software packages in a unique and
6341 consistent way across data sources. I considered several ways to do
6342 this, for example coming up with my own naming scheme like using URLs
6343 to project home pages or URLs to the Freshmeat entries, or using some
6344 existing naming scheme. And it seem like I am not the first one to
6345 come across this problem, as MITRE already proposed and implemented a
6346 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
6347 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
6348 software, hardware and other platform components. The CPE ids are
6349 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
6350 Vulnerability Database
</a
>, allowing me to look up know security
6351 issues for any CPE name. With this in place, all I need to do is to
6352 locate the CPE id for the software packages we use at the university.
6353 This is fairly trivial (I google for
'cve cpe $package
' and check the
6354 NVD entry if a CVE for the package exist).
</p
>
6356 <p
>To give you an example. The GNU gzip source package have the CPE
6357 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
6358 check out, one could look up
6359 <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
6360 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
6361 The most recent one is
6362 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
6363 and at the bottom of the NVD page for this vulnerability the complete
6364 list of affected versions is provided.
</p
>
6366 <p
>The NVD database of CVEs is also available as a XML dump, allowing
6367 for offline processing of issues. Using this dump, I
've written a
6368 small script taking a list of CPEs as input and list all CVEs
6369 affecting the packages represented by these CPEs. One give it CPEs
6370 with version numbers as specified above and get a list of open
6371 security issues out.
</p
>
6373 <p
>Of course for this approach to be useful, the quality of the NVD
6374 information need to be high. For that to happen, I believe as many as
6375 possible need to use and contribute to the NVD database. I notice
6377 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
6378 map from CVE to CPE
</a
>, indicating that they are using the CPE
6379 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
6381 <p
>To get an idea about the quality for free software, I spent some
6382 time making it possible to compare the CVE database from Debian with
6383 the CVE database in NVD. The result look fairly good, but there are
6384 some inconsistencies in NVD (same software package having several
6385 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6386 Debian believe are affected by a CVE). Hope to find time to improve
6387 the quality of NVD, but that require being able to get in touch with
6388 someone maintaining it. So far my three emails with questions and
6389 corrections have not seen any reply, but I hope contact can be
6390 established soon.
</p
>
6392 <p
>An interesting application for CPEs is cross platform package
6393 mapping. It would be useful to know which packages in for example
6394 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6395 this would be trivial if all linux distributions provided CPE entries
6396 for their packages.
</p
>
6401 <title>Which module is loaded for a given PCI and USB device?
</title>
6402 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
6403 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
6404 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
6405 <description><p
>In the
6406 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
6407 package in Debian, there is a script to report useful information
6408 about the running hardware for use when people report missing
6409 information. One part of this script that I find very useful when
6410 debugging hardware problems, is the part mapping loaded kernel module
6411 to the PCI device it claims. It allow me to quickly see if the kernel
6412 module I expect is driving the hardware I am struggling with. To see
6413 the output, make sure discover-data is installed and run
6414 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
6415 one of my machines like this:
</p
>
6419 10de:
03eb i2c_nforce2
6422 10de:
03f0 snd_hda_intel
6431 <p
>The code in question look like this, slightly modified for
6432 readability and to drop the output to file descriptor
3:
</p
>
6435 if [ -d /sys/bus/pci/devices/ ] ; then
6436 echo loaded pci modules:
6438 cd /sys/bus/pci/devices/
6439 for address in * ; do
6440 if [ -d
"$address/driver/module
" ] ; then
6441 module=`cd $address/driver/module ; pwd -P | xargs basename`
6442 if grep -q
"^$module
" /proc/modules ; then
6443 address=$(echo $address |sed s/
0000://)
6444 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
6445 echo
"$id $module
"
6454 <p
>Similar code could be used to extract USB device module
6458 if [ -d /sys/bus/usb/devices/ ] ; then
6459 echo loaded usb modules:
6461 cd /sys/bus/usb/devices/
6462 for address in * ; do
6463 if [ -d
"$address/driver/module
" ] ; then
6464 module=`cd $address/driver/module ; pwd -P | xargs basename`
6465 if grep -q
"^$module
" /proc/modules ; then
6466 address=$(echo $address |sed s/
0000://)
6467 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
6468 if [
"$id
" ] ; then
6469 echo
"$id $module
"
6479 <p
>This might perhaps be something to include in other tools as
6485 <title>How to test if a laptop is working with Linux
</title>
6486 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
6487 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
6488 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
6489 <description><p
>The last few days I have spent at work here at the
<a
6490 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
6491 batch of computers will work with Linux. Every year for the last few
6492 years the university have organised shared bid of a few thousand
6493 computers, and this year HP won the bid. Two different desktops and
6494 five different laptops are on the list this year. We in the UNIX
6495 group want to know which one of these computers work well with RHEL
6496 and Ubuntu, the two Linux distributions we currently handle at the
6497 university.
</p
>
6499 <p
>My test method is simple, and I share it here to get feedback and
6500 perhaps inspire others to test hardware as well. To test, I PXE
6501 install the OS version of choice, and log in as my normal user and run
6502 a few applications and plug in selected pieces of hardware. When
6503 something fail, I make a note about this in the test matrix and move
6504 on. If I have some spare time I try to report the bug to the OS
6505 vendor, but as I only have the machines for a short time, I rarely
6506 have the time to do this for all the problems I find.
</p
>
6508 <p
>Anyway, to get to the point of this post. Here is the simple tests
6509 I perform on a new model.
</p
>
6513 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
6514 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6515 RHEL5 and Debian Edu/Squeeze.
</li
>
6517 <li
>Is X.org working? If the graphical login screen show up after
6518 installation, X.org is working.
</li
>
6520 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
6521 package mesa-utils on Ubuntu) and writing down the frames per second
6522 reported by the program.
</li
>
6524 <li
>Is sound working? With Gnome and KDE, a sound is played when
6525 logging in, and if I can hear this the test is successful. If there
6526 are several audio exits on the machine, I try them all and check if
6527 the Gnome/KDE audio mixer can control where to send the sound. I
6528 normally test this by playing
6529 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
6530 video
</a
> in Firefox/Iceweasel.
</li
>
6532 <li
>Is the USB subsystem working? I test this by plugging in a USB
6533 memory stick and see if Gnome/KDE notices this.
</li
>
6535 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
6536 I have lying around, and see if Gnome/KDE notices this.
</li
>
6538 <li
>Is any built in camera working? Test using cheese, and see if a
6539 picture from the v4l device show up.
</li
>
6541 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6542 any bluetooth devices are discovered. In my office, I normally see a
6545 <li
>For laptops, is the SD or Compaq Flash reader working. I have
6546 memory modules lying around, and stick them in and see if Gnome/KDE
6547 notice this.
</li
>
6549 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
6550 special button work, and if the laptop continue to work after
6553 <li
>For laptops, is the extra buttons working, like audio level,
6554 adjusting background light, switching on/off external video output,
6555 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6556 laptop to laptop, so I just write down which are working and which are
6559 <li
>Some laptops have smart card readers, finger print readers,
6560 acceleration sensors etc. I rarely test these, as I do not know how
6561 to quickly test if they are working or not, so I only document their
6562 existence.
</li
>
6566 <p
>By now I suspect you are really curious what the test results are
6567 for the HP machines I am testing. I
'm not done yet, so I will report
6568 the test results later. For now I can report that HP
8100 Elite work
6569 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
6570 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
6571 can see, I have most machines left to test. One interesting
6572 observation is that Ubuntu Lucid has almost twice the frame rate than
6573 RHEL6 with glxgears. No idea why.
</p
>
6578 <title>Some thoughts on BitCoins
</title>
6579 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
6580 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
6581 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
6582 <description><p
>As I continue to explore
6583 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
6584 what properties the system have, and how it will be affected by laws
6585 and regulations here in Norway. Here are some random notes.
</p
>
6587 <p
>One interesting thing to note is that since the transactions are
6588 verified using a peer to peer network, all details about a transaction
6589 is known to everyone. This means that if a BitCoin address has been
6590 published like I did with mine in my initial post about BitCoin, it is
6591 possible for everyone to see how many BitCoins have been transfered to
6592 that address. There is even a web service to look at the details for
6593 all transactions. There I can see that my address
6594 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
6595 have received
16.06 Bitcoin, the
6596 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
6597 address of Simon Phipps have received
181.97 BitCoin and the address
6598 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
6599 of EFF have received
2447.38 BitCoins so far. Thank you to each and
6600 every one of you that donated bitcoins to support my activity. The
6601 fact that anyone can see how much money was transfered to a given
6602 address make it more obvious why the BitCoin community recommend to
6603 generate and hand out a new address for each transaction. I
'm told
6604 there is no way to track which addresses belong to a given person or
6605 organisation without the person or organisation revealing it
6606 themselves, as Simon, EFF and I have done.
</p
>
6608 <p
>In Norway, and in most other countries, there are laws and
6609 regulations limiting how much money one can transfer across the border
6610 without declaring it. There are money laundering, tax and accounting
6611 laws and regulations I would expect to apply to the use of BitCoin.
6612 If the Skolelinux foundation
6613 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
6614 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
6615 normal bank transfers like EFF is doing, how should this be accounted?
6616 Given that it is impossible to know if money can cross the border or
6617 not, should everything or nothing be declared? What exchange rate
6618 should be used when calculating taxes? Would receivers have to pay
6619 income tax if the foundation were to pay Skolelinux contributors in
6620 BitCoin? I have no idea, but it would be interesting to know.
</p
>
6622 <p
>For a currency to be useful and successful, it must be trusted and
6623 accepted by a lot of users. It must be possible to get easy access to
6624 the currency (as a wage or using currency exchanges), and it must be
6625 easy to spend it. At the moment BitCoin seem fairly easy to get
6626 access to, but there are very few places to spend it. I am not really
6627 a regular user of any of the vendor types currently accepting BitCoin,
6628 so I wonder when my kind of shop would start accepting BitCoins. I
6629 would like to buy electronics, travels and subway tickets, not herbs
6630 and books. :) The currency is young, and this will improve over time
6631 if it become popular, but I suspect regular banks will start to lobby
6632 to get BitCoin declared illegal if it become popular. I
'm sure they
6633 will claim it is helping fund terrorism and money laundering (which
6634 probably would be true, as is any currency in existence), but I
6635 believe the problems should be solved elsewhere and not by blaming
6636 currencies.
</p
>
6638 <p
>The process of creating new BitCoins is called mining, and it is
6639 CPU intensive process that depend on a bit of luck as well (as one is
6640 competing against all the other miners currently spending CPU cycles
6641 to see which one get the next lump of cash). The
"winner
" get
50
6642 BitCoin when this happen. Yesterday I came across the obvious way to
6643 join forces to increase ones changes of getting at least some coins,
6644 by coordinating the work on mining BitCoins across several machines
6645 and people, and sharing the result if one is lucky and get the
50
6647 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
6648 if this sounds interesting. I have not had time to try to set up a
6649 machine to participate there yet, but have seen that running on ones
6650 own for a few days have not yield any BitCoins througth mining
6653 <p
>Update
2010-
12-
15: Found an
<a
6654 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
6655 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
6656 it was interesting to read. The arguments presented seem to be
6657 equally valid for gold, which was used as a currency for many years.
</p
>
6662 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
6663 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
6664 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
6665 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
6666 <description><p
>With this weeks lawless
6667 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
6668 attacks
</a
> on Wikileak and
6669 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
6670 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
6671 not be trusted to handle money transactions.
6673 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
6674 Phipps on bitcoin
</a
> reminded me about a project that a friend of
6675 mine mentioned earlier. I decided to follow Simon
's example, and get
6676 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
6677 some help from my friend to get it all running, and he even handed me
6678 some bitcoins to get started. I even donated a few bitcoins to Simon
6679 for helping me remember BitCoin.
</p
>
6681 <p
>So, what is bitcoins, you probably wonder? It is a digital
6682 crypto-currency, decentralised and handled using peer-to-peer
6683 networks. It allows anonymous transactions and prohibits central
6684 control over the transactions, making it impossible for governments
6685 and companies alike to block donations and other transactions. The
6686 source is free software, and while the key dependency wxWidgets
2.9
6687 for the graphical user interface is missing in Debian, the command
6688 line client builds just fine. Hopefully Jonas
6689 <a href=
"http://bugs.debian.org/
578157">will get the package into
6690 Debian
</a
> soon.
</p
>
6692 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
6693 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
6694 bitcoins
</a
> when selling services and goods, and there are even
6695 currency
"stock
" markets where the exchange rate is decided. There
6696 are not many users so far, but the concept seems promising. If you
6697 want to get started and lack a friend with any bitcoins to spare,
6699 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
6700 bitcoin at the time of writing). Use
6701 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
6702 on the current exchange rates.
</p
>
6704 <p
>As an experiment, I have decided to set up bitcoind on one of my
6705 machines. If you want to support my activity, please send Bitcoin
6706 donations to the address
6707 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
6712 <title>Why isn
't Debian Edu using VLC?
</title>
6713 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
6714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
6715 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
6716 <description><p
>In the latest issue of Linux Journal, the readers choices were
6717 presented, and the winner among the multimedia player were VLC.
6718 Personally, I like VLC, and it is my player of choice when I first try
6719 to play a video file or stream. Only if VLC fail will I drag out
6720 gmplayer to see if it can do better. The reason is mostly the failure
6721 model and trust. When VLC fail, it normally pop up a error message
6722 reporting the problem. When mplayer fail, it normally segfault or
6723 just hangs. The latter failure mode drain my trust in the program.
<p
>
6725 <p
>But even if VLC is my player of choice, we have choosen to use
6726 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
6727 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
6728 plugin to play web videos seamlessly, and the VLC browser plugin is
6729 not very good. For example, it lack in-line control buttons, so there
6730 is no way for the user to pause the video. Also, when I
6731 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
6732 tested the browser plugins
</a
> available in Debian, the VLC plugin
6733 failed on several video pages where mplayer based plugins worked. If
6734 the browser plugin for VLC was as good as the gecko-mediaplayer
6735 package (which uses mplayer), we would switch.
</P
>
6737 <p
>While VLC is a good player, its user interface is slightly
6738 annoying. The most annoying feature is its inconsistent use of
6739 keyboard shortcuts. When the player is in full screen mode, its
6740 shortcuts are different from when it is playing the video in a window.
6741 For example, space only work as pause when in full screen mode. I
6742 wish it had consisten shortcuts and that space also would work when in
6743 window mode. Another nice shortcut in gmplayer is [enter] to restart
6744 the current video. It is very nice when playing short videos from the
6745 web and want to restart it when new people arrive to have a look at
6746 what is going on.
</p
>
6751 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
6752 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
6753 <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>
6754 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
6755 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
6756 upgrade testing of the
6757 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6758 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
6759 This seem like a very good idea, so I adjusted by test scripts and
6760 can now present the updated result from today:
</p
>
6762 <p
>This is for Gnome:
</p
>
6764 <p
>Installed using apt-get, missing with aptitude
</p
>
6766 <blockquote
><p
>
6771 browser-plugin-gnash
6778 freedesktop-sound-theme
6780 gconf-defaults-service
6795 gnome-desktop-environment
6799 gnome-session-canberra
6804 gstreamer0.10-fluendo-mp3
6810 libapache2-mod-dnssd
6813 libaprutil1-dbd-sqlite3
6816 libboost-date-time1.42
.0
6817 libboost-python1.42
.0
6818 libboost-thread1.42
.0
6820 libchamplain-gtk-
0.4-
0
6822 libclutter-gtk-
0.10-
0
6829 libfreerdp-plugins-standard
6844 libgnomepanel2.24-cil
6849 libgtksourceview2.0-common
6850 libmono-addins-gui0.2-cil
6851 libmono-addins0.2-cil
6852 libmono-cairo2.0-cil
6853 libmono-corlib2.0-cil
6854 libmono-i18n-west2.0-cil
6855 libmono-posix2.0-cil
6856 libmono-security2.0-cil
6857 libmono-sharpzip2.84-cil
6858 libmono-system2.0-cil
6861 libndesk-dbus-glib1.0-cil
6862 libndesk-dbus1.0-cil
6872 libtelepathy-farsight0
6881 nautilus-sendto-empathy
6885 python-aptdaemon-gtk
6887 python-beautifulsoup
6902 python-gtksourceview2
6913 python-pkg-resources
6920 python-twisted-conch
6926 python-zope.interface
6931 rhythmbox-plugin-cdrecorder
6938 system-config-printer-udev
6940 telepathy-mission-control-
5
6951 </p
></blockquote
>
6953 <p
>Installed using apt-get, removed with aptitude
</p
>
6955 <blockquote
><p
>
6961 fast-user-switch-applet
6980 libgtksourceview2.0-
0
6982 libsdl1.2debian-alsa
6988 system-config-printer
6993 </p
></blockquote
>
6995 <p
>Installed using aptitude, missing with apt-get
</p
>
6997 <blockquote
><p
>
6998 gstreamer0.10-gnomevfs
6999 </p
></blockquote
>
7001 <p
>Installed using aptitude, removed with apt-get
</p
>
7003 <blockquote
><p
>
7005 </p
></blockquote
>
7007 <p
>This is for KDE:
</p
>
7009 <p
>Installed using apt-get, missing with aptitude
</p
>
7011 <blockquote
><p
>
7013 </p
></blockquote
>
7015 <p
>Installed using apt-get, removed with aptitude
</p
>
7017 <blockquote
><p
>
7020 </p
></blockquote
>
7022 <p
>Installed using aptitude, missing with apt-get
</p
>
7024 <blockquote
><p
>
7038 kdeartwork-emoticons
7040 kdeartwork-theme-icon
7044 kdebase-workspace-bin
7045 kdebase-workspace-data
7059 kscreensaver-xsavers
7074 plasma-dataengines-workspace
7076 plasma-desktopthemes-artwork
7077 plasma-runners-addons
7078 plasma-scriptengine-googlegadgets
7079 plasma-scriptengine-python
7080 plasma-scriptengine-qedje
7081 plasma-scriptengine-ruby
7082 plasma-scriptengine-webkit
7083 plasma-scriptengines
7084 plasma-wallpapers-addons
7085 plasma-widget-folderview
7086 plasma-widget-networkmanagement
7090 xscreensaver-data-extra
7092 xscreensaver-gl-extra
7093 xscreensaver-screensaver-bsod
7094 </p
></blockquote
>
7096 <p
>Installed using aptitude, removed with apt-get
</p
>
7098 <blockquote
><p
>
7100 google-gadgets-common
7118 libggadget-qt-
1.0-
0b
7123 libkonqsidebarplugin4a
7132 libplasma-geolocation-interface4
7134 libplasmagenericshell4
7148 libsmokeknewstuff2-
3
7149 libsmokeknewstuff3-
3
7151 libsmokektexteditor3
7159 libsmokeqtnetwork4-
3
7165 libsmokeqtuitools4-
3
7177 plasma-dataengines-addons
7178 plasma-scriptengine-superkaramba
7179 plasma-widget-lancelot
7180 plasma-widgets-addons
7181 plasma-widgets-workspace
7185 update-notifier-common
7186 </p
></blockquote
>
7188 <p
>Running apt-get autoremove made the results using apt-get and
7189 aptitude a bit more similar, but there are still quite a lott of
7190 differences. I have no idea what packages should be installed after
7191 the upgrade, but hope those that do can have a look.
</p
>
7196 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
7197 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
7198 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
7199 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
7200 <description><p
>Most of the computers in use by the
7201 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
7202 are virtual machines. And they have been Xen machines running on a
7203 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
7204 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
7205 bit harder that it could have been, because we set up the Xen virtual
7206 machines to get the virtual partitions from LVM, which as far as I
7207 know is not supported by KVM. So to migrate, we had to convert
7208 several LVM logical volumes to partitions on a virtual disk file.
</p
>
7211 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
7212 nice recipe
</a
> to do this, and wrote the following script to do the
7213 migration. It uses qemu-img from the qemu package to make the disk
7214 image, parted to partition it, losetup and kpartx to present the disk
7215 image partions as devices, and dd to copy the data. I NFS mounted the
7216 new servers storage area on the old server to do the migration.
</p
>
7222 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7227 if [ -z
"$
1" ] ; then
7228 echo
"Usage: $
0 &lt;hostname
&gt;
"
7234 if [ ! -e /dev/vg_data/$host-disk ] ; then
7235 echo
"error: unable to find LVM volume for $host
"
7239 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7240 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7241 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7242 totalsize=$(( ( $disksize + $swapsize ) ))
7245 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
7246 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7248 parted $img mklabel msdos
7249 parted $img mkpart primary linux-swap
0 $disksize
7250 parted $img mkpart primary ext2 $disksize $totalsize
7251 parted $img set
1 boot on
7254 losetup /dev/loop0 $img
7255 kpartx -a /dev/loop0
7257 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
7258 fsck.ext3 -f /dev/mapper/loop0p1 || true
7259 mkswap /dev/mapper/loop0p2
7261 kpartx -d /dev/loop0
7262 losetup -d /dev/loop0
7265 <p
>The script is perhaps so simple that it is not copyrightable, but
7266 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
7268 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
7269 the new disk image attached, installed grub-pc and linux-image-
686 and
7270 set up grub to boot from the disk image. After this, the KVM machines
7271 seem to work just fine.
</p
>
7276 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
7277 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
7278 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
7279 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
7280 <description><p
>I
'm still running upgrade testing of the
7281 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7282 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
7283 status. Here is a short update based on a test I ran
20101118.
</p
>
7285 <p
>I still do not know what a correct migration should look like, so I
7286 report any differences between apt and aptitude and hope someone else
7287 can see if anything should be changed.
</p
>
7289 <p
>This is for Gnome:
</p
>
7291 <p
>Installed using apt-get, missing with aptitude
</p
>
7293 <blockquote
><p
>
7294 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7295 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
7296 dmz-cursor-theme empathy empathy-common finger
7297 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7298 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7299 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7300 gnome-cards-data gnome-codec-install gnome-core
7301 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7302 gnome-search-tool gnome-session-canberra gnome-spell
7303 gnome-system-log gnome-themes-extras gnome-themes-more
7304 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7305 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7306 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7307 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7308 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
7309 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
7310 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
7311 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
7312 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
7313 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7314 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
7315 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7316 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7317 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7318 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7319 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7320 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7321 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7322 libmono-security2.0-cil libmono-sharpzip2.84-cil
7323 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
7324 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
7325 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
7326 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
7327 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
7328 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
7329 libxalan2-java libxerces2-java media-player-info mesa-utils
7330 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
7331 nautilus-sendto-empathy openoffice.org-writer2latex
7332 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
7333 python-aptdaemon python-aptdaemon-gtk python-axiom
7334 python-beautifulsoup python-bugbuddy python-clientform
7335 python-coherence python-configobj python-crypto python-cupshelpers
7336 python-cupsutils python-eggtrayicon python-elementtree
7337 python-epsilon python-evolution python-feedparser python-gdata
7338 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7339 python-gtksourceview2 python-httplib2 python-louie python-mako
7340 python-markupsafe python-mechanize python-nevow python-notify
7341 python-opengl python-openssl python-pam python-pkg-resources
7342 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7343 python-tagpy python-twisted-bin python-twisted-conch
7344 python-twisted-core python-twisted-web python-utidylib python-webkit
7345 python-xdg python-zope.interface remmina remmina-plugin-data
7346 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7347 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7348 software-center svgalibg1 system-config-printer-udev
7349 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
7350 totem totem-coherence totem-mozilla totem-plugins
7351 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7353 </p
></blockquote
>
7355 Installed using apt-get, removed with aptitude
7357 <blockquote
><p
>
7358 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7359 epiphany-extensions epiphany-gecko evolution-exchange
7360 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7361 gedit-common gnome-app-install gnome-games gnome-games-data
7362 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7363 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7364 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7365 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
7366 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
7367 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
7368 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
7369 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7370 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7371 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7372 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
7373 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
7374 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7375 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7376 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7377 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7378 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
7379 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
7380 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
7381 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
7382 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
7383 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7384 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7385 sound-juicer swfdec-gnome system-config-printer totem-common
7386 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7387 </p
></blockquote
>
7389 <p
>Installed using aptitude, missing with apt-get
</p
>
7391 <blockquote
><p
>
7392 gstreamer0.10-gnomevfs
7393 </p
></blockquote
>
7395 <p
>Installed using aptitude, removed with apt-get
</p
>
7397 <blockquote
><p
>
7399 </p
></blockquote
>
7401 <p
>This is for KDE:
</p
>
7403 <p
>Installed using apt-get, missing with aptitude
</p
>
7405 <blockquote
><p
>
7406 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
7407 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7408 ghostscript-x git gnome-audio gnugo granatier gs-common
7409 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7410 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7411 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7412 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7413 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7414 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7415 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7416 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7417 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7418 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7419 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7420 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
7421 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7422 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7423 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7424 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7425 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7426 libkrossui4 libmailtools-perl libmime-tools-perl
7427 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7428 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7429 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7430 lirc luatex marble networkstatus noatun-plugins
7431 openoffice.org-writer2latex palapeli palapeli-data parley
7432 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7433 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7434 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7436 </p
></blockquote
>
7438 <p
>Installed using apt-get, removed with aptitude
</p
>
7440 <blockquote
><p
>
7441 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7442 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7443 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7444 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7445 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7446 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7447 kitchensync kiten kjumpingcube klatin klettres klickety klines
7448 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7449 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7450 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7451 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7452 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7453 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7454 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7455 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7456 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7457 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
7458 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
7459 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7460 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
7461 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
7462 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7463 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7464 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7465 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7466 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7467 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7468 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
7469 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
7470 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7471 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7472 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7473 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7474 </p
></blockquote
>
7476 <p
>Installed using aptitude, missing with apt-get
</p
>
7478 <blockquote
><p
>
7479 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7480 kdeartwork kdebase kdebase-apps kdebase-workspace
7481 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7482 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7483 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7484 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7485 xscreensaver-screensaver-bsod
7486 </p
></blockquote
>
7488 <p
>Installed using aptitude, removed with apt-get
</p
>
7490 <blockquote
><p
>
7491 kdebase-bin konq-plugins konqueror
7492 </p
></blockquote
>
7497 <title>Gnash buildbot slave and Debian kfreebsd
</title>
7498 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
7499 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
7500 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
7501 <description><p
>Answering
7502 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
7503 call from the Gnash project
</a
> for
7504 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
7505 current source, I have set up a virtual KVM machine on the Debian
7506 Edu/Skolelinux virtualization host to test the git source on
7507 Debian/Squeeze. I hope this can help the developers in getting new
7508 releases out more often.
</p
>
7510 <p
>As the developers want less main-stream build platforms tested to,
7511 I have considered setting up a
<a
7512 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
7513 machine as well. I have also considered using the kfreebsd
7514 architecture in Debian as a file server in NUUG to get access to the
5
7515 TB zfs volume we currently use to store DV video. Because of this, I
7516 finally got around to do a test installation of Debian/Squeeze with
7517 kfreebsd. Installation went fairly smooth, thought I noticed some
7518 visual glitches in the cdebconf dialogs (black cursor left on the
7519 screen at random locations). Have not gotten very far with the
7520 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7521 fatal problem. Have to spend some more time on it to see if it is
7522 useful as a file server for NUUG. Will try to find time to set up a
7523 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
7528 <title>Debian in
3D
</title>
7529 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
7530 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
7531 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
7532 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
7534 <p
>3D printing is just great. I just came across this Debian logo in
7536 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
7537 thingiverse blog
</a
>.
</p
>
7542 <title>Software updates
2010-
10-
24</title>
7543 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
7544 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
7545 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
7546 <description><p
>Some updates.
</p
>
7548 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
7549 raise money for the project is going well. The lower limit of
10
7550 signers was reached in
24 hours, and so far
13 people have signed it.
7551 More signers and more funding is most welcome, and I am really curious
7552 how far we can get before the time limit of December
24 is reached.
7555 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
7556 about what appear to be a great code coverage tool capable of
7557 generating code coverage stats without any changes to the source code.
7559 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
7560 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
7561 It is missing in Debian, but the git source built just fine in Squeeze
7562 after I installed libelf-dev, libdwarf-dev, pkg-config and
7563 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7564 solvable. I hope kcov make it into Debian soon.
</p
>
7566 <p
>Finally found time to wrap up the release notes for
<a
7567 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
7568 new alpha release of Debian Edu
</a
>, and just published the second
7569 alpha test release of the Squeeze based Debian Edu /
7570 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
7571 release. Give it a try if you need a complete linux solution for your
7572 school, including central infrastructure server, workstations, thin
7573 client servers and diskless workstations. A nice touch added
7574 yesterday is RDP support on the thin client servers, for windows
7575 clients to get a Linux desktop on request.
</p
>
7580 <title>Some notes on Flash in Debian and Debian Edu
</title>
7581 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
7582 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
7583 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
7584 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
7585 popularity-contest numbers
</a
>, the adobe-flashplugin package the
7586 second most popular used package that is missing in Debian. The sixth
7587 most popular is flashplayer-mozilla. This is a clear indication that
7588 working flash is important for Debian users. Around
10 percent of the
7589 users submitting data to popcon.debian.org have this package
7590 installed.
</p
>
7592 <p
>In the report written by Lars Risan in August
2008
7593 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
7594 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7595 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
7596 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
7597 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
7598 web sites require Flash to work, and lacking working Flash support in
7599 the web browser and the problems with installing it was perceived as a
7600 good reason to stay with Windows.
</p
>
7602 <p
>I once saw a funny and sad comment in a web forum, where Linux was
7603 said to be the retarded cousin that did not really understand
7604 everything you told him but could work fairly well. This was a
7605 comment regarding the problems Linux have with proprietary formats and
7606 non-standard web pages, and is sad because it exposes a fairly common
7607 understanding of whose fault it is if web pages that only work in for
7608 example Internet Explorer
6 fail to work on Firefox, and funny because
7609 it explain very well how annoying it is for users when Linux
7610 distributions do not work with the documents they receive or the web
7611 pages they want to visit.
</p
>
7613 <p
>This is part of the reason why I believe it is important for Debian
7614 and Debian Edu to have a well working Flash implementation in the
7615 distribution, to get at least popular sites as Youtube and Google
7616 Video to working out of the box. For Squeeze, Debian have the chance
7617 to include the latest version of Gnash that will make this happen, as
7618 the new release
0.8.8 was published a few weeks ago and is resting in
7619 unstable. The new version work with more sites that version
0.8.7.
7620 The Gnash maintainers have asked for a freeze exception, but the
7621 release team have not had time to reply to it yet. I hope they agree
7622 with me that Flash is important for the Debian desktop users, and thus
7623 accept the new package into Squeeze.
</p
>
7628 <title>Circular package dependencies harms apt recovery
</title>
7629 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
7630 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
7631 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
7632 <description><p
>I discovered this while doing
7633 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
7634 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
7635 in Debian still got circular dependencies, and it is often claimed
7636 that apt and aptitude should be able to handle this just fine, but
7637 some times these dependency loops causes apt to fail.
</p
>
7639 <p
>An example is from todays
7640 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
7641 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
7642 causes perl-modules to fail to upgrade. The cause is simple. If a
7643 package fail to unpack, then only part of packages with the circular
7644 dependency might end up being unpacked when unpacking aborts, and the
7645 ones already unpacked will fail to configure in the recovery phase
7646 because its dependencies are unavailable.
</p
>
7648 <p
>In this log, the problem manifest itself with this error:
</p
>
7650 <blockquote
><pre
>
7651 dpkg: dependency problems prevent configuration of perl-modules:
7652 perl-modules depends on perl (
>=
5.10.1-
1); however:
7653 Version of perl on system is
5.10.0-
19lenny
2.
7654 dpkg: error processing perl-modules (--configure):
7655 dependency problems - leaving unconfigured
7656 </pre
></blockquote
>
7658 <p
>The perl/perl-modules circular dependency is already
7659 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
7660 hopefully be solved as soon as possible, but it is not the only one,
7661 and each one of these loops in the dependency tree can cause similar
7662 failures. Of course, they only occur when there are bugs in other
7663 packages causing the unpacking to fail, but it is rather nasty when
7664 the failure of one package causes the problem to become worse because
7665 of dependency loops.
</p
>
7668 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
7669 tireless effort by Bill Allombert
</a
>, the number of circular
7671 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
7672 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
7674 <p
>Todays testing also exposed a bug in
7675 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
7676 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
7677 apt-get and aptitude, the latter possibly caused by some circular
7678 dependency. Reported both to BTS to try to get someone to look at
7684 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
7685 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
7686 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
7687 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
7688 <description><p
>This is a
7689 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
7691 <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
7693 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
7694 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
7696 <p
>As a step to try to see if it possible to merge the DNS and DHCP
7697 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7698 and dhcp3-server-ldap in Debian use the LDAP server. The two
7699 implementations are quite different in how they use LDAP.
</p
>
7701 To get this information, I started slapd with debugging enabled and
7702 dumped the debug output to a file to get the LDAP searches performed
7703 on a Debian Edu main-server. Here is a summary.
7705 <p
><strong
>powerdns
</strong
></p
>
7707 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
7708 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
7711 <p
>PowerDNS have two modes of operation using LDAP as its backend.
7712 One
"strict
" mode where the forward and reverse DNS lookups are done
7713 using the same LDAP objects, and a
"tree
" mode where the forward and
7714 reverse entries are in two different subtrees in LDAP with a structure
7715 based on the DNS names, as in tjener.intern and
7716 2.2.0.10.in-addr.arpa.
</p
>
7718 <p
>In tree mode, the server is set up to use a LDAP subtree as its
7719 base, and uses a
"base
" scoped search for the DNS name by adding
7720 "dc=tjener,dc=intern,
" to the base with a filter for
7721 "(associateddomain=tjener.intern)
" for the forward entry and
7722 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
7723 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
7724 forward entries, it is looking for attributes named dnsttl, arecord,
7725 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7726 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7727 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7728 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7729 spfrecord and modifytimestamp. For reverse entries it is looking for
7730 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7731 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7732 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7733 ldapsearch commands could look like this:
</p
>
7735 <blockquote
><pre
>
7736 ldapsearch -h ldap \
7737 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7738 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7739 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7740 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7741 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7742 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7744 ldapsearch -h ldap \
7745 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7746 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
7747 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7748 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7749 srvrecord naptrrecord modifytimestamp
7750 </pre
></blockquote
>
7752 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
7753 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7754 example LDAP objects used there. In addition to these objects, the
7755 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7756 also exist.
</p
>
7758 <blockquote
><pre
>
7759 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7761 objectclass: dnsdomain
7762 objectclass: domainrelatedobject
7765 associateddomain: tjener.intern
7767 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7769 objectclass: dnsdomain2
7770 objectclass: domainrelatedobject
7772 ptrrecord: tjener.intern
7773 associateddomain:
2.2.0.10.in-addr.arpa
7774 </pre
></blockquote
>
7776 <p
>In strict mode, the server behaves differently. When looking for
7777 forward DNS entries, it is doing a
"subtree
" scoped search with the
7778 same base as in the tree mode for a object with filter
7779 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
7780 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7781 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7782 naptrrecord and modifytimestamp. For reverse entires it also do a
7783 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
7784 and the requested attributes are associateddomain, dnsttl and
7785 modifytimestamp. In short, in strict mode the objects with ptrrecord
7786 go away, and the arecord attribute in the forward object is used
7789 <p
>The forward and reverse searches can be simulated using ldapsearch
7790 like this:
</p
>
7792 <blockquote
><pre
>
7793 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7794 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7795 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7796 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7797 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7798 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7800 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7801 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
7802 </pre
></blockquote
>
7804 <p
>In addition to the forward and reverse searches , there is also a
7805 search for SOA records, which behave similar to the forward and
7806 reverse lookups.
</p
>
7808 <p
>A thing to note with the PowerDNS behaviour is that it do not
7809 specify any objectclass names, and instead look for the attributes it
7810 need to generate a DNS reply. This make it able to work with any
7811 objectclass that provide the needed attributes.
</p
>
7813 <p
>The attributes are normally provided in the cosine (RFC
1274) and
7814 dnsdomain2 schemas. The latter is used for reverse entries like
7815 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
7817 <p
>In Debian Edu, we have created DNS objects using the object classes
7818 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7819 attributes) and domainrelatedobject (for associatedDomain). The use
7820 of structural object classes make it impossible to combine these
7821 classes with the object classes used by DHCP.
</p
>
7823 <p
>There are other schemas that could be used too, for example the
7824 dnszone structural object class used by Gosa and bind-sdb for the DNS
7825 attributes combined with the domainrelatedobject object class, but in
7826 this case some unused attributes would have to be included as well
7827 (zonename and relativedomainname).
</p
>
7829 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
7830 mode and not use any of the existing objectclasses (dnsdomain,
7831 dnsdomain2 and dnszone) when one want to combine the DNS information
7832 with DHCP information, and instead create a auxiliary object class
7833 defined something like this (using the attributes defined for
7834 dnsdomain and dnsdomain2 or dnszone):
</p
>
7836 <blockquote
><pre
>
7837 objectclass ( some-oid NAME
'dnsDomainAux
'
7840 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7841 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7842 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7843 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7844 A6Record $ DNAMERecord
7846 </pre
></blockquote
>
7848 <p
>This will allow any object to become a DNS entry when combined with
7849 the domainrelatedobject object class, and allow any entity to include
7850 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
7851 developers asking for their view on this schema and if they are
7852 interested in providing such schema with PowerDNS, and I hope my
7853 message will be accepted into their mailing list soon.
</p
>
7855 <p
><strong
>ISC dhcp
</strong
></p
>
7857 <p
>The DHCP server searches for specific objectclass and requests all
7858 the object attributes, and then uses the attributes it want. This
7859 make it harder to figure out exactly what attributes are used, but
7860 thanks to the working example in Debian Edu I can at least get an idea
7861 what is needed without having to read the source code.
</p
>
7863 <p
>In the DHCP server configuration, the LDAP base to use and the
7864 search filter to use to locate the correct dhcpServer entity is
7865 stored. These are the relevant entries from
7866 /etc/dhcp3/dhcpd.conf:
</p
>
7868 <blockquote
><pre
>
7869 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
7870 ldap-dhcp-server-cn
"dhcp
";
7871 </pre
></blockquote
>
7873 <p
>The DHCP server uses this information to nest all the DHCP
7874 configuration it need. The cn
"dhcp
" is located using the given LDAP
7875 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
7876 search result is this entry:
</p
>
7878 <blockquote
><pre
>
7879 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7882 objectClass: dhcpServer
7883 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7884 </pre
></blockquote
>
7886 <p
>The content of the dhcpServiceDN attribute is next used to locate the
7887 subtree with DHCP configuration. The DHCP configuration subtree base
7888 is located using a base scope search with base
"cn=DHCP
7889 Config,dc=skole,dc=skolelinux,dc=no
" and filter
7890 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
7891 The search result is this entry:
</p
>
7893 <blockquote
><pre
>
7894 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7897 objectClass: dhcpService
7898 objectClass: dhcpOptions
7899 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7900 dhcpStatements: ddns-update-style none
7901 dhcpStatements: authoritative
7902 dhcpOption: smtp-server code
69 = array of ip-address
7903 dhcpOption: www-server code
72 = array of ip-address
7904 dhcpOption: wpad-url code
252 = text
7905 </pre
></blockquote
>
7907 <p
>Next, the entire subtree is processed, one level at the time. When
7908 all the DHCP configuration is loaded, it is ready to receive requests.
7909 The subtree in Debian Edu contain objects with object classes
7910 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7911 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7912 and information about netmasks, dynamic range etc. Leaving out the
7913 details here because it is not relevant for the focus of my
7914 investigation, which is to see if it is possible to merge dns and dhcp
7915 related computer objects.
</p
>
7917 <p
>When a DHCP request come in, LDAP is searched for the MAC address
7918 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
7919 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
7920 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7921 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
7924 <blockquote
><pre
>
7925 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7928 objectClass: dhcpHost
7929 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7930 dhcpStatements: fixed-address hostname
7931 </pre
></blockquote
>
7933 <p
>There is less flexiblity in the way LDAP searches are done here.
7934 The object classes need to have fixed names, and the configuration
7935 need to be stored in a fairly specific LDAP structure. On the
7936 positive side, the invidiual dhcpHost entires can be anywhere without
7937 the DN pointed to by the dhcpServer entries. The latter should make
7938 it possible to group all host entries in a subtree next to the
7939 configuration entries, and this subtree can also be shared with the
7940 DNS server if the schema proposed above is combined with the dhcpHost
7941 structural object class.
7943 <p
><strong
>Conclusion
</strong
></p
>
7945 <p
>The PowerDNS implementation seem to be very flexible when it come
7946 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
7947 come to the the LDAP structure, the
"strict
" mode is very flexible,
7948 allowing DNS objects to be stored anywhere under the base cn specified
7949 in the configuration.
</p
>
7951 <p
>The DHCP implementation on the other hand is very inflexible, both
7952 regarding which LDAP schemas to use and which LDAP structure to use.
7953 I guess one could implement ones own schema, as long as the
7954 objectclasses and attributes have the names used, but this do not
7955 really help when the DHCP subtree need to have a fairly fixed
7956 structure.
</p
>
7958 <p
>Based on the observed behaviour, I suspect a LDAP structure like
7959 this might work for Debian Edu:
</p
>
7961 <blockquote
><pre
>
7963 cn=machine-info (dhcpService) - dhcpServiceDN points here
7964 cn=dhcp (dhcpServer)
7965 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7966 cn=
10.0.2.0 (dhcpSubnet)
7967 cn=group1 (dhcpGroup/dhcpOptions)
7968 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7969 cn=
192.168.0.0 (dhcpSubnet)
7970 cn=group1 (dhcpGroup/dhcpOptions)
7971 ou=machines - PowerDNS base points here
7972 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7973 </pre
></blockquote
>
7975 <P
>This is not tested yet. If the DHCP server require the dhcpHost
7976 entries to be in the dhcpGroup subtrees, the entries can be stored
7977 there instead of a common machines subtree, and the PowerDNS base
7978 would have to be moved one level up to the machine-info subtree.
</p
>
7980 <p
>The combined object under the machines subtree would look something
7981 like this:
</p
>
7983 <blockquote
><pre
>
7984 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7987 objectClass: dhcpHost
7988 objectclass: domainrelatedobject
7989 objectclass: dnsDomainAux
7990 associateddomain: hostname.intern
7991 arecord:
10.11.12.13
7992 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7993 dhcpStatements: fixed-address hostname.intern
7994 </pre
></blockquote
>
7996 </p
>One could even add the LTSP configuration associated with a given
7997 machine, as long as the required attributes are available in a
7998 auxiliary object class.
</p
>
8003 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8004 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8005 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8006 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8007 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8008 DHCP services in Debian Edu to use the same LDAP objects for a given
8009 computer, to avoid the possibility of having a inconsistent state for
8010 a computer in LDAP (as in DHCP but no DNS entry or the other way
8011 around) and make it easier to add computers to LDAP.
</p
>
8013 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8014 information finally found a solution that seem to work.
</p
>
8016 <p
>The old setup required three LDAP objects for a given computer.
8017 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8018 we switch powerdns to use its strict LDAP method (ldap-method=strict
8019 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8020 merged into one while making it impossible to transfer the reverse map
8021 to a slave DNS server.
</p
>
8023 <p
>If we also replace the object class used to get the DNS related
8024 attributes to one allowing these attributes to be combined with the
8025 dhcphost object class, we can merge the DNS and DHCP entries into one.
8026 I
've written such object class in the dnsdomainaux.schema file (need
8027 proper OIDs, but that is a minor issue), and tested the setup. It
8028 seem to work.
</p
>
8030 <p
>With this test setup in place, we can get away with one LDAP object
8031 for both DNS and DHCP, and even the LTSP configuration I suggested in
8032 an earlier email. The combined LDAP object will look something like
8035 <blockquote
><pre
>
8036 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8038 objectClass: dhcphost
8039 objectclass: domainrelatedobject
8040 objectclass: dnsdomainaux
8041 associateddomain: hostname.intern
8042 arecord:
10.11.12.13
8043 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8044 dhcpstatements: fixed-address hostname
8046 </pre
></blockquote
>
8048 <p
>The DNS server uses the associateddomain and arecord entries, while
8049 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8050 before asking DNS to resolve the fixed-adddress. LTSP will use
8051 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8053 <p
>I am not yet sure if I can get the DHCP server to look for its
8054 dhcphost in a different location, to allow us to put the objects
8055 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8056 that. If I can
't figure out a way to do that, we can still get rid of
8057 the hosts subtree and move all its content into the DHCP Config tree
8058 (which probably should be renamed to be more related to the new
8059 content. I suspect cn=dnsdhcp,ou=services or something like that
8060 might be a good place to put it.
</p
>
8062 <p
>If you want to help out with implementing this for Debian Edu,
8063 please contact us on debian-edu@lists.debian.org.
</p
>
8068 <title>Idea for storing LTSP configuration in LDAP
</title>
8069 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8070 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8071 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8072 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8073 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8074 clients, and that this can be used to fetch configuration from LDAP if
8075 Debian Edu choose to store configuration there.
</p
>
8077 <p
>Armed with this information, I got inspired and wrote a test module
8078 to get configuration from LDAP. The idea is to look up the MAC
8079 address of the client in LDAP, and look for attributes on the form
8080 ltspconfigsetting=value, and use this to export SETTING=value to the
8081 LTSP clients.
</p
>
8083 <p
>The goal is to be able to store the LTSP configuration attributes
8084 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8085 allowing us to store all information about a computer in one place.
</p
>
8087 <p
>This is a untested draft implementation, and I welcome feedback on
8088 this approach. A real LDAP schema for the ltspClientAux objectclass
8089 need to be written. Comments, suggestions, etc?
</p
>
8091 <blockquote
><pre
>
8092 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8094 # Fetch LTSP client settings from LDAP based on MAC address
8096 # Uses ethernet address as stored in the dhcpHost objectclass using
8097 # the dhcpHWAddress attribute or ethernet address stored in the
8098 # ieee802Device objectclass with the macAddress attribute.
8100 # This module is written to be schema agnostic, and only depend on the
8101 # existence of attribute names.
8103 # The LTSP configuration variables are saved directly using a
8104 # ltspConfig prefix and uppercasing the rest of the attribute name.
8105 # To set the SERVER variable, set the ltspConfigServer attribute.
8107 # Some LDAP schema should be created with all the relevant
8108 # configuration settings. Something like this should work:
8110 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
8113 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8115 LDAPSERVER=$(debian-edu-ldapserver)
8116 if [
"$LDAPSERVER
" ] ; then
8117 LDAPBASE=$(debian-edu-ldapserver -b)
8118 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8119 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8120 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8121 grep
'^ltspConfig
' | while read attr value ; do
8122 # Remove prefix and convert to upper case
8123 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8124 # bass value on to clients
8125 eval
"$attr=$value; export $attr
"
8129 </pre
></blockquote
>
8131 <p
>I
'm not sure this shell construction will work, because I suspect
8132 the while block might end up in a subshell causing the variables set
8133 there to not show up in ltsp-config, but if that is the case I am sure
8134 the code can be restructured to make sure the variables are passed on.
8135 I expect that can be solved with some testing. :)
</p
>
8137 <p
>If you want to help out with implementing this for Debian Edu,
8138 please contact us on debian-edu@lists.debian.org.
</p
>
8140 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
8141 configuration in LDAP that was created around year
2000 by
8142 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
8143 Xperience, Inc.,
2000</a
>. I found its
8144 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
8145 personal home page over at redhat.com.
</p
>
8150 <title>jXplorer, a very nice LDAP GUI
</title>
8151 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8152 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8153 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8154 <description><p
>Since
8155 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8156 last post
</a
> about available LDAP tools in Debian, I was told about a
8157 LDAP GUI that is even better than luma. The java application
8158 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8159 moving LDAP objects and subtrees using drag-and-drop, and can
8160 authenticate using Kerberos. I have only tested the Kerberos
8161 authentication, but do not have a LDAP setup allowing me to rewrite
8162 LDAP with my test user yet. It is
8163 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8164 Debian
</a
> testing and unstable at the moment. The only problem I
8165 have with it is how it handle errors. If something go wrong, its
8166 non-intuitive behaviour require me to go through some query work list
8167 and remove the failing query. Nothing big, but very annoying.
</p
>
8172 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8173 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8174 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8175 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8176 <description><p
>Here is a short update on my
<a
8177 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8178 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8179 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8180 not reporting the status for KDE, because the upgrade crashes when
8181 aptitude try because of missing conflicts
8182 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8183 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8185 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8186 complete list of the installed packages. Based on this I see these
8187 differences when I did a test run today. As usual, I do not really
8188 know what the correct set of packages would be, but thought it best to
8189 publish the difference.
</p
>
8191 <p
>Installed using apt-get, missing with aptitude
</p
>
8193 <blockquote
><p
>
8194 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
8195 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
8196 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8197 libgtksourceview-common libpt-
1.10.10-plugins-alsa
8198 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8199 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8200 python-
4suite-xml python-eggtrayicon python-gtkhtml2
8201 python-gtkmozembed svgalibg1 xserver-xephyr zip
8202 </p
></blockquote
>
8204 <p
>Installed using apt-get, removed with aptitude
</p
>
8206 <blockquote
><p
>
8207 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8208 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8209 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
8210 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
8211 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
8212 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
8213 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8214 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8215 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8216 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
8217 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
8218 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
8219 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8220 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
8221 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8222 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
8223 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
8224 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8225 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8226 mysql-common swfdec-gnome totem-gstreamer wodim
8227 </p
></blockquote
>
8229 <p
>Installed using aptitude, missing with apt-get
</p
>
8231 <blockquote
><p
>
8232 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8233 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8234 xserver-xorg-input-all xserver-xorg-input-evdev
8235 xserver-xorg-input-kbd xserver-xorg-input-mouse
8236 xserver-xorg-input-synaptics xserver-xorg-video-all
8237 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8238 xserver-xorg-video-chips xserver-xorg-video-cirrus
8239 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8240 xserver-xorg-video-glint xserver-xorg-video-i128
8241 xserver-xorg-video-i740 xserver-xorg-video-mach64
8242 xserver-xorg-video-mga xserver-xorg-video-neomagic
8243 xserver-xorg-video-nouveau xserver-xorg-video-nv
8244 xserver-xorg-video-r128 xserver-xorg-video-radeon
8245 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8246 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8247 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8248 xserver-xorg-video-sis xserver-xorg-video-sisusb
8249 xserver-xorg-video-tdfx xserver-xorg-video-tga
8250 xserver-xorg-video-trident xserver-xorg-video-tseng
8251 xserver-xorg-video-vesa xserver-xorg-video-vmware
8252 xserver-xorg-video-voodoo
8253 </p
></blockquote
>
8255 <p
>Installed using aptitude, removed with apt-get
</p
>
8257 <blockquote
><p
>
8258 deskbar-applet xserver-xorg xserver-xorg-core
8259 xserver-xorg-input-wacom xserver-xorg-video-intel
8260 xserver-xorg-video-openchrome
8261 </p
></blockquote
>
8263 <p
>I was told on IRC that the xorg-xserver package was
8264 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
8265 in git
</a
> today to try to get apt-get to not remove xorg completely.
8266 No idea when it hits Squeeze, but when it does I hope it will reduce
8267 the difference somewhat.
8272 <title>LUMA, a very nice LDAP GUI
</title>
8273 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
8274 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
8275 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
8276 <description><p
>The last few days I have been looking into the status of the LDAP
8277 directory in Debian Edu, and in the process I started to miss a GUI
8278 tool to browse the LDAP tree. The only one I was able to find in
8279 Debian/Squeeze and Lenny is
8280 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
8281 be a great tool to get a overview of the current LDAP directory
8282 populated by default in Skolelinux. Thanks to it, I have been able to
8283 find empty and obsolete subtrees, misplaced objects and duplicate
8284 objects. It will be installed by default in Debian/Squeeze. If you
8285 are working with LDAP, give it a go. :)
</p
>
8287 <p
>I did notice one problem with it I have not had time to report to
8288 the BTS yet. There is no .desktop file in the package, so the tool do
8289 not show up in the Gnome and KDE menus, but only deep down in in the
8290 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8293 <p
>I have not yet been able to get it to modify the tree yet. I would
8294 like to move objects and remove subtrees directly in the GUI, but have
8295 not found a way to do that with LUMA yet. So in the mean time, I use
8296 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
8298 <p
>If you have tips on other GUI tools for LDAP that might be useful
8299 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
8301 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
8302 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
8303 useful GUI alternative. It seem like a good tool, but is unmaintained
8304 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8305 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
8310 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
8311 <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>
8312 <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>
8313 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
8314 <description><p
>A while back, I
8315 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
8316 about the fact
</a
> that it is not possible with the provided schemas
8317 for storing DNS and DHCP information in LDAP to combine the two sets
8318 of information into one LDAP object representing a computer.
</p
>
8320 <p
>In the mean time, I discovered that a simple fix would be to make
8321 the dhcpHost object class auxiliary, to allow it to be combined with
8322 the dNSDomain object class, and thus forming one object for one
8323 computer when storing both DHCP and DNS information in LDAP.
</p
>
8325 <p
>If I understand this correctly, it is not safe to do this change
8326 without also changing the assigned number for the object class, and I
8327 do not know enough about LDAP schema design to do that properly for
8328 Debian Edu.
</p
>
8330 <p
>Anyway, for future reference, this is how I believe we could change
8332 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
8333 schema
</a
> to solve at least part of the problem with the LDAP schemas
8334 available today from IETF.
</p
>
8337 --- dhcp.schema (revision
65192)
8338 +++ dhcp.schema (working copy)
8340 objectclass (
2.16.840.1.113719.1.203.6.6
8341 NAME
'dhcpHost
'
8342 DESC
'This represents information about a particular client
'
8346 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8347 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
8350 <p
>I very much welcome clues on how to do this properly for Debian
8351 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8352 package, and should thus be free to rewrite it as we see fit.
</p
>
8354 <p
>If you want to help out with implementing this for Debian Edu,
8355 please contact us on debian-edu@lists.debian.org.
</p
>
8360 <title>Calling tasksel like the installer, while still getting useful output
</title>
8361 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
8362 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
8363 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
8364 <description><p
>A few times I have had the need to simulate the way tasksel
8365 installs packages during the normal debian-installer run. Until now,
8366 I have ended up letting tasksel do the work, with the annoying problem
8367 of not getting any feedback at all when something fails (like a
8368 conffile question from dpkg or a download that fails), using code like
8371 <blockquote
><pre
>
8372 export DEBIAN_FRONTEND=noninteractive
8373 tasksel --new-install
8374 </pre
></blockquote
>
8376 This would invoke tasksel, let its automatic task selection pick the
8377 tasks to install, and continue to install the requested tasks without
8378 any output what so ever.
8380 Recently I revisited this problem while working on the automatic
8381 package upgrade testing, because tasksel would some times hang without
8382 any useful feedback, and I want to see what is going on when it
8383 happen. Then it occured to me, I can parse the output from tasksel
8384 when asked to run in test mode, and use that aptitude command line
8385 printed by tasksel then to simulate the tasksel run. I ended up using
8388 <blockquote
><pre
>
8389 export DEBIAN_FRONTEND=noninteractive
8390 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
8392 </pre
></blockquote
>
8394 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
8395 --without-recommends -o APT::Install-Recommends=no -y install
8396 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8397 ~pimportant
</tt
>", which will install the gnome desktop task, the
8398 laptop task and all packages with priority standard , required and
8399 important, just like tasksel would have done it during
8400 installation.
</p
>
8402 <p
>A better approach is probably to extend tasksel to be able to
8403 install packages without using debconf-apt-progress, for use cases
8404 like this.
</p
>
8409 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
8410 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
8411 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
8412 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
8413 <description><p
>My
8414 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
8415 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
8416 finally made the upgrade logs available from
8417 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
8418 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8419 apt and aptitude, and found their differences interesting. This time
8420 I will only focus on their removal plans.
</p
>
8422 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
8423 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
8424 surprising part is that it want to remove xorg and all
8425 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8426 sure why. When asking aptitude to do the same, it want to remove
129
8427 packages, but most of them are library packages I suspect are no
8428 longer needed. Both of them want to remove bluetooth packages, which
8429 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
8431 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
8432 which seem like a bad idea and xorg the same way as with Gnome. Asking
8433 aptitude for the same, it wants to remove
192 packages, none which are
8434 too surprising.
</p
>
8436 <p
>I guess the removal of xorg during upgrades should be investigated
8437 and avoided, and perhaps others as well. Here are the complete list
8438 of planned removals. The complete logs is available from the URL
8439 above. Note if you want to repeat these tests, that the upgrade test
8440 for kde+apt-get hung in the tasksel setup because of dpkg asking
8441 conffile questions. No idea why. I worked around it by using
8442 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
8445 <p
><b
>apt-get gnome
72</b
>
8446 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
8447 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8448 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
8449 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8450 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8451 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8452 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8453 xserver-xorg-input-kbd xserver-xorg-input-mouse
8454 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8455 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8456 xserver-xorg-video-ati xserver-xorg-video-chips
8457 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8458 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8459 xserver-xorg-video-glint xserver-xorg-video-i128
8460 xserver-xorg-video-i740 xserver-xorg-video-imstt
8461 xserver-xorg-video-intel xserver-xorg-video-mach64
8462 xserver-xorg-video-mga xserver-xorg-video-neomagic
8463 xserver-xorg-video-nsc xserver-xorg-video-nv
8464 xserver-xorg-video-openchrome xserver-xorg-video-r128
8465 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8466 xserver-xorg-video-rendition xserver-xorg-video-s3
8467 xserver-xorg-video-s3virge xserver-xorg-video-savage
8468 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8469 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8470 xserver-xorg-video-tga xserver-xorg-video-trident
8471 xserver-xorg-video-tseng xserver-xorg-video-v4l
8472 xserver-xorg-video-vesa xserver-xorg-video-vga
8473 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
8474 xulrunner-
1.9-gnome-support
</p
>
8476 <p
><b
>aptitude gnome
129</b
>
8478 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
8479 djvulibre-desktop finger gnome-app-install gnome-mount
8480 gnome-network-admin gnome-spell gnome-vfs-obexftp
8481 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8482 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8483 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8484 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
8485 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
8486 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
8487 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
8488 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
8489 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
8490 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
8491 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
8492 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
8493 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8494 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
8495 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
8496 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
8497 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
8498 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
8499 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8500 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8501 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8502 openoffice.org-writer2latex openssl-blacklist p7zip
8503 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
8504 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8505 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8506 swfdec-mozilla totem-gstreamer update-manager wodim
8507 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8508 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8511 <p
><b
>apt-get kde
82</b
>
8513 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8514 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8515 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8516 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8517 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8518 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8519 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8520 xserver-xorg-input-kbd xserver-xorg-input-mouse
8521 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8522 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8523 xserver-xorg-video-ati xserver-xorg-video-chips
8524 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8525 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8526 xserver-xorg-video-glint xserver-xorg-video-i128
8527 xserver-xorg-video-i740 xserver-xorg-video-imstt
8528 xserver-xorg-video-intel xserver-xorg-video-mach64
8529 xserver-xorg-video-mga xserver-xorg-video-neomagic
8530 xserver-xorg-video-nsc xserver-xorg-video-nv
8531 xserver-xorg-video-openchrome xserver-xorg-video-r128
8532 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8533 xserver-xorg-video-rendition xserver-xorg-video-s3
8534 xserver-xorg-video-s3virge xserver-xorg-video-savage
8535 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8536 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8537 xserver-xorg-video-tga xserver-xorg-video-trident
8538 xserver-xorg-video-tseng xserver-xorg-video-v4l
8539 xserver-xorg-video-vesa xserver-xorg-video-vga
8540 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
8542 <p
><b
>aptitude kde
192</b
>
8543 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
8544 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8545 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8546 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8547 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8548 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8549 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8550 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8551 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8552 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8553 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8554 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8555 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8556 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8557 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8558 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8559 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8560 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8561 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
8562 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8563 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8564 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
8565 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8566 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8567 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8568 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8569 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8570 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
8571 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
8572 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8573 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8574 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8575 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8576 texlive-common texlive-doc-base texlive-fonts-recommended
8577 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8578 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8579 xulrunner-
1.9</p
>
8585 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
8586 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
8587 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
8588 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
8589 <description><p
>The last few days I have done some upgrade testing in Debian, to
8590 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8591 have been discovered and reported in the process
8592 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
8593 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
8594 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
8595 kdebase-workspace-data), and to get a more regular testing going on, I
8596 am working on a script to automate the test.
</p
>
8598 <p
>The idea is to create a Lenny chroot and use tasksel to install a
8599 Gnome or KDE desktop installation inside the chroot before upgrading
8600 it. To ensure no services are started in the chroot, a policy-rc.d
8601 script is inserted. To make sure tasksel believe it is to install a
8602 desktop on a laptop, the tasksel tests are replaced in the chroot
8603 (only acceptable because this is a throw-away chroot).
</p
>
8605 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8606 currently always fail because udev refuses to upgrade with the kernel
8607 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8608 is created. The bug report
8609 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
8610 this problem do not trigger in a chroot, but I touch the file anyway
8611 to make sure the upgrade go well. Testing on virtual and real
8612 hardware have failed me because of udev so far, and creating this file
8613 do the trick in such settings anyway. This is a
8614 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
8615 issue
</a
> and the current udev behaviour is intended by the udev
8616 maintainer because he lack the resources to rewrite udev to keep
8617 working with old kernels or something like that. I really wish the
8618 udev upstream would keep udev backwards compatible, to avoid such
8619 upgrade problem, but given that they fail to do so, I guess
8620 documenting the way out of this mess is the best option we got for
8621 Debian Squeeze.
</p
>
8623 <p
>Anyway, back to the task at hand, testing upgrades. This test
8624 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
8627 <blockquote
><pre
>
8631 if [
"$
1" ] ; then
8640 exec
&lt; /dev/null
8642 mirror=http://ftp.skolelinux.org/debian
8643 tmpdir=chroot-$from-upgrade-$to-$desktop
8645 debootstrap $from $tmpdir $mirror
8646 chroot $tmpdir aptitude update
8647 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
8651 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8655 mount -t proc proc $tmpdir/proc
8656 # Make sure proc is unmounted also on failure
8657 trap exit_cleanup EXIT INT
8659 chroot $tmpdir aptitude -y install debconf-utils
8661 # Make sure tasksel autoselection trigger. It need the test scripts
8662 # to return the correct answers.
8663 echo tasksel tasksel/desktop multiselect $desktop | \
8664 chroot $tmpdir debconf-set-selections
8666 # Include the desktop and laptop task
8667 for test in desktop laptop ; do
8668 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
8672 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8675 DEBIAN_FRONTEND=noninteractive
8676 DEBIAN_PRIORITY=critical
8677 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8678 chroot $tmpdir tasksel --new-install
8680 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
8681 chroot $tmpdir aptitude update
8682 touch $tmpdir/etc/udev/kernel-upgrade
8683 chroot $tmpdir aptitude -y dist-upgrade
8685 </pre
></blockquote
>
8687 <p
>I suspect it would be useful to test upgrades with both apt-get and
8688 with aptitude, but I have not had time to look at how they behave
8689 differently so far. I hope to get a cron job running to do the test
8690 regularly and post the result on the web. The Gnome upgrade currently
8691 work, while the KDE upgrade fail because of the bug in
8692 kdebase-workspace-data
</p
>
8694 <p
>I am not quite sure what kind of extract from the huge upgrade logs
8695 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
8696 post, so I will refrain from trying. I can report that for Gnome,
8697 aptitude report
760 packages upgraded,
448 newly installed,
129 to
8698 remove and
1 not upgraded and
1024MB need to be downloaded while for
8699 KDE the same numbers are
702 packages upgraded,
507 newly installed,
8700 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
8702 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
8703 is able to migrate to dependency based boot sequencing and parallel
8704 booting without a hitch. Was unsure if there were still bugs with
8705 packages failing to clean up their obsolete init.d script during
8706 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8712 <title>Upstart or sysvinit - as init.d scripts see it
</title>
8713 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
8714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
8715 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
8716 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
8717 scripts to migrate (some of) their operations to upstart job while
8718 keeping the init.d for hurd and kfreebsd. The packages with such
8719 needs will need a way to get their init.d scripts to behave
8720 differently when used with sysvinit and with upstart. Because of
8721 this, I had a look at the environment variables set when a init.d
8722 script is running under upstart, and when it is not.
</p
>
8724 <p
>With upstart, I notice these environment variables are set when a
8725 script is started from rcS.d/ (ignoring some irrelevant ones like
8728 <blockquote
><pre
>
8734 UPSTART_EVENTS=startup
8736 UPSTART_JOB=rc-sysinit
8737 </pre
></blockquote
>
8739 <p
>With sysvinit, these environment variables are set for the same
8742 <blockquote
><pre
>
8743 INIT_VERSION=sysvinit-
2.88
8748 </pre
></blockquote
>
8750 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
8751 sysvinit are not set by upstart. Not sure if it is intentional or not
8752 to not be compatible with sysvinit in this regard.
</p
>
8754 <p
>For scripts needing to behave differently when upstart is used,
8755 looking for the UPSTART_JOB environment variable seem to be a good
8761 <title>A manual for standards wars...
</title>
8762 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
8763 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
8764 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
8765 <description><p
>Via the
8766 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
8767 of Rob Weir
</a
> I came across the very interesting essay named
8768 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
8769 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
8770 following the standards wars of today.
</p
>
8775 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
8776 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
8777 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
8778 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
8779 <description><p
>When using sitesummary at a site to track machines, it is possible
8780 to get a list of the machine types in use thanks to the DMI
8781 information extracted from each machine. The script to do so is
8782 included in the sitesummary package, and here is example output from
8783 the Skolelinux build servers:
</p
>
8785 <blockquote
><pre
>
8786 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8788 Dell Computer Corporation
1
8791 eserver xSeries
345 -[
8670M1X]-
1
8795 </pre
></blockquote
>
8797 <p
>The quality of the report depend on the quality of the DMI tables
8798 provided in each machine. Here there are Intel machines without model
8799 information listed with Intel as vendor and no model, and virtual Xen
8800 machines listed as [no-dmi-info]. One can add -l as a command line
8801 option to list the individual machines.
</p
>
8803 <p
>A larger list is
8804 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
8805 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
8806 provide the basic sitesummary report publicly. In their report there
8807 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
8808 their machines, and as sitesummary is available in both distributions,
8809 it is trivial to get all of them to report to the same central
8810 collector.
</p
>
8815 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
8816 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
8817 <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>
8818 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
8819 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
8820 start at boot when an NVidia video card is used is handled. The
8821 problem seem to be that the nvidia X.org driver uses a long time to
8822 initialize, and this duration is longer than kdm is configured to
8825 <p
>I came across two bugs related to this issue,
8826 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
8827 against initscripts and passed on to nvidia-glx when it became obvious
8828 that the nvidia drivers were involved, and
8829 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
8830 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
8832 <p
>To me, it seem that no-one is interested in actually solving the
8833 problem nvidia video card owners experience and make sure the Debian
8834 distribution work out of the box for these users. The nvidia driver
8835 maintainers expect kdm to be set up to wait longer, while kdm expect
8836 the nvidia driver maintainers to fix the driver to start faster, and
8837 while they wait for each other I guess the users end up switching to a
8838 distribution that work for them. I have no idea what the solution is,
8839 but I am pretty sure that waiting for each other is not it.
</p
>
8841 <p
>I wonder why we end up handling bugs this way.
</p
>
8846 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
8847 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
8848 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
8849 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
8850 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
8851 The feature seem to hold up pretty well, but three fairly serious
8852 issues are known and should be solved:
8856 <li
>The wicd package seen to
8857 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
8858 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
8859 parallel booting is enabled. No idea why, but the wicd maintainer
8860 seem to be on the case.
</li
>
8862 <li
>The nvidia X driver seem to
8863 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
8864 triggered more easily when parallel booting is in effect. The
8865 maintainer is on the case.
</li
>
8867 <li
>The sysv-rc package fail to properly enable dependency based boot
8868 sequencing (the shutdown is broken) when old file-rc users
8869 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
8870 sysv-rc. One way to solve it would be for file-rc to create
8871 /etc/init.d/.legacy-bootordering, and another is to try to make
8872 sysv-rc more robust. Will investigate some more and probably upload a
8873 workaround in sysv-rc to help those trying to move from file-rc to
8874 sysv-rc get a working shutdown.
</li
>
8876 </ul
></p
>
8878 <p
>All in all not many surprising issues, and all of them seem
8879 solvable before Squeeze is released. In addition to these there are
8880 some packages with bugs in their dependencies and run level settings,
8881 which I expect will be fixed in a reasonable time span.
</p
>
8883 <p
>If you report any problems with dependencies in init.d scripts to
8884 the BTS, please usertag the report to get it to show up at
8885 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8886 list of usertagged bugs related to this
</a
>.
</p
>
8888 <p
>Update: Correct bug number to file-rc issue.
</p
>
8893 <title>More flexible firmware handling in debian-installer
</title>
8894 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
8895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
8896 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
8897 <description><p
>After a long break from debian-installer development, I finally
8898 found time today to return to the project. Having to spend less time
8899 working dependency based boot in debian, as it is almost complete now,
8900 definitely helped freeing some time.
</p
>
8902 <p
>A while back, I ran into a problem while working on Debian Edu. We
8903 include some firmware packages on the Debian Edu CDs, those needed to
8904 get disk and network controllers working. Without having these
8905 firmware packages available during installation, it is impossible to
8906 install Debian Edu on the given machine, and because our target group
8907 are non-technical people, asking them to provide firmware packages on
8908 an external medium is a support pain. Initially, I expected it to be
8909 enough to include the firmware packages on the CD to get
8910 debian-installer to find and use them. This proved to be wrong.
8911 Next, I hoped it was enough to symlink the relevant firmware packages
8912 to some useful location on the CD (tried /cdrom/ and
8913 /cdrom/firmware/). This also proved to not work, and at this point I
8914 found time to look at the debian-installer code to figure out what was
8915 going to work.
</p
>
8917 <p
>The firmware loading code is in the hw-detect package, and a closer
8918 look revealed that it would only look for firmware packages outside
8919 the installation media, so the CD was never checked for firmware
8920 packages. It would only check USB sticks, floppies and other
8921 "external
" media devices. Today I changed it to also look in the
8922 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8923 solve the problem I ran into with Debian edu. I also changed it to
8924 look in /firmware/, to make sure the installer also find firmware
8925 provided in the initrd when booting the installer via PXE, to allow us
8926 to provide the same feature in the PXE setup included in Debian
8929 <p
>To make sure firmware deb packages with a license questions are not
8930 activated without asking if the license is accepted, I extended
8931 hw-detect to look for preinst scripts in the firmware packages, and
8932 run these before activating the firmware during installation. The
8933 license question is asked using debconf in the preinst, so this should
8934 solve the issue for the firmware packages I have looked at so far.
</p
>
8936 <p
>If you want to discuss the details of these features, please
8937 contact us on debian-boot@lists.debian.org.
</p
>
8942 <title>Parallellized boot is now the default in Debian/unstable
</title>
8943 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
8944 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
8945 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
8946 <description><p
>Since this evening, parallel booting is the default in
8947 Debian/unstable for machines using dependency based boot sequencing.
8948 Apparently the testing of concurrent booting has been wider than
8949 expected, if I am to believe the
8950 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8951 on debian-devel@
</a
>, and I concluded a few days ago to move forward
8952 with the feature this weekend, to give us some time to detect any
8953 remaining problems before Squeeze is frozen. If serious problems are
8954 detected, it is simple to change the default back to sequential boot.
8955 The upload of the new sysvinit package also activate a new upstream
8958 More information about
8959 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8960 based boot sequencing
</a
> is available from the Debian wiki. It is
8961 currently possible to disable parallel booting when one run into
8962 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
8964 <blockquote
><pre
>
8966 </pre
></blockquote
>
8968 <p
>If you report any problems with dependencies in init.d scripts to
8969 the BTS, please usertag the report to get it to show up at
8970 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8971 list of usertagged bugs related to this
</a
>.
</p
>
8976 <title>Sitesummary tip: Listing MAC address of all clients
</title>
8977 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
8978 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
8979 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
8980 <description><p
>In the recent Debian Edu versions, the
8981 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
8982 system
</a
> is used to keep track of the machines in the school
8983 network. Each machine will automatically report its status to the
8984 central server after boot and once per night. The network setup is
8985 also reported, and using this information it is possible to get the
8986 MAC address of all network interfaces in the machines. This is useful
8987 to update the DHCP configuration.
</p
>
8989 <p
>To give some idea how to use sitesummary, here is a one-liner to
8990 ist all MAC addresses of all machines reporting to sitesummary. Run
8991 this on the collector host:
</p
>
8993 <blockquote
><pre
>
8994 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
8995 </pre
></blockquote
>
8997 <p
>This will list all MAC addresses assosiated with all machine, one
8998 line per machine and with space between the MAC addresses.
</p
>
9000 <p
>To allow system administrators easier job at adding static DHCP
9001 addresses for hosts, it would be possible to extend this to fetch
9002 machine information from sitesummary and update the DHCP and DNS
9003 tables in LDAP using this information. Such tool is unfortunately not
9004 written yet.
</p
>
9009 <title>systemd, an interesting alternative to upstart
</title>
9010 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9011 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9012 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9013 <description><p
>The last few days a new boot system called
9014 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9016 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9018 to the free software world. I have not yet had time to play around
9019 with it, but it seem to be a very interesting alternative to
9020 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9021 a good alternative for Debian when we are able to switch to an event
9022 based boot system. Tollef is
9023 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9024 systemd into Debian, and I look forward to seeing how well it work. I
9025 like the fact that systemd handles init.d scripts with dependency
9026 information natively, allowing them to run in parallel where upstart
9027 at the moment do not.
</p
>
9029 <p
>Unfortunately do systemd have the same problem as upstart regarding
9030 platform support. It only work on recent Linux kernels, and also need
9031 some new kernel features enabled to function properly. This means
9032 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9033 system. Not sure how that will be handled if systemd proves to be the
9034 way forward.
</p
>
9036 <p
>In the mean time, based on the
9037 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9038 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9039 decided to enable full parallel booting as the default in Debian as
9040 soon as possible (probably this weekend or early next week), to see if
9041 there are any remaining serious bugs in the init.d dependencies. A
9042 new version of the sysvinit package implementing this change is
9043 already in experimental. If all go well, Squeeze will be released
9044 with parallel booting enabled by default.
</p
>
9049 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9050 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9051 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9052 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9053 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9054 complete, so complete that it is actually possible to run all the
9055 init.d scripts in parallell based on these dependencies. If you want
9056 to test your Squeeze system, make sure
9057 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9058 based boot sequencing
</a
> is enabled, and add this line to
9059 /etc/default/rcS:
</p
>
9061 <blockquote
><pre
>
9062 CONCURRENCY=makefile
9063 </pre
></blockquote
>
9065 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9066 scripts in parallel using the dependency information stored in
9067 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9068 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9069 to try to start the kdm and gdm scripts as early as possible, and will
9070 start the facilities required by kdm or gdm as early as possible to
9071 make this happen.
</p
>
9073 <p
>Give it a try, and see if you like the result. If some services
9074 fail to start properly, it is most likely because they have incomplete
9075 init.d script dependencies in their startup script (or some of their
9076 dependent scripts have incomplete dependencies). Report bugs and get
9077 the package maintainers to fix it. :)
</p
>
9079 <p
>Running scripts in parallel could be the default in Debian when we
9080 manage to get the init.d script dependencies complete and correct. I
9081 expect we will get there in Squeeze+
1, if we get manage to test and
9082 fix the remaining issues.
</p
>
9084 <p
>If you report any problems with dependencies in init.d scripts to
9085 the BTS, please usertag the report to get it to show up at
9086 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9087 list of usertagged bugs related to this
</a
>.
</p
>
9092 <title>Debian has switched to dependency based boot sequencing
</title>
9093 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
9094 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
9095 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
9096 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
9097 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
9098 have been migrated to using dependency based boot sequencing. This
9099 conclude work me and others have been doing for the last three days.
9100 It feels great to see this finally part of the default Debian
9101 installation. Now we just need to weed out the last few problems that
9102 are bound to show up, to get everything ready for Squeeze.
</p
>
9104 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
9105 fixing the more fundamental problem of handing the event based
9106 non-predictable kernel in the early boot.
</p
>
9111 <title>Taking over sysvinit development
</title>
9112 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
9113 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
9114 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
9115 <description><p
>After several years of frustration with the lack of activity from
9116 the existing sysvinit upstream developer, I decided a few weeks ago to
9117 take over the package and become the new upstream. The number of
9118 patches to track for the Debian package was becoming a burden, and the
9119 lack of synchronization between the distribution made it hard to keep
9120 the package up to date.
</p
>
9122 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9123 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9124 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9125 and Fedora), based on the patches currently in use in these
9126 distributions. We Debian maintainers plan to move to this tarball as
9127 the new upstream as soon as we find time to do the merge. Since the
9128 new tarball was created, we agreed with Werner at SuSe to make a new
9129 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
9130 development there. The project is registered and currently waiting
9131 for approval by the Savannah administrators, and as soon as it is
9132 approved, we will import the old versions from svn and continue
9133 working on the future release.
</p
>
9135 <p
>It is a bit ironic that this is done now, when some of the involved
9136 distributions are moving to upstart as a syvinit replacement.
</p
>
9141 <title>Debian boots quicker and quicker
</title>
9142 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
9143 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
9144 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
9145 <description><p
>I spent Monday and tuesday this week in London with a lot of the
9146 people involved in the boot system on Debian and Ubuntu, to see if we
9147 could find more ways to speed up the boot system. This was an Ubuntu
9149 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9150 gathering
</a
>. It was quite productive. We also discussed the future
9151 of boot systems, and ways to handle the increasing number of boot
9152 issues introduced by the Linux kernel becoming more and more
9153 asynchronous and event base. The Ubuntu approach using udev and
9154 upstart might be a good way forward. Time will show.
</p
>
9156 <p
>Anyway, there are a few ways at the moment to speed up the boot
9157 process in Debian. All of these should be applied to get a quick
9162 <li
>Use dash as /bin/sh.
</li
>
9164 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9165 clock is in UTC.
</li
>
9167 <li
>Install and activate the insserv package to enable
9168 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9169 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9173 These points are based on the Google summer of code work done by
9174 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9177 <p
>Support for makefile-style concurrency during boot was uploaded to
9178 unstable yesterday. When we tested it, we were able to cut
6 seconds
9179 from the boot sequence. It depend on very correct dependency
9180 declaration in all init.d scripts, so I expect us to find edge cases
9181 where the dependences in some scripts are slightly wrong when we start
9182 using this.
</p
>
9184 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9185 introduced by Raphael Geissert today, one that could affect the
9186 startup speed as well. Instead of starting some scripts concurrently
9187 from rcS.d/ and another set of scripts from rc2.d/, it would be
9188 possible to run a of them in the same process. A quick way to test
9189 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9190 insserv
'. Will need to test if that work. :)
</p
>
9195 <title>BSAs påstander om piratkopiering møter motstand
</title>
9196 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
9197 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
9198 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
9199 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
9200 programvareselskapene som Microsoft og Apple, publisert en rapport der
9201 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9202 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9204 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
9205 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
9206 dagene. Et spesielt interessant kommentar fra Sverige,
9207 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
9208 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
9211 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
9212 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9213 företag.
"Man bör nog kanske inte se de här siffrorna som helt
9214 exakta
", säger BSAs Sverigechef John Hugosson.
9217 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
9218 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
9219 piracy figures need a shot of reality
</a
> og
<a
9220 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
9221 Copyright Treaty Work?
</a
></p
>
9223 <p
>Fant lenkene via
<a
9224 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
9225 på Slashdot
</a
>.
</p
>
9230 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
9231 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
9232 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
9233 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
9234 <description><p
>Kom over
9235 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
9236 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9237 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9238 jobber til daglig. En rask opptelling forteller meg at vi har
490
9239 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
9240 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
9241 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
9246 <title>Kryptert harddisk - naturligvis
</title>
9247 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
9248 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
9249 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
9250 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
9251 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
9252 når en tar tap av arbeidstid, fortrolige dokumenter,
9253 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9254 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9255 til at jeg har kryptert harddisken på både kontormaskinen og min
9256 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9257 komme på avveie, den første informasjon relatert til jobben min ved
9258 Universitetet i Oslo, og den andre relatert til blant annet
9259 foreningsarbeide. Kryptering av diskene gjør at det er lite
9260 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9261 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9262 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9263 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9264 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9265 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9266 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9267 det er gjort slik jeg gjør det er minimale, og gevinstene er
9268 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9269 maskinen reinstalleres og alt er tapt.
</p
>
9271 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9272 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9273 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9274 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9275 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9276 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9277 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9278 betydelige.
</p
>
9283 <title>Two projects that have improved the quality of free software a lot
</title>
9284 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
9285 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
9286 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
9287 <description><p
>There are two software projects that have had huge influence on the
9288 quality of free software, and I wanted to mention both in case someone
9289 do not yet know them.
</p
>
9291 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
9292 tool to detect and expose errors in the memory handling of programs.
9293 It is easy to use, all one need to do is to run
'valgrind program
',
9294 and it will report any problems on stdout. It is even better if the
9295 program include debug information. With debug information, it is able
9296 to report the source file name and line number where the problem
9297 occurs. It can report things like
'reading past memory block in file
9298 X line N, the memory block was allocated in file Y, line M
', and
9299 'using uninitialised value in control logic
'. This tool has made it
9300 trivial to investigate reproducible crash bugs in programs, and have
9301 reduced the number of this kind of bugs in free software a lot.
9303 <p
>The second one is
9304 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
9305 a source code checker. It is able to process the source of a program
9306 and find problems in the logic without running the program. It
9307 started out as the Stanford Checker and became well known when it was
9308 used to find bugs in the Linux kernel. It is now a commercial tool
9309 and the company behind it is running
9310 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
9311 free software community, where a lot of free software projects get
9312 their source checked for free. Several thousand defects have been
9313 found and fixed so far. It can find errors like
'lock L taken in file
9314 X line N is never released if exiting in line M
', or
'the code in file
9315 Y lines O to P can never be executed
'. The projects included in the
9316 community service project have managed to get rid of a lot of
9317 reliability problems thanks to Coverity.
</p
>
9319 <p
>I believe tools like this, that are able to automatically find
9320 errors in the source, are vital to improve the quality of software and
9321 make sure we can get rid of the crashing and failing software we are
9322 surrounded by today.
</p
>
9327 <title>No patch is not better than a useless patch
</title>
9328 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
9329 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
9330 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
9331 <description><p
>Julien Blache
9332 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
9333 patch is better than a useless patch
</a
>. I completely disagree, as a
9334 patch allow one to discuss a concrete and proposed solution, and also
9335 prove that the issue at hand is important enough for someone to spent
9336 time on fixing it. No patch do not provide any of these positive
9337 properties.
</p
>
9342 <title>Standardize on protocols and formats, not vendors and applications
</title>
9343 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
9344 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
9345 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
9346 <description><p
>Where I work at the University of Oslo, one decision stand out as a
9347 very good one to form a long lived computer infrastructure. It is the
9348 simple one, lost by many in todays computer industry: Standardize on
9349 open network protocols and open exchange/storage formats, not applications.
9350 Applications come and go, while protocols and files tend to stay, and
9351 thus one want to make it easy to change application and vendor, while
9352 avoiding conversion costs and locking users to a specific platform or
9353 application.
</p
>
9355 <p
>This approach make it possible to replace the client applications
9356 independently of the server applications. One can even allow users to
9357 use several different applications as long as they handle the selected
9358 protocol and format. In the normal case, only one client application
9359 is recommended and users only get help if they choose to use this
9360 application, but those that want to deviate from the easy path are not
9361 blocked from doing so.
</p
>
9363 <p
>It also allow us to replace the server side without forcing the
9364 users to replace their applications, and thus allow us to select the
9365 best server implementation at any moment, when scale and resouce
9366 requirements change.
</p
>
9368 <p
>I strongly recommend standardizing - on open network protocols and
9369 open formats, but I would never recommend standardizing on a single
9370 application that do not use open network protocol or open formats.
</p
>
9375 <title>Returning from Skolelinux developer gathering
</title>
9376 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
9377 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
9378 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
9379 <description><p
>I
'm sitting on the train going home from this weekends Debian
9380 Edu/Skolelinux development gathering. I got a bit done tuning the
9381 desktop, and looked into the dynamic service location protocol
9382 implementation avahi. It look like it could be useful for us. Almost
9383 30 people participated, and I believe it was a great environment to
9384 get to know the Skolelinux system. Walter Bender, involved in the
9385 development of the Sugar educational platform, presented his stuff and
9386 also helped me improve my OLPC installation. He also showed me that
9387 his Turtle Art application can be used in standalone mode, and we
9388 agreed that I would help getting it packaged for Debian. As a
9389 standalone application it would be great for Debian Edu. We also
9390 tried to get the video conferencing working with two OLPCs, but that
9391 proved to be too hard for us. The application seem to need more work
9392 before it is ready for me. I look forward to getting home and relax
9398 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
9399 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
9400 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
9401 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
9402 <description><p
>The state of standardized LDAP schemas on Linux is far from
9403 optimal. There is RFC
2307 documenting one way to store NIS maps in
9404 LDAP, and a modified version of this normally called RFC
2307bis, with
9405 some modifications to be compatible with Active Directory. The RFC
9406 specification handle the content of a lot of system databases, but do
9407 not handle DNS zones and DHCP configuration.
</p
>
9409 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
9410 we would like to store information about users, SMB clients/hosts,
9411 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9412 and LTSP configuration in LDAP. These objects have a lot in common,
9413 but with the current LDAP schemas it is not possible to have one
9414 object per entity. For example, one need to have at least three LDAP
9415 objects for a given computer, one with the SMB related stuff, one with
9416 DNS information and another with DHCP information. The schemas
9417 provided for DNS and DHCP are impossible to combine into one LDAP
9418 object. In addition, it is impossible to implement quick queries for
9419 netgroup membership, because of the way NIS triples are implemented.
9420 It just do not scale. I believe it is time for a few RFC
9421 specifications to cleam up this mess.
</p
>
9423 <p
>I would like to have one LDAP object representing each computer in
9424 the network, and this object can then keep the SMB (ie host key), DHCP
9425 (mac address/name) and DNS (name/IP address) settings in one place.
9426 It need to be efficently stored to make sure it scale well.
</p
>
9428 <p
>I would also like to have a quick way to map from a user or
9429 computer and to the net group this user or computer is a member.
</p
>
9431 <p
>Active Directory have done a better job than unix heads like myself
9432 in this regard, and the unix side need to catch up. Time to start a
9433 new IETF work group?
</p
>
9438 <title>Endelig er Debian Lenny gitt ut
</title>
9439 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
9440 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
9441 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
9442 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
9443 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
9444 Et langt steg videre for Debian-prosjektet, og en rekke nye
9445 programpakker blir nå tilgjengelig for de av oss som bruker den
9446 stabile utgaven av Debian. Neste steg er nå å få
9447 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
9448 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
9449 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9450 slippes løs på skolene. Takk til alle debian-utviklerne som har
9451 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9452 bootsekvens tilgjengelig i stabil utgave, vha pakken
9453 <tt
>insserv
</tt
>.
</p
>
9458 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
9459 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
9460 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
9461 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
9462 <description><p
>This weekend we had a small developer gathering for Debian Edu in
9463 Oslo. Most of Saturday was used for the general assemly for the
9464 member organization, but the rest of the weekend I used to tune the
9465 LTSP installation. LTSP now work out of the box on the
10-network.
9466 Acer Aspire One proved to be a very nice thin client, with both
9467 screen, mouse and keybard in a small box. Was working on getting the
9468 diskless workstation setup configured out of the box, but did not
9469 finish it before the weekend was up.
</p
>
9471 <p
>Did not find time to look at the
4 VGA cards in one box we got from
9472 the Brazilian group, so that will have to wait for the next
9473 development gathering. Would love to have the Debian Edu installer
9474 automatically detect and configure a multiseat setup when it find one
9475 of these cards.
</p
>
9480 <title>The sorry state of multimedia browser plugins in Debian
</title>
9481 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
9482 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
9483 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
9484 <description><p
>Recently I have spent some time evaluating the multimedia browser
9485 plugins available in Debian Lenny, to see which one we should use by
9486 default in Debian Edu. We need an embedded video playing plugin with
9487 control buttons to pause or stop the video, and capable of streaming
9488 all the multimedia content available on the web. The test results and
9489 notes are available on
9490 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
9491 Debian wiki
</a
>. I was surprised how few of the plugins are able to
9492 fill this need. My personal video player favorite, VLC, has a really
9493 bad plugin which fail on a lot of the test pages. A lot of the MIME
9494 types I would expect to work with any free software player (like
9495 video/ogg), just do not work. And simple formats like the
9496 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
9497 totem and vlc plugins. I hope the situation will improve soon. No
9498 wonder sites use the proprietary Adobe flash to play video.
</p
>
9500 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
9501 be the only one fitting our needs. :/
</p
>