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>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
11 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
13 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
14 <description><p
>This summer, I read a great article
15 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
16 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
17 how to profile multi-threaded programs. It presented a system for
18 profiling software by running experiences in the running program,
19 testing how run time performance is affected by
"speeding up
" parts of
20 the code to various degrees compared to a normal run. It does this by
21 slowing down parallel threads while the
"faster up
" code is running
22 and measure how this affect processing time. The processing time is
23 measured using probes inserted into the code, either using progress
24 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
25 can also measure unmodified code by measuring complete the program
26 runtime and running the program several times instead.
</p
>
28 <p
>The project and presentation was so inspiring that I would like to
29 get the system into Debian. I
30 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
31 a WNPP request for it
</a
> and contacted upstream to try to make the
32 system ready for Debian by sending patches. The build process need to
33 be changed a bit to avoid running
'git clone
' to get dependencies, and
34 to include the JavaScript web page used to visualize the collected
35 profiling information included in the source package.
36 But I expect that should work out fairly soon.
</p
>
38 <p
>The way the system work is fairly simple. To run an coz experiment
39 on a binary with debug symbols available, start the program like this:
41 <p
><blockquote
><pre
>
42 coz run --- program-to-run
43 </pre
></blockquote
></p
>
45 <p
>This will create a text file profile.coz with the instrumentation
46 information. To show what part of the code affect the performance
47 most, use a web browser and either point it to
48 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
49 or use the copy from git (in the gh-pages branch). Check out this web
50 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
51 profiling more useful you include
&lt;coz.h
&gt; and insert the
52 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
53 code, rebuild and run the profiler. This allow coz to do more
54 targeted experiments.
</p
>
56 <p
>A video published by ACM
57 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
58 Coz profiler
</a
> is available from Youtube. There is also a paper
59 from the
25th Symposium on Operating Systems Principles available
61 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
62 finding code that counts with causal profiling
</a
>.
</p
>
64 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
65 for Coz is available from github. It will only build with clang
67 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
68 feature missing in GCC
</a
>, but I
've submitted
69 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
70 it
</a
> and hope it will be included in the upstream source soon.
</p
>
72 <p
>Please get in touch if you, like me, would like to see this piece
73 of software in Debian. I would very much like some help with the
74 packaging effort, as I lack the in depth knowledge on how to package
75 C++ libraries.
</p
>
80 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
81 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
82 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
83 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
84 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
85 to be a slight challenge. Here is the recipe if I ever need to do it
86 again. It all started by me wanting to try the recipe to set up
87 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
88 hardened Android installation
</a
> from the Tor project blog on a
89 device I had access to. It is a old mobile phone with a broken
90 microphone The initial idea had been to just
91 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
92 CyanogenMod on it
</a
>, but did not quite find time to start on it
93 until a few days ago.
</p
>
95 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
96 loader (press volume down and power at the same time), (
2) select
97 'fastboot
' before (
3) connecting the device via USB to a Linux
98 machine, (
4) request the device identifier token by running
'fastboot
99 oem get_identifier_token
', (
5) request the device unlocking key using
100 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
101 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
103 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
104 or newer, and the device I was working on had
2.00.0027. This
105 apparently can be easily fixed by downloading a Windows program and
106 running it on your Windows machine, if you accept the terms Microsoft
107 require you to accept to use Windows - which I do not. So I had to
108 come up with a different approach. I got a lot of help from AndyCap
109 on #nuug, and would not have been able to get this working without
112 <p
>First I needed to extract the hboot firmware from
113 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
114 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
115 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
116 project named unruu
</a
> using libunshield. The unshield tool did not
117 recognise the file format, but unruu worked and extracted rom.zip,
118 containing the new hboot firmware and a text file describing which
119 devices it would work for.
</p
>
121 <p
>Next, I needed to get the new firmware into the device. For this I
122 followed some instructions
123 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
124 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
125 machine with Debian testing:
</p
>
128 adb reboot-bootloader
129 fastboot oem rebootRUU
130 fastboot flash zip rom.zip
131 fastboot flash zip rom.zip
133 </pre
></p
>
135 <p
>The flash command apparently need to be done twice to take effect,
136 as the first is just preparations and the second one do the flashing.
137 The adb command is just to get to the boot loader menu, so turning the
138 device on while holding volume down and the power button should work
141 <p
>With the new hboot version in place I could start following the
142 instructions on the HTC developer web site. I got the device token
146 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
149 <p
>And once I got the unlock code via email, I could use it like
153 fastboot flash unlocktoken Unlock_code.bin
154 </pre
></p
>
156 <p
>And with that final step in place, the phone was unlocked and I
157 could start stuffing the software of my own choosing into the device.
158 So far I only inserted a replacement recovery image to wipe the phone
159 before I start. We will see what happen next. Perhaps I should
160 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
165 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
166 <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>
167 <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>
168 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
169 <description><p
>For a while now, I have wanted to test
170 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
171 said to provide end to end encrypted communication and several of my
172 friends and family are already using it. As I by choice do not own a
173 mobile phone, this proved to be harder than expected. And I wanted to
174 have the source of the client and know that it was the code used on my
175 machine. But yesterday I managed to get it working. I used the
176 Github source, compared it to the source in
177 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
178 Signal Chrome app
</a
> available from the Chrome web store, applied
179 patches to use the production Signal servers, started the app and
180 asked for the hidden
"register without a smart phone
" form. Here is
181 the recipe how I did it.
</p
>
183 <p
>First, I fetched the Signal desktop source from Github, using
186 git clone https://github.com/WhisperSystems/Signal-Desktop.git
189 <p
>Next, I patched the source to use the production servers, to be
190 able to talk to other Signal users:
</p
>
193 cat
&lt;
&lt;EOF | patch -p0
194 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
195 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
196 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
201 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
202 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
203 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
204 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
206 window.getSocketStatus = function() {
207 if (messageReceiver) {
208 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
209 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
210 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
213 'use strict
';
214 - var BUILD_EXPIRATION =
0;
215 + var BUILD_EXPIRATION =
1474492690000;
217 window.extension = window.extension || {};
222 <p
>The first part is changing the servers, and the second is updating
223 an expiration timestamp. This timestamp need to be updated regularly.
224 It is set
90 days in the future by the build process (Gruntfile.js).
225 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
227 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
228 script to launch Signal in Chromium.
</p
>
235 --proxy-server=
"socks://localhost:
9050" \
236 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
239 <p
> The script start the app and configure Chromium to use the Tor
240 SOCKS5 proxy to make sure those controlling the Signal servers (today
241 Amazon and Whisper Systems) as well as those listening on the lines
242 will have a harder time location my laptop based on the Signal
243 connections if they use source IP address.
</p
>
245 <p
>When the script starts, one need to follow the instructions under
246 "Standalone Registration
" in the CONTRIBUTING.md file in the git
247 repository. I right clicked on the Signal window to get up the
248 Chromium debugging tool, visited the
'Console
' tab and wrote
249 'extension.install(
"standalone
")
' on the console prompt to get the
250 registration form. Then I entered by land line phone number and
251 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
252 repeated the verification code three times. After entering the number
253 into the verification code field in the form, I could start using
254 Signal from my laptop.
256 <p
>As far as I can tell, The Signal app will leak who is talking to
257 whom and thus who know who to those controlling the central server,
258 but such leakage is hard to avoid with a centrally controlled server
259 setup. It is something to keep in mind when using Signal - the
260 content of your chats are harder to intercept, but the meta data
261 exposing your contact network is available to people you do not know.
262 So better than many options, but not great. And sadly the usage is
263 connected to my land line, thus allowing those controlling the server
264 to associate it to my home and person. I would prefer it if only
265 those I knew could tell who I was on Signal. There are options
266 avoiding such information leakage, but most of my friends are not
267 using them, so I am stuck with Signal for now.
</p
>
272 <title>The new
"best
" multimedia player in Debian?
</title>
273 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
274 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
275 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
276 <description><p
>When I set out a few weeks ago to figure out
277 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
278 multimedia player in Debian claimed to support most file formats /
279 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
280 the various players claimed support for. The range was from
55 to
130
281 MIME types. I suspect most media formats are supported by all
282 players, but this is not really reflected in the MimeTypes values in
283 their desktop files. There are probably also some bogus MIME types
284 listed, but it is hard to identify which one this is.
</p
>
286 <p
>Anyway, in the mean time I got in touch with upstream for some of
287 the players suggesting to add more MIME types to their desktop files,
288 and decided to spend some time myself improving the situation for my
289 favorite media player VLC. The fixes for VLC entered Debian unstable
290 yesterday. The complete list of MIME types can be seen on the
291 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
292 player MIME type support status
</a
> Debian wiki page.
</p
>
294 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
295 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
296 kmplayer. I am sure some of the other players desktop files support
297 several of the formats currently listed as working only with vlc,
298 toten and parole.
</p
>
300 <p
>A sad observation is that only
14 MIME types are listed as
301 supported by all the tested multimedia players in Debian in their
302 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
303 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
304 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
305 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
306 it sad that video/ogg and video/webm is not supported by all the media
307 players in Debian. As far as I can tell, all of them can handle both
313 <title>A program should be able to open its own files on Linux
</title>
314 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
315 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
316 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
317 <description><p
>Many years ago, when koffice was fresh and with few users, I
318 decided to test its presentation tool when making the slides for a
319 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
320 wrote the first draft of the slides, saved the result and went to bed
321 the day before I would give the talk. The next day I took a plane to
322 the location where the meeting should take place, and on the plane I
323 started up koffice again to polish the talk a bit, only to discover
324 that kpresenter refused to load its own data file. I cursed a bit and
325 started making the slides again from memory, to have something to
326 present when I arrived. I tested that the saved files could be
327 loaded, and the day seemed to be rescued. I continued to polish the
328 slides until I suddenly discovered that the saved file could no longer
329 be loaded into kpresenter. In the end I had to rewrite the slides
330 three times, condensing the content until the talk became shorter and
331 shorter. After the talk I was able to pinpoint the problem
&ndash;
332 kpresenter wrote inline images in a way itself could not understand.
333 Eventually that bug was fixed and kpresenter ended up being a great
334 program to make slides. The point I
'm trying to make is that we
335 expect a program to be able to load its own data files, and it is
336 embarrassing to its developers if it can
't.
</p
>
338 <p
>Did you ever experience a program failing to load its own data
339 files from the desktop file browser? It is not a uncommon problem. A
340 while back I discovered that the screencast recorder
341 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
342 browser would refuse to open. No video player claimed to understand
343 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
344 returning the application/ogg MIME type, which no video player I had
345 installed listed as a MIME type they would understand. I asked for
346 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
347 behavour
</a
> and use the MIME type video/ogg instead. I also asked
348 several video players to add video/ogg to their desktop files, to give
349 the file browser an idea what to do about Ogg Theora files. After a
350 while, the desktop file browsers in Debian started to handle the
351 output from gtk-recordmydesktop properly.
</p
>
353 <p
>But history repeats itself. A few days ago I tested the music
354 system Rosegarden again, and I discovered that the KDE and xfce file
355 browsers did not know what to do with the Rosegarden project files
356 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
357 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
358 included in the next upload. To increase the chance of me remembering
359 how to fix the problem next time some program fail to load its files
360 from the file browser, here are some notes on how to fix it.
</p
>
362 <p
>The file browsers in Debian in general operates on MIME types.
363 There are two sources for the MIME type of a given file. The output from
364 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
365 shared MIME type registry (under /usr/share/mime/). The file MIME
366 type is mapped to programs supporting the MIME type, and this
367 information is collected from
368 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
369 desktop files
</a
> available in /usr/share/applications/. If there is
370 one desktop file claiming support for the MIME type of the file, it is
371 activated when asking to open a given file. If there are more, one
372 can normally select which one to use by right-clicking on the file and
373 selecting the wanted one using
'Open with
' or similar. In general
374 this work well. But it depend on each program picking a good MIME
376 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
377 MIME type registered with IANA
</a
>), file and/or the shared MIME
378 registry recognizing the file and the desktop file to list the MIME
379 type in its list of supported MIME types.
</p
>
381 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
382 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
383 Shared MIME database
</a
> look like this:
</p
>
385 <p
><blockquote
><pre
>
386 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
387 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
388 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
389 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
390 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
391 &lt;glob pattern=
"*.rg
"/
&gt;
392 &lt;/mime-type
&gt;
393 &lt;/mime-info
&gt;
394 </pre
></blockquote
></p
>
396 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
397 (it is a gzipped XML file). Note, it is much better to use an
398 official MIME type registered with IANA than it is to make up ones own
399 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
401 <p
>The desktop file of the rosegarden program failed to list
402 audio/x-rosegarden in its list of supported MIME types, causing the
403 file browsers to have no idea what to do with *.rg files:
</p
>
405 <p
><blockquote
><pre
>
406 % grep Mime /usr/share/applications/rosegarden.desktop
407 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
408 X-KDE-NativeMimeType=audio/x-rosegarden-composition
410 </pre
></blockquote
></p
>
412 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
413 MimeType= line.
</p
>
415 <p
>If you run into a file which fail to open the correct program when
416 selected from the file browser, please check out the output from
417 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
418 MIME type is registered somewhere under /usr/share/mime/ and check
419 that some desktop file under /usr/share/applications/ is claiming
420 support for this MIME type. If not, please report a bug to have it
426 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
427 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
428 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
429 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
430 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
431 system
</a
> is a user-focused solution in Debian for handling hardware
432 related packages. The idea is to have a database of mappings between
433 hardware and packages, and pop up a dialog suggesting for the user to
434 install the packages to use a given hardware dongle. Some use cases
435 are when you insert a Yubikey, it proposes to install the software
436 needed to control it; when you insert a braille reader list it
437 proposes to install the packages needed to send text to the reader;
438 and when you insert a ColorHug screen calibrator it suggests to
439 install the driver for it. The system work well, and even have a few
440 command line tools to install firmware packages and packages for the
441 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
443 <p
>The system was initially written using aptdaemon, because I found
444 good documentation and example code on how to use it. But aptdaemon
445 is going away and is generally being replaced by
446 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
447 so Isenkram needed a rewrite. And today, thanks to the great patch
448 from my college Sunil Mohan Adapa in the FreedomBox project, the
449 rewrite finally took place. I
've just uploaded a new version of
450 Isenkram into Debian Unstable with the patch included, and the default
451 for the background daemon is now to use PackageKit. To check it out,
452 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
453 and see if it is recognised.
</p
>
455 <p
>If you want to know what kind of packages isenkram would propose for
456 the machine it is running on, you can check out the isenkram-lookup
457 program. This is what it look like on a Thinkpad X230:
</p
>
459 <p
><blockquote
><pre
>
475 </pre
></blockquote
></p
>
477 <p
>The hardware mappings come from several places. The preferred way
478 is for packages to announce their hardware support using
479 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
480 cross distribution appstream system
</a
>.
482 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
483 blog posts about isenkram
</a
> to learn how to do that.
</p
>
488 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
489 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
490 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
491 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
492 <description><p
>Yesterday I updated the
493 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
494 package in Debian
</a
> with a few patches sent to me by skilled and
495 enterprising users. There were some nice user and visible changes.
496 First of all, both desktop menu entries now work. A design flaw in
497 one of the script made the history graph fail to show up (its PNG was
498 dumped in ~/.xsession-errors) if no controlling TTY was available.
499 The script worked when called from the command line, but not when
500 called from the desktop menu. I changed this to look for a DISPLAY
501 variable or a TTY before deciding where to draw the graph, and now the
502 graph window pop up as expected.
</p
>
504 <p
>The next new feature is a discharge rate estimator in one of the
505 graphs (the one showing the last few hours). New is also the user of
506 colours showing charging in blue and discharge in red. The percentages
507 of this graph is relative to last full charge, not battery design
510 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
512 <p
>The other graph show the entire history of the collected battery
513 statistics, comparing it to the design capacity of the battery to
514 visualise how the battery life time get shorter over time. The red
515 line in this graph is what the previous graph considers
100 percent:
517 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
519 <p
>In this graph you can see that I only charge the battery to
80
520 percent of last full capacity, and how the capacity of the battery is
521 shrinking. :(
</p
>
523 <p
>The last new feature is in the collector, which now will handle
524 more hardware models. On some hardware, Linux power supply
525 information is stored in /sys/class/power_supply/ACAD/, while the
526 collector previously only looked in /sys/class/power_supply/AC/. Now
527 both are checked to figure if there is power connected to the
530 <p
>If you are interested in how your laptop battery is doing, please
532 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
533 in Debian unstable, or rebuild it on Jessie to get it working on
534 Debian stable. :) The upstream source is available from
<a
535 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
536 Patches are very welcome.
</p
>
538 <p
>As usual, if you use Bitcoin and want to show your support of my
539 activities, please send Bitcoin donations to my address
540 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
545 <title>Debian now with ZFS on Linux included
</title>
546 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
547 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
548 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
549 <description><p
>Today, after many years of hard work from many people,
550 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
551 Debian. The package status can be seen on
552 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
553 for zfs-linux
</a
>. and
554 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
555 team status page
</a
>. If you want to help out, please join us.
556 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
557 source code
</a
> is available via git on Alioth. It would also be
558 great if you could help out with
559 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
560 it is an important piece of the puzzle to get ZFS working.
</p
>
565 <title>What is the best multimedia player in Debian?
</title>
566 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
567 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
568 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
569 <description><p
><strong
>Where I set out to figure out which multimedia player in
570 Debian claim support for most file formats.
</strong
></p
>
572 <p
>A few years ago, I had a look at the media support for Browser
573 plugins in Debian, to get an idea which plugins to include in Debian
574 Edu. I created a script to extract the set of supported MIME types
575 for each plugin, and used this to find out which multimedia browser
576 plugin supported most file formats / media types.
577 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
578 result
</a
> can still be seen on the Debian wiki, even though it have
579 not been updated for a while. But browser plugins are less relevant
580 these days, so I thought it was time to look at standalone
583 <p
>A few days ago I was tired of VLC not being listed as a viable
584 player when I wanted to play videos from the Norwegian National
585 Broadcasting Company, and decided to investigate why. The cause is a
586 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
587 desktop file
</a
>. In the process I wrote a script to compare the set
588 of MIME types announced in the desktop file and the browser plugin,
589 only to discover that there is quite a large difference between the
590 two for VLC. This discovery made me dig up the script I used to
591 compare browser plugins, and adjust it to compare desktop files
592 instead, to try to figure out which multimedia player in Debian
593 support most file formats.
</p
>
595 <p
>The result can be seen on the Debian Wiki, as
596 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
597 table listing all MIME types supported by one of the packages included
598 in the table
</a
>, with the package supporting most MIME types being
599 listed first in the table.
</p
>
601 </p
>The best multimedia player in Debian? It is totem, followed by
602 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
603 kmplayer. Time for the other players to update their announced MIME
609 <title>The Pyra - handheld computer with Debian preinstalled
</title>
610 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
611 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
612 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
613 <description>A friend of mine made me aware of
614 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
615 handheld computer which will be delivered with Debian preinstalled. I
616 would love to get one of those for my birthday. :)
</p
>
618 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
619 plugs and many others connectors, and include a full keyboard and a
5"
620 LCD touch screen. The
6000mAh battery is claimed to provide a whole
621 day of battery life time, but I have not seen any independent tests
622 confirming this. The vendor is still collecting preorders, and the
623 last I heard last night was that
22 more orders were needed before
624 production started.
</p
>
626 <p
>As far as I know, this is the first handheld preinstalled with
627 Debian. Please let me know if you know of any others. Is it the
628 first computer being sold with Debian preinstalled?
</p
>
633 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
634 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
636 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
637 <description><p
>During this weekends
638 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
639 squashing party and developer gathering
</a
>, we decided to do our part
640 to make sure there are good books about Debian available in Norwegian
641 Bokmål, and got in touch with the people behind the
642 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
643 project
</a
> to get started. If you want to help out, please start
645 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
646 hosted weblate project page
</a
>, and get in touch using
647 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
648 translators mailing list
</a
>. Please also check out
649 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
650 contributors
</a
>.
</p
>
652 <p
>The book is already available on paper in English, French and
653 Japanese, and our goal is to get it available on paper in Norwegian
654 Bokmål too. In addition to the paper edition, there are also EPUB and
655 Mobi versions available. And there are incomplete translations
656 available for many more languages.
</p
>
661 <title>One in two hundred Debian users using ZFS on Linux?
</title>
662 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
663 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
664 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
665 <description><p
>Just for fun I had a look at the popcon number of ZFS related
666 packages in Debian, and was quite surprised with what I found. I use
667 ZFS myself at home, but did not really expect many others to do so.
668 But I might be wrong.
</p
>
670 <p
>According to
671 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
672 results for spl-linux
</a
>, there are
1019 Debian installations, or
673 0.53% of the population, with the package installed. As far as I know
674 the only use of the spl-linux package is as a support library for ZFS
675 on Linux, so I use it here as proxy for measuring the number of ZFS
676 installation on Linux in Debian. In the kFreeBSD variant of Debian
677 the ZFS feature is already available, and there
678 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
679 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
680 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
682 <p
>But even though the Debian project leader Lucas Nussbaum
683 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
684 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
685 cleared, the package is still not in Debian. The package is again in
686 the NEW queue. Several uploads have been rejected so far because the
687 debian/copyright file was incomplete or wrong, but there is no reason
688 to give up. The current status can be seen on
689 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
690 team status page
</a
>, and
691 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
692 source code
</a
> is available on Alioth.
</p
>
694 <p
>As I want ZFS to be included in next version of Debian to make sure
695 my home server can function in the future using only official Debian
696 packages, and the current blocker is to get the debian/copyright file
697 accepted by the FTP masters in Debian, I decided a while back to try
698 to help out the team. This was the background for my blog post about
699 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
700 updating and checking debian/copyright semi-automatically
</a
>, and I
701 used the techniques I explored there to try to find any errors in the
702 copyright file. It is not very easy to check every one of the around
703 2000 files in the source package, but I hope we this time got it
704 right. If you want to help out, check out the git source and try to
705 find missing entries in the debian/copyright file.
</p
>
710 <title>Full battery stats collector is now available in Debian
</title>
711 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
712 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
713 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
714 <description><p
>Since this morning, the battery-stats package in Debian include an
715 extended collector that will collect the complete battery history for
716 later processing and graphing. The original collector store the
717 battery level as percentage of last full level, while the new
718 collector also record battery vendor, model, serial number, design
719 full level, last full level and current battery level. This make it
720 possible to predict the lifetime of the battery as well as visualise
721 the energy flow when the battery is charging or discharging.
</p
>
723 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
724 in the version
0.5.1 package in unstable. Get the new battery level graph
725 and lifetime prediction by running:
728 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
729 </pre
></p
>
731 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
733 <p
>The flow in/out of the battery can be seen by running (no menu
734 entry yet):
</p
>
737 /usr/share/battery-stats/battery-stats-graph-flow
738 </pre
></p
>
740 <p
>I
'm not quite happy with the way the data is visualised, at least
741 when there are few data points. The graphs look a bit better with a
742 few years of data.
</p
>
744 <p
>A while back one important feature I use in the battery stats
745 collector broke in Debian. The scripts in
746 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
747 suspect it happened when Jessie started using systemd, but I do not
748 know. The issue is reported as
749 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
750 pm-utils. I managed to work around it by adding an udev rule to call
751 the collector script every time the power connector is connected and
752 disconnected. With this fix in place it was finally time to make a
753 new release of the package, and get it into Debian.
</p
>
755 <p
>If you are interested in how your laptop battery is doing, please
757 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
758 in Debian unstable, or rebuild it on Jessie to get it working on
759 Debian stable. :) The upstream source is available from
760 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
761 As always, patches are very welcome.
</p
>
766 <title>Making battery measurements a little easier in Debian
</title>
767 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
768 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
769 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
770 <description><p
>Back in September, I blogged about
771 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
772 system I wrote to collect statistics about my laptop battery
</a
>, and
773 how it showed the decay and death of this battery (now replaced). I
774 created a simple deb package to handle the collection and graphing,
775 but did not want to upload it to Debian as there were already
776 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
777 package in Debian
</a
> that should do the same thing, and I did not see
778 a point of uploading a competing package when battery-stats could be
779 fixed instead. I reported a few bugs about its non-function, and
780 hoped someone would step in and fix it. But no-one did.
</p
>
782 <p
>I got tired of waiting a few days ago, and took matters in my own
783 hands. The end result is that I am now the new upstream developer of
784 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
785 battery-stats in Debian, and the package in Debian unstable is finally
786 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
787 information provided by the Linux kernel. If you install the
788 battery-stats package from unstable now, you will be able to get a
789 graph of the current battery fill level, to get some idea about the
790 status of the battery. The source package build and work just fine in
791 Debian testing and stable (and probably oldstable too, but I have not
792 tested). The default graph you get for that system look like this:
</p
>
794 <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
>
796 <p
>My plans for the future is to merge my old scripts into the
797 battery-stats package, as my old scripts collected a lot more details
798 about the battery. The scripts are merged into the upstream
799 battery-stats git repository already, but I am not convinced they work
800 yet, as I changed a lot of paths along the way. Will have to test a
801 bit more before I make a new release.
</p
>
803 <p
>I will also consider changing the file format slightly, as I
804 suspect the way I combine several values into one field might make it
805 impossible to know the type of the value when using it for processing
806 and graphing.
</p
>
808 <p
>If you would like I would like to keep an close eye on your laptop
809 battery, check out the battery-stats package in
810 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
812 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
813 I would love some help to improve the system further.
</p
>
818 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
819 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
820 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
821 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
822 <description><p
>Making packages for Debian requires quite a lot of attention to
823 details. And one of the details is the content of the
824 debian/copyright file, which should list all relevant licenses used by
825 the code in the package in question, preferably in
826 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
827 readable DEP5 format
</a
>.
</p
>
829 <p
>For large packages with lots of contributors it is hard to write
830 and update this file manually, and if you get some detail wrong, the
831 package is normally rejected by the ftpmasters. So getting it right
832 the first time around get the package into Debian faster, and save
833 both you and the ftpmasters some work.. Today, while trying to figure
834 out what was wrong with
835 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
836 zfsonlinux copyright file
</a
>, I decided to spend some time on
837 figuring out the options for doing this job automatically, or at least
838 semi-automatically.
</p
>
840 <p
>Lucikly, there are at least two tools available for generating the
841 file based on the code in the source package,
842 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
843 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
844 not sure which one of them came first, but both seem to be able to
845 create a sensible draft file. As far as I can tell, none of them can
846 be trusted to get the result just right, so the content need to be
847 polished a bit before the file is OK to upload. I found the debmake
849 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
850 blog posts from
2014</a
>.
852 <p
>To generate using debmake, use the -cc option:
855 debmake -cc
> debian/copyright
856 </pre
></p
>
858 <p
>Note there are some problems with python and non-ASCII names, so
859 this might not be the best option.
</p
>
861 <p
>The cme option is based on a config parsing library, and I found
863 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
864 blog post from
2015</a
>. To generate using cme, use the
'update
865 dpkg-copyright
' option:
868 cme update dpkg-copyright
869 </pre
></p
>
871 <p
>This will create or update debian/copyright. The cme tool seem to
872 handle UTF-
8 names better than debmake.
</p
>
874 <p
>When the copyright file is created, I would also like some help to
875 check if the file is correct. For this I found two good options,
876 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
877 to focus on license types and file matching, and is able to detect
878 ineffective blocks in the copyright file. The latter reports missing
879 copyright holders and years, but was confused by inconsistent license
880 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
881 fix all issues reported by them before uploading. But I do not know
882 if the tools and the ftpmasters agree on what is important to fix in a
883 copyright file, so the package might still be rejected.
</p
>
885 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
886 will read through the source and try to find all copyright statements.
887 It is not comparing the result to the content of debian/copyright, but
888 can be useful when verifying the content of the copyright file.
</p
>
890 <p
>Are you aware of better tools in Debian to create and update
891 debian/copyright file. Please let me know, or blog about it on
892 planet.debian.org.
</p
>
894 <p
>As usual, if you use Bitcoin and want to show your support of my
895 activities, please send Bitcoin donations to my address
896 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
898 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
899 on how to use licensecheck and cdbs to create a draft copyright file
902 licensecheck --copyright -r `find * -type f` | \
903 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
904 </pre
></p
>
906 <p
>He mentioned that he normally check the generated file into the
907 version control system to make it easier to discover license and
908 copyright changes in the upstream source. I will try to do the same
909 with my packages in the future.
</p
>
911 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
912 against using -quiet for new users, so I removed it from the proposed
913 command line.
</p
>
918 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
919 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
920 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
921 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
922 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
923 is taking shape in Debian, and one provided feature is a very
924 convenient way to tell you which package to install to make a given
925 firmware file available when the kernel is looking for it. This can
926 be done using apt-file too, but that is for someone else to blog
929 <p
>Here is a small recipe to find the package with a given firmware
930 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
931 picked from the set of firmware announced using appstream in Debian
932 unstable. In general you would be looking for the firmware requested
933 by the kernel during kernel module loading. To find the package
934 providing the example file, do like this:
</p
>
936 <blockquote
><pre
>
937 % apt install appstream
941 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
942 awk
'/Package:/ {print $
2}
'
945 </pre
></blockquote
>
947 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
948 appstream wiki
</a
> page to learn how to embed the package metadata in
949 a way appstream can use.
</p
>
951 <p
>This same approach can be used to find any package supporting a
952 given MIME type. This is very useful when you get a file you do not
953 know how to handle. First find the mime type using
<tt
>file
954 --mime-type
</tt
>, and next look up the package providing support for
955 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
956 and you can find all packages handling this type like this:
</p
>
958 <blockquote
><pre
>
959 % apt install appstream
963 % appstreamcli what-provides mimetype image/svg+xml | \
964 awk
'/Package:/ {print $
2}
'
986 </pre
></blockquote
>
988 <p
>I believe the MIME types are fetched from the desktop file for
989 packages providing appstream metadata.
</p
>
994 <title>Creepy, visualise geotagged social media information - nice free software
</title>
995 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
996 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
997 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
998 <description><p
>Most people seem not to realise that every time they walk around
999 with the computerised radio beacon known as a mobile phone their
1000 position is tracked by the phone company and often stored for a long
1001 time (like every time a SMS is received or sent). And if their
1002 computerised radio beacon is capable of running programs (often called
1003 mobile apps) downloaded from the Internet, these programs are often
1004 also capable of tracking their location (if the app requested access
1005 during installation). And when these programs send out information to
1006 central collection points, the location is often included, unless
1007 extra care is taken to not send the location. The provided
1008 information is used by several entities, for good and bad (what is
1009 good and bad, depend on your point of view). What is certain, is that
1010 the private sphere and the right to free movement is challenged and
1011 perhaps even eradicated for those announcing their location this way,
1012 when they share their whereabouts with private and public
1015 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1017 <p
>The phone company logs provide a register of locations to check out
1018 when one want to figure out what the tracked person was doing. It is
1019 unavailable for most of us, but provided to selected government
1020 officials, company staff, those illegally buying information from
1021 unfaithful servants and crackers stealing the information. But the
1022 public information can be collected and analysed, and a free software
1023 tool to do so is called
1024 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1025 discovered it when I read
1026 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1027 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1028 November
2014, and decided to check if it was available in Debian.
1029 The python program was in Debian, but
1030 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1031 Debian
</a
> was completely broken and practically unmaintained. I
1032 uploaded a new version which did not work quite right, but did not
1033 have time to fix it then. This Christmas I decided to finally try to
1034 get Creepy operational in Debian. Now a fixed version is available in
1035 Debian unstable and testing, and almost all Debian specific patches
1037 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1039 <p
>The Creepy program visualises geolocation information fetched from
1040 Twitter, Instagram, Flickr and Google+, and allow one to get a
1041 complete picture of every social media message posted recently in a
1042 given area, or track the movement of a given individual across all
1043 these services. Earlier it was possible to use the search API of at
1044 least some of these services without identifying oneself, but these
1045 days it is impossible. This mean that to use Creepy, you need to
1046 configure it to log in as yourself on these services, and provide
1047 information to them about your search interests. This should be taken
1048 into account when using Creepy, as it will also share information
1049 about yourself with the services.
</p
>
1051 <p
>The picture above show the twitter messages sent from (or at least
1052 geotagged with a position from) the city centre of Oslo, the capital
1053 of Norway. One useful way to use Creepy is to first look at
1054 information tagged with an area of interest, and next look at all the
1055 information provided by one or more individuals who was in the area.
1056 I tested it by checking out which celebrity provide their location in
1057 twitter messages by checkout out who sent twitter messages near a
1058 Norwegian TV station, and next could track their position over time,
1059 making it possible to locate their home and work place, among other
1060 things. A similar technique have been
1061 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
1062 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
1063 tool to discover lying governments, and a useful tool to help people
1064 understand the value of the private information they provide to the
1067 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
1068 it depend on several python modules currently missing in Jessie (at
1069 least python-instagram, python-flickrapi and
1070 python-requests-toolbelt).
</p
>
1072 <p
>(I have uploaded
1073 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
1074 screenshots.debian.net
</a
> and licensed it under the same terms as the
1075 Creepy program in Debian.)
</p
>
1080 <title>Always download Debian packages using Tor - the simple recipe
</title>
1081 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
1082 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
1083 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
1084 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
1085 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
1086 that those listening on the Internet lines would have good reason to
1087 believe a computer have a given security hole
</a
> if it download a
1088 security fix from a Debian mirror. This is a good reason to always
1089 use encrypted connections to the Debian mirror, to make sure those
1090 listening do not know which IP address to attack. In August, Richard
1091 Hartmann observed that encryption was not enough, when it was possible
1092 to interfere download size to security patches or the fact that
1093 download took place shortly after a security fix was released, and
1094 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
1095 to always use Tor to download packages from the Debian mirror
</a
>. He
1096 was not the first to propose this, as the
1097 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
1098 package by Tim Retout already existed to make it easy to convince apt
1099 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
1100 aware of that package when I read the blog post from Richard.
</p
>
1102 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
1103 sysadmins, and he set up a Tor hidden service on one of the central
1104 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1105 it possible to download packages directly between two tor nodes,
1106 making sure the network traffic always were encrypted.
</p
>
1108 <p
>Here is a short recipe for enabling this on your machine, by
1109 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
1110 urls with tor+http and tor+https, and using the hidden service instead
1111 of the official Debian mirror site. I recommend installing
1112 <tt
>etckeeper
</tt
> before you start to have a history of the changes
1113 done in /etc/.
</p
>
1115 <blockquote
><pre
>
1116 apt install apt-transport-tor
1117 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
1118 sed -i
's% http% tor+http%
' /etc/apt/sources.list
1119 </pre
></blockquote
>
1121 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
1122 the sed commands for these too. The sed command is assuming your are
1123 using the ftp.debian.org Debian mirror. Adjust the command (or just
1124 edit the file manually) to match your mirror.
</p
>
1126 <p
>This work in Debian Jessie and later. Note that tools like
1127 <tt
>apt-file
</tt
> only recently started using the apt transport
1128 system, and do not work with these tor+http URLs. For
1129 <tt
>apt-file
</tt
> you need the version currently in experimental,
1130 which need a recent apt version currently only in unstable. So if you
1131 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
1133 <p
>Another advantage from this change is that your machine will start
1134 using Tor regularly and at fairly random intervals (every time you
1135 update the package lists or upgrade or install a new package), thus
1136 masking other Tor traffic done from the same machine. Using Tor will
1137 become normal for the machine in question.
</p
>
1139 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
1140 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
1141 enabled. It would be great if it was the default on any Debian
1147 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
1148 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
1149 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
1150 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
1151 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
1152 call the car license plate numbers in those days. I would write the
1153 numbers down in my little book and compare notes with the other kids
1154 to see how many region codes we had seen and if we had seen some
1155 exotic or special region codes and numbers. It was a fun game to pass
1156 time, as we kids have plenty of it.
</p
>
1158 <p
>A few days I came across
1159 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
1160 project
</a
>, a free software project to automatically discover and
1161 report license plates in images and video streams, and provide the
1162 "car numbers
" in a machine readable format. I
've been looking for
1163 such system for a while now, because I believe it is a bad idea that the
1164 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
1165 number plate recognition
</a
> tool only is available in the hands of
1166 the powerful, and want it to be available also for the powerless to
1167 even the score when it comes to surveillance and sousveillance. I
1168 discovered the developer
1169 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
1170 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
1171 help him get it into shape to get the package uploaded into the Debian
1174 <p
>Today we finally managed to get the package into shape and uploaded
1175 it into Debian, where it currently
1176 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
1177 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
1179 <p
>I guess you are wondering why on earth such tool would be useful
1180 for the common folks, ie those not running a large government
1181 surveillance system? Well, I plan to put it in a computer on my bike
1182 and in my car, tracking the cars nearby and allowing me to be notified
1183 when number plates on my watch list are discovered. Another use case
1184 was suggested by a friend of mine, who wanted to set it up at his home
1185 to open the car port automatically when it discovered the plate on his
1186 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1187 capable of placing his license plate number of a piece of cardboard to
1188 open his car port, men replied that it was always unlocked anyway. I
1189 guess for such use case it make sense. I am sure there are other use
1190 cases too, for those with imagination and a vision.
</p
>
1192 <p
>If you want to build your own version of the Debian package, check
1193 out the upstream git source and symlink ./distros/debian to ./debian/
1194 before running
"debuild
" to build the source. Or wait a bit until the
1195 package show up in unstable.
</p
>
1200 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
1201 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
1202 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
1203 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
1204 <description><p
>Around three years ago, I created
1205 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
1206 system
</a
> to get a more practical solution in Debian for handing
1207 hardware related packages. A GUI system in the isenkram package will
1208 present a pop-up dialog when some hardware dongle supported by
1209 relevant packages in Debian is inserted into the machine. The same
1210 lookup mechanism to detect packages is available as command line
1211 tools in the isenkram-cli package. In addition to mapping hardware,
1212 it will also map kernel firmware files to packages and make it easy to
1213 install needed firmware packages automatically. The key for this
1214 system to work is a good way to map hardware to packages, in other
1215 words, allow packages to announce what hardware they will work
1218 <p
>I started by providing data files in the isenkram source, and
1219 adding code to download the latest version of these data files at run
1220 time, to ensure every user had the most up to date mapping available.
1221 I also added support for storing the mapping in the Packages file in
1222 the apt repositories, but did not push this approach because while I
1223 was trying to figure out how to best store hardware/package mappings,
1224 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
1225 appstream system
</a
> was announced. I got in touch and suggested to
1226 add the hardware mapping into that data set to be able to use
1227 appstream as a data source, and this was accepted at least for the
1228 Debian version of appstream.
</p
>
1230 <p
>A few days ago using appstream in Debian for this became possible,
1231 and today I uploaded a new version
0.20 of isenkram adding support for
1232 appstream as a data source for mapping hardware to packages. The only
1233 package so far using appstream to announce its hardware support is my
1234 pymissile package. I got help from Matthias Klumpp with figuring out
1235 how do add the required
1236 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
1237 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
1238 this content:
</p
>
1240 <blockquote
><pre
>
1241 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1242 &lt;component
&gt;
1243 &lt;id
&gt;pymissile
&lt;/id
&gt;
1244 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
1245 &lt;name
&gt;pymissile
&lt;/name
&gt;
1246 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
1247 &lt;description
&gt;
1249 Pymissile provides a curses interface to control an original
1250 Marks and Spencer / Striker USB Missile Launcher, as well as a
1251 motion control script to allow a webcamera to control the
1254 &lt;/description
&gt;
1255 &lt;provides
&gt;
1256 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
1257 &lt;/provides
&gt;
1258 &lt;/component
&gt;
1259 </pre
></blockquote
>
1261 <p
>The key for isenkram is the component/provides/modalias value,
1262 which is a glob style match rule for hardware specific strings
1263 (modalias strings) provided by the Linux kernel. In this case, it
1264 will map to all USB devices with vendor code
1130 and product code
1267 <p
>Note, it is important that the license of all the metadata files
1268 are compatible to have permissions to aggregate them into archive wide
1269 appstream files. Matthias suggested to use MIT or BSD licenses for
1270 these files. A challenge is figuring out a good id for the data, as
1271 it is supposed to be globally unique and shared across distributions
1272 (in other words, best to coordinate with upstream what to use). But
1273 it can be changed later or, so we went with the package name as
1274 upstream for this project is dormant.
</p
>
1276 <p
>To get the metadata file installed in the correct location for the
1277 mirror update scripts to pick it up and include its content the
1278 appstream data source, the file must be installed in the binary
1279 package under /usr/share/appdata/. I did this by adding the following
1280 line to debian/pymissile.install:
</p
>
1282 <blockquote
><pre
>
1283 debian/pymissile.metainfo.xml usr/share/appdata
1284 </pre
></blockquote
>
1286 <p
>With that in place, the command line tool isenkram-lookup will list
1287 all packages useful on the current computer automatically, and the GUI
1288 pop-up handler will propose to install the package not already
1289 installed if a hardware dongle is inserted into the machine in
1292 <p
>Details of the modalias field in appstream is available from the
1293 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
1295 <p
>To locate the modalias values of all hardware present in a machine,
1296 try running this command on the command line:
</p
>
1298 <blockquote
><pre
>
1299 cat $(find /sys/devices/|grep modalias)
1300 </pre
></blockquote
>
1302 <p
>To learn more about the isenkram system, please check out
1303 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1304 blog posts tagged isenkram
</a
>.
</p
>
1309 <title>The GNU General Public License is not magic pixie dust
</title>
1310 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
1311 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
1312 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
1313 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
1314 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
1315 GPL is not magic pixie dust
</a
>" explain the importance of making sure
1316 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
1317 I quote the blog post from Paul in full here with his permission:
<p
>
1321 <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
>
1324 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
1326 The first step is to choose a
1327 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
1330 The next step is, when someone fails to follow that copyleft license,
1331 <b
>it must be enforced
</b
><br/
>
1333 and its a simple fact of our modern society that such type of
1336 is incredibly expensive to do and incredibly difficult to do.
1339 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
1340 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
1341 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
1342 0x57</a
></small
></p
>
1344 <p
>As the Debian Website
1345 <a href=
"https://bugs.debian.org/
794116">used
</a
>
1346 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
1347 imply, public domain and permissively licensed software can lead to
1348 the production of more proprietary software as people discover useful
1349 software, extend it and or incorporate it into their hardware or
1350 software products. Copyleft licenses such as the GNU GPL were created
1351 to close off this avenue to the production of proprietary software but
1352 such licenses are not enough. With the ongoing adoption of Free
1353 Software by individuals and groups, inevitably the community
's
1354 expectations of license compliance are violated, usually out of
1355 ignorance of the way Free Software works, but not always. As Karen
1356 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
1357 Freedom
">FaiF
</a
>
1358 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
1359 copyleft is nothing if no-one is willing and able to stand up in court
1360 to protect it. The reality of today
's world is that legal
1361 representation is expensive, difficult and time consuming. With
1362 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
1363 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
1364 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
1365 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
1366 of the Linux project, Debian and other groups against GPL violations.
1367 In March the SFC supported a
1368 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
1369 by Christoph Hellwig
</a
> against VMware for refusing to
1370 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
1371 with the GPL
</a
> in relation to their use of parts of the Linux
1372 kernel. Since then two of their sponsors pulled corporate funding and
1374 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
1375 or cancelled their talks
</a
>. As a result they have decided to rely
1376 less on corporate funding and more on the broad community of
1377 individuals who support Free Software and copyleft. So the SFC has
1378 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
1379 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
1380 a community of folks who stand up for copyleft and the GPL by
1381 supporting their work on promoting and supporting copyleft and Free
1384 <p
>If you support Free Software,
1385 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
1386 what the SFC do, agree with their
1387 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
1388 principles
</a
>, are happy about their
1389 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
1390 work on a project that is an SFC
1391 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
1392 just want to stand up for copyleft, please join
1393 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
1394 Allan Webber
</a
>,
1395 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
1397 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
1398 Bacon
</a
>, myself and
1399 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
1401 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
1402 next week your donation will be
1403 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
1404 by an anonymous donor. Please also consider asking your employer to
1405 match your donation or become a sponsor of SFC. Don
't forget to
1406 spread the word about your support for SFC via email, your blog and or
1407 social media accounts.
</p
>
1411 <p
>I agree with Paul on this topic and just signed up as a Supporter
1412 of Software Freedom Conservancy myself. Perhaps you should be a
1413 supporter too?
</p
>
1418 <title>PGP key transition statement for key EE4E02F9
</title>
1419 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
1420 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
1421 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
1422 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
1423 set it up properly. I wanted to generate it offline and have it
1424 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
1425 smart card
</a
> for daily use, and learning how to do it and finding
1426 time to sit down with an offline machine almost took forever. But
1427 finally I
've been able to complete the process, and have now moved
1428 from my old GPG key to a new GPG key. See
1429 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
1430 full transition statement, signed with both my old and new key
</a
> for
1431 the details. This is my new key:
</p
>
1434 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
1435 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
1436 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
1437 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
1438 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
1439 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
1440 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
1443 <p
>The key can be downloaded from the OpenPGP key servers, signed by
1444 my old key.
</p
>
1446 <p
>If you signed my old key
1447 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
1448 I
'd very much appreciate a signature on my new key, details and
1449 instructions in the transition statement. I m happy to reciprocate if
1450 you have a similarly signed transition statement to present.
</p
>
1455 <title>The life and death of a laptop battery
</title>
1456 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
1457 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
1458 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
1459 <description><p
>When I get a new laptop, the battery life time at the start is OK.
1460 But this do not last. The last few laptops gave me a feeling that
1461 within a year, the life time is just a fraction of what it used to be,
1462 and it slowly become painful to use the laptop without power connected
1463 all the time. Because of this, when I got a new Thinkpad X230 laptop
1464 about two years ago, I decided to monitor its battery state to have
1465 more hard facts when the battery started to fail.
</p
>
1467 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
1469 <p
>First I tried to find a sensible Debian package to record the
1470 battery status, assuming that this must be a problem already handled
1471 by someone else. I found
1472 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
1473 which collects statistics from the battery, but it was completely
1474 broken. I sent a few suggestions to the maintainer, but decided to
1475 write my own collector as a shell script while I waited for feedback
1477 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
1478 blog post about the battery development on a MacBook Air
</a
> I also
1480 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
1481 available in Debian.
</p
>
1483 <p
>I started my collector
2013-
07-
15, and it has been collecting
1484 battery stats ever since. Now my
1485 /var/log/hjemmenett-battery-status.log file contain around
115,
000
1486 measurements, from the time the battery was working great until now,
1487 when it is unable to charge above
7% of original capacity. My
1488 collector shell script is quite simple and look like this:
</p
>
1493 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
1495 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
1496 logfile=/var/log/hjemmenett-battery-status.log
1498 files=
"manufacturer model_name technology serial_number \
1499 energy_full energy_full_design energy_now cycle_count status
"
1501 if [ ! -e
"$logfile
" ] ; then
1503 printf
"timestamp,
"
1505 printf
"%s,
" $f
1508 )
> "$logfile
"
1512 # Print complete message in one echo call, to avoid race condition
1513 # when several log processes run in parallel.
1514 msg=$(printf
"%s,
" $(date +%s); \
1515 for f in $files; do \
1516 printf
"%s,
" $(cat $f); \
1518 echo
"$msg
"
1521 cd /sys/class/power_supply
1524 (cd $bat
&& log_battery
>> "$logfile
")
1528 <p
>The script is called when the power management system detect a
1529 change in the power status (power plug in or out), and when going into
1530 and out of hibernation and suspend. In addition, it collect a value
1531 every
10 minutes. This make it possible for me know when the battery
1532 is discharging, charging and how the maximum charge change over time.
1533 The code for the Debian package
1534 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
1535 available on github
</a
>.
</p
>
1537 <p
>The collected log file look like this:
</p
>
1540 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1541 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
1543 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1544 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1547 <p
>I wrote a small script to create a graph of the charge development
1548 over time. This graph depicted above show the slow death of my laptop
1551 <p
>But why is this happening? Why are my laptop batteries always
1552 dying in a year or two, while the batteries of space probes and
1553 satellites keep working year after year. If we are to believe
1554 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
1555 University
</a
>, the cause is me charging the battery whenever I have a
1556 chance, and the fix is to not charge the Lithium-ion batteries to
100%
1557 all the time, but to stay below
90% of full charge most of the time.
1558 I
've been told that the Tesla electric cars
1559 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
1560 the charge of their batteries to
80%
</a
>, with the option to charge to
1561 100% when preparing for a longer trip (not that I would want a car
1562 like Tesla where rights to privacy is abandoned, but that is another
1563 story), which I guess is the option we should have for laptops on
1564 Linux too.
</p
>
1566 <p
>Is there a good and generic way with Linux to tell the battery to
1567 stop charging at
80%, unless requested to charge to
100% once in
1568 preparation for a longer trip? I found
1569 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
1570 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1571 80%
</a
>, but could not get it to work (kernel module refused to
1574 <p
>I wonder why the battery capacity was reported to be more than
100%
1575 at the start. I also wonder why the
"full capacity
" increases some
1576 times, and if it is possible to repeat the process to get the battery
1577 back to design capacity. And I wonder if the discharge and charge
1578 speed change over time, or if this stay the same. I did not yet try
1579 to write a tool to calculate the derivative values of the battery
1580 level, but suspect some interesting insights might be learned from
1583 <p
>Update
2015-
09-
24: I got a tip to install the packages
1584 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1585 packages instead of the tp-smapi-dkms package I had tried to use
1586 initially, and use
'tlp setcharge
40 80' to change when charging start
1587 and stop. I
've done so now, but expect my existing battery is toast
1588 and need to be replaced. The proposal is unfortunately Thinkpad
1594 <title>New laptop - some more clues and ideas based on feedback
</title>
1595 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
1596 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
1597 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
1598 <description><p
>Several people contacted me after my previous blog post about my
1599 need for a new laptop, and provided very useful feedback. I wish to
1600 thank every one of these. Several pointed me to the possibility of
1601 fixing my X230, and I am already in the process of getting Lenovo to
1602 do so thanks to the on site, next day support contract covering the
1603 machine. But the battery is almost useless (I expect to replace it
1604 with a non-official battery) and I do not expect the machine to live
1605 for many more years, so it is time to plan its replacement. If I did
1606 not have a support contract, it was suggested to find replacement parts
1607 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
1608 might present a language barrier as I do not understand French.
</p
>
1610 <p
>One tip I got was to use the
1611 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
1612 compare laptop models. It seem to have more models available than
1613 prisjakt.no. Another tip I got from someone I know have similar
1614 keyboard preferences was that the HP EliteBook
840 keyboard is not
1615 very good, and this matches my experience with earlier EliteBook
1616 keyboards I tested. Because of this, I will not consider it any further.
1618 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
1619 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1620 (which is missing from the X240), and is working fairly well with
1621 Debian Sid/Unstable according to
1622 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
1623 got on the keyboard quality are not consistent. Some say the keyboard
1624 is good, others say it is ok, while others say it is not very good.
1625 Those with experience from X41 and and X60 agree that the X250
1626 keyboard is not as good as those trusty old laptops, and suggest I
1627 keep and fix my X230 instead of upgrading, or get a used X230 to
1628 replace it. I
'm also told that the X250 lack leds for caps lock, disk
1629 activity and battery status, which is very convenient on my X230. I
'm
1630 also told that the CPU fan is running very often, making it a bit
1631 noisy. In any case, the X250 do not work out of the box with Debian
1632 Stable/Jessie, one of my requirements.
</p
>
1634 <p
>I have also gotten a few vendor proposals, one was
1635 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
1636 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
1637 The latter look very attractive to me.
</p
>
1639 <p
>Again, thank you all for the very useful feedback. It help a lot
1640 as I keep looking for a replacement.
</p
>
1642 <p
>Update
2015-
07-
06: I was recommended to check out the
1643 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
1645 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
1646 thinkpad X models
</a
>, and provide one year warranty.
</p
>
1651 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
1652 <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>
1653 <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>
1654 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
1655 <description><p
>My primary work horse laptop is failing, and will need a
1656 replacement soon. The left
5 cm of the screen on my Thinkpad X230
1657 started flickering yesterday, and I suspect the cause is a broken
1658 cable, as changing the angle of the screen some times get rid of the
1659 flickering.
</p
>
1661 <p
>My requirements have not really changed since I bought it, and is
1663 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
1664 described them in
2013</a
>. The last time I bought a laptop, I had
1666 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
1667 where I could select at least a few of the requirements (mouse pin,
1668 wifi, weight) and go through the rest manually. Three button mouse
1669 and a good keyboard is not available as an option, and all the three
1670 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
1671 G2) lack three mouse buttons). It is also unclear to me how good the
1672 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1673 the keyboard, even if the quality and robustness in the X series have
1674 deteriorated since X41.
</p
>
1676 <p
>I wonder how I can find a sensible laptop when none of the options
1677 seem sensible to me? Are there better services around to search the
1678 set of available laptops for features? Please send me an email if you
1679 have suggestions.
</p
>
1681 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
1682 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
1683 of endorsed hardware
</a
>, which is useful background information.
</p
>
1688 <title>How to stay with sysvinit in Debian Jessie
</title>
1689 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
1690 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
1691 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
1692 <description><p
>By now, it is well known that Debian Jessie will not be using
1693 sysvinit as its boot system by default. But how can one keep using
1694 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1696 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
1697 Schubert
</a
> and
1698 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
1701 <p
>If you already are using Wheezy and want to upgrade to Jessie and
1702 keep sysvinit as your boot system, create a file
1703 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
1704 you upgrade:
</p
>
1706 <p
><blockquote
><pre
>
1707 Package: systemd-sysv
1708 Pin: release o=Debian
1710 </pre
></blockquote
><p
>
1712 <p
>This file content will tell apt and aptitude to not consider
1713 installing systemd-sysv as part of any installation and upgrade
1714 solution when resolving dependencies, and thus tell it to avoid
1715 systemd as a default boot system. The end result should be that the
1716 upgraded system keep using sysvinit.
</p
>
1718 <p
>If you are installing Jessie for the first time, there is no way to
1719 get sysvinit installed by default (debootstrap used by
1720 debian-installer have no option for this), but one can tell the
1721 installer to switch to sysvinit before the first boot. Either by
1722 using a kernel argument to the installer, or by adding a line to the
1723 preseed file used. First, the kernel command line argument:
1725 <p
><blockquote
><pre
>
1726 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
1727 </pre
></blockquote
><p
>
1729 <p
>Next, the line to use in a preseed file:
</p
>
1731 <p
><blockquote
><pre
>
1732 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1733 </pre
></blockquote
><p
>
1735 <p
>One can of course also do this after the first boot by installing
1736 the sysvinit-core package.
</p
>
1738 <p
>I recommend only using sysvinit if you really need it, as the
1739 sysvinit boot sequence in Debian have several hardware specific bugs
1740 on Linux caused by the fact that it is unpredictable when hardware
1741 devices show up during boot. But on the other hand, the new default
1742 boot system still have a few rough edges I hope will be fixed before
1743 Jessie is released.
</p
>
1745 <p
>Update
2014-
11-
26: Inspired by
1746 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
1747 blog post by Torsten Glaser
</a
>, added --purge to the preseed
1753 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
1754 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
1755 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
1756 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
1757 <description><p
>The right to communicate with your friends and family in private,
1758 without anyone snooping, is a right every citicen have in a liberal
1759 democracy. But this right is under serious attack these days.
</p
>
1761 <p
>A while back it occurred to me that one way to make the dragnet
1762 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1763 the whisleblower Snowden) more expensive for Internet email,
1764 is to deliver all email using SMTP via Tor. Such SMTP option would be
1765 a nice addition to the FreedomBox project if we could send email
1766 between FreedomBox machines without leaking metadata about the emails
1767 to the people peeking on the wire. I
1768 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
1769 this on the FreedomBox project mailing list in October
</a
> and got a
1770 lot of useful feedback and suggestions. It also became obvious to me
1771 that this was not a novel idea, as the same idea was tested and
1772 documented by Johannes Berg as early as
2006, and both
1773 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
1774 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
1775 propose a similar method / protocol to pass emails between users.
</p
>
1777 <p
>To implement such system one need to set up a Tor hidden service
1778 providing the SMTP protocol on port
25, and use email addresses
1779 looking like username@hidden-service-name.onion. With such addresses
1780 the connections to port
25 on hidden-service-name.onion using Tor will
1781 go to the correct SMTP server. To do this, one need to configure the
1782 Tor daemon to provide the hidden service and the mail server to accept
1783 emails for this .onion domain. To learn more about Exim configuration
1784 in Debian and test the design provided by Johannes Berg in his FAQ, I
1785 set out yesterday to create a Debian package for making it trivial to
1786 set up such SMTP over Tor service based on Debian. Getting it to work
1787 were fairly easy, and
1788 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
1789 source code for the Debian package
</a
> is available from github. I
1790 plan to move it into Debian if further testing prove this to be a
1791 useful approach.
</p
>
1793 <p
>If you want to test this, set up a blank Debian machine without any
1794 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
1795 get rid of exim4). Install tor, clone the git repository mentioned
1796 above, build the deb and install it on the machine. Next, run
1797 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
1798 the instructions to get the service up and running. Restart tor and
1799 exim when it is done, and test mail delivery using swaks like
1802 <p
><blockquote
><pre
>
1803 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1804 --to fbx@dutlqrrmjhtfa3vp.onion
1805 </pre
></blockquote
></p
>
1807 <p
>This will test the SMTP delivery using tor. Replace the email
1808 address with your own address to test your server. :)
</p
>
1810 <p
>The setup procedure is still to complex, and I hope it can be made
1811 easier and more automatic. Especially the tor setup need more work.
1812 Also, the package include a tor-smtp tool written in C, but its task
1813 should probably be rewritten in some script language to make the deb
1814 architecture independent. It would probably also make the code easier
1815 to review. The tor-smtp tool currently need to listen on a socket for
1816 exim to talk to it and is started using xinetd. It would be better if
1817 no daemon and no socket is needed. I suspect it is possible to get
1818 exim to run a command line tool for delivery instead of talking to a
1819 socket, and hope to figure out how in a future version of this
1822 <p
>Until I wipe my test machine, I can be reached using the
1823 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
1824 SMTorP. :)
</p
>
1829 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
1830 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
1831 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
1832 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
1833 <description><p
>If you ever had to moderate a mailman list, like the ones on
1834 alioth.debian.org, you know the web interface is fairly slow to
1835 operate. First you visit one web page, enter the moderation password
1836 and get a new page shown with a list of all the messages to moderate
1837 and various options for each email address. This take a while for
1838 every list you moderate, and you need to do it regularly to do a good
1839 job as a list moderator. But there is a quick alternative,
1840 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
1841 listadmin program
</a
>. It allow you to check lists for new messages
1842 to moderate in a fraction of a second. Here is a test run on two
1843 lists I recently took over:
</p
>
1845 <p
><blockquote
><pre
>
1846 % time listadmin xiph
1847 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1848 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1854 </pre
></blockquote
></p
>
1856 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
1857 there are no message in the moderation queue. Every morning I
1858 currently moderate
68 mailman lists, and it normally take around two
1859 minutes. When I took over the two pkg-xiph lists above a few days
1860 ago, there were
400 emails waiting in the moderator queue. It took me
1861 less than
15 minutes to process them all using the listadmin
1864 <p
>If you install
1865 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
1866 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
1867 with content like this, the moderation task is a breeze:
</p
>
1869 <p
><blockquote
><pre
>
1870 username username@example.org
1873 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
1876 adminurl https://{domain}/mailman/admindb/{list}
1877 mailman-list@lists.example.com
1880 other-list@otherserver.example.org
1881 </pre
></blockquote
></p
>
1883 <p
>There are other options to set as well. Check the manual page to
1884 learn the details.
</p
>
1886 <p
>If you are forced to moderate lists on a mailman installation where
1887 the SSL certificate is self signed or not properly signed by a
1888 generally accepted signing authority, you can set a environment
1889 variable when calling listadmin to disable SSL verification:
</p
>
1891 <p
><blockquote
><pre
>
1892 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
1893 </pre
></blockquote
></p
>
1895 <p
>If you want to moderate a subset of the lists you take care of, you
1896 can provide an argument to the listadmin script like I do in the
1897 initial screen dump (the xiph argument). Using an argument, only
1898 lists matching the argument string will be processed. This make it
1899 quick to accept messages if you notice the moderation request in your
1902 <p
>Without the listadmin program, I would never be the moderator of
68
1903 mailing lists, as I simply do not have time to spend on that if the
1904 process was any slower. The listadmin program have saved me hours of
1905 time I could spend elsewhere over the years. It truly is nice free
1908 <p
>As usual, if you use Bitcoin and want to show your support of my
1909 activities, please send Bitcoin donations to my address
1910 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1912 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
1913 configuration example. Also, I
've been told that the
1914 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
1920 <title>Debian Jessie, PXE and automatic firmware installation
</title>
1921 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
1922 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
1923 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
1924 <description><p
>When PXE installing laptops with Debian, I often run into the
1925 problem that the WiFi card require some firmware to work properly.
1926 And it has been a pain to fix this using preseeding in Debian.
1927 Normally something more is needed. But thanks to
1928 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
1929 package
</a
> and its recent tasksel extension, it has now become easy
1930 to do this using simple preseeding.
</p
>
1932 <p
>The isenkram-cli package provide tasksel tasks which will install
1933 firmware for the hardware found in the machine (actually, requested by
1934 the kernel modules for the hardware). (It can also install user space
1935 programs supporting the hardware detected, but that is not the focus
1936 of this story.)
</p
>
1938 <p
>To get this working in the default installation, two preeseding
1939 values are needed. First, the isenkram-cli package must be installed
1940 into the target chroot (aka the hard drive) before tasksel is executed
1941 in the pkgsel step of the debian-installer system. This is done by
1942 preseeding the base-installer/includes debconf value to include the
1943 isenkram-cli package. The package name is next passed to debootstrap
1944 for installation. With the isenkram-cli package in place, tasksel
1945 will automatically use the isenkram tasks to detect hardware specific
1946 packages for the machine being installed and install them, because
1947 isenkram-cli contain tasksel tasks.
</p
>
1949 <p
>Second, one need to enable the non-free APT repository, because
1950 most firmware unfortunately is non-free. This is done by preseeding
1951 the apt-mirror-setup step. This is unfortunate, but for a lot of
1952 hardware it is the only option in Debian.
</p
>
1954 <p
>The end result is two lines needed in your preseeding file to get
1955 firmware installed automatically by the installer:
</p
>
1957 <p
><blockquote
><pre
>
1958 base-installer base-installer/includes string isenkram-cli
1959 apt-mirror-setup apt-setup/non-free boolean true
1960 </pre
></blockquote
></p
>
1962 <p
>The current version of isenkram-cli in testing/jessie will install
1963 both firmware and user space packages when using this method. It also
1964 do not work well, so use version
0.15 or later. Installing both
1965 firmware and user space packages might give you a bit more than you
1966 want, so I decided to split the tasksel task in two, one for firmware
1967 and one for user space programs. The firmware task is enabled by
1968 default, while the one for user space programs is not. This split is
1969 implemented in the package currently in unstable.
</p
>
1971 <p
>If you decide to give this a go, please let me know (via email) how
1972 this recipe work for you. :)
</p
>
1974 <p
>So, I bet you are wondering, how can this work. First and
1975 foremost, it work because tasksel is modular, and driven by whatever
1976 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1977 isenkram-cli package place two files for tasksel to find. First there
1978 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
1980 <p
><blockquote
><pre
>
1981 Task: isenkram-packages
1983 Description: Hardware specific packages (autodetected by isenkram)
1984 Based on the detected hardware various hardware specific packages are
1986 Test-new-install: show show
1988 Packages: for-current-hardware
1990 Task: isenkram-firmware
1992 Description: Hardware specific firmware packages (autodetected by isenkram)
1993 Based on the detected hardware various hardware specific firmware
1994 packages are proposed.
1995 Test-new-install: mark show
1997 Packages: for-current-hardware-firmware
1998 </pre
></blockquote
></p
>
2000 <p
>The key parts are Test-new-install which indicate how the task
2001 should be handled and the Packages line referencing to a script in
2002 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2003 list of packages to install. The for-current-hardware-firmware script
2004 look like this to list relevant firmware for the machine:
2006 <p
><blockquote
><pre
>
2009 PATH=/usr/sbin:$PATH
2011 isenkram-autoinstall-firmware -l
2012 </pre
></blockquote
></p
>
2014 <p
>With those two pieces in place, the firmware is installed by
2015 tasksel during the normal d-i run. :)
</p
>
2017 <p
>If you want to test what tasksel will install when isenkram-cli is
2018 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2019 --new-install
</tt
> to get the list of packages that tasksel would
2022 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2023 pilots in testing this feature, as isenkram is used there now to
2024 install firmware, replacing the earlier scripts.
</p
>
2029 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2030 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2031 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2032 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2033 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2034 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2035 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2036 on a screen normally showing the bread types and prizes:
</p
>
2038 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2040 <p
>If it had booted as it was supposed to, I would never had known
2041 about this hidden Linux installation. It is interesting what
2042 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
2047 <title>New lsdvd release version
0.17 is ready
</title>
2048 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
2049 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
2050 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
2051 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
2052 got a new set of developers a few weeks ago, after the original
2053 developer decided to step down and pass the project to fresh blood.
2054 This project is now maintained by Petter Reinholdtsen and Steve
2057 <p
>I just wrapped up
2058 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
2059 new lsdvd release
</a
>, available in git or from
2060 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
2061 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
2066 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
2067 <li
>Check for garbage in the program chains, which indicate that a track is
2068 non-existant, to work around additional copy protection
</li
>
2069 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
2070 <li
>Fix pallete display of first entry
</li
>
2071 <li
>Fix include orders
</li
>
2072 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
2073 <li
>Fix the chapter count
</li
>
2074 <li
>Make sure the array size and the array limit used when initialising
2075 the palette size is the same.
</li
>
2076 <li
>Fix array printing.
</li
>
2077 <li
>Correct subsecond calculations.
</li
>
2078 <li
>Add sector information to the output format.
</li
>
2079 <li
>Clean up code to be closer to ANSI C and compile without warnings
2080 with more GCC compiler warnings.
</li
>
2084 <p
>This change bring together patches for lsdvd in use in various
2085 Linux and Unix distributions, as well as patches submitted to the
2086 project the last nine years. Please check it out. :)
</p
>
2091 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
2092 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
2093 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
2094 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
2095 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2096 project
</a
> provide a Linux solution for schools, including a
2097 powerful desktop with education software, a central server providing
2098 web pages, user database, user home directories, central login and PXE
2099 boot of both clients without disk and the installation to install Debian
2100 Edu on machines with disk (and a few other services perhaps to small
2101 to mention here). We in the Debian Edu team are currently working on
2102 the Jessie based version, trying to get everything in shape before the
2103 freeze, to avoid having to maintain our own package repository in the
2105 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
2106 status
</a
> can be seen on the Debian wiki, and there is still heaps of
2107 work left. Some fatal problems block testing, breaking the installer,
2108 but it is possible to work around these to get anyway. Here is a
2109 recipe on how to get the installation limping along.
</p
>
2111 <p
>First, download the test ISO via
2112 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
2113 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
2115 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
2116 The ISO build was broken on Tuesday, so we do not get a new ISO every
2117 12 hours or so, but thankfully the ISO we already got we are able to
2118 install with some tweaking.
</p
>
2120 <p
>When you get to the Debian Edu profile question, go to tty2
2121 (use Alt-Ctrl-F2), run
</p
>
2123 <p
><blockquote
><pre
>
2124 nano /usr/bin/edu-eatmydata-install
2125 </pre
></blockquote
></p
>
2127 <p
>and add
'exit
0' as the second line, disabling the eatmydata
2128 optimization. Return to the installation, select the profile you want
2129 and continue. Without this change, exim4-config will fail to install
2130 due to a known bug in eatmydata.
</p
>
2132 <p
>When you get the grub question at the end, answer /dev/sda (or if
2133 this do not work, figure out what your correct value would be. All my
2134 test machines need /dev/sda, so I have no advice if it do not fit
2135 your need.
</p
>
2137 <p
>If you installed a profile including a graphical desktop, log in as
2138 root after the initial boot from hard drive, and install the
2139 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2140 or mate. If you want several desktop options, install more than one
2141 metapackage. Once this is done, reboot and you should have a working
2142 graphical login screen. This workaround should no longer be needed
2143 once the education-tasks package version
1.801 enter testing in two
2146 <p
>I believe the ISO build will start working on two days when the new
2147 tasksel package enter testing and Steve McIntyre get a chance to
2148 update the debian-cd git repository. The eatmydata, grub and desktop
2149 issues are already fixed in unstable and testing, and should show up
2150 on the ISO as soon as the ISO build start working again. Well the
2151 eatmydata optimization is really just disabled. The proper fix
2152 require an upload by the eatmydata maintainer applying the patch
2153 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
2154 The rest have proper fixes in unstable.
</p
>
2156 <p
>I hope this get you going with the installation testing, as we are
2157 quickly running out of time trying to get our Jessie based
2158 installation ready before the distribution freeze in a month.
</p
>
2163 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
2164 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
2165 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
2166 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
2167 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
2168 to handle my fairly large DVD collection. It is a nice command line
2169 tool to get details about a DVD, like title, tracks, track length,
2170 etc, in XML, Perl or human readable format. But lsdvd have not seen
2171 any new development since
2006 and had a few irritating bugs affecting
2172 its use with some DVDs. Upstream seemed to be dead, and in January I
2173 sent a small probe asking for a version control repository for the
2174 project, without any reply. But I use it regularly and would like to
2175 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
2176 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
2177 the project admin, and after getting a reply from him explaining that
2178 he was no longer interested in the project, I asked if I could take
2179 over. And yesterday, I became project admin.
</p
>
2181 <p
>I
've been in touch with a Gentoo developer and the Debian
2182 maintainer interested in joining forces to maintain the upstream
2183 project, and I hope we can get a new release out fairly quickly,
2184 collecting the patches spread around on the internet into on place.
2185 I
've added the relevant Debian patches to the freshly created git
2186 repository, and expect the Gentoo patches to make it too. If you got
2187 a DVD collection and care about command line tools, check out
2188 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
2189 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
2190 list
</a
>. :)
</p
>
2195 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
2196 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
2197 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
2198 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
2199 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
2200 a lot quicker. When we install more than
2000 packages in
2201 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
2202 tasksel in the installer, unpacking the binary packages take forever.
2203 A part of the slow I/O issue was discussed in
2204 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
2205 much file system sync-ing done by dpkg, which is the package
2206 responsible for unpacking the binary packages. Other parts (like code
2207 executed by postinst scripts) might also sync to disk during
2208 installation. All this sync-ing to disk do not really make sense to
2209 me. If the machine crash half-way through, I start over, I do not try
2210 to salvage the half installed system. So the failure sync-ing is
2211 supposed to protect against, hardware or system crash, is not really
2212 relevant while the installer is running.
</p
>
2214 <p
>A few days ago, I thought of a way to get rid of all the file
2215 system sync()-ing in a fairly non-intrusive way, without the need to
2216 change the code in several packages. The idea is not new, but I have
2217 not heard anyone propose the approach using dpkg-divert before. It
2218 depend on the small and clever package
2219 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
2220 uses LD_PRELOAD to replace the system functions for syncing data to
2221 disk with functions doing nothing, thus allowing programs to live
2222 dangerous while speeding up disk I/O significantly. Instead of
2223 modifying the implementation of dpkg, apt and tasksel (which are the
2224 packages responsible for selecting, fetching and installing packages),
2225 it occurred to me that we could just divert the programs away, replace
2226 them with a simple shell wrapper calling
2227 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
2228 Two days ago I decided to test the idea, and wrapped up a simple
2229 implementation for the Debian Edu udeb.
</p
>
2231 <p
>The effect was stunning. In my first test it reduced the running
2232 time of the pkgsel step (installing tasks) from
64 to less than
44
2233 minutes (
20 minutes shaved off the installation) on an old Dell
2234 Latitude D505 machine. I am not quite sure what the optimised time
2235 would have been, as I messed up the testing a bit, causing the debconf
2236 priority to get low enough for two questions to pop up during
2237 installation. As soon as I saw the questions I moved the installation
2238 along, but do not know how long the question were holding up the
2239 installation. I did some more measurements using Debian Edu Jessie,
2240 and got these results. The time measured is the time stamp in
2241 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
2242 "pkgsel: finishing up
" lines, if you want to do the same measurement
2243 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2244 timing thus do not depend on how quickly the user handle the tasksel
2247 <p
><table
>
2250 <th
>Machine/setup
</th
>
2251 <th
>Original tasksel
</th
>
2252 <th
>Optimised tasksel
</th
>
2253 <th
>Reduction
</th
>
2257 <td
>Latitude D505 Main+LTSP LXDE
</td
>
2258 <td
>64 min (
07:
46-
08:
50)
</td
>
2259 <td
><44 min (
11:
27-
12:
11)
</td
>
2260 <td
>>20 min
18%
</td
>
2264 <td
>Latitude D505 Roaming LXDE
</td
>
2265 <td
>57 min (
08:
48-
09:
45)
</td
>
2266 <td
>34 min (
07:
43-
08:
17)
</td
>
2267 <td
>23 min
40%
</td
>
2271 <td
>Latitude D505 Minimal
</td
>
2272 <td
>22 min (
10:
37-
10:
59)
</td
>
2273 <td
>11 min (
11:
16-
11:
27)
</td
>
2274 <td
>11 min
50%
</td
>
2278 <td
>Thinkpad X200 Minimal
</td
>
2279 <td
>6 min (
08:
19-
08:
25)
</td
>
2280 <td
>4 min (
08:
04-
08:
08)
</td
>
2281 <td
>2 min
33%
</td
>
2285 <td
>Thinkpad X200 Roaming KDE
</td
>
2286 <td
>19 min (
09:
21-
09:
40)
</td
>
2287 <td
>15 min (
10:
25-
10:
40)
</td
>
2288 <td
>4 min
21%
</td
>
2291 </table
></p
>
2293 <p
>The test is done using a netinst ISO on a USB stick, so some of the
2294 time is spent downloading packages. The connection to the Internet
2295 was
100Mbit/s during testing, so downloading should not be a
2296 significant factor in the measurement. Download typically took a few
2297 seconds to a few minutes, depending on the amount of packages being
2298 installed.
</p
>
2300 <p
>The speedup is implemented by using two hooks in
2301 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
2302 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
2303 finish-install.d hook to remove the divert at the end of the
2304 installation. I picked the pre-pkgsel.d hook instead of the
2305 post-base-installer.d hook because I test using an ISO without the
2306 eatmydata package included, and the post-base-installer.d hook in
2307 Debian Edu can only operate on packages included in the ISO. The
2308 negative effect of this is that I am unable to activate this
2309 optimization for the kernel installation step in d-i. If the code is
2310 moved to the post-base-installer.d hook, the speedup would be larger
2311 for the entire installation.
</p
>
2313 <p
>I
've implemented this in the
2314 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
2315 git repository, and plan to provide the optimization as part of the
2316 Debian Edu installation. If you want to test this yourself, you can
2317 create two files in the installer (or in an udeb). One shell script
2318 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
2320 <p
><blockquote
><pre
>
2323 . /usr/share/debconf/confmodule
2325 logger -t my-pkgsel
"info: $*
"
2328 logger -t my-pkgsel
"error: $*
"
2330 override_install() {
2331 apt-install eatmydata || true
2332 if [ -x /target/usr/bin/eatmydata ] ; then
2333 for bin in dpkg apt-get aptitude tasksel ; do
2335 # Test that the file exist and have not been diverted already.
2336 if [ -f /target$file ] ; then
2337 info
"diverting $file using eatmydata
"
2338 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
2339 > /target$file.edu
2340 chmod
755 /target$file.edu
2341 in-target dpkg-divert --package debian-edu-config \
2342 --rename --quiet --add $file
2343 ln -sf ./$bin.edu /target$file
2345 error
"unable to divert $file, as it is missing.
"
2349 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
2354 </pre
></blockquote
></p
>
2356 <p
>To clean up, another shell script should go into
2357 /usr/lib/finish-install.d/ with code like this:
2359 <p
><blockquote
><pre
>
2361 . /usr/share/debconf/confmodule
2363 logger -t my-finish-install
"error: $@
"
2365 remove_install_override() {
2366 for bin in dpkg apt-get aptitude tasksel ; do
2368 if [ -x /target$file.edu ] ; then
2370 in-target dpkg-divert --package debian-edu-config \
2371 --rename --quiet --remove $file
2374 error
"Missing divert for $file.
"
2377 sync # Flush file buffers before continuing
2380 remove_install_override
2381 </pre
></blockquote
></p
>
2383 <p
>In Debian Edu, I placed both code fragments in a separate script
2384 edu-eatmydata-install and call it from the pre-pkgsel.d and
2385 finish-install.d scripts.
</p
>
2387 <p
>By now you might ask if this change should get into the normal
2388 Debian installer too? I suspect it should, but am not sure the
2389 current debian-installer coordinators find it useful enough. It also
2390 depend on the side effects of the change. I
'm not aware of any, but I
2391 guess we will see if the change is safe after some more testing.
2392 Perhaps there is some package in Debian depending on sync() and
2393 fsync() having effect? Perhaps it should go into its own udeb, to
2394 allow those of us wanting to enable it to do so without affecting
2397 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
2398 will break installation of all programs using gnutls because of
2399 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
2400 eatmydata package in Debian will solve it.
</p
>
2402 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
2403 the optimization work again. And I have discovered that the
2404 dpkg-divert trick is not really needed and implemented a slightly
2405 simpler approach as part of the debian-edu-install package. See
2406 tools/edu-eatmydata-install in the source package.
</p
>
2408 <p
>Update
2014-
11-
11: Unfortunately, a new
2409 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
2410 triggering on i386 made it into testing, and broke this installation
2411 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
2412 request
768893</a
> is accepted, it should be working again.
</p
>
2417 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
2418 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
2419 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
2420 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
2421 <description><p
>Yesterday, I had the pleasure of attending a talk with the
2422 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
2423 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
2424 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
2425 learn that there is a large set of publicly available key servers to
2426 use when looking for peoples public key. So far I have used
2427 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2428 were misbehaving, but those days are ended. The servers I have used
2429 up until yesterday have been slow and some times unavailable. I hope
2430 those problems are gone now.
</p
>
2432 <p
>Behind the round robin DNS entry of the
2433 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
2434 there is a pool of more than
100 keyservers which are checked every
2435 day to ensure they are well connected and up to date. It must be
2436 better than what I have used so far. :)
</p
>
2438 <p
>Yesterdays speaker told me that the service is the default
2439 keyserver provided by the default configuration in GnuPG, but this do
2440 not seem to be used in Debian. Perhaps it should?
</p
>
2442 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
2445 <p
><blockquote
><pre
>
2446 keyserver pool.sks-keyservers.net
2447 </pre
></blockquote
></p
>
2449 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
2450 entries in DNS. Just for fun, I did just that at work, so now every
2451 user of GnuPG at the University of Oslo should find a OpenGPG
2452 keyserver automatically should their need it:
</p
>
2454 <p
><blockquote
><pre
>
2455 % host -t srv _pgpkey-http._tcp.uio.no
2456 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
2458 </pre
></blockquote
></p
>
2460 <p
>Now if only
2461 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
2462 HKP lookup protocol
</a
> supported finding signature paths, I would be
2463 very happy. It can look up a given key or search for a user ID, but I
2464 normally do not want that, but to find a trust path from my key to
2465 another key. Given a user ID or key ID, I would like to find (and
2466 download) the keys representing a signature path from my key to the
2467 key in question, to be able to get a trust path between the two keys.
2468 This is as far as I can tell not possible today. Perhaps something
2469 for a future version of the protocol?
</p
>
2474 <title>From English wiki to translated PDF and epub via Docbook
</title>
2475 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
2476 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
2477 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
2478 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2479 project
</a
> provide an instruction manual for teachers, system
2480 administrators and other users that contain useful tips for setting up
2481 and maintaining a Debian Edu installation. This text is about how the
2482 text processing of this manual is handled in the project.
</p
>
2484 <p
>One goal of the project is to provide information in the native
2485 language of its users, and for this we need to handle translations.
2486 But we also want to make sure each language contain the same
2487 information, so for this we need a good way to keep the translations
2488 in sync. And we want it to be easy for our users to improve the
2489 documentation, avoiding the need to learn special formats or tools to
2490 contribute, and the obvious way to do this is to make it possible to
2491 edit the documentation using a web browser. We also want it to be
2492 easy for translators to keep the translation up to date, and give them
2493 help in figuring out what need to be translated. Here is the list of
2494 tools and the process we have found trying to reach all these
2497 <p
>We maintain the authoritative source of our manual in the
2498 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
2499 wiki
</a
>, as several wiki pages written in English. It consist of one
2500 front page with references to the different chapters, several pages
2501 for each chapter, and finally one
"collection page
" gluing all the
2502 chapters together into one large web page (aka
2503 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
2504 AllInOne page
</a
>). The AllInOne page is the one used for further
2505 processing and translations. Thanks to the fact that the
2506 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
2507 wiki.debian.org support exporting pages in
2508 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
2509 the list of pages to export using the raw version of the AllInOne
2510 page, loop over each of them to generate a Docbook XML version of the
2511 manual. This process also download images and transform image
2512 references to use the locally downloaded images. The generated
2513 Docbook XML files are slightly broken, so some post-processing is done
2514 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
2515 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2516 a handfull of images. The XML file can now be used to generate PDF, HTML
2517 and epub versions of the English manual. This is the basic step of
2518 our process, making PDF (using dblatex), HTML (using xsltproc) and
2519 epub (using dbtoepub) version from Docbook XML, and the resulting files
2520 are placed in the debian-edu-doc-en binary package.
</p
>
2522 <p
>But English documentation is not enough for us. We want translated
2523 documentation too, and we want to make it easy for translators to
2524 track the English original. For this we use the
2525 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
2526 which allow us to transform the English Docbook XML file into a
2527 translation file (a .pot file), usable with the normal gettext based
2528 translation tools used by those translating free software. The pot
2529 file is used to create and maintain translation files (several .po
2530 files), which the translations update with the native language
2531 translations of all titles, paragraphs and blocks of text in the
2532 original. The next step is combining the original English Docbook XML
2533 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2534 create a translated Docbook XML file (in this case
2535 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2536 translated, if the translation is not complete) Docbook XML file can
2537 then be used like the original to create a PDF, HTML and epub version
2538 of the documentation.
</p
>
2540 <p
>The translators use different tools to edit the .po files. We
2542 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
2543 while some use emacs and vi, others can use web based editors like
2544 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
2545 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
2546 is where the .po file end up, in our git repository. Updated
2547 translations can either be committed directly to git, or submitted as
2548 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
2549 against the debian-edu-doc package
</a
>.
</p
>
2551 <p
>One challenge is images, which both might need to be translated (if
2552 they show translated user applications), and are needed in different
2553 formats when creating PDF and HTML versions (epub is a HTML version in
2554 this regard). For this we transform the original PNG images to the
2555 needed density and format during build, and have a way to provide
2556 translated images by storing translated versions in
2557 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2558 package maintainers know more.
</p
>
2560 <p
>If you wonder what the result look like, we provide
2561 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
2562 of the documentation packages on the web
</a
>. See for example the
2563 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
2564 PDF version
</a
> or the
2565 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
2566 HTML version
</a
>. We do not yet build the epub version by default,
2567 but perhaps it will be done in the future.
</p
>
2569 <p
>To learn more, check out
2570 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
2571 debian-edu-doc package
</a
>,
2572 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
2573 manual on the wiki
</a
> and
2574 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
2575 translation instructions
</a
> in the manual.
</p
>
2580 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
2581 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
2582 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
2583 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
2584 <description><p
>It would be nice if it was easier in Debian to get all the hardware
2585 related packages relevant for the computer installed automatically.
2586 So I implemented one, using
2587 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
2588 package
</a
>. To use it, install the tasksel and isenkram packages and
2589 run tasksel as user root. You should be presented with a new option,
2590 "Hardware specific packages (autodetected by isenkram)
". When you
2591 select it, tasksel will install the packages isenkram claim is fit for
2592 the current hardware, hot pluggable or not.
<p
>
2594 <p
>The implementation is in two files, one is the tasksel menu entry
2595 description, and the other is the script used to extract the list of
2596 packages to install. The first part is in
2597 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
2600 <p
><blockquote
><pre
>
2603 Description: Hardware specific packages (autodetected by isenkram)
2604 Based on the detected hardware various hardware specific packages are
2606 Test-new-install: mark show
2608 Packages: for-current-hardware
2609 </pre
></blockquote
></p
>
2611 <p
>The second part is in
2612 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
2615 <p
><blockquote
><pre
>
2620 isenkram-autoinstall-firmware -l
2622 </pre
></blockquote
></p
>
2624 <p
>All in all, a very short and simple implementation making it
2625 trivial to install the hardware dependent package we all may want to
2626 have installed on our machines. I
've not been able to find a way to
2627 get tasksel to tell you exactly which packages it plan to install
2628 before doing the installation. So if you are curious or careful,
2629 check the output from the isenkram-* command line tools first.
</p
>
2631 <p
>The information about which packages are handling which hardware is
2632 fetched either from the isenkram package itself in
2633 /usr/share/isenkram/, from git.debian.org or from the APT package
2634 database (using the Modaliases header). The APT package database
2635 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2636 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
2637 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
2638 the python-apt code (bug
2639 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
2640 workaround I was able to get rid of the file descriptor leak and
2641 reduce the memory leak from ~
30 MiB per hardware detection down to
2642 around
2 MiB per hardware detection. It should make the desktop
2643 daemon a lot more useful. The fix is in version
0.7 uploaded to
2644 unstable today.
</p
>
2646 <p
>I believe the current way of mapping hardware to packages in
2647 Isenkram is is a good draft, but in the future I expect isenkram to
2648 use the AppStream data source for this. A proposal for getting proper
2649 AppStream support into Debian is floating around as
2650 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
2651 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
2652 project
</a
> will take place this summer to improve the situation. I
2653 look forward to seeing the result, and welcome patches for isenkram to
2654 start using the information when it is ready.
</p
>
2656 <p
>If you want your package to map to some specific hardware, either
2657 add a
"Xb-Modaliases
" header to your control file like I did in
2658 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
2659 package
</a
> or submit a bug report with the details to the isenkram
2661 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
2662 blog posts tagged isenkram
</a
> for details on the notation. I expect
2663 the information will be migrated to AppStream eventually, but for the
2664 moment I got no better place to store it.
</p
>
2669 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
2670 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
2671 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
2672 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
2673 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2674 project
</a
> is working on providing the software and hardware to make
2675 it easy for non-technical people to host their data and communication
2676 at home, and being able to communicate with their friends and family
2677 encrypted and away from prying eyes. It is still going strong, and
2678 today a major mile stone was reached.
</p
>
2680 <p
>Today, the last of the packages currently used by the project to
2681 created the system images were accepted into Debian Unstable. It was
2682 the freedombox-setup package, which is used to configure the images
2683 during build and on the first boot. Now all one need to get going is
2684 the build code from the freedom-maker git repository and packages from
2685 Debian. And once the freedombox-setup package enter testing, we can
2686 build everything directly from Debian. :)
</p
>
2688 <p
>Some key packages used by Freedombox are
2689 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
2690 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
2691 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
2692 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
2693 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
2694 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
2695 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
2696 are plans to integrate more packages into the setup. User
2697 documentation is maintained on the Debian wiki. Please
2698 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
2699 the manual
</a
> and help us improve it.
</p
>
2701 <p
>To test for yourself and create boot images with the FreedomBox
2702 setup, run this on a Debian machine using a user with sudo rights to
2703 become root:
</p
>
2705 <p
><pre
>
2706 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2707 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2709 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2711 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2712 </pre
></p
>
2714 <p
>Root access is needed to run debootstrap and mount loopback
2715 devices. See the README in the freedom-maker git repo for more
2716 details on the build. If you do not want all three images, trim the
2717 make line. Note that the virtualbox-image target is not really
2718 virtualbox specific. It create a x86 image usable in kvm, qemu,
2719 vmware and any other x86 virtual machine environment. You might need
2720 the version of vmdebootstrap in Jessie to get the build working, as it
2721 include fixes for a race condition with kpartx.
</p
>
2723 <p
>If you instead want to install using a Debian CD and the preseed
2724 method, boot a Debian Wheezy ISO and use this boot argument to load
2725 the preseed values:
</p
>
2727 <p
><pre
>
2728 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2729 </pre
></p
>
2731 <p
>I have not tested it myself the last few weeks, so I do not know if
2732 it still work.
</p
>
2734 <p
>If you wonder how to help, one task you could look at is using
2735 systemd as the boot system. It will become the default for Linux in
2736 Jessie, so we need to make sure it is usable on the Freedombox. I did
2737 a simple test a few weeks ago, and noticed dnsmasq failed to start
2738 during boot when using systemd. I suspect there are other problems
2739 too. :) To detect problems, there is a test suite included, which can
2740 be run from the plinth web interface.
</p
>
2742 <p
>Give it a go and let us know how it goes on the mailing list, and help
2743 us get the new release published. :) Please join us on
2744 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2745 irc.debian.org)
</a
> and
2746 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2747 mailing list
</a
> if you want to help make this vision come true.
</p
>
2752 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
2753 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
2754 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
2755 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
2756 <description><p
>For a while now, I have been looking for a sensible offsite backup
2757 solution for use at home. My requirements are simple, it must be
2758 cheap and locally encrypted (in other words, I keep the encryption
2759 keys, the storage provider do not have access to my private files).
2760 One idea me and my friends had many years ago, before the cloud
2761 storage providers showed up, was to use Google mail as storage,
2762 writing a Linux block device storing blocks as emails in the mail
2763 service provided by Google, and thus get heaps of free space. On top
2764 of this one can add encryption, RAID and volume management to have
2765 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2766 I never found time to implement such system. But the last few weeks I
2767 have looked at a system called
2768 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
2769 mounted network backed file system with the features I need.
</p
>
2771 <p
>S3QL is a fuse file system with a local cache and cloud storage,
2772 handling several different storage providers, any with Amazon S3,
2773 Google Drive or OpenStack API. There are heaps of such storage
2774 providers. S3QL can also use a local directory as storage, which
2775 combined with sshfs allow for file storage on any ssh server. S3QL
2776 include support for encryption, compression, de-duplication, snapshots
2777 and immutable file systems, allowing me to mount the remote storage as
2778 a local mount point, look at and use the files as if they were local,
2779 while the content is stored in the cloud as well. This allow me to
2780 have a backup that should survive fire. The file system can not be
2781 shared between several machines at the same time, as only one can
2782 mount it at the time, but any machine with the encryption key and
2783 access to the storage service can mount it if it is unmounted.
</p
>
2785 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
2786 package is included already. So to get started, run
<tt
>apt-get
2787 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
2788 Greenqloud, after reading their nice recipe on
2789 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
2790 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
2791 in Iceland more than those in USA when it come to keeping my personal
2792 data safe and private, and thus would rather spend money on a company
2793 in Iceland. Another nice recipe is available from the article
2794 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
2795 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
2796 Admin magazine. When the provider is picked, figure out how to get
2797 the API key needed to connect to the storage API. With Greencloud,
2798 the key did not show up until I had added payment details to my
2801 <p
>Armed with the API access details, it is time to create the file
2802 system. First, create a new bucket in the cloud. This bucket is the
2803 file system storage area. I picked a bucket name reflecting the
2804 machine that was going to store data there, but any name will do.
2805 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
2806 the API login and password, and a locally created password. Store it
2807 all in ~root/.s3ql/authinfo2 like this:
2809 <p
><blockquote
><pre
>
2811 storage-url: s3c://s.greenqloud.com:
443/bucket-name
2812 backend-login: API-login
2813 backend-password: API-password
2814 fs-passphrase: local-password
2815 </pre
></blockquote
></p
>
2817 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
2818 but any sensible way to create a fairly random password should do it.
2819 Armed with these details, it is now time to run mkfs, entering the API
2820 details and password to create it:
</p
>
2822 <p
><blockquote
><pre
>
2823 # mkdir -m
700 /var/lib/s3ql-cache
2824 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2825 --ssl s3c://s.greenqloud.com:
443/bucket-name
2826 Enter backend login:
2827 Enter backend password:
2828 Before using S3QL, make sure to read the user
's guide, especially
2829 the
'Important Rules to Avoid Loosing Data
' section.
2830 Enter encryption password:
2831 Confirm encryption password:
2832 Generating random encryption key...
2833 Creating metadata tables...
2843 Compressing and uploading metadata...
2844 Wrote
0.00 MB of compressed metadata.
2845 #
</pre
></blockquote
></p
>
2847 <p
>The next step is mounting the file system to make the storage available.
2849 <p
><blockquote
><pre
>
2850 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2851 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2852 Using
4 upload threads.
2853 Downloading and decompressing metadata...
2863 Mounting filesystem...
2865 Filesystem Size Used Avail Use% Mounted on
2866 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
2868 </pre
></blockquote
></p
>
2870 <p
>The file system is now ready for use. I use rsync to store my
2871 backups in it, and as the metadata used by rsync is downloaded at
2872 mount time, no network traffic (and storage cost) is triggered by
2873 running rsync. To unmount, one should not use the normal umount
2874 command, as this will not flush the cache to the cloud storage, but
2875 instead running the umount.s3ql command like this:
2877 <p
><blockquote
><pre
>
2880 </pre
></blockquote
></p
>
2882 <p
>There is a fsck command available to check the file system and
2883 correct any problems detected. This can be used if the local server
2884 crashes while the file system is mounted, to reset the
"already
2885 mounted
" flag. This is what it look like when processing a working
2886 file system:
</p
>
2888 <p
><blockquote
><pre
>
2889 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
2890 Using cached metadata.
2891 File system seems clean, checking anyway.
2892 Checking DB integrity...
2893 Creating temporary extra indices...
2894 Checking lost+found...
2895 Checking cached objects...
2896 Checking names (refcounts)...
2897 Checking contents (names)...
2898 Checking contents (inodes)...
2899 Checking contents (parent inodes)...
2900 Checking objects (reference counts)...
2901 Checking objects (backend)...
2902 ..processed
5000 objects so far..
2903 ..processed
10000 objects so far..
2904 ..processed
15000 objects so far..
2905 Checking objects (sizes)...
2906 Checking blocks (referenced objects)...
2907 Checking blocks (refcounts)...
2908 Checking inode-block mapping (blocks)...
2909 Checking inode-block mapping (inodes)...
2910 Checking inodes (refcounts)...
2911 Checking inodes (sizes)...
2912 Checking extended attributes (names)...
2913 Checking extended attributes (inodes)...
2914 Checking symlinks (inodes)...
2915 Checking directory reachability...
2916 Checking unix conventions...
2917 Checking referential integrity...
2918 Dropping temporary indices...
2919 Backing up old metadata...
2929 Compressing and uploading metadata...
2930 Wrote
0.89 MB of compressed metadata.
2932 </pre
></blockquote
></p
>
2934 <p
>Thanks to the cache, working on files that fit in the cache is very
2935 quick, about the same speed as local file access. Uploading large
2936 amount of data is to me limited by the bandwidth out of and into my
2937 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
2938 which is very close to my upload speed, and downloading the same
2939 Debian installation ISO gave me
610 kiB/s, close to my download speed.
2940 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
2941 network, not the file system code. I do not know what a good cache
2942 size would be, but suspect that the cache should e larger than your
2943 working set.
</p
>
2945 <p
>I mentioned that only one machine can mount the file system at the
2946 time. If another machine try, it is told that the file system is
2949 <p
><blockquote
><pre
>
2950 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2951 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2952 Using
8 upload threads.
2953 Backend reports that fs is still mounted elsewhere, aborting.
2955 </pre
></blockquote
></p
>
2957 <p
>The file content is uploaded when the cache is full, while the
2958 metadata is uploaded once every
24 hour by default. To ensure the
2959 file system content is flushed to the cloud, one can either umount the
2960 file system, or ask S3QL to flush the cache and metadata using
2963 <p
><blockquote
><pre
>
2964 # s3qlctrl upload-meta /s3ql
2965 # s3qlctrl flushcache /s3ql
2967 </pre
></blockquote
></p
>
2969 <p
>If you are curious about how much space your data uses in the
2970 cloud, and how much compression and deduplication cut down on the
2971 storage usage, you can use s3qlstat on the mounted file system to get
2974 <p
><blockquote
><pre
>
2976 Directory entries:
9141
2979 Total data size:
22049.38 MB
2980 After de-duplication:
21955.46 MB (
99.57% of total)
2981 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
2982 Database size:
2.39 MB (uncompressed)
2983 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2985 </pre
></blockquote
></p
>
2987 <p
>I mentioned earlier that there are several possible suppliers of
2988 storage. I did not try to locate them all, but am aware of at least
2989 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
2990 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
2991 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
2992 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
2993 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
2994 accept payment in Bitcoin. Pick one that suit your need. Some of
2995 them provide several GiB of free storage, but the prize models are
2996 quite different and you will have to figure out what suits you
2999 <p
>While researching this blog post, I had a look at research papers
3000 and posters discussing the S3QL file system. There are several, which
3001 told me that the file system is getting a critical check by the
3002 science community and increased my confidence in using it. One nice
3004 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3005 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3006 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3007 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3008 and Pamela Smith. Please have a look.
</p
>
3010 <p
>Given my problems with different file systems earlier, I decided to
3011 check out the mounted S3QL file system to see if it would be usable as
3012 a home directory (in other word, that it provided POSIX semantics when
3013 it come to locking and umask handling etc). Running
3014 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3015 test code to check file system semantics
</a
>, I was happy to discover that
3016 no error was found. So the file system can be used for home
3017 directories, if one chooses to do so.
</p
>
3019 <p
>If you do not want a locally file system, and want something that
3020 work without the Linux fuse file system, I would like to mention the
3021 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3022 provide locally encrypted backup using a command line client. It have
3023 a nicer access control system, where one can split out read and write
3024 access, allowing some systems to write to the backup and others to
3025 only read from it.
</p
>
3027 <p
>As usual, if you use Bitcoin and want to show your support of my
3028 activities, please send Bitcoin donations to my address
3029 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3034 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3035 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3036 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3037 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3038 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3039 project
</a
> is working on providing the software and hardware for
3040 making it easy for non-technical people to host their data and
3041 communication at home, and being able to communicate with their
3042 friends and family encrypted and away from prying eyes. It has been
3043 going on for a while, and is slowly progressing towards a new test
3044 release (
0.2).
</p
>
3046 <p
>And what day could be better than the Pi day to announce that the
3047 new version will provide
"hard drive
" / SD card / USB stick images for
3048 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3049 system), and can also be installed using a Debian installer preseed
3050 file. The Debian based Freedombox is now based on Debian Jessie,
3051 where most of the needed packages used are already present. Only one,
3052 the freedombox-setup package, is missing. To try to build your own
3053 boot image to test the current status, fetch the freedom-maker scripts
3055 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
3056 with a user with sudo access to become root:
3059 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3061 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3062 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3064 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3067 <p
>Root access is needed to run debootstrap and mount loopback
3068 devices. See the README for more details on the build. If you do not
3069 want all three images, trim the make line. But note that thanks to
<a
3070 href=
"https://bugs.debian.org/
741407">a race condition in
3071 vmdebootstrap
</a
>, the build might fail without the patch to the
3072 kpartx call.
</p
>
3074 <p
>If you instead want to install using a Debian CD and the preseed
3075 method, boot a Debian Wheezy ISO and use this boot argument to load
3076 the preseed values:
</p
>
3079 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3082 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
3083 recently introduced bug in apt in Jessie
</a
>, the installer will
3084 currently hang while setting up APT sources. Killing the
3085 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
3086 installation will get the installation going. This affect all
3087 installations in Jessie, and I expect it will be fixed soon.
</p
>
3089 <p
>Give it a go and let us know how it goes on the mailing list, and help
3090 us get the new release published. :) Please join us on
3091 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3092 irc.debian.org)
</a
> and
3093 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3094 mailing list
</a
> if you want to help make this vision come true.
</p
>
3099 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
3100 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
3101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
3102 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
3103 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
3104 innetgr tools, because I needed them in
3105 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
3106 ng-utils, and it has served me well. I placed the project under the
3107 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
3108 repository. But many years ago, the CVS repository was dropped (lost,
3109 not migrated to new hardware, not sure), and the project have lacked a
3110 proper home since then.
</p
>
3112 <p
>Last summer, I had a look at the package and made a new release
3113 fixing a irritating crash bug, but was unable to store the changes in
3114 a proper source control system. I applied for a project on
3115 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
3116 to follow up on it. Until today. :)
</p
>
3118 <p
>After many hours of cleaning and migration, the ng-utils project
3119 now have a new home, and a git repository with the highlight of the
3120 history of the project. I published all release tarballs and imported
3121 them into the git repository. As the project is really stable and not
3122 expected to gain new features any time soon, I decided to make a new
3123 release and call it
1.0. Visit the new project home on
3124 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
3125 if you want to check it out. The new version is also uploaded into
3126 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
3131 <title>Testing sysvinit from experimental in Debian Hurd
</title>
3132 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
3133 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
3134 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
3135 <description><p
>A few days ago I decided to try to help the Hurd people to get
3136 their changes into sysvinit, to allow them to use the normal sysvinit
3137 boot system instead of their old one. This follow up on the
3138 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
3139 Google Summer of Code work
</a
> done last summer by Justus Winter to
3140 get Debian on Hurd working more like Debian on Linux. To get started,
3141 I downloaded a prebuilt hard disk image from
3142 <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
>,
3143 and started it using virt-manager.
</p
>
3145 <p
>The first think I had to do after logging in (root without any
3146 password) was to get the network operational. I followed
3147 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
3148 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
3149 commands as root to get the machine to accept a IP address from the
3150 kvm internal DHCP server:
</p
>
3152 <p
><blockquote
><pre
>
3153 settrans -fgap /dev/netdde /hurd/netdde
3154 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
3155 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
3157 </pre
></blockquote
></p
>
3159 <p
>After this, the machine had internet connectivity, and I could
3160 upgrade it and install the sysvinit packages from experimental and
3161 enable it as the default boot system in Hurd.
</p
>
3163 <p
>But before I did that, I set a password on the root user, as ssh is
3164 running on the machine it for ssh login to work a password need to be
3165 set. Also, note that a bug somewhere in openssh on Hurd block
3166 compression from working. Remember to turn that off on the client
3169 <p
>Run these commands as root to upgrade and test the new sysvinit
3172 <p
><blockquote
><pre
>
3173 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
3174 deb http://http.debian.net/debian/ experimental main
3177 apt-get dist-upgrade
3178 apt-get install -t experimental initscripts sysv-rc sysvinit \
3179 sysvinit-core sysvinit-utils
3180 update-alternatives --config runsystem
3181 </pre
></blockquote
></p
>
3183 <p
>To reboot after switching boot system, you have to use
3184 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
3185 yet a sysvinit process able to receive the signals from the normal
3186 'reboot
' command. After switching to sysvinit as the boot system,
3187 upgrading every package and rebooting, the network come up with DHCP
3188 after boot as it should, and the settrans/pkill hack mentioned at the
3189 start is no longer needed. But for some strange reason, there are no
3190 longer any login prompt in the virtual console, so I logged in using
3193 <p
>Note that there are some race conditions in Hurd making the boot
3194 fail some times. No idea what the cause is, but hope the Hurd porters
3195 figure it out. At least Justus said on IRC (#debian-hurd on
3196 irc.debian.org) that they are aware of the problem. A way to reduce
3197 the impact is to upgrade to the Hurd packages built by Justus by
3198 adding this repository to the machine:
</p
>
3200 <p
><blockquote
><pre
>
3201 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
3202 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3204 </pre
></blockquote
></p
>
3206 <p
>At the moment the prebuilt virtual machine get some packages from
3207 http://ftp.debian-ports.org/debian, because some of the packages in
3208 unstable do not yet include the required patches that are lingering in
3209 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
3211 <p
><blockquote
><pre
>
3212 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
3213 i emacs - GNU Emacs editor (metapackage)
3214 i gdb - GNU Debugger
3215 i hurd-recommended - Miscellaneous translators
3216 i isc-dhcp-client - ISC DHCP client
3217 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3218 i libc-bin - Embedded GNU C Library: Binaries
3219 i libc-dev-bin - Embedded GNU C Library: Development binaries
3220 i libc0.3 - Embedded GNU C Library: Shared libraries
3221 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3222 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3223 i multiarch-support - Transitional package to ensure multiarch compatibilit
3224 i A x11-common - X Window System (X.Org) infrastructure
3225 i xorg - X.Org X Window System
3226 i A xserver-xorg - X.Org X server
3227 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3229 </pre
></blockquote
></p
>
3231 <p
>All in all, testing hurd has been an interesting experience. :)
3232 X.org did not work out of the box and I never took the time to follow
3233 the porters instructions to fix it. This time I was interested in the
3234 command line stuff.
<p
>
3239 <title>New chrpath release
0.16</title>
3240 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
3241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
3242 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
3243 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
3244 find problems in C, C++ and Java code using static source code
3245 analysis. It can detect a lot of different problems, and is very
3246 useful to find memory and locking bugs in the error handling part of
3247 the source. The company behind it provide
3248 <a href=
"https://scan.coverity.com/
">check of free software projects as
3249 a community service
</a
>, and many hundred free software projects are
3250 already checked. A few days ago I decided to have a closer look at
3251 the Coverity system, and discovered that the
3252 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
3253 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
3254 projects I am involved with was already registered. But these are
3255 fairly big, and I would also like to have a small and easy project to
3256 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
3257 checking of the chrpath project
</a
>. It was
3258 added to the checker and discovered seven potential defects. Six of
3259 these were real, mostly resource
"leak
" when the program detected an
3260 error. Nothing serious, as the resources would be released a fraction
3261 of a second later when the program exited because of the error, but it
3262 is nice to do it right in case the source of the program some time in
3263 the future end up in a library. Having fixed all defects and added
3264 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
3265 mailing list for the chrpath developers
</a
>, I decided it was time to
3266 publish a new release. These are the release notes:
</p
>
3268 <p
>New in
0.16 released
2014-
01-
14:
</p
>
3272 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
3273 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
3274 <li
>Mention new project mailing list in the documentation.
</li
>
3279 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3280 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
3281 project if something is wrong with the new release. The test suite
3282 did not discover any old errors, so if you find a new one, please also
3283 include a test suite check.
</p
>
3288 <title>New chrpath release
0.15</title>
3289 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
3290 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
3291 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
3292 <description><p
>After many years break from the package and a vain hope that
3293 development would be continued by someone else, I finally pulled my
3294 acts together this morning and wrapped up a new release of chrpath,
3295 the command line tool to modify the rpath and runpath of already
3296 compiled ELF programs. The update was triggered by the persistence of
3297 Isha Vishnoi at IBM, which needed a new config.guess file to get
3298 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
3299 is working on. I checked the
3300 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
3301 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
3302 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
3303 packages for interesting patches (failed to find the source from
3304 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3305 These are the release notes:
</p
>
3307 <p
>New in
0.15 released
2013-
11-
24:
</p
>
3311 <li
>Updated config.sub and config.guess from the GNU project to work
3312 with newer architectures. Thanks to isha vishnoi for the heads
3315 <li
>Updated README with current URLs.
</li
>
3317 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3318 Matthias Klose.
</li
>
3320 <li
>Added missing help for -k|--keepgoing option, using patch by
3321 Petr Machata found in Fedora.
</li
>
3323 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
3324 .dynamic is a NULL terminated string. Based on patch found in
3325 Fedora credited Axel Thimm and Christian Krause.
</li
>
3330 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3331 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
3332 project if something is wrong with the new release. The test suite
3333 did not discover any old errors, so if you find a new one, please also
3334 include a testsuite check.
</p
>
3339 <title>Debian init.d boot script example for rsyslog
</title>
3340 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
3341 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
3342 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
3343 <description><p
>If one of the points of switching to a new init system in Debian is
3344 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
3345 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
3346 init.d scripts at all. Here is an example init.d script, ie a rewrite
3347 of /etc/init.d/rsyslog:
</p
>
3349 <p
><pre
>
3350 #!/lib/init/init-d-script
3353 # Required-Start: $remote_fs $time
3354 # Required-Stop: umountnfs $time
3355 # X-Stop-After: sendsigs
3356 # Default-Start:
2 3 4 5
3357 # Default-Stop:
0 1 6
3358 # Short-Description: enhanced syslogd
3359 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3360 # It is quite compatible to stock sysklogd and can be
3361 # used as a drop-in replacement.
3363 DESC=
"enhanced syslogd
"
3364 DAEMON=/usr/sbin/rsyslogd
3365 </pre
></p
>
3367 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
3368 script was
137 lines, and the above is just
15 lines, most of it meta
3369 info/comments.
</p
>
3371 <p
>How to do this, you ask? Well, one create a new script
3372 /lib/init/init-d-script looking something like this:
3374 <p
><pre
>
3377 # Define LSB log_* functions.
3378 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
3379 # and status_of_proc is working.
3380 . /lib/lsb/init-functions
3383 # Function that starts the daemon/service
3389 #
0 if daemon has been started
3390 #
1 if daemon was already running
3391 #
2 if daemon could not be started
3392 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
3394 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3397 # Add code here, if necessary, that waits for the process to be ready
3398 # to handle requests from services started subsequently which depend
3399 # on this one. As a last resort, sleep for some time.
3403 # Function that stops the daemon/service
3408 #
0 if daemon has been stopped
3409 #
1 if daemon was already stopped
3410 #
2 if daemon could not be stopped
3411 # other if a failure occurred
3412 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
3413 RETVAL=
"$?
"
3414 [
"$RETVAL
" =
2 ]
&& return
2
3415 # Wait for children to finish too if this is a daemon that forks
3416 # and if the daemon is only ever run from this initscript.
3417 # If the above conditions are not satisfied then add some other code
3418 # that waits for the process to drop all resources that could be
3419 # needed by services started subsequently. A last resort is to
3420 # sleep for some time.
3421 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
3422 [
"$?
" =
2 ]
&& return
2
3423 # Many daemons don
't delete their pidfiles when they exit.
3425 return
"$RETVAL
"
3429 # Function that sends a SIGHUP to the daemon/service
3433 # If the daemon can reload its configuration without
3434 # restarting (for example, when it is sent a SIGHUP),
3435 # then implement that here.
3437 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
3442 scriptbasename=
"$(basename $
1)
"
3443 echo
"SN: $scriptbasename
"
3444 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
3445 script=
"$
1"
3452 NAME=$(basename $DAEMON)
3453 PIDFILE=/var/run/$NAME.pid
3455 # Exit if the package is not installed
3456 #[ -x
"$DAEMON
" ] || exit
0
3458 # Read configuration variable file if it is present
3459 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
3461 # Load the VERBOSE setting and other rcS variables
3464 case
"$
1" in
3466 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
3468 case
"$?
" in
3469 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3470 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3474 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
3476 case
"$?
" in
3477 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3478 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3482 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
3484 #reload|force-reload)
3486 # If do_reload() is not implemented then leave this commented out
3487 # and leave
'force-reload
' as an alias for
'restart
'.
3489 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
3493 restart|force-reload)
3495 # If the
"reload
" option is implemented then remove the
3496 #
'force-reload
' alias
3498 log_daemon_msg
"Restarting $DESC
" "$NAME
"
3500 case
"$?
" in
3503 case
"$?
" in
3505 1) log_end_msg
1 ;; # Old process is still running
3506 *) log_end_msg
1 ;; # Failed to start
3516 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
3522 </pre
></p
>
3524 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
3525 lot. I did not really polish the approach, so it might not always
3526 work out of the box, but you get the idea. I did not try very hard to
3527 optimize it nor make it more robust either.
</p
>
3529 <p
>A better argument for switching init system in Debian than reducing
3530 the size of init scripts (which is a good thing to do anyway), is to
3531 get boot system that is able to handle the kernel events sensibly and
3532 robustly, and do not depend on the boot to run sequentially. The boot
3533 and the kernel have not behaved sequentially in years.
</p
>
3538 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
3539 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
3540 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
3541 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
3542 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
3543 remote display access is the preferred solution with oVirt and RedHat
3544 Enterprise Virtualization, and I was sad to discover the other day
3545 that the browser plugin needed to use these systems seamlessly was
3546 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
3547 for a package
</a
> was from
2012-
04-
10 with no progress since
3548 2013-
04-
01, so I decided to wrap up a package based on the great work
3549 from Cajus Pollmeier and put it in a collab-maint maintained git
3550 repository to get a package I could use. I would very much like
3551 others to help me maintain the package (or just take over, I do not
3552 mind), but as no-one had volunteered so far, I just uploaded it to
3553 NEW. I hope it will be available in Debian in a few days.
</p
>
3555 <p
>The source is now available from
3556 <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
>
3561 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
3562 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
3563 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
3564 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
3565 <description><p
>The
3566 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
3567 program is a a very nice system to create virtual machine images. It
3568 create a image file, add a partition table, mount it and run
3569 debootstrap in the mounted directory to create a Debian system on a
3570 stick. Yesterday, I decided to try to teach it how to make images for
3571 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
3572 of a plan to simplify the build system for
3573 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
3574 project
</a
>. The FreedomBox project already uses vmdebootstrap for
3575 the virtualbox images, but its current build system made multistrap
3576 based system for Dreamplug images, and it is lacking support for
3577 Raspberry Pi.
</p
>
3579 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
3580 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3581 code and adjusted it to be able to build armel images on my amd64
3582 Debian laptop. I ended up giving vmdebootstrap five new options,
3583 allowing me to replicate the image creation process I use to make
3584 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
3585 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
3586 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
3587 call debootstrap with --foreign and to copy the handler into the
3588 generated chroot before running the second stage. This allow
3589 vmdebootstrap to create armel images on an amd64 host. Next I added
3590 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
3591 fstype
</tt
> to teach it to create a separate /boot/ partition with the
3592 given file system type, allowing me to create an image with a vfat
3593 partition for the /boot/ stuff. I also added a
<tt
>--variant
3594 variant
</tt
> option to allow me to create smaller images without the
3595 Debian base system packages installed. Finally, I added an option
3596 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
3597 as a boot loader. It is not needed on the Raspberry Pi and probably
3598 most other non-x86 architectures. The changes were accepted by the
3599 upstream author of vmdebootstrap yesterday and today, and is now
3601 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
3602 upstream project page
</a
>.
</p
>
3604 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
3605 create a small script (the customize script) to add the non-free
3606 binary blob needed to boot the Raspberry Pi and the APT source
3609 <p
><pre
>
3611 set -e # Exit on first error
3612 rootdir=
"$
1"
3613 cd
"$rootdir
"
3614 cat
&lt;
&lt;EOF
> etc/apt/sources.list
3615 deb http://http.debian.net/debian/ jessie main contrib non-free
3617 # Install non-free binary blob needed to boot Raspberry Pi. This
3618 # install a kernel somewhere too.
3619 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3620 -O $rootdir/usr/bin/rpi-update
3621 chmod a+x $rootdir/usr/bin/rpi-update
3622 mkdir -p $rootdir/lib/modules
3623 touch $rootdir/boot/start.elf
3624 chroot $rootdir rpi-update
3625 </pre
></p
>
3627 <p
>Next, fetch the latest vmdebootstrap script and call it like this
3628 to build the image:
</p
>
3631 sudo ./vmdebootstrap \
3634 --distribution jessie \
3635 --mirror http://http.debian.net/debian \
3644 --root-password raspberry \
3645 --hostname raspberrypi \
3646 --foreign /usr/bin/qemu-arm-static \
3647 --customize `pwd`/customize \
3649 --package git-core \
3650 --package binutils \
3651 --package ca-certificates \
3654 </pre
></p
>
3656 <p
>The list of packages being installed are the ones needed by
3657 rpi-update to make the image bootable on the Raspberry Pi, with the
3658 exception of netbase, which is needed by debootstrap to find
3659 /etc/hosts with the minbase variant. I really wish there was a way to
3660 set up an Raspberry Pi using only packages in the Debian archive, but
3661 that is not possible as far as I know, because it boots from the GPU
3662 using a non-free binary blob.
</p
>
3664 <p
>The build host need debootstrap, kpartx and qemu-user-static and
3665 probably a few others installed. I have not checked the complete
3666 build dependency list.
</p
>
3668 <p
>The resulting image will not use the hardware floating point unit
3669 on the Raspberry PI, because the armel architecture in Debian is not
3670 optimized for that use. So the images created will be a bit slower
3671 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
3676 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
3677 <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>
3678 <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>
3679 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
3680 <description><p
>The last few days I came across a few good causes that should get
3681 wider attention. I recommend signing and donating to each one of
3684 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
3685 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
3686 Women program which is a Google Summer of Code like initiative to get
3687 more women involved in free software. One debian sponsor has offered
3688 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
3689 earmarked
</a
> for this initiative. I donated a few minutes ago, and
3690 hope you will to. :)
</p
>
3692 <p
>And the Electronic Frontier Foundation just announced plans to
3693 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
3694 documentaries about the excessive spying
</a
> on every Internet user that
3695 take place these days, and their need to fund the work. I
've already
3696 donated. Are you next?
</p
>
3698 <p
>For my Norwegian audience, the organisation Studentenes og
3699 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3700 statement under the heading
3701 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
3702 Access
</a
> for those of us asking for more focus on open access in the
3703 Norwegian government. So far
499 signatures. I hope you will sign it
3709 <title>Videos about the Freedombox project - for inspiration and learning
</title>
3710 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
3711 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
3712 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
3713 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
3714 project
</a
> have been going on for a while, and have presented the
3715 vision, ideas and solution several places. Here is a little
3716 collection of videos of talks and presentation of the project.
</p
>
3720 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
3721 2,
5 minute marketing film
</a
> (Youtube)
</li
>
3723 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
3724 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
3726 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
3727 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3728 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
3729 (Youtube)
</li
>
3731 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
3732 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
3734 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
3735 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
3737 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
3738 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3739 York City in
2012</a
> (Youtube)
</li
>
3741 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
3742 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
3743 (Youtube)
</li
>
3745 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
3746 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
3748 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
3749 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
3751 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
3752 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3753 2013</a
> (Youtube)
</li
>
3757 <p
>A larger list is available from
3758 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
3759 Freedombox Wiki
</a
>.
</p
>
3761 <p
>On other news, I am happy to report that Freedombox based on Debian
3762 Jessie is coming along quite well, and soon both Owncloud and using
3763 Tor should be available for testers of the Freedombox solution. :) In
3764 a few weeks I hope everything needed to test it is included in Debian.
3765 The withsqlite package is already in Debian, and the plinth package is
3766 pending in NEW. The third and vital part of that puzzle is the
3767 metapackage/setup framework, which is still pending an upload. Join
3768 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
3769 (#freedombox on irc.debian.org)
</a
> and
3770 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3771 mailing list
</a
> if you want to help make this vision come true.
</p
>
3776 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
3777 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
3778 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
3779 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
3780 <description><p
>I was introduced to the
3781 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
3782 in
2010, when Eben Moglen presented his vision about serving the need
3783 of non-technical people to keep their personal information private and
3784 within the legal protection of their own homes. The idea is to give
3785 people back the power over their network and machines, and return
3786 Internet back to its intended peer-to-peer architecture. Instead of
3787 depending on a central service, the Freedombox will give everyone
3788 control over their own basic infrastructure.
</p
>
3790 <p
>I
've intended to join the effort since then, but other tasks have
3791 taken priority. But this summers nasty news about the misuse of trust
3792 and privilege exercised by the
"western
" intelligence gathering
3793 communities increased my eagerness to contribute to a point where I
3794 actually started working on the project a while back.
</p
>
3796 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
3797 Debian initiative
</a
> based on the vision from Eben Moglen, is to
3798 create a simple and cheap Debian based appliance that anyone can hook
3799 up in their home and get access to secure and private services and
3800 communication. The initial deployment platform have been the
3801 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
3802 which is a piece of hardware I do not own. So to be able to test what
3803 the current Freedombox setup look like, I had to come up with a way to install
3804 it on some hardware I do have access to. I have rewritten the
3805 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
3806 image build framework to use .deb packages instead of only copying
3807 setup into the boot images, and thanks to this rewrite I am able to
3808 set up any machine supported by Debian Wheezy as a Freedombox, using
3809 the previously mentioned deb (and a few support debs for packages
3810 missing in Debian).
</p
>
3812 <p
>The current Freedombox setup consist of a set of bootstrapping
3814 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
3815 and a administrative web interface
3816 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
3817 withsqlite), as well as a privacy enhancing proxy based on
3818 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
3819 (freedombox-privoxy). There is also a web/javascript based XMPP
3820 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
3821 trying (unsuccessfully so far) to talk to the XMPP server
3822 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
3823 web interface is pluggable, and the goal is to use it to enable OpenID
3824 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3825 this is really working yet, see
3826 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
3827 project TODO
</a
> for links to GIT repositories. Most of the code is
3828 on github at the moment. The HTTP proxy is operational out of the
3829 box, and the admin web interface can be used to add/remove plinth
3830 users. I
've not been able to do anything else with it so far, but
3831 know there are several branches spread around github and other places
3832 with lots of half baked features.
</p
>
3834 <p
>Anyway, if you want to have a look at the current state, the
3835 following recipes should work to give you a test machine to poke
3838 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
3842 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
3843 <li
>Boot from it, either as CD or USB stick.
</li
>
3844 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
3845 to the Debian installer:
<p
>
3846 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
3848 <li
>Answer the few language/region/password questions and pick disk to
3849 install on.
</li
>
3851 <li
>When the installation is finished and the machine have rebooted a
3852 few times, your Freedombox is ready for testing.
</li
>
3856 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
3860 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
3861 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
3862 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
3864 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
3865 </pre
></li
>
3866 <li
><p
>Run this as root:
</p
>
3868 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3871 apt-get install freedombox-setup
3872 /usr/lib/freedombox/setup
3873 </pre
></li
>
3874 <li
>Reboot into your freshly created Freedombox.
</li
>
3878 <p
>You can test it on other architectures too, but because the
3879 freedombox-privoxy package is binary, it will only work as intended on
3880 the architectures where I have had time to build the binary and put it
3881 in my APT repository. But do not let this stop you. It is only a
3882 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
3884 <p
>Note that by default Freedombox is a DHCP server on the
3885 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
3886 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
3887 disable
</tt
>" as root.
</p
>
3889 <p
>Please let me know if this works for you, or if you have any
3890 problems. We gather on the IRC channel
3891 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
3892 irc.debian.org and the
3893 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
3894 mailing list
</a
>.
</p
>
3896 <p
>Once you get your freedombox operational, you can visit
3897 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
3898 welcome screen (dead end - do not be surprised if you are unable to
3899 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
3900 to look at the rest of plinth. The default user is
'admin
' and the
3901 default password is
'secret
'.
</p
>
3906 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
3907 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
3908 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
3909 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
3910 <description><p
>Earlier, I reported about
3911 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
3912 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
3913 told by IBM that the original disk should be thrown away. And as
3914 there no longer was a problem if I bricked the firmware, I decided
3915 today to try to install Intel firmware to replace the Lenovo firmware
3916 currently on the disk.
</p
>
3918 <p
>I searched the Intel site for firmware, and found
3919 <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
>
3920 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3921 according to the site should contain the latest firmware for SSD
3922 disks. I inserted the broken disk in one of my spare laptops and
3923 booted the ISO from a USB stick. The disk was recognized, but the
3924 program claimed the newest firmware already were installed and refused
3925 to insert any Intel firmware. So no change, and the disk is still
3926 unable to handle write load. :( I guess the only way to get them
3927 working would be if Lenovo releases new firmware. No idea how likely
3928 that is. Anyway, just blogging about this test for completeness. I
3929 got a working Samsung disk, and see no point in spending more time on
3930 the broken disks.
</p
>
3935 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
3936 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
3937 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
3938 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
3939 <description><p
>Today I switched to
3940 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
3941 new laptop
</a
>. I
've previously written about the problems I had with
3942 my new Thinkpad X230, which was delivered with an
3943 <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
3944 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
3945 sustained writes. My hardware supplier have been very forthcoming in
3946 trying to find a solution, and after first trying with another
3947 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
3948 disk instead to fix it once and for all. The Samsung disk survived
3949 the installation of Debian with encrypted disks (filling the disk with
3950 random data during installation killed the first two), and I thus
3951 decided to trust it with my data. I have installed it as a Debian Edu
3952 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3953 server at home using Kerberos and LDAP, and will use it as my work
3954 station from now on.
</p
>
3956 <p
>As this is a solid state disk with no moving parts, I believe the
3957 Debian Wheezy default installation need to be tuned a bit to increase
3958 performance and increase life time of the disk. The Linux kernel and
3959 user space applications do not yet adjust automatically to such
3960 environment. To make it easier for my self, I created a draft Debian
3961 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
3962 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
3963 for the ssd-setup package
</a
> is available from collab-maint, and it
3964 is set up to adjust the setup of the machine by just installing the
3965 package. If there is any non-SSD disk in the machine, the package
3966 will refuse to install, as I did not try to write any logic to sort
3967 file systems in SSD and non-SSD file systems.
</p
>
3969 <p
>I consider the package a draft, as I am a bit unsure how to best
3970 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3971 where I set up the machine with one large encrypted partition (in
3972 addition to /boot), put LVM on top of this and set up partitions on
3973 top of this again. See the README file in the package source for the
3974 references I used to pick the settings. At the moment these
3975 parameters are tuned:
</p
>
3979 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
3980 (adding discard to /etc/crypttab)
</li
>
3982 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
3983 this case a cryptsetup partition) by changing issue_discards from
3984 0 to
1 in /etc/lvm/lvm.conf.
</li
>
3986 <li
>Set relatime as a file system option for ext3 and ext4 file
3989 <li
>Tell swap to use TRIM commands by adding
'discard
' to
3990 /etc/fstab.
</li
>
3992 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
3994 <li
>Run fstrim on every ext3 and ext4 file system every night (from
3995 cron.daily).
</li
>
3997 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
3998 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4002 <p
>During installation, I cancelled the part where the installer fill
4003 the disk with random data, as this would kill the SSD performance for
4004 little gain. My goal with the encrypted file system is to ensure
4005 those stealing my laptop end up with a brick and not a working
4006 computer. I have no hope in keeping the really resourceful people
4007 from getting the data on the disk (see
4008 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4009 Thus I concluded that adding the discard option to crypttab is the
4010 right thing to do.
</p
>
4012 <p
>I considered using the noop I/O scheduler, as several recommended
4013 it for SSD, but others recommended deadline and a benchmark I found
4014 indicated that deadline might be better for interactive use.
</p
>
4016 <p
>I also considered using the
'discard
' file system option for ext3
4017 and ext4, but read that it would give a performance hit ever time a
4018 file is removed, and thought it best to that that slowdown once a day
4019 instead of during my work.
</p
>
4021 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4022 this is already done by Debian Edu.
</p
>
4024 <p
>I have not yet started on the user space tuning. I expect
4025 iceweasel need some tuning, and perhaps other applications too, but
4026 have not yet had time to investigate those parts.
</p
>
4028 <p
>The package should work on Ubuntu too, but I have not yet tested it
4031 <p
>As for the answer to the question in the title of this blog post,
4032 as far as I know, the only solution I know about is to replace the
4033 disk. It might be possible to flash it with Intel firmware instead of
4034 the Lenovo firmware. But I have not tried and did not want to do so
4035 without approval from Lenovo as I wanted to keep the warranty on the
4036 disk until a solution was found and they wanted the broken disks
4042 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4043 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4044 <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>
4045 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
4046 <description><p
>A few days ago, I wrote about
4047 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
4048 problems I experienced with my new X230 and its SSD disk
</a
>, which
4049 was dying during installation because it is unable to cope with
4050 sustained write. My supplier is in contact with
4051 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
4052 replacement disk to try to fix the problem. They decided to send an
4053 identical model, so my hopes for a permanent fix was slim.
</p
>
4055 <p
>Anyway, today I got the replacement disk and tried to install
4056 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4057 same firmware version as the original. This time my hope raised
4058 slightly as the installation progressed, as the original disk used to
4059 die after
4-
7% of the disk was written to, while this time it kept
4060 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
4061 died again and I was back on square one. I still do not have a new
4062 laptop with a disk I can trust. I can not live with a disk that might
4063 lock up when I download a new
4064 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
4065 other large files. I look forward to hearing from my supplier with
4066 the next proposal from Lenovo.
</p
>
4068 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
4069 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4070 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4071 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
4072 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4073 P/N
45N8295, P0C38732.
</p
>
4075 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
4076 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
4077 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4078 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
4079 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4080 P/N
45N8295, P0C38732.
</p
>
4082 <p
>The only difference is in the first number (serial number?), ISN,
4083 SA, date and WNPP values. Mentioning all the details here in case
4084 someone is able to use the information to find a way to identify the
4085 failing disk among working ones (if any such working disk actually
4091 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
4092 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
4093 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
4094 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
4095 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
4096 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4097 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
4098 member assosiation NUUG
</a
> and
4099 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
4100 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
4101 Bitraf
</a
>.
</p
>
4103 <p
>It starts
10:
00 and continue until late evening. Everyone is
4104 welcome, and there is no fee to participate. There is on the other
4105 hand limited space, and only room for
30 people. Please put your name
4106 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
4107 wiki page
</a
> if you plan to join us.
</p
>
4112 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
4113 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
4114 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
4115 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
4116 <description><p
>Half a year ago, I reported that I had to find a
4117 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
4118 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
4119 time to spend on it, and it took a while to find a model I believe
4120 will do the job, but two days ago the replacement finally arrived. I
4122 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
4123 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4124 a roaming workstation, and it seemed to work flawlessly. But my
4125 second installation with encrypted disk was not as successful. More
4126 on that below.
</p
>
4128 <p
>I had a hard time trying to track down a good laptop, as my most
4129 important requirements (robust and with a good keyboard) are never
4130 listed in the feature list. But I did get good help from the search
4131 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4132 allowed me to limit the list of interesting laptops based on my other
4133 requirements. A bit surprising that SSD disk are not disks according
4134 to that search interface, so I had to drop specifying the number of
4135 disks from my search parameters. I also asked around among friends to
4136 get their impression on keyboards and robustness.
</p
>
4138 <p
>So the new laptop arrived, and it is quite a lot wider than the
4139 X41. I am not quite convinced about the keyboard, as it is
4140 significantly wider than my old keyboard, and I have to stretch my
4141 hand a lot more to reach the edges. But the key response is fairly
4142 good and the individual key shape is fairly easy to handle, so I hope
4143 I will get used to it. My old X40 was starting to fail, and I really
4144 needed a new laptop now. :)
</p
>
4146 <p
>Turning off the touch pad was simple. All it took was a quick
4147 visit to the BIOS during boot it disable it.
</p
>
4149 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
4150 lock up during load. And this happen when installing Debian Wheezy
4151 with encrypted disk, while the disk is being filled with random data.
4152 I also tested to install Ubuntu Raring, and it happen there too if I
4153 reenable the code to fill the disk with random data (it is disabled by
4154 default in Ubuntu). And the bug with is already known. It was
4155 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
4156 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
4157 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4158 kernel developers as
4159 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
4160 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
4161 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4162 Lenovo forums, both for
4163 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
4164 2012-
11-
10</a
> and for
4165 <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
4166 03-
20-
2013</a
>. The problem do not only affect installation. The
4167 reports state that the disk lock up during use if many writes are done
4168 on the disk, so it is much no use to work around the installation
4169 problem and end up with a computer that can lock up at any moment.
4171 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
4172 available
</a
> that will lock up the hard drive after running a few
4173 minutes by writing to a file.
</p
>
4175 <p
>I
've contacted my supplier and asked how to handle this, and after
4176 contacting PCHELP Norway (request
01D1FDP) which handle support
4177 requests for Lenovo, his first suggestion was to upgrade the disk
4178 firmware. Unfortunately there is no newer firmware available from
4179 Lenovo, as my disk already have the most recent one (version LF1i). I
4180 hope to hear more from him today and hope the problem can be
4186 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
4187 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
4188 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
4189 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
4190 <description><p
>Half a year ago, I reported that I had to find a replacement for my
4191 trusty old Thinkpad X41. Unfortunately I did not have much time to
4192 spend on it, but today the replacement finally arrived. I ended up
4193 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
4194 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
4195 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4196 this, it is installing what I hope will be a more final installation,
4197 with a encrypted hard drive to ensure any dope head stealing it end up
4198 with an expencive door stop.
</p
>
4200 <p
>I had a hard time trying to track down a good laptop, as my most
4201 important requirements (robust and with a good keyboard) are never
4202 listed in the feature list. But I did get good help from the search
4203 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4204 allowed me to limit the list of interesting laptops based on my other
4205 requirements. A bit surprising that SSD disk are not disks, so I had
4206 to drop number of disks from my search parameters.
</p
>
4208 <p
>I am not quite convinced about the keyboard, as it is significantly
4209 wider than my old keyboard, and I have to stretch my hand a lot more
4210 to reach the edges. But the key response is fairly good and the
4211 individual key shape is fairly easy to handle, so I hope I will get
4212 used to it. My old X40 was starting to fail, and I really needed a
4213 new laptop now. :)
</p
>
4215 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
4220 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
4221 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
4222 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
4223 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
4224 <description><p
>It annoys me when the computer fail to do automatically what it is
4225 perfectly capable of, and I have to do it manually to get things
4226 working. One such task is to find out what firmware packages are
4227 needed to get the hardware on my computer working. Most often this
4228 affect the wifi card, but some times it even affect the RAID
4229 controller or the ethernet card. Today I pushed version
0.4 of the
4230 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
4231 including a new script isenkram-autoinstall-firmware handling the
4232 process of asking all the loaded kernel modules what firmware files
4233 they want, find debian packages providing these files and install the
4234 debian packages. Here is a test run on my laptop:
</p
>
4236 <p
><pre
>
4237 # isenkram-autoinstall-firmware
4238 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4239 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4240 info: locating packages with the requested firmware files
4241 info: Updating APT sources after adding non-free APT source
4242 info: trying to install firmware-ipw2x00
4245 Preconfiguring packages ...
4246 Selecting previously deselected package firmware-ipw2x00.
4247 (Reading database ...
259727 files and directories currently installed.)
4248 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4249 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
4251 </pre
></p
>
4253 <p
>When all the requested firmware is present, a simple message is
4254 printed instead:
</p
>
4256 <p
><pre
>
4257 # isenkram-autoinstall-firmware
4258 info: did not find any firmware files requested by loaded kernel modules. exiting
4260 </pre
></p
>
4262 <p
>It could use some polish, but it is already working well and saving
4263 me some time when setting up new machines. :)
</p
>
4265 <p
>So, how does it work? It look at the set of currently loaded
4266 kernel modules, and look up each one of them using modinfo, to find
4267 the firmware files listed in the module meta-information. Next, it
4268 download the Contents file from a nearby APT mirror, and search for
4269 the firmware files in this file to locate the package with the
4270 requested firmware file. If the package is in the non-free section, a
4271 non-free APT source is added and the package is installed using
4272 <tt
>apt-get install
</tt
>. The end result is a slightly better working
4275 <p
>I hope someone find time to implement a more polished version of
4276 this script as part of the hw-detect debian-installer module, to
4277 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
4278 #
655507</a
>. There really is no need to insert USB sticks with
4279 firmware during a PXE install when the packages already are available
4280 from the nearby Debian mirror.
</p
>
4285 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
4286 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
4287 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
4288 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
4289 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4290 the screen just turn black when Linux boot, either during installation
4291 or on first boot from the hard disk. I
've seen it once in a while the
4292 last few years, but only recently understood the cause. I
've seen it
4293 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4294 The reason seem to be in the wiring of some laptops. The system to
4295 control the screen background light is inverted, so when Linux try to
4296 turn the brightness fully on, it end up turning it off instead. I do
4297 not know which Linux drivers are affected, but this post is about the
4298 i915 driver used by the
4299 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4300 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
4302 <p
>The problem can be worked around two ways. Either by adding
4303 i915.invert_brightness=
1 as a kernel option, or by adding a file in
4304 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
4305 option when it load the i915 kernel module. On Debian and Ubuntu, it
4306 can be done by running these commands as root:
</p
>
4309 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
4310 update-initramfs -u -k all
4313 <p
>Since March
2012 there is
4314 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
4315 mechanism in the Linux kernel
</a
> to tell the i915 driver which
4316 hardware have this problem, and get the driver to invert the
4317 brightness setting automatically. To use it, one need to add a row in
4318 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
4319 intel_quirks array
</a
> in the driver source
4320 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
4321 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
4322 number (vendor number
8086 is assumed) and subdevice vendor and device
4325 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
4326 -vvnn
</tt
> for the video card in question:
</p
>
4328 <p
><pre
>
4329 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
4330 3rd Gen Core processor Graphics Controller [
8086:
0156] \
4331 (rev
09) (prog-if
00 [VGA controller])
4332 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
4333 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4334 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4335 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
4336 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
4338 Interrupt: pin A routed to IRQ
42
4339 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
4340 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
4341 Region
4: I/O ports at
4000 [size=
64]
4342 Expansion ROM at
<unassigned
> [disabled]
4343 Capabilities:
<access denied
>
4344 Kernel driver in use: i915
4345 </pre
></p
>
4347 <p
>The resulting intel_quirks entry would then look like this:
</p
>
4349 <p
><pre
>
4350 struct intel_quirk intel_quirks[] = {
4352 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4353 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
4356 </pre
></p
>
4358 <p
>According to the kernel module instructions (as seen using
4359 <tt
>modinfo i915
</tt
>), information about hardware needing the
4360 invert_brightness flag should be sent to the
4361 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
4362 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
4363 developers. But my email about the laptop sent
2013-
06-
03 have not
4365 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
4366 web archive for the mailing list
</a
>, so I suspect they do not accept
4367 emails from non-subscribers. Because of this, I sent my patch also to
4368 the Debian bug tracking system instead as
4369 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
4370 sure the patch is not lost.
</p
>
4372 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
4373 with this problem working properly with Linux. If you use Gnome, your
4374 worries should be over at this point. But if you use KDE, there is
4375 something in KDE ignoring the invert_brightness setting and turning on
4376 the screen during login. I
've reported it to Debian as
4377 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
4378 have no idea yet how to figure out exactly what subsystem is doing
4379 this. Perhaps you can help? Perhaps you know what the Gnome
4380 developers did to handle this, and this can give a clue to the KDE
4381 developers? Or you know where in KDE the screen brightness is changed
4382 during login? If so, please update the BTS report (or get in touch if
4383 you do not know how to update BTS).
</p
>
4385 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
4386 acpi_backlight=vendor, to disable ACPI backlight support completely,
4387 as the ACPI information on the machine is trash and it is better to
4388 leave it to the intel video driver to control the screen
4389 backlight.
</p
>
4394 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
4395 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
4396 <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>
4397 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
4398 <description><p
>Two days ago, I asked
4399 <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
4400 I could install Linux on a Packard Bell EasyNote LV computer
4401 preinstalled with Windows
8</a
>. I found a solution, but am horrified
4402 with the obstacles put in the way of Linux users on a laptop with UEFI
4403 and Windows
8.
</p
>
4405 <p
>I never found out if the cause of my problems were the use of UEFI
4406 secure booting or fast boot. I suspect fast boot was the problem,
4407 causing the firmware to boot directly from HD without considering any
4408 key presses and alternative devices, but do not know UEFI settings
4409 enough to tell.
</p
>
4411 <p
>There is no way to install Linux on the machine in question without
4412 opening the box and disconnecting the hard drive! This is as far as I
4413 can tell, the only way to get access to the firmware setup menu
4414 without accepting the Windows
8 license agreement. I am told (and
4415 found description on how to) that it is possible to configure the
4416 firmware setup once booted into Windows
8. But as I believe the terms
4417 of that agreement are completely unacceptable, accepting the license
4418 was never an alternative. I do not enter agreements I do not intend
4419 to follow.
</p
>
4421 <p
>I feared I had to return the laptops and ask for a refund, and
4422 waste many hours on this, but luckily there was a way to get it to
4423 work. But I would not recommend it to anyone planning to run Linux on
4424 it, and I have become sceptical to Windows
8 certified laptops. Is
4425 this the way Linux will be forced out of the market place, by making
4426 it close to impossible for
"normal
" users to install Linux without
4427 accepting the Microsoft Windows license terms? Or at least not
4428 without risking to loose the warranty?
</p
>
4430 <p
>I
've updated the
4431 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
4432 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
4433 do not have to struggle as much as I did to get Linux into the
4436 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4437 Michael Tokarev and others for feedback and ideas.
</p
>
4442 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
4443 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
4444 <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>
4445 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
4446 <description><p
>I
've run into quite a problem the last few days. I bought three
4447 new laptops for my parents and a few others. I bought Packard Bell
4448 Easynote LV to run Kubuntu on and use as their home computer. But I
4449 am completely unable to figure out how to install Linux on it. The
4450 computer is preinstalled with Windows
8, and I suspect it uses UEFI
4451 instead of a BIOS to boot.
</p
>
4453 <p
>The problem is that I am unable to get it to PXE boot, and unable
4454 to get it to boot the Linux installer from my USB stick. I have yet
4455 to try the DVD install, and still hope it will work. when I turn on
4456 the computer, there is no information on what buttons to press to get
4457 the normal boot menu. I expect to get some boot menu to select PXE or
4458 USB stick booting. When booting, it first ask for the language to
4459 use, then for some regional settings, and finally if I will accept the
4460 Windows
8 terms of use. As these terms are completely unacceptable to
4461 me, I have no other choice but to turn off the computer and try again
4462 to get it to boot the Linux installer.
</p
>
4464 <p
>I have gathered my findings so far on a Linlap page about the
4465 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4466 EasyNote LV
</a
> model. If you have any idea how to get Linux
4467 installed on this machine, please get in touch or update that wiki
4468 page. If I can
't find a way to install Linux, I will have to return
4469 the laptop to the seller and find another machine for my parents.
</p
>
4471 <p
>I wonder, is this the way Linux will be forced out of the market
4472 using UEFI and
"secure boot
" by making it impossible to install Linux
4473 on new Laptops?
</p
>
4478 <title>How to transform a Debian based system to a Debian Edu installation
</title>
4479 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
4480 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
4481 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
4482 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
4483 an operating system based on Debian intended for use in schools. It
4484 contain a turn-key solution for the computer network provided to
4485 pupils in the primary schools. It provide both the central server,
4486 network boot servers and desktop environments with heaps of
4487 educational software. The project was founded almost
12 years ago,
4488 2001-
07-
02. If you want to support the project, which is in need for
4489 cash to fund developer gatherings and other project related activity,
4490 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
4491 donate some money
</a
>.
4493 <p
>A topic that come up again and again on the Debian Edu mailing
4494 lists and elsewhere, is the question on how to transform a Debian or
4495 Ubuntu installation into a Debian Edu installation. It isn
't very
4496 hard, and last week I wrote a script to replicate the steps done by
4497 the Debian Edu installer.
</p
>
4499 <p
>The script,
4500 <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/
>
4501 in the debian-edu-config package, will go through these six steps and
4502 transform an existing Debian Wheezy or Ubuntu (untested) installation
4503 into a Debian Edu Workstation:
</p
>
4507 <li
>Add skolelinux related APT sources.
</li
>
4508 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
4509 <li
>Install debian-edu-install to load preseeding values and pull in
4510 our configuration.
</li
>
4511 <li
>Preseed debconf database with profile setup in
4512 /etc/debian-edu/config, and run tasksel to install packages
4513 according to the profile specified in the config above,
4514 overriding some of the Debian automation machinery.
</li
>
4515 <li
>Run debian-edu-cfengine-D installation to configure everything
4516 that could not be done using preseeding.
</li
>
4517 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
4521 <p
>There are some steps in the Debian Edu installation that can not be
4522 replicated like this. Disk partitioning and LVM setup, for example.
4523 So this script just assume there is enough disk space to install all
4524 the needed packages.
</p
>
4526 <p
>The script was created to help a Debian Edu student working on
4527 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
4528 Debian Edu client, and using it he can take the existing
4529 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
4530 transform it into a fully functioning Debian Edu Workstation (or
4531 Roaming Workstation, or whatever :).
</p
>
4533 <p
>The default setting in the script is to create a KDE Workstation.
4534 If a LXDE based Roaming workstation is wanted instead, modify the
4535 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
4537 <p
><pre
>
4538 PROFILE=
"Roaming-Workstation
"
4539 DESKTOP=
"lxde
"
4540 </pre
></p
>
4542 <p
>The script could even become useful to set up Debian Edu servers in
4543 the cloud, by starting with a virtual Debian installation at some
4544 virtual hosting service and setting up all the services on first
4550 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
4551 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
4552 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
4553 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
4554 <description><P
>In January,
4555 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
4556 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
4557 channel #debian-lego
</a
>, for those of us in the Debian and Linux
4558 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
4559 marvellous construction system from Denmark. We also created
4560 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
4561 a place to take notes and write down our plans and hopes. And several
4562 people showed up to help. I was very happy to see the effect of my
4563 call. Since the small start, we have a debtags tag
4564 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
4565 tag for LEGO related packages, and now count
10 packages related to
4566 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
4568 <p
><table
>
4569 <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
>
4570 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
4571 <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
>
4572 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
4573 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
4574 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
4575 <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
>
4576 <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
>
4577 <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
>
4578 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
4579 </table
></p
>
4581 <p
>Some of these are available in Wheezy, and all but one are
4582 currently available in Jessie/testing. leocad is so far only
4583 available in experimental.
</p
>
4585 <p
>If you care about LEGO in Debian, please join us on IRC and help
4586 adding the rest of the great free software tools available on Linux
4587 for LEGO designers.
</p
>
4592 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
4593 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
4594 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
4595 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
4596 <description><p
>When I woke up this morning, I was very happy to see that the
4597 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
4598 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
4599 Debian release, and I expect to move my machines at home over to it fairly
4602 <p
>The new debian release contain heaps of new stuff, and one program
4603 in particular make me very happy to see included. The
4604 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
4605 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
4606 included for the first time. Alongside similar programs like
4607 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
4608 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
4609 it allow for visual programming where syntax errors can not happen,
4610 and a friendly programming environment for learning to control the
4611 computer. Scratch will also be included in the next release of Debian
4614 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
4615 Edu/Skolelinux release too. The
4616 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
4617 alpha release
</a
> went out last week, and the next should soon
4623 <title>Isenkram
0.2 finally in the Debian archive
</title>
4624 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
4625 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
4626 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
4627 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
4628 package
</a
> finally made it into the archive, after lingering in NEW
4629 for many months. I uploaded it to the Debian experimental suite
4630 2013-
01-
27, and today it was accepted into the archive.
</p
>
4632 <p
>Isenkram is a system for suggesting to users what packages to
4633 install to work with a pluggable hardware device. The suggestion pop
4634 up when the device is plugged in. For example if a Lego Mindstorm NXT
4635 is inserted, it will suggest to install the program needed to program
4636 the NXT controller. Give it a go, and report bugs and suggestions to
4642 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
4643 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
4644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
4645 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
4646 <description><p
>My
4647 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
4648 bitcoin related blog post
</a
> mentioned that the new
4649 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
4650 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4651 2013-
01-
19, and have been available in unstable since then. It was
4652 automatically copied to Ubuntu, and is available in their Raring
4653 version too.
</p
>
4655 <p
>But there is a strange problem with the build that block this new
4656 version from being available on the i386 and kfreebsd-i386
4657 architectures. For some strange reason, the autobuilders in Debian
4658 for these architectures fail to run the test suite on these
4659 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
4660 We are so far unable to reproduce it when building it manually, and
4661 no-one have been able to propose a fix. If you got an idea what is
4662 failing, please let us know via the BTS.
</p
>
4664 <p
>One feature that is annoying me with of the bitcoin client, because
4665 I often run low on disk space, is the fact that the client will exit
4666 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
4667 #
696715</a
>). So make sure you have enough disk space when you run
4670 <p
>As usual, if you use bitcoin and want to show your support of my
4671 activities, please send Bitcoin donations to my address
4672 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4677 <title>Welcome to the world, Isenkram!
</title>
4678 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
4679 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
4680 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
4681 <description><p
>Yesterday, I
4682 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
4683 for testers
</a
> for my prototype for making Debian better at handling
4684 pluggable hardware devices, which I
4685 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
4686 out to create
</a
> earlier this month. Several valuable testers showed
4687 up, and caused me to really want to to open up the development to more
4688 people. But before I did this, I want to come up with a sensible name
4689 for this project. Today I finally decided on a new name, and I have
4690 renamed the project from hw-support-handler to this new name. In the
4691 process, I moved the source to git and made it available as a
4692 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
4693 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
4694 To fetch and build the latest version of the source, use
</p
>
4697 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4698 cd isenkram
&& git-buildpackage -us -uc
4701 <p
>I have not yet adjusted all files to use the new name yet. If you
4702 want to hack on the source or improve the package, please go ahead.
4703 But please talk to me first on IRC or via email before you do major
4704 changes, to make sure we do not step on each others toes. :)
</p
>
4706 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
4707 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4708 stuff, in other words. I
've been told it is the Norwegian variant of
4709 the German word eisenkram, for those that are familiar with that
4712 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
4713 instructions, to avoid confusing people with an error from the signing
4716 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
4717 clone argument to avoid the need for authentication.
</p
>
4722 <title>First prototype ready making hardware easier to use in Debian
</title>
4723 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
4724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
4725 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
4726 <description><p
>Early this month I set out to try to
4727 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
4728 the Debian support for pluggable hardware devices
</a
>. Now my
4729 prototype is working, and it is ready for a larger audience. To test
4731 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
4732 from the Debian Edu subversion repository
</a
>, build and install the
4733 package. You might have to log out and in again activate the
4734 autostart script.
</p
>
4736 <p
>The design is simple:
</p
>
4740 <li
>Add desktop entry in /usr/share/autostart/ causing a program
4741 hw-support-handlerd to start when the user log in.
</li
>
4743 <li
>This program listen for kernel events about new hardware (directly
4744 from the kernel like udev does), not using HAL dbus events as I
4745 initially did.
</li
>
4747 <li
>When new hardware is inserted, look up the hardware modalias in
4748 the APT database, a database
4749 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
4750 via HTTP
</a
> and a database available as part of the package.
</li
>
4752 <li
>If a package is mapped to the hardware in question, the package
4753 isn
't installed yet and this is the first time the hardware was
4754 plugged in, show a desktop notification suggesting to install the
4755 package or packages.
</li
>
4757 <li
>If the user click on the
'install package now
' button, ask
4758 aptdaemon via the PackageKit API to install the requrired package.
</li
>
4760 <li
>aptdaemon ask for root password or sudo password, and install the
4761 package while showing progress information in a window.
</li
>
4765 <p
>I still need to come up with a better name for the system. Here
4766 are some screen shots showing the prototype in action. First the
4767 notification, then the password request, and finally the request to
4768 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
4770 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
4771 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
4772 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
4773 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
4774 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
4776 <p
>The prototype still need to be improved with longer timeouts, but
4777 is already useful. The database of hardware to package mappings also
4778 need more work. It is currently compatible with the Ubuntu way of
4779 storing such information in the package control file, but could be
4780 changed to use other formats instead or in addition to the current
4781 method. I
've dropped the use of discover for this mapping, as the
4782 modalias approach is more flexible and easier to use on Linux as long
4783 as the Linux kernel expose its modalias strings directly.
</p
>
4785 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
4786 here is the command required to check out and build the source: Use
4787 '<tt
>svn checkout
4788 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4789 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
4790 devscripts package.
</p
>
4792 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
4793 renamed to Isenkram and the source moved from the Debian Edu
4794 subversion repository to a Debian collab-maint git repository. See
4795 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
4796 instructions
</a
> for details.
</p
>
4801 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
4802 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
4803 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
4804 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
4805 <description><p
>This Christmas my trusty old laptop died. It died quietly and
4806 suddenly in bed. With a quiet whimper, it went completely quiet and
4807 black. The power button was no longer able to turn it on. It was a
4808 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4809 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4810 Compaq I had before that. Now I need to find a replacement. To keep
4811 going during Christmas, I moved the one year old SSD disk to my old
4812 X40 where it fitted (only one I had left that could use it), but it is
4813 not a durable solution.
4815 <p
>My laptop needs are fairly modest. This is my wishlist from when I
4816 got a new one more than
10 years ago. It still holds true.:)
</p
>
4820 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
4821 than A4).
</li
>
4822 <li
>Robust, it will be in my backpack every day.
</li
>
4823 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
4824 <li
>Long battery life time. Preferable a week.
</li
>
4825 <li
>Internal WIFI network card.
</li
>
4826 <li
>Internal Twisted Pair network card.
</li
>
4827 <li
>Some USB slots (
2-
3 is plenty)
</li
>
4828 <li
>Good keyboard - similar to the Thinkpad.
</li
>
4829 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
4831 <li
>Hardware supported by Debian Stable, ie the default kernel and
4832 X.org packages.
</li
>
4833 <li
>Quiet, preferably fan free (or at least not using the fan most of
4838 <p
>You will notice that there are no RAM and CPU requirements in the
4839 list. The reason is simply that the specifications on laptops the
4840 last
10-
15 years have been sufficient for my needs, and I have to look
4841 at other features to choose my laptop. But are there still made as
4842 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4843 robust, and Thinkpads seem to be heading in the wrong direction since
4844 Lenovo took over. But I
've been told that X220 and X1 Carbon might
4845 still be useful.
</p
>
4847 <p
>Perhaps I should rethink my needs, and look for a pad with an
4848 external keyboard? I
'll have to check the
4849 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
4850 well-supported laptops, or perhaps just buy one preinstalled from one
4851 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
4852 Pre-loaded site
</a
>.
</p
>
4857 <title>How to find a browser plugin supporting a given MIME type
</title>
4858 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
4859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
4860 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
4861 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
4862 install to get support for a given MIME type. Thanks to
4863 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
4864 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
4865 Unfortunately, not very many packages provide the needed meta
4866 information, Anyway, here is a small script to look up all browser
4867 plugin packages announcing ther MIME support using this specification:
</p
>
4873 def pkgs_handling_mimetype(mimetype):
4878 version = pkg.candidate
4880 version = pkg.installed
4883 record = version.record
4884 if not record.has_key(
'Npp-MimeType
'):
4886 mime_types = record[
'Npp-MimeType
'].split(
',
')
4887 for t in mime_types:
4888 t = t.rstrip().strip()
4890 thepkgs.append(pkg.name)
4892 mimetype =
"audio/ogg
"
4893 if
1 < len(sys.argv):
4894 mimetype = sys.argv[
1]
4895 print
"Browser plugin packages supporting %s:
" % mimetype
4896 for pkg in pkgs_handling_mimetype(mimetype):
4897 print
" %s
" %pkg
4900 <p
>It can be used like this to look up a given MIME type:
</p
>
4903 % ./apt-find-browserplug-for-mimetype
4904 Browser plugin packages supporting audio/ogg:
4906 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4907 Browser plugin packages supporting application/x-shockwave-flash:
4908 browser-plugin-gnash
4912 <p
>In Ubuntu this mechanism is combined with support in the browser
4913 itself to query for plugins and propose to install the needed
4914 packages. It would be great if Debian supported such feature too. Is
4915 anyone working on adding it?
</p
>
4917 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
4918 request for icweasel support for this feature is
4919 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
4920 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
4921 of manpower and wish for a different design is the reason thus feature
4922 is not yet in iceweasel from Debian.
</p
>
4927 <title>What is the most supported MIME type in Debian?
</title>
4928 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
4929 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
4930 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
4931 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
4932 proposal to add AppStream information to the Debian archive
</a
>, is a
4933 proposal to make it possible for a Desktop application to propose to
4934 the user some package to install to gain support for a given MIME
4935 type, font, library etc. that is currently missing. With such
4936 mechanism in place, it would be possible for the desktop to
4937 automatically propose and install leocad if some LDraw file is
4938 downloaded by the browser.
</p
>
4940 <p
>To get some idea about the current content of the archive, I decided
4941 to write a simple program to extract all .desktop files from the
4942 Debian archive and look up the claimed MIME support there. The result
4944 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
4945 site
</a
>. Using the collected information, it become possible to
4946 answer the question in the title. Here are the
20 most supported MIME
4947 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4948 The complete list is available from the link above.
</p
>
4950 <p
><strong
>Debian Stable:
</strong
></p
>
4954 ----- -----------------------
4970 18 application/x-ogg
4977 <p
><strong
>Debian Testing:
</strong
></p
>
4981 ----- -----------------------
4997 18 application/x-ogg
5004 <p
><strong
>Debian Unstable:
</strong
></p
>
5008 ----- -----------------------
5025 18 application/x-ogg
5031 <p
>I am told that PackageKit can provide an API to access the kind of
5032 information mentioned in DEP-
11. I have not yet had time to look at
5033 it, but hope the PackageKit people in Debian are on top of these
5036 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5037 discovering a typo in my script.
</p
>
5042 <title>Using modalias info to find packages handling my hardware
</title>
5043 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5045 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
5046 <description><p
>Yesterday, I wrote about the
5047 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
5048 values provided by the Linux kernel
</a
> following my hope for
5049 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
5050 dongle support in Debian
</a
>. Using this knowledge, I have tested how
5051 modalias values attached to package names can be used to map packages
5052 to hardware. This allow the system to look up and suggest relevant
5053 packages when I plug in some new hardware into my machine, and replace
5054 discover and discover-data as the database used to map hardware to
5057 <p
>I create a modaliases file with entries like the following,
5058 containing package name, kernel module name (if relevant, otherwise
5059 the package name) and globs matching the relevant hardware
5062 <p
><blockquote
>
5063 Package: package-name
5064 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
5065 </blockquote
></p
>
5067 <p
>It is fairly trivial to write code to find the relevant packages
5068 for a given modalias value using this file.
</p
>
5070 <p
>An entry like this would suggest the video and picture application
5071 cheese for many USB web cameras (interface bus class
0E01):
</p
>
5073 <p
><blockquote
>
5075 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
5076 </blockquote
></p
>
5078 <p
>An entry like this would suggest the pcmciautils package when a
5079 CardBus bridge (bus class
0607) PCI device is present:
</p
>
5081 <p
><blockquote
>
5082 Package: pcmciautils
5083 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5084 </blockquote
></p
>
5086 <p
>An entry like this would suggest the package colorhug-client when
5087 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
5089 <p
><blockquote
>
5090 Package: colorhug-client
5091 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
5092 </blockquote
></p
>
5094 <p
>I believe the format is compatible with the format of the Packages
5095 file in the Debian archive. Ubuntu already uses their Packages file
5096 to store their mappings from packages to hardware.
</p
>
5098 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
5099 announce the hardware it support in a way my prototype understand.
5100 This allow those publishing packages in an APT source outside the
5101 Debian archive as well as those backporting packages to make sure the
5102 hardware mapping are included in the package meta information. I
've
5103 tested such header in the pymissile package, and its modalias mapping
5104 is working as it should with my prototype. It even made it to Ubuntu
5107 <p
>To test if it was possible to look up supported hardware using only
5108 the shell tools available in the Debian installer, I wrote a shell
5109 implementation of the lookup code. The idea is to create files for
5110 each modalias and let the shell do the matching. Please check out and
5112 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
5113 shell script. It run without any extra dependencies and fetch the
5114 hardware mappings from the Debian archive and the subversion
5115 repository where I currently work on my prototype.
</p
>
5117 <p
>When I use it on a machine with a yubikey inserted, it suggest to
5118 install yubikey-personalization:
</p
>
5120 <p
><blockquote
>
5121 % ./hw-support-lookup
5122 <br
>yubikey-personalization
5124 </blockquote
></p
>
5126 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5127 propose to install the pcmciautils package:
</p
>
5129 <p
><blockquote
>
5130 % ./hw-support-lookup
5131 <br
>pcmciautils
5133 </blockquote
></p
>
5135 <p
>If you know of any hardware-package mapping that should be added to
5136 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
5137 database
</a
>, please tell me about it.
</p
>
5139 <p
>It could be possible to generate several of the mappings between
5140 packages and hardware. One source would be to look at packages with
5141 kernel modules, ie packages with *.ko files in /lib/modules/, and
5142 extract their modalias information. Another would be to look at
5143 packages with udev rules, ie packages with files in
5144 /lib/udev/rules.d/, and extract their vendor/model information to
5145 generate a modalias matching rule. I have not tested any of these to
5146 see if it work.
</p
>
5148 <p
>If you want to help implementing a system to let us propose what
5149 packages to install when new hardware is plugged into a Debian
5150 machine, please send me an email or talk to me on
5151 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5156 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
5157 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
5158 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
5159 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
5160 <description><p
>While looking into how to look up Debian packages based on hardware
5161 information, to find the packages that support a given piece of
5162 hardware, I refreshed my memory regarding modalias values, and decided
5163 to document the details. Here are my findings so far, also available
5165 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5166 Debian Edu subversion repository
</a
>:
5168 <p
><strong
>Modalias decoded
</strong
></p
>
5170 <p
>This document try to explain what the different types of modalias
5171 values stands for. It is in part based on information from
5172 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
5173 &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;,
5174 &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
5175 &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;.
5177 <p
>The modalias entries for a given Linux machine can be found using
5178 this shell script:
</p
>
5181 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
5184 <p
>The supported modalias globs for a given kernel module can be found
5185 using modinfo:
</p
>
5188 % /sbin/modinfo psmouse | grep alias:
5189 alias: serio:ty05pr*id*ex*
5190 alias: serio:ty01pr*id*ex*
5194 <p
><strong
>PCI subtype
</strong
></p
>
5196 <p
>A typical PCI entry can look like this. This is an Intel Host
5197 Bridge memory controller:
</p
>
5199 <p
><blockquote
>
5200 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5201 </blockquote
></p
>
5203 <p
>This represent these values:
</p
>
5208 sv
00001028 (subvendor)
5209 sd
000001AD (subdevice)
5211 sc
00 (bus subclass)
5215 <p
>The vendor/device values are the same values outputted from
'lspci
5216 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
5217 0600. The
0600 class is a host bridge. Other useful bus values are
5218 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
5220 <p
>Not sure how to figure out the interface value, nor what it
5223 <p
><strong
>USB subtype
</strong
></p
>
5225 <p
>Some typical USB entries can look like this. This is an internal
5226 USB hub in a laptop:
</p
>
5228 <p
><blockquote
>
5229 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5230 </blockquote
></p
>
5232 <p
>Here is the values included in this alias:
</p
>
5235 v
1D6B (device vendor)
5236 p
0001 (device product)
5238 dc
09 (device class)
5239 dsc
00 (device subclass)
5240 dp
00 (device protocol)
5241 ic
09 (interface class)
5242 isc
00 (interface subclass)
5243 ip
00 (interface protocol)
5246 <p
>The
0900 device class/subclass means hub. Some times the relevant
5247 class is in the interface class section. For a simple USB web camera,
5248 these alias entries show up:
</p
>
5250 <p
><blockquote
>
5251 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5252 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5253 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5254 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5255 </blockquote
></p
>
5257 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
5258 camera),
0101 is audio control device and
0102 is audio streaming (aka
5259 microphone). Thus this is a camera with microphone included.
</p
>
5261 <p
><strong
>ACPI subtype
</strong
></p
>
5263 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
5264 receiver in a Thinkpad X40:
</p
>
5266 <p
><blockquote
>
5267 acpi:IBM0071:PNP0511:
5268 </blockquote
></p
>
5270 <p
>The values between the colons are IDs.
</p
>
5272 <p
><strong
>DMI subtype
</strong
></p
>
5274 <p
>The DMI table contain lots of information about the computer case
5275 and model. This is an entry for a IBM Thinkpad X40, fetched from
5276 /sys/devices/virtual/dmi/id/modalias:
</p
>
5278 <p
><blockquote
>
5279 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5280 </blockquote
></p
>
5282 <p
>The values present are
</p
>
5285 bvn IBM (BIOS vendor)
5286 bvr
1UETB
6WW(
1.66) (BIOS version)
5287 bd
06/
15/
2005 (BIOS date)
5288 svn IBM (system vendor)
5289 pn
2371H4G (product name)
5290 pvr ThinkPadX40 (product version)
5291 rvn IBM (board vendor)
5292 rn
2371H4G (board name)
5293 rvr NotAvailable (board version)
5294 cvn IBM (chassis vendor)
5295 ct
10 (chassis type)
5296 cvr NotAvailable (chassis version)
5299 <p
>The chassis type
10 is Notebook. Other interesting values can be
5300 found in the dmidecode source:
</p
>
5304 4 Low Profile Desktop
5317 17 Main Server Chassis
5318 18 Expansion Chassis
5320 20 Bus Expansion Chassis
5321 21 Peripheral Chassis
5323 23 Rack Mount Chassis
5332 <p
>The chassis type values are not always accurately set in the DMI
5333 table. For example my home server is a tower, but the DMI modalias
5334 claim it is a desktop.
</p
>
5336 <p
><strong
>SerIO subtype
</strong
></p
>
5338 <p
>This type is used for PS/
2 mouse plugs. One example is from my
5339 test machine:
</p
>
5341 <p
><blockquote
>
5342 serio:ty01pr00id00ex00
5343 </blockquote
></p
>
5345 <p
>The values present are
</p
>
5354 <p
>This type is supported by the psmouse driver. I am not sure what
5355 the valid values are.
</p
>
5357 <p
><strong
>Other subtypes
</strong
></p
>
5359 <p
>There are heaps of other modalias subtypes according to
5360 file2alias.c. There is the rest of the list from that source: amba,
5361 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5362 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5363 vmbus, x86cpu and zorro. I did not spend time documenting all of
5364 these, as they do not seem relevant for my intended use with mapping
5365 hardware to packages when new stuff is inserted during run time.
</p
>
5367 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
5369 <p
>To check which kernel modules provide support for a given modalias,
5370 one can use the following shell script:
</p
>
5373 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
5374 echo
"$id
" ; \
5375 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
5379 <p
>The output can look like this (only the first few entries as the
5380 list is very long on my test machine):
</p
>
5384 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
5386 FATAL: Module acpi:device: not found.
5388 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
5389 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
5390 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
5391 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5392 acpi:IBM0071:PNP0511:
5393 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
5394 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
5395 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
5399 <p
>If you want to help implementing a system to let us propose what
5400 packages to install when new hardware is plugged into a Debian
5401 machine, please send me an email or talk to me on
5402 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5404 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
5405 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
5406 in /sys/ with space in them.
</p
>
5411 <title>Moved the pymissile Debian packaging to collab-maint
</title>
5412 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
5413 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
5414 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
5415 <description><p
>As part of my investigation on how to improve the support in Debian
5416 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5417 Launcher and updated the Debian package
5418 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
5419 sure udev will fix the device permissions when it is plugged in. I
5420 also added a
"Modaliases
" header to test it in the Debian archive and
5421 hopefully make the package be proposed by jockey in Ubuntu when a user
5422 plug in his rocket launcher. In the process I moved the source to a
5423 git repository under collab-maint, to make it easier for any DD to
5424 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
5425 is not very active, but the software still work for me even after five
5426 years of relative silence. The new git repository is not listed in
5427 the uploaded package yet, because I want to test the other changes a
5428 bit more before I upload the new version. If you want to check out
5429 the new version with a .desktop file included, visit the
5430 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
5431 view
</a
> or use
"<tt
>git clone
5432 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
5437 <title>Lets make hardware dongles easier to use in Debian
</title>
5438 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
5439 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
5440 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
5441 <description><p
>One thing that annoys me with Debian and Linux distributions in
5442 general, is that there is a great package management system with the
5443 ability to automatically install software packages by downloading them
5444 from the distribution mirrors, but no way to get it to automatically
5445 install the packages I need to use the hardware I plug into my
5446 machine. Even if the package to use it is easily available from the
5447 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5448 suggest to automatically install the python-nxt, nbc and t2n packages
5449 I need to talk to it. When I plug in a Yubikey, it could propose the
5450 yubikey-personalization package. The information required to do this
5451 is available, but no-one have pulled all the pieces together.
</p
>
5453 <p
>Some years ago, I proposed to
5454 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
5455 the discover subsystem to implement this
</a
>. The idea is fairly
5460 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
5461 starting when a user log in.
</li
>
5463 <li
>Set this program up to listen for kernel events emitted when new
5464 hardware is inserted into the computer.
</li
>
5466 <li
>When new hardware is inserted, look up the hardware ID in a
5467 database mapping to packages, and take note of any non-installed
5468 packages.
</li
>
5470 <li
>Show a message to the user proposing to install the discovered
5471 package, and make it easy to install it.
</li
>
5475 <p
>I am not sure what the best way to implement this is, but my
5476 initial idea was to use dbus events to discover new hardware, the
5477 discover database to find packages and
5478 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
5481 <p
>Yesterday, I found time to try to implement this idea, and the
5482 draft package is now checked into
5483 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5484 Debian Edu subversion repository
</a
>. In the process, I updated the
5485 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
5486 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5487 the relevant packages in Debian, and uploaded a new version
5488 2.2013.01.09 to unstable. I also discovered that the current
5489 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
5490 package in Debian no longer discovered any USB devices, because
5491 /proc/bus/usb/devices is no longer present. I ported it to use
5492 libusb as a fall back option to get it working. The fixed package
5493 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
5494 because of the freeze).
</p
>
5496 <p
>With this prototype in place, I can insert my Yubikey, and get this
5497 desktop notification to show up (only once, the first time it is
5498 inserted):
</p
>
5500 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
5502 <p
>For this prototype to be really useful, some way to automatically
5503 install the proposed packages by pressing the
"Please install
5504 program(s)
" button should to be implemented.
</p
>
5506 <p
>If this idea seem useful to you, and you want to help make it
5507 happen, please help me update the discover-data database with mappings
5508 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
5509 list the package you would like to have installed when a given
5510 hardware device is inserted into your computer, and report bugs using
5511 reportbug if it isn
't. Or, if you know of a better way to provide
5512 such mapping, please let me know.
</p
>
5514 <p
>This prototype need more work, and there are several questions that
5515 should be considered before it is ready for production use. Is dbus
5516 the correct way to detect new hardware? At the moment I look for HAL
5517 dbus events on the system bus, because that is the events I could see
5518 on my Debian Squeeze KDE desktop. Are there better events to use?
5519 How should the user be notified? Is the desktop notification
5520 mechanism the best option, or should the background daemon raise a
5521 popup instead? How should packages be installed? When should they
5522 not be installed?
</p
>
5524 <p
>If you want to help getting such feature implemented in Debian,
5525 please send me an email. :)
</p
>
5530 <title>New IRC channel for LEGO designers using Debian
</title>
5531 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
5532 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
5533 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
5534 <description><p
>During Christmas, I have worked a bit on the Debian support for
5535 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
5536 NXT
</a
>. My son and I have played a bit with my NXT set, and I
5537 discovered I had to build all the tools myself because none were
5538 already in Debian Squeeze. If Debian support for LEGO is something
5539 you care about, please join me on the IRC channel
5540 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
5541 irc.debian.org). There is a lot that could be done to improve the
5542 Debian support for LEGO designers. For example both CAD software
5543 and Mindstorm compilers are missing. :)
</p
>
5545 <p
>Update
2012-
01-
03: A
5546 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
5547 including links to Lego related packages is now available.
</p
>
5552 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
5553 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
5554 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
5555 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
5556 <description><p
>Let me start by wishing you all marry Christmas and a happy new
5557 year! I hope next year will prove to be a good year.
</p
>
5559 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
5560 decentralised
"currency
" that allow people to transfer bitcoins
5561 between each other with minimal overhead, is a very interesting
5562 experiment. And as I wrote a few days ago, the bitcoin situation in
5563 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
5564 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
5565 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
5566 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
5567 for one of the ftpmasters to approve the new bitcoin-qt package
5570 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
5571 team in Debian, you can easily test the package in Debian Squeeze
5572 using the following steps to get a set of working packages:
</p
>
5574 <blockquote
><pre
>
5575 git clone git://git.debian.org/git/collab-maint/bitcoin
5577 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5578 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5579 </pre
></blockquote
>
5581 <p
>You might have to install some build dependencies as well. The
5582 list of commands should give you two packages, bitcoind and
5583 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5584 client will download the complete set of bitcoin
"blocks
", which need
5585 around
5.6 GiB of data on my machine at the moment. Make sure your
5586 ~/.bitcoin/ directory have lots of spare room if you want to download
5587 all the blocks. The client will warn if the disk is getting full, so
5588 there is not really a problem if you got too little room, but you will
5589 not be able to get all the features out of the client.
</p
>
5591 <p
>As usual, if you use bitcoin and want to show your support of my
5592 activities, please send Bitcoin donations to my address
5593 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5598 <title>A word on bitcoin support in Debian
</title>
5599 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
5600 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
5601 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
5602 <description><p
>It has been a while since I wrote about
5603 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
5604 peer-to-peer based crypto-currency, and the reason is simply that I
5605 have been busy elsewhere. But two days ago, I started looking at the
5606 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
5607 Debian
</a
> again to try to recover my old bitcoin wallet. The package
5608 is now maintained by a
5609 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
5610 people
</a
>, and the grunt work had already been done by this team. We
5611 owe a huge thank you to all these team members. :)
5612 But I was sad to discover that the bitcoin client is missing in
5613 Wheezy. It is only available in Sid (and an outdated client from
5614 backports). The client had several RC bugs registered in BTS blocking
5615 it from entering testing. To try to help the team and improve the
5616 situation, I spent some time providing patches and triaging the bug
5617 reports. I also had a look at the bitcoin package available from Matt
5619 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
5620 Ubuntu
</a
>, and moved the useful pieces from that version into the
5621 Debian package.
</p
>
5623 <p
>After checking with the main package maintainer Jonas Smedegaard on
5624 IRC, I pushed several patches into the collab-maint git repository to
5625 improve the package. It now contains fixes for the RC issues (not from
5626 me, but fixed by Scott Howard), build rules for a Qt GUI client
5627 package, konqueror support for the bitcoin: URI and bash completion
5628 setup. As I work on Debian Squeeze, I also created
5629 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
5630 patch to backport
</a
> the latest version. Jonas is going to look at
5631 it and try to integrate it into the git repository before uploading a
5632 new version to unstable.
5634 <p
>I would very much like bitcoin to succeed, to get rid of the
5635 centralized control currently exercised in the monetary system. I
5636 find it completely unacceptable that the USA government is collecting
5637 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5638 that the major credit card companies can block legal money
5639 transactions to Wikileaks. But for bitcoin to succeed, more people
5640 need to use bitcoins, and more people need to accept bitcoins when
5641 they sell products and services. Improving the bitcoin support in
5642 Debian is a small step in the right direction, but not enough.
5643 Unfortunately the user experience when browsing the web and wanting to
5644 pay with bitcoin is still not very good. The bitcoin: URI is a step
5645 in the right direction, but need to work in most or every browser in
5646 use. Also the bitcoin-qt client is too heavy to fire up to do a
5647 quick transaction. I believe there are other clients available, but
5648 have not tested them.
</p
>
5651 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
5652 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
5653 I received
20.15 BTC so far on the address I provided in my blog two
5654 years ago, as can be
5655 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
5656 on the blockexplorer service
</a
>. Thank you everyone for your
5657 donation. The blockexplorer service demonstrates quite well that
5658 bitcoin is not quite anonymous and untracked. :) I wonder if the
5659 number of users have gone up since then. If you use bitcoin and want
5660 to show your support of my activity, please send Bitcoin donations to
5661 the same address as last time,
5662 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5667 <title>Git repository for song book for Computer Scientists
</title>
5668 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
5669 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
5670 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
5671 <description><p
>As I
5672 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
5673 this summer
</a
>, I have created a Computer Science song book a few
5674 years ago, and today I finally found time to create a public
5675 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
5676 repository for the project
</a
>.
</p
>
5678 <p
>If you want to help out, please clone the source and submit patches
5679 to the HTML version. To generate the PDF and PostScript version,
5680 please use prince XML, or let me know about a useful free software
5681 processor capable of creating a good looking PDF from the HTML.
</p
>
5683 <p
>Want to sing? You can still find the song book in HTML, PDF and
5684 PostScript formats at
5685 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
5686 Science Songbook
</a
>.
</p
>
5691 <title>Gratulerer med
19-årsdagen, Debian!
</title>
5692 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
5693 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
5694 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
5695 <description><p
>I dag fyller
5696 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
5697 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
5698 si gratulerer med dagen, Debian!
</p
>
5703 <title>Song book for Computer Scientists
</title>
5704 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
5705 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
5706 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
5707 <description><p
>Many years ago, while studying Computer Science at the
5708 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
5709 collecting computer related songs for use at parties. The original
5710 version was written in LaTeX, but a few years ago I got help from
5711 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5712 while keeping the ability to create a nice book in PDF format. I have
5713 not had time to maintain the book for a while now, and guess I should
5714 put it up on some public version control repository where others can
5715 help me extend and update the book. If anyone is volunteering to help
5716 me with this, send me an email. Also let me know if there are songs
5717 missing in my book.
</p
>
5719 <p
>I have not mentioned the book on my blog so far, and it occured to
5720 me today that I really should let all my readers share the joys of
5721 singing out load about programming, computers and computer networks.
5722 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
5723 12</a
> is about to start (and I am not going). Want to sing? Check
5724 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
5725 Computer Science Songbook
</a
>.
5730 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
5731 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
5732 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
5733 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
5734 <description><p
>At work we have heaps of servers. I believe the total count is
5735 around
1000 at the moment. To be able to get help from the vendors
5736 when something go wrong, we want to keep the firmware on the servers
5737 up to date. If the firmware isn
't the latest and greatest, the
5738 vendors typically refuse to start debugging any problems until the
5739 firmware is upgraded. So before every reboot, we want to upgrade the
5740 firmware, and we would really like everyone handling servers at the
5741 university to do this themselves when they plan to reboot a machine.
5742 For that to happen we at the unix server admin group need to provide
5743 the tools to do so.
</p
>
5745 <p
>To make firmware upgrading easier, I am working on a script to
5746 fetch and install the latest firmware for the servers we got. Most of
5747 our hardware are from Dell and HP, so I have focused on these servers
5748 so far. This blog post is about the Dell part.
</P
>
5750 <p
>On the Dell FTP site I was lucky enough to find
5751 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
5752 with firmware information for all
11th generation servers, listing
5753 which firmware should be used on a given model and where on the FTP
5754 site I can find it. Using a simple perl XML parser I can then
5755 download the shell scripts Dell provides to do firmware upgrades from
5756 within Linux and reboot when all the firmware is primed and ready to
5757 be activated on the first reboot.
</p
>
5759 <p
>This is the Dell related fragment of the perl code I am working on.
5760 Are there anyone working on similar tools for firmware upgrading all
5761 servers at a site? Please get in touch and lets share resources.
</p
>
5763 <p
><pre
>
5767 use File::Temp qw(tempdir);
5769 # Install needed RHEL packages if missing
5771 'XML::Simple
' =
> 'perl-XML-Simple
',
5773 for my $module (keys %rhelmodules) {
5774 eval
"use $module;
";
5776 my $pkg = $rhelmodules{$module};
5777 system(
"yum install -y $pkg
");
5778 eval
"use $module;
";
5782 my $errorsto =
'pere@hungry.com
';
5788 sub run_firmware_script {
5789 my ($opts, $script) = @_;
5791 print STDERR
"fail: missing script name\n
";
5794 print STDERR
"Running $script\n\n
";
5796 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
5797 print STDERR
"success: firmware script ran succcessfully\n
";
5799 print STDERR
"fail: firmware script returned error\n
";
5803 sub run_firmware_scripts {
5804 my ($opts, @dirs) = @_;
5805 # Run firmware packages
5806 for my $dir (@dirs) {
5807 print STDERR
"info: Running scripts in $dir\n
";
5808 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
5809 while (my $s = readdir $dh) {
5810 next if $s =~ m/^\.\.?/;
5811 run_firmware_script($opts,
"$dir/$s
");
5819 print STDERR
"info: Downloading $url\n
";
5820 system(
"wget --quiet \
"$url\
"");
5825 my $product = `dmidecode -s system-product-name`;
5828 if ($product =~ m/PowerEdge/) {
5830 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5831 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
5833 my $tmpdir = tempdir(
5837 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
5838 system(
'gunzip Catalog.xml.gz
');
5839 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
5840 # -q is quiet, disabling interactivity and reducing console output
5841 my $fwopts =
"-q
";
5843 for my $url (@paths) {
5844 fetch_dell_fw($url);
5846 run_firmware_scripts($fwopts, $tmpdir);
5848 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5849 print STDERR
"error: Please report to $errorsto.\n
";
5853 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5854 print STDERR
"error: Please report to $errorsto.\n
";
5860 my $url =
"ftp://ftp.us.dell.com/$path
";
5864 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5865 # firmware packages to download from Dell. Only work for Linux
5866 # machines and
11th generation Dell servers.
5867 sub fetch_dell_fw_list {
5868 my $filename = shift;
5870 my $product = `dmidecode -s system-product-name`;
5872 my ($mybrand, $mymodel) = split(/\s+/, $product);
5874 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
5876 my $xml = XMLin($filename);
5878 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
5879 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
5880 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
5882 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
5883 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
5885 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
5887 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
5889 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
5892 for my $component (@{$xml-
>{SoftwareComponent}}) {
5893 my $componenttype = $component-
>{ComponentType}-
>{value};
5895 # Drop application packages, only firmware and BIOS
5896 next if
'APAC
' eq $componenttype;
5898 my $cpath = $component-
>{path};
5899 for my $path (@paths) {
5900 if ($cpath =~ m%/$path$%) {
5901 push(@paths, $cpath);
5909 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
5910 it could work on other platforms with some tweaking. Anyone know a
5911 index like Catalog.xml is available from HP for HP servers? At the
5912 moment I maintain a similar list manually and it is quickly getting
5918 <title>How is booting into runlevel
1 different from single user boots?
</title>
5919 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
5920 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
5921 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
5922 <description><p
>Wouter Verhelst have some
5923 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
5924 comments and opinions
</a
> on my blog post on
5925 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
5926 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
5927 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
5928 default KDE desktop in Debian
</a
>. I only have time to address one
5929 small piece of his comment now, and though it best to address the
5930 misunderstanding he bring forward:
</p
>
5932 <p
><blockquote
>
5933 Currently, a system admin has four options: [...] boot to a
5934 single-user system (by adding
'single
' to the kernel command line;
5935 this runs rcS and rc1 scripts)
5936 </blockquote
></p
>
5938 <p
>This make me believe Wouter believe booting into single user mode
5939 and booting into runlevel
1 is the same. I am not surprised he
5940 believe this, because it would make sense and is a quite sensible
5941 thing to believe. But because the boot in Debian is slightly broken,
5942 runlevel
1 do not work properly and it isn
't the same as single user
5943 mode. I
'll try to explain what is actually happing, but it is a bit
5944 hard to explain.
</p
>
5946 <p
>Single user mode is defined like this in /etc/inittab:
5947 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
5948 executed in single user mode is sulogin. Single user mode is a boot
5949 state
"between
" the runlevels, and when booting into single user mode,
5950 only the scripts in /etc/rcS.d/ are executed before the init process
5951 enters the single user state. When switching to runlevel
1, the state
5952 is in fact not ending in runlevel
1, but it passes through runlevel
1
5953 and end up in the single user mode (see /etc/rc1.d/S03single, which
5954 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
5955 1. It is confusing that the
'S
' (single user) init mode is not the
5956 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5959 <p
>This summary might make it clearer. When booting for the first
5960 time into single user mode, the following commands are executed:
5961 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
5962 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
5963 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
5964 trying to continue after visiting single user mode. Not all services
5965 are started again as they should, causing the machine to end up in an
5966 unpredicatble state. This is why Debian admins recommend rebooting
5967 after visiting single user mode.
</p
>
5969 <p
>A similar problem with runlevel
1 is caused by the amount of
5970 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
5971 to runlevel
1, the services started from /etc/rcS.d/ are not properly
5972 stopped when passing through the scripts in /etc/rc1.d/, and not
5973 started again when switching away from runlevel
1 to the runlevels
5974 2-
5. I believe the problem is best fixed by moving all the scripts
5975 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
5976 functioning single user mode during boot.
</p
>
5978 <p
>I have spent several years investigating the Debian boot system,
5979 and discovered this problem a few years ago. I suspect it originates
5980 from when sysvinit was introduced into Debian, a long time ago.
</p
>
5985 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
5986 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
5987 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
5988 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
5989 <description><p
>In the Debian boot system, several packages include scripts that
5990 are started from /etc/rcS.d/. In fact, there is a bite more of them
5991 than make sense, and this causes a few problems. What kind of
5992 problems, you might ask. There are at least two problems. The first
5993 is that it is not possible to recover a machine after switching to
5994 runlevel
1. One need to actually reboot to get the machine back to
5995 the expected state. The other is that single user boot will sometimes
5996 run into problems because some of the subsystems are activated before
5997 the root login is presented, causing problems when trying to recover a
5998 machine from a problem in that subsystem. A minor additional point is
5999 that moving more scripts out of rcS.d/ and into the other rc#.d/
6000 directories will increase the amount of scripts that can run in
6001 parallel during boot, and thus decrease the boot time.
</p
>
6003 <p
>So, which scripts should start from rcS.d/. In short, only the
6004 scripts that _have_ to execute before the root login prompt is
6005 presented during a single user boot should go there. Everything else
6006 should go into the numeric runlevels. This means things like
6007 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6008 the numeric runlevels. Today in Debian, there are around
115 init.d
6009 scripts that are started from rcS.d/, and most of them should be moved
6010 out. Do your package have one of them? Please help us make single
6011 user and runlevel
1 better by moving it.
</p
>
6013 <p
>Scripts setting up the screen, keyboard, system partitions
6014 etc. should still be started from rcS.d/, but there is for example no
6015 need to have the network enabled before the single user login prompt
6016 is presented.
</p
>
6018 <p
>As always, things are not so easy to fix as they sound. To keep
6019 Debian systems working while scripts migrate and during upgrades, the
6020 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6021 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6022 and the next ones can only be moved when their dependencies have been
6023 moved first. This migration must be done sequentially while we ensure
6024 that the package system upgrade packages in the right order to keep
6025 the system state correct. This will require some coordination when it
6026 comes to network related packages, but most of the packages with
6027 scripts that should migrate do not have anything in rcS.d/ depending
6028 on them. Some packages have already been updated, like the sudo
6029 package, while others are still left to do. I wish I had time to work
6030 on this myself, but real live constrains make it unlikely that I will
6031 find time to push this forward.
</p
>
6036 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6037 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6038 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6039 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6040 <description><p
>While at Debconf11, I have several times during discussions
6041 mentioned the issues I believe should be improved in Debian for its
6042 desktop to be useful for more people. The use case for this is my
6043 parents, which are currently running Kubuntu which solve the
6046 <p
>I suspect these four missing features are not very hard to
6047 implement. After all, they are present in Ubuntu, so if we wanted to
6048 do this in Debian we would have a source.
</p
>
6052 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
6053 are new packages available for upgrades, a icon in the KDE status bar
6054 indicate this, and clicking on it will activate the simple upgrade
6055 tool to handle it. I have no problem guiding both of my parents
6056 through the process over the phone. If a kernel reboot is required,
6057 this too is indicated by the status bars and the upgrade tool. Last
6058 time I checked, nothing with the same features was working in KDE in
6061 <li
><strong
>Simple handling of missing Firefox browser
6062 plugins.
</strong
> When the browser encounter a MIME type it do not
6063 currently have a handler for, it will ask the user if the system
6064 should search for a package that would add support for this MIME type,
6065 and if the user say yes, the APT sources will be searched for packages
6066 advertising the MIME type in their control file (visible in the
6067 Packages file in the APT archive). If one or more packages are found,
6068 it is a simple click of the mouse to add support for the missing mime
6069 type. If the package require the user to accept some non-free
6070 license, this is explained to the user. The entire process make it
6071 more clear to the user why something do not work in the browser, and
6072 make the chances higher for the user to blame the web page authors and
6073 not the browser for any missing features.
</li
>
6075 <li
><strong
>Simple handling of missing multimedia codec/format
6076 handlers.
</strong
> When the media players encounter a format or codec
6077 it is not supporting, a dialog pop up asking the user if the system
6078 should search for a package that would add support for it. This
6079 happen with things like MP3, Windows Media or H
.264. The selection
6080 and installation procedure is very similar to the Firefox browser
6081 plugin handling. This is as far as I know implemented using a
6082 gstreamer hook. The end result is that the user easily get access to
6083 the codecs that are present from the APT archives available, while
6084 explaining more on why a given format is unsupported by Ubuntu.
</li
>
6086 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
6087 displaying a text/plain file in my Debian browser, it will propose to
6088 start emacs to show it. If I remember correctly, when doing the same
6089 in Kunbutu it show the file as a text file in the browser. At least I
6090 know Opera will show text files within the browser. I much prefer the
6091 latter behaviour.
</li
>
6095 <p
>There are other nice features as well, like the simplified suite
6096 upgrader, but given that I am the one mostly doing the dist-upgrade,
6097 it do not matter much.
</p
>
6099 <p
>I really hope we could get these features in place for the next
6100 Debian release. It would require the coordinated effort of several
6101 maintainers, but would make the end user experience a lot better.
</p
>
6106 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
6107 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
6108 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
6109 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
6110 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
6111 site is build on Debian/Squeeze, and this platform was chosen because
6112 I am most familiar with Debian (being a Debian Developer for around
10
6113 years) because it is the latest stable Debian release which should get
6114 security support for a few years.
</p
>
6116 <p
>The web service is written in Perl, and depend on some perl modules
6117 that are missing in Debian at the moment. It would be great if these
6118 modules were added to the Debian archive, allowing anyone to set up
6119 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
6120 in their own country using only Debian packages. The list of modules
6121 missing in Debian/Squeeze isn
't very long, and I hope the perl group
6122 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
6123 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6124 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6125 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6126 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6127 easier in the future.
</p
>
6129 <p
>Thanks to the great tools in Debian, getting the missing modules
6130 installed on my server was a simple call to
'cpan2deb Module::Name
'
6131 and
'dpkg -i
' to install the resulting package. But this leave me
6132 with the responsibility of tracking security problems, which I really
6133 do not have time for.
</p
>
6138 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
6139 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
6140 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
6141 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
6142 <description><p
>Here is a small update for my English readers. Most of my blog
6143 posts have been in Norwegian the last few weeks, so here is a short
6144 update in English.
</p
>
6146 <p
>The kids still keep me too busy to get much free software work
6147 done, but I did manage to organise a project to get a Norwegian port
6148 of the British service
6149 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
6150 and it has been running for a month now. The entire project has been
6151 organised by me and two others. Around Christmas we gathered sponsors
6152 to fund the development work. In January I drafted a contract with
6153 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
6154 and in February the development took place. Most of it involved
6155 converting the source to use GPS coordinates instead of British
6156 easting/northing, and the resulting code should be a lot easier to get
6157 running in any country by now. The Norwegian
6158 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
6159 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
6160 source and the source for administrative borders in Norway, and
6161 support for this had to be added/fixed.
</p
>
6163 <p
>The Norwegian version went live March
3th, and we spent the weekend
6164 polishing the system before we announced it March
7th. The system is
6165 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
6166 problem reports in a few weeks. Soon we hope to announce the Android
6167 and iPhone versions making it even easier to report problems with the
6168 public infrastructure.
</p
>
6170 <p
>Perhaps something to consider for those of you in countries without
6171 such service?
</p
>
6176 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
6177 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
6178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
6179 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
6180 <description><p
>The last few days I have looked at ways to track open security
6181 issues here at my work with the University of Oslo. My idea is that
6182 it should be possible to use the information about security issues
6183 available on the Internet, and check our locally
6184 maintained/distributed software against this information. It should
6185 allow us to verify that no known security issues are forgotten. The
6186 CVE database listing vulnerabilities seem like a great central point,
6187 and by using the package lists from Debian mapped to CVEs provided by
6188 the testing security team, I believed it should be possible to figure
6189 out which security holes were present in our free software
6190 collection.
</p
>
6192 <p
>After reading up on the topic, it became obvious that the first
6193 building block is to be able to name software packages in a unique and
6194 consistent way across data sources. I considered several ways to do
6195 this, for example coming up with my own naming scheme like using URLs
6196 to project home pages or URLs to the Freshmeat entries, or using some
6197 existing naming scheme. And it seem like I am not the first one to
6198 come across this problem, as MITRE already proposed and implemented a
6199 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
6200 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
6201 software, hardware and other platform components. The CPE ids are
6202 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
6203 Vulnerability Database
</a
>, allowing me to look up know security
6204 issues for any CPE name. With this in place, all I need to do is to
6205 locate the CPE id for the software packages we use at the university.
6206 This is fairly trivial (I google for
'cve cpe $package
' and check the
6207 NVD entry if a CVE for the package exist).
</p
>
6209 <p
>To give you an example. The GNU gzip source package have the CPE
6210 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
6211 check out, one could look up
6212 <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
6213 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
6214 The most recent one is
6215 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
6216 and at the bottom of the NVD page for this vulnerability the complete
6217 list of affected versions is provided.
</p
>
6219 <p
>The NVD database of CVEs is also available as a XML dump, allowing
6220 for offline processing of issues. Using this dump, I
've written a
6221 small script taking a list of CPEs as input and list all CVEs
6222 affecting the packages represented by these CPEs. One give it CPEs
6223 with version numbers as specified above and get a list of open
6224 security issues out.
</p
>
6226 <p
>Of course for this approach to be useful, the quality of the NVD
6227 information need to be high. For that to happen, I believe as many as
6228 possible need to use and contribute to the NVD database. I notice
6230 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
6231 map from CVE to CPE
</a
>, indicating that they are using the CPE
6232 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
6234 <p
>To get an idea about the quality for free software, I spent some
6235 time making it possible to compare the CVE database from Debian with
6236 the CVE database in NVD. The result look fairly good, but there are
6237 some inconsistencies in NVD (same software package having several
6238 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6239 Debian believe are affected by a CVE). Hope to find time to improve
6240 the quality of NVD, but that require being able to get in touch with
6241 someone maintaining it. So far my three emails with questions and
6242 corrections have not seen any reply, but I hope contact can be
6243 established soon.
</p
>
6245 <p
>An interesting application for CPEs is cross platform package
6246 mapping. It would be useful to know which packages in for example
6247 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6248 this would be trivial if all linux distributions provided CPE entries
6249 for their packages.
</p
>
6254 <title>Which module is loaded for a given PCI and USB device?
</title>
6255 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
6256 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
6257 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
6258 <description><p
>In the
6259 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
6260 package in Debian, there is a script to report useful information
6261 about the running hardware for use when people report missing
6262 information. One part of this script that I find very useful when
6263 debugging hardware problems, is the part mapping loaded kernel module
6264 to the PCI device it claims. It allow me to quickly see if the kernel
6265 module I expect is driving the hardware I am struggling with. To see
6266 the output, make sure discover-data is installed and run
6267 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
6268 one of my machines like this:
</p
>
6272 10de:
03eb i2c_nforce2
6275 10de:
03f0 snd_hda_intel
6284 <p
>The code in question look like this, slightly modified for
6285 readability and to drop the output to file descriptor
3:
</p
>
6288 if [ -d /sys/bus/pci/devices/ ] ; then
6289 echo loaded pci modules:
6291 cd /sys/bus/pci/devices/
6292 for address in * ; do
6293 if [ -d
"$address/driver/module
" ] ; then
6294 module=`cd $address/driver/module ; pwd -P | xargs basename`
6295 if grep -q
"^$module
" /proc/modules ; then
6296 address=$(echo $address |sed s/
0000://)
6297 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
6298 echo
"$id $module
"
6307 <p
>Similar code could be used to extract USB device module
6311 if [ -d /sys/bus/usb/devices/ ] ; then
6312 echo loaded usb modules:
6314 cd /sys/bus/usb/devices/
6315 for address in * ; do
6316 if [ -d
"$address/driver/module
" ] ; then
6317 module=`cd $address/driver/module ; pwd -P | xargs basename`
6318 if grep -q
"^$module
" /proc/modules ; then
6319 address=$(echo $address |sed s/
0000://)
6320 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
6321 if [
"$id
" ] ; then
6322 echo
"$id $module
"
6332 <p
>This might perhaps be something to include in other tools as
6338 <title>How to test if a laptop is working with Linux
</title>
6339 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
6340 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
6341 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
6342 <description><p
>The last few days I have spent at work here at the
<a
6343 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
6344 batch of computers will work with Linux. Every year for the last few
6345 years the university have organised shared bid of a few thousand
6346 computers, and this year HP won the bid. Two different desktops and
6347 five different laptops are on the list this year. We in the UNIX
6348 group want to know which one of these computers work well with RHEL
6349 and Ubuntu, the two Linux distributions we currently handle at the
6350 university.
</p
>
6352 <p
>My test method is simple, and I share it here to get feedback and
6353 perhaps inspire others to test hardware as well. To test, I PXE
6354 install the OS version of choice, and log in as my normal user and run
6355 a few applications and plug in selected pieces of hardware. When
6356 something fail, I make a note about this in the test matrix and move
6357 on. If I have some spare time I try to report the bug to the OS
6358 vendor, but as I only have the machines for a short time, I rarely
6359 have the time to do this for all the problems I find.
</p
>
6361 <p
>Anyway, to get to the point of this post. Here is the simple tests
6362 I perform on a new model.
</p
>
6366 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
6367 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6368 RHEL5 and Debian Edu/Squeeze.
</li
>
6370 <li
>Is X.org working? If the graphical login screen show up after
6371 installation, X.org is working.
</li
>
6373 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
6374 package mesa-utils on Ubuntu) and writing down the frames per second
6375 reported by the program.
</li
>
6377 <li
>Is sound working? With Gnome and KDE, a sound is played when
6378 logging in, and if I can hear this the test is successful. If there
6379 are several audio exits on the machine, I try them all and check if
6380 the Gnome/KDE audio mixer can control where to send the sound. I
6381 normally test this by playing
6382 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
6383 video
</a
> in Firefox/Iceweasel.
</li
>
6385 <li
>Is the USB subsystem working? I test this by plugging in a USB
6386 memory stick and see if Gnome/KDE notices this.
</li
>
6388 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
6389 I have lying around, and see if Gnome/KDE notices this.
</li
>
6391 <li
>Is any built in camera working? Test using cheese, and see if a
6392 picture from the v4l device show up.
</li
>
6394 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6395 any bluetooth devices are discovered. In my office, I normally see a
6398 <li
>For laptops, is the SD or Compaq Flash reader working. I have
6399 memory modules lying around, and stick them in and see if Gnome/KDE
6400 notice this.
</li
>
6402 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
6403 special button work, and if the laptop continue to work after
6406 <li
>For laptops, is the extra buttons working, like audio level,
6407 adjusting background light, switching on/off external video output,
6408 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6409 laptop to laptop, so I just write down which are working and which are
6412 <li
>Some laptops have smart card readers, finger print readers,
6413 acceleration sensors etc. I rarely test these, as I do not know how
6414 to quickly test if they are working or not, so I only document their
6415 existence.
</li
>
6419 <p
>By now I suspect you are really curious what the test results are
6420 for the HP machines I am testing. I
'm not done yet, so I will report
6421 the test results later. For now I can report that HP
8100 Elite work
6422 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
6423 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
6424 can see, I have most machines left to test. One interesting
6425 observation is that Ubuntu Lucid has almost twice the frame rate than
6426 RHEL6 with glxgears. No idea why.
</p
>
6431 <title>Some thoughts on BitCoins
</title>
6432 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
6433 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
6434 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
6435 <description><p
>As I continue to explore
6436 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
6437 what properties the system have, and how it will be affected by laws
6438 and regulations here in Norway. Here are some random notes.
</p
>
6440 <p
>One interesting thing to note is that since the transactions are
6441 verified using a peer to peer network, all details about a transaction
6442 is known to everyone. This means that if a BitCoin address has been
6443 published like I did with mine in my initial post about BitCoin, it is
6444 possible for everyone to see how many BitCoins have been transfered to
6445 that address. There is even a web service to look at the details for
6446 all transactions. There I can see that my address
6447 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
6448 have received
16.06 Bitcoin, the
6449 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
6450 address of Simon Phipps have received
181.97 BitCoin and the address
6451 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
6452 of EFF have received
2447.38 BitCoins so far. Thank you to each and
6453 every one of you that donated bitcoins to support my activity. The
6454 fact that anyone can see how much money was transfered to a given
6455 address make it more obvious why the BitCoin community recommend to
6456 generate and hand out a new address for each transaction. I
'm told
6457 there is no way to track which addresses belong to a given person or
6458 organisation without the person or organisation revealing it
6459 themselves, as Simon, EFF and I have done.
</p
>
6461 <p
>In Norway, and in most other countries, there are laws and
6462 regulations limiting how much money one can transfer across the border
6463 without declaring it. There are money laundering, tax and accounting
6464 laws and regulations I would expect to apply to the use of BitCoin.
6465 If the Skolelinux foundation
6466 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
6467 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
6468 normal bank transfers like EFF is doing, how should this be accounted?
6469 Given that it is impossible to know if money can cross the border or
6470 not, should everything or nothing be declared? What exchange rate
6471 should be used when calculating taxes? Would receivers have to pay
6472 income tax if the foundation were to pay Skolelinux contributors in
6473 BitCoin? I have no idea, but it would be interesting to know.
</p
>
6475 <p
>For a currency to be useful and successful, it must be trusted and
6476 accepted by a lot of users. It must be possible to get easy access to
6477 the currency (as a wage or using currency exchanges), and it must be
6478 easy to spend it. At the moment BitCoin seem fairly easy to get
6479 access to, but there are very few places to spend it. I am not really
6480 a regular user of any of the vendor types currently accepting BitCoin,
6481 so I wonder when my kind of shop would start accepting BitCoins. I
6482 would like to buy electronics, travels and subway tickets, not herbs
6483 and books. :) The currency is young, and this will improve over time
6484 if it become popular, but I suspect regular banks will start to lobby
6485 to get BitCoin declared illegal if it become popular. I
'm sure they
6486 will claim it is helping fund terrorism and money laundering (which
6487 probably would be true, as is any currency in existence), but I
6488 believe the problems should be solved elsewhere and not by blaming
6489 currencies.
</p
>
6491 <p
>The process of creating new BitCoins is called mining, and it is
6492 CPU intensive process that depend on a bit of luck as well (as one is
6493 competing against all the other miners currently spending CPU cycles
6494 to see which one get the next lump of cash). The
"winner
" get
50
6495 BitCoin when this happen. Yesterday I came across the obvious way to
6496 join forces to increase ones changes of getting at least some coins,
6497 by coordinating the work on mining BitCoins across several machines
6498 and people, and sharing the result if one is lucky and get the
50
6500 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
6501 if this sounds interesting. I have not had time to try to set up a
6502 machine to participate there yet, but have seen that running on ones
6503 own for a few days have not yield any BitCoins througth mining
6506 <p
>Update
2010-
12-
15: Found an
<a
6507 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
6508 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
6509 it was interesting to read. The arguments presented seem to be
6510 equally valid for gold, which was used as a currency for many years.
</p
>
6515 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
6516 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
6517 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
6518 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
6519 <description><p
>With this weeks lawless
6520 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
6521 attacks
</a
> on Wikileak and
6522 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
6523 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
6524 not be trusted to handle money transactions.
6526 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
6527 Phipps on bitcoin
</a
> reminded me about a project that a friend of
6528 mine mentioned earlier. I decided to follow Simon
's example, and get
6529 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
6530 some help from my friend to get it all running, and he even handed me
6531 some bitcoins to get started. I even donated a few bitcoins to Simon
6532 for helping me remember BitCoin.
</p
>
6534 <p
>So, what is bitcoins, you probably wonder? It is a digital
6535 crypto-currency, decentralised and handled using peer-to-peer
6536 networks. It allows anonymous transactions and prohibits central
6537 control over the transactions, making it impossible for governments
6538 and companies alike to block donations and other transactions. The
6539 source is free software, and while the key dependency wxWidgets
2.9
6540 for the graphical user interface is missing in Debian, the command
6541 line client builds just fine. Hopefully Jonas
6542 <a href=
"http://bugs.debian.org/
578157">will get the package into
6543 Debian
</a
> soon.
</p
>
6545 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
6546 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
6547 bitcoins
</a
> when selling services and goods, and there are even
6548 currency
"stock
" markets where the exchange rate is decided. There
6549 are not many users so far, but the concept seems promising. If you
6550 want to get started and lack a friend with any bitcoins to spare,
6552 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
6553 bitcoin at the time of writing). Use
6554 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
6555 on the current exchange rates.
</p
>
6557 <p
>As an experiment, I have decided to set up bitcoind on one of my
6558 machines. If you want to support my activity, please send Bitcoin
6559 donations to the address
6560 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
6565 <title>Why isn
't Debian Edu using VLC?
</title>
6566 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
6567 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
6568 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
6569 <description><p
>In the latest issue of Linux Journal, the readers choices were
6570 presented, and the winner among the multimedia player were VLC.
6571 Personally, I like VLC, and it is my player of choice when I first try
6572 to play a video file or stream. Only if VLC fail will I drag out
6573 gmplayer to see if it can do better. The reason is mostly the failure
6574 model and trust. When VLC fail, it normally pop up a error message
6575 reporting the problem. When mplayer fail, it normally segfault or
6576 just hangs. The latter failure mode drain my trust in the program.
<p
>
6578 <p
>But even if VLC is my player of choice, we have choosen to use
6579 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
6580 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
6581 plugin to play web videos seamlessly, and the VLC browser plugin is
6582 not very good. For example, it lack in-line control buttons, so there
6583 is no way for the user to pause the video. Also, when I
6584 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
6585 tested the browser plugins
</a
> available in Debian, the VLC plugin
6586 failed on several video pages where mplayer based plugins worked. If
6587 the browser plugin for VLC was as good as the gecko-mediaplayer
6588 package (which uses mplayer), we would switch.
</P
>
6590 <p
>While VLC is a good player, its user interface is slightly
6591 annoying. The most annoying feature is its inconsistent use of
6592 keyboard shortcuts. When the player is in full screen mode, its
6593 shortcuts are different from when it is playing the video in a window.
6594 For example, space only work as pause when in full screen mode. I
6595 wish it had consisten shortcuts and that space also would work when in
6596 window mode. Another nice shortcut in gmplayer is [enter] to restart
6597 the current video. It is very nice when playing short videos from the
6598 web and want to restart it when new people arrive to have a look at
6599 what is going on.
</p
>
6604 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
6605 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
6606 <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>
6607 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
6608 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
6609 upgrade testing of the
6610 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6611 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
6612 This seem like a very good idea, so I adjusted by test scripts and
6613 can now present the updated result from today:
</p
>
6615 <p
>This is for Gnome:
</p
>
6617 <p
>Installed using apt-get, missing with aptitude
</p
>
6619 <blockquote
><p
>
6624 browser-plugin-gnash
6631 freedesktop-sound-theme
6633 gconf-defaults-service
6648 gnome-desktop-environment
6652 gnome-session-canberra
6657 gstreamer0.10-fluendo-mp3
6663 libapache2-mod-dnssd
6666 libaprutil1-dbd-sqlite3
6669 libboost-date-time1.42
.0
6670 libboost-python1.42
.0
6671 libboost-thread1.42
.0
6673 libchamplain-gtk-
0.4-
0
6675 libclutter-gtk-
0.10-
0
6682 libfreerdp-plugins-standard
6697 libgnomepanel2.24-cil
6702 libgtksourceview2.0-common
6703 libmono-addins-gui0.2-cil
6704 libmono-addins0.2-cil
6705 libmono-cairo2.0-cil
6706 libmono-corlib2.0-cil
6707 libmono-i18n-west2.0-cil
6708 libmono-posix2.0-cil
6709 libmono-security2.0-cil
6710 libmono-sharpzip2.84-cil
6711 libmono-system2.0-cil
6714 libndesk-dbus-glib1.0-cil
6715 libndesk-dbus1.0-cil
6725 libtelepathy-farsight0
6734 nautilus-sendto-empathy
6738 python-aptdaemon-gtk
6740 python-beautifulsoup
6755 python-gtksourceview2
6766 python-pkg-resources
6773 python-twisted-conch
6779 python-zope.interface
6784 rhythmbox-plugin-cdrecorder
6791 system-config-printer-udev
6793 telepathy-mission-control-
5
6804 </p
></blockquote
>
6806 <p
>Installed using apt-get, removed with aptitude
</p
>
6808 <blockquote
><p
>
6814 fast-user-switch-applet
6833 libgtksourceview2.0-
0
6835 libsdl1.2debian-alsa
6841 system-config-printer
6846 </p
></blockquote
>
6848 <p
>Installed using aptitude, missing with apt-get
</p
>
6850 <blockquote
><p
>
6851 gstreamer0.10-gnomevfs
6852 </p
></blockquote
>
6854 <p
>Installed using aptitude, removed with apt-get
</p
>
6856 <blockquote
><p
>
6858 </p
></blockquote
>
6860 <p
>This is for KDE:
</p
>
6862 <p
>Installed using apt-get, missing with aptitude
</p
>
6864 <blockquote
><p
>
6866 </p
></blockquote
>
6868 <p
>Installed using apt-get, removed with aptitude
</p
>
6870 <blockquote
><p
>
6873 </p
></blockquote
>
6875 <p
>Installed using aptitude, missing with apt-get
</p
>
6877 <blockquote
><p
>
6891 kdeartwork-emoticons
6893 kdeartwork-theme-icon
6897 kdebase-workspace-bin
6898 kdebase-workspace-data
6912 kscreensaver-xsavers
6927 plasma-dataengines-workspace
6929 plasma-desktopthemes-artwork
6930 plasma-runners-addons
6931 plasma-scriptengine-googlegadgets
6932 plasma-scriptengine-python
6933 plasma-scriptengine-qedje
6934 plasma-scriptengine-ruby
6935 plasma-scriptengine-webkit
6936 plasma-scriptengines
6937 plasma-wallpapers-addons
6938 plasma-widget-folderview
6939 plasma-widget-networkmanagement
6943 xscreensaver-data-extra
6945 xscreensaver-gl-extra
6946 xscreensaver-screensaver-bsod
6947 </p
></blockquote
>
6949 <p
>Installed using aptitude, removed with apt-get
</p
>
6951 <blockquote
><p
>
6953 google-gadgets-common
6971 libggadget-qt-
1.0-
0b
6976 libkonqsidebarplugin4a
6985 libplasma-geolocation-interface4
6987 libplasmagenericshell4
7001 libsmokeknewstuff2-
3
7002 libsmokeknewstuff3-
3
7004 libsmokektexteditor3
7012 libsmokeqtnetwork4-
3
7018 libsmokeqtuitools4-
3
7030 plasma-dataengines-addons
7031 plasma-scriptengine-superkaramba
7032 plasma-widget-lancelot
7033 plasma-widgets-addons
7034 plasma-widgets-workspace
7038 update-notifier-common
7039 </p
></blockquote
>
7041 <p
>Running apt-get autoremove made the results using apt-get and
7042 aptitude a bit more similar, but there are still quite a lott of
7043 differences. I have no idea what packages should be installed after
7044 the upgrade, but hope those that do can have a look.
</p
>
7049 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
7050 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
7051 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
7052 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
7053 <description><p
>Most of the computers in use by the
7054 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
7055 are virtual machines. And they have been Xen machines running on a
7056 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
7057 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
7058 bit harder that it could have been, because we set up the Xen virtual
7059 machines to get the virtual partitions from LVM, which as far as I
7060 know is not supported by KVM. So to migrate, we had to convert
7061 several LVM logical volumes to partitions on a virtual disk file.
</p
>
7064 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
7065 nice recipe
</a
> to do this, and wrote the following script to do the
7066 migration. It uses qemu-img from the qemu package to make the disk
7067 image, parted to partition it, losetup and kpartx to present the disk
7068 image partions as devices, and dd to copy the data. I NFS mounted the
7069 new servers storage area on the old server to do the migration.
</p
>
7075 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7080 if [ -z
"$
1" ] ; then
7081 echo
"Usage: $
0 &lt;hostname
&gt;
"
7087 if [ ! -e /dev/vg_data/$host-disk ] ; then
7088 echo
"error: unable to find LVM volume for $host
"
7092 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7093 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7094 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7095 totalsize=$(( ( $disksize + $swapsize ) ))
7098 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
7099 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7101 parted $img mklabel msdos
7102 parted $img mkpart primary linux-swap
0 $disksize
7103 parted $img mkpart primary ext2 $disksize $totalsize
7104 parted $img set
1 boot on
7107 losetup /dev/loop0 $img
7108 kpartx -a /dev/loop0
7110 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
7111 fsck.ext3 -f /dev/mapper/loop0p1 || true
7112 mkswap /dev/mapper/loop0p2
7114 kpartx -d /dev/loop0
7115 losetup -d /dev/loop0
7118 <p
>The script is perhaps so simple that it is not copyrightable, but
7119 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
7121 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
7122 the new disk image attached, installed grub-pc and linux-image-
686 and
7123 set up grub to boot from the disk image. After this, the KVM machines
7124 seem to work just fine.
</p
>
7129 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
7130 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
7131 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
7132 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
7133 <description><p
>I
'm still running upgrade testing of the
7134 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7135 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
7136 status. Here is a short update based on a test I ran
20101118.
</p
>
7138 <p
>I still do not know what a correct migration should look like, so I
7139 report any differences between apt and aptitude and hope someone else
7140 can see if anything should be changed.
</p
>
7142 <p
>This is for Gnome:
</p
>
7144 <p
>Installed using apt-get, missing with aptitude
</p
>
7146 <blockquote
><p
>
7147 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7148 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
7149 dmz-cursor-theme empathy empathy-common finger
7150 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7151 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7152 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7153 gnome-cards-data gnome-codec-install gnome-core
7154 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7155 gnome-search-tool gnome-session-canberra gnome-spell
7156 gnome-system-log gnome-themes-extras gnome-themes-more
7157 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7158 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7159 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7160 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7161 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
7162 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
7163 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
7164 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
7165 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
7166 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7167 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
7168 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7169 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7170 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7171 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7172 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7173 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7174 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7175 libmono-security2.0-cil libmono-sharpzip2.84-cil
7176 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
7177 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
7178 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
7179 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
7180 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
7181 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
7182 libxalan2-java libxerces2-java media-player-info mesa-utils
7183 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
7184 nautilus-sendto-empathy openoffice.org-writer2latex
7185 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
7186 python-aptdaemon python-aptdaemon-gtk python-axiom
7187 python-beautifulsoup python-bugbuddy python-clientform
7188 python-coherence python-configobj python-crypto python-cupshelpers
7189 python-cupsutils python-eggtrayicon python-elementtree
7190 python-epsilon python-evolution python-feedparser python-gdata
7191 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7192 python-gtksourceview2 python-httplib2 python-louie python-mako
7193 python-markupsafe python-mechanize python-nevow python-notify
7194 python-opengl python-openssl python-pam python-pkg-resources
7195 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7196 python-tagpy python-twisted-bin python-twisted-conch
7197 python-twisted-core python-twisted-web python-utidylib python-webkit
7198 python-xdg python-zope.interface remmina remmina-plugin-data
7199 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7200 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7201 software-center svgalibg1 system-config-printer-udev
7202 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
7203 totem totem-coherence totem-mozilla totem-plugins
7204 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7206 </p
></blockquote
>
7208 Installed using apt-get, removed with aptitude
7210 <blockquote
><p
>
7211 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7212 epiphany-extensions epiphany-gecko evolution-exchange
7213 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7214 gedit-common gnome-app-install gnome-games gnome-games-data
7215 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7216 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7217 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7218 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
7219 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
7220 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
7221 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
7222 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7223 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7224 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7225 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
7226 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
7227 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7228 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7229 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7230 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7231 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
7232 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
7233 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
7234 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
7235 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
7236 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7237 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7238 sound-juicer swfdec-gnome system-config-printer totem-common
7239 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7240 </p
></blockquote
>
7242 <p
>Installed using aptitude, missing with apt-get
</p
>
7244 <blockquote
><p
>
7245 gstreamer0.10-gnomevfs
7246 </p
></blockquote
>
7248 <p
>Installed using aptitude, removed with apt-get
</p
>
7250 <blockquote
><p
>
7252 </p
></blockquote
>
7254 <p
>This is for KDE:
</p
>
7256 <p
>Installed using apt-get, missing with aptitude
</p
>
7258 <blockquote
><p
>
7259 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
7260 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7261 ghostscript-x git gnome-audio gnugo granatier gs-common
7262 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7263 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7264 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7265 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7266 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7267 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7268 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7269 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7270 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7271 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7272 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7273 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
7274 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7275 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7276 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7277 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7278 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7279 libkrossui4 libmailtools-perl libmime-tools-perl
7280 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7281 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7282 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7283 lirc luatex marble networkstatus noatun-plugins
7284 openoffice.org-writer2latex palapeli palapeli-data parley
7285 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7286 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7287 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7289 </p
></blockquote
>
7291 <p
>Installed using apt-get, removed with aptitude
</p
>
7293 <blockquote
><p
>
7294 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7295 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7296 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7297 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7298 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7299 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7300 kitchensync kiten kjumpingcube klatin klettres klickety klines
7301 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7302 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7303 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7304 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7305 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7306 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7307 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7308 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7309 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7310 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
7311 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
7312 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7313 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
7314 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
7315 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7316 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7317 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7318 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7319 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7320 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7321 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
7322 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
7323 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7324 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7325 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7326 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7327 </p
></blockquote
>
7329 <p
>Installed using aptitude, missing with apt-get
</p
>
7331 <blockquote
><p
>
7332 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7333 kdeartwork kdebase kdebase-apps kdebase-workspace
7334 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7335 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7336 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7337 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7338 xscreensaver-screensaver-bsod
7339 </p
></blockquote
>
7341 <p
>Installed using aptitude, removed with apt-get
</p
>
7343 <blockquote
><p
>
7344 kdebase-bin konq-plugins konqueror
7345 </p
></blockquote
>
7350 <title>Gnash buildbot slave and Debian kfreebsd
</title>
7351 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
7352 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
7353 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
7354 <description><p
>Answering
7355 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
7356 call from the Gnash project
</a
> for
7357 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
7358 current source, I have set up a virtual KVM machine on the Debian
7359 Edu/Skolelinux virtualization host to test the git source on
7360 Debian/Squeeze. I hope this can help the developers in getting new
7361 releases out more often.
</p
>
7363 <p
>As the developers want less main-stream build platforms tested to,
7364 I have considered setting up a
<a
7365 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
7366 machine as well. I have also considered using the kfreebsd
7367 architecture in Debian as a file server in NUUG to get access to the
5
7368 TB zfs volume we currently use to store DV video. Because of this, I
7369 finally got around to do a test installation of Debian/Squeeze with
7370 kfreebsd. Installation went fairly smooth, thought I noticed some
7371 visual glitches in the cdebconf dialogs (black cursor left on the
7372 screen at random locations). Have not gotten very far with the
7373 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7374 fatal problem. Have to spend some more time on it to see if it is
7375 useful as a file server for NUUG. Will try to find time to set up a
7376 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
7381 <title>Debian in
3D
</title>
7382 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
7383 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
7384 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
7385 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
7387 <p
>3D printing is just great. I just came across this Debian logo in
7389 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
7390 thingiverse blog
</a
>.
</p
>
7395 <title>Software updates
2010-
10-
24</title>
7396 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
7397 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
7398 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
7399 <description><p
>Some updates.
</p
>
7401 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
7402 raise money for the project is going well. The lower limit of
10
7403 signers was reached in
24 hours, and so far
13 people have signed it.
7404 More signers and more funding is most welcome, and I am really curious
7405 how far we can get before the time limit of December
24 is reached.
7408 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
7409 about what appear to be a great code coverage tool capable of
7410 generating code coverage stats without any changes to the source code.
7412 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
7413 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
7414 It is missing in Debian, but the git source built just fine in Squeeze
7415 after I installed libelf-dev, libdwarf-dev, pkg-config and
7416 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7417 solvable. I hope kcov make it into Debian soon.
</p
>
7419 <p
>Finally found time to wrap up the release notes for
<a
7420 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
7421 new alpha release of Debian Edu
</a
>, and just published the second
7422 alpha test release of the Squeeze based Debian Edu /
7423 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
7424 release. Give it a try if you need a complete linux solution for your
7425 school, including central infrastructure server, workstations, thin
7426 client servers and diskless workstations. A nice touch added
7427 yesterday is RDP support on the thin client servers, for windows
7428 clients to get a Linux desktop on request.
</p
>
7433 <title>Some notes on Flash in Debian and Debian Edu
</title>
7434 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
7435 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
7436 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
7437 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
7438 popularity-contest numbers
</a
>, the adobe-flashplugin package the
7439 second most popular used package that is missing in Debian. The sixth
7440 most popular is flashplayer-mozilla. This is a clear indication that
7441 working flash is important for Debian users. Around
10 percent of the
7442 users submitting data to popcon.debian.org have this package
7443 installed.
</p
>
7445 <p
>In the report written by Lars Risan in August
2008
7446 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
7447 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7448 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
7449 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
7450 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
7451 web sites require Flash to work, and lacking working Flash support in
7452 the web browser and the problems with installing it was perceived as a
7453 good reason to stay with Windows.
</p
>
7455 <p
>I once saw a funny and sad comment in a web forum, where Linux was
7456 said to be the retarded cousin that did not really understand
7457 everything you told him but could work fairly well. This was a
7458 comment regarding the problems Linux have with proprietary formats and
7459 non-standard web pages, and is sad because it exposes a fairly common
7460 understanding of whose fault it is if web pages that only work in for
7461 example Internet Explorer
6 fail to work on Firefox, and funny because
7462 it explain very well how annoying it is for users when Linux
7463 distributions do not work with the documents they receive or the web
7464 pages they want to visit.
</p
>
7466 <p
>This is part of the reason why I believe it is important for Debian
7467 and Debian Edu to have a well working Flash implementation in the
7468 distribution, to get at least popular sites as Youtube and Google
7469 Video to working out of the box. For Squeeze, Debian have the chance
7470 to include the latest version of Gnash that will make this happen, as
7471 the new release
0.8.8 was published a few weeks ago and is resting in
7472 unstable. The new version work with more sites that version
0.8.7.
7473 The Gnash maintainers have asked for a freeze exception, but the
7474 release team have not had time to reply to it yet. I hope they agree
7475 with me that Flash is important for the Debian desktop users, and thus
7476 accept the new package into Squeeze.
</p
>
7481 <title>Circular package dependencies harms apt recovery
</title>
7482 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
7483 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
7484 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
7485 <description><p
>I discovered this while doing
7486 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
7487 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
7488 in Debian still got circular dependencies, and it is often claimed
7489 that apt and aptitude should be able to handle this just fine, but
7490 some times these dependency loops causes apt to fail.
</p
>
7492 <p
>An example is from todays
7493 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
7494 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
7495 causes perl-modules to fail to upgrade. The cause is simple. If a
7496 package fail to unpack, then only part of packages with the circular
7497 dependency might end up being unpacked when unpacking aborts, and the
7498 ones already unpacked will fail to configure in the recovery phase
7499 because its dependencies are unavailable.
</p
>
7501 <p
>In this log, the problem manifest itself with this error:
</p
>
7503 <blockquote
><pre
>
7504 dpkg: dependency problems prevent configuration of perl-modules:
7505 perl-modules depends on perl (
>=
5.10.1-
1); however:
7506 Version of perl on system is
5.10.0-
19lenny
2.
7507 dpkg: error processing perl-modules (--configure):
7508 dependency problems - leaving unconfigured
7509 </pre
></blockquote
>
7511 <p
>The perl/perl-modules circular dependency is already
7512 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
7513 hopefully be solved as soon as possible, but it is not the only one,
7514 and each one of these loops in the dependency tree can cause similar
7515 failures. Of course, they only occur when there are bugs in other
7516 packages causing the unpacking to fail, but it is rather nasty when
7517 the failure of one package causes the problem to become worse because
7518 of dependency loops.
</p
>
7521 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
7522 tireless effort by Bill Allombert
</a
>, the number of circular
7524 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
7525 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
7527 <p
>Todays testing also exposed a bug in
7528 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
7529 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
7530 apt-get and aptitude, the latter possibly caused by some circular
7531 dependency. Reported both to BTS to try to get someone to look at
7537 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
7538 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
7539 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
7540 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
7541 <description><p
>This is a
7542 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
7544 <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
7546 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
7547 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
7549 <p
>As a step to try to see if it possible to merge the DNS and DHCP
7550 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7551 and dhcp3-server-ldap in Debian use the LDAP server. The two
7552 implementations are quite different in how they use LDAP.
</p
>
7554 To get this information, I started slapd with debugging enabled and
7555 dumped the debug output to a file to get the LDAP searches performed
7556 on a Debian Edu main-server. Here is a summary.
7558 <p
><strong
>powerdns
</strong
></p
>
7560 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
7561 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
7564 <p
>PowerDNS have two modes of operation using LDAP as its backend.
7565 One
"strict
" mode where the forward and reverse DNS lookups are done
7566 using the same LDAP objects, and a
"tree
" mode where the forward and
7567 reverse entries are in two different subtrees in LDAP with a structure
7568 based on the DNS names, as in tjener.intern and
7569 2.2.0.10.in-addr.arpa.
</p
>
7571 <p
>In tree mode, the server is set up to use a LDAP subtree as its
7572 base, and uses a
"base
" scoped search for the DNS name by adding
7573 "dc=tjener,dc=intern,
" to the base with a filter for
7574 "(associateddomain=tjener.intern)
" for the forward entry and
7575 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
7576 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
7577 forward entries, it is looking for attributes named dnsttl, arecord,
7578 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7579 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7580 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7581 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7582 spfrecord and modifytimestamp. For reverse entries it is looking for
7583 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7584 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7585 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7586 ldapsearch commands could look like this:
</p
>
7588 <blockquote
><pre
>
7589 ldapsearch -h ldap \
7590 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7591 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7592 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7593 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7594 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7595 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7597 ldapsearch -h ldap \
7598 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7599 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
7600 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7601 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7602 srvrecord naptrrecord modifytimestamp
7603 </pre
></blockquote
>
7605 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
7606 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7607 example LDAP objects used there. In addition to these objects, the
7608 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7609 also exist.
</p
>
7611 <blockquote
><pre
>
7612 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7614 objectclass: dnsdomain
7615 objectclass: domainrelatedobject
7618 associateddomain: tjener.intern
7620 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7622 objectclass: dnsdomain2
7623 objectclass: domainrelatedobject
7625 ptrrecord: tjener.intern
7626 associateddomain:
2.2.0.10.in-addr.arpa
7627 </pre
></blockquote
>
7629 <p
>In strict mode, the server behaves differently. When looking for
7630 forward DNS entries, it is doing a
"subtree
" scoped search with the
7631 same base as in the tree mode for a object with filter
7632 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
7633 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7634 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7635 naptrrecord and modifytimestamp. For reverse entires it also do a
7636 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
7637 and the requested attributes are associateddomain, dnsttl and
7638 modifytimestamp. In short, in strict mode the objects with ptrrecord
7639 go away, and the arecord attribute in the forward object is used
7642 <p
>The forward and reverse searches can be simulated using ldapsearch
7643 like this:
</p
>
7645 <blockquote
><pre
>
7646 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7647 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7648 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7649 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7650 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7651 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7653 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7654 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
7655 </pre
></blockquote
>
7657 <p
>In addition to the forward and reverse searches , there is also a
7658 search for SOA records, which behave similar to the forward and
7659 reverse lookups.
</p
>
7661 <p
>A thing to note with the PowerDNS behaviour is that it do not
7662 specify any objectclass names, and instead look for the attributes it
7663 need to generate a DNS reply. This make it able to work with any
7664 objectclass that provide the needed attributes.
</p
>
7666 <p
>The attributes are normally provided in the cosine (RFC
1274) and
7667 dnsdomain2 schemas. The latter is used for reverse entries like
7668 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
7670 <p
>In Debian Edu, we have created DNS objects using the object classes
7671 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7672 attributes) and domainrelatedobject (for associatedDomain). The use
7673 of structural object classes make it impossible to combine these
7674 classes with the object classes used by DHCP.
</p
>
7676 <p
>There are other schemas that could be used too, for example the
7677 dnszone structural object class used by Gosa and bind-sdb for the DNS
7678 attributes combined with the domainrelatedobject object class, but in
7679 this case some unused attributes would have to be included as well
7680 (zonename and relativedomainname).
</p
>
7682 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
7683 mode and not use any of the existing objectclasses (dnsdomain,
7684 dnsdomain2 and dnszone) when one want to combine the DNS information
7685 with DHCP information, and instead create a auxiliary object class
7686 defined something like this (using the attributes defined for
7687 dnsdomain and dnsdomain2 or dnszone):
</p
>
7689 <blockquote
><pre
>
7690 objectclass ( some-oid NAME
'dnsDomainAux
'
7693 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7694 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7695 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7696 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7697 A6Record $ DNAMERecord
7699 </pre
></blockquote
>
7701 <p
>This will allow any object to become a DNS entry when combined with
7702 the domainrelatedobject object class, and allow any entity to include
7703 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
7704 developers asking for their view on this schema and if they are
7705 interested in providing such schema with PowerDNS, and I hope my
7706 message will be accepted into their mailing list soon.
</p
>
7708 <p
><strong
>ISC dhcp
</strong
></p
>
7710 <p
>The DHCP server searches for specific objectclass and requests all
7711 the object attributes, and then uses the attributes it want. This
7712 make it harder to figure out exactly what attributes are used, but
7713 thanks to the working example in Debian Edu I can at least get an idea
7714 what is needed without having to read the source code.
</p
>
7716 <p
>In the DHCP server configuration, the LDAP base to use and the
7717 search filter to use to locate the correct dhcpServer entity is
7718 stored. These are the relevant entries from
7719 /etc/dhcp3/dhcpd.conf:
</p
>
7721 <blockquote
><pre
>
7722 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
7723 ldap-dhcp-server-cn
"dhcp
";
7724 </pre
></blockquote
>
7726 <p
>The DHCP server uses this information to nest all the DHCP
7727 configuration it need. The cn
"dhcp
" is located using the given LDAP
7728 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
7729 search result is this entry:
</p
>
7731 <blockquote
><pre
>
7732 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7735 objectClass: dhcpServer
7736 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7737 </pre
></blockquote
>
7739 <p
>The content of the dhcpServiceDN attribute is next used to locate the
7740 subtree with DHCP configuration. The DHCP configuration subtree base
7741 is located using a base scope search with base
"cn=DHCP
7742 Config,dc=skole,dc=skolelinux,dc=no
" and filter
7743 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
7744 The search result is this entry:
</p
>
7746 <blockquote
><pre
>
7747 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7750 objectClass: dhcpService
7751 objectClass: dhcpOptions
7752 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7753 dhcpStatements: ddns-update-style none
7754 dhcpStatements: authoritative
7755 dhcpOption: smtp-server code
69 = array of ip-address
7756 dhcpOption: www-server code
72 = array of ip-address
7757 dhcpOption: wpad-url code
252 = text
7758 </pre
></blockquote
>
7760 <p
>Next, the entire subtree is processed, one level at the time. When
7761 all the DHCP configuration is loaded, it is ready to receive requests.
7762 The subtree in Debian Edu contain objects with object classes
7763 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7764 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7765 and information about netmasks, dynamic range etc. Leaving out the
7766 details here because it is not relevant for the focus of my
7767 investigation, which is to see if it is possible to merge dns and dhcp
7768 related computer objects.
</p
>
7770 <p
>When a DHCP request come in, LDAP is searched for the MAC address
7771 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
7772 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
7773 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7774 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
7777 <blockquote
><pre
>
7778 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7781 objectClass: dhcpHost
7782 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7783 dhcpStatements: fixed-address hostname
7784 </pre
></blockquote
>
7786 <p
>There is less flexiblity in the way LDAP searches are done here.
7787 The object classes need to have fixed names, and the configuration
7788 need to be stored in a fairly specific LDAP structure. On the
7789 positive side, the invidiual dhcpHost entires can be anywhere without
7790 the DN pointed to by the dhcpServer entries. The latter should make
7791 it possible to group all host entries in a subtree next to the
7792 configuration entries, and this subtree can also be shared with the
7793 DNS server if the schema proposed above is combined with the dhcpHost
7794 structural object class.
7796 <p
><strong
>Conclusion
</strong
></p
>
7798 <p
>The PowerDNS implementation seem to be very flexible when it come
7799 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
7800 come to the the LDAP structure, the
"strict
" mode is very flexible,
7801 allowing DNS objects to be stored anywhere under the base cn specified
7802 in the configuration.
</p
>
7804 <p
>The DHCP implementation on the other hand is very inflexible, both
7805 regarding which LDAP schemas to use and which LDAP structure to use.
7806 I guess one could implement ones own schema, as long as the
7807 objectclasses and attributes have the names used, but this do not
7808 really help when the DHCP subtree need to have a fairly fixed
7809 structure.
</p
>
7811 <p
>Based on the observed behaviour, I suspect a LDAP structure like
7812 this might work for Debian Edu:
</p
>
7814 <blockquote
><pre
>
7816 cn=machine-info (dhcpService) - dhcpServiceDN points here
7817 cn=dhcp (dhcpServer)
7818 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7819 cn=
10.0.2.0 (dhcpSubnet)
7820 cn=group1 (dhcpGroup/dhcpOptions)
7821 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7822 cn=
192.168.0.0 (dhcpSubnet)
7823 cn=group1 (dhcpGroup/dhcpOptions)
7824 ou=machines - PowerDNS base points here
7825 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7826 </pre
></blockquote
>
7828 <P
>This is not tested yet. If the DHCP server require the dhcpHost
7829 entries to be in the dhcpGroup subtrees, the entries can be stored
7830 there instead of a common machines subtree, and the PowerDNS base
7831 would have to be moved one level up to the machine-info subtree.
</p
>
7833 <p
>The combined object under the machines subtree would look something
7834 like this:
</p
>
7836 <blockquote
><pre
>
7837 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7840 objectClass: dhcpHost
7841 objectclass: domainrelatedobject
7842 objectclass: dnsDomainAux
7843 associateddomain: hostname.intern
7844 arecord:
10.11.12.13
7845 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7846 dhcpStatements: fixed-address hostname.intern
7847 </pre
></blockquote
>
7849 </p
>One could even add the LTSP configuration associated with a given
7850 machine, as long as the required attributes are available in a
7851 auxiliary object class.
</p
>
7856 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
7857 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
7858 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
7859 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
7860 <description><p
>For a while now, I have wanted to find a way to change the DNS and
7861 DHCP services in Debian Edu to use the same LDAP objects for a given
7862 computer, to avoid the possibility of having a inconsistent state for
7863 a computer in LDAP (as in DHCP but no DNS entry or the other way
7864 around) and make it easier to add computers to LDAP.
</p
>
7866 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
7867 information finally found a solution that seem to work.
</p
>
7869 <p
>The old setup required three LDAP objects for a given computer.
7870 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7871 we switch powerdns to use its strict LDAP method (ldap-method=strict
7872 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7873 merged into one while making it impossible to transfer the reverse map
7874 to a slave DNS server.
</p
>
7876 <p
>If we also replace the object class used to get the DNS related
7877 attributes to one allowing these attributes to be combined with the
7878 dhcphost object class, we can merge the DNS and DHCP entries into one.
7879 I
've written such object class in the dnsdomainaux.schema file (need
7880 proper OIDs, but that is a minor issue), and tested the setup. It
7881 seem to work.
</p
>
7883 <p
>With this test setup in place, we can get away with one LDAP object
7884 for both DNS and DHCP, and even the LTSP configuration I suggested in
7885 an earlier email. The combined LDAP object will look something like
7888 <blockquote
><pre
>
7889 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7891 objectClass: dhcphost
7892 objectclass: domainrelatedobject
7893 objectclass: dnsdomainaux
7894 associateddomain: hostname.intern
7895 arecord:
10.11.12.13
7896 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
7897 dhcpstatements: fixed-address hostname
7899 </pre
></blockquote
>
7901 <p
>The DNS server uses the associateddomain and arecord entries, while
7902 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7903 before asking DNS to resolve the fixed-adddress. LTSP will use
7904 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
7906 <p
>I am not yet sure if I can get the DHCP server to look for its
7907 dhcphost in a different location, to allow us to put the objects
7908 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
7909 that. If I can
't figure out a way to do that, we can still get rid of
7910 the hosts subtree and move all its content into the DHCP Config tree
7911 (which probably should be renamed to be more related to the new
7912 content. I suspect cn=dnsdhcp,ou=services or something like that
7913 might be a good place to put it.
</p
>
7915 <p
>If you want to help out with implementing this for Debian Edu,
7916 please contact us on debian-edu@lists.debian.org.
</p
>
7921 <title>Idea for storing LTSP configuration in LDAP
</title>
7922 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
7923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
7924 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
7925 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
7926 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7927 clients, and that this can be used to fetch configuration from LDAP if
7928 Debian Edu choose to store configuration there.
</p
>
7930 <p
>Armed with this information, I got inspired and wrote a test module
7931 to get configuration from LDAP. The idea is to look up the MAC
7932 address of the client in LDAP, and look for attributes on the form
7933 ltspconfigsetting=value, and use this to export SETTING=value to the
7934 LTSP clients.
</p
>
7936 <p
>The goal is to be able to store the LTSP configuration attributes
7937 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
7938 allowing us to store all information about a computer in one place.
</p
>
7940 <p
>This is a untested draft implementation, and I welcome feedback on
7941 this approach. A real LDAP schema for the ltspClientAux objectclass
7942 need to be written. Comments, suggestions, etc?
</p
>
7944 <blockquote
><pre
>
7945 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7947 # Fetch LTSP client settings from LDAP based on MAC address
7949 # Uses ethernet address as stored in the dhcpHost objectclass using
7950 # the dhcpHWAddress attribute or ethernet address stored in the
7951 # ieee802Device objectclass with the macAddress attribute.
7953 # This module is written to be schema agnostic, and only depend on the
7954 # existence of attribute names.
7956 # The LTSP configuration variables are saved directly using a
7957 # ltspConfig prefix and uppercasing the rest of the attribute name.
7958 # To set the SERVER variable, set the ltspConfigServer attribute.
7960 # Some LDAP schema should be created with all the relevant
7961 # configuration settings. Something like this should work:
7963 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
7966 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7968 LDAPSERVER=$(debian-edu-ldapserver)
7969 if [
"$LDAPSERVER
" ] ; then
7970 LDAPBASE=$(debian-edu-ldapserver -b)
7971 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
7972 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
7973 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
7974 grep
'^ltspConfig
' | while read attr value ; do
7975 # Remove prefix and convert to upper case
7976 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
7977 # bass value on to clients
7978 eval
"$attr=$value; export $attr
"
7982 </pre
></blockquote
>
7984 <p
>I
'm not sure this shell construction will work, because I suspect
7985 the while block might end up in a subshell causing the variables set
7986 there to not show up in ltsp-config, but if that is the case I am sure
7987 the code can be restructured to make sure the variables are passed on.
7988 I expect that can be solved with some testing. :)
</p
>
7990 <p
>If you want to help out with implementing this for Debian Edu,
7991 please contact us on debian-edu@lists.debian.org.
</p
>
7993 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
7994 configuration in LDAP that was created around year
2000 by
7995 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
7996 Xperience, Inc.,
2000</a
>. I found its
7997 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
7998 personal home page over at redhat.com.
</p
>
8003 <title>jXplorer, a very nice LDAP GUI
</title>
8004 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8005 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8006 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8007 <description><p
>Since
8008 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8009 last post
</a
> about available LDAP tools in Debian, I was told about a
8010 LDAP GUI that is even better than luma. The java application
8011 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8012 moving LDAP objects and subtrees using drag-and-drop, and can
8013 authenticate using Kerberos. I have only tested the Kerberos
8014 authentication, but do not have a LDAP setup allowing me to rewrite
8015 LDAP with my test user yet. It is
8016 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8017 Debian
</a
> testing and unstable at the moment. The only problem I
8018 have with it is how it handle errors. If something go wrong, its
8019 non-intuitive behaviour require me to go through some query work list
8020 and remove the failing query. Nothing big, but very annoying.
</p
>
8025 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8026 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8027 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8028 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8029 <description><p
>Here is a short update on my
<a
8030 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8031 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8032 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8033 not reporting the status for KDE, because the upgrade crashes when
8034 aptitude try because of missing conflicts
8035 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8036 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8038 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8039 complete list of the installed packages. Based on this I see these
8040 differences when I did a test run today. As usual, I do not really
8041 know what the correct set of packages would be, but thought it best to
8042 publish the difference.
</p
>
8044 <p
>Installed using apt-get, missing with aptitude
</p
>
8046 <blockquote
><p
>
8047 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
8048 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
8049 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8050 libgtksourceview-common libpt-
1.10.10-plugins-alsa
8051 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8052 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8053 python-
4suite-xml python-eggtrayicon python-gtkhtml2
8054 python-gtkmozembed svgalibg1 xserver-xephyr zip
8055 </p
></blockquote
>
8057 <p
>Installed using apt-get, removed with aptitude
</p
>
8059 <blockquote
><p
>
8060 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8061 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8062 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
8063 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
8064 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
8065 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
8066 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8067 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8068 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8069 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
8070 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
8071 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
8072 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8073 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
8074 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8075 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
8076 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
8077 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8078 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8079 mysql-common swfdec-gnome totem-gstreamer wodim
8080 </p
></blockquote
>
8082 <p
>Installed using aptitude, missing with apt-get
</p
>
8084 <blockquote
><p
>
8085 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8086 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8087 xserver-xorg-input-all xserver-xorg-input-evdev
8088 xserver-xorg-input-kbd xserver-xorg-input-mouse
8089 xserver-xorg-input-synaptics xserver-xorg-video-all
8090 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8091 xserver-xorg-video-chips xserver-xorg-video-cirrus
8092 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8093 xserver-xorg-video-glint xserver-xorg-video-i128
8094 xserver-xorg-video-i740 xserver-xorg-video-mach64
8095 xserver-xorg-video-mga xserver-xorg-video-neomagic
8096 xserver-xorg-video-nouveau xserver-xorg-video-nv
8097 xserver-xorg-video-r128 xserver-xorg-video-radeon
8098 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8099 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8100 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8101 xserver-xorg-video-sis xserver-xorg-video-sisusb
8102 xserver-xorg-video-tdfx xserver-xorg-video-tga
8103 xserver-xorg-video-trident xserver-xorg-video-tseng
8104 xserver-xorg-video-vesa xserver-xorg-video-vmware
8105 xserver-xorg-video-voodoo
8106 </p
></blockquote
>
8108 <p
>Installed using aptitude, removed with apt-get
</p
>
8110 <blockquote
><p
>
8111 deskbar-applet xserver-xorg xserver-xorg-core
8112 xserver-xorg-input-wacom xserver-xorg-video-intel
8113 xserver-xorg-video-openchrome
8114 </p
></blockquote
>
8116 <p
>I was told on IRC that the xorg-xserver package was
8117 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
8118 in git
</a
> today to try to get apt-get to not remove xorg completely.
8119 No idea when it hits Squeeze, but when it does I hope it will reduce
8120 the difference somewhat.
8125 <title>LUMA, a very nice LDAP GUI
</title>
8126 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
8127 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
8128 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
8129 <description><p
>The last few days I have been looking into the status of the LDAP
8130 directory in Debian Edu, and in the process I started to miss a GUI
8131 tool to browse the LDAP tree. The only one I was able to find in
8132 Debian/Squeeze and Lenny is
8133 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
8134 be a great tool to get a overview of the current LDAP directory
8135 populated by default in Skolelinux. Thanks to it, I have been able to
8136 find empty and obsolete subtrees, misplaced objects and duplicate
8137 objects. It will be installed by default in Debian/Squeeze. If you
8138 are working with LDAP, give it a go. :)
</p
>
8140 <p
>I did notice one problem with it I have not had time to report to
8141 the BTS yet. There is no .desktop file in the package, so the tool do
8142 not show up in the Gnome and KDE menus, but only deep down in in the
8143 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8146 <p
>I have not yet been able to get it to modify the tree yet. I would
8147 like to move objects and remove subtrees directly in the GUI, but have
8148 not found a way to do that with LUMA yet. So in the mean time, I use
8149 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
8151 <p
>If you have tips on other GUI tools for LDAP that might be useful
8152 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
8154 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
8155 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
8156 useful GUI alternative. It seem like a good tool, but is unmaintained
8157 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8158 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
8163 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
8164 <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>
8165 <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>
8166 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
8167 <description><p
>A while back, I
8168 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
8169 about the fact
</a
> that it is not possible with the provided schemas
8170 for storing DNS and DHCP information in LDAP to combine the two sets
8171 of information into one LDAP object representing a computer.
</p
>
8173 <p
>In the mean time, I discovered that a simple fix would be to make
8174 the dhcpHost object class auxiliary, to allow it to be combined with
8175 the dNSDomain object class, and thus forming one object for one
8176 computer when storing both DHCP and DNS information in LDAP.
</p
>
8178 <p
>If I understand this correctly, it is not safe to do this change
8179 without also changing the assigned number for the object class, and I
8180 do not know enough about LDAP schema design to do that properly for
8181 Debian Edu.
</p
>
8183 <p
>Anyway, for future reference, this is how I believe we could change
8185 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
8186 schema
</a
> to solve at least part of the problem with the LDAP schemas
8187 available today from IETF.
</p
>
8190 --- dhcp.schema (revision
65192)
8191 +++ dhcp.schema (working copy)
8193 objectclass (
2.16.840.1.113719.1.203.6.6
8194 NAME
'dhcpHost
'
8195 DESC
'This represents information about a particular client
'
8199 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8200 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
8203 <p
>I very much welcome clues on how to do this properly for Debian
8204 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8205 package, and should thus be free to rewrite it as we see fit.
</p
>
8207 <p
>If you want to help out with implementing this for Debian Edu,
8208 please contact us on debian-edu@lists.debian.org.
</p
>
8213 <title>Calling tasksel like the installer, while still getting useful output
</title>
8214 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
8215 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
8216 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
8217 <description><p
>A few times I have had the need to simulate the way tasksel
8218 installs packages during the normal debian-installer run. Until now,
8219 I have ended up letting tasksel do the work, with the annoying problem
8220 of not getting any feedback at all when something fails (like a
8221 conffile question from dpkg or a download that fails), using code like
8224 <blockquote
><pre
>
8225 export DEBIAN_FRONTEND=noninteractive
8226 tasksel --new-install
8227 </pre
></blockquote
>
8229 This would invoke tasksel, let its automatic task selection pick the
8230 tasks to install, and continue to install the requested tasks without
8231 any output what so ever.
8233 Recently I revisited this problem while working on the automatic
8234 package upgrade testing, because tasksel would some times hang without
8235 any useful feedback, and I want to see what is going on when it
8236 happen. Then it occured to me, I can parse the output from tasksel
8237 when asked to run in test mode, and use that aptitude command line
8238 printed by tasksel then to simulate the tasksel run. I ended up using
8241 <blockquote
><pre
>
8242 export DEBIAN_FRONTEND=noninteractive
8243 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
8245 </pre
></blockquote
>
8247 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
8248 --without-recommends -o APT::Install-Recommends=no -y install
8249 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8250 ~pimportant
</tt
>", which will install the gnome desktop task, the
8251 laptop task and all packages with priority standard , required and
8252 important, just like tasksel would have done it during
8253 installation.
</p
>
8255 <p
>A better approach is probably to extend tasksel to be able to
8256 install packages without using debconf-apt-progress, for use cases
8257 like this.
</p
>
8262 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
8263 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
8264 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
8265 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
8266 <description><p
>My
8267 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
8268 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
8269 finally made the upgrade logs available from
8270 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
8271 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8272 apt and aptitude, and found their differences interesting. This time
8273 I will only focus on their removal plans.
</p
>
8275 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
8276 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
8277 surprising part is that it want to remove xorg and all
8278 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8279 sure why. When asking aptitude to do the same, it want to remove
129
8280 packages, but most of them are library packages I suspect are no
8281 longer needed. Both of them want to remove bluetooth packages, which
8282 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
8284 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
8285 which seem like a bad idea and xorg the same way as with Gnome. Asking
8286 aptitude for the same, it wants to remove
192 packages, none which are
8287 too surprising.
</p
>
8289 <p
>I guess the removal of xorg during upgrades should be investigated
8290 and avoided, and perhaps others as well. Here are the complete list
8291 of planned removals. The complete logs is available from the URL
8292 above. Note if you want to repeat these tests, that the upgrade test
8293 for kde+apt-get hung in the tasksel setup because of dpkg asking
8294 conffile questions. No idea why. I worked around it by using
8295 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
8298 <p
><b
>apt-get gnome
72</b
>
8299 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
8300 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8301 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
8302 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8303 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8304 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8305 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8306 xserver-xorg-input-kbd xserver-xorg-input-mouse
8307 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8308 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8309 xserver-xorg-video-ati xserver-xorg-video-chips
8310 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8311 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8312 xserver-xorg-video-glint xserver-xorg-video-i128
8313 xserver-xorg-video-i740 xserver-xorg-video-imstt
8314 xserver-xorg-video-intel xserver-xorg-video-mach64
8315 xserver-xorg-video-mga xserver-xorg-video-neomagic
8316 xserver-xorg-video-nsc xserver-xorg-video-nv
8317 xserver-xorg-video-openchrome xserver-xorg-video-r128
8318 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8319 xserver-xorg-video-rendition xserver-xorg-video-s3
8320 xserver-xorg-video-s3virge xserver-xorg-video-savage
8321 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8322 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8323 xserver-xorg-video-tga xserver-xorg-video-trident
8324 xserver-xorg-video-tseng xserver-xorg-video-v4l
8325 xserver-xorg-video-vesa xserver-xorg-video-vga
8326 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
8327 xulrunner-
1.9-gnome-support
</p
>
8329 <p
><b
>aptitude gnome
129</b
>
8331 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
8332 djvulibre-desktop finger gnome-app-install gnome-mount
8333 gnome-network-admin gnome-spell gnome-vfs-obexftp
8334 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8335 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8336 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8337 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
8338 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
8339 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
8340 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
8341 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
8342 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
8343 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
8344 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
8345 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
8346 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8347 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
8348 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
8349 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
8350 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
8351 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
8352 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8353 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8354 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8355 openoffice.org-writer2latex openssl-blacklist p7zip
8356 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
8357 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8358 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8359 swfdec-mozilla totem-gstreamer update-manager wodim
8360 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8361 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8364 <p
><b
>apt-get kde
82</b
>
8366 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8367 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8368 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8369 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8370 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8371 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8372 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8373 xserver-xorg-input-kbd xserver-xorg-input-mouse
8374 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8375 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8376 xserver-xorg-video-ati xserver-xorg-video-chips
8377 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8378 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8379 xserver-xorg-video-glint xserver-xorg-video-i128
8380 xserver-xorg-video-i740 xserver-xorg-video-imstt
8381 xserver-xorg-video-intel xserver-xorg-video-mach64
8382 xserver-xorg-video-mga xserver-xorg-video-neomagic
8383 xserver-xorg-video-nsc xserver-xorg-video-nv
8384 xserver-xorg-video-openchrome xserver-xorg-video-r128
8385 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8386 xserver-xorg-video-rendition xserver-xorg-video-s3
8387 xserver-xorg-video-s3virge xserver-xorg-video-savage
8388 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8389 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8390 xserver-xorg-video-tga xserver-xorg-video-trident
8391 xserver-xorg-video-tseng xserver-xorg-video-v4l
8392 xserver-xorg-video-vesa xserver-xorg-video-vga
8393 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
8395 <p
><b
>aptitude kde
192</b
>
8396 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
8397 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8398 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8399 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8400 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8401 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8402 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8403 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8404 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8405 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8406 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8407 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8408 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8409 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8410 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8411 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8412 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8413 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8414 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
8415 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8416 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8417 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
8418 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8419 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8420 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8421 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8422 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8423 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
8424 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
8425 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8426 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8427 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8428 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8429 texlive-common texlive-doc-base texlive-fonts-recommended
8430 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8431 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8432 xulrunner-
1.9</p
>
8438 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
8439 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
8440 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
8441 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
8442 <description><p
>The last few days I have done some upgrade testing in Debian, to
8443 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8444 have been discovered and reported in the process
8445 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
8446 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
8447 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
8448 kdebase-workspace-data), and to get a more regular testing going on, I
8449 am working on a script to automate the test.
</p
>
8451 <p
>The idea is to create a Lenny chroot and use tasksel to install a
8452 Gnome or KDE desktop installation inside the chroot before upgrading
8453 it. To ensure no services are started in the chroot, a policy-rc.d
8454 script is inserted. To make sure tasksel believe it is to install a
8455 desktop on a laptop, the tasksel tests are replaced in the chroot
8456 (only acceptable because this is a throw-away chroot).
</p
>
8458 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8459 currently always fail because udev refuses to upgrade with the kernel
8460 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8461 is created. The bug report
8462 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
8463 this problem do not trigger in a chroot, but I touch the file anyway
8464 to make sure the upgrade go well. Testing on virtual and real
8465 hardware have failed me because of udev so far, and creating this file
8466 do the trick in such settings anyway. This is a
8467 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
8468 issue
</a
> and the current udev behaviour is intended by the udev
8469 maintainer because he lack the resources to rewrite udev to keep
8470 working with old kernels or something like that. I really wish the
8471 udev upstream would keep udev backwards compatible, to avoid such
8472 upgrade problem, but given that they fail to do so, I guess
8473 documenting the way out of this mess is the best option we got for
8474 Debian Squeeze.
</p
>
8476 <p
>Anyway, back to the task at hand, testing upgrades. This test
8477 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
8480 <blockquote
><pre
>
8484 if [
"$
1" ] ; then
8493 exec
&lt; /dev/null
8495 mirror=http://ftp.skolelinux.org/debian
8496 tmpdir=chroot-$from-upgrade-$to-$desktop
8498 debootstrap $from $tmpdir $mirror
8499 chroot $tmpdir aptitude update
8500 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
8504 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8508 mount -t proc proc $tmpdir/proc
8509 # Make sure proc is unmounted also on failure
8510 trap exit_cleanup EXIT INT
8512 chroot $tmpdir aptitude -y install debconf-utils
8514 # Make sure tasksel autoselection trigger. It need the test scripts
8515 # to return the correct answers.
8516 echo tasksel tasksel/desktop multiselect $desktop | \
8517 chroot $tmpdir debconf-set-selections
8519 # Include the desktop and laptop task
8520 for test in desktop laptop ; do
8521 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
8525 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8528 DEBIAN_FRONTEND=noninteractive
8529 DEBIAN_PRIORITY=critical
8530 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8531 chroot $tmpdir tasksel --new-install
8533 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
8534 chroot $tmpdir aptitude update
8535 touch $tmpdir/etc/udev/kernel-upgrade
8536 chroot $tmpdir aptitude -y dist-upgrade
8538 </pre
></blockquote
>
8540 <p
>I suspect it would be useful to test upgrades with both apt-get and
8541 with aptitude, but I have not had time to look at how they behave
8542 differently so far. I hope to get a cron job running to do the test
8543 regularly and post the result on the web. The Gnome upgrade currently
8544 work, while the KDE upgrade fail because of the bug in
8545 kdebase-workspace-data
</p
>
8547 <p
>I am not quite sure what kind of extract from the huge upgrade logs
8548 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
8549 post, so I will refrain from trying. I can report that for Gnome,
8550 aptitude report
760 packages upgraded,
448 newly installed,
129 to
8551 remove and
1 not upgraded and
1024MB need to be downloaded while for
8552 KDE the same numbers are
702 packages upgraded,
507 newly installed,
8553 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
8555 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
8556 is able to migrate to dependency based boot sequencing and parallel
8557 booting without a hitch. Was unsure if there were still bugs with
8558 packages failing to clean up their obsolete init.d script during
8559 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8565 <title>Upstart or sysvinit - as init.d scripts see it
</title>
8566 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
8567 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
8568 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
8569 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
8570 scripts to migrate (some of) their operations to upstart job while
8571 keeping the init.d for hurd and kfreebsd. The packages with such
8572 needs will need a way to get their init.d scripts to behave
8573 differently when used with sysvinit and with upstart. Because of
8574 this, I had a look at the environment variables set when a init.d
8575 script is running under upstart, and when it is not.
</p
>
8577 <p
>With upstart, I notice these environment variables are set when a
8578 script is started from rcS.d/ (ignoring some irrelevant ones like
8581 <blockquote
><pre
>
8587 UPSTART_EVENTS=startup
8589 UPSTART_JOB=rc-sysinit
8590 </pre
></blockquote
>
8592 <p
>With sysvinit, these environment variables are set for the same
8595 <blockquote
><pre
>
8596 INIT_VERSION=sysvinit-
2.88
8601 </pre
></blockquote
>
8603 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
8604 sysvinit are not set by upstart. Not sure if it is intentional or not
8605 to not be compatible with sysvinit in this regard.
</p
>
8607 <p
>For scripts needing to behave differently when upstart is used,
8608 looking for the UPSTART_JOB environment variable seem to be a good
8614 <title>A manual for standards wars...
</title>
8615 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
8616 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
8617 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
8618 <description><p
>Via the
8619 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
8620 of Rob Weir
</a
> I came across the very interesting essay named
8621 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
8622 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
8623 following the standards wars of today.
</p
>
8628 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
8629 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
8630 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
8631 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
8632 <description><p
>When using sitesummary at a site to track machines, it is possible
8633 to get a list of the machine types in use thanks to the DMI
8634 information extracted from each machine. The script to do so is
8635 included in the sitesummary package, and here is example output from
8636 the Skolelinux build servers:
</p
>
8638 <blockquote
><pre
>
8639 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8641 Dell Computer Corporation
1
8644 eserver xSeries
345 -[
8670M1X]-
1
8648 </pre
></blockquote
>
8650 <p
>The quality of the report depend on the quality of the DMI tables
8651 provided in each machine. Here there are Intel machines without model
8652 information listed with Intel as vendor and no model, and virtual Xen
8653 machines listed as [no-dmi-info]. One can add -l as a command line
8654 option to list the individual machines.
</p
>
8656 <p
>A larger list is
8657 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
8658 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
8659 provide the basic sitesummary report publicly. In their report there
8660 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
8661 their machines, and as sitesummary is available in both distributions,
8662 it is trivial to get all of them to report to the same central
8663 collector.
</p
>
8668 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
8669 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
8670 <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>
8671 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
8672 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
8673 start at boot when an NVidia video card is used is handled. The
8674 problem seem to be that the nvidia X.org driver uses a long time to
8675 initialize, and this duration is longer than kdm is configured to
8678 <p
>I came across two bugs related to this issue,
8679 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
8680 against initscripts and passed on to nvidia-glx when it became obvious
8681 that the nvidia drivers were involved, and
8682 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
8683 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
8685 <p
>To me, it seem that no-one is interested in actually solving the
8686 problem nvidia video card owners experience and make sure the Debian
8687 distribution work out of the box for these users. The nvidia driver
8688 maintainers expect kdm to be set up to wait longer, while kdm expect
8689 the nvidia driver maintainers to fix the driver to start faster, and
8690 while they wait for each other I guess the users end up switching to a
8691 distribution that work for them. I have no idea what the solution is,
8692 but I am pretty sure that waiting for each other is not it.
</p
>
8694 <p
>I wonder why we end up handling bugs this way.
</p
>
8699 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
8700 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
8701 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
8702 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
8703 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
8704 The feature seem to hold up pretty well, but three fairly serious
8705 issues are known and should be solved:
8709 <li
>The wicd package seen to
8710 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
8711 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
8712 parallel booting is enabled. No idea why, but the wicd maintainer
8713 seem to be on the case.
</li
>
8715 <li
>The nvidia X driver seem to
8716 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
8717 triggered more easily when parallel booting is in effect. The
8718 maintainer is on the case.
</li
>
8720 <li
>The sysv-rc package fail to properly enable dependency based boot
8721 sequencing (the shutdown is broken) when old file-rc users
8722 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
8723 sysv-rc. One way to solve it would be for file-rc to create
8724 /etc/init.d/.legacy-bootordering, and another is to try to make
8725 sysv-rc more robust. Will investigate some more and probably upload a
8726 workaround in sysv-rc to help those trying to move from file-rc to
8727 sysv-rc get a working shutdown.
</li
>
8729 </ul
></p
>
8731 <p
>All in all not many surprising issues, and all of them seem
8732 solvable before Squeeze is released. In addition to these there are
8733 some packages with bugs in their dependencies and run level settings,
8734 which I expect will be fixed in a reasonable time span.
</p
>
8736 <p
>If you report any problems with dependencies in init.d scripts to
8737 the BTS, please usertag the report to get it to show up at
8738 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8739 list of usertagged bugs related to this
</a
>.
</p
>
8741 <p
>Update: Correct bug number to file-rc issue.
</p
>
8746 <title>More flexible firmware handling in debian-installer
</title>
8747 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
8748 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
8749 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
8750 <description><p
>After a long break from debian-installer development, I finally
8751 found time today to return to the project. Having to spend less time
8752 working dependency based boot in debian, as it is almost complete now,
8753 definitely helped freeing some time.
</p
>
8755 <p
>A while back, I ran into a problem while working on Debian Edu. We
8756 include some firmware packages on the Debian Edu CDs, those needed to
8757 get disk and network controllers working. Without having these
8758 firmware packages available during installation, it is impossible to
8759 install Debian Edu on the given machine, and because our target group
8760 are non-technical people, asking them to provide firmware packages on
8761 an external medium is a support pain. Initially, I expected it to be
8762 enough to include the firmware packages on the CD to get
8763 debian-installer to find and use them. This proved to be wrong.
8764 Next, I hoped it was enough to symlink the relevant firmware packages
8765 to some useful location on the CD (tried /cdrom/ and
8766 /cdrom/firmware/). This also proved to not work, and at this point I
8767 found time to look at the debian-installer code to figure out what was
8768 going to work.
</p
>
8770 <p
>The firmware loading code is in the hw-detect package, and a closer
8771 look revealed that it would only look for firmware packages outside
8772 the installation media, so the CD was never checked for firmware
8773 packages. It would only check USB sticks, floppies and other
8774 "external
" media devices. Today I changed it to also look in the
8775 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8776 solve the problem I ran into with Debian edu. I also changed it to
8777 look in /firmware/, to make sure the installer also find firmware
8778 provided in the initrd when booting the installer via PXE, to allow us
8779 to provide the same feature in the PXE setup included in Debian
8782 <p
>To make sure firmware deb packages with a license questions are not
8783 activated without asking if the license is accepted, I extended
8784 hw-detect to look for preinst scripts in the firmware packages, and
8785 run these before activating the firmware during installation. The
8786 license question is asked using debconf in the preinst, so this should
8787 solve the issue for the firmware packages I have looked at so far.
</p
>
8789 <p
>If you want to discuss the details of these features, please
8790 contact us on debian-boot@lists.debian.org.
</p
>
8795 <title>Parallellized boot is now the default in Debian/unstable
</title>
8796 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
8797 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
8798 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
8799 <description><p
>Since this evening, parallel booting is the default in
8800 Debian/unstable for machines using dependency based boot sequencing.
8801 Apparently the testing of concurrent booting has been wider than
8802 expected, if I am to believe the
8803 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8804 on debian-devel@
</a
>, and I concluded a few days ago to move forward
8805 with the feature this weekend, to give us some time to detect any
8806 remaining problems before Squeeze is frozen. If serious problems are
8807 detected, it is simple to change the default back to sequential boot.
8808 The upload of the new sysvinit package also activate a new upstream
8811 More information about
8812 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8813 based boot sequencing
</a
> is available from the Debian wiki. It is
8814 currently possible to disable parallel booting when one run into
8815 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
8817 <blockquote
><pre
>
8819 </pre
></blockquote
>
8821 <p
>If you report any problems with dependencies in init.d scripts to
8822 the BTS, please usertag the report to get it to show up at
8823 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8824 list of usertagged bugs related to this
</a
>.
</p
>
8829 <title>Sitesummary tip: Listing MAC address of all clients
</title>
8830 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
8831 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
8832 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
8833 <description><p
>In the recent Debian Edu versions, the
8834 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
8835 system
</a
> is used to keep track of the machines in the school
8836 network. Each machine will automatically report its status to the
8837 central server after boot and once per night. The network setup is
8838 also reported, and using this information it is possible to get the
8839 MAC address of all network interfaces in the machines. This is useful
8840 to update the DHCP configuration.
</p
>
8842 <p
>To give some idea how to use sitesummary, here is a one-liner to
8843 ist all MAC addresses of all machines reporting to sitesummary. Run
8844 this on the collector host:
</p
>
8846 <blockquote
><pre
>
8847 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
8848 </pre
></blockquote
>
8850 <p
>This will list all MAC addresses assosiated with all machine, one
8851 line per machine and with space between the MAC addresses.
</p
>
8853 <p
>To allow system administrators easier job at adding static DHCP
8854 addresses for hosts, it would be possible to extend this to fetch
8855 machine information from sitesummary and update the DHCP and DNS
8856 tables in LDAP using this information. Such tool is unfortunately not
8857 written yet.
</p
>
8862 <title>systemd, an interesting alternative to upstart
</title>
8863 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
8864 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
8865 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
8866 <description><p
>The last few days a new boot system called
8867 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
8869 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
8871 to the free software world. I have not yet had time to play around
8872 with it, but it seem to be a very interesting alternative to
8873 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
8874 a good alternative for Debian when we are able to switch to an event
8875 based boot system. Tollef is
8876 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
8877 systemd into Debian, and I look forward to seeing how well it work. I
8878 like the fact that systemd handles init.d scripts with dependency
8879 information natively, allowing them to run in parallel where upstart
8880 at the moment do not.
</p
>
8882 <p
>Unfortunately do systemd have the same problem as upstart regarding
8883 platform support. It only work on recent Linux kernels, and also need
8884 some new kernel features enabled to function properly. This means
8885 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8886 system. Not sure how that will be handled if systemd proves to be the
8887 way forward.
</p
>
8889 <p
>In the mean time, based on the
8890 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8891 on debian-devel@
</a
> regarding parallel booting in Debian, I have
8892 decided to enable full parallel booting as the default in Debian as
8893 soon as possible (probably this weekend or early next week), to see if
8894 there are any remaining serious bugs in the init.d dependencies. A
8895 new version of the sysvinit package implementing this change is
8896 already in experimental. If all go well, Squeeze will be released
8897 with parallel booting enabled by default.
</p
>
8902 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
8903 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
8904 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
8905 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
8906 <description><p
>These days, the init.d script dependencies in Squeeze are quite
8907 complete, so complete that it is actually possible to run all the
8908 init.d scripts in parallell based on these dependencies. If you want
8909 to test your Squeeze system, make sure
8910 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8911 based boot sequencing
</a
> is enabled, and add this line to
8912 /etc/default/rcS:
</p
>
8914 <blockquote
><pre
>
8915 CONCURRENCY=makefile
8916 </pre
></blockquote
>
8918 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
8919 scripts in parallel using the dependency information stored in
8920 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8921 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8922 to try to start the kdm and gdm scripts as early as possible, and will
8923 start the facilities required by kdm or gdm as early as possible to
8924 make this happen.
</p
>
8926 <p
>Give it a try, and see if you like the result. If some services
8927 fail to start properly, it is most likely because they have incomplete
8928 init.d script dependencies in their startup script (or some of their
8929 dependent scripts have incomplete dependencies). Report bugs and get
8930 the package maintainers to fix it. :)
</p
>
8932 <p
>Running scripts in parallel could be the default in Debian when we
8933 manage to get the init.d script dependencies complete and correct. I
8934 expect we will get there in Squeeze+
1, if we get manage to test and
8935 fix the remaining issues.
</p
>
8937 <p
>If you report any problems with dependencies in init.d scripts to
8938 the BTS, please usertag the report to get it to show up at
8939 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8940 list of usertagged bugs related to this
</a
>.
</p
>
8945 <title>Debian has switched to dependency based boot sequencing
</title>
8946 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
8947 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
8948 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
8949 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
8950 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
8951 have been migrated to using dependency based boot sequencing. This
8952 conclude work me and others have been doing for the last three days.
8953 It feels great to see this finally part of the default Debian
8954 installation. Now we just need to weed out the last few problems that
8955 are bound to show up, to get everything ready for Squeeze.
</p
>
8957 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
8958 fixing the more fundamental problem of handing the event based
8959 non-predictable kernel in the early boot.
</p
>
8964 <title>Taking over sysvinit development
</title>
8965 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
8966 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
8967 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
8968 <description><p
>After several years of frustration with the lack of activity from
8969 the existing sysvinit upstream developer, I decided a few weeks ago to
8970 take over the package and become the new upstream. The number of
8971 patches to track for the Debian package was becoming a burden, and the
8972 lack of synchronization between the distribution made it hard to keep
8973 the package up to date.
</p
>
8975 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8976 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
8977 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
8978 and Fedora), based on the patches currently in use in these
8979 distributions. We Debian maintainers plan to move to this tarball as
8980 the new upstream as soon as we find time to do the merge. Since the
8981 new tarball was created, we agreed with Werner at SuSe to make a new
8982 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
8983 development there. The project is registered and currently waiting
8984 for approval by the Savannah administrators, and as soon as it is
8985 approved, we will import the old versions from svn and continue
8986 working on the future release.
</p
>
8988 <p
>It is a bit ironic that this is done now, when some of the involved
8989 distributions are moving to upstart as a syvinit replacement.
</p
>
8994 <title>Debian boots quicker and quicker
</title>
8995 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
8996 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
8997 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
8998 <description><p
>I spent Monday and tuesday this week in London with a lot of the
8999 people involved in the boot system on Debian and Ubuntu, to see if we
9000 could find more ways to speed up the boot system. This was an Ubuntu
9002 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9003 gathering
</a
>. It was quite productive. We also discussed the future
9004 of boot systems, and ways to handle the increasing number of boot
9005 issues introduced by the Linux kernel becoming more and more
9006 asynchronous and event base. The Ubuntu approach using udev and
9007 upstart might be a good way forward. Time will show.
</p
>
9009 <p
>Anyway, there are a few ways at the moment to speed up the boot
9010 process in Debian. All of these should be applied to get a quick
9015 <li
>Use dash as /bin/sh.
</li
>
9017 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9018 clock is in UTC.
</li
>
9020 <li
>Install and activate the insserv package to enable
9021 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9022 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9026 These points are based on the Google summer of code work done by
9027 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9030 <p
>Support for makefile-style concurrency during boot was uploaded to
9031 unstable yesterday. When we tested it, we were able to cut
6 seconds
9032 from the boot sequence. It depend on very correct dependency
9033 declaration in all init.d scripts, so I expect us to find edge cases
9034 where the dependences in some scripts are slightly wrong when we start
9035 using this.
</p
>
9037 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9038 introduced by Raphael Geissert today, one that could affect the
9039 startup speed as well. Instead of starting some scripts concurrently
9040 from rcS.d/ and another set of scripts from rc2.d/, it would be
9041 possible to run a of them in the same process. A quick way to test
9042 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9043 insserv
'. Will need to test if that work. :)
</p
>
9048 <title>BSAs påstander om piratkopiering møter motstand
</title>
9049 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
9050 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
9051 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
9052 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
9053 programvareselskapene som Microsoft og Apple, publisert en rapport der
9054 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9055 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9057 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
9058 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
9059 dagene. Et spesielt interessant kommentar fra Sverige,
9060 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
9061 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
9064 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
9065 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9066 företag.
"Man bör nog kanske inte se de här siffrorna som helt
9067 exakta
", säger BSAs Sverigechef John Hugosson.
9070 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
9071 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
9072 piracy figures need a shot of reality
</a
> og
<a
9073 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
9074 Copyright Treaty Work?
</a
></p
>
9076 <p
>Fant lenkene via
<a
9077 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
9078 på Slashdot
</a
>.
</p
>
9083 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
9084 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
9085 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
9086 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
9087 <description><p
>Kom over
9088 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
9089 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9090 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9091 jobber til daglig. En rask opptelling forteller meg at vi har
490
9092 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
9093 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
9094 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
9099 <title>Kryptert harddisk - naturligvis
</title>
9100 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
9101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
9102 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
9103 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
9104 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
9105 når en tar tap av arbeidstid, fortrolige dokumenter,
9106 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9107 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9108 til at jeg har kryptert harddisken på både kontormaskinen og min
9109 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9110 komme på avveie, den første informasjon relatert til jobben min ved
9111 Universitetet i Oslo, og den andre relatert til blant annet
9112 foreningsarbeide. Kryptering av diskene gjør at det er lite
9113 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9114 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9115 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9116 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9117 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9118 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9119 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9120 det er gjort slik jeg gjør det er minimale, og gevinstene er
9121 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9122 maskinen reinstalleres og alt er tapt.
</p
>
9124 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9125 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9126 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9127 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9128 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9129 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9130 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9131 betydelige.
</p
>
9136 <title>Two projects that have improved the quality of free software a lot
</title>
9137 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
9138 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
9139 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
9140 <description><p
>There are two software projects that have had huge influence on the
9141 quality of free software, and I wanted to mention both in case someone
9142 do not yet know them.
</p
>
9144 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
9145 tool to detect and expose errors in the memory handling of programs.
9146 It is easy to use, all one need to do is to run
'valgrind program
',
9147 and it will report any problems on stdout. It is even better if the
9148 program include debug information. With debug information, it is able
9149 to report the source file name and line number where the problem
9150 occurs. It can report things like
'reading past memory block in file
9151 X line N, the memory block was allocated in file Y, line M
', and
9152 'using uninitialised value in control logic
'. This tool has made it
9153 trivial to investigate reproducible crash bugs in programs, and have
9154 reduced the number of this kind of bugs in free software a lot.
9156 <p
>The second one is
9157 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
9158 a source code checker. It is able to process the source of a program
9159 and find problems in the logic without running the program. It
9160 started out as the Stanford Checker and became well known when it was
9161 used to find bugs in the Linux kernel. It is now a commercial tool
9162 and the company behind it is running
9163 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
9164 free software community, where a lot of free software projects get
9165 their source checked for free. Several thousand defects have been
9166 found and fixed so far. It can find errors like
'lock L taken in file
9167 X line N is never released if exiting in line M
', or
'the code in file
9168 Y lines O to P can never be executed
'. The projects included in the
9169 community service project have managed to get rid of a lot of
9170 reliability problems thanks to Coverity.
</p
>
9172 <p
>I believe tools like this, that are able to automatically find
9173 errors in the source, are vital to improve the quality of software and
9174 make sure we can get rid of the crashing and failing software we are
9175 surrounded by today.
</p
>
9180 <title>No patch is not better than a useless patch
</title>
9181 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
9182 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
9183 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
9184 <description><p
>Julien Blache
9185 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
9186 patch is better than a useless patch
</a
>. I completely disagree, as a
9187 patch allow one to discuss a concrete and proposed solution, and also
9188 prove that the issue at hand is important enough for someone to spent
9189 time on fixing it. No patch do not provide any of these positive
9190 properties.
</p
>
9195 <title>Standardize on protocols and formats, not vendors and applications
</title>
9196 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
9197 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
9198 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
9199 <description><p
>Where I work at the University of Oslo, one decision stand out as a
9200 very good one to form a long lived computer infrastructure. It is the
9201 simple one, lost by many in todays computer industry: Standardize on
9202 open network protocols and open exchange/storage formats, not applications.
9203 Applications come and go, while protocols and files tend to stay, and
9204 thus one want to make it easy to change application and vendor, while
9205 avoiding conversion costs and locking users to a specific platform or
9206 application.
</p
>
9208 <p
>This approach make it possible to replace the client applications
9209 independently of the server applications. One can even allow users to
9210 use several different applications as long as they handle the selected
9211 protocol and format. In the normal case, only one client application
9212 is recommended and users only get help if they choose to use this
9213 application, but those that want to deviate from the easy path are not
9214 blocked from doing so.
</p
>
9216 <p
>It also allow us to replace the server side without forcing the
9217 users to replace their applications, and thus allow us to select the
9218 best server implementation at any moment, when scale and resouce
9219 requirements change.
</p
>
9221 <p
>I strongly recommend standardizing - on open network protocols and
9222 open formats, but I would never recommend standardizing on a single
9223 application that do not use open network protocol or open formats.
</p
>
9228 <title>Returning from Skolelinux developer gathering
</title>
9229 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
9230 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
9231 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
9232 <description><p
>I
'm sitting on the train going home from this weekends Debian
9233 Edu/Skolelinux development gathering. I got a bit done tuning the
9234 desktop, and looked into the dynamic service location protocol
9235 implementation avahi. It look like it could be useful for us. Almost
9236 30 people participated, and I believe it was a great environment to
9237 get to know the Skolelinux system. Walter Bender, involved in the
9238 development of the Sugar educational platform, presented his stuff and
9239 also helped me improve my OLPC installation. He also showed me that
9240 his Turtle Art application can be used in standalone mode, and we
9241 agreed that I would help getting it packaged for Debian. As a
9242 standalone application it would be great for Debian Edu. We also
9243 tried to get the video conferencing working with two OLPCs, but that
9244 proved to be too hard for us. The application seem to need more work
9245 before it is ready for me. I look forward to getting home and relax
9251 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
9252 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
9253 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
9254 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
9255 <description><p
>The state of standardized LDAP schemas on Linux is far from
9256 optimal. There is RFC
2307 documenting one way to store NIS maps in
9257 LDAP, and a modified version of this normally called RFC
2307bis, with
9258 some modifications to be compatible with Active Directory. The RFC
9259 specification handle the content of a lot of system databases, but do
9260 not handle DNS zones and DHCP configuration.
</p
>
9262 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
9263 we would like to store information about users, SMB clients/hosts,
9264 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9265 and LTSP configuration in LDAP. These objects have a lot in common,
9266 but with the current LDAP schemas it is not possible to have one
9267 object per entity. For example, one need to have at least three LDAP
9268 objects for a given computer, one with the SMB related stuff, one with
9269 DNS information and another with DHCP information. The schemas
9270 provided for DNS and DHCP are impossible to combine into one LDAP
9271 object. In addition, it is impossible to implement quick queries for
9272 netgroup membership, because of the way NIS triples are implemented.
9273 It just do not scale. I believe it is time for a few RFC
9274 specifications to cleam up this mess.
</p
>
9276 <p
>I would like to have one LDAP object representing each computer in
9277 the network, and this object can then keep the SMB (ie host key), DHCP
9278 (mac address/name) and DNS (name/IP address) settings in one place.
9279 It need to be efficently stored to make sure it scale well.
</p
>
9281 <p
>I would also like to have a quick way to map from a user or
9282 computer and to the net group this user or computer is a member.
</p
>
9284 <p
>Active Directory have done a better job than unix heads like myself
9285 in this regard, and the unix side need to catch up. Time to start a
9286 new IETF work group?
</p
>
9291 <title>Endelig er Debian Lenny gitt ut
</title>
9292 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
9293 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
9294 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
9295 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
9296 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
9297 Et langt steg videre for Debian-prosjektet, og en rekke nye
9298 programpakker blir nå tilgjengelig for de av oss som bruker den
9299 stabile utgaven av Debian. Neste steg er nå å få
9300 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
9301 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
9302 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9303 slippes løs på skolene. Takk til alle debian-utviklerne som har
9304 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9305 bootsekvens tilgjengelig i stabil utgave, vha pakken
9306 <tt
>insserv
</tt
>.
</p
>
9311 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
9312 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
9313 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
9314 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
9315 <description><p
>This weekend we had a small developer gathering for Debian Edu in
9316 Oslo. Most of Saturday was used for the general assemly for the
9317 member organization, but the rest of the weekend I used to tune the
9318 LTSP installation. LTSP now work out of the box on the
10-network.
9319 Acer Aspire One proved to be a very nice thin client, with both
9320 screen, mouse and keybard in a small box. Was working on getting the
9321 diskless workstation setup configured out of the box, but did not
9322 finish it before the weekend was up.
</p
>
9324 <p
>Did not find time to look at the
4 VGA cards in one box we got from
9325 the Brazilian group, so that will have to wait for the next
9326 development gathering. Would love to have the Debian Edu installer
9327 automatically detect and configure a multiseat setup when it find one
9328 of these cards.
</p
>
9333 <title>The sorry state of multimedia browser plugins in Debian
</title>
9334 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
9335 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
9336 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
9337 <description><p
>Recently I have spent some time evaluating the multimedia browser
9338 plugins available in Debian Lenny, to see which one we should use by
9339 default in Debian Edu. We need an embedded video playing plugin with
9340 control buttons to pause or stop the video, and capable of streaming
9341 all the multimedia content available on the web. The test results and
9342 notes are available on
9343 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
9344 Debian wiki
</a
>. I was surprised how few of the plugins are able to
9345 fill this need. My personal video player favorite, VLC, has a really
9346 bad plugin which fail on a lot of the test pages. A lot of the MIME
9347 types I would expect to work with any free software player (like
9348 video/ogg), just do not work. And simple formats like the
9349 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
9350 totem and vlc plugins. I hope the situation will improve soon. No
9351 wonder sites use the proprietary Adobe flash to play video.
</p
>
9353 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
9354 be the only one fitting our needs. :/
</p
>